Database Develop

[Q] Vivid Leaked ICS to Official ICS

I upgraded my phone using the leaked ICS build that hit a little bit before the final one was released. I would like to get my phone updated to the official ICS build. I was looking through GSLEON's thread in the dev forum and he mentions:
GSLEON3 said:
The absolute safest way to update to ICS is to relock your device & return it to as close to stock as you can get it. Relocked you can flash the leaked GB AT&T rom in football's thread.
Click to expand...
Click to collapse
I found the thread: http://forum.xda-developers.com/showthread.php?t=1338919 and am downloading RUU_Holiday_Cingular_US_1.63.502.4_Radio_1.11.1020.03_30.77.551061.02L_release_221238_signed.exe
In the "Official AT&T Vivid ICS RUU from HTC" thread GSLEON3 says
GSLEON3 said:
Make sure that if you have a custom recovery that is is updated & double check that it is. Write the version numbers down to confirm, both before & after.
There was an early recovery that could not (CANNOT) be overwritten without flashing a modified PH39IMG file first, then flashing stock or new modified recovery.
If you update with your device with that original recovery, you may be very sorry.
Click to expand...
Click to collapse
I'm pretty sure this applies to me, here's my information:
Code:
Locked
Holiday PVT Ship S-On RL
Hboot-1.85.0024
MICROP-0360
OpenADSP-v02.6.0.226.00.0202
eMMC-boot
Feb 10 2012,22:49:47
Software Information
More Screen
My problem with this is two-fold:
1. I'm not sure where to get the specially modified ph39img
2. I'm really nervous because I like my phone a lot!
Any help you can offer would be really appreciated!
Here's a screenshot of my homescreen because I accidentally took one while getting it out of the case!

newsaint said:
I upgraded my phone using the leaked ICS build that hit a little bit before the final one was released. I would like to get my phone updated to the official ICS build. I was looking through GSLEON's thread in the dev forum and he mentions:
I found the thread: http://forum.xda-developers.com/showthread.php?t=1338919 and am downloading RUU_Holiday_Cingular_US_1.63.502.4_Radio_1.11.1020.03_30.77.551061.02L_release_221238_signed.exe
In the "Official AT&T Vivid ICS RUU from HTC" thread GSLEON3 says
I'm pretty sure this applies to me, here's my information:
Code:
Locked
Holiday PVT Ship S-On RL
Hboot-1.85.0024
MICROP-0360
OpenADSP-v02.6.0.226.00.0202
eMMC-boot
Feb 10 2012,22:49:47
Software Information
More Screen
My problem with this is two-fold:
1. I'm not sure where to get the specially modified ph39img
2. I'm really nervous because I like my phone a lot!
Any help you can offer would be really appreciated!
Here's a screenshot of my homescreen because I accidentally took one while getting it out of the case!
Click to expand...
Click to collapse
Well firstly the RUU your referring to is for official gingerbread. You dont need to flash the modified file unless you have the old recovery so thats un needed. Use this official RUU link http://dl3.htc.com/application/htc_vivid_att_RUU_3.26.502.56_US.exe to flash your phone to the official ics build.

Thanks for the heads up, sorry for misinterpreting things. I'll give this a go when I get off work!

Looks like it worked! Thanks again

TWRP OK?
I have done some research on this and have found that I can get s-off by flashing a RUU rom. The thing is is that I have to have an updated recovery. Right NOw i have the TWRP 2.4.4.0 and wondering if Im good to flash the RUU or if i need to return to stock recovery.
I dont mind losing root as I can re root it.
Originally Posted by sketchscarz View Post
I used the steps and it gives me this message. I am s-on
Old beer detected...... Ple
Starting up......
Connecting to device...
Backing up......
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.....
Try it again but you have to use original RUU ICS for your device before following these steps
you can download that from here : http://forum.xda-developers.com/show....php?t=1564776

vivid almost unlocked need to verify recovery or flash stock recovery
config.dat ran to change radio, since not s=off failed.
need to flash recovery to stock recovery/ current recovery could brick phone whjen flashing stock RUU .IMG ROM
Not positive that i have the recovery that makes brick sandwich, becasue there is a old recovery that does not allow certain system files to fetch the files needed to install RUU.
Need to verify recovery/flash stock RUU rom
if recovery is not verified / flash stock recovery
proceed to write radio
---------- Post added at 03:58 AM ---------- Previous post was at 03:25 AM ----------
sketchscarz said:
config.dat ran to change radio, since not s=off failed.
need to flash recovery to stock recovery/ current recovery could brick phone whjen flashing stock RUU .IMG ROM
Not positive that i have the recovery that makes brick sandwich, becasue there is a old recovery that does not allow certain system files to fetch the files needed to install RUU.
Need to verify recovery/flash stock RUU rom
if recovery is not verified / flash stock recovery
proceed to write radio
Click to expand...
Click to collapse
Found some more research with the borked ROm which seems to turn s-off. The rom is compiled from a stock ruu so im thinking I can still flash this Unlock_code.bin and get me unlocked with this awesome rom
http://forum.xda-developers.com/showthread.php?t=2171741
all thanks goes to homeslice976 and please dont beat me up for posting your link as I am looking for easier ways to get this phone unlocked so i can activate it on tmobile.
It seems that I have found an alternative to having the bootloader unlocked and the s-off to be able to change the radio to tmobile with Unlock_code.bin on the stock RUU img
I have since flashed the WXC recovery pretty awesome wildchild, great work!

[Q] Back to stock for Waranty

Hi,
I need to get my phone back to stock for warranty before my USB port completely dies (not it works only at certain angles).
I read few threads regarding getting the phone back to stock but I am missing few infos I am asking for your help on this.
The data that I got and believe that is needed:
mainver: 2.32.1010.1
RADIO: 3822.01.08.14_M
HBOOT: 6.13.1002
and I bough phone in Switzerland and have: HTC_GER version (102)
I believe that following the post http://forum.xda-developers.com/showthread.php?t=1359555 is the way to go.
Which RUU do I use due to my mainver ang HTC_GER?
Will vivo_downgrade.img from mentioned thread work for me; basically should the procedure and links on mentioned thread work for my phone?
Thank you very much!

mrepovz said:
Hi,
I need to get my phone back to stock for warranty before my USB port completely dies (not it works only at certain angles).
I read few threads regarding getting the phone back to stock but I am missing few infos I am asking for your help on this.
The data that I got and believe that is needed:
mainver: 2.32.1010.1
RADIO: 3822.01.08.14_M
HBOOT: 6.13.1002
and I bough phone in Switzerland and have: HTC_GER version (102)
I believe that following the post http://forum.xda-developers.com/showthread.php?t=1359555 is the way to go.
Which RUU do I use due to my mainver ang HTC_GER?
Will vivo_downgrade.img from mentioned thread work for me; basically should the procedure and links on mentioned thread work for my phone?
Thank you very much!
Click to expand...
Click to collapse
Yes you have found the correct procedure to follow:
At this link:
http://forum.xda-developers.com/showthread.php?t=1033922
I noticed that they have the 2.32.1010.1 RUU that you should use given the current mainver you have.

Thank you but I do have a question regarding the radio.
Will I have a problem flashing mainver RUU since I upgraded the radio or will everything work ok?
Sent from my HTC Incredible S using XDA App

mrepovz said:
Thank you but I do have a question regarding the radio.
Will I have a problem flashing mainver RUU since I upgraded the radio or will everything work ok?
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
The RUU should work

I checked on http://www.filefactory.com/f/e45d6fe3dcf51228/ for ROM for mainver: 2.32.1010.1 nad it is KT_KR (honestly I do not know what it stands for) but I figured out that my phone is suppose to have HTC_GER version (102).
How will that work for warranty - which ROM to use?

mrepovz said:
I checked on http://www.filefactory.com/f/e45d6fe3dcf51228/ for ROM for mainver: 2.32.1010.1 nad it is KT_KR (honestly I do not know what it stands for) but I figured out that my phone is suppose to have HTC_GER version (102).
How will that work for warranty - which ROM to use?
Click to expand...
Click to collapse
Then you will need to use the 3.08.405.3 version because the 2.30.405.1 version is lower than the mainver that your phone is reporting. You only option is to use a RUU with a higher version. You should be able to use 3.08.405.3 for your region.

Now I am stuck at splash screen.
What I did is download RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed.exe
got out the rom.zip file, renamed it to PG32...zip and rebooted my phone to update (go back to stock ROM). Later my intentions were to use the vivodowngrade to get back to S-ON.
After the update I am stuck at HTC logo. What to do?

mrepovz said:
Now I am stuck at splash screen.
What I did is download RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed.exe
got out the rom.zip file, renamed it to PG32...zip and rebooted my phone to update (go back to stock ROM). Later my intentions were to use the vivodowngrade to get back to S-ON.
After the update I am stuck at HTC logo. What to do?
Click to expand...
Click to collapse
Just follow this guide.

I managed to somehow get it to the next state:
I installed a rom.zip form (RUU_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signe.exe) since it has the same maiver as I had it by renaming it to PG32IMG.zip and placing it to the SD.
After "flashing" it wrote me that it is a wrong version. The result:
If I turn it off it turns on again by it self (I can't turn it off unless i bull the battery) and it displays (no ROM is started):
**** Security Warning****
VIVO PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-3805.06.03.16_M
eMMC-boot
...
...
...
It looks like it is S-ON - is this correct? (I might have done something wright )
Can I now try to install a RUU (RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed.exe) ? or do I have to get rom.zip and the procedure on http://forum.xda-developers.com/showthread.php?t=1359555 ?
Thank you!

I tried to install via RUU and it worked
Thanks everyone for help

[Q] I'm lost and have no idea where to go from here.

Okay so rewind back to July, I just got my T-Mobile HTC One and the first thing I do is unlock the bootloader, install a custom recovery and flash the HTC One Google Play Edition rom. Now, I do not remember anything about rooting or bootloader or anything of the sort and I desperately want to go back to Stock.
I have tried reading tutorials on it but they all use terms I don't fully understand (SID, HBOOT, DEOXED etc) and have instructions that seem very vague to me and I really do not want to brick my phone. I'm not sure how to check my firmware, recovery version or anything of the sort. I also do not have root access for some reason and I can't flash most roms (I think the cyanogen based ones) as it gives me the "wrong device" error (I am definitely sure I'm not trying to flash the wrong rom onto my device).
tl;dr: I want to have a stock HTC rom with root privileges and have no clue how to do it.
Here's the info I do have
Rom: http://forum.xda-developers.com/showthread.php?t=2341395 (This may be an updated version)
Android Version: 4.3
Kernel Version: 3.4.10 (ge22f38b)
Clockwork Mod recovery: 6.0.3.3
S-On
HBOOT: 1.44.0000
Radio: 4A.14.3250.15
Ps. In this thread (http://forum.xda-developers.com/showthread.php?t=2353812) what do the numbers 1.27.531.8 and 1.27.531.11 mean, and how can I find out which one my phone has?

Unoriginal_Name said:
Okay so rewind back to July, I just got my T-Mobile HTC One and the first thing I do is unlock the bootloader, install a custom recovery and flash the HTC One Google Play Edition rom. Now, I do not remember anything about rooting or bootloader or anything of the sort and I desperately want to go back to Stock.
I have tried reading tutorials on it but they all use terms I don't fully understand (SID, HBOOT, DEOXED etc) and have instructions that seem very vague to me and I really do not want to brick my phone. I'm not sure how to check my firmware, recovery version or anything of the sort. I also do not have root access for some reason and I can't flash most roms (I think the cyanogen based ones) as it gives me the "wrong device" error (I am definitely sure I'm not trying to flash the wrong rom onto my device).
tl;dr: I want to have a stock HTC rom with root privileges and have no clue how to do it.
Here's the info I do have
Rom: http://forum.xda-developers.com/showthread.php?t=2341395 (This may be an updated version)
Android Version: 4.3
Kernel Version: 3.4.10 (ge22f38b)
Clockwork Mod recovery: 6.0.3.3
S-On
HBOOT: 1.44.0000
Radio: 4A.14.3250.15
Ps. In this thread (http://forum.xda-developers.com/showthread.php?t=2353812) what do the numbers 1.27.531.8 and 1.27.531.11 mean, and how can I find out which one my phone has?
Click to expand...
Click to collapse
Read this first, if you still have questions, post back here
http://forum.xda-developers.com/showthread.php?t=2358738

[Q] Help unrooting a problematic (only turns on into bootloader) htc one m7

Hi all, I have a rooted htc m7 who I'd like to give to my niece however it's a bit problematic at the moment:
Whenever it runs out of battery or is turned off for some reason it needs to be turned on into bootloader mode and then restarted, it won't start otherwise.
Since I rooted it and am running a different bootloader, I assume that is the cause and would therefore like to un-root it and return it to how it was before I started fidgeting with it.
Some info you might want:
I'm running the stock (htc) android version: 4.4.2 - Android_Revolution_HD-One_81.0.zip
Htc sense version 5.5
Software number 4.19.401.11
HTC sdk level 5.68
Baseband 4A.14.3250.13_10.33.1150.01L
Kernel 3.4.10-g7fe1bad [email protected] #1 SMP PREEMPT
Build number 4.19.401.11 CL304164 release-keys
Bootloader:
[*]M7_UL PVT SHIP S-ON RH​[*]HBOOT-1.44.0000​[*]RADIO-4A.14.3250.13​[*]OpenDSP-v26.120.274.0202​[*]eMMC-boot​[*]Mar 18 2013,18:29:18:-1​
Recovery:
[*]Team Win Recovery Project v2.7.0.0 (TWRP)​
Thanks in advance for any help you could provide
P.S,
The rom also has two other problems I think my niece wouldn't like:
1. it doesn't update OTA
2. it has a red message on the screen when it boots saying that it's tampered, I know it's silly but I want it to look new...

eladkatz said:
Hi all, I have a rooted htc m7 who I'd like to give to my niece however it's a bit problematic at the moment:
Whenever it runs out of battery or is turned off for some reason it needs to be turned on into bootloader mode and then restarted, it won't start otherwise.
Since I rooted it and am running a different bootloader, I assume that is the cause and would therefore like to un-root it and return it to how it was before I started fidgeting with it.
Some info you might want:
I'm running the stock (htc) android version: 4.4.2 - Android_Revolution_HD-One_81.0.zip
Htc sense version 5.5
Software number 4.19.401.11
HTC sdk level 5.68
Baseband 4A.14.3250.13_10.33.1150.01L
Kernel 3.4.10-g7fe1bad [email protected] #1 SMP PREEMPT
Build number 4.19.401.11 CL304164 release-keys
Bootloader:
[*]M7_UL PVT SHIP S-ON RH​[*]HBOOT-1.44.0000​[*]RADIO-4A.14.3250.13​[*]OpenDSP-v26.120.274.0202​[*]eMMC-boot​[*]Mar 18 2013,18:29:18:-1​
Recovery:
[*]Team Win Recovery Project v2.7.0.0 (TWRP)​
Thanks in advance for any help you could provide
P.S,
The rom also has two other problems I think my niece wouldn't like:
1. it doesn't update OTA
2. it has a red message on the screen when it boots saying that it's tampered, I know it's silly but I want it to look new...
Click to expand...
Click to collapse
can i assume u have unlocked ur phone via HTCdev?

ictoaun said:
can i assume u have unlocked ur phone via HTCdev?
Click to expand...
Click to collapse
Yep

eladkatz said:
Yep
Click to expand...
Click to collapse
Change your recovery some people have had issues with that one. Try TWRP 2.6.3.3 it seems to work better with ARHD. FYI, most roms don't install or change the bootloader that is done with firmware.

eladkatz said:
Yep
Click to expand...
Click to collapse
Your hboot is 1.44 it should be very easy to s-off and return the phone to stock. So it will get OTA and etc.
See @nkk71 Superguide here for instructions
http://forum.xda-developers.com/showthread.php?t=2541082
you can also just flash this RUU and the phone will be Stock but relocked
http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
to relock the bootloader to run the RUU
use fastboot in command prompt
with the phone in the bootloader screen (power + volume down)
bootlooder in fastboot USB (this happens when you hook up the phone to the PC)
now from command prompt use
fastboot oem lock
your now ready to run the RUU on the PC and the phone will be back to stock

[Q] Questions about hboot version, Kernel, and Firmware

Hello,
I have just been given a rooted HTC M7 (AT&T). It hasn't been used for almost a year, but it seems to work. It only has a recovery on it, not a ROM. I have no idea how to get it from where it is up to the latest and greatest. Any help or recommendations would be appreciated. I tried to read up on everything, but i couldn't parse out the info I needed from existing threads. I hope my terminology is correct!
Here's what I've got:
Device: AT&T HTC One M7
BOOTLOADER Info:
*** Tampered ***
*** Unlocked ***
M7_UL PVT SHIP S-OFF RH
CID-CWS_001
HBOOT-1.4.4.0000
RADIO-4a.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013, 19:16:59: -1
RECOVERY Info:
TWRP 2.8.1.0
ROM INFO:
I have not loaded a rom onto the device at this point. I haven't felt comfortable since I don't know if the phone in its current state will run the latest roms.
Here's what I need to know.
1. Do I need to update my bootloader? It seems like 1.44 is much older than what other people are currently using. I've seen most people on 1.57 or 1.56. If I do need to update it, what version should I update to?
2. My recovery seems to be almost up to date. I am pretty sure i know how to get the .zip for the latest version, but I don't know if I have to flash it or use another way to install it.
3. I cannot get fastboot working on my windows 8.1 machine. It does work on an old windows 7 laptop I have. It seems like others have this issue on hboot 1.44. Is there any fix for it?
4. Firmware, Kernals, and Radios. How do you know what firmware, kernel, and radio to use for a given device? does it depend on the rom you choose? There seems to be so many and it isn't clear to me.
5. Does it matter if i choose a GPE rom, a Cyanogen Rom, or a Sense Rom? Do kernels, firmwares, and radios depend on the type of rom I choose?
Thanks for all your help! I look forward to using my new to me device.

thenaysayer said:
Hello,
I have just been given a rooted HTC M7 (AT&T). It hasn't been used for almost a year, but it seems to work. It only has a recovery on it, not a ROM. I have no idea how to get it from where it is up to the latest and greatest. Any help or recommendations would be appreciated. I tried to read up on everything, but i couldn't parse out the info I needed from existing threads. I hope my terminology is correct!
Here's what I've got:
Device: AT&T HTC One M7
BOOTLOADER Info:
*** Tampered ***
*** Unlocked ***
M7_UL PVT SHIP S-OFF RH
CID-CWS_001
HBOOT-1.4.4.0000
RADIO-4a.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013, 19:16:59: -1
RECOVERY Info:
TWRP 2.8.1.0
ROM INFO:
I have not loaded a rom onto the device at this point. I haven't felt comfortable since I don't know if the phone in its current state will run the latest roms.
Here's what I need to know.
1. Do I need to update my bootloader? It seems like 1.44 is much older than what other people are currently using. I've seen most people on 1.57 or 1.56. If I do need to update it, what version should I update to?
2. My recovery seems to be almost up to date. I am pretty sure i know how to get the .zip for the latest version, but I don't know if I have to flash it or use another way to install it.
3. I cannot get fastboot working on my windows 8.1 machine. It does work on an old windows 7 laptop I have. It seems like others have this issue on hboot 1.44. Is there any fix for it?
4. Firmware, Kernals, and Radios. How do you know what firmware, kernel, and radio to use for a given device? does it depend on the rom you choose? There seems to be so many and it isn't clear to me.
5. Does it matter if i choose a GPE rom, a Cyanogen Rom, or a Sense Rom? Do kernels, firmwares, and radios depend on the type of rom I choose?
Thanks for all your help! I look forward to using my new to me device.
Click to expand...
Click to collapse
you have an AT&T Phone with s-off. Start updating with this RUU from windows 7
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
After this RUU windows 8 will see your phone again
Then this Firmware > http://fs1.d-h.st/download/00101/a1w/4.18.502.7 Custom Firmware.zip
followed by this RUU >> http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
To flash the Firmware use
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
when your done check for software updates in settings before you flash a custom recovery and root.
you should get the 5.x.502 OTA update

Amazing. Thank you so much.

clsA said:
you have an AT&T Phone with s-off. Start updating with th....and root.
you should get the 5.x.502 OTA update
Click to expand...
Click to collapse
just clearing concepts
Why you told him to 1st flash ruu then firmware then higher ruu
Why not higher firmware or ruu directly ?

yatindroid said:
just clearing concepts
Why you told him to 1st flash ruu then firmware then higher ruu
Why not higher firmware or ruu directly ?
Click to expand...
Click to collapse
because a lot of people have problem flashing the 4.x RUU alone, they get a error 155 .. flashing the firmware first solves this problem
And the 3.x Full RUU insures he does not get any problem upgrading from hboot 1.44
so he in fact went the same route AT&T released the updates