Hi there. I've got a taiwanese M7_U on my hands. Someone before me tried to flash custom ROM and failed dramatically. It's unlocked, has TWRP, but has no ROM flashed. I tried to reinstall stock ROM, but it fails as well: any Sense-based zip ROM goes into bootloop. I tried latest Android Revolution, ViperOne and stock zip repacks. I was able to capture logcat of ViperOne but couldn't find any obvious reasons of bootloops, so it is attached. Only ROM I got to boot on this device at least was CM12.1 nightly build. The worst - i can't install RUU for some reason, even after bootloader relock and flashing stock recovery. I suspect that the trouble is because of incompatible MID (PN0711000) and CID (HTC__621) for most RUU packages. The only compatible RUU build I was able to find is obviously outdated (1.20.709.101 vs current mainver of 7.18.709.102). I can't get S-OFF because HBOOT is already updated to 1.61.
I guess that if I want to get a stock-ish ROM running on that device my options are:
1. Figuring out why ViperOne and AndroidRevolution are bootloopin' (again, logcat attached)
2. Getting latest RUU for MID = PN0711000 and CID = HTC__621
3. Managing to get S-OFF for HBOOT 1.61, changing MID and CID and flashing common M7_UL RUU
4. Patching common M7_UL RUU to bypass MID/CID check.
I would appreciate any help in getting any of these options to work. I might've missed some importand guides, but quick search didn't help much, any help with finding guides or compatible RUUs would be appreciated as well.
k3lwin said:
Hi there. I've got a taiwanese M7_U on my hands. Someone before me tried to flash custom ROM and failed dramatically. It's unlocked, has TWRP, but has no ROM flashed. I tried to reinstall stock ROM, but it fails as well: any Sense-based zip ROM goes into bootloop. I tried latest Android Revolution, ViperOne and stock zip repacks. I was able to capture logcat of ViperOne but couldn't find any obvious reasons of bootloops, so it is attached. Only ROM I got to boot on this device at least was CM12.1 nightly build. The worst - i can't install RUU for some reason, even after bootloader relock and flashing stock recovery. I suspect that the trouble is because of incompatible MID (PN0711000) and CID (HTC__621) for most RUU packages. The only compatible RUU build I was able to find is obviously outdated (1.20.709.101 vs current mainver of 7.18.709.102). I can't get S-OFF because HBOOT is already updated to 1.61.
I guess that if I want to get a stock-ish ROM running on that device my options are:
1. Figuring out why ViperOne and AndroidRevolution are bootloopin' (again, logcat attached)
2. Getting latest RUU for MID = PN0711000 and CID = HTC__621
3. Managing to get S-OFF for HBOOT 1.61, changing MID and CID and flashing common M7_UL RUU
4. Patching common M7_UL RUU to bypass MID/CID check.
I would appreciate any help in getting any of these options to work. I might've missed some importand guides, but quick search didn't help much, any help with finding guides or compatible RUUs would be appreciated as well.
Click to expand...
Click to collapse
What is your custom recovery version?
7.18.709.120 ruu here: http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_U/
Requires s-off
Won't work. You can only flash signed ruu on a s-on phone. Any alteration of the ruu will prevent it to be flashed.
alray said:
What is your custom recovery version?
7.18.709.120 ruu here:
Requires s-off
Won't work. You can only flash signed ruu on a s-on phone. Any alteration of the ruu will prevent it to be flashed.
Click to expand...
Click to collapse
1. Tried flashing Viper and ARHD with both TWRP 2.8.6.0 and CWM Touch 6.0.4.8, no luck.
2. I've got 7.18.709.102 and 7.21.707.105 RUU zips, installation via fastboot of both fails with error (remote: 02 data length is too large).
I think that exe RUU of 7.18.709.102 might work, but I can't find it anywhere. Any suggestions?
k3lwin said:
1. Tried flashing Viper and ARHD with both TWRP 2.8.6.0 and CWM Touch 6.0.4.8, no luck.
2. I've got 7.18.709.102 and 7.21.707.105 RUU zips, installation via fastboot of both fails with error (remote: 02 data length is too large).
I think that exe RUU of 7.18.709.102 might work, but I can't find it anywhere. Any suggestions?
Click to expand...
Click to collapse
Try with twrp 2.6.3.3
you need to use htc_fastboot.exe not the regular (google) fastboot.
alray said:
Try with twrp 2.6.3.3
you need to use htc_fastboot.exe not the regular (google) fastboot.
Click to expand...
Click to collapse
With TWRP 2.6.3.3 I still got bootloop after flashing ARHD, but flashing RUU with htc_fastboot finally got this device working. Thanks a lot!
Related
HTC One
Tamperd
Relocked
2.24.401.8
S-ON
Cidnum HTC_Y13
Hboot: 1.54.0
I'm using this 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
I double checked my fastboot connection, every thing seems to be working just fine.
Everytime i try to run it it get stuck at checking headers (5%)
what am i doing wrong ?
I think there is something wrong with that ruu. I have not been able to run the 4.x RUU
SaHiLzZ said:
I think there is something wrong with that ruu. I have not been able to run the 4.x RUU
Click to expand...
Click to collapse
Any other RUU suggested ?, i'm currently stuck with the bootloader, can i even normally boot up the device with the current ROM ?
SaHiLzZ said:
I think there is something wrong with that ruu. I have not been able to run the 4.x RUU
Click to expand...
Click to collapse
S7atem said:
what do you suggest i should do ?, i'm currently stuck with the bootloader, can i even normally boot up the device with the current ROM ?
Click to expand...
Click to collapse
It does actually work, just seems very sensitive to OS, USB ports, drivers, (possibly even locale), etc.
Recommend you use a plain vanilla Win7 PC with USB2 port.
Try extract Rom.zip & flash with fastboot
from HTC One
yatindroid said:
Try extract Rom.zip & flash with fastboot
from HTC One
Click to expand...
Click to collapse
where can i find the .ZIP of this ROM ?
S7atem said:
where can i find the .ZIP of this ROM ?
Click to expand...
Click to collapse
you can extract it from current ruu exe
Follow thread http://forum.xda-developers.com/showthread.php?t=2497614
from HTC One
I had this exact problem trying to go back from 5.11.401.10. When i extracted the rom.zip, fastboot came back with remote: 02 data length is too large.
I had already unlocked with HTCDev, flashed TWRP and s-off. i just wanted a stock ruu to go back to sense 5.5. In the end, i found TeHashX has created a twrp flash here: Link I flashed that without root, with radio and recovery and I'm back to stock. You'll probably need to be s-off for this but I'm not sure. I kept s-off and the unlocked bootloader.
Ps. You can remove the tampered with a rooted rom in the process.
Craig
craiglay said:
I had this exact problem trying to go back from 5.11.401.10. When i extracted the rom.zip, fastboot came back with remote: 02 data length is too large.
I had already unlocked with HTCDev, flashed TWRP and s-off. i just wanted a stock ruu to go back to sense 5.5. In the end, i found TeHashX has created a twrp flash here: Link I flashed that without root, with radio and recovery and I'm back to stock. You'll probably need to be s-off for this but I'm not sure. I kept s-off and the unlocked bootloader.
Ps. You can remove the tampered with a rooted rom in the process.
Craig
Click to expand...
Click to collapse
I have also been unable to use any of the 4.xx RUU... They worked once but none of them work now. Anyway I just wanted to say I also created a Guru Reset for the 5.21.502.2 (AT&T) here >> http://www.androidfilehost.com/?fid=23501681358545274 to go along with the files posted by @TeHashX
The only thing i can think of was the hboot prevents it now but i wasnt going to play with that. I personally went to 4.xx to get away from sense 6
Is there any other maybe older stock ROM i can try ?
I tried 1.29.401.x and that failed too. There was a note with the download saying you need to flash hboot 1.44 which i didn't bother with.
HTC One M7
SPRINT
S-ON
UNLOCKED
HBOOT 1.56
Radio 1.00.20.1108
OS 4.06.651.9
CM 11 20140504-SNAPSHOT
I need to restore my phone to a version of stock android (either an actual stock RUU or Android Revolution or whatever) so that I can get to the UICC option to turn off my SIM card (this setting is not available in CyanogenMod apparently).
Because I am on a newer firmware and because I am S-ON I do not seem to be able to install any of the (mostly older) RUUs I have found. Any suggestions? Is there an RUU for 4.06.651.9 that I am not seeing? Is there another way to roll back my OS to allow an older RUU to be installed? Another option altogether? A way to S-OFF while on CM?
Thanks for your help
pc010121 said:
HTC One M7
SPRINT
S-ON
UNLOCKED
HBOOT 1.56
Radio 1.00.20.1108
OS 4.06.651.9
CM 11 20140504-SNAPSHOT
I need to restore my phone to a version of stock android (either an actual stock RUU or Android Revolution or whatever) so that I can get to the UICC option to turn off my SIM card (this setting is not available in CyanogenMod apparently).
Because I am on a newer firmware and because I am S-ON I do not seem to be able to install any of the (mostly older) RUUs I have found. Any suggestions? Is there an RUU for 4.06.651.9 that I am not seeing? Is there another way to roll back my OS to allow an older RUU to be installed? Another option altogether? A way to S-OFF while on CM?
Thanks for your help
Click to expand...
Click to collapse
you can use this then take the OTA updates
http://www.htc1guru.com/dld/guru_reset_m7_sprint_3-04-651-2-zip/
Is this the 3.04.651.2 RUU? If so, I already have a copy, and when I attempt to run the ARUwizard I get Error 155. Most likely I am doing something wrong. I just assumed that since I am already on 4.06.651.9 that the problem was I couldn't install the older 3.04.651.2 version. Thoughts?
pc010121 said:
Is this the 3.04.651.2 RUU? If so, I already have a copy, and when I attempt to run the ARUwizard I get Error 155. Most likely I am doing something wrong. I just assumed that since I am already on 4.06.651.9 that the problem was I couldn't install the older 3.04.651.2 version. Thoughts?
Click to expand...
Click to collapse
This is exactly the same issue I'm experiencing. Well, now I'm even beyond this point... I am only able to boot the phone to the bootloader.
Edit: I am relocked as I am S-ON. I can't update firmware as the signature check fails. Flashing the 3.04.651.2 zip has a signature verify fail, as well.
Hope this helps
cheesesoda said:
This is exactly the same issue I'm experiencing. Well, now I'm even beyond this point... I am only able to boot the phone to the bootloader.
Click to expand...
Click to collapse
If you can still boot to bootloader your phone is fine. You should still have recovery (TWRP?) on your phone I assume. Regardless here are some steps that should help:
1. Figure out if you are S-ON (is found on the bootloader screen)
2. If you are S-ON, try Rumrunner to get S-OFF (just google it). This will allow you to install any RUU regardless of your firmware.
3. If Rumrunner doesn't work or you don't want to go to S-OFF then download the 4.06 RUU here http://forum.xda-developers.com/showthread.php?t=2658910
The problem is your firmware is ahead of the corresponding firmware of the 3.X release. As such you have to install from the newer RUU.
pc010121 said:
If you can still boot to bootloader your phone is fine. You should still have recovery (TWRP?) on your phone I assume. Regardless here are some steps that should help:
1. Figure out if you are S-ON (is found on the bootloader screen)
2. If you are S-ON, try Rumrunner to get S-OFF (just google it). This will allow you to install any RUU regardless of your firmware.
3. If Rumrunner doesn't work or you don't want to go to S-OFF then download the 4.06 RUU here http://forum.xda-developers.com/showthread.php?t=2658910
The problem is your firmware is ahead of the corresponding firmware of the 3.X release. As such you have to install from the newer RUU.
Click to expand...
Click to collapse
Actually, it seems that the phone is wiped; I can't boot my recovery. As a result, I can't really get S-OFF. I'll try the 4.06 RUU, but would it make a difference that it's .4 and not .9?
EDIT: I'm talking out of my ass right now. Long day, and this isn't helping. I am figuring it out; unlocked the bootloader, and now things seem to be functional. Well, except CM doesn't seem to want to boot any longer, but that shouldn't matter for long.
EDIT 2: How can I get S-OFF without enabling debugging? As of right now, CM is just in a boot loop.
Sim Unlock Sprint HTC One Max
I almost cannot believe how many different ROMs I've tried to flash after wiping out my original ROM.
Bootloader unlocked and rooted I managaged to relock the bootloader while trying to fastboot flash a stock ROM, which also failed.
Beleive it or not, I've have found a couple that will boot up with my Sprint HTC One Max . I was able to re-unlock the bootloader, flash a new rom and even recover user data I had backed up to my PC via adb backup.
All this for not, as I still cannot find a Sense ROM that will flash on my device and allow me to unnlock the Sim via Sim Unlock Helper.
Any help would be greatly appreciated!!!
TAMPERED
UNLOCKED
Sprint HTC One T6WL S-OFF
CID-SPCS_001
HBOOT-2.49.000
RADIO-1.48.50.0425
I recall reading somewhere that the Unlock Sim Helper should work on Sense 4.1.2 ROM. ????
So I accidentally deleted my os, rom, everything and for the past day or so I have been trying to go back to stock and I simply can't. I downloaded both an RUU.zip and exe and made sure the android-info.txt file had the same modelid and cidnum but it still fails. I will post images below of where my problem arises. I have s-off unlocked bootloader and was able to go from 1.56 hboot back to the 1.44 hboot no problem. In the second image I tried using an RUU, stock odexed rom, and then a firmware update but all failed . The errors occur when checking the info parsing or model id.
xXgOrAiZeXx said:
So I accidentally deleted my os, rom, everything and for the past day or so I have been trying to go back to stock and I simply can't. I downloaded both an RUU.zip and exe and made sure the android-info.txt file had the same modelid and cidnum but it still fails. I will post images below of where my problem arises. I have s-off unlocked bootloader and was able to go from 1.56 hboot back to the 1.44 hboot no problem. In the second image I tried using an RUU, stock odexed rom, and then a firmware update but all failed . The errors occur when checking the info parsing or model id.
Click to expand...
Click to collapse
first you can not use "fastboot flash zip" to flash odexed rom or any other roms, they must be flashed using a custom recovery. Only firmware pacakge and ruu can be flashed this way.
I also see that your version main is 1.10.605.10 which is for verizon phones MID: PN0731000 (yours is PN0713000) and cid VZW__001 (yours is T-MOB010). It looks like you have flashed a verizon firmware on your t-mobile phone which is not a good thing.... Dont know what you have previously done to this phone but it looks like you are trying to hard brick it
Dont understand neither why you are trying to flash the 6.09.401.5 odexed rom that doesnt match your phone info...
Here are the ruu for your phone (PN0713000 and T-MOB010):
http://www.htc1guru.com/dld/ruu_m7_...0-20_10-40-1150-04_release_324846_signed-exe/
http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/
http://www.htc1guru.com/dld/ruu-zip...157-04_release_336982_signed_2_decrypted-zip/
use one of them and see if your phone can recover (I hope that flashing the wrong firmware did not bricked it)
@alray Thanks for much for the info! Can't believe I was trying to flash the wrong ruu's :/. I will download the ones you provided and report back in few hours when I get home and hopefully my phone can still be saved.
I am attempting to convert my HTC One M7 (Telstra Australia) to Developer/Unlock edition but have hit a snag in trying to S-off my device. I now cannot get to install the developer ROM nor being able to go back to my stock ROM.
I have tried rumrunner and firewater without success having HBOOT 1.57 and having an eMMC CID 9001xx.
I am attenpting to run SunShine but on a custom rom but it doesn't run due to ro.debuggable=1.
I have attempted to revert back to my stock ROM using Clockwork recovery and Guru Reset Telstra WWE (Australia) ROM 2.24.841.1 - mid: PN0714000 cid: TELST001 but SunShine does not run on that kernel version.
I have attempted to do OTA updates to 4.4.3 but it fails to install once downloaded. Recovery was reloaded during the guru install. If I fastboot the recovery.img via USB from the Guru Reset ROM, the OTA update will install, but once complete "boot loops".
I have now installed a 4.4.3/Sense 6 InsertCoin ROM and have looked to modify the boot.img to set ro.debuggable=0 but haven't been successful in tearing apart the .img file and feel like im starting to get myself in a little deep. I was following a tutorial (cant post link as im a newbie! - 2nd response in google "How to Edit Android boot.img in Windows") using cygwin but keep getting "cannot execute binary file".
Any suggestions for either the stock restore or modified boot.img approach? Should i keep the Clockwork recovery when installing the Guru Reset? Is there something from stopping the OTA updates working?
Any help appreciated.
Hi guys,
I have soft bricked my device and currently the only way I see out of this is to flash RUU but then my version is way too high than the RUU available on the internet I've gone through. My current version is 4.20.707.7 but so far I've only found 1.29.707.3 the highest RUU version available on the internet.I have SuperCID but device is currently relocked and S-ON. I tried flashing other region's RUU which has higher version than mine believing the fact that I can flash it because I have SuperCID but I failed and received an error 155 which I searched and it means I'm using the wrong RUU. So I guess I can't flash other region's RUU and have to stick with my current region's.
Question:
1) Is it possible to flash the same version of RUU with the device?
2) Is it possible to flash other region's RUU if I have S-OFF? If yes, I only have access to fastboot and recovery and as far as I know, you only can S-OFF with a working homescreen, so how do I S-OFF while I only have access to fastboot and recovery?
If yes, does anyone have RUU for version 4.20.707.7 ( my current version ) or above?
If no, does anyone have RUU for version above 4.20.707.7?
Please help. Replies are much appreciated. Thank you And sorry for the tiny misleading information on the title. My current version is 4.20.707.7 not 4.20.707.6.
chaun1308 said:
Hi guys,
I have soft bricked my device and currently the only way I see out of this is to flash RUU but then my version is way too high than the RUU available on the internet I've gone through. My current version is 4.20.707.7 but so far I've only found 1.29.707.3 the highest RUU version available on the internet.I have SuperCID but device is currently relocked and S-ON. I tried flashing other region's RUU which has higher version than mine believing the fact that I can flash it because I have SuperCID but I failed and received an error 155 which I searched and it means I'm using the wrong RUU. So I guess I can't flash other region's RUU and have to stick with my current region's.
Question:
1) Is it possible to flash the same version of RUU with the device?
2) Is it possible to flash other region's RUU if I have S-OFF? If yes, I only have access to fastboot and recovery and as far as I know, you only can S-OFF with a working homescreen, so how do I S-OFF while I only have access to fastboot and recovery?
Click to expand...
Click to collapse
Yes, with s-on you can flash same or newer ruu version to your phone as long that it match your MID/CID + Firmware base (x.xx.707.x)
Yes you can flash other region RUU if s-off. You might need to change your CID and MID which can be done from fastboot (CID) and from recovery (MID). You can flash a close to stock rom like arhd to achieve s-off.
If yes, does anyone have RUU for version 4.20.707.7 ( my current version ) or above?
If no, does anyone have RUU for version above 4.20.707.7?
Click to expand...
Click to collapse
Many option for you.
You can restore the 4.20.707.7 version using the 4.20.707.7 stock reset rom (to be flashed in custom recovery)
You can flash the 7.21.707.5 ruu but in order to do that, your phone firmware must be at least 6.xx.707.x or 7.xx.707.x so it will requires to flash one of these firmware before the ruu.
Honestly I would simply flash the 4.20.707.7 reset rom, simple to do. When installing the rom, select "yes" to stock recovery and radio. Select "no" for root. when flashed, take all ota updates until you are on latest (7.21.707.5). From there you can flash a custom recovery and root if you want and returning back to stock from this point (if something else happen) will be as simple as flashing the 7.21.707.5 ruu.
alray said:
Yes, with s-on you can flash same or newer ruu version to your phone as long that it match your MID/CID + Firmware base (x.xx.707.x)
Yes you can flash other region RUU if s-off. You might need to change your CID and MID which can be done from fastboot (CID) and from recovery (MID). You can flash a close to stock rom like arhd to achieve s-off.
Many option for you.
You can restore the 4.20.707.7 version using the 4.20.707.7 stock reset rom (to be flashed in custom recovery)
You can flash the 7.21.707.5 ruu but in order to do that, your phone firmware must be at least 6.xx.707.x or 7.xx.707.x so it will requires to flash one of these firmware before the ruu.
Honestly I would simply flash the 4.20.707.7 reset rom, simple to do. When installing the rom, select "yes" to stock recovery and radio. Select "no" for root. when flashed, take all ota updates until you are on latest (7.21.707.5). From there you can flash a custom recovery and root if you want and returning back to stock from this point (if something else happen) will be as simple as flashing the 7.21.707.5 ruu.
Click to expand...
Click to collapse
@alray
Hey man, thanks for the useful information. I flashed the 4.20.707.7 reset ROM and did what you have told me but then the problem in the end is still the same as flashing other ROMs ( custom and stock ). The problem will be after unlocking the screen, green HTC logo appears and stays there for quite some time while dialer keeps crashing from time to time, and after few minutes, reboots by itself. This cycle will go on forever. Any advice ? Thanks again bro.
chaun1308 said:
@alray
Hey man, thanks for the useful information. I flashed the 4.20.707.7 reset ROM and did what you have told me but then the problem in the end is still the same as flashing other ROMs ( custom and stock ). The problem will be after unlocking the screen, green HTC logo appears and stays there for quite some time while dialer keeps crashing from time to time, and after few minutes, reboots by itself. This cycle will go on forever. Any advice ? Thanks again bro.
Click to expand...
Click to collapse
Looks like an hardware problem. Is your phone still having an IMEI # when doing "fastboot getvar all" ?