Related
Because of my stupid mistakes of making my SD card failed the first time, I found a way to actually downgrade the system using HBoot mode even if you have a new HBoot system (i.e. Official Chinese version, Carrier Locked version, etc).
First thing to do, is to download the 2.73.405.5 official WWE RUU package (the exe);
Then, run that wizard, and while the wizard's program is running, search in your PC's %userprofile% folder, and look for "rom.zip"
Rename that rom.zip to HEROIMG.zip.
Put that file into your MicroSD card's root folder. Do not modify its contents.
put that SD card into your phone.
While the card is in, hboot the device (vol down + power).
it will pop up the HBOOT mode of the device. It will now check for a few files if they exist on your SD card. (HERODIAG.zip, etc)
in the last check, it will look for HEROIMG.zip, and tries to load it. Once the loading bar is complete on the top right side of the device, it will ask you to press home to continue the upgrade, or press other key to escape it. (i am not 100% sure if those are the keys, but you can read english so figure that part out).
Once the flashing is done (remember, this method will wipe everything. including radio, recovery, system, data, cache), you will now have a complete original ROM on your system. From there, use InstantRoot or any other rooting exploit, to root your device, put Cyanogen's recovery there, and start upgrading into custom roms!
Let me know if this method works or not. it worked on 3 of my friend's HTCs.
/* p.s. however i still have my unresolved issue about the SD card slot and USB device not recognized issue. */
Nope, I tried that before and it fails the CID check.
Guiness in a can? BRILLIANT!
yea, everyone has been jumping through their butts trying to figure out how to make goldcards and bypasses... why not just use hboot like htc probally uses it? Duh! Thanks for this!
edit..... oh snap....
does not work for me!
Once the loading bar is complete on the top right side of the device
go back to hboot...
and nothing to do
this won't work because the SPL is still checking the CID of the rom.zip you renamed to HEROIMG
for some people the flash will work, but thats because they have a hero with a CID thats in the range of the cid numbers (open the .zip file and check the android-info.txt to see the list.
changing topic is this is confusing people
nice try though
Otiginal IMG
Confirm ...works for me.After rooting...... and flashing couple images i try reflash back original rom - official ruu not want work ...stop on bootloader .....extracted rom not be a flashable trough sd card and amon ra loader....this way work like charm.Thnx.
Original IMG
Confirm ...works for me.After rooting...... and flashing couple images i try reflash back original rom - official ruu not want work ...stop on bootloader .....extracted rom not be a flashable trough sd card and amon ra loader....this way work like charm.Thnx.
Thank you, you are the man!
Thank you so much, i was about to eat my phone. it is htc hero and it worked. thank you so much...
since we have this thread i can ask as well...
is HEROIMG.ZIP signed, or why wouldn't one just alter the CID values in android-info.txt?
kendong2 said:
since we have this thread i can ask as well...
is HEROIMG.ZIP signed, or why wouldn't one just alter the CID values in android-info.txt?
Click to expand...
Click to collapse
I believe it is signed using HTC's own personal keys, preventing us changing the RUU extract.
anon2122 said:
I believe it is signed using HTC's own personal keys, preventing us changing the RUU extract.
Click to expand...
Click to collapse
Might be worth a test to do self signed ?
Jesterz said:
this won't work because the SPL is still checking the CID of the rom.zip you renamed to HEROIMG
for some people the flash will work, but thats because they have a hero with a CID thats in the range of the cid numbers (open the .zip file and check the android-info.txt to see the list.
changing topic is this is confusing people
nice try though
Click to expand...
Click to collapse
hi, i have the same problem and my cid is in in the list.
what could be the problem?
How the hell did you came up with that?
It worked perfectly! Cannot thank you enough.
You're the man.
been looking for this for nearly a week.
got my wife a new phone and want to store it original, but couldnt get back to stock,all cid fails.
with this version no cid fail and stock htc hero again.
thanks, you tha man.
Hello,
I'm new to the forums, and have only just recently got a HTC Wildfire A3333 running 2.2.1.
I have tried to use " [GUIDE] Downgrade to HTC Froyo WWE for AlphaRevX (HBOOT 1.01.0001) " to downgrade the h boot as to start to gain root.
But when I have followed the instructions, it appears to complete ok, but when I reboot in to the system menu, it still shows as .002 hboot and does not install the rom supplied.
any help would be great
EDIT: IT TOLD ME I HAD SUCCESSFULLY CREATED GOLD CARD
GlennBrownie
same goes with me mate, i got the gold card and then i insert it, it all goes but when the cmd closes it still shows hboot 1.01.002
This happened to me on a Telstra wildfire (A3335). if you make it so the CMD window doesn’t close (I used an alternative shell) you will see that it actually gets some error before closing, which is why it doesn’t actually change the hboot.
I must have done it 20 times before I got it to work. I can't remember what I did differently the time I made it work, but it was something to do with which usb mode the phone was in for each step, and when I decided to change it from one mode to the other. Basically trying to make it so the phone wouldn’t say “preparing SD card” after I had made the goldcard.
Worst part was when I finally downgraded my Hboot, alphrev X still wouldn’t work for me. Continued to get the error of “Retrieving Caroline from certain doom...” and "mtd: not writing bad block at 0x00000000" I've since given up..
okays, thanks for the help, ill try that, but with alpharevx the problem they are tring to fix is the part where you need to restart into fastboot the second time, so in this case, ill give that a try. the thing is that im useing windows 7 enterprise, i have the hboot drivers all installed and etc, i used the intructions given to me and everyone else where you have to make the gold card. in that intruction it stated to put the sd card into the usb or sd port, the thing i did was switch my phone to mount the SD card and create it via there, i think the part where we all went wrong is unmounted it after we finished making the sd card. so try that, and with your problem i tghink you need to try and run the program in ADMIN mode (right click and run as admin) and then try and get the HBOOT drivers from Unrevoked installed. give that a try and hope it all works out
cheers
Well I managed to get step2.bat to run in a cmd so that it stayed open,
it came up with "FAILED <remote: 42 custom id check fail>".
when HTC booted in to bootloader it still showed same h.boot (.0002)
Please see attached screenshot.
Question!! / problem!!
GlennBrownie said:
Hello,
I'm new to the forums, and have only just recently got a HTC Wildfire A3333 running 2.2.1.
I have tried to use " [GUIDE] Downgrade to HTC Froyo WWE for AlphaRevX (HBOOT 1.01.0001) " to downgrade the h boot as to start to gain root.
But when I have followed the instructions, it appears to complete ok, but when I reboot in to the system menu, it still shows as .002 hboot and does not install the rom supplied.
any help would be great
GlennBrownie
Click to expand...
Click to collapse
my question is, when i run alpharevx, it asks me for the beta key, note that it doesnt show my device name or anything like how i did it before i downgraded, any ideas why? and does anyone have a beta key for me to use? because the one i got with my phone when i entered it in said it was incorrect, when before before i downgraded it worked perfectly fine (except the rotting part).
what Beta key, I dont recall one?
To get a new beta key just follow this link, click download and then enter your phone's SN.
http://alpharev.nl/x/beta/
GlennBrownie said:
Well I managed to get step2.bat to run in a cmd so that it stayed open,
it came up with "FAILED <remote: 42 custom id check fail>".
when HTC booted in to bootloader it still showed same h.boot (.0002)
Please see attached screenshot.
Click to expand...
Click to collapse
Make sure you properly created a working gold card. Retry with gold card.
Sent from my HTC Wildfire using XDA App
technolust109 said:
my question is, when i run alpharevx, it asks me for the beta key, note that it doesnt show my device name or anything like how i did it before i downgraded, any ideas why? and does anyone have a beta key for me to use? because the one i got with my phone when i entered it in said it was incorrect, when before before i downgraded it worked perfectly fine (except the rotting part).
Click to expand...
Click to collapse
If it doesn’t show your device properly just reboot your phone. Basically every time the program fails it won’t show your device properly until you reboot again (This will also fix the issue where it thinks you have the wrong beta key). People suggesting to go get a new beta key have no idea. Have they not noticed that it doesn’t matter which HBoot version you select on the site you still get the same key based on your serial number.
yes, i used mt wildfire SN and i use the code it gives me still getting the same problem,
nejc121 said:
To get a new beta key just follow this link, click download and then enter your phone's SN.
Click to expand...
Click to collapse
currently running windows so cannot download as windows version under review.
bharatgaddameedi said:
Make sure you properly created a working gold card. Retry with gold card.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
completed program and it had a pop up saying something like, "success, you now have a gold key"....
GlennBrownie said:
Well I managed to get step2.bat to run in a cmd so that it stayed open,
it came up with "FAILED <remote: 42 custom id check fail>".
when HTC booted in to bootloader it still showed same h.boot (.0002)
Please see attached screenshot.
Click to expand...
Click to collapse
in other words, your goldcard is not created correctly.
ieftm said:
in other words, your goldcard is not created correctly.
Click to expand...
Click to collapse
done it twice and it still come up with success message?
even did it through hex editor....
I tried to do it again to show screenshots.
firstly, I ran step one and it says "cannot stat" followed by file name and says "no such file or directory". see image1.jpg
I then checked the buzzdowngrade folder, and all files are there. see image4.jpg
I then attempted the goldcard, and I clicked get cid, and it loaded a CID with a lot of 0's in it so I dont think its showing correct CID, possibly hiding real CID?
image2.jpg
when I clicked patch MMC, it came up with an error message. see image3.jpg
Have you installed the HTC driver 3.0.0.007. If not, install it first before even going with step1.
And regarding step2, creating a working gold card is important. If you still get custom id errors, try with a different memory card. And run the gold card tool as administrator. And in that you will see mmc0 and mmc1 options. Try creating with the other if one fails.
Sent from my HTC Wildfire using XDA App
GlennBrownie said:
I tried to do it again to show screenshots.
firstly, I ran step one and it says "cannot stat" followed by file name and says "no such file or directory". see image1.jpg
I then checked the buzzdowngrade folder, and all files are there. see image4.jpg
I then attempted the goldcard, and I clicked get cid, and it loaded a CID with a lot of 0's in it so I dont think its showing correct CID, possibly hiding real CID?
image2.jpg
when I clicked patch MMC, it came up with an error message. see image3.jpg
Click to expand...
Click to collapse
Just downgraded and i think i know what is the problem.
You have to change the connection status from charge only to Mass storage
then click refresh and the memory card will be available.
HTC MMC : select you sd card.
And now patch.
right, got an update.
managed to succeed with the dmisc.img and others that failed - thanks to Mattyyey, cheers Matt
We then got to flashing the rom and it failed, any suggestions?
we recreated the gold card and formated the microSD card and patched and it told us that it had succeeded.
please see screenshot.
bharatgaddameedi said:
And regarding step2, creating a working gold card is important. If you still get custom id errors, try with a different memory card...........Try creating with the other if one fails.
Click to expand...
Click to collapse
its probably your fake SD card! I was able to run the commands in step 1 and 2 from the cmd, all but the final ROM flash. I think after we create it we should confirm its been put on the SD card via hex workshop.... I did think of this last night but I was getting tired and you dont have it installed. I suspect its just the goldcard isn't done, everything else works when typed manually into cmd.
Unless anyone else has another reason for the custom ID check failing?
MATTYYEY was correct, it was due to fake microSD card, completed gold card with authentic SD card and it worked.
Sent from my HTC Wildfire android 2.3.4 Cyanogen V7.1 ROM using XDA App, GREAT rom running perfect.
I need to send my HOX in for warranty. I am going through this:
http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone
My CID is 'none'. My version is 1.29.709.12. Which makes sense, as I noticed something about Taiwan when I bought it.
I downloaded a 1.29.709.7 RUU but it just seems to run in background and quit when I try to run it. I am not sure if it was corrupt or not. But I couldn't even get the ROM file out of the temp directory. 7Zip was unable to open the .exe as an archive file either. Downloading a 1.26.709..3 file right now. Do I need a 1.29.709.12 file?
~S
sheamus said:
I need to send my HOX in for warranty. I am going through this:
http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone
My CID is 'none'. My version is 1.29.709.12. Which makes sense, as I noticed something about Taiwan when I bought it.
I downloaded a 1.29.709.7 RUU but it just seems to run in background and quit when I try to run it. I am not sure if it was corrupt or not. But I couldn't even get the ROM file out of the temp directory. 7Zip was unable to open the .exe as an archive file either. Downloading a 1.26.709..3 file right now. Do I need a 1.29.709.12 file?
~S
Click to expand...
Click to collapse
An older one won't work.
sheamus said:
I need to send my HOX in for warranty. I am going through this:
http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone
My CID is 'none'. My version is 1.29.709.12. Which makes sense, as I noticed something about Taiwan when I bought it.
I downloaded a 1.29.709.7 RUU but it just seems to run in background and quit when I try to run it. I am not sure if it was corrupt or not. But I couldn't even get the ROM file out of the temp directory. 7Zip was unable to open the .exe as an archive file either. Downloading a 1.26.709..3 file right now. Do I need a 1.29.709.12 file?
~S
Click to expand...
Click to collapse
You have to have the same version or higher ruu. Make sure your bootloaders locked/relocked and run the ruu.
You can't go back to complete stock as your bootloader will say relocked
sent from my One X using xda venom premium
I did relock boot loader.
What number has to be higher? the 1.29 or the last set of digits after the region code (709)?
The 709 RUU's seem extremely hard to find. I somehow managed to download one from an Asian language site, but it was a zip file not an RUU.exe. The zip contains what looks to be a filesystem, but does not contain the two .img files mentioned in the instructions I am using.
I guess I'll keep hunting for 709 RUU's. If anyone know of a 709 RUU that would work, please PM me, getting a little nervous here.
~S
Using 1.29.709.7 I am trying to do ./fastboot-mac flash boot boot_signed.img but I am getting an error:
sending 'boot' (4290 KB)... OKAY
writing 'boot'... FAILED (remote: not allowed)
Anyone know what this error means?
Hello,
I recently uninstalled some (system / T-Mobile) apps with Titanium Backup. And I did not make a backup first. The phone still runs fine but the OTA fails.
I tried so far:
- RUU 1.28 -> does not work, because system is already 1.29
- find rom.zip and unpack -> Ok, but cannot unpack system.img, unyafs fails.
The file which the OTA misses, according to logfile is named: 4661_TMODE_Music_One.odex
If someone could sent me this file or upload it somewhere I would be thankful.
There is a good chance that there are more files missing, but the log stops after the first fail.
I see in the system.img that there are at least 4 files with similar names:
4661_TMODE_Music_One.odex
4661_TMODE_Music_One.apk
4662_TMDE_Games_One.odex
4662_TMDE_Games_One.apk
If anyone knows how to unpack these, this would also helpful.
deleted
I think the best way to get all your bloatware back is to lock the bootloader and then flash the 129 RUU. Here is the link for the RUU if its T-mobile uk.
http://www.filefactory.com/file/6y1...Radio_1.1204.105.14_release_260731_signed.exe
Once your back to stock you can unlock again with your unlock token, flash cwm and make a stock nandroid backup.
If you need a file factory password pm me.
No, it's T-Mobile Germany, so I guess this will not help.
At the moment I'm trying to unpack the files from the system.img, but none of the methods described in the forums are working.
It is almost crazy, I can see the filenames and contents (lots of "PK" headers for instance) within the system.img but I've no idea how to extract them.
Get in touch with football. He might be able to get the RUU for you.
ghori1989 said:
Get in touch with football. He might be able to get the RUU for you.
Click to expand...
Click to collapse
Ok, tried that, waiting for the reply.
Meanwhile I'm able to mount the system image with some modifications as ext4 image and copy the contents. If there is an interest for this, I propably could write some tool to make this automatic.
Anyway, it did not help me, because the versions of the files in the image do not match the ones expected from the OTA.
Hello as suggested by ''Sawdoctor" (scary name btw.) I post my original from XDA Assist right here.
Okay guys I know this title isn't the best. But I don't want you to delete me because it has been already made. Because I DON'T EVEN KNOW WHAT THE HECK THE PROBLEM IS.
Alright Phone : HTC One M9 (1,5 years old)
After downloading an app from google play ''Spy Camera OS 3 (SC-OS3)'' , I guess someone from you guys developed it. No idea. I don't even know if it was this app that caused it. BUT - after I downloaded it and used for a while other apps started crashing ( for example : Facebook, Instagram). So I thought oh wow. I reset my phone and it will fix everything( dummy me) . Ye I did restart it and ended up in this funny screen ( maybe you would call it BOOTLOADER ? no idea)
It says tho :
***Software status : Modified***
*** LOCKED ***
*** S-ON ***
*** SECURITY WARNING***
/*<VOL UP> to previous item <VOL DOWN> to next item<POWER> to select item */
REBOOT
REBOOT TO BOOTLOADER
BOOT TO DOWNLOAD MODE
BOOT TO RECOVERY MODE
POWER DOWN
I have only tried those that are green colored and ended up back there where I started. Any ideas ? I am rookie. I have never done a root on my phones. No idea how to do it. So explain to me like to a kid. Thanks a lot.
Unfortunately just after 10 posts I can add pics. Hope you can help without seeing what I see.
Either a failed root attempt or a borked nand. The app didn't cause it.
Beamed in by telepathy.
shivadow said:
Either a failed root attempt or a borked nand. The app didn't cause it.
Beamed in by telepathy.
Click to expand...
Click to collapse
Alright man, I am telling you I have never done root on my devices !! Because I know you can **** your phone up and I never wanted that.
I simply restarted phone. Turned on. This came up. Don't even know how to root.
I think (hopefully) the problem can be solved by re-flashing stock ROM. You just need to find correct RUU.zip file for your device. Rename this zip file as 0PJAIMG.zip and put zip file in your microSD card. Power off your phone. Put microSD card. Press and hold vol- and power button simultaneously (it will boot to download mode and try to install zip file in SD card). Let me know the result
oscar_ferreiro said:
I think (hopefully) the problem can be solved by re-flashing stock ROM. You just need to find correct RUU.zip file for your device. Rename this zip file as 0PJAIMG.zip and put zip file in your microSD card. Power off your phone. Put microSD card. Press and hold vol- and power button simultaneously (it will boot to download mode and try to install zip file in SD card). Let me know the result
Click to expand...
Click to collapse
Hello, great suggestion. I am going to try it. One more question to it. Do I place it in specific folder in SD card so the phones reads the .zip file first ??
Let's try this ! Hopefully it works.
Btw. is there a difference restoring it from RUU.zip file and RUU.exe file ??
EDIT: Well I just realized, I don't have any USB connector for SD cards nor available android phone to put the file via that (only iPhones at home right now) . I am going to try it tommorow and hopefull it works.
YoYiXxX said:
Hello, great suggestion. I am going to try it. One more question to it. Do I place it in specific folder in SD card so the phones reads the .zip file first ??
Let's try this ! Hopefully it works.
Btw. is there a difference restoring it from RUU.zip file and RUU.exe file ??
Click to expand...
Click to collapse
Well, place it on root folder. And better to have empty SD card. So there will be only that file
About second question, I think there is no difference. Have not found proper RUU.exe for mine, so have not experienced restoring from it
oscar_ferreiro said:
Well, place it on root folder. And better to have empty SD card. So there will be only that file
About second question, I think there is no difference. Have not found proper RUU.exe for mine, so have not experienced restoring from it
Click to expand...
Click to collapse
Last question what exactly am I looking for in .ZIP file ? When my release date was Dec 17 2015, 0:40:10, can I use another ? With the same OS ( 3.35.161.12) and RADIO(01.01_U11440792_96.00.51201G_F) info, which I think is more important. I don't know what exactly has to be the same in the RUU file and what can difffer and is not that important. Thanks in advance
YoYiXxX said:
Last question what exactly am I looking for in .exe file ? When my release date was Dec 17 2015, 0:40:10, can I use another ? With the same OS ( 3.35.161.12) and RADIO(01.01_U11440792_96.00.51201G_F) info, which I think is more important. I don't know what exactly has to be the same in the RUU file and what can difffer and is not that important. Thanks in advance
Click to expand...
Click to collapse
In order to succeed, you should chose by following criteria:
- RUU software version equal or higher than what's on the phone (as it is S-On in your condition)
- MID should match
- CID should match
- HTC Syncmanager (for drivers if you are going to use exe file)
- Some other miscellaneous things that are most of PC already have pre-installed (again for exe file)
oscar_ferreiro said:
In order to succeed, you should chose by following criteria:
- RUU software version equal or higher than what's on the phone (as it is S-On in your condition)
- MID should match
- CID should match
- HTC Syncmanager (for drivers if you are going to use exe file)
- Some other miscellaneous things that are most of PC already have pre-installed (again for exe file)
Click to expand...
Click to collapse
my phone says following :
***LOCKED***
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.01_U11440792_96.00.51201G_F
OpenDSP-15.6.1.00522.8994_1026
OS-3.35.161.12
Dec 17 2015, 00:40:10(671447)
The matching file I downloaded says :
0PJAIMG_HIMA_UHL_M60_SENSE70_MR_Vodafone_UK_3.35.161.12_Radio_01.01_U11440792_96.00.51201G_F_release_464298_signed.zip
Cyan colored I see matches. Only release date, UK( I have the phone from Germany Vodafone) don't match. M60 I don't really understand, what that stands for.
IT WORKED
Big thanks to user : oscar_ferreiro
Your suggestion worked. I am back in my phone. You're boss. Hopefully it won't stop working in following days.
Thanks a lot. Have a nice day. XDA forever.
-YoYiXxX
Very glad that could help you. Please don't forget to hit the "Thanks!" button under my post. Good luck and hope your phone will last long
YoYiXxX said:
Alright man, I am telling you I have never done root on my devices !! Because I know you can **** your phone up and I never wanted that.
I simply restarted phone. Turned on. This came up. Don't even know how to root.
Click to expand...
Click to collapse
Then it's a borked nand. Before you flash anything blindly I suggest you spend a day or two reading about possible errors you may encounter and how to resolve them.
Good luck!.
Beamed in by telepathy.
F*ck this...
Alright listen, here we are 4 days later ... again out of nowhere !! my phone started crashing every single app.. EVERY single app, no app would work for me... I knew that if I do turn off my phone the same screen pops up with that ''Reboot'' stuff.. so I did turn the phone off ( IT DID VIBRATE BEFORE THE SCREEN COMPLETELY WENT OFF, if that's a trigger to someone) and the ''Reboot' white screen popped up as expected. WHAT THE F*CK ANDROID. I HAVE NEVER EXPERIENCED SOMETHING LIKE THIS.
I don't know what kind of virus can that be or whatever. I know that if I use the file I used before to reload the Stock ROM it will somehow work, but as you can see only for couple days. I didn't do anything to cause it in terms of trying to root my phone. Trust me.
Anyone willing to help ?
shivadow said:
Then it's a borked nand. Before you flash anything blindly I suggest you spend a day or two reading about possible errors you may encounter and how to resolve them.
Good luck!.
Beamed in by telepathy.
Click to expand...
Click to collapse
Yes I will do the research. Thought you just threw nonsense words with that ''borked nand".