Related
I purchased a phone that was suppose to be setup for verizon, i got it home and found out it had been rooted and set up for criket.
after many hours of reading and searching i have the phone flashed back to factory settings, but, when i dial *228 to program for verizon it still calls criket.
I was told i need to flash the antenna ?? or something like that...
can someone help me with this.. thanks
have you flashed the stock sbf?
follow these instructions
i cant post links, wtf
instead of flashing the 2.1sbf file listed there you can use the 2.2 file from this site
i cant post links, wtf
the radios are also listed there, i've been told you need to flash the radios in order, meaning you can't just start at the last one, you need to flash each one seperately. BUT i have no idea how to flash a radio on a stock phone, so if i were you i'd attempt the spf flash with rsd lite, then root the phone and install sprecovery, then install the radios one at a time.
I had the same issue and went to Verizon today and had them flash the stock Froyo using RSD Verizon software. Make sure you enable USB debugging first.
Sent from my Droid using XDA App
OMG... i was told i had to have the phone rooted.. i just got done rooting it again
so... it needs to be un-rooted for me to take it to verizon to get it working on there network ?
No need to unroot; just bring the phone to Verizon and they can restore it back to the original 2.2.
Update:
I was able to flash the XT860 into my ME863, works now, just need to get the bootstrap running so i can upgrade to CM7 or CM 9
and needed a fix for the data problem
please help, any more sbfs, or why i am getting errors,
been messing with it too much, should not had tried the XT roms, cuz my device is the ME863
now my phone is at the flash Failure screen
how do i fix this please help
I'm pretty sure there's a 60.1.101 ME863 SBF floating around the forums...
I _thought_ the problem was people were unable to move _to_ the XT860 once they'd flashed the ME863 SBF.
You're having problems going the other way?
I'd think you'd be best off running the stock rom that either came with your phone, or one that's appropriate for your location, if that turns out to be possible.
well i am runnin XT 860 brazil retail rom , everything works, just i need to set up the mobile set points
evooo said:
well i am runnin XT 860 brazil retail rom , everything works, just i need to set up the mobile set points
Click to expand...
Click to collapse
try restoring your original me863 apns-conf.xml. It's in /system/etc/
Bump.
I and I'm sure many other users are curious as to if/how you fixed this issue and if you're running custom firmware on your me863 yet. Also, I've made a new patch and I'm curious if it works on the me863 (you guys have safestrap on that rom?)
Hiii
I have XT862 flashed with XT883 (purchased from e bay). It has around 3 GB app partition.
Safe strap doesn't work (Back Option) on this phone due to some partition mapping issue. (Known issue for XT 883, ME863)
Sr. member TBBle suggested a tweak with safestrap & with that I am able to Backup my phone, do disaster recovery etc.
"http://forum.xda-developers.com/showthread.php?t=1625877"
But whenever I install a ROM in safe system it boots to black screen. I tried with Maverick 4.5 & CM7.2 both same result.
I am not able to decide if it's safe strap problem or ROM compatibility with XT883.
So please suggest me what shall I do?
singh.r said:
Hiii
I have XT862 flashed with XT883 (purchased from e bay). It has around 3 GB app partition.
Safe strap doesn't work (Back Option) on this phone due to some partition mapping issue. (Known issue for XT 883, ME863)
Sr. member TBBle suggested a tweak with safestrap & with that I am able to Backup my phone, do disaster recovery etc.
"http://forum.xda-developers.com/showthread.php?t=1625877"
But whenever I install a ROM in safe system it boots to black screen. I tried with Maverick 4.5 & CM7.2 both same result.
I am not able to decide if it's safe strap problem or ROM compatibility with XT883.
So please suggest me what shall I do?
Click to expand...
Click to collapse
I have a xt860 and sometimes when I flash something in safestrap and reboot I get a blank screen as well (it almost looks like the screen is off). I just pull the battery and then it boots fine. Maybe that will help if you haven't tried doing it yet, otherwise I'm not sure how to help sorry.
Well I have same issue. I already saw you post in other forum in 4.5 Mav ROM thread.
What are you looking for ? Use TATA CDMA OMH on Droid 3 ??
If Yes, message me, I shall give you a way out. Using mvp's method, you can use any Verzion ROM or custom ROM with Droid 3.
The issue is we can't use Maverick ROM with XT883, do you know any ROM compatible with XT883 ?
may be need Verizon 890 stock rom and XT883 rom mixed together.
flash the mixed rom,which should use safestrap.
Verizon 890 files:
1.boot.img 2.cdrom 3.cdt.bin 4.device_tree.bin 5.lbl 6.logo.bin mbm.bin
7.allow-mbmloader-flashing-mbm-.bin 8.ebr 9.mbmloader.bin 10.mbr
11.preinstall.img
xt883 rom files:
others files except above.
recovery.img file I am not sure whether xt883 or verizon,need test.
modify xml according to md5 of these files.
I'm pretty lazy, if someone successful please tell me,hahahaha!!!!!
kapilthio said:
What are you looking for ? Use TATA CDMA OMH on Droid 3 ??
If Yes, message me, I shall give you a way out. Using mvp's method, you can use any Verzion ROM or custom ROM with Droid 3.
Click to expand...
Click to collapse
Thanks, please guide. I want my phone to work with both GSM/CDMA sim cards, as it's working now. Have not dared to remove stock ROM just cause I am not sure if I will get the same functionality after changing the ROM or not. Due to that reason only I was trying to taste it with safestrap, but of no use.
Thanx for your help, & sorry for late reply, seems I forgot to subscribe the the thread.
NIGHTMARE- said:
The issue is we can't use Maverick ROM with XT883, do you know any ROM compatible with XT883 ?
Click to expand...
Click to collapse
No luck till now. I have tried (in safe mode) CM7.2, AOKP 40, Milestone 6, XT862 .906 ROMs. All installs fine but won't boot at all.
Will update you as soon as I get any thing to work. Or may be we have to SBF with some verizon ROM & then only it will work.
adamskub said:
I have a xt860 and sometimes when I flash something in safestrap and reboot I get a blank screen as well (it almost looks like the screen is off). I just pull the battery and then it boots fine. Maybe that will help if you haven't tried doing it yet, otherwise I'm not sure how to help sorry.
Click to expand...
Click to collapse
Thanx already tried that few times, each time left phone for more than 30 mins, but it stays black with back lights on.
Actually till now I am not even sure if it's ROM compatiblity issue or safe strap version or my Phone current ROM.
Hopefully I will figure it out soon.
mvp3 said:
may be need Verizon 890 stock rom and XT883 rom mixed together.
flash the mixed rom,which should use safestrap.
Verizon 890 files:
1.boot.img 2.cdrom 3.cdt.bin 4.device_tree.bin 5.lbl 6.logo.bin mbm.bin
7.allow-mbmloader-flashing-mbm-.bin 8.ebr 9.mbmloader.bin 10.mbr
11.preinstall.img
xt883 rom files:
others files except above.
recovery.img file I am not sure whether xt883 or verizon,need test.
modify xml according to md5 of these files.
I'm pretty lazy, if someone successful please tell me,hahahaha!!!!!
Click to expand...
Click to collapse
Thanx, but it will take me some time to reach that level. I am just a beginner who is doing things with helpful posts of experts like you.
Meanwhile I will try to figure out some thing easier or learn to do what you are saying.
# Sorry for late respone, I forgot to subscribe the thread. (Changed to automatic for all future posts)
For now I'm only using Xt883 ROM.
I have tried out.
flash Verizon 890 stock rom
then use moto-fastboot flash 4 files of xt883 rom,boot.img system.img recovery.img radio.img
moto-fastboot.exe flash boot boot.img
moto-fastboot.exe flash system system.img
moto-fastboot.exe flash recovery recovery.img
moto-fastboot.exe flash radio radio.img
then use recovery to update ota 60.3.250 and GMS package.
root.
Droid3Safestrap 2.00 works normally.
mvp3 said:
I have tried out.
flash Verizon 890 stock rom
then use moto-fastboot flash 3 files of xt883 rom,boot.img system.img recovery.img
This should let you can use safestrap normally.
Click to expand...
Click to collapse
Thanx
I need it to work with GSM/CDMA OMH, do I need to flash radio as well?
singh.r said:
Thanx
I need it to work with GSM/CDMA OMH, do I need to flash radio as well?
Click to expand...
Click to collapse
yes ,I forgot,sorry
singh.r said:
...
I have XT862 flashed with XT883 (purchased from e bay). It has around 3 GB app partition.
...
Click to expand...
Click to collapse
I've bought 3 of these phones from ebay (XT862 on the label, flashed wit XT883).
Simply SBF them with .890 or .906 and you should be good to go
srtzlyn said:
I've bought 3 of these phones from ebay (XT862 on the label, flashed wit XT883).
Simply SBF them with .890 or .906 and you should be good to go
Click to expand...
Click to collapse
Thanx.
Did you get them to work with GSM/CDMA both after flashing verizon.
Does the verizon dialler has recording button while in call.
Does FM works on verizon ROM.
I know how to SBF, do you know any link for .906 ROM which can be SBFd, or I have to flash .890 & then apply update for .906.
Thanx again
singh.r said:
Thanx.
Did you get them to work with GSM/CDMA both after flashing verizon.
Does the verizon dialler has recording button while in call.
Does FM works on verizon ROM.
I know how to SBF, do you know any link for .906 ROM which can be SBFd, or I have to flash .890 & then apply update for .906.
Thanx again
Click to expand...
Click to collapse
I'm not sure about CDMA because we don't have that here in europe.
Also I haven't really used the stock rom, directly flashed MavROM 4.5 with safestrap, so I don't know about the verizon features in stock...
The .890 (title says it's the .906) SBF can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=1686911
there's a better way.
http://forum.xda-developers.com/showthread.php?t=1519844
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
dinosaur swagg said:
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
Click to expand...
Click to collapse
It may have been flashed to the 883 radio. I would do a complete SBF.
dinosaur swagg said:
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
Click to expand...
Click to collapse
Your build.prop has to match the radio. If you've flashed the XT883 radio, you must use a modified build.prop.
Here is a post I made for someone with a similar issue. It has necessary files and instructions on flashing the stock and XT883 radio. Flash the stock XT862 radio and see if that helps.
I have sbf'ed the phone, but it hasn't fixed the problem. I have installed the 833 radio previously and made sure I have pushed the build.prop into the system folder still without luck of fixing the problem. After a little more research, could the EFS folder be corrupt/deleted causing the problem?
Skreelink said:
Your build.prop has to match the radio. If you've flashed the XT883 radio, you must use a modified build.prop.
Here is a post I made for someone with a similar issue. It has necessary files and instructions on flashing the stock and XT883 radio. Flash the stock XT862 radio and see if that helps.
Click to expand...
Click to collapse
I do remember using your method although I didn't transfer the build.prop in that case. Does the build.prop in the flash kit match the XT862-890.img radio?
dinosaur swagg said:
I do remember using your method although I didn't transfer the build.prop in that case. Does the build.prop in the flash kit match the XT862-890.img radio?
Click to expand...
Click to collapse
Just use the stock build.prop with the xt862 890 radio. It is the stock radio, works on systems 890 and 906, tested personally. It will work with verizon and non-us gsm. If you require us-gsm such as att, lemme know and I can upload my current build.prop for gb roms.
htsebar meafure
Skreelink said:
Just use the stock build.prop with the xt862 890 radio. It is the stock radio, works on systems 890 and 906, tested personally. It will work with verizon and non-us gsm. If you require us-gsm such as att, lemme know and I can upload my current build.prop for gb roms.
Click to expand...
Click to collapse
I am currently outside of the US and would require a GSM radio. Does this mean that I would flash the XT862-890.img radio in your flash tools? Along with that I would need the stock build.prop I take? Yet I believe I overwrite this when I flashed the 886 radio and pushed the modified build.prop into the system folder. Where can I get the stock build.prop? Thanks very much for the help too
dinosaur swagg said:
I am currently outside of the US and would require a GSM radio. Does this mean that I would flash the XT862-890.img radio in your flash tools? Along with that I would need the stock build.prop I take? Yet I believe I overwrite this when I flashed the 886 radio and pushed the modified build.prop into the system folder. Where can I get the stock build.prop? Thanks very much for the help too
Click to expand...
Click to collapse
Both radios support gsm. The ONLY reason users flash the xt883 radio is because of the mnc block on 310 built into the xt862 radio. This does not affect foreign non-us gsm networks. If you flash any roms, do not modify the build.prop and it should work with the xt862-890 radio. It seems users always rush into either suggesting flash the xt883 radio or lib files, which either one just confuses more than helps an average user... it is better to troubleshoot first..
Anyway, my suggestion (since you seem to have a grasp on flashing radios) is use the kit I gave you, flash the xt862-890.img radio, then flash any rom, such as maverick (I use version 4.0 of this), minimoto, etc. Gb roms will be your most stable and have everything working, such as camera. Do not modify the build.prop, check under wireless settings to change network type to gsm/umts and apns.
The ONLY modification to the build.prop will be after you get it working, changing one line to fix the signal bars display. (Verizon has these nerfed to make gsm look bad) although not a true indication of signal, always check status.
Skreelink said:
Both radios support gsm. The ONLY reason users flash the xt883 radio is because of the mnc block on 310 built into the xt862 radio. This does not affect foreign non-us gsm networks. If you flash any roms, do not modify the build.prop and it should work with the xt862-890 radio. It seems users always rush into either suggesting flash the xt883 radio or lib files, which either one just confuses more than helps an average user... it is better to troubleshoot first..
Anyway, my suggestion (since you seem to have a grasp on flashing radios) is use the kit I gave you, flash the xt862-890.img radio, then flash any rom, such as maverick (I use version 4.0 of this), minimoto, etc. Gb roms will be your most stable and have everything working, such as camera. Do not modify the build.prop, check under wireless settings to change network type to gsm/umts and apns.
The ONLY modification to the build.prop will be after you get it working, changing one line to fix the signal bars display. (Verizon has these nerfed to make gsm look bad) although not a true indication of signal, always check status.
Click to expand...
Click to collapse
Okay so I have just re-flashed the XT862-890 radio then flashed CM10 (a ROM I had sitting on my SD) but I did so without rebooting after the radio flash as I wasn't sure if it were necessary. This still hasn't solved the problem. You did mention not to edit the build.prop wich I wish I had known earlier. I'm not sure whether the build.prop I had in the system file was modified or not so I did a quick google search and found what seemed to be the stock build.prop text (http://www.droidforums.net/forum/droid-3-hacks/159002-build-prop-those-wanting-look.html). I then copied the text to notepad and saved as build.prop prior to pushing to the system folder. Could this have been a bad mistake?
dinosaur swagg said:
Okay so I have just re-flashed the XT862-890 radio then flashed CM10 (a ROM I had sitting on my SD) but I did so without rebooting after the radio flash as I wasn't sure if it were necessary. This still hasn't solved the problem. You did mention not to edit the build.prop wich I wish I had known earlier. I'm not sure whether the build.prop I had in the system file was modified or not so I did a quick google search and found what seemed to be the stock build.prop text (http://www.droidforums.net/forum/droid-3-hacks/159002-build-prop-those-wanting-look.html). I then copied the text to notepad and saved as build.prop prior to pushing to the system folder. Could this have been a bad mistake?
Click to expand...
Click to collapse
Uh, yeah... that build.prop will not work on cm10, also all kexec roms (cm10/aokp/cm10.1) have issues with gsm anyway. Just try to sbf back to stock. If you still get unknown for baseband, etc. Then you may have a hardware problem. After flashing the radio and rebooting, it should show an android with an open box with a meter, then reboot itself. If your build.prop is correct for the radio, your baseband, prl, etc will show. You *may* have to toggle global/gsm/cdma a few times to get signal. Flash a stock based rom (maverick or minimoto) and see if that shows baseband.
Skreelink said:
Uh, yeah... that build.prop will not work on cm10, also all kexec roms (cm10/aokp/cm10.1) have issues with gsm anyway. Just try to sbf back to stock. If you still get unknown for baseband, etc. Then you may have a hardware problem. After flashing the radio and rebooting, it should show an android with an open box with a meter, then reboot itself. If your build.prop is correct for the radio, your baseband, prl, etc will show. You *may* have to toggle global/gsm/cdma a few times to get signal. Flash a stock based rom (maverick or minimoto) and see if that shows baseband.
Click to expand...
Click to collapse
I'm really hoping that this is not a hardware problem and that there is a solution. I'm going to SBF back to stock using this method (http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/) as the method via RSDlite never seems to work for me (failed at flashing process). I believe the last attempt failed to flash the radio as that screen with the android never did show up. I will SBF, reflash radio, and if that doesn't work I will flash minimoto. Do you think that the method I used copying the build.prop off the post will work or even is the correct build.prop? Thanks very much for the help by the way, much appreciated.
dinosaur swagg said:
I'm really hoping that this is not a hardware problem and that there is a solution. I'm going to SBF back to stock using this method (http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/) as the method via RSDlite never seems to work for me (failed at flashing process). I believe the last attempt failed to flash the radio as that screen with the android never did show up. I will SBF, reflash radio, and if that doesn't work I will flash minimoto. Do you think that the method I used copying the build.prop off the post will work or even is the correct build.prop? Thanks very much for the help by the way, much appreciated.
Click to expand...
Click to collapse
The build.prop was wrong for the system. If using the stock radio, do not touch the build.prop on any rom you flash. Roms generally have verizon cdma in mind, but foreign gsm works as well. The build.prop should only be swapped to use at&t/tmobile in the US.
Skreelink said:
The build.prop was wrong for the system. If using the stock radio, do not touch the build.prop on any rom you flash. Roms generally have verizon cdma in mind, but foreign gsm works as well. The build.prop should only be swapped to use at&t/tmobile in the US.
Click to expand...
Click to collapse
Okay so I have the 883 modified build.prop. Do you happen to have or know where/how I can get the stock build.prop?
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