Open TryHardDieHard opened 9 years ago
My guess is that the LilDebi install filled up your /data
partition entirely. Having /data
100% full will make your phone do that. That happened to @SDkie while he was working on the "internal storage" support. Lil' Debi is supposed to check whether there is enough space in /data
for the install.
In any case, it is very hard to say what happened without the install log. @TryHardDieHard if you can get the install log from /data/data/info.guardianproject.lildebi/app_log/install.log
that would be very helpful in figuring out what happened.
Sorry, I already deleted everything and re-flashed the phone. I can't get the error logs.
On 04/14/2015 11:36 AM, Hans-Christoph Steiner wrote:
My guess is that the LilDebi install filled up your /data partition entirely. Having /data 100% full will make your phone do that. That happened to @SDkie https://github.com/SDkie while he was working on the "internal storage" support. Lil' Debi is supposed to check whether there is enough space in /data for the install.
In any case, it is very hard to say what happened without the install log. @TryHardDieHard https://github.com/TryHardDieHard if you can get the install log from /data/data/info.guardianproject.lildebi/app_log/install.log that would be very helpful in figuring out what happened.
— Reply to this email directly or view it on GitHub https://github.com/guardianproject/lildebi/issues/170#issuecomment-92964077 .
I attempted to install lil deb on my Samsung Galaxy S3 i9300 with Replicant 4.2 002. During the installation process, the phone rebooted and the Replicant boot image appeared. The phone is stuck in this state and won't boot fully.