I was flashing ROMs and had DLed a bunch from a site exclusively for RAZR M phones and some guy had put a bunch of stuff for the XT910 and I accidentally flashed a AOKP GSM zip and now I can't flash anything or RSDLite back to stock, which was always my failsafe out of a soft brick. I still have TWRP and I was able to restore my backup but boot and system files only, data wouldn't restore. Now my phone will boot to the custom splash screen but it just loops. And I first get the red Moto M circle and do NOT get the unlocked boot loader warning. So any help? I will post the RSDLite results when I get home.
ok heres the site I got the file from, this guy should be hung...surdu_petru...http://www.androidfilehost.com/?w=developers&did=70
noone? help is needed please! OK well I restored to a TWRP recovery i had and it worked partially, as long as i unchecked the data partition, the boot and system partitions stuck, so now my unlocked bootloader warning is back as is my custom ROM splash screen, but in a bootloop. I tried RSDLite flashing it again and the 4.1.1 firmware seemed to work but still loops. 4.1.2 and 4.0.4 wont flash because of the "get var, OEM" issue. I had this happen once before aswhile back but was using CWM recovery and juyst switched to TWRP, which fixed it, but not so lucky this time around. So I am wondering if i flash some other partitions like the persist forthe radio, esp since i flashed a xt910 GSM file which is why my phone now thinks its a xt910. Any ideas? please!!!
ok PROBLEM SOLVED. aFTER LOSING THE CUSTOM RECOVERY BY TRYING TO FASTBOOT WITH RSDLITE I DID THE "delete the Getvar and OEM LINES FROM THE FACTORY FIRMWARE OF 4.1.2 (THE .78 VERSION) AND SINCE THE xt910 ROM WAS 4.2.2 AND MY RADIO HAD PREVIOUSLY BEEN UPDATED TO .78, I FIGURED THE .78 4.1.2 WOULD BE MY BEST SHOT, AND SO IT WAS. THAT "GETVAR" ISSUE IS DEFINATE PROBLEM THAT SHOULD BE RESOLVED ANYWAY. wELL ANOTHER TRAGEDY AVERTED, AND IM GETTING PRETTY GOOD AT THIS, LOL, AVOIDING MISTAKES WOULD BE BEST THO. sO BEWARE OF THE "ANDROIDFILEHOST" SITE, THEY HAVE A GUY POSTING XT910 ROMS UNDER XT907 FOLDER! almost cost me a phone Close this thread
Edit does not work on either of my razr m phones
one last note, I thought i was unable to get the radio/modem working again as a resullt of flashing a GSM ROM for the XT910, but that issue was fixed with a Firmware flash, or FXZ file, through RSDLite. The issue is actually the RAZR Ms US GSM unlock (NV edit using RadioComm) that is still not working. As with my other RAZR M (LOCKED, rooted, and SS installed) I can not seem to get it working by using RC or DFS, and I am really starting to think the .78 or .94 update killed this edit just as it did the bootloader unlock, even though everyone says it doesnt and that this edit can be performed on locked, unrooted and completely updated devices. If so then....
CAN SOMEONE EXPLAIN WHY BOTH MY LOCKED AND UNLOCKED RAZR M DEVICES WILL NOT ACCEPT THE US GSM EDIT???? PLEASE?
Here is my Feedback for you...
rocketrazr99 said:
one last note, I thought i was unable to get the radio/modem working again as a resullt of flashing a GSM ROM for the XT910, but that issue was fixed with a Firmware flash, or FXZ file, through RSDLite. The issue is actually the RAZR Ms US GSM unlock (NV edit using RadioComm) that is still not working. As with my other RAZR M (LOCKED, rooted, and SS installed) I can not seem to get it working by using RC or DFS, and I am really starting to think the .78 or .94 update killed this edit just as it did the bootloader unlock, even though everyone says it doesnt and that this edit can be performed on locked, unrooted and completely updated devices. If so then....
CAN SOMEONE EXPLAIN WHY BOTH MY LOCKED AND UNLOCKED RAZR M DEVICES WILL NOT ACCEPT THE US GSM EDIT???? PLEASE?
Click to expand...
Click to collapse
The Reason why it doesn't accept the Us GSM edit Is because the Motorola Droid Razr M is not a gsm phone it is a CDMA phone with LTE. Thus it will not work on any GSM providers unless that provider is like straight talk with multiple networks supported otherwise the phone is stuck on verizon wireless or any other carrier you bought it from. Have A Good Day. By the way my two old accounts got banned for no reason. if you want to know what experience i have look at my devices on the accounts Droidxpert and Droidxpert1. Thanks
rocketrazr99 said:
one last note, I thought i was unable to get the radio/modem working again as a resullt of flashing a GSM ROM for the XT910, but that issue was fixed with a Firmware flash, or FXZ file, through RSDLite. The issue is actually the RAZR Ms US GSM unlock (NV edit using RadioComm) that is still not working. As with my other RAZR M (LOCKED, rooted, and SS installed) I can not seem to get it working by using RC or DFS, and I am really starting to think the .78 or .94 update killed this edit just as it did the bootloader unlock, even though everyone says it doesnt and that this edit can be performed on locked, unrooted and completely updated devices. If so then....
CAN SOMEONE EXPLAIN WHY BOTH MY LOCKED AND UNLOCKED RAZR M DEVICES WILL NOT ACCEPT THE US GSM EDIT???? PLEASE?
Click to expand...
Click to collapse
The phones will accept the edit and will work on GSM if you unlock with RadioComm. He ran into issues because he didn't unlock with RadioComm.
Sent from my Droid RAZR MAXX HD using xda app-developers app
ImDroidxpert said:
The Reason why it doesn't accept the Us GSM edit Is because the Motorola Droid Razr M is not a gsm phone it is a CDMA phone with LTE. Thus it will not work on any GSM providers unless that provider is like straight talk with multiple networks supported otherwise the phone is stuck on verizon wireless or any other carrier you bought it from. Have A Good Day. By the way my two old accounts got banned for no reason. if you want to know what experience i have look at my devices on the accounts Droidxpert and Droidxpert1. Thanks
Click to expand...
Click to collapse
Sorry but they both unlocked. The issue was (I think) that I was typing "01" but only needed to actually type "1" and then the window shows "01". It was something like that anyway.
soft bricked now
Now my problem is I wiped the whole phone by mistake and cant restore since i lost CWM and cant RSDLite any firmware since the latest was already on it and some error message showed that i had flashed an earlier version or somthing, IDK. But I read that to fix it i need a newer firmware to run on RSDLite, of which none exists. So my phone is soft bricked until Kitkat gets released for the M, which is never, lol
rocketrazr99 said:
Now my problem is I wiped the whole phone by mistake and cant restore since i lost CWM and cant RSDLite any firmware since the latest was already on it and some error message showed that i had flashed an earlier version or somthing, IDK. But I read that to fix it i need a newer firmware to run on RSDLite, of which none exists. So my phone is soft bricked until Kitkat gets released for the M, which is never, lol
Click to expand...
Click to collapse
You don't need to run a newer firmware, you just need to run one that's equivalent to what you have now. You got the TZ fail because you tried to flash an older FW.
RikRong said:
You don't need to run a newer firmware, you just need to run one that's equivalent to what you have now. You got the TZ fail because you tried to flash an older FW.
Click to expand...
Click to collapse
It was actually more than just that. I cant remember but saw a thread about it saying that it had an old firmware and a present firmware and it needs a newer firmware, but I am onm the newest one already so I have to wait for one to get pushed out, idk. Now i can get as far as flashing process 17/21, which is the system flash, when te phone returns a fail. i will try a few tricks i learned from prior luck
rocketrazr99 said:
It was actually more than just that. I cant remember but saw a thread about it saying that it had an old firmware and a present firmware and it needs a newer firmware, but I am onm the newest one already so I have to wait for one to get pushed out, idk. Now i can get as far as flashing process 17/21, which is the system flash, when te phone returns a fail. i will try a few tricks i learned from prior luck
Click to expand...
Click to collapse
OK, Rik was right, I didnt have to wait for a new firmware release. I kept trying to flash the most recent version of 4.1.2 and kept hitting a wall at 17/21, which is the flashing of the system image. Occasionally it would fail before that at 16/21, which is CDROM files. That always happened the first attempt after I unhooked the phone and restarted everything, so I started thinking, what is causing the flash to fail for no apparent reason. Then it finally hit me....it was as if my phone was running out of storage space. But that just isnt possible when you are flashing with RSDLite since it wipes out everything first. So I then remembered that my PC has very little room left on its hard drive. Could it be that RSDLite needed more space to work? Hmmmmm, so I deleted a few videos and moved the firmware file to that area (it may or may not help) of the drive and tried again. After the initial fail at 16/21 I was met with a successful flash, although it took a very long time to flash the system image, which I attribute to low disk space. So there you have it.... of course I had to modify the XML file and remove the "getvar" line, and realized I had forgot a golden rule.... all programs and apps need a certain amount of disk drive space in order to operate, and RSDLite is no exception! So now my locked phone will get the carrier unlock edit and Safestrap installed with an extra ROM in slot 1, then it goes on eBay, lol. I have my other RAZR M in semi retirement, it has the BL unlocked as well as the carrier, but I couldnt pass up a new Nexus 5 for $250, but I will surely be swapping the SIM card back and forth because I really miss my RAZR M already. Wish they would make a RAZR M with the processing power of the Nexus 5. Anyhow, PLEASE CLOSE THIS THREAD, TY.
Use this I used it when I bricked mine
Sent from my XT907 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2249773
Sent from my XT907 using Tapatalk
I'm having a similar problem with my xt907. The phone will boot and loop on the boot loader. I have tried to restore with rsd lite bit haven't had any luck. Any suggestions, I know it may not be enough information. If you ask I might be able to give you more details.
---------- Post added at 10:33 PM ---------- Previous post was at 10:28 PM ----------
Also I can't get into recovery.
ImDroidxpert said:
The Reason why it doesn't accept the Us GSM edit Is because the Motorola Droid Razr M is not a gsm phone it is a CDMA phone with LTE. Thus it will not work on any GSM providers unless that provider is like straight talk with multiple networks supported otherwise the phone is stuck on verizon wireless or any other carrier you bought it from. Have A Good Day. By the way my two old accounts got banned for no reason. if you want to know what experience i have look at my devices on the accounts Droidxpert and Droidxpert1. Thanks
Click to expand...
Click to collapse
I am sorry to say that you are uninformed and the XT907 CAN have van NV edit which allows it to be used on GSM networks. The phone is already setup to be comparable with GSN since Verizon made it a "global" handset, but....they also blocked any GSM capabilities in the U.S., until of course you do the NV edit. So please remove your post.
Related
Hello, I just got a Motorola Milestone X. Its running on ACS alaska network. From reading I've done this phone appears to be the moto x but just not the vws branded phone? My question does anyone know of a way to root it and or any custom roms for it? Its filled with bloatware and no way to remove it and the stock rom is very ugly.
Ive tried z4root, superoot, androot and various other rooting guides that were supposed to work on the Moto X but all have failed me. Its running 2.2.1 and from what I gather this might be the problem?
Any help or info from anyone else familiar with this phone would be greatly appreciated as I hate it in its current stock form and would like to at least be able to remove the bloatware and crap I dont use even if there arent any custom roms for it. Thank you
Possible root
I also have a milestone x from a local carrier, and was able to root it.
I downloaded and installed all the Motorola drivers.
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Hooked the phone up and went through each mode to ensure all the drivers were installed.
I then installed the latest version of SuperOneClick from http://forum.xda-developers.com/showthread.php?t=803682
I then extracted and ran SuperOneClick, chose the psneuter exploit and clicked root. This was able to root the phone. I did need to reboot the phone before the superuser application would work though.
I haven't looked into custom roms yet.
thank you very much for the information. I tried super one click but it would always lock up but maybe i'll give it another try. Is your phone running 2.2.1? Thanks again for the reply.
Inciner8Fire said:
I also have a milestone x from a local carrier, and was able to root it.
I downloaded and installed all the Motorola drivers.
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Hooked the phone up and went through each mode to ensure all the drivers were installed.
I then installed the latest version of SuperOneClick from http://forum.xda-developers.com/showthread.php?t=803682
I then extracted and ran SuperOneClick, chose the psneuter exploit and clicked root. This was able to root the phone. I did need to reboot the phone before the superuser application would work though.
I haven't looked into custom roms yet.
Click to expand...
Click to collapse
I must have used a older version of SuperOneClick before. This one you linked worked with no problems at all. Thank you so much!
No prob, glad it worked for ya.
Thanks for the post. I was going through the same frustrations with my new ACS Milestone X. I see now that there is a new version of SuperOneClick ... anybody else trying to make this work, make sure you use v1.7.
So back to JDinAZ74's second question ... now that we've rooted are there custom roms for our CDMA version of this phone? I see tons of roms but none that I've noticed specify GSM or CDMA, which usually means it's GSM. Anybody know for sure?
the dx is on verizon, so its all cdma. i not sure it would matter though...
Yeah I'm not sure it matters either ... I know on my HTC Desire it mattered. If I flashed it with a GSM rom it would not boot.
Okay so somewhat unrelated ... i've got bootstrap installed and was able to do a rom backup via clockwork recovery. Is there a way to boot into recovery from the device being off? I tried every combination of buttons while pressing the on button but nothing works. I've looked all over the forum (and googled) but can't find anything.
I want to start installing custom roms but am affraid of something going wrong and me not being able to reflash my backup.
Then again maybe I'm just confused because I'm coming from a Desire which I've discovered Motorola and HTC modding differs significantly.
Im still looking for roms as well and kinda afraid to just start trying things like you said. If you come across anything that works let me know and ill do the same.
to get to stock recovery, hold power and home till the moto logo appears, then release the power button until you get an exclamation point, then let go and click the search button.
to get to cw recovery, do a battery pull and reboot.
if you completely **** your phone, sbf.
mattmartin77 said:
to get to stock recovery, hold power and home till the moto logo appears, then release the power button until you get an exclamation point, then let go and click the search button.
to get to cw recovery, do a battery pull and reboot.
if you completely **** your phone, sbf.
Click to expand...
Click to collapse
Wouldn't the SBf only work on a Droid x?
mattmartin77 said:
to get to stock recovery, hold power and home till the moto logo appears, then release the power button until you get an exclamation point, then let go and click the search button.
to get to cw recovery, do a battery pull and reboot.
if you completely **** your phone, sbf.
Click to expand...
Click to collapse
Fantastic! Thank you.
I don't know that they could do an sbf being on a non Verizon carrier. The sbf files out are all for Verizon. If you do screw up your phone you would have to take it into the store and have them sbf it. And they might not. I think you guys just need to be a little careful. Unless you can find an sbf file from your carrier. Try apex, rubix, or liberty roms for flashing. All the roms are cdma. Good luck and be careful.
Sent from my DROIDX using XDA App
The milestone x uses the same RSA key for its bootloader as the original Droid X. You CAN flash a Verizon SBF into it and it will work, HOWEVER, it will NO LONGER work with your carrier. It is also important to note that ANY SBF will overwrite the baseband AND the baseband configuration (unless specifically noted NOT to do so) rendering the phone useless, requiring re-programming, which for the voice part is no big deal, but to get EVDo working again you'll need to edit some non-user accessible parameters with QPST and what not to get it to connect back to the non verizon carrier.
What you CAN do with this phone is non-baseband patching updates/roms. If you've got a Milestone X you're not on verizon, so you're not able to use the leaked SBF's and what not, which removes a decent safety net. So flash with caution. If your carrier is small enough they are likely to re-sbf your phone for you if you brick it.
One last word of caution.. Verizon's DX on leaked GB's updates the BL to a newer version than is on the Milestone X. This will turn your phone into a Droid X, with no ability to go backwards until the same BL is available on the Milestone X.
In short, we non VZW DX owners have a lot less fun..
Bollocks to that.
really wish I knew if someone had tried, I really want to try that leaked gingerbread.
went ahead and took the plunge with... SUCCESS. I installed Liberty 2.0.1 and nothing went wrong, you just got to be more careful than others who have the sbf backup.
Went to ACS today because i'm considering this phone, ACS is partnering with Verison(GSM), and GCI is partnering with Sprint (CDMA).
Just incase it's not clear i'm sure roms for Verizon will work for ACS and roms for sprint should work with GCI.
Double check incase i have the two "bands mixed up" i know i have the carrier relationships right.
Does anyone know if we can overclock with out romming?
I tried droid overclock a few times which always sent the phone into a boot loop. Id have to pull the battery and do a factory reset to get it running again.
I tried to use the rooted 3.2.2 rom that was listed under development, but I could never get my wifi to connect. Now I am unable to get my 4G to work. I used to have the option to choose preferred network mode LTE/CDMA, but now that no longer shows. I am on 3.2.2 using build HLK42B.
I was wondering if someone who received their xoom back from the upgrade has the latest image I can try.
Tell me how to dump it. Never done it before. I am n stock 3.2.2 fresh back from the upgrade.
Sent from my Xoom using xda premium
I wish I knew.. I will have to research that.
Sent from my PG86100 using xda premium
I just posted an upload link over at http://forum.xda-developers.com/showpost.php?p=18204881&postcount=13
hammer4203 said:
Tell me how to dump it. Never done it before. I am n stock 3.2.2 fresh back from the upgrade.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
You need to flash the modded recovery, then in adb shell, run
mount /data
mkdir /data/media/Stock
dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/data/media/Stock/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/boot of=/data/media/Stock/boot.img
sync
Then reboot and pull the files, should be in a "Stock" folder on the internal storage.
*Thanks to solarnz for these instructions
Ok, I have pulled HLK75C images which should be flashable through fastboot thanks to short/y's Rogue CWM nandroid backup. Usual disclaimers apply here, don't try this unless you know what your doing, not my fault if something messes up. That being said, download images here: http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z zip password is "AceXMachine" without the quotes. After unpacking files go to the command prompt
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
It goes without saying that you need your xoom unlocked for this, need adb setup/working and may need to wipe data. I would do a nandroid backup of your current config before doing this. I was able to restore the "data" backup from a previous backup after restoring the "system" and "boot" from short/y's backup. Only problem I had was my market shortcut on the home screen had to be replaced since my "data" backup had the link to the older market. I rooted this before pulling these images so you should already have root when you flash this. I tested and have working WiFi and 4G with this setup. Feel free to ask questions or PM me if needed. Thanks again to short/y for his nandroid backup...even if he did make me load the Rogue recovery just so I could use it ;P
4G LTE
I got my Xoom back some time ago. I've been waiting to root it until it came back. (Really didn't want to go through it, and have to undo it just to figure out how to do it again)
I'm trying to find the official file from Moto for the HLK42B build that came back on my 4G Xoom. I'm on the Moto Dev site, but they only have up through the 3G upgrade listed. Anybody know where I can get the official file in case anything goes wrong? I want to make sure I have it, before I start.
Thanks
Thanks Ace, it worked for me. It wasn't rooted because I imediately got and updated to HLK57D
AceXMachine said:
Ok, I have pulled HLK75C images which should be flashable through fastboot thanks to short/y's Rogue CWM nandroid backup. Usual disclaimers apply here, don't try this unless you know what your doing, not my fault if something messes up. That being said, download images here: http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z zip password is "AceXMachine" without the quotes. After unpacking files go to the command prompt
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
It goes without saying that you need your xoom unlocked for this, need adb setup/working and may need to wipe data. I would do a nandroid backup of your current config before doing this. I was able to restore the "data" backup from a previous backup after restoring the "system" and "boot" from short/y's backup. Only problem I had was my market shortcut on the home screen had to be replaced since my "data" backup had the link to the older market. I rooted this before pulling these images so you should already have root when you flash this. I tested and have working WiFi and 4G with this setup. Feel free to ask questions or PM me if needed. Thanks again to short/y for his nandroid backup...even if he did make me load the Rogue recovery just so I could use it ;P
Click to expand...
Click to collapse
Thanks for the img files. They will save many headaches for a lot of people.
It is a damn shame that Motorola will not post the updated img files though...
I've tried both Ace and Shorty's backups. They seem to work restore fine but I still can't get any 3G/4G data. I've tried both HLK75C and D. I've done many factory resets and cache wipes. I had VZW send me a new SIM card which they manually activated while I was on the phone with them and according to their end they can see my Xoom contacting the tower but there is no activity beyond that. I really never believed that was the problem since I was able to swap SIMs with my Bionic and the Bionic worked great with the Xoom's SIM (but not the other way around of course).
I'm still suspicious about the radio Baseband version. I am missing the second "ltedc_u_05.19.00" that I've seen in HLK75C screen shots and I don't have the option to select a network mode under Mobile network settings that I know needs to be checked. This makes me think my Xoom's hardware is ok since it is able to talk with the tower over the 4G modem for activation, however the OS software is not able to select the 4G radio for actual system use. Are the radio files built into the system or boot images? Where do the baseband versions listed in About tablet come from and how might these be backed up/restored? I've never really bothered flashing radios before so this part of the process is new to me. I'm really hoping this can be solved without having to return the device to Moto.
zarkuu said:
I've tried both Ace and Shorty's backups. They seem to work restore fine but I still can't get any 3G/4G data. I've tried both HLK75C and D. I've done many factory resets and cache wipes. I had VZW send me a new SIM card which they manually activated while I was on the phone with them and according to their end they can see my Xoom contacting the tower but there is no activity beyond that. I really never believed that was the problem since I was able to swap SIMs with my Bionic and the Bionic worked great with the Xoom's SIM (but not the other way around of course).
I'm still suspicious about the radio Baseband version. I am missing the second "ltedc_u_05.19.00" that I've seen in HLK75C screen shots and I don't have the option to select a network mode under Mobile network settings that I know needs to be checked. This makes me think my Xoom's hardware is ok since it is able to talk with the tower over the 4G modem for activation, however the OS software is not able to select the 4G radio for actual system use. Are the radio files built into the system or boot images? Where do the baseband versions listed in About tablet come from and how might these be backed up/restored? I've never really bothered flashing radios before so this part of the process is new to me. I'm really hoping this can be solved without having to return the device to Moto.
Click to expand...
Click to collapse
This is my same exact problem. Can't seem to figure out the baseband problem.
I wonder if anyone has contacted Motorola regarding a way to flash the baseband to the LTE 4G version?
Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.
You can get the hlk75c which is rooted then take the hlk75d update and reroot using the universal root method. That will put you back.
Sent from my ADR6400L using xda premium
Jewremy said:
Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.
Click to expand...
Click to collapse
Oh, duh, it's so simple. I'll definitely be trying this when I get home from work today.
If it works - you will be my savior.
Scratch that - it didn't even reactivate my 3G.
Jewremy said:
Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.
Click to expand...
Click to collapse
I don't think that will work unless you open it up and physically remove the LTE modem. my understanding is once the LTE modem was installed the internal 3g modem is deactivated. Even if this did work it would deactivate your SIM card so you wouldn't be able to use LTE in the future without getting a new one. I had the idea to switch my currently useless Xoom data plan over to my old OG Droid and then wifi tether. I asked VZW about switching and found I *could* do this but going from a 4g device back to 3g would deactivate the SIM card and I won't be able to switch without getting a new one. Too much trouble in my opinion.
I spent about 2 hours in a Verizon store yesterday after 2 hours on the phone the previous night and eventually ended up with an RMA with Motorola. I'll be returning it to them and hopefully it will come back correct in about a week. Such a hassle when I could probably flash this myself if I had the right files but at this point I don't know what else to try.
Can you repost link please. I am trying to get this on a Mac running OSX and I cant seem to unzip the file. Any suggestions?! PLease HELP!!!
---------- Post added at 09:22 PM ---------- Previous post was at 09:09 PM ----------
how do you unzip HLK75Csystemboot.7z on Mac OSX??? Please Help!!!
download 7zip or use winrar
Jewremy said:
Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.
Click to expand...
Click to collapse
This does not work I've tried it a bunch of times in different fashions. I even flashed 3.2.2 then flashed the official recovery took the next update and nothing. Actually its been said that HRI66 over rights stuff that we need. Take that with a grain of salt.
zone23 said:
This does not work I've tried it a bunch of times in different fashions. I even flashed 3.2.2 then flashed the official recovery took the next update and nothing. Actually its been said that HRI66 over rights stuff that we need. Take that with a grain of salt.
Click to expand...
Click to collapse
Yeah, it does. The radios are in the bootloader, aka mmcblk1p1, aka the ebb partition.
Theoretically, we should be able to get a dump of the post-upgrade bootloader, dd it over our borked bootloaders and have it working. Problem is, getting that dump and figuring out how to do the flash. We definitely don't want to do it in a powered up system...that leaves recovery or fastboot.
Jewremy said:
Yeah, it does. The radios are in the bootloader, aka mmcblk1p1, aka the ebb partition.
Theoretically, we should be able to get a dump of the post-upgrade bootloader, dd it over our borked bootloaders and have it working. Problem is, getting that dump and figuring out how to do the flash. We definitely don't want to do it in a powered up system...that leaves recovery or fastboot.
Click to expand...
Click to collapse
It restores your device but it will not bring back 3G/4G. If it does please tell me how because I've flashed it a few times and it did not bring back 3G.
Actually in reading your post a few times you say it yourself that its a borked bootloader. Flashing HRI66 will not fix this. If it did we would be finished and we could close this thread.
Hi All,
My Bell Atrix was rooted but not BL unlocked when I finally got tired of the pop up message wanting to update to the latest firmware and decided to let it update. I had checked a while back and I thought people were having no problem updating even though rooted.
If I remove and replace the battery the phone will boot up completely but then immediately re-boots before I can do anything and on the reboot it goes to the Failed to boot 2, Starting RSD mode screen and stays there.
Because this phone was not unlocked I'm not sure how to proceed. Can I use RSD lite to recover and if so, what files should I be looking to write.
I don't mind ending up with a BL unlocked phone as I had been intending to do that eventually, but just hadn't gotten around to it yet.
As far as what version I was at, the phone took a big update a month or two ago, and after a while wanted to do another update (teh latest I assume). I had downloaded it (wasn't very big) and was only getting around to letting it install now when this happened.
Please, need some help quick here!
Regarding what rev I was at, I believe I was at 4.5.91 updating to 4.5.141...if this make sense for Bell.
Hi Again,
From further reading, I believe I was trying to update to this:
System Version
45.21.MB860.BellMobility.en.ca
(previous: 45.2.17.MB860.BellMobility.en.ca)
Android version
2.3.6
(previous: 2.3.4)
Webtop Version
WT-1.2.0-167-BELL
(previous: WT-1.2.0-135_BELL)
Kernel version
2.6.32.9
[email protected] #2
(previous: 2.6.32.9-00002-gd5bf03a
[email protected] #2)
Build number
4.5.2A-51_OLL-17.8
(previous:4.5.2A-51_OLL-17)
Sorry for the confusion, but I obviously can't use phone to see where I was at and where I was going. Basically, it was the latest Bell update excluding ICS, supposively that is available now?
Surely someone can toss me a bone on this one?
Got the same issue but used rsd lite and working now ..
http://forum.xda-developers.com/showthread.php?t=1490283
This link is for AT&T is it not? I think I need a specific file to load with RSD or fastboot to fix the softbrick created when OTA ing from Bell 234 to 236.
I assume you were AT&T bobby2nag?
Try this http://forum.xda-developers.com/showthread.php?t=1302423
Sent from my MB860 using Tapatalk
I am on the same boat, i am on AT&T i was rooted, and i hit the update button =(
Got it to work thank to you ! =)
Followed this up until proper recovery section which i did not have to do.
This worked for me also. Seemed just the process of unlocking the bootloader fixed things. I needed to unlock anyway, so that was good, however I believe the more appropriate fix would have been this:
http://forum.xda-developers.com/showthread.php?t=1501454
All good in the end! Thanks much!
Telcel MEXICO
Hi i was so stupid i didnt make a backup, i rooted my phone then from ROM Manager i tried to install ClockWor*#*$$# and then when it was finished the phone restarted and FAILED TO BOOT 2 and now i dunno what to do, like i said im from mexico telcel
Quinton99 said:
This link is for AT&T is it not? I think I need a specific file to load with RSD or fastboot to fix the softbrick created when OTA ing from Bell 234 to 236.
I assume you were AT&T bobby2nag?
Click to expand...
Click to collapse
Yes mine is at&t .
Finally yours Atrix is back .
Telco Mexico - clearing the caches might help, up to you to decide
Have a look here: http://forum.xda-developers.com/showthread.php?t=1501454
You never said if you were in a boot loop or not, upon battery pull/insert does it boot up and then reboot immediately and bring you to Failed to boot 2? If so, I would try the caches myselp, JMHO!
I didn't see any threads that referred to (quite) the dilemma I have, so forgive me if starting a new thread was unnecessary... So, I have a Razr M, 4.1.1, I rooted it when I first got it, using motofail2go, which added SuperSU. Recently, an OTA update became available, and installing it would fail every time due to being rooted. (at least that is my understanding.) So, I un-rooted from within SuperSU, and still no luck. I then got the stock fastboot files for 4.1.1, and downloaded RSD 6.1.4. I already had the USB drivers installed, and I have ADB installed too. I powered the phone up into fastboot, connected the USB cable, selected (within RSD lite) the fastboot file on my laptop's hdd, and it flashed it, and rebooted the phone, and said it was successful. heres the weird part: Everything I installed is still on the phone, every app, every setting, it's like nothing happened. BUT... the OTA update worked this time! So, am I using RSD lite incorrectly? Is it because my bootloader is still locked? (I didnt think you needed root access OR an unlocked b/l to flash stuff over fastboot, but I could very well be wrong) Or lastly, is that what is supposed to happen? Sorry for rambling, and sorry if any of this is stupid, i'm just really confused
update
I didn't even see this until now, but everything that I have installed since new remained on the phone, as I mentioned, but it also reinstalled everything I had deleted from it (Zappos app, NFL app, other bloatware). So I guess it DID work, but apparently I need to do a data wipe before flashing the stock fastboot files?
internickcg said:
I didn't even see this until now, but everything that I have installed since new remained on the phone, as I mentioned, but it also reinstalled everything I had deleted from it (Zappos app, NFL app, other bloatware). So I guess it DID work, but apparently I need to do a data wipe before flashing the stock fastboot files?
Click to expand...
Click to collapse
Yeah, generally, you want to do a full wipe and FDR, prior to fastbooting. However, it sounds like it worked, since you have all the old crap in there. Now, unlock that thing and start flashing away.
Don't think rsd touches /data so that's why it kept your stuff
Sent from my Nexus 7 using Tapatalk HD
internickcg said:
I didn't see any threads that referred to (quite) the dilemma I have, so forgive me if starting a new thread was unnecessary... So, I have a Razr M, 4.1.1, I rooted it when I first got it, using motofail2go, which added SuperSU. Recently, an OTA update became available, and installing it would fail every time due to being rooted. (at least that is my understanding.) So, I un-rooted from within SuperSU, and still no luck. I then got the stock fastboot files for 4.1.1, and downloaded RSD 6.1.4. I already had the USB drivers installed, and I have ADB installed too. I powered the phone up into fastboot, connected the USB cable, selected (within RSD lite) the fastboot file on my laptop's hdd, and it flashed it, and rebooted the phone, and said it was successful. heres the weird part: Everything I installed is still on the phone, every app, every setting, it's like nothing happened. BUT... the OTA update worked this time! So, am I using RSD lite incorrectly? Is it because my bootloader is still locked? (I didnt think you needed root access OR an unlocked b/l to flash stuff over fastboot, but I could very well be wrong) Or lastly, is that what is supposed to happen? Sorry for rambling, and sorry if any of this is stupid, i'm just really confused
Click to expand...
Click to collapse
can u plz tell me that can i flash tose fastboot files on my razer xt905 rooted bootloader locked running 4.0.4 but the main thing is that mine is a korean version SK TELECOM and these files must be for the verizon soooo not sure to flash or not
taha mustafa said:
can u plz tell me that can i flash tose fastboot files on my razer xt905 rooted bootloader locked running 4.0.4 but the main thing is that mine is a korean version SK TELECOM and these files must be for the verizon soooo not sure to flash or not
Click to expand...
Click to collapse
SBF has all the stock firmware FXZ files. There is a file for the XT905, but it says it's for Australia. I'm not sure if that will work for you. Scroll down until you see your device, download the file, then flash in RSD.
http://sbf.droid-developers.org/
RikRong said:
SBF has all the stock firmware FXZ files. There is a file for the XT905, but it says it's for Australia. I'm not sure if that will work for you. Scroll down until you see your device, download the file, then flash in RSD.
thanks for the reply buddy but flashing a non sktelecom rom to mine would really make a difference i mean if it adds bloatware it dosent matter ????
Click to expand...
Click to collapse
Just use matts utility it will bring you back to like new stock
Sent from my XT907 using Tapatalk 2
I have had my Maxx HD since launch and unlocked very soon after it became available,
Recently I downgraded from the last OTA with matgroffs 1.21 utility and enjoyed a wonderful clean slate experience but after a while (today) I went for the OTA to get prepared for KK coming soon hopefully, the install failed entirely and my bootloader is now back in a locked state the phone is stuck in fastboot and will not take a flash from any utility on here, 1.21, 1.3x 2.0 ext including rsd lite.(RSD will not even detect the phone)
Ive tried the utilities on Mac and Windows 7, nothing has worked so I broke down and called verizon and ordered a recertified razr HD for a discounted price.
So just a warning there is a way the bootloader can get relocked. will take a picture and load soon to show the screen of the phone incase someone can help. Just a side note my vibrate motor failed and I have been having 4g radio problems before I went back on matgroffs utility.
You tried house of moto to fastboot flash 98.30.1? Sux they found a way to relock them...
Sent from my XT907 using Tapatalk
This only shows up when you get the GPT error. It will still be unlocked once you get this restored. This came up when the OTA was released. A few people with unlocked BL had this GPT error. There's a fix somewhere around here, just search for the error.
RikRong said:
This only shows up when you get the GPT error. It will still be unlocked once you get this restored. This came up when the OTA was released. A few people with unlocked BL had this GPT error. There's a fix somewhere around here, just search for the error.
Click to expand...
Click to collapse
@AndroidGreg
There's a line in the fastboot xml file with gpt_main0.bin (somithing really similar to that, been a while since I flashed it...) and all that's necessary is removing that line and flashing the fastboot with rsd, or just manually flash the fastboot skipping that partition, either or will work and fix the problem. Even though the bootloader is unlocked, that particular partition IS still controlled by securtiy and is blocked from downgrading -- luckily for us the partition table never changed between rom versions so it's perfectly safe to flash or not to flash it.
I've never flashed with RSD, but IIRC, there's also two more lines in the fastboot's xml that need to be removed for it to properly flash. I've only flashed my phone with moto-fastboot from linux and used MythTools from windows -- MythTools is an interactive script for the Atrix HD to flash stock fastboots, root, unlock the bootloader, flash a custom recovery, boot logos, and soon different radios -- Similar to Mattlgroff's tool.
The Atrix HD has the exact same issue with that partition.
download the sbf file from http://sbf.droid-developers.org/phone.php?device=5
install these drivers https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481/action/auth
connect the phone in fastboot mode.
now extract the "fastboot_rsd.zip " to a folder.
extract the contents of the downloaded sbf/xml file into the fastboot_rsd.zip folder
execute "flash_fastboot_erase_userdata"
worth a shot.
always works for me..
good luck.
RSD does not detect the phone at all, only the quick utilities did and they failed. Verizon overnighted my new phone and its here already, not unlockable im just gona root and keep it for a while till I switch to strait talk with the nexus 5, I cant afford $100 a month anymore anyway.
First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
If not possible, hopefully someone will build a flashable version of the OTA KK update when it FINALLY arrives. I'm way too unstock for the update to work OTA, that's a fact.
LifeAsADroid said:
First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
If not possible, hopefully someone will build a flashable version of the OTA KK update when it FINALLY arrives. I'm way too unstock for the update to work OTA, that's a fact.
Click to expand...
Click to collapse
It only shows that his BL is locked because of the GPT error. I can assure you it is still unlocked. Many, many people updated and we still have unlocked BLs. Heck, I've flashed the latest OTA on my M and HD with RSD and am still good. He just needs to fix the error, but he have up and got another phone.
RikRong said:
It only shows that his BL is locked because of the GPT error. I can assure you it is still unlocked. Many, many people updated and we still have unlocked BLs. Heck, I've flashed the latest OTA on my M and HD with RSD and am still good. He just needs to fix the error, but he have up and got another phone.
Click to expand...
Click to collapse
Exactly. The Atrix HD gives us this error if we flashed the stock Mexican firmware (our latest) and try to flash anything below it, or the Bell firmware (2nd newest) and anything below that, and so on and so forth. All that's necessary is to remove the gpt flashing line and go again....just like we have to remove the oem lines from the fastboot xml.
First time I had that error, I went WTF (the first flash after unlocking my bootloader if ya'll's curious), knew that GPT is a partition table from grub experience, figured that the partition table has never changed since stock ICS roms, removed the GPT line, flashed ICS, and I was happy.
I'd love to be able to combine all the data, system, cache, and any other partition that don't need a fixed place (like modem, etc) and be able to use ZFS or BTRFS volumes to maximize the amount of storage we can have -- I've always wondered why they don't do something like that already...
Ok 3 computers 1 xp and 2 windows 7, nothing, mac nothing, even made a factory cable because the battery just got to low, nothing, no computer will detect it, using any of the 3 motorola branded usb cables plugged directly into the laptops. Now the utilities from matgroff and the other guy (cant think of his name but he made the 2.0 utility) will not even try to flash the phone they say please plug a phone in that is in fastboot mode, I
Serious question, but have you tried Linux? My old Bravo wasn't detected by Windows (XP or 7, been 2 years now) after a bad RSD flash, but I was able to manually flash it from Linux (either Manjaro or Debian Testing). After that, to this day it'll flash with RSD, but it isn't detected properly. I still flash it, and almost everything else, from Linux because I don't trust flashing from Windows anymore. I made an exception recently to help with a tool and because my Linux partition was down for a month.
LifeAsADroid said:
First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
Click to expand...
Click to collapse
I tried doing the exact same thing as the OP - factory reset to "stock" and then flash back up in preparation for KK, after using TiBu to save everything and using SafeStrap to make a Nandroid (very thankful I did). I ended up with the identical screen that the OP had, even stating that my previously unlocked BL had been apparently "relocked." For me, RSD Lite did recognize my phone (I updated RSD to the latest version beforehand), however it would not flash anything for me (the flashing process would start and then immediately say "failed").
See my post for the details and the solution I used: http://forum.xda-developers.com/showthread.php?t=2674431.
I was completely freaked out for a couple of hours until I stumbled upon bweN diorD's GPT partition fix. And then everything was fine for me.
Hope this helps anyone who falls into the same trap.
AndroidGreg said:
I have had my Maxx HD since launch and unlocked very soon after it became available,
Recently I downgraded from the last OTA with matgroffs 1.21 utility and enjoyed a wonderful clean slate experience but after a while (today) I went for the OTA to get prepared for KK coming soon hopefully, the install failed entirely and my bootloader is now back in a locked state the phone is stuck in fastboot and will not take a flash from any utility on here, 1.21, 1.3x 2.0 ext including rsd lite.(RSD will not even detect the phone)
Ive tried the utilities on Mac and Windows 7, nothing has worked so I broke down and called verizon and ordered a recertified razr HD for a discounted price.
So just a warning there is a way the bootloader can get relocked. will take a picture and load soon to show the screen of the phone incase someone can help. Just a side note my vibrate motor failed and I have been having 4g radio problems before I went back on matgroffs utility.
Click to expand...
Click to collapse
I had this same problem when i tried to go back to stock a while back. You need to flash the gpt_main0.bin file to fix it. Here are the steps I used to fix the problem: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Another user took my steps and edited a script so give this a shot if you want to run something thats automatic: http://forum.xda-developers.com/showpost.php?p=48587194&postcount=89
scoobaspeaz said:
I had this same problem when i tried to go back to stock a while back. You need to flash the gpt_main0.bin file to fix it. Here are the steps I used to fix the problem: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Another user took my steps and edited a script so give this a shot if you want to run something thats automatic: http://forum.xda-developers.com/showpost.php?p=48587194&postcount=89
Click to expand...
Click to collapse
@AndroidGreg, do you still have the phone?
Sent from my DROID RAZR HD using Xparent BlueTapatalk 2