Ruu for 2.24.401.1 - One (M7) Q&A, Help & Troubleshooting

hi there
i cant't lock my m7 back after rooted
i upgrade the device to cyanogenmod 10.2 4.3 and i found a problem with camera lens which is factory fault
want to lock my decice again by using ruu to return the warranty back but unfortunetly ive got signature verify fail
then i tried to flash stock same either
the ruu file is
OTA_M7_UL_JB_50_S_HTC_Europe_2.24.401.1-1.29.401.12_P2_release_324936_signedma8j1sa3e2o09s35.zip
build number is 2.24.401.1
htc_j15 with baseband version 4A.17.3250.14 s-on
any help?

That's an OTA file, not an RUU, so it can't be flashed without first being on 1.29.401.12 and you also need to be S-OFF. If you ARE S-OFF already, just flash the 1.28.401.7 RUU and you'll then get the OTAs to get back to the latest stock build (2.24.401.8)

EddyOS said:
That's an OTA file, not an RUU, so it can't be flashed without first being on 1.29.401.12 and you also need to be S-OFF. If you ARE S-OFF already, just flash the 1.28.401.7 RUU and you'll then get the OTAs to get back to the latest stock build (2.24.401.8)
Click to expand...
Click to collapse
Im not s-off
Is there a way to get Ruu?
Why the device should be on 1.29.401.12 and im on 2.24.401.1 right now?
Sorry im beginner

RUUs leak from people with contacts with HTC, there hasn't been a leak since 1.28.401.7

EddyOS said:
RUUs leak from people with contacts with HTC, there hasn't been a leak since 1.28.401.7
Click to expand...
Click to collapse
Is this means that i have to wait till ruu out?

Can i use this ruu to go back to stock using guru reset
GuruReset Zip Files Posted – Stock ROM 2.24.401.1 with Aroma Installer

murtadha50 said:
Can i use this ruu to go back to stock using guru reset
GuruReset Zip Files Posted – Stock ROM 2.24.401.1 with Aroma Installer
Click to expand...
Click to collapse
you can S-OFF hboot 1.54 with new method Rumrunner
http://forum.xda-developers.com/showthread.php?t=2487888

You should do these steps to get back fully stock:
1 - Go S-OFF with rumrunner (before do this, suggest to install a stock odexed rom)
2 - Run an RUU exe file like : 1.28.401.7 to downgrade hboot and remove TAMPERED in boot
3 - Then you can use revone to switch to LOCKED and remove revone file
4 - Now you can go S-ON with a single command from fastboot
5 - Now you have a fully stocked device

komsboy_more said:
You should do these steps to get back fully stock:
1 - Go S-OFF with rumrunner (before do this, suggest to install a stock odexed rom)
2 - Run an RUU exe file like : 1.28.401.7 to downgrade hboot and remove TAMPERED in boot
3 - Then you can use revone to switch to LOCKED and remove revone file
4 - Now you can go S-ON with a single command from fastboot
5 - Now you have a fully stocked device
Click to expand...
Click to collapse
good advice i will try sure
thanks

Related

[Q] Get completely back to stock for repair

