Htc One stuck 4 triangle please help - One (M7) Q&A, Help & Troubleshooting

Hi guys, when i've try to install official ruu RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
i've got error 152 and now my phone stuck with htc and 4 triangle, what can i do to repair it?
My situation
S-On
Locked Bootloader
Stock recovery
Cid E_11

Antoo1984 said:
Hi guys, when i've try to install official ruu RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
i've got error 152 and now my phone stuck with htc and 4 triangle, what can i do to repair it?
My situation
S-On
Locked Bootloader
Stock recovery
Cid E_11
Click to expand...
Click to collapse
which HBOOT version are you on ?

You need to be S-offed and boot loader should be unlocked in order to flash ruu
Sent from my HTC One using Tapatalk

Harish_Kumar said:
You need to be S-offed and boot loader should be unlocked in order to flash ruu
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
No, S-OFF is not compulsory if the HBOOT version of the phone matches the RUU version. Bootloader HAS TO BE LOCKED/RELOCKED

raghav kapur said:
No, S-OFF is not compulsory if the HBOOT version of the phone matches the RUU version. Bootloader HAS TO BE LOCKED/RELOCKED
Click to expand...
Click to collapse
i'm on hboot 1.56

Harish_Kumar said:
You need to be S-offed and boot loader should be unlocked in order to flash ruu
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Not really, With S-ON you can flash signed ruu of same or higher version with bootloader LOCKED or RE-LOCKED.
S-OFF is only needed to flash unsigned RUU or for downgrading, and with S-OFF you can flash a RUU with a locked/relocked or unlocked bootloader.
---------- Post added at 01:54 PM ---------- Previous post was at 01:53 PM ----------
Antoo1984 said:
i'm on hboot 1.56
Click to expand...
Click to collapse
DId you MD5 check the ruu before flashing? error 152 is for ''image error'' and the four triangles with exclamation marks means the ruu did not flash completely.
Edit: So you were on 4.19.401.11 before flashing 4.19.401.9 ? You can't downgrade with S-ON

DId you MD5 check the ruu before flashing? error 152 is for ''image error'' and the four triangles with exclamation marks means the ruu did not flash completely.
no i've downloaded this ruu from htc1guru RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1
and i've got the error
now what can i do?

Antoo1984 said:
DId you MD5 check the ruu before flashing? error 152 is for ''image error'' and the four triangles with exclamation marks means the ruu did not flash completely.
no i've downloaded this ruu from htc1guru RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1
and i've got the error
now what can i do?
Click to expand...
Click to collapse
The issue was that before flashing the RUU, the phone firmware was higher than the RUU firmware. The phone was 4.19.401.11 while the RUU is 4.19.401.9. S-OFF is required to flash a lower firmware
Your solution:
1) Unlock bootloader
2) Flash TWRP 2.6.3.3
3) adb sideload ARHD
4) S-OFF using Firewater
5) Then relock/lock the bootloader. Remove TAMPERED if you want. Then flash the RUU
(you can set the bootloader to LOCKED and remove the TAMPERED flag if S-OFF)

raghav kapur said:
The issue was that before flashing the RUU, the phone firmware was higher than the RUU firmware. The phone was 4.19.401.11 while the RUU is 4.19.401.9. S-OFF is required to flash a lower firmware
Your solution:
1) Unlock bootloader
2) Flash TWRP 2.6.3.3
3) adb sideload ARHD
4) S-OFF using Firewater
5) Then relock/lock the bootloader. Remove TAMPERED if you want. Then flash the RUU
(you can set the bootloader to LOCKED and remove the TAMPERED flag if S-OFF)
Click to expand...
Click to collapse
i've try to unlock bootloader but noting happen, say always relocked

Antoo1984 said:
i've try to unlock bootloader but noting happen, say always relocked
Click to expand...
Click to collapse
You don't get to the unlock bootloader option ??

no nothing

Antoo1984 said:
no nothing
Click to expand...
Click to collapse
I really don't know if there is a solution, maybe we could ask @nkk71 if he have an idea....
OP is stuck in ruu mode after an incomplete ruu flash from 4.19.401.11 to 4.19.401.9. S-ON, bootloader relocked (not able to unlock again). THe only option in bootloader is RUU in orange.

