Trying to go back to stock. Failing... - Sprint HTC One (M7)

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

Related

[Q] RUU to downgrade 4.2.2 to 4.1.2?

Alright, so my friend has an AT&T One and it had 1.26.502.10 firmware (like mine), but he had some camera issues... He decided to do all the modding (root, s-off, etc...) and upgraded to 4.2.2 firmware 2.24. His camera issues continue, and he plans on returning to 4.1.2 with the available RUU that returns the phone to 1.26.502.12. He is s-off, supercid, unlocked bootloader, rooted, running twrp 2.6.0.1 and is on stock rooted 2.24.401.1 Rom. I thought of just using that RUU to return him to fully stock, but since it has all the mods I'm not really sure if I should take another approach or other steps. Please help me out here, I don't wanna brick his phone (even though he's taking it to be replaced). Thanks in advanced!
just download this and run it
https://support.htc.com/en-us/010-H..._Maintenance_Release_Instructions_|_5.30.2013
he couldnt run this with out the mods
Just run the RUU, as he's S-OFF there should be no issues
jerrycoffman45 said:
just download this and run it
https://support.htc.com/en-us/010-H..._Maintenance_Release_Instructions_|_5.30.2013
he couldnt run this with out the mods
Click to expand...
Click to collapse
Yes, that's the very file I have. Thanks! Will run it now! Thanks for the quick reply!
EddyOS said:
Just run the RUU, as he's S-OFF there should be no issues
Click to expand...
Click to collapse
Will do, thanks for ur quick reply!
There's the odd thread here and there saying if you're on the 1.54 HBOOT you need to downgrade to 1.44 before the RUU will work but try it first and see how you get on
EddyOS said:
There's the odd thread here and there saying if you're on the 1.54 HBOOT you need to downgrade to 1.44 before the RUU will work but try it first and see how you get on
Click to expand...
Click to collapse
Hmm, will I get a kind of error during the RUU process that might possibly brick the device or will it warn me before the RUU process starts? Can I and should I just flash the 1.44 RUU from fastboot before starting the RUU? The phone's on 2.24 right now with the modded 1.54 hboot (I know he first has to flash the original, but can/should he flash the 1.44 instead?).
EDIT: As far as I've read till now, the ones having errors were converted to Google Edition with GE hboot and all... I did read about 2 people (one with 2.17 and the other with 2.24 like my friend's phone) both on 1.54 hboot and it worked for both of em. I'm just gonna go ahead and flash the RUU on my friend's phone and hope for the best

[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] Bricked and RUU doesn't change anything

So I have bricked my phone and all I want is to go back to stock. I have tried flashing OMJ's 3.04.651.2 firmware through fastboot and it completes it successfully... so it says. When I proceed to reboot, I am yet again taken to the HTC screen, the screen then goes black, after a while the screen shows an HTC one with a red triangle in it. I am desperite, please help!
Relocked
S-on
HBOOT 1.55
Radio 1.00.20.0913_3
OS 3.04.651.2
MacSkizzle said:
So I have bricked my phone and all I want is to go back to stock. I have tried flashing OMJ's 3.04.651.2 firmware through fastboot and it completes it successfully... so it says. When I proceed to reboot, I am yet again taken to the HTC screen, the screen then goes black, after a while the screen shows an HTC one with a red triangle in it. I am desperite, please help!
Relocked
S-on
HBOOT 1.55
Radio 1.00.20.0913_3
OS 3.04.651.2
Click to expand...
Click to collapse
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
jab74101 said:
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can I get s-off? All I can access is my bootloader.
jab74101 said:
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I downloaded, extracted, and ran the correct soju but I get an error. It says to run rumrunner again and READ... I don't know what I did wrong. I did this with my phone in fastboot usb mode, is that right?
MacSkizzle said:
Can I get s-off? All I can access is my bootloader.
Click to expand...
Click to collapse
I'm pretty sure that's all you need. But I could be wrong.
TriBeard said:
I'm pretty sure that's all you need. But I could be wrong.
Click to expand...
Click to collapse
When I run the rumrunner program, I type 'Yes' twice then I get an error telling me to run rumrunner again and READ. What did I do wrong?
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
ZHoob2004 said:
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
Click to expand...
Click to collapse
I'll try this tonight when I get home from work, thanks for the input.
ZHoob2004 said:
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
Click to expand...
Click to collapse
This didn't do it either. PLEASE SOMEONE HELP ME
I don't know if you can flash OMJ's firmware if your bootloader is set to "Relocked". I could be wrong but I think what you need to do is unlock it again first and install a recovery. Then flash OMJ's stock firmware from recovery. From there you can probably do the S-OFF process and RUU back to stock.
You do need to be able to boot into your ROM for S-OFF to work, as you start the S-OFF process while the phone is booted up and running.
MacSkizzle said:
This didn't do it either. PLEASE SOMEONE HELP ME
Click to expand...
Click to collapse
Look HERE

[Q] RUU update: stuck @ 5% checking headers

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.

[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