[Q] Fastboot on power-up - Motorola Atrix HD

Apologies if this has been answered before, I searched the other threads and it seems so one has my exact same problem. I bought an Atrix HD from a local seller, unaware of this little problem that it boots into fastboot mode after powering down and back up. (seems he had been tinkering around with it with no success) I found out I could do the pwr+vol.up+vol.dwn trick, causing it to go to the boot menu screen and then booting up normally. I figured I could live with that small annoyance.
But after doing more research I found out that this AHD had been updated with the most recent OTA that irreversibly locks the bootloader and disables any possible rooting. I just dont want to keep this phone anymore if Im going to be stuck on stock JB ROM, and no flashing capabilities. And I really want to have that HDMI overscan option that apparently was in ICS and they took it away. (I know, stupid me for not researching this before buying). I just want to be able to sell this phone WITHOUT having to warn the buyer of this fastboot problem, which I think would really decrease the value of the phone.
Any ideas of a method to fix this?

Have you tried the Myth Tools?

moebius_2033 said:
Have you tried the Myth Tools?
Click to expand...
Click to collapse
I had checked that out, and noticed it uses motochopper and motopocalypse for rooting and unlocking bootloader. I had already tried those methods with no success, and figured it was because of the July OTA locking it all up. But I got a private message from a member who said he was in my same situation and able to flash a ROM back with myth tools. So maybe I just wasnt doing it right. I'll try again, paying attention to detail...

Update: still no joy. Installed JDK and the adb-fastboot-apk I cant root or unlock BL with myth tools. It just hangs. Even tried just flashing a couple ROM's listed in the myth tools instructions thread, because hey, what could it hurt now? No success, just kind of formats my phone but still the same version.
If it's of any use, system version is: 98.4.20.MB886.ATT.en.US
build number: 9.8.0Q-97_MB886_FFW-20

Are you sure the bootloader was unlocked. Once unlocked, it can't be relocked.

have you tried flashing Mex retail using rsd lite to downgrade a version

I didn't know the atrix got an update. I thought it was only for the razr. To fix that issue re flash the boot image.
Sent from my PACMAN MATRIX HD MAXX

Checkout my post on this thread. Just skip making a backup.
http://forum.xda-developers.com/showthread.php?t=2394238
PM me and click Thanks if I helped.
Sent from my Atrix HD

Ya need to restore using rsd lite

Related

[SBF] Gingerbread - 4.5.91 with Unlocked Bootloader US AT&T Only