Antoo1984 said:
no nothing
Click to expand...
Click to collapse
Yes, @nkk71 might have an idea. Im just sharing what I know- If you cannot get into fastboot also, you really have a serious problem. Your only option (not 100% sure) is an RUU based on 4.19.401.11, which doesn't currently exist. If there is another solution, I don't know. But I think you will have to wait for an RUU based on your version.

Antoo1984 said:
i'm on hboot 1.56
Click to expand...
Click to collapse
That screenshot does not look nice!
you're firmware is in limbo... from the looks of it, you did the first flash, but didn't do the second flash.
So first make sure the RUU you have is not corrupt, the MD5 should be 9AD4111CE86981E3DFFCCE6D9EE80551
Second, do you still have a custom recovery installed, or a rooted ROM?

I've stock recovery , i'm sure
Before i've a stock rom by grureset
I can use ruu 4.19.401.9? Or can i flash rom.zip with fastboot?
Inviato dal mio GT-N8000 usando XDA Premium HD app

Finally i've found a solution!!!!
i've downloaded the ota 4.19.401.11 extract firmware.zip
flash it with fastboot 2 times and now i can access to bootloader!!
Thanks for support

Related

[SOLVED] Dead phone, RUU fails

The recovery is broken, and the rom doesn't boot.
I can enter the recovery, but as soon as I try to wipe data or install a rom, it reboots. I tried "fastboot erase cache", I tried reflashing CWM and TWRP, and I tried ADB Sideload on both, same results.
The only way for me is to run RUU, but the problem is, any RUU that I try says "The ROM Update Utility Cannot update you Android phone. Please get the correct ROM Update Utility and try again.
I am s-off and supercid on hboot 1.55, with the 3.57 firmware. Any ideas on how to get the RUU working? Thanks!
Shu. said:
The recovery is broken, and the rom doesn't boot.
I can enter the recovery, but as soon as I try to wipe data or install a rom, it reboots. I tried "fastboot erase cache", I tried reflashing CWM and TWRP, and I tried ADB Sideload on both, same results.
The only way for me is to run RUU, but the problem is, any RUU that I try says "The ROM Update Utility Cannot update you Android phone. Please get the correct ROM Update Utility and try again.
I am s-off and supercid on hboot 1.55, with the 3.57 firmware. Any ideas on how to get the RUU working? Thanks!
Click to expand...
Click to collapse
which RUU are using? you probably have to change CID to SuperCID.
also read through this about recovery problems: http://forum.xda-developers.com/showthread.php?t=2494111
EDIT: also for RUU to work, I believe you need to be locked or relocked.
nkk71 said:
which RUU are using? you probably have to change CID to SuperCID.
also read through this about recovery problems: http://forum.xda-developers.com/showthread.php?t=2494111
EDIT: also for RUU to work, I believe you need to be locked or relocked.
Click to expand...
Click to collapse
Okay, then that seems to be the issue, i'll try to relock, thanks!
Shu. said:
Okay, then that seems to be the issue, i'll try to relock, thanks!
Click to expand...
Click to collapse
DO NOT GO S-ON !!
and check CID if it's compatible with the RUU, otherwise change to SuperCID.
nkk71 said:
DO NOT GO S-ON !!
and check CID if it's compatible with the RUU, otherwise change to SuperCID.
Click to expand...
Click to collapse
I am already super CID, so I think the only issue is with the unlocked boot loader. I'm gonna try to re-lock it now. And thanks again for the warning, I won't go s-on
If you have S-off you don't have to lock your bootloader to run a ruu.
Shu. said:
I am already super CID, so I think the only issue is with the unlocked boot loader. I'm gonna try to re-lock it now. And thanks again for the warning, I won't go s-on
Click to expand...
Click to collapse
No problem :good:
Post back with your results so we know
maxal said:
If you have S-off you don't have to lock your bootloader to run a ruu.
Click to expand...
Click to collapse
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
maxal said:
If you have S-off you don't have to lock your bootloader to run a ruu.
Click to expand...
Click to collapse
EddyOS said:
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
Click to expand...
Click to collapse
If that is the case, could the newer version of the hboot cause the issue? because I'm trying to flash an old RUU. I tried the hTC_Asia_WWE_1.29.707.3, which is for my region, as well as US_WWE_1.29.1540.16 (developer edition) as I'm supercid. both failed
maxal said:
If you have S-off you don't have to lock your bootloader to run a ruu.
Click to expand...
Click to collapse
EddyOS said:
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
Click to expand...
Click to collapse
I stand corrected
---------- Post added at 05:11 PM ---------- Previous post was at 05:09 PM ----------
Shu. said:
If that is the case, could the newer version of the hboot cause the issue? because I'm trying to flash an old RUU. I tried the hTC_Asia_WWE_1.29.707.3, which is for my region, as well as US_WWE_1.29.1540.16 (developer edition) as I'm supercid. both failed
Click to expand...
Click to collapse
with S-Off it's no problem to downgrade. where did you get the RUU, can you post link.
And what's the exact error you get?
EddyOS said:
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
Click to expand...
Click to collapse
Now I tried the developer edition 3.22.1540.1 that I just downloaded from HTC dev, and its installing, so I think its gonna be okay. Thanks to everyone for the speedy replies!
Shu. said:
Now I tried the developer edition 3.22.1540.1 that I just downloaded from HTC dev, and its installing, so I think its gonna be okay. Thanks to everyone for the speedy replies!
Click to expand...
Click to collapse
For other RUUs check this site: http://www.htc1guru.com/downloads/ruu-file-downloads/
I find HTCdev way too confusing, as it clutters everything together, you can easily download a RUU for "HTC One S" instead of "HTC One" (aka M7)
And since you're S-Off downgrading is no problem

