Related
So my phone has decided to soft-brick itself after upgrading to Lollipop. It never even made it a single normal bootup after the upgrade. I get to the Optimizing Apps screen and then it shuts itself down after that finishes. I can't get into the OS, but I can boot into Recovery Mode. I've tried to wipe the cache partition to no luck. I haven't tried to Wipe Data/Factory Reset because I want to try and recover my data.
I haven't rooted the device or put on a custom recovery. Is there any way to get in there and grab the files off? I can see the device listed under 'fastboot devices' using ADB but don't know where to go from here. I tried to flash a custom recovery but it doesn't work because the bootloader is locked?
Am I basically screwed and my only option to just factory reset and lose my data?
I found a rooted ROM on rootjunkysdl (sorry I'm new and can't link) Can I use RSDLite to flash that on the device and go from there?
achobgood said:
So my phone has decided to soft-brick itself after upgrading to Lollipop. It never even made it a single normal bootup after the upgrade. I get to the Optimizing Apps screen and then it shuts itself down after that finishes. I can't get into the OS, but I can boot into Recovery Mode. I've tried to wipe the cache partition to no luck. I haven't tried to Wipe Data/Factory Reset because I want to try and recover my data.
I haven't rooted the device or put on a custom recovery. Is there any way to get in there and grab the files off? I can see the device listed under 'fastboot devices' using ADB but don't know where to go from here. I tried to flash a custom recovery but it doesn't work because the bootloader is locked?
Am I basically screwed and my only option to just factory reset and lose my data?
I found a rooted ROM on rootjunkysdl (sorry I'm new and can't link) Can I use RSDLite to flash that on the device and go from there?
Click to expand...
Click to collapse
The rooted rom that you see there is a kitkat rom. Since your bootloader is now expecting lollipop, flashing that would be a very bad idea. In fact, since you've taken the lollipop update, the odds of you ever being able to root your device are unfortunately near 0. But to answer your question, full firmware files for the 5.1 Turbo firmware have not yet been released by Verizon. That's what you would need to flash with RSDlite. So your options are to wait for those or to factory reset.
TheSt33v said:
The rooted rom that you see there is a kitkat rom. Since your bootloader is now expecting lollipop, flashing that would be a very bad idea. In fact, since you've taken the lollipop update, the odds of you ever being able to root your device are unfortunately near 0. But to answer your question, full firmware files for the 5.1 Turbo firmware have not yet been released by Verizon. That's what you would need to flash with RSDlite. So your options are to wait for those or to factory reset.
Click to expand...
Click to collapse
Would something like this work? http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
If it's just for a hardbrick could I flash the wrong firmware then use this tool to get it working again?
achobgood said:
Would something like this work? http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
If it's just for a hardbrick could I flash the wrong firmware then use this tool to get it working again?
Click to expand...
Click to collapse
At a glance, it seems like that should work. I'm not too familiar with that method. Also, you're in luck. It seems that Verizon dropped the official image today. You can find it here: http://forum.xda-developers.com/dro...-5-1-image-t3152229/post61744745#post61744745
Apparently, trying to get myself to install a clean rom has ended up on me having no rom at all, only FastBoot access and access to TWRP 2.8.1.0. So. How in this world do i install ANYTHING, when apparently every single ROM version patches over the older versions? where do i find a clean stock rom i can install through TWRP? ( Default recovery throws a cust error ). This is kind of getting insane already.
I hate being this kind of person who registers on a forum just to have some ( possibly incredibly stupid ) problems solved. But here i go.
Since i've heard that there's a lollipop update for Android ( literally 2 days ago ), i decided to start an upgrade. Sadly, it seems like somehow when i installed Se7en ROM, i ****ed something up. After looking around i did manage to find a proper copy of TWRP 2.8.1.0 that i could use for recovery, and after fighting a half brick i had following some of the comments left over here i have gotten back to "normal operation"
The device boots normaly but it seems like it won't do anything on Recovery. The bootloader states it's from version 133 so i am trying to install that as i am writting this. With that said, i see a lot of confusion going on on how to update, and the few threads i find with boot and recovery images, seem to be either dead or get my phone stuck on a bootloop. the custom recovery seems to work but it is not doing any IO operations, apparently. If this is relevant, it seems like the caché partition has been broken somehow. something that would easily be fixed, if it weren't because of the fact it isn't writting or reading.
Is there a way i can safely go to stock from where i am? ( i got an unlocked bootloader, so there is that ), and from there on, how do i safely upgrade to a more modern build? All the mirrors for TWRP2870 seem to crash, returning my phone back to the bootloader. And apparently that is mandatory for an upgrade later on.
I apologize for my lack of knowledge on this.
I apparently have deleted my somewhat working system for nothing. I need to have the stock firmware as a ZIP file for it to be flashed. Does anyone have an idea?
Aaaand now, trying to flash an updated bootloader and recovery i am stuck in what looks like a complete full brick.
Go me.
Flash MyRom 1.2 (http://forum.xda-developers.com/showthread.php?t=2948887) through TWRP. Now you've should got a running system back.
Then flash the emui 2.3 stock Recovery. If you don't find any link the download a B1xx Rom (the last 4 characters of the build-number matters) and extract recovery.img with the huawei update extractor.
After beeing back on stock recocery flash B609 with the normal update-methode. Go on for B621 -> B623 -> B830.
TWRP 2.8.7.0 will work once you updated to at least B609.
I'd been in a comparable situation once again. The correlation of different firmwares/recoverys/custom roms is just confusing when you start dealing with.. So I really can feel with you[emoji14]
l3Nni said:
Flash MyRom 1.2 (http://forum.xda-developers.com/showthread.php?t=2948887) through TWRP. Now you've should got a running system back.
Then flash the emui 2.3 stock Recovery. If you don't find any link the download a B1xx Rom (the last 4 characters of the build-number matters) and extract recovery.img with the huawei update extractor.
After beeing back on stock recocery flash B609 with the normal update-methode. Go on for B621 -> B623 -> B830.
TWRP 2.8.7.0 will work once you updated to at least B609.
I'd been in a comparable situation once again. The correlation of different firmwares/recoverys/custom roms is just confusing when you start dealing with.. So I really can feel with you[emoji14]
Click to expand...
Click to collapse
Well. i may probably be in trouble since i tried to flash directl ythe B609 bootloader and Recovery from the update.app ( as it looks like 609 is the last known "full" update ), and i can't seem to get back to it. But if i do manage to get enough to flash TWRP again I now know how to get back on track. Right now no matter what buttons do i press, i am stuck at the carrier logo, then it jsut reboots again.
Thank you very much for the reply! i now wish i was patient enough to have waited for this instead of doing a bad flash.
Was there an error or was the B609 Flash successful? Maybe (when you managed to boot into bootloader) flashing TWRP 2.8.1.0 fails now. If so, then try version 2.8.7.0 and use MyRom 3.3.
Did you try connecting your (powered off) device to your PC while pressing volume down permanently? I'm not sure if the phone boots itself now, probably you have to press power, too. Hopefully the phone boots now into bootloader.
l3Nni said:
Was there an error or was the B609 Flash successful? Maybe (when you managed to boot into bootloader) flashing TWRP 2.8.1.0 fails now. If so, then try version 2.8.7.0 and use MyRom 3.3.
Did you try connecting your (powered off) device to your PC while pressing volume down permanently? I'm not sure if the phone boots itself now, probably you have to press power, too. Hopefully the phone boots now into bootloader.
Click to expand...
Click to collapse
Fastboot gave me no failures. it did your typical "sending data .... OK" message. Only remarkable message is that it said that fastboot was informed that the target device only had 800MB ( in bytes ) available for usage. which i fail to recognize as a proper size for any volume that the device could contain.
I could not get into either the recovery or the bootloader, i even tried to press all three buttons and see if i could initiate a update, at least to know if the recovery worked. No luck.
I don't have my phone right now with me since i'm out and i am using an older, backup phone, but i will definetly try once i get back. and give it another try, maybe doing it coldly will make it work.
I use TWRP 2.8.7.1(which was flashed to the phone) and now after flashing this nightly version, the recovery gets stuck on the TWRP screen and flashes every 60 seconds, but never lets me use it.
I've searched through all the forums, but can't find anyone else with this problem. I just want to flash CM12.1 Snapshot, but I can't without the recovery working.
Everytime I flash the same recovery(TWRP2.8.7.1), the bootloader gives me the error "Mismatched partition size". I've tried "Fastboot boot TWRP2.8.7.1.img, but it sits stuck on the loading TWRP screen. I've cleared the cache, but still nothing.
The only recovery that I can get to work is CWM by booting the .img from the bootloader, but that still does nothing because none of the directories will mount, so I cant flash from the recovery.
I'm waiting on motorola to send me the stock files and just reflash stock and start from scratch, but I really want to save my data.
Does anybody have any clue as to what I'm doing wrong before I reset to stock?
Try this one:
http://forum.xda-developers.com/showthread.php?p=61558425
If this recovery doesn't work, you may have to reflash the full stock rom
uluf said:
Try this one:
http://forum.xda-developers.com/showthread.php?p=61558425
If this recovery doesn't work, you may have to reflash the full stock rom
Click to expand...
Click to collapse
Nope.. didn't work. I had the 5.0 files from motorola that I flashed, and I'll update from there.
I really wish motorola would leave those files open to download instead of having to wait... sucks not having a phone, but I survived.
i have the same issue, any idea how to fix it ?
Hey guys, I updated my mom's Nexus 6 OTA to 7 point something and it was working at first but after a month, idk what happened but the phone is in a bootloop now. The Nexus Root Toolkit doesn't work as it requires the bootloader to be unlocked and this was a completely stock phone. HALP
xida1125 said:
Hey guys, I updated my mom's Nexus 6 OTA to 7 point something and it was working at first but after a month, idk what happened but the phone is in a bootloop now. The Nexus Root Toolkit doesn't work as it requires the bootloader to be unlocked and this was a completely stock phone. HALP
Click to expand...
Click to collapse
Wipe cashes in the recovery, if it doesn't help flash latest factory image without userdata
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
xida1125 said:
Hey guys, I updated my mom's Nexus 6 OTA to 7 point something and it was working at first but after a month, idk what happened but the phone is in a bootloop now. The Nexus Root Toolkit doesn't work as it requires the bootloader to be unlocked and this was a completely stock phone. HALP
Click to expand...
Click to collapse
In my experience with bootloops is that when you you update to an new ROM sometimes the kernel gets affected in the process. It's happened to me a few times but my phone is rooted so I do a lot more flashing and updating.
It's an easy fix tho, use the Toolkit and open the Launch screen look at the top middle and there should be a tab for flashing the boot.img, in your case since your on stock ROM just restore the image file for the build number that is currently running. So if you just updated to Android N, the build number will start with an N. The toolkit will install the correct file to restore the phone back to normal working order.
His bootloader is locked, thus he can't use the toolkit or fastboot.
@xida1125: Enter into the recovery and wipe the cache. That may fix the bootloop. If it doesn't, download the latest OTA and sideload it. Be prepared for the possibility of having to factory reset the device if nothing else works.
Strephon Alkhalikoi said:
His bootloader is locked, thus he can't use the toolkit or fastboot.
@xida1125: Enter into the recovery and wipe the cache. That may fix the bootloop. If it doesn't, download the latest OTA and sideload it. Be prepared for the possibility of having to factory reset the device if nothing else works.
Click to expand...
Click to collapse
I'm gonna try that tonight, not sure how to sideload it but I'm sure I'll figure it out. I already gave my mom my Nexus 6P to use and she likes it because it has a better camera. I tried factory reset in bootloader but it didn't do anything. Forgot to try and go into recovery menu.
If you've switched devices with your Mom, you can probably factory reset in recovery without issue. Sideloading an OTA is reasonably easy. Download the OTA, move it to internal storage, and from recovery there should be a menu option to sideload the OTA.
Once you've gotten everything fixed, dig into the developer options and enable oem unlocking in both the N6 and the N6P. Doing so will not unlock the bootloader, but will give you the opportunity to unlock the bootloader if the need or want arises in the future.
Strephon Alkhalikoi said:
If you've switched devices with your Mom, you can probably factory reset in recovery without issue. Sideloading an OTA is reasonably easy. Download the OTA, move it to internal storage, and from recovery there should be a menu option to sideload the OTA.
Once you've gotten everything fixed, dig into the developer options and enable oem unlocking in both the N6 and the N6P. Doing so will not unlock the bootloader, but will give you the opportunity to unlock the bootloader if the need or want arises in the future.
Click to expand...
Click to collapse
-Tried going into recovery via bootloader, just bootlooped
-Tried factory reset in boatloader, doesn't do anything
I don't think I can sideload can I? I can't even get to recovery menu...
Based upon your descriptions, it's sounding more and more likely that you have a dead emmc chip. In other words, hardware failure.
xida1125 said:
-Tried going into recovery via bootloader, just bootlooped
-Tried factory reset in boatloader, doesn't do anything
I don't think I can sideload can I? I can't even get to recovery menu...
Click to expand...
Click to collapse
May you try the steps without a inserted simcard, otherwise I hope for you it's not the hardware
xida1125 said:
-Tried going into recovery via bootloader, just bootlooped
-Tried factory reset in boatloader, doesn't do anything
I don't think I can sideload can I? I can't even get to recovery menu...
Click to expand...
Click to collapse
OK... Here we go...
You have fastboot and adb on your computer?
Boot to fastboot... On your phone
Use fastboot to wipe userdata and cache... (I forget the commands... Google is your friend)
Try and boot... Be patient... It's gotta rebuild ART... Will take some time
If no boot...
I THINK... THINK (repeated because I don't know for sure) you can flash the factory images without unlocking the bootloader... Because they are signed by Google...
FWIW... It's something on your data partition... Or in cache...
It sounds like the phone shutdown while writing to disk...
As long as you haven't done something really dumb... Like wiping boot, aboot, system, etc... You should be able to bring it back...
Also... There is a fastboot command that will tell you partitions on the device... Not sure if the N6 has the command... That would give you more information...
This... Is a textbook example of why you shouldn't use toolkits... You're stuck... And haven't read enough or experimented enough to know how to fix your device...
So I was in the middle of using Lineage OS 14.1 when it notified that there was a May 20th update. I allowed it to update, when for some reason it just took me straight to Recovery.
When I tried to reboot back to the system, for some reason it continued to boot straight to recovery.
I tried wiping everything and reinstalling Lineage, but the same thing happened. Same with AICP.
I figured it was an issue with the recovery, so I flashed the latest img from recovery (since I can't do it from fastboot) yet the problem continues to persist..
Can anybody help? I can't do anything with fastboot because it always fails, I can't flash anything, I'm just stuck on TWRP no matter what I do. I even checked the system and everything and despite TWRP saying I "successfully installed rom" or whatever, nothing gets installed into the system or anything, it just stays empty. How do I fix this?
I read somewhere that it may be because it's trying to update something, and since TWRP is installed instead of the actual LG recovery, it can't install it or whatever. I was previously on a stock rom before I installed Lineage. Could that be it? I figured I can fix it using THIS method, but I'm not sure. The link to the KZD is dead and the only download available for D415 is "old" so I don't want to risk bricking my device.
Help is appreciated ahead of time!
I also just realized that I can't really do anything about flashing the stock rom manually because the download mode is registered as fastboot and it doesn't seem to properly register in the Device Manager at all...
I've also just attempted to factory reset the device, but the only thing that does is also boot into TWRP..
Fivavoa said:
I've also just attempted to factory reset the device, but the only thing that does is also boot into TWRP..
Click to expand...
Click to collapse
In twrp there is a terminal so you might be able to get access to fastboot by removing download mode.
Look at the thread below.
https://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
Hi :3
Fivavoa said:
So I was in the middle of using Lineage OS 14.1 when it notified that there was a May 20th update. I allowed it to update, when for some reason it just took me straight to Recovery.
When I tried to reboot back to the system, for some reason it continued to boot straight to recovery.
I tried wiping everything and reinstalling Lineage, but the same thing happened. Same with AICP.
I figured it was an issue with the recovery, so I flashed the latest img from recovery (since I can't do it from fastboot) yet the problem continues to persist..
Can anybody help? I can't do anything with fastboot because it always fails, I can't flash anything, I'm just stuck on TWRP no matter what I do. I even checked the system and everything and despite TWRP saying I "successfully installed rom" or whatever, nothing gets installed into the system or anything, it just stays empty. How do I fix this?
I read somewhere that it may be because it's trying to update something, and since TWRP is installed instead of the actual LG recovery, it can't install it or whatever. I was previously on a stock rom before I installed Lineage. Could that be it? I figured I can fix it using THIS method, but I'm not sure. The link to the KZD is dead and the only download available for D415 is "old" so I don't want to risk bricking my device.
Help is appreciated ahead of time!
Click to expand...
Click to collapse
Hello, look at this page, this would solve the problem:
https://www.androidsis.com/solucionar-problema-bootloop-recovery-actualizacion-ota-linageos/