Related
so I rooted my Atrix HD (running 4.1.1) and decided to flash a custom ROM, so after installing a recovery and downloading a ROM I wanted, I flashed it.
problem is, I forgot to unlock the bootloader
after I flashed the ROM, I rebooted the phone and it booted into AP Fastboot
I tried using RSD Tool to flash the 4.1.1 firmware I found at sbf.droid-developers but it fails and says "Failed flashing process. Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL; phone connected"
I already edited the xml file and removed the two lines containing max-download-size
also it says low battery on the Fastboot screen and I assume it's not charging at all when plugged in on the Fastboot screen so this may be a problem in the very near future or may already be a problem
am I totally screwed? how can I fix this?
buttwhole said:
so I rooted my Atrix HD (running 4.1.1) and decided to flash a custom ROM, so after installing a recovery and downloading a ROM I wanted, I flashed it.
problem is, I forgot to unlock the bootloader
after I flashed the ROM, I rebooted the phone and it booted into AP Fastboot
I tried using RSD Tool to flash the 4.1.1 firmware I found at sbf.droid-developers but it fails and says "Failed flashing process. Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL; phone connected"
I already edited the xml file and removed the two lines containing max-download-size
also it says low battery on the Fastboot screen and I assume it's not charging at all when plugged in on the Fastboot screen so this may be a problem in the very near future or may already be a problem
am I totally screwed? how can I fix this?
Click to expand...
Click to collapse
I had the exact same problem, I could not get it to work no matter what I did, I finally got it working by using MythTools http://forum.xda-developers.com/showthread.php?t=2262726 That ones recovery got it working for me, I hope you can get it fixed, but don't give up, it took me about 6-7 hours before I fixed it lol, I ended up flashing stock ICS and then it finally came back for me.
And no, it does not charge in fastboot, or at least it doesn't seem to, and battery seems to drain rapidly, I'd say let it charge on USB for a while while it's off and start trying again
Silentwidow said:
I had the exact same problem, I could not get it to work no matter what I did, I finally got it working by using MythTools http://forum.xda-developers.com/showthread.php?t=2262726 That ones recovery got it working for me, I hope you can get it fixed, but don't give up, it took me about 6-7 hours before I fixed it lol, I ended up flashing stock ICS and then it finally came back for me.
And no, it does not charge in fastboot, or at least it doesn't seem to, and battery seems to drain rapidly, I'd say let it charge on USB for a while while it's off and start trying again
Click to expand...
Click to collapse
tried this, doesn't work
still fails to boot (Fastboot Reason: Boot Failure)
whenever I plug it in it automatically turns on and goes to Fastboot so I can't charge it with the screen off
buttwhole said:
tried this, doesn't work
still fails to boot (Fastboot Reason: Boot Failure)
whenever I plug it in it automatically turns on and goes to Fastboot so I can't charge it with the screen off
Click to expand...
Click to collapse
a couple more details
I tried this with both 4.0.4 and 4.1.1
the tool extracts them, asks me if I'm ready to flash, I say yes, then it asks me if I'm in normal mode or fastboot mode to which I answer fastboot
the only difference between 4.0.4 and 4.1.1 is at this point on 4.0.4 it asks me if I'm flashing 4.0.4 ICS
after that it says "Starting flash process..." and reboots my phone into fastboot again (and it lists the fastboot reason as sticky bit instead of boot failure)
and stays on this for about a minute, then asks if I want to use stock or CWM recovery (stock), then it says flashing stock and it reboots my device...
...which reboots back into fastboot with reason listed as boot failure
also I tried following /showthread.php?t=2231249 to a T but the same thing that I described in the OP happened
Did you try to flash system using fast boot?
Sent from my MB886 using xda premium
ai6908 said:
Did you try to flash system using fast boot?
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
no, I just tried with RSD and Myth Tools
edit- I tried flashing with fastboot and it failed because the battery is too low
I ordered a factory cable and will report back when that gets here
I got my fastboot cable today. flashed 4.1.1 with RSD, no problems encountered
feels good having a working phone again
now I can add this fastboot cable to my collection of stuff I had to buy when I ****ed up big (my Galaxy S download mode jig comes to mind)
edit- so frustrating
the AOKP ROM I want to use is laggy in general use
the CM10.1 and PACman ROMs I tried are a lot smoother but aren't as customizable
buttwhole said:
I got my fastboot cable today. flashed 4.1.1 with RSD, no problems encountered
feels good having a working phone again
now I can add this fastboot cable to my collection of stuff I had to buy when I ****ed up big (my Galaxy S download mode jig comes to mind)
edit- so frustrating
the AOKP ROM I want to use is laggy in general use
the CM10.1 and PACman ROMs I tried are a lot smoother but aren't as customizable
Click to expand...
Click to collapse
Yea the CM10.1 skrillex night isn't bad, but the camcorder doesn't work, I personally am going to Mexico Retail and just wiping out a bunch of system apps and replacing the 4.1 apps with 4.2.
Silentwidow said:
Yea the CM10.1 skrillex night isn't bad, but the camcorder doesn't work, I personally am going to Mexico Retail and just wiping out a bunch of system apps and replacing the 4.1 apps with 4.2.
Click to expand...
Click to collapse
gl
buttwhole said:
gl
Click to expand...
Click to collapse
Wasn't too bad, I have it running right now, ended up using ATT retail instead, just because of the "LTE" on the 4g symbol(I know!), but I pretty much wiped out all Motorola apps and deodexed it, runs smooth without issue, and it's fast, but I really want the Tablet UI!
Search for Tablet UI...see below thread as well...
http://forum.xda-developers.com/showthread.php?p=38670671
Have a NAND backup before you use this...
If you end up doing this, please report your results and any issues you run into. I have tried some tablet ui stuff(roms that offer it) and haven't found a huge value in doing it...
Though, a full fledged tablet UI would be cool to try out. I'll probably end up trying it at some point, but if you take a first stab, any tips/tricks with what you did would be helpful.
thanks!
Maam.
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
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
Hey, was just setting up my mi5 for custom roms. Got the bootloader unlocked, then installed TWRP via fastboot as per the instructions here (https://twrp.me/devices/xiaomimi5.html).
After I got into TWRP I made a quick backup of the image, and then set the phone to reboot. Now its in a bootloop, flashing the mi logo (and bootloader unlock on the bottom). Doesn't turn off, doesn't do anything when plugged into pc, fastboot reboot doesn't do anything.
Any ideas? Didn't think I had done anything wrong (done this kind of thing a couple times before).
Cheers!
EDIT: Hang on, managed to get into fastboot, I guess I should be able to sort things out from there? What should I aim to do. I can also get into recovery. Still won't boot into system anymore though.
flobbadob said:
Hey, was just setting up my mi5 for custom roms. Got the bootloader unlocked, then installed TWRP via fastboot as per the instructions here (https://twrp.me/devices/xiaomimi5.html).
After I got into TWRP I made a quick backup of the image, and then set the phone to reboot. Now its in a bootloop, flashing the mi logo (and bootloader unlock on the bottom). Doesn't turn off, doesn't do anything when plugged into pc, fastboot reboot doesn't do anything.
Any ideas? Didn't think I had done anything wrong (done this kind of thing a couple times before).
Cheers!
EDIT: Hang on, managed to get into fastboot, I guess I should be able to sort things out from there? What should I aim to do. I can also get into recovery. Still won't boot into system anymore though.
Click to expand...
Click to collapse
Which twrp version are you using?
Did you actually flash any custom rom or do you try to start miui?
Did you change any partition?
Something similar happened to me one time. I solved it by doing the root right after installing the twrp. And magically started my rom.
lanceindie said:
Something similar happened to me one time. I solved it by doing the root right after installing the twrp. And magically started my rom.
Click to expand...
Click to collapse
+1! Thanks :highfive:
Did you solve it? I might have some ideas.
Have tried flashing various miui and a few custom roms, all get stuck on animation. Have tried miui fastboot roms first build and latest, pretty much everything I can think of to no avail. Am I missing something? Open to any suggestions to get this phone working again. Fastboot and recovery (custom and stock) all work, flashing works it just won't get past that loading screen.
hoopsnake said:
Have tried flashing various miui and a few custom roms, all get stuck on animation. Have tried miui fastboot roms first build and latest, pretty much everything I can think of to no avail. Am I missing something? Open to any suggestions to get this phone working again. Fastboot and recovery (custom and stock) all work, flashing works it just won't get past that loading screen.
Click to expand...
Click to collapse
If flashing a fastboot ROM isn't working, then maybe something physically has gone wrong with the phone. Are you using the clean all or the keep data option, when flashing? Make sure you're using the clean all option (but definitely not the clean and lock option).
Fastboot ROMs are normally the last resort, failsafe way to recover the phone, so it's unusual for them not to work.
Also how long are you waiting at the initial animation screen?
Also try a different, good quality USB lead and/or a different USB port and/or a different PC if you can.
Robbo.5000 said:
If flashing a fastboot ROM isn't working, then maybe something physically has gone wrong with the phone. Are you using the clean all or the keep data option, when flashing? Make sure you're using the clean all option (but definitely not the clean and lock option).
Fastboot ROMs are normally the last resort, failsafe way to recover the phone, so it's unusual for them not to work.
Also how long are you waiting at the initial animation screen?
Also try a different, good quality USB lead and/or a different USB port and/or a different PC if you can.
Click to expand...
Click to collapse
Something more than likely broke hardware wise.
Always clean all, but unfortunately after many hours of trying I misclicked and locked a few hours ago, on the stock rom but which would of been lucky if I wasn't already stuck in bootloop.
Next option, took back panel off and had a look, red water indicator near headphone jack, the rest are still white so many some sort of water damage has happened idk how, everything else is clean and dry.
Next best bet is edl with a authorized mi account (no luck yet) or just ship it off to Xiaomi.
Umm, what did you do before you got this problem?
tbh, most users just skip a step and then nothing works. I'm assuming this is the case?
What is your phone variant? previous ROM? ROM you tried to apply?
what vendor are you using? and most importantly, what steps are you doing to flash the new rom.
Sandeeep Kiran said:
Umm, what did you do before you got this problem?
tbh, most users just skip a step and then nothing works. I'm assuming this is the case?
What is your phone variant? previous ROM? ROM you tried to apply?
what vendor are you using? and most importantly, what steps are you doing to flash the new rom.
Click to expand...
Click to collapse
Literally nothing, flashed global stable zip a week before with f2fs, and dfe, it was about a week without modifying anything or even entering twrp and it just did a random reboot then just died and started boot looping.
K20 Pro, previous was lineage os, format data to get back to miui, flash miui, f2fs, dfe.
Now since bootloop, and edl, fastboot, recovery all work but with locked bootloader, I guess only option is edl flash.
My mi account must be magic or something, so downloaded mi unlock and bootloader unlocked immediately, no wait time. Was very surprised so to double check did fastboot OEM device-info and indeed bootloader is unlocked. Now flashing fastboot rom fingers crossed.
IT BOOTED, I have my phone backkkkkk. No idea how or what happened, happened but it's back up and running hopefully for good.
Somehow locking and unlocking bootloader fixed it.