Related
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.
Okay, so I decided to screw around with my HTC One again, and ended up trying the new Cyanogenmod installer. Needless to say, I have screwed my phone up worse than ever and I have no idea how to get it back. It is stuck in bootloader, I can't go into recovery or reboot or even power off. It just keeps rebooting to bootloader. I tried the RUU, but it comes back with an error that the image version isn't correct, and I tried flashing another recovery, but i still can't get into recovery. Right now, I am sitting in my bootloader with nothing to boot into. I can use ADB however, just please help me.
CaRBiiNeZz said:
Okay, so I decided to screw around with my HTC One again, and ended up trying the new Cyanogenmod installer. Needless to say, I have screwed my phone up worse than ever and I have no idea how to get it back. It is stuck in bootloader, I can't go into recovery or reboot or even power off. It just keeps rebooting to bootloader. I tried the RUU, but it comes back with an error that the image version isn't correct, and I tried flashing another recovery, but i still can't get into recovery. Right now, I am sitting in my bootloader with nothing to boot into. I can use ADB however, just please help me.
Click to expand...
Click to collapse
Try, "fastboot erase cache" and then try to go into recovery.
Sent from my HTCONE using Tapatalk
Hi XDA,
I currently have an issue with my One, I'm stuck at the white HTC-screen where it says "powered by android" at the bottom, I can't get into the bootloader, no matter what I try (I've tried every combination there is, multiple times) the PC detects an Android ADB Interface, but it says "unauthorized".
This happened after I unlocked my bootloader regularly via the HTC Dev-method.
If I type "adb reboot bootloader" into a command prompt, it says "error: device unauthorized. Please check the confirmation dialog on your device." but there is nothing on my screen other than the splash-logo.
Is there anything I could do?
Thanks in advance for your time and help.
edit:
I just noticed that the softkeys don't flash when I hold down the power-button, not sure if this helps you determine the error.
No ideas? :/
HeavyHDx said:
Hi XDA,
I currently have an issue with my One, I'm stuck at the white HTC-screen where it says "powered by android" at the bottom, I can't get into the bootloader, no matter what I try (I've tried every combination there is, multiple times) the PC detects an Android ADB Interface, but it says "unauthorized".
This happened after I unlocked my bootloader regularly via the HTC Dev-method.
If I type "adb reboot bootloader" into a command prompt, it says "error: device unauthorized. Please check the confirmation dialog on your device." but there is nothing on my screen other than the splash-logo.
Is there anything I could do?
Thanks in advance for your time and help.
edit:
I just noticed that the softkeys don't flash when I hold down the power-button, not sure if this helps you determine the error.
Click to expand...
Click to collapse
This is a long shot, try Ubuntu/Linux. You can boot into it without installing Linux on your computer and it handles ADB & Fastboot more smoothly. Read and follow FAQ Q5, you must install Ubuntu 12.04 for these procedures to work. If you install the newest version, there are several more steps. Just scroll down the first page and near the bottom there is a link to older versions. If you get fastboot working, then I would try a fastboot erase cache first with fastboot reboot to see if the problem is resolved. If that didn't work then try to get back to bootloader and select factory reset.
majmoz said:
This is a long shot, try Ubuntu/Linux. You can boot into it without installing Linux on your computer and it handles ADB & Fastboot more smoothly. Read and follow FAQ Q5, you must install Ubuntu 12.04 for these procedures to work. If you install the newest version, there are several more steps. Just scroll down the first page and near the bottom there is a link to older versions. If you get fastboot working, then I would try a fastboot erase cache first with fastboot reboot to see if the problem is resolved. If that didn't work then try to get back to bootloader and select factory reset.
Click to expand...
Click to collapse
The problem is that I can't enter the bootloader, so Fastboot won't work.
HeavyHDx said:
The problem is that I can't enter the bootloader, so Fastboot won't work.
Click to expand...
Click to collapse
The other problem is that your phone is not recognized by Windows. If Ubuntu recognizes your phone, then you may be able to use the adb reboot bootloader command. It is a shot in the dark but if it works then great, if not you are in the same place you are now.
If you are S-OFF then try to find a RUU to run, if you are S-ON then you can not run a RUU with an unlocked bootloader.
majmoz said:
The other problem is that your phone is not recognized by Windows. If Ubuntu recognizes your phone, then you may be able to use the adb reboot bootloader command. It is a shot in the dark but if it works then great, if not you are in the same place you are now.
If you are S-OFF then try to find a RUU to run, if you are S-ON then you can not run a RUU with an unlocked bootloader.
Click to expand...
Click to collapse
I don't think using Ubuntu will resolve the "unauthorized"-issue, but It's worth a try, thanks!
Did you try holding the power button under a bright light? Make sure the ambient light sensor (two ports in upper left corner) is exposed.
iElvis said:
Did you try holding the power button under a bright light? Make sure the ambient light sensor (two ports in upper left corner) is exposed.
Click to expand...
Click to collapse
Yep, tried that too, didn't help :/
Has it been stuck at that white screen all this time? You may need to wait until the battery dies and see if it will reboot properly from there.
iElvis said:
Has it been stuck at that white screen all this time? You may need to wait until the battery dies and see if it will reboot properly from there.
Click to expand...
Click to collapse
I left it there for about an hour, no change.
There also isn't anything to boot into, I wiped /system/ and /data/ before unlocking the bootloader.
I was trying to get S-Off and it didn't work with CyanogenMod, so I locked the bootloader and tried to install an RUU and of course, that doesn't work if you don't have S-Off, so I wanted to unlock it again and install a sense based ROM after that, but that's where I got stuck in this bootloop.
In retrospect, it probably was really stupid to wipe those partitions before. Not sure what I was thinking at the time :/
I'll try Ubuntu tomorrow and I'll try it with a brighter light, maybe that works. Otherwise I just have to send it in. Worst that could happen is that they somehow get into the bootloader and discover that it says Tampered, but at that point they can just send it back and with a working bootloader I can fix it myself.
HeavyHDx said:
I left it there for about an hour, no change.
There also isn't anything to boot into, I wiped /system/ and /data/ before unlocking the bootloader.
I was trying to get S-Off and it didn't work with CyanogenMod, so I locked the bootloader and tried to install an RUU and of course, that doesn't work if you don't have S-Off, so I wanted to unlock it again and install a sense based ROM after that, but that's where I got stuck in this bootloop.
In retrospect, it probably was really stupid to wipe those partitions before. Not sure what I was thinking at the time :/
I'll try Ubuntu tomorrow and I'll try it with a brighter light, maybe that works. Otherwise I just have to send it in. Worst that could happen is that they somehow get into the bootloader and discover that it says Tampered, but at that point they can just send it back and with a working bootloader I can fix it myself.
Click to expand...
Click to collapse
Sorry, I was thinking that if you ran it down, then plugged it in, you might be able to get into the bootloader.
Battery's full right now, do you think it will get empty over night?
HeavyHDx said:
Battery's full right now, do you think it will get empty over night?
Click to expand...
Click to collapse
hold the power plus volume down for about 20 seconds when the phone shuts off and comes back on continue holding the buttons till it goes off for a second time. Then let go of power and continue to hold volume down. This has got me into the bootloader many time's. Do this in a well lit room or under a lamp.
HeavyHDx said:
Battery's full right now, do you think it will get empty over night?
Click to expand...
Click to collapse
If it's stuck on the white screen, yeah that should run it down pretty quickly.
But I'm thinking now this might be a bit risky. It will stay on until the battery dies completely instead of shutting down properly. Normally, the system will shut down with a little bit of charge left because if the battery goes completely dead, it may not be able to restart.
I'd try your other ideas first, and if you're ready to return it, give this a shot.
clsA said:
hold the power plus volume down for about 20 seconds when the phone shuts off and comes back on continue holding the buttons till it goes off for a second time. Then let go of power and continue to hold volume down. This has got me into the bootloader many time's. Do this in a well lit room or under a lamp.
Click to expand...
Click to collapse
If I release the power-button when the screen turns black the second time, it just stays off.
It's almost as if the volume-buttons aren't recognized at all :/
@iElvis okay then that'll be my last resort.
HeavyHDx said:
If I release the power-button when the screen turns black the second time, it just stays off.
It's almost as if the volume-buttons aren't recognized at all :/
@iElvis okay then that'll be my last resort.
Click to expand...
Click to collapse
well running the battery dead will not be any different than the shutdown you just did. did you continue to hold volume down and hit the power again after the shut down ? is the usb plugged in this hole time or no?
clsA said:
well running the battery dead will not be any different than the shutdown you just did. did you continue to hold volume down and hit the power again after the shut down ?
Click to expand...
Click to collapse
Yep, I held the button all the time, tried waiting longer and everything, I have already played around with combinations a fair bit before posting this, nothing seemed to work.
Why can't HTC have something like USB Jigs? :/ It's so convenient to just plug this thing in and be in download-mode, regardless how f*cked up your software is.
HeavyHDx said:
Yep, I held the button all the time, tried waiting longer and everything, I have already played around with combinations a fair bit before posting this, nothing seemed to work.
Why can't HTC have something like USB Jigs? :/ It's so convenient to just plug this thing in and be in download-mode, regardless how f*cked up your software is.
Click to expand...
Click to collapse
ok I wish you luck
clsA said:
ok I wish you luck
Click to expand...
Click to collapse
Thanks I just got this thing back from a 2 week repair because the volume-buttons wouldn't work, barely had it a day and now I can send it back again My own fault, but still annoying...
HeavyHDx said:
Thanks I just got this thing back from a 2 week repair because the volume-buttons wouldn't work, barely had it a day and now I can send it back again My own fault, but still annoying...
Click to expand...
Click to collapse
Update:
The place where I sent it to just messaged me this:
http://imgur.com/npdyLgO
I'm curious, how did they manage to get the bootloader working again? Is there another method for getting into the bootloader, other than pressing the buttons?
They want 218€ for fixing it (lol) so I obviously told them to send it back without fixing it, after all I can do that myself if the bootloader works.
Edit:
just got it back, Bootloader works now.
So I recently decided to flash a rom based on the newest android m preview. Everything flashed fine, no errors, no 'failed' messages. However, when I try to reboot my phone it immediately sends me to the boot loader with a Boot Failed message. Furthermore, at the top of the log it says "fastboot fall through from normal boot mode". I have never experienced this code before and could not find an answer on the forums. I was really hoping I could get a solution as this is my primary phone.
Thanks guys.
Naked Sam said:
So I recently decided to flash a rom based on the newest android m preview. Everything flashed fine, no errors, no 'failed' messages. However, when I try to reboot my phone it immediately sends me to the boot loader with a Boot Failed message. Furthermore, at the top of the log it says "fastboot fall through from normal boot mode". I have never experienced this code before and could not find an answer on the forums. I was really hoping I could get a solution as this is my primary phone.
Thanks guys.
Click to expand...
Click to collapse
Did you flash the M bootloader?
Yep. Boot loader and radio. My guess is something wonky happened with the damn toolkit. Probably what I get for being lazy. I'm gonna try manually reflashing all of it via adb and see how it goes.
Naked Sam said:
Yep. Boot loader and radio. My guess is something wonky happened with the damn toolkit. Probably what I get for being lazy. I'm gonna try manually reflashing all of it via adb and see how it goes.
Click to expand...
Click to collapse
Not ADB. Fastboot flash while in bootloader.
Yeah, fastboot. My bad. I actually just got done with attempt # god knows how many and so far no luck. I still get the same messages on reboot.
Good morning everyone. So yesterday my phone was working just fine. I went to go take the dogs out and a minute later I come back to my phone rebooting. I didn't think anything of it. And then I started to realize my phone kept rebooting. It is completely stuck at the Google Logo.
I did power and volume down to try and go into any mode possible, but it just boots back to the Google screen and keeps rebooting.
Any idea what might be wrong?
khanhathan said:
...
I did power and volume down to try and go into any mode possible, but it just boots back to the Google screen and keeps rebooting.....
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2426426/
Maybe the info in this thread.guide is helpful.
I've tried that with no success. I have also tried doing a re flash on WUGS root kit and it still bootloops.
NLBeev said:
http://forum.xda-developers.com/showthread.php?t=2426426/
Maybe the info in this thread.guide is helpful.
Click to expand...
Click to collapse