[Q] Soft Bricked my m7, adb and fastboot not working - One (M7) Q&A, Help & Troubleshooting

I created a backup using twrp 2.6 , and just to be sure I tried restoring it, however it failed to restore and now i cant boot. I've bootloader and recovery working, however neither fastboot or adb sideloading is working so that i can flash another rom.
Please Help :crying:

akshat10 said:
I created a backup using twrp 2.6 , and just to be sure I tried restoring it, however it failed to restore and now i cant boot. I've bootloader and recovery working, however neither fastboot or adb sideloading is working so that i can flash another rom.
Please Help :crying:
Click to expand...
Click to collapse
sorry to answer you with more questions, but.....
what is the complete version of your recovery? 2.6.0.0? 2.6.3.3?
Why does it failed? any error message? What partitions did you backed-up and restored?
What is your adb version? you need 1.0.29 and above to use sideload
Code:
adb version
do you have installed your drivers to use fastboot and adb? What does it say in windows device manager when your phone is in bootloader? and in recovery?
What is your computer OS?
What is your bootloader version?

alray said:
sorry to answer you with more questions, but.....
what is the complete version of your recovery? 2.6.0.0? 2.6.3.3?
Why does it failed? any error message? What partitions did you backed-up and restored?
What is your adb version? you need 1.0.29 and above to use sideload
Code:
adb version
do you have installed your drivers to use fastboot and adb? What does it say in windows device manager when your phone is in bootloader? and in recovery?
What is your computer OS?
What is your bootloader version?
Click to expand...
Click to collapse
Hi, thanks for the help,
1. Version of recovery 2.6.3.0
2. The backup was successfully created, i still have it, but when im trying to recover it it does not give any error message the log I get above is:

akshat10 said:
Hi, thanks for the help,
1. Version of recovery 2.6.3.0
Click to expand...
Click to collapse
2.6.3.0 is outdated. Latest version is 2.7.1.1 but we recommend using 2.6.3.3 or 2.6.3.4
2. The backup was successfully created, i still have it, but when im trying to recover it it does not give any error message the log I get above is:
Click to expand...
Click to collapse
is ?
waiting for 3-4-5-6

Hi, thanks for the help,
1. Version of recovery 2.6.3.0
2. The backup was successfully created, i still have it, but when im trying to recover it it does not give any error message the log I get above is:
[RESTORE STARTED]
It restores the boot, and data.
then, I see:
Wiping System
Formatting System using make_ext4fs function.
Restoring System...
and then I see a message Failed flashed at the top of the scree.
3. adb version is 1.0.31
4. My drivers worked perfectly tomorrow, thats when I rooted my m7,so today I thought of flashing a custom rom, I took a backup using twrp and just to be sure it was all backed up, I tried restoring it, however it failed with the same message,also today the drivers dont seem to be working after the failed restoration, the device manager shows it as a portable device today when connected in recovery, whereas was showing it as an android device yesterday.
When in fastboot mode, a message showing installing android 1.0 is flashed and the phone also shows connected to FASTBOOT USB, but the fastboot devices command returns nothing and so does the adb devices command.
5. I have a windows 8.1 system.
6.Bootloader Details are:
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OPEN-DSP- v32.120.274.0909
OS-5.12.707.104
Sorry, I'm completely new to this, thanks for your help !

akshat10 said:
4. My drivers worked perfectly tomorrow
Click to expand...
Click to collapse
well wait for tomorrow yeah i know, you meant yesterday...
First you will need to fix your drivers issue.
try this fix:
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways​
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
if it doesn't works, try different usb ports, different cables even another computer (best would be a win 7 computer, not 8.1). make sure you are not using any usb hub, connect phone dirrectly to computer, usb 2.0 ports preferred.
then when your drivers will be fixed. flash twrp 2.6.3.3 (anyway almost all newer rom required at least 2.6.3.3), clear cache and boot in recovery. try to restore the backup again. if it still fail, you'll be able to push and flash a rom to your phone.
also post the output of ''fastboot getvar all'' except imei and serialno when your drivers issues are fixed.
---------- Post added at 09:21 AM ---------- Previous post was at 09:16 AM ----------
im out for today, but im sure other members will comes here to assist. ill be back tomorrow
good luck

Got it working, turns out the drivers were fine, you have to switch the HTC Sync Manager once and the drivers start working properly.
Thanks for your help.
Would be grateful if you can give a guide to choosing a rom to flash ( odexed or de-odexed)
Thanks !

akshat10 said:
Got it working, turns out the drivers were fine, you have to switch the HTC Sync Manager once and the drivers start working properly.
Thanks for your help.
Would be grateful if you can give a guide to choosing a rom to flash ( odexed or de-odexed)
Thanks !
Click to expand...
Click to collapse
There is no guide for choosing a rom here, because rom comparison threads aren't allowed. Rom preferences are always subjective, you will need to find one that fits what you need.
http://forum.xda-developers.com/htc-one#romList
always read the rom OP carefully before flashing. Some roms have specific requirements. (i.e using a specific recovery, or s-off requirement for GPE roms)

Related

[Q] Wiped my phone in TWRP, Now ADB does not work, and I'm stuck.

