D2G Boot Problems SBF - Droid 2 Global General

Hey all, hope you can help, ive been reading forums all day but cant find out exactly if the problem I have is fixable or not....
Im working on a D2G, last week something happened and it was stuck at the motorola screen, would not load android.
I did the usual stuff, Hard Reset, wipe cache etc. but it did not help
Today I attempted to reload SBF files using RSD lite 5.6
I tried two of the SBF files located here: hxxxs://sites.google.com/site/motosbf/droid-2-global-sbf-files
RSD seems to work fine, I started the bootloader, connected cable, it was recognized on the phone and in RSD and loaded the files to 100% complete, and then it reboots the phone.
After reboot, I get the same thing each time:
Bootloader D0.11
Err: A5, 70,70,00,1F
NewMap: Blank
Svc Required
Battery OK
OK To Program
Connect USB
Data Cable
If any of you guys can point me in the right direction or let me know if im fuct, would be appreciated!!
-Mongrat

Mongrat said:
Hey all, hope you can help, ive been reading forums all day but cant find out exactly if the problem I have is fixable or not....
Im working on a D2G, last week something happened and it was stuck at the motorola screen, would not load android.
I did the usual stuff, Hard Reset, wipe cache etc. but it did not help
Today I attempted to reload SBF files using RSD lite 5.6
I tried two of the SBF files located here: hxxxs://sites.google.com/site/motosbf/droid-2-global-sbf-files
RSD seems to work fine, I started the bootloader, connected cable, it was recognized on the phone and in RSD and loaded the files to 100% complete, and then it reboots the phone.
After reboot, I get the same thing each time:
Bootloader D0.11
Err: A5, 70,70,00,1F
NewMap: Blank
Svc Required
Battery OK
OK To Program
Connect USB
Data Cable
If any of you guys can point me in the right direction or let me know if im fuct, would be appreciated!!
-Mongrat
Click to expand...
Click to collapse
Try Posting this in the correct forum

you tried to flash wrong SBF
try the 2.3.4 sbf aka 1FF-p3_droid2we_cdma_droid2we-user-2.3.4-4.5.1_57_D2GA-59-120117-test-keys-signed-Verizon-US.sbf
https://sites.google.com/site/motosbf/droid-2-global-sbf-files
or if you want root just
New All-in-One D2G recovery & Root CD for .629 update(EzSbf method) **D2G A956 only**
or http://forum.xda-developers.com/showthread.php?t=1592154
and http://rootzwiki.com/topic/23207-how-tounbricking-downgraded-629-root-normal-function-ota-629/

Related

i may have bricked my phone please help

i cant believe i did this but i have a sprint tp2 and i accidentally install the wrong rom, i installed 1.8b_Sense_2.5_2012_Full, and after the update the phone wont turn on so i cant even do the bootloader. and hard reset either, nothing is responding. is there any way i can get out of this with a working phone?? would the people at sprint be able to help? and please no smart ass comments im really bummed out about this right now
It should be ok if you only install a gsm rom. If you installed a gsm unlocker than it is bricked. Just push the bootloader buttons with the phone off. If it doesn't go to bootloader it is bricked.
i installed the rom but i think the damn thing CAME with the radio unlocker inside the rom. i cant get into bootloader...
please help
If you can't get into bootloader and it wont turn on it is bricked.
Not to hijack the thread, but on the subject of bricking the phone...
I tried to install Hard SPL using SSPL Manual (downloaded from a link on ppcgeeks.com). I ran it from the phone, and the screen blanked as normal, but no USB device was detected after doing so and the manual Hard SPL would not work either.
I tried to reset and remove the battery. The phone will not turn on, will not enter boot loader mode, nothing! EXCEPT for one thing, when I plug in USB now, it is detected as a Qualcomm CDMA Technologies MSM. No driver though (Win 7 or Win XP).
Is there any way to recover from this?
Hi!
Download and install this:
_ftp://up.ppcgeeks.com/Touch%20Pro%202/Stock%20ROMs/RUU_Rhodium_W_Sprint_WWE_1.21.651.3_RS_1.96WF_NV_SPCS_1.42_0430_PRL60652_Ship.exe
I think it help you.
ted2001 said:
Hi!
Download and install this:
_ftp://up.ppcgeeks.com/Touch%20Pro%202/Stock%20ROMs/RUU_Rhodium_W_Sprint_WWE_1.21.651.3_RS_1.96WF_NV_SPCS_1.42_0430_PRL60652_Ship.exe
I think it help you.
Click to expand...
Click to collapse
Hi, I have the exact same issue as the member above. I tryed to go to the ftp site you reccomended, but can't download. Can you please help! I cant sleep or think of anything else. Can't believe I did that to my phone.
go here and then to touch pro 2 stock roms. ftp://up.ppcgeeks.com/
Thanks for the replies.
I can't load the stock ROM since the phone is not recognized by ActiveSync. While you can see it when you connect USB, it isn't actually usuable as there is no driver loaded for it. And many drivers I've tried for it do not work either.
I did try [to install the ROM] though just to make sure there was no magic going on behind the scenes, but no go.
EDIT: Grammer fix

Help Me for my Xoom

Hi,
I need help because I've brikked (i think...) my Xoom wifi
When I turn on, on display appear logo Motorola's dual-core and top left:
SOS 0x0002 failed image
Starting RSD mode 2
My iMac (with SDK) does not detect it. I tried to win with RSD Lite 5 but even that is detected by the PC.
Help me please!
I have same problem any one can help please ?
You will need to use the RSD application and use something simular to this:
THIS IS FOR THE VERIZON 3G VERSION:
http://forum.xda-developers.com/showthread.php?t=980803
Still looking for the WiFi SBF
I used this yesterday after using the One click Unroot which broke my Xoom.
I try but pc will not recognize through adb or RSD 5.0
abuaban said:
I try but pc will not recognize through adb or RSD 5.0
Click to expand...
Click to collapse
Correct ADB would not work for me but RSD 4.9 did. I'm guessing you already have the drivers installed and set correctly in device manager.The link I posted is for the 3G version only a WiFi version is not available yet. Just making that clear.
i just went thru this last night! What worked for me was at start up hold power+volume down while plugged in to computer. Rerun the one click root. Then (my problem) flash back to stock kernal before trying to do whatever it is you are trying to do.

[Q] Oh my. SBF failed. Am I out of luck? !Resolved!

I have (er, HAD) a rooted stock droid 2 global. I read copious amounts of info to guarantee that my move from a blur-laden rom to a considerably-blur-LESS rom (Hexen) would go as pain free as possible. I printed out all the rsdlite info I could find, located all the appropriate files and drivers, found a good, md5 verified stock sbf, and prepared to make my phone better.
Step-by-step I re-read the instructions until I thought I had it right. I started, and waited for the final step "phone[0000]: phone is being rebooted."
It never came. I did everything right and it ended with rsdlite's status on the phone reading :"failed flashing process. phone [0000]: error switching phone to bp pass through mode (0x70bE); phone disconnected," and my pc giving me a "found new hardware: flash mdm6600" message. I am not able to find a driver for the mysterious new device that crops up as my phone is trying to reboot.
My phone sits unperturbed, still reading "SW Update in progress..." If I try to shut it off, it doesn't respond. And when I battery-pull and put the battery back in, it starts up immediately with a "Bootloader D0.11 Code corrupt..." message.
I cannot make it go into bootloader mode. All it does it what I've told you.
So, you tell me, please, am I screwed? Am I the proud owner of a 3-month old brick?
Dan
resolution
My phone is back.
Half the reason (okay 9/10ths) I posted was because I thought my phone was finished. I had searched thru here and the web many times during each SBF re-attempt, and I seriously think there were at least a dozens tries minimum.
No documentation was found for my issue: Bootloader D0.11
On my last search I found a set of Motorola USB drivers that were a newer version than what I had found every other time. They made the difference. The drivers that *worked* were V4.7.2.0. The previous drivers were 4.6.5.
I hope this helps...
Dan
What did you do to get out of the bootloader D0.11 screen?
Well, like I've said, all I did was use a different set of Motorola USB drivers. The drivers made the phone be recognized by the PC during the RSDlite process.
These are the drivers I used: Motorola_Driver_Installer_v4.7.2.0.msi.zip
All I did was RSD *again* exactly as I had been doing.
The only differences are that the whole process begins with the bootloader error message being displayed on the phone. RSDlite will recognize the phone when it gets to that part of the process. And when you get to the "switching the phone into BP mode" message and the simultaneous PC message "found new hardware: flash mdm6600" the pc message appears *very briefly* (presumably because *now* it has MDM6600 drivers) and the RSD process continues, exactly as it was supposed to.
I hope I've answered your question clearly. And I hope this helps you with your D0.11 error.
Just so that you know, I am *no* expert by any means when it comes to this stuff. I'm just like you: looking for answers.
Good luck,
Dan
Thanks for the help. After two hours last of searching and downloading last night, I finally got my wife's droid restored.

[Q] My Alcatel One Touch Blaze Glory X 918N won't open.

Hi everyone!
I just had a problem with my android phone. It is rooted, and I tried to downgrade my GB 2.3.6 to 2.3.5. I followed a certain instructions about this, using a Flash Tool with a scatter-file Europe_2.3.5.txt. After I downloaded it, my phone won't open now. I'm afraid I hardly bricked it.
It won't open, won't show if it's charging (but i'm pretty sure it is), can't be booted to recovery mode or download mode, can't be detected by PC when I connect it to the USB. No response at all. Please, if there are any people who can help me out there, help me. I'm starting to panic about it.
Chichakhorn said:
Hi everyone!
I just had a problem with my android phone. It is rooted, and I tried to downgrade my GB 2.3.6 to 2.3.5. I followed a certain instructions about this, using a Flash Tool with a scatter-file Europe_2.3.5.txt. After I downloaded it, my phone won't open now. I'm afraid I hardly bricked it.
It won't open, won't show if it's charging (but i'm pretty sure it is), can't be booted to recovery mode or download mode, can't be detected by PC when I connect it to the USB. No response at all. Please, if there are any people who can help me out there, help me. I'm starting to panic about it.
Click to expand...
Click to collapse
well.. your phone is hard bricked,.
solution: JTAG

[Completed] How to install ROM on Vonino Pluri Q8 tablet ?

Hi there,
Today i've received this tablet. All good and dandy until it notified me it has an update so obviously i've gone and do the update. Surprise.. after reboot, update installment and so on the device won't boot anymore at all, and recover mode doesn't work to enter.
I've found official ROM package on their site:
ftp.vonino.org/public/Firmware/Vonino_Tablets/Pluri%20Q8/Orange%20Version/Android%206.0/
Tablet can connect to the PC, but it isn't recognized because "some drivers" missing. How can i install this ROM on the tablet from my pc ?
Thank you.
Hi,
I can't find anything about it on xda or anywhere. You'll need to contact the manufacturer for drivers and instructions on flashing their firmware.
Good luck!
After i tried like almost the entire day i got the tablet in rescue mode or fastboot mode..
I've wiped/data or factory reset and the same happens... it stays in a loop when boot at logo.
I've let it to do so until the battery went dead from 100% and still the same.
I have official ROM but can't install it at all. I think the bootloader is locked?! And it doesnt even unlock it when using some fastboot commands
Also can't install nothing from SD card and when tryin to use ADB the PC can't see the device, but when using fastboot I can work on it.
In rescue mode i've done some root integrity check and at the end of the check some /system files are modified. I believe this is causing the entire problem.
denede said:
After i tried like almost the entire day i got the tablet in rescue mode or fastboot mode..
I've wiped/data or factory reset and the same happens... it stays in a loop when boot at logo.
I've let it to do so until the battery went dead from 100% and still the same.
I have official ROM but can't install it at all. I think the bootloader is locked?! And it doesnt even unlock it when using some fastboot commands
Also can't install nothing from SD card and when tryin to use ADB the PC can't see the device, but when using fastboot I can work on it.
In rescue mode i've done some root integrity check and at the end of the check some /system files are modified. I believe this is causing the entire problem.
Click to expand...
Click to collapse
Typically, on devices I know of, it's fastboot that you would use to flash factory images. So you should be good there. But again, I don't know if that is how your device works too. And it would also typically not matter what's been altered on your device, system wise, you would simply flash the appropriate images with fastboot.
So I'd still say you need to determine the correct procedure to flash the files you got from their site. Perhaps there site has instructions? Or a support number for help of its not working as it should?
I've talked with the support. They gave me a link with an official ROM, a different one that the one that was from the site. But they didn't even told how to use it, LOL.
Have the damn files and don't know what to do with them, OMG.
I've placed the zip archive on SD card and tried to use the option from rescue mode with 'update via sd card". The zip archive is visible but after i select it says Installation aborted :|
I've googled around and maybe my tablet needs to be at over 50% power... but it was plugged into the wall it should've worked.
edit: 100% and no good...
edit2: they sent me another e-mail with a pdf file in which it is explained how to flash their device.

Categories

Resources