Do I just switch back the CID, and install the OTA normally (after relocking ofc?) What order would I need to do it in?
Id like to have a back up of the stock WIND ICS for warranty purposes
rbaruch said:
Do I just switch back the CID, and install the OTA normally (after relocking ofc?) What order would I need to do it in?
Id like to have a back up of the stock WIND ICS for warranty purposes
Click to expand...
Click to collapse
Are you super cid? If so, nope, you'll have to install the wind GB ROM via fastboot since it's an exe file, then update via the ota file using the ota file method in the bible, if you get a cid error, there's a note at the bottom to fix it.
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
Are you super cid? If so, nope, you'll have to install the wind GB ROM via fastboot since it's an exe file, then update via the ota file using the ota file method in the bible, if you get a cid error, there's a note at the bottom to fix it.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
Yes I switched CID to Tmo's to install the ICS OTA they leaked a while ago. I'm on NRGZ ICS release right now
rbaruch said:
Yes I switched CID to Tmo's to install the ICS OTA they leaked a while ago. I'm on NRGZ ICS release right now
Click to expand...
Click to collapse
Just super cid instead of changing to one specific carrier's cid, saves you having to change it. You'll have to be on wind GB to use the OTA file though. So downgrade then upgrade back to wind ICS.
Dark Nightmare said:
Just super cid instead of changing to one specific carrier's cid, saves you having to change it. You'll have to be on wind GB to use the OTA file though. So downgrade then upgrade back to wind ICS.
Click to expand...
Click to collapse
even with a custom eng hboot? last time I asked this a while ago if I could downgrade to GB and they said Id risk bricking my phone
rbaruch said:
even with a custom eng hboot? last time I asked this a while ago if I could downgrade to GB and they said Id risk bricking my phone
Click to expand...
Click to collapse
Once you're s-off, you can upgrade and downgrade as you please, I've done it multiple times, how do you think I'm on Telus stock ICS when I have a T-Mobile device? You just have to be s-off with an unlocked bootloader, s-on will brick your device, s-off opens up the device completely mounting everything as rewritable, just don't flash a ruu from another device other than the stock amaze ruus and don't flash from another carrier if you're not super cid. Simple as that.
Dark Nightmare said:
Once you're s-off, you can upgrade and downgrade as you please, I've done it multiple times, how do you think I'm on Telus stock ICS when I have a T-Mobile device? You just have to be s-off with an unlocked bootloader, s-on will brick your device, s-off opens up the device completely mounting everything as rewritable, just don't flash a ruu from another device other than the stock amaze ruus and don't flash from another carrier if you're not super cid. Simple as that.
Click to expand...
Click to collapse
I was on SUPERCID didn't realize. So flashing the WIND GB RUU wont change my hboot?
rbaruch said:
I was on SUPERCID didn't realize. So flashing the WIND GB RUU wont change my hboot?
Click to expand...
Click to collapse
Once you're super cid it shouldn't matter, but if it gives an error, just change it back. HBoot should remain the same, but some devices tend to let the ruu change them, but that shouldn't matter either.
Dark Nightmare said:
Once you're super cid it shouldn't matter, but if it gives an error, just change it back. HBoot should remain the same, but some devices tend to let the ruu change them, but that shouldn't matter either.
Click to expand...
Click to collapse
Sorry for the endless stream of questions, but what are chances of bricking my device while doing this?
rbaruch said:
Sorry for the endless stream of questions, but what are chances of bricking my device while doing this?
Click to expand...
Click to collapse
Nada, once you don't do something stupid like a battery pull while the exe file is restoring you to stock GB.
And don't worry about the questions, ask all you want.
Related
This thread is regarding RUU for HTC devices.
I've seen some similar threads but could not fully get the answer I was looking for.
From what I already understand, a RUU updates the ROM, the H-BOOT possibly and updates the recovery with a stock recovery. It cannot do anything that a BL-Unlocked user cannot do through adb or fastboot because the RUU uses only adb and fastboot. This means that the RUU does not (And cannot) update the radio. Am I correct in this?
And if so, what is the point of updating the RUU once you start flashing custom ROMs because they also flash the /system and /boot partitions and the only thing a custom ROM doesn't do is reflash the H-BOOT and the recovery.
And even if you update using a RUU for some reason (Whether it updates or if you just want to return to stock), do you have to choose the RUU that exactly matches your current radio version?
Assume for all the questions that the device is either BL-Unlocked or Stock (But S-ON either way).
Thanks in advance.
AceRoom said:
This thread is regarding RUU for HTC devices.
I've seen some similar threads but could not fully get the answer I was looking for.
From what I already understand, a RUU updates the ROM, the H-BOOT possibly and updates the recovery with a stock recovery. It cannot do anything that a BL-Unlocked user cannot do through adb or fastboot because the RUU uses only adb and fastboot. This means that the RUU does not (And cannot) update the radio. Am I correct in this?
And if so, what is the point of updating the RUU once you start flashing custom ROMs because they also flash the /system and /boot partitions and the only thing a custom ROM doesn't do is reflash the H-BOOT and the recovery.
And even if you update using a RUU for some reason (Whether it updates or if you just want to return to stock), do you have to choose the RUU that exactly matches your current radio version?
Assume for all the questions that the device is either BL-Unlocked or Stock (But S-ON either way).
Thanks in advance.
Click to expand...
Click to collapse
Hi, an ruu updates what you mentioned and a lot more. It will do things like change the splash screen, update the radio. and change the hboot which you cannot do with only an unlocked bootloader. It can do those things because its signed.
I had to use ruu's a few times, recently for an hboot downgrade to achieve s-off. Now that I have s-off I can flash any file I want in hboot asblong as its named correctly. Like a splash screen, or a lower hboot version.
Since an ruu updates the radio, it doesn't matter which version you choose, as long as its the same version you have or higher, but it won't let you flash a lower versionWith s-off I can flash any ruu version I want.
ok, so if I am currently running 2.3.4 and htc sense 3.0, does that mean that I can flash my phone with ics (4.0) as long as it is for the right phone and carrier???
HTC evo 3D with Rogers
icecursor said:
ok, so if I am currently running 2.3.4 and htc sense 3.0, does that mean that I can flash my phone with ics (4.0) as long as it is for the right phone and carrier???
HTC evo 3D with Rogers
Click to expand...
Click to collapse
Yes.
Theonew said:
Yes.
Click to expand...
Click to collapse
now, if I upgrade it through the ruu, is that the exact same upgrade that comes from the carrier? As in, even the HTC update too?
And if it is, is the ruu just the rooted phones way of updating?
Thanks
icecursor said:
now, if I upgrade it through the ruu, is that the exact same upgrade that comes from the carrier? As in, even the HTC update too?
And if it is, is the ruu just the rooted phones way of updating?
Thanks
Click to expand...
Click to collapse
Yes it is the same update. Updating with the RUU can be used either way (rooted or non-rooted). Just keep in mind that you'll lose root access after updating.
Theonew said:
Yes.
Click to expand...
Click to collapse
Theonew said:
Yes it is the same update. Updating with the RUU can be used either way (rooted or non-rooted). Just keep in mind that you'll lose root access after updating.
Click to expand...
Click to collapse
ok, so last question,
do I need hboot 1.5? I am currently running revolutionary s-off, HBOOT 1.49.1107.
Originally Posted by Theonew
Yes.
Click to expand...
Click to collapse
Originally Posted by Theonew
Yes it is the same update. Updating with the RUU can be used either way (rooted or non-rooted). Just keep in mind that you'll lose root access after updating.
Click to expand...
Click to collapse
ok, so last question,
do I need hboot 1.5? I am currently running revolutionary s-off, HBOOT 1.49.1107.
Click to expand...
Click to collapse
I'm not sure for your device, but as long as the RUU is for it, it should work (boot loader version doesn't usually affect it).
hello, i wanted to know if RUU also achieves S-ON. I need to return my droid incredible to verizon for replacement due to screen malfunction. I cannot see anything on the display, but everything inside works fine.
I had unlocked bootloader using htcdev and rooted with S-OFF running 4.1.1. I am now on stock Froyo thanks to RUU, but I still need to get S-ON and bootloader locked.
So does the RUU achieve S-ON? I have downloaded the forever SON zip file. But I dont know how to flash it using ADB. Can someone guide me.
haunteddevil619 said:
hello, i wanted to know if RUU also achieves S-ON. I need to return my droid incredible to verizon for replacement due to screen malfunction. I cannot see anything on the display, but everything inside works fine.
I had unlocked bootloader using htcdev and rooted with S-OFF running 4.1.1. I am now on stock Froyo thanks to RUU, but I still need to get S-ON and bootloader locked.
So does the RUU achieve S-ON? I have downloaded the forever SON zip file. But I dont know how to flash it using ADB. Can someone guide me.
Click to expand...
Click to collapse
The RUU does not return S-ON. What is in the zip file?
achieve S-ON on htc...
haunteddevil619 said:
hello, i wanted to know if RUU also achieves S-ON. I need to return my droid incredible to verizon for replacement due to screen malfunction. I cannot see anything on the display, but everything inside works fine.
I had unlocked bootloader using htcdev and rooted with S-OFF running 4.1.1. I am now on stock Froyo thanks to RUU, but I still need to get S-ON and bootloader locked.
So does the RUU achieve S-ON? I have downloaded the forever SON zip file. But I dont know how to flash it using ADB. Can someone guide me.
Click to expand...
Click to collapse
for S-ON try this Post ...
I have started searching and am having a hard time finding exactly what I need. Anyway, I haven't used my Rezound since I got my S3 so I am not really up to speed on where the Rezound is in terms of OTA updates and whatnot. Right now my Rezound is S-Off on a engineering hboot (I believe) and rooted, but it was stock otherwise (up until I stopped using it).
I would like to get it back to 100% stock (other than S-Off, I will leave that as is for now). What is the easiest way to get there? I am assuming flashing an RUU of the latest stock build? If so, what is the latest stock build that I would get if I re-activated the phone and updated it (meaning I don't want any leaks or anything).
Also, it has been so long since I did any flashing on the phone, but what is the easiest way to flash a RUU (since I have never done that). And can I just flash the latest RUU without flashing anything else first?
Thanks, and sorry for all of the noob questions.
xceebeex said:
I have started searching and am having a hard time finding exactly what I need. Anyway, I haven't used my Rezound since I got my S3 so I am not really up to speed on where the Rezound is in terms of OTA updates and whatnot. Right now my Rezound is S-Off on a engineering hboot (I believe) and rooted, but it was stock otherwise (up until I stopped using it).
I would like to get it back to 100% stock (other than S-Off, I will leave that as is for now). What is the easiest way to get there? I am assuming flashing an RUU of the latest stock build? If so, what is the latest stock build that I would get if I re-activated the phone and updated it (meaning I don't want any leaks or anything).
Also, it has been so long since I did any flashing on the phone, but what is the easiest way to flash a RUU (since I have never done that). And can I just flash the latest RUU without flashing anything else first?
Thanks, and sorry for all of the noob questions.
Click to expand...
Click to collapse
Find the lastest RUU. I know its on android police. Place the file on the root of your SD card, check md5, rename to ph98img.zip, boot into bootloader and let it do its thing. You should be up to date.
EDIT: for you http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
topgun1953 said:
Find the lastest RUU. I know its on android police. Place the file on the root of your SD card, check md5, rename to ph98img.zip, boot into bootloader and let it do its thing. You should be up to date.
Click to expand...
Click to collapse
Thanks! Yea, I just found it on android police. I am assuming it won't wipe the SD card or anything right? Since I am S-OFF I don't have to worry about re-locking correct?
Also, will that RUU get it back to the point where someone could get the OTA's and everything as if it was 100% stock with S-ON?
EDIT: How come that 4.03.605.2 isn't listed on HTC website yet? Has it not been pushed out yet? The one listed on their site is the 3.14.605.12
xceebeex said:
EDIT: How come that 4.03.605.2 isn't listed on HTC website yet? Has it not been pushed out yet? The one listed on their site is the 3.14.605.12
Click to expand...
Click to collapse
4.03.605.2 is the latest leak. it has changes to make the rezound a Verizon global phone.
3.14.605.12 is the last nationwide OTA official ICS.
HowardZ said:
4.03.605.2 is the latest leak. it has changes to make the rezound a Verizon global phone.
3.14.605.12 is the last nationwide OTA official ICS.
Click to expand...
Click to collapse
Ok thanks! So I think I want to stick with the 3.14.605.12 then since I am trying to sell the phone. So if I am Unlocked and S-OFF can I just flash the RUU or do I have to relock first? And do I need to flash the gingerbread firmware patch?
s-off and unlocked is fine to ruu.
---------- Post added at 10:30 AM ---------- Previous post was at 10:28 AM ----------
s-off and unlocked is fine to ruu.
no patch needed
HowardZ said:
s-off and unlocked is fine to ruu.
Click to expand...
Click to collapse
Awesome, thanks! It won't wipe the SD card I am assuming right? Just the phone?
xceebeex said:
Awesome, thanks! It won't wipe the SD card I am assuming right? Just the phone?
Click to expand...
Click to collapse
my experience is it wipes the internal sd, but left the removable microSD card untouched.
HowardZ said:
my experience is it wipes the internal sd, but left the removable microSD card untouched.
Click to expand...
Click to collapse
Ok cool. That is what I would assume would happen. The only other question is if I need the GB firmware patch as well or does the RUU take care of everything?
Thanks for your help!
It takes care of everything
Sent from my ADR6425LVW using Tapatalk 2
mjones73 said:
It takes care of everything
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Thanks everyone!
EDIT: Will it also stay "Locked" and S-OFF?
xceebeex said:
Thanks everyone!
EDIT: Will it also stay "Locked" and S-OFF?
Click to expand...
Click to collapse
Yes , running the RUU will not effect s-off status nor your bootloader locked status.
not to hijack the thread....but I have a question that relates to getting back to stock. I am running business sense, with the OTA. I would like to get the other global OTA.. I am s on. How do I go about doing that?
flash stock recovery
relock
run which RUU? the newest one is a PH file on android police
unlock
flash amon ra
flash new rom
does that sound right?
the part that I am questioning is the fact the global RUU is a PH file. But it says I have to be completly back to stock and locked.
any help would be greatly appreciated
Thanks
putney1477 said:
not to hijack the thread....but I have a question that relates to getting back to stock. I am running business sense, with the OTA. I would like to get the other global OTA.. I am s on. How do I go about doing that?
flash stock recovery
relock
run which RUU? the newest one is a PH file on android police
unlock
flash amon ra
flash new rom
does that sound right?
the part that I am questioning is the fact the global RUU is a PH file. But it says I have to be completly back to stock and locked.
any help would be greatly appreciated
Thanks
Click to expand...
Click to collapse
I not sure about s on but I think you have to stock recovery and locke the hboot then runn the ruu on hboot
This is the latest one
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Why don't you s off before updating?
Kratz17 said:
I not sure about s on but I think you have to stock recovery and locke the hboot then runn the ruu on hboot
This is the latest one
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Why don't you s off before updating?
Click to expand...
Click to collapse
I tried to get s off a few months ago.....I could not get it to work. the 2 doff Hboot things scared me.
I would really like to do it. But I need my phone for work, I am on call most nights. I am looking into getting a used smartphone just so that I can use that while trying to get s off.
thanks
putney1477 said:
I tried to get s off a few months ago.....I could not get it to work. the 2 doff Hboot things scared me.
I would really like to do it. But I need my phone for work, I am on call most nights. I am looking into getting a used smartphone just so that I can use that while trying to get s off.
thanks
Click to expand...
Click to collapse
Ok I understand but whenever you decide to do it follow this guide its pretty easy.
http://forum.xda-developers.com/showthread.php?t=1696394
It says to be on a certain firmware but I have heard from other users that it's works with any ics firmware. Good Luck
putney1477 said:
I tried to get s off a few months ago.....I could not get it to work. the 2 doff Hboot things scared me.
I would really like to do it. But I need my phone for work, I am on call most nights. I am looking into getting a used smartphone just so that I can use that while trying to get s off.
thanks
Click to expand...
Click to collapse
I did s-off procedure a few months ago. it took several hours and kept failing. I used a large insulated paperclip with the insulating material removed from each end for good electrical contact.
What I had been doing wrong was not keeping the wire nice and straight in the hole. when the wire is not straight, it will not make good electrical contact with whatever is directly beneath the hole.
I just thought I'd share this tip in case it helps others.
regards,
Howard
p.s. There is no need to install the jbear modified hboot if you are uncomfortably with it. Installing the modified hboot is optional at the end of the s-off procedure. You will still have benefits of s-off with a htcdev unlocked bootloader while using a stock unlocked hboot. For example one can flash kernels via fastboot flash command with a stock hboot. s-off and jbear modified hboot are two separate modifications to the phone.
HowardZ said:
p.s. There is no need to install the jbear modified hboot if you are uncomfortably with it. Installing the modified hboot is optional at the end of the s-off procedure. You will still have benefits of s-off with a htcdev unlocked bootloader while using a stock unlocked hboot. For example one can flash kernels via fastboot flash command with a stock hboot. s-off and jbear modified hboot are two separate modifications to the phone.
Click to expand...
Click to collapse
actually, on a stock, locked HBoot, you CAN'T use any fastboot commands. That's why it's highly recommended to install the JBear HBoot, plus it gives you an easy option to do it and it does it without the user having to do anything
I successfully installed Fresh Evo LTE 5.3.1 on my phone.
One of the suggestions is to update the Radio but I'm having a tough time doing that.
Here are my specs:
HBOOT 1.15.0000
S-ON
FreshEVO 5.3.1 ROM
I went to the link from the FreshEVO LTE 5.3.1 page to update the radio and have tried the following to install the Radio:
Attempt 1
Downloaded the Full Firmware zip file
Rename it "PJ75IMG"
Place it in the root of my SD card
Reboot into Bootloader
The PJ75IMG.zip file is detect but I only get 'Parsing PJ75IMG.zip' and then the Fastboot, Recovery, etc. options are displayed.
Attempt 2
From the same page where I downloaded the Full Firmware zip file, I also tried:
Download the Boot.img Only (signed) file
Flash it through the command prompt while in Fastboot ("fastboot flash boot boot.img")
Go into Bootloader
The PJ75IMG.zip is detected but still get the "Parsing..." message and nothing else happens.
Attempt 3
I have also tried going into my TWRP recovery and installing the Full Firmware zip AND the Radio 1.12.11.0809 Only.zip file but the installation fails.
Any pointers or a link to a video or a post would be much appreciated.
Thanks and sorry if this is a duplicate post but I really couldn't find any post that showed step-by-step process.
revert to stock and accept the ota, you can then fastboot recovery again and reflash. hboot 1.15 can not directly flash any firmware
edit: you may have to relock your hboot but ive seen users state they didnt. if you decide to relock the phone you will have to unlock the bootloader again to enable fastboot
om4 said:
The easiest way to update your firmware is to revert to stock and accept the ota, you can then fastboot recovery again and reflash
Click to expand...
Click to collapse
I don't have my stock backup anymore.
I've heard stuff about using RUU or something like that. Any quick guide on how to revert back to stock?
DO NOT UNROOT TO ACCEPT THE OTA OR RUU
I'd highly suggest just staying with your current radios and waiting for S-OFF before trying to update the radios. You can still flash the new ROMS in the meantime
You cannot update radios or firmware with Hboot 1.15 or 1.19------->Thats why it is suggested and not required
Rxpert said:
DO NOT UNROOT TO ACCEPT THE OTA OR RUU
I'd highly suggest just staying with your current radios and waiting for S-OFF before trying to update the radios. You can still flash the new ROMS in the meantime
You cannot update radios or firmware with Hboot 1.15 or 1.19------->Thats why it is suggested and not required
Click to expand...
Click to collapse
Thanks for the warning.
Since I'm pretty new to all this, I'll play it safe and stick to what I have.
sorry guys internet crapped out and i got stuck trying to post lol. rxpert has a point but with so much negativity about s-off never coming I'm starting to consider taking the OTA.
also you should always have a back up, its your go to solution when nothing else seems to be working since its a back up of when everything was new and working be it stock or custom
The new radios aren't worth losing the possibility, no matter how small
Sent from my EVO using Tapatalk 2
True...
om4 said:
sorry guys internet crapped out and i got stuck trying to post lol. rxpert has a point but with so much negativity about s-off never coming I'm starting to consider taking the OTA.
also you should always have a back up, its your go to solution when nothing else seems to be working since its a back up of when everything was new and working be it stock or custom
Click to expand...
Click to collapse
Just so I am clear, I too am 1.5 so if have my orginal rom, (the one after I unlocked my bootloader) i can restore it and accept the OTA without having to relock my phone? (it wont brick):good: Or do i have some other steps to take, I read the don't panic instructions, but it only mentioned what the OTA does ( relocks with a new rom) but nothing about what happens if I don't relock before I accept the OTA, I know i seem a bit slow, 4g lte isn't as interesting as OG 4g without S-off.
RamesisX said:
Just so I am clear, I too am 1.5 so if have my orginal rom, (the one after I unlocked my bootloader) i can restore it and accept the OTA without having to relock my phone? (it wont brick):good: Or do i have some other steps to take, I read the don't panic instructions, but it only mentioned what the OTA does ( relocks with a new rom) but nothing about what happens if I don't relock before I accept the OTA, I know i seem a bit slow, 4g lte isn't as interesting as OG 4g without S-off.
Click to expand...
Click to collapse
I havent yet done it myself but users have said they didnt need to relock, how ever as captain said there is no real need to update right now. If you decide to go ahead it would be a good idea to relock ( fastboot oem lock ) just to make sure, you can unlock afterwards. I neglect to mention this in my guide because most phones now are on 1.19 anyway and those still on 1.15 are holding out for soff
You will want to have the stock recovery to take the ota. Most people do this by relocking and running the ruu
Once again, I'm providing the info but I don't recommend it
Sent from my EVO using Tapatalk 2
Rxpert said:
You will want to have the stock recovery to take the ota. Most people do this by relocking and running the ruu
Once again, I'm providing the info but I don't recommend it
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I am still researching how to relock without issues. I have my orginal rom but still leary about the entire relocking process. I was hoping i could restore to orginal sense rom, then take the OTA. otherwise I am looking for the simplest way to accompish the relocking task, but frankly nothing is easy when i comes to playing around with 4g lte, except it is rather difficult to brick. With my luck i might succeed in that LMAO
:good::laugh:
RamesisX said:
I am still researching how to relock without issues. I have my orginal rom but still leary about the entire relocking process. I was hoping i could restore to orginal sense rom, then take the OTA. otherwise I am looking for the simplest way to accompish the relocking task, but frankly nothing is easy when i comes to playing around with 4g lte, except it is rather difficult to brick. With my luck i might succeed in that LMAO
:good::laugh:
Click to expand...
Click to collapse
there is no simpler method for relocking hboot, simply fastboot oem lock
om4 said:
there is no simpler method for relocking hboot, simply fastboot oem lock
Click to expand...
Click to collapse
Used that and it worked great.
Evo 4G LTE
h-boot 1.19, s-on, HTCDev unlocked
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
Just my luck that Verizon puts this new OTA out the day before I was going to root this thing! It looks to me like we have no option now to root these updated devices. Anyone have any ideas?
therreid said:
Just my luck that Verizon puts this new OTA out the day before I was going to root this thing! It looks to me like we have no option now to root these updated devices. Anyone have any ideas?
Click to expand...
Click to collapse
You either need to wait, or try search how to revert the update.
dafuzzbudd said:
You either need to wait, or try search how to revert the update.
Click to expand...
Click to collapse
I tried to wipe/factory reset then install stock 2.17.605.2 RUU last night from .exe file. Wouldn't let it load due to updated bootloader. I also tried flashing unlock_code.bin from previous unlock experience with Hasoon2000's toolkit without luck as well as running through mdmower's unlock script with attempt to change CID. Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. I'm guessing I probably need root to modify bootloader to revert to old to unlock it... so probably just screwed until someone smarter figures out a way to unlock the new bootloader...
dkkunkel said:
Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. ..
Click to expand...
Click to collapse
Did you make sure your copy and paste to HTC was correct? That was my problem a couple of weeks ago. A single <space> was the culprit for me.
pmcall said:
Did you make sure your copy and paste to HTC was correct? That was my problem a couple of weeks ago. A single <space> was the culprit for me.
Click to expand...
Click to collapse
Yes, it was correct; just like other successful times... Did yours unlock after the latest OTA or was it prior to the update?
dkkunkel said:
I tried to wipe/factory reset then install stock 2.17.605.2 RUU last night from .exe file. Wouldn't let it load due to updated bootloader. I also tried flashing unlock_code.bin from previous unlock experience with Hasoon2000's toolkit without luck as well as running through mdmower's unlock script with attempt to change CID. Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. I'm guessing I probably need root to modify bootloader to revert to old to unlock it... so probably just screwed until someone smarter figures out a way to unlock the new bootloader...
Click to expand...
Click to collapse
Were you rooted with s-off, or s-on?
dkkunkel said:
I tried to wipe/factory reset then install stock 2.17.605.2 RUU last night from .exe file. Wouldn't let it load due to updated bootloader. I also tried flashing unlock_code.bin from previous unlock experience with Hasoon2000's toolkit without luck as well as running through mdmower's unlock script with attempt to change CID. Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. I'm guessing I probably need root to modify bootloader to revert to old to unlock it... so probably just screwed until someone smarter figures out a way to unlock the new bootloader...
Click to expand...
Click to collapse
dkkunkel said:
Yes, it was correct; just like other successful times... Did yours unlock after the latest OTA or was it prior to the update?
Click to expand...
Click to collapse
Prior to update coming out, I have not installed the OTA.
junkmail9 said:
Were you rooted with s-off, or s-on?
Click to expand...
Click to collapse
Rooted, s-on. had avatar nightly installed//had issues with no data service and eventually re-loaded stock RUU with hopes to find a fix (after wiping, clean install, flash/re-flash firmware multiple times) and put avatar back on.... but then the OTA hit and here I am... unable to unlock bootloader.
dkkunkel said:
Rooted, s-on. had avatar nightly installed//had issues with no data service and eventually re-loaded stock RUU with hopes to find a fix (after wiping, clean install, flash/re-flash firmware multiple times) and put avatar back on.... but then the OTA hit and here I am... unable to unlock bootloader.
Click to expand...
Click to collapse
Hopefully you at least have data service now. Unless you can manage SuperCID, you might be out of luck for a while. I hope I'm wrong about that.
I am now curious if anyone who is s-off installed the OTA (either accidentally or intentionally) and retained s-off. In theory, if you're s-off you can recover from nearly anything. (I will admit that I have absolutely no desire to try it for myself)
junkmail9 said:
Hopefully you at least have data service now. Unless you can manage SuperCID, you might be out of luck for a while. I hope I'm wrong about that.
I am now curious if anyone who is s-off installed the OTA (either accidentally or intentionally) and retained s-off. In theory, if you're s-off you can recover from nearly anything. (I will admit that I have absolutely no desire to try it for myself)
Click to expand...
Click to collapse
How were you able to get the CID to change? I followed the CID change script manually using temp-root and DD commands through shell with a hex editor and it would NOT change the CID although I was given no errors. Crazy.
stevey500 said:
How were you able to get the CID to change? I followed the CID change script manually using temp-root and DD commands through shell with a hex editor and it would NOT change the CID although I was given no errors. Crazy.
Click to expand...
Click to collapse
I used DirtyRacun back on the 2nd OTA to obtain s-off, and DirtyRacun does not require the SuperCID method. I have not done anything with the latest OTA, as it isn't worth the risk to me... I somehow doubt that the DirtyRacun will work with the latest OTA, but I do not recall seeing anyone post that they have tried it, either.
junkmail9 said:
I used DirtyRacun back on the 2nd OTA to obtain s-off, and DirtyRacun does not require the SuperCID method. I have not done anything with the latest OTA, as it isn't worth the risk to me... I somehow doubt that the DirtyRacun will work with the latest OTA, but I do not recall seeing anyone post that they have tried it, either.
Click to expand...
Click to collapse
Ah... I'll go ahead and give it a try. This phone bone-stock is nearly unbearably slow. HTC bloating the hell out of these phone and then locking the bootloaders is a sad marketing scheme.
stevey500 said:
Ah... I'll go ahead and give it a try. This phone bone-stock is nearly unbearably slow. HTC bloating the hell out of these phone and then locking the bootloaders is a sad marketing scheme.
Click to expand...
Click to collapse
Anyone figure out if this works?? DirtyRacun after OTA I mean. thanks
join in for the unbelievable ... post2014-OTA [S-OFF] has been achieved
http://forum.xda-developers.com/showthread.php?t=2664460