Hi,
i need to get back to stock after i did
- S-OFF via revone (without unlocking via htcdev)
- Flash TWRP recovery
- Did a NANDROID of the stock rom
- Install ViperOne ROM
Originalbuild:
1.29.401.16 CL177101 release-keys
I think there are 2 options:
1) Run a RUU
2) Restore stock rom via RWRP and flash original recovery, then S-ON via revone
Is this right? What shall i do best?
And where do i get the stock recovery for 2)
And the 1.29 RUU WWE Europe is not available, can i just run the way older one and then OTA to 1.29?
Thank you very much!
Regards
Daniel
Backup data you want to keep
Download the 1.28.401.7 RUU
Flash it
S-ON
Send to HTC
EddyOS said:
Backup data you want to keep
Download the 1.28.401.7 RUU
Flash it
S-ON
Send to HTC
Click to expand...
Click to collapse
You mean this one
"RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe"
?
Is it possible to flash an older RUU when a newer version is installed at the moment?
S-ON is done with the RUU? Or do i need to do this seperately?
Then just OTA to get 1.29 (which they delivered)?
Dacoco said:
You mean this one
"RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe"
?
Is it possible to flash an older RUU when a newer version is installed at the moment?
S-ON is done with the RUU? Or do i need to do this seperately?
Then just OTA to get 1.29 (which they delivered)?
Click to expand...
Click to collapse
Yep, that one. With S-OFF you can flash an older RUU as it doesn't check the current mainver on the device. Once you have flashed the RUU and confirmed it's working you can then set the CID back to HTC__001 (if you changed it to Super CID) and then back to S-ON and you're good to go!
EddyOS said:
Yep, that one. With S-OFF you can flash an older RUU as it doesn't check the current mainver on the device. Once you have flashed the RUU and confirmed it's working you can then set the CID back to HTC__001 (if you changed it to Super CID) and then back to S-ON and you're good to go!
Click to expand...
Click to collapse
Great! Thank you very much. I need to wait for a repsonse from htc, then i'll try it.
dont forget to remove tampered and lock the bootloader with revone and also remove traces of revone
Gigalabz said:
dont forget to remove tampered and lock the bootloader with revone and also remove traces of revone
Click to expand...
Click to collapse
Tampered should not appear when i did not unlock via htcdev i thought?
Where do i find the traces of revone?
Hi,
here is my report of getting back to stock:
1) Flashed latest available RUU
2) Updated via OTA but did not get the absolute latest software (which was on the device before)
3) pushed revone to the device and locked it again
4) wrote secureflag 3 for s-on
5) deleted revone from /data/local/tmp (!!!)
6) flashed the latest OTA via fastboot manually (http://forum.xda-developers.com/showthread.php?p=42924796)
Done
Worked like a charm
Thanks guys! Thanks revone Team!

can i downgrade with a nandroid using TWRP/CWM

basically trying to get s-off on my device i am on hboot 1.54 as i recently updated to sense 4.2.2
CID: ORANG001
MID: PN0710000
version main: 2.24.61.1
now i have rooted with TWRP & wondering if i can use this nandroid to downgrade:
M7 CWM Nandroid Backup / CID ORANG001 / 1.28.61.7 (Orange UK - Thanks to Azzabear)
http://click.xda-developers.com/api... / 1.28.61.7&jsonp=vglnk_jsonp_13761274174228
would it work & would it downgrade the hboot?
Nandroid won't downgrade hboot.
Sent from my HTC One using xda premium
could i use an older RUU to replace hboot?
zFayZz said:
could i use an older RUU to replace hboot?
Click to expand...
Click to collapse
Sorry, I've no experience with RUUs - never used one. I would guess it would but since you're S-ON you obviously can't superCID, so you would need to find the proper RUU for your CID.
There is no known way to downgrade an hboot on an s-on device.
gunnyman said:
There is no known way to downgrade an hboot on an s-on device.
Click to expand...
Click to collapse
Just wondering for my own interest, gunny.. what does an RUU restore? I thought it was stock hboot, firmware, rom, recovery, etc. (everything basically). Or is it just that it can't downgrade even with an RUU if you are S-ON and would need to wait on a new RUU being released? Unless you're S-off and can superCID, then your can run any RUU - and that would downgrade *everything*..
cheers
redbull123 said:
Just wondering for my own interest, gunny.. what does an RUU restore? I thought it was stock hboot, firmware, rom, recovery, etc. (everything basically). Or is it just that it can't downgrade even with an RUU if you are S-ON and would need to wait on a new RUU being released? Unless you're S-off and can superCID, then your can run any RUU - and that would downgrade *everything*..
cheers
Click to expand...
Click to collapse
The RUU is as far as I know a collection of all of the partition images for the phone.
Even with S-off it is not possible to downgrade an HBoot without flashing that HBoot separately. IOW if you are on a 1.54 firmware, in order to flash an RUU containing 1.44 Hboot you have to flash the 1.44 Hboot by itself or else the RUU will fail.
SuperCID (11111111) will pass the CID check
It is my understanding that in the past, S-off meant you could downgrade with just the RUU but that doesn't seem to be the case anymore.
The RUU install checks a few things
MID and CID
HBoot must be the same or greater version number
if these checks fail, the RUU won't flash even with S-off
The beauty of S-off is, we can flash these things manually without the RUU bypassing the checks.
You can simply use the DD command in a root shell and copy the partitions to the phone, but this is dangerous, because if you put a partition in the wrong location, BRICK.
My knowledge here is not as advanced as many here, so someone please correct me if I got any of this wrong.
.

[Q] Just want to confirm if I can flash RUU when I"m S-OFF and CID11111111

All,
I have the Dev Edition with S-OFF and CID111111 running ARHD 13.3. With the latest update to the Dev Edition to 4.3, can I just flash the RUU for the latest of the Dev Edition? Will it work with TWRP custom recovery?
Thanks for any info.
Emh, the RUU isn't a zip, but an exe that you have to flash with the pc...
However, you can flash it
You can flash an RUU when S-OFF with Super CID, I've done it a number of times
The RUU is a complete update so it will overwrite the custom recovery anyway
Awesome guys....with that being said, I have a few more question. Since I'm S-Off and Super CID, you said I can flash any RUU, but it will wipe the custom recovery. That is fine, but when I want to flash a ROM in the future, I will have to reflash a new recovery correct? Will this mess with my HBOOT? I'm on 1.55 right now.
Also, I'm on the http://forum.xda-developers.com/showthread.php?p=39588860 looking at the collecdtion of RUU's...do I flash the ZIP, EXE or the Decrypted RUU's?
Again, thanks for your replies!
Download the RUU from HTCDev directly so you know you've got the right file, then flash it with the phone connected in fastboot. It will downgrade the HBOOT and put the phone back to 1.29.1540.16 and be just like it was out the box (except you'll still be S-OFF with Super CID). You can then get the OTA to .17 and then the OTA to Android 4.3...after that, you can flash a custom recovery and do what you want (but I'd take a nandorid first of course)
EDDYOS,
Thanks for all your info!! I will do exactly that!
One last question, I promise...since I am on S-OFF I should not be worried that flashing the RUU and downgrading to HBOOT 1.54 and not be able to achieve SOFF again? Cause isn't 1.54 having issues with SOFF? Or does that not matter to me since I have the Dev Editoin?
Again, thanks for all your advice.
You'll stay S-OFF so it's irrelevant...the only way you'll go S-ON is if YOU make it. RUUs/OTAs don't touch it
Example:
I'm currently on 2.24.401.8, HBOOT 1.54 and have S-OFF (as I did it when I could ages ago). I recently went back to 1.28.401.7 using the RUU and was still S-OFF. I then got the 4 OTAs to get back to 2.24.401.8 and I'm still S-OFF
EddyOS said:
You'll stay S-OFF so it's irrelevant...the only way you'll go S-ON is if YOU make it. RUUs/OTAs don't touch it
Example:
I'm currently on 2.24.401.8, HBOOT 1.54 and have S-OFF (as I did it when I could ages ago). I recently went back to 1.28.401.7 using the RUU and was still S-OFF. I then got the 4 OTAs to get back to 2.24.401.8 and I'm still S-OFF
Click to expand...
Click to collapse
EddyOS...
Thanks alot! Gotcha!

[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] I need help with restoring my One to stock for warranty purposes.

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).

Categories

Resources