Here is a link to the latest US AT&T 4.5.91 sbf with the unlocked bootloader and /preinstall root added.
Warning!
Use this with caution, and don't downgrade to 1.26, 1.5.7, or 1.8.3 unless it has the unlocked bootloader properly integrated into the sbf, and you have already used fastboot to unlock. In general I don't recommend downgrading at all.
If you already installed the official sbf without modification or updated to OTA without unlock, and not unlocked, then I recommend waiting and not installing anything from anyone for now.
We do have reports of hard bricks. We don't yet understand why only a few people have hard bricked. You are doing this at your own risk.
Download:
4.5.91 sbf with unlocked bootloader and /preinstall root
Thanks the2dcour!
Thanks is awasome
Nice. Is this safe? This is the official GB AT&T update with unlocked boot-loader correct? Can you use the preinstall method to root afterwards?
Has anyone used this over Gingerblur?
Great, what's the difference between this and another sbf posted today itself. Looks like both are same.
Sent from my MB860 using XDA Premium App
Did someone already tested this?
Sent from my MB860 using XDA App
Noob question... can I update this over the OTA that was leaked by Sam? Since his wasn't unlocked..?
anupash said:
Did someone already tested this?
Click to expand...
Click to collapse
This was tested before release on two phones.
ceo.mtcl said:
Great, what's the difference between this and another sbf posted today itself. Looks like both are same.
Click to expand...
Click to collapse
This is the same sbf, but with the unlocked bootloader added.
n0kia916 said:
Noob question... can I update this over the OTA that was leaked by Sam? Since his wasn't unlocked..?
Click to expand...
Click to collapse
I'd also be interested to know whether this is a possibility.
Even better, can you update over the OTA version that I flashed using the Motorola Update Service???
n0kia916 said:
Noob question... can I update this over the OTA that was leaked by Sam? Since his wasn't unlocked..?
Click to expand...
Click to collapse
If you already installed OTA without an unlock. Then you have the fuse burned that prevents you from downgrading to the official 1.8.3 sbf. If you do, you will brick your phone.
This sbf should work over the OTA. Think of it like a full reinstall of Windows, but in this case it is Android. To extend the metaphor further, this sbf is like having SP1 slipstreamed in, in that it has the unlocked bootloader integrated.
gogorman said:
I'd also be interested to know whether this is a possibility.
Even better, can you update over the OTA version that I flashed using the Motorola Update Service???
Click to expand...
Click to collapse
As I said in the post above, yes.
Isn't there a rooted version of this on the pudding page? or is it different
I updated over the OTA 2.3.4 by Samcripp but..
edgan said:
If you already installed OTA without an unlock. Then you have the fuse burned that prevents you from downgrading to the official 1.8.3 sbf. If you do, you will brick your phone.
This sbf should work over the OTA. Think of it like a full reinstall of Windows, but in this case it is Android. To extend the metaphor further, this sbf is like having SP1 slipstreamed in, in that it has the unlocked bootloader integrated.
Click to expand...
Click to collapse
So I decided to try and use RSD Lite 5.0 to update with the sbf posted from edgan. Previous version I had was the OTA update that was posted by Sammcripp but I wanted an unlocked bootloader. While waiting for the rsd to finish it failed at 99 percent when the phone rebooted and got an error 0x1000.. at this point I was ****ting myself..wtf! So it automatically went to fastboot mode and nothing else.. not even volume down menu.
To resolve this issue.. I did a fastboot oem unlock (your UID #)
then did a fastboot reboot and first it was stuck at the dual core screen. I rebooted again and did the volume down~ approach and was able to get into Recovery mode then allowed me to wipe data / cache and restore to factory defaults... bam phone booted up fine with unlocked message and able to use my phone again.. thanks Edgan! lol sorry if It's hard to understand me..
Also just ran quadrant and comparing to the leak 2.3.4 by samcripp this one gives me 300 more points consistently....
n0kia916 said:
So I decided to try and use RSD Lite 5.0 to update with the sbf posted from edgan. Previous version I had was the OTA update that was posted by Sammcripp but I wanted an unlocked bootloader. While waiting for the rsd to finish it failed at 99 percent when the phone rebooted and got an error 0x1000.. at this point I was ****ting myself..wtf! So it automatically went to fastboot mode and nothing else.. not even volume down menu.
To resolve this issue.. I did a fastboot oem unlock (your UID #)
then did a fastboot reboot and first it was stuck at the dual core screen. I rebooted again and did the volume down~ approach and was able to get into Recovery mode then allowed me to wipe data / cache and restore to factory defaults... bam phone booted up fine with unlocked message and able to use my phone again.. thanks Edgan! lol sorry if It's hard to understand me..
Also just ran quadrant and comparing to the leak 2.3.4 by samcripp this one gives me 300 more points consistently....
Click to expand...
Click to collapse
I don't know why you would see any performance difference. It should be exactly the same.
As for your 0x1000 problem, I have no idea why you got this. I tried this on some phones, and didn't have this problem. Though I used sbf_flash instead of RSD Lite 5.0.
I went back and checked the fuses on one phone to be sure a new one hadn't been blown. It came up the way I expected, not blown.
cat ReservedOdm
10000000000010001000100000000
Is that cat /mnt/proc/ReservedOdm that gives those 32 bits?
10000000000010001000100000000
This is great. What version of RSD does this work with? I did my friends with another method, and was missing all sounds/motoblur login didn't work. I will refer him to this thread.
From seeing the new MotoBlur, it is really nice. The screen rotation animation is very nice (not sure why all OEM's don't do that) very smooth.
edgan said:
I don't know why you would see any performance difference. It should be exactly the same.
As for your 0x1000 problem, I have no idea why you got this. I tried this on some phones, and didn't have this problem. Though I used sbf_flash instead of RSD Lite 5.0.
I went back and checked the fuses on one phone to be sure a new one hadn't been blown. It came up the way I expected, not blown.
cat ReservedOdm
10000000000010001000100000000
Click to expand...
Click to collapse
Before I flashed with rsd my RerservedOdm was and still is after upgrade is 10000000000010001000300004000 which showed my fuse was blown.
I didn't use fruit/pudding with the samcripp update. just did update.zip from the recovery.
stvmac11 said:
Isn't there a rooted version of this on the pudding page? or is it different
Click to expand...
Click to collapse
I have the same question. I just finished downloading the one on the pudding thread then saw this and am downloading it now. Does this have root? Is there any difference between the two?
lutharigno said:
I have the same question. I just finished downloading the one on the pudding thread then saw this and am downloading it now. Does this have root? Is there any difference between the two?
Click to expand...
Click to collapse
This doesn't come rooted.. you would have to do it again real quick.
OK I just bought another atrix of my friend who had already updated to the ota last night, will it be safe for me to use this?
Sent from my MB860 using XDA Premium App

Unable to get into Recovery after 4.1.2 upgrade...

Ok, so I ran into a VERY weird issue and was wondering if anyone else has experienced this or has a better solution then what I found.
My Nexus7 was running stock JRO03D. I had it rooted, using the Motley kernel with CWM Recovery - but outside of that, everything else was pretty stock. Anyway, I decided to upgrade to the 4.1.2 image. I pulled the one it downloaded automatically out of /cache and looked at the updater-script to see what it did. I noticed it replaced a lot, including the boot image, so I figured it would be better just to let it do everything and revert my custom stuff later. So I replaced the kernel with the stock JRO03D kernel and, using CWM, flashed the upgrade. Everything seemed to go perfect and it completed the upgrade. Prior to rebooting it, I also flashed the "unofficial" motley 4.1.2 kernel posted on XDA. I rebooted the device, and CWM warned me that 'su' needed to be fixed (how nice!) and made it suid again. It rebooted and after android "updated", everything was up and running. I confirmed in settings that it was on 4.1.2 with the custom kernel. SU was suid root as well. Perfect!
Not quite.
I decided to try rebooting into recovery to make sure CWM was still there, or flash it back if it wasn't. I opened up a terminal emulator, removed the new recovery-recovery image in /system, and did "reboot recovery". The Nexus7 rebooted, but rebooted right back into normal operation. Very weird. So I hooked it up to my computer, figuring CWM was gone, and tried to fastboot flash it back. Fastboot said it did, but I still wasn't able to reboot into recovery. I tried three different versions of CWM and even TWRP, but no dice. Every time I tried rebooting into recovery (using terminal emulator, adb shell or bootloader method) it just went right back into the normal boot process.
I spoke to some people on IRC who recommended reflashing the stock image from Google (without wiping user data). I reflashed the bootloader and then did a fastboot update <stock image>, and it said it replaced boot, recovery, system, etc. It rebooted automatically, and I tried going into stock recovery. That still did NOT work. Instead, I got a very sick looking android guy who was lying down with a red triangle with an exclamation point over him. I was a bit worried and upset at this point. I tried reflashing CWM/TWRP again, but nothing. When I did this, I no longer got the unhappy android image, but it just booted up normally.
I decided to try and doing a more thorough wipe, using fastboot to wipe cache/boot/recovery/system manually. Then I reflashed the bootloader and stock image. Still no recovery (stock or custom).
As you can imagine, I was getting even more concerned now. Especially since I was no without root and no way to get it back (since I couldn't get into recovery to flash the zip for it).
I tried every other thing I could think of to flash recovery back, but nothing worked. It wouldn't load at all.
Finally, I was about to do a complete factory reset and wipe/reflash of everything, but one last thought crossed my mind. I found the older (JRO03D) bootloader and flashed that. Reloaded bootloader and selected "Recovery". Voila, I was in TWRP Recovery Mode! (which was the last one I tried installing). I was able to reinstall my SU.zip and get everything back up and running.
SO, long story short, I'm now on 4.1.2, running the newer unofficial motley kernel and have su back. But I'm also stuck on the older 3.34 bootloader. If I try upgrading it back to 3.41, I won't be able to get into recovery.
Has this happened to anyone else? It doesn't seem like it. Is there a HW issue with my device causing this problem? I can't believe it's software related since I tried two different copies of the 3.41 image. Does anyone have any other suggestions on how I can upgrade the bootloader while keeping the ability to get into recovery mode?
Also, while everything *seems* to be working OK using 3.34, do you think it will cause other problems since I'm using 4.1.2?
Thanks.
*MOD EDIT* please don't quote the entire OP
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
MetalWych said:
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
Click to expand...
Click to collapse
No problem. I'm glad to hear that my solution above helped someone else, and also that I'm not the only one experiencing the problem. I assume you mean you only went back to the JRO03D bootloader and not the whole image, right?
What I'm most concerned about is that it seems like my N7 (and possibly yours as well) is defective. I'm not an uber-expert on Android, but I'm fairly knowledgeable. With a stock system, outside of userdata, that I reflashed multiple times from multiple sources, to have any type of recovery (stock or custom) not work is a bit upsetting. Since it works fine on the older bootloader, it definitely seems to be an issue with that. But since most people do not have the same issue, the only variable I can see being the difference is hardware.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It looked more like a warning symbol that something went very wrong then a stock recovery screen.
I've gone into stock recovery on other Android devices before, and it looked similar to CWM. There was a menu that allowed you to install "authorized" update.zip files, factory reset the device, etc. There was no menu here, just a very pissed off and sick looking android guy .
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
There's a big thread around here somewhere with people having the same problem as the op. Unfortunately, staying with the 3.34 bootloader is the only 'fix' I've read about. I still can't figure out why some people run into this problem and some don't. I used twrp to flash the update when it became available, and twrp continued to work afterwards.
spongers said:
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It took me a long time to find the old full JRO03D update, since Google only has the latest one on their page. I uploaded the bootloader out of it and you can download it here:
http://core.routed.com/bootloader-grouper-3.34.img
Reboot the Nexus7 into bootloader mode and run:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
and then you should be able to flash recovery and get into it.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The android with the red triangle does not sound like the stock recovery, it is THE stock recovery.
Under JB 4.1.2 you do not need anymore to connect the N7 to a computer - like it had to be under JB 4.1.1 - to access the bootloader and then the recovery.
Now, pressing volume + power brings the bootloader , the up volume, one press, and then power press put the N7 to recovery. The recovery is the android with the red triangle. To enter in the recovery menu pressing power + volume up brings the menu with the following options:
i) reboot system now,
ii) apply update from ADB,
iii) wipe data/factory reset,
iiii)wipe cache partition.
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
smirkis said:
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
Click to expand...
Click to collapse
Smirkis, my initial thought was that something went wrong in the upgrade process, possibly with the kernel like you suggested, so, as I mentioned in the OP, I flashed everything back to stock 4.1.2. I used flashboot to manually erase boot, cache, recovery and system. I then reinstalled the bootloader from Google's update tarball. I then used fastboot to update to image-nakasi-jzo54k.zip. At this point, outside of wiping sdcard, everything was stock 4.1.2.
While I will admit that I didn't realize that the dead-looking android meant stock recovery (and that's good to hear), subsequently flashing a custom recovery (CWM or TWRP) would continually fail to load it. In fact, I couldn't even boot into the recovery manually without flashing it. While using 100% stock, I attempted to flash three different versions of CWM and one version of TWRP. It claimed it updated, but I was not able to get back into recovery - either through bootloader, adb or "reboot recovery".
I know it's easy for people to always jump to the "user error" answer, but I fail to see how that is the case here. Based on your response, I don't think you actually read what I did and just jumped to the wrong conclusion, especially since I already tried your recommendation and much more. I am not running any custom ROM - everything was always stock outside of recovery, root and kernel. If you can explain your reasoning for thinking I did something wrong in all of my numerous attempts to get it working, I would appreciate it since maybe that would provide a solution. While I did attempt to use a custom kernel originally, that obviously isn't the issue if going back to stock didn't fix it.
Additionally, reverting back to the older bootloader magically fixed everything, while all other attempts failed. Subsequently reinstalling the custom kernel didn't break anything either. So if it wasn't the bootloader and something else was broken, I would assume it would be broken in both versions of the bootloader. The fact that this problem is affecting others, granted a small number, and the same solution works for them, leads me to believe that there is either a bug in the bootloader affecting some N7s or some rare HW defect causing a few of us problems.
There is a conversation about the new android update the boot-loader update and A Power management chip on the nexus 7.. It seems this chip is being changed out. The new chip functions the same as they have been using but Its not compatible with the old boot-loader . The above is the reason for the boot-loader change.. Google is aware of the troubles everyone in this thread is having . I would be looking for a new very tiny update in the near days. Just a guess im wondering if the truth is they are gearing up for the 3g version of nexus .maybe the pm chip being changed has a issue with the added radios. They did say ITS NOT A Chip upgrade but will not say why they are making the switch .
sorry i do not have a link . but everyone knows how to get to google groups ..
Happy Reading..
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
smirkis said:
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
Click to expand...
Click to collapse
Just to clarify, going from bootloader->recovery never worked for me either. Whenever I needed to get into recovery mode, I just opened up a terminal, su'd to root and then ran "reboot recovery", or occasionally doing it via adb. However, those methods always worked for me until I upgraded to the latest bootloader. Then, no custom recoveries would load via any method.
My Nexus7 was first generation. I actually picked it up in Sams Club the day before they were officially released. So if Google made any HW changes in the different revisions, that might explain the difference in results on 4.1.2. Though I imagine most people on XDA also picked theirs up out of the first batch, so I don't think that could be the case. What seems more likely is that there are minor hardware differences that are causing some people's to fail with the 3.41 bootloader, while most don't have that issue. It will be interesting to see if you experience the same issue on your new one though.
gunner1937 said:
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
Click to expand...
Click to collapse
It didn't worked for me. I've tried Rootkeeper apk, but it was useless.
This was driving me crazy until I've found this topic! I've tried resetting it to original settings, using rootkeeper and traditional methods, nothing, zero!
At last, phonic saved my life, and finally I a could root my Nexus 7!
I never responded but my RMA worked as it should. but the issue has been resolved with recovery updates from the developers. the rest of the world who had issues should be good to go. I ended up selling my 16gb unit and got a 32 and it works as it should as well. are we all happy campers now?
Sent from my Nexus 7 using xda premium
I've had similar experiences where the way certain kernels install zips are packaged, the wipe custom recoveries at install. In that situation, I've never wiped anything from system, but rebooted into bootloader and fastboot boot recovery "recovery.img". Then from there install the recovery.zip. The worst is when this happens when you get flash happy away from home and the kernel doesn't work. No way to fix without a comp w/SDK. Glad you're back up and running.
(I cannot be held responsible if the aforementioned damages your device; do the research and own the process.)
I am so glad to have found this thread. This problem was beginning to drive me nuts.

