Related
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.
I've hacked my bionic for tmobile. If i install a custom rom, will i need to re hack it using radiocomm, etc?
Custom ROM's (in almost all cases) are merely edits to the /system partition of your phone. They do not make changes to the NVRAM portion of your phone where the baseband processor reads for network communication.
However, there is a small chance that the build.prop of the new ROM will need to be re-edited to enforce GSM mode for the phone.
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?
Hello everyone,
Not quite sure where else to put this, but I can't reply in the android dev thread since I am a new member.
I flashed (using SafeStrap 3.05) the newest stable Avatar rom for D3 (using CM 10.1 and android 4.2.2 I think) and it booted ok, mostly everything seemed to work fine (except for camera but that seems to be expected) however I have absolutely no cell service. Not even just data, but the basic cell service for texts and calls isn't on. I tried doing the Verizon activation call, but it would tell me to turn airplane mode off, (which I did, but it either seemed to turn itself back on or not matter if it was on or off anyways).
Has anyone else had this problem and has a work around for it?
Thank you
apefist said:
Hello everyone,
Not quite sure where else to put this, but I can't reply in the android dev thread since I am a new member.
I flashed (using SafeStrap 3.05) the newest stable Avatar rom for D3 (using CM 10.1 and android 4.2.2 I think) and it booted ok, mostly everything seemed to work fine (except for camera but that seems to be expected) however I have absolutely no cell service. Not even just data, but the basic cell service for texts and calls isn't on. I tried doing the Verizon activation call, but it would tell me to turn airplane mode off, (which I did, but it either seemed to turn itself back on or not matter if it was on or off anyways).
Has anyone else had this problem and has a work around for it?
Thank you
Click to expand...
Click to collapse
Do you have a sim card in the phone? This was an issue with some Jellybean/ICS roms. It happens to me as well. For some reason when placing a sim card in the phone(it doesn't need to be active) it allows your phone to get reception.
pandam00nium said:
Do you have a sim card in the phone? This was an issue with some Jellybean/ICS roms. It happens to me as well. For some reason when placing a sim card in the phone(it doesn't need to be active) it allows your phone to get reception.
Click to expand...
Click to collapse
Hey,
So this actually worked, thanks for the heads up!
step by step
apefist said:
Hello everyone,
Not quite sure where else to put this, but I can't reply in the android dev thread since I am a new member.
I flashed (using SafeStrap 3.05) the newest stable Avatar rom for D3 (using CM 10.1 and android 4.2.2 I think) and it booted ok, mostly everything seemed to work fine (except for camera but that seems to be expected) however I have absolutely no cell service. Not even just data, but the basic cell service for texts and calls isn't on. I tried doing the Verizon activation call, but it would tell me to turn airplane mode off, (which I did, but it either seemed to turn itself back on or not matter if it was on or off anyways).
Has anyone else had this problem and has a work around for it?
Thank you
Click to expand...
Click to collapse
Hey, Glad u got your issue resolved..
i am getting my first Android phone (Droid 3 XT862 Gingerbread 2.3 ) and i want to install a custom rom the same way u have..... i was wondering if you or anyone else on the forum could give me step by step guide on how to go about installing the custom rom with the ability to revert back to my original stock OS wen i need to......
i had posted a thread here http://forum.xda-developers.com/showthread.php?t=2378162 and i got some good advise so far:
you or anyone here could reply with the instructions i need or at least send me a link to a tutorial .... as i said this is my first Android so i really dont want to make any mistakes while doing this..
THANX MUCH !!!!!!!
Tha slayer said:
Hey, Glad u got your issue resolved..
i am getting my first Android phone (Droid 3 XT862 Gingerbread 2.3 ) and i want to install a custom rom the same way u have..... i was wondering if you or anyone else on the forum could give me step by step guide on how to go about installing the custom rom with the ability to revert back to my original stock OS wen i need to......
i had posted a thread here http://forum.xda-developers.com/showthread.php?t=2378162 and i got some good advise so far:
you or anyone here could reply with the instructions i need or at least send me a link to a tutorial .... as i said this is my first Android so i really dont want to make any mistakes while doing this..
THANX MUCH !!!!!!!
Click to expand...
Click to collapse
Hey, so this was my process.
First, I made sure that the stock software on the phone was up to date. I did this since that way if you have to go back to stock, you are on the latest version, and you can confirm that you are using the correct rooting application. The root tool I link to below will work on 5.7.906 which I believe is the latest.
Second, root your phone. You will need to go HERE to download the tool. Follow the instructions on the page, and it should go fine. The phone will reboot several times during the process, this is normal. Once the program says it is done, you can go check for the Superuser application in your app drawer (it might be SuperSU or something similar, I can't quite remember).
After you have root access on your phone download the safestrap application for Droid 3 HERE. Make sure you get the one that is specifically for Droid 3. Transfer that file (should be called Droid3Safestrap-3.05.apk) onto your phone.
There are a few ways to transfer files onto your phone. You will also need to do this later to transfer the .zip of whatever ROM you decide on). If you have a micro-sd card that you can put into your computer, that works. Or, you can have the phone on and plug it into the computer and transfer it that way. I believe you can transfer to either the micro SD or the internal memory. I prefer micro SD since you might want to wipe the internal memory to fix things or switch ROMs.
After the .apk is transferred find where you put it using a file manager (I personally use Root Explorer but I think Astro or stock will work), and install it. Go to the new app and run it and it should request root access, which you grant, and it should flash the recovery.
Once you have the recovery installed you can install whatever custom ROM you want, pretty easily. Safestrap is great because even if you screw up the ROM somehow, you can always just boot back into Stock.
Here is where you'll have to chose what custom ROM you want. Now as far as I know, the Droid 3 is fairly limited in its ROM selection. It does have a Cyanogen Mod 10 version, but it is not a stable version and in my experience, doesn't run super great. If you want to try Cyanogen Mod 10, I actually suggest you get the Avatar Rom variant HERE, but keep in mind that apparently you do need a SIM card inserted for the cell signal to work at all. Overall it did seem to run fairly choppy but they are still releasing newer nightly versions (July 20th was the last) so it might have gotten better. One thing to know about these ones is that the camera does not work at all, so if that matters to you just skip these.
Now those two (CM 10 and avatar) are ROMS that will bring the droid 3 up to Android 4.2 Jellybean. If you don't care about getting up to the latest version (Jellybean actually isn't the latest anymore but still pretty darn close), then there are a few other Gingerbread ROMS out there that work a bit better.
HERE is a list of a few other droid 3 ROMs, my favorite Gingerbread one that worked overall really well and stable was Steel Droid. Otherwise, you can just look around and see what's available or what other people are suggesting. Choose your ROM (or several, it's fairly easy to install them so try a few!), and download it. You should get a .zip that is approx. 150-170 MB in size. As an aside you will probably also want to download the corresponding GApps package HERE and put that on the SD card as well. I think some ROMs have that included, but if you boot into a room and it doesn't have the Play store installed, you need to go back into safestrap and install the GApps package over it. You don't have to delete and recreate the rom slot, just go back into install and install it over. When I say corresponding, the different packages go with different versions of Android so for example the one labelled 20110307 would go with Android 2.3.4 which is Gingerbread, the version that Steel Droid uses.
For whichever one you choose, the install process is mostly the same. Reboot your phone, and after the Motorola Logo comes up, you should see the Safestrap splash screen. To get into the recovery menu you have to hit the "Menu" soft-key (the one all the way on the left) within 10 seconds so keep an eye on it.
From the recovery menu go into "Boot Options" You should see 5 options, rom-slot 1-4 and Stock. When you want to switch what ROM you are booting you select on the corresponding slot, and hit activate, then you can reboot through the menu option and it will start that ROM.
To install you will go into "Boot Options" chose whichever rom slot you want (most likely #1). You will have to create that slot, which can take a few minutes. After the slot is created, back out of boot options, and go to "Install". Find the .zip of whichever ROM you chose, and select that to install, and then you can install the corresponding GApps package.
After the install is complete, you can reboot (make sure it says rom slot 1 is selected up to), and it should boot into the Setup process of the ROM. If you ever need to go back to stock, just reboot, go back into Safestrap > Boot options, activate the "Stock" one and boot into that.
A few notes, if you want to switch ROMs, or install multiple ROMs you can do that using the different rom slots with a few exceptions. The Cyanogen Mod 10 and the Avatar Rom (most Jelly bean ones I think) have to be installed in rom slot 1, so if you're doing those and another like Steel Droid, put the Jellybean one in rom slot 1 and the Gingerbread on in rom slot 2. Also if you want to install a different ROM, it's generally best to just completely erase the rom slot and recreate it, then install the different ROM in the newly created rom slot. You can always create backups with Safestrap and restore them with Safestrap. Oh and make sure your phone has a decent charge before doing a lot of the safestrap stuff (I would say at least 60%) you can also have the phone plugged in while doing this stuff, but I'm not always confident it is charging so try and get it charged up before hand.
Finally, if you ever mess up to the point where you're worried that you broke the phone, (boot loops or it is stuck on the Motorola Logo) you can download this restore tool HERE. This should completely wipe and restore the stock software on your phone. It will bring it back one version previous though, so be sure to go through the standard update process to bring it back to 5.7.906 so that the root tool will work. This tool has saved me a few times and is pretty easy to run.
Sorry, I know that is a lot of stuff and looks pretty scary. It really is just a few steps that you should research and make sure you are comfortable doing.
1: Get Root access on the stock software on the phone
2: Install safestrap and flash the custom recovery
3: Boot into recovery and install whichever custom ROM you want
If you have any questions feel free to ask!
Much appreciated !!! ..... i will try these steps as soon as i get my phone..... hope it doesnt make a difference if my D3 is an unlocked GSM phone because all service providers in my country uses GSM
Tha slayer said:
Much appreciated !!! ..... i will try these steps as soon as i get my phone..... hope it doesnt make a difference if my D3 is an unlocked GSM phone because all service providers in my country uses GSM
Click to expand...
Click to collapse
if you are using gms you may need Rom version with a modified build prop, most of the roms threads will have a modified version for GMS, in the OP or somewhere in the thread. if you can't find it just ask in the original rom thread
also some good how to videos here https://sites.google.com/site/tomsgt123/all-videos/videos-page-4
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