Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,730,051 Members 53,597 Now Online
XDA Developers Android and Mobile Development Forum

Failed: Return to stock and unrooted

Tip us?
 
geeibara
Old
(Last edited by geeibara; 6th January 2014 at 07:50 PM.)
#1  
Member - OP
Thanks Meter 2
Posts: 39
Join Date: Feb 2013
Default Failed: Return to stock and unrooted

I used this thread to unroot and return to stock http://forum.xda-developers.com/show...highlight=s-on
I had done this before with one of CM 10 and I kept the files used in this thread.

I switched to AOKP kitkat 12-30-13. I wanted to return to stock and unrooted.
I got to the oem ruu and kept receiving this message. FAILED (remote: 90 hboot pre-update! please flush image again immediately)

I did this repeatedly as followed. It went over 5 times. I figured this was a problem. Now I am stuck in the bootloader where my phone is locked and S-on. I tried to flash it again and now I get remote: 12 signature verify failed.
It also says ***TAMPERED*** at the top of bootloader, above ***LOCKED***

Edit: I wanted to mention that I do have a backup of my kitkat state at the beginning of all of this. It is in twrp, but I can't flash install the twrp.img, signature verify failed.
 
bregga
Old
#2  
Member
Thanks Meter 3
Posts: 68
Join Date: Dec 2011
Default ouch

hmm not sure if this will help or not but at this point
http://forum.xda-developers.com/show....php?t=2317536
what happens if you try the adb commands in

http://forum.xda-developers.com/show...ock+bootloader

---------- Post added at 08:01 AM ---------- Previous post was at 07:59 AM ----------

Quote:
Originally Posted by geeibara View Post
I used this thread to unroot and return to stock http://forum.xda-developers.com/show...highlight=s-on
I had done this before with one of CM 10 and I kept the files used in this thread.

I switched to AOKP kitkat 12-30-13. I wanted to return to stock and unrooted.
I got to the oem ruu and kept receiving this message. FAILED (remote: 90 hboot pre-update! please flush image again immediately)

I did this repeatedly as followed. It went over 5 times. I figured this was a problem. Now I am stuck in the bootloader where my phone is locked and S-on. I tried to flash it again and now I get remote: 12 signature verify failed.
It also says ***TAMPERED*** at the top of bootloader, above ***LOCKED***
can you try the fastboot ruu and attempt to write a 1.54 hboot or a custom recovery
 
geeibara
Old
(Last edited by geeibara; 6th January 2014 at 07:48 PM.)
#3  
Member - OP
Thanks Meter 2
Posts: 39
Join Date: Feb 2013
Quote:
Originally Posted by bregga View Post
hmm not sure if this will help or not but at this point
http://forum.xda-developers.com/show....php?t=2317536
what happens if you try the adb commands in

http://forum.xda-developers.com/show...ock+bootloader

---------- Post added at 08:01 AM ---------- Previous post was at 07:59 AM ----------



can you try the fastboot ruu and attempt to write a 1.54 hboot or a custom recovery
When running the supercid I get the following:
(bootloader) [SD_ERR] The project does not support SD card
(bootloader) E0902910 E0902E20
FAILED (status read failed (too many links))
FINISHED

Then when I try to read the cid my phone freezes, or it was frozen and doesn't respond to any commands. Then I just have to manually turn it off.

for the unlock bootloader, adb commands do not work in bootloader, it does not recognize the device. My computer only recognizes fastboot commands. also in that post it says that I need s-off, while my device is currently s-on.

For your last suggestion I do not know how to do those things. For a custom recovery do you mean like TWRP? I tried to flash recovery twrp.img but got FAILED (remote: signature verify failed).
If it helps I do happen to have a backup when my phone was unlocked/s-off running aokp kitkat as mentioned above. It is from twrp.
 
bregga
Old
#4  
Member
Thanks Meter 3
Posts: 68
Join Date: Dec 2011
Default don't know

not sure how to do it now that you are s locked again sorry i was reading original post didn't see the different names
 
geeibara
Old
#5  
Member - OP
Thanks Meter 2
Posts: 39
Join Date: Feb 2013
So from my research I have done so far it seems that because I failed to flash the ruu and proceeded to s-on that my phone was bricked, or soft-bricked.
I gave up and asked verizon for a new replacement. I was quite hesitant on this choice at first because at the very start the phone says ***TAMPERED*** at the very top of the bootloader, so I wasn't sure if verizon would accept it for free, or they would make me pay 550-300.

Now after more research I saw this http://www.droid-life.com/2011/06/16...nes-if-rooted/ and am a bit for relieved.

If anyone reading this should learn anything, be very careful re-locking your phone, because in unintelligent hands it can be very hard to fix it.
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes