Summary: Phone won't get past the bootloader, I've tried flashing .sbf's, update.zip's and updating the baseband with no luck.
Full Story: A couple weeks ago my 100% stock unrooted Droid 1 stopped getting a signal. It over 24 hours so I took it in to Verizon. They tried a factory reset, said it's out of warranty and told me to buy a new phone. How convenient for them, my contract ended in a week.
I decided to squeeze some more life out of it and started using it WiFi only. That lasted about a week until I restarted it and it hasn't been able to get past the bootloader since.
In it's current state it cannot boot Android at all, I only have access to the bootloader and recovery.
The first thing I tried was the Cyanogen Motorola Droid: Full Update Guide, but when I was ADB'ing it became apparent I had bigger issues. Commands like "su", "cp", and "chmod" were returning "not found".
Next I tried to flash a stock .sbf using RSDlite. It hangs at 99% with an error "Phone[0000] BP Pass Through Mode". The only info I could find about that was to try it on 32 bit WinXP, which I did, and it also failed.
So then I tried flashing older and rooted .sbf's since nothing else was working. It had the same "BP pass through mode" errors. One changed my boot animation from the white M logo to a blue skateboarding Android, but that's it.
The only .sbf's that are completing are recovery only. So far I've flashed SPRecovery, ClockworkRecovery and RZRecovery with no issues.
My next step was trying update.zips. signed-voles-FRG22D-Master_OTA.zip came back with the error:
Code:
assert failed: sholes.update_cdma_bp("/tmp/1rdl.bin", "/tmp/1bp.img")
E:Error in /sdcard/update.zip
(Status 7)
Google couldn't find anything useful about that error.
That error message made me think it had something to do with the baseband, so then I tried updating that with C_01.43.01P.zip and another .zip I found of the same version but a different file size. Both returned the same error listed above.
So now I don't know what else I can do. Did my Droid 1 really irreversibly brick itself for no reason?
Its very important you have the latest version of RSDlite when flashing an SBF. I struggled for about 3 hours to try and fix my phone when i thought I bricked it. I went from RSDlite 4.8, to 4.9 and suddenly the flash was successful. It was very much a head slap moment. See if that helps you.
I am using RSDlite 4.9, which I'm pretty sure is the latest version.
Related
I've tryed to root the tattoo with superoneclick but it failed to root, since and the end came across some supposely memory errors and when when I boot into system its all apparently the same. I guessed it hadn't done anything so I jumped to the method as described on http://forum.xda-developers.com/showpost.php?p=5835675&postcount=1
I even done the gold card. And tried it. it does some command lines with no errors and at the end it boots normally. The problem is when I try to go to recovery mode it doesn't go to it and when I try to go to normal stock boot loader it algo fails. It tries to enter, I even see the screen for some part of a second but it just doesn't enters.
It boots aparently with no errors into to the system, but somehow somethings seem not work properly like factory reset and screen callibration.
It seems I've got stuck between halfway to nothing.
I just wanted some 2.3.3 goodness to my haunt and I'm afraid I've just messed up her phone!
Any smart and easy solutions? Even back to full stock would be good!
Thanks in advanced!
you can allways (well, as long as its not completely bricked) flash a RUU to go back to stock rom.
for me first time rooting also failed (dont remember the errors exactly), then i installed the RUU, tried rooting again and it worked.
Tattoo RUUs: http://shipped-roms.com/shipped/Click/
potattoo said:
you can allways (well, as long as its not completely bricked) flash a RUU to go back to stock rom.
for me first time rooting also failed (dont remember the errors exactly), then i installed the RUU, tried rooting again and it worked.
Tattoo RUUs: http://shipped-roms.com/shipped/Click/
Click to expand...
Click to collapse
Thanks!
I thought that could be a solution! I promissed I've been trying to resolve this situation for about 4 days. And I did it!!!
Everytime I ran a root solution it said it failed but they also said it was rooted.
tried again using this app:
http://forum.xda-developers.com/showthread.php?t=761507
Used the CM7 recovery (http://forum.xda-developers.com/showthread.php?t=854152) with described method: http://forum.xda-developers.com/showpost.php?p=9192029&postcount=21
i thought the problem could be not the rooting part but the flashing of the recovery.
Did it step by step and worked!
Thank you very much for your reply!
I have seen a lot of issues with installing the OTA and seeing installations that are aborted and having this message :
Assert failed apply_patch_check
To help troubleshoot the issue you need to post the full error message so someone can figure out what it is failing on.
But if you get that "Assert failed apply_patch_check" and in the parentheses it says "boot" and then letters and numbers, it means your kernel is different than .886. "But I am stock .886". No you are not, you installed a leaked update, your kernel is different than .886 and you cannot update with the OTA.
Hopefully 5.7.893 will follow and put most of us back on track and then 8.894 will put the rest except for some that installed some other strange versions floating out there.
Hi! Yea I'm having massive troubles here. I've downloaded around 10 different ROMs, and all but the Cyanogenmod 7.1.0.2 aborts the installation process. Even worse, I've removed the original ROM and cannot use anything computer-based (like flashtool, fastboot) because of this.
can I update/repair my kernel? (when I reboot I see the icon of the "freexperia" logo from a leftover installation).
So the only things I have are my boot-unlocked SE Xperia Arc S, and Clockworkmod (CWM-based recovery v5.0.2.6) and a possibility to transfer files to my sd card via usb cable.
I just bought my Arc S, but since the #"%"ยค# SE bloatware I got massive slowdowns and mermory-related issues very fast, so I wanted to uninstall some stuff. Of course it led me down a path of insane troubles so now I just want back to stock ROM. I've already wasted 10 hours of my life on this so soon a new phone will be cheaper
Any help is HUGELY appreciated.
you cant boot into the bootloader? hold down the volume buttons and the power button. once you do that you can flash the stock fxz files and get your phone back.
Long story short: Phone won't boot past "Unlocked Bootloader" warning; Recoveries won't stick; Unknown Error & Freezing when trying to Flash System.img
I own an ATT Locked Moto X, but went ahead and unlocked it by purchasing the oem code. No issues there.
I decided to go ahead and try rooting it too, and was able to flash TWRP as my recovery. Still, everything seemed to be looking good, until I tried hard rebooting (to see if root would last). Upon rebooting, I could not get past the warning sign, notifying me that the bootloader was unlocked. I waited, and waited, and restarted again, but all progress stopped there. I would be the first to admit that whatever happened was probably my fault; perhaps I flashed some files in the wrong order, or entered a wrong command into fastboot. I don't know, and frankly don't care. My only question is how to get out of this mess and back to rooting, or at the very least, back to stock ROM now that I'm unlocked.
Booting into recovery only leads to the red triangle over an open android mascot, with the "Android Recovery" title. So clearly TWRP didn't stick; I tried reflashing, but nothing lasts past reboot. Then I tried flashing Philz Touch instead, which, upon exit, notified me that root was not enabled. So I rooted, rebooted, and was finally able to see Philz Tough again, even though I still can't boot normally. That time, both Philz Touch as well as root seemed to have stuck.
With that minor victory I downloaded the latest firmware for my model and tried to flash the components over, thinking I had somehow corrupted the existing OS files, but here's where it gets particularly frustrating. I am able to flash every file except for system.img, even though I am using moto-fastboot, which I understand is a common mistake. I get no specific error code, simply "Unknown Error," upon which the phone is frozen in fastboot. The phone remains unresponsive until I hard reboot [back into fastboot], and see that, once again, Recovery is back to stock. So now I'm baffled. I can't seem to find a way to flash the system file, factory resetting doesn't work, and my recoveries are constantly reverted back to stock. Does anyone have any advice, or suggestions for what I could try next?
You try RSD lite?
Sent from my XT1058 using xda app-developers app
southern87 said:
You try RSD lite?
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
I was already downloading it just as I saw your post, as my last-ditch effort. It also failed, but it gave me "Unknown USB Error," which is all I needed, it seems. I tried a different USB slot on another side of the computer, and lo-and-behold, the flash finished.
I'm not sure what saddens me more, the fact that I pushed off making this post for hours, only to have the solution less than an hour after I do, or the fact that I never thought to try a different USB port... In any case, sorry for the uselessness of this post. I think I'll save rooting for another day though...
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
chg911225 said:
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
Click to expand...
Click to collapse
If your bootloader is unlocked, you should be able to either flash the stock factory image, or re-flash each partition separately through the tool-kit. Since you're getting remote errors with the toolkit, double check that you have the right drivers installed, the tookit and a search on the forum should help with that.
did you already try :
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Don't want to raise any alarms already but I shut mine down on Sunday night (Unlocked/ Rooted/ custom kernel & rom) in order to boot in Recovery and flash a new kernel version and:
1) The sdcard looked empty, it read ~ 26 GB free (I had no more than 20 gb free before reboot) and no folders whatsoever.
2) The phone was stuck at the Google logo heating up but going nowhere.
As I said don't want to start assuming things but the phone randomly going "nuts" and losing all data is scary... I had to spent my entire day yesterday flashing stock 5.0.1 back and re-setting up everything. I followed the guide posted above (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 oh, go with Method 2 and it will work fine).
Out of curiosity how does your SD look like from recovery? Oh, but then you say you can't even boot to Recovery. Which recovery do you have? (I had/have TWRP 2.8.3.1 ). Anyway to repair it you only need to be able to boot into Bootloader properly I guess.
okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
dorkydroid said:
okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
Click to expand...
Click to collapse
try stock 5.1.2 firmware
otherwise there is no fix that I know of
Sent from my KFFOWI using XDA Labs
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
dorkydroid said:
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
Click to expand...
Click to collapse
I fear I'm in the same boat. Which version of flash fire were you using?
Any further progress?
Sent from my Nexus 7 using XDA-Developers mobile app