[Q] HTC One M7 freezes on bootscreen - One (M7) Q&A, Help & Troubleshooting

Hey guys,
I've got a problem with my HTC One. I tried to flash my branded ROM from Swisscom in order to replace it with a stock HTC One ROM. Therefore I unlocked the bootloader and installed the newest TWRP. Before that I copied a stock ROM (zip file) into the folder "/sdcard/download". After that I whiped my phone in order to install the stock ROM. By whiping my phone however I am unable start my branded OS and I am also unable to install the new stock ROM since it isn't recognized by the TWRP (or maybe it doesn't exist anymore?). I can also see the directory tree with TWRP but no files are shown.
Now I am stuck, since I only come to the TWRP. Via ADB I can't put any files (for example the stock ROM) on my phone, as the device isn't listed or recognized on my computer. ADB sideloading therefore also doesn't work. With Fastboot my device is recognized but I also can't transfer any files to it. When I try to install the stock ROM with the command "update" it tells me that the files "android.txt" and "android-product.txt" etc. are missing.
What can I do at this point? Do I have to compile my own kernel? Would it help if I would flash a new boot.img? Is RUU an option?
I would appreciate any kind of help I could get from you guys. :highfive:
Matthias.

Related

freeze in start - impossible to push a new ROM

Hello
I have update my HTC One (europe) into 4.2.2 recently.
I have unlocked the bootloader, installed a recovery (ClockWorkMod Touch 6), and root the device.
But after wanted to install a module founded on the net, I blocked the device (without any save obviously), and the device starts but freeze on the screen of HTC logo.
I always have access to the bootloader (and to fastboot) and to recovery CM6.
To reinstall ROM, I found several solutions on the web but none of theses worked :
- I tried to install a RUU ROM and relocked my bootloader before => impossible, error 140 because it considers that my bootloader does not have the good version. Indeed the RUU availables on the web are only 4.1 and apparently the downgrade is not authorized.
- I tried to inject a custom ROM via ADB sideload but there were a new issue : my device is not recognized! DEVICE NOT FOUND. The fastboot command works well, the HTC is detected, but not the ADB command, which is the only one enabling me to copy a custom ROM in the internal memory of the device (I reinstalled the drivers several times obviously).
I dont know what to do anymore, I feel that the device can be saved because I have access to the bootloader, fastboot and recovery.
But I do not see which other method to use to finally be able to replace the exsiting ROM by a new clean ROM
Thank you very much of your assistance.
You need to be in recovery and sideload mode when using the adb command. I'm not sure about CWM but on TWRP sideload mode is located under advanced options.
AT&T HTC One
BaadNewz's InsertCoin 3.0-7
Flar2's Bulletproof 3.4
If you re-locked your bootloader when trying to run the RUU, you will have to go to htcdev again and get a new token and unlock the bootloader again before you will be able to flash anything in recovery.
Thats maybe why you can't sideload in adb.
Also you have the phone device drivers installed on your PC right?
Could also try sideloading and other troubleshooting by using a toolkit:
http://forum.xda-developers.com/showthread.php?t=2242635
crushalot said:
If you re-locked your bootloader when trying to run the RUU, you will have to go to htcdev again and get a new token and unlock the bootloader again before you will be able to flash anything in recovery.
Thats maybe why you can't sideload in adb.
Also you have the phone device drivers installed on your PC right?
Could also try sideloading and other troubleshooting by using a toolkit:
http://forum.xda-developers.com/showthread.php?t=2242635
Click to expand...
Click to collapse
rename the ROM from its original name to "ROM.zip" without the quotes, and then try again ADB
if it didnt work inject TWRP, and copy the ROM to a USB Stick and using a USB OTG ($1) mount the USB Stick in TWRP and install the ROM
it worked %100 for me

[Q] PLEASE POST full STOCK HTC ONE ROM exe for AT&T new kitkat Vers: 4.18.502.7

ISSUE RESOLVED: keeping post since active since I still need the rom exe. But boot looping fixed.
My AT&T HTC One is stuck in boot loop, probably to do with the KK OTA update. I have looked everywhere, read posts all night, and tried all of the various reboots and reflashings of recovery files and firmware, erased caches, locked and unlocked bootloaders. Can anyone post the executable RUU for the stock ROM KK version 4.18.502.7? I'd really appreciate it. I can't sideload a zip (it stalls). I'm aware of the other post asking for the same thing and the response in it with a link to the file, but that link actually is only to a recovery zip with darkbootloader, which seems also to require S-OFF, even if I did have some way to sideload it.
The firmware updated before it began looping, so I can't just reinstall a prior stock ROM exe file, as far as I can tell. I tried anyway!
I hesitate to install the .1540. Dev. Ed. version of the ROM that's available because it says in the notes that it's "compatible" with my cid and PN, etc, but I think they mean for recovery file purposes and not for a full ROM install. So I think I just need the ROM exe, if anyone has it? Thanks!
more info
by the way, when it crashed i had installed the ota update and then restarted play around with it, then rebooted in bootloader and unlocked, reinstalled twrp and AndRev HD 51. I've noticed two problems there. The first is that the Xposed module's latest update totally defeats my internet wifi and especially crashes vpn sevice. prior versions did not and I could not down-install to prior version (is preinstalled in HD 51). The other problem is that in looking around for this boot loop probably, turns out that TWRP apparently doesn't get along well with the encryption. don't know why. this stuff may or may not be part of the problem, but at this point i have no OS, an erased cache and can't even get into recovery (tried flashing twrp, older twrps and CWM. thanks.
You are screwed if you have no recovery, and the phone is s-on. You need to find a way to get in recovery. Alternatively try to flash the firmware only from OTA to get stock recovery.
sent from my mobile device
randomOne1111 said:
My AT&T HTC One is stuck in boot loop, probably to do with the KK OTA update. I have looked everywhere, read posts all night, and tried all of the various reboots and reflashings of recovery files and firmware, erased caches, locked and unlocked bootloaders. Can anyone post the executable RUU for the stock ROM KK version 4.18.502.7? I'd really appreciate it. I can't sideload a zip (it stalls). I'm aware of the other post asking for the same thing and the response in it with a link to the file, but that link actually is only to a recovery zip with darkbootloader, which seems also to require S-OFF, even if I did have some way to sideload it.
The firmware updated before it began looping, so I can't just reinstall a prior stock ROM exe file, as far as I can tell. I tried anyway!
I hesitate to install the .1540. Dev. Ed. version of the ROM that's available because it says in the notes that it's "compatible" with my cid and PN, etc, but I think they mean for recovery file purposes and not for a full ROM install. So I think I just need the ROM exe, if anyone has it? Thanks!
Click to expand...
Click to collapse
This RUU does not exist yet, only the FOTA version - I've been in talks with HTC about this very thing. They do not have an ETA for the RUU, unfortunately.
SaHiLzZ said:
You are screwed if you have no recovery, and the phone is s-on. You need to find a way to get in recovery. Alternatively try to flash the firmware only from OTA to get stock recovery.
sent from my mobile device
Click to expand...
Click to collapse
Hm. I did flash the firmware from an OTA. But couldn't actually boot into recovery after that. I can flash custom recoveries but can sideload without the intall stalling about a third of the way through (just hangs, no error messages). Then after that if I restart it loops. I can maybe fix the "tampered" warning and swap it out somewhere. I think it's the encryption while using twrp maybe resulted in some hiccup. But I thought the firmware flash would fix that. And I'm not sure how you can actually tell whether the flashed firmware is successful. (it says it is in the command prompt, but the phone doesn't really do anything all that different and i already updated with the OTA so the numbers won't change).
Looking at the board today and reading through the posts I see many people reporting basically being in the same boot loop boat after the OTA update, though with diff versions maybe there's some FW problem. weird so many posts of similar boot looping.
Thanks for responding.
This issue is temporarily resolved, was able to push ARHD in TWRP (would not sideload without erroring out during install, but was able to push zip to sdcard and then install from there) after much wiping using both twrp and cwm. Did notice when using CWM recovery would not install ARHD off sdcard push, and would flag unknown files .... android..security during wipes, so i am guessing that encrypting a custom ROM at least with TWRP as recovery was a bad idea. hopefully this will stay stable until the KK OEM RUU EXE is available. Thanks for the help.

[Q] HTC ONE Flashboot boot recovery (no flashing)

Hi all.
On my HTC one hboot 1.44.000, I can run i ADB
fastboot boot boot boot.img
To boot on a custom recovery image without actually flashing the image.
On newer HTC one hboot 1.55.000 this has been disabled.
Does anyone know of any workaround to this problem?
Its a bit of a pain to do the initial backup of the stock recovery, rom and boot when you have to overwrite the stock recovery to do so.
Can the stock recovery be backed up to an img file from the ADB prompt, with stock recovery still loaded somehow?
In fact its a classic CATCH 22
I know you can extract the stock recovery later on from a the latest OAT update, but it would just be a lot more simple, if all you what is root, to boot on the image without flashing, install the super user app, then restore all the needed HTC specific apps you lose when unlocking and then you are back to stock with root.
Does anyone know the exact location of the OAT from where you can extract the stock boot and recovery from firmware.zip, and is this OAT deleted after it has been run, or if its still available to grab later one?
Since the device is not rooted yet, its not possible to check the \cashe folder for the OAT file before you rooted it.
What if its not there? How will you find the original stock recovery that fits your current system, any new OAT may have a different one, that mayl not work.
Again a CATCH 22
Why does HTC support unlocking the bootloader, and then limits it use, not allowing to boot on a recovery without flashing it ?
requa3r0 said:
Hi all.
On my HTC one hboot 1.44.000, I can run i ADB
fastboot boot boot boot.img <---- you mean fastboot boot recovery.img ?
To boot on a custom recovery image without actually flashing the image.
On newer HTC one hboot 1.55.000 this has been disabled.
Does anyone know of any workaround to this problem?
Click to expand...
Click to collapse
Afaik this is no longer possible to use remote recovery booting, htc disabled it.
requa3r0 said:
How will you find the original stock recovery that fits your current system, any new OAT may have a different one, that mayl
Click to expand...
Click to collapse
There is many stock recoveries uploaded here if you can't find yours, then just request it and someone will probably upload it.

[Q] Flashing a ROM with Unlocked Bootloader but S-ON. Possible ?

Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks
anirudhgargi said:
Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks
Click to expand...
Click to collapse
as mentioned in the previous post you made, you need to install a custom ROM first in order to boot back into your phone. You have unlocked the bootloader and installed TWRP recovery. Now you need to sideload the ROM by adb sideload commands in order to boot the phone up again
Do not run an earlier RUU.zip as you will brick your phone. Firewater needs a working ROM, there are no ways to bypass this
Flash ARHD 81 or Insert Coin or Team Venom Rom
Step 1. Unlock Bootloader and Install TWRP 2.7.x.x recovery. Don't install Twrp v2.8.x.x, wont work with any roms.
Step 2. Boot to Recovery.
Step 3. Mount the system using twrp. I am assuming that you don't have custom rom on your phone storage.
Note that TWRP v2.7.x.x wont mount the phone storage. v2.7 and above always had issues. My recommendation is to install TWRP v2.8 for temporary purposes. Now mount the phone storage copy any rom you downloaded to the system.
Step 4. Assuming that you install TWRP v2.8 to copy rom files to phone storage. Boot to bootloader again and Install TWRP using fastboot. Command: "Fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img"
Step 5. Reboot to recovery. WIPE DATA, CACHE, DALVIK CACHE, SYSTEM > Install Rom.
Note do not wipe "internal storage." Otherwise you have to go back and start again with installing twrp v2.8, then copy rom...
Step 6: follow the steps.
IMO ARHD 81 is a stable rom, provides better battery life. If you like Sense then stick with this Rom, if you want Stock Android aka AOSP then try aospa legacy, CM, SlimKAT, AOSB and many more.
Moreover, i haven't found RUU for Sense 6 KK4.4.3, if you do please provide me a link as well.
As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho
Not able to copy my custom rom in phone.
stovie_steve said:
As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho
Click to expand...
Click to collapse
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.
anirudhgargi said:
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.
Click to expand...
Click to collapse
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again
No luck ! Fastboot mode also not getting detected now.
stovie_steve said:
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again
Click to expand...
Click to collapse
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,
anirudhgargi said:
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,
Click to expand...
Click to collapse
Sounds also like a driver issue
Try instling HTC sync to get the up to date HTC drivers and retry. Use different usb ports (2.0 preferably) and different cables. If it's saying fastboot ac then the phone is not being detected correctly, so it's a driver issue
You can also try manually installing the driver by searching for I think the Google naked driver

Trying to get back to stock rom

Hello,
Tried rooting my phone with no prior experience. Worked, but eventually I got to where the phone wouldn't boot past splash screen (logo came up, then screen went black while backlight is on and didn't respond to stimuli until battery was removed). Possibly resulted from a build.prop file problem. Did get into boot though, so I fixed that problem by installing a cyanogen rom from a zip file using twrp recovery. I didn't want a custom mod though since I'm used to the look and feel of the 4.0.3 ICS I had, and the cyanogen doesn't seem to have google play so I can't even download anything (original purpose of rooting was to get incompatible apps by spoofing via build.prop file). Currently trying to get back to stock. Unfortunately I didn't make a nandroid backup of the system before the problem occurred, hence I have no backup to flash.
What I tried:
1. Use the official HTC 4.0.3 RUU .exe to upload to the phone. Unfortunately HTC Sync doesn't see this phone, even though I have the correct drivers installed.
2. Attempted to use twrp recovery to install the rom.zip extracted from the RUU directly, the same way I successfully installed the cyanogenmod rom. Failed, claiming it's unable to open zip. The .zip file was checked for integrity and returned by an archiver app.
3. Tried to use these commands from the cmd with phone connected to install the .zip from fastboot:
fastboot erase cache
fastboot oem rebootRuu
fastboot flash zip rom.zip (rom.zip being the functional file of the stock rom)
Failed, saying it's not allowed. Tried it with both locked and unlocked bootloader, no difference.
4. Unzipped the file and tried to flash the system.img file directly, but that failed with a "data length is too large" error.
5. My recovery being twrp 2.1.1, tried looking for altenatives. Can't find any links to download the WCX recovery, but I found several for newer twrp versions, including 2.3.1.0 and 2.6.3.0 which I tried downloading flashing. After flashing the phone got stuck at the cyanogenmod loading logo and wouldn't boot further, and the recovery itself didn't work, just showed the HTC splash, turned black, then booted again normally, getting stuck at the cyanogen logo. Same thing for the 2.6.3.0 version, so I reflashed the original 2.1.1, at which point I can get into recovery but the phone is still stuck at the cyanogenmod during normal boot. At this point I installed the original cyanogenmod .zip from recovery and now at least the phone boots up normally. Still need to get stock back somehow.
Out of ideas and exhausted from this. Any help would be appreciated. Perhaps anyone has a working stock 4.0.3 rom for the Vivid, nandroid backup, etc., or any other ideas. Thanks for reading.
Oh crap...
OK... First... Stock rom can be found in development... Most of the roms there are stock... Read the OP... It'll tell you...
Second... You should use TWRP 2.5.3.0 or something like that I forget...
Third... When you tried the ruu... Did you relock your bootloader...
Side note... Could you get your phone to show up with 'fastboot devices'

Categories

Resources