Can't Re-Stock Device Using ANYTHING?

To start off with
1. No im not Boot loader Unlocked ( i forgot to Unlock Boot loader )
2. i used to be rooted? ( not sure now? )
3. i got phone it was on 4.0.4 Stock i got OTA now its on 4.1.1 Stock with Root ( not sure any more? )
4. its AT&T US
so right now what im looking at is this
I Can Charge battery with ICON %Battery
I can access Recovery ( Slandered ) Not Custom Rooted One booo
i can access Fastboot & well that white menu by holding VOL - & VOL +
i can see it telling me Device Locked Statue 0
now what happen to get to this point was this
i wanted to change the AT&T Carrier Logo to something else i download app off internet and i was stupid to give it ROOT ACCESS.... ya i know
next thing i know poof it tells me to reboot i reboot and now i see Moto Logo then nothing but Black screen.....
i try to use RSD Lite and use the .XML.zip files all 3 of them but no luck
i try everything no luck.... im freaking out..... with no luck lol.....
can someone help with this?.....
when i try to RSD LITE it i got many errors
some forums told me to Edit 2 to 3 lines to remove a VAR or somthing it started to work bu then got stuck at Boot.img and other system.img and anohter called NON-HLOS.bin?
i try to use another file called Blur_Version.77.12.22.MB886.ATT.en.US.zip
its got some strange files in it? ..... ill upload photo but i place it on sd card and try to update it but tells me somehting about ro.build pro 4.0.4 release keys ro.build pro 4.1.1? makes no since to me?
View attachment 2802750
I'm helping a friend on the same situation.
Phone doesn't boot.
Stuck on M logo.
Locked bootloader.
Able to go to AP fastboot
No custom recovery.
Particularly this is my first time dealing with a motorola phone. Have flashed HTC and have owned mostly samsung phones.
But I know my way a bit on adb and fastboot.
Anyways I'll keep an eye on this thread and let you know if I find something on my own.
I'll try with RSDLite, Myth tools and fastboot.
Maybe one of them will work.
Good luck.
Silenus21 said:
I'm helping a friend on the same situation.
Phone doesn't boot.
Stuck on M logo.
Locked bootloader.
Able to go to AP fastboot
No custom recovery.
Particularly this is my first time dealing with a motorola phone. Have flashed HTC and have owned mostly samsung phones.
But I know my way a bit on adb and fastboot.
Anyways I'll keep an eye on this thread and let you know if I find something on my own.
I'll try with RSDLite, Myth tools and fastboot.
Maybe one of them will work.
Good luck.
Click to expand...
Click to collapse
from what i can tell..... RSD LITE is not gonna work.... but im sure if i get the New 4.1.1 Update zip file that u add to SD CARD and Flash update through there it will work as long as its singed. i have 4.0.4 but keeps crashing durning install telling me ro.buildprop 4.0.4 & ro.buildprop.4.1.1 so i think that i has a 4.0.4 update file when i need a 4.1.1 but unsure where to get it? ..... so mad i spent $250 bucks on this thing to have a Rouge App do this to me lol...... next time NO more root for me lol
Have you tried mythtools??
Sent from my ATRIX HD using XDA Free mobile app
Silenus21 said:
I'm helping a friend on the same situation.
Phone doesn't boot.
Stuck on M logo.
Locked bootloader.
Able to go to AP fastboot
No custom recovery.
Particularly this is my first time dealing with a motorola phone. Have flashed HTC and have owned mostly samsung phones.
But I know my way a bit on adb and fastboot.
Anyways I'll keep an eye on this thread and let you know if I find something on my own.
I'll try with RSDLite, Myth tools and fastboot.
Maybe one of them will work.
Good luck.
Click to expand...
Click to collapse
From fastboot, I recommend unlocking the bootloader, install Philz, and flash a custom KK ROM.
Manual fastboot didn't work. Always stuck on flashing boot.img and system.img
The same happen on that step in rds lite and myth tools.
Phone said can't downgrade or something like that.
So I haven't had any luck yet.
Open to suggestions.
Sent from my SM-N900V using XDA Premium 4 mobile app
Silenus21 said:
Manual fastboot didn't work. Always stuck on flashing boot.img and system.img
The same happen on that step in rds lite and myth tools.
Phone said can't downgrade or something like that.
So I haven't had any luck yet.
Open to suggestions.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
im just gonna sell it on Craigslist & let it be someone else issue!
News
so i went to here http://sbf.droid-developers.org/phone.php?device=7 to just see if they added a new Update file and Poof they did.
they added: Android 4.1.1
Blur_Version.98.5.38.MB886.ATT.en.US
so i ran RSD LITE nothing fail, i edit the xml, nothing fail... i used the Mytool thing that people keep saying to use for Moto phones and Poof it worked now my phone works again and i did not has to sell it on craglist dead.... but now there is an issue that was not there before... 4 times a day i get a RED CROSS with no signal and no bars and no service telling me emergancy calls only so i do air plane mode and works again for a while? does any one know why it does this?
any way back to sell it to craglist lol....
Maybe have to flash a modem.
Thanks for the update, I gave the phone back to my friend but will tell him to bring it back to me to test.
Hopefully this works for that phone too.