My computer says "error: device not found" when trying to execute any ADB command.
Fastboot Devices = Detection, but I cannot do anything because ADB does not work.
I also cannot flash any recoveries, and doing so results in a boot loop.
I currently have NO rom running. I've been stuck for now, 4-5 hours.
Thanks.
When my recovery DID work, I could not flash through OTG USB because nothing was detected, and TWRP sideload was also broken.
After that, my recovery mysteriously stopped working, and I can't re-flash any recoveries because ADB fails to find any devices. I've repeatedly attempted to uninstall, and install drivers, but nothing seems to work.
RUU's also fail because they are out of date, and an updated one does not exist. (To fix this problem i need S-OFF which i need ADB function to do... #sadlyfe)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
^ Ran the RUU again, same error, and it's about the bootloader.
Just RUU and start over. When I installed the newest twrp yesterday I wiped everything including internal storage and I was planning on side loading a rom but I couldn't get adb to recognize the phone so I was stuck also. I just ran the RUU and started over. I think the newest twrp has issues when trying to use adb or something.
Lancerz said:
Just RUU and start over. When I installed the newest twrp yesterday I wiped everything including internal storage and I was planning on side loading a rom but I couldn't get adb to recognize the phone so I was stuck also. I just ran the RUU and started over. I think the newest twrp has issues when trying to use adb or something.
Click to expand...
Click to collapse
When trying to RUU i run into an error, and i'm guessing that's from being on 4.3 firmware or something that i don't know
Oh yeah I'm S-off so I had no problems. So I guess you are S-on then? I was on the 4.3 firmware also.
Lancerz said:
Oh yeah I'm S-off so I had no problems. So I guess you are S-on then? I was on the 4.3 firmware also.
Click to expand...
Click to collapse
Yep, S-ON
Because I am S-ON, I can't change the fact that it says TAMPERED and RELOCKED SECURITY WARNING, which is probably preventing from the RUU from running.
There is a post somewhere that will show you how to get s-off from where you're at. I'll see if I can find it
Google universal naked HTC one drivers,make sure HTC sync is uninstalled and disable any antivirus and firewalls, including Windows firewall.
Sent from my HTCONE using xda app-developers app
Konfuzion said:
Google universal naked HTC one drivers,make sure HTC sync is uninstalled and disable any antivirus and firewalls, including Windows firewall.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Thanks, I'm going to try that right now.
Still nothing
EDIT: Restarted computer, no detection.
Anyone have any clue?
dmarkmd5 said:
Anyone have any clue?
Click to expand...
Click to collapse
Long shot, try a different usb port? And don't plug the phone in until you are booted into fastboot. Also make sure your android sdk is up to date, I have heard it wasn't working for some people with 4.3 until they updated it.
Also maybe try this with phone connected in fastboot
1. Download the Universal Naked Drivers
2. Unzip to any location you want. Just remember where you put them.
3. Plug in your phone to your USB cable.
4. Open your Device Manager (Windows Key + X and select Device manager) and locate HTC under Other Devices and right click on it and select Update Driver Software
5. Select "Browse my computer for driver software"
6. Click Browse and then select the folder you unzipped with the drivers in it then click next.
7. It should now install your drivers and then in your device manager it will now show up "My HTC" under Android USB Devices.
Sent from my HTCONE using xda app-developers app
im in the same boat
Konfuzion said:
Long shot, try a different usb port? And don't plug the phone in until you are booted into fastboot. Also make sure your android sdk is up to date, I have heard it wasn't working for some people with 4.3 until they updated it.
Also maybe try this with phone connected in fastboot
1. Download the Universal Naked Drivers
2. Unzip to any location you want. Just remember where you put them.
3. Plug in your phone to your USB cable.
4. Open your Device Manager (Windows Key + X and select Device manager) and locate HTC under Other Devices and right click on it and select Update Driver Software
5. Select "Browse my computer for driver software"
6. Click Browse and then select the folder you unzipped with the drivers in it then click next.
7. It should now install your drivers and then in your device manager it will now show up "My HTC" under Android USB Devices.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
This is what my Android SDK looks like
and yeah, i uninstalled the drivers, restarted, installed naked htc one drivers, restarted, and still nothing from adb device.
Surprise I GOT SOMETHING!
http://i.imgur.com/U9LfolR.png
Surprise I GOT SOMETHING!
http://i.imgur.com/U9LfolR.png
now you can help me
The solution to this problem was beyond simple, and just plain stupid....
the solution was to flash Installing PhilZ Touch[CWM Advanced Edition]
by sending this command while on fastboot usb fastboot flash recovery philz_touch_5.11.2-m7spr.img
That's all it took, then i go into recovery, activate ADB sideload, it accepts it, goes to 100%, wait for the flash, reboot and bam i'm working again.
..... be iight back
---------- Post added at 04:30 AM ---------- Previous post was at 04:19 AM ----------
flashed phiz touch stl get device not found
lburner said:
..... be iight back
---------- Post added at 04:30 AM ---------- Previous post was at 04:19 AM ----------
flashed phiz touch stl get device not found
Click to expand...
Click to collapse
Did you go into the phillZ adb sideload mode?
dmarkmd5 said:
Did you go into the phillZ adb sideload mode?
Click to expand...
Click to collapse
yup
---------- Post added at 05:09 AM ---------- Previous post was at 05:01 AM ----------
Thankz man i got it, needed the Universal_Naked_Driver_0.73 too ****ing windows 8 will make your kill yoursf
Relocked bootloader isn't the problem. I had an unlocked bootloader and use used the fastboot oem lock command to relock it, then used the RUU to flash back to 1.29
http://forum.xda-developers.com/showthread.php?p=42407269
That is what I use.

