Database Users

[Q] Stuck at bootloader screen

So, I've exhausted just about every bit of time looking, searching, and trying everything to get my Droid 2 back working again. I'll explain everything I've tried plus the current error messages I'm getting and see if someone else can help.
Before we start, yes, I do have the current moto drivers (plus old drivers too). Yes, I've uninstalled, reinstalled the drivers and RSDLite a million times, and yes, I've rebooted after installing everything to make sure that wasn't the problem.
Right now, I've flashed the bootloader back to d2.35. But I can flash back to d2.37.
Using RSDLite, every time I flash it doesn't make it past the BP pass through mode. Right as soon as it gets to it, the computer disconnects the phone, and on the phone is says:
SW update...
Complete
And when it reboots it is still at the bootloader screen. I load into recovery, and it tells me that:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
Once I wipe cache/factory reset, I reboot and it still goes to bootloader screen.
So, I load into recovery again, and this time it gives me the error:
E: Can't open /cache/recovery/command
I've used RSDLite 4.7+patch and flashed, same thing.
I've used RSDLite 4.8/4.9/5.6 and so on, everytime, same thing.
I've burned the Linux iso to disc, booted that up, and flashed that way, same results.
I think that pretty much sums everything up. I've searched every forum, I've googled everything about the phone known to man. Usually I just silently lurk the forums since I've never encountered a problem flashing any other phone, but this one has me stumped. Thanks ahead for any information.

What is the name of the sbf you're trying to flash?
Sent from my EncounterICS droid 2

VRZ_A955_2.3.20_1FF_01.sbf
size unpacked: 455,586,301
packed: 253,561,045

Ok and what were you trying to flash when it broke?
EDIT: that is the correct sbf but you might want to check the md5
Sent from my EncounterICS droid 2

Yea, check the md5. Also, try to manually mount it in the linux terminal.

I'll check the md5 tonight, didnt think about that. And what was i trying to flash..? And mount it in a linux terminal?
Sent from my SCH-I400 using XDA App

The only md5's I can find of the file to verify it with say that it's incorrect. I'm trying several different downloads now to see if I can find one that matches. Anyone have a working sbf that I can check my md5 with theirs just to make sure?

http://wiki.cyanogenmod.com/wiki/Motorola_Droid_2:_Full_Update_Guide
That's where my SBF's come from whenever I need to go stock. Never had a problem with it before.

MD5 checks out now, flashed on Windows XP, still fails at BP pass through, and tried again on Windows 7, still fails at BP pass through. I honestly have no idea what's going on with it. I know the phone disconnects right as soon as it hits BP pass through mode. Then, it reboots the phone saying it's complete, then I pull battery, then wipe/erase, and still goes to bootloader. On the screen it shows:
WinXP:
Failed flashing process. Failed flashing process. Phone[0000]: Error switching phone to BP Pass through mode [0x70BE]: phone disconnected
Win7:
Failed flashing process. Failed flashing process. Phone[0000]: Error switching phone to BP Pass through mode [0x70BE]: phone connected
Is there any config settings that need to be specified? Or is the phone just a complete paper weight now?

I'm not sure exactly. I've never used RSDLite. I've only ever flashed on Linux.
Are you able to wipe Dalvik cache just to be sure? Also, just as a fail safe, if you have an SD card in there take it out.
Here's what I found:
Computer engineer here. Registered so I could post this and hopefully help a few of you guys out
I was running into the same problem, with Win7 x64, RSD Lite 4.6, latest drivers. Did some investigation into the error log and looks like I found a bug in their programming. Go into the directory you installed RSD Lite (for Win7 x64 the default is C:\Program Files (x86)\Motorola\RSD Lite\) and look for a file that starts with "FlashErrorLog". Open it, and if you see something like this:
Code:
Line: 865
ERROR: \\?\c:\SPRecovery_ESE81.sbfwtƒyoþÿÿÿ‚qawñrawðiµ was not found.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashFileIO.cpp
then you are experiencing this same bug that I had (looks like adr3nalin3 had this problem too). For those fellow programmers out there, looks like they are copying the filename into uninitialized memory and not explicitly adding the NULL terminator, meaning it's pure luck whether the filename is recognized or not. Since the uninitialized memory produces random results, this explains why people have had it work after restarting their computer, trying several times, using a different computer, etc. Hopefully if you follow my instructions below, you will be able to make it work right away.
So the work around for this problem is to rename the file so that the real filename overwrites all the unwanted junk characters at the end. These junk characters are random, and they are likely to change each time you open RSD Lite.
Here are step by step instructions:
Go to the folder where you installed RSD Lite
Delete any files that start with "FlashErrorLog"
Right click on "SDL.exe" and click "Run As Administrator"
Move your recovery file to the root C:\ directory
Rename the recovery file to something short, like "r.sbf", so that you will have space left for the filename to overwrite the junk characters
Try flashing the file with RSD Lite - it will most likely fail, don't worry (if it works then good job, you are lucky )
In the RSD Lite folder, open the newly created FlashErrorLog... file
Count the number of junk characters after the real filename - for example if you have this error:
Code:
ERROR: \\?\c:\r.sbfqawñraï was not found.
then the junk characters are "qawñraï" and there are 7 of them, so we are going to add 7 extra letters to the real filename
Rename the file to add the same number of letters/numbers as junk characters in the log file. In this case, we need to add 7, so change the filename to something like "r1234567.sbf" - make sure you add the characters BEFORE the file extension (".sbf"), not after!
Point RSD Lite to the renamed file, click Start, and it should work!
Note that some of the junk characters can't be displayed in the log, so there might actually be 8 of them when you can only see 7, etc. Just repeat the process from step 6, adding 1 character at a time (don't remove any), and it should work after a few tries.
Note that just making the filename really long won't work, you need to be precise so that you only overwrite the extra stuff, nothing more and nothing less.
Click to expand...
Click to collapse
I hope that works for ya. Different phone, but same idea.

