Hi All,
I have an HTC one M7 unlocked. Two days ago I tried to restart my phone and it is stuck on the Fast boot /bootloader screen. I tried to use the recovery and Reset Factory options, but these are bringing me back to Fastboot screen. Took my phone to a gadget shop and they said OS has gone. Any idea how to proceed? I am a newbie to this forum and any help would be much appreciated
***LOCKED***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.000
OS-6.13.707.107
eMMC-BOOT 2048M
Jan 7 2015,14:50:53.0
FASTBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER>to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Unlock the bootloader first then install custom recovery
what's up everyone... got a little question and apologise if it's been asked many times before. my wife loves htc (sense UI) so recently i bought a brand new one for her (M7)... the reason im telling this is the fact that I have already drivers and adb installed on my pc (unlocked, rooted and flashed a rom for her on the second day after buying it) but few days ago I bought another M7 at a good price just to use with mhl-vga converter (as a stationary with Bluetooth keyboard and mouse connected so we wouldn't have to connect her m7 or my s5 all the time back and forth) but the thing is, that volume rocker (the one you actually need to enter a fastboot mode, the Volume Down) - dont work, so my question is, - is it possible to enter a fastboot mode through pc using cmd ? I've read that it is possible but yesterday I connected, opened command window, typed ADB devices just to see if pc recognizes the device and nothing, then typed other commands I found googling... commands for reboot, reboot to fastboot... whatever... so I'm asking is it possible? or the only way to get there is to use power and volume down buttons? thanx.
edit : drivers are all good (updated), adb us on my pc. the device was On (booted).
methoddon1 said:
what's up everyone... got a little question and apologise if it's been asked many times before. my wife loves htc (sense UI) so recently i bought a brand new one for her (M7)... the reason im telling this is the fact that I have already drivers and adb installed on my pc (unlocked, rooted and flashed a rom for her on the second day after buying it) but few days ago I bought another M7 at a good price just to use with mhl-vga converter (as a stationary with Bluetooth keyboard and mouse connected so we wouldn't have to connect her m7 or my s5 all the time back and forth) but the thing is, that volume rocker (the one you actually need to enter a fastboot mode, the Volume Down) - dont work, so my question is, - is it possible to enter a fastboot mode through pc using cmd ? I've read that it is possible but yesterday I connected, opened command window, typed ADB devices just to see if pc recognizes the device and nothing, then typed other commands I found googling... commands for reboot, reboot to fastboot... whatever... so I'm asking is it possible? or the only way to get there is to use power and volume down buttons? thanx.
edit : drivers are all good (updated), adb us on my pc. the device was On (booted).
Click to expand...
Click to collapse
You can reboot to the bootloader / fastboot usb mode by using the command "adb reboot bootloader". To use this command, you must have the latest HTC drivers installed on your computer and "USB debugging" option turned on in the developer option menu. If you can't access the developer menu from the settings menu (not in the list), you must active it by going to "settings --> about --> Software info --> more" then start tapping on the "build number" until you see a notification "You are now a developer" telling you that the developer option menu is enabled. Then go back to the settings menu --> Developer option -> USB debug --> ON.
Another important thing when using adb from a booted rom is to make sure that you have unlocked the screen using your PIN (or any other security method). ADB won't work if the screen is locked for obvious security reasons.
Once in the bootloader, if you can't use the volume down key to navigate the options, there is not much you can do except using fastboot commands. If you want to boot in recovery mode for example, since the volume key is broken, you'll need to reboot in the OS and use the "adb reboot recovery" command so you can access the recovery mode. If you want to exit the bootloader, use "fastboot reboot".
I I
alray said:
You can reboot to the bootloader / fastboot usb mode by using the command "adb reboot bootloader". To use this command, you must have the latest HTC drivers installed on your computer and "USB debugging" option turned on in the developer option menu. If you can't access the developer menu from the settings menu (not in the list), you must active it by going to "settings --> about --> Software info --> more" then start tapping on the "build number" until you see a notification "You are now a developer" telling you that the developer option menu is enabled. Then go back to the settings menu --> Developer option -> USB debug --> ON.
Another important thing when using adb from a booted rom is to make sure that you have unlocked the screen using your PIN (or any other security method). ADB won't work if the screen is locked for obvious security reasons.
p. s. with my wife's phone I was done in 15 minutes (including unlocking, rooting, flashing a rom and a boot up). so I'm confused a bit. but since wife's June us new and obviously the volume rocker is functioning, I had no problem getting to bootloader and take it from there.
Once in the bootloader, if you can't use the volume down key to navigate the options, there is not much you can do except using fastboot commands. If you want to boot in recovery mode for example, since the volume key is broken, you'll need to reboot in the OS and use the "adb reboot recovery" command so you can access the recovery mode. If you want to exit the bootloader, use "fastboot reboot".
Click to expand...
Click to collapse
thanx for such detailed info. I'm not" working " a lot with htc, I'm myself a Galaxy Series kinda guy but im familiar with the basics of htc. I'll try again tomorrow. but commands don't do what they were meant to do. after updating the drivers with htc sync and having USB debugging On, and adb installed (everything I used to unlock, root etc my wife's device, this device gives me problems). got to see in manager (on pc) if it's even sees the device. but the command Adb devices didn't show anything connected.
methoddon1 said:
I I
thanx for such detailed info. I'm not" working " a lot with htc, I'm myself a Galaxy Series kinda guy but im familiar with the basics of htc. I'll try again tomorrow. but commands don't do what they were meant to do. after updating the drivers with htc sync and having USB debugging On, and adb installed (everything I used to unlock, root etc my wife's device, this device gives me problems). got to see in manager (on pc) if it's even sees the device. but the command Adb devices didn't show anything connected.
Click to expand...
Click to collapse
Yep and post a screenshot of your devices manager when you'll have time.
alray said:
Yep and post a screenshot of your devices manager when you'll have time.
Click to expand...
Click to collapse
what do you mean? I meant go into pc, open a manager and see if the pc sees it.
methoddon1 said:
what do you mean? I meant go into pc, open a manager and see if the pc sees it.
Click to expand...
Click to collapse
Exactly and if the phone isn't detected or is incorrectly detected (yellow triangle with an exclamation mark) take a screenshot of your windows devices manager and post it here.
I will.
alray said:
Exactly and if the phone isn't detected or is incorrectly detected (yellow triangle with an exclamation mark) take a screenshot of your windows devices manager and post it here.
Click to expand...
Click to collapse
here is the thing, - I was gonna switch my interface to English so it'd be easier for you but don't have it installed and since we just had a major storm, my Internet is down for a minute so here is the thing... in the manager it showd all is good as you see, when you double tap on My HTC, in the little window in General it shows Connected but in time in the same General it'll show "At this moment the device isn't connected (code45). To solve this problem reconnect the device."
p. s. in Drivers tab (just for the hell of it I pressed Update but the drivers are up to date. so does HTC Sync... connected, synced.
oh sh**, I'm finally in after trying and trying... adb devices - Recognised, adb reboot bootloader - rebooted... never mind right now, I'll take it from here. out of time right now but I'll get back to it when my Internet connection fixed. thanx again, but I might be back with another question.
---------- Post added at 09:46 AM ---------- Previous post was at 09:27 AM ----------
maybe it's a coincidence but I deleted folders that I used to work with my wife's htc (in mini-sdk folder was unlock code that I got unlocking her device) and unzipped (still had the zip) again. now I have no problems using adb commands.?
alray said:
Exactly and if the phone isn't detected or is incorrectly detected (yellow triangle with an exclamation mark) take a screenshot of your windows devices manager and post it here.
Click to expand...
Click to collapse
well, I fckd it up... after successfully going through process of unlocking, flashing twrp, restoring apps from Titanium Backup, last thing I had to do was install xposed installer... i installed exactly the same that I did before 4beta but instead of flashing 68 arm 21 zip to install framework I flashed 74 arm 21 zip, wiped dalvik but no boot up. that's it! htc one logo... connected the device to pc, now it sees it but it says it's off line (in cmd). another thing, - as soon as I connect it the Manager shows everything is fine, then I open cmd, go to cd C:\ (everything is still ok in the Manager) but as soon as I type mini-sdk (the adb folder), the Android USB at the top of the Manager stays the same but Removable Devices gers a triangle. any clue??? Jesus, I was there, everything was fine, I've got a backup of stock rom after flashing twrp but now a brick.
here it is
I was using mini-sdk but just now installed 15 seconds ADB program and tried with it... same sh**. it sees it but the status is offline... tested on my Galaxy s5, works just fine. wtf? did I hardbricked my htc?! can it actually see the # but be Offline. still on htc logo.
p. s. on connecting the s5, in the line where htc (pic above) has yellow triangle, it's not there on s5.is there a solution? double pressing on HTC with yellow triangle and in the window popping up in General tab it says, - Impossible to start (code 10).
and another thing... i honestly don't remember if I enabled Debugging when I flashed ARHD Rom... is it On by default in custom roms in htc?
---------- Post added at 03:56 PM ---------- Previous post was at 03:21 PM ----------
alray said:
Exactly and if the phone isn't detected or is incorrectly detected (yellow triangle with an exclamation mark) take a screenshot of your windows devices manager and post it here.
Click to expand...
Click to collapse
look at this... the craziest sh**. look at the commands... on adb reboot - device not found, on adb devices - it shows up but as offline and at that exact moment HTC line on Manager changes to a yellow triangle but not before.
pic
methoddon1 said:
pic
Click to expand...
Click to collapse
You can't use adb if the phone isn't fully booted to the OS or booted in a custom recovery. What version of android or what firmware version is installed on the phone? The Xposed version you need to install depends the android version that is installed on the phone. Bootloop caused by xposed is something easy to fix normally, but you need to get in recovery mode which is a problem without a working volume down key
alray said:
You can't use adb if the phone isn't fully booted to the OS or booted in a custom recovery. What version of android or what firmware version is installed on the phone? The Xposed version you need to install depends the android version that is installed on the phone. Bootloop caused by xposed is something easy to fix normally, but you need to get in recovery mode which is a problem without a working volume down key
Click to expand...
Click to collapse
I know.... (about the volume)... it was on official 5.0... when I was done with it, it was with a latest twrp and ARHD 92.0 Rom installed. everything was fine... i didn't spend much time on it (had to set it all up), so restored everything with Titanium but instead of waiting for my wife to come back from work (I'm sure I didn't even delete the RIGHT xposed zip. it's still on her phone), I've decided to go and f*** it all up by just flashing the wrong one ....
---------- Post added at 04:24 PM ---------- Previous post was at 04:13 PM ----------
so you're saying it's either fixing a volume rocker or throwing it out?! but the thing is, because I was planning on changing the casing anyway, i took off the back cover to have access to the volume down button and I can feel a weak click but it's there (the click) and couldn't enter a fastboot anyway. f*******ck.
methoddon1 said:
I know.... (about the volume)... it was on official 5.0... when I was done with it, it was with a latest twrp and ARHD 92.0 Rom installed. everything was fine... i didn't spend much time on it (had to set it all up), so restored everything with Titanium but instead of waiting for my wife to come back from work (I'm sure I didn't even delete the RIGHT xposed zip. it's still on her phone), I've decided to go and f*** it all up by just flashing the wrong one ....
Click to expand...
Click to collapse
xposed-v74-sdk21-arm.zip should have worked fine on ARHD 92 (android 5.0.2) but flashing xposed can sometimes cause boot problems, even simply enabling a module can cause boot problems. That was a little risky to do it on a that phone since you need adb to reboot in recovery/bootloader because of the broken volume button.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
methoddon1 said:
so you're saying it's either fixing a volume rocker or throwing it out?! but the thing is, because I was planning on changing the casing anyway, i took off the back cover to have access to the volume down button and I can feel a weak click but it's there (the click) and couldn't enter a fastboot anyway. f*******ck.
Click to expand...
Click to collapse
Unfortunately yes.
Like I said this problem should be easy to fix, but without access to the bootloader or the recovery, there is not much you can do
ok thanx.
I wish youd reminded of that earlier... I've been using Samsung for too long...
deleted
Related
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 (WILL ALSO WORK FOR 4.2, just use the correct file that I link to) on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Thank you =) will try
-Google
I hope people actually watch and learn from this tutorial instead of waiting around for some point and click tool powered by unicorn blood and hamsters. It's an excellent tutorial and gets you in touch with your device by using the exact tools Google provided you to use for this exact thing.. Use them, they are invaluable.
This means we can't use the old method of putting update.zip file in the root folder and let the system upgrades by itself.
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
EDIT: I'm bone stock, no root.
DirkBelig said:
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
Click to expand...
Click to collapse
I have the same exact same problem, except my bootloader is unlocked. Tried everything I could think of, and it still doesn't go into android recovery.
Insert your USB cable and make sure it's plugged into a charger or PC.. Recovery won't appear unless you are plugged in. It's an odd bug fixed when you update
I've been plugged in to both a charger and the PC. Come on, if I've fired off adb recovery reboot, doesn't that automatically suggest that I'm connected to the computer? I press Power+Volume Up and it does NOT instantly go to the screen it should, but brings up a Google logo and sits there forever.
styckx said:
Insert your USB cable and make sure it's plugged into a charger or PC.. Recovery won't appear unless you are plugged in. It's an odd bug fixed when you update
Click to expand...
Click to collapse
Doesn't work in either case, it just hangs until the hard reboot kicks in.
DirkBelig said:
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
EDIT: I'm bone stock, no root.
Click to expand...
Click to collapse
Omega360 said:
I have the same exact same problem, except my bootloader is unlocked. Tried everything I could think of, and it still doesn't go into android recovery.
Click to expand...
Click to collapse
I had the exact same issues. Turns out, I had to hold my volume button directly in the middle while holding power.
ShannonMS81 said:
I had the exact same issues. Turns out, I had to hold my volume button directly in the middle while holding power.
Click to expand...
Click to collapse
THIS WORKED!!!!!!
OMFG!!! I burned the time I was going to watch the making of Prometheus Blu-ray trying to get this stupid thing to work! Where were you hours ago, man?!?!? Thank you!!! Better late than never.
Glad you got it.. BTW.. I did-misread what you said and yes, you would have had a USB cable in. All these posts are running together of people asking for help and having issues. Mah poor brain is getting em all mixed together.
Nexus 7 needs a coffee maker attachment!
qbking77 said:
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Click to expand...
Click to collapse
Great video! I might just be using this in the near future. I plan on waiting for the factory image (I just like having a full install on my devices when possible) instead of using just the zip file (that is if I dont get the update). Although if the update isnt showing up sometime soon then this is going to work for me just fine.
qbking77 said:
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Click to expand...
Click to collapse
can't enterthe stock recovery since i instaled CWM. removing it would bring the stock back ?
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Same issue, when I "adb device" it will sometimes show as "device" and other times as something else (don't recall but not device). I can get into recover via "adb reboot recovery" and then into "update via adb" but when I "adb sideload.....(see above)" it just runs through the different commands as if "sideload" is not an option? Followed the video to a "T" and nothing.....thinking about rooting and doing it the old fashion way but this is the first android device I've had that I've not seen a reason to root right away...maybe should just wait for the OTA?
Ram1500 said:
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Click to expand...
Click to collapse
While in stock recovery and in the "apply update from adb" screen, type in the command window "adb devices". It should say:
<your device serial number> sideload
If it does not, check the drivers in device manager. You may need to manually install it. I had to on mine.
Cheers qbking77, worked a treat.
First time I pushed using adb & after following your tut life is good. Thanks again!
Ram1500 said:
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Click to expand...
Click to collapse
You may be using an older version of adb that does not support the sideload command.
Jwoc12 said:
Same issue, when I "adb device" it will sometimes show as "device" and other times as something else (don't recall but not device). I can get into recover via "adb reboot recovery" and then into "update via adb" but when I "adb sideload.....(see above)" it just runs through the different commands as if "sideload" is not an option? Followed the video to a "T" and nothing.....thinking about rooting and doing it the old fashion way but this is the first android device I've had that I've not seen a reason to root right away...maybe should just wait for the OTA?
Click to expand...
Click to collapse
It should say 8sdgfs3JKSDBFkjk3 device or something like that. If it does not, you need to install the the correct driver.
My computer did not recognize my tablet at first. I went to this thread and installed PDAnet which installed the driver.
http://forum.xda-developers.com/showthread.php?t=1809195
I was trying to flash one of the kitkat based new roms i found on this site through the app and it didn't seem to work as i recieved the message saying installation aborted, then my phone buzzed and flashed and restarted but it's stuck on the htc quietly brilliant screen and i cannot get to recovery at all. when i try i see the lights at the bottom menu buttons just flashing.
I did a backup before the install but can't get into recovery now. i've found a proper nandroid backup but my phone wont turn off,restart or go into recovery now, so pissed. please help asap
p.s. the rom i can't even remember the name of it but it said it was one for all versions of htc one.
mine is the canadian version on rogers if it matters.
.and it looks like my computer isn't recognizing it now either
playboypaul said:
I was trying to flash one of the kitkat based new roms i found on this site through the app and it didn't seem to work as i recieved the message saying installation aborted, then my phone buzzed and flashed and restarted but it's stuck on the htc quietly brilliant screen and i cannot get to recovery at all. when i try i see the lights at the bottom menu buttons just flashing.
I did a backup before the install but can't get into recovery now. i've found a proper nandroid backup but my phone wont turn off,restart or go into recovery now, so pissed. please help asap
p.s. the rom i can't even remember the name of it but it said it was one for all versions of htc one.
mine is the canadian version on rogers if it matters.
.and it looks like my computer isn't recognizing it now either
Click to expand...
Click to collapse
What I'm gonna say is ridiculous! BUT IF YOU DIDN'T **** UP YOUR BOOTLOADER you should be able to boot into the bootloader by performing these steps:
First: Press the power and volume up/down button for about two minutes... your phone should respond with vibrate/flashing...
Secondly: Hold your phone under a bright light and press the powerbutton for a minute or so... then try different combinations with the hardwarebutton until it boots into the bootloader.
From bootloader you can perform the following steps to get a OS working on your phone:
This is a quote by me, someone had almost the same problem like you:
Okay, first here you have the correct adb and fastboot files, I uploaded them quickliy for you, I think this way they should work properly:
http://uploaded.net/file/ykwya517
Next thing are these HTC Drivers, in this post are a few of them: http://forum.xda-developers.com/show....php?t=2089508 and on my computer there are the 4.3.0.001 drivers, so I'd recommand downloading those(Credits go to @mdmower):
http://www.mediafire.com/download/n5...+4.3.0.001.exe
Now shut down your phone and boot in into the bootloader with pressing the power button and the volume down button. Then select fastboot and enter this menu. Now if the drivers are installed correctly there should be written FASTBOOT USB. I think you said you are unlocked... so the following command should run just fine. Open a command prompt and navigate to the folder where adb and fastboot are placed. In this folder you copy your custom recovery(TWRP) and you flash it with this command:
Code:
Code:
fastboot flash recovery [recoveryname].img
And DON'T worry about adb in the bootloader! ADB doesn't work with the bootloader. Now you boot into your recovery by chosing Recovery somewhere in your bootloader. If you are in the bootloader you somehow need to push the ROM to your HTC One... This should work with this command...
Code:
adb push "C:\FolderWhereRomIsStored\rom.zip" "/data/media/0/rom.zip"
Click to expand...
Click to collapse
And if this doesn't copy it correctly simply place your zip on your computer to a folder that is empty and push this folder to your HTC One with:
Code:
adb push "C:\FolderWhereRomIsStored" "/data/media/0"
Click to expand...
Click to collapse
Now you are good to go, simply flash the zip form TWRP. I think you know how this works Simply go to install and then chose the zip and flash it.
If you now want to s off... then ask me again. I'll give you an advice
Click to expand...
Click to collapse
Thanks I got it working finally but it was sticking on the HTC screen for over an hr twice and the lamp worked within 10 seconds to get into recovery? I was so amazed that the lamp worked that I did it again and same results, stuck on HTC screen and the light worked again. That's to awesome. Thanks
Sent from my HTC One using xda app-developers app
playboypaul said:
Thanks I got it working finally but it was sticking on the HTC screen for over an hr twice and the lamp worked within 10 seconds to get into recovery? I was so amazed that the lamp worked that I did it again and same results, stuck on HTC screen and the light worked again. That's to awesome. Thanks
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
The funny thing is that I don't believe it neither.. but if someone has this kind of error it always works However, nice to know that your device is back alive... if you have any further questions reply/quote this comment so I get notified
LibertyMarine said:
The funny thing is that I don't believe it neither.. but if someone has this kind of error it always works However, nice to know that your device is back alive... if you have any further questions reply/quote this comment so I get notified
Click to expand...
Click to collapse
Hello again I'm glad I found you on find myself with almost the same exact issue as before, this time I've accidentally deleted my OS but I can boot to bootloader and my twrp although my device HTC m7 isn't recognised by my computer or when I try an adb push to the device. I have android sdk installed and the HTC sync manager and the drivers are installed but when I plug device says drivers are Not installed?
playboypaul said:
Hello again I'm glad I found you on find myself with almost the same exact issue as before, this time I've accidentally deleted my OS but I can boot to bootloader and my twrp although my device HTC m7 isn't recognised by my computer or when I try an adb push to the device. I have android sdk installed and the HTC sync manager and the drivers are installed but when I plug device says drivers are Not installed?
Click to expand...
Click to collapse
Hey there. It's quite some time ago since I last "played around" with my HTC One M7 but I think I am still able to help you solve your problem.
Firsr a few questions:
> What OS are you using for adb? Win7/8/10?
> Do you have an USB OTG cable? (would make fixing very easy. You just copy the OS zip onto an USB stick and then plug it into your Cellphone using an OTG cable. Then flashing can be done without any problems)
If you've already solved your problem, notify my anyways
LibertyMarine said:
Hey there. It's quite some time ago since I last "played around" with my HTC One M7 but I think I am still able to help you solve your problem.
Firsr a few questions:
> What OS are you using for adb? Win7/8/10?
> Do you have an USB OTG cable? (would make fixing very easy. You just copy the OS zip onto an USB stick and then plug it into your Cellphone using an OTG cable. Then flashing can be done without any problems)
If you've already solved your problem, notify my anyways
Click to expand...
Click to collapse
sorry i was at work but OS is windows 7 home premium
maybe i should look into the OTG cable.
i get a message saying "cannot read rom.zip" when trying to use command line to push as per the thousands of tutorials online lol.
when i plug in the phone to computer and turn phone on (which is on the HTC splash screen since no OS) then a popup on computer says installing device driver software.
Android Phone X Device Unplugged
USB Composite Device Ready to use
HTC MTP Device X Failed
USB storage devie Ready to use
My HTC Ready to use
HTC android USB Device Ready to use
my cable is really wobbly and none ive tried lately seem to want to fit in the slot snug so HTC MTP Device installed again and now says "Ready to Use also, then cycled the install again and settled on FAILED so only Android Phone has an X for device unplugged since no OS to turn on and HTC MTP has an X for Fail. this is where ill enter fastboot mode or recovery to try push/flash my copy of cm14 and gapps to the device.
i have cmd window open with rom and gapps and an updated version of twrp in adb and fastboot folder.
i entered fastboot mode and pushed recovery through then as per the tutorial i then entered recovery which flashed properly with the new version. then i went to adb sideload and all commands worked like adb kill-sever and adb usb also adb devices came with text saying list of attached devices which theyre is none.
then adb sideload rom.zip came back with:
error: device not found
I picked up an M7 with a busted power button and want to root it because, reasons.
I'm on KK 4.4.2 with Sense 6 (use Nova Launcher though) and my kernel version is 3.4.10-gb9492d4 [email protected] #1 SMP PREEMPT
I looked through some similar threads about this for Samsung and Nexus devices and found that I can use 'adb' in cmd on Windows to reboot/boot to recovery and such but when further researching I couldn't find "step 1". Any atempts to do it in cmd came back with errors saying I could not do it due to missing something, or in the case of a GUI assisted Windows tray app I found on XDA(can't remember name), saying no device was detected at all.
I also read some business about having to have "fastboot" enabled but without a power button and a having a metal unibody phone I'm still stuck.
Sorry if this has been covered but I Googled extensively and kept coming back to "but where do I start?" I have rooted a Samsung S3 before but obviously it was a different process considering I have all working buttons on the thing.
Thanks for any help!
Zertonshfits said:
I picked up an M7 with a busted power button and want to root it because, reasons.
I'm on KK 4.4.2 with Sense 6 (use Nova Launcher though) and my kernel version is 3.4.10-gb9492d4 [email protected] #1 SMP PREEMPT
I looked through some similar threads about this for Samsung and Nexus devices and found that I can use 'adb' in cmd on Windows to reboot/boot to recovery and such but when further researching I couldn't find "step 1". Any atempts to do it in cmd came back with errors saying I could not do it due to missing something, or in the case of a GUI assisted Windows tray app I found on XDA(can't remember name), saying no device was detected at all.
I also read some business about having to have "fastboot" enabled but without a power button and a having a metal unibody phone I'm still stuck.
Sorry if this has been covered but I Googled extensively and kept coming back to "but where do I start?" I have rooted a Samsung S3 before but obviously it was a different process considering I have all working buttons on the thing.
Thanks for any help!
Click to expand...
Click to collapse
Ok well assumeing you already have adb/fastboot and the drivers for your Device installed you need Fast boot disabled in power settings. And Usb debugging enabled in developer options.
While the phone is booted to the Android OS go to
Settings>Power at the very bottom is the option "Fast boot" make sure this is disabled. Now go to
Settings>Developer Options and enable "Usb debugging"
Now you should be able to boot recovery from the adb command window with
Code:
adb reboot recovery
Or
adb reboot-bootloader
Be very careful flashing roms though. Make sure your recovery is tested and working with the Rom your going to install. If you end up in a bootloop there's very little chance of rescuing it without functional volume keys
Edit :- P.S if you don't see developer options in your settings menu go to
Settings>About>Software Information>More and tap on the Build Number repeatedly untill it says you are now a developer :good:
Danny201281 said:
Ok well assumeing you already have adb/fastboot and ...
Click to expand...
Click to collapse
Ah ha! The 'assume' part is what gets me.
How to I 'get' adb? I assumed that it was a command baked into cmd.
I do have dev options enabled and my drivers installed. Also to clarify my volume buttons are fine, its my power button that is dead.
I woouuuuld like to try some ROMs but untill I get the button actually fixed ill probably stick to xposed and the like to get more out of it, just in case.
Thanks for the quick reply. Once Im able to boot it into different modes should be just the regular process right? (Unlock BLer, custom recov, bing bang boom?)
Zertonshfits said:
Ah ha! The 'assume' part is what gets me.
How to I 'get' adb? I assumed that it was a command baked into cmd.
I do have dev options enabled and my drivers installed. Also to clarify my volume buttons are fine, its my power button that is dead.
I woouuuuld like to try some ROMs but untill I get the button actually fixed ill probably stick to xposed and the like to get more out of it, just in case.
Thanks for the quick reply. Once Im able to boot it into different modes should be just the regular process right? (Unlock BLer, custom recov, bing bang boom?)
Click to expand...
Click to collapse
See this easy installer and guide for adb/fastboot http://forum.xda-developers.com/showthread.php?t=2317790
:good:
Then you can use fastboot to flash a recovery and install a Rom
Woohoo! Ill post my findings when I get a sec to try it!
Anyone have any problems getting the Axon work correctly with Windows?
I am trying to use helium to back up/restore data from my PC (I would use Titanium but I haven't rooted the Axon). I have no problems with my Nexus 5 but Windows is throwing all sorts of errors when I try to copy files to the Axon (any file starting with "." like ".media" it doesn't like. When trying to connect via adb (e.g. like running "adb devices" to see what devices are connected) I see no devices.When the Axon is connected in device manager I see under "Other devices" "ADB interface" but windows indicates no driver available.
Are there current ZTE drivers available somewhere? Helium points to some (ZTEUSBHostDriver5.2066.1.6-signed) but they look very old...with files dating back to 2010...and I couldn't get these to work anyway (I am currently using Windows 8.1).
Any feedback would be much appreciated. I have also raised a ticket with ZTE support and they said they would get back to me tomorrow.
That's strange. I'm on Windows 10, plugged in phone, drivers installed, showed up as A1P and moved all music to device without issue. Didn't try anything elaborate though.
I've gotten ADB to recognize it, but it looks to be only for sideloading. I'm trying to figure out how to boot straight into fastboot, but I'm not sure of the button combination. So far I have, Volume down + Power goes into Factory Test Mode (FTM), but this isn't recognized in WIndows so far for me so I'm not sure how useful it is (unless the drivers could help). Volume up + power goes into Android system recovery which is where I can "Apply update from ADB" but I'm not able to fastboot from there for some reason (I was hoping it might be this easy). Also, if I "reboot to bootloader", the phone just boots up normally, which is also strange. Finally, Volume up and down + power just seems to boot into a blank screen with the Home button lit up. Not sure what this screen is, but ADB doesn't seem to recognize it either.
That being said, I'm not a pro at this so any help would be appreciated. I would love OEM unlock and root ASAP! Thanks.
Sithben24 said:
I've gotten ADB to recognize it, but it looks to be only for sideloading. I'm trying to figure out how to boot straight into fastboot, but I'm not sure of the button combination. So far I have, Volume down + Power goes into Factory Test Mode (FTM), but this isn't recognized in WIndows so far for me so I'm not sure how useful it is (unless the drivers could help). Volume up + power goes into Android system recovery which is where I can "Apply update from ADB" but I'm not able to fastboot from there for some reason (I was hoping it might be this easy). Also, if I "reboot to bootloader", the phone just boots up normally, which is also strange. Finally, Volume up and down + power just seems to boot into a blank screen with the Home button lit up. Not sure what this screen is, but ADB doesn't seem to recognize it either.
That being said, I'm not a pro at this so any help would be appreciated. I would love OEM unlock and root ASAP! Thanks.
Click to expand...
Click to collapse
I've been trying the same thing with the button combos
I don't think the camera button is doing anything. Do you know how to sideload SU or twrp/cwm? I think I could get that possibly. I also tried king root which looked like it worked but didn't.
I booted into the blank screen with the glowing home button. My computer is recognizing it as "Handset Diagnostic Interface (DFU)" I'm assuming this is a debug mode for the factory. No separate drivers downloaded for this mode.
Hmmm. It seems to work better on a Mac. I didn't have any problems on the Mac using adb with the Axon.
I used the Google drivers that come with the SDK tools from the Android SDK.
Any progress on root?
augie7107 said:
Any progress on root?
Click to expand...
Click to collapse
I've used a few of the quick root tools, but nothing so far. Everything seems to fail at the end, and I still can't get into fastboot.
watch it'll be backwards and you'll have to root it first to get into fastboot to unlock it.
gflash2015 said:
Anyone have any problems getting the Axon work correctly with Windows?
I am trying to use helium to back up/restore data from my PC (I would use Titanium but I haven't rooted the Axon). I have no problems with my Nexus 5 but Windows is throwing all sorts of errors when I try to copy files to the Axon (any file starting with "." like ".media" it doesn't like. When trying to connect via adb (e.g. like running "adb devices" to see what devices are connected) I see no devices.When the Axon is connected in device manager I see under "Other devices" "ADB interface" but windows indicates no driver available.
Are there current ZTE drivers available somewhere? Helium points to some (ZTEUSBHostDriver5.2066.1.6-signed) but they look very old...with files dating back to 2010...and I couldn't get these to work anyway (I am currently using Windows 8.1).
Any feedback would be much appreciated. I have also raised a ticket with ZTE support and they said they would get back to me tomorrow.
Click to expand...
Click to collapse
OK, I missed the obvious. When you connect to the PC and choose "Install Driver" it appears as a new drive on your PC with an auto-run to install the driver (I thought I had tried this before and didn't see anything). Now I can access adb from my PC. Still has problems with files starting with "." though (the Nexus 5 doesn't have this problem).
Source code is out now. http://opensource.ztedevice.com/ should be the first option, A1P.
Sounds to me like the phone has two boot loaders like other new ZTE phones
dligon said:
watch it'll be backwards and you'll have to root it first to get into fastboot to unlock it.
Click to expand...
Click to collapse
Cant wait for root, i guess well have to wait a little longer, this area looks like a desert.
Nal Rodriguez said:
Cant wait for root, i guess well have to wait a little longer, this area looks like a desert.
Click to expand...
Click to collapse
Haha yeah I know! Supposedly the ZTE phones could be bootloader unlocked via fastboot oem unlock, but only if we could get to fastboot mode.
Archfeind2 said:
Haha yeah I know! Supposedly the ZTE phones could be bootloader unlocked via fastboot oem unlock, but only if we could get to fastboot mode.
Click to expand...
Click to collapse
Sent from my ZTE Blade L3 Apex using XDA Free mobile app
---------- Post added at 05:19 PM ---------- Previous post was at 05:15 PM ----------
903tex said:
Sounds to me like the phone has two boot loaders like other new ZTE phones
Click to expand...
Click to collapse
Sent from my ZTE Blade L3 Apex using XDA Free mobile app
adb reboot bootloader also just reboots the phone from ADB. There has to be a way to get into the bootloader on this phone. I can get to factory test mode and a blank screen with the home light turned on as well as the stock recovery. grrr...
delete
So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks
jgro1976 said:
So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks
Click to expand...
Click to collapse
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.
Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
MDV106 said:
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.
Click to expand...
Click to collapse
Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
jgro1976 said:
Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
Click to expand...
Click to collapse
Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
jgro1976 said:
Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
Click to expand...
Click to collapse
jgro1976 said:
Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
Click to expand...
Click to collapse
Im guessing you finally realised they after getting the android icon with the red triangle u have to press volume up and hold it then tap the power key to enter the recovery. Good to know you managed to unlock the bootloader eventually.
A lot of people have been having issues with fastboot, especially on Windows machines . Try restarting the shell or use a different USB port on your computer?also maybe try a different driver version and see if it helps.