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?
Related
Given that most of the custom roms are using RIL from AT&T Stock, I wanted to see if I can flash Bell Stock raider RIL ,
I am assuming that would prevent all the 4G/3G toggle that I still see.
RILs will not prevent the toggling. RILs are simply libraries(drivers) that interface with the radio. some people usually report that matching RILs with the radio that you are on will yield better signal/battery life. technically they should be the same between the AT&T and Bell/Rogers....
it can definitely be flashed without S-Off since they are simply files located in /system/lib, and do not touch the radio anything.
i will package the BELL and ROGERS RILs up and add them to my thread. it might take me a little while unless someone else has them ready to package up.
That would be really great..you are really great ...I may have to send some more monsters to you (Hopefully this weekend )
So would I just copy *ril.so" files from stock Bell ROM under /system/lib/*.
Assuming I backup , I hope I can do no damage , ofcourse If can edit the system.img (Doubt that it would straight forward)
Tried to flash RIL and failed (attached files I used)
So I tried and it did not work, and even reverting to backup files that I over wrote did not work
I attached the files that I tried to extract from Bell Stock RUU and I hope they are correct ones.
I have tried for days to get ICS working on my phone. I am using the Chinese radio and everything is working fine on GB.
When I update to ICS it says baseband unknown
Updating the Build prop from default 4 to 3 does nothing.
On Gummy it just stalls and won't boot up.
Using the zips for GSM fix and RWAILY's Modified build in safestrap aborts the Installation. Updating the xt883 radio aborts installation
Why is my phone being such a douchebag.
Try using rick#2's xt860 patch
Sent from my XT860 running ICS using xda premium
http://forum.xda-developers.com/showthread.php?t=1560519 here you can find the build prop for ICS just replace it with root explorer and you should be good.
Sent from my XT862 using XDA
Thanks but they still don't work.
The GSM fix will not flash in safestrap. When I take the build prop and replace it manually, the splash screen hangs
Anytime the build prop is tweaked, I run into problems in ICS. GB is fine though.
phonephoenix said:
Thanks but they still don't work.
The GSM fix will not flash in safestrap. When I take the build prop and replace it manually, the splash screen hangs
Anytime the build prop is tweaked, I run into problems in ICS. GB is fine though.
Click to expand...
Click to collapse
hi
try to make a comparison between a stock GB build.prop vs the modified one for chinesse.
with that info update manually the build prop in ics.
because if you simply put the GB buildprop on ICS ICS will die
if that works can you post which changes you noted
I'm experiencing the same thing. But in my case I also get baseband unknown is GB (verizon gb without radio). Still looking for solution
Sent from my SGH-T839 using XDA
This should work for AOKP at least. It did for me.
nikeusfr said:
For gsm user, this is solution and all works well :
install safestrap
format data, cache and system
install aokp and gapps
reboot without sim card in the phone
edit build.prop with rootexplorer or other :
# Default network type.
# 7 => Global Phone (4 => CDMA).
ro.telephony.default_network=3 (instead of 7 or 4)
# BEGIN Moto,IKDROIDPRO-430, a17673
# Feature33857 on DroidWE, support DualMode switch, UMTS/CDMA
ro.mot.FTR.33857=false (instead of true)
# END IKDROIDPRO-430
# BEGIN Moto, IKSTABLETWO-1284, nfjb73
# without this property, the lock screen would take global phone as UMTS
# block user to operate before setup
keyguard.no_require_sim =false (instead of true)
# End Moto
save build.prop after this change
new step, enter *#*#4636#*#* into the dialer. Then goto "Phone Information". Near the bottom of that screen there's a drop down of network preference. For GSM-ONLY use GSM (PRL). Exit that screen and reboot the phone.
shut off phone, insert your sim card and boot the phone.....
thanks to hashcode and all over.
Click to expand...
Click to collapse
I've done everything. I still get the same results.
When i enter *#*#4636#*#*
I go into phone information
I try to change it from unknown to GSM and it won't do it.
Phone is a big D Bag.
EDIT: Thank you for trying though.
Can you recommend any GB roms? I had Mav and it was pretty good
I use this exact build.prop with my droid 3 on tmobile and ics
http://forum.xda-developers.com/showpost.php?p=23884104&postcount=1368
Hope it helps
SithDagger said:
I use this exact build.prop with my droid 3 on tmobile and ics
http://forum.xda-developers.com/showpost.php?p=23884104&postcount=1368
Hope it helps
Click to expand...
Click to collapse
But can you tell me if you have data connection with T-Mobile?
I am using Mavrom 3.5 and my provider is AT&T. 3G DATA is working so nice and i like this rom but i am thinking to move to ICS.
But if DATA connection is not working with GSM providers, i will stick with Maverick rom.
koukobin said:
But can you tell me if you have data connection with T-Mobile?
I am using Mavrom 3.5 and my provider is AT&T. 3G DATA is working so nice and i like this rom but i am thinking to move to ICS.
But if DATA connection is not working with GSM providers, i will stick with Maverick rom.
Click to expand...
Click to collapse
Yes, fully working 2g data connection with tmobile, wouldnt have ics on my phone without it. 3g would only work with at&t though, since the droid3's hardware doesnt support tmobiles 3g band.
Also, dunno if this helps, but i dont use *#*#4636#*#* to setup, i go into the mobile network settings, and scan for a network operator, connects just fine.
SithDagger said:
Yes, fully working 2g data connection with tmobile, wouldnt have ics on my phone without it. 3g would only work with at&t though, since the droid3's hardware doesnt support tmobiles 3g band.
Also, dunno if this helps, but i dont use *#*#4636#*#* to setup, i go into the mobile network settings, and scan for a network operator, connects just fine.
Click to expand...
Click to collapse
Thanks sounds very nice. Can you also please tell me if you are using CM9 ICS or AOKP ICS?
koukobin said:
Thanks sounds very nice. Can you also please tell me if you are using CM9 ICS or AOKP ICS?
Click to expand...
Click to collapse
CM9, havent tried AOKP yet, need to try it sometime.
SithDagger said:
I use this exact build.prop with my droid 3 on tmobile and ics
http://forum.xda-developers.com/showpost.php?p=23884104&postcount=1368
Hope it helps
Click to expand...
Click to collapse
Hash should add that **** onto his post. I'm seeing a ton of requests for this very thing.
I think your problem is not with the build.prop. Its with the radio that you have before flashing. In my case i have the stock verizon rom with the chinese radio and when i flash to ICS i have the same problem. No signal, unkown imei, etc.
You have to flash the original verizon radio(XT862) and then flash to ICS.
Look at this post:
http://forum.xda-developers.com/showthread.php?t=1544125
Tell me if you fix your problem
chemicalboyxda said:
I think your problem is not with the build.prop. Its with the radio that you have before flashing. In my case i have the stock verizon rom with the chinese radio and when i flash to ICS i have the same problem. No signal, unkown imei, etc.
You have to flash the original verizon radio(XT862) and then flash to ICS.
Look at this post:
http://forum.xda-developers.com/showthread.php?t=1544125
Tell me if you fix your problem
Click to expand...
Click to collapse
But cm9 doesn't touch the radio... I flashed cm9 from stock when I had the chinese radio installed on stock, so I dunno, no problems here.
Of course after I flashed I went to settings, wireless and networks, more, mobile networks, and then network operators, then I selected tmobile, problem solved. This was after modifying the build.prop, and flashing cm9.
I see no reason to flash the stock radio when the chinese is needed for tmobile/at&t, and cm9 doesn't touch it.
sent from Sheogorath with cheese!
SithDagger said:
But cm9 doesn't touch the radio... I flashed cm9 from stock when I had the chinese radio installed on stock, so I dunno, no problems here.
Of course after I flashed I went to settings, wireless and networks, more, mobile networks, and then network operators, then I selected tmobile, problem solved. This was after modifying the build.prop, and flashing cm9.
I see no reason to flash the stock radio when the chinese is needed for tmobile/at&t, and cm9 doesn't touch it.
sent from Sheogorath with cheese!
Click to expand...
Click to collapse
In my case if i flash to CM9 from stock+chinese radio i have the problems that i mention(unkown imei, baseband, no signal, etc). If i flash to CM9 from stock+stock radio that problems dissapear.
I bought a used Droid 3 XT862 which was running 5.7.905 firmware and i went back to 5.6.890 (Kernel and bootloader remained intact as expected). Then i rooted the phone and flashed the chinese radio. I installed CM9 and then i used the buid.prop from this link:
http://forum.xda-developers.com/showpost.php?p=23884104&postcount=1368
I couldn't flash this zip file through safestrap (at least no go for my occasion) so pushed it to /system by using root explorer.
I rebooted the phone and i had 3G data connection working just fine. My provider is AT&T.
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
Hi Everyone,
I bought a used phone, verizon droid 3 with the XT883 radio flashed on it, and have working safestrap 3.05. Currently I am able to use CDMA OMH, but without data. I have tried multiple options including flashing the newer version of the radio, as well as pppd-ril.options editing but it does not work. CDMA apn settings are disabled. I have also made changes to build.prop without any results. Anything else I can try?
One of my options is to flash the chinese ROM as it supports CDMA apn settings. I am not sure I can use RSD lite in one of the ROM slots.Can I select one of the ROM slots as active and flash the xt883 files on it? I think it will write to the stock ROM partition itself? Any help on how to go about it?
EDIT:
So I uninstalled safestrap and tried to flash the XT883 ROM(57.1.60) using RSD lite as described, but the following files showed an error in flashing and the phone bricked 1) Cdt.bin 2) Recovery 3) boot. I tried to flash by editing the xml file and skipping these files, but the phone showed a black screen on normal boot.
I tried to recover using psouza's rar file, but even there recovery and boot failed to flash. The phone is working though, and I am able to retain former functionality using motofail and flashing the XT 883 Radio again. Can someone suggest me a solution by which I can install the XT883 ROM and/or be able to access CDMA APN settings? Currently my fastboot suggests that my system is on .890 version, though the settings>about phone suggest I am on XT883 (possibly because of the radio)
dinu_dr said:
Hi Everyone,
I bought a used phone, verizon droid 3 with the XT883 radio flashed on it, and have working safestrap 3.05. Currently I am able to use CDMA OMH, but without data. I have tried multiple options including flashing the newer version of the radio, as well as pppd-ril.options editing but it does not work. CDMA apn settings are disabled. I have also made changes to build.prop without any results. Anything else I can try?
One of my options is to flash the chinese ROM as it supports CDMA apn settings. I am not sure I can use RSD lite in one of the ROM slots.Can I select one of the ROM slots as active and flash the xt883 files on it? I think it will write to the stock ROM partition itself? Any help on how to go about it?
EDIT:
So I uninstalled safestrap and tried to flash the XT883 ROM(57.1.60) using RSD lite as described, but the following files showed an error in flashing and the phone bricked 1) Cdt.bin 2) Recovery 3) boot. I tried to flash by editing the xml file and skipping these files, but the phone showed a black screen on normal boot.
I tried to recover using psouza's rar file, but even there recovery and boot failed to flash. The phone is working though, and I am able to retain former functionality using motofail and flashing the XT 883 Radio again. Can someone suggest me a solution by which I can install the XT883 ROM and/or be able to access CDMA APN settings? Currently my fastboot suggests that my system is on .890 version, though the settings>about phone suggest I am on XT883 (possibly because of the radio)
Click to expand...
Click to collapse
I have same problem plz if have any idea about it plz share
Thanks
While I was running CyanogenMod, I suddenly had a devastating issue where the phone would not even detect SIM Cards, and Bluetooth would sometimes cause the phone to force reboot. Afterwards some custom ROMs have the same issues, and reboot literally randomly, sometimes endlessly bootlooping.
The stock 5.1 ROM also had the issues but also didn't wanna connect to WiFi.
I recently followed a guide to install the 6.0.1 update on the Turbo, and suddenly, everything worked again. No random reboots, Bluetooth working, and WiFi. However ANY other ROM would have the issues.
Is there something that the OTA 6.0.1 update fixes that all other ROMs cause these problems?
No one else has those problems on custom ROMs. So, there's nothing to "fix".
No one would be running any of the custom ROMs if they had such issues.
Stock 5.1 also didn't have connection issues nor Wi-Fi issues.
Flashing 6.0.1 stock reflashed your radio, which "fixed" your issue, probably. THAT was probably all you needed to do. You can also flash @bhb27 clear modem file, which fixes stuff like GPS. Sometimes flashing a custom ROM will confuse a radio/modem and clearing the cache/stats with that file helps as well as reflashing the radio.
I thought that might have been what happened, but even after flashing the 6.0.1, which has everything working, installing a custom ROM gives the issues. Before this I always thought my hardware simply failed but this is the only ROM where it works now, the 6.0.1.
So what I should try is clearing the modem status or reflashing the radio even after installing a custom ROM just to refresh the things?
ethangarsia517 said:
I thought that might have been what happened, but even after flashing the 6.0.1, which has everything working, installing a custom ROM gives the issues. Before this I always thought my hardware simply failed but this is the only ROM where it works now, the 6.0.1.
So what I should try is clearing the modem status or reflashing the radio even after installing a custom ROM just to refresh the things?
Click to expand...
Click to collapse
Yes, some of your symptoms like the endless bootlooping seem very unusual. I don't know of radio-related issues that cause that. But not being able to use GPS, Wi-Fi connection issues, or even not detecting SIM cards are symptoms of radio/modem problems.
When flashing a custom ROM on our Quarks, GPS especially was a complaint. There were workarounds to fix it as early as 2015, but then @bhb27 (who is the dev for several custom ROMs) came up with the @bhb27 Clear Modem File. You flash that. In simplistic terms it clears the cache of your modem. It has helped countless people, with Droid Turbo/Moto Turbo/Moto Maxx.
Often just that fixes any issues, but you can also then take the next step of re-flashing the most current radio/modem for the Droid Turbo.
ROMs don't have radio/modems included inside the ROM. When you flash a custom ROM, it uses the radio you already have. Clearing the cache, and reflashing makes everything new again.
We've had custom ROMs for over two years now for our Quark phones. True the Droid Turbo XT1254 bootloader was finally unlocked back in November of 2015, but still that's been 1.5 years. There's tons of custom ROMs and if you look at the download stats of those ROMs there's THOUSANDS of people using them. If the ROMs had the issues you had, there would be no users, believe me!
The issue is for a percentage of people, not even a majority, but a percentage, the radio/modem becomes confused when flashing a custom ROM. But it's easily fixed...
Go look at this page from just two days ago. Similar issue with AOKP 7.X. EXCEPT it's NOT an issue with the ROM. It's the issue of someone not reading thoroughly.
Phone calls not working
https://forum.xda-developers.com/droid-turbo/development/rom-aokp-7-x-quark-t3504629/page67
Yet, the dev clearly says in post #2:
NepoRood said:
Last, but not least, you just might need to clean your modem:
Download Zip
Click to expand...
Click to collapse
Once the user flashed that, all was well.
raginhomosapien said:
I just flashed the clean modem.zip, and everything seems to be properly working now! I have rebooted and started a call 5 times, and it has worked each of those times. I'll see how things go over the next few days, whether it breaks again or continues to work without issues.
Thanks for the help!
Click to expand...
Click to collapse
and this guy over in RR 7.x last week, with a Moto Maxx XT1225:
Wi-Fi won't connect.
https://forum.xda-developers.com/showpost.php?p=71652207&postcount=1474
I helped him by providing the link to the clear modem file and the latest radio/modem for his model. (He flashed both, just to make sure.)
kenedi jr said:
Ahahah thank you... All works now. You saved my life
Click to expand...
Click to collapse
* Here's the Clear Modem File, also called the Clean Modem file:
@bhb27 Clean_modem_status
https://www.androidfilehost.com/?fid=24531035584725320
*Here's the latest TWRP-flashable Marshmallow radio/modem for the XT1254 Droid Turbo.
TheSt33v said:
By popular demand, here are just the (XT1254) modems:
XT1254 MARSHMALLOW MCG24.251-5-5 100% Stock
https://mega.nz/#!m9xnwDjD!jvvLXbGpCN9QVzRY1hph6JOyZv8kiBcLs2bsCdIgv8w
Click to expand...
Click to collapse
*For those with the XT1225 Moto Turbo/Moto Maxx, here's the latest TWRP-flashable radio/modem:
XT1225 MARSHMALLOW Radio_Flasher_Stock_MPGS24.107-70.2-2.zip
https://www.androidfilehost.com/?fid=457095661767122577
Do NOT flash an XT1254 radio over an XT1225 or an XT1225 radio over an XT1254. I am including both radios in this thread for people who may need them.
The clear modem file/clean modem status file (whatever you want to call it) is for ALL Quarks, but the radio/modem files are very device specific.
I always keep a copy of the Clear Modem file and the latest TWRP-flashable radio in my Download folder on my phone. Whenever I flash a new ROM or even an update to a ROM, I always flash those files too. It can never hurt and can only help.
ChazzMatt said:
* Here's the Clear Modem File, also called the Clean Modem file:
@bhb27 Clean_modem_status
https://www.androidfilehost.com/?fid=24531035584725320
*Here's the latest TWRP-flashable Marshmallow radio/modem for the XT1254 Droid Turbo.
Do NOT flash an XT1254 radio over an XT1225 or an XT1225 radio over an XT1254. I am including both radios in this thread for people who may need them.
The clear modem file/clean modem status file (whatever you want to call it) is for ALL Quarks, but the radio/modem files are very device specific.
I always keep a copy of the Clear Modem file and the latest TWRP-flashable radio in my Download folder on my phone. Whenever I flash a new ROM or even an update to a ROM, I always flash those files too. It can never hurt and can only help.
Click to expand...
Click to collapse
Unfortunately, flashing the clean modem.zip didn't bring about anything than a very temporal fix. Now it's basically a complete crapshoot as to whether I will get complete silence on my end and my mic muted for the other person, or whether the call will go through, but after some a mount of time I will lose all audio and my mic will mute. A couple times calling worked fine. Would you recommend flashing the XT1254 radio/modem zip you included now that I've flashed the clean modem?
raginhomosapien said:
Would you recommend flashing the XT1254 radio/modem zip you included now that I've flashed the clean modem?
Click to expand...
Click to collapse
Yes, if you have an XT1254.
In TWRP, flash back-to-back with the Clean Modem file first, then the radio/modem.
Then let TWRP clear all caches (it's an option anytime you "install" something), then reboot to system.
raginhomosapien said:
Unfortunately, flashing the clean modem.zip didn't bring about anything than a very temporal fix. Now it's basically a complete crapshoot as to whether I will get complete silence on my end and my mic muted for the other person, or whether the call will go through, but after some a mount of time I will lose all audio and my mic will mute. A couple times calling worked fine. Would you recommend flashing the XT1254 radio/modem zip you included now that I've flashed the clean modem?
Click to expand...
Click to collapse
ChazzMatt said:
Yes, if you have an XT1254.
In TWRP, flash back-to-back with the Clean Modem file first, then the radio/modem.
Then let TWRP clear all caches (it's an option anytime you "install" something), then reboot to system.
Click to expand...
Click to collapse
FYI: just re-flashing the modem doesn't fix all issues -- and just flashing the Clear Modem file doesn't always fix all issues (but it does fix a lot). However, a combination of the two, YES.
Back before the @bhb27 coded the Clear Modem file, just re-flashing the modem did NOT fix GPS issues which plagued a minority of users. I never had the issue, but for people that did have it, they complained and complained. For us who didn't have it, we couldn't figure out what they were doing "wrong".
Someone figured out a a very complicated workaround (going back to stock, getting a GPS lock, then immediately flashing the custom ROM, etc.) And then someone figured out they could share a TWRP backup of their "good" modem for people with GPS problems.
But the @bhb27 Clear Modem file FIXED ALL THAT, for GPS. All you had to do was flash that, after installing a custom ROM.
But for other radio/modem problems, some people flashing the Clear Modem file AND then re-flashing radio/modem is the key.
You can flash them both back to back in TWRP -- the Clean Modem file first, then the radio/modem.