Database Develop

ME863 tried flash the brazil rom failed then try the me663 rom also fail at cdt.

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?)

ICS working for Bell XT860 without SBF change

Hey Guys, I don't think this has been posted before, so thought I'd share. I managed to get CM9 working with my Bell XT860 *without* needing to change up the phone using another country's fastboot file.
My phone was Bell 2.3.6, rooted, otherwise stock. I used Hashcode's safestrap to make a nandroid backup and install the latest patched CM9 from Rick#2 available here: http://forum.xda-developers.com/showthread.php?t=1465297
I actually didn't expect it to boot up, but thought I'd give it a go since even if it failed the worst that could happen is that I'd have to SBF anyways.
At first it was a black screen, I had to do a battery pull. After the battery went back in, it started booting up with the animation screen, which showed multiple times over about 5-10 minutes. Then the phone started up Ice Cream Sandwich!
I've been testing it out a bit.. not much yet, but Market is working, data 3g seems to be working 2700 kbps up / 1341 kbps down (with a server that's super far away, 321ms ping). GPS is working... Wifi good. Camera does not work.
Wow, I never expected this. I think this gives hope to those who want to try out Ice Cream Sandwich but still want the ability to go back to stock. Or am I missing something?

ncho2233 said:
Hey Guys, I don't think this has been posted before, so thought I'd share. I managed to get CM9 working with my Bell XT860 *without* needing to change up the phone using another country's fastboot file.
My phone was Bell 2.3.6, rooted, otherwise stock. I used Hashcode's safestrap to make a nandroid backup and install the latest patched CM9 from Rick#2 available here: http://forum.xda-developers.com/showthread.php?t=1465297
I actually didn't expect it to boot up, but thought I'd give it a go since even if it failed the worst that could happen is that I'd have to SBF anyways.
At first it was a black screen, I had to do a battery pull. After the battery went back in, it started booting up with the animation screen, which showed multiple times over about 5-10 minutes. Then the phone started up Ice Cream Sandwich!
I've been testing it out a bit.. not much yet, but Market is working, data 3g seems to be working 2700 kbps up / 1341 kbps down (with a server that's super far away, 321ms ping). GPS is working... Wifi good. Camera does not work.
Wow, I never expected this. I think this gives hope to those who want to try out Ice Cream Sandwich but still want the ability to go back to stock. Or am I missing something?
Click to expand...
Click to collapse
If you bootloop while in safe mode DON'T SBF. Safestrap works by renaming /system to /systemorig and making /preinstall your new /system.
This means when you're in safemode you can always access recovery. So if you bootloop just battery pull to get out of the loop and then you'll e able to hit menu and enter safestrap. Either flash a different rom or return to nonsafe. If you are using safestrap 1.08 and not 1.08d you can't even flash nonsafe mode (1.08d is tweaked to allow advanced user to flash over their nonsafe, for example I have both liberty and eclipse roms on my phone no stock at all)
Also first boot of a rom always takes a long time. After that it should boot much faster
As another note if you do manage to screw up /systemorig somehow you can use motofastboot utility to flash just the system.img part of the SBF package. This will only replace the rom, then you just reboot, install safestrap and restore you backup.
Sent from my XT860 using xda premium

Wow, thanks for the warning, very good information! It's so good to be able to try some custom roms again. I'm out of CM9 already for lack of camera but so far am really impressed with Liberty, it's like my phone has come to life again. Very quick and responsive, amazing ability to customize as well.

