[Q] Failed to boot 2, Starting RSD mode - Atrix 4G General

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!

Related

[Q] Milestone 2 in bootloop

Hey all there,
i just bought for some cheap money a milestone 2 on the bay with bootloop problems.
it startsup like this:
just power on with the power button:
red m logo, after some seconds it turns for about a half second to a black screen, again red m logo, and again and again and again
enter the bootloader works fine - 70.13
enter the system recovery works on charger, wiping out didn't help
flashing with rsd lite worked, but didn't change the situation with the bootloop. even after flashing, and wipe out after that.
i'm using windows 7 32bit and x64 on another computer in combination with rsd-lite 5.6
with rsd-lite 4.9 or earlier my device isn't recognized. admin and compitibility is on at all versions of rsd-lite.
anone an idea how to get this stone working again?
i'm a little confused, cause i saw so many posts, of people getting the stone back after flashing with rsd...hmm any help is pleased
greetz
Download rom GingerBread of UK
http://www.multiupload.com/TUZHXCGLMZ
Flash with RSD Lite 5.6... reboot
make wipes (POWER and X....... Vol + and Vol -)... reboot
has to boot normally ...
Just tried several versions of firmware. nothing did work.
i'm thinking about getting the 70.13 bootloader file and flash the bootloader once more.
or give it a try and flash the phone with an update.zip over recovery mode.
but first problem is: i don't have the booloader and the only mirror was megaload, at second i don't have any oem update.zip files. well i will look forward. can't understand why the phone is still looping.
would be happy about any other good suggestions.
greetz
Bootloader 70.13
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
MKSilver said:
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
Click to expand...
Click to collapse
Don't use a 2 ou 2.2 android..I think it's on GB so you can't downgrade..
Charge your battery to 100%
Folow the step here with a 2.3.4 SBF take here
Have a nice day.
Hey all there,
i already tried to flash GB 2.3.4 Firmware for: Germany, DACH, UK - didn't work out.
of course i did a wipe after installing.
also i tried a rebuilt by renaming CG66.img into CG37img - didn't work out.
just saw, that when i rebuilt the firmware after changing cg66.img to cg37.img, the cg37.img file doesn't appear in the new built SBF.
any reason for that? hmm...
while depacking and rebuilt a SBF i saw, that the RAMDLD.img (ramdownloader) in the 2.3.4 GB DE retail SBF is in version 70.12. i'm no expert in built SBF files, just did this the first time, but could this have an incompatibility with the 70.13 bootloader?
well cause the phone was quite cheap, i will go on trying. may be some more of you guys have any ideas.
the standing now is:
reflash 70.13 bootloader - didn't work out,
flash any 2.3.4 GB SBF and wiping out data after flash - didn't work out
flash update.zip from recovery mode - haven't tried yet - need update.zip file or instruction how to built one.
the last point is my next step i think. i will now go reading how to get this manage.
any help is welcome!
greetz
Okay just learned, that flashing an update.zip with system recovery, doesn't erase any data on the phone, so will look forward, trying flash the phone with sbf under linux live cd.
may be this will help.
does anyone of you know some hardware testing tools for the milestone 2?
to test the ram/rom hardware...
i'm starting to think, that some of the hardware chips may be damaged.
hmm i always thought, that it is not possible to brick a stone with original bootloader/rom-image/firmware. just starting to learn, that it is possible although.
any help is welcome guys! my ideas are going to end.
greetz
Got still no luck and tried to flash it with sfb about 16 times now. RSD-Lite tells me it was everything okay, but still bootloop.
Any good ideas?
Greetz
You have no real idea of the phones history, so you may have to accept the possibilty that it could be a hardware issue. Perhaps it has taken some water damage (the indicators do not always end up going off btw - I fell into a pool fully clothed and the nokia i had at the time wouldn't ever recognize a sim again, yet no water damage indicators get wet somehow . Yet the rest was soaking)
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
A thought occurs.... does it actually have a sim card slot? Like... is it possibly a Droid 2? :S
---------- Post added at 10:25 AM ---------- Previous post was at 10:20 AM ----------
Mikevhl said:
I know it's a bit extreme to do, but it might help for you. Try installing ubuntu or wubi, then use sbf_flash on ubuntu. It takes some time, but if you REALLY need to SBF you should give it a try. Usage is:
chmod 777 sbf_flash
./sbf_flash /path/to/sbf/file
Click to expand...
Click to collapse
Got that from the recovery thread.
I dug up this guide to using ubuntu live cd to flash sbf's for the droid 2, hopefully you are switched on enough to workout what you need to do differently for the MS2
http://forum.xda-developers.com/showthread.php?t=804088
I'd try that and see what happen
Hey guys,
first: thx to DreadPirateDan. you're right, i don't know enough about the phone. So i sat down after work and startet to read and with all the basic information i know about the phone. While analysing all the things i just saw a special thing in the bootloader:
When the phone is switched on into bootloader, the screen shows:
"Bootloader Fastboot mode
70.13
Battery OK
OK to Program
Transfer Mode:
USB"
So it seems that i've got the fastboot script active. So i should do everything with the phone i want to do, right?
i will go on reading. maybe i will find any way to check all the files.
Is it possible, that the phone loops because of fastboot mode and a secret saftyissue which bans all phones booting with active fastboot?
May any of u check on a not rooted and for difference rooted milestone 2, if the fastboot notify is standard?
Btw - got a Sim-Slot, so it seems to be a Milestone 2.
greetz
This ones a long shot - but if you have another USB cable available, try using that. Perhaps the one you are using is somewhat damaged - not enough to cause errors flashing, but enough to corrupt data? I don't know but i'd certainly give it a try! .
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
Yeah that's the screen of bootloader saying it's all sweet to flash with rsd-lite
So that's a good sign
I'm concerned perhaps it's had some physical damage to the system storage.
I'm just confused, your steps appear to be all correct, what you've done allready, and it should have worked allready!
How did u get into Bootloader Fastboot mode???
Are you sure it says 'Fastboot' coz Fastboot could mean unlockable bootloader?
May be some developer could throw some more light on this.
When we first got the Chinese GB link I remember there were a couple of guys who had deceloper phones.. They never explained how they'd got them though lol
Sent from my MotoA953 using xda premium
Fastboot confirmed
Hey Guys,
well its definitly Fastboot. I installed Android SDK yesterday and tested a little bit.
I can flash images through fastboot and all those things.
Poblem is, i'm not so familiar with all those things. I know a little bit of electronics but not so much about how software and specially android works with the hardware. Just started yesterday to read about this.
Attached are some pics of my phone during bootloader and how it looks.
Now it would be first nice, to get this thing work!
Because at the moment it hangs still during booting, cause i don't know so much about how to flash from fastboot.
When it is true, that this could help this forum here, i won't sell it anymore. But i need help to work all this out.
I contated parallely the customer service of motorola at my country, to ask, if this device has still waranty via IMEI, but they don't have this IMEI in their database.
So come on guys, more information, how get the phone work again, may be with any rom we wish someday without hacking anything
greetz
I have the same problem. tried to bootstrap after ive installed cyanogen 7 and now im stuck on the M logo. wiping cache or factory reset won't work
thing is the links for sbf files at and-developers won't work :\ so now i cant flash anything
plz help
Alot of file sharing stuff got shut down just recently that's why all the links are dead
if you had previously upgraded to gingerbread, that is your problem - cm7 doesn't work with it. Have a crack at the dowgrade method endless7 has and then you can flash cm7 with CWM.
ok, i figured it out. just searched google for one of the builds. flashed it and it turned out to be a french retail version of froyo. installed MIUI rom. works fine
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Nikunj3xP said:
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Click to expand...
Click to collapse
hi,
Can you please explain clearly if you are able to boot CWM recovery or are you just getting a boot loop and unable to boot to recovery? As far as I know you won't be able to flash clockwork mod recovery for the Milestone 2 using ROMManager .You need to use Droid 2 bootstrap recovery.

[Q] Flashing stock 4.1.1 with RSD Lite

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

[Q] defy cant get to any bootloader at all

first off im not a noob at this kinda stuff ive rooted tablets and other phones before. so ive spent the past week or so every night for hrs searching around for an answer to my problems.
phone info
carrier:Straight Talk
MN: XT555C
AV:2.3.7
Base band vr: PCR
Kernel vr:Apps_2.6.38.6-perf
Build number:1_67D_1014
OK on to the proses i used:
first rooted phone with VROOT
pic 1(the pic with the Foreign letters)
gained root
pic2 (pic with root checker)
easy enough right
then tried 2int every vr of it witch said they installed just fine
but every time i would try to go in into the boot-loader nothing no blue light no auto boot loader screen just nothing.
so i searched for different kinda boot loaders witch lead me to twrp and only like two more
nothing couldn't get any of them to work on account of the fact that they needed a Boot-loader to install them.
then i decided i would try rsd lite
downloaded sbfs
http://sbf.droid-developers.org/umts_jordan/list.php
ive tried the first and last one not sure witch one is for my phone
when i hit VOL+ power i get this screen:
pic 3(white screen with blue letters)
and rsd reconised the phone but phone info came up mostly as
N/A and nothing would flash just kept giving me
error:failed flashing process. failed flashing process phone 0000 error sending ram to bootloader
then when i had the phone try to just boot normaly with rsd open i got this screen:
pic 4(black screen with white letters)
all things aside i have gained root but to no avail can i get a Boot-Loader to work. im just looking for some one to help shed some light on this matter and help me get off of Ginger Bread
jimbob60 said:
sorry about pic i cant post them
they are on my fb my only public album
my fackbook url:
/jacob.g.shaffer
first off im not a noob at this kinda stuff ive rooted tablets and other phones before. so ive spent the past week or so every night for hrs searching around for an answer to my problems.
phone info
carrier:Straight Talk
MN: XT555C
AV:2.3.7
Base band vr: PCR
Kernel vr:Apps_2.6.38.6-perf
Build number:1_67D_1014
OK on to the proses i used:
first rooted phone with VROOT
pic 1(the pic with the Foreign letters)
gained root
pic2 (pic with root checker)
easy enough right
then tried 2int every vr of it witch said they installed just fine
but every time i would try to go in into the boot-loader nothing no blue light no auto boot loader screen just nothing.
so i searched for different kinda boot loaders witch lead me to twrp and only like two more
nothing couldn't get any of them to work on account of the fact that they needed a Boot-loader to install them.
then i decided i would try rsd lite
downloaded sbfs
when i hit VOL+ power i get this screen:
pic 3(white screen with blue letters)
and rsd reconised the phone but phone info came up mostly as
N/A and nothing would flash just kept giving me
error:failed flashing process. failed flashing process phone 0000 error sending ram
then when i had the phone try to just boot normaly with rsd open i got this screen:
pic 4(black screen with white letters)
all things aside i have gained root but to no avail can i get a Boot-Loader to work. im just looking for some one to help shed some light on this matter and help me get off of Ginger Bread
Click to expand...
Click to collapse
Have you tried this: http://forum.xda-developers.com/showthread.php?t=1743764
It worked for me.
i have now tried that and it was useful as far as the commands in the bat file but still nothing i did worked
i unrooted it the wipe cash and factory restore the Zerg Exploit did not work it would not root it so i used the commands to install bootloader it worked with no errors my led turned green to show success but still no blue light or Boot-loader. even when i use
E:\android\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
$ su
su
# reboot boot-loader
reboot boot-loader
it just reboots normally
any one else have some info?
so i still cant get a bootloader to come up ive been at this for a while and am still stumped i gain root and su but no custom boot loader just the stock one.
Root, install 2ndinit, install CM10, install CM10.2, install update-recovery.zip, REBOOT (without any wipe), install CM11 and GApps.
^
so this is just so people can see where im at in the chain of things here. im at the install 2ndinit
nother update so i desided i needed to push the files from bootmenu.tar.gz onto my system and see if it changed anything(also did the same for twrp and a few vrs of other bootloaders)
so i went and got http://forum.xda-developers.com/showthread.php?t=1687590
witch worked well and after i used the program to send the files where they need to be and tryed to reboot into bootmenu the phone still just restarted normally.so now the files are where they need to be adn it should let me into the bootloader but no im at a loss i dont understand how sompthing so simple could turn out to be like this. every one else can get it and ive followed like every set of direction i could find on this site over and over agen then i started experimenting with it and still nothing no matter how the files get there still no bootloader all i want is to be able to install JB and get the hell off of GB. and its not like im getting any help from this post i hope a dev can come by here soon and help me shed some light on things. untill then ill keep updating the post
jimbob60 said:
nother update so i desided i needed to push the files from bootmenu.tar.gz onto my system and see if it changed anything(also did the same for twrp and a few vrs of other bootloaders)
so i went and got http://forum.xda-developers.com/showthread.php?t=1687590
witch worked well and after i used the program to send the files where they need to be and tryed to reboot into bootmenu the phone still just restarted normally.so now the files are where they need to be adn it should let me into the bootloader but no im at a loss i dont understand how sompthing so simple could turn out to be like this. every one else can get it and ive followed like every set of direction i could find on this site over and over agen then i started experimenting with it and still nothing no matter how the files get there still no bootloader all i want is to be able to install JB and get the hell off of GB. and its not like im getting any help from this post i hope a dev can come by here soon and help me shed some light on things. untill then ill keep updating the post
Click to expand...
Click to collapse
I don't think the XT555c has a JB or even a ICS ROM. You can debloat GB and stay on it.
Sent from my Nexus 7 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2392187
http://forum.xda-developers.com/showthread.php?t=1216982
http://forum.xda-developers.com/showthread.php?t=1768702
http://forum.xda-developers.com/showthread.php?t=1032212
ive read thru a few threads other than those also and other people with the same mn and build have done it......
thats from my understanding that they wer able to get a boot-loader to work witch i can not get into a bootloader at all.and RSD wont flash anything to the phone evern tho ive used diffrent vr of rsd and the moto drivers.
so am i to assume that it just cant b done? that i could understand but other people with this phone/67d have done it and ive sent them pms but no reply same with some of the devs here who have helped others get this phone going so i guess im at a loss with this straight talk phone at least with installing a custom boot-loader/ROM.at least the phone works.....just outdated.screw you motorola
just a reply
@jimbob it my feelings that the "USA Moto defy xt555c, Straighttalk" does not have a blue LED built in. There is no evidence of it other than i have never seen one during the last year or so of having the phone (yes i do a lot of bluetooth stuff). Also to shed some light on your situation it is my understanding that 67d firmware has patched an exploit with the older bootloader and now has been upgraded to bl7. if this is your bl ver number then it is slim you will find the answer to your problems here. the only option i can come up with is to get or make fixed sbf for the device and flash/ downgrade. fixing the sbf only lies to the phone and tells it you have a higher ver android than you really do.... go figure motorola would be good at burning bridges! LMAO
thanks for replying. not to sure how to make a fixed sbf and the ones i found would not work because i couldn't get the program to flash anything to the phone. but then agen i never made a custom one

[Q] Bricked? RSDLite won't work

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.

Just a warning

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

Categories

Resources