Hello!
I got big problems with my HTC ONE M7.
In September I flashed Cyanogenmod 12.1 on the device.
The ROM coused some problems with one of aplications important to me so I decided to go back to stock.
Then problems arised.
I could not go back to stock. Tried several methods. Any of them worked.
Today I tried HTC Guru's way: Guru Reset one from htc1guru.com
I flashed TWRP recovery instead of Cyanogeon one.
It installed properly. Wiped cache, dalvik, system
Then I run GuruReset file from my SD card. Stock ROM installed properly, without errors. Phone booted in stock, made first customisation steps, locked bootloader and waited for OTA.
Then some problem with WIFI occured so I put a SIM card inside phone and downloaded OTA. Phone was in stock, with SIM working properly. In downloaded and started to install.
After install phone reboot and... started to loop.
Worse, phone cannot go into recovery. It boots into bootloader but cannot go into recovery. After install there were no USB debugging ON.
So situation is:
- phone is without USB debug (no fastboot usb, only fastboot)
- cannot enter recovery: when i try there is red exlamation mark in some geometrical figure after 2-3 minutes phone reboots itself and loops.
- there is loop when system loads: white HTC logo, several seconds, reboot.
I run of options, my limited knowledge of Android left me helpless here.
Is there a way to run recovery?
Phone is HTC ONE M7, LTE edition
As I read before it was (under CM 12.1) PN710000, CID 032
Bootloader:
Tampered, relocked
M7_UL PVT SHIP S-ON RH
HBOOT - 1.61.0000
Radio-4T.35.3218.16
OPENDSP-V35.120.274.0718
OS- (7.19.401.2) <--- this is in red color
eMMc- boot 2048 MB
Feb 12.2015
The goal was to return to stock not to brick...
Help me please step by step how to make phone work.
Lustenmord said:
Hello!
I got big problems with my HTC ONE M7.
In September I flashed Cyanogenmod 12.1 on the device.
The ROM coused some problems with one of aplications important to me so I decided to go back to stock.
Then problems arised.
I could not go back to stock. Tried several methods. Any of them worked.
Today I tried HTC Guru's way: Guru Reset one from htc1guru.com
I flashed TWRP recovery instead of Cyanogeon one.
It installed properly. Wiped cache, dalvik, system
Then I run GuruReset file from my SD card. Stock ROM installed properly, without errors. Phone booted in stock, made first customisation steps, locked bootloader and waited for OTA. ---> Locking the bootloader wasn't required to receive ota updates
Then some problem with WIFI occured so I put a SIM card inside phone and downloaded OTA. Phone was in stock, with SIM working properly. In downloaded and started to install.
After install phone reboot and... started to loop. ---> Probably because you have used the wrong guru reset rom version and that installing the ota caused problems.
Worse, phone cannot go into recovery. It boots into bootloader but cannot go into recovery. After install there were no USB debugging ON. ---> USB debugging doesn't matter. when the phone isn't booted in the system you don't need usb debug to connect to the phone.
So situation is:
- phone is without USB debug (no fastboot usb, only fastboot) ---> Most likely a driver issue, re-install the latest drivers so you can have a "fastboot usb" connection. this is your #1 priority.
- cannot enter recovery: when i try there is red exlamation mark in some geometrical figure after 2-3 minutes phone reboots itself and loops. --> this is the stock recovery splash screen (the exclamation mark inside a triangle). You have tu use volume up and power to reveal the menu, anyway there is nothing useful to do in stock recovery for your situation.
- there is loop when system loads: white HTC logo, several seconds, reboot. ---> You should be able to flash the 7.19.401.2 ruu but it will requires to fix the "fastboot usb" issue first.
I run of options, my limited knowledge of Android left me helpless here.
Is there a way to run recovery?
Phone is HTC ONE M7, LTE edition
As I read before it was (under CM 12.1) PN710000, CID 032
Bootloader:
Tampered, relocked
M7_UL PVT SHIP S-ON RH
HBOOT - 1.61.0000
Radio-4T.35.3218.16
OPENDSP-V35.120.274.0718
OS- (7.19.401.2) <--- this is in red color ----> that mean the firmware didn't updated successfully and that the phone is waiting for the firmware to be updated.
eMMc- boot 2048 MB
Feb 12.2015
The goal was to return to stock not to brick...
Help me please step by step how to make phone work.
Click to expand...
Click to collapse
read comments in red in above quote.
Thank you.
I will try to restore fastboot usb.
May you point me to apriopriate ROM for my device?
The red fragment in bootloader- which indicates bad firmware installation- was already just after Cyanogen install. So the problem started before i tried to go back to stock.
I was lookin for ROMS CID __032 and PN710000 for HTC with LTE. Maybe I did something wrong? I live in Poland if it matters...
Lustenmord said:
Thank you.
I will try to restore fastboot usb.
May you point me to apriopriate ROM for my device?
The red fragment in bootloader- which indicates bad firmware installation- was already just after Cyanogen install. So the problem started before i tried to go back to stock.
I was lookin for ROMS CID __032 and PN710000 for HTC with LTE. Maybe I did something wrong? I live in Poland if it matters...
Click to expand...
Click to collapse
Once you'll have fastboot usb connection working, you'll have to flash the 7.19.401.2 RUU posted here. Follow instructions of post #1 to flash it.
So your version-main (in red) was the same version number before flashing the guru reset rom? And it was red before? What version of the guru reset rom did you flashed?
alray said:
Once you'll have fastboot usb connection working, you'll have to flash the 7.19.401.2 RUU posted here. Follow instructions of post #1 to flash it.
So your version-main (in red) was the same version number before flashing the guru reset rom? And it was red before? What version of the guru reset rom did you flashed?
Click to expand...
Click to collapse
I do not remember what was original version, must say. First was stock OTA updated to last version, then cyanogen from September, then Cyanogen October, then Guru Reset.
I noticed red writing after 2nd Cyanogen install (October) when I decided to go back to stock and started to have problems. Maybe it was red before, dunno.
What version Guru I do not remmeber, maybe it is still on my phone, when I get acces to SD I will write it down.
Thank you for your flashy (intended!) response!
Lustenmord said:
I do not remember what was original version, must say. First was stock OTA updated to last version, then cyanogen from September, then Cyanogen October, then Guru Reset.
I noticed red writing after 2nd Cyanogen install (October) when I decided to go back to stock and started to have problems. Maybe it was red before, dunno.
What version Guru I do not remmeber, maybe it is still on my phone, when I get acces to SD I will write it down.
Thank you for your flashy (intended!) response!
Click to expand...
Click to collapse
Well what I wanted to know by asking you this question is if you used the right guru version for your phone. You should have used the version number that matched your phone version-main. If I understand correctly, you were on 7.19.401.2 then flashed CM in September, updated CM in October and then flashed the guru reset rom. Flashing CM doesn't change your version-main (firmware version). So it sounds like you have flashed the wrong guru reset version on your phone since there is no guru reset for 7.19.401.2. Anyway it doesn't really matter anymore, if you can have back the "fastboot usb" connectivity, it should be pretty easy to fix by flashing the ruu mentioned above.
Reporting Fastboot USB working Hope is returning. Rom is downloading, 1 hour left, Canadian server is slow. Thank you, mate.
Lustenmord said:
Reporting Fastboot USB working Hope is returning. Rom is downloading, 1 hour left, Canadian server is slow. Thank you, mate.
Click to expand...
Click to collapse
I'm also downloading from Can servers since im located there and never had speed issue maybe to much traffic today
When flashing the ruu, don't forget to use htc_fastboot.exe like explained in the other thread. The normal "fastboot.exe" from the android sdk won't work to flash the ruu because it can't deal with files as large as this ruu. Just download htc_fastboot.exe and save it in the same folder where you already have fastboot.exe, adb.exe and their .dll files installed on your computer. When you want to use htc_fastboot.exe instead of fastboot.exe, like for flashing the ruu, start your command with "htc_fastboot" instead of "fastboot"
e.g.
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
htc_fastboot reboot
instead of
Code:
[STRIKE]fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
fastboot reboot[/STRIKE]
When issuing "htc_fastboot flash zip ruu.zip" a few files will be flashed to your phone, then it will stop, the phone will reboot itself and the flash will continue. Don't touch anything until the ruu is completely flashed ---> it should output "Okay. Finished, total time: XXX" when its done. Then its safe to reboot using "htc_fastboot reboot".
First boot can take longer than usual. The phone will sit at the white HTC splash screen for a few min then it will eventually boot to the welcome/setup screen.
You'll then have 2 ota updates to install (settings --> about --> software info --> check for updates)
one from 7.19.401.2 to 7.19.401.22
another one from 7.19.401.22 to 7.19.401.30 which is currently the latest version (android 5.0.2, Sense 6.0)
Now receivin 2nd OTA.
Tommorow afternoon will post a final result but for now I must say that you, sir, helped a lot. Thanks. Big ones.
Lustenmord said:
Now receivin 2nd OTA.
Tommorow afternoon will post a final result but for now I must say that you, sir, helped a lot. Thanks. Big ones.
Click to expand...
Click to collapse
You're welcome, glad it worked :good:
Related
I recently came across a modified Google Nexus One (N1) that has been experimented on. Upon boot up, I get a black screen with the HTC logo and four exclamation marks inside triangles in each of the four corners of the screen. As I attempted to enter hboot, I saw it has been replaced with Blackrose which leads me to believe it has been unlocked/rooted at some point in time. ( I am fairly new at this, but I lurk around the forum ). I tried hooking the N1 up to RUU to flash it back to a stock ROM, however that proved unsuccessful - the phone boots up to the above mentioned logo and stays that way. When I try to go to recovery/hboot, instead of the usual menu choices, there's only RUU as an option... Is the phone bricked, and if not, how can I revert it to a working state ?
I have attached pictures of what the boot screen looks like, as well as the recovery menu.
Thank you in advance.
It's in the middle of RUU mode, entered by executing "fastboot oem rebootRUU" (I might not remember it 100% correct, so check it with Google).
This should be enough for you to check with Google how you exit RUU mode.
The only way I see to exit this mode is if I flash it with something via fastboot ( since no recovery works, custom or stock ). What image file or zip do I flash it with, in order to revert it back to complete stock ( stock hboot, stock recovery, stock ROM ) - I want the phone like it was out of the box, so I can reroot it and unlock it myself.
I tried flashing it with PASSIMG_Passion_Google_WWE_3.13.1700.1_GRK39F_release_signed.zip through fastboot, for a moment it seemed to be going ok, then at the very end, while it was unpacking the [user data] image I get a partition update fail message 51, and after reboot - still the gray HTC letters and Blackrose instead of HBOOT.
Any suggestions ?
Short googling with the error would have revealed you the bad news.
Partition update fail means bad stuff - your NAND is malfunctioning, which equals a dead phone.
Have you tried to uninstall Blackrose?
tommert38 said:
Have you tried to uninstall Blackrose?
Click to expand...
Click to collapse
doesn't the phone need to be working in order for me to hook it up to Blackrose ? As of now, with this screen, the PC doesn't seem to detect it as a working phone, only fastboot. And Blackrose just says waiting for device... how do I uninstall it then?
I also tried this RUU: RUU_Passion_Vodafone_Generic_3.11.151.3_GRJ22_release, flashing the ROM to an image version 3.11.151.3, but at the end I get a message saying ERROR [110]: FILE OPEN ERROR. The RUU cannot open the requested files or the files are damaged. The RUU cannot continue with the update. Please get a complete RUU package and try again. Can someone please refer me to a working RUU package for the Nexus One, I am really scared of experimenting trying to find one by myself, seeing how the phone is already hanging in the balance, I would be thankful
You could try to flash this stock HBOOT, and if you have resized partitions I guess you could always use blackrose_manual_120421.zip to change to stock partition layout (145/95/196).
Edit: I've never flashed a HBOOT this way, and I never resized my partitions the manual way, so I would check the Blackrose for details. And I'm not responsible if you brick your phone
Edit2: I see you haven't got working recovery, so you should find a way to flash the HBOOT via fastboot. Maybe the Blackrose developer dla5244 can help you out (or Google).
Edit3: You could also try to flash this engineering HBOOT
tommert38 said:
You could try to flash this stock HBOOT, and if you have resized partitions I guess you could always use blackrose_manual_120421.zip to change to stock partition layout (145/95/196).
Edit: I've never flashed a HBOOT this way, and I never resized my partitions the manual way, so I would check the Blackrose for details. And I'm not responsible if you brick your phone
Edit2: I see you haven't got working recovery, so you should find a way to flash the HBOOT via fastboot. Maybe the Blackrose developer dla5244 can help you out (or Google).
Edit3: You could also try to flash this engineering HBOOT
Click to expand...
Click to collapse
Thanks for your time friend, I tried the above mentioned steps, it says OK all across the board in fastboot while I flash, but after I reboot it just goes back to the same screen, stuck in RUU. I did some digging around and found this which seems to be exactly my problem:
RUU PROBLEMS
"I tried using a RUU, but it failed, and now my phone is stuck on a black HTC Screen with /!\ In every corner!"
Possible Causes:
- You were S-OFF and you flashed a custom bootloader from alpharev
- You didn't check the MD5 Sums before proceeding, and the download may have been corrupted.
- You tried using the wrong RUU
Fixing your problem
Your phone is stuck in RUU mode. RUU mode is like fastboot mode, and can still receive fastboot commands, therefore it can be easily "fixed".
It helps to have a goldcard for this problem, so that you can use any RUU you want.
S-OFF
[STEP1]- download "Bravo Stock" from Alpharev
[STEP2]- download Android Flasher
[STEP3]- use android flasher to flash "Bravo Stock"
[STEP4]- run the RUU again and wait for it to finish
S-ON
If you're S-ON it eliminates the possibility of you having a custom bootloader, and the only possibility now is that the RUU was corrupted or you
used the wrong RUU for your device. Therefore, for this process you need a goldcard.
[STEP1]- Create the goldcard from the tutorial
[STEP1]- Use the WWE RUU
However, this is from a thread for the HTC Bravo. Anything similar for the N1 ?
Edit1: Could it be that the hboot partition was resized with Blackrose and therefore the RUU I tried to flash it with needs stock partition layout ?
Your partitions ARE resized. 2nd picture 2nd line JB-220/10/206. If it's b*tching about the resized partitions, then that would be about your cache partition (which is 85MB smaller than its stock size).
Edit: you should also try to wipe your partitions with fastboot, then flash the img's that are inside the passimg
what's the command line to wipe the partition ? fastboot format hboot/recovery/system ?
Dude, your Nexus One is dead, the internal NAND is damaged and therefore unrecoverable.
Sent from my Nexus S using Tapatalk 2
fastboot erase system/cache/userdata/boot
Good morning,
I've 'inherited' an Incredible S where an attempt to try a custom ROM has gone wrong. The handset has ARHD 6 ROM installed in it which never gets past the white HTC bootscreen, probably because it hasn't had the BlackRose bootloader installed. Obviously there is no Nandroid to make life easy.
It's on HBoot 2.02, S-on, and the bootloader is unlocked with 4Ext installed.
Quick question: is there a ROM I can install on bootloader 2.2 via 4Ext that will enable the phone to be used, e.g. Virtuous Quattro?
Longer question: Can anybody point me in the direction of a good method to downgrade the bootloader, bearing in mind I can't boot to the ROM. I do seem to have fastboot access and don't mind command line work, I just can't see the best combination of bootloader/ROM that isn't on a dead link.
Alternatively an RUU suitable for the bootloader would be good, but for some reason the list on HTCDev.com doesn't seem to be filtering properly for me on Opera or Iron.
Thanks in advance,
RH
Bossk128 said:
Good morning,
I've 'inherited' an Incredible S where an attempt to try a custom ROM has gone wrong. The handset has ARHD 6 ROM installed in it which never gets past the white HTC bootscreen, probably because it hasn't had the BlackRose bootloader installed. Obviously there is no Nandroid to make life easy.
It's on HBoot 2.02, S-on, and the bootloader is unlocked with 4Ext installed.
Quick question: is there a ROM I can install on bootloader 2.2 via 4Ext that will enable the phone to be used, e.g. Virtuous Quattro?
Longer question: Can anybody point me in the direction of a good method to downgrade the bootloader, bearing in mind I can't boot to the ROM. I do seem to have fastboot access and don't mind command line work, I just can't see the best combination of bootloader/ROM that isn't on a dead link.
Alternatively an RUU suitable for the bootloader would be good, but for some reason the list on HTCDev.com doesn't seem to be filtering properly for me on Opera or Iron.
Thanks in advance,
RH
Click to expand...
Click to collapse
Download CM7.2
Go back to bootloader.
Go to Recovery.
Mount USB storage and transfer CM7.2 to SD card
Now Flash CM7.2
Flash boot.img of CM7.2
Enable USB Debugging after you've booted up (no need for GApps atm)
Continue with downgrade guide (Everything is in sticky roll up thread)
072665995 said:
Download CM7.2
Go back to bootloader.
Go to Recovery.
Mount USB storage and transfer CM7.2 to SD card
Now Flash CM7.2
Flash boot.img of CM7.2
Enable USB Debugging after you've booted up (no need for GApps atm)
Continue with downgrade guide (Everything is in sticky roll up thread)
Click to expand...
Click to collapse
Nice one, thanks. I've downloaded the ROM from http://get.cm/get/2KU and will flash from 4Ext recovery.
The bootloader in in that same zip file, I'll flash as follows:
At ADB prompt:
fastboot flash boot boot.img
Reboot, ROM should load up fine. I spotted the downgrade guide yeterday and it looks very good. I'll give it a shot if CM isn't suitable.
Again, thanks very much.
Time for 2 small questions? How long does it take to flash the boot.img, 10 seconds? 5 minutes? Why does the boot image have to be flashed manually?
Cheers!
Bossk128 said:
Nice one, thanks. I've downloaded the ROM from http://get.cm/get/2KU and will flash from 4Ext recovery.
The bootloader in in that same zip file, I'll flash as follows:
At ADB prompt:
fastboot flash boot boot.img
Reboot, ROM should load up fine. I spotted the downgrade guide yeterday and it looks very good. I'll give it a shot if CM isn't suitable.
Again, thanks very much.
Time for 2 small questions? How long does it take to flash the boot.img, 10 seconds? 5 minutes? Why does the boot image have to be flashed manually?
Cheers!
Click to expand...
Click to collapse
boot.img flashing should take >1s or around that at least...
And the boot.img has to be flashed manually only if you are S-ON. S-ON doesn't give you full clearance to some particular partition that I forget. S-OFF will so when you achieve S-OFF, you will no longer need to flash the boot.img manually
072665995 said:
boot.img flashing should take >1s or around that at least...
And the boot.img has to be flashed manually only if you are S-ON. S-ON doesn't give you full clearance to some particular partition that I forget. S-OFF will so when you achieve S-OFF, you will no longer need to flash the boot.img manually
Click to expand...
Click to collapse
OK, same as my HOX then. Anyway, I've followed your instructions.
Hm, ROM installed and now trying to flash boot.img (from the rom zip).
Fastboot devices shows one device.
Command line states "sending boot (2182 kb)..." but hasn't changed for over 3 minutes. Handset says Fastboot USB and is unresponsive (as expected) at this moment.
I'll leave it until it errors.
RH
Edit: 30minutes later i pulled the usb cable.
"FAILED (status read failed (Too many links))"
Handset is in the same state, i.e.fastboot/hboot and recovery are fine, but ROM doesn't boot and handset stalls at white screen with green HTC letters.
Any ideas why I can't flash the boot.img?
Success! After reinstalling the the drivers and moving the USB cable to another port, the boot.img was successfully pushed, and booted into CM.
I'll now go for downgrading!
thanks for the help.
RH
Hi all,
So let me explain. I was given a HTC One for repair and the person just told me that her child did something wrong in the settings and the phone didn't boot anymore. The phone was on an older stock ROM and didn't get past the HTC One logo. Something was corrupted because the startup sound was cutting off before it had played like it should.
anyways: the phone is S-ON and I have unlocked the bootloader via HTCDev. I can install CWM, CWM Touch and TWRP but can't install any Sense rom because of the antique HBoot 1.56. I can however boot into CM 10.2.1 stable with no problems and ARHD 9.4 but with nou touch. On both ROMs firewather and rumrunner fail (usb debugging is on and root also for adb and apps).
Possible fixes I think off:
-Install an older ARHD version like 42 or 61 or 62 that is compitable with my firmware (but can't find them anywhere);
-install an insecure kernel compatible with CM10.2 (can't find one);
-Somehow just revert back to a Sense rom, wich I can't.
I just want S-off but every s-off tool fails. Is there another way to instal RUU exe or ZIP without S-OFF or at least upgrade the damn antique radio image that belongs in a museum ?
Thanks in advance
soulaiman said:
Hi all,
So let me explain. I was given a HTC One for repair and the person just told me that her child did something wrong in the settings and the phone didn't boot anymore. The phone was on an older stock ROM and didn't get past the HTC One logo. Something was corrupted because the startup sound was cutting off before it had played like it should.
anyways: the phone is S-ON and I have unlocked the bootloader via HTCDev. I can install CWM, CWM Touch and TWRP but can't install any Sense rom because of the antique HBoot 1.56. I can however boot into CM 10.2.1 stable with no problems and ARHD 9.4 but with nou touch. On both ROMs firewather and rumrunner fail (usb debugging is on and root also for adb and apps).
Possible fixes I think off:
-Install an older ARHD version like 42 or 61 or 62 that is compitable with my firmware (but can't find them anywhere);
-install an insecure kernel compatible with CM10.2 (can't find one);
-Somehow just revert back to a Sense rom, wich I can't.
I just want S-off but every s-off tool fails. Is there another way to instal RUU exe or ZIP without S-OFF or at least upgrade the damn antique radio image that belongs in a museum ?
Thanks in advance
Click to expand...
Click to collapse
Hboot 1.56 is not that old the current is 1.57! You can install RUU being S-ON the RUU must be the same or higher version, signed and the bootloader has to be locked/relocked. For Sense ROMs you might try TWRP 2.6.3.3 it seems to work best. ARHD 81 should work with your phone you have to wipe in Aroma before you install it.
I couldn't get ARHD 81 to work, but if someone is in the same situation here is what I did:
1) Relock your bootloader with this command:
fastboot oem lock
2) download this signed radio file : https://www.androidfilehost.com/?w=file-thanks&fid=23622183712460395&mid=70&download_id=t0kvkiiupbv0r5gakftasij7d5&tid=1412801244&hc=731cbdd91c39e4104b17bb47e6236fd9614838fa88b158009a1006be6b2ec5ea
3) Place the file in the same platform-tools directory for ease of use and insert this command:
fastboot oem rebootRUU
4) Once the phone reboots into a black HTC screen enter:
fastboot flash zip <name_of_the_file_here_without_quotes>
5) Normally it should succeed and tell you to immediatly flush, if it fails reattempt to flash the zip and it will succeed.
6) Download your prefered Recovery, mine is CWM but TWRP is even better sometimes and enter:
fastboot reboot-bootloader and then fastboot flash recovery <recovery.img>
6B) EDIT: to be able to flash a recovery IMG with S-On you need to unlock you bootloader again.
fastboot flash unlocktoken Unlocktoken_bin or whatever your unlocktoken is called
Then accept the security warning on your phone with the volume keys and power key.
7) Once succeed enter recovery and flash Maximus HD
8) Once done please enter bootloader again by pressing vol- + power or bij selecting advanced, reboot bootloader in recovery.
9) Because we're S-On, we need to manually flash boot.img
fastboot flash boot boot.img and if you get bootloops fastboot erase cache
Once this is done you should be able to boot into the rom and everything should work. Flashing this has upgraded my hboot to 1.57. Now I will report if I succeed to get S-off.
Well I couldn't find an RUU that was signed and for my version. Also I don't know why but I couldn't get ARHD to work. Maybe I need s-off or another recovery but even with elemental X it didn't boot.
soulaiman said:
Well I couldn't find an RUU that was signed and for my version. Also I don't know why but I couldn't get ARHD to work. Maybe I need s-off or another recovery but even with elemental X it didn't boot.
Click to expand...
Click to collapse
Okay so what I want to suggest you do is for starters go in unlock the bootloader as re locking it before doing anything is pointless when once everything is fixed is when you'd need to do it. Also I recommend that you install the custom recovery first and flash the rom from there rather than trying to flash it using fastboot as then at least we can get a standard recovery message which may be easier to find an answer for, I recommend using the very latest twrp recovery from their site as that should be able to flash all roms but make sure you install a stock sense 6 rom as the phone needs to be on the latest update with the kk radios and obviously that means having an hboot of 1.57 which would allow you to install custom roms that are running on kk otherwise you'll have issues and if you've followed what I suggest and it doesn't work a logcat and even a video of what is actually happening will help a lot to see what's going on but first things first is make sure that phone is on the latest hboot and the latest radio.
Also what version of phone is it? is it a m7ul? I'll send you an ruu link if I know what version we're looking at
dc959 said:
Okay so what I want to suggest you do is for starters go in unlock the bootloader as re locking it before doing anything is pointless when once everything is fixed is when you'd need to do it. Also I recommend that you install the custom recovery first and flash the rom from there rather than trying to flash it using fastboot as then at least we can get a standard recovery message which may be easier to find an answer for, I recommend using the very latest twrp recovery from their site as that should be able to flash all roms but make sure you install a stock sense 6 rom as the phone needs to be on the latest update with the kk radios and obviously that means having an hboot of 1.57 which would allow you to install custom roms that are running on kk otherwise you'll have issues and if you've followed what I suggest and it doesn't work a logcat and even a video of what is actually happening will help a lot to see what's going on but first things first is make sure that phone is on the latest hboot and the latest radio.
Also what version of phone is it? is it a m7ul? I'll send you an ruu link if I know what version we're looking at
Click to expand...
Click to collapse
Thanks for the info and help.
The phone is allready been returned to the owner, it was just a repair job because the phone was out of waranty and nobody in this town could fix it. in fact, some idiot that didn't know what he was doing flashed the wrong hboot version (other phone/model) on it somehow and it was a mess.
I did manage to repair it trough an RUU I found I think or I did install a custom sense 6 rom... I don' remember exactly but it had a mismatching hboot version that's all I remember
[Q&A] [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013
Q&A for [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Stuck in bootloader/recovery, Return to stock
Hello!
First post here so please be nice
77_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.29.3218.08
openDSP-v32.120.274.0909
OS-6.09.401.5
eMMC-boot 2048MB
Jul 28 2014,18:52:08.0
I've got a problem with my HTC ONE m7
Tried to install ARHD 81.
So I unlocked the bootloader, installed TWRP and then flashed the ROM.
Rebooted the phone and it stuck to the white HTC loading screen.
Waited for about 20mins. then rebooted the phone. tried flashing the ROM again but no luck there.
So then I did a recovery cache wipe, flashed the recovery, and flashed the ROM again but still stuck.
In desperation I did a wipe... and deleted the actual ROM.zip.
Now I've tried to Sideload the .zip (and original oexed) but get stuck/fail when nearly done.
I've tried to download all the "EU" RUU's and install them but get either error 170 (USB) or error 155 (unknown)
Also tried to download RUU.zip but that didn't work either.
So now i'm stuck! If anyone could point me in the right direction that would be great!
Thanks!
0413Fixxer said:
Hello!
First post here so please be nice
77_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.29.3218.08
openDSP-v32.120.274.0909
OS-6.09.401.5
eMMC-boot 2048MB
Jul 28 2014,18:52:08.0
I've got a problem with my HTC ONE m7
Tried to install ARHD 81.
So I unlocked the bootloader, installed TWRP and then flashed the ROM.
Rebooted the phone and it stuck to the white HTC loading screen.
Waited for about 20mins. then rebooted the phone. tried flashing the ROM again but no luck there.
So then I did a recovery cache wipe, flashed the recovery, and flashed the ROM again but still stuck.
In desperation I did a wipe... and deleted the actual ROM.zip.
Now I've tried to Sideload the .zip (and original oexed) but get stuck/fail when nearly done.
I've tried to download all the "EU" RUU's and install them but get either error 170 (USB) or error 155 (unknown)
Also tried to download RUU.zip but that didn't work either.
So now i'm stuck! If anyone could point me in the right direction that would be great!
Thanks!
Click to expand...
Click to collapse
Looks like you did not flashed arhd using twrp version 2.6.3.3.
flash twrp 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in recovery and adb push arhd:
Code:
adb push name_of_rom.zip /sdcard/
command prompt will be unresponsive for the duration of the push (5-15 min)
then in twrp 2.6.3.3 select "install" and browse to find arhd zip file, select it and swipe to flash then reboot phone.
forget about using a RUU because all RUU available for your phone require S-OFF. (downgrade)
Thank you so very much!
Works brilliantly now!!
Cheers mate! :highfive:
Waiting for device msg after recovery boot
Hi. Please, help me.
So I unlocked my M7 successfully. Then I've tried to make a recovery - I used CWM: recovery-clockwork-touch-6.0.4.8-m7.
But something went wrong. Here's log:
C:\mini-sdk>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting... OKAY
But nothing happened, just screen with "root menu". I tried volume up and down - nothing. Power button - nothing. When I repeated command I got:
C:\mini-sdk>fastboot boot recovery.img
< waiting for device >
What can I do now? Why it went wrong?
In fact I don't even know what was my Android or Sense version after unlocking.
terhie said:
Hi. Please, help me.
So I unlocked my M7 successfully. Then I've tried to make a recovery - I used CWM: recovery-clockwork-touch-6.0.4.8-m7.
But something went wrong. Here's log:
C:\mini-sdk>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting... OKAY
But nothing happened, just screen with "root menu". I tried volume up and down - nothing. Power button - nothing. When I repeated command I got:
C:\mini-sdk>fastboot boot recovery.img
< waiting for device >
What can I do now? Why it went wrong?
In fact I don't even know what was my Android or Sense version after unlocking.
Click to expand...
Click to collapse
you can't boot recovery unless your on hboot 1.44
you have to flash the recovery to the phone to boot to it
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
clsA said:
you can't boot recovery unless your on hboot 1.44
you have to flash the recovery to the phone to boot to it
Click to expand...
Click to collapse
Oh, right! Thanks! My phone is working again.
@clsA
I rather ask than be sorry, so...
After my newbie recovery flashing I have now TWRP and CWM recoveries. How can I delete them (then I'd like to flash CWM once and proper)?
An second question: I'm not sure how to choose between recovery mode and standard. When I want to get to recovery I do it through fastboot. But is it enough to power down if in recovery and power up for standard mode?
Edit:
When in CW Manager I go to recovery mode I recover in TWRP recovery instead of CWM.
terhie said:
@clsA
I rather ask than be sorry, so...
After my newbie recovery flashing I have now TWRP and CWM recoveries. How can I delete them (then I'd like to flash CWM once and proper)?
An second question: I'm not sure how to choose between recovery mode and standard. When I want to get to recovery I do it through fastboot. But is it enough to power down if in recovery and power up for standard mode?
Edit:
When in CW Manager I go to recovery mode I recover in TWRP recovery instead of CWM.
Click to expand...
Click to collapse
you don't have both recovery's ..when you installed TWRP it overwrites any other recovery. If your goal is to flash roms you want TWRP 2.6.3.3 on their.
What is CW Manager and why do you need it ?
clsA said:
you don't have both recovery's ..when you installed TWRP it overwrites any other recovery. If your goal is to flash roms you want TWRP 2.6.3.3 on their.
What is CW Manager and why do you need it ?
Click to expand...
Click to collapse
Clockwork ROM Manager. It showed both recoveries - TWRP and CWM. But then I flashed Stock Recovery, then TWRP 2.6.3.3, then ROM, then again... Well, after few hours of searching, trying, learning differences between flash and boot, and adrenaline kicks when my HTC One didn't boot or stuck somewhere I manage to flash ARHD ROM. I'm quite proud of myself. I wonder though how much trash I left on phone after all of this (yeah, we girls like to have everything in order...)
And if I can - few more questions
I noticed that battery drain is much faster - I probably should calibrate it. Is there a best-for-ARHD-app, or any should be ok?
And in some apps, like Goodreads, I have now additional menu bar at the bottom. I'm sure there is some mode for removing it (specially if stock can do that), but I can't find it.
terhie said:
Clockwork ROM Manager. It showed both recoveries - TWRP and CWM. But then I flashed Stock Recovery, then TWRP 2.6.3.3, then ROM, then again... Well, after few hours of searching, trying, learning differences between flash and boot, and adrenaline kicks when my HTC One didn't boot or stuck somewhere I manage to flash ARHD ROM. I'm quite proud of myself. I wonder though how much trash I left on phone after all of this (yeah, we girls like to have everything in order...)
And if I can - few more questions
I noticed that battery drain is much faster - I probably should calibrate it. Is there a best-for-ARHD-app, or any should be ok?
And in some apps, like Goodreads, I have now additional menu bar at the bottom. I'm sure there is some mode for removing it (specially if stock can do that), but I can't find it.
Click to expand...
Click to collapse
Theirs no left over trash on the phone (except the CW rom manager)
the phone works with partitions. Only one thing can occupy the partition at a time. Whatever you flashed last is all that's their.
The menu bar you mention is only their on GPe roms .. is this what your using ? Their should be no menu bar using ARHD 81
clsA said:
The menu bar you mention is only their on GPe roms .. is this what your using ? Their should be no menu bar using ARHD 81
Click to expand...
Click to collapse
I'm using ARHD 82. I read the FAQ and I think it is that menu (although looks different than on stock Sense6):
http://forum.xda-developers.com/showthread.php?t=2183023 said:
9. How do I get rid of the 3-dot-menu?
As of the 4.2.2 update HTC introduced the Long-press-home-as-menu functionality, which also removes the black menu bar. Activate it under Settings -> Display -> Home Button.
Click to expand...
Click to collapse
but I don't have this option there.
terhie said:
I'm using ARHD 82. I read the FAQ and I think it is that menu (although looks different than on stock Sense6):
but I don't have this option there.
Click to expand...
Click to collapse
It must be a really bad coded app ..that menu was gone by version 4.3 and your Rom is version 4.4.3 - 6.09.401.10
clsA said:
It must be a really bad coded app ..that menu was gone by version 4.3 and your Rom is version 4.4.3 - 6.09.401.10
Click to expand...
Click to collapse
Yeah, they probably don't care about updating to Google changes. But it's not the same menu as 3 dot menu on Stock which was easy to hide. It's not really menu for an app, 3 dots button doesn't even work and rest of buttons is for phone navigation. Any ideas how to hide it?
Guys, I apologize in advance if this is wrong section for my question but it seems my searching powers are not as good as they used to be
I need help regarding HTC One M7_ul 801s PN0714000
This phone has problems with google processes being stopped and it has all kind of chinese apps and bloatware and I would like to install an european rom on it...Phone is s-offed, it has supercid and modelid is PN0711****
Now, I managed to find one kitkat zip file and tried to flash it with "fastboot flash zip" command but i keep getting remote:02 data length is too large...I tried renaming it to PN0714IMG.zip, it didn't help as well...
Is there anything else I should do(beside s-off and supercid) to be able to flash any rom on it, and should I rather go with RUU exe file...if so, can someone please point me out to a place where I can download official roms...I noticed that htc1gury is down...
One more thing, bootloader is locked, phone is not rooted and has no custom recovery installed, and I would like to keep it that way if possible...supercid and s-off were done with Java card, if it is an important info at all...
Please, let me know where I'm making a mistake and if you need any additional info....I apologize one more time if this is a wrong thread or if the answer was so obvious and I was so blind to find it
Tnx in advance....
will method 1 works on HTC one M8 ?
and if .. will i receive OTA update ?
Hello there,
today I tried to install a Custom ROM on my M7 for the first time.
So I unlocked my device with htcdev.com. Btw: it wasn't possible to skip step 11 and I'm using Mac.
So my device is currently unlocked with S-ON (as it can be seen in bootloader).
I want to flash custom recovery and my problem is step 7. ("In the Command Prompt type following command: fastboot boot recovery.img (this command might not with newer hboots)").
When I try this command (on Mac: fastboot-mac), my phone freezes with both ClockworkMod Touch [OFFICIAL] and TWRP. My hboot version is 1.61, maybe that's the problem as mentioned. But I don't want to flash a recovery, maybe I can't use that device after doing that.
Any tips for me?
Best regards
inspi83 said:
Hello there,
today I tried to install a Custom ROM on my M7 for the first time.
So I unlocked my device with htcdev.com. Btw: it wasn't possible to skip step 11 and I'm using Mac.
So my device is currently unlocked with S-ON (as it can be seen in bootloader).
I want to flash custom recovery and my problem is step 7. ("In the Command Prompt type following command: fastboot boot recovery.img (this command might not with newer hboots)").
When I try this command (on Mac: fastboot-mac), my phone freezes with both ClockworkMod Touch [OFFICIAL] and TWRP. My hboot version is 1.61, maybe that's the problem as mentioned. But I don't want to flash a recovery, maybe I can't use that device after doing that.
Any tips for me?
Best regards
Click to expand...
Click to collapse
"fastboot boot recovery.img" was only possible on hboot 1.44. Flash your recovery using "fastboot flash recovery recovery.img". Use latest TWRP recovery.
thx, it worked. phew
Hello guys,
im new to the HTC world, mostly familiar with Sony devices, have a friend who has given me their HTC which isn't booting up, it only boots to the start screen then goes blank, she told me the phone was charging and there was a power surge wherever she was and since then the device misbehaves and doesn't boot past the start screen.
how can I flash it back to stock, as from my experience it seems like its a software issue.
Hey Guys,
Really strange situation here with my HTC One:
It is originally from T-Mobile US although I have brought it to Europe now.
Basically, and I think this happened when implementing an OTA update from my rom, I have lost all access to recovery... any recovery
1) I have erased and re flashed recovery from fastboot, tried both TWRP and Clockwork.
2) I have tried different firmware versions, albeit I don't know which combination is most likely to work...
3) cannot access recovery from phone or via fastboot/adb command, cannot factory reset, cannot flash another rom...
4) Even with hboot locking unlocking and then reflashing of Recovery, still no access.
Funnily, the rom was working fine, but I could not upgrade or change it without recovery...
Phone details below, any help you can provide would be most welcome, I'm not a developer but I've been using custom android roms on phones and tablets for some years and have never encountered this.
Many Many thanks!
Phone Details:
- Carrier Unlocked with T-Mobile code
- Bootloader unlocked with HTC Dev method
- Super CID
- S-OFF
- HBOOT 1.54 (was also on 1.57 but have changed as part of trouble shooting)
- Radio 4T.29.3218.08
- OS 6.09.401.5 (have tried a couple of firmware versions)
- Rom MaximusHD 44.0.1 (now wiped due to troubleshooting with locked/unlocked hboot)
Ammon-Ra said:
Hey Guys,
Really strange situation here with my HTC One:
It is originally from T-Mobile US although I have brought it to Europe now.
Basically, and I think this happened when implementing an OTA update from my rom, I have lost all access to recovery... any recovery
1) I have erased and re flashed recovery from fastboot, tried both TWRP and Clockwork.
2) I have tried different firmware versions, albeit I don't know which combination is most likely to work...
3) cannot access recovery from phone or via fastboot/adb command, cannot factory reset, cannot flash another rom...
4) Even with hboot locking unlocking and then reflashing of Recovery, still no access.
Funnily, the rom was working fine, but I could not upgrade or change it without recovery...
Phone details below, any help you can provide would be most welcome, I'm not a developer but I've been using custom android roms on phones and tablets for some years and have never encountered this.
Many Many thanks!
Phone Details:
- Carrier Unlocked with T-Mobile code
- Bootloader unlocked with HTC Dev method
- Super CID
- S-OFF
- HBOOT 1.54 (was also on 1.57 but have changed as part of trouble shooting)
- Radio 4T.29.3218.08
- OS 6.09.401.5 (have tried a couple of firmware versions)
- Rom MaximusHD 44.0.1 (now wiped due to troubleshooting with locked/unlocked hboot)
Click to expand...
Click to collapse
So what exactly is the problem, does the flash fail? Or successfully flashing but won't load? Does it bootloop or get stuck on a particular screen?
Ammon-Ra said:
Hey Guys,
Really strange situation here with my HTC One:
It is originally from T-Mobile US although I have brought it to Europe now.
Basically, and I think this happened when implementing an OTA update from my rom, I have lost all access to recovery... any recovery
1) I have erased and re flashed recovery from fastboot, tried both TWRP and Clockwork.
2) I have tried different firmware versions, albeit I don't know which combination is most likely to work...
3) cannot access recovery from phone or via fastboot/adb command, cannot factory reset, cannot flash another rom...
4) Even with hboot locking unlocking and then reflashing of Recovery, still no access.
Funnily, the rom was working fine, but I could not upgrade or change it without recovery...
Phone details below, any help you can provide would be most welcome, I'm not a developer but I've been using custom android roms on phones and tablets for some years and have never encountered this.
Many Many thanks!
Phone Details:
- Carrier Unlocked with T-Mobile code
- Bootloader unlocked with HTC Dev method
- Super CID
- S-OFF
- HBOOT 1.54 (was also on 1.57 but have changed as part of trouble shooting)
- Radio 4T.29.3218.08
- OS 6.09.401.5 (have tried a couple of firmware versions)
- Rom MaximusHD 44.0.1 (now wiped due to troubleshooting with locked/unlocked hboot)
Click to expand...
Click to collapse
i guess your problem is you see that written " Entering Recovery " but it wont . right ? if it is the case then you have to lock the bootloader and unlock it again after you unlock it type fastboot erase cache in the fastboot mod and then flash the recovery and then clear cache again ( reboot bootloader maybe and then enter recovery )it will definitely work. Well worked for me Best of Luck
Danny201281 said:
So what exactly is the problem, does the flash fail? Or successfully flashing but won't load? Does it bootloop or get stuck on a particular screen?
Click to expand...
Click to collapse
When you enter recovery, be it from reboot or from bootloader, it shows "entering recovery", then goes dark for a second (you'd expect TWRP screen next) and then goes back to "entering recovery" and doesn't move.
Ammon-Ra said:
When you enter recovery, be it from reboot or from bootloader, it shows "entering recovery", then goes dark for a second (you'd expect TWRP screen next) and then goes back to "entering recovery" and doesn't move.
Click to expand...
Click to collapse
Try this one http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Code:
fastboot flash recovery "name-of -recovery".img
fastboot erase cache
fastboot reboot-bootloader
Then select recovery from the bootloader menu. :good:
Danny201281 said:
Try this one http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Code:
fastboot flash recovery "name-of -recovery".img
fastboot erase cache
fastboot reboot-bootloader
Then select recovery from the bootloader menu. :good:
Click to expand...
Click to collapse
Tried playguy1 method but with the 2.7 TWRP I was originally on. No luck, after relock/unlock/wipe cache/flash/rewipe Cache I was still stuck in entering recovery.
After that tried reboot/wipe cache/ flash Danny201281's suggested openrecovery-twrp-2.6.3.3-m7 and erased cache / reboot...
WORKED!!!!! Many thanks to both guys!
Seems related to ROM/Firmware/Radio/TWRP version combination but it worked fine before.
Danny201281: Is there a particular reason you pointed towards openrecovery-twrp-2.6.3.3-m7 ? Most stable version for HTC One?
Again, great help! Thank you both. :good:
Ammon-Ra said:
Tried playguy1 method but with the 2.7 TWRP I was originally on. No luck, after relock/unlock/wipe cache/flash/rewipe Cache I was still stuck in entering recovery.
After that tried reboot/wipe cache/ flash Danny201281's suggested openrecovery-twrp-2.6.3.3-m7 and erased cache / reboot...
WORKED!!!!! Many thanks to both guys!
Seems related to ROM/Firmware/Radio/TWRP version combination but it worked fine before.
Danny201281: Is there a particular reason you pointed towards openrecovery-twrp-2.6.3.3-m7 ? Most stable version for HTC One?
Again, great help! Thank you both. :good:
Click to expand...
Click to collapse
It's not the first time I've come across this problem here on the forums, and in every case that is the version that always works. Unfortunately it doesn't necessarily mean an end to your problem you may find that is the only recovery that will successfully load.
You can try some different recoveries and see what happens but when all else fails use TWRP 2.6.3.3.