Problems Downgrading From 4.06.651.9 - Sprint HTC One (M7)

OK....I am on 4.06.651.9 --- S-off --- 1.56 H-boot ---CID SPCS_001 --- Unlocked. I've been trying to completely downgrade and tried using RUU 1_29_651_10, both zip and exe and I get the same notification ---"FAILED"--- Device is recognized and I've tried it with both "locked" and "unlocked" and with the Sprint CID and with Super Cid. I feel like I'm out of options. Anyone have a sure-fire fix for this?

devo3d said:
OK....I am on 4.06.651.9 --- S-off --- 1.56 H-boot ---CID SPCS_001 --- Unlocked. I've been trying to completely downgrade and tried using RUU 1_29_651_10, both zip and exe and I get the same notification ---"FAILED"--- Device is recognized and I've tried it with both "locked" and "unlocked" and with the Sprint CID and with Super Cid. I feel like I'm out of options. Anyone have a sure-fire fix for this?
Click to expand...
Click to collapse
Follow this guide to get back to JB then use the 1.29 RUU to accomplish what you are trying to do.
Something changed with hboot 1.56...for some reason it won't allow you to run an older RUU even though you are s-off

BD619 said:
Follow this guide to get back to JB then use the 1.29 RUU to accomplish what you are trying to do.
Something changed with hboot 1.56...for some reason it won't allow you to run an older RUU even though you are s-off
Click to expand...
Click to collapse
THANK YOU!! I'll definitely try it... I'll post my results :fingers-crossed:

Well crap....it didn't work. I got the "error 155". Do I need to downgrade the h-boot to 1.55 or should it have worked for 1.56? Thats the only reason I can see why it didn't work. Also, I downloaded and ran the ".exe" file at the top of the page, should I have used the modified firmware ".zip" ?
EDIT: Oh man...I feel so dumb...I somehow missed the part about downloading the "decrypted" file....I just saw it saying "Developers" and didn't think that was the one....I'll try that one tomorrow..

devo3d said:
Well crap....it didn't work. I got the "error 155". Do I need to downgrade the h-boot to 1.55 or should it have worked for 1.56? Thats the only reason I can see why it didn't work. Also, I downloaded and ran the ".exe" file at the top of the page, should I have used the modified firmware ".zip" ?
EDIT: Oh man...I feel so dumb...I somehow missed the part about downloading the "decrypted" file....I just saw it saying "Developers" and didn't think that was the one....I'll try that one tomorrow..
Click to expand...
Click to collapse
I finally got it done right I wasn't able to flash the second RUU like the first (through Fastboot) so I had to run the ".exe" file and it completed.
Thanks for all your help :victory:

devo3d said:
I finally got it done right I wasn't able to flash the second RUU like the first (through Fastboot) so I had to run the ".exe" file and it completed.
Thanks for all your help :victory:
Click to expand...
Click to collapse
may I ask why you were trying to downgrade?

Related

RUU

Hi guys, i just want to be on the safe side before doing anything like S-off, so i wonder how do i find which RUU is made for my phone model ? i have tried searching but didn't get anywhere.
http://forum.xda-developers.com/showthread.php?p=39588860
No offense but you didn't look very hard. Its in a sticky in the dev thread
Once you s-off (which is ridiculously easy for this device) you can use any RUU. Good luck and enjoy
Sent from my One using Tapatalk 2
Anicane said:
Hi guys, i just want to be on the safe side before doing anything like S-off, so i wonder how do i find which RUU is made for my phone model ? i have tried searching but didn't get anywhere.
Click to expand...
Click to collapse
You haven't said what OS you're on or what Hboot you have, S-Off might not even be an option, nor might an RUU if you are on a 2.24 base with Hboot 1.54 ... A little more info would help to make sure you are given the best, most accurate advice.
AllAboutTheCore said:
You haven't said what OS you're on or what Hboot you have, S-Off might not even be an option, nor might an RUU if you are on a 2.24 base with Hboot 1.54 ... A little more info would help to make sure you are given the best, most accurate advice.
Click to expand...
Click to collapse
I haven't updated my phone to this new Hboot 1.54, i am still on with the old one, i have read not to update if i want S-Off. The reason i want this is because if suddenly i had to return my phone to a service or something, i don't want to void my warranty. If i am not wrong when you S-Off, you can reverse it also.
Anicane said:
I haven't updated my phone to this new Hboot 1.54, i am still on with the old one, i have read not to update if i want S-Off. The reason i want this is because if suddenly i had to return my phone to a service or something, i don't want to void my warranty. If i am not wrong when you S-Off, you can reverse it also.
Click to expand...
Click to collapse
Cool, yes, you are correct, S-Off can be reverted ... It's also worth noting that if you S-Off now, you'd be able to upgrade to Hboot 1.54 and still maintain S-Off. The problem lies with those, like me, who are on the 1.54 Hboot but haven't gone S-Off ... We're now stuck until a solution is available, although I didn't want to go S-Off so it's not really a problem.
If you go S-Off btw you can flash any RUU from any region and change your Cid/Mid, although I can't help you on the whole RUU when S-Off process as I've never run one, nor been S-Off as I previously mentioned lol.
I still can't find which RUU is for my phone, is there anyway to find ? is it via CID or any other way ?
What software build are you on at the moment? So to Settings>About phone>Software information and post the version, e.g. 2.24.401.8
EddyOS said:
What software build are you on at the moment? So to Settings>About phone>Software information and post the version, e.g. 2.24.401.8
Click to expand...
Click to collapse
It is 1.29.401.16
Anicane said:
It is 1.29.401.16
Click to expand...
Click to collapse
There is an RUU ZIP for that somewhere but I can't find it. I'm sure someone has a link to it somewhere!
EddyOS said:
There is an RUU ZIP for that somewhere but I can't find it. I'm sure someone has a link to it somewhere!
Click to expand...
Click to collapse
I didn't find an actuall 1.29.401.16 RUU, but there is some zips, which i am kinda not interested. But i found 1.29.401.12 OTA's . So i want to know if it is possible to flash the 1.29.401.12 and let the Htc one update itself ? and than do an S-on if i wanted to return it to a service ?
Anicane said:
I didn't find an actuall 1.29.401.16 RUU, but there is some zips, which i am kinda not interested. But i found 1.29.401.12 OTA's . So i want to know if it is possible to flash the 1.29.401.12 and let the Htc one update itself ? and than do an S-on if i wanted to return it to a service ?
Click to expand...
Click to collapse
The 1.29.401.16 ZIP is the RUU but in ZIP format so it's the same thing. Basically in the RUU.exe there is a ZIP called ROM.zip - this is what is the actual ROM and is flashed via the RUU in fastboot mdoe. It's fine and it's the one you want as there is nothing else available for your phone
EddyOS said:
The 1.29.401.16 ZIP is the RUU but in ZIP format so it's the same thing. Basically in the RUU.exe there is a ZIP called ROM.zip - this is what is the actual ROM and is flashed via the RUU in fastboot mdoe. It's fine and it's the one you want as there is nothing else available for your phone
Click to expand...
Click to collapse
Well, i am thinking of a scenario which i don't know is possible or not, so here it goes. Since i want to be on the safe side, how about i take a nandorid back of the stock, and than if i wanted to returen to stock, simply flash an RUU like 1.29.401.16, and than simply recover the nandroid backup over it, and update if i wanted to ? Is it possible ?
The only problem is that i don't know how to remove the custom recovery when it restore the nandorid back, and update it.

[Q] 4.3 Sprint RUU

Hi, I was wondering if there was going to be an RUU for 4.03.651.2 firmware. I tried to take the update with an outdated version of TWRP, and I would like to go back to stock and reroot. I have tried and failed to gain S-Off with Revone and moonshine. I am unsure of what to do. My phone is not recognized by ADB in recovery, so I cannot use the S-Off workaround to flash an old RUU. Any suggestions/responses are appreciated.
Thanks,
Vobeyo
Vobeyo said:
Hi, I was wondering if there was going to be an RUU for 4.03.651.2 firmware. I tried to take the update with an outdated version of TWRP, and I would like to go back to stock and reroot. I have tried and failed to gain S-Off with Revone and moonshine. I am unsure of what to do. My phone is not recognized by ADB in recovery, so I cannot use the S-Off workaround to flash an old RUU. Any suggestions/responses are appreciated.
Thanks,
Vobeyo
Click to expand...
Click to collapse
there should be in the future but we still dont even have a 1.31 RUU yet.. only 1.29
P.Mobile said:
there should be in the future but we still dont even have a 1.31 RUU yet.. only 1.29
Click to expand...
Click to collapse
Hmm... I just assumed that there wouldn't be an RUU for 1.31. Do you know of any way to gain S-Off so that I can flash the 1.29 RUU?
RUU
This can be very frustrating, I know.
I used Moonshine to achieve S-OFF, yesterday. Reason was because I managed to delete almost everything, I still don't know exactly what happened. However, if I remember correctly, you need S-On in order to run a stock RUU. There are several threads that pretty much will walk you thru the steps needed to flash the RUU. I was on them yesterday.
Good luck.
retiredtrebor said:
This can be very frustrating, I know.
I used Moonshine to achieve S-OFF, yesterday. Reason was because I managed to delete almost everything, I still don't know exactly what happened. However, if I remember correctly, you need S-On in order to run a stock RUU. There are several threads that pretty much will walk you thru the steps needed to flash the RUU. I was on them yesterday.
Good luck.
Click to expand...
Click to collapse
You don't need S-Off or S-On to run the RUU, but the bootloader has to be locked (or relocked). Believe that I read that HTC was going to not release RUUs any more because they didn't want others to tear them apart, etc. But don't quote me on that one...
From my understanding, S-Off is required to flash an RUU for a firmware version that does not match the version you are currently on. Could you please refer me to one of these threads? I would appreciate it very much.
Vobeyo said:
From my understanding, S-Off is required to flash an RUU for a firmware version that does not match the version you are currently on. Could you please refer me to one of these threads? I would appreciate it very much.
Click to expand...
Click to collapse
I've also heard the same however how can I gain S-Off without mounting the internal storage? Or ADB? I can't get either to work.
Sirricharic said:
I've also heard the same however how can I gain S-Off without mounting the internal storage? Or ADB? I can't get either to work.
Click to expand...
Click to collapse
I believe that if you have a custom recovery installed, you can use the workaround by accessing the terminal from the recovery, type the command, and then lock the bootloader. I am not completely sure on that, though.
If your on 4.3 there is no RUU and no s-off exploit at this time. This is why it's always recommended to root/s-off before you update.
Sent from my HTCONE using xda app-developers app
Vobeyo said:
From my understanding, S-Off is required to flash an RUU for a firmware version that does not match the version you are currently on. Could you please refer me to one of these threads? I would appreciate it very much.
Click to expand...
Click to collapse
Here's one of the links: http://forum.xda-developers.com/showthread.php?t=2251800
Check in the Sprint HTC One Forums, the first two sub-forums both have info you're looking for.
retiredtrebor said:
Here's one of the links: http://forum.xda-developers.com/showthread.php?t=2251800
Check in the Sprint HTC One Forums, the first two sub-forums both have info you're looking for.
Click to expand...
Click to collapse
If you updated your phone to latest sprint 4.3 that's it you cannot instal RUU any more
s-on s-off not gonna help you
you can download naked drivers for htc one http://dl.xda-developers.com/attachd...river_0.72.zip but first delate/uninstal all htc/syn drivers
and jus push any 4.3 rooted rom to your phone and install g-luck
Don't know if this will help you or not, just stumbled across it a couple of minutes ago.
http://forum.xda-developers.com/showthread.php?t=2236418
retiredtrebor said:
Here's one of the links: http://forum.xda-developers.com/showthread.php?t=2251800
Check in the Sprint HTC One Forums, the first two sub-forums both have info you're looking for.
Click to expand...
Click to collapse
Thanks. I will look into this as soon as time permits.

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

