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?
Related
I've restored successfully using RRU a couple of times using UK TMO images but I'm no longer able to.
What I did was RRU an image and then OTA update to a version which is unavailable as a RRU. It's currently bricked I just see the pink circle although I can get to the bootloader via power-back (although not via power-vol down oddly).
I think the RRU isn't allowing downgrade now. Is there anyway of either forcing the Windows RRU updater to ignore version or flash more directly?
Enter recovery and flash a stock rooted Rom then ruu it
Or enter fastboot plug phone in then run ruu as administrator
Sent from my HTC Desire using XDA Premium App
I lost recovery it just goes to the pink circle. I only have bootloader.
And I can't run RUU on any of the available UK T-Mobile images without error.
gruntling said:
I lost recovery it just goes to the pink circle. I only have bootloader.
And I can't run RUU on any of the available UK T-Mobile images without error.
Click to expand...
Click to collapse
Hmm. If you have s-off, can you try to flash recovery via fastboot, then wipe everything and flash rom of choice? Never done that but I think my logic is good?
What is long hex code for goldcard?
I think the issue with my failing RUU update is that I have 2.12.110.4 and there isn't a RUU for T-Mobile for that version -- the last is 1.12.110.4 and RUU gives error "error 140 bootloader version error".
I've tried the OTA update as a PB99IMG.ZIP via fastboot but that doesn't work. I assume the ZIPs are signed and I can't mix the RUU extracted rom and OTA.
I think my best option is a goldcard but I don't have access to read the long hex CID from the phone.
I can see cid::T-MOB005 from fastboot.exe oem boot. Is there any way of translating that to the long hex code?
gruntling said:
I think the issue with my failing RUU update is that I have 2.12.110.4 and there isn't a RUU for T-Mobile for that version -- the last is 1.12.110.4 and RUU gives error "error 140 bootloader version error".
I've tried the OTA update as a PB99IMG.ZIP via fastboot but that doesn't work. I assume the ZIPs are signed and I can't mix the RUU extracted rom and OTA.
I think my best option is a goldcard but I don't have access to read the long hex CID from the phone.
I can see cid::T-MOB005 from fastboot.exe oem boot. Is there any way of translating that to the long hex code?
Click to expand...
Click to collapse
This may help I think:
http://forum.xda-developers.com/archive/index.php/t-921398.html
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
Help please urgently needed.
I need a stock backup of JB on telecom nz. CID TELNZ001. with s on
or a firmware.zip with JB and hboot included.
Reason: MAINVER IS HIGHER THAN ANY MAINVER THAT EXISTS IN THE WORLD.
it was updated in the androidinfo.txt.... so it permently updated the mainver. unable to roll back to stock ICS as mainver is newer.
and there is no RUU for JB on telnz001.
even if there was a RUU, it would result in an error as mainver is newer than ANY JB firmware in the world 3.76.xx.
many attempts of trying firmware.zip, rom.zip ruu, flashing through fastboot, ruu mode etc all do not work.
i can restore to stock ICS software by changing androidinfo.txt to match my mainver..... but with OTA updates it results in constant rebooting or rebooting into fastboot as mainver is newer than OTA update.
and yes when i tried all this i relocked bootloader, reflashed stock boot and recovery, tried many different boot.img, recovery.img files. nothing seems to work
and 9/10 times a zip is ALWAYS corrupt.
IF ANYONE HAS JB TELNZ001 nandroid or firmware.zip could they please upload, also needed hboot so JB works thanks
You need a ICS nandroid backup or a lower version than that. Your bootloader says 1.12 hboot, that's not a JB hboot.
Mr Hofs said:
You need a ICS nandroid backup or a lower version than that. Your bootloader says 1.12 hboot, that's not a JB hboot.
Click to expand...
Click to collapse
No i dont, i need a JB firmware.zip / rom.zip or a nandroid backup, i have hboot1.39 for telnz001 which i can flash IF i get the nandroid backup.
IF i put ICS on it WILL crash on OTA updates, it reaches the 2.17 update and CRASHES it boots and reaches the ring lock screen and restarts, i have tried this dozens of times, with my own ics backup, other ics backups, extracting the rom from telecom nz ruu (ics) and everytime it crashes after the OTA.
By flashing hboot 1.39 for my own carrier i will be able to use JB TELNZ001 this is why i am asking for it, as a last resort i created a username and password specifically for this question as i have been trying to revert back to stock ( and have it FULLY UPDATE WITHOUT FAIL ) to JB and have not been able to as it fails,
after doing this i have updated kernals and other img files, and have not been able to get it to fully boot after the OTA update.
You say you have the firmware for the 1.39 hboot, yet you ask for a JB nandroid and a JB firmware. I read it very clear in your OP
No i have the hboot 1.39 FILE, NOT THE FIRMWARE, the firmware i said i had was ICS stock, which when i update it FAILS ALL the time. i made that clear, if i had the firmware for JB i wouldnt be asking for nandroid backup... all i am asking for is the nandroid backup of jb telnz001 as all i have is the ICS nandroid, ruu , firmware.zip and rom.zip, which all of the above when installed refuse to flash properly or boot, its not even the JB update it crashes on, its the update just before the JB update. However i did say i have the JB firmware OTA zip, which is USELESS as it CANNOT be flashed
Edit : nevermind !
I wish you al the best and good luck to find a nandroid.
Mr Hofs said:
Then you might have used the wrong words. The file to update the hboot to 1.39 is the firmware. And the firmware you speak of as ics stock is the nandroid backup ics !
I know what im talking about mate.
I wish you al the best and good luck to find a nandroid.
Click to expand...
Click to collapse
So do i , i obtained the hboot 1.39 from an OTA JB zip file, whch in a way i supose is firmware. but there is no way to install the zip file onto ics. or is there? its not flashable and contains recovery.img hboot 1.39 boot.img and a system folder and a few other things, if the folders were img files i would just flash these and wouldnt have a problem.
i guarantee if i can obtain a nandroid backup of JB it will work, i have been susessfull on another htc one with a very similar problem, but the problem is i cant use their nandroid they are no longer in the same town , so i am unable to use it untill one is available to download
misterr.mann said:
So do i , i obtained the hboot 1.39 from an OTA JB zip file, whch in a way i supose is firmware. but there is no way to install the zip file onto ics. or is there? its not flashable and contains recovery.img hboot 1.39 boot.img and a system folder and a few other things, if the folders were img files i would just flash these and wouldnt have a problem.
i guarantee if i can obtain a nandroid backup of JB it will work, i have been susessfull on another htc one with a very similar problem, but the problem is i cant use their nandroid they are no longer in the same town , so i am unable to use it untill one is available to download
Click to expand...
Click to collapse
Paste the firmware.zip in your fastboot folder.
THen
1. fastboot oem lock
2. fastboot oem rebootRUU
3.fastboot flash zip firmware,zip
The hboot is upgraded.But you cant boot up cause tou are locked.
Again unlock with fastboot and your unlock_tocken.bin
A standalone firmare.zip is flashable. But i don't know if it can be extracted directly from the ota. Search in the collection of firmare updates. Maybe there is news about that
The firmare can be flashed with
Fastboot oem rebootRUU
Fastboot flash zip firmare.zip
These commands and the right firmware will update the hboot to 1.39.
The only question is if you can flash the firmware.zip without it needing to be modified or not ?
i can flash a modified or unmodified firmware.zip easly with adb / fastboot with phone in RUU mode, the only problem is the contents in the OTA update are folders so its not flashable, i zip boot.img hboot file recovery.img and system.img and androidinfo.txt name it firmware.zip and flash it... the problem is i can not find the system img which has JB contents, as the zip contains apks, folders and files and its not flashable lol. hence why im asking for someone to upload nandroid backup , or a firmware.zip containing JB as i can put my TELNZ001 hboot file in the zip and susessfully flash JB onto my hox
Maybe you can ask here too about a firmware ?
http://forum.xda-developers.com/showthread.php?t=1957376
{< r o N o $ said:
Paste the firmware.zip in your fastboot folder.
THen
1. fastboot oem lock
2. fastboot oem rebootRUU
3.fastboot flash zip firmware,zip
The hboot is upgraded.But you cant boot up cause tou are locked.
Again unlock with fastboot and your unlock_tocken.bin
Click to expand...
Click to collapse
contained in the ota update is many files folders and img, except system img its just a dir folder, there is a firmware.zip but its corrupt. actually almost every zip i extract from or download (flashable ones) are ALWAYS corrupt, and i have noticed MANY peol;e have this issue.
also if i put ics on and ota it boot loops regardless of weather im locked or unlocked, regardless of boot img, recovery or even flashing kernal no matter what still boot loops
I think the firmware.zip is encrypted and not corrupt.....
Mr Hofs said:
Maybe you can ask here too about a firmware ?
http://forum.xda-developers.com/showthread.php?t=1957376
Click to expand...
Click to collapse
thanks dude, i asked there and they updated the link.. but its still 1.29 (ics)
i have a file named
OTA_ENDEAVOR_U_JB_45_S_Telecom_NZ_WWE_3.17.781.2-2.17.781.3_release_304681lsq8o9k2p8n4minf.zip
it contains firmware.zip with hboot.139 in it, i cant flash as it comes back unknown error 99
regardless of locked or unlocked bootloader.
i tried extracting files, and editing androidinfo.txt to match my mainver, but still comes back with an error.
is there any other way to flash the hboot? i have the img itself, and still have the original ota update zip but its not flashable
OK so i can only run one rom.
stock ics
any other rom will not boot, even after flashing boot.img i really just want to get this phone working
Hi, not sure if you have managed to find a nandroid backup for TELNZ001 stock firmware yet, but if you're still searching for it, here it is:
http://forum.xda-developers.com/showpost.php?p=37519317&postcount=39
Hi,
I want to increase my internal memory by using Link2SD, for which I need my phone rooted. I have spent 2 days already trying to figure this out, but I have made zero progress. I have tried everything I could google, but most guides refer to revolutionary.io website, which is down.
I found this guide - http://forum.xda-developers.com/showthread.php?t=1600904
Even though it's for Incredible, I though the steps would be similar, perhaps with different files. Anyway, I'm stuck on step one where I need to unlock bootloader using HTCdev.
fastboot oem get_identifier_token returns command error:
(bootloader) [ERR] Command error !!!
OKAY [ 0.010s]
finished. total time: 0.010s
Click to expand...
Click to collapse
I am sure I have all my drivers installed correctly, both adb and fastboot work just fine (both show device when connected).
From what I understand, it is because of my HBOOT version, right? I tried running different RUUs I could find, but it always ends up with an error - either model id error [130], or something saying my image is newer than the one I want to upload (maybe it's bootloader version error [140], I don't remember now).
How should I proceed now?
Thanks
Phone specs:
Unbranded
HBOOT 1.02.001
S-ON
Android version 2.3.3
Baseband 32.56.00.32U_5.17.05.23
Software number 3.14.405.1
I have the exact same problem, except my device is branded, but I guess it doesn't matter much.
My software and HBOOT versions match yours
same problem ))
the same problem
HBOOT 1.02.001
S-ON
Android version 2.3.3
Baseband 32.56.00.32U_5.17.05.23
Software number 3.14.405.1
Google rumrunner s-off. Dunno if it will work r not but its for htc devices
jmcclue said:
Google rumrunner s-off. Dunno if it will work r not but its for htc devices
Click to expand...
Click to collapse
It won't, because HTCDEV unlock is necessary for it. And we can't perform it because of the reasons explained in the first post.
try this http://forum.xda-developers.com/htc...-froyo-2-2-to-stock-2-1-t3187731/post62534573
installing pre-rooted update zip on S-ON - this method doesn't work, system goes to reboot on atempt to update
yep! but I got a root other way
I have already written tutorial but in russian. make sure to download attachments you need register https://translate.google.ru/transla...8&view=findpost&p=42658143&edit-text=&act=url
if in short , I received a temporary root with Zerg Rush , and then changed version of rom with this tut http://forum.xda-developers.com/showthread.php?t=1550397 and then flash the official RUU 2.29.405.5 then installed the update 2.29.405.14 , and then install another update from htcdev is updated hboot to 1.03 version , then you can get the official unlock well then flash custom recovery and from his custom rom. sorry for my bad English, almost everything Google translator
Desire Bravo said:
yep! but I got a root other way
I have already written tutorial but in russian. make sure to download attachments you need register https://translate.google.ru/transla...8&view=findpost&p=42658143&edit-text=&act=url
if in short , I received a temporary root with Zerg Rush , and then changed version of rom with this tut http://forum.xda-developers.com/showthread.php?t=1550397 and then flash the official RUU 2.29.405.5 then installed the update 2.29.405.14 , and then install another update from htcdev is updated hboot to 1.03 version , then you can get the official unlock well then flash custom recovery and from his custom rom. sorry for my bad English, almost everything Google translator
Click to expand...
Click to collapse
i can read russian, haha http://4pda.ru/forum/index.php?showtopic=247349
& !THE SOLUTION! - it really works, thanks! - see http://forum.xda-developers.com/showpost.php?p=62647076&postcount=1260
Hello guys! Will this method work with 2.2.2 and HBoot 0.93.0001? I was trying to find the downgrade utility to 2.1 so i could use unrevoked, but unfortunately all links are dead.
Hi! You can Root with unrevoked.com
then S-off with alpharev.nl
and then flash any firmware.
Or you can flash any RUU firmware, but you need downgrade your firmware version with this Tutorial http://forum.xda-developers.com/showthread.php?p=24039156#post24039156
make sure: do not download and flash 2.3 firmware in step 2, download and flash for example RUU_Bravo_HTC_WWE_1.21.405.2
Desire Bravo can you help me?
@Desire Bravo,
You can also root your Desire (After you get your bootloader unlocked, of course) with Super One Click, this will work if you press the "Root" button while the HTC logo is displayed.
Are you the author of this russian tutorial?
I need help with the "downgrade.zip" and the second "PB99IMG.zip" files, seems to be missing. On the other hand, I don't know when I should flash the first "PB99IMG.zip" file or how to overwrite the "misc" partition. Can you help me with this?
Thank you very much in advance. Best regards.
Hi! Yes i can help, what is your hboot version? write info from the bootloader (vol down + power)
Are you from usa? Downgrade your Firmware version nummer, then try flash RUU Telstra from http://shipped-roms.com/download.ph...8.00.32U_5.11.05.14_release_150162_signed.exe
and unlock with htc dev
@Desire Bravo
Hello again Desire Bravo.
HBOOT 1.02.0001 Bootloader Locked. S-ON
Firmware version 2.3.3 Gingerbread signed 3.14.405.1
No, I'm from Spain (GSM Phone, not CDMA).
So I will use RUU WWE 2.29.405.5 firmware, but I don't know in which one of those steps I should flash the first PB99IMG.zip file (the modified "rom.zip"), neither how to overwrite the misc partition
Thank you very much in advance. Best regards.
Soooo Have you downgrade firmware version? if yes, you have version 1.15.405.3 and now you can flash "any" RUU an firmware. Try flash .exe (boot too bootloader and run Ruu 2.29.405.5 . exe ) http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_159811_signed.exe
OR extract rom.zip rename to PB99IMG and flash with pB methode.
OR follow this guide and write 2.29.405.14 manuell http://forum.xda-developers.com/showthread.php?t=1550397
then run PB9920000_Bravo_Froyo_hboot_1.03.0003_R.exe
Desire Bravo said:
Soooo Have you downgrade firmware version? if yes, you have version 1.15.405.3 and now you can flash "any" RUU an firmware. Try flash .exe (boot too bootloader and run Ruu 2.29.405.5 . exe ) http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_159811_signed.exe
OR extract rom.zip rename to PB99IMG and flash with pB methode.
OR follow this guide and write 2.29.405.14 manuell http://forum.xda-developers.com/showthread.php?t=1550397
then run PB9920000_Bravo_Froyo_hboot_1.03.0003_R.exe
Click to expand...
Click to collapse
u cant just run "any" ruu otherwise why would there be so many? why not only one for each android version?
if his phone is branded, vodafone etc etc then a wwe ruu would not work, or atleast shouldnt, it would give id error. u should ask these questions first before telling people to run ruu's.
ok if you know more, tell but there isn't enough choice on the site htc dev.
At me too branded t-mobile desire, that to me didn't prevent to flash RUU_Bravo_Froyo_HTC_WWE_2.29.405.5 then to flash update OTA_2.29.405.14_ and then PB9920000_Bravo_Froyo_hboot_1.03.0003_R
I told as at me it turned out, at others it can not turn out, then it is necessary to try with other firmware therefore I also told "any"
I now will make experiment, it became interesting to me))
UPD: i have found simple way to update hboot 1.02 - to 1.03
I will write small tutorial soon
@Desire Bravo,
No, I didn't downgrade my firmware version yet, as I don't know when I have to flash the rom.zip file (renamed as PB99IMG.zip), that's what I'm asking to you.
On the other hand, I don't know how to overwrite the "misc" partition.
So, when I fully understand "how" and "when" to perform each one of those steps I will go ahead with the tutorial.
@jmcclue,
My original firmware was FR83G (Orange) Android Froyo, signed 2.29.405.14, I have found this firmware in a .tar.gz file but don't how to flash it as it's not a zip or a RUU file.
Can I decompress the .tar.gz and put its content in a .zip file? If it's not, please, can you tell me how to get a valid FR83G file?
Do you know how to overwrite the "misc" partition of the Desire?
Thank you very much in advance to both of you. Best regards.
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.