Help - cannot enter system after clean installation of Android Revolution

So aftter downloading the Android Revolution and wiping the data, I tried installing the ROM.
However it keeps booting into recovery mode. I have no idea how to fix this.
The phone tries to boot up normally, but fails to do so. It restarts and boots into recovery. (TWRP 2.5.0.0)
I have tried deleting installing a few times. Where I cleared both the cache and dalvik cache.
Still nothing. Is there any way to get another ROM onto my phone now? My computer doesn't recognize the device anymore.
After the installation it says complete, but shows an error: "set_metadata_recursive: some changes failed"
after this it says: "installation was succesful!" and tells me to do 1 full system boot before flashing mods.:crying::crying:
"Update, I found out I used a rom designed for M8 and not M7.
If anyone could help me getting ADB to work and a rom I can flash and pretty much a tutorial. I would be super grateful
So I found a m7 rom. But when trying to push it using ADB it takes a really long time and ends in protocol error.
Aisu64 said:
boots into recovery. (TWRP 2.5.0.0)
Click to expand...
Click to collapse
Here is one problem. You won't be able to flash any recent roms using twrp 2.5.0.0. Update your recovery first: https://dl.twrp.me/m7/
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
make sure you have the latest adb version (1.0.32) using the command:
Code:
adb version
If not update your android sdk-tools: https://developer.android.com/sdk/index.html#Other
Also make sure you have the latest htc drivers installed on your computer
With the latest twrp and drivers you'll be able to transfer a rom to your phone using MTP protocol when booted in twrp main menu (simply drag and drop your file from your computer to your phone storage).
If using newer roms (android 5.0.2) your phone must have a 7.xx.xxx.x firmware installed on it. Older firmware running new roms cam have issues. To determine your firmware version, use the command "fastboot getvar version-main" or "fastboot getvar all"
Finally pushed the files to the phone.
But after installing my phone still keeps entering recovery mode (twrp).
Aisu64 said:
Finally pushed the files to the phone.
But after installing my phone still keeps entering recovery mode (twrp).
Click to expand...
Click to collapse
Did you updated your twrp recovery?
alray said:
Here is one problem. You won't be able to flash any recent roms using twrp 2.5.0.0. Update your recovery first: https://dl.twrp.me/m7/
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Can you help me a little bit? I can't see the device connected unless I'm in recovery. Can I flash a recovery in recovery?
Click to expand...
Click to collapse
Aisu64 said:
Here is one problem. You won't be able to flash any recent roms using twrp 2.5.0.0. Update your recovery first: https://dl.twrp.me/m7/
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Can you help me a little bit? I can't see the device connected unless I'm in recovery. Can I flash a recovery in recovery?
Click to expand...
Click to collapse
afaik, not with 2.5.0.0. If you can't see the device when in bootloader / fastboot usb mode then you have drivers issues. make sur eyou have latest htc drivers installed. If needed download htc sync. This will install htc sync and the latest drivers. Then uninstall htc sync (but don't uninstall the drivers). You don't want HTC sync on your computer because it will interfere with fastboot / adb connectivity.
alray said:
Aisu64 said:
afaik, not with 2.5.0.0. If you can't see the device when in bootloader / fastboot usb mode then you have drivers issues. make sur eyou have latest htc drivers installed. If needed download htc sync. This will install htc sync and the latest drivers. Then uninstall htc sync (but don't uninstall the drivers). You don't want HTC sync on your computer because it will interfere with fastboot / adb connectivity.
Click to expand...
Click to collapse
I have tried deleting, restarting and reinstalling the drivers. But my phone wont show up under devices anymore. I really appreciate your help, but I really have to go to bed as I have a long day at work tomorrow.
Click to expand...
Click to collapse
Aisu64 said:
I have tried deleting, restarting and reinstalling the drivers. But my phone wont show up under devices anymore. I really appreciate your help, but I really have to go to bed as I have a long day at work tomorrow.
Click to expand...
Click to collapse
No problem, go take some rest and I'll help you later :good:
alray said:
No problem, go take some rest and I'll help you later :good:
Click to expand...
Click to collapse
So I've been playing around installing and reinstalling and deleting and restarting my computer.
My computer can see the device only in recovery. Everytime I'm in the bootloader/fastboot menu it dissapears from the device list in ADB.
Is it possible to flash the phone while in recovery?
Aisu64 said:
So I've been playing around installing and reinstalling and deleting and restarting my computer.
My computer can see the device only in recovery. Everytime I'm in the bootloader/fastboot menu it dissapears from the device list in ADB.
Click to expand...
Click to collapse
you won't get any adb connectivity when booted in bootloader / fastboot usb mode. ADB only works from a booted rom with usb debug turned on or from a custom recovery. In bootloader you must use fastboot commands. To see if your phone is detected by your computer when in bootlaoder / fastboot usb mode, use the command "fastboot devices"
If your phone isn't listed with this command, please post a screenshot of your Windows devices manager with the phone connected and booted in bootloader / fastboot usb mode. Also need to know what is your bootloader version? 1.44/1.54/1.55/1.56/1.57 or 1.61 ? You can see this info when booted in bootloader mode
Is it possible to flash the phone while in recovery?
Click to expand...
Click to collapse
You might want to read what I said again:
You won't be able to flash any recent rom using twrp 2.5.0.0
You can't flash a new recovery using twrp 2.5.0.0, you must use fastboot
:good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It says Hboot - 1.44
atm I can't even get it to show up in recovery.
Screenshot: http://imgur.com/So88OLm
Aisu64 said:
It says Hboot - 1.44
atm I can't even get it to show up in recovery.
Screenshot: http://imgur.com/So88OLm
Click to expand...
Click to collapse
ok hboot 1.44 is the oldest one and have compatibility issues with windows 8 and 10. Do you have access to a windows 7 computer?
alray said:
ok hboot 1.44 is the oldest one and have compatibility issues with windows 8 and 10. Do you have access to a windows 7 computer?
Click to expand...
Click to collapse
Yes I do. A super ancient one.
Also this is how it looks like when I'm in recovery: http://imgur.com/SxW9p66
Aisu64 said:
Yes I do. A super ancient one.
Click to expand...
Click to collapse
Please setup everything on this computer (HTC drivers + Android sdk tools (adb and fastboot), this will be much easier to work with Win7 because of your 1.44 hboot. Later, once your hboot will be updated, you'll be able to use your Win10 computer without any problem but for now better to work with Win7. Once you got everything installed on your win7 computer, boot the phone in bootloader / fastboot usb mode and use the command "fastboot devices" to see if your phone is detected. If yes then use "fastboot getvar all" command. take a screenshot of this command output and post it here (censor the IMEI number and the SERIALNO number before uploading your picture). Don't update the recovery for now.
Also this is how it looks like when I'm in recovery: http://imgur.com/SxW9p66
Click to expand...
Click to collapse
Everything is fine here.
alray said:
Please setup everything on this computer (HTC drivers + Android sdk tools (adb and fastboot), this will be much easier to work with Win7 because of your 1.44 hboot. Later, once your hboot will be updated, you'll be able to use your Win10 computer without any problem but for now better to work with Win7. Once you got everything installed on your win7 computer, boot the phone in bootloader / fastboot usb mode and use the command "fastboot devices" to see if your phone is detected. If yes then use "fastboot getvar all" command. take a screenshot of this command output and post it here (censor the IMEI number and the SERIALNO number before uploading your picture). Don't update the recovery for now.
Everything is fine here.
Click to expand...
Click to collapse
You might aswell type the next part. Cuz this will be taking a few hours ^^
Aisu64 said:
You might aswell type the next part. Cuz this will be taking a few hours ^^
Click to expand...
Click to collapse
well I need to see your "fastboot getvar all" before i can tell anything more.
alray said:
well I need to see your "fastboot getvar all" before i can tell anything more.
Click to expand...
Click to collapse
My windows 7 computer keeps asking for a "android 1.0" driver, even though I installed the HTC one m7 driver package downloaded from HTC. I also tried installing HTC Sync, but it doesn't seem to help. Also it only shows "Android 1.0" while in fastboot so I assume this is the fastboot driver?
one more thing. I can't get it to show it's connected to ADB while in recovery.
Aisu64 said:
My windows 7 computer keeps asking for a "android 1.0" driver, even though I installed the HTC one m7 driver package downloaded from HTC. I also tried installing HTC Sync, but it doesn't seem to help. Also it only shows "Android 1.0" while in fastboot so I assume this is the fastboot driver?
one more thing. I can't get it to show it's connected to ADB while in recovery.
Click to expand...
Click to collapse
Strange, it should be easy to make it work on win7. You might want to try this drivers: http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339
alray said:
Strange, it should be easy to make it work on win7. You might want to try this drivers: http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339
Click to expand...
Click to collapse
I borrowed a friends win7 computer and fastboot works! After installing the drivers you linked me to. Here is a screenshot! http://imgur.com/CN0uLu6

Problem with ADB

Hey guys,
i have an big problem with my HTC One M7:
I installed "One_M7_7.15.401.1_stock_system_dump.zip" from HD Revolution to get on Lollipop but it showed an Error and after restarting i cant get into the Phone and i cant get into the recovery. The recovery pops up for like one second or less and throws me into a bootloop.
I wanted to flash a new Recovery via adb/fastboot but my Computer doesnt shows me my device. On the bootloader in the fastboot menu it shows "Fastboot USB" in red.
I installed much different drivers but it just doesnt show up. In device manager it says: Unknown USB Device (device failed enumeration) and the error code 43 in details.
I just dont know what to do anymore...
Anyone got an solution for that?
Mrdestroierr1 said:
Hey guys,
i have an big problem with my HTC One M7:
I installed "One_M7_7.15.401.1_stock_system_dump.zip" from HD Revolution to get on Lollipop
Click to expand...
Click to collapse
Not really sure why you installed this one. This is a non-official/leaked version before the official one was released (7.19.401.2) and the latest version is 7.19.401.51.
but it showed an Error
Click to expand...
Click to collapse
Would help to be more precise, what error exactly?
and after restarting i cant get into the Phone and i cant get into the recovery. The recovery pops up for like one second or less and throws me into a bootloop.
Click to expand...
Click to collapse
What recovery (name + version) is installed on your phone?
I wanted to flash a new Recovery via adb/fastboot but my Computer doesnt shows me my device. On the bootloader in the fastboot menu it shows "Fastboot USB" in red.
Click to expand...
Click to collapse
well at least you have "fastboot usb" which mean there is actually a working data connection between the phone and your ocmputer
I installed much different drivers but it just doesnt show up. In device manager it says: Unknown USB Device (device failed enumeration) and the error code 43 in details.
Click to expand...
Click to collapse
You need the latest drivers from htc. What is your windows version? What is your bootloader version?
sorry i had to make a new account:/
alray said:
Not really sure why you installed this one. This is a non-official/leaked version before the official one was released (7.19.401.2) and the latest version is 7.19.401.51.
Would help to be more precise, what error exactly?
some changes failed
What recovery (name + version) is installed on your phone?
i had cwm but i dont know which version (the m7 was inactive for 1-2 years)
well at least you have "fastboot usb" which mean there is actually a working data connection between the phone and your ocmputer
You need the latest drivers from htc. What is your windows version? What is your bootloader version?
i downloaded the drivers yesterday. i got windows 10 (im now trying with ubuntu). it got hboot 1.44
Click to expand...
Click to collapse
---------- Post added at 03:47 PM ---------- Previous post was at 03:25 PM ----------
I think i got it. Ubuntu worked. thanks alray for your answer. Because of you i checked HBoot 1.44 and this isnt compatible with Windows 10/8. In Ubuntu adb doesnt work but fastboot does. Now i flashed TWRP and installed the Rom again.
Now it boots up but it is in the boot screen since 5 Minutes:/
#Edit It doesnt boot up... and adb doesnt work so i cant push another rom on the phone..
#edit 2 adb works when im in recovery (tought i had to be in bootloader -> fastboot) now it could work with a downloaded nandroid backup :good:
mrdestroierrr1 said:
sorry i had to make a new account:/
Click to expand...
Click to collapse
You shouldn't, its against forum rules
http://forum.xda-developers.com/announcement.php?a=81
You should contact a moderator to disable the other account or this one might also be disabled.
I think i got it. Ubuntu worked. thanks alray for your answer. Because of you i checked HBoot 1.44 and this isnt compatible with Windows 10/8
Click to expand...
Click to collapse
Yep, exactly why I wanted to know, good job.
In Ubuntu adb doesnt work but fastboot does.
Click to expand...
Click to collapse
ADB will only work from a booted rom or from a custom recovery, not in bootloader mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
help htc one m7
I am trying to send a ROOM from the computer to my internal memory via ADB sideload command to be able to install by twrp, so it is not going to talk that it is not possible to read, I tested with ADB devices and perfectly motra my device, someone can you help me?
C:\HTC>adb devices
List of devices attached
SH3ALW904272 sideload
C:\HTC>adb sideload Rom.zip
loading: 'Rom.zip'
* cannot read 'Rom.zip' *
C:\HTC>
ewvisjean said:
I am trying to send a ROOM from the computer to my internal memory via ADB sideload command to be able to install by twrp, so it is not going to talk that it is not possible to read, I tested with ADB devices and perfectly motra my device, someone can you help me?
C:\HTC>adb devices
List of devices attached
SH3ALW904272 sideload
C:\HTC>adb sideload Rom.zip
loading: 'Rom.zip'
* cannot read 'Rom.zip' *
C:\HTC>
Click to expand...
Click to collapse
What version of TWRP are you using?

HTC M8 mini 2 Android System Recovery <3e> loop - no connection via PC possible

Hello, I've done something that my phone didn't like.
I wanted my phone back into default state because of company policies and did not use the correct stock ROM. I used the one for the M8 and not for the M8 One mini 2.
So this is what the current state of the phone is and what I have done so far trying to solve my problem:
The phone keep looping at start up, ending with a red triangle and exclamation point. After a minute or so the phone boots again, and again and again...
When pressing volume up/power button i get into "Android System Recovery". See image for the details.
My computer does not recognize the phone. Installed the HTC drivers, HTC M8 toolkit and Android Studio. I am using the original cable.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
By using the SD card I tried to install the:
- correct firmware (M8_MINI_UL_Firmware_2.19.401.1.zip)
- Nandroid backup
- Change the name of the files (for example to 0P8B20000.zip)
But whatever I do, I get the message "Check CID failed".
Before I started I get this information by using fastboot (yes, when it worked):
bootloader: 3.19.0.0000
version main:
HTC_001
product: htc_memul
0P8B20000
Is there anyone who can help me with this?
mvds_M8 said:
Hello, I've done something that my phone didn't like.
I wanted my phone back into default state because of company policies and did not use the correct stock ROM. I used the one for the M8 and not for the M8 One mini 2.
So this is what the current state of the phone is and what I have done so far trying to solve my problem:
The phone keep looping at start up, ending with a red triangle and exclamation point. After a minute or so the phone boots again, and again and again...
When pressing volume up/power button i get into "Android System Recovery". See image for the details.
My computer does not recognize the phone. Installed the HTC drivers, HTC M8 toolkit and Android Studio. I am using the original cable.
By using the SD card I tried to install the:
- correct firmware (M8_MINI_UL_Firmware_2.19.401.1.zip)
- Nandroid backup
- Change the name of the files (for example to 0P8B20000.zip)
But whatever I do, I get the message "Check CID failed".
Before I started I get this information by using fastboot (yes, when it worked):
bootloader: 3.19.0.0000
version main:
HTC_001
product: htc_memul
0P8B20000
Is there anyone who can help me with this?
Click to expand...
Click to collapse
go to HTC dev website and follow steps to unlock bootloader, ifstill locked.
to connect to pc you must be in bootloader/fasboot not recovery
use the tools here to restore.
plenty of videos in youtube in how to do it.
Good luck
kativiti said:
go to HTC dev website and follow steps to unlock bootloader, ifstill locked.
to connect to pc you must be in bootloader/fasboot not recovery
use the tools here to restore.
plenty of videos in youtube in how to do it.
Good luck
Click to expand...
Click to collapse
Thanks for your reply. I've seen your answers before and downloaded the files. I've managed to get into bootloader and unlocked my phone. It has now the status TAMPERED | UNLOCKED and S-ON.
By using fastboot I flashed:
memul-stock-recovery-2.16.401.1.img
twrp-2.8.1.0-20142812-memul.img
Via TWRP i flashed UPDATE-SuperSU-v2.02.zip
When I reboot in Recovery mode I'm in TWRP v.2.8.1.0.
At this moment i am downloading the file:
0P8BIMG_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.18.401.3_Radio_1.101.1102.19.1017_10.26.4149.00L_release_402779_combined_signed.zip
from this post http://forum.xda-developers.com/one-mini-2/general/stock-ruu-rom-recovry-htc-one-mini-2-t3250020
Is this a the file I should install via TWRP?
mvds_M8 said:
Thanks for your reply. I've seen your answers before and downloaded the files. I've managed to get into bootloader and unlocked my phone. It has now the status TAMPERED | UNLOCKED and S-ON.
By using fastboot I flashed:
memul-stock-recovery-2.16.401.1.img
twrp-2.8.1.0-20142812-memul.img
Via TWRP i flashed UPDATE-SuperSU-v2.02.zip
When I reboot in Recovery mode I'm in TWRP v.2.8.1.0.
At this moment i am downloading the file:
0P8BIMG_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.18.401.3_Radio_1.101.1102.19.1017_10.26.4149.00L_release_402779_combined_signed.zip
from this post http://forum.xda-developers.com/one-mini-2/general/stock-ruu-rom-recovry-htc-one-mini-2-t3250020
Is this a the file I should install via TWRP?
Click to expand...
Click to collapse
i recommend using the one i sent you but if thats a recovery than yes you can using restore option in TWRP
mvds_M8 said:
Hello, I've done something that my phone didn't like.
I wanted my phone back into default state because of company policies and did not use the correct stock ROM. I used the one for the M8 and not for the M8 One mini 2.
So this is what the current state of the phone is and what I have done so far trying to solve my problem:
The phone keep looping at start up, ending with a red triangle and exclamation point. After a minute or so the phone boots again, and again and again...
When pressing volume up/power button i get into "Android System Recovery". See image for the details.
My computer does not recognize the phone. Installed the HTC drivers, HTC M8 toolkit and Android Studio. I am using the original cable.
By using the SD card I tried to install the:
- correct firmware (M8_MINI_UL_Firmware_2.19.401.1.zip)
- Nandroid backup
- Change the name of the files (for example to 0P8B20000.zip)
But whatever I do, I get the message "Check CID failed".
Before I started I get this information by using fastboot (yes, when it worked):
bootloader: 3.19.0.0000
version main:
HTC_001
product: htc_memul
0P8B20000
Is there anyone who can help me with this?
Click to expand...
Click to collapse
For your device looping in boot, you need to flash boot image to solve this issue, since you can't connect with PC you will have to place the file into your SD card and then choose option apply update from SD Card.
As for flashing stock ROM, you can only flash 2.18.xx.xx if you have a similar version or newer version, any older version will only work if you have S-Off, plus you can't flash stock ROM with TWRP you will need to flash stock recovery also through Apply Update from SD Card option to flash stock ROM.
Fully charge your device before performing flashes or you might make the device dead, if you are not sure how much charge do you have, leave it connected to power source for about 1.5 hours, turned off, looping device connected to charge can heat up the device.
I managed to flash the twrp and recovery (both were your files). But my phone only roboot to TWRP.
fastboot getvar all gives version-main: 2.19.401.1 and not 2.16.401.1.
How can I go back to 2.16.4011?
In fastboot it says:
TAMPERED
UNLOCKED
S-ON
mvds_M8 said:
I managed to flash the twrp and recovery (both were your files). But my phone only roboot to TWRP.
fastboot getvar all gives version-main: 2.19.401.1 and not 2.16.401.1.
How can I go back to 2.16.4011?
In fastboot it says:
TAMPERED
UNLOCKED
S-ON
Click to expand...
Click to collapse
You cannot flash both TWRP and stock recovery as, in a way they both are the same thing, you have to use only 1 of them, either Stock Recovery or TWRP.
You will NOT be able to flash any older version with S-On, the only way to get any old OS is to get a Nandroid backup from someone and restore it through TWRP.
What device is yours, Asia, Europe or is it a Network Locked unit ?
If you have TWRP and your device is no more looping, then you can try and restore this Nandroid, if you device is Europe then this will work definitely : https://www.androidfilehost.com/?fid=24052804347818782
STEPS TO RESTORE NANDROID BACKUP THROUGH TWRP USING COMPUTER:
- REBOOT AND ENTER TWRP, PERFORM A BACKUP (THIS WILL CREATE A TWRP BACK UP FOLDER WITH DEVICE SERIAL NUMBER IN THE SD CARD) (ON DEVICE)
- DOWNLOAD AND EXTRACT THE NANDROID BACK UP FILE (ON COMPUTER)
- PLACE THE EXTRACTED FILES IN TO THE TWRP>BACKUP<DEVICE SERIAL NUMBER> FOLDER IN THE SD CARD (ON COMPUTER)
- RESTART THE DEVICE AND ENTER TWRP, CHOOSE RESTORE (ON DEVICE)
- LOCATE THE FOLDER COPIED IN THE ROOT OF THE SDCARD (ON DEVICE)
- SWIPE TO RESTORE (ON DEVICE)
- FOR SOME REASON THE NANDROID BACKUP DOES NOT CONTAIN CALCULATOR, FLASH LIGHT WHICH CAN BE DOWNLOADED HERE: http://www.apkmirror.com/apk/htc-corporation/
TryllZ said:
You cannot flash both TWRP and stock recovery as, in a way they both are the same thing, you have to use only 1 of them, either Stock Recovery or TWRP.
You will NOT be able to flash any older version with S-On, the only way to get any old OS is to get a Nandroid backup from someone and restore it through TWRP.
What device is yours, Asia, Europe or is it a Network Locked unit ?
Click to expand...
Click to collapse
My device is Europe. Which nandroid version should i look for?
mvds_M8 said:
My device is Europe. Which nandroid version should i look for?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24052804347818782
TryllZ said:
https://www.androidfilehost.com/?fid=24052804347818782
Click to expand...
Click to collapse
Thanks!!! :good: Work in progress. I'll let you know when it is done!
TryllZ said:
https://www.androidfilehost.com/?fid=24052804347818782
Click to expand...
Click to collapse
THANKS TRYLLZ!!! After more than 24 hours figuring out and trying you (and kativiti) made my day!!!
Thanks for your help and patience!!!

Required Help with connecting phone to PC in order to root

I am trying to root my device, to the final goal of installing a Nougat build on it. Been browsing through lots of guides, including this one which looks rather friendly:
https://www.idroidspace.com/how-to-root-htc-one-m7/
The problem is that the software did not recognize my phone.
I have enabled USB debugging. the PC detects the phone, I also have HTC Driver installed (downloaded HTC Sync Manager).
I also unlocked the boot-loader in the past, with success to the best of my knowledge (anyway I can confirm?).
Another problem I got that may come from the same source is that when opening command prompt and putting ADB Devices it wouldn't detect anything.
I have already old version of TWRP installed but I cannot flash the nougat from it, and in order to update the TWRP I wanted to root the device.
Am pretty much a beginner but can follow orders.
Droriley said:
I am trying to root my device, to the final goal of installing a Nougat build on it.
Click to expand...
Click to collapse
It's a waste of time to root if you're planning to flash a Nougat rom. It's a well spread misconception when ppl say "I want to root my phone" cause you're not rooting the phone, you're rooting the operating system on it (the rom). Most custom roms are pre-rooted so when flashing it on your phone you'll already have root. If you flash a non-rooted rom over your already rooted rom, you'll loose root hence why it's a waste of time to do it now. The only thing needed to flash a custom rom is a unlocked bootloader and a custom recovery.
Been browsing through lots of guides, including this one which looks rather friendly:
https://www.idroidspace.com/how-to-root-htc-one-m7/
The problem is that the software did not recognize my phone.
Click to expand...
Click to collapse
Outdated guide and tools
I also unlocked the boot-loader in the past, with success to the best of my knowledge (anyway I can confirm?).
Click to expand...
Click to collapse
Reboot in bootloader mode and check the first line of text it will either be ***LOCKED*** ***UNLOCKED*** or ***RELOCKED***
Another problem I got that may come from the same source is that when opening command prompt and putting ADB Devices it wouldn't detect anything.
Click to expand...
Click to collapse
Make sure you have the latest drivers version. ADB commands are only usable when booted in the OS with usb debugging turned on and you also need to unlock your screen once after connecting the phone to your PC. ADB commands will also work when booted in TWRP recovery. WIll not work in bootloader mode where you have to use FASTBOOT commands.
I have already old version of TWRP installed but I cannot flash the nougat from it
Click to expand...
Click to collapse
What is your twrp version and what rom do you want to flash? What is your "fastboot getvar all" ?
and in order to update the TWRP I wanted to root the device.
Click to expand...
Click to collapse
You don't need root to update TWRP, just flash the latest version using fastboot in bootloader mode:
Code:
fastboot flash recovery file_name.img
fastboot erase cache
fastboot reboot-bootloader
Alray, thanks for your thorough reply. I'd appreciate further help.
Reboot in bootloader mode and check the first line of text it will either be ***LOCKED*** ***UNLOCKED*** or ***RELOCKED***
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://www.dropbox.com/s/iyxepbaiu4x1uva/2017-06-12 00.23.29.jpg?dl=0
I believe the Bootloader is indeed unlocked.
Make sure you have the latest drivers version. ADB commands are only usable when booted in the OS with usb debugging turned on and you also need to unlock your screen once after connecting the phone to your PC. ADB commands will also work when booted in TWRP recovery. WIll not work in bootloader mode where you have to use FASTBOOT commands.
Click to expand...
Click to collapse
I don't know where from do I get the latest ADB drivers. As said, I downloaded HTC Sync Manager.
USB Debugging is turned on.
I tried in TWRP Recovery - still with no success.
What is your twrp version and what rom do you want to flash? What is your "fastboot getvar all" ?
Click to expand...
Click to collapse
https://www.dropbox.com/s/n8gojoe3jgv8wzm/2017-06-12 00.24.19.jpg?dl=0
You don't need root to update TWRP, just flash the latest version using fastboot in bootloader mode:
Click to expand...
Click to collapse
Much like trying to flash the below rom - I was not able to flash the newer TWRP.
https://www.dropbox.com/s/l2wvgrhjgifjlcp/2017-06-12 00.24.51.jpg?dl=0
https://www.dropbox.com/sh/jhmyj852saithxa/AABalcp37aOSFrI2FTarRTUoa?dl=0
Code:
fastboot flash recovery file_name.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Need assistance with the step before.
Droriley said:
Alray, thanks for your thorough reply. I'd appreciate further help.
https://www.dropbox.com/s/iyxepbaiu4x1uva/2017-06-12 00.23.29.jpg?dl=0
I believe the Bootloader is indeed unlocked.
I don't know where from do I get the latest ADB drivers. As said, I downloaded HTC Sync Manager.
USB Debugging is turned on.
I tried in TWRP Recovery - still with no success.
https://www.dropbox.com/s/n8gojoe3jgv8wzm/2017-06-12 00.24.19.jpg?dl=0
Much like trying to flash the below rom - I was not able to flash the newer TWRP.
https://www.dropbox.com/s/l2wvgrhjgifjlcp/2017-06-12 00.24.51.jpg?dl=0
https://www.dropbox.com/sh/jhmyj852saithxa/AABalcp37aOSFrI2FTarRTUoa?dl=0
Need assistance with the step before.
Click to expand...
Click to collapse
TWRP 2.6.3.0 is really outdated. This version does not have the required kernel to support the fstab file system used by recent roms. You need at least twrp 2.7.1.1, or the latest version: 3.1.N0.0
Are you using the original usb cable that came with the phone? If no you might want to double check if your usb cable is capable of data transfer (there are usb cables that only have the +5v and ground connections for charging but not the data+ and data- connections). Try another usb ports/cable.
alray said:
TWRP 2.6.3.0 is really outdated. This version does not have the required kernel to support the fstab file system used by recent roms. You need at least twrp 2.7.1.1, or the latest version: 3.1.N0.0
Are you using the original usb cable that came with the phone? If no you might want to double check if your usb cable is capable of data transfer (there are usb cables that only have the +5v and ground connections for charging but not the data+ and data- connections). Try another usb ports/cable.
Click to expand...
Click to collapse
This one ain't good? https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
any other way I can sort it out? I cannot manage to connect to my phone via command promp - I tried both in Fast boot and in Recovery.
PC feels the phone though - when on normal landing page I can see the phone content on explorer + it generates HTC Sync Manager.
Any way I can flash the updated TWRP from phone itself?
Droriley said:
PC feels the phone though - when on normal landing page I can see the phone content on explorer + it generates HTC Sync Manager.
Click to expand...
Click to collapse
You need to uninstall HTC sync manager, otherwise it will not work.
Or eaven better way is to install just naked drivers instead of sync manager.
Tarx100 said:
You need to uninstall HTC sync manager, otherwise it will not work.
Or eaven better way is to install just naked drivers instead of sync manager.
Click to expand...
Click to collapse
Where from?
Sent from my SM-G920F using Tapatalk

Categories

Resources