Hi folks,
I recently rooted by N4. It was running Android 5.0.
I also have MultiROM installed, with CyanogenMod installed as a secondary ROM.
I didn't realise I couldn't apply the OTA updates to the stock Android system (my oversight), and I allowed the device to download and (attempt an) the recent 5.0.1 update from Google.
When the update attempted to reboot the device, I could see in the terminal data that popped up, that it failed.
After that device now gets stuck in the booting stage with the little coloured balls drifting around.
I continued to use my phone with the secondary ROM (Cyanogen) for some days until I had time to sort this out.
MY ATTEMPTED RECOVERY
I read that ordinarily on a rooted device one would manually apply the various image files from the full 5.0.1 package.
So, following instructions found here: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Using method two (long method).
... In fastboot mode I flashed the system, boot, recovery, cache (after clearing cache), radio images from the 5.0.1 stock image.
At first I didn't flash the bootloader (as I wanted to maintain the multiboot loader I had installed) nor the user.img (I don't want to lose my user data). I read this should work. But it didn't.
When it came to booting into recovery mode to finish the process, an android icon with a ! warning on it would appear, and I could not do the recovery.
So, I have since flashed the bootloader also. That didn't change much, except that my dual-boot boot loader is now gone, and the device is still not recoverable.
Is there something I am not doing correctly? How can I recover this device so that it has 5.0.1, my existing user data, and my existing dual boot bootloader?
Cheers,...
May have solved it...
I'll post another update in a moment. Posting this just in case someone starts responding to my question in the interim.
After further fiddling around, I may have resolved this issue. I've managed to get it into recovery menu, rebooted from there, and device is now in "Android is updating" mode. Looking good.
Will post new message soon as to whether this was successful or not.
Issues continue
So, after the device booted a screen appeared for a fraction of a second, that appeared to be the screen for selecting system language (as per what happens when a device is first run after a clean install). But the screen almost instantly goes black except for the little network icon and battery icon and time in the top right of the screen.
If I use the power button to lock the screen and again to activate it, the screen very briefly flashed up the language selector, then goes blank again.
So... it seems something odd is happening after applying the 5.0.1 file.
Any suggestions?
Flash the 5.0.1 factory image with fastboot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Flash the 5.0.1 factory image with fastboot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well, this is what I resorted to doing. And it worked. Phone started and was as new. Of course, I lost my user data which is a ****. I did pull the SDCARD content over ADB, but am not sure how I'd go about pushing it all back on, into right locations, etc.
BUT—and it's a BIG BUT—when I re-rooted it and applied SuperSu, it couldn't be put into recovery mode any more. It would keep running through the SuperSu install process each time I'd attempt to go into Recovery.
I ended up ignoring this, and installing Busybox (with Play) and SuperSu.apk (via Play). But the SuperSU apk would keep saying its files needed to be installed/updated.
I forget the exact mess that unfolded, but eventually (after installing MultiROM) I could boot the phone as it would ALWAYS go into (custom) recovery.
So I starter the whole process again, with another clean install of 5.0.1, and yet now it is stuck at the bootloader (the little swirling balls screen).
AndroidWelcome said:
Well, this is what I resorted to doing. And it worked. Phone started and was as new. Of course, I lost my user data which is a ****. I did pull the SDCARD content over ADB, but am not sure how I'd go about pushing it all back on, into right locations, etc.
BUT—and it's a BIG BUT—when I re-rooted it and applied SuperSu, it couldn't be put into recovery mode any more. It would keep running through the SuperSu install process each time I'd attempt to go into Recovery.
I ended up ignoring this, and installing Busybox (with Play) and SuperSu.apk (via Play). But the SuperSU apk would keep saying its files needed to be installed/updated.
I forget the exact mess that unfolded, but eventually (after installing MultiROM) I could boot the phone as it would ALWAYS go into (custom) recovery.
So I starter the whole process again, with another clean install of 5.0.1, and yet now it is stuck at the bootloader (the little swirling balls screen).
Click to expand...
Click to collapse
Try a full wipe from Factory Recovery, and see if it will fix the bootloop.
Bootloop no more...
ariesgodofwar said:
Try a full wipe from Factory Recovery, and see if it will fix the bootloop.
Click to expand...
Click to collapse
(wiping the sweat from his brow...)
After many tedious hours of messing around with this beast... there is life beyond the bootloop.
Back to a stock install.
So, now I am wondering why the SuperSu/Root process didn't work on my last round on this.
The SuperSu installer would kick in EVERY time I went into Recovery mode, and would then reboot the phone. This made it impossible to do things with ADP because I essentially couldn't get into recovery mode. I wanted to push through some of the stuff I pulled using ADP before I wiped the phone previously.
I installed MultiROM (which includes TWRP [is that what it's called] recovery system. BUT then go stuck in a Recovery loop.
Not wishing to repeat that fiasco... does anyone more knowledgeable than I (not a difficult status to achieve) have any suggestions to what might have caused those issues?
Related
Hi folks,
After reading all of the horror stories about attempting to update a rooted/custom-recovery LG G2 to the latest vs98024a KitKat update, I still decided to give it a go. Mostly due to the pestering of the update dialog that kept coming up. Having a fully backed-up phone made me a little less uneasy about it. My phone is both rooted and has CWM recovery.
First, rather than attempting OTA, I used the windows-based software updater application that comes on the phone. My last OTA attempt failed, so I didn't even bother this time. The program ended up launching C:\LGMobileUpgrade\LGMOBILEAX\BYRLauncher.exe, and after downloading and installing the ROM, the phone took the update just fine. Even despite saying "ROOTED" after the phone rebooted to flash the new ROM. At this point, I have a phone that is updated to KitKat, and it's retained all of my preferences. Cool. But the phone is no longer rooted.
Oddly, the OTA dialog still came up, despite being for the same ROM version that I'm running. I allow it, and it fails. And no longer prompts me. Fine.
Back to the root thing. ioroot25 should get me root again on the phone. I follow the steps, it says that it's rebooting into recovery and then says When recovery loads, select: *apply update from adb* with power button.... Only it doesn't seem to reboot into recovery, and it doesn't give me any options. It just sits at an animated Android icon for a bit. The phone reboots and it goes through the initial setup. It did a factory reset! It's still KitKat, but everything including the SD card is cleared. Perhaps this all happened because I had CWM installed before upgrading? Slight annoyance, as I've got backups.
I do ioroot25 once again, and this time it does reboot into recovery where I can select apply update from adb. At this point I have a rooted KitKat G2. I do a reverse rsync to restore the contents of the SD card, and then restore apps via Google's backup and/or TitaniumBackup, as well as restore SMS/MMS messages via TitaniumBackup. The main annoyance now is to re-arrange icons how I had them before.
What's not clear at this point is how I get CWM back onto the phone. I had originally used FreeGee, but it reports that my phone isn't supported. ROM Manager says that CWM (from FreeGee) is installed, but rebooting into recovery still results in the Android system recovery <3e> menu system that was present when doing the successful ioroot. This is a stock android recovery, right? I don't recall seeing it before, but I guess it may be different between android phones and versions. I also tried installing CWM via ROM Manager, and the installed version number updates to what it supposedly installs, but rebooting into recovery still shows the same menu system.
Is CWM not (yet?) supported on my KK LG G2? If it is, how can I get it loaded?
Thanks.
forrestgump2000 said:
Is CWM not (yet?) supported on my KK LG G2? If it is, how can I get it loaded?
Click to expand...
Click to collapse
FTR, I ended up using AutoRec to install TWRP. It was trivial to do and worked fine.
I've never had problems like this and I've been flashing custom roms and recovery since HTC G1 days. Maybe you chaps can enlighten me a bit.
I can boot into all partitions of my device just fine, regular system, recovery, bootloader all okay. My daily rom (Vanir), however, has been getting a little bogged down lately so I'm trying to do an update.
I transferred my rom and gapps files to the sdcard and boot into twrp 2.6.3.1 to update, but lo and behold, the files are now missing. All my other files are there, just not the rom or the gapps. Not too worried yet, I'll just use the sideload method instead.
Start up sideload and watch it transfer over the new rom (MIUI at this point, and I factory reset before hand). From the cmd line I can see it going over just fine and the device seems to be accepting it as well. It gets to 100% and starts a quick error free install on the device, but when I reboot, nothing has been changed and I'm back in Vanir. Okay...I'll update the recovery and see if a new one works.
So I boot into the fastboot to update the recovery.
Code:
fastboot flash recovery openrecovery-twrp-2.7.0.0-grouper.img
Looks good, no error messages, cmd line shows it has been written, so I reboot into my new recovery, only its not new, its still twrp 2.6.3.1 and everything still doesn't work.
Long story long, I also tried installing CWM instead of TWRP -- didn't work, using adb push to move the files and that didn't work, and every time I seem to just lose the zip files after a reboot or update attempt. In fact, when I boot back into Vanir, all my regular files are there, but even though I haven't removed them none of the rom or gapps zips are anywhere. I am sure they have successfully transferred multiple times, but they never seem to make it through a boot sequence.
At this point I'm stuck, and wondering about my boot partitions being messed up. Any help you can provide is much appreciated.
Update, with new information.
I tried to do a complete wipe a la the guide that's stickied in this forum, and it's led me to a bit of new information. It seems that my bootloader is repeatedly failing to update from version 3.23 every time giving either the "InvalidState" error, or when I use older bootloaders that are supposed to work like the JWR66V bootloader mention in this post, it doesn't say "InvalidState" but still fails just the same with a blank where it would say "InvalidState".
I've also realized that none of my changes to my tablet are persisting through a boot sequence. If I download a new app, it is gone upon restarting. In fact, every time I power it up, it downloads the same 3 app updates to the device. Perhaps that can help narrow the problem down a little bit? Sounds like a data wipe is happening every time, but only for changes since I began to try to update the tablet a few days ago, all my files from before the update attempt are never removed or altered at all.
Lastly, according to Rom Manager, I have both TWRP and ClockworkMod as recovery. Actually, that makes me think it might be a boot.img issue. If anyone has any ideas at all, I am open to try any of them at this point. Thanks for reading and for your suggestions in advance!
Sprint LS980 in an odd state after trying to flash CyanogenMod 12.1
Ok... so I got two of these Sprint LG G2's. I was able to successfully flash the first one with a minimum amount of problems considering I was just learning how to do it.
This second one is a problem though. Here's what I did:
I tried to root but it could not due to the version of the Sprint firmware on the phone. I did the TOT stock flash to get it back to stock. That worked fine.
Then I was able to root it via ioroot. Once rooted, I installed FreeGee and tried to install TWRP, that didn't seem to work, so I installed CWM Recovery. I did option two on this thread to try to get the loki stuff installed using openrecovery-twrp-2.6.3.4-ls980. That "installed" and I was able to boot into it. I installed cm-12.1-20151125-NIGHTLY-ls980 (same one I used on the other phone). That would not install via CWM and gave an error about not being able to lokify (or something like that).
So I said, OK, I must have done something wrong, so I tried to redo stock flash again. That acts like everything works fine LGFlash does it's thing (using LS980ZVA_01.TOT), but the phone boots up and does not seem to finish the install process. The LG logo comes up and not the Sprint screen that I would expect. I can do this over and over again and the results are the same whether I let it sit for an hour or 10 minutes after flashing. So now, the phone boots, but I can't do anything with the touch screen, and will then go into a reboot loop (getting into the OS but rebooting shortly after). I CAN get into CWM where I can wipe data/factory reset and wipe cache partition. After I do that, the phone will boot and will let me interact with it, but after a short time (a few minutes I think), it will reboot again and be in the same state it was before I went into CWM. I tried to do a factory reset in settings. It would say that two reboots would occur, but then nothing happens.
I'm at a bit of a loss as to where to go from here. I don't think that it's an unrecoverable brick, but heck if I know how to fix it.
In between reboots, ADB does see the device in ADB Devices, but shows that it's offline, so I can push an APK to it.
Here are the options that I get in recovery mode:
Reboot System Now
Apply Update From External SD Card
Apply Update From Cache
Apply Update from ADB
Wipe data/factory reset
Wipe cache partition
Any assistance is greatly appreciated!
Ok.. well.. I downloaded and flashed ZVE and it seems to have greatly stabilized the phone. However, it seems that I have lost the ability to do download mode and recovery mode. I can still get into the device through ADB, but ioroot no longer is able to root the device, so I can't install any recovery. There is a system update available to install, but didn't want to do that unless I'm good an stuck in this mode.
I also don't seem to be able to enable the cellular service. I don't know if the update it wants to install would fix that or not.
Edit: I can still do ADB reboot recovery and get into recovery mode with these options:
Apply Update From External SD Card
Apply Update From Cache
Apply Update from ADB
Wipe data/factory reset
Wipe cache partition
Edit2: I was able to root with Stump. FreeGee won't run on ZVE, so not sure what to do from here. The phone does not work at all. None of the phone info is listed in About Phone. No IMEI or anything.
Edit3: I have been able to get TWRP installed and can boot into it. I have also verified that I can get into download mode now. I'm very concerned about my EFS info though. I did back it up, but not to the PC, so effectively I have no EFS backup and no way to recover the IMEI information. Not cool...
Hopefully someone can help. There was an update on Google Play today for the Chainfire SuperSU. I ran the update, clicked the message that I needed to update the binary, chose TWRP (I'm on 2.8.7.0), and the phone rebooted. After booting, it went into recovery, tried to run something (I wish I had written it down), and rebooted again. It did this again and again, looping about 10 times before I finally held the power button. At that point, the phone tried to boot normally, but never went past the boot animation (waited about 30 minutes).
I can still get into recovery, luckily... I just don't know what I should do at this point. I am running the stock MM, just debloated.
From which SuperSU version did you run the update?
Before you do anything else, try wiping cache and dalvik from TWRP. Sometimes you get lucky and that's all it takes to stop a bootloop.
I was able to fix the issue by booting into recovery, copying the latest supersu zip to internal storage via MTP, and installing the zip manually. Once that was done, the phone finally booted all the way.
andry23jsv said:
From which SuperSU version did you run the update?
Click to expand...
Click to collapse
The update was from the newest one in the store. It came up just like any other app update does. The funny thing is, when I went back to look at the latest version in Play, it was definitely older. I wonder if it was pulled.
jason2678 said:
Before you do anything else, try wiping cache and dalvik from TWRP. Sometimes you get lucky and that's all it takes to stop a bootloop.
Click to expand...
Click to collapse
I had tried all that. It's usually the first thing I do when I have issues like that.
Hey, i am using a note 4 . Currently my phone is in recovery mode and is boot looping. It would boot for 2 secs then reboot again. i cant exit the recovery mode at all the clear any cache or stuff. I may have misclicked the normal boot and clicked the TWRP after updating supersu. Is there a fix for it?
Did you try manually copying the latest SuperSU zip file to your internal storage (via MTP, or adb), then installing it from recovery?
Flapjack said:
Did you try manually copying the latest SuperSU zip file to your internal storage (via MTP, or adb), then installing it from recovery?
Click to expand...
Click to collapse
hi the problem is that i cant get pass the recovery mode. its there for about 2 secs then gone
I guess I'm not sure what you mean. You can't get "past" recovery mode? When you reboot (without button intervention), what happens? Does it try to load the OS partition, then reboot? Can you press whatever button combo the Note 4 has to get into recovery (as opposed to booting the phone normally?
Not sure how much help I can be, as I've never had a Note. I got off the Samsung train after the S4. I've had enough of locked bootloaders, bloatware, and crappy UIs. It's a shame, too.... as I really like their hardware.
Flapjack said:
I guess I'm not sure what you mean. You can't get "past" recovery mode? When you reboot (without button intervention), what happens? Does it try to load the OS partition, then reboot? Can you press whatever button combo the Note 4 has to get into recovery (as opposed to booting the phone normally?
Not sure how much help I can be, as I've never had a Note. I got off the Samsung train after the S4. I've had enough of locked bootloaders, bloatware, and crappy UIs. It's a shame, too.... as I really like their hardware.
Click to expand...
Click to collapse
Hey man tks for replying so promptly though. I think i know what went wrong. Just that i don't know how to fix it. My phone is now recovery booting through TWRP. But i don't remember having TWRP. Is there a way to change the boot to normal?
I was running xXx 4.5, and decided to "upgrade" to 5.0.
I did the usual, wiped data/system, then flashed.
I got stuck in a bootloop, and found I had to double back and wipe /data.
I did that, got stuck at the boot animation.
If I go back to recovery, all the data is jumbled, I assume encrypted? I flashed a different twrp for 8.0 compatibility, no change.
I can't push/sideload anything (roms, recovery zips sideload fine), it fails.
So I flashed the stock recovery in fastboot, rebooted there, and tried to sideload via adb the stock 8.0 flash files.
Now it works at it for a few minutes and just comes back as "Installation Failed".
Where do I go next? All i can get to is recovery, fastboot, bootloader.
I've already factory reset/wiped everything, so don't care if I lose anything anymore.
Help?
Thanks.
It appears I found a solution, just a few posts below my own! I hate it when that happens.
Anyways ,
https://forum.xda-developers.com/showpost.php?p=75364805&postcount=7
seems to have got the ball rolling, I was able to copy files to my phone while in twrp, which I couldn't do before, and currently have xXx installing. The first time it installed it didn't ask about encrypted/decrypted and didn't give me any warnings, this time it did.
xXx still won't boot after flashing, trying stock full flash file..
edit 2: Was able to flash full oneplus update file and boot. had to do a factory reset after rebooting as it was crashing a ton and wouldn't get through setup. It's been running fine since though. Now I'm a little skittish to try again, there are some root features I'd really like to still have.
I have a OnePlus 5 phone stuck in the Fastboot mode, been contacting them for days now but I still keep hearing the same excuses that the matter has been escalated to their tier 2 tech support team Nd would be contacted. Please is there a way to copy files off the phone in this state before it's flashed?