Well, here is the story:
I had downloaded a SBF file for the DROID 2 not paying attention to the fact that it said A955 and after I had accidently flashed it I noticed it said "Do NOT flash for the DROID 2 GLOBAL" and I now have a paper weight that only boots into the DROID 2 bootloader. D2.37. it says Error: A5,70,00,00 MEM_MAP Blank Service req'd
Every time I try to flash a droid 2 global stock SBF it sais Critical Error FEBE 0047. I think the only way for me to unbrick my phone is to flash a SBF of the Droid 2 Global D0.11 Bootloader file, or any Droid 2 Global Bootloader file, since SBFs for The Droid 2 Global and the Droid 2 Global R2D2 both work on my phone, Would there be any way to fix my problem, or at least SBF-Flash a Bootloader into my phone, and if there is a lockup would there be a way to bypass the SBF error-s?
Update: Tried exSBF as Gasai Yuno said, this is my results:
On Screen: Waiting for phone: Connected
>>Uploading RDL03: 100.0x
--OK
>>Verifying Ramloader
-- OK
>> Executaing Ramloader
RX(7) : [02}ERR[1e]G[03]
!! Failed
>> Rebooting
and my phone still has the Critical Error FEBE 0047
Tried with a different SBF and this is my result:
Indexes 0-14 Unexpected Chip 32
Bunch of numbers from slots 0-14
Then:
Droid X found.
?? uploading RDL03
Uploading 100% OK
>>Verifying Ramloader
--OK
>> Executing Ramloader
Expected ACK
RX(9) [02]ERR[G[03]08
!! Failed
>> Rebooting
and still the FEBE 0047
sd_shadow said:
the 4.5.629 SBF is out GB2.3.4/4.5.629 NS Device Full SBF
are you sure you have a D2G?, bootloader doesn't usually change if you flash wrong SBF, just says
Bootloader
D0.11
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Batery OK
OK to Program
Transfer Mode:
USB
Click to expand...
Click to collapse
I'll try that SBF, but I'm not sure if its a D2G boot loader, it used to be D0.11 but after flashing the Droid 2 SBF I see the 2.37 with that error, but let me try that sbf
jabberwockish said:
What version number was the D2 SBF file you flashed?
Have you tried any other D2G SBFs, or only the 2.4.29 one?
I am not certain, but I don't think any of the available D2G SBFs include a bootloader. When/if an SBF for 4.5.629 leaks, it should include the updated one.
Click to expand...
Click to collapse
I used the 2.4.29, the 2.4.33 and the 2.4.608 ones, but I'll try the one SD shadow mentioned
Update: Well, I had found a Full SBF file, and flashed it, somehow that got through my FEBE 0047 problem and my phone is flashing now...
Try ezSBF.
Gasai Yuno said:
Try ezSBF.
Click to expand...
Click to collapse
Tried that with the 1KDStaz_D2G_2.4.29 file,and more, and this is what I get:
On Screen: Waiting for phone: Connected
>>Uploading RDL03: 100.0x
--OK
>>Verifying Ramloader
-- OK
>> Executaing Ramloader
RX(7) : [02}ERR[1e]G[03]
!! Failed
>> Rebooting
and my phone still has the Critical Error FEBE 0047
Tried with a different SBF and this is my result:
Indexes 0-14 Unexpected Chip 32
Bunch of numbers from slots 0-14
Then:
Droid X found.
?? uploading RDL03
Uploading 100% OK
>>Verifying Ramloader
--OK
>> Executing Ramloader
Expected ACK
RX(9) [02]ERR[G[03]08
!! Failed
>> Rebooting
and still the FEBE 0047
What version number was the D2 SBF file you flashed?
Have you tried any other D2G SBFs, or only the 2.4.29 one?
I am not certain, but I don't think any of the available D2G SBFs include a bootloader. When/if an SBF for 4.5.629 leaks, it should include the updated one.
the 4.5.629 SBF is out GB2.3.4/4.5.629 NS Device Full SBF
are you sure you have a D2G?, bootloader doesn't usually change if you flash wrong SBF, just says
Bootloader
D0.11
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Batery OK
OK to Program
Transfer Mode:
USB
sd_shadow said:
the 4.5.629 SBF is out GB2.3.4/4.5.629 NS Device Full SBF
are you sure you have a D2G?, bootloader doesn't usually change if you flash wrong SBF, just says
Bootloader
D0.11
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Batery OK
OK to Program
Transfer Mode:
USB
Click to expand...
Click to collapse
I'll try that SBF, but I'm not sure if its a D2G boot loader, it used to be D0.11 but after flashing the Droid 2 SBF I see the 2.37 with that error, but let me try that sbf
jabberwockish said:
What version number was the D2 SBF file you flashed?
Have you tried any other D2G SBFs, or only the 2.4.29 one?
I am not certain, but I don't think any of the available D2G SBFs include a bootloader. When/if an SBF for 4.5.629 leaks, it should include the updated one.
Click to expand...
Click to collapse
I used the 2.4.29, the 2.4.33 and the 2.4.608 ones, but I'll try the one SD shadow mentioned
Update: Tried the SBF jump failed again. I really think I should flash a SBF of the bootloader, if there us a possible way there is a boot loader file, would there be a way for me to extract it from a SBF file?
Sent from my Glitched Icy Fassy using XDA
Attaching the bootloader image.
Thanks, I'll try it as soon as I reach my desktop
Update: Ok, that file did not work either, I think I'll try to edit a Droid 2 SBF and sneak the bootloader into there if it's possible :s )
Sent from my SCH-I500 using XDA
Gasai Yuno said:
Attaching the bootloader image.
Click to expand...
Click to collapse
I don't believe I have encountered this file before. Is it possible flashing this onto a D2G that has received the .629 update would enable downgrading to an older stock firmware (2.4.x or 4.5.60x) without bricking?
Edit: Never mind, I should have read this thread before posting that. Nice to know some more experienced folks had the same thought, though!
sd_shadow said:
the 4.5.629 SBF is out GB2.3.4/4.5.629 NS Device Full SBF
Click to expand...
Click to collapse
I'm not sure I believe that file is really compatible with retail D2Gs. Forgive my skepticism, but (1) the file name is in a completely different format than previous leaked SBFs, (2) the file name includes "4.5.1_57" rather than "4.5.629," and (3) that poster's grasp of English seems…tenuous (by which I mean no insult to him or her; only that it makes accurate understanding of their intended meaning more difficult).
jabberwockish, I'm afraid that 1FF-p3_droid2we_cdma_droid2we-user-2.3.4-4.5.1_57_D2GA-59-120117-test-keys-signed-Verizon-US.sbf is fully compatible with retail A956. Sorry to disappoint you.
I also regret to inform you that people have used this SBF image to produce the unbricker.
Please accept my condolences.
You have a wicked sense of humor, G.Y. Thanks for the information.
R2D2
Gasai Yuno said:
jabberwockish, I'm afraid that 1FF-p3_droid2we_cdma_droid2we-user-2.3.4-4.5.1_57_D2GA-59-120117-test-keys-signed-Verizon-US.sbf is fully compatible with retail A956. Sorry to disappoint you.
I also regret to inform you that people have used this SBF image to produce the unbricker.
Please accept my condolences.
Click to expand...
Click to collapse
I need help to unbrick an R2D2 , can you tell me where to start ?
AutoTechR2D2 said:
I need help to unbrick an R2D2 , can you tell me where to start ?
Click to expand...
Click to collapse
start here my list https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
droid wiki http://droid.koumakan.jp/wiki/Welcome
read how to boot to recovery and bootloader, flash sbf
you will need sbf, rsd lite, and moto driver installer
find those in my list
or use ezsbf for d2, easiest but you will lose r2d2 theme and sounds, but you won't need sbf, drivers, or rsd lite
Just curious if anyone knows if this might work for the Photon Q eventually.
http://forum.xda-developers.com/showthread.php?t=2225022
We don't need that, Photon Q BL is normally unlockable officially.
Yeah, but WOULD it work if we wanted to unlock that way?
Just curious.
It would - but your warranty would still be void (because if they are actually checking it, they will use the phone's fastboot).
Yes.
The result is the same, no matter if you use the official or the unofficial way.
The qfuse is blown > the bootloader is unlocked > the moto warranty is void.
No difference.
Thanks. That's all I was wondering.
I could see where someone would prefer to use an unofficial method. Seems like Moto wants a lot of info for "permission" to mod a phone. So, maybe someone would want to unlock, but not go through registering all of that with Moto.
Warranty, swarranty. Not too concerned about that personally. My experience with warranty is that they will find a reason not to honor the warranty anyway.
kabaldan said:
Yes.
The result is the same, no matter if you use the official or the unofficial way.
The qfuse is blown > the bootloader is unlocked > the moto warranty is void.
No difference.
Click to expand...
Click to collapse
Just wondering, what exactly is the "qfuse" ? I am deducing that it is a file that tells if the Q's boot loader has been unlocked, but does it determine that fact regardless of if it's unlocked officially or unofficially? And, if done so unofficially, would re-locking the boot loader change the "qfuse" and dupe the Motorola team from determining if the boot loader has ever been unlocked? Thanks!
Moto Q stock with Arrrghhh's kernel v.0.10
galacticservant said:
Just wondering, what exactly is the "qfuse" ? I am deducing that it is a file that tells if the Q's boot loader has been unlocked, but does it determine that fact regardless of if it's unlocked officially or unofficially? And, if done so unofficially, would re-locking the boot loader change the "qfuse" and dupe the Motorola team from determining if the boot loader has ever been unlocked? Thanks!
Moto Q stock with Arrrghhh's kernel v.0.10
Click to expand...
Click to collapse
Here's some info I found:
"There are two kinds of electronic fuses: Qfuses and efuses. efuses are programmable, usually by software once and by JTAG multiple times. However, Qfuses are WORM according to the information I have, which means iff the Milestone has a security Qfuse, and it is blown, then this cannot be reversed. There is usually no software programming to the Qfuses available, it is blown once during manufacturing/initial programming."
Source
Has anyone actually tested this on the photon Q and can say beyond a shadow of a doubt? I am guessing I am not the ony person who really wishes they could unlock the bootloader but can't because moto said no when they tried the official way, but I worry that trying an untested method for another phone has a chance to brick.
Every Photon Q is unlockable the official way, even from CSpire. You have a typo somewhere.
First off I'm a noob at unlocking bootloaders. This will be my first time. I have rooted, SIM unlocked and flashed before, but never unlocked the bootloader. The reason for unlocking is I want to flash CM 10.1/10.2.
So I recently picked up a cheap Droid Razr HD XT925 Locked to Rogers. I have unlocked and rooted it. It is running jellybean 4.1.2
I have been looking around on how to unlock my bootloader when I came across a handy tool called the Motorola Bootloader Unlocking Program. Unfortunately I am not allowed to post an outside link. So please google it. It supports my device. So far I have downloaded the android SDK and installed my devices latest drivers. Is it safe to proceed? Is it a good idea to unlock my device via this method or consider another method and if so which?
Thanks so much for any help you can give me
It's a Motorola service for a Motorola phone, how would it not be safe?
Go ahead and unlock it.
I unlocked mine 2 months ago, and or was the first time i unlocked a phone and my first smartphone.
Nothing to worry about
Go ahead and unlock it of that what you want.
Sent from my XT925 using Tapatalk 4 Beta
+1
very safe , just make sure you don't interrupt any process
Hi, my question is: if bootloader is unlocked, is it possible to relocked it and then re-stock all? I mean how can if i unlocked bl to return to complete stock rom and bl blocked?
You can relock but the bootloader will indicate that it previously has been unlocked.
nupi said:
You can relock but the bootloader will indicate that it previously has been unlocked.
Click to expand...
Click to collapse
In which way it will indicate that?
..so we will need of some hack like on samsung to reset that count, right?
I'm not sure if the Moto G is like the Moto Atrix HD but unlocking the bootloader blows one or more fuses which can't be fixed. Maybe the Moto G is the same?
http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html
audit13 said:
I'm not sure if the Moto G is like the Moto Atrix HD but unlocking the bootloader blows one or more fuses which can't be fixed. Maybe the Moto G is the same?
http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html
Click to expand...
Click to collapse
Interesting reading. If motorola were ever to stop issuing bootloader unlock codes it could potentially be hacked.
obvious said:
Interesting reading. If motorola were ever to stop issuing bootloader unlock codes it could potentially be hacked.
Click to expand...
Click to collapse
I had an Atrix HD for about 5 days before I decided to unlock the bootloader in order to load a custom rom. I tried locking the bootloader to no avail. Not a big deal since it didn't cost me anything when I did a hardware upgrade and the phone has been rock solid.
The Atrix HD is a great phone with the right rom.
The Moto G's stock looks very much like an AOSP rom.
I want to reloack my bootloader on my Motorola Electrify M xt901 and read on the Motorola site that is possible if you can find a " Motorola signed image " for my device. I got a hold of them but they will give it for there newer devices but will not support mine. Any help on this matter will be appreciated.
Billc47 said:
I want to reloack my bootloader on my Motorola Electrify M xt901 and read on the Motorola site that is possible if you can find a " Motorola signed image " for my device. I got a hold of them but they will give it for there newer devices but will not support mine. Any help on this matter will be appreciated.
Click to expand...
Click to collapse
according to the information i found on your phone, once you unlock the bootloader it can NOT be re-locked.
i could be wrong, but that's the answer i read from a couple post of your exact question.