Endoroid said:
If you bootloop while in safe mode DON'T SBF. Safestrap works by renaming /system to /systemorig and making /preinstall your new /system.
This means when you're in safemode you can always access recovery. So if you bootloop just battery pull to get out of the loop and then you'll e able to hit menu and enter safestrap. Either flash a different rom or return to nonsafe. If you are using safestrap 1.08 and not 1.08d you can't even flash nonsafe mode (1.08d is tweaked to allow advanced user to flash over their nonsafe, for example I have both liberty and eclipse roms on my phone no stock at all)
Also first boot of a rom always takes a long time. After that it should boot much faster
As another note if you do manage to screw up /systemorig somehow you can use motofastboot utility to flash just the system.img part of the SBF package. This will only replace the rom, then you just reboot, install safestrap and restore you backup.
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
hi there ,i using 1.08d and try to flash willis111's bell 2.3.6 rom ,and I want to flash it to the orig system ,not the preinstall ,but every I flashed it ,the my xt860 restart and into the ori rom(2.3.5 bra),not the bell 2.3.6.
here is what i do
1 restart my xt860,and press menu
2 in the safestrap,wipe date ,format system ,then in advance flash .zip nonsafe
3 restart my xt860,and still the 2.3.5 bra rom ..
sorry for my bad English ,and great thx
---------- Post added at 04:44 AM ---------- Previous post was at 04:29 AM ----------
Endoroid said:
(1.08d is tweaked to allow advanced user to flash over their nonsafe, for example I have both liberty and eclipse roms on my phone no stock at all)
Click to expand...
Click to collapse
all I want to know is how to ....thxxxxxxxxx

That's how it should be done
Last time I flashed my /systemorig was before 1.08d had been released so I did it co ming off a fresh fastboot flash using bootstrap to flash liberty, then installed safestrap. I haven't found a rom to replace liberty in my /systemorig yet so I haven't tried the advance flash yet. Sorry.
Sent from my XT860 using xda premium

newaxis said:
hi there ,i using 1.08d and try to flash willis111's bell 2.3.6 rom
Click to expand...
Click to collapse
Hi
i' desperate for willis111's bell 2.3.6 rom but can't download from rapidshar, there is a way you upload the file to non-repidsher site?
Thanks ahead

Help: deleted back up of stock rom from safestrap recovery

I was attempting to flash the stock att firmware via rsd and have deleted the stock rom from safestrap recovery in the process. I would like to get back to stock rom (ATT). I can boot in safestrap and currently have golden rom on another rom slot but need to get back to stock firmware or stock rom as im selling the phone atrix HD.

Oneofonex1 said:
I was attempting to flash the stock att firmware via rsd and have deleted the stock rom from safestrap recovery in the process. I would like to get back to stock rom (ATT). I can boot in safestrap and currently have golden rom on another rom slot but need to get back to stock firmware or stock rom as im selling the phone atrix HD.
Click to expand...
Click to collapse
I can inbox you a link to my restore, note: I have personal files, so I'm going to trust you'll delete the data partition. Tell me if your interested.

Maybachiswhereitsat said:
I can inbox you a link to my restore, note: I have personal files, so I'm going to trust you'll delete the data partition. Tell me if your interested.
Click to expand...
Click to collapse
Thats amazingly generous of you, but I was able to upgrade RSD lite and flash the stock firmware. Again, i greatly appreciate your help.

No problem, glad you could fix your phone.
Sent from my DROID Atrix HD MAXX using xda app-developers app

Is your AT&T ROM image still available?
Maybachiswhereitsat said:
No problem, glad you could fix your phone.
Hi, I have an Atrix HD with Batakang in slot 1 and of course the stock AT&T ROM in, well, the Stock slot. I have Safestrap 3.11. I wanted to unlock the phone for int'l use, and it simply would not give me the prompt to enter the unlock code (said "Invalid SIM" or something like that), so I left it with an AT&T dealer because the process should have been simple, but wasn't.
They couldn't do it either, but when I got the phone back, the entire 8GB ROM space was wiped! Batakang was gone, the Stock slot is empty, and unfortunately, the Safestrap backup I made of Stock (and left on the internal SD) was gone too!
I did have a Batakang backup which restored fine, I entered the unlock code OK in it (I assume that worked - there was no confirmation message), but still have an empty AT&T stock slot.
What ROM images I've found are not compatible with Safestrap, so what I'm looking for is either a Safestrap backup or a zip installer compatible with Safestrap, or any other suggestions appreciated! Thanks!
Click to expand...
Click to collapse

[Q] Help - Droid 3 information "unknown"

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?

Flashing XT883 ROM using safestrap

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