Related
So I have a PG76100 according to whats inscribed on the phone.
marvel pvt ship s-on rl
hboot-0.90.0000
microchip-0451
radio-7.46.35.08
apr 08,2011 17:45:10
image version 1.35.707.3
I tried the RUU's for PG7610000 none of which worked , also tried the HTC India Asia Ruu just in case which didnt work either. So perhaps there is a long wait for me yet again to root the phone
100% SUCCESSFUL!!! I am now HBoot Unlocked I have awaited this day for to long...
Ok so I brought the phone from Telecom, it says its a A510b, model number PG76120 (found behind the battery, just below the SIM card slot)
So what I have done to achieve this result:
1: Simply sign up to the HTCdev website www.htcdev.com/bootloader/ once done, select the HTC Wildfire S from the drop list to begin
2: After accepting all the terms and agreements bla bla their is a list of ROMS, their was only 3 options for the model that I have PG76120, so I downloaded the HTC Thailand RUU
3: Ok so if you end up running the RUU it will tell you that the ROM is out of date with an error message, what I found out (this took me all day...) when you first open the RUU (this is if you run Windows) their will be a Temp folder made with all the files that the RUU needs to run, if you search the Temp Folder (usually found under the user folder in Documents and Settings\<User>\Local Settings\Temp) these files will only exist if you leave the RUU Program open, so just open it up and move the window to the side, search under the Temp folder for rom
4: You will find 2 zip folders named rom_01 and rom_02, copy these 2 zips to your desktop
5: Now change the name of rom_01 (im not 100% sure if its 01 or 02 that you need to do first, I cant remember) to PG76IMG and copy it over to a microSD, insert into your phone and boot into HBoot, it will go through the normal process of detecting and then opening the zip and will ask you if you wish to update the radio to v2 (it should only ask to update the radio, because you need to do it first before you use the second file which asks to update both the radio and hboot) allow to do so and it will do its thing and when completed ask to reboot.
6: Now change the name of the second rom (if I have the order right this should be rom_02) to PG76IMG, remove the first file you put on the microSD and replace it with second, back into HBoot, it will read the file and ask you to update HBoot and Radio, allow it to do so and it will update the HBoot, should say OK next to HBoot, once completed it will ask to be rebooted
7: To check that this has all happended correctly, go back into HBoot (remove your microSD before this) and you should have a pink box up the top stating *LOCKED* if you see this and your HBoot version is now 1.08.0099 (if you used the RUU that I did) you are now ready to go through the HTCdev Bootunlock process
8: Do the HTCdev Bootunlock process, it is straight forward and easy to do!
9: Forget needing to use the XTC and starting modding you HTC Wildfire S!!!
---------- Post added at 10:02 PM ---------- Previous post was at 10:02 PM ----------
Hope this helps you, I managed to do this all today
Best of luck
I'm about to try this method. Hope it works. Will let you know if it does
Thanks!
edit: Didn't work. I tried both HTC Thailand and HTC Asia/India. Thanks though.
Now im wondering how to remove that Pink locked thing..
VibrantWind said:
I'm about to try this method. Hope it works. Will let you know if it does
Thanks!
edit: Didn't work. I tried both HTC Thailand and HTC Asia/India. Thanks though.
Now im wondering how to remove that Pink locked thing..
Click to expand...
Click to collapse
Well if its saying *LOCKED* then its all good to go ahead and do the HTCdev Bootunlock
anoobiser said:
So I have a PG76100 according to whats inscribed on the phone.
marvel pvt ship s-on rl
hboot-0.90.0000
microchip-0451
radio-7.46.35.08
apr 08,2011 17:45:10
image version 1.35.707.3
I tried the RUU's for PG7610000 none of which worked , also tried the HTC India Asia Ruu just in case which didnt work either. So perhaps there is a long wait for me yet again to root the phone
Click to expand...
Click to collapse
hey ill help you with this,
I was also getting the same problem before,
do this
1)download this zip file http://forum.xda-developers.com/showthread.php?t=1432474
2) place this file in on your sd card.
3) reboot into your bootloader by pressing vol - and power button.
4) Let is update your bootlader.
5) Now u are ready to go. no need to update the the ruu.
6) Just follow the steps on htcdev.com without updateing the ruu.
there you go its easy.
Just hit thanks if i helped you thanks
mxvc200 said:
hey ill help you with this,
I was also getting the same problem before,
do this
1)download this zip file http://forum.xda-developers.com/showthread.php?t=1432474
2) place this file in on your sd card.
3) reboot into your bootloader by pressing vol - and power button.
4) Let is update your bootlader.
5) Now u are ready to go. no need to update the the ruu.
6) Just follow the steps on htcdev.com without updateing the ruu.
there you go its easy.
Just hit thanks if i helped you thanks
Click to expand...
Click to collapse
Unfortunately this did not work as well, but thanks anyway.
I wanted to try this out but (Step 3/4) there are no rom_1 zip or even folders in the temp folder ( I use windows 7 C:\Users\XxX\AppData\Local\Temp ) I did a search as well for ROM but did not yield any results. And yes I had the program open when I was looking for the zips.
Can you tell specifically what error yop are getting?
would be happy to help.
Did you flash the zip file in the given link???
Me too
My Wildfire S ROM version is 1.35.707.3 too (other details are also the same). I got failed too with RUU HTC EU (PG7610000_Marvel_hboot_1.08.0099_20111216.exe). Many other RUUs says MODEL ID ERROR (Wrong RUU version I think).
These are the screenshots.
I also just got mailed from HTC Customer Care saying this:
"May I confirm with you have you ever rooted your original ROM, please? If you have never rooted your original ROM, then there's no need to ask about the RUU and just avoid this step and proceed with the next step."
I put the zip on the sd card & followed the instructions.
Parsing
1] booloader -bypassed
2]radiov2 updating
then
1] booloader -bypassed
2]radiov2 OK
update complete
press power to reboot
My bootloader is still 0.90.0000 but my radio updated to 7.53.39.03M from 7.46.35.08
With RUU HTC EU? Can you proceed now with fastboot command to get your token?
Just wanna say thanks once again
I finally got it to work. I got the same specs as the OP
Didnt realize that i needed to skip all the RUU process and just go straight to the next step. Did that and followed the instructions. And now finally got an unlocked bootloader
THANKS!
VibrantWind said:
Just wanna say thanks once again
I finally got it to work. I got the same specs as the OP
Didnt realize that i needed to skip all the RUU process and just go straight to the next step. Did that and followed the instructions. And now finally got an unlocked bootloader
THANKS!
Click to expand...
Click to collapse
Glad to hear that. But your version is for is different from mine.
No Luck for me , this is what i get
C:\android>fastboot oem get_identifier)token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
anoobiser said:
I put the zip on the sd card & followed the instructions.
Parsing
1] booloader -bypassed
2]radiov2 updating
then
1] booloader -bypassed
2]radiov2 OK
update complete
press power to reboot
My bootloader is still 0.90.0000 but my radio updated to 7.53.39.03M from 7.46.35.08
Click to expand...
Click to collapse
Dude... You need to flash the rom_1.zip first and then the rom_2.zip!!(both renamed to PG76IMG.zip and flashed by placing them i sd one after the other!)
U cant just flash one of them!!!
it first upgrades your radiov2 thing for some reason in the rom_1.zip then it upgrades ur bootloader and your radiov2 thing!
181charan said:
Dude... You need to flash the rom_1.zip first and then the rom_2.zip!!(both renamed to PG76IMG.zip and flashed by placing them i sd one after the other!)
U cant just flash one of them!!!
it first upgrades your radiov2 thing for some reason in the rom_1.zip then it upgrades ur bootloader and your radiov2 thing!
Click to expand...
Click to collapse
This was for the method suggested by mxvc200.
The 2nd method was a failure from inception as I was unable to locate the rom_1.zip & rom_2.zip files
---------- Post added at 12:12 AM ---------- Previous post was at 12:03 AM ----------
anoobiser said:
I put the zip on the sd card & followed the instructions.
Parsing
1] booloader -bypassed
2]radiov2 updating
then
1] booloader -bypassed
2]radiov2 OK
update complete
press power to reboot
My bootloader is still 0.90.0000 but my radio updated to 7.53.39.03M from 7.46.35.08
Click to expand...
Click to collapse
Similar problem it is observable two days. It is a lot of people. In some phones the loader 0.90.0000 is updated easily, and in others is not updated. The decision yet do not send. The reason of the similar phenomenon too is unknown. The given phenomenon was observed also at change of 1.33 - 1.66 - 2.13. Thus the loader remained 0.90.0000....
What it is possible to try to make in a similar situation? We tried to make:
1) Temporary root
2) the install hboot through adb.
But it has turned out nothing because of signature check
Uksus17 said:
---------- Post added at 12:12 AM ---------- Previous post was at 12:03 AM ----------
Similar problem it is observable two days. It is a lot of people. In some phones the loader 0.90.0000 is updated easily, and in others is not updated. The decision yet do not send. The reason of the similar phenomenon too is unknown. The given phenomenon was observed also at change of 1.33 - 1.66 - 2.13. Thus the loader remained 0.90.0000....
What it is possible to try to make in a similar situation? We tried to make:
1) Temporary root
2) the install hboot through adb.
But it has turned out nothing because of signature check
Click to expand...
Click to collapse
What you might be doing wrong is that your not getting those rom files from the correct RUU depending on that model of your Wildfire (found behind the battery under the SIM carrier) you have to use the right one that suits your phone and then go through the process that I have posted up, other wise it wont work.
anoobiser said:
This was for the method suggested by mxvc200.
The 2nd method was a failure from inception as I was unable to locate the rom_1.zip & rom_2.zip files
Click to expand...
Click to collapse
Thanks, I have understood all. The most interesting, that after an insertion of the first archive with radio special the hboot became S-OFF 0.90.0000. Can be it is not necessary to raise it and not to install the second archive? There can be it would be real S-OFF or no?
anoobiser said:
I wanted to try this out but (Step 3/4) there are no rom_1 zip or even folders in the temp folder ( I use windows 7 C:\Users\XxX\AppData\Local\Temp ) I did a search as well for ROM but did not yield any results. And yes I had the program open when I was looking for the zips.
Click to expand...
Click to collapse
The rom_01 and rom_02 files only appear in the temp files briefly during the update process, I couldn't find them at first either.
What I did was step through the RUU process (clicking next) and looking in the temp directory after each step, I think they appear before you hit next to start the update (and then vanish when you hit next to start the process).
Am on windows 7 too and found them in the same directory you mentioned.
Who should read this post?
You have updated your One X to a newer version via OTA, then you want to restore the software/ return stock but the latest RUU is not available. (boot to fastboot mode and type the following command "fastboot getvar version-main", This is the true version of your phone!)
You have some basic skills to flash things using "fastboot"
Those who want to back to stock and wait for the JB OTA.
Those with ICS hboot should works without any problem, someone had test it on JB hboot and works(updated in step 6, 7). but we need more testers.
The concept behind.
1. Fool the RUU to make it believe that it is flashing the latest ROM, but actually, we are flashing an older version.
2. after that, boot up the phone with older version of software, then OTA and update the phone to latest software.
How to do that?
0. backup all your stuff including those in SD, all your stuff in your phone will be lost. Then wipe all data (including SD) using your custom recovery. (important! Otherwise, you may not be able to receive OTA).
1. You have to download a "custom RUU" that can be found here.
http://db.tt/z8ajRTuH
Feel free to give a thanks to billd2439, he provide this working link to download the custom RUU.
Just go to #115 http://forum.xda-developers.com/showthread.php?p=35139501#post35139501 and give him a thanks
2. Download the ROM file, it should be in zip format. (You can also extract the rom file by running a RUU, just run the RUU, don't click anything and search the computer for "rom.zip") (In my case, I have an older version 1.29.708.15 rom extracted from RUU)
you may want to find RUU here http://www.htcruu.com
3. unzip the customRUU.zip to a folder, e.g. "customRUU"
4. unzip and extract "android-info.txt", "boot_signed.img" and "system.img" to a folder
5. open android-info.txt with "notepad" (notepad++ is highly recommended)
6. type the following command to get the information from your phone.
fastboot getvar all
you should pay attention to the following information
modelid:
cidnum:
mainver:
hbootpreupdate:
7. edit the value of "modelid", "cidnum", "mainver" and "hbootpreupdate" to match the information you get from step 6.
by doing this your will try to fool the RUU to belive that you are going to flash a newer version e.g (I have OTA my phone to 2.17.708.7, but now I want to fool the RUU with this old rom with a version number of 1.29.708.15, so I change the value to 2.17.708.7 )
Thanks ahmedaljaf for telling me to modify hbootpreupdate to makes JB downgrade works
8. save the file.
9. zip "android-info.txt", "boot_signed.img" and "system.img" and rename the zip to "rom.zip". (remember only zip the files, not the whole folder!)
10. place the "rom.zip" you just created to the "customRUU" folder
11. make sure your phone is still "unlock", remember to turn on USB Debugging, unplug the USB cable and reboot your phone, then goto fastboot mode and connect the USB cable.
(important, do the above to avoid error messages in RUU)
12. run the file "ARUWizard.exe" inside the folder "customRUU" (see the Attached Readme_Eng.pdf if the customRUU cannot display in correct language)
You can change the customRUU to English version by just delete or rename the language file "ARUWizard_Eng.lng" (Thanks ahmedaljaf for telling me this :good
13. follow the on screen instruction,
14. your phone should reboot and boot up with and old version of software.
15. restart the phone and go to fastboot mode.
16. extract the "recovery_signed.img" from your old "rom.zip" (not the rom.zip you create! ) and place it to some where.
17. flash the recovery by typing the following command "fastboot flash recovery recover_signed.img"
18. relock the phone
19. boot up the phone and try OTA
18. if the OTA download finish but fail to reboot to recovery update automatically, just manually boot to recovery and the update will be ok.
If you can return stock with this method, please reply and list the version here. And you can give me a "thanks" :good:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
There's NO way to downgrade hboot unless you have s-off.
Sent from my HTC One X using xda premium
ionut.micu said:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
Click to expand...
Click to collapse
They are somebody on chinese forum who use this method claimed he was able to do hboot downgrade through this method, but no one seem suceed so for.
Well, technically this method able to get you spoof ROM version because it check on your PC. While for hboot it validate the signature and version on the phone before upgrading itself. You can see the process if you push the firmware yourself via fastboot.
HebeGuess said:
They are somebody on chinese forum who use this method claimed he was able to do hboot downgrade through this method, but no one seem suceed so for.
Well, technically this method able to get you spoof ROM version because it check on your PC. While for hboot it validate the signature and version on the phone before upgrading itself. You can see the process if you push the firmware yourself via fastboot.
Click to expand...
Click to collapse
What if we hex edit the 0.95.0000 before we put it into the rom.zip to make it think that it's a newer version, will that brake the signature?
Sorry but I don't have the guts to try it myself
a good link
hokoonho said:
Who should read this post?
You have updated your One X to a newer version via OTA, then you want to restore the software/ return stock but the latest RUU is not available.
You have some basic skills to flash things using "fastboot"
Those who want to back to stock and wait for the JB OTA.
The concept behind.
1. Fool the RUU to make it believe that it is flashing the latest ROM, but actually, we are flashing an older version.
2. after that, boot up the phone with older version of software, then OTA and update the phone to latest software.
How to do that?
0. backup all your stuff including those in SD, all your stuff in your phone will be lost.
1. You have to download a "custom RUU" that can be found here (you can also found a rom that for One X for HK only).
http://pan.baidu.com/share/link?shareid=64762&uk=1042525484
If your phone is from other region, you may want to find the rom or RUU here http://www.htcruu.com
2. Download the ROM file, it should be in zip format. (You can also extract the rom file by running a RUU, just run the RUU, don't click anything and search the computer for "rom.zip") (In my case, I have an older version 1.29.708.15 rom extracted from RUU)
3. unzip the customRUU.zip to a folder, e.g. "customRUU"
4. unzip and extract "android-info.txt", "boot_signed.img" and "system.img" to a folder
5. open android-info.txt with "notepad" (notepad++ is highly recommended)
6. edit the value of"cidnum" to match your phone, e.g. ("HTC__622" for HK, "HTC__621" for Taiwan)
7. edit the value of "mainver" to the current software version your phone. e.g (I have OTA my phone to 2.17.708.7, but now I want to fool the RUU with this old rom with a version number of 1.29.708.15, so I change the value to 2.17.708.7 )
8. save the file.
9. zip "android-info.txt", "boot_signed.img" and "system.img" and rename the zip to "rom.zip". (remember only zip the files, not the whole folder!)
10. place the "rom.zip" you just created to the "customRUU" folder
11. make sure your phone is still "unlock"
12. run the file "ARUWizard.exe" inside the folder "customRUU"
13. follow the on screen instruction,
14. your phone should reboot and boot with and old version of software.
15. restart the phone and go to fastboot mode.
16. extract the "recovery_signed.img" from your old "rom.zip" (not the rom.zip you create! ) and place it to some where.
17. flash the recovery by typing the following command "fastboot flash recovery recover_signed.img"
18. relock the phone
19. boot up the phone and try OTA
18. if the OTA download finish but fail to reboot to recovery update automatically, just manually boot to recovery and the update will be ok.
Click to expand...
Click to collapse
link to custom ruu its dead. any alternative?
ionut.micu said:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
Click to expand...
Click to collapse
No, if you include the old hboot, the process will be fail.
Sent from my HTC One X using xda premium
darckreign1984 said:
link to custom ruu its dead. any alternative?
Click to expand...
Click to collapse
link updated, enjoy
Sent from my HTC One X using xda premium
or you could just cook yourself a flashable zip from the rom.zip. Then fastboot flash rec and boot. Chances are ics wont boot on the newer hboots. Still the ota can be flashed as update.zip maybe.
usefull for some case
bookmarked
BRILLIANT! Absolutely brilliant! Thanks a million hokoonho. This method worked like a treat on my HK_621 HOX which was running ARHD 9.7.2
unsucces
speedofheat said:
BRILLIANT! Absolutely brilliant! Thanks a million hokoonho. This method worked like a treat on my HK_621 HOX which was running ARHD 9.7.2
Click to expand...
Click to collapse
arhd 12 and hboot 1.28 - not working
the 10 min time to flash its useles.... nothing its flashing in this time
darckreign1984 said:
arhd 12 and hboot 1.28 - not working
the 10 min time to flash its useles.... nothing its flashing in this time
Click to expand...
Click to collapse
The method works well with ICS, even with other HTC model as well, but I am not sure if it still work will JB and latest hboot. But it won't kill your phone.
Sent from my HTC One X using xda premium
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
lukems said:
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
Click to expand...
Click to collapse
It's OK, The RUU may not be able to select the right language to display, but It still works, since the RUU only use adb and fastboot to finish its process, and all these adb and fastboot are run in English...
A brief translation was made for those cannot Open the customRUU in correct language. go to OP for the pdf file
hokoonho said:
It's OK, The RUU may not be able to select the right language to display, but It still works, since the RUU only use adb and fastboot to finish its process, and all these adb and fastboot are run in English...
I am translating the Text to English and will upload a guide, just follow the guide to click the buttons... wait for a few minutes please.
Click to expand...
Click to collapse
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
lukems said:
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
Click to expand...
Click to collapse
Could you provide a ling to the English version you've got ? Thanks
lukems said:
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
Click to expand...
Click to collapse
Don't relock at this moment, otherwise, you will not be able to flash the stock recovery. Unlock it first. Make sure USB debugging is on, then REBOOT to fastboot and start the RUU. Or...Try another USB cable, DON'T connect via a USB hub...
Sent from my HTC One X using xda premium
hokoonho said:
Don't relock at this moment, otherwise, you will not be able to flash the stock recovery. Unlock it first. Make sure USB debugging is on, then REBOOT to fastboot and start the RUU. Or...Try another USB cable, DON'T connect via a USB hub...
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Ok will try now.
Edit: I am now waiting for it to finish... we will see soon enough if it works.
Screenshot showing upgrade screen uploaded.
Edit 2: It completed successfully
build downgraded from 2.17.401.2 to 1.28.771.9
lukems said:
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
Click to expand...
Click to collapse
lukems said:
Ok will try now.
Click to expand...
Click to collapse
I have updated step 11. should disconnect the USB cable during reboot. If it still not work, restart both your phone and PC.
have m8 with cid htc__002
s on
need a ruu and stock recovery
bootloader unlocked
system status modifed
Download RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10 here : http://forum.xda-developers.com/showpost.php?p=56140330&postcount=1 - use the first link for the exe
1. put your device in bootloader/fastboot mode and connect to PC
2. relock bootloader - fastboot oem lock
3. Right click the RUU exe that you downloaded, select "run as administrator" .. wait for it to run, later there is a dialog box, accept, next, next, update, blablabla until it finish and your device rebooted... done.
Note : this will wipe everything on your internal storage. Make a backup of important files before you proceed.
AAA
mann got this error after downloading exe firmware
PC error ? Have you restart PC ?
Is the md5 correct ? 8cb9b5d9091164cd57b6e04459bee3c6
Is the size correct ? 1,537,519 KB
Do you follow step 1, 2, 3 accordingly ?
ckpv5 said:
PC error ? Have you restart PC ?
Is the md5 correct ? 8cb9b5d9091164cd57b6e04459bee3c6
Is the size correct ? 1,537,519 KB
Do you follow step 1, 2, 3 accordingly ?
Click to expand...
Click to collapse
ye bro i follow all steps bootloader is re locked and s-on with cid 002 but ruu not starting on any other pc also i restarts laptop and try diffrent ports etc but still no luck can i flash via zip file? in post ruu fastboot zip methood ?
Follow this thread on how to use RUU zip : http://forum.xda-developers.com/showthread.php?t=2735235
Note the important part is to use htc_fastboot.exe not the regular fastboot.exe
MAn Good nEws
mani can confirm that fastboot zip method works fine and now i have stock lollipop m8 but you have to take care of htc fastboot file just put in fastboot mode and your device will be flash back to stock with s-on yes yes :good::good:
problems
man all things are working fine but got only 2 problem yet
1>> a htc eye experiance pop ups again and again
>>> there is not auto brightness option in display now
Don't really understand your questions. Maybe screenshots can explain better what you're trying to say.
All Done
Man Iam flashed stock lollipop 5.01 but there were many bugs like auto brightness date lose on restart etc so i flash custom recovery and flash Android Revolution HD 34.6 Now Phone Running smooth
Getting the 2.10.401.1 step by step, crystal clean instructions.
This guide is mostly for the people who are stuck on lower versions where "About" says that there are no updates and that their device is up to date. Especially users who previously did 1.32.401.17 RUU. This version is know to have some major flaws and it tends not to read any updates, accept auto and manual OTAs nor zipped RUUs.
- Alright so I saw good number of people being stuck on European 1.32.401.17, 1.32.401.15 and 1.32.401.8 and unable to grab auto OTA and unable to manual OTA install due to various errors being thrown in twrp. There are also users who are having issues with SD transfers, transfers from PC to to phone especially when they transfer zipped RUU (0PJAIMG). Do not worry, I am going to help you with this. Just follow my simple steps. Note that you can forget about custom recoveries, microsds, system dumps, zipped ruus that "wont copy" to your device and others. You won't need any of these in my procedure. Simply ignore them. Now focus on my steps.
Step 1; Download the 1.32.401.17 exe RUU from here; DO NOT RUN THIS YET.
Step 2; Download the 1.40.401.8 0PJAIMG (ZIPPED RUU). Do not open/modify this yet.
Step 3; Backup your data on the phone such as contacts, SMS and so on. I personally use Wondershare mobilego for those things.
Step 4; Navigate to temp folder by typing %temp% in the search bar or C:\Users\Username\AppData\Local\Temp\ >>
Step 5; Under that folder you may or may not delete the files you don't need for easier navigation. Now this part is very important. Focus on that folder.
Step 6; Go back to 1.32.401.17 exe you downloaded in the step 1. Right click on it and Run it as admin. Once ran, it might take several minutes to open actual installer. Let it load all they where you see next/cancel. Stay there and do not cancel it or hit next.
Step 7; Go in your temp folder under step 4. You will see two newly created folders. You only need this one. Under that folder you should see another one with few random files. Go into other subfolder and navigate to the file named rom.zip. Delete this folder.
Step 8; Now go back to the file you downloded in step 2. Name that file to rom.zip and place it where you previously deleted the zip file from temp subfolder.
Step 9; Go back to the RUU installer interface and press next and do the procedure like you did with version x.17. You should see this. Now let the RUU installer updates your phone.
Step 10; Go under Settings > About > Updates. Now if you did all right you should see the magic: http://i.imgur.com/aqR4YwD.png >> Grab this new 100% fresh and stock OTA update and enjoy.
- I tested this few times on several devices and it works for every one of them. I am not aware of the other carrier users are having issues but same procedure can be done. Do not install custom recovery or root your device before you updated your device to 2.10. If in any case updater wont pick the 2.10 update you can flash your recovery and firmware from 1.40.401.8 version (prior to the 2.10 update). Do not panic if update is taking a while, it will reboot your device few times and thats it. To be on more safe side you can always flash the firmware once device is properly updated to 2.10.
*Flashing the firmware to 2.10*
Download from here and put it where your ADB interface is;
Put your device to download mode and open up the cmd where adb interface and latest firmware is.
do the following commands:
a.) fastboot oem rebootRUU
b.) fastboot flash zip firmware.zip
c.) fastboot reboot
- Make sure the phone is not rooted or tampered with. If something is not clear feel free to ask. I hope this helped to you.
Nikola
Nikolay82 said:
*Flashing the firmware to 2.10*
Download from here and put it where your ADB interface is;
Put your device to download mode and open up the cmd where adb interface and latest firmware is.
do the following commands:
a.) fastboot oem rebootRUU
b.) fastboot flash zip firmware.zip
c.) fastboot reboot
- Make sure the phone is not rooted or tampered with. If something is not clear feel free to ask. I hope this helped to you.
Nikola
Click to expand...
Click to collapse
S-ON Users should not try to do this if they weren't able to get and install the 2.XX.XXX.X uptdate before they get to this step. The firmware pack does not update the rom and it can only be flashed on S-ON devices if the bootloader is locked or relocked. HTC introduced a new "security feature" with the 2.XX.XXX.X firmware. This "feature" blocks the Bootloader Unlock if the option "OEM unlocking" in the Developer Options isn't activated. Without an up to date rom you won't be able to activate this option because it does not exist in earlier versions. Since there are no international 2.XX.XXX.X RUUs S-ON Users who follow this part of the guide and did not install the OTA beforehand would then be stuck with the 2.XX.XXX.X firmware and a 1.XX.XXX.X rom.
Except for that missing warning it's a very nice written guide.
I've tested this on S-ON device. I've successfully flashed 2.x for the sake of testing, both s-off and s-on. That part is probably not something many people will need, but its there just to be on safe side. The RUU itself will throw an error if there is a CID conflict anyway. Personally, I am not a fan of tampering with CID unless it is a must. User should be able to find proper RUU/OTA to match their CID.
I am working with the phones and I often have people who likes to tamper with their device. Good number of them will even write different CID, or even "universal" one just so they can go through RUU process and update. However, later they stuck on "no mobile data" unable to fix things. 99.9% of them failed to update their current model to latest so they resort to changing CID and putting in different country ROM just because it is newer. As for HTC introducing new security feature I wont go much into detail about it because it falls under hacking and reverse engineering in order to benefit from said action. Let's just say they never got around some crucial elements which pretty much made their security feature vain. Apple claimed similar thing. One day I sat down and put in the windows OS just because "tiles" were trend back then. I am yet to see a safe and totally secure update. Apple was the closest with their icloud and findmyphone but I decided for droid mostly because i wanted more freedom for what I pay. Cheers.
Nikolay82 said:
I've tested this on S-ON device. I've successfully flashed 2.x for the sake of testing, both s-off and s-on.
Click to expand...
Click to collapse
I never said that you won't be able to flash the firmware with S-ON. And please don't get me wrong. Your guide is very good.
The problem is that there is a special kind of xda readers which tends to skip some of the important steps that are described in instructions. If those people flash the firmware without installing the OTA beforehand they will be stuck with an unlockable, (re-)locked bootloader and a 1.XX.XXX.X rom on a 2.XX.XXX.X firmware. There are already plenty of threads which describe similair scenarios here on xda. That's the reason for the warning in my last post.
Hello everybody
I'm the owner of a HTC One M9 and I really love it! I'm kind of newbie on Android.
This is my case, I can't upgrade my firmware to 6.0.1 (or later) I'm still on Android 5.0.2 and I tried to install a cyanogenmod firm that kind of fit with my model... BUT! it start to have some many problems.. like the display starts to break the images and start to repetitive the image like an a glitch... when a phone call comes it turn off or restart it was like a dead phone... Then I install a MaximusHD 1.0.0 and it come back the same way it was but it returns to Android 5.0.2... I already unlock my phone and it's S-OFF via sunshine...
So, If you have some info that help me fix this (upgrade to Android 6.0.1 or later) or you have the same experience please leave your comment!
My data:
MODEL: htc_himawl
CID: LRA_001
MID: OPJA30000
Cheers!
Alvaro
Boot your phone into download mode, connect it to your computer and make sure ADB and FASTBOOT drivers are installed and working.
To ensure your device is connected, type "fastboot devices".
Your Bootloader needs to be unlocked, this is done with "fastboot oem unlock".
First step: Change your CID to SuperCID "fastboot writecid 11111111"
Second step: Change your MID to 0PJA1100 "fastboot writemid 0PJA1100"
Third step: Flash latest RUU for developer edition. To make sure you have the right RUU, usually it is x.x.617.x.
Kartoffelrudi said:
[...]First step: Change your CID to SuperCID "fastboot writecid 11111111"
Second step: Change your MID to 0PJA1100 "fastboot writemid 0PJA1100"
Third step: Flash latest RUU for developer edition. To make sure you have the right RUU, usually it is x.x.617.x.
Click to expand...
Click to collapse
Please don't give such advise if you don't know what you're talking about. The OP owns a CDMA device and the dev firmware is GSM. GSM and CDMA aren't compatible and you can't convert the one into the other due to their different partition layouts. In the worst case this can lead to unrecoverable damages.
Edit: This post isn't meant to be an offense. I just want to prevent the OP from doing something he/she could regret afterwards.
Edit 2 @cedricpixler: You'll need a windows PC if you want to use the following instructions. Win 10 and 8 (or 8.1) might not work whereas win 7 is always fine. I'm using win 10 myself without any problems but others have been reporting that they needed to use a win 7 PC.
Charge your phone to at least 50 %.
Go to HTC's US website and download the latest RUU for your SKU. Your current firmware is stated in Download Mode in the line that starts with "OS". The SKU are the numbers behind the second dot of the firmware version.
If not already done you should download and install the HTC Sync manager. Uninstall it directly, afterwards. This way you update the needed drivers to the latest version. If you keep the manager you might face some connectivity issues during the upcoming steps. Next you need to boot your phone to Download Mode and to connect it via USB (if possible use a 2.0 cable and port instead of 3.0) with your PC.
Disconnect your PC from the internet. Disable your antivirus program and your firewall and execute the RUU as an admin. In some cases the flashing process might take some time so don't worry if it hasn't finished after 10 minutes.
When the RUU has finished you can re-activate your av program and your firewall. Afterwards you can re-connect your PC with the internet. Your phone should be up to date now.
Not every step is actually essential but if you follow these instructions the most frequently occurring problems should be prevented.
Sidenote: Every problem you faced with custom roms is based on the difference between your current firmware and the base of the mentioned roms.
If you want to use a sense-based custom rom after you updated your firmware you need to re-flash the stock boot.img of your firmware after you flashed the rom. For non-sense-based roms like CM you need to flash thicklizards mono kernel. If you don't do this your phone won't recognize your sim card.
Sent from my HTC One S using XDA Labs
Thank you @Flippy498, I will take this steps you write and I will write here the results.
Somebody from LlaTooFer Maximus was helping me and send me this
"Well, your device is not capable with my custom rom due to different hardware. I recommend you to install Viper ROM prior that you need to update CID to VZW__001 and flash this full firmware https://www.androidfilehost.com/?fid=24651430732237625
After that you have to flash this RUU https://www.androidfilehost.com/?fid=24651430732238098
Once you do that you can install custom twrp recovery https://dl.twrp.me/hima/twrp-3.0.2-0-hima.img.html and custom rom http://forum.xda-developers.com/one-m9/development/rom-viperonem9-1-0-0-tweaks-hub-t3072773
Make sure you set Verizon during installation."
I tried the first step (installing the full firmware but this error comes up "C:\Program Files (x86)\platform-tools>fastboot flash zip 3.37.605.13_FULL_firmware.zip
target reported max download size of 800000000 bytes
sending 'zip' (41818 KB)...
OKAY [ 3.430s]
writing 'zip'...
(bootloader) HOSD CL#523158
(bootloader) ERR CID not matched
(bootloader) ERR [SD_UPDATE_ERR] CID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 7
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 7
(bootloader) [email protected]
FAILED (remote: 7: fail to flash via downloadzip)
finished. total time: 4.567s"
But they or he doesn't tell me whats going on.... or what to do next.. @Flippy498 do you know if this instructions could help to change my CID or MID..? and If my phone is CDMA can I re Write the CID or MID
cedricpixler said:
[...]"Well, your device is not capable with my custom rom due to different hardware. I recommend you to install Viper ROM prior that you need to update CID to VZW__001 and flash this full firmware https://www.androidfilehost.com/?fid=24651430732237625
After that you have to flash this RUU https://www.androidfilehost.com/?fid=24651430732238098
Once you do that you can install custom twrp recovery https://dl.twrp.me/hima/twrp-3.0.2-0-hima.img.html and custom rom http://forum.xda-developers.com/one-m9/development/rom-viperonem9-1-0-0-tweaks-hub-t3072773
Make sure you set Verizon during installation."[...]
Click to expand...
Click to collapse
Interesting, being a 24/7 Viper user since the One S was my main device I didn't know that Llabtoofer doesn't support CDMA devices at all.
My bad. I missed the fact that you don't have the Verizon CID. (I only looked at your MID and wasn't even aware that this MID belongs to more than one CID.) If you want to change your CID then you need to do so manually via fastboot use "fastboot oem writecid VZW__001" while your phone is booted to Download Mode and connected to your PC via USB. Flashing that firmware pack before the RUU shouldn't be necessary (but it shouldn't hurt either). Besides I would download the latest 605 RUU (605 is the Verizon SKU) directly from HTC. Afterwards it's your choice whether you stay on stock or whether you want to install the latest Viper rom.
The MID of a CDMA device should never be changed. Even the sprint firmware (CDMA, too) isn't compatible with Verizon devices and vice versa. Changing the CID should be fine, though.
Sent from my HTC One S using XDA Labs
Update: Well I save my phone! the fact is that I just change the CID to VZW__001 and practically I followed the instructions I posted here and flash the last ViperOne firm and Kaboom! I have the latest firmware and it's so stable! If any one has the problem I had just ask me how I do.
Cheers!
@Flippy498 I see that Nugat comes for HTC M9, did you know if there is any official 7.0 stock from HTC? for CDMA phones like mine? Cheers!
Only the dev edition (GSM) got the update yet.
Last year Android M got released one day before Christmas for that sku and most of the rest of the world received it between mid January and the end of February 2016. Therefore I think that the unbranded skus might get the update around the end of this year (if we're lucky) or at the beginning of 2017. Branded skus like the CDMA ones always need a little more time than the unbranded ones due to all the bloat the carriers want HTC to add to the system.
I don't have a direct link at hand but there is an article on the xda portal which explains in general (not HTC-specific) why carrier-branded phones need to wait that much for their updates. If I remember correctly it got published sometime during the summer.
Sent from my HTC One M9 using XDA Labs