Kindly Guide Me

I have one HTC One M8 Sprint (Non HK version). presently it has android 4.4, S-ON, sim unlocked, rooted, twrp.
i want to install lolipop rom on it. kindly guide me how to proceed with all requirements step by step. and which lolipop rom is good for daily use.
thanks
We can't. Sunshine doesn't seem to work anymore to gain s-off do we are screwed until someone that doesn't support a paywall figures out how to be able to gain s-off so we can flash the RUU.
I hate this damn phone and I wish I knew how to develop myself.
ipetloudog said:
We can't. Sunshine doesn't seem to work anymore to gain s-off do we are screwed until someone that doesn't support a paywall figures out how to be able to gain s-off so we can flash the RUU.
I hate this damn phone and I wish I knew how to develop myself.
Click to expand...
Click to collapse
FYI you don't need to be s-off to run an RUU
Tell that to my phone after I tried 3 different methods and it still will not flash
ipetloudog said:
Tell that to my phone after I tried 3 different methods and it still will not flash
Click to expand...
Click to collapse
Our phones don't come s-off so why would they need to be s-off to RUU?
Beats me. I tried the external sd method. Fastboot method. Changed my CID. nothing works.
ipetloudog said:
Tell that to my phone after I tried 3 different methods and it still will not flash
Click to expand...
Click to collapse
Plenty of other people have successfully RUU'd their phones while S-on. It does require an extra step but it can be done. Also, as far as S-off with Sunshine, I believe the latest version (3.0) is compatible with Lollipop.
To the OP: Hit the second link in my sig. Scroll down to the RUU section and take a read. A link to OMJ's RUU thread can be found at the bottom of the first post of my thread. Download the latest applicable RUU (4.25.651.14 for NON-HK or 4.25.654.14 for the HK version). Follow my instructions in my thread to run the RUU on your device.
ipetloudog said:
Beats me. I tried the external sd method. Fastboot method. Changed my CID. nothing works.
Click to expand...
Click to collapse
External sd method = needs s-off so won't work for s-on users.
Fastboot method = most RUU's are exe files so most likely won't work via fastboot method.
Changed my CID = cannot be done unless you are s-off.
BD619 said:
FYI you don't need to be s-off to run an RUU
Click to expand...
Click to collapse
But I thought if you are s-on you cannot go backwards to an older hboot version. I thought you had to be s-off if you wanted to go backwards?
-Apollo- said:
But I thought if you are s-on you cannot go backwards to an older hboot version. I thought you had to be s-off if you wanted to go backwards?
Click to expand...
Click to collapse
You do have to be s-off to go backwards, but just to RUU s-off is not required
Are you by chance using a computer, not to be a ****, but like what are some of the results and we can try to help you with using the RUU... Sometimes they are touchy and need to be done in an exact way...and patience is key

[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