INSTRUCTIONS:
Download the 90.78ch Boot Loader from here. Boot Loaders lower than the version you currently have (eg. attempting to flash 90.73 on a bootloader 90.78 milestone CAN brick, and I think you can flash back to the stock 90.78 bootloader after flashing this one, untested). Unpack to safe location.
Install RSD Lite & Drivers (mentioned in another thread). Choose the SBF with 90.78ch boot loader in it in the RSD Lite window.
Reboot in bootloader mode, via Holding Up while turning milestone on (you'll get screen like BOOT LOADER 90.78ch READY TO PROGRAM, BLAH BLAH).
Start the update from RSD Lite. When it reboots the phone, hold up on the Dpad to re-enter boot loader mode, or else it will succeed (and you won't get a brick) but RSD Lite will say fail. To exit boot loader, press Power for about three seconds, and then turn it back on again.
DO NOT REMOVE USB CABLE WHILE THE SCREEN SAYS "SW UPDATE IN PROGRESS". IF ON A LAPTOP, CONNECT CHARGER. IF THE BOOT LOADER FAILS TO FLASH, YOU WILL HAVE A BRICK.
If all goes well, Boot loader should say 90.78ch. You're running the latest bootloader, originally from the XT702 (Sholes Tablet?)
WARNINGS:
I am not responsible if you blow up your Milestone or it randomly starts swearing at you for flashing a dodgy boot loader or your girlfriend hates you after flashing the boot loader. You are on your own. Read the instructions carefully. I also will not offer support if you just say "Doesn't work". Tell me what didn't work eg. "Got stuck at 53% upload, then said fail" or "BSOD while Flashing!"
Enjoy the latest boot loader.
Is there any reason to flash this "new" bootloader?
Is this one not locked?
I am not sure I get it.
It's still locked, but it's the same one that the XT702 device uses. That would mean if the bootloader on that device is hacked, the hack could be useful for us people with Bootloader 90.78ch installed.
EDIT: I have a hunch that the "ch" part just means a Chinese version of the boot loader, which might mean some slight code mods...
nice work, thank's!
Coburn64 said:
EDIT: I have a hunch that the "ch" part just means a Chinese version of the boot loader, which might mean some slight code mods...
Click to expand...
Click to collapse
Actually "ch" is the country code for switzerland
what are the benefits?
Coburn, I see the logic in what you are doing. It is a pretty good idea.
However, I believe that the XT702 is not exactly a popular phone, thus the chances of its booloader being hacked are even fewer.
By contrast, if you were able to flash a Droid X bootloader on our milestone....now THAT would be something.
However, I am assuming that is not possible due to the fact it is a CDMA [Verizon] phone.
Absolutely no reason to do that for now,only if you want to see how easy is to brick a perfectly good device.i seriously doubt that ANY bootloader wiil be totaly bypassed (unlock is out of the question).
Sent from my Milestone
I did it!
yesterday, I loaded the new bootloader to my device without any issues, I came from 90.73, the phone since yesterday it´s working normally.
now that´s make me wonder if it´s possible modify the droid´s bootloader and try to port it to the Milestone, of course I don´t know which are the current methods used to try to hack the Milestone´s bootloader or even if someone tried that before, but thinking about the fact that both devices are very similars in hardware, I think it could be done!
if my last comment it´s outdated please forget it!
PS: sorry for my bad English!
So I suppose there is more chance the latest bootloader from motorola would be hacked then an older version ? takin into consideration its not possible to downgrade atm one could only think how great of an idea it would be to install this ,<insert sarcasm>
Coburn64 said:
That would mean if the bootloader on that device is hacked, the hack could be useful for us people with Bootloader 90.78ch installed.
Click to expand...
Click to collapse
long time that no talk about this project..
I have a question, this process only will work with the hack of liberation the Milestone XT702 or to with a bootloader of XT702 for install in Motola Milestone?
if exist a ROM of XT702 able make swape will serve for Milestone?
Hi all,
When my D2G have 4.5.629 (Settings - System - Update), I sbfing 4.5.608 sbf and my D2G shows this message:
Bootloader
D0.11
Err: A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to program
Connect USB
Data Cable
----
I tried this sbfs and no result:
VRZ_A955_2.3.20_1FF_01.sbf
HS_S_signed_BL_D11_cdma_droid2we_Consumer_replacer.sbf
Milestone 2 SBF 4.5.629
VRZ_A956_2.4.33_1FF_01.sbf
Is my only way wait 4.5.629? please help me, and sorry my bad english. all regards, greetings
sorry to tell u but uve probably soft bricked ur d2g. hopefully .629 sbf will b licked soon
the-light said:
sorry to tell u but uve probably soft bricked ur d2g. hopefully .629 sbf will b licked soon
Click to expand...
Click to collapse
Thanks, I'm waiting...
I hope founds another way...
thanks....
Kutukcu said:
Thanks, I'm waiting...
I hope founds another way...
thanks....
Click to expand...
Click to collapse
No idea if this works, or if it can help an already bricked version, but this was posted today:
http://rootzwiki.com/topic/23207-stuck-at-rootless-629check-this/
[/SIZE][/SIZE]Start Updated on 7-20-2012
****** Due to heavy download from wordwide users, Dropbox has temporay disabled my Public share because the traffic. ******
I had to created a new PRIVATE share to keep ALL files alive
In-order to download the files you need to have account with DropBox and click here to download
To help keep all links alive, please open new account with Dropbox by click here http://db.tt/AxpJcW9F , you will receive 2.5 GB of FREE cloud storage which can acces anywhere, anytime.
End Updated on 7-20-2012
After spend days reading hundred threads on multiple sites, I have come up with a quick instruction in 1 page on how to unbrick D2G and unlock the band to use on CDMA, GSM network such as Verizon, AT&T and T-Mobile. (Sim must be unlocked by calling Verizon or using third parties unlocked from internet search)
All credit will go to the original posters; I'm just combined all together to create an instruction easy for new users plus all the files download are in one place too.
Copy files from step 5, 6, 7, 9 and 18 to SD card before perform "How to" steps below:
How to un-bricked and band-unlock Droid 2 Global:
1. Flash 608 SBF using RSDLite (VRZ_A956_4.5.608_1FF_01.sbf) (press up arrow on keyboard while power up to enter flash mode)
2. Flash Repack_629 SBF using RSDLite (BL=2 BOOT REC CDTf__Repack_629.sbf)
3. Reboot, wipe data and cache (press x on keyboard while power up then press volume Up+Down at the same time )
4. Enable Unknown Source and Development features in Setting (To Bypass activation, press TopLeft, TopRight, BottomRight, BottomLeft (above Emergency))
5. Root D2G withSuperOneClick v2.3.3
6. InstallOtaRootKeeper, Run Protect-root then temp-unroot
7. Reboot to recovery then install 629 OTA update.zip then reboot(Blur_Version.4.5.608.A956.Verizon.en.US.zip)
8. Open OtaRootKeeper and restore Root
9. InstallDroid 2 Recovery Bootstap.apk then Reboot to Recovery
10. At Clockwork Recovery, run Backup the nan-droid
11. Flash 330 SBF suing RSDLite (VRZ_A956_2.4.33_1FF_01.sbf) --> After flash completed, phone will BRICKED, don’t worry
12. Flash 608 using EzSBF on USB stick (1KDStaz_D2G_4.5.608.iso) --> After flash completed, phone will BRICKED, don’t worry
13. Flash Repack_629 SBF using RSDLite (2_BL=2 BOOT REC CDTf__Repack_629.sbf)
14. Reboot, wipe data and cache
15. Enable Unknown source and Development features in Setting
16. Root D2G with SuperOneClick v2.3.3
17. Install Droid 2 Recovery Bootstap.apk then Reboot to Recovery
18. At Clockwork Recovery, Wipe Cache and install band unlock (TBH_Band_Unlock_v2.0.zip)
19. At Clockwork Recovery, run RESTORE the nan-droid (the one that backup on step 10)
20. Reboot phone then it should be able to us AT&T, T-Mobile and Verizon and enjoy
If you have any questions or problems, please post it here so we can help.
Please post your feedback here after your phone is unlocked.
Also, please select your RATING :good: at the Top Right of this post
Regard,
KEY
It worked!!
I am one of the (un)lucky owners of a non-unlockable D2G. I was able to use it to make calls with a SIM interposer (i-smartsim), but wasn't able to get data working on the 850Mhz band (900Mhz worked fine on EDGE, with another carrier). After following this how-to, now I get full speed 3G (H+) on my "locked" D2G using i-smartsim!
I know that I shouldn't use data with the interposer, that it will probably burn out, but I just feel better knowing that I can use data now if I need to
Hope this helps, and thank you for the post, key5000!
Key5000, thanks for posting this over here. BEH from rootzwiki here, and I was just looking here to see if this topic had been covered here yet.
I also wanted to add a little explanatory note explaining why the different flashing methods need to be used, for those who might wonder why use Rsdlite one time, and EzSbf another.
Rsdlite flashes the radio baseband, and sbf_flash (used by EzSbf) does not flash the radio. So, by flashing 330 with RsdLite, we flash the Froyo band unlock-able radio (actually the complete system, but all we are interested in is the radio). If you try flashing 330 with EzSbf, the radio will not be flashed, Rsdlite must be used.
Now that we have the radio we want, we need to get back to Gingerbread, but if we flash GB with Rsdlite, we will overwrite the radio we need be able to do the band unlock. Since sbf_flash flashes everything except the radio, we are able to use it to get back to a recoverable state (608+629-repack). the 629 repack contains no radio baseband, so it is able to be flashed from Rsdlite.
At this point, if we were to take the OTA update, we would overwrite the radio we are trying to preserve again, so we need to restore a nandroid backup to prevent doing that.
Incidentally, I have a clean nandroid backup of 629, if someone has somewhere to host it. This would effectively eliminate all of the initial rooting steps (1-10) other than the copying of files to the SD card. Let me know, and I can get the file to you.
Hope this is helpful or interesting to someone.
This trully works, I rooted My D2g on 2.3.4
Thank you Key 5000 for the final summary.
I just rooted, unbanded and now am on AT&T on my Droid 2 Global. and this is my very first attempt at the bootloader of android. Everything works now.
Thank s to everyone, starting from someone from china "my wife got milk", shadow, etc.
Let me contribute from my own experince working on my 2.3.4 version od D2g.
I had issues with:
Rooting with item #5, Superone click and the zip files on #10 and #12.
I had to download a program to run the superoneclick on my computer with the phone attached,
I also had to download clockworkmod from google play store, and finally,
for #12, using the usb method, you need to look up the instruction on booting your computer on USB.
Key5000, please double check the zip files, EZsbf and the band unlock. i had to get them elsewhere, they appear to be invalid. the same files though.
Also double check the item #11 zip file. I had to get it from Shadow's post.
Thanks again. You've made my day.
All files has been re-upload again.
Nice job! Convoluted but it has to be to accomplish the right sequence of flashes.
Very clever work.
Thanks for the How-To easy to follow and was able to unbrick one of my two phones.
The other phone already has the Band Unlock and is running on .608 I was wondering to upgrade to .629 do I just follow the same instructions but start at step 13, skip the Band Unlock, and use the nandroid from the recovered bricked phone?
By the way can't thank you enough for the unbrick solution.
Not sure if there is any benefit to updating to 629 if you don't have to, I don't know what the real differences between .608 and .629 really are (I got my phone with 629 already on it). One advantage to doing this that I can think of would be not accidentally taking the OTA update and getting the baseband overwritten at a later date. There are other ways to prevent the OTA update, such as renaming the updater file.
I am thinking, and someone else might be able to correct me if I am wrong, that in order to update from 608 to 629, without updating the baseband, the proper way would be to flash an updated kernel file, much as the method mentioned at
http://forum.xda-developers.com/showthread.php?t=1345071
and then flash the nandroid backup. I am not sure of the differences between the kernels of 608 and 629, but am thinking that they are different, and that it might cause issues to simply flash the Nandroid backup, without also updating the kernel. For some reason, I am thinking I read that one of the reasons that wifi etc don't work during the unbricking step of 629 is that 608 is running with the 629 kernel, and they aren't completely compatible. In your case, you would be running 629 with the 608 kernel, and you would probably be the first one to ever try that combination.
Someone else can likely fill more in, hope this helps.
Hello, thank u 4 the info, I don't even know how to sbf :s... I really want to unlock the bands but when you say it will brick. Don't worry, I actually worry lol, you mean that rsdlite will brick after flashing and rebooting? Then I have to enter in bootloader again? How it is? Am sorry for my ignorance
First off, if you are wanting to unlock the bands, is your phone sim-unlocked? If not, unlocking the bands will not sim-unlock the phone, it just allows an already unlocked phone to work on AT&T or T-Mobile.
Regarding to worry or not to worry, as with anything, there is a potential danger anytime the phone is flashed. The same is true when the phone receives an OTA update from Verizon, it is rare, but there is the potential for mishaps.
In this case, we are deliberately "bricking" the phone temporarily, as it is the only way to get the it rooted and band-unlocked.
After the latest ota update, the .629 update, any attempt to flash the phone to a previous version will "brick" the phone, but since there is a method to recover from the bricking, he says don't worry.
When we flash 330 to the phone, it flashes the software to the phone, but then the bootloader recognizes that it isn't the proper software, so it won't boot past the bootloader. It is necessary to flash 330, as that gives us the unlockable radio. Then, we have to flash .608 using ezsbf (or another method to flash without using rsdlite), to flash back to a recoverable state, without losing the radio. It is still bricked at this point and won't boot past the bootloader, but now recoverable with the repacked .629 sbf. We don't flash the whole 629 sbf, just enough parts of it to enable the phone to work.
After this, the phone is back to a partially usable state, where we can root it, and then restore the backup file, bringing it back to a fully usable state.
Hope this answers your questions.
dabigserver said:
Hello, thank u 4 the info, I don't even know how to sbf :s...
Click to expand...
Click to collapse
It is not difficult. Follow this how-to: http://droid.koumakan.jp/wiki/SBF
hi
I think i followed the instruction to do this. But my phone does not work for sim card and I need some help. My phone acts little weird. Can I start this steps all over from #1? Please help. Thanks
What do you mean by your phone doesn't work for SIM card?
Does your phone have a SIM card slot, and if so, is it SIM unlocked for global use?
If your phone doesn't have a SIM slot, then this isn't for you.
You can start the instructions over from the beginning, but in order for this to help your phone has to be SIM unlocked first. If you get an Enter Unlock Code message when you put a SIM in, then this won't really help you, other than for rooting your phone.
Thank you
I did every steps all over again and my phone works.
a question, these steps be discharged the phone to accept any telephone company?
These steps allow your phone to use AT&T or Tmobile, if your phone is already unlocked to use Foreign SIM cards. If your phone is still SIM locked, it won't unlock it for you.
By default Verizon blocks the use of the phone (even when unlocked) on AT&T and Tmobile, and this bypasses that block.
bhigham said:
These steps allow your phone to use AT&T or Tmobile, if your phone is already unlocked to use Foreign SIM cards. If your phone is still SIM locked, it won't unlock it for you.
By default Verizon blocks the use of the phone (even when unlocked) on AT&T and Tmobile, and this bypasses that block.
Click to expand...
Click to collapse
and is there anyway to unlock it to any company?
Yes, just get an unlock code from Verizon. Or, if you aren't on VZW and willing to bet/feeling adventurous, use those unlock services on the internets.
My D2G always goes into Bootloader whatever i do adn shows
"Bootloader
D0.11"
I flashed it with VRZ_A956_4.5.608_1FF_01.sbf then BL=2 BOOT REC CDT.sbf but again the same problem. Couple of times phone got started but for only some time, after some time when i reboot the phone it goes into bootloader. i need immediate help guys...
One thing more i have another D2G which got bricked after .629 but when unbrick method was discovered it got fixed with no issues. the reason i am sharing this is that it was going into bootloader straightaway when i press power button BUT this new one shows M logo for some time and then goes into bootloader...
plz help me out....
Gasai Yuno said:
Yes, just get an unlock code from Verizon. Or, if you aren't on VZW and willing to bet/feeling adventurous, use those unlock services on the internets.
Click to expand...
Click to collapse
I'm not really in the U.S. so that he could not apply the code, I know a website is legal and recommended that I can get the unlock code paying?
Hey guys,
Has anybody attempted to flash Fido/Rogers RAZR HD XT925 to Retail Brazil 4.0.4?
I get the error:
failed to hab check for devtree: 0x56
Using RSD 6.1.5. Bootloader is locked.
I had to reflash Rogers firmware (which flashed ok with minor xml modification).
Thank you.
zzzn00bzzz said:
Hey guys,
Has anybody attempted to flash Fido/Rogers RAZR HD XT925 to Retail Brazil 4.0.4?
I get the error:
failed to hab check for devtree: 0x56
Using RSD 6.1.5. Bootloader is locked.
I had to reflash Rogers firmware (which flashed ok with minor xml modification).
Thank you.
Click to expand...
Click to collapse
Bootloader is locked means bootloader is locked. Either stay on Rogers firmware, or go to motorola's website and request a bootloader unlock code. THIS WILL VOID YOUR WARRANTY. Just so you know.
Go here if you wish to proceed. https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
EdwardN said:
Bootloader is locked means bootloader is locked. Either stay on Rogers firmware, or go to motorola's website and request a bootloader unlock code. THIS WILL VOID YOUR WARRANTY. Just so you know.
Go here if you wish to proceed. https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
So let me get this straight, even with Motorola signed firmware I can't get away from Rogers firmware to stock LATAM Brazil Retail. IIRC that was not the case with XT910?
Please confirm,
Thank you.
zzzn00bzzz said:
So let me get this straight, even with Motorola signed firmware I can't get away from Rogers firmware to stock LATAM Brazil Retail. IIRC that was not the case with XT910?
Please confirm,
Thank you.
Click to expand...
Click to collapse
Hmm. You are right, that seems odd. Try re-downloading the Brazil rom, installing the latest moto drivers from https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481, and grab a copy of RSD_Lite 6.1.4
Try again, maybe one of those will fix it.
EdwardN said:
Hmm. You are right, that seems odd. Try re-downloading the Brazil rom, installing the latest moto drivers from https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481, and grab a copy of RSD_Lite 6.1.4
Try again, maybe one of those will fix it.
Click to expand...
Click to collapse
Thanks, will give it a shot. :good:
Hello, I'm kind of a noob on these things but here we go:
My Razr is stuck on the red Motorola logo (the boot animation when you turn on the phone) I believe this is what you call "bricked" (?).
I found out some methods here about downloading an XML file and replacing it but where can I find this file? And where do I need to replace it, it is on the firmware file, right? I wanted to get a USA firmware because in my country (Mexico) the KitKat update hasn't been liberated for us and I want to be able to update it.
A friend told me that if I put a firmware from USA it would ask me to update but to do this I need to unlock the bootloader.
I saw a tutorial on unlocking it with Motopocalypse but to do this I need to put the phone on Debugging Mode and I can't do that since my phone is bricked.
Is there a way to unbrick my phone and being able to install KitKat?
If not, of course my priority is to just unbrick it asap regardless if it is with KitKat or JB :/
Thank you so much in advance.
First, you need to tell us exactly what you did that "bricked" it. And I say "bricked" because if you can get to the Motorola logo, it probably isn't really bricked.
Either way, your friend's advice sounds like a bad idea to me. The US firmware is meant for the xt926, which uses Verizon's network. You should either wait for firmware to be released in your region or use a custom ROM (something you can do if you end up unlocking the bootloader).
Do the same: http://forum.xda-developers.com/showthread.php?p=57063750 doesn't care if your device is "bricked"
killrhythm09 said:
First, you need to tell us exactly what you did that "bricked" it. And I say "bricked" because if you can get to the Motorola logo, it probably isn't really bricked.
Either way, your friend's advice sounds like a bad idea to me. The US firmware is meant for the xt926, which uses Verizon's network. You should either wait for firmware to be released in your region or use a custom ROM (something you can do if you end up unlocking the bootloader).
Click to expand...
Click to collapse
When I turn it on it is stuck on the red Motorola logo, it goes like that for hours until battery is dead.
I can go into the bootloader options (when you press vol +/- and power) and I have tried wiping all the data to factory settings but the result is the same.
Sorry if I'm using the wrong terminology.
DorianX said:
Do the same: http://forum.xda-developers.com/showthread.php?p=57063750 doesn't care if your device is "bricked"
Click to expand...
Click to collapse
Can I do that even if I have never unlocked my bootloader?
Update:
I tried flashing with my carrier firmware and deleting the proper lines on the .xml file, then opened with RSD but it shows:
"Failed flashing process 14/21 flash boot "boot_signed" -> Phone returned FAIL"
And on the Fastboot manu on the phone it shows:
"Partition (boot) Security Version Downgraded"
"preflash validation failed for boot"
Please help me
mauber said:
Can I do that even if I have never unlocked my bootloader?
Click to expand...
Click to collapse
If you never upgraded to KK you don't need to have unlocked bootloader, but why don't you unlock your bootloader? I see only benefits with.
DorianX said:
If you never upgraded to KK you don't need to have unlocked bootloader, but why don't you unlock your bootloader? I see only benefits with.
Click to expand...
Click to collapse
Is not that I don't want to, it is that I can't. I'm having trouble flashing the firmware.
Just follow the tutorial http://www.grupoandroid.com/topic/71673-instalar-un-firmware-por-fastboot-en-imágenes/ and use Claro Puerto Rico firmware, then take the OTA
DorianX said:
Just follow the tutorial http://www.grupoandroid.com/topic/71673-instalar-un-firmware-por-fastboot-en-imágenes/ and use Claro Puerto Rico firmware, then take the OTA
Click to expand...
Click to collapse
I did but it got stuck on the "boot_signed" step (RSD lite), deleting that line on the XML file and then it showed the "system_signed" step error, deleted that line on the XML and it apparently flashed successfully but the phone is back to where it was before, stuck on the red Motorola logo boot animation.