The recovery is broken, and the rom doesn't boot.
I can enter the recovery, but as soon as I try to wipe data or install a rom, it reboots. I tried "fastboot erase cache", I tried reflashing CWM and TWRP, and I tried ADB Sideload on both, same results.
The only way for me is to run RUU, but the problem is, any RUU that I try says "The ROM Update Utility Cannot update you Android phone. Please get the correct ROM Update Utility and try again.
I am s-off and supercid on hboot 1.55, with the 3.57 firmware. Any ideas on how to get the RUU working? Thanks!
Shu. said:
The recovery is broken, and the rom doesn't boot.
I can enter the recovery, but as soon as I try to wipe data or install a rom, it reboots. I tried "fastboot erase cache", I tried reflashing CWM and TWRP, and I tried ADB Sideload on both, same results.
The only way for me is to run RUU, but the problem is, any RUU that I try says "The ROM Update Utility Cannot update you Android phone. Please get the correct ROM Update Utility and try again.
I am s-off and supercid on hboot 1.55, with the 3.57 firmware. Any ideas on how to get the RUU working? Thanks!
Click to expand...
Click to collapse
which RUU are using? you probably have to change CID to SuperCID.
also read through this about recovery problems: http://forum.xda-developers.com/showthread.php?t=2494111
EDIT: also for RUU to work, I believe you need to be locked or relocked.
nkk71 said:
which RUU are using? you probably have to change CID to SuperCID.
also read through this about recovery problems: http://forum.xda-developers.com/showthread.php?t=2494111
EDIT: also for RUU to work, I believe you need to be locked or relocked.
Click to expand...
Click to collapse
Okay, then that seems to be the issue, i'll try to relock, thanks!
Shu. said:
Okay, then that seems to be the issue, i'll try to relock, thanks!
Click to expand...
Click to collapse
DO NOT GO S-ON !!
and check CID if it's compatible with the RUU, otherwise change to SuperCID.
nkk71 said:
DO NOT GO S-ON !!
and check CID if it's compatible with the RUU, otherwise change to SuperCID.
Click to expand...
Click to collapse
I am already super CID, so I think the only issue is with the unlocked boot loader. I'm gonna try to re-lock it now. And thanks again for the warning, I won't go s-on
If you have S-off you don't have to lock your bootloader to run a ruu.
Shu. said:
I am already super CID, so I think the only issue is with the unlocked boot loader. I'm gonna try to re-lock it now. And thanks again for the warning, I won't go s-on
Click to expand...
Click to collapse
No problem :good:
Post back with your results so we know
maxal said:
If you have S-off you don't have to lock your bootloader to run a ruu.
Click to expand...
Click to collapse
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
maxal said:
If you have S-off you don't have to lock your bootloader to run a ruu.
Click to expand...
Click to collapse
EddyOS said:
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
Click to expand...
Click to collapse
If that is the case, could the newer version of the hboot cause the issue? because I'm trying to flash an old RUU. I tried the hTC_Asia_WWE_1.29.707.3, which is for my region, as well as US_WWE_1.29.1540.16 (developer edition) as I'm supercid. both failed
maxal said:
If you have S-off you don't have to lock your bootloader to run a ruu.
Click to expand...
Click to collapse
EddyOS said:
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
Click to expand...
Click to collapse
I stand corrected
---------- Post added at 05:11 PM ---------- Previous post was at 05:09 PM ----------
Shu. said:
If that is the case, could the newer version of the hboot cause the issue? because I'm trying to flash an old RUU. I tried the hTC_Asia_WWE_1.29.707.3, which is for my region, as well as US_WWE_1.29.1540.16 (developer edition) as I'm supercid. both failed
Click to expand...
Click to collapse
with S-Off it's no problem to downgrade. where did you get the RUU, can you post link.
And what's the exact error you get?
EddyOS said:
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
Click to expand...
Click to collapse
Now I tried the developer edition 3.22.1540.1 that I just downloaded from HTC dev, and its installing, so I think its gonna be okay. Thanks to everyone for the speedy replies!
Shu. said:
Now I tried the developer edition 3.22.1540.1 that I just downloaded from HTC dev, and its installing, so I think its gonna be okay. Thanks to everyone for the speedy replies!
Click to expand...
Click to collapse
For other RUUs check this site: http://www.htc1guru.com/downloads/ruu-file-downloads/
I find HTCdev way too confusing, as it clutters everything together, you can easily download a RUU for "HTC One S" instead of "HTC One" (aka M7)
And since you're S-Off downgrading is no problem
Related
hello every one this is my first post i need some help please.
i bought a htc one preowned and i have since been in settings and its running a custom rom
android revolution hd 12.1 by mike 1986
my phone cid is htc_001
how do i return it to stock htc os
i have read a few posts before posting here i no i have to re lock bootloader then flash the ruu
i was wondering is there an easier way to relock bootloader and flash the ruu could some one also point me in the right direction
to which ruu to download with a link if possible to download.
thanks in advance for any help u may give with some simple instructions that i can understand as this is new to me and do not want to
make a mistake.
thankyou.
Is it S-OFF at the moment?
EddyOS said:
Is it S-OFF at the moment?
Click to expand...
Click to collapse
says m7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4a.18.3263.15
openDSP-v26.120.274.0202
eMMC-boot
so im guessing so
You don't need to relock, if you're s-off you can run whatever RUU you like.
iElvis said:
You don't need to relock, if you're s-off you can run whatever RUU you like.
Click to expand...
Click to collapse
thnks for your help can u link me to the correct ruu if u dont mind been looking not sure which one to download
thanks very much for your help to all.
Infamouslimey said:
thnks for your help can u link me to the correct ruu if u dont mind been looking not sure which one to download
thanks very much for your help to all.
Click to expand...
Click to collapse
Where was the phone purchased and what was the carrier? It's possible your CID was changed.
Assuming htc__001 is correct, the RUU collection is here:
http://forum.xda-developers.com/showthread.php?p=39588860
There are no RUUs for 4.2, so this would mean downgrading. But you should then start getting OTAs.
Note that running a RUU will fully wipe the phone. So back up anything on it you want to keep.
iElvis said:
Where was the phone purchased and what was the carrier? It's possible your CID was changed.
Assuming htc__001 is correct, the RUU collection is here:
http://forum.xda-developers.com/showthread.php?p=39588860
There are no RUUs for 4.2, so this would mean downgrading. But you should then start getting OTAs.
Click to expand...
Click to collapse
will i ran cid getter and it tells me the cid is htc_001
but in above post its cid_11111111
Infamouslimey said:
will i ran cid getter and it tells me the cid is htc_001
but in above post its cid_11111111
Click to expand...
Click to collapse
You have superCID, which means any RUU will run. You have the generic European model. CIDGetter is pulling the original cid from some system file, but it doesn't reflect the actual cid.
Infamouslimey said:
will i ran cid getter and it tells me the cid is htc_001
but in above post its cid_11111111
Click to expand...
Click to collapse
will this ruu work
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
Infamouslimey said:
will this ruu work
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
Click to expand...
Click to collapse
Yes, that's the one you want. You don't need to relock or anything being s-off. Just plug into your computer and run the ruu.
iElvis said:
Yes, that's the one you want. You don't need to relock or anything being s-off. Just plug into your computer and run the ruu.
Click to expand...
Click to collapse
thank you very much for all your help great site with such helpful members.
will this method re-lock bootloader and put s-off back to s-on or whatever its called ?
Infamouslimey said:
will this method re-lock bootloader and put s-off back to s-on or whatever its called ?
Click to expand...
Click to collapse
No and no. You have to do those manually, and there is no need to here.
if i wanted to re lock bootloader and put s back on how would i do it trying to learn so i dont have to keep asking for help ?
Infamouslimey said:
if i wanted to re lock bootloader and put s back on how would i do it trying to learn so i dont have to keep asking for help ?
Click to expand...
Click to collapse
That is a bit trickier and riskier since you don't know what was done to your phone before you bought it. I don't recommend going back to s-on because of this. However, running the correct RUU should put you back to safe stock.
Once the RUU has run and you've confirmed that the phone boots and is back to a stable stock configuration, you need to reboot and run a series of commands in fastboot:
fastboot oem writecid HTC__001
This will restore your stock CID. Note that there are two underscores there.
fastboot reboot-bootloader
Confirm on your bootloader screen that the CID is correct.
fastboot oem lock
This will relock your bootloader. Reboot again and confirm that it says "LOCKED" on your bootloader (Not "RELOCKED"). Boot up your phone and confirm that everything seems to be running correctly. You may want to give this a few days. Then reboot to bootloader when you're comfortable with it.
fastboot oem writesecureflag 3
This will put you back to s-on. When you reboot from here, your bootloader should say LOCKED and S-ON as if it was out of the box.
iElvis said:
That is a bit trickier and riskier since you don't know what was done to your phone before you bought it. I don't recommend going back to s-on because of this. However, running the correct RUU should put you back to safe stock.
Once the RUU has run and you've confirmed that the phone boots and is back to a stable stock configuration, you need to reboot and run a series of commands in fastboot:
fastboot oem writecid HTC__001
This will restore your stock CID. Note that there are two underscores there.
fastboot reboot-bootloader
Confirm on your bootloader screen that the CID is correct.
fastboot oem lock
This will relock your bootloader. Reboot again and confirm that it says "LOCKED" on your bootloader (Not "RELOCKED"). Boot up your phone and confirm that everything seems to be running correctly. You may want to give this a few days. Then reboot to bootloader when you're comfortable with it.
fastboot oem writesecureflag 3
This will put you back to s-on. When you reboot from here, your bootloader should say LOCKED and S-ON as if it was out of the box.
Click to expand...
Click to collapse
thanks very much for all your help ill install the fastboot files anyway so if need them there there.
many thanks
I too need to put my T-mobile HTC One back to stock somehow, but don't even know where to start, I saw this thread so I didn't want to clutter up the subforum, and thought that maybe I should ask here. I'm at 1.27.531.11, S-ON, rooted w/ unlocked bootloader, and would like to make it look like nothing happened to it when I return it to the store tomorrow. Could you please give me some pointers?
N0wy0ud1e said:
I too need to put my T-mobile HTC One back to stock somehow, but don't even know where to start, I saw this thread so I didn't want to clutter up the subforum, and thought that maybe I should ask here. I'm at 1.27.531.11, S-ON, rooted w/ unlocked bootloader, and would like to make it look like nothing happened to it when I return it to the store tomorrow. Could you please give me some pointers?
Click to expand...
Click to collapse
You need to s-off first or it will say "RELOCKED" on the bootloader. Problem is you may or may not be able to s-off right now. There is a new T-Mo exploit that supposedly works but I know nothing about it.
Once you do that, you can run an older RUU, which will remove the TAMPERED from the bootloader, then relock and s-on as described above.
iElvis said:
You need to s-off first or it will say "RELOCKED" on the bootloader. Problem is you may or may not be able to s-off right now. There is a new T-Mo exploit that supposedly works but I know nothing about it.
Once you do that, you can run an older RUU, which will remove the TAMPERED from the bootloader, then relock and s-on as described above.
Click to expand...
Click to collapse
Crap. Well I know they're not going to check the bootloader lol, just that when you turn on the phone, you'll see the red text at the bottom saying "Developmental purposes" and I can't remember the rest of the message. Can I make that disappear so it just shows nothing on the white background but the green HTC logo? Btw thanks for the reply.
N0wy0ud1e said:
Crap. Well I know they're not going to check the bootloader lol, just that when you turn on the phone, you'll see the red text at the bottom saying "Developmental purposes" and I can't remember the rest of the message. Can I make that disappear so it just shows nothing on the white background but the green HTC logo? Btw thanks for the reply.
Click to expand...
Click to collapse
That goes away when you relock.
Hey guys. I was trying to install a ROM, but when I installed TWRP I was put into a bootloop. Now, I have managed to get myself into a bad pickle. I have S-On and my bootloader is relocked. I cannot get fastboot oem unlock to work so I'm pretty limited. I need large amounts of help now. Thanks guys.
rjd210 said:
Hey guys. I was trying to install a ROM, but when I installed TWRP I was put into a bootloop. Now, I have managed to get myself into a bad pickle. I have S-On and my bootloader is relocked. I cannot get fastboot oem unlock to work so I'm pretty limited. I need large amounts of help now. Thanks guys.
Click to expand...
Click to collapse
As long as TWRP still works your not totally screwed, flash a rom and get s-off again and use the GURU bootloader tool to unlock, don't try and flash a RUU or firmware with stock recovery that will really be the end
clsA said:
As long as TWRP still works your not totally screwed, flash a rom and get s-off again and use the GURU bootloader tool to unlock, don't try and flash a RUU or firmware with stock recovery that will really be the end
Click to expand...
Click to collapse
Do you know what ROM I could try to flash?
rjd210 said:
Do you know what ROM I could try to flash?
Click to expand...
Click to collapse
whats your hboot? if it's 1.44 or 1.54 flash a JB rom like ARHD 31.6
if your on hboot 1.55 or 1.56 and TWRP 2.6.3.3 flash ARHD 53.0
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
clsA said:
whats your hboot? if it's 1.44 or 1.54 flash a JB rom like ARHD 31.6
if your on hboot 1.55 or 1.56 and TWRP 2.6.3.3 flash ARHD 53.0
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
Click to expand...
Click to collapse
I'm on 1.54. So i can flash it using fastboot flash system arhd.zip right? Even with a locked bootloader and S-On?
No flash it with TWRP
Sent from my HTC One using Tapatalk
clsA said:
No flash it with TWRP
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Bad news. Can't even get into TWRP and can't reflash it because the bootloader is relocked.
rjd210 said:
Bad news. Can't even get into TWRP and can't reflash it because the bootloader is relocked.
Click to expand...
Click to collapse
In the first post you said
when I installed TWRP I was put into a bootloop
Click to expand...
Click to collapse
. Second post I said
As long as TWRP still works your not totally screwed
Click to expand...
Click to collapse
Now you telling me TWRP don't work ??
Hi guys, when i've try to install official ruu RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
i've got error 152 and now my phone stuck with htc and 4 triangle, what can i do to repair it?
My situation
S-On
Locked Bootloader
Stock recovery
Cid E_11
Antoo1984 said:
Hi guys, when i've try to install official ruu RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
i've got error 152 and now my phone stuck with htc and 4 triangle, what can i do to repair it?
My situation
S-On
Locked Bootloader
Stock recovery
Cid E_11
Click to expand...
Click to collapse
which HBOOT version are you on ?
You need to be S-offed and boot loader should be unlocked in order to flash ruu
Sent from my HTC One using Tapatalk
Harish_Kumar said:
You need to be S-offed and boot loader should be unlocked in order to flash ruu
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
No, S-OFF is not compulsory if the HBOOT version of the phone matches the RUU version. Bootloader HAS TO BE LOCKED/RELOCKED
raghav kapur said:
No, S-OFF is not compulsory if the HBOOT version of the phone matches the RUU version. Bootloader HAS TO BE LOCKED/RELOCKED
Click to expand...
Click to collapse
i'm on hboot 1.56
Harish_Kumar said:
You need to be S-offed and boot loader should be unlocked in order to flash ruu
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Not really, With S-ON you can flash signed ruu of same or higher version with bootloader LOCKED or RE-LOCKED.
S-OFF is only needed to flash unsigned RUU or for downgrading, and with S-OFF you can flash a RUU with a locked/relocked or unlocked bootloader.
---------- Post added at 01:54 PM ---------- Previous post was at 01:53 PM ----------
Antoo1984 said:
i'm on hboot 1.56
Click to expand...
Click to collapse
DId you MD5 check the ruu before flashing? error 152 is for ''image error'' and the four triangles with exclamation marks means the ruu did not flash completely.
Edit: So you were on 4.19.401.11 before flashing 4.19.401.9 ? You can't downgrade with S-ON
DId you MD5 check the ruu before flashing? error 152 is for ''image error'' and the four triangles with exclamation marks means the ruu did not flash completely.
no i've downloaded this ruu from htc1guru RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1
and i've got the error
now what can i do?
Antoo1984 said:
DId you MD5 check the ruu before flashing? error 152 is for ''image error'' and the four triangles with exclamation marks means the ruu did not flash completely.
no i've downloaded this ruu from htc1guru RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1
and i've got the error
now what can i do?
Click to expand...
Click to collapse
The issue was that before flashing the RUU, the phone firmware was higher than the RUU firmware. The phone was 4.19.401.11 while the RUU is 4.19.401.9. S-OFF is required to flash a lower firmware
Your solution:
1) Unlock bootloader
2) Flash TWRP 2.6.3.3
3) adb sideload ARHD
4) S-OFF using Firewater
5) Then relock/lock the bootloader. Remove TAMPERED if you want. Then flash the RUU
(you can set the bootloader to LOCKED and remove the TAMPERED flag if S-OFF)
raghav kapur said:
The issue was that before flashing the RUU, the phone firmware was higher than the RUU firmware. The phone was 4.19.401.11 while the RUU is 4.19.401.9. S-OFF is required to flash a lower firmware
Your solution:
1) Unlock bootloader
2) Flash TWRP 2.6.3.3
3) adb sideload ARHD
4) S-OFF using Firewater
5) Then relock/lock the bootloader. Remove TAMPERED if you want. Then flash the RUU
(you can set the bootloader to LOCKED and remove the TAMPERED flag if S-OFF)
Click to expand...
Click to collapse
i've try to unlock bootloader but noting happen, say always relocked
Antoo1984 said:
i've try to unlock bootloader but noting happen, say always relocked
Click to expand...
Click to collapse
You don't get to the unlock bootloader option ??
no nothing
Antoo1984 said:
no nothing
Click to expand...
Click to collapse
I really don't know if there is a solution, maybe we could ask @nkk71 if he have an idea....
OP is stuck in ruu mode after an incomplete ruu flash from 4.19.401.11 to 4.19.401.9. S-ON, bootloader relocked (not able to unlock again). THe only option in bootloader is RUU in orange.
Antoo1984 said:
no nothing
Click to expand...
Click to collapse
Yes, @nkk71 might have an idea. Im just sharing what I know- If you cannot get into fastboot also, you really have a serious problem. Your only option (not 100% sure) is an RUU based on 4.19.401.11, which doesn't currently exist. If there is another solution, I don't know. But I think you will have to wait for an RUU based on your version.
Antoo1984 said:
i'm on hboot 1.56
Click to expand...
Click to collapse
That screenshot does not look nice!
you're firmware is in limbo... from the looks of it, you did the first flash, but didn't do the second flash.
So first make sure the RUU you have is not corrupt, the MD5 should be 9AD4111CE86981E3DFFCCE6D9EE80551
Second, do you still have a custom recovery installed, or a rooted ROM?
I've stock recovery , i'm sure
Before i've a stock rom by grureset
I can use ruu 4.19.401.9? Or can i flash rom.zip with fastboot?
Inviato dal mio GT-N8000 usando XDA Premium HD app
Finally i've found a solution!!!!
i've downloaded the ota 4.19.401.11 extract firmware.zip
flash it with fastboot 2 times and now i can access to bootloader!!
Thanks for support
Hi friends,
i have a problem. I wanna flash a stock rom. But i found no manual for the right RUU for my phone.
I have the follow things:
Viper 7 Rom
HTC_102 Cid
S-OFF
Tempered deleted
HBOOT 1.57.0000
Can someone help me? Link for the right RUU maybe?
thanks!
alex2709 said:
Hi friends,
i have a problem. I wanna flash a stock rom. But i found no manual for the right RUU for my phone.
I have the follow things:
Viper 7 Rom
HTC_102 Cid
S-OFF
Tempered deleted
HBOOT 1.57.0000
Can someone help me? Link for the right RUU maybe?
thanks!
Click to expand...
Click to collapse
There you go http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Thanks! And maybe a manual or instruction for noobs?
Is that a goog manual? Is there nothing else to do?
So i tried it . But it doesnt work I relocked the bootloader and started the RUU exe in fastboot mod. Then the silver HTC logo shown and on the computer came an error message
alex2709 said:
So i tried it . But it doesnt work I relocked the bootloader and started the RUU exe in fastboot mod. Then the silver HTC logo shown and on the computer came an error message
Click to expand...
Click to collapse
What error message did you get running the RUU?
And which RUU are you running?
Good question what the error message was. I don't know. I have to try it again to tell you what was the error.
I used the ruu from the link above.
alex2709 said:
Good question what the error message was. I don't know. I have to try it again to tell you what was the error.
I used the ruu from the link above.
Click to expand...
Click to collapse
Looking at your hboot it's likely that the RUU won't work because you would be downgrading the software using that RUU, which you cannot do as you are s on
alex2709 said:
Thanks! And maybe a manual or instruction for noobs?
Click to expand...
Click to collapse
stovie_steve said:
Looking at your hboot it's likely that the RUU won't work because you would be downgrading the software using that RUU, which you cannot do as you are s on
Click to expand...
Click to collapse
But i have S-OFF, so i have to downgrade too HBOOT 1.44 to install der RUU from the link?
Or exists a RUU for the HBOOT 1.57 that i have?
alex2709 said:
But i have S-OFF, so i have to downgrade too HBOOT 1.44 to install der RUU from the link?
Or exists a RUU for the HBOOT 1.57 that i have?
Click to expand...
Click to collapse
Ahhhh. My mistake and I didn't read the post correctly *face Palm*
You can downgrade your hboot to 1.44 but the touch screen won't work with your current Rom. You can supercid though and run any RUU if you are s off
Hello everyone,
I've been trying to get back to stock on my Sprint HTC One. I have tried using the RUU in this thread: http://forum.xda-developers.com/showthread.php?t=2795856 and no luck. I am HBoot 1.55, S-ON, and running a stock rooted rom that is on 4.4.2
So here is what I tried. I relock my bootloader and proceed to run the RUU, but 2 times I get stuck on 4% so I have no luck. I tried getting S-Off and maybe that could help me bring back to stock, but that did not work either. Really need to get this phone back to Stock, any help is appreciate it, no one responded in that thread so I'm asking here. Thanks in advance.
You'll need to flash the Full Firmware first.
If it still gets stuck try a different USB Port...USB 2 work best or try a different PC.
BD619 said:
You'll need to flash the Full Firmware first.
If it still gets stuck try a different USB Port...USB 2 work best or try a different PC.
Click to expand...
Click to collapse
That is what the video at the bottom of the first post on that thread is about, correct?
Don't I have to be S-Off for that? It says on the video that I have to, and I am not.
PaoloMix09 said:
That is what the video at the bottom of the first post on that thread is about, correct?
Don't I have to be S-Off for that? It says on the video that I have to, and I am not.
Click to expand...
Click to collapse
Use This Firmware
You will need to re-lock your bootloader (fastboot oem lock)
Flash firmware (follow the video)
Run the RUU and you will be back to stock.
You do not need to be s-off to do either.
BD619 said:
Use This Firmware
You will need to re-lock your bootloader (fastboot oem lock)
Flash firmware (follow the video)
Run the RUU and you will be back to stock.
You do not need to be s-off to do either.
Click to expand...
Click to collapse
Trying to flash it but it won't . Fails checking signature. "Signature verify fail"
Sent from crispy tocino
PaoloMix09 said:
Trying to flash it but it won't . Fails checking signature. "Signature verify fail"
Sent from crispy tocino
Click to expand...
Click to collapse
Did you re-lock your bootloader?
Is the firmware in your adb/fastboot/platform tools folder?
BD619 said:
Did you re-lock your bootloader?
Is the firmware in your adb/fastboot/platform tools folder?
Click to expand...
Click to collapse
Yes sir. Relocked, only that at the top it says "security warning." I renamed the folder to firmware.zip and it is on the platform tools folder. Did all the commands, but the second time I run the same command (like it says on the video) it gives me the error I mentioned and I don't even get the loading bar on the phone. Tried 3 times, no luck.
Sent from crispy tocino
Check PM
Same problem actually
BD619 said:
Check PM
Click to expand...
Click to collapse
I am actually having the same issue as described above, and cannot for the life of me figure out what I did wrong.
Any insight?
saxman126 said:
I am actually having the same issue as described above, and cannot for the life of me figure out what I did wrong.
Any insight?
Click to expand...
Click to collapse
So Hboot 1.55, S-ON, and can't go back to stock?
Go to this: http://forum.xda-developers.com/showthread.php?t=2658910
Download that RUU. Now, go into fastboot and relock your bootloader. Flash the firmware on that thread through fastboot, there's a video there showing you how. After that is done, go back to fastboot and you can run the RUU you downloaded from that thread. That's what I did and worked like a charm. Recommended if you use USB 2.0
PaoloMix09 said:
So Hboot 1.55, S-ON, and can't go back to stock?
Go to this: http://forum.xda-developers.com/showthread.php?t=2658910
Flash the firmware on that thread through fastboot, there's a video there showing you how. After that is done, go back to fastboot and you can run the RUU you downloaded from that thread.
Click to expand...
Click to collapse
Hi. You mean flash 4.06.651.4 version at first and then flash 5.05.651.2 version ? Is it update HBOOT from 1.55 to 1.56? What about warning message on that thread "***IMPORTANT NOTE*** you must first update your hboot to 1.56 to flash this 4.06 RUU, see full firmware below ( I recommend being s-off before doing so)"
I have. Hboot 1.55, S-on, Custom ViperOne 7.0.1
kai82 said:
Hi. You mean flash 4.06.651.4 version at first and then flash 5.05.651.2 version ? Is it update HBOOT from 1.55 to 1.56? What about warning message on that thread "***IMPORTANT NOTE*** you must first update your hboot to 1.56 to flash this 4.06 RUU, see full firmware below ( I recommend being s-off before doing so)"
I have. Hboot 1.55, S-on, Custom ViperOne 7.0.1
Click to expand...
Click to collapse
Just flash firmware 4.06.651.4 (you'll be on hboot 1.56) and then run that RUU. Don't worry about 5.05.651.2 firmware or RUU.
Make sure you relock your bootloader before anything.
Whenever the RUU is done and you're back in stock, you'll get the OTAs to 5.05.651.2, just telling you exactly what I did that worked, I also had a lot of trouble getting back to stock/unrooting.
Sent from crispy tocino