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.
Related
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.
Hi guys,
Apologies for starting a new thread, but I've spent the last day trying to root my DHD without success. I've tried everything I could from searching through similar problems on the forums but I'm getting stuck and very frustrated and need some help please.
My phone:
Vodafone Australia branded
Android version 2.3.5
Sense 3.0
Software number 3.12.178.2
HBOOT-2.00.0027
My noob attempts so far:
1. First I did a factory reset
2. Then I tried to install Miui following this link - http://en.miui.com/a-57.html & this tutorial - http://www.youtube.com/watch?v=wNoMelTPvok, but it got stuck installing VISIONary.apk and wouldn't do a temp root.
3. I then found this forum & started reading up
4. I tried the EasyAceRootTool but get this error;
Obtaining Unlock Token
< waiting for device >
... INFO[ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.057s
5. Upon further reading it seems I needed to update my hboot, so I got the correct RUU from HTCdev site, but I get the message - Error 191 when using RUU - Rom not supported.
This is where I'm stuck and all my attempts to update the hboot have failed, despite reading through similar problems on the forum. So is my only option to create a gold card with this link? - http://forum.xda-developers.com/showthread.php?t=970157 Do I use my phones sdcard or do I need a spare one?
Hopefully there's something obvious I'm doing wrong and would really appreciate any help thanks.
Rob
yokelhama said:
Hi guys,
Apologies for starting a new thread, but I've spent the last day trying to root my DHD without success. I've tried everything I could from searching through similar problems on the forums but I'm getting stuck and very frustrated and need some help please.
My phone:
Vodafone Australia branded
Android version 2.3.5
Sense 3.0
Software number 3.12.178.2
HBOOT-2.00.0027
My phone is 3 years old and I wanted to give it a new lease of life with a new ROM. First I did a factory reset, then tried the EasyAceRootTool but get this error;
Obtaining Unlock Token
< waiting for device >
... INFO[ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.057s
Upon further reading it seems I need to update my hboot, so I got the correct RUU from HTCdev site, but I get the message - Error 191 when using RUU - Rom not supported. This is where I'm stuck and can't find any further solutions. Is my only option to create a gold card with this link? - http://forum.xda-developers.com/showthread.php?t=970157 Do I use my phones sdcard or do I need a spare one?
Hopefully there's something obvious I'm doing wrong and would really appreciate any help thanks.
Rob
Click to expand...
Click to collapse
No, you can use the easy ace root tool script that creates the goldcard image. Then use simple gold card tool to patch the SD card. Link is in my signature.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
glevitan said:
No, you can use the easy ace root tool script that creates the goldcard image. Then use simple gold card tool to patch the SD card. Link is in my signature.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Ok, so I run GC.cmd as admin first, then follow the steps?
So I've managed to create a succesful goldcard thanks, but now I need to "flash it in the PD98IMG.zip way". Not 100% sure the process for that, so about to have a read around.
I'm still confused about how to "flash it in the PD98IMG.zip way" as referenced here - http://forum.xda-developers.com/showthread.php?t=2169515 I don't understand what I'm menat to download, from where, or where to put or run it?
I managed to run EasyAceRoot.cmd as admin and got an unlock token. I put that into the token folder, but the command prompt window just displayed 'waiting for device' and nothing happened.
Now, I'm trying this step - http://www.htcdev.com/bootloader/unlock-instructions/page-4/ but it wants me to download a 440mb sdk file, was I supposed to have all this installed first, don't recall reading that anywhere.
So, at this stage I have a goldcard & unlock token, but my phone is still not rooted. Please any more help?
Bah, I'm ready to give up, gonna take a break for awhile. I'm getting a Error[170] Usb connection error now.
About to head to bed in Aus, I've spent all day going round in circles here, so hopefully someone will have some help in the morning for me.
Basically I'm stuck at these steps with no root still:
IF YOUR BUILD VERSION IS NOT SUPPORTED TO UPDATE THEN:
1. Create a goldcard using this tool: http://d-h.st/VMw, once you have the .img file patch it using the SimpleGoldCard Tool included in the tools folder. (you need a working phone for this)
DONE
2. Find a RUU which main version is supported and higher than yours and flash it in the PD98IMG.zip way, that is what is the goldcard for. If you have a .exe RUU, then extract the rom.zip file using this method: http://www.xda-developers.com/xda-tv...-an-ruu-xdatv/
I've tried various RUU's changing the ROM.zip to PD98IMG.zip on the sdcard, but they all fail in hboot. I tried the RUU that auto downloads with EasyAceRootTool, the stock Vodafone Australia ROM (http://forum.xda-developers.com/showthread.php?t=842722) & even one from shipped-roms, but they give this message "Main version is older! Update Fail!"
3. Re run the tool and you will be able to update the hboot and unlock it
I've tried this also but get the following message "Error[170] Usb connection error". I have pdanet, htcsync & android sdk tools all installed.
I even tried to downgrade to an earlier version using this guide but couldn't pass the final step.
Any help at all is greatly greatly appreciated, please what am I doing wrong?
Cheers
Rob
yokelhama said:
About to head to bed in Aus, I've spent all day going round in circles here, so hopefully someone will have some help in the morning for me.
Basically I'm stuck at these steps with no root still:
IF YOUR BUILD VERSION IS NOT SUPPORTED TO UPDATE THEN:
1. Create a goldcard using this tool: http://d-h.st/VMw, once you have the .img file patch it using the SimpleGoldCard Tool included in the tools folder. (you need a working phone for this)
DONE
2. Find a RUU which main version is supported and higher than yours and flash it in the PD98IMG.zip way, that is what is the goldcard for. If you have a .exe RUU, then extract the rom.zip file using this method: http://www.xda-developers.com/xda-tv...-an-ruu-xdatv/
I've tried various RUU's changing the ROM.zip to PD98IMG.zip on the sdcard, but they all fail in hboot. I tried the RUU that auto downloads with EasyAceRootTool, the stock Vodafone Australia ROM (http://forum.xda-developers.com/showthread.php?t=842722) & even one from shipped-roms, but they give this message "Main version is older! Update Fail!"
3. Re run the tool and you will be able to update the hboot and unlock it
I've tried this also but get the following message "Error[170] Usb connection error". I have pdanet, htcsync & android sdk tools all installed.
I even tried to downgrade to an earlier version using this guide but couldn't pass the final step.
Any help at all is greatly greatly appreciated, please what am I doing wrong?
Cheers
Rob
Click to expand...
Click to collapse
Try this.
http://forum.xda-developers.com/showpost.php?p=38947050&postcount=10
download the hbootupdate_kit zip and the rom.zip from there.Extract the hbootupdatekit in any folder you'd like, and place the rom.zip in C:
Run the HBOOT Update .bat and see what it tells you.I've used this to update to .0029 numerous times and it has worked.
Iydryne ftrong
Steam. said:
Try this.
http://forum.xda-developers.com/showpost.php?p=38947050&postcount=10
download the hbootupdate_kit zip and the rom.zip from there.Extract the hbootupdatekit in any folder you'd like, and place the rom.zip in C:
Run the HBOOT Update .bat and see what it tells you.I've used this to update to .0029 numerous times and it has worked.
Click to expand...
Click to collapse
Hi, thanks for your help.
This is what happens, I waited for 10mins but no change. The phone screen is black with the HTC logo displayed.
Success! I finally got it all sorted, but not really sure how lol.
In hboot this morning it says I'm updated, ran the easyacetool and everything finally worked perfectly.
Hello all. I'm sorry for my English, i'm from Poland.
Okay, i can't do anythink with my HTC HDH. Below is spec of my phone:
Code:
Wersja systemu Android:
2.3.5
Wersja HTC Sense:
3.0
Numer oprogramowania:
3.13.771.2
Wersja jądra:
2.6.35-10.g931a37e
[email protected] #1
Wed Nov 9 14:04:03 CST 2011
Wersja pasma podst.:
12.65.60.29U_26.14.04.28_M
Numer kompilacji:
3.13.771.2 CL208029 release-keys
Wersja przeglądarki:
WebKit/533.1
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
RADIO-26.14.04.28_M
I used many guides like:
http://forum.xda-developers.com/showthread.php?t=2221039 (Can't unlock bootloader, look below:
#1 http://pbrd.co/1cMCkIv
#2 http://pbrd.co/1cMCq2S
#3 http://pbrd.co/1cMCr6Y
Huh?!)
http://forum.xda-developers.com/showthread.php?t=857537 - the same...
AAHK says ~all is okay~ - but it isn't.. Still've 2.3.5 / 3.0 S-ON UHH.
Can anyone help me with VNC / TeamViewer? PLEASE!
I'm waiting for msg!
You need to find a compatible RUU to update you bootloader from .27 to .29. Then unlock your bootloader, either using HTCDEV or the Easy Ace Unlock Tool or the Easy Ace Root Tool. AAHK is retired; the only way to get S-Off now is manually.
I'll send you big beer if you'll help me to find compatible RUU for:
3.13.771.2
maybe you can try this AAHK2 script..this is a simple way and complete script that make your phone completed gain s-off and have custom recovery too,
but still need the right ruu too if the script needed to downgrade the phone first..
hopefully can help..
I don't believe.. Nobody hasn't RUU for 3.13.772.2 ? God...
On the HTC DEV BOOTLOADER - RUU DOWNLOADS is the RUU for my phone:
Code:
H3G UK 3.13.771.2 PD9810000
But look:
Code:
"Verify that you want to update the ROM version:
From:
Image Version:
3.13.771.2
To:
Image Version:
3.13.00"
Code:
"ERROR [190]: ROM IS NOT UPDATED
Your ROM version is not the latest version.
Please upgrade to 3.13.405.1 to apply this RUU to be able to unlock your bootloader.
On your phone, go to Menu > Settings > About phone > Software updates > Check now.
After you have updated, please run the RUU again to upgrade your HBOOT to unlock your phone. We apologize for the inconvenience."
Why, when i'm downloading "the compatible" RUU for My HTC HDH it show these alerts?!
Seentol said:
I don't believe.. Nobody hasn't RUU for 3.13.772.2 ? God...
On the HTC DEV BOOTLOADER - RUU DOWNLOADS is the RUU for my phone:
Code:
H3G UK 3.13.771.2 PD9810000
But look:
Code:
"Verify that you want to update the ROM version:
From:
Image Version:
3.13.771.2
To:
Image Version:
3.13.00"
Code:
"ERROR [190]: ROM IS NOT UPDATED
Your ROM version is not the latest version.
Please upgrade to 3.13.405.1 to apply this RUU to be able to unlock your bootloader.
On your phone, go to Menu > Settings > About phone > Software updates > Check now.
After you have updated, please run the RUU again to upgrade your HBOOT to unlock your phone. We apologize for the inconvenience."
Why, when i'm downloading "the compatible" RUU for My HTC HDH it show these alerts?!
Click to expand...
Click to collapse
Here is your link to 3.13.415.2 if it means something to you:
http://hotfile.com/dl/152413307/1ed..._26.14.04.28_M_release_227469_signed.exe.html
Okay, thank you! I'm downloading it now. Soo, do you think it'll help me with update my HBOOT?
@edit
Error [131]: "Client identificator error"... Uh :/
Seentol said:
Okay, thank you! I'm downloading it now. Soo, do you think it'll help me with update my HBOOT?
@edit
Error [131]: "Client identificator error"... Uh :/
Click to expand...
Click to collapse
Your best bet maybe create a goldcard and flash unbranded ruu
Sent from my Desire HD using xda premium
Okay, i've got ~29 HBOOT version. What now? The best metod to fast and safe got some 4.1.2/4.2.2 rom?
Seentol said:
Okay, i've got ~29 HBOOT version. What now? The best metod to fast and safe got some 4.1.2/4.2.2 rom?
Click to expand...
Click to collapse
have you already tried the AAHK2 script the link that i give to you before...?
with that script you don't need to unlock bootloader with htcdev unlock first..
you just need find the right ruu (PD98IMG-GB1.zip or PD98IMG-GB2.zip or else until GB9.zip) that suitable with your phone cidnum to downgrade first..and then repeated the AAHK2 script to completed all process..
check your cidnum
start your phone in fastboot mode
connect your phone with pc
open andoid SDK in cmd
then type "fasboot getvar all"
in the line "INFO cidnum" that's your cidnum... (sample HTC__001)
sample if your cidnum HTC__001 then download ruu PD98IMG-GB2.zip to use downgrade process first required by AAHK2 script before repeated AAHK2 script to completed all process..
last process after completed and success AAHK2 script..you must flashing the modified/ rooted ruu by Phiber2000 before installing any custom rom..
hopefully this can help...
I'm sorry, it didn't work :/. Cmd terminal say all's okay, but phone is still S-ON...
Now other questions (i didn't found reply for questions):
HBOOT-2.00.0029
Android 2.3.5
HTC Sense 3.0
S-ON
I'll unlock bootloader, so i'm going to htc/dev/bootloader for my ruu (3.13.771.2), downloading, then try to install. BUT - RUU Error [191].
I did Goldcard by "~Goldcard helper~" but what's the next step?
Seentol said:
I'm sorry, it didn't work :/. Cmd terminal say all's okay, but phone is still S-ON...
Now other questions (i didn't found reply for questions):
HBOOT-2.00.0029
Android 2.3.5
HTC Sense 3.0
S-ON
I'll unlock bootloader, so i'm going to htc/dev/bootloader for my ruu (3.13.771.2), downloading, then try to install. BUT - RUU Error [191].
I did Goldcard by "~Goldcard helper~" but what's the next step?
Click to expand...
Click to collapse
you mean you've already running that script for downgrade first and then running 2nd time that script again for completed process with the right step by step process..but the result of the phone still S-ON..?
by the way...i don't have experiences with htcdev unlock but about the goldcard what i know is..if you already had a goldcard now you can continued installing ruu..
I'm sorry. I din't sleep last ~50h. I've got token and i unlocked bootloader. What now for Root and install some rom like cm 10.0?
Seentol said:
I'm sorry. I din't sleep last ~50h. I've got token and i unlocked bootloader. What now for Root and install some rom like cm 10.0?
Click to expand...
Click to collapse
now your phone is already anlocked..then next you must installing custom recovery first..
to do that..
1. you must download recovery.zip from here then rename it as PD98IMG.zip
2. copy that file to the root of your sd card (please make sure nothing any zip file in the root of your sd card)
3. reboot your phone to bootloader and wait until hboot detect your zip file and ask you to install update...then you can confirm yes with volume up.. then wait until finish..
4. when finish...it will ask you to press the power to confirm reboot..so confirm to reboot..
5. now you have success intalling custom recovery... (don't forget to delete PD98IMG.zip from your sd card after success installing recovery)
6. now you can installing any custom rom but don't forget..because the status of your bootloader is still s-on so..you must always flashing the boot.img too through fastboot after every installing new custom rom from the rom.zip it self..
hopefully this can help..and you can enjoy the sleep after this...
It didn't work.. I've only one file, that recovery.zip renamed by me to PD98IMG.zip in root of sd card. I turn on the hboot menu, i'm waiting and nothing happen. Any ideas? ._. Huh, i hate that DHD... Or he doesn't love me.
Seentol said:
It didn't work.. I've only one file, that recovery.zip renamed by me to PD98IMG.zip in root of sd card. I turn on the hboot menu, i'm waiting and nothing happen. Any ideas? ._. Huh, i hate that DHD... Or he doesn't love me.
Click to expand...
Click to collapse
ok..there is still 2nd method...
1. on your computer..extract recovery.zip file..
2. delete a PD98IMG.zip from the sd card you put earlier..then copy recovery.img that you already extracted to your sdk/ adb folder..
3. reboot your phone to bootloader..select fastboot
4. connecting your phone with your computer
5. open sdk folder through cmd..then type "fastboot flash recovery recovery.img" wait until finish..
6. reboot to bootloader again and check your recovery
7. if success now your phone have 4EXT Recovery Tuch
by the way may i know what a brand of you sd card..?
maybe this is cause of HBOOT can't read PD98IMG.zip file because of some brand of the sd card can't compatible reading from HBOOT..
hopefully this work..
Okay, i've got ****UNLOCKED****
The last question.
I've S-ON RL and cyanogenmod10.1.zip + gapps. How can i flash the kernel? I tried to use Kernel Update Utility, but i've there 3 options:
- Select a cwm zip (i don't look at this)
* Select Kernel
* Select Kernel Modules.
Okay, i selected kernel, but i can't go to the next step, because it can't be done without "kernel modules" what's it?
(Ye, i've CWM, etc)
@edit
in cmd.exe "fastboot flash boot boot.img" for kernel didn't work. Uh, one step to get free from that hated (by me) sense...
Seentol said:
Okay, i've got ****UNLOCKED****
The last question.
I've S-ON RL and cyanogenmod10.1.zip + gapps. How can i flash the kernel? I tried to use Kernel Update Utility, but i've there 3 options:
- Select a cwm zip (i don't look at this)
* Select Kernel
* Select Kernel Modules.
Okay, i selected kernel, but i can't go to the next step, because it can't be done without "kernel modules" what's it?
(Ye, i've CWM, etc)
@edit
in cmd.exe "fastboot flash boot boot.img" for kernel didn't work. Uh, one step to get free from that hated (by me) sense...
Click to expand...
Click to collapse
just extracted boot.img from cyanogenmod10.1.zip..then copy sdk/ adb folder that you have..
then reboot your phone to bootloader..then select "FASTBOOT"..
connect your phone to the computer until in the phone "FASTBOOTUSB"
open sdk through cmd and then type command "fastboot flash boot boot.img"...finish and done..
Thank you very much!
I've now Cyanogenmod 10.1 nightly + gapps.
Finally - rooted, fast phone
Seentol said:
Thank you very much!
I've now Cyanogenmod 10.1 nightly + gapps.
Finally - rooted, fast phone
Click to expand...
Click to collapse
you're welcome..
glad to hear that..hope you can always enjoy your dhd now..
As the title states, I recently woke up to find my phone in the fast boot menu.
I have no idea what's going on or why it's in this state, as I've done nothing to it.
No root. No custom recovery. Nothing.
I simply put it down before I went to bed and that was all.
I've tried going into the 'hboot' option and selecting Fastboot, recovery, and even Factory Reset as a final option. All that happens whenever I've selected any option is that the phone reloads back into fastboot. The splash screen before hand is of 3 android mascots on skateboards.
I've seen some other threads here with similar issues, yet none like mine.
They've all seemed to be rooted phones, with or without custom recoveries on them.
I've no idea what's going on with the phone and would really appreciate any help or advice.
What is your OS number on the bootloader screen?
redpoint73 said:
What is your OS number on the bootloader screen?
Click to expand...
Click to collapse
The OS Number is 4.20.531.5
ViaJCE said:
The OS Number is 4.20.531.5
Click to expand...
Click to collapse
So if its never been modded, the bootloader screen should also say LOCKED near the top and SOFTWARE OFFICIAL (or something like that). Can you confirm those?
If so, you can try to run the RUU and see if that helps the issue. Just download the RUU to a Windows PC (Win7 and USB 2.0 for best results), connect the phone to the PC in bootloader-fastboot mode, and double-lock the RUU executable to run it. You'll also need to have HTC Sync installed on the PC.
Find the 4.20.531.5 RUU here: http://forum.xda-developers.com/showthread.php?t=2714456
redpoint73 said:
So if its never been modded, the bootloader screen should also say LOCKED near the top and SOFTWARE OFFICIAL (or something like that). Can you confirm those?
If so, you can try to run the RUU and see if that helps the issue. Just download the RUU to a Windows PC (Win7 and USB 2.0 for best results), connect the phone to the PC in bootloader-fastboot mode, and double-lock the RUU executable to run it. You'll also need to have HTC Sync installed on the PC.
Find the 4.20.531.5 RUU here: http://forum.xda-developers.com/showthread.php?t=2714456
Click to expand...
Click to collapse
Yeah, as you said, it says
*** Software status: Official ***
*** LOCKED *** (highlighted in purple) on top in the menu.
I have actually tried using the RUU software before. The times that I've tried using it, it attempts to reboot the phone back into the fastboot menu, which turns it off. The phone never turns back on in time, for as soon as it does, the software says it's unable to do it.
Though I haven't tried that double-lock method you mentioned. And I do have the HTC Sync software installed as well.
ViaJCE said:
Though I haven't tried that double-lock method you mentioned.
Click to expand...
Click to collapse
It should say "double click" (to run the RUU program). Not sure if there was some runaway spellcheck going on there, when I posted. But its not any different from what you've tried.
Another method you can try, is to download the RUU zip from Post #4 of the same thread: http://forum.xda-developers.com/showpost.php?p=51836733&postcount=4
Rename to 0P6BIMG.zip, copy to SD card, insert card into phone, and reboot into bootloader, and it should automatically install it.
redpoint73 said:
It should say "double click" (to run the RUU program). Not sure if there was some runaway spellcheck going on there, when I posted. But its not any different from what you've tried.
Another method you can try, is to download the RUU zip from Post #4 of the same thread: http://forum.xda-developers.com/showpost.php?p=51836733&postcount=4
Rename to 0P6BIMG.zip, copy to SD card, insert card into phone, and reboot into bootloader, and it should automatically install it.
Click to expand...
Click to collapse
Thanks for the replies and the help so far. I clicked on the link with the 4.20.531.4 ROM, yet it no longer seems to be there.
ViaJCE said:
Thanks for the replies and the help so far. I clicked on the link with the 4.20.531.4 ROM, yet it no longer seems to be there.
Click to expand...
Click to collapse
Search to see if it was posted elsewhere (4.20.530.4 RUU in zip format). Otherwise, another option is to run the RUU.exe on your PC, then look in your Windows temp folder for a ROM.zip, which is the same thing (zip format RUU).
redpoint73 said:
Search to see if it was posted elsewhere (4.20.530.4 RUU in zip format). Otherwise, another option is to run the RUU.exe on your PC, then look in your Windows temp folder for a ROM.zip, which is the same thing (zip format RUU).
Click to expand...
Click to collapse
Alright, so I've gotten the rom.zip from the ruu.exe.
I've renamed it as you said to, moved it to an SD card, and popped that SD card into the M8.
I turned on the M8 and it went into the fastboot menu as expected. I then selected the hboot option.
It then started to read the zip and flash it, then asking if I want to start the update.
After selecting yes, the bootloader started updating, but the partition update failed.
it read,
[1] BOOTLOADER - Fail-PU
*then after a list of 15 other items
Partition update fail!
Update Fail!
Device halted due to large image update fail!
Press <power> to reboot.
Hi,
You should unlock your bootloader and flash recovery to get it back in stock if the RUU don't work..
BelDev said:
Hi,
You should unlock your bootloader and flash recovery to get it back in stock if the RUU don't work..
Click to expand...
Click to collapse
Thanks for the suggestion, though I've already tried that. It hadn't worked. Wasn't able to do it: I forgot the error it gave me
@ViaJCE
If you got a error, verify if you have all drivers installed and if adb detect your device..
BelDev said:
Hi,
You should unlock your bootloader and flash recovery to get it back in stock if the RUU don't work..
Click to expand...
Click to collapse
This is false. Stock recovery is not needed for RUU, but it is for OTA (which RUU and OTA are two very different things).
In any case, it doesn't appear the device was ever modded (to not have the stock recovery) in the first place.
---------- Post added at 09:13 AM ---------- Previous post was at 09:08 AM ----------
ViaJCE said:
[1] BOOTLOADER - Fail-PU
*then after a list of 15 other items
Partition update fail!
Update Fail!
Device halted due to large image update fail!
Press <power> to reboot.
Click to expand...
Click to collapse
Can you post the whole install log output?
Failure to write partitions with the proper RUU (locked bootloader, stock device), plus the spontaneous OS failure that started this whole discussion, to me implies a sudden hardware failure (bad emmc, etc.) and you might be out of luck here.
*bump*
redpoint73 said:
This is false. Stock recovery is not needed for RUU, but it is for OTA (which RUU and OTA are two very different things).
In any case, it doesn't appear the device was ever modded (to not have the stock recovery) in the first place.
---------- Post added at 09:13 AM ---------- Previous post was at 09:08 AM ----------
Can you post the whole install log output?
Failure to write partitions with the proper RUU (locked bootloader, stock device), plus the spontaneous OS failure that started this whole discussion, to me implies a sudden hardware failure (bad emmc, etc.) and you might be out of luck here.
Click to expand...
Click to collapse
Posting everything the phone says when it's going through the process will be hard, but I'll try to anyways.
redpoint73 said:
This is false. Stock recovery is not needed for RUU, but it is for OTA (which RUU and OTA are two very different things).
In any case, it doesn't appear the device was ever modded (to not have the stock recovery) in the first place.
---------- Post added at 09:13 AM ---------- Previous post was at 09:08 AM ----------
Can you post the whole install log output?
Failure to write partitions with the proper RUU (locked bootloader, stock device), plus the spontaneous OS failure that started this whole discussion, to me implies a sudden hardware failure (bad emmc, etc.) and you might be out of luck here.
Click to expand...
Click to collapse
From selecting hboot on the Fastboot menu, it then says,
SD Checking
No gift file
Loading . . . [0P6BDIAG.zip]
No Image!
Loading . . . [0P6BDIAG.nbh]
No image or wrong image!
Loading . . . [0P6BDIMG.zip]
then it finishes loading, to then say 'flashing zip'
some other text flies by on the screen to fast to be read, then it says 'Checking Hboot Version . . .'
Then it says,
Parsing . . . [SD ZIP]
Reset HTC Debug Flag . . .
[ 1 ] Bootloader
[ 2 ] Splash1
[ 3 ] Trust_Zone
[ 4 ] RPM
[ 5 ] ADSP
[ 6 ] PG2FS_SPCUSTOM
[ 7 ] WCNSS
[ 8 ] TP (2)
[ 9 ] SENSOR HUB
[ 10 ] SDI
[ 11 ] SBL1 (4)
[ 12 ] Recovery
[ 13 ] Boot
[ 14 ] Radio_V2
[ 15 ] Radio_CUST
Do you want to start update?
After clicking yes, it begins to update the bootloader
[ 1 ] Bootloader - Updating
but then that fails, saying
[ 1 ] Bootloader - Fail - PU
The at the bottom of the list, it states,
Partition update fail!
Update Fail!
Device halted due to large image update fail!
Press <power> to reboot.
Unfortunately, the full output doesn't shed any additional light. Based on the collection of symptoms, I'd tend to think you have a hardware failure. Sorry . . .
redpoint73 said:
Unfortunately, the full output doesn't shed any additional light. Based on the collection of symptoms, I'd tend to think you have a hardware failure. Sorry . . .
Click to expand...
Click to collapse
Well, thank you for trying to help out anyways. I'll continue to exhaust any and all additional options I have left, as I still think that the phone can be saved. If I'm proven wrong, and there's nothing that can be done, then I'll give up.
Still got hope though
Hi all,Any help will be greatly received,
my stock 10 started having random lock ups,freezes and reboots ,
it has now even decided to give itself a factory reset on its own WTF?
so i thought software has gone corrupt, so ive downloaded the correct firmware and put it on the sd,when i boot into download
mode from bootloader it says sd not mounted?? tried formatting sd card to fat 32 and ntfs.
it also has lost its recovery as just get the red exclamation icon,
and because it factory reset itself without me entering my pin google has set the 24hrs timer so i cant even get further than the google sign in page to root it and flash it that way...
please help
cheers
Markieboy said:
Hi all,Any help will be greatly received,
my stock 10 started having random lock ups,freezes and reboots ,
it has now even decided to give itself a factory reset on its own WTF?
so i thought software has gone corrupt, so ive downloaded the correct firmware and put it on the sd,when i boot into download
mode from bootloader it says sd not mounted?? tried formatting sd card to fat 32 and ntfs.
it also has lost its recovery as just get the red exclamation icon,
and because it factory reset itself without me entering my pin google has set the 24hrs timer so i cant even get further than the google sign in page to root it and flash it that way...
please help
cheers
Click to expand...
Click to collapse
Have you checked your Google account on a PC or other device ? check all is well there first
Lol flash twrp and install any rom.
if you are ok with losing all your data you can use a RUU to restore the system from your current state.
1. download this: https://androidfilehost.com/?fid=24671318762849095
2. rename the zip file to 2PS6IMG.zip
3. put it on your SD card and put it in your phone.
4. boot into download mode, it will recognise the zip and begin the ruu process.
5. once it's finished it will reboot; it might take a little longer than usual to boot but just wait about 5min or so.
done.
at a guess i'd say that if it doesn't work or it happens again then your board is probably cooked and you should start looking for a new phone...
---------- Post added at 07:50 PM ---------- Previous post was at 07:48 PM ----------
also when booting into stock recovery the red exclamation mark screen is normal; what you have to do is hold down the power button and press vol up and the recovery menu should appear.
diagonals said:
if you are ok with losing all your data you can use a RUU to restore the system from your current state.
1. download this: https://androidfilehost.com/?fid=24671318762849095
2. rename the zip file to 2PS6IMG.zip
3. put it on your SD card and put it in your phone.
4. boot into download mode, it will recognise the zip and begin the ruu process.
5. once it's finished it will reboot; it might take a little longer than usual to boot but just wait about 5min or so.
done.
at a guess i'd say that if it doesn't work or it happens again then your board is probably cooked and you should start looking for a new phone...
---------- Post added at 07:50 PM ---------- Previous post was at 07:48 PM ----------
also when booting into stock recovery the red exclamation mark screen is normal; what you have to do is hold down the power button and press vol up and the recovery menu should appear.
Click to expand...
Click to collapse
Are you sure this is the proper RUU for him? First of all, that RUU is super old. Probably too old for the OP to use unless he's S-Off (you can't go backwards with firmware while S-On)
Second of all, you don't even know which model he has. That RUU is for WWE/European. It won't work on US Unlocked/Sprint/Verizon/o2/T-mo etc...... but ONLY on a WWE branded device. You need matching MID and CID for the RUUs to work.
@Markieboy don't use that RUU. Boot to download mode and post here what it says next to "OS" and I or someone else can provide you with the appropriate one to use (although I'm not sure if it will work in this case).
Try this: If you can boot to download mode, you should be able to flash TWRP via fastboot (your bootloader is unlocked, correct?).
Then boot to TWRP > advanced > file manager then navigate to /data/system/ and delete the locksettings.db file. This will disable your lockscreen PIN/password.
xunholyx said:
Are you sure this is the proper RUU for him? First of all, that RUU is super old. Probably too old for the OP to use unless he's S-Off (you can't go backwards with firmware while S-On)
Second of all, you don't even know which model he has. That RUU is for WWE/European. It won't work on US Unlocked/Sprint/Verizon/o2/T-mo etc...... but ONLY on a WWE branded device. You need matching MID and CID for the RUUs to work.
@Markieboy don't use that RUU. Boot to download mode and post here what it says next to "OS" and I or someone else can provide you with the appropriate one to use (although I'm not sure if it will work in this case).
Try this: If you can boot to download mode, you should be able to flash TWRP via fastboot (your bootloader is unlocked, correct?).
Then boot to TWRP > advanced > file manager then navigate to /data/system/ and delete the locksettings.db file. This will disable your lockscreen PIN/password.
Click to expand...
Click to collapse
Hello, i have exactly the same issue battery health is like 65 percent when i look at accubattery and it crashes often wen battery is lower than 25% or so. It closes and never opens. Enters a boot loop. Sometimes it shuts down and enters boot loop too. Here is information that i see at download mode :
hTC download mode
*** LOCKED ***
htc_pmeuhl PVT S-ON
LK-1.0.0.0000
RADIO - [email protected]
OpenDSP - v.20.0.8996.00007_0809
OS-2.41.401.41
Aug 2 2017, 12:18:15(857212)
system info
show barcode
bla bla
Security checking falied GT_CONNECT_FAI
L
Security Warning
if you flash this phone with any rom bla bla
SD Mounted
OTG NOT MOUNTED
File NOT FOUND
xunholyx said:
Are you sure this is the proper RUU for him? First of all, that RUU is super old. Probably too old for the OP to use unless he's S-Off (you can't go backwards with firmware while S-On)
Second of all, you don't even know which model he has. That RUU is for WWE/European. It won't work on US Unlocked/Sprint/Verizon/o2/T-mo etc...... but ONLY on a WWE branded device. You need matching MID and CID for the RUUs to work.
@Markieboy don't use that RUU. Boot to download mode and post here what it says next to "OS" and I or someone else can provide you with the appropriate one to use (although I'm not sure if it will work in this case).
Try this: If you can boot to download mode, you should be able to flash TWRP via fastboot (your bootloader is unlocked, correct?).
Then boot to TWRP > advanced > file manager then navigate to /data/system/ and delete the locksettings.db file. This will disable your lockscreen PIN/password.
Click to expand...
Click to collapse
Hi no unfortunately the phone is bog standard I haven't unlocked the bootloader or anything. It's a non branded wwe firmware version....
i'd say pay for the s-off, there's no other way to fix your phone. but i still think your board is cooked.
Markieboy said:
Hi no unfortunately the phone is bog standard I haven't unlocked the bootloader or anything. It's a non branded wwe firmware version....
Click to expand...
Click to collapse
Sorry for taking so long to respond. This is the RUU.zip you should use. You can follow the instructions a few posts back, just use this download instead of the one linked.
Markieboy said:
Hi no unfortunately the phone is bog standard I haven't unlocked the bootloader or anything. It's a non branded wwe firmware version....
Click to expand...
Click to collapse
Many thanks... Things have been resolved now,, the missus took it into carphonewarehouse, and they said because it's a software issue it'll be repaired free! Phones about a year old...
Well it came back with the repair report...
NEW MAIN BOARD firred
NEW USB C PORT fitted
NEW BATTERY fitted
wow.. Don't mind if I do.. Lol
Markieboy said:
Many thanks... Things have been resolved now,, the missus took it into carphonewarehouse, and they said because it's a software issue it'll be repaired free! Phones about a year old...
Well it came back with the repair report...
NEW MAIN BOARD firred
NEW USB C PORT fitted
NEW BATTERY fitted
wow.. Don't mind if I do.. Lol
Click to expand...
Click to collapse
Are you saying they replaced those? on the house? I'm
Markieboy said:
Many thanks... Things have been resolved now,, the missus took it into carphonewarehouse, and they said because it's a software issue it'll be repaired free! Phones about a year old...
Well it came back with the repair report...
NEW MAIN BOARD firred
NEW USB C PORT fitted
NEW BATTERY fitted
wow.. Don't mind if I do.. Lol
Click to expand...
Click to collapse
The question is, what were doing on that phone to cook all these? Mining Bitcoin?