Please Help!
Yesterday, my Milestone crashed while using the camera, tried to reboot and got stuck at the M logo.
I CAN NOT access recovery, it sticks at the M logo.
Tried reflashing using RSDLite using both Service and Non-Service ROMS, it appears to work OK, gets to where the phone reboots, the phone stays at the M logo and RSDLite says manually reboot phone. If I reboot to bootloader mode, RSDLite says PASS, but rebooting the phone stays at the M logo.
I was running GOT's SHOLS_U2_02.36.0, Rooted, Overclock (800mhz), Memhack.
I also tried reflashing the bootloader, both 90.73 (my original), also 90.78 (just in case the camera button was broken and was the reason I couldn't access recovery). Same result, stuck at M logo.
Also, if I plug the Milestone into the Wall charger, it sticks at the M logo, I don't get the recharging logo.
I have also tried reflashing the both the SIM card and SDCard removed, still stuck at the M logo and cant get to recovery.
Please help, if anyone has any ideas, this is driving me absolutely crazy.
Hi there,
I got this problem when I flashing the milestone back to offical ROMs using RSD method. Also stuck at the M logo no matter uplung the battery or using the recovery mode.
I solved this by wipe the data and cache in the recovery mode then reboot.......everything works fine. Hope this help!!
sunnylai01 said:
Hi there,
I got this problem when I flashing the milestone back to offical ROMs using RSD method. Also stuck at the M logo no matter uplung the battery or using the recovery mode.
I solved this by wipe the data and cache in the recovery mode then reboot.......everything works fine. Hope this help!!
Click to expand...
Click to collapse
Thanks for the info, but my problem is I can not get into recovery to wipe data and cache. Everytime I try to boot into recovery, it just gets stuck at the M logo.
Did you mean when you plug the battery in,it bootup automatically?
If so, press the carmera button before you plug the battery in,it will boot into recovery mode.
Hope this help.
sunnylai01 said:
Did you mean when you plug the battery in,it bootup automatically?
If so, press the carmera button before you plug the battery in,it will boot into recovery mode.
Hope this help.
Click to expand...
Click to collapse
When I put it the battery, it tries to boot automatically. I had already tried what you suggested, that's the method I can use to access the bootloader menu for flashing. Also, if you pull out the SIM card, the phone doesn't automatically start to boot, I tried that method with power and camera buttons, but didn't work either.
No matter what I try, it won't let me boot into recovery mode. I am sure that if I could access recovery mode, I could wipe data and davlik cache and this would fix my problem.
The only thing I can access is the Bootloader menu (power switch and Up on the keyboard) for flashing with RSDLite.
I am having this problem too. Is there a true fix for this???
Did you tried starting the milestone without battery? When the great battery appears you can put the battery in and let it charge.
I don't have a problem with the battery as i was able to fully charge it. I've tried every thing that i can flash to try to bring it back to life to no avail. Can't get to recovery either. I keep seeing a bunch of people saying that re-flashing it back to stock would un-brick this, but i am starting to think i have a brick.
BTW i have a Telus Milestone.
Maybe the case you have upgraded bootloader?
Have you already tried to flash only the vulnerable recovery and then try to boot in recovery mode?
pippocannelunghe said:
Maybe the case you have upgraded bootloader?
Have you already tried to flash only the vulnerable recovery and then try to boot in recovery mode?
Click to expand...
Click to collapse
I have bootloader 90.78. And yes i have tried the vulnerable recovery. When i try to boot to recovery mode it just sits at a blank screen and reboots back to the moto logo.
I believe it is next to impossible to brick a Milestone as we can't touch anything along the bootline.
DannyDroid said:
I believe it is next to impossible to brick a Milestone as we can't touch anything along the bootline.
Click to expand...
Click to collapse
Everytime i flash the Telus SBF it shows that it finished sucessfully but after it reboots it goes back to the Bootloader 90.78 screen.
I've even tried flashing different sbfs and the same result.
cheerup38 said:
I am having this problem too. Is there a true fix for this???
Click to expand...
Click to collapse
I eventually fixed this by flashing a rom with a diferent baseband. My milestone is a UK model, when I tried flasing the GOT 2.2 for telsus, it actually worked, then I reflashed a UK rom.
I don't know why that worked, maybe I had a corruption is the baseband files, but if that was the case, flashing a uk rom should of worked also.
Hope you get yours going again.
jason600 said:
I eventually fixed this by flashing a rom with a diferent baseband. My milestone is a UK model, when I tried flasing the GOT 2.2 for telsus, it actually worked, then I reflashed a UK rom.
I don't know why that worked, maybe I had a corruption is the baseband files, but if that was the case, flashing a uk rom should of worked also.
Hope you get yours going again.
Click to expand...
Click to collapse
Yeah, i saw your solution on another forum, i tried that and no go. its getting frustrating.
Hy,
This seems a little odd,but at least it's an idea:
Unplug the battery and leave it unplugged for at least one hour. In the meantime(battery still unplugged) press the power button for 5-10 secs or so...this guarantees that there will be no current left on the phone...after the hour,try to reboot and keep the fingers crossed..i know this sounds stupid,but at least give it a try
Good luck!
Sent from my Milestone
cheerup38 said:
Everytime i flash the Telus SBF it shows that it finished sucessfully but after it reboots it goes back to the Bootloader 90.78 screen.
I've even tried flashing different sbfs and the same result.
Click to expand...
Click to collapse
Just to clarify, after you've flashed it boots straight into the bootloader? Does you get any type of error message such as code corrupt or a string of hex codes?
Are you trying to flash 2.1 or 2.2 or have you tried both?
When my was bricked, flashing 2.1 would boot to the m logo and sit there forever. Flashing 2.2 would boot to the m logo, stay there for maybe 30 seconds, then reboot and repeat. It was the diferent effects of flashing the two versions that lead me to try diferent basebands. Also, I'm pretty sure that I tried flashing diferent basebands for 2.1 without it working.
Also, what happens when you plug into the wall charger? Do you get the battery graphic or does it stick at the m logo?
jason600 said:
Just to clarify, after you've flashed it boots straight into the bootloader? Does you get any type of error message such as code corrupt or a string of hex codes?
Are you trying to flash 2.1 or 2.2 or have you tried both?
When my was bricked, flashing 2.1 would boot to the m logo and sit there forever. Flashing 2.2 would boot to the m logo, stay there for maybe 30 seconds, then reboot and repeat. It was the diferent effects of flashing the two versions that lead me to try diferent basebands. Also, I'm pretty sure that I tried flashing diferent basebands for 2.1 without it working.
Also, what happens when you plug into the wall charger? Do you get the battery graphic or does it stick at the m logo?
Click to expand...
Click to collapse
After the flash it goes straight back to the bootloader screen and with a string of hex codes: a5,69,35,00,27
I've flashed both 2.1 & 2.2 sbfs. Same thing happens after each flash, nothing different like you mentioned. So i can't really narrow it down.
I do not get a battery graphic when i plug in the wall charger, it goes from the moto logo to the bootloader 90.78 screen and then reboots. it probably does this about 5 times and then turns off.
cheerup38 said:
After the flash it goes straight back to the bootloader screen and with a string of hex codes: a5,69,35,00,27
I've flashed both 2.1 & 2.2 sbfs. Same thing happens after each flash, nothing different like you mentioned. So i can't really narrow it down.
I do not get a battery graphic when i plug in the wall charger, it goes from the moto logo to the bootloader 90.78 screen and then reboots. it probably does this about 5 times and then turns off.
Click to expand...
Click to collapse
That code is for a bad flash. See this link on android-hilfe.de (its german, link is with google translate), scroll down to lesson 9:
http://translate.googleusercontent....&twu=1&usg=ALkJrhhoVzir_DtnGt57By9kO93AsPmS8g
Try flashing with diferent versions of RSDLite. Re-install usb drivers, try flashing from a different PC, make sure your flashing NON-SERVICE sbf's.
Hope this helps
jason600 said:
That code is for a bad flash. See this link on android-hilfe.de (its german, link is with google translate), scroll down to lesson 9:
http://translate.googleusercontent....&twu=1&usg=ALkJrhhoVzir_DtnGt57By9kO93AsPmS8g
Try flashing with diferent versions of RSDLite. Re-install usb drivers, try flashing from a different PC, make sure your flashing NON-SERVICE sbf's.
Hope this helps
Click to expand...
Click to collapse
Oh ok, i will try this, Thanks.
cheerup38 said:
Oh ok, i will try this, Thanks.
Click to expand...
Click to collapse
Also, redownload your your sbf files, the one your flashing might be corrput.
Related
So right now, my phone keeps on getting stuck at the 'android' word bootscreen. It keeps repeating and seems to go on forever! Someone please help me! I heard its due to rooting! Can anyone confirm this?
What did you do? I tried once to install aps 2 card and the phone stood in android screen about 20 min
Anyway if it doesn't start. Flash new android: nand restore or sbf
.
Sent from my Milestone using Tapatalk
Finally somebody replied back. Its been going on for days, I've removed the battery, placed it back, same thing.
Also, sorry but I have no idea how to flash something. How do I do it? And it doesn't even go past it.
I should spend on time in this sub-forum.
If you have flash a custom ROM then just reflash it or try another ROM.
It's highly, highly unlikely that your phone it breaked so don't worry about.
I have never flashed a custom rom. I don't even know how to flash in the first place.
turn off hp.try to hold up-dpad(towards screen) button and switch on your milestone.
then you see black screen written Bootloader.
battery OK.
OK to program
connect USB
data cable.
if you can go into this screen, then u can start to learn to flash vulnerable recovery.
and ready to install custom room.
google around on how to instal vulnerable recovery for milestone .
under18 said:
turn off hp.try to hold up-dpad(towards screen) button and switch on your milestone.
then you see black screen written Bootloader.
battery OK.
OK to program
connect USB
data cable.
if you can go into this screen, then u can start to learn to flash vulnerable recovery.
and ready to install custom room.
google around on how to instal vulnerable recovery for milestone .
Click to expand...
Click to collapse
Yep, I can go into it. But I checked, and can't find how to install a vulnerable recovery. Any help?
My site is down atm, but this may help;
http://forum.xda-developers.com/showthread.php?t=932196
shut down phone ->hold down hard keyboard x key and power button->when M logo appears release power button but keep pressing x key until recovery mode shows up
there is an option for clearing data/factory reset
you'll loose everything but it propably fix the problem
Including my contacts?
ray243 said:
Including my contacts?
Click to expand...
Click to collapse
your contacts if you have chosen it will be at your Gmail account and they will be restored.
Hi all,
I have had my N1 for 1year and two weeks now (yes, warranty just expired). I was charging the device and it seemed to overheat and reboot. I unplugged it, took the battery out, let it rest for a bit and tried to boot it again. The phone now gets stuck on the X logo (not moving) and never boots.
I'm currently abroad (in the UK) and can't have it sent back for repair (I'd have to pay the repair too).
Will rooting the phone and installing an alternate OS fix my phone?
Is there any way to get HTC to honor the warranty after two weeks of expiration (I've been getting this problem for a while now, but that was only an issue if I made extensive use of the device while charging, which I almost never do so I didn't bother.)
Is there any way to fix this issue without messing with rooting? I'm abroad right now and all I want is my phone to work.
Any suggestions are welcome.
Try booting into bootloader from power off (vol- pwr) if that doesn't work then try the 3 figure salute (pwr vol- tb) your phone should boot into fastboot then just select bootloader.
If either of these work the your good you can get the static x fixed all you need to do is passimg (search wiki if you don't know what it is) as for the charging problem passimg will factory reset the phone so if that doesn't fix it then no you'll need to try rooting or it might be hardware.
Yes, I'm able to go into the bootloader.
I tried clearing the storage, choosing fastboot, etc. The phone seems to be working, just won't boot past the static X.
From your last reply, you're saying passimg has good chances to fix my phone. What does that involve? Do you have a link to a how-to that I could follow (it would really be a bad time for me to brick my phone, a good how-to would be really appreciated).
Cheers!
Yes passimg is used for many things it just reflashes a shipment ROM to the phone through bootloader. Like I said you can visit the wiki to have a how to here is a link http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials scroll down to "Unroot / Restore your Nexus" then follow the instructions. This should restore you to frg33 then you just need to update back to 2.3.4.
NOTE: this will wipe your data.
Ahh there's a way to unroot the nexus one now!
I had no idea! This is good to know (last time I checked was in December I think).
I will give that passimg a try as soon as I get home.
Can anyone confirm that this ("Attention: Latest stock ROMs don't flash using PASSIMG.ZIP method. Use the provided latest Froyo PASSIMG, and upgrade it after flashing.") means I can still reflash using this if I have the latest ROM (2.3.4) but will simply have to update again after (which I might not do given the issues I'm facing).
Cheers!
Confirmed - Dude is giving you good info... xD
Just to verify, unrooting is not the same as relocking. If you unlocked your bootloader (have a little lock symbol under the X screen), there is no way to relock it.
But the passimg is a good option. It will take you back to an older version of Android, and then you just let the system update itself.
Since you are out of your warranty, I can highly suggest looking into custom firmwares. These give you a lot more features and in many cases, perform better. CyanogenMod is probably the most popular one. These will fully replace your Android OS. CyanogenMod really doesn't even differ in look from stock all that much. Most people probably wouldn't even have a clue they are running something different, except for the stability and performance increases.
You can read up about this stuff in the wiki as well.
Oh, I see, thanks for the info.
I'm actually trying to get the FRG83 passimg file but the link is dead. Does anyone have an alternate one?
Use the FRG33 image
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Try the passimg, but it's possible that you are looking at hardware failure...
ldiamond2 said:
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Click to expand...
Click to collapse
If you are still running stock Android, you can't reboot between installing the recovery and getting into it. Stock Android will replace it. Try to go back to the bootloader and select recovery then, or fastboot to load the recovery, and then use fastboot to boot off of it.
Code:
fastboot flash recovery "c:\location to\recovery.img"
fastboot boot recovery "c:\location to\recovery.img"
Hopefully this will get you into Amon_RA so you can try again.
But the passimg method is used in the bootloader, not in recovery. You don't need a custom recovery to use the passimg method.
Amazing, thanks for pointing out my mistake, that give me a little bit of hope now . (I was at the point where I'd open the thing and look for a broken solder joint.)
I will try this as soon as I get home!
**Edit** I actually am not sure if I really rebooted or went straight to recovery. I'll update this thread tonight.
According to some other people, this would be a common issue with the internal memory dieing.
Is there a utility I can use to check the state of the memory?
None that I know of. Our phone internal memory uses the yaffs2 (Yet Another Flash File System v2) file system. I haven't heard of any programs that can check it.
Same situation
Hello, all. I haven't signed in on here in ages just because I've been so happy with how my Nexus has been running.
I ran into the same problem as OP stated.
I think I have some sort of hardware issue because my phone used to randomly freeze and couldn't be restarted unless I pulled the battery. Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Is there any way to check for hardware damage? My warranty is over as well so I'd have to pay for any repairs to my phone if I sent it in.
If it's running, you can try to pull a log, and see what error reports you get?
andythefan said:
Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Click to expand...
Click to collapse
Your power button might just be dead. Try having the phone plugged into a power source and removing and reinserting the battery. While you are doing that, hold the Volume Down button. This will get you into the bootloader which would allow a passimg to be performed. Hopefully your reboots aren't a hardware problem.
So , after pulling my battery, pulling the sim and the sd card, it finally turned on and went to recovery without freezing. I was able to wipe and reflash cyan 7. It's working well for now, but I'm really afraid this is going to happen again because this isn't the first time that it's just froze repeatedly.
Does anyone know what the problem could be?
Alright,
I did "fastboot flash recovery MYIMG" then "fastboot boot MYIMG", didn't work.
Then I tried "fastboot flash recovery MYIMG" then go to bootloader (without rebooting) and selected recovery.
Still no luck.
It always freezes on the static X logo. What else can I do? Will using passimg be any different (I don't have any way to put the file on the micro SD card but I can manage to do it if it's worth the shot).
Thanks
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
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
mediaman123 said:
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
Click to expand...
Click to collapse
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
jeromechrome1 said:
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
Click to expand...
Click to collapse
Please! Anyone!
by manually do you mean flashing all the separate parts of the stock image separately, system, boot, recovery, cache and so on..........
I don't know what else to do after going through with that process.....
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
I'm a total newb here so take what I tell you with a grain of salt. I had your exact same problem on my Nexus 5. Every single thing you just described is what happened to my N5. And just like your N6...I was able to boot up into recovery (stock and TWRP), I was able to flash all the things manually and even used Wug's NRT. But then whenever I tried to actually boot up the device it could never pass the Google logo....basically EVERYTHING THAT IS HAPPENING TO YOU.
What I did to fix everything? Changed my battery. Sounds stupid and totally irrelevant but that did the trick. When I opened up my phone I noticed my battery had a nasty bulge and realized it was defective. Bought a new one for $25 and have never had any issues ever since. I suggest you look at your battery and see if that is the root of your problem. I have heard of the N6 having some batteries expanding and causing the back covers to pop off...this could be related to your problem.
Like I said I am a newb and thought I'd share my experience in the hopes it solves your problem.
Good luck buddy! :good:
my N6 is actually away getting repaired for the exact issue you described, expanding battery [assumed], and cover coming away from the bezel.....
I believe though that if you keep the device plugged into the wall when trying to boot up with this battery defect it will get through the boot, at least in the beginning anyway....
I believe also that if it was a battery issue the device would power off first, as opposed to just sticking on the Google logo.........
ldkud50 said:
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
Click to expand...
Click to collapse
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
jeromechrome1 said:
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
Click to expand...
Click to collapse
Thats too bad. Maybe the device is hosed. RMA for a new one.
Same thing happened to me. As soon as I updated to the newest version of fastboot on my computer, everything worked...
jeromechrome1 said:
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
Click to expand...
Click to collapse
I know, it's been a long time, but coud you tell me what happened to the phone?
I have my rog 2 stuck in a bootloop. I don't really know why in the first place, because I don't like to change and mess around with custom roms. So i've never done that.
The case was that I was watching a video on YouTube and suddenly the touch screen stopped responding, the phone kept responding to other inputs such as the power button and the volume rocker. So I decided to restart the phone. And then it didn't turn on again. Got stuck in a boot loop.
I've been trying to fix it for a long time. But I just can't do it. Nor am I able to see what is happening with the phone. I have used this guide.
EVERYTHING works perfectly, it doesn't give me any errors during flashing or anything like that. Even the program tells me that the rom has been flashed correctly, and even the rog logo during boot, changes (I suppose because it is a version of the rom prior to the one I had.). The fact is that even with that the phone is still stuck in the bootloop. I have tried more things but this is the one that has taken me the furthest. I don't know what else to try. If anyone has any ideas, please tell me.
P.D. Sorry if my English is a bit rusty.
go back to stock and try other rom.
atoyu said:
go back to stock and try other rom.
Click to expand...
Click to collapse
Any suggestions which rom I can use? I have tried the rom of the guide and the ones that Asus has on their website. None of them have bailed me out.
@Arnau17 Any Updates? I am facing the same issue. Mine reaches till boot logo and then freezes and reboots again. Tried flashing stock ROM as well but no Luck
I am in the same situation, tried several raw rom files, still in bootloop
USB plug correctly on side USB port? can you enter recovery or fastboot mode?
i have same problems before, if fixed after flash RAW rom, hope this help.
is there a guide to fix AVB VERIFY FAIL on Rog Phone 2