Related
Got the update through today.
Put the original recovery back in place as CM fails the install.
It's now been sat on a picture of a phone with green arrow circles above it, and a scroll bar stuck on ~30% for about an hour and a half. So I guess nothing is happening- thoughts?
*EDIT - tried turning it off. When I turned it back on, it said "Entering recovery" and is now back at the same point?
jmbillings said:
Got the update through today.
Put the original recovery back in place as CM fails the install.
It's now been sat on a picture of a phone with green arrow circles above it, and a scroll bar stuck on ~30% for about an hour and a half. So I guess nothing is happening- thoughts?
*EDIT - tried turning it off. When I turned it back on, it said "Entering recovery" and is now back at the same point?
Click to expand...
Click to collapse
Is your phone rooted and were you on a stock rom when you downloaded the update ?
maxal said:
Is your phone rooted and were you on a stock rom when you downloaded the update ?
Click to expand...
Click to collapse
I /was/ rooted, although after it rebooted the first time and tried to update in CWM that seemed to deactivate itself. Stock ROM, yes.
I have since tried wiping cache and re-flashing stock recovery once more, but now the recovery just goes to the warning triangle rather than the green arrows, so I've probably made it worse
I can still get into fastboot ok. Can I get the OTA zip and flash it through fastboot anywhere?
jmbillings said:
I /was/ rooted, although after it rebooted the first time and tried to update in CWM that seemed to deactivate itself. Stock ROM, yes.
I have since tried wiping cache and re-flashing stock recovery once more, but now the recovery just goes to the warning triangle rather than the green arrows, so I've probably made it worse
I can still get into fastboot ok. Can I get the OTA zip and flash it through fastboot anywhere?
Click to expand...
Click to collapse
I have the same problem. I tried fixing it trough flashing a firmware.zip but I think it might've been the 4.2.2 firmware zip and now my phone's proper messed up. Still boots and everything works except for camera and sd card.
markvdn said:
I have the same problem. I tried fixing it trough flashing a firmware.zip but I think it might've been the 4.2.2 firmware zip and now my phone's proper messed up. Still boots and everything works except for camera and sd card.
Click to expand...
Click to collapse
I would advice trying a factory reset if you have a backup of your data to see if that helps with the issue's.
I know there are some issue's being reported when trying to update to 4.2.2 with root
gazlufc said:
I would advice trying a factory reset if you have a backup of your data to see if that helps with the issue's.
I know there are some issue's being reported when trying to update to 4.2.2 with root
Click to expand...
Click to collapse
Hmm okay, did a factory reset through fastboot, will try the 4.2.2 OTA again.
Will report back in 5 mins.
markvdn said:
Hmm okay, did a factory reset through fastboot, will try the 4.2.2 OTA again.
Will report back in 5 mins.
Click to expand...
Click to collapse
Kewl waiting to hear if all works again
I have the same problem with mine
I may just do a full wipe and start over with a new ROM. Seems as good a time as any seeing as it's buggered! Unless anyone knows where to get the OTA from and how to flash it through fastboot
I found the OTA zip on my phone this place : /data/data/com.android.providers.downloads/cache
Impossible to flash it, it returns errors
gazlufc said:
Kewl waiting to hear if all works again
Click to expand...
Click to collapse
Doesn't seem to be working, freezes in the exact same place as before
Took a bit longer cause I had to download it over 3G instead of wifi.
---------- Post added at 05:52 PM ---------- Previous post was at 05:27 PM ----------
Can anyone provide me with the firmware.zips for 4.1? I've accidentally flashed the 4.2 ones and need to revert to 4.1 for the OTA to work.
I'm stuck too, phone was rooted previously did I didn't reroot after the last upgrade, just flashed CWM. Flashed stock recover from ARHD, accepted OTA update, now stuck on upgrade screen. Pain in the arse, really hoping to avoid starting from scratch.
dahamsta said:
I'm stuck too, phone was rooted previously did I didn't reroot after the last upgrade, just flashed CWM. Flashed stock recover from ARHD, accepted OTA update, now stuck on upgrade screen. Pain in the arse, really hoping to avoid starting from scratch.
Click to expand...
Click to collapse
I gave up. Put Revolution Stock ROM onto a 4Gb memory stick, flashed CWM, mounted external SD and installed the zip.
To be fair, HTC Backup has restored my email accounts already. Apps downloading now.
I hard-cycled and it restarted, completed, and went to black for an extended period of time. Hard-cycled again and it completed. Terrible process feedback.
I had the same problem, it was stuck around ~25% and just didn't move. I turned mine off and held the down volume button down, but that just took it back into recovery but this time it installed. Bar is just at ~90% now.
Do you have S-OFF or S-ON?
I still had root but I recovered my recovery from clockwork to original and also relocked bootloader and remove tampered message and then did S-ON before doing the OTA.
Since writing this, my install has just finished and on the reboot now.
nicelad_uk said:
I still had root but I recovered my recovery from clockwork to original and also relocked bootloader and remove tampered message and then did S-ON before doing the OTA.
Since writing this, my install has just finished and on the reboot now.
Click to expand...
Click to collapse
Hi nicelad,
Could you explain how did you get your One relocked and S-on ? Thanks
I used revone to do the relocking and then a fastboot oem writesecurelock 3 via cmd on pc to write the S-ON
Sent from my HTC One using Tapatalk 4 Beta
Thanks, i'm going to try this
Edit : Did what you said, but still can't update. The update stops at almost 20 %
Hello guys.
So my cousin's AHD started to reboot all times and can't cross over the "M" logo.
I tried everything, opened stock recovery, wiped data/cache, downloaded stock firmware and flashed with RSD, then flashed manually, step-by-step, but still no luck.
Phone starts, moto logo appears, then it restarts and so on.
Might it be a hardware issue?
For the sake of god, help me guys
Demsee said:
Hello guys.
So my cousin's AHD started to reboot all times and can't cross over the "M" logo.
I tried everything, opened stock recovery, wiped data/cache, downloaded stock firmware and flashed with RSD, then flashed manually, step-by-step, but still no luck.
Phone starts, moto logo appears, then it restarts and so on.
Might it be a hardware issue?
For the sake of god, help me guys
Click to expand...
Click to collapse
When you flash with RSD Lite, does it gives you an error? Have you tried doing it manually with fastboot?
mauchito said:
When you flash with RSD Lite, does it gives you an error? Have you tried doing it manually with fastboot?
Click to expand...
Click to collapse
not a single error dude, everything goes OK. i tried with manual method as well, but still no go.
any1?
I cant tjink of anything other then asking what rom version you are using
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
Well, you could try "fastboot -w" (a factory reset via fastboot) to see if the problem is related to the internal SD or userdata. That's a common issue we were having when CM10.2 sucked and users were swapping between stock roms and custom 4.2+ roms (the sd card is stored differently from 4.1 to 4.2+). It was a cause of some of my bootloops.
I noticed you metioned using stock recovery....is your bootloader locked? If yes then only use the fastboot zip of your last stock rom and nothing else. Even with an unlocked bootloader we can't downgrade gpt_main0.bin (the first thing fastboot flashes) so stick with your stock rom just in case this is a hardware issue....cause it would seriously suck to be voided for warranty because they detected the wrong partition table, and they will detect that because an RSD flash is the first thing they'll do.
If you could, post some screenshots of you flashing crap with RSD and from the terminal. Most of the time those screenshots help us more than what's actually posted in text. If you're unlocked with CWM and ADB up and running, then after a loop access CWM and do "adb shell cat /proc/last_kmsg > C:\last_kmsg.txt" and post the last_kmsg.txt here. That'll tell us if this is a kernel error or not.
skeevydude said:
Well, you could try "fastboot -w" (a factory reset via fastboot) to see if the problem is related to the internal SD or userdata. That's a common issue we were having when CM10.2 sucked and users were swapping between stock roms and custom 4.2+ roms (the sd card is stored differently from 4.1 to 4.2+). It was a cause of some of my bootloops.
I noticed you metioned using stock recovery....is your bootloader locked? If yes then only use the fastboot zip of your last stock rom and nothing else. Even with an unlocked bootloader we can't downgrade gpt_main0.bin (the first thing fastboot flashes) so stick with your stock rom just in case this is a hardware issue....cause it would seriously suck to be voided for warranty because they detected the wrong partition table, and they will detect that because an RSD flash is the first thing they'll do.
If you could, post some screenshots of you flashing crap with RSD and from the terminal. Most of the time those screenshots help us more than what's actually posted in text. If you're unlocked with CWM and ADB up and running, then after a loop access CWM and do "adb shell cat /proc/last_kmsg > C:\last_kmsg.txt" and post the last_kmsg.txt here. That'll tell us if this is a kernel error or not.
Click to expand...
Click to collapse
thanks mate for respond.
first of all, BL is locked and i know about RSD and all that crap things. There is latest stock JB installed on this phone, i also tried fastboot -w command, but it makes nothing, still boot loop.
I haven't CWM, because of locked BL.
I saw video on youtube, how to fix boot loop. Guy in that video, removed battery, gave it on external direct charge and fixed phone. If necessary, i'll post the link. I just wanna know, if it's hardware or software issue. Thanks in advance
Demsee said:
thanks mate for respond.
first of all, BL is locked and i know about RSD and all that crap things. There is latest stock JB installed on this phone, i also tried fastboot -w command, but it makes nothing, still boot loop.
I haven't CWM, because of locked BL.
I saw video on youtube, how to fix boot loop. Guy in that video, removed battery, gave it on external direct charge and fixed phone. If necessary, i'll post the link. I just wanna know, if it's hardware or software issue. Thanks in advance
Click to expand...
Click to collapse
Probably a software issue. For some reason these phones can be very finicky.
In that video I'd assume that guy used a Moto Factory cable...that's the only think I can think of that will allow us to do that. The Factory cable is able to power the board directly from USB and is a good tool to keep around (I actually need to get one myself).
When you say "latest stock JB" do you mean "latest stock AT&T JB or Bell JB or Mex Retail JB". It matters. If your last stock was AT&T and you flash Mex Retail system, dev_tree, & boot.img then it won't work (gpt_main0.bin will detect the different partition md5 and halt the boot). If you can manually flash gpt_main0.bin from AT&T JB then your last stock was AT&T JB, if not then use the Bell JB fxz, if still not then use Mex Retail fxz. (snap-fastboot flash partition gpt_main0.bin....snap-fastboot is what I renamed our custom fastboot executable to).
skeevydude said:
Probably a software issue. For some reason these phones can be very finicky.
In that video I'd assume that guy used a Moto Factory cable...that's the only think I can think of that will allow us to do that. The Factory cable is able to power the board directly from USB and is a good tool to keep around (I actually need to get one myself).
When you say "latest stock JB" do you mean "latest stock AT&T JB or Bell JB or Mex Retail JB". It matters. If your last stock was AT&T and you flash Mex Retail system, dev_tree, & boot.img then it won't work (gpt_main0.bin will detect the different partition md5 and halt the boot). If you can manually flash gpt_main0.bin from AT&T JB then your last stock was AT&T JB, if not then use the Bell JB fxz, if still not then use Mex Retail fxz. (snap-fastboot flash partition gpt_main0.bin....snap-fastboot is what I renamed our custom fastboot executable to).
Click to expand...
Click to collapse
Of course i mean AT&T stock JB. I didn't flash anything, except at&t stock firmware.
this is link, to that fix http://www.youtube.com/watch?v=5QgavcY0OAg
One more thing guys.
When i try to flash with RSD, it can't be finished, because of loop.
there is 23 step for flashing.
It writes system, writes boot, writes everything, than it erases cache and reboots, but stucks in boot loop.
Result is "In Progress", if i look on RSD.
Suddenly phone came back to life, idk why.
but now i'm afraid to unlock bootloader, coz i'm not sure, if it comes back to life after reboot.
what should i do?
Demsee said:
Suddenly phone came back to life, idk why.
but now i'm afraid to unlock bootloader, coz i'm not sure, if it comes back to life after reboot.
what should i do?
Click to expand...
Click to collapse
Maybe use it as is for a while to make sure it is functioning properly. It could be a hardware problem, no?
audit13 said:
Maybe use it as is for a while to make sure it is functioning properly. It could be a hardware problem, no?
Click to expand...
Click to collapse
i really don't know, but suddenly it came back to life, than i rooted, installed CWM, unlocked bootloader and phone works like a charm. i have no words to say, it fixed itself, but maybe some day it will loop again. just dont know
Demsee said:
i really don't know, but suddenly it came back to life, than i rooted, installed CWM, unlocked bootloader and phone works like a charm. i have no words to say, it fixed itself, but maybe some day it will loop again. just dont know
Click to expand...
Click to collapse
The fact that you were able to do all of that is awesome. Let's hope the phone lasts for a while and enjoy:fingers-crossed:
audit13 said:
The fact that you were able to do all of that is awesome. Let's hope the phone lasts for a while and enjoy:fingers-crossed:
Click to expand...
Click to collapse
thanks mate ^_^
seems like it's fixed, i restarted about 20-25times and loop has gone
installed holoblur and enjoying this phone.
thank you all for respond
I have Moto X Verizon Dev eition on 4.4. unlocked bootloader, Installed TWRP few weeks back with SuperSU for root. Worked perfect.
4.4.2 upgrade messages kept coming up, but I just ignored them by hitting back button.
This morning, while I was typing something and I was about to hit send, that message popped up and instead of hitting send, i hit INSTALL NOW. no warning, no confirmation, it said "power off" and started process of updating.
But the problem is that I still have twrp and is rooted, so everytime it reboots it goes to Team Win Recovery page and if I reboot from there, it goes back to normal boot up but then reboots automatically in 15 secs and goes on in an infinite loop.
I cannot start/stop anything when it boots up normally because I have literally 15 secs before it reboots automatically.
Any idea? On teamwin reocovery page, should I goto wipe>> factory reset? and then upgrade and so the whole TWRP and SuperSu again?
and of course, i am to stupid to have no backups made
KhAjUr said:
I have Moto X Verizon Dev eition on 4.4. unlocked bootloader, Installed TWRP few weeks back with SuperSU for root. Worked perfect.
4.4.2 upgrade messages kept coming up, but I just ignored them by hitting back button.
This morning, while I was typing something and I was about to hit send, that message popped up and instead of hitting send, i hit INSTALL NOW. no warning, no confirmation, it said "power off" and started process of updating.
But the problem is that I still have twrp and is rooted, so everytime it reboots it goes to Team Win Recovery page and if I reboot from there, it goes back to normal boot up but then reboots automatically in 15 secs and goes on in an infinite loop.
I cannot start/stop anything when it boots up normally because I have literally 15 secs before it reboots automatically.
Any idea? On teamwin reocovery page, should I goto wipe>> factory reset? and then upgrade and so the whole TWRP and SuperSu again?
Click to expand...
Click to collapse
turn phone off. boot into bootloader/fastboot mode. run "fastboot erase cache". your reboots will stop. then use tibu to freeze motorola ota and you wont get ota things pop up anymore.
jayboyyyy said:
turn phone off. boot into bootloader/fastboot mode. run "fastboot erase cache". your reboots will stop. then use tibu to freeze motorola ota and you wont get ota things pop up anymore.
Click to expand...
Click to collapse
Awesome. gorked like a charm.
just a note for someone else trying this.... first time i booted up after doing a "fastboot clear cache", i got a warning saying failed to load info. I clicked okay and I would get no service. Rebooted normally again, and everything worked fine.
Thanks again fro the response.
So are you now on 4.4.2?
The Tallest said:
So are you now on 4.4.2?
Click to expand...
Click to collapse
Nope. I rolled back. seems like I will have to roll back the root and then install 4.2.2 and then root again or something. Too much mess to go to 4.2.2. There are no specific and detailed directions for vzw dev edition rooted phone that I could find, so would leave it alone for now.
KhAjUr said:
Nope. I rolled back. seems like I will have to roll back the root and then install 4.2.2 and then root again or something. Too much mess to go to 4.2.2. There are no specific and detailed directions for vzw dev edition rooted phone that I could find, so would leave it alone for now.
Click to expand...
Click to collapse
If you're stock rooted, you just need to flash the stock recovery (available from the moto dev site) and make sure you don't have any missing or modified system files. You can then just take the OTA like normal, then reflash TWRP after.
KhAjUr said:
Nope. I rolled back. seems like I will have to roll back the root and then install 4.2.2 and then root again or something. Too much mess to go to 4.2.2. There are no specific and detailed directions for vzw dev edition rooted phone that I could find, so would leave it alone for now.
Click to expand...
Click to collapse
There are a lot of threads discussing this.
If you have a Dev Edition X with an unlocked bootloader, as long as you have stock recovery on the phone, and are close enough to stock, you can just take the 4.4.2 OTA and re-root using the same TWRP and SuperSU process. (more details -> http://mark.cdmaforums.com/MotoX-OTA.html which is based on many threads here on XDA)
Downgrading to 4.2.2, etc.. while rooting was for locked bootloaders only.
jayboyyyy said:
turn phone off. boot into bootloader/fastboot mode. run "fastboot erase cache". your reboots will stop. then use tibu to freeze motorola ota and you wont get ota things pop up anymore.
Click to expand...
Click to collapse
I'm fairly positive this will fix my problem since I'm experiencing the exact same thing as the OP.
However, I'm still new to bootloaders and rooting, etc...
Can someone breakdown what jayboyyyy is saying here? I can get into my TWRP bootloader. How do I run "fastboot erase cache"? Do I use the built in terminal command? Do I need to plug into my computer? Do I need to point my cmd to the TWRP I originally downloaded and installed on my phone?
I really do not want to mess this up. Like I said, I'm sure this is the fix for my phone. Thanks in advance!
TWRP is recovery, not bootloader / fastboot
You will need to plug into your computer, you should probably read more before you break things worse tho.
Start here: http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358
vennardk said:
I'm fairly positive this will fix my problem since I'm experiencing the exact same thing as the OP.
However, I'm still new to bootloaders and rooting, etc...
Can someone breakdown what jayboyyyy is saying here? I can get into my TWRP bootloader. How do I run "fastboot erase cache"? Do I use the built in terminal command? Do I need to plug into my computer? Do I need to point my cmd to the TWRP I originally downloaded and installed on my phone?
I really do not want to mess this up. Like I said, I'm sure this is the fix for my phone. Thanks in advance!
Click to expand...
Click to collapse
TWRP is a RECOVERY, not bootloader.
Do you remember how you flashed TWRP on your phone? You booted the phone into Fastboot/Bootloader mode. Connected the phone to PC via USB cable, then from command prompt on the PC used the Fastboot or mFastboot command... Same thing. However in this case the command to clear your phone's cache is... mfastboot erase cache
The other option is, you can see if there is an "erase cache" menu option while in TWRP as that would work too.
Then to take an OTA, you need to flash stock recovery back on your phone. If you try to accept an OTA while TWRP or other custom recovery is on your phone, you will get stuck in a boot loop like this.
My brother just got an atrix hd from a guy at work. The phone will not boot into normal, recovery, or anything else besides the AP Fastboot mode. in the AP fastboot screen the text says:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-2e68372, 2012-11-17 23:3308)
eMMC info: size 8GB
Device is LOCKED, Status Code:0
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Boot menu selected
From what my brother knows the guy had the phone in his lunchbox and when he got home from work and tried to turn it on this is what the phone was doing.
Is there something i can try or a way to flash a system image? I've rooted, unlocked the bootloader and installed custom roms on a variety of phones and im sure i can get this phone straightened out if i was just pointed in the right direction. Thanks for any and all the help! its greatly appreciated!!!
Mythtools is your friend. Here's a link to the thread.
http://forum.xda-developers.com/showthread.php?t=2262726
[Tools][TheMythTeam] Myth Tools for Atrix HD - Update v1.3 (24/03) - Big Update
Sent from my MB886 using XDA Free mobile app
jrodbrown58 said:
My brother just got an atrix hd from a guy at work. The phone will not boot into normal, recovery, or anything else besides the AP Fastboot mode. in the AP fastboot screen the text says:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-2e68372, 2012-11-17 23:3308)
eMMC info: size 8GB
Device is LOCKED, Status Code:0
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Boot menu selected
From what my brother knows the guy had the phone in his lunchbox and when he got home from work and tried to turn it on this is what the phone was doing.
Is there something i can try or a way to flash a system image? I've rooted, unlocked the bootloader and installed custom roms on a variety of phones and im sure i can get this phone straightened out if i was just pointed in the right direction. Thanks for any and all the help! its greatly appreciated!!!
Click to expand...
Click to collapse
Well, firstly, you need to unlock its bootloader IMMEDIATELY then you can try other action (reflash stock roms, etc..). Using Myth Tools is recommended in the post above.
After unlocking bootloader, you can try to download stock firmware from here:
Then flash it with Myth Tools (recommend) or RSDLite
If you satisfy with stock one, just keep it and do further mods or you can flash custom recovery before flashing custom roms.
That's my recommendation but you need to do the FIRST step is Unlocking Bootloader right now
Hope it helps.
DK
I can't even root it, the phone shuts off if disconnected from a charger. And even when on the charger it keeps boot looping.
Sent from my GT-N7105 using Tapatalk
jrodbrown58 said:
I can't even root it, the phone shuts off if disconnected from a charger. And even when on the charger it keeps boot looping.
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
The boot looping which you mean is going to the fastboot mode, right?
Did you try to enter bootmenu (turn off phone, hold both vol + and vol - then press press powermenu to turn on) and select "normal powerup"?
Can you tell me whether your phone has ATT logo on its screen's bottom?
Maybe flashing back to its correct original firmware by RSDLite can help to bring it back then we can root and unlock bootloader.
But we need to know exactly which is its original firmware before it stucks there.
I've got it fixed...turns out the battery was bad. So luckily I switched it out with an atrix HD with a broken screen we had and it booted right up so I rooted, unlocked the bootloader and flashed the stock logo and a custom ROM. All smiles now! Thanks for everyone's help!
Sent from my GT-N7105 using Tapatalk
Congrats!
devilsking said:
The boot looping which you mean is going to the fastboot mode, right?
Did you try to enter bootmenu (turn off phone, hold both vol + and vol - then press press powermenu to turn on) and select "normal powerup"?
Can you tell me whether your phone has ATT logo on its screen's bottom?
Maybe flashing back to its correct original firmware by RSDLite can help to bring it back then we can root and unlock bootloader.
But we need to know exactly which is its original firmware before it stucks there.
Click to expand...
Click to collapse
Having a issue with bootlooping, I unlocked the bootloader. I tried to install stock firmware but the phone doesnt even get past the motorola symbol it justs goes blank that tries to boot again. I can get it in to fastboot though. Its ATT version, is there anyway I can fix it?
Did Myth complete the flashing process? Have you tried using RSD lite to flash stock?
PCiE said:
Having a issue with bootlooping, I unlocked the bootloader. I tried to install stock firmware but the phone doesnt even get past the motorola symbol it justs goes blank that tries to boot again. I can get it in to fastboot though. Its ATT version, is there anyway I can fix it?
Click to expand...
Click to collapse
do you install custom roms before flashing stock firmware?
devilsking said:
do you install custom roms before flashing stock firmware?
Click to expand...
Click to collapse
you thinking it's the internal sd crap too...
devilsking said:
do you install custom roms before flashing stock firmware?
Click to expand...
Click to collapse
No
think im bootlooped after changing a digitizer
Someone in a club that i am in ask if anyone fixed phones, I'm a hobbyist, but very good with hardware and worked on countless ipods, tablets, Iphones, you name it. Some of you guys are like GOD MODE ON but i get buy, and really was just trying to help someone. (i haven't even cashed her check) so i tell her hey 15 bucks a phone i'll change the glass if you buy the parts.. grrr my mistake. i got this atrix hd. all i did was change the digitizer and now it hangs at the at&T screen... i tried RSD and flashed successfully, i tried myth and flashed successfully. i have no idea whats wrong with this POS.. i can get in fast boot and recovery ok. Does this phone need a sim in for first boot? i'm loosing my mind, i can't help but wonder if it's the new chinese digitizer, I wish i could get a system log outta this thing to see how it's hanging up.... any help would be greatly appreciated.
fudpucker said:
Someone in a club that i am in ask if anyone fixed phones, I'm a hobbyist, but very good with hardware and worked on countless ipods, tablets, Iphones, you name it. Some of you guys are like GOD MODE ON but i get buy, and really was just trying to help someone. (i haven't even cashed her check) so i tell her hey 15 bucks a phone i'll change the glass if you buy the parts.. grrr my mistake. i got this atrix hd. all i did was change the digitizer and now it hangs at the at&T screen... i tried RSD and flashed successfully, i tried myth and flashed successfully. i have no idea whats wrong with this POS.. i can get in fast boot and recovery ok. Does this phone need a sim in for first boot? i'm loosing my mind, i can't help but wonder if it's the new chinese digitizer, I wish i could get a system log outta this thing to see how it's hanging up.... any help would be greatly appreciated.
Click to expand...
Click to collapse
What ROM was on there before you changed the digitizer? Have you tried flashing a custom recovery and a custom ROM?
fudpucker said:
Someone in a club that i am in ask if anyone fixed phones, I'm a hobbyist, but very good with hardware and worked on countless ipods, tablets, Iphones, you name it. Some of you guys are like GOD MODE ON but i get buy, and really was just trying to help someone. (i haven't even cashed her check) so i tell her hey 15 bucks a phone i'll change the glass if you buy the parts.. grrr my mistake. i got this atrix hd. all i did was change the digitizer and now it hangs at the at&T screen... i tried RSD and flashed successfully, i tried myth and flashed successfully. i have no idea whats wrong with this POS.. i can get in fast boot and recovery ok. Does this phone need a sim in for first boot? i'm loosing my mind, i can't help but wonder if it's the new chinese digitizer, I wish i could get a system log outta this thing to see how it's hanging up.... any help would be greatly appreciated.
Click to expand...
Click to collapse
There's a chance that it could be the digitizer. About a week ago I replaced my Dad's digitizer and I read a crap ton of reviews before purchasing the one I did. Of the bad ones, a few had people complaining about it not working, most were the top 10% of the screen wouldn't respond to touches (like swiping down the nonfiction drawer), and I saw a couple describing your situation.
If you never had a custom rom installed, were rooted, or had the bootloader unlocked before doing this, I doubt that there's anything you can flash that'll fix this. If the bootloader was unlocked before doing this and there was a custom rom installed on the phone, you might have to flash Philz CWM, format the internal sd, and change its mount point to /data/media then format it again. Not changing the internal sd mount point after flashing a fastboot when coming from custom 4.2+ roms causes bootloops.
This is the digitizer I used to fix my Dad's Atrix HD last week. He hasn't had a problem with it whatsoever. My Dad is an ass of the highest degree so I'd know with a loud angry voice if there was ANY minor issue with it.
AT&T splash screen stuck after chinese digitizer install
skeevydude said:
There's a chance that it could be the digitizer. About a week ago I replaced my Dad's digitizer and I read a crap ton of reviews before purchasing the one I did. Of the bad ones, a few had people complaining about it not working, most were the top 10% of the screen wouldn't respond to touches (like swiping down the nonfiction drawer), and I saw a couple describing your situation.
If you never had a custom rom installed, were rooted, or had the bootloader unlocked before doing this, I doubt that there's anything you can flash that'll fix this. If the bootloader was unlocked before doing this and there was a custom rom installed on the phone, you might have to flash Philz CWM, format the internal sd, and change its mount point to /data/media then format it again. Not changing the internal sd mount point after flashing a fastboot when coming from custom 4.2+ roms causes bootloops.
Click to expand...
Click to collapse
Ok so there are multiple questions to answer here.
#1 i do not recall which rom was on the phone.. although it appears it was the lastest AT&T as RSD re-Flashed it with a pass. I suppose i should have checked but i've never ran in to this situation. I was just changing the glass out.... you remove about 16 screws, pop the glass out and put a new one it...
#2 the customer does not want the phone rooted or moded, just stock
#3 the bootloader is locked and mythtool instructions are saying you have to be in debugging mode to unlock.... thats not gonna happen cause it don't boot..
So does anyone know if this thing needs a sim for a first boot after an actuall battery pull?
Also..
I unplugged the digitizer and tried to boot thinking hey other phones will boot without the digitizer, but same thing... AT&T Screen and it's hung. everything on this board is shielded.. so i doubt it got ESD zapped, and i did take static potective precautions.
I bet this thing would look good with a .45cal hole in it.
fudpucker said:
Ok so there are multiple questions to answer here.
#1 i do not recall which rom was on the phone.. although it appears it was the lastest AT&T as RSD re-Flashed it with a pass. I suppose i should have checked but i've never ran in to this situation. I was just changing the glass out.... you remove about 16 screws, pop the glass out and put a new one it...
#2 the customer does not want the phone rooted or moded, just stock
#3 the bootloader is locked and mythtool instructions are saying you have to be in debugging mode to unlock.... thats not gonna happen cause it don't boot..
So does anyone know if this thing needs a sim for a first boot after an actuall battery pull?
Also..
I unplugged the digitizer and tried to boot thinking hey other phones will boot without the digitizer, but same thing... AT&T Screen and it's hung. everything on this board is shielded.. so i doubt it got ESD zapped, and i did take static potective precautions.
I bet this thing would look good with a .45cal hole in it.
Click to expand...
Click to collapse
#1 That's what I'd assume...and it's 22 screws with fine threading... And if you're getting the AT&T boot logo after a fastboot flash, the bootloader is locked.
#2 Customer's loss
#3 Never actually tested that, but I've never once needed a sim for it to boot up....actually, my first boot ever might have been sim free...been a year now so I'm not really sure.
And I didn't take static precautions.
You didn't accidentally warp or mess up the motherboard on the blow dryer part of the digitizer swap? Or any unnecessary bending on the board with you were prying the screen from it? Those two are the only "dangerous" parts in any Atrix HD repair...unless someone isn't steady with a screwdriver, then there are 46 "dangerous" parts to the repair.
Next time you power up the phone, hold down both volumes and power to access the boot menu. Use volume down to scroll to recovery and volume up to select it. Once in recovery, do a factory reset as well as any cache or dalvik wipes available. If a fastboot flash and all the wipes in stock recovery don't fix it, I'm not really sure what will aside from a new motherboard -- in which case you're better off spending an extra 20-30 and just getting a used Atrix HD like I did....I mean, 50 for just a motherboard or 80 for the all the hardware plus accessories...not really a hard choice seeing as the customer will at least have some backup repair parts in case something bad happens in the future.
Stock recovery is worthless
skeevydude said:
#1 That's what I'd assume...and it's 22 screws with fine threading... And if you're getting the AT&T boot logo after a fastboot flash, the bootloader is locked.
did the factory reset and delete cache.. stock recovery doesn't give an option for dalvik cache... can you flash phills with a locked bootloader?
Click to expand...
Click to collapse
fudpucker said:
skeevydude said:
#1 That's what I'd assume...and it's 22 screws with fine threading... And if you're getting the AT&T boot logo after a fastboot flash, the bootloader is locked.
did the factory reset and delete cache.. stock recovery doesn't give an option for dalvik cache... can you flash phills with a locked bootloader?
Click to expand...
Click to collapse
I wouldn't use Philz until you unlock the bootloader.
Click to expand...
Click to collapse
fudpucker said:
skeevydude said:
#1 That's what I'd assume...and it's 22 screws with fine threading... And if you're getting the AT&T boot logo after a fastboot flash, the bootloader is locked.
did the factory reset and delete cache.. stock recovery doesn't give an option for dalvik cache... can you flash phills with a locked bootloader?
Click to expand...
Click to collapse
The only thing you can flash with a locked bootloader is your stock rom with fastboot. That's it. When locked, if manually flashing all the partitions, flashing with RSD, wiping everything that can be wiped, and you're still not booting, then the phone is either truly bricked or you're not doing something correctly.
The only exception to the above is if something went bad during the OTA and you have some sort of partition mix up, in which case the official fastboot for the OTA might fix it for you -- there isn't a stock fastboot for the OTA yet.
Click to expand...
Click to collapse
Hello my fellow friends in HTC Desire 626s Metro PCs land.
This is Isaiah speaking. I've run into a little misfortune here and I wanted to know if someone would be kind enough to help me out.
I have seemed to get myself in a little snag, were for some reason after I relock my phone, it won't reboot the system. What happens is, it boots right into download mode. So I unlocked it again and guess what. Everything booted normally.
Then I go to unlock it again, it jumps right back to download mode. I'm going bonkers over here, like Willy Wonka bonkers because i can't figure out why I can't relock my phone without it going right back to download mode. I flashed stock recovery through cmd, before I relocked it, that didn't work. All I did was root my phone. No debloated roms or anything. Just simply rooted my phone. I'm on Android 6.0.1. Somebody will you please help me get back to stock. Sigh, momma told there'd be days like this! Lol!!! I had to throw in a little humor.
I had the exact same problem. I found a possible fix. If you are just trying to get back to the recovery area.
Press and hold the power and volume down keys then release the power.
Once on the download mode screen scroll to Reboot to bootloader
Once in the bootloader area select Reboot to recovery mode.
This is the only way I can get to recovery mode.
Ace18o said:
I had the exact same problem. I found a possible fix. If you are just trying to get back to the recovery area.
Press and hold the power and volume down keys then release the power.
Once on the download mode screen scroll to Reboot to bootloader
Once in the bootloader area select Reboot to recovery mode.
This is the only way I can get to recovery mode.
Click to expand...
Click to collapse
What i'm trying to do is actually get back to the stock recovery so that I can re-flash the official ruu file from the official HTC Roms Website because my phone has not been running smoothly on the ota update they sent out in July. I figured since the the sites ruu file is 1.32gb and the actual ota update was 845mb, may-be there's something in the ruu that will fix this issue.
I already tried unrooting it by flashing stock recovery through command prompt then going back and re-locking my device. But after I re-locked my phone, instead of it rebooting normally where it goes to the boot animation, then loads the welcome screen to allow you to go through putting your wifi info and email address etc. It returns to download mode, or boot loader mode. Then every time I restart my phone it does the same thing and it goes back to the same screen. But when I re-unlock it, it boots fine.
s3llz said:
What i'm trying to do is actually get back to the stock recovery so that I can re-flash the official ruu file from the official HTC Roms Website because my phone has not been running smoothly on the ota update they sent out in July. I figured since the the sites ruu file is 1.32gb and the actual ota update was 845mb, may-be there's something in the ruu that will fix this issue.
I already tried unrooting it by flashing stock recovery through command prompt then going back and re-locking my device. But after I re-locked my phone, instead of it rebooting normally where it goes to the boot animation, then loads the welcome screen to allow you to go through putting your wifi info and email address etc. It returns to download mode, or boot loader mode. Then every time I restart my phone it does the same thing and it goes back to the same screen. But when I re-unlock it, it boots fine.
Click to expand...
Click to collapse
Ahh my bad, I was very tired last night.
s3llz said:
What i'm trying to do is actually get back to the stock recovery so that I can re-flash the official ruu file from the official HTC Roms Website because my phone has not been running smoothly on the ota update they sent out in July. I figured since the the sites ruu file is 1.32gb and the actual ota update was 845mb, may-be there's something in the ruu that will fix this issue.
I already tried unrooting it by flashing stock recovery through command prompt then going back and re-locking my device. But after I re-locked my phone, instead of it rebooting normally where it goes to the boot animation, then loads the welcome screen to allow you to go through putting your wifi info and email address etc. It returns to download mode, or boot loader mode. Then every time I restart my phone it does the same thing and it goes back to the same screen. But when I re-unlock it, it boots fine.
Click to expand...
Click to collapse
Just don't lock the boot loader, I didn't lock my boot loader to run the RUU. My phone was running the firmware that if came with and I had unlocked the boot loader, flashed TWRP, and rooted. All I did was flash the stock recovery then ran the RUU(it didn't work turned off so I booted into fastboot) and it updated.
Problem solved
IsaacGuti said:
Just don't lock the boot loader, I didn't lock my boot loader to run the RUU. My phone was running the firmware that if came with and I had unlocked the boot loader, flashed TWRP, and rooted. All I did was flash the stock recovery then ran the RUU(it didn't work turned off so I booted into fastboot) and it updated.
Click to expand...
Click to collapse
Thank you so much for your advice. It worked like a charm. Consider this case closed. I downloaded the official ruu file for my particular carrier and left the boot loader unlocked, but installed the stock recovery through command prompt. Then, I connected my device to my pc via usb as instructed through the ruu. Then, zing.....watched it zap my phone with the stock rom of 6.0.1. Solved my lagging issues as well as my network switching issues as well. For some strange reason, my device kept switching between different carriers which caused me not to be able to sent text messages. I was like "What in the Doc Brown Marty McFly is going on here!!!" Had me like Doc Brown "Great Scott!!!!" LOL!! Thanks buddy for your advice though. Problem Solved.:good::highfive::victory::victory:
s3llz said:
Thank you so much for your advice. It worked like a charm. Consider this case closed. I downloaded the official ruu file for my particular carrier and left the boot loader unlocked, but installed the stock recovery through command prompt. Then, I connected my device to my pc via usb as instructed through the ruu. Then, zing.....watched it zap my phone with the stock rom of 6.0.1. Solved my lagging issues as well as my network switching issues as well. For some strange reason, my device kept switching between different carriers which caused me not to be able to sent text messages. I was like "What in the Doc Brown Marty McFly is going on here!!!" Had me like Doc Brown "Great Scott!!!!" LOL!! Thanks buddy for your advice though. Problem Solved.:good::highfive::victory::victory:
Click to expand...
Click to collapse
By any chance, do you have the stock recovery link? I'm having the same issue :/
Sharkyzz said:
By any chance, do you have the stock recovery link? I'm having the same issue :/
Click to expand...
Click to collapse
I will upload it so that you can dowload it. Make sure when you go in to command prompt that you type exactly what it says "Stock_Recovery.img" without the parenthesis of course. Thats what i had to do. it will look like this when you type it in "fastboot flash recovery Stock_Recovery.img"
Link below.
https://drive.google.com/file/d/0ByVHpaOig07QT1hfUmY4bkZrbGs/view?usp=sharing
s3llz said:
I will upload it so that you can dowload it. Make sure when you go in to command prompt that you type exactly what it says "Stock_Recovery.img" without the parenthesis of course. Thats what i had to do. it will look like this when you type it in "fastboot flash recovery Stock_Recovery.img"
Link below.
https://drive.google.com/file/d/0ByVHpaOig07QT1hfUmY4bkZrbGs/view?usp=sharing
Click to expand...
Click to collapse
PS. Also, when I used the Rom update utility it failed once. But if you look carefully at the picture instructions on the screen, it tells you to unplug your usb cable and pull out the battery. But of course we both know we can't take out the battery. So what you do is, just unplug the usb, but don't restart your phone. Leave it on the screen where it stopped on. When you get to the screen where it tells you to plug your usb back in, then you plug it back in. After that, you just follow the instructions on the screen of the ruu, and it will begin flashing your device with the stock rom. That was the step I kept missing. To unplug the usb and then plug it back in when the ruu says to.
s3llz said:
I will upload it so that you can dowload it. Make sure when you go in to command prompt that you type exactly what it says "Stock_Recovery.img" without the parenthesis of course. Thats what i had to do. it will look like this when you type it in "fastboot flash recovery Stock_Recovery.img"
Link below.
https://drive.google.com/file/d/0ByVHpaOig07QT1hfUmY4bkZrbGs/view?usp=sharing
Click to expand...
Click to collapse
PS. Also, when I used the Rom update utility it failed once. But if you look carefully at the picture instructions on the screen, it tells you to unplug your usb cable and pull out the battery. But of course we both know we can't take out the battery. So what you do is, just unplug the usb, but don't restart your phone. Leave it on the screen where it stopped on. When you get to the screen where it tells you to plug your usb back in, then you plug it back in. After that, you just follow the instructions on the screen of the ruu, and it will begin flashing your device with the stock rom. That was the step I kept missing. To unplug the usb and then plug it back in when the ruu says to.