Related
i get a s-on IS with asia rom, can only upgrade to RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe via goldcard, but
the alpharevX program seems not work on this ROM, always stuck at
=============================
| AlphaRev-X HBOOT S-OFF tool |
=============================
Waiting for device...
Found your device: HTC Incredible S (vivo-1.13.0000, Android: 2.3.3)
This is a beta release and requires a beta release key.
Please visit: http://alpharev.nl/x/beta for more information.
Enter beta key [serial: HC14KTD00XXX]: nbhf1lawFz8WFicU
Beta key accepted - thank you for participating!
Acquiring root (method 2)...
(if we hang here for a *long* time [15mins+], please reboot your phone and try a
gain.)
i checked the device manager in winxp, the phone is correctly recognized as "my htc", usb_debug mode open, HTC sync not running.
does someone has same problem?
I'll test after RUU upgrade.
I report soon...
my Incredible S was also shipped with an Asian ROM that was not campatible with AlpharevX.
but it's an easy fix, download and install, RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio _20.2803.30.085AU_3805.04.03.12_M_release_185028_s igned.exe
( http://forum.xda-developers.com/showthread.php?t=1033922 )
then AlpharevX worked in seconds.
S-OFF ftw!
It works with the first gingerbread WWE that has the .22 radio. Not sure about the newer Gingerbread WWE.
Sent from my HTC Incredible S using XDA Premium App
Don't works. Tested now.
MrPontus said:
my Incredible S was also shipped with an Asian ROM that was not campatible with AlpharevX.
but it's an easy fix, download and install, RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio _20.2803.30.085AU_3805.04.03.12_M_release_185028_s igned.exe
( http://forum.xda-developers.com/showthread.php?t=1033922 )
then AlpharevX worked in seconds.
S-OFF ftw!
Click to expand...
Click to collapse
u r lucky, my IS shipped S-on with higher version rom v2.21.1400.8, can't downgrade to Optus.2.21.980.2, that's why i flash the wwe_2.30.405.1, but no luck, damn..
babyporch said:
Don't works. Tested now.
Click to expand...
Click to collapse
thanks, now i am trying to unlock it again under RH linux but seems fail, also stuck at acquring root for a long time.
Yes, stuck on acquring root. Worked well on old rom.
Please post your problem on alpharevx form.
babyporch said:
Yes, stuck on acquring root. Worked well on old rom.
Please post your problem on alpharevx form.
Click to expand...
Click to collapse
did it when generating the key. i chose the 'it doesnot work' and attach problem description, hope they improve the program soon
I also have the same problem.
I was on India Rom and Alpharex was not working for me.
then I changed to WWE 2.30.405.1 but still no luck.
I tried to upgrade my rom to Optus but it fails on the bootoader with 'main version is older' error
thahaac said:
I also have the same problem.
I was on India Rom and Alpharex was not working for me.
then I changed to WWE 2.30.405.1 but still no luck.
I tried to upgrade my rom to Optus but it fails on the bootoader with 'main version is older' error
Click to expand...
Click to collapse
no way to downgrade to a lower version if it's S-on, even you get a goldcard.
waiting patiently for the alpharevx update..
thahaac said:
waiting patiently for the alpharevx update..
Click to expand...
Click to collapse
or waiting someone to root this rom,then you can downgrade to old wwe and soff it
ma20at said:
or waiting someone to root this rom,then you can downgrade to old wwe and soff it
Click to expand...
Click to collapse
ma20at said:
or waiting someone to root this rom,then you can downgrade to old wwe and soff it
Click to expand...
Click to collapse
I dont it will be possible to install even if the Rom is rooted, since the device is S-ON
If you make a goldcard can you downgrade to a lower version? I had flashed my phone to 2.12.707.5 which is an Asia gingerbread ROM. I couldn't S-Off with alpharevx. So I made a goldcard and flashed my phone to 2.12.405.7 which is a Europe Gingerbread rom From there I was able to S-Off. Point being I went from a higher version to a lower version.
Sent from my HTC Incredible S using XDA Premium App
thahaac said:
I dont it will be possible to install even if the Rom is rooted, since the device is S-ON
Click to expand...
Click to collapse
that is possible, a rooted system can change the current version number to lower to trick the ruu so that you can flash a low version into the phone
Is there any progress is still not possible to
Has anybody scuccede Rooting the 2.30.405.1 Rom with the new AlpharevX 0.2pre5?
No temp root on 2.30.405.1 for now, then alpharevx can't works.
and how much time it will take untill the alpharevx team create a www 2.30.405.1 compitable version?
Hey I just want to make sure of a few things before I try this... I saw the thread below but it doesn't saying anything about being able to downgrade later on. I have a Bell incS with the stock 2.3.3 version 2.28.666.3. My phone is not rooted or S-Off but I have made a gold card and was going to flash the WWE RUU 2.30.405.1 to get rid of the bloat. Is it as simple as that? Would it be possible to downgrade back to the original Bell 2.28.666.3 RUU later if I needed warranty with the gold card or not? Also any issues to worry about with debranding like radio/wifi problems or anything else? Thanks
patrick92260 said:
Hey I just want to make sure of a few things before I try this... I saw the thread below but it doesn't saying anything about being able to downgrade later on. I have a Bell incS with the stock 2.3.3 version 2.28.666.3. My phone is not rooted or S-Off but I have made a gold card and was going to flash the WWE RUU 2.30.405.1 to get rid of the bloat. Is it as simple as that? Would it be possible to downgrade back to the original Bell 2.28.666.3 RUU later if I needed warranty with the gold card or not? Also any issues to worry about with debranding like radio/wifi problems or anything else? Thanks
Click to expand...
Click to collapse
If you don't have S-OFF on your BM IncS, then you won't be able to flash the WWE 2.30.405.1 RUU because that ROM is for the S710E model (model id PG321300) and the BM Incs is a S710A model (model id PG321200) and it will fail with 'wrong model id' error.
If you go ahead and S-OFF, then you can take the WWE 2.30.405.1 RUU and extract the ROM.zip and modify the android-info.txt file in the ROM.zip to change the model id. After that process, you would copy the modified ROM.zip file to the root of your SD card and rename it PG32IMG.zip. Then boot into HBOOT and it will find the PG32IMG.zip file and ask if you want to apply the update. You will then have an unbranded, unrooted IncS. The second advantage of S-OFF is that it will allow you to reflash the BM 2.28.666.3 RUU.
I'm looking at doing the same thing. Wondering if patrick92260 has had any success. I have the Virgin IS and want to debrand it as its loaded with useless BELL apps. Will be attempting this myself, let you know how it goes.
Q: First question is, now that I have the .exe of RUU. How do I go about getting the ROM.zip file.
Figured it out on my own, but for others who are curious.
A:Windows > Run > %TEMP%
Then list by 'last modified folder' and it should be the first one there.
I decided not to debrand the phone because of the different model ID for the Canadian IncS. If you debrand the phone to a WWE RUU it most likely won't ever be able to get an OTA update because when it's tries to update the phone's model ID will still be different. If there is no RUU for that new update then you'll probably be stuck with what you have.
Maybe if the IncS ever gets an actual radio S-Off I will try it.
If you still tried to debrand it though, how did it go?
patrick92260 said:
I decided not to debrand the phone because of the different model ID for the Canadian IncS. If you debrand the phone to a WWE RUU it most likely won't ever be able to get an OTA update because when it's tries to update the phone's model ID will still be different. If there is no RUU for that new update then you'll probably be stuck with what you have.
Maybe if the IncS ever gets an actual radio S-Off I will try it.
If you still tried to debrand it though, how did it go?
Click to expand...
Click to collapse
Just a point of clarification. When I debranded my Bell IncS, I put the original WWE GB 2.12.405.7 ROM on it. I then received the OTA notification that 2.30.405.1 was available, so even though you won't get a Bell OTA, you do get the WWE unbranded OTAs.
tpbklake said:
Just a point of clarification. When I debranded my Bell IncS, I put the original WWE GB 2.12.405.7 ROM on it. I then received the OTA notification that 2.30.405.1 was available, so even though you won't get a Bell OTA, you do get the WWE unbranded OTAs.
Click to expand...
Click to collapse
Hmm maybe I'll go ahead and give it a try then. You didn't have any issues upgrading to the WWE OTA or have problems once it was debranded? I ask just because I know if you debranded the original Desire it would kill the WiFi and I think it caused reception issues.
patrick92260 said:
Hmm maybe I'll go ahead and give it a try then. You didn't have any issues upgrading to the WWE OTA or have problems once it was debranded? I ask just because I know if you debranded the original Desire it would kill the WiFi and I think it caused reception issues.
Click to expand...
Click to collapse
I have not had any issues of debranding my Bell IncS with the WWE roms.
The OTA downloaded fine, but like all OTAs, it checks to make sure you have a stock version of the previous ROM, in this case 2.12.405.7. If you have ClockworkMod installed, the OTA will fail because that isn't the stock recovery. I could have flashed the stock recovery and ran the OTA, but I choose to take the 2.30.405.1 RUU and make a rooted version of it using dsi's XDA Android kitchen and ended up flashing that.
Debranding went smoothly. Flashed the WWE just fine after editing the file.
Then went ahead and installed 4EXTRecovery and Virtuous Unity over that though.
Whether doing the debranding helped or not, I'm not sure. Either way I'm down to just essential apps in this rom, no bloatware.
As for OTA updates, who cares really. If you're on this forum, you've got enough knowledge to flash yourself and not have to wait for OTA updates to arrive.
Original Bell Incredible S rom
Any one have the OEM "stock" rom/radio/kernel from Bell in case of warranty?
I did not think about this when I flashed mine and it would be great in case the hardware fail..
everything is working perfectly fine right now so it's just a "in case" question.
neurobrake said:
Any one have the OEM "stock" rom/radio/kernel from Bell in case of warranty?
I did not think about this when I flashed mine and it would be great in case the hardware fail..
everything is working perfectly fine right now so it's just a "in case" question.
Click to expand...
Click to collapse
Yes, the shipped Bell Mobile stock Gingerbread RUU can be found here:
RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805 .30.085AU_3805.04.03.27_M_release_199657_signed.
http://www.filefactory.com/file/cc9d...657_signed.exe
Thanks to football for posting the shipped ROMs in the Development section.
The file is gone.
tpbklake said:
Yes, the shipped Bell Mobile stock Gingerbread RUU can be found here:
RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805 .30.085AU_3805.04.03.27_M_release_199657_signed.
http://www.filefactory.com/file/cc9d...657_signed.exe
Thanks to football for posting the shipped ROMs in the Development section.
Click to expand...
Click to collapse
justaway2 said:
The file is gone.
Click to expand...
Click to collapse
Use the link that is in this thread (must have been a bad copy and paste):
http://forum.xda-developers.com/showthread.php?t=1033922
I need this file
tpbklake said:
Use the link that is in this thread (must have been a bad copy and paste):
http://forum.xda-developers.com/showthread.php?t=1033922
Click to expand...
Click to collapse
I need this file. Can you please update the link? Point me to it.
digitzgal said:
I need this file. Can you please update the link? Point me to it.
Click to expand...
Click to collapse
Go to the site HTCDEV.com and you can download the final ICS RUU.
Followup question
Thanks a tonne for responding.
I''ve an HTC Incredible S, it was at Bell's stock version, RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805 .30.085AU_3805.04.03.27_M_release_199657_signed. I followed this guide(http://forum.xda-developers.com/showthread.php?t=2118187) to root, install recovery-clockwork-5.0.2.0-vivo.img and soff my phone. I did not install any custom images on it.
In order to unroot and install the HTC OTA update/RUU:
Can I directly run this zip from HTC site and will it work? OR do I need to follow some other procedure to downgrade my phone to the default image(v2.3) and then upgrade to v4.0 ?
I found this v4.0 for Incrediable S for NAM (Canada) listed on HTCDEV site. Nothing else v2.3 or anything for Bell is listed there.
Incredible S
HTC
NAM (Canada)
RUU
N/A
v4.0 374.4 MB
4.14.405.2
digitzgal said:
Thanks a tonne for responding.
I''ve an HTC Incredible S, it was at Bell's stock version, RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805 .30.085AU_3805.04.03.27_M_release_199657_signed. I followed this guide(http://forum.xda-developers.com/showthread.php?t=2118187) to root, install recovery-clockwork-5.0.2.0-vivo.img and soff my phone. I did not install any custom images on it.
In order to unroot and install the HTC OTA update/RUU:
Can I directly run this zip from HTC site and will it work? OR do I need to follow some other procedure to downgrade my phone to the default image(v2.3) and then upgrade to v4.0 ?
I found this v4.0 for Incrediable S for NAM (Canada) listed on HTCDEV site. Nothing else v2.3 or anything for Bell is listed there.
Incredible S
HTC
NAM (Canada)
RUU
N/A
v4.0 374.4 MB
4.14.405.2
Click to expand...
Click to collapse
No, if you have BlackRose S-OFF, you will not be able to flash the 4.14.405.2 RUU. There is a link in my signature that is a stock, rooted ROM based on this RUU that you can safely install. I would recommend that along with poondog's kernel that is also linked in my signature.
Followup
Thanks tpbklake,
I didn't perform Step11, to install Blackrose.
I followed, Step 1, Skipped 2. Couldn't follow Step3, since I had bootrom HBOOT 1.13.0000, I could never get the OEM identifier token. Then I directly performed Step 9 to get revolutionary soff. Then I followed Step 4,5 to install clockwork recovery and root my phone. Then I performed Step 6. That's it. No other steps or flashing of custom rom.
Can I go ahead with the 4.0 RUU from HTCDev?
digitzgal said:
Thanks tpbklake,
I didn't perform Step11, to install Blackrose.
I followed, Step 1, Skipped 2. Couldn't follow Step3, since I had bootrom HBOOT 1.13.0000, I could never get the OEM identifier token. Then I directly performed Step 9 to get revolutionary soff. Then I followed Step 4,5 to install clockwork recovery and root my phone. Then I performed Step 6. That's it. No other steps or flashing of custom rom.
Can I go ahead with the 4.0 RUU from HTCDev?
Click to expand...
Click to collapse
No. Run the blackrose tool. (Make sure you have CM7 or another rooted ROM for this). Fully run it so that now, in the bootloader, instead of Revolutionary, You should see Blackrose. Then run the tool again but this time select Uninstall Blackrose and at the end of that, you should have HBOOT 1.13.0000. Relock bootloader and then run the RUU.
Or you can just use tbpklake's stock rooted ROM. That was built off the lateset WWE RUU I believe.
072665995 said:
No. Run the blackrose tool. (Make sure you have CM7 or another rooted ROM for this). Fully run it so that now, in the bootloader, instead of Revolutionary, You should see Blackrose. Then run the tool again but this time select Uninstall Blackrose and at the end of that, you should have HBOOT 1.13.0000. Relock bootloader and then run the RUU.
Or you can just use tbpklake's stock rooted ROM. That was built off the lateset WWE RUU I believe.
Click to expand...
Click to collapse
Thanks I can't use rooted ROM for a test I am doing.
So keep following the previous guide(http://forum.xda-developers.com/showthread.php?t=2118187) to perform Steps 10,11 for flashing CM7 and Blackrose. Then re-run Blackrose utility to uninstall it. Then lock the bootloader and run RUU from htcdev. Correct?
How do I lock the bootloader again?
digitzgal said:
Thanks I can't use rooted ROM for a test I am doing.
So keep following the previous guide(http://forum.xda-developers.com/showthread.php?t=2118187) to perform Steps 10,11 for flashing CM7 and Blackrose. Then re-run Blackrose utility to uninstall it. Then lock the bootloader and run RUU from htcdev. Correct?
How do I lock the bootloader again?
Click to expand...
Click to collapse
Ok now I'm just freaking confused. What are you trying to do?? Are you trying to root?? Or what??
i can't turn on wifi because i get error showing and i need help to installing stock rom and the hboot is 1.16 so please help me out to fix it so i can see if the wifi is working if not then i need stock rom to fix the wifi under warrenty please
morgy59 said:
i can't turn on wifi because i get error showing and i need help to installing stock rom and the hboot is 1.16 so please help me out to fix it so i can see if the wifi is working if not then i need stock rom to fix the wifi under warrenty please
Click to expand...
Click to collapse
Ok a little more information please. Is this a new IncS that shipped with HBOOT 1.16? If not, did you receive an OTA update that installed HBOOT 1.16? In either case unless you went through the procedure at HTCDEV site to UnLock the bootloader and flash a custom recovery and a new ROM, ou probably still have a stock ROM on it.
So if you could explain in more detail the current state of your system it would help.
i got hboot 1.16 preinstalled and i'm currently trying to boot miui rom
morgy59 said:
i got hboot 1.16 preinstalled and i'm currently trying to boot miui rom
Click to expand...
Click to collapse
So you have unlocked the bootloader and flashed a custom recovery and then flashed MIUI? After you flashed MIUI did you extract the boot.img from the MIUI zip file and flash it using the FASTBOOT command?
i just done it and i would like to know how to reinstall stock rom with hboot 1.16 and radio version is 3805.07.03.05 please
morgy59 said:
i just done it and i would like to know how to reinstall stock rom with hboot 1.16 and radio version is 3805.07.03.05 please
Click to expand...
Click to collapse
This post has a whole bunch of shipped stock ROMs. Download the one for your carrier and then run the RUU.exe on your PC and follow the instructions.
http://forum.xda-developers.com/showthread.php?t=1033922
which operating system is best to use ruu on i am running windows 7 x64 sp1
morgy59 said:
which operating system is best to use ruu on i am running windows 7 x64 sp1
Click to expand...
Click to collapse
I have run RUU successfully using Windows 7 X64. Just make sure you have the current HTC Sync drivers installed.
error [155]: unknown error
the rom update utility cannot update your android phone
please get the correct rom update utility and try again
morgy59 said:
error [155]: unknown error
the rom update utility cannot update your android phone
please get the correct rom update utility and try again
Click to expand...
Click to collapse
What carrier are you on and which RUU did you try to run?
optus and using optus ruu
morgy59 said:
optus and using optus ruu
Click to expand...
Click to collapse
Ok the only Optus RUU that is there is the original Optus GB ROM and not the most current that has HBOOT 1.16 in it. That is why the RUU is failing. HBOOT 1.16 will not let you downgrade the HBOOT version by running an older RUU.
so how can i restore to stock using ruu hboot 1.16 then
morgy59 said:
so how can i restore to stock using ruu hboot 1.16 then
Click to expand...
Click to collapse
Did you make a nandroid backup in recovery before you tried flashing Miui? If not then you are stuck with using custom ROMs until your RUU is available for downloading.
no and i using Nik IncredibleS TriNiTy SensationXL V 2.0 and i had to use a different rom then fastboot the boot.img then i reinstall Nik IncredibleS TriNiTy SensationXL V 2.0 and the wifi working again
Help, I am trying to Install custom rom and i get the Error[155] Unknown Error while trying to S-Off the Device.
Earlier i had tried to S-Off and had done it successfully, somewhere, somehow, i had managed to screwup the phone where it would not pass the the HTC screen. so i had to try and get the phone back to stock and i guess thats where the issue began. I downloaded the RUU "RUU_VIVO_ICS_35_S_hTC_Asia_WWE_4.10.707.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266513_signed" and was successful in installing, after which any RUU i run, i get the Error 155. the RUU is a Asian release and not happy with it as there is no English UK or US in it.
currently the details of my Device are as Follows
Security: S-On
HBoot: 2.02.0002
Radio: 3831.18.00.11_M
Bootloader: Unlocked
Managed to install ROM "vivo_signed_WWE_4.10.405.1_ICS_SENSE36_8" today. But i desperately want to install a ROM with Sense 4. Any help is appreciated. Thanks in advance.
Nav
(Code 155 )means that your bootloader is unlocked !
I do not understand fully , but To install A (Ruu.exe) your bootloader must be relocked
Relock bootloader
And install this Ruu
http://d-h.st/7UC
Greet serge
Sent from my Incredible S using XDA Premium App
77777777777777 said:
(Code 155 )means that your bootloader is unlocked !
Relock
And install this Ruu:
http://d-h.st/7UC
Greet serge
Sent from my Incredible S using XDA Premium App
Click to expand...
Click to collapse
Thank you 77777777777777,
i tried what you said. relocked the boot loader and then ran the RUU you recommended.
I still get the same error
Nav
In fastboot usb to pc !
press power button to select fasboot
And on your phone is (fastboot USB) visible ? Yes
Than install the ruu !
Sent from my Incredible S using XDA Premium App
nvnran said:
Help, I am trying to Install custom rom and i get the Error[155] Unknown Error while trying to S-Off the Device.
Earlier i had tried to S-Off and had done it successfully, somewhere, somehow, i had managed to screwup the phone where it would not pass the the HTC screen. so i had to try and get the phone back to stock and i guess thats where the issue began. I downloaded the RUU "RUU_VIVO_ICS_35_S_hTC_Asia_WWE_4.10.707.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266513_signed" and was successful in installing, after which any RUU i run, i get the Error 155. the RUU is a Asian release and not happy with it as there is no English UK or US in it.
currently the details of my Device are as Follows
Security: S-On
HBoot: 2.02.0002
Radio: 3831.18.00.11_M
Bootloader: Unlocked
Managed to install ROM "vivo_signed_WWE_4.10.405.1_ICS_SENSE36_8" today. But i desperately want to install a ROM with Sense 4. Any help is appreciated. Thanks in advance.
Nav
Click to expand...
Click to collapse
With an unlocked bootloader, you simply need to flash a custom Recovery to your device and then you will be able to flash any custom ROM you want. The only drawback is to remember to manually flash the ROM's boot.img file in FASTBOOT USB mode since you have an unlocked bootloader.
There is a sticky thread that details how to install a custom recovery and flash custom ROMs. It's title indicates HBOOT 1.16 and 2.00, but it will also work with unlocked 2.02.0002. that you have also.
If you really insist of getting S-OFF back, then you will need to visit the Downgrade Script sticky post and use that procedure to downgrade your ROM and HBOOT.
I do Have ClockworkMod Recovery Installed.
Thanks 77777777777777 and tpbklake
Tried what you both have mentioned. Now i got a New Error. Error [140]: BOOTLOADER VERSION ERROR
please advise
Nav
nvnran said:
Thanks 77777777777777 and tpbklake
Tried what you both have mentioned. Now i got a New Error. Error [140]: BOOTLOADER VERSION ERROR
please advise
Nav
Click to expand...
Click to collapse
You are not going to be able to flash an official RUU because you currently have the most recent one installed and you cannot downgrade without using the Downgrade script.
Beside, you said you want a ROM with Sense 4 so your only choice is going to be a custom ROM. So just unlock your bootloader and go to the Development section and try out the different Sense 4 ROMs and quit trying to get a RUU going.
tpbklake said:
You are not going to be able to flash an official RUU because you currently have the most recent one installed and you cannot downgrade without using the Downgrade script.
Beside, you said you want a ROM with Sense 4 so your only choice is going to be a custom ROM. So just unlock your bootloader and go to the Development section and try out the different Sense 4 ROMs and quit trying to get a RUU going.
Click to expand...
Click to collapse
Thank you tpbklake,
I did try to use the Custom Rom by Nik (Nik's Project X)
After installing the ROM, the boot process does not pass beyond the Initial HTC Screen. It gets stuck there. also triedleaving it at the same screen for over an hour.
Any thoughts on that?
Nav
Tried Installing IceCold Sandwich 8.3 and Cooldroid 6.1 (previously Nik's Project X)
All of them give the same result.
after installing the rom, restart, Initial HTC Screen, and stuck there.
your thoughts please.
Nav
nvnran said:
Tried Installing IceCold Sandwich 8.3 and Cooldroid 6.1 (previously Nik's Project X)
All of them give the same result.
after installing the rom, restart, Initial HTC Screen, and stuck there.
your thoughts please.
Nav
Click to expand...
Click to collapse
Try to fastboot flash boot boot.img
Steps are outlined in the sticky by lynt in this forum
Sent from my Nexus 7
nvnran said:
Thank you tpbklake,
I did try to use the Custom Rom by Nik (Nik's Project X)
After installing the ROM, the boot process does not pass beyond the Initial HTC Screen. It gets stuck there. also triedleaving it at the same screen for over an hour.
Any thoughts on that?
Nav
Click to expand...
Click to collapse
nvnran said:
Tried Installing IceCold Sandwich 8.3 and Cooldroid 6.1 (previously Nik's Project X)
All of them give the same result.
after installing the rom, restart, Initial HTC Screen, and stuck there.
your thoughts please.
Nav
Click to expand...
Click to collapse
Once again, when you have the unlocked bootloader and you are flashing a custom ROM via Recovery, you then need to extract the boot.img file that is in the ROM's zip file and flash it manually in FASTBOOT USB mode! That is how you get around the issue with hanging at the HTC Screen and that is the step you have missed. I even gave you a link yesterday to the thread that tells you how to flash a custom ROM on the unlocked hboot.
So please read the posts to your questions very carefully and completely.
---------- Post added at 07:41 AM ---------- Previous post was at 07:40 AM ----------
markj338 said:
Try to fastboot flash boot boot.img
Steps are outlined in the sticky by lynt in this forum
Sent from my Nexus 7
Click to expand...
Click to collapse
Maybe if he hears it from someone else he might get it. Thx.
So I have bricked my phone and all I want is to go back to stock. I have tried flashing OMJ's 3.04.651.2 firmware through fastboot and it completes it successfully... so it says. When I proceed to reboot, I am yet again taken to the HTC screen, the screen then goes black, after a while the screen shows an HTC one with a red triangle in it. I am desperite, please help!
Relocked
S-on
HBOOT 1.55
Radio 1.00.20.0913_3
OS 3.04.651.2
MacSkizzle said:
So I have bricked my phone and all I want is to go back to stock. I have tried flashing OMJ's 3.04.651.2 firmware through fastboot and it completes it successfully... so it says. When I proceed to reboot, I am yet again taken to the HTC screen, the screen then goes black, after a while the screen shows an HTC one with a red triangle in it. I am desperite, please help!
Relocked
S-on
HBOOT 1.55
Radio 1.00.20.0913_3
OS 3.04.651.2
Click to expand...
Click to collapse
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
jab74101 said:
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can I get s-off? All I can access is my bootloader.
jab74101 said:
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I downloaded, extracted, and ran the correct soju but I get an error. It says to run rumrunner again and READ... I don't know what I did wrong. I did this with my phone in fastboot usb mode, is that right?
MacSkizzle said:
Can I get s-off? All I can access is my bootloader.
Click to expand...
Click to collapse
I'm pretty sure that's all you need. But I could be wrong.
TriBeard said:
I'm pretty sure that's all you need. But I could be wrong.
Click to expand...
Click to collapse
When I run the rumrunner program, I type 'Yes' twice then I get an error telling me to run rumrunner again and READ. What did I do wrong?
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
ZHoob2004 said:
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
Click to expand...
Click to collapse
I'll try this tonight when I get home from work, thanks for the input.
ZHoob2004 said:
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
Click to expand...
Click to collapse
This didn't do it either. PLEASE SOMEONE HELP ME
I don't know if you can flash OMJ's firmware if your bootloader is set to "Relocked". I could be wrong but I think what you need to do is unlock it again first and install a recovery. Then flash OMJ's stock firmware from recovery. From there you can probably do the S-OFF process and RUU back to stock.
You do need to be able to boot into your ROM for S-OFF to work, as you start the S-OFF process while the phone is booted up and running.
MacSkizzle said:
This didn't do it either. PLEASE SOMEONE HELP ME
Click to expand...
Click to collapse
Look HERE