So basically, I was running a rooted stock 2.2 on my Droid 2 when I noticed the notification for an update... so I allowed it to download and install the update and it failed, of course. So no biggie, right? I'll just wipe the system and flash the 2.3.20 update.zip - well, the flash worked but broke my camera app, my dialer, my keyboard and a few other system apps.
SO, I downloaded and reflashed... same thing.
Now, my plan was to wipe the system again and flash the SBF... Opened up RSD, loaded the SBF and started the flash.
after about 10 minutes, I get an error in RSD telling me the flash failed and the "system is corrupt"
My phone now says:
Bootloader
D2.35
Code Corrupt
Battery OK
OK to Program
Transfer Mode:
USB
So I tried flashing the SBF again... same error. Phone won't eve make it to the splash screen..
Now what?
*EDIT/UPDATE:
3rd time's a charm!!! The third SBF flash attempt succeeded, phone is rebooting now. *crosses fingers*
Okay we're good - anyone know why the flash would fail twice and then succeed with absolutely nothing different??
Related
I have the 2ndbootin thing, the stock moto recovery, and never ending boot animation. If I wipe the cache using the moto recovery, I can get it past the boot loop and then it gets stuck in "android is upgrading". I figured I can flash a custom recovery using RSD, the problem is I don't know, and googling the problem didn't came up with useful solutions. My top priority is to get the phone working again, and that it will have the data is got now (though I did a backup of the data before starting this failed upgrade).
Also relevant:
http://forum.xda-developers.com/showthread.php?p=48088388#post48088388
Achiron said:
I have the 2ndbootin thing, the stock moto recovery, and never ending boot animation. If I wipe the cache using the moto recovery, I can get it past the boot loop and then it gets stuck in "android is upgrading". I figured I can flash a custom recovery using RSD, the problem is I don't know, and googling the problem didn't came up with useful solutions. My top priority is to get the phone working again, and that it will have the data is got now (though I did a backup of the data before starting this failed upgrade).
Click to expand...
Click to collapse
Man, you need to start again from stock.
Install the stock SBF using RSD, root, install 2ndinit, install CM10, install CM10.2, install the updaterecovery.zip package, reboot (don't wipe), then install CM11 and Gapps. It worked for me, it worked for other defy users, it will work for you.
leandrolutz said:
Man, you need to start again from stock.
Install the stock SBF using RSD, root, install 2ndinit, install CM10, install CM10.2, install the updaterecovery.zip package, reboot (don't wipe), then install CM11 and Gapps. It worked for me, it worked for other defy users, it will work for you.
Click to expand...
Click to collapse
I gave up and went to the RSD, downloaded what I thought was he right SBF, flashed it in RSD, and after it finished the device is BRICKED. No lights, it doesn't turn on. :crying:
Achiron said:
I gave up and went to the RSD, downloaded what I thought was he right SBF, flashed it in RSD, and after it finished the device is BRICKED. No lights, it doesn't turn on. :crying:
Click to expand...
Click to collapse
The defy doesn't really brick, because the bootloader is locked.
It may be no charge in the battery...
You need to use an external charger, or McGyver method, because the defy won't charge by the usb or wall charger...
After you make it, try RSD again, and choose the right SBF, from your carrier.
Hope it helps... gogogo defy :victory:
I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?
Jon-G said:
I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?
Click to expand...
Click to collapse
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.
Skipjacks said:
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.
Click to expand...
Click to collapse
Thanks for the reply.
Regarding the versions of CM and TWRP, I deliberately picked these versions due to their high download count (A sign I can trust these builds, being not too buggy). I'll try a newer CM version and another TWRP version if that didn't help.
I will also verify the MD5 for the downloaded file this time.
If I restore to stock via Odin, wouldn't that override the recovery? I've looked on some tutorial on how it's done, and it seems like the stock recovery is flashed, then used to restore the stock. Is there any way to use Odin to flash other ROMs?
EDIT: Nope cm-11-20140210 also failed, and I did verify the MD5 now. My TWRP is the newest available for jgedlte in the download page (2.8.0.1).
I did manage getting into some sort of a boot loop (The initial "Reboot System" brought back the recovery, but after a full power off and a reboot, the screen remains black and the phone vibrates every 4 seconds or so.)
EDIT 2: I tried to flash the stock back, following this tutorial. I downloaded the Open European version, flashed the AP but it failed during the write of system.img.ext4, saying that the image is invalid. I tried again with the PIT file, but it failed too (secure check fail while repartitioning...).
Yesterday I wanted to update my Nexus 4 to the latest nightly cm-13.0-20160221-NIGHTLY-mako.zip using the built-in update tool. The old build was cm-13.0-20160209-NIGHTLY-mako.zip.
But after hitting reboot, the screen went off and on repeatedly (just plain black). I let it like this for the night. In the morning it was still turning the screen on and off. I was able to reboot to the bootloader. Apparently, the update deleted TWRP and installed Cyanogenmod Recovery. I re-flashed twrp.img, and now I'm stuck there: booting ALWAYS goes to TWRP (or the bootloader), I can't boot the system anymore. I tried re-flashing the old nightly, retried the new one, tried sideloading an even newer one (cm-13.0-20160222-NIGHTLY-mako.zip), wiped cache, wiped data - nothing helped.
What can I do to unbrick my phone?
Do u have a back up to your stock Rom or any other Rom aside from CM?
Flash back to stock and start over with twrp, cm, and gapps.
I just flashed back to stock, the problem persists: bootloop, the lying android with a red warning sign is showing up very briefly, then it reboots.
My first attempt to go go back to stock was manually. Now I tried again using the Nexus Root Toolkit. (Note: both time I flashed build LMY48T
After it finished flashing, the error message (lying android with red warning sign) appeared again, but this time it stayed - no bootloop anymore.
Then I rebooted into revovery mode, and there was some output:
Code:
Finding update package...
Opening update package...
E:unknown volume for path [/storage/emulated/0/cmupdater/cm-13.0-20160221-NIGHTLY-mako.zip]
E:failed to map file
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
So, despite all flashing, apparently it is STILL looking for the - now missing - cm13 update. Where is this coming from? There must be some flag somewhere, some config file or whatever.
So, after the next reboot, the ominous boot parameters seem to be gone - I'm on a fresh 5.1.1, build LMY48T.
I'm still curious what happened here. I guess the whole flashing wasn't necessary, I just needed to get rid of the malicious boot parameter. Maybe a file or a file system was readonly?
Any idea how this happened?
So i just did the new update on my V20 and it sent me straight to TWRP and i cant get out of it. It always boots into TWRP. What can i do? ive already tried a factory reset and restoring my back up and nada. Help please.
Its now looking for stock boot image which on yours is currently modified with system rooted.
Try using lgbridge to repairs your boot image or if you have it flash the stock boot image using fast boot command or do a factory reset while in twrp then flash entire stock image with lgbridge.
Sent from my LG-H990 using XDA-Developers Legacy app
somemadcaaant said:
Its now looking for stock boot image which on yours is currently modified with system rooted.
Try using lgbridge to repairs your boot image or if you have it flash the stock boot image using fast boot command or do a factory while in twrp then flash entire stock image with lgbridge.
Sent from my LG-H990 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yeah none of those work. The OS is setting off some sort of flag that states it must go into recovery and wont stop going into recovery until that flag is changed which I assume is done by the update. I tried updating with UPPERCUT/LGUP and it errors out at 4%. So right now it's still stuck
It didnt install the update
type
Code:
fastboot erase fota
from bootloader and see if it boots after that.
This will for sure fix you up...
https://forum.xda-developers.com/v20/how-to/how-fixed-bricked-lg-v20-t3501310
listen to me2151
delete fota and then pull battery and reboot.
ota's downloaded to the fota folder will cause endless twrp loop.
freeze ota in system/privapps to avoid this again.
Sorry to post on here, but maybe we can get a few tips from each other.
Im also stuck at TWRP. I installed a ROM and went back and forth between both ROMS. After about 4 times of going back and forth between ROMS, my pattern didn't recognize on boot with my original backup and daily. I tried my pattern over 10 times and it wiped everything on me. The strange part was I was swiping my pattern 100% and it failed. Also, my tries were going up and down. It would say I have 6 tries left before my phone wipes, then I would stop anjd turn the screen off, and the screen would say I have 3 tries left, then 5 tries left. My tries were inconsistent, and it finally wiped everything.
I am now stuck on TWRP with no luck of restoring. I flashed the vs995 boot image and system image and it goes back to TWRP. I factory reset, wiped everything, made sure the system folder was clean, then flashed both images again and the same thing, no luck.
I also tried to restore with LGUP, but keeps stopping at 9%. I extracted the dll and copied it into the common folder and I get the same thing.
Error: Error Code = 0x2000, Flashing Fail
When I plug the phone into my computer it shows us996 and not vs995. Strange.
Any help would be amazing.
EDIT: Figured it out!
So, I extracted the dll file from the kdz file and I had to replace it with the one in the common folder. My error was not renaming the file, so the LGUP would stop at 9%. Make sure you pull the file, rename it, remove the old file from the folder, and flash on LGUP.
leyvatron said:
Sorry to post on here, but maybe we can get a few tips from each other.
Im also stuck at TWRP. I installed a ROM and went back and forth between both ROMS. After about 4 times of going back and forth between ROMS, my pattern didn't recognize on boot with my original backup and daily. I tried my pattern over 10 times and it wiped everything on me. The strange part was I was swiping my pattern 100% and it failed. Also, my tries were going up and down. It would say I have 6 tries left before my phone wipes, then I would stop anjd turn the screen off, and the screen would say I have 3 tries left, then 5 tries left. My tries were inconsistent, and it finally wiped everything.
I am now stuck on TWRP with no luck of restoring. I flashed the vs995 boot image and system image and it goes back to TWRP. I factory reset, wiped everything, made sure the system folder was clean, then flashed both images again and the same thing, no luck.
I also tried to restore with LGUP, but keeps stopping at 9%. I extracted the dll and copied it into the common folder and I get the same thing.
Error: Error Code = 0x2000, Flashing Fail
When I plug the phone into my computer it shows us996 and not vs995. Strange.
Any help would be amazing.
Click to expand...
Click to collapse
why dont you try flash custom rom?
rowihel2012 said:
why dont you try flash custom rom?
Click to expand...
Click to collapse
Tried and no luck. Stuck in TWRP.
akobirovruslan said:
So i just did the new update on my V20 and it sent me straight to TWRP and i cant get out of it. It always boots into TWRP. What can i do? ive already tried a factory reset and restoring my back up and nada. Help please.
Click to expand...
Click to collapse
Have you tried booting into twrp manually and reflashing twrp again? Try that
THIS WILL FIX YOUR TWRP BOOTLOOP. Tried and true. Follow step-by-step.
https://forum.xda-developers.com/v20/how-to/how-fixed-bricked-lg-v20-t3501310
i did this it worked https://forum.xda-developers.com/v20/help/lg-v20-access-to-fastboot-t3557328
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?