[Q] Going back to Stock ATT

hello everyone,
i recently changed my ATT HTC to International version with Mid-PN0710000 and CID- HTC_J15 and i would like to go back to stock ATT, im currently running 4.3, S-OFF,unlocked and HBOOT-1.55.. i should change my CID and MID to ATT and then what ??
biopl said:
hello everyone,
i recently changed my ATT HTC to International version with Mid-PN0710000 and CID- HTC_J15 and i would like to go back to stock ATT, im currently running 4.3, S-OFF,unlocked and HBOOT-1.55.. i should change my CID and MID to ATT and then what ??
Click to expand...
Click to collapse
and then go there: http://forum.xda-developers.com/showthread.php?t=2541082
Best guide on how to return stock.
hope it help
alray said:
and then go there: http://forum.xda-developers.com/showthread.php?t=2541082
Best guide on how to return stock.
hope it help
Click to expand...
Click to collapse
thanks for quick reply.... downgrading Hboot, will it work on any S-off device??
biopl said:
thanks for quick reply.... downgrading Hboot, will it work on any S-off device??
Click to expand...
Click to collapse
yes
But before downgrading hboot, check what RUU are available for ATT. I think there is a 3.xx.502.x RUU that works with hboot 1.55
alray said:
yes
But before downgrading hboot, check what RUU are available for ATT. I think there is a 3.xx.502.x RUU that works with hboot 1.55
Click to expand...
Click to collapse
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 Radio 4A.19.3263.13 10.38j.1157.04 Release 334235 Signed 2
this RUU.exe should be good ryt ?
biopl said:
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 Radio 4A.19.3263.13 10.38j.1157.04 Release 334235 Signed 2
this RUU.exe should be good ryt ?
Click to expand...
Click to collapse
yes that's the one and on a side note theirs a decrypted version RUU.zip of it that will work with your current MID and CID with a small alteration to the android-info.txt
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
Instructions for Flashing RUU Zip Files:
Download the RUU.zip file and place in your ADB/fastboot folder. I would recommend renaming the zip file to something simple like ruu.zip.
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
adb reboot-bootloader
Now use these fastboot commands:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the ruu.zip file:
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
fastboot reboot
**Notes about the RUU.zip method. You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first. If you are running the RUU.zip as base to downgrade all your firmware because you are going to then going to restore a stock Nandroid so the RUU might not be made for your MID, so you may need to edit the android-info.txt inside the ruu.zip to include your MID or CID.
Click to expand...
Click to collapse
clsA said:
yes that's the one and on a side note theirs a decrypted version RUU.zip of it that will work with your current MID and CID with a small alteration to the android-info.txt
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
Click to expand...
Click to collapse
i have changed my cid and mid to ATT, now just i need to run RUU.exe ryt ?
biopl said:
i have changed my cid and mid to ATT, now just i need to run RUU.exe ryt ?
Click to expand...
Click to collapse
yes
biopl said:
i have changed my cid and mid to ATT, now just i need to run RUU.exe ryt ?
Click to expand...
Click to collapse
do NOT try going S-On with that hboot version!
nkk71 said:
do NOT try going S-On with that hboot version!
Click to expand...
Click to collapse
i dont plan to
biopl said:
i dont plan to
Click to expand...
Click to collapse
:good::good:
nkk71 said:
:good::good:
Click to expand...
Click to collapse
I don't understand .. the only time it is safe to go s-on is after flashing the signed ruu
why are you saying different ?
Keep in mind I'm on the side of never going s-on for any reason!
clsA said:
I don't understand .. the only time it is safe to go s-on is after flashing the signed ruu
why are you saying different ?
Keep in mind I'm on the side of never going s-on for any reason!
Click to expand...
Click to collapse
hboot 1.55 introduced an interesting patch, when going from S-Off to S-On, after a few reboots it comes back with "tamper detected - rebooting", and then TAMPERED is back in bootloader.
NB: i cannot confirm this to be 100% true, but i've seen more than a few posts that confirm, even after a full signed ruu etc etc etc, this has happened.
only way to avoid it was to go s-on before updating to 1.55 (hence my guide says to downgrade to lowest version)

