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.
Related
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. ????
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
Hi!
I've already read like a million tutorials on how to do that, but I think they won't work on my phone. I have the international unlocked version that I later converted to Google Play Edition. So now I have a GPE bootloader, TWRP recovery and root. Below I include a picture of my bootloader. My hboot is 1.54 so I can't use revone to relock the bootloader and make it s-on again, right? I really need you help guys, what should I do?
Edit: I downloaded 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 " - will it work on my phone? I'm not doing anything yet, because I don't want to brick it.
Edit 2: I downgraded my hboot to 1.44 and my phone still hasn't blown up so I guess that's a good sign.
seklerek said:
Hi!
I've already read like a million tutorials on how to do that, but I think they won't work on my phone. I have the international unlocked version that I later converted to Google Play Edition. So now I have a GPE bootloader, TWRP recovery and root. Below I include a picture of my bootloader. My hboot is 1.54 so I can't use revone to relock the bootloader and make it s-on again, right? I really need you help guys, what should I do?
Edit: I downloaded 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 " - will it work on my phone? I'm not doing anything yet, because I don't want to brick it.
Edit 2: I downgraded my hboot to 1.44 and my phone still hasn't blown up so I guess that's a good sign.
Click to expand...
Click to collapse
if your phone was on a x.xx.401.x version originally, then use the 1.28.401.7 ruu, then remove *tampered* and *relocked* banner using guru bootloader reset tool by booting a custom recovery using "fastboot boot recovery.img". You can then turn back s-on and send your phone. Everything is described in nkk71's guide linked in my signature.
Don't forget to set back your original CID and MID if you have changed them to convert your phone to GPE before running the ruu
Can't I use the RUU I downloaded? It's 4.19.401.9. I'm not sure what the original number was, but according to the download page it's compatible with my MID and CID.
seklerek said:
Can't I use the RUU I downloaded? It's 4.19.401.9. I'm not sure what the original number was, but according to the download page it's compatible with my MID and CID.
Click to expand...
Click to collapse
not for warranty purpose cause you must be on hboot 1.44 or 1.54 to remove the "tampered" and "relocked" flags form bootloader.
4.x.401.x ruu is hboot 1.55
1.x.401.x ruu is hboot 1.44
@alray I didn't know RUUs could also update hboot. Thank you for the information. So the 1.x.401.x files are Jelly Bean RUUs, but I'll be able to update to kitkat over the air when I'm done restoring to stock?
seklerek said:
@alray I didn't know RUUs could also update hboot. Thank you for the information. So the 1.x.401.x files are Jelly Bean RUUs, but I'll be able to update to kitkat over the air when I'm done restoring to stock?
Click to expand...
Click to collapse
Ruu update everything, firmware and software.
Yes you'll be able to take ota update after but don't update before you have removed tampered and relocked from the bootloader. Follow instructions in the guide.
@alray Alright, thank you very much. Will I be able to return to a full GPE after I receive it back from the service?
seklerek said:
@alray Alright, thank you very much. Will I be able to return to a full GPE after I receive it back from the service?
Click to expand...
Click to collapse
If you are able to achieve s-off again yes.
They will probably update your phone so it might be more difficult to achieve when it comes back.
@alray I'm having a problem with the guide you linked. It says to enter CWM recovery and use adb commands to remove flags and lock the bootloader, but I can't use any adb commands inside CWM. How do I fix this?
Edit: OK, I fixed this by using TWRP instead of CWM. Can I leave S-OFF and update the device normally, then restore it to GPE after I receive it back from service?
seklerek said:
@alray I'm having a problem with the guide you linked. It says to enter CWM recovery and use adb commands to remove flags and lock the bootloader, but I can't use any adb commands inside CWM. How do I fix this?
Edit: OK, I fixed this by using TWRP instead of CWM. Can I leave S-OFF and update the device normally, then restore it to GPE after I receive it back from service?
Click to expand...
Click to collapse
do not update the phone now, just turn back s-on and send it for repair. Its easier to get back s-off on lower version so better not to take any ota, however they will maybe update your phone at the service center (hopefully not).
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.
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" ?