Related
not helpful
how about a quick English tutorial ? did you tested the package ?
on what CID you managed to flash the altered rom zip file ?
I have used Googe to translate the Read Me
View attachment 1453868
1immortal said:
how about a quick English tutorial ? did you tested the package ?
on what CID you managed to flash the altered rom zip file ?
Click to expand...
Click to collapse
I have unlocked bootloader
RUU extract 1.19.exe, I have rom.zip
extract rom.zip
in the rom folder, I change mainver of the android-info.txt from 1.29 to 2.17
perform file compression 3 (android-info.txt, boot_signed.img, recovery_signed.img, system.img) with a new name "rom.zip" (it is different from the original rom.zip) and copy the file "rom.zip "the tool Endeavoru_CustomRUU
HTC trip one x on fastboot
run ARUWizard.exe
Just a heads up ... Updating bootloaders are irreversible I would recommend to wait until a recognized developer conforms it otherwise you may end up bricking the device permanently.
did anyone test it?
if we can re sign the zip file it may give s-off too
ShyamSasi said:
Just a heads up ... Updating bootloaders are irreversible I would recommend to wait until a recognized developer conforms it otherwise you may end up bricking the device permanently.
Click to expand...
Click to collapse
I've done successfully on my htc one x
heobanhki said:
I've done successfully on my htc one x
Click to expand...
Click to collapse
This does not help in any way because if you try flashing ROM.zip with hboot.img inside it won't flash because of signature verification failed..
You can do system.img and boot.img and recovery sure will pass because that is what unlocked bootloader is already allowing you too flash other then that it just won't flash...hboot still can't pass the verification...
MemAllocatoR said:
This does not help in any way because if you try flashing ROM.zip with hboot.img inside it won't flash because of signature verification failed..
You can do system.img and boot.img and recovery sure will pass because that is what unlocked bootloader is already allowing you too flash other then that it just won't flash...hboot still can't pass the verification...
Click to expand...
Click to collapse
rom.zip signatures are disabled
Not possible.
This method tampered signature of ROM.zip. It did fool the edited RUU pass version check for ROM installation, but remember the ROM.zip signature is no more signed from HTC thus can only install on unlock phone.
While the firmware.zip required lock bootloader to work with. A S-On's hboot will also check the sign of firmware.zip before flashing. Under this method, firmware.zip inside remain untampered but it will not be accept by existing hboot as bootloader is not lock and if firmware.zip contain a older version of hboot.
REVISED: firmware.zip (hboot lay inside) is not required lock bootloader because OTA can be apply on unlock bootloader. However, it will check signature from HTC before replacing itself.
Recently, some taiwan guys use this method to create custom RUU to getting back to *stock* because they only have an ROM.zip extracted from 2.17 RUU but not RUU itself. Nice to tell that their method also caplable to convert three taiwan carriers CID into taiwan unbranded CID and received .709. OTA. This was possible because the firmware.zip itself allow it.
HebeGuess said:
Not possible.
This method tampered signature of ROM.zip. It did fool the edited RUU pass version check for ROM installation, but remember the ROM.zip signature is no more signed from HTC thus can only install on unlock phone.
While the firmware.zip required lock bootloader to work with. A S-On's hboot will also check the sign of firmware.zip before flashing. Under this method, firmware.zip inside remain untampered but it will not be accept by existing hboot as bootloader is not lock and if firmware.zip contain a older version of hboot.
Recently, some taiwan guys use this method to create custom RUU to getting back to *stock* because they only have an ROM.zip extracted from 2.17 RUU but not RUU itself. Nice to tell that their method also caplable to convert three taiwan carriers CID into taiwan unbranded CID and received .709. OTA. This was possible because the firmware.zip itself allow it.
Click to expand...
Click to collapse
thanks for all
Happy days
So does it work or no?
It seems that there are a few shady Chinese forums that are publicising the RUU for HTC_044 JB version. Is this for real? Has anyone tried it? Please let us all know.
You failed to provide a link or a filename or any other useful information. So no, nobody knows if they've tried "it".
well what do you know..there were a bunch of them yesterday night..but today they have all disappeared..
Remember the link that you reported to Mod and that get deleted ?
I replied to your post but your post was deleted too : http://forum.xda-developers.com/showpost.php?p=34800519&postcount=770
But I manage to download the RUU from that link before it was deleted.
What I want to say... the RUU is genuine and I already run it to my device and it was a successful flash.
Now .. that RUU discussion already in Football's thread http://forum.xda-developers.com/showthread.php?t=1543604&page=246
ckpv5 said:
Remember the link that you reported to Mod and that get deleted ?
I replied to your post but your post was deleted too : http://forum.xda-developers.com/showpost.php?p=34800519&postcount=770
But I manage to download the RUU from that link before it was deleted.
What I want to say... the RUU is genuine and I already run it to my device and it was a successful flash.
Now .. that RUU discussion already in Football's thread http://forum.xda-developers.com/showthread.php?t=1543604&page=246
Click to expand...
Click to collapse
The reason I said it was corrupted was that I couldn't extract the boot and recovery images from the rom.zip file. I'm on custom rom and I need to have boot and recovery images to flash the ruu. How did you extract these images. Plus, do you have the link again?
Sent from my HTC One X using xda app-developers app
To flash the RUU, you don't need the boot.img and recovery.img. Just relock the bootloader and run the RUU in fastboot mode.
Currently, there is no proper way to extract the JB rom.zip, that is why you thought the RUU was corrupted.
Is your device is on CID HTC__044 ? This RUU is only for HTC__044.
If you still need the RUU, boot.img and the recovery.img, PM me and I'll give you links to download them. BTW, you also can get the RUU from Football's thread in Dev section.
http://forum.xda-developers.com/showpost.php?p=34846885&postcount=2468
amirage said:
The reason I said it was corrupted was that I couldn't extract the boot and recovery images from the rom.zip file. I'm on custom rom and I need to have boot and recovery images to flash the ruu. How did you extract these images. Plus, do you have the link again?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
The same, I have the RUU but I cant extract from rom.zip, it show CRC error.
the RUU.exe MD5 is correct. how to extract now?
ckpv5 said:
To flash the RUU, you don't need the boot.img and recovery.img. Just relock the bootloader and run the RUU in fastboot mode.
Currently, there is no proper way to extract the JB rom.zip, that is why you thought the RUU was corrupted.
Is your device is on CID HTC__044 ? This RUU is only for HTC__044.
If you still need the RUU, boot.img and the recovery.img, PM me and I'll give you links to download them. BTW, you also can get the RUU from Football's thread in Dev section.
http://forum.xda-developers.com/showpost.php?p=34846885&postcount=2468
Click to expand...
Click to collapse
Hey thanks for the headsup. Yes, my device is HTC__044. I'm currently on Maximum V10 (which is really good) but I thought of going back to stock again. Since I'm on a custom boot/ recovery, I was under the impression that you need to flash the stock boot and recovery images and then flash the RUU while in fastboot mode. This was how I went back to stock while I was on ICS. Thanks for the link, though. Please check your PM.
vua777 said:
The same, I have the RUU but I cant extract from rom.zip, it show CRC error.
the RUU.exe MD5 is correct. how to extract now?
Click to expand...
Click to collapse
Flash RUU to your HOX, then dump boot+system.img
Command prompt :
> adb shell
> su
> dd if=/dev/block/mmcblk0p4 of=/sdcard/boot.img
Click to expand...
Click to collapse
Command prompt :
> dd if=/dev/block/mmcblk0p12 of=/sdcard/system.img
Click to expand...
Click to collapse
amirage said:
The reason I said it was corrupted was that I couldn't extract the boot and recovery images from the rom.zip file.
Click to expand...
Click to collapse
Now I know why we can not unzip rom.zip, HTC have make some encryption to JB rom.zip http://forum.xda-developers.com/showthread.php?t=1989308
Hello, been looking for a way to return to stock xx.xxx.709.xx with cid_621. I'm on developer firmware atm and the only way to return is by flashing a RUU, but unfortunatly I've not been able to find any. Any help would be highly appriciated. Doesn't matter which version just a RUU for 709 works. Thanks
I assume your device is S-Off, if not how can you have Developer Edition firmware on it, right ?
Why do you need a RUU to revert to stock ? You can simply restore a 4.24.709.3 backup and its stock recovery then do OTA to 6.12.709.4
You can get all the needed files here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If you insist to install RUU, there is one untested but a very old RUU, means if it is successful installed .. you need to do a lot .. a lot of OTA up to 6.12.709.4
You can find it here, it listed on top and it's a RUU zip, not exe - http://androidruu.com/?developer=M8
ckpv5 said:
I assume your device is S-Off, if not how can you have Developer Edition firmware on it, right ?
Why do you need a RUU to revert to stock ? You can simply restore a 4.24.709.3 backup and its stock recovery then do OTA to 6.12.709.4
You can get all the needed files here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If you insist to install RUU, there is one untested but a very old RUU, means if it is successful installed .. you need to do a lot .. a lot of OTA up to 6.12.709.4
You can find it here, it listed on top and it's a RUU zip, not exe - http://androidruu.com/?developer=M8
Click to expand...
Click to collapse
Ah, didn't know you could take update without full RUU. Thx alot!
Wallee97 said:
Ah, didn't know you could take update without full RUU. Thx alot!
Click to expand...
Click to collapse
Yeah .. don't need RUU .. you need a non-rooted stock ROM and stock recovery.
Hi I have T mobile HTC one m8 which is running on firmware 4.20.531.5 .
Firmware 6.20.531.5 is out for T-mob so I donloaded RUU and before that RELOCKED the bootloader.
On fastboot screen it says RELOCKED.
So I went ahead with RUU installation ( downloaded from htc support website) and ran it.
I get error[155} unknown error with my phone displaying htc logo in white.
This error is due to bootloader not locked but mine is relocked.
I am pretty sure the RUU is correct and I can just go to bootloader screen only.
what should I do now?
Please help.
rahulsethi said:
Hi I have T mobile HTC one m8 which is running on firmware 4.20.531.5 .
Firmware 6.20.531.5 is out for T-mob so I donloaded RUU and before that RELOCKED the bootloader.
On fastboot screen it says RELOCKED.
So I went ahead with RUU installation ( downloaded from htc support website) and ran it.
I get error[155} unknown error with my phone displaying htc logo in white.
This error is due to bootloader not locked but mine is relocked.
I am pretty sure the RUU is correct and I can just go to bootloader screen only.
what should I do now?
Please help.
Click to expand...
Click to collapse
to bring it to top
rahulsethi said:
I get error[155} unknown error
Click to expand...
Click to collapse
This is a common problem for folks trying to go from LP to MM by RUU.
You'll need to find or extract the 6.20.531.5 firmware.zip, and flash it in fastboot RUU mode. Then the RUU should install properly.
Are you unable to get OTAs? If the RUU doesn't work, you can just keep updating the phone through OTAs. The function is found in Settings > About > Software Updates.
redpoint73 said:
This is a common problem for folks trying to go from LP to MM by RUU.
You'll need to find or extract the 6.20.531.5 firmware.zip, and flash it in fastboot RUU mode. Then the RUU should install properly.
Click to expand...
Click to collapse
How could I extract this firmware from exe file ? or do I have to find signed zip of this firmware ?
And should I flash it in adb by fastboot flash firmware firmware.zip ?
use this method to flash firmware T-Mobile first
download FW here
copy FW to folder adb fastboot
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip **frimware name.zip**
fastboot flash zip **frimware name.zip** - yes, 2 times
fastboot reboot-bootloader
atter that, you can flash RUU.exe
md07 said:
use this method to flash firmware T-Mobile first
download FW here
Click to expand...
Click to collapse
Yes, to the OP that is what you want (the full stock firmware if you are s-on . . . I believe that one is signed).
---------- Post added at 09:02 AM ---------- Previous post was at 09:00 AM ----------
rahulsethi said:
How could I extract this firmware from exe file ? or do I have to find signed zip of this firmware ?
Click to expand...
Click to collapse
If you are s-on, it needs to be signed in order to flash it.
When you run the exe, it will make a ROM.zip in the WIndows temp folder, which is a zip version of the full RUU. You can extract firmware.zip from ROM.zip, but I don't know if its signed anymore after you extract it that way.
It worked
md07 you are the freaking man
redpoint73 said:
Yes, to the OP that is what you want (the full stock firmware if you are s-on . . . I believe that one is signed).
---------- Post added at 09:02 AM ---------- Previous post was at 09:00 AM ----------
If you are s-on, it needs to be signed in order to flash it.
When you run the exe, it will make a ROM.zip in the WIndows temp folder, which is a zip version of the full RUU. You can extract firmware.zip from ROM.zip, but I don't know if its signed anymore after you extract it that way.
Click to expand...
Click to collapse
md07 said:
use this method to flash firmware T-Mobile first
download FW here
copy FW to folder adb fastboot
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip **frimware name.zip**
fastboot flash zip **frimware name.zip** - yes, 2 times
fastboot reboot-bootloader
atter that, you can flash RUU.exe
Click to expand...
Click to collapse
redpoint73 said:
Yes, to the OP that is what you want (the full stock firmware if you are s-on . . . I believe that one is signed).
---------- Post added at 09:02 AM ---------- Previous post was at 09:00 AM ----------
If you are s-on, it needs to be signed in order to flash it.
When you run the exe, it will make a ROM.zip in the WIndows temp folder, which is a zip version of the full RUU. You can extract firmware.zip from ROM.zip, but I don't know if its signed anymore after you extract it that way.
Click to expand...
Click to collapse
Thanks guys! Finally had a chance to flash my firmware. However I flashed signed MM firmware from a thread by @ckpv5 instead of one you gave me @md07 as I was S-on
Thanks a lot @redpoint and @md07
Help please!
rahulsethi said:
Thanks guys! Finally had a chance to flash my firmware. However I flashed signed MM firmware from a thread by @ckpv5 instead of one you gave me @md07 as I was S-on
Thanks a lot @redpoint and @md07
Click to expand...
Click to collapse
I bought a htc one m8, its unlocked and now I just s-Off , but when i try to run the .exe RUU say the error [151] , the info of my device its:
***Software status: Modified***
***UNLOCKED***
CID-BS_US001
i just want the oficial developer edition 6.0 marshmallow, can someone help me?
seangtz said:
I bought a htc one m8, its unlocked and now I just s-Off , but when i try to run the .exe RUU say the error [151] , the info of my device its:
***Software status: Modified***
***UNLOCKED***
CID-BS_US001
i just want the oficial developer edition 6.0 marshmallow, can someone help me?
Click to expand...
Click to collapse
If updating to MM from LP (or KK for that matter) you need to first flash the MM firmware with the same number as the RUU. Its a peculiarity with US Marshmallow RUUs.
Help pls I need the correct ruu for this model (attached is the getvar all)
thanks!
mentioning @ckpv5 that helped me before please help again hehehe thanks! and GODBLESS
your security is off and you have super CCID you can install any RRU almost. change CCID and MID to what ever you want and download one RRU from any thread.
How many M8 that you have ? You have a phone shop ?
With current CID/MID ... you can install RUU :
1. T-MOB 6.20.531.5 RUU or
2. Developer Edition 6.12.1540.4 RUU
but you need to fastboot flash its firmware zip first before you run RUU
If you don't use the device is US, it's best to change MID to EU MID then install 6.12.401.4 RUU
ckpv5 said:
How many M8 that you have ? You have a phone shop ?
With current CID/MID ... you can install RUU :
1. T-MOB 6.20.531.5 RUU or
2. Developer Edition 6.12.1540.4 RUU
but you need to fastboot flash its firmware zip first before you run RUU
If you don't use the device is US, it's best to change MID to EU MID then install 6.12.401.4 RUU
Click to expand...
Click to collapse
hi @ckpv5 I just helping some of my friends in facebook that bricked their device, so here's is the new getvar all we flash the firmware yesterday 6.12.401.4 then we decided to flash custom rom now wifi doesnt work, how can I change the mid then? BTW thanks for your always support may GOD bless you
That's most probably incomplete firmware that you installed because I can see the radio is old.
You need full firmware install or if modded one that remove boot & recovery only.
Check general section on how to change MID if you want to properly do it.
(Can't link now as I'm on mobile)
ckpv5 said:
That's most probably incomplete firmware that you installed because I can see the radio is old.
You need full firmware install or if modded one that remove boot & recovery only.
Check general section on how to change MID if you want to properly do it.
(Can't link now as I'm on mobile)
Click to expand...
Click to collapse
ok since we update the firm all we need to do now is to change mid to europe then flash the ruu?
MID change first then firmware then RUU.
You already have TWRP installed, right ? I can see you're using outdated TWRP 2.7.x.x
Boot to TWRP, select Mount - System
Open command prompt from your adb/fastboot folder, then run command
adb shell
change MID code
no need command "su"
Code, get it here : http://forum.xda-developers.com/showthread.php?t=2708581
Once done select reboot -bootloader
install 6.12.401.4 firmware - you can get the full signed firmware from my backup thread post #5
then install RUU - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
(you can try to install RUU without firmware flashed first .. if I'm not wrong this RUU zip doesn't require MM firmware been installed)