[Resolved] Moto X randomly bricked itself

So, I imported and gifted this device to my GF and will describe what happened as she did. She was downloading a torrent and suddenly the screen just went black. After holding the power button for awhile, the phone came back on but, would get stuck on the boot logo(welcome message) screen and in a boot loop. I know that it is a SIM unlocked Moto X(XT 1053?)
So far, I've tried getting into the bootloader and am able to. The only problem is when I get to the recovery, I don't see the little dead Android dude. The phone ends up dying. Now I have it charging and I'm on the bootloader screen, but I still can't get into recovery. I just get a blank screen when I try.
It will be hard, time consuming and maybe a little expensive RMAing the device, as I'd probably have to send it back to the US for the warranty.
I'm thinking maybe I just try and unlock the bootloader and see if the subsequent factory reset helps. But I don't know if this will work.
I have tried fastboot erase cache but it didn't help.
I think somehow my recovery is gone. I've tried flashing a recovery.img but it errors out. (failed to hab check for recovery)
Any ideas?
Did you root the XT1053 before you sent it to her? If so, how?
Next, do you know what ROM was on there before it got stuck in this state? the failed hab check when flashing recovery makes me question if there is a missmatch somewhere... i.e. attempt to down grade from 4.4.3 or 4.4.2 to lower... or the stock recovery you are trying to flash doesn't match the rom version on the phone.
KidJoe said:
Did you root the XT1053 before you sent it to her? If so, how?
Next, do you know what ROM was on there before it got stuck in this state? the failed hab check when flashing recovery makes me question if there is a missmatch somewhere... i.e. attempt to down grade from 4.4.3 or 4.4.2 to lower... or the stock recovery you are trying to flash doesn't match the rom version on the phone.
Click to expand...
Click to collapse
No, it was not rooted, completely stock and the bootloader was locked. Something just got borked I guess. It was on 4.4.3. It was like there was no recovery and I attempted to access it a bunch of time.
So, my solution was to just void my warranty and unlock the bootloader. This worked. But, on reboot it went to the dead Android logo, and I could suddenly access recovery again(WTF?!). I did a factory reset and now it seems to be working fine!
Now, for the fun bit. I'm going to use your guide to make my face her boot logo! :cyclops:
deejaylobo said:
No, it was not rooted, completely stock and the bootloader was locked. Something just got borked I guess. It was on 4.4.3. It was like there was no recovery and I attempted to access it a bunch of time.
So, my solution was to just void my warranty and unlock the bootloader. This worked. But, on reboot it went to the dead Android logo, and I could suddenly access recovery again(WTF?!). I did a factory reset and now it seems to be working fine!
Now, for the fun bit. I'm going to use your guide to make my face her boot logo! :cyclops:
Click to expand...
Click to collapse
Funny. I've read of another having a similar issue... locked, not-rooted, and had the phone just "brick." Warranty replacement was needed. So keep an eye on that.
Since you factory reset already, you could consider re-flashing the firmware to the phone, just in case.. To be safe, make sure you are flashing the EXACT same rom, do not attempt to downgrade. I would consider using mFastboot rather than RSDLite... and follow option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html (and yes, there are a couple of lines repeated in that sequence, its intentional).
As for using your face for her bootlogo.. hmm... you sure she is ok with that? then again, the X doesn't need to be rebooted often, so she wont see it
KidJoe said:
Funny. I've read of another having a similar issue... locked, not-rooted, and had the phone just "brick." Warranty replacement was needed. So keep an eye on that.
Since you factory reset already, you could consider re-flashing the firmware to the phone, just in case.. To be safe, make sure you are flashing the EXACT same rom, do not attempt to downgrade. I would consider using mFastboot rather than RSDLite... and follow option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html (and yes, there are a couple of lines repeated in that sequence, its intentional).
As for using your face for her bootlogo.. hmm... you sure she is ok with that? then again, the X doesn't need to be rebooted often, so she wont see it
Click to expand...
Click to collapse
I only found one person with a similar issue, and you're right, he did end up getting a replacement. That's just not an option for me. It's too much of a pain sending it back to the US.
Yeah, I think I will reflash a ROM. Can you point me towards figuring out which is the correct ROM? My System Version is 212.44.21.ghost_row.Retail.en.US. So, I just grab the corresponding SBF, yeah? I flashed the logo with mfastboot, so I'm okay with that. EDIT: No worries. Foudn the right file. Sorted. Everything seems to be working fine. Thanks!
The face thing, is just to prank her. I previously had a custom message set up for her through the Moto Maker. I think she'll be rebooting her phone more often now.

