Database Develop

Ruu for 2.24.401.1

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

HTC One T-MOB101 how to revert it back to stock?

I have a T-MOB101 (Germany device HTC One), and i would like to revert it back to stock and sell it.
Read all the guides here at XDA, but couldn't achieve it.
My device now is:
HBOOT 1.54.00
S-Off with SuperCID 11111111
Unlocked bootloader
ARHD 13.4 rom
There isn't any RUU for T-MOB101. I found a CWM stock Nandroid backup but for some reason CWM can't install it.
I've installed the odexed 2.24.401.1 stock rom, reverted the CID back to T-MOB101, locked the Bootloader but now it says RELOCKED instead of LOCKED. And couldn't make it S-On maybe because of the HBOOT 1.54.00?
Please, help me, i would like to sell the device and the future owner don't have any issues with the warranty.

So, unlock your bootloader, go here, download the 1.44 hboot and flash it with the guide.
After, use the revone tool to go locked and s-on

Guich said:
So, unlock your bootloader, go here, download the 1.44 hboot and flash it with the guide.
After, use the revone tool to go locked and s-on
Click to expand...
Click to collapse
Thanks for the reply Guich.
I'm kinda lost in the above thread.
1) Which Base Firmware should i download for T-MOB101 German device? I would like for it to have automatic updates for the future.
2) After that i will have to download the HBOOT 1.44.0000 Original unmodified, right?
3) In which order should i flash them? It's the same method for both Base Firmware and HBOOT?
4) Lastly, my bootloader now is unlocked with the HTC's method. How i can use the Revone to go Locked and S-On? Also, when should i change the CID to T-MOB101 from SuperCID 11111111?
Excuse me for all these questions, after almost 8 hours in front of the PC with no luck my head's gonna explode..
Thanks a bunch,
Bill

bill_viper said:
Thanks for the reply Guich.
I'm kinda lost in the above thread.
1) Which Base Firmware should i download for T-MOB101 German device? I would like for it to have automatic updates for the future.
2) After that i will have to download the HBOOT 1.44.0000 Original unmodified, right?
3) In which order should i flash them? It's the same method for both Base Firmware and HBOOT?
4) Lastly, my bootloader now is unlocked with the HTC's method. How i can use the Revone to go Locked and S-On? Also, when should i change the CID to T-MOB101 from SuperCID 11111111?
Excuse me for all these questions, after almost 8 hours in front of the PC with no luck my head's gonna explode..
Thanks a bunch,
Bill
Click to expand...
Click to collapse
1) I will advise you to transform your T-MOB phone into an unbranded phone.
So, donwload the 1.29 firmware umodified and flash this.
2) Yupp, 1.44 hboot and go s-on and locked
3) Use the guide, i will advice firmware and after hboot.
4) Yup, with 1.44 hboot you can use the revone tool for go to LOCKED and not RELOCKED and s-on
But, before go to s-on, change the cid into HTC__001.
5) If you're tired do this tomoz
p.s. If you need more help, you can contact me in pm

[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] return to stock after rum runner

I am TMOB101 (the german t-mobile) i have successfully s-offed using rum runner.
There is no RUU for my phone as far as i know..
Is there a way to s-on again?
does rum runner backup my original hboot, so i can restore it to go back s-on?

Nomader0 said:
I am TMOB101 (the german t-mobile) i have successfully s-offed using rum runner.
There is no RUU for my phone as far as i know..
Is there a way to s-on again?
does rum runner backup my original hboot, so i can restore it to go back s-on?
Click to expand...
Click to collapse
You can flash the GuruReset ROM for your version: http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/
Make sure you choose to flash stock recovery and boot etc.
When all back to fully stock you are then safe to s-on again by issuing the following command: fastboot oem writesecureflag 3
Hope that comes in useful

Nomader0 said:
I am TMOB101 (the german t-mobile) i have successfully s-offed using rum runner.
There is no RUU for my phone as far as i know..
Is there a way to s-on again?
does rum runner backup my original hboot, so i can restore it to go back s-on?
Click to expand...
Click to collapse
Why do you need to s-on? And with s-off you can flash any RUU that you want. To s-on again, the command is "fastboot oem writesecureflag 3", but you need to be COMPLETELY stock before you do this, or you'll have a hard brick.
Sent from my iPod touch using Tapatalk

thank you for your answers.. I want to s-on to send back for warranty issues (purple tint).
I just want to understand how it works..
Rum runner installed an unsecured hboot. correct?
in order to s-off i need to go back to stock hboot first? people install RUU so they can install 1)stock rom, 2)stock radio, 3) stock recovery 4)stock hboot correct?
the Guru Reset rom just installs rom, recovery and radio (no hboot?)
can i just install any RUU and s-on? i thought i needed the one matching my phone

ok i found this http://www.htc1guru.com/guides/return-stock-guide/ and answered most of my questions.. except one:
As i said there is no RUU for me.. i will use a nandroid to restore most of the stuff. BUT there will be a mismatch between my stock Rom installed and the firmware (what is written in bootloader screen OS:XXXXXXX) How can i fix that?
can i just install the TMOB101 firmware from here http://android-revolution-hd.blogspot.gr/p/android-revolution-hd-mirror-site-var.html and fix the mismatch?

Nomader0 said:
ok i found this http://www.htc1guru.com/guides/return-stock-guide/ and answered most of my questions.. except one:
As i said there is no RUU for me.. i will use a nandroid to restore most of the stuff. BUT there will be a mismatch between my stock Rom installed and the firmware (what is written in bootloader screen OS:XXXXXXX) How can i fix that?
can i just install the TMOB101 firmware from here http://android-revolution-hd.blogspot.gr/p/android-revolution-hd-mirror-site-var.html and fix the mismatch?
Click to expand...
Click to collapse
Once you flash the guru reset, and then perform the OTA, you'll be on the same firmware after install.

Yeah but that will be different than the one my cid is supposed to have.. won't HTC service notice?

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