How do you wipe dalvik without clockwork recovery mod?
Sent from my SCH-I400 using XDA App

Try this tool
http://www.droidforums.net/forum/droid-2-hacks/161849-tool-ezsbf.html
It works 100% of the time for me. As long as you can get to the bootloader screen (by pressing the up button on the hardware keyboard while powering up), it will work. Please try it and let me know how it works for you. You will need a blank CD
Sent from my DROID2 using XDA App

I already tried that. It didnt work for me. Still get the same error messages as i stated in OP and after i wipe data it still boots to the bootloader.
Sent from my SCH-I400 using XDA App

ripdarkness said:
MD5 checks out now, flashed on Windows XP, still fails at BP pass through, and tried again on Windows 7, still fails at BP pass through. I honestly have no idea what's going on with it. I know the phone disconnects right as soon as it hits BP pass through mode. Then, it reboots the phone saying it's complete, then I pull battery, then wipe/erase, and still goes to bootloader. On the screen it shows:
WinXP:
Failed flashing process. Failed flashing process. Phone[0000]: Error switching phone to BP Pass through mode [0x70BE]: phone disconnected
Win7:
Failed flashing process. Failed flashing process. Phone[0000]: Error switching phone to BP Pass through mode [0x70BE]: phone connected
Is there any config settings that need to be specified? Or is the phone just a complete paper weight now?
Click to expand...
Click to collapse
read
http://droid.koumakan.jp/wiki/SBF
it's for the 2 global but should still work
also try deleting rsd lite error log
program files/motorola/rsdlite/ flasherrorlog11_15_24_45.log
yours will be different

Yeah, I don't know what it is. I think it's pretty much bricked. Nothings worked, and nothings even remotely came close to fixing it. I've tried everything. The only thing I notice is as soon as it hits BP pass through, the phone gets disconnected, and it doesn't reconnect till the phone reboots after saying:
SW update...
Complete.
And then it reboots into bootloader. So whatever it is, it's something to do with that.

Failed root need help! Samsung galaxy note 3

Hello everyone,
2 days ago i tried rooting my friends phone using kingo root.
I know its a one-click root app and easy but it didnt work.
It got stuck at 40%, its when it powers on the phone to download mode.
unplugged the phone and removed battery, the phone booted normaly and everything on the phone was still intact and opperating normaly. ( glad it didnt write anything to the phone yet. )
So i adviced my friend there is an alternative way to do it (sorta) manualy and flash it with odin. I did it before on my own phone and of some friends but theres a higher chance of human errors. He agreed so we proceeded and i found a neat guide that walks us past this proces.
The guide can be found on ( cant post links yet): galaxynote3root dot com / galaxy-note-3-root / how-to-root-galaxy-note-3
Or found searching for this google: "galaxy note 3 root"
So i got all the necesary things, got the right files for the right model (sm-n9005) running on android 5.0 and started the proces.
Now in odin it didnt succeed and i dont really remember the exact message but it emidiately failed when it started to use the download mode. (i can use download mode but it stops when it starts sending)
at this point i couldnt use the recovery mode (volume up + home button + power button) but could use the download mode (volume down + home button + power button). it also didnt boot and gave an error that i needed to repair my firmware.
Now i knew i had to fix it and i read that i can go back to the official firmware from samsung using odin also.
So i head over to ( sammobile dot com ) and got the right firmware (Netherlands, Vodafone).
After getting the right firmware i started it and it failed again at the start of the download mode.
Odin gave an error about the EXT4 partitions. after some research i found out i needed to get a .PIT file that repartitions it for you while flashing. So i tried the PIT file for the SM-N9005 32GB, it didnt work... again an error....
I wasnt sure if its 32GB so i tried the 16GB PIT file also. this one gave another error.
So the errors were something like this :
16GB Error: whrong size
32GB Error: EXT4 102400 < 408600
My excuse for not the exact error, ill look it up later.
Thanks in advance for reading about my problem!
I really hope somebody knows whats whrong and how to fix it if it can be fixed.
Any help would be greatly appreciated!:fingers-crossed:

