Hello.
I woke up yesterday, dig into my pocket tried to turn it on... battery was dead so I plugged it in, and then ever since, the power button is unresponsive. It showed no previous signs of flakiness. But I've since spent the last 2 days digging and searching for ways to salvage. I see that Cyanogenmod has a nice trackball wake feature that could solve my problem. I download the sdk, and try to unlock the bootloader with fastboot, but fastboot FAILED with status read failed too many links (on windows 7). I tried on a Mac and it also failed for similar reasons. ./fastboot-mac oem unlock
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory
So from what I've read, pretty much all flashing of roms require either a power button and/or fastboot (because of the radio?). Is there another option I'm missing? I was able to root the phone by downgrading from 2.3.4 to 2.2.1 using the passimg method and using superoneclick. So now I have a rooted froyo phone, with no power button and can't seem to access with fastboot.
Any assistance would be great. I'm just trying to salvage the phone and resurrect it.
Thanks.
Ok, I think I've done something wrong. I used ROM manager to download and install cyanogenmod 7 but now my phone hangs on the X. I let it sit for like 30 mins. Then pulled the battery and booted into recovery mode and reloaded the passimg file from before. It is currently back to froyo. What, if anything can I do? Thanks.
You're never going to be able to use fastboot, because unlocking the bootloader requires you to use the power button to confirm that you wish to unlock...
Make sure you wipe before you flash a new ROM.
Using the ROM manager I selected to wipe everything and then it reboots into the triangle exclamation point. What is the method to flash without fastboot or a power button... it seems even the ROM manager needs the power button. What am missing here?
You need to install a custom recovery. You can do this from ROM Manager - don't use Clockwork 3.x
Thank you so much! I was able to push it through that way. Now that I've got CM7 on it I'm good... but now I'm left wondering if there are better ROMs out there... guess its time to play. Thanks again.
Ok, Now of course... there have been issues. Just getting it up and running had me a bit too excited. Now it seems that the screen is fading in and out... while 'sleeping' and usually when I unlock the screen the power off/airplane mode menu comes up. I 'think' the power button has regained some limited function... and is constantly pressed perhaps. Because now when the screen does remain asleep for a second, I can push the power button and it will wake. But when the phone is on, if I push it, it doesn't go to sleep. I've done some searching but haven't been able to find an app that disables the power button on the N1.
Any thoughts on what I could do, because this is quite annoying. It just flashes off and on and off and on. Thanks again.
The power button is on a separate board connected by a ribbon cable. You could just disconnect the cable?
You could just buy the button with a flex cable, and fix the phone...
Yeah, that too - lol!
Once inside the box, its sometimes difficult to think outside it! xD
Related
A friend of mines son was installing roms on his HTC Hero and bootlooped it. I've followed all the methods I could find to put this thing in a flash mode, or a recovery mode but all it does is flash the HTC logo. Home/End seems to be the way to get into the recovery mode but it does nothing.
Can you put this thing into a flash only mode and at least get it to its original state? It is unknown as to what exactly he did to it. I was told that he had been installing lots of roms and eventually one made it do this.
I found this link http://forum.xda-developers.com/showthread.php?t=682551&page=2 but pushing the volume up/end keys only makes it vibrate 3 times then sit idle not doing anything.
thanks.
talktojer said:
A friend of mines son was installing roms on his HTC Hero and bootlooped it. I've followed all the methods I could find to put this thing in a flash mode, or a recovery mode but all it does is flash the HTC logo. Home/End seems to be the way to get into the recovery mode but it does nothing.
Can you put this thing into a flash only mode and at least get it to its original state? It is unknown as to what exactly he did to it. I was told that he had been installing lots of roms and eventually one made it do this.
I found this link http://forum.xda-developers.com/showthread.php?t=682551&page=2 but pushing the volume up/end keys only makes it vibrate 3 times then sit idle not doing anything.
thanks.
Click to expand...
Click to collapse
The only way to effectively help you/him is to know how he got there, and what recovery/rom/kernel/theme/etc he is running. It would also help to know if this phone has an eng-spl fastboot or an s-off hboot.
il Duce said:
The only way to effectively help you/him is to know how he got there, and what recovery/rom/kernel/theme/etc he is running. It would also help to know if this phone has an eng-spl fastboot or an s-off hboot.
Click to expand...
Click to collapse
theres no standard way to get to a flash mode with a sprint htc hero? what are some other key combinations i might try?
talktojer said:
theres no standard way to get to a flash mode with a sprint htc hero? what are some other key combinations i might try?
Click to expand...
Click to collapse
you mean like this: hold home and then power?
il Duce said:
you mean like this: hold home and then power?
Click to expand...
Click to collapse
yeah, so if that didnt work..screwed?
talktojer said:
yeah, so if that didnt work..screwed?
Click to expand...
Click to collapse
Not really... in very rare cases has the hero been bricked.
If nothing else, you could always run the Sprint/HTC RUU through your computer, that will restore the Hero to "Out-of-Box" state. From there you could root back again and flash any ROM you would like.
With the phone turned off, press and hold the volume up button. Whole holding it press the power button. When you see the logo let go of the volume up button. If that doesn't work you'll have to run an ruu from fastboot or get a hercimg and flash it from fastboot.
Sent from my HERO200 using XDA App
unCoRrUpTeD said:
With the phone turned off, press and hold the volume up button. Whole holding it press the power button. When you see the logo let go of the volume up button. If that doesn't work you'll have to run an ruu from fastboot or get a hercimg and flash it from fastboot.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
how do I get into this fastboot mode? I'd love to restore it to factory software, but I'm unable to figure out how to get the phone into a mode that the PC will recognize. Volume up/end vibrates 3 times but never actually turns on or shows a logo. just stays black. If I could get this thing back to its original state that would be great.
unCoRrUpTeD said:
If that doesn't work you'll have to run an ruu from fastboot or get a hercimg and flash it from fastboot.
Click to expand...
Click to collapse
Anyone know how to do this? I can't figure out how to get into the fastboot mode. I run the ruu executable, and it says it can't find the phone. I'm sure I need to put it in some kind of flash mode, but seem to be unable.
Not to hijack your thread, but I'm having this same problem. I've run several ROMs including cyanogen 6.0 and 6.1 and today was installing the cyanogen 7 with 2.3 android. I wiped everything and flashed the rom and the gapps and the phone went into constant reboot cycles. I could at that point, hold the power/home and get it back to the recovery menu. I had the Amon RA recovery and thought I would try the 3.0 clockwork, so I flashed that recovery image...rebooted without a problem. I tried wiping and reflashing, but still the constant reboot. So I took the advice on the wiki and flashed the DecaFuct-12222010-691.zip kernel. My phone rebooted and did not start the cycling, so I thought it was an improvement. However, 1/2 an hour later, it's still sitting at the HTC logo and the power/home does not reboot into recovery. Nor does trying to adb find any devices.
Apparently I haven't posted enough on these forums to be able to post to the dev thread. But I've done some base development work on the phone and have been using adb for over a year now. Any help on getting back to a working phone would be greatly appreciated!
Lynne
Ah, a coworker manager to get the buttons to respond. Yay! At least I'm back to recovery and can push a different ROM. Tho not CM7 since it keeps rebooting constantly!
lrandolph said:
Ah, a coworker manager to get the buttons to respond. Yay! At least I'm back to recovery and can push a different ROM. Tho not CM7 since it keeps rebooting constantly!
Click to expand...
Click to collapse
any idea what he/she did to get the buttons to respond? I still am unable to get into the recovery mode.
talktojer said:
any idea what he/she did to get the buttons to respond? I still am unable to get into the recovery mode.
Click to expand...
Click to collapse
First, power off and remove the battery. Make sure the USB is not plugged in
This is why you get 3 vibrations and no power on. If it does this again, remove the battery and start over
With the power off and the USB unplugged, hold Vol Up and press power on (End key)
It should then boot into fastboot. (a white page with green letters) At this time, plug the USB in (should change from Fastboot to Fastboot USB) and run the RUU .5 or .6 from your computer.
AT some point the RUU install will say waiting for bootloader. When this happens, you will already be in bootloader (Fastboot USB)
This should work to get you back to fully unrooted stock ROM. From there, reroot, install a custom recovery and rom.
Let me know if this works
ccrosno said:
First, power off and remove the battery. Make sure the USB is not plugged in
This is why you get 3 vibrations and no power on. If it does this again, remove the battery and start over
With the power off and the USB unplugged, hold Vol Up and press power on (End key)
It should then boot into fastboot. (a white page with green letters) At this time, plug the USB in (should change from Fastboot to Fastboot USB) and run the RUU .5 or .6 from your computer.
AT some point the RUU install will say waiting for bootloader. When this happens, you will already be in bootloader (Fastboot USB)
This should work to get you back to fully unrooted stock ROM. From there, reroot, install a custom recovery and rom.
Let me know if this works
Click to expand...
Click to collapse
here's what happens.
1. Remove battery
2. Replace battery
3. Press and hold volume up
4. While holding volume up, press and hold end key to turn unit on.
5. Unit vibrates 3 times and never powers on
This is without USB plugged in.
I asked the guy who owns the phone what he was doing, he said he had flashed ASOP Gingerbread or something and it never worked again.
talktojer said:
here's what happens.
1. Remove battery
2. Replace battery
3. Press and hold volume up
4. While holding volume up, press and hold end key to turn unit on.
5. Unit vibrates 3 times and never powers on
This is without USB plugged in.
I asked the guy who owns the phone what he was doing, he said he had flashed ASOP Gingerbread or something and it never worked again.
Click to expand...
Click to collapse
Interesting. Mine only does the 3 vibrate thing when I have the USB plugged in and I am trying to enter Fastboot. I unplug the USB, remove the battery, replace the battery, hold vol up and press end. Bing, right into Fastboot.
Do you know if he has the ENG SPL/S-Off installed? If not, the issue may lay in that. Not for sure though.
Also, it may have to do with the way the phone was originally rooted, that has an affect on things as well. Some of the overclocked kernels have an affect on boot. Some Heros wont boot with the kernel set to over 691.
I have installed every build pf ASOP 2.3.2 GB that has been posted, now grated they each had there issues but none of them put me in a loop or froze the phone.
I would also suggest downloading android commander to your computer. Just Google android commander and you will find it. With this program you can boot to bootloader. If you are getting to the HTC screen then Android Commander should recognize the phone. It is a great program.
talktojer said:
Anyone know how to do this? I can't figure out how to get into the fastboot mode. I run the ruu executable, and it says it can't find the phone. I'm sure I need to put it in some kind of flash mode, but seem to be unable.
Click to expand...
Click to collapse
Not sure, but you may try removing the sdcard and/or putting a different one in. Or when the phone first gets to the HTC screen press and hold the menu button and keep holding it.
Sent from my dual-booted liquidsense 2.1
unCoRrUpTeD said:
Not sure, but you may try removing the sdcard and/or putting a different one in. Or when the phone first gets to the HTC screen press and hold the menu button and keep holding it.
Sent from my dual-booted liquidsense 2.1
Click to expand...
Click to collapse
ive removed the sdcard, results are no different.
ccrosno said:
Interesting. Mine only does the 3 vibrate thing when I have the USB plugged in and I am trying to enter Fastboot. I unplug the USB, remove the battery, replace the battery, hold vol up and press end. Bing, right into Fastboot.
Do you know if he has the ENG SPL/S-Off installed? If not, the issue may lay in that. Not for sure though.
Also, it may have to do with the way the phone was originally rooted, that has an affect on things as well. Some of the overclocked kernels have an affect on boot. Some Heros wont boot with the kernel set to over 691.
I have installed every build pf ASOP 2.3.2 GB that has been posted, now grated they each had there issues but none of them put me in a loop or froze the phone.
I would also suggest downloading android commander to your computer. Just Google android commander and you will find it. With this program you can boot to bootloader. If you are getting to the HTC screen then Android Commander should recognize the phone. It is a great program.
Click to expand...
Click to collapse
android commander relies on adb..i've already tried adb and it can't see the device. already tried that the first night. I think I'm about out of options.
talktojer said:
android commander relies on adb..i've already tried adb and it can't see the device. already tried that the first night. I think I'm about out of options.
Click to expand...
Click to collapse
Interesting you say that. Here are 2 snips taken at the same time. One of my ADB shell showing no devics found and the other of my android command shell clearly showing connection to the device.
Try the android commander. It is a great program and it is GUI based.
Let me know
Edit: Even stranger, although ADB shows no devices, if I type LS, a list of the phone directories shows up.
ccrosno said:
Interesting you say that. Here are 2 snips taken at the same time. One of my ADB shell showing no devics found and the other of my android command shell clearly showing connection to the device.
Try the android commander. It is a great program and it is GUI based.
Let me know
Edit: Even stranger, although ADB shows no devices, if I type LS, a list of the phone directories shows up.
Click to expand...
Click to collapse
You would actually do
adb devices
You don't do it from inside adb.
Sent from my dual-booted liquidsense 2.1
Hi everyone!
I just purchased a slightly used N1 for my dad for fathers day, and the guy was telling me about how N1s have a problem with their power button. He told me it hasn't happened at all with the phone I purchased, but I wanted to ask XDA..
"Do you have a nexus one with a failing power button? & how long have you had the nexus one?"
18 months and no failure. A free app called Quickboot in the market allows you to power down with a soft button, lengthening the click-life.
Ya I use trackball wake, widget locker and quickboot so I never have to touch my power button except to turn it on from power off or to select in bootloader. The thing is is that nexus one power buttons fail after a while but it depends how much you press it if it's once every 5 minutes ya it'll die faster you can't know if it will die soon there is not really an average dying rate.
BTW: I've had mine 10 months
Power Button failure
I am desperate about my power button status, is completely out of order. I am on latest nightlies but due to FC of launcher, i had to power off my n1. Because of my power button I can not restart or access recovery mode, now it is in bootloop.
Is there any solution???
vithudu said:
Power Button failure
I am desperate about my power button status, is completely out of order. I am on latest nightlies but due to FC of launcher, i had to power off my n1. Because of my power button I can not restart or access recovery mode, now it is in bootloop.
Is there any solution???
Click to expand...
Click to collapse
Is your bootloader unlocked??
If yes then try fastboot flashing if not then do passimg instructions are in the wiki (under unroot/restore) http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials#Unroot_.2F_Restore_your_Nexus
Thank you Dude Random 21,
Yes, my N1 is already rooted, bootloader unlocked, however s-on not s-off. I dont quite understand why is always s-off for more than a year, but i can do everything as rooted device. I read somewhere that my N1 is not completely unlocked, this may be other story
In my situation now the power button do not properly operate as required, so I cannot shut down, ie power down my phone, for recovery option.
Help!!!
You can power down just to turn it on you'll need to plug in your charger (to your computer if you'll be flastboot flashing anyway) and then remove your battery and reinsert it (while holding trackball so you boot into fastboot) you may have to try it multiple times to get it to work.
my power button works fine after 15 months, but that is because i purposely use track ball wake and rarely ever touch the power button. and i use quickboot app as well. i just dont feel like even dealing with the possibility.
so really just root, install cyan 7 or some other ROM with trackball wake, and save the hassle.
18 months, and I use it constantly. I've installed Quickboot, but never use it. I've enabled trackball wake, but never use it...
I'm prepared for when it dies - which will probably be later this evening, now that I've said this...
My power button died after 3 months of use... I'm currently using "anyunlock".
15 months and no issues whatsoever.
P.S. I have never used trackball wake...
Sent from my Nexus One using XDA Premium App
tempaznx said:
Hi everyone!
I just purchased a slightly used N1 for my dad for fathers day, and the guy was telling me about how N1s have a problem with their power button. He told me it hasn't happened at all with the phone I purchased, but I wanted to ask XDA..
"Do you have a nexus one with a failing power button? & how long have you had the nexus one?"
Click to expand...
Click to collapse
No problem here, but I have been careful. I normally use "Power Off and Lock" to turn it off and Trackball to wake. Owned just over a year at this point.
I worry about the trackball wearing out, but I figure if it does it won't kill me, as I don't really use it for much anything else. Love my RGB notification disco ball though, I WILL miss that, even if I don't physically use the trackball itself.
@Dude Random21 and Danger-rat
You can power down just to turn it on you'll need to plug in your charger (to your computer if you'll be flastboot flashing anyway) and then remove your battery and reinsert it (while holding trackball so you boot into fastboot) you may have to try it multiple times to get it to work.
Click to expand...
Click to collapse
I got to white screen with 3 robotic skaters, ie screen with options: fastboot, recovery, clear storage, and simlock. As I said before, my power button does not work any more, so that I can not push pwr botton for activating recovery mode.
I tried other option using method of recovery image at http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Recovery_Images. After typing the cmd "fastboot flash recovery recovery.img" the notification is " waiting for device". I think adb cannot see/ regconize my n1, so that I cannot enter recovery mode.
Please enlighten me.
To use fastboot, your bootloader needs to be unlocked and the phone needs to be at the fastboot screen (hold trackball while powering up - looks like the same white 3 android screen, but the menu is slightly different)
If your bootloader isn't already unlocked you may be out of luck (you need to use the power button as part of the unlocking process).
You can use adb to boot into recovery, but you need to be in either recovery (pointless), or booted normally to use adb (won't work from hboot).
I started having problems 5 months after purchase and Videotron replaced it. My wife's N1 just started playing games, also after 5 months.
Sent from my Nexus One using XDA App
Thank you danger-rat,
To use fastboot, your bootloader needs to be unlocked and the phone needs to be at the fastboot screen (hold trackball while powering up - looks like the same white 3 android screen, but the menu is slightly different)
If your bootloader isn't already unlocked you may be out of luck (you need to use the power button as part of the unlocking process).
You can use adb to boot into recovery, but you need to be in either recovery (pointless), or booted normally to use adb (won't work from hboot).
Click to expand...
Click to collapse
Ok, I got to the fastboot screen with menu option: fastboot USB..., bootloader, reboot, rebootbootloader, and power down. So 2 question:
In my case, my bootloader is considered as unlock??? If it is unlock how can proceed further ?????, because for selection one of options my pwr button does not work.
With ADB method: this method does not required using the pwr button: I tried as instructions
For unlocked bootloader - using fastboot
The following won't work unless your bootloader is unlocked.
1. Download Amon_RA's Recovery from one of the versions above.
2. Rename Amon_Ra's Recovery Image to simply recovery.img.
3. Download this file - Stock Recovery Remover - and copy it to the root of SDcard.
4. Toggle on USB Debugging (Settings » Applications » Development). Power off the Nexus One.
5. Boot into bootloader mode. (Hold volume down & power button until you see white screen with skateboarding androids)
6. Connect the Nexus One to the computer.
7. On the computer... Open a command prompt/terminal & navigate to the Android SDK Tools folder.
8. Type in the following commands (assuming recovery.img is in the current directory):
fastboot flash recovery recovery.img
fastboot reboot recovery
Click to expand...
Click to collapse
The result is the notifications:" wait for device" and i waited for hours...
In both cases, I cant go further, any way out???
If your phone has the padlock on the static x screen it is unlocked. It also tells you in fastboot if its locked.
Anyways as I think danger stated you need to use fastboot commands when the phone is in fastboot mode connected to the PC etc. It is a not a adb command. Its fastboot devices...etc
I'm the end you will issue the fastboot flash recovery command. Then fastboot boot recovery....
If you're unlocked your fine. You don't need power button. If you're locked you're ****ed
Sent from my Nexus One using XDA App
Yes, I confirm that there is a padlock, and I understand that my N1 is unlock.
I redid cmd: fastboot flash recovery recovery.img and fastboot reboot recovery
But nothing happen. It is my N1 bricked???
My last hope is to replace Power Button.
Any suggestion???
First, make sure your phone is connected by typing:
fastboot devices
If that works, then try flashing the recovery. Post any error messages, rather than saying "it didn't work"...
Using Nexus One from April 2010 - power button working fine. Bought Nexus One directly on google site.
I have a Motorola milestone (second hand) and tried to load a update for it then i noticed the following problems:
- boot looping at the android logo
-when i tried going into bootloader i get a blank black screen
-when i go into recovery and try to update using "update.zip" i get a EOCD error and another time i get a authorization error
WHAT TO DO????
Come on dude,
Just search EOCD error, I think you will find at least 15 topics.
You lost root, Nedd to flash vulnerable recovery sbf. You will find latest instructions on nadalbak site.
You can find site inside his cm7 topic. Milestone android development.
Sent from my Milestone using xda premium
i'm fairly new to the milestone side, the version that is on the phone is 2.2
Everybody's instruction is to put the phone in bootloader mode and connect to the pc but i only get a black screen and then the phone restarts hence rsd lite not picking it up
Put it in recovery and try to flash another sbf, it should work.
Trough rsd lite.
try that just now and still no response on the pc, and i know the usb port is working because i charged the phone
Are you sure your drivers for phone are correctly installed?
Explain correctly installed?
yeah so what about when i try going into boot loader and get a blank screen?
In the early development of moto driver's phone wasn't recognised by rsd lite.
I didn't hear of that problem anymore though. The solution was to reinstall / install drivers again or try on another pc.
Cable could also be a problem.
Are you trying to enter bootloader with the cable connected to phone? If yes try without and after connect it.
The cable isnt the problem, im sure of that and i tried on two other laptops but they are 64 bit windows 7 but anyways why when i press "power+vol up + camera" i only get a black screen and not black screen with other milestones?
I'm thinking thats the problem or reason why rsd lite not picking up the phone cuz its not in bootloader mode
Ahhh
It took some time since last used bootloader.
But I think is power + x for bootloader.
==== update ====
my bad that's for recovery
oky just tested:
it's power + up key from keyboard
now when i first pressed the power i got a black screen, so i pressed the power again while holding the up key .. and voila:
bootloader 90.78
battery ok
....
good luck ..
when this happened to me i was shocked so much , but then i got it fixed so yay
sigh was trying that from lastnight but no luck
Does anybody have a video to how this done because i'm wondering if i'm doing it right cuz i'm still getting black screen when trying to go into bootloader, i pressed "power + up button on DPAD" and then pressed the power button again but still black screen
While the phone is off, hold the up button on the D-pad and press the power button. Do not let go of the up button until the bootloader screen comes up.
while the phone is off? i can't turn off the phone because its just looping so i take out the battery then put it in and press up and power button so is that the right way?
Yes,
If it doesn't work, for pre 90.78 bootloader I think it was another combination of keys.
Google it
Got it all wrong, the problem was that a app was installed and then the phone was restarted then the looping start at the android sign
no luck, the ways i see is the same as urs
reesieBennett said:
Got it all wrong, the problem was that a app was installed and then the phone was restarted then the looping start at the android sign
no luck, the ways i see is the same as urs
Click to expand...
Click to collapse
about the video:
found this on youtube:
bootloader:
http://www.youtube.com/watch?v=xjQcvg3Eplc
recovery:
http://www.youtube.com/watch?v=H3Vl9NbU6Ag&feature=related
if you enter recovery try wiping everything / factory reset and see if it get into android.
other than this i haven't got any other idea,
it is possible to reboot it with adb if you got a rom that supports adb at boot. ex CM7. cm6 and froyo rom not sure but this is a long shot.
I finally found solution! Bootloader on my phone isn't nearly same as usual one, no white screen, just a few lines which designate modes. 4 are present:
-normal boot
-fastboot
-recovery
-UART boot
I accessed it by pressing and holding power button and volume up button at the same time during device boot.
I hope someone with a same problem will find this helpful!
I managed to boot to system but I still can't get in bootloader. No combos and neither adb works.
I got my HTC One from second hand several days ago and I instantly noticed that something wasn't right. System was naked, no bloatware, no usual settings, no proper identification so I decided to install custom rom. I tried to boot to bootloader which I wanted to unlock(I guessed it's locked 'cause recovery is stock) with key combos, adb but it simply didn't boot to bootloader nor it rebooted or sometimes it went to factory mode which is on chinese. Again, I tried to find which version of phone I own but I can't figure it out. Moreover, I downloaded and put stock rom on virtual sd card and booted to recovery, opened menu with power button and selected to install package from zip just like it's said in thread but it outputted 'Install /sdcard...' and nothing else for past couple hours. Recovery isn't frozen, It shows\hides menu when power button is pressed. I tried to force shut down it by holding only\in combination with power button\volume buttons but nothing happens. I don't know what else to do...
Any help would be appreciated.
EDIT: It eventually discharged but when I turn it on with charger in it I get blinking white screen on every 3 seconds and when long pressing power button phone just vibrates. In combination with volume down it keeps blinking on every 3 secs and with volume up on every 5 seconds. To me, it looks like it's trying to boot but bootloader can't find anything installed. Computer is recognizing usb device on the moments when I connect it with usb just like when device is rebooting.
Jon2555 said:
I got my HTC One from second hand several days ago and I instantly noticed that something wasn't right. System was naked, no bloatware, no usual settings, no proper identification so I decided to install custom rom. I tried to boot to bootloader which I wanted to unlock(I guessed it's locked 'cause recovery is stock) with key combos, adb but it simply didn't boot to bootloader nor it rebooted or sometimes it went to factory mode which is on chinese. Again, I tried to find which version of phone I own but I can't figure it out. Moreover, I downloaded and put stock rom on virtual sd card and booted to recovery, opened menu with power button and selected to install package from zip just like it's said in thread but it outputted 'Install /sdcard...' and nothing else for past couple hours. Recovery isn't frozen, It shows\hides menu when power button is pressed. I tried to force shut down it by holding only\in combination with power button\volume buttons but nothing happens. I don't know what else to do...
Any help would be appreciated.
Click to expand...
Click to collapse
You have a fake phone
I agree, you've probably got a counterfeit One, but you can't flash custom roms from stock recovery anyway.
Firstly, thank you for any answer. How do you mean 'fake'?! I got it in original box and IMEI's are same(on box and device) What can I do with it then?
I tried to flash stock rom designed for stock recovery, at least that's how I understood.
MIDN07100 (Europe, a guy from which I got device claimed that it's from England so this should fit)
IMEI:354436053103493(same on device and on box, checked with IMEI checker it appears as valid HTC One device)
So first things first:
I am not a noob, I have been flashing phones for years
The phone has an UNLOCKED bootloader
I know what a bootloader/recovery are etc
So last night I upgraded my phone to 6.0.1. I then decided to root it and get a kernel on for color control. So I download one of the new kernels (Elementalx) for 6.0.1 and the systemless root that he recommended in his post. I flash both files and boot the phone, the phone bootloops twice after the password to boot screen and then it works fine. I install a few things adjust a few things (nothing pertaining to root) and then before I jump into the shower I reboot it. I look at it after a few minutes and it is sitting at the google screen with the padlock, no worries it has happened before so I reboot it only to be met with this same screen. Over and over it just halts here. I do the button trick to get into the bootloader, no dice. No button combination can get me past this screen.
I then go over to my PC and try it out and see if I am getting a Q_BULK issue (I had it happen to my Galaxy Nexus before) and the PC doesn't even acknowledge it, so now I am getting a little worried. I cannot power off the device normally, it just reboots back to here. I can manage a trick with the power cable and some quick button presses to enter the "charging" mode and from there it appears to shut down. Upon boot though it comes right back to this halt. :-/
So, does anyone have ANY experience with this before I contact Motorola? I really don't want to because I have frame swapped and don't look kindly on the process of undoing it for a replacement, but if it must be then it must be. Below is a TLR
Phone boots to Google/padlock screen
CANNOT access the bootloader/recovery through normal means
PC does not recognize it (I did prior in both fastboot and recovery so the drivers are all installed)
the phone does NOT appear to be in Q_BULK
the phone will not shut down, it just boots back to here
It "was" running ElementalX and the systemless root (both are the newest) for 6.0.1
-Current status, sitting on this screen waiting to die... but it has an almost full charge
OK, first off... YOU ARE A NEWBIE.
Turn off the phone and boot to bootloader and use that to load your custom recovery and restore your working backup.
Failing that, fastboot flash the stock image from bootloader mode.
What are you hoping to accomplish by draining your battery completely, this can only make matters worse.
@scryan you are a funny man?
you didnt say anything about trying to get into recovery.. i assume you tried getting unto your recovery?
Hold power button, up and down button all at the same time. If you are on stock recovery wipe user data and cache. See if you can boot into the bootloader afterwards. That's unusual you cannot get into stock or custom (if you have it) recovery.
So you're main problem here is that you can't get into your bootloader or recovery right now? Hmm..... that can't be good. My best guess would be to keep trying to get it into your bootloader, just keep on holding volume down and power for a long time, hopefully if you can get into either bootloader or recovery you can fastboot flash a clean stock image, or restore a nandroid backup (assuming you have one) with TWRP. My best guess though.
Briefly, your device powers on, so there's sign of life. It is either your cable, pc' usb port or the usb socket of the phone is at fault. Did you try with another usb cable at another usb port in the pc ?
Let the phone power down completely. And when it dies, connect it to a charger while briefly holding the vol down button to get into the bootloader. It might take a while since the phone doesn't have any juice but this trick might just work.
If already no warranty, so dissasembly the deive, re-attack your battery