stuck in boot loop android is starting optimizing apps after update

sorry if this has been covered but i cant find anything the same as my situation and im pretty stuck.
I have just bought a nexus 6 and the phone prompted me to update to 5.1 so i have, once it restarted i am now stuck in a boot loop with it saying optimizing apps then restarts and the same again, i have tried booting into recovery and wipe data but just get the same.
I have tried using nexus root toolkit (wugsfresh) however cannot find fastboot connectivity so im stuck there.
The phone is not rooted and i cant seem to get access through adb ( i have not turned usb debugging on as the phone is new)
I really am not too clued up so im sorry if i need things explaining abit more.
Thanks in advance
viper1402 said:
sorry if this has been covered but i cant find anything the same as my situation and im pretty stuck.
I have just bought a nexus 6 and the phone prompted me to update to 5.1 so i have, once it restarted i am now stuck in a boot loop with it saying optimizing apps then restarts and the same again, i have tried booting into recovery and wipe data but just get the same.
I have tried using nexus root toolkit (wugsfresh) however cannot find fastboot connectivity so im stuck there.
The phone is not rooted and i cant seem to get access through adb ( i have not turned usb debugging on as the phone is new)
I really am not too clued up so im sorry if i need things explaining abit more.
Thanks in advance
Click to expand...
Click to collapse
flash a factory image, your update went no good. if you havent ever done this, i DO NOT RECOMMEND using a toolkit. toolkits are good for people who know what they are doing. if you dont kniw, you will remain clueless, and could make things much worse.
simms22 said:
flash a factory image, your update went no good. if you havent ever done this, i DO NOT RECOMMEND using a toolkit. toolkits are good for people who know what they are doing. if you dont kniw, you will remain clueless, and could make things much worse.
Click to expand...
Click to collapse
am i able to flash a factory image without being able to connect the device via adb? i just wasnt able to find the device on it
Thanks for the reply
viper1402 said:
am i able to flash a factory image without being able to connect the device via adb? i just wasnt able to find the device on it
Thanks for the reply
Click to expand...
Click to collapse
factory images are only flashed while youre in your bootloader, via fastboot. thetes a stick for directions in the general thread.
simms22 said:
factory images are only flashed while youre in your bootloader, via fastboot. thetes a stick for directions in the general thread.
Click to expand...
Click to collapse
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
I'd suggest avoiding the OTA's and fastboot flash the latest factory image. LMY48I
IMHO....
viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
is it worth it? YES! if you want, you can flaah the factory image for 5.1.1 instead of taking the ota. but chances are that the ota will be fine.
viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
How did u get it sorted? I just had a friend call me with exactly the same problem! He's not very tech savvy so it's proving difficult talking him thru it, so if u found an easy solution for me to pass on that would be great ?
boxa72 said:
How did u get it sorted? I just had a friend call me with exactly the same problem! He's not very tech savvy so it's proving difficult talking him thru it, so if u found an easy solution for me to pass on that would be great
Click to expand...
Click to collapse
As stated before. Forget OTA. Unlock bootloader and fastboot flash the images manually. Do not take OTA with bootloader locked. If OTA fails have to RMA. No fix.
I had the same issue today and like PRDOG1 said I was talking to him on my forum post. As soon as you get the phone unlock that bootloader, then just do flashes through the bootloader. It is safer, and as long as that bootloader is unlocked you can go ahead and load up any image you want thats factory and you will be fine.
Well it should be fine then coz the carriers in Aussie don't lock bootloaders. I just told him to bring the phone to me n I'll re-flash a stock image for him but I thought u may have found another way as I'm more familiar with Samsung and Windows than I am with Nexus. It seems pretty common this bootloop stuff after OTA with the N6.
Sent from my SM-G920I using Tapatalk
I suspect you are confusing carrier SIM lock with bootloader lock.
Carriers do not usually do anything with bootloader lock - they may force a SIM lock to their SIM cards however.
On the Nexus 6 however, unlocking the bootloader is pretty easy (assuming you can boot to the OS and select the option to allow OEM unlock). I'd recommend leaving the bootloader unlocked and flashing twrp asap, in case of any issues later.
Altho in Australia they don't carrier lock bootloaders the software comes locked for security reasons. If he didn"t unlock prior to the OTA update it is bricked and will require RMA.

Categories

Resources