Hi,
I'm on an australian Desire X and I've been trying to install a stock European RUU (i heard you couldn't update the phone while on a custom rom) after rooting and installing the CWM using Hasoons Toolkit on my phone, but it won't let me due to error 131 customer id error.
Since then I have tried to write the cid using android platform-tools which I found didn't work due to my S-On status
Making a gold card which nothing happened
Retrieve the rom.zip from the installation and try to change the android-info.txt but the .zip was corrupt
Had a look at S-Off tutorials, but the programs they use don't seem to support the Desire X
I have a kernel in a zip file and the .md5 for the RUU if that'll help with anything.
I was wondering if there was any way to change the cid or get S-Off on the Desire X?
Thanks in advance.
Not yet, and looking at the HTC One X and One X+, I think it's gonna take a while 'till we get it.
How did you do the thing with goldcard?
nlooooo said:
How did you do the thing with goldcard?
Click to expand...
Click to collapse
Used the gold card helper app and used the mmc1 number
Hex edited microsd
Ran RUU
Still got error 131
alligator06s said:
Used the gold card helper app and used the mmc1 number
Hex edited microsd
Ran RUU
Still got error 131
Click to expand...
Click to collapse
You need to exract rom zip from RUU, rename it to PM66IMG.zip, put it to root of GoldCard and reboot to bootloader, not fastboot. When bootloader is loaded it checks sd card for that kind of file and it will ask you to update from PM66IMG.zip found on sd card. That's the way to bypass cid checking.
nlooooo said:
You need to exract rom zip from RUU, rename it to PM66IMG.zip, put it to root of GoldCard and reboot to bootloader, not fastboot. When bootloader is loaded it checks sd card for that kind of file and it will ask you to update from PM66IMG.zip found on sd card. That's the way to bypass cid checking.
Click to expand...
Click to collapse
The zip i retrieved from the ruu exe is corrupt, looking around apparently it's something htc implemented in the newer files.
alligator06s said:
The zip i retrieved from the ruu exe is corrupt, looking around apparently it's something htc implemented in the newer files.
Click to expand...
Click to collapse
It's not corrupted it's cripted from opening and most likely bootloader decripts. My question stays, have you tried to use it in a way a described?
nlooooo said:
It's not corrupted it's cripted from opening and most likely bootloader decripts. My question stays, have you tried to use it in a way a described?
Click to expand...
Click to collapse
No, but I will try at the end of the week when I have some free time and post results. Unless anyone has tried and knows if it works or not.
Going to attempt tomorrow, but I would like to know if it's possible to brick the phone using this method and if it's recoverable.
PM66IMG
nlooooo said:
You need to exract rom zip from RUU, rename it to PM66IMG.zip, put it to root of GoldCard and reboot to bootloader, not fastboot. When bootloader is loaded it checks sd card for that kind of file and it will ask you to update from PM66IMG.zip found on sd card. That's the way to bypass cid checking.
Click to expand...
Click to collapse
Hi nlooooo, can you please give me a link to download the file "PM66IMG.ZIP"? I tried to extract from RUU but i can´t or i dont know to do it.
Thanks in advanced
nlooooo said:
You need to exract rom zip from RUU, rename it to PM66IMG.zip, put it to root of GoldCard and reboot to bootloader, not fastboot. When bootloader is loaded it checks sd card for that kind of file and it will ask you to update from PM66IMG.zip found on sd card. That's the way to bypass cid checking.
Click to expand...
Click to collapse
I extracted rom zip from RUU and renamed it, put it to root of GoldCard. Bootloader extracts but on loading it fails with error CID Mismatch. Security error. Is there any way to bypass CID checking?
muhammad.bilal said:
I extracted rom zip from RUU and renamed it, put it to root of GoldCard. Bootloader extracts but on loading it fails with error CID Mismatch. Security error. Is there any way to bypass CID checking?
Click to expand...
Click to collapse
Not for now.
nlooooo said:
Not for now.
Click to expand...
Click to collapse
Dear nloooo, are we got ruuveal support for proto and the Rom you created is to be installed using PM66IMG.zip method or custom recovery? Can you please upload the stock ROM which I can install with CID HTC__044 and can have OTA working as well. OTA does not seem to work with DEODEXED roms provided earlier on the forum..:good:
muhammad.bilal said:
Dear nloooo, are we got ruuveal support for proto and the Rom you created is to be installed using PM66IMG.zip method or custom recovery? Can you please upload the stock ROM which I can install with CID HTC__044 and can have OTA working as well. OTA does not seem to work with DEODEXED roms provided earlier on the forum..:good:
Click to expand...
Click to collapse
Yes, we got ruuveal support so I used it to decript rom.zip. However I have problems with upload so I'll upload it a the next few days.
HTC__044
nlooooo said:
Yes, we got ruuveal support so I used it to decript rom.zip. However I have problems with upload so I'll upload it a the next few days.
Click to expand...
Click to collapse
Can you also send instructions when you upload it, how to install it? As I tried both encrypted and decripted rom (from ruuveal) using standard recovery and gold card mechanism, i get cid mismatch error.
Thanks a lot.
You get cid mismatch with recovery?
Sent from my HTC branded muffin...
Stereo8 said:
You get cid mismatch with recovery?
Sent from my HTC branded muffin...
Click to expand...
Click to collapse
yes loaded standard recovery.locked phone as with unlocked complains for security error.renamed rom.zip to PM66IMG.zip and then booted into bootloader and it tries to load zip file and gives cid mismatch
muhammad.bilal said:
yes loaded standard recovery.locked phone as with unlocked complains for security error.renamed rom.zip to PM66IMG.zip and then booted into bootloader and it tries to load zip file and gives cid mismatch
Click to expand...
Click to collapse
Try flashing with CWM...
Sent from my HTC branded muffin...
Stereo8 said:
Try flashing with CWM...
Sent from my HTC branded muffin...
Click to expand...
Click to collapse
CWM complains its invalid zip file.
PM66IMG.zip is not meant to be flashed from recovery, it's not a flashable zip. If you get CID mismatch then RUU is not made for your version of device..
Related
I was try to do this almast 2 mounts.
Very 1st I need to say sorry about my bad English
changing CID is needed for non-europe useres...
1. Unlock your bootloader with HTC Unlocktoken
2. Change your CID on fastboot
fastboot oem writecid HTC__001
Click to expand...
Click to collapse
3.Re-Lock your bootloader
fastboot oem lock
Click to expand...
Click to collapse
[If you already have europian CID and hboot 1.49.0018 you can pass first 2 steps...]
Yes Thats it Now all you need PG86IMG.zip on your SD card.
Download PG86IMG.zip http://www.multiupload.com/39NSAMWQU7 NOTE:it will delete all your internal memory. Before flash it make backup)
4. Put your sd Card to your pc copy PG86IMG.zip to your sd card root
5. Power off your phone.
6. Press Vol Down+Power to open hboot.
7. Let the device find the zip file and flash it.
8. Chk the hboot version now.
9. I thing I don't need to explain how to use Revolutionary tool
Spacial Thanks for Football for the offician RUU, Metronom76 for the CID changing Code, Scorpunix for flashable HBoot files
when you changed CID it will say [FATAL ERROR] you can basicly ignore that. there is no error.
hey thanks for the info, which offical RUU has the older hboot so I can go ahead and download it?
Nice one. I'm sure lots of people will benefit from this
I won't need to. I'm already s-offed using revolutionary
Sent from my HTC EVO 3D X515m using XDA App
kartikb said:
hey thanks for the info, which offical RUU has the older hboot so I can go ahead and download it?
Click to expand...
Click to collapse
This one has HBoot 1.49.0007
RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.90 20.00_10.13.9020.08_2M_release_203403_signed
http://www.filefactory.com/file/cc7e...403_signed.exe
Click to expand...
Click to collapse
I'm still uploading the PG86IMG file. I'll let you know when it's done
thanks, I'll go ahead and download that file, if before that you do manage to upload the hboot file, I'll just download the hboot.
Thanks a lot
my upload is not the Hboot only. It's basicly the same rom for flashing from SD card.
If you managed to spare it be my guess please because it is beyonde my talents
Upload complated link is on OP too
http://www.multiupload.com/39NSAMWQU7
kartikb said:
hey thanks for the info, which offical RUU has the older hboot so I can go ahead and download it?
Click to expand...
Click to collapse
If u want install 1.49.007 bootloader copy allegated file in root of your sd
and restart in bootloader
http://forum.xda-developers.com/showpost.php?p=18594158&postcount=26
Ganii said:
If u want install 1.49.007 bootloader copy allegated file in root of your sd
and restart in bootloader
http://forum.xda-developers.com/showpost.php?p=18594158&postcount=26
Click to expand...
Click to collapse
Thanks... I was not know which files are needed for the flash new hboot.
HBOOT DOWNGRADE ADDED TO OP
Does that really work? Now a way to make S-OFF for devices with HBoot with version bigger than 1.49.0008?
Evengard said:
Does that really work? Now a way to make S-OFF for devices with HBoot with version bigger than 1.49.0008?
Click to expand...
Click to collapse
follow the tutorial it makes your hboot 1.49.0007
n_god said:
Thanks... I was not know which files are needed for the flash new hboot.
HBOOT DOWNGRADE ADDED TO OP
Click to expand...
Click to collapse
No problem!
But don`t know exactly,maybe some users need to edit the
"android-info.txt" inside the PG86IMG.zip,otherwise there can be problems
and downgrade wont work.
With hboot version 1.49.0018 it works!
Ganii said:
No problem!
But don`t know exactly,maybe some users need to edit the
"android-info.txt" inside the PG86IMG.zip,otherwise there can be problems
and downgrade wont work.
Click to expand...
Click to collapse
chaning CID is for that users because I tried chaning txt file and it doesn't work...
Ah Ok,then it should work for all
n_god said:
I was try to do this almast 2 mounts.
Very 1st I need to say sorry about my bad English
changing CID is needed for non-europe useres...
1. Unlock your bootloader with HTC Unlocktoken
2. Change your CID on fastboot
3.Re-Lock your bootloader
Yes Thats it Now all you need PG86IMG.zip on your SD card.
Download PG86IMG.zip http://forum.xda-developers.com/showpost.php?p=18594158&postcount=26
4. Put your sd Card to your pc copy PG86IMG.zip to your sd card root
5. Power off your phone.
6. Press Vol Down+Power to open hboot.
7. Let the device find the zip file and flash it.
8. Chk the hboot version now.
9. I thing I don't need to explain how to use Revolutionary tool
Spacial Thanks for Football for the offician RUU, Metronom76 for the CID changing Code, Scorpunix for flashable HBoot files
Click to expand...
Click to collapse
But why have i do to this downgrade? what is the benefit?
The benefit is S-Off which will allow you to flash any ROM/Kernel. If you currently have 1.49.0011 or above unlocked using the HTC method you would have had troubles where some ROMs just sit at the white HTC screen forever or error messages when trying to flash kernels ect.
This will fix all those issues!
at last i can unleash my evo 3d thanks to all
Sent from my HTC EVO 3D X515m using xda premium
is it possible to change cid without s off !?
Ganii said:
Ah Ok,then it should work for all
Click to expand...
Click to collapse
Notice me main version is older......
---------- Post added at 01:33 AM ---------- Previous post was at 01:25 AM ----------
n_god said:
I was try to do this almast 2 mounts.
Very 1st I need to say sorry about my bad English
changing CID is needed for non-europe useres...
1. Unlock your bootloader with HTC Unlocktoken
2. Change your CID on fastboot
3.Re-Lock your bootloader
Yes Thats it Now all you need PG86IMG.zip on your SD card.
Download PG86IMG.zip http://forum.xda-developers.com/showpost.php?p=18594158&postcount=26
4. Put your sd Card to your pc copy PG86IMG.zip to your sd card root
5. Power off your phone.
6. Press Vol Down+Power to open hboot.
7. Let the device find the zip file and flash it.
8. Chk the hboot version now.
9. I thing I don't need to explain how to use Revolutionary tool
Spacial Thanks for Football for the offician RUU, Metronom76 for the CID changing Code, Scorpunix for flashable HBoot files
Click to expand...
Click to collapse
unlocked+son+chang cid to HTC__001 after i lock the hboot
when loading the PG86IMG.ZIP
no any notice
after checking is jump out
because after offical unlock
main version with recovery must > device version
if i turned to Relock
Only can flash offical PG86IMG.ZIP
I Need a version > 2.5.0.0 with offical signature
My Hboot version is 1.49.0012
waiting for rev soff......
Hi, title says all, i want to downgrade SW from 2.17 to 2.08. Is there a way to do that? Thanks.
luis4ever said:
Hi, title says all, i want to downgrade SW from 2.17 to 2.08. Is there a way to do that? Thanks.
Click to expand...
Click to collapse
go to the correct thread and download the RUU for that SW version and then instal and you should be set to roll... be sure to rename the file and install it to your root to let your hboot install it on its own
wloftus said:
go to the correct thread and download the RUU for that SW version and then instal and you should be set to roll... be sure to rename the file and install it to your root to let your hboot install it on its own
Click to expand...
Click to collapse
I have downloaded the official ROM from sprint for sw 2.08 but now you say I have to rename it? Can I install it like every custom ROM?
luis4ever said:
I have downloaded the official ROM from sprint for sw 2.08 but now you say I have to rename it? Can I install it like every custom ROM?
Click to expand...
Click to collapse
That wouldn't be a rom I don't think if you dl it from sprint. It should be an exe file you run from your pc. Just plug your phone into your pc and run the exe you downloaded. It's called an ruu. It will erase root and your recovery and return you back to stock.
#Root-Hack\Mod*Always_
""Shooter on Deck""
laie1472 said:
That wouldn't be a rom I don't think if you dl it from sprint. It should be an exe file you run from your pc. Just plug your phone into your pc and run the exe you downloaded. It's called an ruu. It will erase root and your recovery and return you back to stock.
#Root-Hack\Mod*Always_
""Shooter on Deck""
Click to expand...
Click to collapse
Yes, i downloaded the RUU, is there a risk doing this or is it safe?
luis4ever said:
Yes, i downloaded the RUU, is there a risk doing this or is it safe?
Click to expand...
Click to collapse
Just make sure its the correct one and make sure your battery is over 70% charged and you should be ok.
#Root-Hack\Mod*Always_
""Shooter on Deck""
wloftus said:
go to the correct thread and download the RUU for that SW version and then instal and you should be set to roll... be sure to rename the file and install it to your root to let your hboot install it on its own
Click to expand...
Click to collapse
I'm not getting what you're saying here. I ran the 2.17 ruu and then I tried the 2.08 and it wouldn't install, I thought it was because it was older, but maybe I'm missing something. What file do you rename, the ruu? Install it to my root? What does that mean? Did it fail to install because I'm 1.5 s-on,?
xcpefrmreality said:
I'm not getting what you're saying here. I ran the 2.17 ruu and then I tried the 2.08 and it wouldn't install, I thought it was because it was older, but maybe I'm missing something. What file do you rename, the ruu? Install it to my root? What does that mean? Did it fail to install because I'm 1.5 s-on,?
Click to expand...
Click to collapse
the RUU...rename that to PG86IMG.zip and move the file over to the root directory of your sdcard....root meaning the main directory.... and no it didnt fail bc of hboot 1.5 and s-on,,, i have the same setup....
http://forum.xda-developers.com/showthread.php?t=1223979&highlight=ruu
if it doesnt work get back at me...there is another method too...
xcpefrmreality said:
I'm not getting what you're saying here. I ran the 2.17 ruu and then I tried the 2.08 and it wouldn't install, I thought it was because it was older, but maybe I'm missing something. What file do you rename, the ruu? Install it to my root? What does that mean? Did it fail to install because I'm 1.5 s-on,?
Click to expand...
Click to collapse
wloftus said:
the RUU...rename that to PG86IMG.zip and move the file over to the root directory of your sdcard....root meaning the main directory.... and no it didnt fail bc of hboot 1.5 and s-on,,, i have the same setup....
http://forum.xda-developers.com/showthread.php?t=1223979&highlight=ruu
if it doesnt work get back at me...there is another method too...
Click to expand...
Click to collapse
I've found that anyone who reported random reboots was using the pg86img.zip files through bootloader to upgrade/downgrade the sw version. It's not that all pg86imgs don't work properly, its just that some don't and I don't know which ones. I'd strongly recommend using an RUU.exe file from your computer to go back to 2.08. I soft bricked my phone for a few hours also trying to install a pg86img.zip (but that was a dumb error on my part, and the RUU.exe fixed my stupidity )
EDIT: if the file you downloaded is an executable file (.exe), run it from your computer and you don't have to rename it anything. If you downloaded a .zip file, it has to be renamed to PG86IMG.zip and you have to put it in the root directory of your SD card
w0rdOo said:
I've found that anyone who reported random reboots was using the pg86img.zip files through bootloader to upgrade/downgrade the sw version. It's not that all pg86imgs don't work properly, its just that some don't and I don't know which ones. I'd strongly recommend using an RUU.exe file from your computer to go back to 2.08. I soft bricked my phone for a few hours also trying to install a pg86img.zip (but that was a dumb error on my part, and the RUU.exe fixed my stupidity )
EDIT: if the file you downloaded is an executable file (.exe), run it from your computer and you don't have to rename it anything. If you downloaded a .zip file, it has to be renamed to PG86IMG.zip and you have to put it in the root directory of your SD card
Click to expand...
Click to collapse
that was my fault and i am sorry... forgot to tell you to relock your bootloader before you install that file to your sdcard and boot into hboot...
I'm trying to reset my device to stock, and for this i need the correct RUU.. But the ones i tried give the same error, saying it's the wrong RUU file.
It's a GSM EVO 3D, rooted/S-OFF'd with revolutionary and has baseband 11.77.3504.00U_11.25.3504.06_M.
I tried downloading and using this one:
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed.exe
But that gives me an error.
Then i remembered i had downloaded the RUU when i got the phone to start with, when i was first rooting my phone so i could revert back if needed (had it stored away on my old HDD). Tried this:
RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.9020.00_10.13.9020.08_2M_release_203403_signed.exe
And still got the same error.
Could anyone help me?
You have to flash it from your computer if you haven't tried that already. Make sure USB debugging is enabled first before attempting to run your exe.
Jsparta26 said:
You have to flash it from your computer if you haven't tried that already. Make sure USB debugging is enabled first before attempting to run your exe.
Click to expand...
Click to collapse
Yes i'm doing it from my computer.
Yes i have USB debugging on.
I can connect just fine using both ADB and Fastboot aswell, so not even drivers can be a problem (if they're even needed).
Try relocking your boot loader.
Assuming you actually do have the right ruu.exe for your region and carrier, I can think of two issues:
1. Did you relock the bootloader as jsparta said?
2. Have you changed your cid/device id in the past? Maybe the ruu thinks the phone is a different model if you did.
coal686 said:
Assuming you actually do have the right ruu.exe for your region and carrier, I can think of two issues:
1. Did you relock the bootloader as jsparta said?
2. Have you changed your cid/device id in the past? Maybe the ruu thinks the phone is a different model if you did.
Click to expand...
Click to collapse
Bingo!
According to this post it looks like his CID has been changed. Many people have had problems flashing an RUU after changing the CID and I'm not sure how to fix it since I've never needed to do that myself.
ramjet73
I never knowingly changed my CID, and it's so long ago i rooted my Evo 3D that i can't even remember exactly how i did it, but i used Revolutionary for some of it (my HBOOT says "Revolutionary" at the top).
I tried to do "fastboot oem lock", and it said "Device is already locked" or something along those lines.
Is there any CID that i can just change to (with "fastboot oem writecid XXX") in order to make the RUU work?
Moonbloom said:
I never knowingly changed my CID, and it's so long ago i rooted my Evo 3D that i can't even remember exactly how i did it, but i used Revolutionary for some of it (my HBOOT says "Revolutionary" at the top).
I tried to do "fastboot oem lock", and it said "Device is already locked" or something along those lines.
Is there any CID that i can just change to (with "fastboot oem writecid XXX") in order to make the RUU work?
Click to expand...
Click to collapse
Don't know much about Revolutionary since I used JuopunutBear (wire trick) to gain S-OFF. I'm also CDMA and not familar with the GSM RUU's, but someone posted this list of CID's and HTC_Y13 seems to be Norway if that helps someone with pointing you to the correct version.
Edit1: BTW, what error are you getting when you try to flash the RUU?
Edit2: This thread might be of some help to you. It looks like CID HTC_Y13 is supported by the RUU you already have, but some people have had to modify it to fix status 6 or 7 errors.
ramjet73
Maybe try to run flash directly from bootloader. Run your RUU file, go to your temp directory and search for file named rom.zip. Change it name to PG86IMG.zip, put it in sd card. Then go to bootloader and it should ask you to flash this soft. This one is stock ics rom and it worked for me but I was on Jbear hboot:
http://www.filefactory.com/file/2hw...00U_11.25.3504.06_M_release_262714_signed.exe
It will change your bootloader to 1.53.0007
Or you can try to find and download some GB RUU and try the same as above.
Good luck!
c000ler said:
Maybe try to run flash directly from bootloader. Run your RUU file, go to your temp directory and search for file named rom.zip. Change it name to PG86IMG.zip, put it in sd card. Then go to bootloader and it should ask you to flash this soft.
Click to expand...
Click to collapse
Good idea.
The link in the second edit of my previous post has a download for the .zip version of the ROM from that same RUU and a PG86IMG.zip firmware file without the bootloader so he doesn't have to extract it from the RUU.exe. If he wants the bootloader that comes with that build he should be able to flash it separately since he is S-OFF.
ramjet73
c000ler said:
Maybe try to run flash directly from bootloader. Run your RUU file, go to your temp directory and search for file named rom.zip. Change it name to PG86IMG.zip, put it in sd card. Then go to bootloader and it should ask you to flash this soft. This one is stock ics rom and it worked for me but I was on Jbear hboot:
http://www.filefactory.com/file/2hw...00U_11.25.3504.06_M_release_262714_signed.exe
It will change your bootloader to 1.53.0007
Or you can try to find and download some GB RUU and try the same as above.
Good luck!
Click to expand...
Click to collapse
ramjet73 said:
Good idea.
The link in the second edit of my previous post has a download for the .zip version of the ROM from that same RUU and a PG86IMG.zip firmware file without the bootloader so he doesn't have to extract it from the RUU.exe. If he wants the bootloader that comes with that build he should be able to flash it separately since he is S-OFF.
ramjet73
Click to expand...
Click to collapse
That RUU was the first one i tried to use, so i already have the file on my desktop at the moment.
Since i'm trying to go completely stock, i guess just flashing the rom.zip (after renaming it to PG86IMG.zip) will return me to stock ICS rom, stock (and updated) bootloader and S-ON ?
Moonbloom said:
That RUU was the first one i tried to use, so i already have the file on my desktop at the moment.
Since i'm trying to go completely stock, i guess just flashing the rom.zip (after renaming it to PG86IMG.zip) will return me to stock ICS rom, stock (and updated) bootloader and S-ON ?
Click to expand...
Click to collapse
If you can flash the RUU successfully from the .zip file, you will need to issue the following fastboot command to set S-ON, but make 100% sure you have the stock bootloader installed or it will brick your phone if you still have Revolutionary or another unsigned custom bootloader:
fastboot oem writesecureflag 3
ramjet73
Assuming that fastboot is saying that you are on locked bootloader, after flashing this stock ics soft you will be on stock 1.53.0007 locked bootloader. After that you must make S-ON, to do that use command:
fastboot oem writesecureflag 3
But make sure that you are 100% on stock bootloader, cause if not, you can birck your phone. Good luck!
ramjet73 was faster
I'll try to do it tomorrow, as I'm heading to bed now, but thanks for the advice so far, I'll probably be back again
Sent from my GT-N7100 using xda app-developers app
I think if you are s-off you don't need to lock the bootloader. Could he just use the PG86IMG version but alter the cid info in the android-info.txt file to match his phone's cid? It seems like it would work. I have done this with extracted portions of an ruu and altered the cid to work with VM evo v. Basically I made an hboot 1.5 PG86IMG for evo v by extracting from the sprint ruu and editing the android-info.txt to use vm cid
Sent from my PG86100 using Tapatalk 2
Brian706 said:
I think if you are s-off you don't need to lock the bootloader. Could he just use the PG86IMG version but alter the cid info in the android-info.txt file to match his phone's cid? It seems like it would work. I have done this with extracted portions of an ruu and altered the cid to work with VM evo v. Basically I made an hboot 1.5 PG86IMG for evo v by extracting from the sprint ruu and editing the android-info.txt to use vm cid
Click to expand...
Click to collapse
I recently discovered that you can specify multiple CID's in the android-info.txt file so the hboot .zip files in this post have all been modified to work with the Evo 3D and Evo V, in case you need to change hboots again.
ramjet73
ramjet73 said:
I recently discovered that you can specify multiple CID's in the android-info.txt file so the hboot .zip files in this post have all been modified to work with the Evo 3D and Evo V, in case you need to change hboots again.
ramjet73
Click to expand...
Click to collapse
Thanks. I actually have a sprint 3vo and have made my own hboot and other files for myself. Just made a couple for the evo v the other day because a few people were looking for 1.5.
So how does that multiple cid work? Do you just add extra lines into the android-info.txt or separate with a comma? I'd like to learn this. It could come in handy TIA!
Eta:
I misread your last post. I will download one of those and check it out. Thank you!
Sent from my PG86100 using Tapatalk 2
---------- Post added at 07:12 PM ---------- Previous post was at 06:45 PM ----------
Cool. It looks just like I pictured it! Thanks for sharing.
Sent from my PG86100 using Tapatalk 2
Brian706 said:
So how does that multiple cid work? Do you just add extra lines into the android-info.txt or separate with a comma? I'd like to learn this. It could come in handy TIA!
Eta:
I misread your last post. I will download one of those and check it out. Thank you!
Click to expand...
Click to collapse
There are instructions towards the end of this post from the Sensation forum. I used UltraEdit instead of Notepad++ and copied the line with the Sprint CID (SPCS_001) to a new line then modified it to the VM CID (SPCS_002). There must be an LF character that the default Notepad doesn't recognize because it opens it as one line, but WordPad and the editors show multiple lines.
Once I had the android-info.txt modified, it was easy to delete the existing version in the hboot zip files using WinZip and then copy the new version to replace it.
ramjet73
I have a replacement phone from T-Mobile that's not getting the update. I have the file. Just need to know where to rename it UPDATE.ZIP so i can install it on Recovery. Anyone?
// Tapatalk HD for Android - Nexus 7 //
Yeah, I'm pretty sure you can do that. Just make sure your bootloader is locked. If it doesn't work, try doing it from the Amaze All In One Kit v5.1 in the Development section.
I don't see any option in Hasoon's kit (screenshot in post 1) for installing an OTA update. Am I missing something?
Bootloader doesn't have to be relocked, BTW, I just updated another Amaze that had it downloaded and ready to install with the bootloader unlocked. Stock recovery image is needed.
Problem is knowing what folder to put the OTA in ... /sdcard/ ? /media/ ? I presume (could be wrong) that the OTA zip file is renamed UPDATE.ZIP and copied somewhere. Looking for some first hand knowledge....
ChromeJob said:
I don't see any option in Hasoon's kit (screenshot in post 1) for installing an OTA update. Am I missing something?
Bootloader doesn't have to be relocked, BTW, I just updated another Amaze that had it downloaded and ready to install with the bootloader unlocked. Stock recovery image is needed.
Problem is knowing what folder to put the OTA in ... /sdcard/ ? /media/ ? I presume (could be wrong) that the OTA zip file is renamed UPDATE.ZIP and copied somewhere. Looking for some first hand knowledge....
Click to expand...
Click to collapse
Leave the zip with its original name and put it in the internal sd card in the download folder. That's where it put it when it was pushed to my phone.
Sent from my HTC_Amaze_4G using xda app-developers app
masondoctorjt said:
Leave the zip with its original name and put it in the internal sd card in the download folder. That's where it put it when it was pushed to my phone.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thanks but doesn't seem to do anything. "There are no updates available for your phone."
// Tapatalk HD for Android - Nexus 7 //
ChromeJob said:
Thanks but doesn't seem to do anything. "There are no updates available for your phone."
// Tapatalk HD for Android - Nexus 7 //
Click to expand...
Click to collapse
Did you anyhow try - renaming that 30MB OTA into PH85IMG.ZIP and placing it on your external sd card, then rebooting into Bootloader? And what?
jauhien said:
Did you anyhow try - renaming that 30MB OTA into PH85IMG.ZIP and placing it on your external sd card, then rebooting into Bootloader? And what?
Click to expand...
Click to collapse
I did but it didn't work
HTC Amaze 4G
Unlocked bootloader and rooted
S-ON
Flashed latest OTA by sports
Faux v29 kernel
Baseband didn't udpate, still 1.14
siva_rknec said:
I did but it didn't work
HTC Amaze 4G
Unlocked bootloader and rooted
S-ON
Flashed latest OTA by sports
Faux v29 kernel
Baseband didn't udpate, still 1.14
Click to expand...
Click to collapse
Apparently it found your custom recovery / root / unlocked boot.. and stopped.
ChromeJob's handheld is the complete stock..
jauhien said:
Did you anyhow try - renaming that 30MB OTA into PH85IMG.ZIP and placing it on your external sd card, then rebooting into Bootloader? And what?
Click to expand...
Click to collapse
(edit) Tries it at home. "I'll be damned...." (/edit)
Too much time spent with Nexus devices this year....
jauhien said:
Apparently it found your custom recovery / root / unlocked boot.. and stopped.
ChromeJob's handheld is the complete stock..
Click to expand...
Click to collapse
On my defective handset, I determined that you can apply the update with the bootloader unlocked, but you DO need to have stock recovery. The recovery image is in firmware.zip inside the OTA update zip file. Seems to require *NIX to unzip, old WinZIP on Windows reported it corrupted.
jauhien said:
Did you anyhow try - renaming that 30MB OTA into PH85IMG.ZIP and placing it on your external sd card, then rebooting into Bootloader? And what?
Click to expand...
Click to collapse
It reads the file, there's a little vertical gas gauge that fills up on the upper right of the screen, then ... nothing. Whut next?
Just an update for those who find this thread. HTC tech support assure me that putting the OTA update in the root of the external SD card (microSDHC) renamed to PH85IMG.ZIP should work. But it never did. I just left the phone on for 10 days, it never automagically alerted me to the update (with regular checks selected/enabled), but a few mornings ago I tapped "Check now" and it found it. Downloaded, installed, etc.
After unlocking again I found that I could boot from CWM recovery externally, make a nandroid backup, etc. So now I can play and restore the system to stock ... after determining if the OTA fixes anything for me.
BIG THANKS to those trying to help. I don't think your suggestions were at fault (though telling me to flash it to an RUU ROM when it was already 100% stock makes no self-evident sense to me), I think HTC hboot, fastboot, and stock recovery are eccentric and faulty.[1] I still learned some tricks and skills from you.... I'm getting better at fastboot and adb on the command line, and understanding how the Android device architecture works.
[1] HTC's own tech support said what I was doing would succeed, but it didn't. Either their information is FU, or the Amaze is FU.
Somehow I managed to soft brick my AT&T HTC one...I've spent the last three days trying to fix it, but I am utterly failing. I'm at the point where I am trying to flash the factory RUU, but I have no idea which RUU.zip to use.
Basic Googling and troubleshooting has brought me to this post; http://forum.xda-developers.com/showthread.php?t=2428276 but I frankly have no idea which one I should choose. I've tried a few but they've all failed. I'm really just looking for some assistance on which zip to use and I should be able to take it from there.
kraze1994 said:
Somehow I managed to soft brick my AT&T HTC one...I've spent the last three days trying to fix it, but I am utterly failing. I'm at the point where I am trying to flash the factory RUU, but I have no idea which RUU.zip to use.
Basic Googling and troubleshooting has brought me to this post; http://forum.xda-developers.com/showthread.php?t=2428276 but I frankly have no idea which one I should choose. I've tried a few but they've all failed. I'm really just looking for some assistance on which zip to use and I should be able to take it from there.
Click to expand...
Click to collapse
Are you S-ON or S-OFF? Also, what version number are you along with your HBOOT. You can do "fastboot getvar all" PLEASE DON'T POST YOUR SERIAL AND IMEI!!!
GalaxyUser50 said:
Are you S-ON or S-OFF? Also, what version number are you along with your HBOOT. You can do "fastboot getvar all" PLEASE DON'T POST YOUR SERIAL AND IMEI!!!
Click to expand...
Click to collapse
I am S-ON and HBOOT is 1.56.0000
kraze1994 said:
I am S-ON and HBOOT is 1.56.0000
Click to expand...
Click to collapse
Try the one thats named: RUU M7 UL K44 SENSE55 MR Cingular US 4.18.502.7 R10 Radio 4T.24.3218.09 10.26.1718.01L Release 356565 Signed 2 (AT&T)
Thats the latest kitkat update. Its signed so it should work for S-On
GalaxyUser50 said:
Try the one thats named: RUU M7 UL K44 SENSE55 MR Cingular US 4.18.502.7 R10 Radio 4T.24.3218.09 10.26.1718.01L Release 356565 Signed 2 (AT&T)
Thats the latest kitkat update. Its signed so it should work for S-On
Click to expand...
Click to collapse
I attempted that one but I can't even get to .exe to run. So I moved onto..
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 Radio 4A.19.3263.13 10.38j.1157.04 Release 334235 Signed 2
I'll report back to let you know if it worked.
kraze1994 said:
I attempted that one but I can't even get to .exe to run. So I moved onto..
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 Radio 4A.19.3263.13 10.38j.1157.04 Release 334235 Signed 2
I'll report back to let you know if it worked.
Click to expand...
Click to collapse
I can't get any of those .exes to work. First one just doesn't open and the second one gives me an error; http://i.imgur.com/YlSItRE.png .
Any suggestions on which .zip files I should use?
kraze1994 said:
I can't get any of those .exes to work. First one just doesn't open and the second one gives me an error; http://i.imgur.com/YlSItRE.png .
Any suggestions on which .zip files I should use?
Click to expand...
Click to collapse
Have you tried "Run as admin" through a right click? Also did you check the MD5? Not sure if the zip files would work because they use an older version and I don't think you can flash an older version with S-ON
GalaxyUser50 said:
Have you tried "Run as admin" through a right click? Also did you check the MD5? Not sure if the zip files would work because they use an older version and I don't think you can flash an older version with S-ON
Click to expand...
Click to collapse
Yes, I tried running as admin on both and the MD5's seem to correct.
kraze1994 said:
Yes, I tried running as admin on both and the MD5's seem to correct.
Click to expand...
Click to collapse
Hmm. What are you able to get into right now? Only HBOOT? Recovery?
GalaxyUser50 said:
Hmm. What are you able to get into right now? Only HBOOT? Recovery?
Click to expand...
Click to collapse
I can get into bootloader and recovery without issues. Though, I keep seeing a pattern here when I try to sideload roms..etc. It doesn't seem like my SD card is mounting properly and I'm not sure how to fix that.
kraze1994 said:
I can get into bootloader and recovery without issues. Though, I keep seeing a pattern here when I try to sideload roms..etc. It doesn't seem like my SD card is mounting properly and I'm not sure how to fix that.
Click to expand...
Click to collapse
Ok, I assume that its a custom recovery, TWRP? What happens when you try to side load a rom? Or any file?
---------- Post added at 07:42 PM ---------- Previous post was at 07:01 PM ----------
GalaxyUser50 said:
Ok, I assume that its a custom recovery, TWRP? What happens when you try to side load a rom? Or any file?
Click to expand...
Click to collapse
You could try the Stock Nandroids for your recovery from that thread if you are able to push a file.
GalaxyUser50 said:
Ok, I assume that its a custom recovery, TWRP? What happens when you try to side load a rom? Or any file?
Click to expand...
Click to collapse
Yes, it's TWRP. The process of sideloading the rom works fine, but it doesn't complete after that(I'm working on getting the exact error).
You could try the Stock Nandroids for your recovery from that thread if you are able to push a file.
Click to expand...
Click to collapse
I'm trying to do this, but it keeps telling me "device not found". I'm trying to figure out why.
kraze1994 said:
Yes, it's TWRP. The process of sideloading the rom works fine, but it doesn't complete after that(I'm working on getting the exact error).
I'm trying to do this, but it keeps telling me "device not found". I'm trying to figure out why.
Click to expand...
Click to collapse
I'm sure you're doing this already, but you are both in the side load menu on TWRP and used the command "adb sideload /sdcard/file" with file being the thing you're trying to side load?
EDIT: A copy of the adb prompt may help me.
GalaxyUser50 said:
I'm sure you're doing this already, but you are both in the side load menu on TWRP and used the command "adb sideload /sdcard/file" with file being the thing you're trying to side load?
EDIT: A copy of the adb prompt may help me.
Click to expand...
Click to collapse
I was able to get it recognized and pushed the TWRP Nandroid onto the SD card, but it doesn't want to restore it. Going to the restore tab shows no files and if I attempt to just flash it. It says "Unable to open zip file". Which makes sense as I couldn't open it locally, but I also tried another one with the same results.
kraze1994 said:
I was able to get it recognized and pushed the TWRP Nandroid onto the SD card, but it doesn't want to restore it. Going to the restore tab shows no files and if I attempt to just flash it. It says "Unable to open zip file". Which makes sense as I couldn't open it locally, but I also tried another one with the same results.
Click to expand...
Click to collapse
Ok, I see, you have to extract the zip and place it into the TWRP backups folder. Haven't used twrp in a while, but isn't there a file manager? If possible you need to extract the zip file and place the folder in the TWRP/BACKUPS/SerialNumber/. I believe that is the directory.
I'm sorry I didn't realize that before.
GalaxyUser50 said:
Ok, I see, you have to extract the zip and place it into the TWRP backups folder. Haven't used twrp in a while, but isn't there a file manager? If possible you need to extract the zip file and place the folder in the TWRP/BACKUPS/SerialNumber/. I believe that is the directory.
I'm sorry I didn't realize that before.
Click to expand...
Click to collapse
I was able to find the folder, but I can't actually unzip the file. Winrar throws..
\HTCOne.zip: Unexpected end of archive.
I've tried with several of those nandroid backups as well.
kraze1994 said:
I was able to find the folder, but I can't actually unzip the file. Winrar throws..
\HTCOne.zip: Unexpected end of archive.
I've tried with several of those nandroid backups as well.
Click to expand...
Click to collapse
Are you able to push a rom, maybe a stock one, to TWRP?
GalaxyUser50 said:
Are you able to push a rom, maybe a stock one, to TWRP?
Click to expand...
Click to collapse
I tried that and it actually pushed without error, but upon boot I just get a black screen. I'm in the process of getting a different one and trying again. I'll report back on if it works or not.
I really do appreciate the help thus far, thank you!
I finally got it working! There is something up with htc1guru.com which is causing it to terminate downloads after a certain period of time. I downloaded it from a server of mine, pushed it to the device and restored. Only issue now is that the touch screen is not working, which I was expecting, but I'm trying to figure out how to issue an OTA update without being able to use the screen.
kraze1994 said:
I finally got it working! There is something up with htc1guru.com which is causing it to terminate downloads after a certain period of time. I downloaded it from a server of mine, pushed it to the device and restored. Only issue now is that the touch screen is not working, which I was expecting, but I'm trying to figure out how to issue an OTA update without being able to use the screen.
Click to expand...
Click to collapse
That's good to hear. What file did you get to work, the RUU, or backup?