Hello,
Cause I want to get SuperCID (just for fun) I decided to downgrade to RUU_Vivo_HTC_WWE_1.36.405.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172670_signed.exe
I was running ARHD 3.0, stock ICS kernel and the latest ICS Radio and 4EXT Recovery. First I used Nonverbose's script to lower my software version. I only changed in his 'runme.cmd' the lines 'misc_version -s 2.00.000.0' to 'misc_version -s 1.00.000.0', cause software version 2.00 is to high for RUU 1.36 WWE.
I did that without errors and directly after that I flashed the RUU. That RUU flashed also in a few minutes without errors and when the phone tried to start for the first time it was totally dead. Nothing signal at all. Only thing I got is this while running 'fastboot devices'
Code:
└▼áß*0000000 fastboot
I can run other commands but nothing is happen. I guess I screwed my phone cause the overwrite protection of Revolutiony HBOOT. What can I do?
I'm able to run RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe, but it hangs on 'waiting for bootloader...', of course it's hanging there, the bootloader is totally screwed.
Can I cure my phone with the RIFF JTAG Box?
Inferi0r said:
Hello,
Cause I want to get SuperCID (just for fun) I decided to downgrade to RUU_Vivo_HTC_WWE_1.36.405.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172670_signed.exe
I was running ARHD 3.0, stock ICS kernel and the latest ICS Radio and 4EXT Recovery. First I used Nonverbose's script to lower my software version. I only changed in his 'runme.cmd' the lines 'misc_version -s 2.00.000.0' to 'misc_version -s 1.00.000.0', cause software version 2.00 is to high for RUU 1.36 WWE.
I did that without errors and directly after that I flashed the RUU. That RUU flashed also in a few minutes without errors and when the phone tried to start for the first time it was totally dead. Nothing signal at all. Only thing I got is this while running 'fastboot devices'
Code:
└▼áß*0000000 fastboot
I can run other commands but nothing is happen. I guess I screwed my phone cause the overwrite protection of Revolutiony HBOOT. What can I do?
I'm able to run RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe, but it hangs on 'waiting for bootloader...', of course it's hanging there, the bootloader is totally screwed.
Click to expand...
Click to collapse
You know you are not suppose to downgrade misc_version lower than 2.00 as it's fatal to your phone :sly:
Sent from my HTC Incredible S using xda premium
zukri90 said:
You know you are not suppose to downgrade misc_version lower than 2.00 as it's fatal to your phone :sly:
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
Lol, I didn't know. I know now. What can I do?
I think this looks great, but I've to pay 120 euro at least for that RIFF Box. Maybe they will repair my phone under warranty cause they don't know why it won't get on? I'm still in the warranty period and the phone looks very nice and untouched.
Inferi0r said:
Lol, I didn't know. I know now. What can I do?
I think this looks great, but I've to pay 120 euro at least for that RIFF Box. Maybe they will repair my phone under warranty cause they don't know why it won't get on? I'm still in the warranty period and the phone looks very nice and untouched.
Click to expand...
Click to collapse
give it a go under warrenty
Inferi0r said:
Hello,
Cause I want to get SuperCID (just for fun) I decided to downgrade to RUU_Vivo_HTC_WWE_1.36.405.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172670_signed.exe
I was running ARHD 3.0, stock ICS kernel and the latest ICS Radio and 4EXT Recovery. First I used Nonverbose's script to lower my software version. I only changed in his 'runme.cmd' the lines 'misc_version -s 2.00.000.0' to 'misc_version -s 1.00.000.0', cause software version 2.00 is to high for RUU 1.36 WWE.
I did that without errors and directly after that I flashed the RUU. That RUU flashed also in a few minutes without errors and when the phone tried to start for the first time it was totally dead. Nothing signal at all. Only thing I got is this while running 'fastboot devices'
Code:
└▼áß*0000000 fastboot
I can run other commands but nothing is happen. I guess I screwed my phone cause the overwrite protection of Revolutiony HBOOT. What can I do?
I'm able to run RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe, but it hangs on 'waiting for bootloader...', of course it's hanging there, the bootloader is totally screwed.
Can I cure my phone with the RIFF JTAG Box?
Click to expand...
Click to collapse
You have officially radio bricked your phone. All of the GB ROMS and above used version 2 of the radio and you cannot downgrade or flash the radio back to version 1 which you have tried to do with the RUU you chose to flash. You now have a bricked phone and I have not seen any documented procedures that an end user can do to get out of this state.
tpbklake said:
You have officially radio bricked your phone. All of the GB ROMS and above used version 2 of the radio and you cannot downgrade or flash the radio back to version 1 which you have tried to do with the RUU you chose to flash. You now have a bricked phone and I have not seen any documented procedures that an end user can do to get out of this state.
Click to expand...
Click to collapse
Oke that would make sense. Cause misc_version succesfully lowered my version number to 1.00 and I was be able to run a full RUU downgrade after that, it couldn't be the version thing.
I remember that there is truly a overwrite protection on Revolutionary which has to be disabled first, but also that RUU 1.36 WWE is running hboot-1.09 and that Revolutionary should be running that hboot too.
I guess it defenitley a RADIO thing then. I will give it a go under warranty. I hope that they won't be able to see that I'm still on a S-OFF device. But just for documentation, what would be the right procedure to go from an ICS ROM+ICS Radio to Froyo ROM+Froyo Radio. How should we do that?
If even the official RUU can't downgrade that Radio, what else can do?
I don't think there is any way to go back to Froyo, as per what tpbklake said. You can only go back to GB.
Out of interest, what was the reasoning of going back to a Froyo ROM? Is this supposed to open up a different method of altering your CID?
mr nick said:
I don't think there is any way to go back to Froyo, as per what tpbklake said. You can only go back to GB.
Out of interest, what was the reasoning of going back to a Froyo ROM? Is this supposed to open up a different method of altering your CID?
Click to expand...
Click to collapse
Yes, with the tool incsfree (in dev section) we should be able to get SuperCID, but the tool works only on Froyo. Froyo and S-OFF should be enough.
Sent from my HTC One S using xda premium
Inferi0r said:
Oke that would make sense. Cause misc_version succesfully lowered my version number to 1.00 and I was be able to run a full RUU downgrade after that, it couldn't be the version thing.
I remember that there is truly a overwrite protection on Revolutionary which has to be disabled first, but also that RUU 1.36 WWE is running hboot-1.09 and that Revolutionary should be running that hboot too.
I guess it defenitley a RADIO thing then. I will give it a go under warranty. I hope that they won't be able to see that I'm still on a S-OFF device. But just for documentation, what would be the right procedure to go from an ICS ROM+ICS Radio to Froyo ROM+Froyo Radio. How should we do that?
If even the official RUU can't downgrade that Radio, what else can do?
Click to expand...
Click to collapse
mr nick said:
I don't think there is any way to go back to Froyo, as per what tpbklake said. You can only go back to GB.
Out of interest, what was the reasoning of going back to a Froyo ROM? Is this supposed to open up a different method of altering your CID?
Click to expand...
Click to collapse
There is no way to revert a ROM/radio combo once you are on V2 back to a V1 ROM/radio combo!
Woah guys:laugh:
The didn't see at HTC that I screwed the phone myself. They did a boardswap under warranty for free and my phone is up and running again.
Inferi0r said:
Woah guys:laugh:
The didn't see at HTC that I screwed the phone myself. They did a boardswap under warranty for free and my phone is up and running again.
Click to expand...
Click to collapse
Awesome, glad to see you're up and running, welcome back
If its actually dead and doesn't do anything, from experience at other service centres I have had, its not worth replacing one part to fix the phone, taking an hour or so, rather than just replace the motherboard for double/triple the cost, but only a few mins
Happy to have you back mate and to hear some good news
Sent from my Incredible S
Inferi0r said:
Woah guys:laugh:
The didn't see at HTC that I screwed the phone myself. They did a boardswap under warranty for free and my phone is up and running again.
Click to expand...
Click to collapse
So did you retrieve s-off and root in your phone? And never downgrade your misc_version lower than 2.00 :/
Sent from my potato chips using xda qwertyuiop
Inferi0r said:
Woah guys:laugh:
The didn't see at HTC that I screwed the phone myself. They did a boardswap under warranty for free and my phone is up and running again.
Click to expand...
Click to collapse
You're lucky you still had warranty left. Congrats on getting your phone back to working condition. I didn't see this thread when you originally posted this.
Related
So I just s-offed using Alpha rev last nigh and then rooted using gingerbreak. I've been able to flash both Android Rev. and Unity but in both cases I lose any incall earpiece or speaker sound when attempting a call. speaker works for music and slacker. Anyone else seeing this issue. I've not flashed a new radio in both cases
gmarcoux said:
So I just s-offed using Alpha rev last nigh and then rooted using gingerbreak. I've been able to flash both Android Rev. and Unity but in both cases I lose any incall earpiece or speaker sound when attempting a call. speaker works for music and slacker. Anyone else seeing this issue. I've not flashed a new radio in both cases
Click to expand...
Click to collapse
i had the same issue; you need to flash the Gingerbread radio recommended in the respective ROM threads and you'll be good to go.
cortez.i said:
i had the same issue; you need to flash the Gingerbread radio recommended in the respective ROM threads and you'll be good to go.
Click to expand...
Click to collapse
Can this be done without the ENG HBOOT?
Don't you need a S-Off Radio for that? Only way I know to do that is the XTC Clip
ohh geez, in order for getting ENG HBOOT we need radio S-OFF, and software solution isnt up yet... lucky my stock radio matches the android rev radio
my AlphaRev keeps hanging at Acquring Root (method 2)
I seriously hate this Incredible S, after Gingerbread i've not nothing but trouble.
all I want to do is flash it to the different Aus Carrier Rom cos that has no issues apparently.
other than smashing the phone with a hammer, which I've done numerous times before, why is AlphaRev being a c**t?
I have an Asia Rom, apparently that causes trouble.
MADCV said:
my AlphaRev keeps hanging at Acquring Root (method 2)
I seriously hate this Incredible S, after Gingerbread i've not nothing but trouble.
all I want to do is flash it to the different Aus Carrier Rom cos that has no issues apparently.
other than smashing the phone with a hammer, which I've done numerous times before, why is AlphaRev being a c**t?
I have an Asia Rom, apparently that causes trouble.
Click to expand...
Click to collapse
Yes it is the asian rom because apparently gingerbreak is patched, you need to flash the optus or virgin or wwe rom using a goldcard, search in google how to create a goldcard.
first you flash virgin or wwe gb ruu
than you s-off
than birds make love, and we all happy..
Hawkysoft said:
first you flash virgin or wwe gb ruu
than you s-off
than birds make love, and we all happy..
Click to expand...
Click to collapse
I've tried that and no way has worked.
Plus I can't flash things with the S-On, hence me using this Alpha-Rev thing to get S-Off.
Ignoring that I still have S-on, since Alpha-Rev does nothing,
the RUU I downloaded, and I've down loaded 3 different AUS ones, gets to a certain point then says Error 131.
thats the official way.
or if I do it the "Volume Down/Power Button" with the renamed Zips on the SD Card
it loads and then says "Error, reboot" in a red font.
I seriously hate this phone.
It takes me 2 seconds to reflash a Nokia.
***Update***
Disregard, Alpha-Rev doesn't work on my Asia Rom, so i'm going to smash it with a small hammer and go back to my iphones and Nokias
You're going to go back to iphone which you can't flash? Relax a bit and actually search to solve your problem which you hijacked this thread for.
Sent from my HTC Incredible S using XDA Premium App
well no one was any help so yeah, looks like its back to Nokia for me
MADCV said:
well no one was any help so yeah, looks like its back to Nokia for me
Click to expand...
Click to collapse
Dude stop having a hissy fit and do some research, i too was a newbie but spending some time has taught me alot of things.
You don't need to be s-off to flash an ruu, i did it and it worked you just have to spend some time and do it properly.
http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
Make a goldcard first, then put it in your phone and flash the ruu.
Then you should be able to use alpharevx
Hello,
Please, I did root Incredible S, but I need to go back (unroot). I need back guarantee. Is this possible?
Thank you very much for your answers.
Just do an official update from here
http://forum.xda-developers.com/showthread.php?t=1033922
i only suggest that you do not do not flash HTC_WWE_2.30.405.1
(that one can not yet and maybe never be rooted)
also next time just try using the search button and this question had been answered before, but enjoy
Ouuu, thank you very much I was looking for, but I was confused, so I was completely out.
Hello, How do I install the shipped rom, if I am from the Czech Republic?
or it does not matter what install the rom?
and how do I install it, just run only one. exe?
thank you so much
Well done, but I still have the S-OFF. Does it matter when the claim or not? to complain.
No way to unroot if permanent s-off?
May I ask you about some details? Which RUU did you applied and so on?
I unlocked bootloader with xtc clip, rooted device my and am running the latest ARHD now. Everything works fine except when I try to unroot (flash the stock gingerbread). It seems to be just impossible. It doesn't matter if I try to run ruu on my Vista och use goldcard method I always get either "error [130]: model ID error" or "model id error uppdate fail"
I've used two sd-cards: Kingston 2mb that worked perfect on my old Legend and original Sandisk 8mb that was shipped with my Incredible S. I followed all possible tutorials step by step but without effect. I always get the same error.
I live in Sweden and I bought my device from retailer. I'm not really sure what's the valid RUU version for our region so I've used:
RUU_Vivo_Gingerbread_S_HTC_WWE_2.12.405.7_Radio_20.2804.30.085AU_3805.04.03.22_M_release_187295_signed
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed (especially this due to the same program and radio version)
but even optus and RUU_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20. 2810.30.085AU_3805.06.03.16_M_release_199684_signe d.
Unfortunately it's always the same error after reboot into bootloader. Has anybody of you (that used xtc clip but not only) faced the same problem? Is there any way to bypass it? I will be very very grateful for any answer.
m.kochan10 said:
May I ask you about some details? Which RUU did you applied and so on?
I unlocked bootloader with xtc clip, rooted device my and am running the latest ARHD now. Everything works fine except when I try to unroot (flash the stock gingerbread). It seems to be just impossible. It doesn't matter if I try to run ruu on my Vista och use goldcard method I always get either "error [130]: model ID error" or "model id error uppdate fail"
I've used two sd-cards: Kingston 2mb that worked perfect on my old Legend and original Sandisk 8mb that was shipped with my Incredible S. I followed all possible tutorials step by step but without effect. I always get the same error.
I live in Sweden and I bought my device from retailer. I'm not really sure what's the valid RUU version for our region so I've used:
RUU_Vivo_Gingerbread_S_HTC_WWE_2.12.405.7_Radio_20.2804.30.085AU_3805.04.03.22_M_release_187295_signed
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed (especially this due to the same program and radio version)
but even optus and RUU_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20. 2810.30.085AU_3805.06.03.16_M_release_199684_signe d.
Unfortunately it's always the same error after reboot into bootloader. Has anybody of you (that used xtc clip but not only) faced the same problem? Is there any way to bypass it? I will be very very grateful for any answer.
Click to expand...
Click to collapse
If you are S-OFF with a XTC-Clips, you can't get S-ON, because it's a "hardware" S-OFF:
jkolner said:
If you are S-OFF with a XTC-Clips, you can't get S-ON, because it's a "hardware" S-OFF:
Click to expand...
Click to collapse
Thanks a lot for reply but well...It's not what I asked I was asking about unrooting (just pure taking away this little f... pirate and possibility to come back to stock rom) I'm totally aware of permanent character of my unlocked bootloader.
Anyway I solved problem with help of two threads: http://forum.xda-developers.com/showthread.php?t=1070348&page=7 and this about canadian dudes' problem with their PG32120 devices and bell stock. As it turned out I accidently change my Modelid during s-offing and wrote it as PG321200, which i didn't know until i succesfully installed ENG s-off and rebooted bootloader todays afternoon. I used xtc clip again (I had to re-create goldcard - hboot 0.99x200 (bell) though) and reverted quite easily back to my original PG3213000. After that I installed RUU without any single issue. Just ENG s-off disappeared, but I can live without that
Can you not downgrade the HBOOT then run said RUU with a gold card. Or you could extract the ROM.zip and use that in HBOOT mode.
Believe me I tried several times and it didn't work as long as I had modelid PG321200. Once I changed model id with xtc clip problem disappeared
Hello
Can someone please help me out with a stock rom as i want to unroot because my phone has decided to refuse a usb connection and simply just charge. I have tried various different cables but still no luck, so need to go back to stock so I dont void warranty.
crazee87 said:
Hello
Can someone please help me out with a stock rom as i want to unroot because my phone has decided to refuse a usb connection and simply just charge. I have tried various different cables but still no luck, so need to go back to stock so I dont void warranty.
Click to expand...
Click to collapse
Is your phone branded or unbranded??
Do you know which Rom came with it??
I can send you detailed instructions to unroot and S-On your device but first you need to tell which region your phone belongs and if its branded with some carrier or unbranded???
Ehsan
Can somebody tell me how to go back to S-on. I've got dust under mine frontcamera so i have to bring it back to the store. I already flashed a RUU, only the S-off is still there. I checked the forums but i can't figure it out. I had Revol. Used to gain S-off. Can someone explain me how to do it please?
Sent from my HTC Incredible S using XDA App
Zoeriva said:
Can somebody tell me how to go back to S-on. I've got dust under mine frontcamera so i have to bring it back to the store. I already flashed a RUU, only the S-off is still there. I checked the forums but i can't figure it out. I had Revol. Used to gain S-off. Can someone explain me how to do it please?
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
Follow this guide that I just posted:
http://forum.xda-developers.com/showthread.php?t=1287111
Regards.
Ehsan
Ehsan,
Thanks for your help, i will try this today!
Sent from my HTC Incredible S using XDA App
Hello Ehsan,
I'l tried your methode but the phone is still S-off?
Do you have another way to try?
Thanks anaway for your help!
Sent from my HTC Incredible S using XDA App
Zoeriva said:
Hello Ehsan,
I'l tried your methode but the phone is still S-off?
Do you have another way to try?
Thanks anaway for your help!
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
It worked fine for me and so did for a few others but I heard recently that there are some changes in AlphaRevX and the bootloader needs to be downgraded now.
I S-off my phone long ago when AlphaRevX method was just introduced so may be that's why my bootloader was overwritten by the Rom easily.
Try following this guide:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
By the way my guide is meant to be used when your USB is not working
Ehsan
PS. I dont own an Incredible S anymore so cant test it myself sorry
Howdy!
What is this?
This is a PH39IMG.zip that you flash via HBOOT to restore your phone to stock unrooted Gingerbread shipping ROM. This will also remove Clockwork Recovery
Click to expand...
Click to collapse
Why should I use this/care?
If you've updated your phone to the Ice Cream Sandwich build that AT&T pushed out OTA, or flashed your phone manually, you may at some point in time wish to go back to Gingerbread.
If you do, you'll find that the PH39IMG.zip and RUU that you would have previously tried to use don't work, since ICS updated your HBOOT.
This is essentially a "return to warranty" kit. This doesn't remove the "*UNLOCKED*" flag on HBOOT, but it will allow you to return to some semblance of stock just in case.
Click to expand...
Click to collapse
How do I use this?
Your bootloader must be unlocked to flash this.
Download the file, put it on your external SD, and boot to HBOOT. Accept the update when prompted.
If you're trying to return your phone to AT&T for warranty, you should probably also re-lock your bootloader also ("fastboot oem lock")
Please note!
This is not for HTC Raider / Velocity / Generic Holiday users!
This restores the shipping HTC Vivid ROM for AT&T.
Click to expand...
Click to collapse
Downloads
Restore to unrooted Gingerbread Stock: http://goo-inside.me/private/iomonster/htcvivid/roms/restore-gb-from-ics/PH39IMG.zip
Click to expand...
Click to collapse
Hopefully this should alleviate some of the fears associated with updating your phone.
I will upload a "return to stock ICS" ph39img here too soon...
<Removed>
Youssarian said:
Ok, I was stuck in boot loop after OTA, then going to the rooted rom. Could not get it to play nice. Tried this to take me back to GB so I could start over and did the above exactly. After running the update, which appears to work with the little status bar going up and down as it should, it gets stuck at the Hboot screen. (Attached.)
After pulling the battery, it boots to HTC white screen, reboots once, then sticks on the HTC white screen. I can get back to Hboot, but not sure where to proceed from here?
Click to expand...
Click to collapse
How do you have S-OFF?
Sent from my HTC PH39100
JEANRIVERA said:
How do you have S-OFF?
Sent from my HTC PH39100
Click to expand...
Click to collapse
His device came like that when it was purchased
Sent from my HTC Holiday
Youssarian said:
Ok, I was stuck in boot loop after OTA, then going to the rooted rom. Could not get it to play nice. Tried this to take me back to GB so I could start over and did the above exactly. After running the update, which appears to work with the little status bar going up and down as it should, it gets stuck at the Hboot screen. (Attached.)
After pulling the battery, it boots to HTC white screen, reboots once, then sticks on the HTC white screen. I can get back to Hboot, but not sure where to proceed from here?
Click to expand...
Click to collapse
What I did was take out the sd card and put into a card reader and deleted the ph file then booted back into fastboot to finish process
Sent from my HTC Flyer P510e using Tapatalk
Youssarian said:
Ok, I was stuck in boot loop after OTA, then going to the rooted rom. Could not get it to play nice. Tried this to take me back to GB so I could start over and did the above exactly. After running the update, which appears to work with the little status bar going up and down as it should, it gets stuck at the Hboot screen. (Attached.)
After pulling the battery, it boots to HTC white screen, reboots once, then sticks on the HTC white screen. I can get back to Hboot, but not sure where to proceed from here?
Click to expand...
Click to collapse
You need to pull the PH39IMG.zip file off your SD card as Hboot looks for it to see if an update is available before it does anything else.
Sent from my HTC PH39100 using xda premium
<Removed>
removed........
Is there anyway to flash this on lock boot loaders.
Sent from my Galaxy Nexus using xda premium
Dxtra said:
Is there anyway to flash this on lock boot loaders.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
If your bootloader was relocked prior to attempting to flash the RUU or PH39img.zip, then youre doing the right thing.
8125Omnimax said:
If your bootloader was relocked prior to attempting to flash the RUU or PH39img.zip, then youre doing the right thing.
Click to expand...
Click to collapse
I've never got a chance to unlock the bootloaders. I was completely stock before the ics update.
Sent from my Galaxy Nexus using xda premium
You must have your bootloader unlocked to flash this image. You can re-lock it afterwords, but you may get a *SECURITY WARNING* in HBOOT, since if you have the new HBOOT, you technically should also have stock ICS.
Until a *working* ICS RUU surfaces, this is as good as it gets.
thecubed said:
Until a *working* ICS RUU surfaces, this is as good as it gets.
Click to expand...
Click to collapse
i posted a working RUU already....
Pirateghost said:
i posted a working RUU already....
Click to expand...
Click to collapse
Of the same version as the OTA? Apologies if so
thecubed said:
Of the same version as the OTA? Apologies if so
Click to expand...
Click to collapse
2 minor revisions lower than the OTA.....but it serves as an EASY way for the ravenous n00bs to get ICS
Pirateghost said:
2 minor revisions lower than the OTA.....but it serves as an EASY way for the ravenous n00bs to get ICS
Click to expand...
Click to collapse
And that's why I just downloaded and am installing now! Thanks much!!
hey cubed, how are you?
before unlocking bootloader, i flashed the ics ruu so i'm on new hboot and radio,
since i unlocked bootloader and running a wc's 3.5 rom, however i have an issue, when i talk on the phone from speaker, ppl hear their echo, so i'm thinking radio issue, i tried to flash back the gb ruu and no go cuz of bootloader, so i downgraded with the method in OP but it didn't downgrade radio, i tried again to flash gb ruu and no luck, i put the radio.img from the gb ruu into ur zip and now it won't recognize it at all (guessing due to signature) so i'm flashing the stock ics ruu now to see if im gona have the same problem or not. by the way when i flashed ur downgrade zip and loaded, the phone would not connect to any network at all and being a stock rom the option to search for network is greyed out.
so i'm guessing bottom line is im stuck with this new radio since we don't have s-off correct?
is there any way so far to totally downgrade back to the original ship ruu ? bootloader, radio and all ?
thanks
lebmb said:
hey cubed, how are you?
before unlocking bootloader, i flashed the ics ruu so i'm on new hboot and radio,
since i unlocked bootloader and running a wc's 3.5 rom, however i have an issue, when i talk on the phone from speaker, ppl hear their echo, so i'm thinking radio issue, i tried to flash back the gb ruu and no go cuz of bootloader, so i downgraded with the method in OP but it didn't downgrade radio, i tried again to flash gb ruu and no luck, i put the radio.img from the gb ruu into ur zip and now it won't recognize it at all (guessing due to signature) so i'm flashing the stock ics ruu now to see if im gona have the same problem or not. by the way when i flashed ur downgrade zip and loaded, the phone would not connect to any network at all and being a stock rom the option to search for network is greyed out.
so i'm guessing bottom line is im stuck with this new radio since we don't have s-off correct?
is there any way so far to totally downgrade back to the original ship ruu ? bootloader, radio and all ?
thanks
Click to expand...
Click to collapse
I really don't think it's a radio issue. I believe it's a network issue. I've had an echo on several devices I've used from the original iPhone through iPhone 4 blackberrys inspire and now vivid. But it is not all the time just every once in a while.
Sent from my HTC PH39100 using Tapatalk
jayv81 said:
I really don't think it's a radio issue. I believe it's a network issue. I've had an echo on several devices I've used from the original iPhone through iPhone 4 blackberrys inspire and now vivid. But it is not all the time just every once in a while.
Sent from my HTC PH39100 using Tapatalk
Click to expand...
Click to collapse
yeah i've had it happen randomly before in some phones, but this is consistent every single call for the past 3 days. in different areas, with different people at different times.
i just finished flashing the stock ics ruu and it connected to the network fine and made a couple of quick phone calls and no echo
btw the ppl i talk to hear them selves, i don't hear any echo, it all sounds well on my end. im gona try another 3.5 rom and see what happens
EDIT: just tried holiraider, and it did it. leme see what other roms i can flash
so a quick update, even with a custom sense 3.0 rom, i can't connect to a network at all, it only works with 3.5 roms and i people i talk to have an echo, and only fix is running an ics rom, for some reason when i push the ics ril files into a 3.5 rom i loose all network connections, baseband says unknown and all the phone info except serial number is unknown in the hardware info.
so very strange. so even when using this guide, and restoring the fully stock gb i still cant use the phone
uploaded wrong screenies, i'll update in a sec
EDIT: well i tried again, and flashed thecubed zip and i'm back on the stock 3.0 unrooted, and i noticed that i was able to get the signal up and running when i toggle wifi. by default on first boot its on, so i connected to my wifi as usual, but i dunno why i just turned it off so the network came right up and all was fine with the signal. i turned wifi back on and no problems. i turned it off, no problems. so i restarted the phone, and it won't connect to the network, so i turn wifi on and now i am connected and have full signal. strange, so i wonder if that's due to the radio, or something happened to my phone since i seem to be the only one having those issues
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
gladii said:
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
Click to expand...
Click to collapse
Hey mate, official welcome from me Second welcome from me today lol
I would advise against going s-on and fully stock.
You cannot run a ruu or ota with a custom recovery/root.
So the easiest way to get the stock experience you want is by flashing one of tpbklake's rooted stock roms. They are basically stock roms with root and can run on a custom recovery. No tweaks or anything
http://forum.xda-developers.com/showthread.php?t=1773520
http://forum.xda-developers.com/showthread.php?t=1756500
The link above (top one) is based off a newer ruu from asia, although there is not much difference
I would also suggest to try ARHD 3.0.x for the stock optimised rom
Also which bootloader version do you have?
gladii said:
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
Click to expand...
Click to collapse
Yes there a some ROMs in the Development section that are completely stock that you can flash through recovery.
The original GB 2.3.3/Sense 2.1, the GB 2.3.5/Sense 3.0 and the latest ICS 4.0.4/Sense 3.6
markj338 said:
Hey mate, official welcome from me Second welcome from me today lol
I would advise against going s-on and fully stock.
You cannot run a ruu or ota with a custom recovery/root.
So the easiest way to get the stock experience you want is by flashing one of tpbklake's rooted stock roms. They are basically stock roms with root and can run on a custom recovery. No tweaks or anything
http://forum.xda-developers.com/showthread.php?t=1773520
http://forum.xda-developers.com/showthread.php?t=1756500
The link above (top one) is based off a newer ruu from asia, although there is not much difference
I would also suggest to try ARHD 3.0.x for the stock optimised rom
Also which bootloader version do you have?
Click to expand...
Click to collapse
I'm going to sell my device so I need it back the way it was. I want to keep it rooted though, so that the next owner can decide for himself what he wants to do with it. If he he's no techie, he can enjoy the device in stock (including OTAs, or can this be done like you mentioned?). If whe wants to toy with it, he can do that too. If it's easier to just go back to stock entirely, that's fine too.
It seems that I can no longer get into hboot now? After installing that hacked gingerbread, my device just boots into Android when pressing volume down and power??
tpbklake, I'll try to flash one of those when I can get back into recovery
Weird.. Taking out the battery fixed my recovery issue. I'll flash that ROM
Btw I seem to have hboot 6.13.1002 and radio 3805.06.03.03_M. Is this the info you need?
gladii said:
Weird.. Taking out the battery fixed my recovery issue. I'll flash that ROM
Btw I seem to have hboot 6.13.1002 and radio 3805.06.03.03_M. Is this the info you need?
Click to expand...
Click to collapse
Yes
But since you want stock it won't matter
You CANNOT have both root and ota updates
Either one or the other unfortunately
You have to make a choice a rooted stock ROM will be identical to the official ota from htc but you will be able to keep root, but can't get ota updates
but unfortunately I think sense 3.6 4.0.4 is the last update
But, I have been proven wrong before
Sent from my Nexus 7
K then in my case a full stock device would be best. How do I get started with this? First install a stock ROM, then the stock recovery and then put It back in S-OFF? Which ROM should I install (would prefer the stock 2.3.3)? And where can I find the recovery? Sorry for the basic questions but those lists of ROMs can get a bit complicated..
Still getting nowhere If I flash a stock ROM in CWM, my recovery won't go back to stock, will it? Shouldn't I try to get the stock recovery first and then use a RUU? Problem is that I can't seem to find a stock recovery anywhere. And when I extract the ROM from a RUU, it's only about 180 MB, so that can't be right, can it?
gladii said:
Still getting nowhere If I flash a stock ROM in CWM, my recovery won't go back to stock, will it? Shouldn't I try to get the stock recovery first and then use a RUU? Problem is that I can't seem to find a stock recovery anywhere. And when I extract the ROM from a RUU, it's only about 180 MB, so that can't be right, can it?
Click to expand...
Click to collapse
Which ruu? Here's a good guide http://forum.xda-developers.com/showthread.php?t=1359555 but I find it faster to flash the alparev then run the ruu, 2 steps and done.
Nonverbose said:
Which ruu? Here's a good guide http://forum.xda-developers.com/showthread.php?t=1359555 but I find it faster to flash the alparev then run the ruu, 2 steps and done.
Click to expand...
Click to collapse
Sorry for the late reply. I've been busy with exams. I've tried the RUU RUU_IncredibleC_Verizon_WWE_1.22.605.0_Radio_1.00.03.04.06_release_161493_NoDriver (but I don't actually have a Verizon, could that be the problem?).
I really have no idea what all the info in the filename means, so it's difficult to find one that fits my needs. I'll take a look at your link right now and report back!
gladii said:
Sorry for the late reply. I've been busy with exams. I've tried the RUU RUU_IncredibleC_Verizon_WWE_1.22.605.0_Radio_1.00.03.04.06_release_161493_NoDriver (but I don't actually have a Verizon, could that be the problem?).
I really have no idea what all the info in the filename means, so it's difficult to find one that fits my needs. I'll take a look at your link right now and report back!
Click to expand...
Click to collapse
DO NOT attemtp to flash that one!!!! The Verizon DINC2 is a CDMA device and the radio is not compatible.
Please read the post that nonverbose referenced for you. That tells you all you need to do.
tpbklake said:
DO NOT attemtp to flash that one!!!! The Verizon DINC2 is a CDMA device and the radio is not compatible.
Click to expand...
Click to collapse
Wow, good thing it didn't succeed! How about this one:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe
(download link: http://www.filefactory.com/file/c0af340/n/RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe)
gladii said:
Wow, good thing it didn't succeed! How about this one:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe
(download link: http://www.filefactory.com/file/c0a...5AU_3805.06.03.03_M_release_199399_signed.exe)
Click to expand...
Click to collapse
What region of the world are you in? I would recommend the HTC WWE 2.30.405.1.
tpbklake said:
What region of the world are you in? I would recommend the HTC WWE 2.30.405.1.
Click to expand...
Click to collapse
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
gladii said:
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
Click to expand...
Click to collapse
World Wide English with support for most European languages
gladii said:
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
Click to expand...
Click to collapse
Ah, perfect! Canceled my download, but there's a 20 minute interval before starting a new one, so it'll take me at least an hour to download it.
I've encountered this issue before, but randomness seemed to solve it back then: a fastboot command just displays "<waiting for device>" and then keeps hanging there. "fastboot devices" returns an empty line, so that's consistent. Phone is in fastboot USB mode, so I'm not sure what could be the issue?
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
gladii said:
I've encountered this issue before, but randomness seemed to solve it back then: a fastboot command just displays "<waiting for device>" and then keeps hanging there. "fastboot devices" returns an empty line, so that's consistent. Phone is in fastboot USB mode, so I'm not sure what could be the issue?
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
Click to expand...
Click to collapse
Sounds like it may be a port issue, cable issue or driver issue on the PC.
Have you tried different ports or a different cable? Do you have HTC Sync running in the System Tray on the PC?
As for the hboot file, yes that is the one.
gladii said:
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
Click to expand...
Click to collapse
I thought you wanted to go to stock ICS? Hboot 1.13 it a gingerbread hboot. If you just flash the vivo_downgrade.img then run the ruu, there will be no need to extract and flash the hboot from the ruu.
Nonverbose said:
I thought you wanted to go to stock ICS? Hboot 1.13 it a gingerbread hboot. If you just flash the vivo_downgrade.img then run the ruu, there will be no need to extract and flash the hboot from the ruu.
Click to expand...
Click to collapse
No I wanted it back the way I wanted it. Rom, recovery,... all stock. But surely I'll give ICS a testdrive via OTA
I Recently Bought an Htc one (M7) {running android 4.3} from an electronics shop well 4.4 Kitkat Just came out so I was all excited to update to check out all the changes... sadly I was mistaken. The previous owner had tried to root the phone so im stuck with a phone that is "Tampered" "Unlocked"
with "s-on" not to bad right? well the recovery on the phone is Team win project recovery... and the phone is not rooted
I want to return the phone to stock or at least beable to get normal ota updates
Can some one give me a detailed step by step walkthrough of how to switch the phones recovery back to stock im not very tech savy in this field
Smerfurdt92 said:
I Recently Bought an Htc one (M7) {running android 4.3} from an electronics shop well 4.4 Kitkat Just came out so I was all excited to update to check out all the changes... sadly I was mistaken. The previous owner had tried to root the phone so im stuck with a phone that is "Tampered" "Unlocked"
with "s-on" not to bad right? well the recovery on the phone is Team win project recovery... and the phone is not rooted
I want to return the phone to stock or at least beable to get normal ota updates
Can some one give me a detailed step by step walkthrough of how to switch the phones recovery back to stock im not very tech savy in this field
Click to expand...
Click to collapse
you have to flash a RUU
Boachti said:
you have to flash a RUU
Click to expand...
Click to collapse
Its a Tmobile phone is there one for tmobile?
and doesnt that require s-off?
well the ruu I tried wouldnt even run on my Laptop
There are some T-Mobile RUU's. Check the T-Mobile forum. Specifically this thread: http://forum.xda-developers.com/showthread.php?t=2496074
Me personally I would check to see what HBOOT version is on there and if it's lower than 1.57, go S-OFF before doing anything else. Then just use TWRP to flash a stock or stock-ish 4.4 ROM and never mind OTA's.
Sent from my HTC One using xda app-developers app
NxNW said:
There are some T-Mobile RUU's. Check the T-Mobile forum. Specifically this thread: http://forum.xda-developers.com/showthread.php?t=2496074
Me personally I would check to see what HBOOT version is on there and if it's lower than 1.57, go S-OFF before doing anything else. Then just use TWRP to flash a stock or stock-ish 4.4 ROM and never mind OTA's.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thank you guys im looking further into it. Does the phone need to be rooted to flash a rom or just have the bootloader unlocked?
For kit Kat it needs to be s-OFF. Let's get that out of the way first.
And some s-OFF methods require a rooted ROM to work as I recall. So it's already getting complicated.
But a typical custom Rom doesn't *need* root, in fact after flashing you will discover it *gives* you root.
Going that route requires work and some reading. Then again, getting an RUU to run successfully does too.
Basically the situation you''re in is not horrible, but to go all the way forward (S-OFF Kit Kat with ability to do anything you want in the future) or all the way back (totally locked down stock system capable only of accepting OTA's ) will require work either way.
Sent from my HTC One using xda app-developers app
So basicaly it may be simpler if I...
1 s-off
2 download rom
2.5 put on phone memory
3 go to team win recovery
4 Click install and choose said rom?
is that the basics of it?
if I want the least amount of trouble?
Also I guess what makes this most confusing for me is the non stock recovery
and to use fire water for the s-off I need to remove htc sync from the phone?
I feel im doing more work and stressing than i should be?
Yes Im quite Noobish..
Pretty much yes.
There could be adventures along the way, but I think this outcome would position you well for the future.
The biggest question is how old is your HBOOT.
There is no S-OFF for 1.57 and existing exploits for 1.56 don't always work.
If you can get S-OFF, you can do anything, including a) destroying your phone by mistake; b) changing your mind later and going back to S-ON; and, my personal favorite, c) destroying your phone in the act of trying to go back to S-ON (due to modified/ damaged HBOOT partition).
If you can't get S-ON, well, see if you can get back to stock.
Occasionally you are truly stuck and can neither go forward nor backward.
Which in your case is not so bad. 4.3 works great. Honestly plenty of people here are trying to go *back* to 4.3 after trying 4.4.
With S-OFF you can always do that. S-ON, not so much..
Sent from my HTC One using xda app-developers app
Yeah.. now i have a pretty blue screen that once every 10 minutes or so will flash the google logo so yup bricked...
That would qualify as an "adventure". Still, it sounds like something less than "bricked".
See if you can enter HBOOT (hold down volume-down and power buttons for a few seconds or if you're in a boot loop , just hold down volume-down as phone is booting up).
If so, you can select fastboot and you should have the option to power down. That should give the battery a rest and give you time to think.
At some point you need to have the android tools fastboot and adb set up on your computer.
When you do, enter HBOOT, select fastboot (with phone plugged into computer via USB) and run the command fastboot getvar all.
Post the results here.
The first post of this thread doesn't really contain enough detail for others to help you otherwise.
Sent from my HTC One using xda app-developers app