So, as this is my first post on XDA I'd like to first state that I am somewhat new to the rooting scene. I used to have a DX and rooted it with no major problems. I know this is probably best suited to be posted in the Developement section, but I currently dont have premissions to do so. I would like to make sure I have everything I need and a clear understanding of the process before I attempt to root my D3.
As a precaution I would like to comfirm that their is a current .SBF file that can be used to return the phone to stock should I do something stupid during the root process? I have found the following link on this site with a .SBF file but from reading the threads I cant determine if this will return the D3 to stock:
[Recovery] RSD v5.5.0 and 5.5.184 (aka 5.6.890) fastboot partitions/flashable zip: http://forum.xda-developers.com/showthread.php?t=1255198
Can someone confirm/verify if this will return my D3 to stock should I need to?
Also within this thread their is mention of Moto-Fastboot and something abbreviated as abd (i think). I am not familiar with either of these. Could someone also provide a breif explanation of what these are and their importance to the .SBF process?
I am also planing on using the following otpion to root my D3:
[Guide] one-click root for Droid 3 (and others) [UPDATED 9/8/2011]: http://forum.xda-developers.com/showthread.php?t=1240130
I want to say that I read somewhere that I have to download the SU.apk from the market place? Is this correct or does this option one-click process display the SU icon in the app draw as the z4root one click option did on my DX?
Also I know that I need to purchase/download the D3 boot loader file from the market plac, I think? Is there anything else that you would recommend that I download/purchase to ensure I dont brick my phone in the process?
Sorry this is so long, but thank you in advance to those that provide responses/suggestions/comments to my questions.
Yes, there is a fully functioning sbf available for the D3
Yes, that is the sbf that is needed. To actually use the sbf you will need rsd lite, which i also believe to be in that post with the sbf.
This sbf will indeed return your phone to fully functioning stock in the case that it should be needed. (i've had to do it my fair share of times)
ADB is a command prompt interface that allows you to interact with the files on your phone without having to go into something like root explorer.
Fastboot (power + vol up + vol down) is a pre boot menu that allows you to boot into different things (like the AP fastboot mode needed to flash an SBF or to go into recovery). To flash an sbf you need to connect your D3 to the computer (in computer mode, i think), and choose the xml file that is in the SBF after you've extracted it.
The one-click root allows you to root your phone hassle free
When i say this, I mean that it installs the Superuser.apk and pushed the busybox and su to the system/xbin, which is needed for some different processes that require root.
here is the link to the most updated version of the bootstrapper, which allows recovery to be entered through the power-off (by using the bp tools option in fastboot)
http://forum.xda-developers.com/showthread.php?t=1289254
smoshim, thank you very much for your assistance and explanations. I already have RSD Lite on my computer and actually meant to include that in my original post. I had it on hand for when I rooted my DX just incase. I did need to use it once but it wouldnt recognize that my DX was connected for some reason. So I had to use a disck based linux program to SBF my DX when I sold it. Hopefully, RSD Lite doesnt give me any issues should I need it for my D3. Well, It's almost 2 am here in Omaha and I need to get my sorry tail to bed. Gotta be up in 5 and a half hours to get my 3 boys out the door for school. I have been patiently waiting to root my DS as I wanted to be sure that all of the "kinks" have been worked out and also wanted to try out some custom roms. I loved the darkslide rom for the DX. In your opinion do you think I should also go ahead and download/install rom manager?
honestly, rom manager doesn't have much available for the d3 yet. it'll be more productive right now to just manually drop the ROMs into your sd and boot into recovery.
And, in my opinion, the roms that we have out now are awesome. And as people get impatient they're making more and more themselves. So even though there may not be too many to choose from compared to some other devices there are more and more coming into the works all the time. But it sounds like you know what's going on, and the sbf process is pretty painless if you're already familiar with rsd on your DX
I have been all over this place with my bionic. I have tried 901 and went back to 893 using saver and other methods. The tools seem to do the job. My problem is trying to install an update from verizon. It will download and get to the end of the install, but then I get stuck in a failed fastboot with cdt errors. I am able to fix that using the Fixcdt, but every time my phone reboots I have to force it out of fastboot and into normal startup.. I have searched high and low and have found little bits of info out there, but nothing that has nailed it. Does anybody have the answer that I am looking for?
Thanks for they help!
You won't be able to install it. Since you have the .901 cdt.bin on your phone, you will need that file with anything you load until you have the "soon to be official" .902.
To install the official Big Red OS (which is no different than the ones floating on here) you will need to be on 5.5.886. You will need to download it to your phone, then move that to your PC, unzip, replace the cdt.bin file with the .901 file, then Fastboot it with RSD Lite it. Then you will have the .893.
Or you can download the .902 file and flash it in recovery OR you can wait a few days until it is OFFICIALLY pushed to your phone.
I believe this to be correct, but there are more knowledgeable people on the forum that may give you an answer you prefer.
I used to have an Atrix and any time something went wrong, I knew I could flash a Stock image using RSD Lite.
I have not seen this for the Droid 4 yet and was wondering if anyone expects us to be able to use this program on our devices.
I know there's a lot of talk about safestrap with this phone, but not sure if that has anything to do with RSD Lite (sorry kind of a noob with safestrap).
Thanks!
The newer OMAp dual core devices no longer use SBF mode for flashing because they have fastboot support now, so RSD Lite was adapted to use XML.zip files that are an archive of signed fastboot images rather than an SBF, which is a Single Binary File consisting of CG images. The legacy bootloader is still available in the boot menu but you won't find the firmware files in SBF format for these devices.
That said, we are waiting for the full XML.zip for the D4 to be leaked and currently have no way to restore the stock factory signed images for this device.
This means it is very dangerous to do any significant mods on this phone at this stage.
Hashcode and others have done great work to make it as safe as possible, but the risk cannot be overstated.
If you render the device unbootable for any reason, your options are very limited.
That was a really solid explanation and its greatly appreciated.
Although I'm not usually too timid with modding my phone, I think I'll wait a few weeks to see what happens.
Thanks!
i'm currently running the 6.16.217 ics leak on my droid 4 and was wondering if there was any way i could install the lte radio from the 6.16.215 leak over the .217's. i would just install the .215 leak, but i find that everything, but signal/data works better for me on the .217.
oh and is anyone else having problems with playing videos from veoh(.)com on the .215 or .217 leaks?
thank you in advance
englishund the answer to my question.
I'm sure there's a simpler way, but this is how i did it. I used the droid4 utility to go from .217 to .215, then i unziped the .217 fastboot file and removed the line in the .xml file that flashed the radio software and used rsd lite to flash the fastboot files over .215. Once that was done i wiped(just to be safe) and rebooted. Everything, with the exception of some websites(veoh.com), has been running well and i haven't lost signal once since then
maddeath said:
englishund the answer to my question.
I'm sure there's a simpler way, but this is how i did it. I used the droid4 utility to go from .217 to .215, then i unziped the .217 fastboot file and removed the line in the .xml file that flashed the radio software and used rsd lite to flash the fastboot files over .215. Once that was done i wiped(just to be safe) and rebooted. Everything, with the exception of some websites(veoh.com), has been running well and i haven't lost signal once since then
Click to expand...
Click to collapse
Are you certain that there is not anther cause for this issue? If you are certain, I'd be very interested as to why this is... and whether the rest of us could benefit.
Well from what i've seen with my droid 4 and droid razr. This version of motoblur ics doesn't really play well with flash. Someone else has started a thread about this http://forum.xda-developers.com/showthread.php?p=30635637#post30635637 hope it helps? Lol
I have a bionic on stock JB. I have FXZ many times and do not get any errors with FXZ, but it seems that the radio never gets written.
I belive the radio files only get written after the 1st reboot after FXZ process. During that time, I see the robot with the chest open. It appears to be doing some file updates, and I don't get any errors. However, after flashing, I always get "baseband version: unknown" when I check the phone info.
I have attempted to do stock recovery using update_zip. The update zip contains bp.img and lte.imp. When I tried to flashe those file in recovery mode, I see that it goes though some package verification process, then it aborts. So the files never get flashed.
Is there some other way I can flash these radio files? I tried some custom roms like blurry, carbon. None of them include radio files, so the custom roms still run off the corrupt radio files that I have.
Since fxz and stock recovery doesn't flash the radio files, is there any other way to update these file? My phone is rooted, so can safestrap update do it? Or can I do it through adb? Or copy the files in through root explorer?
I heard that the radio files reside on the /radio partition, but I have not seen that directory when I use root explorer. Many it's not normally mounted. Does any know how mount that partition for edit?
The FXZ file has radio.img, but the stock recovery has bp.img/lte.img does anyone know what's the difference?
bobdole said:
I have a bionic on stock JB. I have FXZ many times and do not get any errors with FXZ, but it seems that the radio never gets written.
I belive the radio files only get written after the 1st reboot after FXZ process. During that time, I see the robot with the chest open. It appears to be doing some file updates, and I don't get any errors. However, after flashing, I always get "baseband version: unknown" when I check the phone info.
I have attempted to do stock recovery using update_zip. The update zip contains bp.img and lte.imp. When I tried to flashe those file in recovery mode, I see that it goes though some package verification process, then it aborts. So the files never get flashed.
Is there some other way I can flash these radio files? I tried some custom roms like blurry, carbon. None of them include radio files, so the custom roms still run off the corrupt radio files that I have.
Since fxz and stock recovery doesn't flash the radio files, is there any other way to update these file? My phone is rooted, so can safestrap update do it? Or can I do it through adb? Or copy the files in through root explorer?
I heard that the radio files reside on the /radio partition, but I have not seen that directory when I use root explorer. Many it's not normally mounted. Does any know how mount that partition for edit?
The FXZ file has radio.img, but the stock recovery has bp.img/lte.img does anyone know what's the difference?
Click to expand...
Click to collapse
Dumb question, but have you verfied MD5 on your fxz to make sure your download wasn't corrupt?
useltonm said:
Dumb question, but have you verfied MD5 on your fxz to make sure your download wasn't corrupt?
Click to expand...
Click to collapse
Yes, the MD5 does match up. This brings up the question if I got the file from the right place.
I have not being able to find any other place to down load the JB stock rom other than this place:
http://sbf.droid-developers.org/cdma_targa/list.php
Did I get it from the right place?
bobdole said:
Yes, the MD5 does match up. This brings up the question if I got the file from the right place.
I have not being able to find any other place to down load the JB stock rom other than this place:
http://sbf.droid-developers.org/cdma_targa/list.php
Did I get it from the right place?
Click to expand...
Click to collapse
The bottom one is definitely the correct one for jb on the bionic.
Let me check something and I'll get back to you.
Sent from my XT875 using Tapatalk 4
---------- Post added at 01:32 AM ---------- Previous post was at 01:26 AM ----------
I was going to suggest trying the house of bionic, but it looks like you already went there.
Sent from my XT875 using Tapatalk 4
Can anyone help?
I'm trying to do an experiment to flash just the latest JB bp.img and lte.img (radio files) in stock recovery.
When I do it it fails on package validation.
I found some older 902 and older radio files, those do not fail package validation, but fail to flash.
I assume they fail because of security(no going back to older version).
I need some to help package the bp, lte.img files into a zip. I tried the signapk tool. It seems to generate all the manifest files, but somehow the files do not pass package validation.
I tried taking the 902 radio files that pass package validation and run them through signapk, and sure enough they would fail package validation after signapk.
Can anyone help, please!
https://dl.dropboxusercontent.com/u/7632904/targa_jb_update_radio.zip
This is the radio only update.zip that contains the bp.img and lte.img that are digitally signed by Motorola and is pulled from the radio.img of the Bionic JB release from the XML.zip.
System Version
98.72.22.XT875.Verizon.en.US
Baseband Version
CDMA_N_05.22.00 LTEDC_U_09.1D.00
These are the only files you can flash the radio with on any MDM6600 Motorola device. They must be the signed images in the original file flashed in stock recovery.
If you flash these and still have Baseband Unknown errors then you may have a corrupt amss.mbn and we don't have files to fix that for any recent releases.
That is extremely rare and if you flash the properly signed baseband images it should restore normal function in almost all cases.
cellzealot said:
https://dl.dropboxusercontent.com/u/7632904/targa_jb_update_radio.zip
This is the radio only update.zip that contains the bp.img and lte.img that are digitally signed by Motorola and is pulled from the radio.img of the Bionic JB release from the XML.zip.
System Version
98.72.22.XT875.Verizon.en.US
Baseband Version
CDMA_N_05.22.00 LTEDC_U_09.1D.00
These are the only files you can flash the radio with on any MDM6600 Motorola device. They must be the signed images in the original file flashed in stock recovery.
If you flash these and still have Baseband Unknown errors then you may have a corrupt amss.mbn and we don't have files to fix that for any recent releases.
That is extremely rare and if you flash the properly signed baseband images it should restore normal function in almost all cases.
Click to expand...
Click to collapse
Hi cellzealot,
I really appreciate your help. I tried flashing your file, but I get the same error as when I flash for full JB update file, which is:
assert failed: motorola.motoflash("/tmp/bp.img")
I was wondering if you could do one more thing to help..
Since it's failing assert, what if we modify the script to no do a assert check, but just run the command?
This is the update-script:
assert(show_progress(0.2, 2),
do_format_cache(true);
package_extract_file("bp.img", "/tmp/bp.img"),
package_extract_file("lte.img", "/tmp/lte.img"),
show_progress(0.8, 35),
motorola.motoflash("/tmp/bp.img"),
motorola.motoflash("/tmp/lte.img"),
delete("/tmp/bp.img", "/tmp/lte.img"));
What if we make it like this:
show_progress(0.2, 2),
do_format_cache(true);
package_extract_file("bp.img", "/tmp/bp.img"),
package_extract_file("lte.img", "/tmp/lte.img"),
show_progress(0.8, 35),
motorola.motoflash("/tmp/bp.img"),
motorola.motoflash("/tmp/lte.img"),
delete("/tmp/bp.img", "/tmp/lte.img");
I'm hoping that this might work.
BTW, how did you package the zip file and sign the files?
The original zip file had lots other system/boot files.
Thanks!
I didn't sign or edit the files at all. The update.zip is pulled from the radio.img using a hex editor.
Te radio image is an ext3 partition that just contains the update.zip which itself contains the signed bp.img and lte.img that are flashed in recovery after the device reboots from AP fastboot bootloader.
This is because the MDM6600 Motorola devices are all hybrid chipset boards and the OMAP AP chipset is separate from the Qualcomm MDM6600 CDMA/EVDO/GSM/WCDMA radio and the Motorola TI Wrigley LTE radio.
The radio chips are setup on a BP passthrough only device interface that cannot be flashed in AP Fastboot mode.
This is why you can't see the radio partitions in the file system of the device and the kernel layer only has access to the radio via the RIL.
Regarding the persistent errors, it sounds like it is failing due to the recovery because there is no reason it would fail asserts with the signed files in stock recovery.
cellzealot said:
I didn't sign or edit the files at all. The update.zip is pulled from the radio.img using a hex editor.
Te radio image is an ext3 partition that just contains the update.zip which itself contains the signed bp.img and lte.img that are flashed in recovery after the device reboots from AP fastboot bootloader.
This is because the MDM6600 Motorola devices are all hybrid chipset boards and the OMAP AP chipset is separate from the Qualcomm MDM6600 CDMA/EVDO/GSM/WCDMA radio and the Motorola TI Wrigley LTE radio.
The radio chips are setup on a BP passthrough only device interface that cannot be flashed in AP Fastboot mode.
This is why you can't see the radio partitions in the file system of the device and the kernel layer only has access to the radio via the RIL.
Regarding the persistent errors, it sounds like it is failing due to the recovery because there is no reason it would fail asserts with the signed files in stock recovery.
Click to expand...
Click to collapse
Thank you for your explanation.
I was able to find the radio.img file from the OTA xml.zip for fxz.
Indeed, if I open the radio.img I find the update_radio.zip that you have provided.
What I don't quite understand is why we are able to flash various custom roms that are not signed by motorola through CWM, TWRP.
Would there be a way to run a modified update_radio.zip through CWM, TWRP?
"Now to" needed
cellzealot said:
....... link removed because it won't let me post with it in here.......
This is the radio only update.zip that contains the bp.img and lte.img that are digitally signed by Motorola and is pulled from the radio.img of the Bionic JB release from the XML.zip.
System Version
98.72.22.XT875.Verizon.en.US
Baseband Version
CDMA_N_05.22.00 LTEDC_U_09.1D.00
Click to expand...
Click to collapse
I have found a lot of information about needing to flash the Bionic radios, and that its not included in the custom ROM (I have a current Cyanogen nightly & baseband CDMA_n_05.13.01R LTEDC_U_09.14.00). I downloaded the file you listed above, but now the question that I can't seem to find the answer to.... "Now What"... when I installed safestrap and the custom rom i found some very helpful step by step instructions... I can't not seem to locate the same for flashing in new radio files.... so if someone could point me in the direction of some that would be most helpful...
BTW.... Typing "upgrade bionic radio files" into forums and Google returns everything BUT what I am looking for
RichT1 said:
I have found a lot of information about needing to flash the Bionic radios, and that its not included in the custom ROM (I have a current Cyanogen nightly & baseband CDMA_n_05.13.01R LTEDC_U_09.14.00). I downloaded the file you listed above, but now the question that I can't seem to find the answer to.... "Now What"... when I installed safestrap and the custom rom i found some very helpful step by step instructions... I can't not seem to locate the same for flashing in new radio files.... so if someone could point me in the direction of some that would be most helpful...
BTW.... Typing "upgrade bionic radio files" into forums and Google returns everything BUT what I am looking for
Click to expand...
Click to collapse
Put the radio file on a SD card(leave it as .zip, don't unzip it) put the sd card in in your phone.
The follow these instructions to flash in recovery mode:
http://www.droid-life.com/2011/09/2...boot-menu-for-recovery-sbf-flashing-and-more/
In recovery mood, select update zip from ext-sdcard
Then pick the radio file..
That's it.
bobdole said:
Put the radio file on a SD card(leave it as .zip, don't unzip it) put the sd card in in your phone.
The follow these instructions to flash in recovery mode:
.... link removed .....
In recovery mood, select update zip from ext-sdcard
Then pick the radio file..
That's it.
Click to expand...
Click to collapse
Thank you.... worked like a charm....:victory:
I'm literally a real noob when it comes to this stuff.. But when I tried to flash the radio files from above via recovery, I got this error.
assert failed: motorola.motoflash("/tmp/lte.img")
I've lost my lte baseband way before trying this, I've actually lost it, running a Carbon nightly rom.
EDIT
I've changed the updater script and now I'm having a problem with it aborting the installation alltogether. Any help would be greatly appreciated. I just want to get my LTE radio working :|
cellzealot said:
https://dl.dropboxusercontent.com/u/7632904/targa_jb_update_radio.zip
This is the radio only update.zip that contains the bp.img and lte.img that are digitally signed by Motorola and is pulled from the radio.img of the Bionic JB release from the XML.zip.
System Version
98.72.22.XT875.Verizon.en.US
Baseband Version
CDMA_N_05.22.00 LTEDC_U_09.1D.00
These are the only files you can flash the radio with on any MDM6600 Motorola device. They must be the signed images in the original file flashed in stock recovery.
If you flash these and still have Baseband Unknown errors then you may have a corrupt amss.mbn and we don't have files to fix that for any recent releases.
That is extremely rare and if you flash the properly signed baseband images it should restore normal function in almost all cases.
Click to expand...
Click to collapse
Hi CellZealot,
Do you have radio.zip file(s) from GB versions by any chance? I'm on ICS and want to try GB radio(s) hoping to get better signal strength and possibly enable 900/1800mhz band if it's disabled in ICS radio. I'm still experimenting to get my Bionic (Hw A, 08/12) to work on 900/1800mhz.
Is Droid Razr also MDM6600 Motorola device? If yes, can I try and get its radio and flash on Bionic? Please advise.
Thanks.
https://www.dropbox.com/s/vnob615mwf17xxk/Bionic_Radio.zip
I believe that zip has most or all of the older radios. Posting from phone at work.
cellzealot said:
https://www.dropbox.com/s/vnob615mwf17xxk/Bionic_Radio.zip
I believe that zip has most or all of the older radios. Posting from phone at work.
Click to expand...
Click to collapse
Thanks a lot CellZealot. You're a gem!!
cellzealot said:
https://www.dropbox.com/s/vnob615mwf17xxk/Bionic_Radio.zip
I believe that zip has most or all of the older radios. Posting from phone at work.
Click to expand...
Click to collapse
I tried flashing a couple of radios from that zip file via recovery and the update was successful each time. I did NV edits, buildprop changes and the factory data reset each time. But when I checked the Baseband version info, the LTE component was missing e.g..it only shows CDMA_N_04.07.02R. I suspect somehow LTE part was not flashed via recovery even though no error was shown. Also IMEI and SV show up unknown as well. Did I miss some step or did I do something incorrectly? Please advise.
Thanks in advance.
P.S. I didn't rename the radio zip file to update.zip. Just used the files as is from the above zip. I'm trying to use them on ICS, These GB radios aren't fully compatible with the ICS version kernel or something?
This post helped me fix my bionic... the same process applies to the baseband unknown issue that i had and i found a lot of bionic owners have the issue also. the simplest fix is actually not to put the radios on the sd card but instead to make a copy of the xml doc that is in the fastboot files and delete every step but the radio install (the last step) then use rsd lite and change the xml file to the one with the radio
I have been working on my bionic for months.
Casey Walt said:
This post helped me fix my bionic... the same process applies to the baseband unknown issue that i had and i found a lot of bionic owners have the issue also. the simplest fix is actually not to put the radios on the sd card but instead to make a copy of the xml doc that is in the fastboot files and delete every step but the radio install (the last step) then use rsd lite and change the xml file to the one with the radio
Click to expand...
Click to collapse
This all started back in december 2013. a buddy gave me a bricked bionic.. i was able to "unbrick". and install the 98.72.22 fxz. i only get service half of the day and 3g like maybe 30min...i also have the error where the lte.img will not install. Thus please explain more as to how you were able to fix it. Do you have 4g? i haven't been able to restore it. i had to splice a usb cord and attach the pos and neg to the battery and connect a charging cord from the phone to my desktop to get a led response from the phone during the unbricking process. basically if i install a new rom daily i have steady service all day.. 3g even. but then it just craps out on me. believe me, im not giving up on this phone until i see a 4g icon on my status bar.
I have an S3 now but i can still glady help you.... what i did was put a shim in my sim card holster. then put the .905 radio in the fxz folder and flash it again... you wait like 5-10 min till you have service ( if you did it right there should be no lte in the baseband yet) then put the zip file for the 4.1.2 radio on your sd card and flash it through stock recovery. when you boot your phone up you wait 5-10 min again and you should have both 3g and lte in your baseband
Sent from my SCH-I535 using xda app-developers app