Related
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
i'm currently running the 6.16.217 ics leak on my droid 4 and was wondering if there was any way i could install the lte radio from the 6.16.215 leak over the .217's. i would just install the .215 leak, but i find that everything, but signal/data works better for me on the .217.
oh and is anyone else having problems with playing videos from veoh(.)com on the .215 or .217 leaks?
thank you in advance
englishund the answer to my question.
I'm sure there's a simpler way, but this is how i did it. I used the droid4 utility to go from .217 to .215, then i unziped the .217 fastboot file and removed the line in the .xml file that flashed the radio software and used rsd lite to flash the fastboot files over .215. Once that was done i wiped(just to be safe) and rebooted. Everything, with the exception of some websites(veoh.com), has been running well and i haven't lost signal once since then
maddeath said:
englishund the answer to my question.
I'm sure there's a simpler way, but this is how i did it. I used the droid4 utility to go from .217 to .215, then i unziped the .217 fastboot file and removed the line in the .xml file that flashed the radio software and used rsd lite to flash the fastboot files over .215. Once that was done i wiped(just to be safe) and rebooted. Everything, with the exception of some websites(veoh.com), has been running well and i haven't lost signal once since then
Click to expand...
Click to collapse
Are you certain that there is not anther cause for this issue? If you are certain, I'd be very interested as to why this is... and whether the rest of us could benefit.
Well from what i've seen with my droid 4 and droid razr. This version of motoblur ics doesn't really play well with flash. Someone else has started a thread about this http://forum.xda-developers.com/showthread.php?p=30635637#post30635637 hope it helps? Lol
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 bought two droid 4s, both came loaded with ICS 4.0.4, I kept one as a spare and flashed CM11 on one of them, and i was getting decent battery life. However, one day it just bricked but I managed to revived it using the JB utility, so the device was updated to JB 4.1.2, once again I flashed CM on it but since then the battery life became horrible whenever connected to a GSM network, be it 2g or 3g, the phone could barely make it through the day. I always thought it was probably due to the nightly issues or maybe the phone was never designed for long-term GSM use and thus the poor battery life.
Then today, i took out the other droid 4, and performed a nand restore using the image I created on the droid 4 that I am using (the one that was bricked and revived), so both droid 4s are identical in terms of software and battery, as I replaced the battery in both of them with brand original OEM ones. Then I notice that the droid 4 that was not bricked has excellent battery life, and I mean UNBELIEVABLY great battery life. Both phones were placed at the exact same location next to each other, so I began to wonder. I suspect it is probably due to the baseband, as the droid 4 that was never bricked is still using the baseband from ICS 4.0.4.
So I downgraded the baseband on the droid 4 that was once bricked to the ICS 4.0.4 baseband and I was right, it was indeed due to the baseband. Battery life is now phenomenal, at least when compared to using the JB 4.1.2 baseband. I am not sure how this holds for the CDMD/LTE users, but at least for me as a GSM user the 4.0.4 baseband seems to be the best for battery life (and maybe signal, still testing though). I found out that some droid razr users in China also agree that the 4.0.4 baseband is the best.
I have attached the 4.0.4 baseband (and the latest 4.1.2 in case you want to revert) for those of who interested in trying, just flash it in fastboot mode.
The easiest method is to use the JB utility and replace the radio.img file in the folder with the one I have attached, and use the command "moto-fastboot flash radio radio.img"
4.0.4 baseband
4.1.2 baseband
Please try it at your own discretion, I will not be responsible for any bricks.
Update: I don't understand why did i receive so many request to download the files, you do not need permission to download them. I shall try uploading them to dropbox.
I notice that when using the 4.0.4 baseband, I cannot connect to 802.1x wifi networks, so use at your own discreation.
Asked for permission to download the file. Will it work on CM11 also? And doesn't it affect the GSMpatch by Mentor?
You can find official ICS firmware here - http://sbf.droid-developers.org/phone.php?device=11 . Just picked up radio.img from Blur_Version.6.16.217.XT894.Verizon.en.US and flashed it via DROID 4 Utility XT894Jellybean. It works on CM11, not needed to apply Mentor patch again, now testing)
Thanks for the hint. Im trying it now. I hope it will work.
I'm trying too...
When I use Command Prompt and type "moto-fastboot flash radio radio.img" it says waiting for device. I have it connected and it is in MTP-mode.
What is going wrong?
DiMacho said:
When I use Command Prompt and type "moto-fastboot flash radio radio.img" it says waiting for device. I have it connected and it is in MTP-mode.
What is going wrong?
Click to expand...
Click to collapse
Your phone should be in fastboot mode. Turn your phone off, hold down both the vol up and vol down button, then power on. Select AP-fastboot
DiMacho said:
Asked for permission to download the file. Will it work on CM11 also? And doesn't it affect the GSMpatch by Mentor?
Click to expand...
Click to collapse
It does not affect anything else besides the baseband.
The 4.1.2 radio is the same as used in CM11? Can anyone upload it... just in case
edit: nevermind made a full backup in safestrap
The baseband is not part the android software. It will remind unchaged no matter what software you install on the phone.
For me...it's the same battery life with ICS radio img than the JB radio img....meaby my battery problems are comes from different source..Thanks anyway!
rblanca said:
For me...it's the same battery life with ICS radio img than the JB radio img....meaby my battery problems are comes from different source..Thanks anyway!
Click to expand...
Click to collapse
yes, I agree. downgraded the baseband and don't have any improvement of the battery's life
Flashed the 4.1.2 one back... My WiFi didn't connect to my work AP. And I didn't had the feeling my battery time was longer.