[Q] Downgrade HBoot/firmware for repair?

Hi,
I want to send my HTC One in for repair, so first I need to restore it to stock.
However, I recently updated my firmware (and hboot) to the new 4.4.3 base (http://forum.xda-developers.com/showthread.php?t=2793539) so right now I am (s-off) on hboot 1.57.0000... Is this a problem when sending it in since this firmware isn't officially released yet (or is it)? And if it is, is it possible to downgrade my hboot?
Also, must I flash the firmware WITH the red warning before going S-on and locking the bootloader again?
I have flashed the stock odexed ROM, boot.img and recovery from the ARHD site (http://android-revolution-hd.blogspot.nl/p/android-revolution-hd-mirror-site-var.html).
Thanks in advance for any help!
No that firmware isn't officially released yet, it's still in testing stages so you will have to downgrade your firmware to 5.??.401.? Lucky for you this firmware comes with hboot 1.57 however if you have flashed a modded hboot/firmware ie to remove red text, then you will need to flash an official one, just find the official firmware package and use that, it comes with the hboot inside it, if you s-on with modded firmware or hboot you will have an instant brick.
The arhd site your got the Rom from should have the firmware package too.
Seanie280672 said:
No that firmware isn't officially released yet, it's still in testing stages so you will have to downgrade your firmware to 5.??.401.? Lucky for you this firmware comes with hboot 1.57 however if you have flashed a modded hboot/firmware ie to remove red text, then you will need to flash an official one, just find the official firmware package and use that, it comes with the hboot inside it, if you s-on with modded firmware or hboot you will have an instant brick.
The arhd site your got the Rom from should have the firmware package too.
Click to expand...
Click to collapse
Great, thanks! I will flash the original firmware in a sec, but the most recent RUU I can find is this one: http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
And I am not sure if that is also based on hboot 1.57 and because of that, if I am able to flash this RUU. Currently I am downloading it but the download speed is terrible, I will report back after I tried.
Or are you saying that I can flash the stock firmware 5.xx.401.xx on top of the current 6.xx firmware? I thought that wouldn't be possible because I'm currently on a higher firmware version but I'll give it a shot!
If you are s-off, you can flash or downgrade anything, however I would personally flash the matching firmware to the ruu that you are downloading, however, the firmware and hboot will be included in the ruu and be downgraded when you run the ruu, so just run it, once it's finished and you boot the phone, you can ota up to the latest version.
Seanie280672 said:
If you are s-off, you can flash or downgrade anything, however I would personally flash the matching firmware to the ruu that you are downloading, however, the firmware and hboot will be included in the ruu and be downgraded when you run the ruu, so just run it, once it's finished and you boot the phone, you can ota up to the latest version.
Click to expand...
Click to collapse
Ah I see, thanks a lot! Still waiting for the RUU to finish, I'll download the corresponding firmware and flash it before I start the RUU. Thanks again!
WiiiLDFARMER said:
Ah I see, thanks a lot! Still waiting for the RUU to finish, I'll download the corresponding firmware and flash it before I start the RUU. Thanks again!
Click to expand...
Click to collapse
You may have to remove the TAMPERED flag before running the ruu and also lock your bootloader, not relocked as the ruu will replace which ever recovery you ha e on your phone for the stock one, sometimes the ruu requires a locked bootloader whether s-off or s-on.
Once it's finished, boot the phone once and then back into bootloader and check the hboot version, if it is lower than the version you have on there now then you'll know you have stock hboot and should be safe to s-on, however like I said before, make sure your locked and tampered has gone before setting s-on (not sure if s-on is required for warranty)
Seanie280672 said:
You may have to remove the TAMPERED flag before running the ruu and also lock your bootloader, not relocked as the ruu will replace which ever recovery you ha e on your phone for the stock one, sometimes the ruu requires a locked bootloader whether s-off or s-on.
Click to expand...
Click to collapse
At the moment I don't have a tampered flag, it only says 'unlocked'. I'll try to lock the bootloader before starting the RUU. Do you know if the Tampered flag will return if I S-ON my M7 after completing the RUU?
WiiiLDFARMER said:
At the moment I don't have a tampered flag, it only says 'unlocked'. I'll try to lock the bootloader before starting the RUU. Do you know if the Tampered flag will return if I S-ON my M7 after completing the RUU?
Click to expand...
Click to collapse
Unfortunately I don't know that, there's been some reports it comes back after you s-on not after the ruu, I think it's HTC 's way of catching you out, others say it's been fine, are you sending it to HTC or your operator ?
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
However , if you've had s-off with that phone before, chances are you'll get it again, you'll just have to do whatever you did before to get it, then go back to stock again, and send it s-off.
WiiiLDFARMER said:
Hi,
I want to send my HTC One in for repair, so first I need to restore it to stock.
However, I recently updated my firmware (and hboot) to the new 4.4.3 base (http://forum.xda-developers.com/showthread.php?t=2793539) so right now I am (s-off) on hboot 1.57.0000... Is this a problem when sending it in since this firmware isn't officially released yet (or is it)? And if it is, is it possible to downgrade my hboot?
Also, must I flash the firmware WITH the red warning before going S-on and locking the bootloader again?
I have flashed the stock odexed ROM, boot.img and recovery from the ARHD site (http://android-revolution-hd.blogspot.nl/p/android-revolution-hd-mirror-site-var.html).
Thanks in advance for any help!
Click to expand...
Click to collapse
Try this guide:
http://forum.xda-developers.com/showthread.php?t=2541082
It worked for me, returned full stock!

Trying to go back to stock. Failing...

Hello everyone,
I've been trying to get back to stock on my Sprint HTC One. I have tried using the RUU in this thread: http://forum.xda-developers.com/showthread.php?t=2795856 and no luck. I am HBoot 1.55, S-ON, and running a stock rooted rom that is on 4.4.2
So here is what I tried. I relock my bootloader and proceed to run the RUU, but 2 times I get stuck on 4% so I have no luck. I tried getting S-Off and maybe that could help me bring back to stock, but that did not work either. Really need to get this phone back to Stock, any help is appreciate it, no one responded in that thread so I'm asking here. Thanks in advance.
You'll need to flash the Full Firmware first.
If it still gets stuck try a different USB Port...USB 2 work best or try a different PC.
BD619 said:
You'll need to flash the Full Firmware first.
If it still gets stuck try a different USB Port...USB 2 work best or try a different PC.
Click to expand...
Click to collapse
That is what the video at the bottom of the first post on that thread is about, correct?
Don't I have to be S-Off for that? It says on the video that I have to, and I am not.
PaoloMix09 said:
That is what the video at the bottom of the first post on that thread is about, correct?
Don't I have to be S-Off for that? It says on the video that I have to, and I am not.
Click to expand...
Click to collapse
Use This Firmware
You will need to re-lock your bootloader (fastboot oem lock)
Flash firmware (follow the video)
Run the RUU and you will be back to stock.
You do not need to be s-off to do either.
BD619 said:
Use This Firmware
You will need to re-lock your bootloader (fastboot oem lock)
Flash firmware (follow the video)
Run the RUU and you will be back to stock.
You do not need to be s-off to do either.
Click to expand...
Click to collapse
Trying to flash it but it won't . Fails checking signature. "Signature verify fail"
Sent from crispy tocino
PaoloMix09 said:
Trying to flash it but it won't . Fails checking signature. "Signature verify fail"
Sent from crispy tocino
Click to expand...
Click to collapse
Did you re-lock your bootloader?
Is the firmware in your adb/fastboot/platform tools folder?
BD619 said:
Did you re-lock your bootloader?
Is the firmware in your adb/fastboot/platform tools folder?
Click to expand...
Click to collapse
Yes sir. Relocked, only that at the top it says "security warning." I renamed the folder to firmware.zip and it is on the platform tools folder. Did all the commands, but the second time I run the same command (like it says on the video) it gives me the error I mentioned and I don't even get the loading bar on the phone. Tried 3 times, no luck.
Sent from crispy tocino
Check PM
Same problem actually
BD619 said:
Check PM
Click to expand...
Click to collapse
I am actually having the same issue as described above, and cannot for the life of me figure out what I did wrong.
Any insight?
saxman126 said:
I am actually having the same issue as described above, and cannot for the life of me figure out what I did wrong.
Any insight?
Click to expand...
Click to collapse
So Hboot 1.55, S-ON, and can't go back to stock?
Go to this: http://forum.xda-developers.com/showthread.php?t=2658910
Download that RUU. Now, go into fastboot and relock your bootloader. Flash the firmware on that thread through fastboot, there's a video there showing you how. After that is done, go back to fastboot and you can run the RUU you downloaded from that thread. That's what I did and worked like a charm. Recommended if you use USB 2.0
PaoloMix09 said:
So Hboot 1.55, S-ON, and can't go back to stock?
Go to this: http://forum.xda-developers.com/showthread.php?t=2658910
Flash the firmware on that thread through fastboot, there's a video there showing you how. After that is done, go back to fastboot and you can run the RUU you downloaded from that thread.
Click to expand...
Click to collapse
Hi. You mean flash 4.06.651.4 version at first and then flash 5.05.651.2 version ? Is it update HBOOT from 1.55 to 1.56? What about warning message on that thread "***IMPORTANT NOTE*** you must first update your hboot to 1.56 to flash this 4.06 RUU, see full firmware below ( I recommend being s-off before doing so)"
I have. Hboot 1.55, S-on, Custom ViperOne 7.0.1
kai82 said:
Hi. You mean flash 4.06.651.4 version at first and then flash 5.05.651.2 version ? Is it update HBOOT from 1.55 to 1.56? What about warning message on that thread "***IMPORTANT NOTE*** you must first update your hboot to 1.56 to flash this 4.06 RUU, see full firmware below ( I recommend being s-off before doing so)"
I have. Hboot 1.55, S-on, Custom ViperOne 7.0.1
Click to expand...
Click to collapse
Just flash firmware 4.06.651.4 (you'll be on hboot 1.56) and then run that RUU. Don't worry about 5.05.651.2 firmware or RUU.
Make sure you relock your bootloader before anything.
Whenever the RUU is done and you're back in stock, you'll get the OTAs to 5.05.651.2, just telling you exactly what I did that worked, I also had a lot of trouble getting back to stock/unrooting.
Sent from crispy tocino

[Q] Can I downgrade 6.06 to 1.29 with S-OFF

Hi all, I was just wondering if I should run the RUU ZIP or EXE if I am on S-OFF.
I currently have the 6.06.401.1 firmware along with the stock 6.06.401.1 rom. I need to return to the stock 1.29.707.1 for my HTC__044 before taking the latest OTA to Android Lollipop.
So far, I have used my S-OFF to change my bootloader to *LOCKED* and flashed stock recovery and stock rom for the 6.06.401.1.
I currently have both the 1.29.707.1 RUU EXE and ZIP. Which one should I use? I read that I need to have the 1.44 Hboot but I currently have the 1.54 Hboot.
Halp?
uhm, what? this is nonsense , the lastest available RUU is "4.19.401.9" which must be flashed under hboot 1.56 ... there is no need to go to initial release of android 4.1!
WARNING!!! YOU MUST FLASH HBOOT 1.56 BEFORE APPLYING 4.19.401.9 RUU
RUU: http://d-h.st/KmT
+There is no need to LOCK your bootloader to get an OTA update... Mine is always unlocked and never had a problem with OTA's
+RUU's work only under S-OFF
Androidian10 said:
Hi all, I was just wondering if I should run the RUU ZIP or EXE if I am on S-OFF.
I currently have the 6.06.401.1 firmware along with the stock 6.06.401.1 rom. I need to return to the stock 1.29.707.1 for my HTC__044 before taking the latest OTA to Android Lollipop.
So far, I have used my S-OFF to change my bootloader to *LOCKED* and flashed stock recovery and stock rom for the 6.06.401.1.
I currently have both the 4.20.707.1 RUU EXE and ZIP. Which one should I use? I read that I need to have the 1.44 Hboot but I currently have the 1.54 Hboot.
Halp?
Click to expand...
Click to collapse
you can use the RUU you have fine 4.20.707.1, you'll just have to make sure your cid and mid match first, and also just flash the 4.20.707.1 firmware first, this will put you on the correct HBOOT and system files for the RUU, no need to lock your bootloader with s-off.
or you can skip all of that and just flash the 7.19.401.2 RUU right now as your phone is as your already on the 6.xx.401.x firmware.
you don't really have any reason to back flash.
Seanie280672 said:
you can use the RUU you have fine 4.20.707.1, you'll just have to make sure your cid and mid match first, and also just flash the 4.20.707.1 firmware first, this will put you on the correct HBOOT and system files for the RUU, no need to lock your bootloader with s-off.
or you can skip all of that and just flash the 7.19.401.2 RUU right now as your phone is as your already on the 6.xx.401.x firmware.
you don't really have any reason to back flash.
Click to expand...
Click to collapse
But I can't seem to find a 4.20.707.1 RUU. I only have the 1.29.707.3 firmware. I need a region specific one because I need to trade my phone in.
Could you point me in the direction of a 4.20.707.1 RUU zip?
Also, is it safe to OTA update if I flash back to 1.29 with S-OFF?
Edit: Crap I made a typo in my OP, I mean that I have the 1.29 RUU EXE and ZIP right now.
Androidian10 said:
But I can't seem to find a 4.20.707.1 RUU. I only have the 1.29.707.3 firmware. I need a region specific one because I need to trade my phone in.
Edit: Crap I made a typo in my OP, I mean that I have the 1.29 RUU EXE and ZIP right now.
Could you point me in the direction of a 4.20.707.1 RUU zip?
Also, is it safe to OTA update if I flash back to 1.29 with S-OFF?
Click to expand...
Click to collapse
I thought you said you had the 4.20.707.1 RUU
if not then you'll have to use the 1.29.707 one that you have, you'll just have to flash the 1.44 hboot first or the firmware that matches the RUU.
Seanie280672 said:
I thought you said you had the 4.20.707.1 RUU
if not then you'll have to use the 1.29.707 one that you have, you'll just have to flash the 1.44 hboot first or the firmware that matches the RUU.
Click to expand...
Click to collapse
Yeah I had a typo.
So yeah, I have both the EXE and ZIP RUU.
I'm thinking that the ZIP RUU has the 1.44 hboot no?
Also, most importantly, can I take official OTA updates while I am S-OFFed?
Androidian10 said:
Yeah I had a typo.
So yeah, I have both the EXE and ZIP RUU.
I'm thinking that the ZIP RUU has the 1.44 hboot no?
Also, most importantly, can I take official OTA updates while I am S-OFFed?
Click to expand...
Click to collapse
yes you can take OTA's whilst s-off, do not go s-on at any point.
I would also say try the RUU.zip first.
Seanie280672 said:
yes you can take OTA's whilst s-off, do not go s-on at any point.
I would also say try the RUU.zip first.
Click to expand...
Click to collapse
Righto. Will report back again.
I hope the guy at the store doesn't go into the bootloader when I trade my m7 in. Even then I already set the flag to locked so I think he'll miss that S-OFF portion.
Androidian10 said:
Righto. Will report back again.
I hope the guy at the store doesn't go into the bootloader when I trade my m7 in. Even then I already set the flag to locked so I think he'll miss that S-OFF portion.
Click to expand...
Click to collapse
cid and mid need to match the ruu your flashing first.
Seanie280672 said:
cid and mid need to match the ruu your flashing first.
Click to expand...
Click to collapse
Already checked with fastboot getvar all.
Seanie280672 said:
cid and mid need to match the ruu your flashing first.
Click to expand...
Click to collapse
Actually, problem. :/
I have a matching CID which is HTC__044 but the modelid is PN0714000.
The RUU's android-info has a matching CID of HTC__044 but a modelid of PN0711000.
What now?
Androidian10 said:
Actually, problem. :/
I have a matching CID which is HTC__044 but the modelid is PN0714000.
The RUU's android-info has a matching CID of HTC__044 but a modelid of PN0711000.
What now?
Click to expand...
Click to collapse
unlock your bootloader, flash twrp recovery and change your mid, are you sure your using the RUU for the M7_UL as that looks a lot like the M7_U mid too me, can you give me a link for the RUU's you downloaded please.
---------- Post added at 11:05 AM ---------- Previous post was at 10:57 AM ----------
here you go, do this instead, this is going to be a bit backwards and forwards.
Unlock your bootloader, and flash TWRP recovery, then use the mid change tool to change your mid to the correct one.
https://www.androidfilehost.com/?fid=23622183712469376
next copy this guru reset file to your internal storage and flash it, select no to stock radio and no to stock recovery: http://www.htc1guru.com/2013/11/guru-reset-3-63-707-4-stock-rom/
now lock your bootloader
and finally flash the matching firmwqare from here: http://d-h.st/BWu this will put stock recovery and stock radio on your phone.
Seanie280672 said:
unlock your bootloader, flash twrp recovery and change your mid, are you sure your using the RUU for the M7_UL as that looks a lot like the M7_U mid too me, can you give me a link for the RUU's you downloaded please.
Click to expand...
Click to collapse
I actually ran the RUU. It's now stuck on waiting for device after the usual flush after 90 hboot pre-update.
I changed the modelid in the android-info.txt since it was decrypted.
Anyone help me?
My computer can't see the device anymore after flashing the hboot!
Androidian10 said:
Anyone help me?
My computer can't see the device anymore after flashing the hboot!
Click to expand...
Click to collapse
if your using windows 8 or higher then that's the problem, HBOOT 1.44 doesn't work with it, there is a fix around here somewhere by @clsA but ive never had to use it myself.
trouble with changing the android-info text file is all of the OTA's will fail due to you having the wrong mid on your phone, you'll have to change your phones mid as soon as possible.
Seanie280672 said:
if your using windows 8 or higher then that's the problem, HBOOT 1.44 doesn't work with it, there is a fix around here somewhere by @clsA but ive never had to use it myself.
trouble with changing the android-info text file is all of the OTA's will fail due to you having the wrong mid on your phone, you'll have to change your phones mid as soon as possible.
Click to expand...
Click to collapse
Ok, I have changed to an old Windows 7 laptop and tried doing the fastboot flash zip again. After I press enter, nothing happens at all. Not a single code at all. Just a blinker.
Edit: Started moving again. Phew. I almost had a heart attack.
So now do I do the fastboot writemid command?
Androidian10 said:
Ok, I have changed to an old Windows 7 laptop and tried doing the fastboot flash zip again. After I press enter, nothing happens at all. Not a single code at all. Just a blinker.
Edit: Started moving again. Phew. I almost had a heart attack.
So now do I do the fastboot writemid command?
Click to expand...
Click to collapse
to change the mid you need to use the mid change tool I posted a link to it earlier, install it inside twrp recovery then select the mid you require from the list it gives you.
Seanie280672 said:
to change the mid you need to use the mid change tool I posted a link to it earlier, install it inside twrp recovery then select the mid you require from the list it gives you.
Click to expand...
Click to collapse
It's okay now. I found a matching mid RUU for my phone.
But my question now is should I go S-ON to remove the red "This is a test device. Accordingly, to collect critical information about the device, Tell HTC is enabled and cannot be turned off regardless of device settings" warning? Or just leave it S-OFF and hope that the techies at the store doesn't notice it?
More questions
I have done all the OTAs now so should I do the fastboot oem writesecureflag 3 as the final step before putting the phone aside to trade it in?
Androidian10 said:
More questions
I have done all the OTAs now so should I do the fastboot oem writesecureflag 3 as the final step before putting the phone aside to trade it in?
Click to expand...
Click to collapse
no, leave it s-off, if you turn it back s-on now you will get the tampered flag back.

Categories

Resources