Hey all... I have a problem.
I have a bell htc incredible s, it's stuck at the htc splash screen, there was apparently an issue trying to ruu, I've tried 6-7 times to reflash and in the process lost my recovery. One ruu indicated a successful completion, but returned the same issue upon rebooting... HTC splash, and then either reboot or lock... I have no recovery only bootloader unlocked via revolution... I am in a huge bind... Please reply asap...
Sent from my R800a using xda premium
talira said:
Hey all... I have a problem.
I have a bell htc incredible s, it's stuck at the htc splash screen, there was apparently an issue trying to ruu, I've tried 6-7 times to reflash and in the process lost my recovery. One ruu indicated a successful completion, but returned the same issue upon rebooting... HTC splash, and then either reboot or lock... I have no recovery only bootloader unlocked via revolution... I am in a huge bind... Please reply asap...
Sent from my R800a using xda premium
Click to expand...
Click to collapse
Use the official HTC program to do full recovery. if it says okey but boot stuck still, you probably in trouble, the hardware may fail or flash chip blocks could abnormally wear out. it happens.
talira said:
Hey all... I have a problem.
I have a bell htc incredible s, it's stuck at the htc splash screen, there was apparently an issue trying to ruu, I've tried 6-7 times to reflash and in the process lost my recovery. One ruu indicated a successful completion, but returned the same issue upon rebooting... HTC splash, and then either reboot or lock... I have no recovery only bootloader unlocked via revolution... I am in a huge bind... Please reply asap...
Sent from my R800a using xda premium
Click to expand...
Click to collapse
Which RUU were you trying to flash?
Sounds like he might've flashed the wrong RUU.
Yeah you're also in the DEV section here. Doesn't seem like there are mods that care till you PM them though.
Sorry for the wrong placement for the thread, I'll try to get it fixed... Just figured that developers seem to be most knowledgeable about the workings of the device...
I have tried any number of ruus originally the bell ruu and it said it completed successfully... but i turned on the device and still the issue persists... I feel it may be an issue of hardware failure and that spells disaster...
talira said:
Sorry for the wrong placement for the thread, I'll try to get it fixed... Just figured that developers seem to be most knowledgeable about the workings of the device...
I have tried any number of ruus originally the bell ruu and it said it completed successfully... but i turned on the device and still the issue persists... I feel it may be an issue of hardware failure and that spells disaster...
Click to expand...
Click to collapse
What version of Android were you running before? If you were running Gingerbread 2.3.3 and you tried to go back to the original Bell Froyo 2.2 RUU that is your problem. Once you have flashed a Gingerbread radio you cannot downgrade and flash a Froyo radio.
You should try the this RUU
http://www.filefactory.com/file/c0a...5AU_3805.04.03.27_M_release_199657_signed.exe
Go to the main android development page for incredible s, over there you will find a thread for all the roms grab the official bell ruu and flash it. If that does not work install a recovery through adb flash a rom from the recovery that should sort your problem
Sent from my HTC Incredible S using XDA App
Related
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
I cannot find an answer to my problem as hard as i look. today, i decided to root my phone (HTC vivid). I rooted it successfully, i went to the Superuser and it said it needed to be updated and to flash a kernel or something like that. (i was using this program http://forum.xda-developers.com/showthread.php?t=1498003) I went to the program that i meantioned above and i clicked flash stock vivid kernel, thinking that this was the kernel i had to update or flash or whatever then my phone reboots and its all like Hurr duur im stuck on the HTC screen watcha gonna do about it. I tried many things:
One thing i tried was to do the .zip thingy, with the boot loader relocked, and it wont boot to anything else but the boot loader
i tried also to do the ruu thing, but it kept giving me errors about my phone model or something like that
Can someone please tell me what i did wrong and how to fix it?
i would really appreciate it big time!
Edit: i have an micro sd, if that info helps
I would try to restore it back to stock.
Relock to bootloader if it isn't still locked.
Then run the stock ruu for your phone from http://forum.xda-developers.com/showthread.php?t=1338919
I had my vivid stuck on the HTC screen and this worked for mine.
Also, If you rooted to ICS you are most likely stuck until the official RUU from HTC is out...
FernandoR211 said:
I would try to restore it back to stock.
Relock to bootloader if it isn't still locked.
Then run the stock ruu for your phone from http://forum.xda-developers.com/showthread.php?t=1338919
I had my vivid stuck on the HTC screen and this worked for mine.
Also, If you rooted to ICS you are most likely stuck until the official RUU from HTC is out...
Click to expand...
Click to collapse
You need to install HTC sync or the htcdrivers before running the ruu otherwise it won't see your phone and will just error out.
Sent from my HTC PH39100 using xda premium
pichi123 said:
I cannot find an answer to my problem as hard as i look. today, i decided to root my phone (HTC vivid). I rooted it successfully, i went to the Superuser and it said it needed to be updated and to flash a kernel or something like that. (i was using this program http://forum.xda-developers.com/showthread.php?t=1498003) I went to the program that i meantioned above and i clicked flash stock vivid kernel, thinking that this was the kernel i had to update or flash or whatever then my phone reboots and its all like Hurr duur im stuck on the HTC screen watcha gonna do about it. I tried many things:
One thing i tried was to do the .zip thingy, with the boot loader relocked, and it wont boot to anything else but the boot loader
i tried also to do the ruu thing, but it kept giving me errors about my phone model or something like that
Can someone please tell me what i did wrong and how to fix it?
i would really appreciate it big time!
Edit: i have an micro sd, if that info helps
Click to expand...
Click to collapse
1. You obviously didn't know what you were doing. Lessons for next time.
2. If the .zip thingy made the bootloader update and it seems like it managed to flash everything alright, then you need to make sure the zip isn't on any storage connected to the phone, then go from bootloader to fastboot, unlock the bootloader using the HTCDev bootloader unlock procedure (I hope you kept your unlock_code.bin!), then fastboot flash a recovery.img, then boot to recovery from the bootloader, and flash an ICS ROM, then go back to fastboot and flash the boot.img to get the kernel flashed.
I'm guessing that you may have flashed the ICS bootloaders, but you aren't specific enough. What ruu did you try to run, exactly what zip did you try to install?
You didn't do anything wrong, you just didn't complete the procedure.
kozmikkick said:
You need to install HTC sync or the htcdrivers before running the ruu otherwise it won't see your phone and will just error out.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Well I hope that was a given. BUt I guess I should have listed it. Good point!
If you have an AT&T Vivid, then you should be okay, run the latest ICS RUU and hope for the best. If not, you'll have to do it the old fashioned way through lots of fastboot commands.
thank you everyone!
/thread
Hello all,
I recently got a notification for a software update (ics!) and I quickly accepted and all.
The download dragged on but eventually completed with no problems... then came the installation of the OTA update which I accepted and it rebooted onto a recovery screen with no status bar or anything indicating that it was updating.
I AM ROOTED.
I WAS unlocked but I "RELOCKED" the bootloader which it stated on the recovery page.
I do have ClockworkMod 5.0.2.7 flashed as well.
If there is anyone who can advise me to get stock ics on this device?
Thanks!
well if you can still get into bootloader, I would suggest connecting it via fastboot from bootloader and running the ruu for ics....
Wild Child said:
well if you can still get into bootloader, I would suggest connecting it via fastboot from bootloader and running the ruu for ics....
Click to expand...
Click to collapse
Does my bootloader need to be unlocked to run ruu?
I've never used this method before but sounds interesting.
locked,had to do this earlier on one of my devices
Wild Child said:
locked,had to do this earlier on one of my devices
Click to expand...
Click to collapse
Ah gotcha!
Followed through and everything is running smoothly!
Thank you!
Is it possible to run the RUU when the phone will only go into fastboot and the RUU file is on the computer?
I'm having the same problem.. But when it first tried to install the update it showed a dead android with a exclamation point above him. I relocked the boot loader but now the update boots into the boot loader. It says I'm relocked. I tried several times and it keeps going to the bootloader. I don't have a custom recovery. I tried to flash a stock ph39img.zip and when I rebooted it was just the way I had left it, and now when I try to do the update it says that I'm up to date and to check back in 24hrs. I've tried this several times, I've got the update downloaded.. Not sure what to do.
Sent from my HTC PH39100 using XDA
kos26 said:
I'm having the same problem.. But when it first tried to install the update it showed a dead android with a exclamation point above him. I relocked the boot loader but now the update boots into the boot loader. It says I'm relocked. I tried several times and it keeps going to the bootloader. I don't have a custom recovery. I tried to flash a stock ph39img.zip and when I rebooted it was just the way I had left it, and now when I try to do the update it says that I'm up to date and to check back in 24hrs. I've tried this several times, I've got the update downloaded.. Not sure what to do.
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
If you can get to bootloader, and you're locked or relocked, access Fastboot USB and run the RUU from your computer
(Echo, Echo)
homeslice976 said:
If you can get to bootloader, and you're locked or relocked, access Fastboot USB and run the RUU from your computer
Click to expand...
Click to collapse
I can confirm that this worked for me this morning. I was able to get into fastboot/bootloader so I ran the RUU this morning and it was successful (unlike last night, for some reason). I suggest you give this a shot!
mark72501 said:
I can confirm that this worked for me this morning. I was able to get into fastboot/bootloader so I ran the RUU this morning and it was successful (unlike last night, for some reason). I suggest you give this a shot!
Click to expand...
Click to collapse
Where do I get this ruu? I didn't see a place to download the official release, maybe I'm missing something. Thanks for the help!
Sent from my HTC PH39100 using XDA
kos26 said:
Where do I get this ruu? I didn't see a place to download the official release, maybe I'm missing something. Thanks for the help!
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
Sure...I got mine from the link provided in this thread...
http://forum.xda-developers.com/showthread.php?t=1338919
I grabbed the one that says Cingular in the name.
mark72501 said:
Sure...I got mine from the link provided in this thread...
http://forum.xda-developers.com/showthread.php?t=1338919
I grabbed the one that says Cingular in the name.
Click to expand...
Click to collapse
The only concern I have though is that that file is the leak.. I'd rather have the official release.
Sent from my HTC PH39100 using XDA
kos26 said:
The only concern I have though is that that file is the leak.. I'd rather have the official release.
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
I know. But in the situation I was in I wasn't having any other luck. There may be an official RUU out there, not sure...I had been pointed to this one so I used it. It seems to be working fine on my Vivid but I understand your concern.
Maybe one will be posted soon, if not already.
google ruu 3.26.502.56
Even though the RUU was leaked before being released "officially", it's the same RUU being used. They have not changed RUU version for this update
I found the official ruu from the htc support page. http://www.htc.com/us/support/vivid-att/downloads/
Works great for the most part. Seems like I get a bug here and there where I'll get a white HTC splash screen for a brief second when hitting the home key. I think I've seen someone else mention this some where.
kos26 said:
I found the official ruu from the htc support page. http://www.htc.com/us/support/vivid-att/downloads/
Works great for the most part. Seems like I get a bug here and there where I'll get a white HTC splash screen for a brief second when hitting the home key. I think I've seen someone else mention this some where.
Click to expand...
Click to collapse
That's rosie or systemui or framework having a hissy fit. weird...i'd probably reflash the RUU just to make sure you didn't have something weird happen
Hi guys. Im really having a problem with my phone now. I can't update my phone or do a hard reset as I will be directly brought to the fastboot menu with a security warning on the top. When i go back to the hboot menu and try to do recovery or factory reset, the same thing happens.
I really want to know what is going on and how do I solve this problem..
SEARCH FUNCTION! We have hundreds of threads, guides and tuts about it. I say it again, SEARCH FUNCTION.
Sent from my Incredible S using xda premium
Don't be angry... If you entered recovery and got security warning, try to flash the recovery again.
Sent from my HTC One X using XDA
Silversniper said:
SEARCH FUNCTION! We have hundreds of threads, guides and tuts about it. I say it again, SEARCH FUNCTION.
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
Sorry dude, I cant find any solution regarding to this problem.. that's why i posted..
keroro430 said:
Don't be angry... If you entered recovery and got security warning, try to flash the recovery again.
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Hey, thanks for the advice. but what recovery should I flash again ?
Try the Clockworkmod first. If it is bootable, flash a rom and install 4EXTrecovery via 4EXT Updater.
Sent from my HTC One X using XDA
Did you lock the bootloader or something? Try mentioning the steps leading to your situation, rather than just the end result. We shouldn't have to be playing guessing games especially when you're coming to us asking for help.
Nonverbose said:
Did you lock the bootloader or something? Try mentioning the steps leading to your situation, rather than just the end result. We shouldn't have to be playing guessing games especially when you're coming to us asking for help.
Click to expand...
Click to collapse
Alright guys. Im so sorry. I've actually managed to unlock the bootloader again, and flashed CWM. As gingerbread 2.3.5 was just pushed out to my country several days ago. I've brought my phone to the HTC service centre today. and they are also unable to run the RUU update. So they took in my phone for servicing and they will update my phone when the repair is done. Thanks for your help guys.. still needs to be sent in though.. 4th time im sending this phone in already...
What's version of ROM? Root? S-off?
Need more details...
genesisxkev said:
Alright guys. Im so sorry. I've actually managed to unlock the bootloader again, and flashed CWM. As gingerbread 2.3.5 was just pushed out to my country several days ago. I've brought my phone to the HTC service centre today. and they are also unable to run the RUU update. So they took in my phone for servicing and they will update my phone when the repair is done. Thanks for your help guys.. still needs to be sent in though.. 4th time im sending this phone in already...
Click to expand...
Click to collapse
If you were as quick replying to your thread as you were in taking the phone to HTC we could have got you fixed up. You needed stock recovery flashed, I believe. Hope HTC don't charge you for this "repair".
Rude_Dollah said:
What's version of ROM? Root? S-off?
Need more details...
Click to expand...
Click to collapse
Im still on gingerbread 2.3.3 . Not root yet, S-on. I only unlocked the bootloader as i wanted to root my phone to 2.3.5. but it is already out..
Nonverbose said:
If you were as quick replying to your thread as you were in taking the phone to HTC we could have got you fixed up. You needed stock recovery flashed, I believe. Hope HTC don't charge you for this "repair".
Click to expand...
Click to collapse
Hey, actually i havent sent my phone for the repair yet. any links for the stock recovery file ?
Hey guys. I've read that, installing the same version of RUU will get everything back to stock, including the recovery, but im on version 2.30.707.1 , and the closest file available for download is 2.30.405.1 , So am I able to run 2.30.405.1 's RUU to get everything back to stock ?
My radio version is 3805.09.03.27_M
genesisxkev said:
Hey guys. I've read that, installing the same version of RUU will get everything back to stock, including the recovery, but im on version 2.30.707.1 , and the closest file available for download is 2.30.405.1 , So am I able to run 2.30.405.1 's RUU to get everything back to stock ?
My radio version is 3805.09.03.27_M
Click to expand...
Click to collapse
That should work, but you may need to use a goldcard.
Guys! Everything is okay now!! I've unlocked my bootloader again to flash a stock recovery, locked my bootloader and did the OTA update. Everything is well now! Thanks for all the solutions!!
I've got an Incredible S with me here with Bootloader version 2.02.0000 and official ICS installed (upgraded OTA from GB around 4 months back). I unlocked the bootloader through the HTC Dev site. Every thing went smooth. Next, i flashed a custom recovery (CWM v 5.0.2.) and then the Superuser zip file i found one of the related Incredible S threads. I proceeded to flash the device with a JB ROM (after duly wiping data and cache on the phone) and it went well along with flashing of the gapps package. When rebooting after the procedure was done, the phone remained stuck on the startup HTC white screen. I tried waiting for 10-20 minutes but there was no change. I was (and still am) able to boot into CWMR and hence also tried re-flashing to no avail. Please note that I did not take a nandroid backup (Quite stupid to do so now that i look back) and hence not able to restore. Tried searching for an RUU of the official ICS by HTC for this phone but could not find one. Tried one from HTC's site (Asia specific RUU) but it gave an error saying i had the wrong RUU file for my phone. Also, my phone is S-ON.
I would request members to please point me to the correct sources for the solution of my situation. Please tell me how should i go about from here.
TIA
etMind said:
I've got an Incredible S with me here with Bootloader version 2.02.0000 and official ICS installed (upgraded OTA from GB around 4 months back). I unlocked the bootloader through the HTC Dev site. Every thing went smooth. Next, i flashed a custom recovery (CWM v 5.0.2.) and then the Superuser zip file i found one of the related Incredible S threads. I proceeded to flash the device with a JB ROM (after duly wiping data and cache on the phone) and it went well along with flashing of the gapps package. When rebooting after the procedure was done, the phone remained stuck on the startup HTC white screen. I tried waiting for 10-20 minutes but there was no change. I was (and still am) able to boot into CWMR and hence also tried re-flashing to no avail. Please note that I did not take a nandroid backup (Quite stupid to do so now that i look back) and hence not able to restore. Tried searching for an RUU of the official ICS by HTC for this phone but could not find one. Tried one from HTC's site (Asia specific RUU) but it gave an error saying i had the wrong RUU file for my phone. Also, my phone is S-ON.
I would request members to please point me to the correct sources for the solution of my situation. Please tell me how should i go about from here.
TIA
Click to expand...
Click to collapse
S-OFF and try again.
Sent from one of the few remaining Incredible S'
Follow step 13 from here
http://forum.xda-developers.com/showthread.php?t=1337105
You need to manually flash the boot.IMG of the ROM you are flashing, because you are s on. Not s off.
Sent from my Incredible S using xda app-developers app
Bahowle Effentia
Piccilino said:
S-OFF and try again.
Sent from one of the few remaining Incredible S'
Click to expand...
Click to collapse
Many thanks for your reply! I got the solution after i posted here after a bit more searching around the different threads. I did the exact same thing mentioned by Drugzy below an hour back. Got the device to boot and was running JB with HBOOT version 2.02.000 and S-ON. Later, went ahead with the guide to S-OFF using revolutionary and it was a success as well. Currently running JB with HBOOT version 1.13 and S-OFF .
Drugzy said:
Follow step 13 from here
http://forum.xda-developers.com/showthread.php?t=1337105
You need to manually flash the boot.IMG of the ROM you are flashing, because you are s on. Not s off.
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
Exactly! I too happened to read that a while ago and duly followed the said steps. Anyways, i S-OFFed the phone anyways.
Thanks for replying to the query!
etMind said:
Many thanks for your reply! I got the solution after i posted here after a bit more searching around the different threads. I did the exact same thing mentioned by Drugzy below an hour back. Got the device to boot and was running JB with HBOOT version 2.02.000 and S-ON. Later, went ahead with the guide to S-OFF using revolutionary and it was a success as well. Currently running JB with HBOOT version 1.13 and S-OFF .
Exactly! I too happened to read that a while ago and duly followed the said steps. Anyways, i S-OFFed the phone anyways.
Thanks for replying to the query!
Click to expand...
Click to collapse
Good you got it sorted. S off is much better IMO as you can flash new radios if desired and ROMs are easier to flash etc. Happy romming
Sent from my Incredible S using xda app-developers app
etMind said:
Many thanks for your reply! I got the solution after i posted here after a bit more searching around the different threads. I did the exact same thing mentioned by Drugzy below an hour back. Got the device to boot and was running JB with HBOOT version 2.02.000 and S-ON. Later, went ahead with the guide to S-OFF using revolutionary and it was a success as well. Currently running JB with HBOOT version 1.13 and S-OFF .
Exactly! I too happened to read that a while ago and duly followed the said steps. Anyways, i S-OFFed the phone anyways.
Thanks for replying to the query!
Click to expand...
Click to collapse
Yea S-OFF is much more convenient, as it is easy to flash new things.
Happy Flashing (That sounded wrong)
Sent from one of the few remaining Incredible S'
Drugzy said:
Good you got it sorted. S off is much better IMO as you can flash new radios if desired and ROMs are easier to flash etc. Happy romming
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
True that !
Piccilino said:
Yea S-OFF is much more convenient, as it is easy to flash new things.
Happy Flashing (That sounded wrong)
Sent from one of the few remaining Incredible S'
Click to expand...
Click to collapse
LOL !!