Which firmware/baseband version are you running

Did you use chainfire autoroot: https://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip ?

Try another Odin version
Sent from my SM-N900 using Tapatalk

[Hard Brick] Nexus 6P 7.1.2 Beta 2 [Solved]

Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.

@rmorris003
You said the phone won't even power on. You mean no Google? Hold the power button down for a couple of minutes and see if it will reboot. If not put it on a charger, and after fully charging try the long press power button again. If you can get it to start, try to put it in fastboot mode. (ie. power+vol dn). If you can get to bootloader you can send fastboot commands and fix it. If you can get to this point, there are instructions here.

rmorris003 said:
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
Click to expand...
Click to collapse
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...

5.1 said:
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
Click to expand...
Click to collapse
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.

rmorris003 said:
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
Click to expand...
Click to collapse
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...

5.1 said:
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
Click to expand...
Click to collapse
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.

rmorris003 said:
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
Click to expand...
Click to collapse
You disabled driver signature and rebooted your computer? Then installed Qualcomm drivers from the thread I linked you to? I think you have to reboot your computer once more...
Good luck...

I held the power and vol down and now it shows up under com ports so this is a good sign.

Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.

rmorris003 said:
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
Click to expand...
Click to collapse
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...

5.1 said:
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
Click to expand...
Click to collapse
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.

rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
You could report your experience in the other thread. Maybe it could help other users who faced the issue you had. :good:
Cheers...

rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!

Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT

Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
Falitheman said:
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Click to expand...
Click to collapse
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...

5.1 said:
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
Click to expand...
Click to collapse
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:

Falitheman said:
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Click to expand...
Click to collapse
Hey,
What version of qpst did you install?
Good luck...

5.1 said:
Hey,
What version of qpst did you install?
Good luck...
Click to expand...
Click to collapse
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back

Falitheman said:
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Click to expand...
Click to collapse
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...

5.1 said:
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
Click to expand...
Click to collapse
I tried with the version you suggested and i got the same error i just had. Can you send me your version so i can see if that works?

Need help. Tried rolling back to Kit Kat

Ok, had a slight issue getting everything to work with windows 10. Anyway i was able to get everything going eventually however when I ran "flash-all" i wound up errors all the way and ended with
Getvar: version:bootloader FAILED (command write failed (no error))
Press any key to exit.....
Nothing installed, I'm stuck in bootloader. What can i do from here?

Superman691973 said:
Ok, had a slight issue getting everything to work with windows 10. Anyway i was able to get everything going eventually however when I ran "flash-all" i wound up errors all the way and ended with
Getvar: version:bootloader FAILED (command write failed (no error))
Press any key to exit.....
Nothing installed, I'm stuck in bootloader. What can i do from here?
Click to expand...
Click to collapse
try to flash bootloader v4.23 first and then flash factory image

Having trouble attempting that now as well, laptop doesn't recognize Nexus anymore, it's listed as unknown usb device. Command prompt tells me "waiting for any device" when I try to do anything

Any other ideas? Or do I have a new paperweight on my hands

Brought used OP2.. Now I have a problem

Hello!
I hope this forum is still alive!
I've brought a bricked OnePlus 2 today.. Guy said it got bricked when he flashed wrong ROM.. Not sure if I do believe him tho.
Anyways I've tried to boot up the phone, it's stuck at powered by Android screen.. Tried to boot into fastboot.. It boots.
So I've figured that it must be a software problem, as it boots into fastboot and powers up to the first screen.
Phone does not bootloop - it stays on the screen forever.
Ok.. Went home, searched for some help..
I've done the methods posted here.. This is what I get:
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_main0.bin: OK
userdata.img: FAILED open or read
userdata_64G.img: FAILED open or read
rawprogram0.xml: FAILED
rawprogram0_64G.xml: FAILED
NON-HLOS.bin: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED open or read
cache.img: FAILED open or read
persist.img: OK
recovery.img: FAILED
system.img: FAILED open or read
btw, I've typed in cmd unlock bootloader.. it's unlocked.. It also flashes the twrp fine, but it's like it's not flashed.. just not there.. Cant boot to it.
I've also tried the method from XDA called firs aid (or something like that) It goes trough OK Kind fast tho. but it does not boot.
Device is recognised as Qualcomm HS-USB QDLoader 9008 (COM4).
Any help to get device up and runing I would really appreciate it.

It works. HUGE THANK YOU TO @Sam Nakamura who helped me over on OnePlus forums.. You da man, Sam!

Best 20€ I've ever spent!!

Great to know that it worked. Mind sharing it here?

drwierdo said:
Great to know that it worked. Mind sharing it here?
Click to expand...
Click to collapse
Sure thing!
I've downloaded:
oos-3.6.0-oneplus2-fastboot-20170824.zip
And install it trough fastboot, and it worked!