Gaming Console with Lollipop? Ouya Gets an Android TV Port

Android is a very flexible platform, and it can be used on a large variety of … more

Android App Review: Manage Your Connections Automagically – XDA TV

Material Design is all the buzz in the Android world right now. … more

Official TWRP Recovery Lands on Micromax Canvas Magnus

With the recent release of Android One, Micromax and MediaTek released fully buildable … more

Update Overload: SuperSU Heavily Updated

There are apps and apps out there. Very few can reach the level of popularity required to stay at … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

My AT&T HOX will not update

OP hijodedios51206

15th February 2014, 09:09 PM   |  #1  
OP Member
Flag Murrieta, CA
Thanks Meter: 3
 
41 posts
Join Date:Joined: Jul 2009
More
hello XDA. I appologize if i am breaking rules but i dont know what else to do with my phone.
I recently bought an AT&T X. it had the 2.20 at&t firmware installed. i managed to root it and supercid it and unlock bootloader. however, ever since then, i cannot update thru RUU. i was updating to 2.14 hboot to get facepalm s-off.

writing zip ...
<bootloader> adopting the signature contained in this image...
<bootloader> zip header checking...
<bootloader> zip info parsing...
FAILED <remote: 99 unknown fail>

i tried downloading the OTA and made sure its AT&T software as i do not have s-off yet. I have flashed stock recovery (i had twrp installed after i rooted and supercid) and navigate to OTA files but i get this.

mount SDCARD failed 1 times
mount SDCARD failed 2 times
mount SDCARD failed 3 times
mount SDCARD failed 4 times
mount SDCARD failed 5 times

i chose apply from phone storage and i get:

invalid operation
rebooting...

also i ran JET and successfully downgraded hboot to 1.09 cuz i read it not all parts of s-on were implemented, so i thought i could obtain s-off that way.

i have searched all over xda and google. i do as much research as i can first.
16th February 2014, 01:14 AM   |  #2  
timmaaa's Avatar
Recognized Contributor
Flag Melbourne
Thanks Meter: 7,210
 
15,007 posts
Join Date:Joined: Jun 2011
Donate to Me
More
Whoa, where are you getting your information? Stop what you're doing. Running the jb RUU while s-on and SuperCID is going to brick your phone. You're lucky it's failing.

What makes you think you need to update it to get s-off? Have you attempted the Facepalm procedure yet?

Sent from my Evita
17th February 2014, 06:52 PM   |  #3  
OP Member
Flag Murrieta, CA
Thanks Meter: 3
 
41 posts
Join Date:Joined: Jul 2009
More
Quote:
Originally Posted by timmaaa

Whoa, where are you getting your information? Stop what you're doing. Running the jb RUU while s-on and SuperCID is going to brick your phone. You're lucky it's failing.

What makes you think you need to update it to get s-off? Have you attempted the Facepalm procedure yet?

Sent from my Evita

My bad. Wat happened was i successfully rooted while on 2.20 and proceeded to flash the zip indicated by facepalm s-off thread. thats when i started getting the error 99. i checked cid and made sure it was 11111111, which is required by facepalm s-off. now no RUU's work.. i setting the cid back to its original CWS__001 and ran updated RUU but still got the same errors.
17th February 2014, 06:56 PM   |  #4  
OP Member
Flag Murrieta, CA
Thanks Meter: 3
 
41 posts
Join Date:Joined: Jul 2009
More
i forgot to mention that in the first post. i know RUU while s-off and scid bricks it.
17th February 2014, 07:06 PM   |  #5  
redpoint73's Avatar
Recognized Contributor
Thanks Meter: 3,294
 
7,549 posts
Join Date:Joined: Oct 2007
How many times did you try Facepalm, and got error 99? It seems some folks have gotten error 99, and just ran it again.

Bootloader needs to be relocked to run RUU with s-on. Did you relock the bootloader?
The Following User Says Thank You to redpoint73 For This Useful Post: [ View ]
17th February 2014, 07:10 PM   |  #6  
OP Member
Flag Murrieta, CA
Thanks Meter: 3
 
41 posts
Join Date:Joined: Jul 2009
More
Quote:
Originally Posted by redpoint73

How many times did you try Facepalm, and got error 99? It seems some folks have gotten error 99, and just ran it again.

Bootloader needs to be relocked to run RUU with s-on. Did you relock the bootloader?

i ran it multiple times. i saw a thread i forgot where to find it. i looked thru pages of different threads and i found one that says if u get error 99 just run it again till it flashes. it never flashed for me. i grew a bit impatient and stopped trying.

i tried relocking once but didnt work. i didnt try too much while relocked ill try again when i get the chance.
Last edited by hijodedios51206; 17th February 2014 at 07:12 PM. Reason: forgot to answer second question
17th February 2014, 07:23 PM   |  #7  
timmaaa's Avatar
Recognized Contributor
Flag Melbourne
Thanks Meter: 7,210
 
15,007 posts
Join Date:Joined: Jun 2011
Donate to Me
More
Quote:
Originally Posted by hijodedios51206

i ran it multiple times. i saw a thread i forgot where to find it. i looked thru pages of different threads and i found one that says if u get error 99 just run it again till it flashes. it never flashed for me. i grew a bit impatient and stopped trying.

i tried relocking once but didnt work. i didnt try too much while relocked ill try again when i get the chance.

There are a couple of solutions to the error 99 problem strewn throughout the Facepalm thread, you can't go through more than a few pages without seeing me mention the solutions. Plus there's another s-off method called Rumrunner that you could have tried. You've kinda taken a step backwards by changing your CID back to stock.

Anyway...

What do you mean you tried relocking but it didn't work? Exactly what didn't work?
17th February 2014, 07:31 PM   |  #8  
OP Member
Flag Murrieta, CA
Thanks Meter: 3
 
41 posts
Join Date:Joined: Jul 2009
More
Quote:
Originally Posted by timmaaa

There are a couple of solutions to the error 99 problem strewn throughout the Facepalm thread, you can't go through more than a few pages without seeing me mention the solutions. Plus there's another s-off method called Rumrunner that you could have tried. You've kinda taken a step backwards by changing your CID back to stock.

Anyway...

What do you mean you tried relocking but it didn't work? Exactly what didn't work?

i mean i tried relocking to run RUU but still got error 99. i still have supercid currently. it got to the point i cannot write cid anymore. bootloader simply freezes when i send command to write cid. im not at my computer so ill post cmd's output when i get home. i tried both s-off methods.
17th February 2014, 07:31 PM   |  #9  
redpoint73's Avatar
Recognized Contributor
Thanks Meter: 3,294
 
7,549 posts
Join Date:Joined: Oct 2007
Quote:
Originally Posted by hijodedios51206


i tried relocking once but didnt work.

The RUU will never run with an unlocked bootloader and S-on. So there is your answer right there.
The Following User Says Thank You to redpoint73 For This Useful Post: [ View ]
17th February 2014, 07:37 PM   |  #10  
OP Member
Flag Murrieta, CA
Thanks Meter: 3
 
41 posts
Join Date:Joined: Jul 2009
More
Quote:
Originally Posted by redpoint73

The RUU will never run with an unlocked bootloader and S-on. So there is your answer right there.

alrite ill try it again. ill post the results when i do. thanks.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes