Related
I recently re-locked my bootloader (never had s-off) and flashed the appropriate RUU to restore my device back to complete stock, however now it won't pull the ICS update and I'm having a hard time figuring out what issue is. Is there any chance that someone can help me get this working? When I check the status of the upgrade server it's completely blank except for the source: Verizon Wireless and code: 0 any idea?
Flash the GB RUU and it will update to ICS after the install. If you flashed the ICS leaks then you need to S off so that you can get back to GB. Getting S off is very easy. I would recommend it so you can flash all the new roms.
Sent from my ADR6425LVW using Tapatalk 2
DownRiver_Droid said:
Flash the GB RUU and it will update to ICS after the install. If you flashed the ICS leaks then you need to S off so that you can get back to GB. Getting S off is very easy. I would recommend it so you can flash all the new roms.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Hello, I have a stock Rooted Rezound runniong 2.3.4 android. I got prompted to install ICS, and i delayed it, and it installed anyway and my phone would not get past the HTC screen. I have cwm installed, and i reverted back to the day i rooted.
How do i get the phone back to "stock" so i can get the OTA properly. is there a thread i can follow? i am s-on i think. (how do i tell, i thought i was s-off, see below for the bootloader screen)
when o go to the boot loader it says
*** UNLOCKED *** (in pink)
VIGOR PVT SHIPS S-ON RL
HBOOT-2.11.0000
eMMC-boot
You are S-On.
Download the GB RUU.
Relock the bootloader.
Run the GB RUU.
Let the OTA install.
EmerikL said:
You are S-On.
Download the GB RUU.
Relock the bootloader.
Run the GB RUU.
Let the OTA install.
Click to expand...
Click to collapse
thanks, where do i find the GB RUU? Theres so much stuff on these forums sometimes its hard to find it. I found this unroot thread. but the links to download seem to be down
http://forum.xda-developers.com/showthread.php?t=1472606
DownRiver_Droid said:
Flash the GB RUU and it will update to ICS after the install. If you flashed the ICS leaks then you need to S off so that you can get back to GB. Getting S off is very easy. I would recommend it so you can flash all the new roms.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
That's what I did, it won't pull any update.
john10101 said:
thanks, where do i find the GB RUU? Theres so much stuff on these forums sometimes its hard to find it. I found this unroot thread. but the links to download seem to be down
http://forum.xda-developers.com/showthread.php?t=1472606
Click to expand...
Click to collapse
Check Shipped-roms.com.
Sent from my ADR6425LVW using xda app-developers app
I dont see the rezound listed on that site.
[RUU] HTC Rezound RUU RoundUp
Includes most RUU's release for the Rezound, except the latest 4.3.605.2 version. Their server is a little slow, but it always seems to work.
acejavelin said:
[RUU] HTC Rezound RUU RoundUp
Includes most RUU's release for the Rezound, except the latest 4.3.605.2 version. Their server is a little slow, but it always seems to work.
Click to expand...
Click to collapse
So i think i figured out the shipped roms site. the Rezound is under vigor.
so which one do i flash theres 3 different roms.
how do i figure out which one i am on
1.00.605.3
1.02.605.6
2.01.605.11
also is there another link for the fastboot tool? so i can lock it again? Will these replace cwm on my device?
You have boot 2.11 so you need to get the 2.01 ruu. And yes it will return it too 100 percent stock including the recovery. You want to keep kt that way until after you update with the ota.
Sent from my GT-N8013 using xda premium
DigitalDementia said:
I recently re-locked my bootloader (never had s-off) and flashed the appropriate RUU to restore my device back to complete stock, however now it won't pull the ICS update and I'm having a hard time figuring out what issue is. Is there any chance that someone can help me get this working? When I check the status of the upgrade server it's completely blank except for the source: Verizon Wireless and code: 0 any idea?
Click to expand...
Click to collapse
What happens when you check for a new update? Does it sit there for a couple seconds and then just disappear and not say anything? Or does it at least tell you that "there is no update available"? I had this same issue on the GB update: http://forum.xda-developers.com/showthread.php?t=1469246
basically what I had to do what activate my SIM on another rezound and then put it back into my original and it started pulling the updates.
http://forum.xda-developers.com/showpost.php?p=22502775&postcount=22
murhaava1 said:
What happens when you check for a new update? Does it sit there for a couple seconds and then just disappear and not say anything? Or does it at least tell you that "there is no update available"? I had this same issue on the GB update: http://forum.xda-developers.com/showthread.php?t=1469246
basically what I had to do what activate my SIM on another rezound and then put it back into my original and it started pulling the updates.
http://forum.xda-developers.com/showpost.php?p=22502775&postcount=22
Click to expand...
Click to collapse
Great. so the thread i found has the fast boot tool listed on it for relocking the boot loader (which from what i understand i have to do first) the link to download the tool is down. does anyone have an alternate download location for this tool?
I found the tool in another thread. http://forum.xda-developers.com/showpost.php?p=20780879&postcount=1
I was able to lock the device. Push the RUU 2.01 (like recommended) I then pulled down two OTA updates. One "prepared for ICS" the second installed ICS
thanks for your help.
Hello, I desperately would like to see how to put my HTC Amaze back to stock. A couple of months ago I tried putting it back to stock because the energy rom kept rebooting on me and draining my battery life randomly. Anyways I was not successful and so I just kept the rom and the rebooting problems stopped anyways. Now, its happening again and I would really love for some one to help me get it back to stock so I can see if it improves and maybe get the thing S-OFF later. I am with Wind mobile.
Any help is greatly appreciated,
A frustrated amaze user.
rspierz said:
Hello, I desperately would like to see how to put my HTC Amaze back to stock. A couple of months ago I tried putting it back to stock because the energy rom kept rebooting on me and draining my battery life randomly. Anyways I was not successful and so I just kept the rom and the rebooting problems stopped anyways. Now, its happening again and I would really love for some one to help me get it back to stock so I can see if it improves and maybe get the thing S-OFF later. I am with Wind mobile.
Any help is greatly appreciated,
A frustrated amaze user.
Click to expand...
Click to collapse
Well since you're s on lock your bootloader and flash a wind ruu from bootloader you can find the necessary thread in development section
Sent from my HTC_Amaze_4G using xda premium
ravike14 said:
Well since you're s on lock your bootloader and flash a wind ruu from bootloader you can find the necessary thread in development section
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Hey thanks for the response. So I locked the bootloader and then got the wind RUU renamed it as PH85img.zip or w/e its supposed to be. And now when in the boot screen it cannot find my file I then tried another RUU but this time is used the exe wind one but that one failed as well and came up as an error saying the hboot version is older then what im flashing or something?
So I am stuck at this point. Do you know how to get around this?
Make sure the ruu is on the root of the sd card
Sent from my SGH-T999 using Tapatalk 2
rspierz said:
Hey thanks for the response. So I locked the bootloader and then got the wind RUU renamed it as PH85img.zip or w/e its supposed to be. And now when in the boot screen it cannot find my file I then tried another RUU but this time is used the exe wind one but that one failed as well and came up as an error saying the hboot version is older then what im flashing or something?
So I am stuck at this point. Do you know how to get around this?
Click to expand...
Click to collapse
well you cant flash a exe you have to connect your phone to the pc and run the exe from pc and bout the hboot whats your current version? :/
ravike14 said:
well you cant flash a exe you have to connect your phone to the pc and run the exe from pc and bout the hboot whats your current version? :/
Click to expand...
Click to collapse
Yeah it was connected via usb. I got somewhere, now but im am hoping you can tell me what i need to do now. I followed the second post here : http://forum.xda-developers.com/showthread.php?t=2167596 and now I have GB rom on my phone running unlocked. What do I need to do from here so I can S-off and super CID? PS I tried doing an OTA update from the phone and it wont work.
Looking into the S-off guide it says i must be on a stock RUU. is the one i got install a stock RUU. Also my hboot version is 1.93.0002 (Mar 15 2012) which is ice cream sandwich according to the Unlimited.IO site, but the RUU im on is definitely gingerbread. What can I do about this?
rspierz said:
Looking into the S-off guide it says i must be on a stock RUU. is the one i got install a stock RUU. Also my hboot version is 1.93.0002 (Mar 15 2012) which is ice cream sandwich according to the Unlimited.IO site, but the RUU im on is definitely gingerbread. What can I do about this?
Click to expand...
Click to collapse
What is your android version in settings?? Cuz what your telling is kinda weird
Sent from my HTC_Amaze_4G using xda premium
Adroid Version: 2.3.4
HTC Sense version: 3.0
Software number 1.43.531.3
am I completely screwed now? Cause it seems i wont be able to get S-off or CID off while not on this unsigned rom (t-mobile), i am with Wind. The OTA does not work while on the phone (settings > software update). Would locking my bootloader and then loading the latest OTA zip from wind on the SD card work? I am very stuck!
rspierz said:
am I completely screwed now? Cause it seems i wont be able to get S-off or CID off while not on this unsigned rom (t-mobile), i am with Wind. The OTA does not work while on the phone (settings > software update). Would locking my bootloader and then loading the latest OTA zip from wind on the SD card work? I am very stuck!
Click to expand...
Click to collapse
well you have ginger bread so try the jbear GB s off tool in ubuntu
but what about the hboot version being ICS? Do you think it should still work?
rspierz said:
but what about the hboot version being ICS? Do you think it should still work?
Click to expand...
Click to collapse
what bout your CID?
I havent done anything to the CID, so I believe it is still locked to wind?
rspierz said:
I havent done anything to the CID, so I believe it is still locked to wind?
Click to expand...
Click to collapse
well choice is yours your android version says GB hboot says ICS :/ i say try the GB s-off tool but do at your own risk...
well S-Off worked so thats good haha. Now i am trying to super CID. However, when uploading the proper hboot for doing so it wont let me because of the CID.
Ignore that last post. I figured it out so all is good. Now here is another question, should i flash CM10.1 or your rom that viper one? How would I go about flashing a rom. I remembered before you would just go into recovery and then format all execpt sd card and then install from zip. I tried that with the CM10.1 rom and when I rebooted it did not work.
went ahead and tried installing the Viper rom and after i reboot (when it said all was good) it show a black screen with green arrows. And its stuck on that. I do not know what to do now. Because I should have everything open. Was I supposed to flash something after doing the S-OFF?
This is what I am getting stuck on. I tried another rom too, same thing. I can boot into 4ext. But cant get past this on boot up.
rspierz said:
This is what I am getting stuck on. I tried another rom too, same thing. I can boot into 4ext. But cant get past this on boot up.
Click to expand...
Click to collapse
Now your s off BUT you have gb firmware so you have to flash a ruu 1st then flash a recovery then supersu or just flash any rom you want if you decide to stay with the ruu stock rom to gain root permission flash supersu
Sent from my HTC_Amaze_4G using xda premium
hello all,
I am trying to bring my phone back to stock, I already relocked with bootloader with fastboot.
and when I ran the ATT RUU (RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe)
it came back with an error saying "ERROR [132]: SIGNATURE ERROR"
p.s. I was running cyangen mod 10.1 when trying all this....how do i fix this?
UPDATE: now when I try to reboot the system it goes straight to the bootloader, it wont even boot into an OS.
are you s-off?
skinsfanbdh said:
are you s-off?
Click to expand...
Click to collapse
no, it was never s-off...i thought ATT phones couldn't be s-off.
cms062407 said:
no, it was never s-off...i thought ATT phones couldn't be s-off.
Click to expand...
Click to collapse
s-off is working for all variants i believe but i know it works for at&t
you might be trying to install the wrong ruu.
Ruu fail
cms062407 said:
hello all,
I am trying to bring my phone back to stock, I already relocked with bootloader with fastboot.
and when I ran the ATT RUU (RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe)
it came back with an error saying "ERROR [132]: SIGNATURE ERROR"
p.s. I was running cyangen mod 10.1 when trying all this....how do i fix this?
UPDATE: now when I try to reboot the system it goes straight to the bootloader, it wont even boot into an OS.
Click to expand...
Click to collapse
If you came from a CM variant you might want to re flash what you had. If you want to flash ruu you need to relock bootloader. It took two times for my One to take the update. FYI you will NOT have root with ruu. BTW most US roms are built on that base. If you just want a newer base the international roms like trick droid ( what i am running ), ARHD and insert coin are on the newest builds with jelly bean 4.2.2. just sayin'
skinsfanbdh said:
s-off is working for all variants i believe but i know it works for at&t
you might be trying to install the wrong ruu.
Click to expand...
Click to collapse
Is there a link to all the ATT RUUs? I did notice it said my current version was different than the "your phone will update to this" version.
cms062407 said:
Is there a link to all the ATT RUUs? I did notice it said my current version was different than the "your phone will update to this" version.
Click to expand...
Click to collapse
there is a tread on the international forum in general that has a list of ruus
Stock
myvwrocks said:
If you came from a CM variant you might want to re flash what you had. If you want to flash ruu you need to relock bootloader. It took two times for my One to take the update. FYI you will NOT have root with ruu. BTW most US roms are built on that base. If you just want a newer base the international roms like trick droid ( what i am running ), ARHD and insert coin are on the newest builds with jelly bean 4.2.2. just sayin'
Click to expand...
Click to collapse
I just reread you want to go back to stock. Same applies. Check international att original andriod development boards. They have stock newer builds there than the cingular build. It took three tries to get it to take on my One.
myvwrocks said:
If you came from a CM variant you might want to re flash what you had. If you want to flash ruu you need to relock bootloader. It took two times for my One to take the update. FYI you will NOT have root with ruu. BTW most US roms are built on that base. If you just want a newer base the international roms like trick droid ( what i am running ), ARHD and insert coin are on the newest builds with jelly bean 4.2.2. just sayin'
Click to expand...
Click to collapse
bootloader has been relocked
is there more than one RUU?
myvwrocks said:
I just reread you want to go back to stock. Same applies. Check international att original andriod development boards. They have stock newer builds there than the cingular build. It took three tries to get it to take on my One.
Click to expand...
Click to collapse
hehe international ATT?
International att
cms062407 said:
hehe international ATT?
Click to expand...
Click to collapse
Yes it sounds funny. But there alot of developers building international built completly stock roms for us at&t users
there might be. without s-off you can only install the ruu that is the exact same firmware version your phone came with i believe and yes sometimes it takes a few times to get it to finish without errors
try downloading the RUU again. There's Only ONE RUU for AT&T. Also if you unlock the bootloader again your phone will boot. With a locked bootloader and S-ON, only a fully stock ROM will boot.
okey dokey...i will try again in a bit (my phone isn't charged to 30%)
skinsfanbdh said:
there might be. without s-off you can only install the ruu that is the exact same firmware version your phone came with i believe and yes sometimes it takes a few times to get it to finish without errors
Click to expand...
Click to collapse
sooo the RUU says my current image version is 1.26.502.10 and the updated image version is 1.26.502.12....I read somewhere these numbers have to be the same? is that true???
cms062407 said:
sooo the RUU says my current image version is 1.26.502.10 and the updated image version is 1.26.502.12....I read somewhere these numbers have to be the same? is that true???
Click to expand...
Click to collapse
i think so but im not sure. easiest way if you cant get that to work after a few tries is to reunlock bootloader as gunny said and boot back to your current rom. achieve s-off and supercid then relock bootloader and flash the ruu you have
gunnyman said:
try downloading the RUU again. There's Only ONE RUU for AT&T. Also if you unlock the bootloader again your phone will boot. With a locked bootloader and S-ON, only a fully stock ROM will boot.
Click to expand...
Click to collapse
hmmmm.....i re-downloaded the RUU and tried to reinstall and got the exact same error...
skinsfanbdh said:
i think so but im not sure. easiest way if you cant get that to work after a few tries is to reunlock bootloader as gunny said and boot back to your current rom. achieve s-off and supercid then relock bootloader and flash the ruu you have
Click to expand...
Click to collapse
No. .12 is the latest stock firmware and the only RUU we saw leaked.
gunnyman said:
No. .12 is the latest stock firmware and the only RUU we saw leaked.
Click to expand...
Click to collapse
hmm, that's what I thought on the .12.....
I just noticed the RUU is getting stuck at the "sending" part to my phone, it seems like it isn't even getting to send the RUU to my phone....any idea about this?
i have heard a lot that people get errors a few times then it just works all the sudden. so try a few more times you dont need to keep redownloading it everytime just try flashing. if that doesnt work do what i said before
I have a HTC desire 601 bought this Summer from Virgin Mobile USA, a CDMA based carrier using Sprint network. My son played with it yesterday and now it is bricked. A "HTC" log is shown up and frozen in the display, not able to shutdown the phone by pressing anything.
I asked my son what he did, but he didnt say anything as he is afraid of punishment
what I can do is try to remove the battery, then hold the volume down key and power key, then it brings up this screen:
***Tampered***
***Unlocked***
ZARA_C PVT SHIP S-ON RL
HBOOT-2.20.0000
RADIO-1.14.50.1003
OpenDSP-v16.2.0268.noBeats.0902
OS-1.10.652.9
eMMC-boot 1024MB
Oct 7 2013 18:39.56.0
HBOOT
<vol_up>to previewitem
<vol_down> to next item
<power> to select item
Fastboot
Recovery
Factory reset
CLEAR storage
SIMLOCK
Image CRC
Show barcode
after I press "recovery", it enter this page::
Team Win Recovery project v2.7.1.1(kk)
Install Wipe
Backup Restore
Mount Settings
Advanced Reboot
what I want to to go back to the stock Virgin Mobile ROM. what should I do? thanks.
I'm assuming you don't have a backup... Try a factory reset from twrp, if that didn't help seek out a zara_cl backup
attrunner said:
I have a HTC desire 601 bought this Summer from Virgin Mobile USA, a CDMA based carrier using Sprint network. My son played with it yesterday and now it is bricked. A "HTC" log is shown up and frozen in the display, not able to shutdown the phone by pressing anything.
I asked my son what he did, but he didnt say anything as he is afraid of punishment
what I can do is try to remove the battery, then hold the volume down key and power key, then it brings up this screen:
***Tampered***
***Unlocked***
ZARA_C PVT SHIP S-ON RL
HBOOT-2.20.0000
RADIO-1.14.50.1003
OpenDSP-v16.2.0268.noBeats.0902
OS-1.10.652.9
eMMC-boot 1024MB
Oct 7 2013 18:39.56.0
HBOOT
<vol_up>to previewitem
<vol_down> to next item
<power> to select item
Fastboot
Recovery
Factory reset
CLEAR storage
SIMLOCK
Image CRC
Show barcode
after I press "recovery", it enter this page::
Team Win Recovery project v2.7.1.1(kk)
Install Wipe
Backup Restore
Mount Settings
Advanced Reboot
what I want to to go back to the stock Virgin Mobile ROM. what should I do? thanks.
Click to expand...
Click to collapse
You're still on the old firmware so you can simply use the RUU which can be downloaded from my Drive.
Re-reading your post I see a problem - You installed the KitKat recovery on your device but your device is still Jelly Bean. As stated in the thread, you want the official version from TWRP's site if you're still on Jelly Bean
-Duir- said:
You're still on the old firmware so you can simply use the RUU which can be downloaded from my Drive[/URL].
Re-reading your post I see a problem - You installed the KitKat recovery on your device but your device is still Jelly Bean. As stated in the thread, you want the official version from TWRP's site if you're still on Jelly Bean
Click to expand...
Click to collapse
sir, can you show me where did you see it's Kitkat recovery on my device, and where did you see it's still Jelly bean? I am still leaning.
attrunner said:
sir, can you show me where did you see it's Kitkat recovery on my device, and where did you see it's still Jelly bean? I am still leaning.
Click to expand...
Click to collapse
Team Win Recovery project v2.7.1.1(kk)
^^where it says "kk" at the end means that is a kitkat recovery.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Hedied4me said:
Team Win Recovery project v2.7.1.1(kk)
^^where it says "kk" at the end means that is a kitkat recovery.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Click to expand...
Click to collapse
where it shows it's jelly bean? thank you very much.
attrunner said:
where it shows it's jelly bean? thank you very much.
Click to expand...
Click to collapse
The OS version in your post is Jelly Bean.
-Duir- said:
You're still on the old firmware so you can simply use the RUU which can be downloaded from my Drive.
Re-reading your post I see a problem - You installed the KitKat recovery on your device but your device is still Jelly Bean. As stated in the thread, you want the official version from TWRP's site if you're still on Jelly Bean
Click to expand...
Click to collapse
sir, This is what I did:
1 I tried to use the RUU (file name RUU_ZARA_CL_JB422_SENSE50_Sprint_WWE_VM_1.10.652.9_Radio_1.14.50.1003_NV_SPCS_5.17_003_PRL55009_release_337148_signed_2.exe), but after the RUU erase data, and trying to send data, it has error message:
ERROR[155]: unknown error.
The ROM Update Utility can not update your Android phone.
Please get the correct ROM update utility and try again.
2 I tried different TWRP version as recovery, then use your RUU, all failed as step 1.
openrecovery-twrp-2.6.3.0-zaracl
openrecovery-twrp-2.7.0.0-zaracl
openrecovery-twrp-2.7.1.0-zaracl
3. I tried a stock ROM in Google dirve:
/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing#list
I chose file JB_stock_system_dump.zip, tried to copy to external SD card and install from recovery, but failed.
So please help what should I try next. thank you very much
attrunner said:
sir, This is what I did:
1 I tried to use the RUU (file name RUU_ZARA_CL_JB422_SENSE50_Sprint_WWE_VM_1.10.652.9_Radio_1.14.50.1003_NV_SPCS_5.17_003_PRL55009_release_337148_signed_2.exe), but after the RUU erase data, and trying to send data, it has error message:
ERROR[155]: unknown error.
The ROM Update Utility can not update your Android phone.
Please get the correct ROM update utility and try again.
2 I tried different TWRP version as recovery, then use your RUU, all failed as step 1.
openrecovery-twrp-2.6.3.0-zaracl
openrecovery-twrp-2.7.0.0-zaracl
openrecovery-twrp-2.7.1.0-zaracl
3. I tried a stock ROM in Google dirve:
/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing#list
I chose file JB_stock_system_dump.zip, tried to copy to external SD card and install from recovery, but failed.
So please help what should I try next. thank you very much
Click to expand...
Click to collapse
Lock the bootloader and then run it.
Also:
Custom recovery does not affect the RUU.
The system dump zip is literally that, a dump of the system partition. As such, it's not recovery flashable.
-Duir- said:
Lock the bootloader and then run it.
Also:
Custom recovery does not affect the RUU.
The system dump zip is literally that, a dump of the system partition. As such, it's not recovery flashable.
Click to expand...
Click to collapse
Don't lock the boot loader, that's not why the ruu is failing.
You need to change the mid first
mrplowdan said:
Don't lock the boot loader, that's not why the ruu is failing.
You need to change the mid first
Click to expand...
Click to collapse
That's exactly why it's failing. You need to be relocked to run the RUU.
-Duir- said:
That's exactly why it's failing. You need to be relocked to run the RUU.
Click to expand...
Click to collapse
Perhaps its different for the cl varient but for my ul, I'm 100% positive you don't need to be relocked. However, mid and cid must match the ruu.
*edit*
Also your hboot must be older or the same version as the ruu's hboot
mrplowdan said:
Perhaps its different for the cl varient but for my ul, I'm 100% positive you don't need to be relocked. However, mid and cid must match the ruu.
*edit*
Also your hboot must be older or the same version as the ruu's hboot
Click to expand...
Click to collapse
Well, they have the Virgin Mobile zara_cl variant which the RUU is made for, so the mid and cid shouldn't be an issue since they're S-ON and can't change it. Also, as stated their using 4.2.2. They still have the old firmware and partition layout which is why the version of twrp they installed won't work so hboot version is also not an issue. Also, it throws a different error if your device has a newer hboot than the RUU.
While it's not entirely outside the realm of possibility that something else could be causing the error, it's definitely not hboot version or mid/cid.
Were you S-OFF when you ran RUU on unlocked bootloader? I'm not sure of all the benefits of being S-OFF, but maybe one is being able to RUU with an unlocked bootloader. It makes perfect sense for an unlocked bootloader to throw an error since it can void your warranty and RUUs are generally ran by service techs.
But in all my experience the bootloader needs to be locked/relocked for the RUU to run.
-Duir- said:
... Were you S-OFF when you ran RUU on unlocked bootloader? I'm not sure of all the benefits of being S-OFF, but maybe one is being able to RUU with an unlocked bootloader. It makes perfect sense for an unlocked bootloader to throw an error since it can void your warranty and RUUs are generally ran by service techs.
But in all my experience the bootloader needs to be locked/relocked for the RUU to run.
Click to expand...
Click to collapse
I haven't tried running the ruu while s-on. I'm pretty sure the distinction is if your s-off you can flash ruu zips (which don't have the mid/cid requirements) after running fastboot oem rebootRUU as well as the standard exe RUUs, and if your s-on you can only run exe RUUs.
Hey, guys. I've finally made an account here after clumsily stepping into the world of custom ROMs. I recently got a Zara_CL on Virgin mobile and somehow wound up in the same position as the OP here. I never updated to KitKat due to the update failing with a custom recovery image. After unlocking the bootloader, I installed TWRP 2.7.1.1 and tried to flash InstertCoin yesterday without making a backup (couldn't mount certain partitions and now I know why ^_^). It took many hours to figure out what I did wrong and to make many plans of action to fix those mistakes.
I have re-locked my bootloader and the RUU has allowed me to get the stock Jellybean ROM back on my phone. I tried before while still unlocked and the RUU made no progress at all.
From what I've experienced, S-OFF and Unlocked are sort of interchangeable on a device in this stage of being cracked. One can flash recoveries with S-OFF and a locked loader, or with S-ON and an unlocked loader. I'm still learning after a few months and a successful root, s-off, and rom flash on an ancient EVO 3D. The high of that success drove me to buy this phone and try some magic on it, but my conjuration skills are quite unpolished.
To OP: Relock your bootloader with fastboot command "oem lock" and then run the RUU you found here. This should resurrect your handset flawlessly as it did in my situation. Don't punish your son, but teach him to be more careful. We both learned the hard way, but I guess I learned more quickly.
I had to always lock bootloader before running ruu. Would always get same error otherwise. This was for s-on. I can't remember my one experience running ruu while s-off.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Hedied4me said:
I had to always lock bootloader before running ruu. Would always get same error otherwise. This was for s-on. I can't remember my one experience running ruu while s-off.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Click to expand...
Click to collapse
How to lock bootloader? I only know how to unlock.
Get into boot loader and type "oem lock" into adb/command prompt.
attrunner said:
How to lock bootloader? I only know how to unlock.
Click to expand...
Click to collapse
You're phone needs to be in fastboot mode.
You need adb on your computer and to run a command prompt from your adb folder. Plug your phone into the computer and from the command prompt type "fastboot oem lock" and press enter. You're bootloader will now be locked. If you get a message about too many flags or something and a security warning afterwards, don't worry, it worked.
Ok I unlocked my loader, then i think what happend was clockwerk installed its self to the boot partition so i was stuck in a loop. I used One_M8_All-In-One_Kit_v to flash a new recovery lower version at that and now i do have a bootable recovery. Problem is now i didn't backup like a dumb arse my working OS and flashed a bad one or maybe the radio or some crap needed to be done first since it was going from 4.4.2 to 5+. In short all i have is recovery and sideload and every rom i download fails to sideload on the phone side and says sucessful on the pc cmd window. Need help with this please
Darthdiddy said:
Ok I unlocked my loader, then i think what happend was clockwerk installed its self to the boot partition so i was stuck in a loop. I used One_M8_All-In-One_Kit_v to flash a new recovery lower version at that and now i do have a bootable recovery. Problem is now i didn't backup like a dumb arse my working OS and flashed a bad one or maybe the radio or some crap needed to be done first since it was going from 4.4.2 to 5+. In short all i have is recovery and sideload and every rom i download fails to sideload on the phone side and says sucessful on the pc cmd window. Need help with this please
Click to expand...
Click to collapse
Wipe data, cache, dalvik, put the appropriate ROM for your carrier/build on SD card or root of internal storage and flash. All else fails run an RUU, bring you back to 100% stock then you can properly reinstall the custom recovery of your choice.
CavyS said:
Wipe data, cache, dalvik, put the appropriate ROM for your carrier/build on SD card or root of internal storage and flash. All else fails run an RUU, bring you back to 100% stock then you can properly reinstall the custom recovery of your choice.
Click to expand...
Click to collapse
I do the proper wipe before flashing my new rom, i'm under the AT&T HTC One M8 section i believe my phone was only @ 4.4.2 before this and here is the bootloader info is :
***Tampered***
***Unlocked***
M8_UL_CA_ PVT SHIP S-On
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 18 2014,16:06:33.22985
Tried cm-12-20150131-NIGHTLY-m8 it fails to flash and its on the sd and internal. SkyDragon M8 Sense Rom installs but doesn't boot (tried 2 versions of this rom 700mb and a 1.6gb), believe i tried a couple other roms in my phones section there's only like 9 of them there. I have the stock RUU but fails to detect the phone and fails i think it's meant to sense a turned on functional phone i don't see any kind of recovery method with the stock ruu. All i want is a rom to work with Straight talk the stock os even being unlocked and rooted with su still shoved the default APN down my throat(I even paid 2.99$ for the SQLlite and deleted all other APNs still won't let me check off a APN profile i created as default) making my signal on ST flakey and couldn't get mms to work just picture txting wasn't working. So i went full on like my old HTC One X but dived head first too fast didn't backup my old OS and didn't know firewater was gone till i was at that step of the procedure and it was too late Oh and using TWRP 2.7.1.0 it's the highest i can use before it won't boot.
Darthdiddy said:
I do the proper wipe before flashing my new rom, i'm under the AT&T HTC One M8 section i believe my phone was only @ 4.4.2 before this and here is the bootloader info is :
***Tampered***
***Unlocked***
M8_UL_CA_ PVT SHIP S-On
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 18 2014,16:06:33.22985
Tried cm-12-20150131-NIGHTLY-m8 it fails to flash and its on the sd and internal. SkyDragon M8 Sense Rom installs but doesn't boot (tried 2 versions of this rom 700mb and a 1.6gb), believe i tried a couple other roms in my phones section there's only like 9 of them there. I have the stock RUU but fails to detect the phone and fails i think it's meant to sense a turned on functional phone i don't see any kind of recovery method with the stock ruu. All i want is a rom to work with Straight talk the stock os even being unlocked and rooted with su still shoved the default APN down my throat(I even paid 2.99$ for the SQLlite and deleted all other APNs still won't let me check off a APN profile i created as default) making my signal on ST flakey and couldn't get mms to work just picture txting wasn't working. So i went full on like my old HTC One X but dived head first too fast didn't backup my old OS and didn't know firewater was gone till i was at that step of the procedure and it was too late Oh and using TWRP 2.7.1.0 it's the highest i can use before it won't boot.
Click to expand...
Click to collapse
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
CavyS said:
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
Click to expand...
Click to collapse
Ok TY i'll try that soon as it downloads, i did finally get RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2
To see the phone and no progress bar shows up on the phone and the program errors out, i even did a full system wipe before i tried it again still to no avail.
CavyS said:
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
Click to expand...
Click to collapse
Ok tried that stock ruu and it failed i did finally get the phone running on a badseed rom based on 4.4.2 all seems to be working now except i can't send pictures in texts but regular text, calls, and internet work seems to be a common problem with straight talk. So new problem probably a thread somewhere on here about it i'll take a look, thank you for the help
Darthdiddy said:
Ok tried that stock ruu and it failed i did finally get the phone running on a badseed rom based on 4.4.2 all seems to be working now except i can't send pictures in texts but regular text, calls, and internet work seems to be a common problem with straight talk. So new problem probably a thread somewhere on here about it i'll take a look, thank you for the help
Click to expand...
Click to collapse
You'll have to setup your APN and mms message size settings for straight talk, that should fix the text messaging problems.
CavyS said:
You'll have to setup your APN and mms message size settings for straight talk, that should fix the text messaging problems.
Click to expand...
Click to collapse
No matter what message app i try i can't send pictures or large txts my mms is borked and to make matters worse when i installed this rom i must of removed the stock HTC messaging app so i can't find any settings to set the mms size limits. I'd like to figure out how to put the stock messaging app back on the phone without redoing the whole OS
Using Handcent and hangouts and i see no size limit options within the apps or anywhere in the phone settings. Looked up my phone specifically and where the option/s is supposed to be the said section of options is not even there.
If you've got a stock rom downloaded to your computer or sd card you can unzip it and look in system app folder and find the htc messaging apks. Then just install them as system apps and fix permissions.
Sent from my HTC One_M8 using XDA Free mobile app
Before i try and fix my obvious other problems does anyone know how to fix a bad flash of TWRP? I'm used to just adb command line flashing it and never had a issue before on my HTC One X, but seems it a was bad idea and it landed on boot partition and is causing glitches. is there a stock boot i can flash or what do i need?
Darthdiddy said:
but seems it a was bad idea and it landed on boot partition and is causing glitches.?
Click to expand...
Click to collapse
Why do you think that partition, in particular? If you are talking about boot.img, that gets re-flashed any time your flash a ROM.
Try fastboot erase cache, and flash recovery by fastboot. If Clockwork doesn't work, try TWRP.
If you indeed have some corrupted partition(s), your best bet is to RUU. You are non-specific about what error codes, so its hard to help you troubleshoot why the RUU failed. Try a more updated RUU, such as 2.23.
redpoint73 said:
Why do you think that partition, in particular? If you are talking about boot.img, that gets re-flashed any time your flash a ROM.
Try fastboot erase cache, and flash recovery by fastboot. If Clockwork doesn't work, try TWRP.
If you indeed have some corrupted partition(s), your best bet is to RUU. You are non-specific about what error codes, so its hard to help you troubleshoot why the RUU failed. Try a more updated RUU, such as 2.23.
Click to expand...
Click to collapse
Error 155 Unknown Error it says, do i need to relock the bootloader? I could never find a way to S-Off the device so idk if its that or corrupted partition like you said but all my services on my phone crash constantly. But that's better then aokp_task650_m8_kitkat_5.13.2014 that one won't even make it through setup the services crash so often the badseed rom is the only other rom i found that is actually usable. Oh my RUU is 2.0.16 how can i find the newest one for my HTC One M8?
Darthdiddy said:
Error 155 Unknown Error it says, do i need to relock the bootloader?
Oh my RUU is 2.0.16 how can i find the newest one for my HTC One M8?
Click to expand...
Click to collapse
You always need to relock the bootloader to run RUU with s-on. No exceptions.
Hopefully this will clear up your RUU problem, although the RUU number you just supplied above doesn't make any sense (doesn't correspond to any RUU for this device) Where did you find it, and its not what you referenced in Post #5 above.
CavyS already supplied a link for the "latest" AT&T RUU in Post #4 above. Although be aware, that if you are successful in running the latest RUU, it will render sunshine unable to achieve s-off. I suggest RUU to 1.58 or 2.23 (if you want s-off), as those should still be supported by sunshine.
Darthdiddy said:
I could never find a way to S-Off the device
Click to expand...
Click to collapse
Did you try sunshine? Its the only way to s-off at this time.
redpoint73 said:
You always need to relock the bootloader to run RUU with s-on. No exceptions.
Hopefully this will clear up your RUU problem, although the RUU number you just supplied above doesn't make any sense (doesn't correspond to any RUU for this device) Where did you find it, and its not what you referenced in Post #5 above.
CavyS already supplied a link for the "latest" AT&T RUU in Post #4 above. Although be aware, that if you are successful in running the latest RUU, it will render sunshine unable to achieve s-off. I suggest RUU to 1.58 or 2.23 (if you want s-off), as those should still be supported by sunshine.
Did you try sunshine? Its the only way to s-off at this time.
Click to expand...
Click to collapse
Relocked and flashed the ruu utility version said 2.0.16.2014 and is KK 4.4, idk about sunshine as to reading about people with my phone and it not working so for a 25$ leap of faith not sure what to do about that. My phone is running perfect now in a locked down carrier branded and bloatware way lol. Thanks guys, anyway i can tell if sunshine will work on my phone?
Darthdiddy said:
Relocked and flashed the ruu utility version said 2.0.16.2014 and is KK 4.4
Click to expand...
Click to collapse
I think that is the version of the actual installer software (.exe) not the ROM version it will install on your phone. Kitkat for AT&T would be either 1.58 or 2.23. That number will be in the actual file name of the RUU, so just look there (actually a much longer string of numbers starting with 1.58 or 2.23, but I've abbreviated them for convenience).
Darthdiddy said:
idk about sunshine as to reading about people with my phone and it not working so for a 25$ leap of faith not sure what to do about that. My phone is running perfect now in a locked down carrier branded and bloatware way lol. Thanks guys, anyway i can tell if sunshine will work on my phone?
Click to expand...
Click to collapse
You install the sunshine APK, run it, and sunshine will tell you whether it can s-off the phone or not. You won't be charged unless it can successfully s-off the phone. I haven't heard of any folks here that got charged, and sunshine couldn't s-off the device.
redpoint73 said:
I think that is the version of the actual installer software (.exe) not the ROM version it will install on your phone. Kitkat for AT&T would be either 1.58 or 2.23. That number will be in the actual file name of the RUU, so just look there (actually a much longer string of numbers starting with 1.58 or 2.23, but I've abbreviated them for convenience).
You install the sunshine APK, run it, and sunshine will tell you whether it can s-off the phone or not. You won't be charged unless it can successfully s-off the phone. I haven't heard of any folks here that got charged, and sunshine couldn't s-off the device.
Click to expand...
Click to collapse
Wow thanks for the info! Before i try this can after S-OFF/rooting/SU can i install the unlocked/developer ruu from HTC and get HTC OTA and get away from this bloated carrier branded crap? So much in the forums and i can't find a answer to this question anywhere.