I have an old DINC that I've used over the years primarily for reading Kindle books and for network troubleshooting. I've been through the CyanogenMod ROMs from 9 to 11, and Evervolv KK. I have TWRP 2.0 installed.
I recently got a Google Cardboard VR viewer, and when I tried to install some software for it from the Play store, I got the bogus "Insufficient space" message, even though the only non-ROM app installed was Kindle and ES File Explorer, and there was. That's when the fun began.
I tried reinstalling ev_inc-4.0.0, using my standard procedure of Factory Reset, Flash ROM and GAPPS, clear dalvik cache and reboot. That got stuck in a boot loop, and then I started to work my way backwards through CM 11, 10.2, 10.1, 10.0, still with either a boot loop or a crash as soon as I tried to turn WIFI on. (At this point I am only flashing the ROM, not GAPPS until I'm convinced the ROM will work).
Finally, I got a copy of Stock_inc_4.08.605.16_deodexed.zip and flashed it with TWRP as usual. It actually seemed to work OK for a while, but still would not install the VR program (insufficient space).
Then I began think about how much of a mess I have probably left lying around nooks and crannies of memory, so I took every "erase" option I could find in TWRP and the boot loader, then went into fastboot:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip ______
fastboot reboot
That worked once, to get the Stock ROM running, but still could not install any software.
Before this all started I made a backup with TWRP. When I restore from that backup, I get a running ROM, but with an ancient version of PlayStore (actually "Market!), and when I try to run that, I get a very long license agreement, with no "OK" button - no way out!
I think I need to somehow get the DINC back to some known place and start fresh, but I'm out of ideas. Please help, someone!
Walt
Ive seen a fix patch for this issue somewhere around here. I just stumbled across it, so you should be able to find it easy, if you already have not.
Hello everyone!
I have just recently installed TWRP recovery on my L-09 and attempted to install OpenKirin's RROS from around here. Although the installation seemed to work fine at first, the device was stuck on the roms bootanimation. As such, I did what I would always do in this case, and try to recover my backup that I made through TWRP. Unfortunately though, that dos not boot up either.
Since then I have spent literal hours trying to find a way to make the phone boot , including trying to flash Moonlight and Magic Rainbow to no avail. I tried everything, flashing back to stock recovery, or the inbuilt erecovery or however it is call, nothing works. I have also tried to flash with the dload method, the installation fails with the file I found.
TWRP still seems to work, as does Fastboot mode and everything, so I have a feeling the situation should be salvagable.
Anyone with any better ideas? I have spent sooo long on this and I am on the end of my sanity
Thanks in advance!
Ok, Update: I have found an image that seemed to work with the dload method, but it is still stuck on the "Your device is booting now" screen..
Hello all before I describe my issue lemme tell you how I got there.
First of all, new phone, couldn't install pixelexperience and flashing stock android was being a pain with all methods (read not working), only managed to install stock android with pitch black recovery.
After a while it auto updated to android 9 and I started having wifi issues that people told me were android's fault so I waited for an update. Update came but android was unable to install it, giving errors after errors every time it downloaded the update.
My solution to all of this was to flash another rom, either stock or custom, and pray it works. It was scheduled to happen in 2 days, when I had free time.
Today, when trying to change the permission for a text file for an app from read only to write, some random process crashed, and it triggered a crashing cascade, including the settings app, homescreen launcher, etc until the phone restarted and got stuck in TWRP logo screen.
No key press, combination, resets, etc would fix it. So I got into fastboot and tried a few things with no luck. Flash stock rom again and phone seemed to be working.
Magisk manager couldn't install magisk and root the phone so I went into stock recovery/twrp and every time I did it I got a black screen message saying something like this:
"Your phone/system is corrupt and won't boot ever again *evil laugh*. Oh btw, go to this link in another device to cry more"
and the link redirects to a google page with some non-useful info.
So here I am, unable to root, unable to go into recovery, phone boots though. I force-stoped updates for a while, as android 9 wifi issues were terrible, and I don't know how to proceed.
Do I flash a stock image again, a custom one, try another rooting method?
I don't want to brick a 6month old phone, really sucks.
Btw, is there a reliable way to back up everything in the phone ?(not only google stuff, but app configs and files/folders) Long time ago I read something about Titanium backup but never looked into it further and now with this crash that lost me everything I wanna prepare for the future.
Thanks for all the help and for reading my boring story.
Even I am facing same problem.. In my case my phone is rooted and I cnt flash TWRP and I cnt get into fastboot mode.. I alwys endup with black screen..
I thought I had finally reached nirvana with this device thanks to the help of so many here. I had TWRP, root, defeated encryption, and a nicely running Android. I was even able to make TWRP backups of /data and /boot (to be precise, at one point - not sure when it was but I think after initial Android setup - I was able to make a much more complete TWRP backup with many partitions never shown again but that disappeared at some point).
So I went on with my transition from my old Note3 phone to this device. I spent all day yesterday moving TiBackups of user apps, copying across data, making more limited TWRP backups (of data and boot the only options - except if I mounted system_root, which allowed me to include /system but that did not actually work either), polishing settings, and thinking I had it made! Throughout all of this I had no problems or signs of problems other than some apps not working on the new device and having to be replaced with alternatives which I completely expected.
At cocktail hour I decided to do a reboot to see the "finished product" of all this effort. When I did, the device tried to boot into Android: I saw the thinq logo but no boot animation, just the thinq logo for a very long time - followed by a screen blank and bootloop. I was able to enter TWRP and things looked "normal" from there. I kept trying to boot into system with no progress. I tried wiping /data, I tried restoring the backups I had made. Nothing changed - still bootlooping.
From within TWRP I can use adb shell to look around. I can see familiar stuff from my installed apps in /data/data and /data/app - including from one of the very last apps I installed (from Play not via TiBackup). I know this was not in any TWRP backup I had taken or restored. So this makes me think that my attempts to restore /data from backups or even wiping /data from TWRP have had no effect despite no errors showing. I wanted to see what was in /system so I mounted system and now in adb shell I can see familiar stuff in there too - including busybox installed into xbin. I can also mount vendor and in /vendor/etc I can see the fstab.judypn with encryptable for /data.
One thing I do NOT see is the result of one of the last things I did/tested. I installed Termux, installed the dropbear package, and copied the resulting dbclient binary to /data/local. After doing this I actually invoked /data/local/dbclient with success. Now, I do not see anything in /data/data/com.termux/files/usr related to dropbear nor do I see the dbclient in /data/local.
When I tried to power off from TWRP, the device never fully turned off. The animation showing the power level remained showing all the time but it was just a circle with lightening bolt but no actual power level showing. Removing power cable made no difference. Finally, I left the device in TWRP and powered on. At least I could blank the screen and prevent the battery from running dry.
All of this is with slot A current as reported by TWRP. I cannot seem to enter fastboot mode (I was previously able to do this from a power off condition by holding volume up and inserting USB). Of course, I am not able to achieve a real powered-off condition. Thankfully, I am still able to enter engineering mode and see the device in QFIL. But I have not tried anything here as of now. I can switch to slot b and get into download mode by holding power up and inserting USB. All attempts to use other TWRP boot options (save recovery and "power off") just put me into bootloop again.
I am stumped as to what is happening, how to "fix" this, or what to do.
Thanks for any suggestions.
Same thing happened to me. Yesterday.
I was going through my system programs, and nuked several of the extra Google Play items (Movies, Music, etc.). Same thing. Boot to V40 ThinkQ screen. Sat there for a while. Then reboot.
Nothing I did brought the old girl back to life. So I started over with kdz and redid everything again. Pain in the ass, but it's working again. Interestingly enough, loading the full kdz didn't relock the bootloader. I used both Refurbish and Partition DL on two separate attempts. Bootloader stayed unlocked throughout, and is still unlocked.
Had a devil of a time getting system to mount. Tried over and over again to get Magisk installed.
What finally worked was rebooting into recovery after pushing the .magisk file, and only then installing Magisk.
[NG]Owner
NGOwner said:
Same thing happened to me. Yesterday.
I was going through my system programs, and nuked several of the extra Google Play items (Movies, Music, etc.). Same thing. Boot to V40 ThinkQ screen. Sat there for a while. Then reboot.
Nothing I did brought the old girl back to life. So I started over with kdz and redid everything again. Pain in the ass, but it's working again. Interestingly enough, loading the full kdz didn't relock the bootloader. I used both Refurbish and Partition DL on two separate attempts. Bootloader stayed unlocked throughout, and is still unlocked.
Had a devil of a time getting system to mount. Tried over and over again to get Magisk installed.
What finally worked was rebooting into recovery after pushing the .magisk file, and only then installing Magisk.
[NG]Owner
Click to expand...
Click to collapse
Well, they say misery loves company and I do feel a bit better just knowing I am not alone here.
Since I could enter download mode, I too decided to try re-flashing the .kdz using LGUP's partition dl and specifically NOT checking boot_a, laf_a or boot_b as described here <https://forum.xda-developers.com/showpost.php?p=82206107&postcount=115>. I was not fast enough to get into TWRP on the automatic reboot and saw that I was brought to a bootable system and an Android start page with the boot loader still locked and TWRP still there.
So did the partition dl again and managed to catch TWRP. I mounted vendor but when I tried to push the fstab I got something I have not seen before "remote could not create file: Read-only file system" and 0 files pushed. To be sure, I used adb shell and cat'ed /vendor/etc/fstab.judypn and it contains force encrypt. So I know things are not quite right.
Trying again from the partition dl. And this time I managed the push. I think I missed re-doing the ramdisk and rebooting into recovery. I made sure to do that this time and now I can proceed. I seem to have managed to get back to a bootable Android with TWRP, Magisk, and defeated encryption once again.
So I wonder if I should try to restore anything from a backup or just redo all of yesterday's efforts (like the movie Groundhog Day)?
Can I ask which device and firmware you are using? Thanks
I would not use any backups aside from the backups in your google account. Redo all of yesterday's efforts (except the one thing that caused the reboot loop ... whatever that was!).
You said your bootloader was relocked after LGUP? Or did you mistype there?
Odd. Mine wasn't, not once. Despite multiple LGUP loads.
I've got a crossflashed Sprint LM-V405UA to US specs 20E.
And yes, misery does love company!
[NG]Owner
NGOwner said:
I would not use any backups aside from the backups in your google account. Redo all of yesterday's efforts (except the one thing that caused the reboot loop ... whatever that was!).
You said your bootloader was relocked after LGUP? Or did you mistype there?
Odd. Mine wasn't, not once. Despite multiple LGUP loads.
I've got a crossflashed Sprint LM-V405UA to US specs 20E.
And yes, misery does love company!
[NG]Owner
Click to expand...
Click to collapse
No, you are correct - I mistyped. My bootloader has remained unlocked (this time I got it right)
Nor sure it matters any, but mine if a 405QA with 20E.
I have read some recently (while searching for this bootloop problem) that LG seems to have long had a problem with bootloops on their devices. Not sure I saw anything specifically about the V40 though. Seems that in the past they were "fixed" with software updates. I do not expect any updates beyond 20E and wonder if 20a (which I think I had earlier) would be any different/better.
I have had great luck with Nandroid and TWRP backups in the past. They have really saved me (most often from myself but also from apps/mods gone wild). Indeed, I used TWRP restore yesterday with the previous night's auto-made backup on my Note 3. It seems that in doing something - maybe the TiBackup of all user apps/data - the phone got messed up and even reboots would not fix it. The TWRP restore certainly did!
I am new to the whole Magisk "systemless" root as I have always used SuperSu before. As I understand it (which is limited for sure) the idea here is to NOT modify system in any way. But I also note that this does not seem to preclude me from modifying things in system using my file manager, for example. And I did some of this sort of thing. If you are nuking pre-installed apps, that would be changing system as well, no? I wonder if that is the activity that caused this?
I am a bit hesitant to re-live yesterday. At least not until I have some idea of what I did that caused this. Not sure what I will do.
Thanks for all the help.
PS - given that I had TWRP backup (of at least /data) and how often I rely upon these in everyday life, I decided to at least try restoring and see what happened. Hard to imagine ending up worse that I was earlier this morning. I did the restore and rebooted to system. I was shocked, quite frankly, to see the system come right up and have many of my previously installed apps visible and working. I did find that I had to re-enable the modules in EdXposed (even though they showed as enabled already) since they were not working) and that brought them back to life.
So I guess I can move forward from here being careful, taking TWRP backups even more often, and rebooting more often to see what, if anything, kills this again.
NGOwner said:
Same thing happened to me. Yesterday.
I was going through my system programs, and nuked several of the extra Google Play items (Movies, Music, etc.). Same thing. Boot to V40 ThinkQ screen. Sat there for a while. Then reboot.
Nothing I did brought the old girl back to life. So I started over with kdz and redid everything again. Pain in the ass, but it's working again. Interestingly enough, loading the full kdz didn't relock the bootloader. I used both Refurbish and Partition DL on two separate attempts. Bootloader stayed unlocked throughout, and is still unlocked.
Had a devil of a time getting system to mount. Tried over and over again to get Magisk installed.
What finally worked was rebooting into recovery after pushing the .magisk file, and only then installing Magisk.
[NG]Owner
Click to expand...
Click to collapse
Well, this happened to me once again. I saw no reason why it should not do so. So I have been re-introducing apps from my TiBackup slowly and in under a strict protocol in an effort to (a) limit the damage done to my work and (b) try to isolate the culprit(s). I decided, since I found that I could restore TWRP backups of /data after re-doing the most of the TWRP install and defeat encryption process, that I would install apps slowly and execute them and in small groups. After each group I would do a reboot to see if that worked. If that worked, I would go into TWRP, run a backup, and name the backup of /data with something to id the app group that was added and seemed fine.
I started working backwards by the first letter of the app name. I first did U-Z and found that worked fine. Took a backup and went on to S-T. After this group it was bootloop time! So I put humpty-dumpty back together, restored the /data backup from U-Z, and this time installed only those apps starting with T. After this a no-problem reboot and a backup of /data and I will continue to plod on with those apps starting with S (and so on).
Horribly tedious. I can see no other way to proceed unless someone has a better idea.
PS - So I re-installed apps starting with S and basically had no problems. Hmmm. But I do recall that when testing execution of some of these apps the first time around, I decided to install busybox (Stericson), AdAway, and Afwall+ out of sequence. Before I did this I decided to check a bit more. I found that there is a Magisk busybox module and even though I have always used Stericson without troubles, I thought it best to use the Magisk module for this. I also found that Magisk has a setting for systemless hosts which could be affected by AdAway. So I enabled that before doing anything with AdAway. I also checked to see if AfWall+ might have any issues and found none. So I guess it is possible that using Stericson busybox or failing to use systemless hosts could have been an issue. I may never know for sure but at least so far I am fine after installing apps that I previously installed and had a bootloop. So FYI.
Alright, I'm a total idiot. I went and did this again, following the mantra: If it aint broke, you're not trying hard enough.
Setting all that aside, I went and tried to do some more debloating of my v40 (used this guide, that I was linked to from here), and wound up in "this fresh hell" again. Dammit! Crap.
So apparently there is a system application that is crucial to the boot of the phone that I uninstalled.
There is a fix to this, but it comes at a cost. Get into TWRP. Navigate to advanced, select Fix Recovery Reboot. Your phone will boot normally now. But you will lose root. And (so far) any attempt to reinstall Magisk to re-obtain root will result in the same bootloop again.
So here's where I need some help:
1) So if I wanted to reinstall my system partition to get back to stock from a KDZ, but still keep my installed apps, etc., how do I do that?
2) How do I get my Slot B to work correctly? It has only bootlooped there. Since I got my phone. Once I get my phone back to operational state with root, how do I make sure that Slot B works (so I have a backup I can fall back on if (when) I bork something else?
[NG]Owner
Hi everyone! I have been suffering with this problem for 2 full days on my S10 (SM-G973F/DS) and now i just have absolutely no idea how to fix it, so I thought it was worth writing about it here.
On stock, I used one old and outdated application that made user certificates system certificates, but which worked. Having tried it on EvolutionX 5.9.1 (Android 11), it brought the phone into a bootloop. I didn’t have a backup and because in order not to go through the installation process on a new one again, I decided that I would try to delete the folders from the data partition ONLY, but after half a day of attempts, nothing happened and I started to install the rom from scratch, but then weird things began to happen: after reinstallation/factory reset, boot animation randomly started (check attached video), which either went into an endless boot, or loaded the system back, but then if boot animation started on loading then this loading become endless, and the buttons (in the system) "Reboot to recovery", "Reboot to bootloader" and etc simply turning off the phone without booting into the recovery or bootloader, and if this happened, then somewhere in 2 minutes after turning it off.
I think i tried almost everything: re-installation according to the instructions, re-installation according to the way I did it before, I even tried to install the stock, and after the recovery again and then rom, but absolutely nothing changes, I cannot use custom rom if it is up to this worked fine and everything started on the same version as I was trying to install like before, I even tried to download the rom installation file again, not installing magisk-patch in boot, installing multidisabler, even find my old backup for TWRP that has every partition, but absolutely nothing changes, maybe someone knows how to fix it?
Thanks in advance!
P.S Stock rom works perfectly (android 11), but i want to use custom anyway (also android 11)