Database Info

[GUIDE] How to fix "Failed image LNX 0x0002 / RSD mode 2

I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!

mowassasin said:
I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!
Click to expand...
Click to collapse
So I went and bought the factory cable from the Black Hat guys, and luckily haven't had the need to use it. Any advice you'd like to give in case I need to at some point?

I guess the only advice I can give is: don't re-lock the boot loader when you have a custom rom loaded

You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk

bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
It wouldn't recognise any fastboot commands nor the RSD Lite program for me.
But if it does, then thats good.
Merely a heads up for those who were in the same situation I was

bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.

yaturner said:
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.
Click to expand...
Click to collapse
Over the course of a few hours I was able to fix this, so I am going to write this little walkthrough for you using a rom from bwcorvus's page (CLICK HERE) and then used the guide from dirtymindedx -(CLICK HERE)
The reason it took me this long (as well as doing other things) was because I used the wrong set up to unroot my tablet. I was using the Unofficial images that are on bwcorvus's link. Because I didn't read thoroughly enough in his breakdown, I made myself look like a fool...
What you want is NOT
UNOFFICIAL STOCK IMAGES
Click to expand...
Click to collapse
because you will not be able to lock the bootloader (IF you want it to be that way, which I did, and so it gave me a 0x000004 Error, and yes i see that you are having a 0x000002 but somewhere i read this could help that.) I just wanted to get rid of Clockwork Recovery Manager cause it was not working on my 3.2 rooted tablet, and thought that because i messed up teh whole image with playing around and upgrading and seeing how i could break the image without overclocking, i thought i should actually try and make it back to stock too. With this... I needed to do these steps...
1. Upgrade the Motorola drivers while the XOOM was plugged in, so then I would be able to use the Fastboot Correctly.
2. Download the correct roms for my tablet, (Wi-Fi is mine, just grab the one that fits your version and just follow along.)
3. Upgrade my ADB from google because for soem odd reason my fastboot did not like the xoom till i did that...
4. Used the STOCK CABLE. I can Confirm that the STOCK CABLE that allows you to recharge the phones, WILL WORK for this...
5. Once the ADB was set up, I restarted it, aka Hit the red X and then loaded it back up and then closed it again, just to make sure the services were updated somewhat...
6. Opened Command prompt and navigated to the folder that help the zipfile for the fastboot flashing guide (aka dirtymindedx's guide at the top), be using CD (Drive Letter):/location/of/the/folder/that/is/unzipped
7. I then checked over the information in the folder by using dir /a and then proceeded to read through the guide
7-1. A note here... I did the fastboot erase userdata instead, because I wanted to see if it would brick it again... (sorry, I was in a fowl mood with the world last night so I was waiting for it to get bricked so i had a reason to use it as an ice scraper on my car... (not like i would really do it... just wanted a reason for justification haha)
8. ???
9. Profit
This is only to get rid of a "already slightly bricked" device... which I had done after relocking the Rom that was not official to Motorola and now, after a few updates, i now have Android 4.0.3 for the Xoom that was OTA'ed, looking to see how easy it will be to root to reload my rpg game saves that i got caught up in (hence my disappearance from the forums haha...) but I hopefully helped you out in a direction to heads towards... and as long as you don't lock the boot-loader (which someone posted about it before i did...) you should be fine with any changes to the rom after the updates... Also, you can skip steps on this too... you can just flash the image and not the recovery menu and so forth, allowing you to keep other settings that are not part associated to the rom image.
Also sorry for the insanity in my words... I have been up for a good 36 hours with a half hour nap somewhere in there...

[Q] Clockworkmod warns: "bad recovery" - What to do?

Hello guys,
a few days ago I dared to root my Xperia X10 Mini Pro with SuperOneClick and flashed a Cyanogenmod 7 Android 2.3.3 ROM. All in all, it worked pretty well.
After doing some apps installation stuff I rebooted in the Recovery (Clockworkmod which obviously came along with the ROM) and made a backup, just for the case. Afterwards, I selected "power off" in the CWM menu because I wanted to go to bed.
Then, immediately, CWM said something like "Error - This recovery seems to be bad" and something with a "risk". I managed however to power off. Can't remember if that worked via CWM or if I pushed the power off hardbutton or removed the battery.
Yet - the ROM seems to work. Now I'm a bit anxious because of the CWM error.
Is there really a risk? I planned to dare unlocking the bootloader soon. Is it dangerous to do this with a "bad recovery" or doesn't that matter at all?
Is there a possibility to repair CWM? Can I just install a new CWM? If yes - how?
Sorry - pretty noobish questions, I know.
Can you help me anyway?
Thanks a lot!

deleted post

Thank you for your help! I already thought that no one would answer because the thread disappered on page 3 of this forum
I've never heard from Odin before and therefore googled it. It only occured in connection with Samsung devices. Are you sure it is compatible to my Sony Ericsson?
Anyway, can I also install a new CWM via ROM Manager or wouldn't you recommend this?

Warning: I'm a noob. Take my advice at your own risk!
From what I understand, flashing CWM via Rom Manager is exactly the same as manual flashing (perhaps better, since the Rom Manager presumably keeps up to date). So I think you should be able to do so and make another recovery (without going through any of that manual flashing stuff). You should get a second opinion just because I'm so noobish, but I think this is the case.
However, from my limited understanding, I don't think the recovery will make any difference when dealing with the bootloader. The bootloader is, more or less, the very first set of instructions executed when the phone turns on. If you mess that up, your phone won't even be able to get into recovery mode. Also, the recovery images are stored on your sd card, which is wiped upon unlocking. Once again, I could be wrong.

deleted post

Dude, what are you talking about? You can't use ODIN on a non-Samsung phone.

trich025 said:
don't use rom manager just use the odin for your safety, you can bet that samsung users are the one benefiting on odin but as you can see erricson and samsung are both android phones and if you examine them both device have similar programs, and one thing, always keep in mind that you have to back up your current rom for emergency uses so you can still get back to were you started in case something went wrong.
if i helped you with this problem you could click the thanks button >>>>
Click to expand...
Click to collapse
OK now this is flat out wrong. Each Android device has a different program used. Samsung has Odin, HTC has an RUU. Not sure about SE. But never use a software made for one device on another unless you want a brick. Just because they both use android doesn't mean they are the same.

Thanks to everyone, especially Product F(RED)!
No offence, trich025, but I guess you were wrong.
Can I destroy something by re-installing or updating CWM via ROM-Manager just in case my CWM has a bug?

[Q] A question about my brick

I have combed through these forums and haven't been able to find an answer yet, so please forgive me if I have missed something. So here goes:
If: a) I have updated to JB, and
b) I unlocked my device and
c) I successfully installed TWRP and
d) I managed to brick my device insomuch that ONLY APX mode is available to me when I connect to my PC, is there a solution unbrick my device at this time?
Currently booting my device will only display the first ASUS boot screen and never goes any further.
Many thanks to anybody who can provide some insight.

jeremiah.wells said:
I have combed through these forums and haven't been able to find an answer yet, so please forgive me if I have missed something. So here goes:
If: a) I have updated to JB, and
b) I unlocked my device and
c) I successfully installed TWRP and
d) I managed to brick my device insomuch that ONLY APX mode is available to me when I connect to my PC, is there a solution unbrick my device at this time?
Currently booting my device will only display the first ASUS boot screen and never goes any further.
Many thanks to anybody who can provide some insight.
Click to expand...
Click to collapse
What have you tried in the meantime? Did you install NvFlash before the update to JB? You cannot get to recovery? If you cannot but do have fastboot available, either use TWRP or CWM (which can be flashed via fastboot as well: http://forum.xda-developers.com/showthread.php?t=1926286 in case your recovery has been borked) and then flash a stock ROM from ASUS from here: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Take a look here: http://forum.xda-developers.com/showthread.php?t=1938129 as well.

MartyHulskemper said:
What have you tried in the meantime? Did you install NvFlash before the update to JB? You cannot get to recovery? If you cannot but do have fastboot available, either use TWRP or CWM (which can be flashed via fastboot as well: http://forum.xda-developers.com/showthread.php?t=1926286 in case your recovery has been borked) and then flash a stock ROM from ASUS from here: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Take a look here: http://forum.xda-developers.com/showthread.php?t=1938129 as well.
Click to expand...
Click to collapse
MartyHulskemper, many thanks for your prompt reply. To answer your questions:
1) I have tried (in vain, I now understand) to use nvflash (first using wheelie with a couple configurations) and to no avail
2) I did NOT install nvflash before, as I was excited about rooting and wasn't abreast of all the consequences of updating directly to JB and then unlock and then root with a new device. Unfortunately I had read a post on (another website) that nvflash wasn't working on the TF700T (which I presume was correct at the time it was written) only to now learn that it is.
A note -- fastboot is not available and the only way I can get the device visible to a computer is to put it in APX mode.
This is a classic case of me jumping the gun without fully understanding what's implied with the various updates and root solutions out there. Basically I followed a guide and used a set of files distributed on scottsroms that indeed rooted my device with the TWRP recovery. What I then attempted and (I think what ultimately did my device to its current state) was to attempt to flash CWM. After that flash I couldn't get either recovery to boot and so I attempted a data wipe and was going to reflash with CWM. After that data wipe is when I could not longer boot.
Sorry about the novel but I guess I'm vainly hoping this may trigger and idea from you or a future reader about what my options are. I will look at the link you suggested and go from there.
Again, thank-you for any assistance you may provide.

Can you get into recovery at all when you hold vol down and power? I had the same problem with my infinity when the .18 update came out, i had a freeze and a crash during normal use while the update was either downloading or changing something and when it restarted I couldnt do anything but go into APX. I never unlocked it (mainly because the asus tool wouldnt work) but I had to RMA to get it fixed. If you can at least get to the recovery menu you can try reinstalling the stock rom from an mSD. Otherwise you may have to do the same as me and RMA and hope that they dont tell you tough luck since its unlocked As far as I know the only way to recover the tablet when APX is your only option is with NVFlash, which I never installed because .30 was on my infinity when i bought it.

jeremiah.wells said:
I couldn't get either recovery to boot and so I attempted a data wipe
Click to expand...
Click to collapse
That is the exactly step that bricked many TF700s here (search the forums). "Wipe data" with a broken recovery = bootloader won't do anything else than try to boot the broken recovery.
If you didn't create a blob for wheelie/nvflash before, your only option now is to send it to Asus for a costly "repair" (they claim they have to change the mainboard, I don't know why they don't just use nvflash).

_that said:
That is the exactly step that bricked many TF700s here (search the forums). "Wipe data" with a broken recovery = bootloader won't do anything else than try to boot the broken recovery.
If you didn't create a blob for wheelie/nvflash before, your only option now is to send it to Asus for a costly "repair" (they claim they have to change the mainboard, I don't know why they don't just use nvflash).
Click to expand...
Click to collapse
Yes, with only APX available but no NvFlash backup, there's very little to no light at the end of the tunnel. I also wondered why the reports of RMA'd users mention a motherboard change, but I do remember something about unit-specific code being backed up with NvFlash. Although I'd think it strange, it might be that even ASUS cannot revive a bricked 700 without knowing that code, necessitating the new motherboard with a known code. This is only speculation, of course, but it's the only reason I could think of.
@OP: with no fastboot available, you will not be able to follow either Scott's guide or reflash a recovery. I sincerely feel for you, especially since it was enthusiasm that got you into trouble. I know the resultant feeling, and I hate it, for it quells said enthusiasm in the future and make you overly cautious. I wish you a speedy and effective RMA!

jeremiah.wells said:
MartyHulskemper, many thanks for your prompt reply. To answer your questions:
1) I have tried (in vain, I now understand) to use nvflash (first using wheelie with a couple configurations) and to no avail
2) I did NOT install nvflash before, as I was excited about rooting and wasn't abreast of all the consequences of updating directly to JB and then unlock and then root with a new device. Unfortunately I had read a post on (another website) that nvflash wasn't working on the TF700T (which I presume was correct at the time it was written) only to now learn that it is.
A note -- fastboot is not available and the only way I can get the device visible to a computer is to put it in APX mode.
This is a classic case of me jumping the gun without fully understanding what's implied with the various updates and root solutions out there. Basically I followed a guide and used a set of files distributed on scottsroms that indeed rooted my device with the TWRP recovery. What I then attempted and (I think what ultimately did my device to its current state) was to attempt to flash CWM. After that flash I couldn't get either recovery to boot and so I attempted a data wipe and was going to reflash with CWM. After that data wipe is when I could not longer boot.
Sorry about the novel but I guess I'm vainly hoping this may trigger and idea from you or a future reader about what my options are. I will look at the link you suggested and go from there.
Again, thank-you for any assistance you may provide.
Click to expand...
Click to collapse
I really feel for you...just bricked a phone last week and it's an awful feeling, like you should have known better. Good luck.
Just out of curiosity, did you use Rom Manager to flash CWM recovery? That's the kiss of death for the TF700.

I feel for you too as this happened to me even without any type of modifications to my recovery or bootloader! As far as RMA and the motherboard change I am not sure whether they recovered my device without an actual change. When i got it back from RMA it was on the same firmware as before (not the most recent at the time) as well as retaining the same SN on my device. Since I got it back though I am unable to use the unlocker tool. I get that network error and a refusal from the asus unlock server that lots of people were having issues with a while back. I am in touch with Asus service now, but asus service is usually a long arduous process! I hope that they dont charge you for the replacement, but seeing as you unlocked its very possible if you have any sort of insurance from your credit card that may be a better route by trying to replace it as a lost or broken unit. My RMA was free (except shipping) but again, no unlock!
best of luck.

MartyHulskemper said:
it might be that even ASUS cannot revive a bricked 700 without knowing that code, necessitating the new motherboard with a known code. This is only speculation, of course, but it's the only reason I could think of.
Click to expand...
Click to collapse
They must know the device key, because the unlocking process requires it. However it is plausible that service centers have no access to this information.
It's somehow depressing that not knowing 128 secret bits takes away control over our own devices.

_that said:
They must know the device key, because the unlocking process requires it. However it is plausible that service centers have no access to this information.
It's somehow depressing that not knowing 128 secret bits takes away control over our own devices.
Click to expand...
Click to collapse
In cases like this, I always hope you get a motivated technician that actually hunts down your serial from that database and helps you out. Guess I'm a bit naive in that regard.
Yeah, those 16 bytes keeping the door shut are a major bummer, as is the fact that NvFlash was not pre-installed anyway...

okantomi said:
I really feel for you...just bricked a phone last week and it's an awful feeling, like you should have known better. Good luck.
Just out of curiosity, did you use Rom Manager to flash CWM recovery? That's the kiss of death for the TF700.
Click to expand...
Click to collapse
To answer your curiosity, NO... I did not install or use Rom Manager in any way to get to this state.

Got a question. Mine is rooted but locked, i attempted to install TWRP before unlocking. I can still boot it up but i cant get into recovery. Can i unlock it without a working recovery and just reinstall TWRP? what are my options? Any help would be great.
edit: nevermind, i think i found the answer...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Asus tf300t(g) boot loop and stuck in TWRP wont mount, not recognized. - briked

Hello
I have an asus tf300tg and I did update to 4.2.1 JB. bootloader was unlocked before the update. Tablets started ok then I put TWRP 2.5.0 but it seemed like something was not working well because I could not see external sd card when I tried to give you wipe from TWRP, but said faild. I rebooted the tablet I entered fastboot and in this mode shows, three icons. RTK, android, and wipe again. And naturally I did wipe once, then never turned on.
Now bootloader is unlocked and starts straight into TWRP.
At first my pc (win7 64bit) Recognize that "transformes" then I searched and found "Naked drivers 0.72" in the idea of ​​connecting the tablet in fastboot and write something-anything but I DON'T HAVE SUCCES.
I installed in various ways (asus adb, google adb) of naked driver but I could not communicate via fastboot. Maybe I don't chose the right way
Does anyone else have a procedure that can be repaired?
And that since the corect connection mode that allows me to write on tablet via fastboot ?
I saw that the problem occurs in many places and forums (like here: http://www.teamw.in/project/twrp2/97 Note the comments) but I dont found a solutions.
BR
Mihnea
I wait with many interes your sugestions.

Sorry to say but you should have read a little more about what you were doing. It CLEARLY says over and over and in this forum NOT to use THAT wipe option.
You've just wiped all the files from your device. There are now no files to boot from.
If you can get into fastboot or ADB you may have a chance of saving your tablet. There's a very good chance that you've just bricked it though. Best of luck.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2

wetbiker7 said:
Sorry to say but you should have read a little more about what you were doing. It CLEARLY says over and over and in this forum NOT to use THAT wipe option.
You've just wiped all the files from your device. There are now no files to boot from.
If you can get into fastboot or ADB you may have a chance of saving your tablet. There's a very good chance that you've just bricked it though. Best of luck.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
I dont understand ... WHY is happend that ? TWRP is sucks because I thing that soft dont have safety belt... ??? Because before to upgrate I do wipe and all was very ok .... or other is cause? I think that Asus dont put this obtion ... that people damage our tablets...
I think that good answer must be come from twrp team ???

I had also wiped my device and would have been stuck had I not had nvflash...please guys take all possible precautions before you start messing around with your devices and ensure you can go back and flash a stock ROM...now all I do is get into APX mode, fire up wheelie.exe and I unbrick my device. Did you nvflash your device before? If you can get into fastboot mode there may be some hope yet...
This is a good place to start: http://forum.xda-developers.com/forumdisplay.php?f=1579
If all else fails, please PM me...

mihnea_gsm said:
I dont understand ... WHY is happend that ? TWRP is sucks because I thing that soft dont have safety belt... ??? Because before to upgrate I do wipe and all was very ok .... or other is cause? I think that Asus dont put this obtion ... that people damage our tablets...
I think that good answer must be come from twrp team ???
Click to expand...
Click to collapse
Dude, you really didn't even get into TWRP recovery. If you would have tapped the RCK tab you would have went into TWRP. Don't go blaming it on TWRP because you failed to do your homework. I know there are probably 10 threads where people have done the same thing and tapped the wrong WIPE tab. If I can find and read them then so can you. You just failed to do so.
It really sux that you've messed your tablet up but when you've got a device that costs that much, you are supposed to do your research before trying something you know nothing about. I read through this forum for over a week before I bought and rooted mine because I wanted to make sure I knew what i was doing and didn't end up with a $300 paperweight. If I didn't know or couldn't find the answer I asked questions. :good:

wetbiker7 said:
Dude, you really didn't even get into TWRP recovery. If you would have tapped the RCK tab you would have went into TWRP. Don't go blaming it on TWRP because you failed to do your homework. I know there are probably 10 threads where people have done the same thing and tapped the wrong WIPE tab. If I can find and read them then so can you. You just failed to do so.
It really sux that you've messed your tablet up but when you've got a device that costs that much, you are supposed to do your research before trying something you know nothing about. I read through this forum for over a week before I bought and rooted mine because I wanted to make sure I knew what i was doing and didn't end up with a $300 paperweight. If I didn't know or couldn't find the answer I asked questions. :good:
Click to expand...
Click to collapse
Man no longer take ptr defense that I think you're wrong ...
Look .. when I got the asus app to unlock bootloader it says clearly: If using application note is lost ... guarantee ...
But here in this case I have taken away from the site fisirele .. and nothing in there that you do not press WIPE button
* That's what ... ok there is a software bug and it's understandable ... waiting to see how to solve ...
And another thing ... I have a GSM service ... so I pass many phones and tablets by hand and install a lot and CWM and TWRP and it is the first time that happens ... so do not need me to tell me that I have not done my homework.
Then I recommend the Samsung Galaxy Tab that anything is much simpler and solutions are at hand ... including bootloder destroyed ... then we rewrite bootloder JTAG on the tablet and tablet repair in 1 hour .. simple as that.
Today I gave mail to all those who produce JTAG interfaces (riff jtag, meduse jtag, vulcanobox, easy jtag) to see if anyone has any solutions for NVIDIA Tegra3 jtag, although I do not think ... but if I stick to appear instant boot tablet and restore bootloader, but many people don't have this interfeces...
BR
Mihnea

wetbiker7 said:
Dude, you really didn't even get into TWRP recovery. If you would have tapped the RCK tab you would have went into TWRP. Don't go blaming it on TWRP because you failed to do your homework. I know there are probably 10 threads where people have done the same thing and tapped the wrong WIPE tab. If I can find and read them then so can you. You just failed to do so.
It really sux that you've messed your tablet up but when you've got a device that costs that much, you are supposed to do your research before trying something you know nothing about. I read through this forum for over a week before I bought and rooted mine because I wanted to make sure I knew what i was doing and didn't end up with a $300 paperweight. If I didn't know or couldn't find the answer I asked questions. :good:
Click to expand...
Click to collapse
I've also read those warnings, but if bootloader's wipe is safe with stock recovery and bricks tablet with TWRP flashed, then there is clearly something wrong with TWRP.

mihnea_gsm said:
Man no longer take ptr defense that I think you're wrong ...
Look .. when I got the asus app to unlock bootloader it says clearly: If using application note is lost ... guarantee ...
But here in this case I have taken away from the site fisirele .. and nothing in there that you do not press WIPE button
* That's what ... ok there is a software bug and it's understandable ... waiting to see how to solve ...
And another thing ... I have a GSM service ... so I pass many phones and tablets by hand and install a lot and CWM and TWRP and it is the first time that happens ... so do not need me to tell me that I have not done my homework.
Then I recommend the Samsung Galaxy Tab that anything is much simpler and solutions are at hand ... including bootloder destroyed ... then we rewrite bootloder JTAG on the tablet and tablet repair in 1 hour .. simple as that.
Today I gave mail to all those who produce JTAG interfaces (riff jtag, meduse jtag, vulcanobox, easy jtag) to see if anyone has any solutions for NVIDIA Tegra3 jtag, although I do not think ... but if I stick to appear instant boot tablet and restore bootloader, but many people don't have this interfeces...
BR
Mihnea
Click to expand...
Click to collapse
Man, if you would have read , you would have known not to use the wipe tab. As I said before, there are threads all over the place in here stating NOT TO USE THAT WIPE OPTION. You may have done SOME research but you didn't do enough on THIS tablet. The research on all the other devices you know about doesn't count. LOL It's TF300 series we're talking about.
Oh, and you said for me not to take offense because I think you're wrong. Bro, I don't take offense because you disagree with me. I'm just trying to get you to man up and admit that you made the mistake and didn't do enough reading. LOL
quidrick said:
I've also read those warnings, but if bootloader's wipe is safe with stock recovery and bricks tablet with TWRP flashed, then there is clearly something wrong with TWRP.
Click to expand...
Click to collapse
Well, let me ask you a question. Why would you want to wipe the tablet anyways when it's not in recovery? You MUST press RCK to enter the recovery. The wipe option you guys are talking about is not even a part of TWRP recovery.

Moe5508 said:
I had also wiped my device and would have been stuck had I not had nvflash...please guys take all possible precautions before you start messing around with your devices and ensure you can go back and flash a stock ROM...now all I do is get into APX mode, fire up wheelie.exe and I unbrick my device. Did you nvflash your device before? If you can get into fastboot mode there may be some hope yet...
This is a good place to start: http://forum.xda-developers.com/forumdisplay.php?f=1579
If all else fails, please PM me...
Click to expand...
Click to collapse
in this moment I am in this point:
in this point adb recognized my tablet
C:\adb>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0123456789ABCDEF recovery
but after I want to flash blob
C:\adb>fastboot -i 0x0B05 flash system blob
< waiting for device >
BR
Mihnea

Well, let me ask you a question. Why would you want to wipe the tablet anyways when it's not in recovery? You MUST press RCK to enter the recovery. The wipe option you guys are talking about is not even a part of TWRP recovery.
Click to expand...
Click to collapse
a) Because it's official method to do factory reset, recommended by ASUS when you have problems with your tablet. It is working perfectly fine on stock recovery and some users are used to do this that way.
b) Because it's quite easy to do this by mistake, when you are trying to enter recovery. Please, give me fast and honest answer without checking - which button changes option, and which enters selected option?
My tablet is perfectly fine, running TWRP and custom ROM, but someone has to defend users who used wipe data.
Unless we hear sensible explanation from one of TWRP developers why this option is working fine on stock recovery and is bricking tablets on TWRP, and why it can't work correctly (or at least safe) on custom recovery, then it should be treated as a custom recovery bug.

quidrick said:
a) Because it's official method to do factory reset, recommended by ASUS when you have problems with your tablet. It is working perfectly fine on stock recovery and some users are used to do this that way.
b) Because it's quite easy to do this by mistake, when you are trying to enter recovery. Please, give me fast and honest answer without checking - which button changes option, and which enters selected option?
My tablet is perfectly fine, running TWRP and custom ROM, but someone has to defend users who used wipe data.
Unless we hear sensible explanation from one of TWRP developers why this option is working fine on stock recovery and is bricking tablets on TWRP, and why it can't work correctly (or at least safe) on custom recovery, then it should be treated as a custom recovery bug.
Click to expand...
Click to collapse
Man you are right 100% wipe buton from asus MUST BE - wipe data from recovery (twrp) but I thing that twrp team is not agree with us...
Most important for me in this moment like other people I want to make table tablet alive....
BR
Mihnea

quidrick said:
a) Because it's official method to do factory reset, recommended by ASUS when you have problems with your tablet. It is working perfectly fine on stock recovery and some users are used to do this that way.
b) Because it's quite easy to do this by mistake, when you are trying to enter recovery. Please, give me fast and honest answer without checking - which button changes option, and which enters selected option?
My tablet is perfectly fine, running TWRP and custom ROM, but someone has to defend users who used wipe data.
Unless we hear sensible explanation from one of TWRP developers why this option is working fine on stock recovery and is bricking tablets on TWRP, and why it can't work correctly (or at least safe) on custom recovery, then it should be treated as a custom recovery bug.
Click to expand...
Click to collapse
You guys aren't getting my point at all. I'm not saying that the wipe data option screwing people's tablets up is right. All I'm saying is that the info is here in this forum saying not to do it. Lol If the time is taken to read the info in these threads we wouldn't even have this thread. :thumbup:
If myself and all the other people have been able to find this information and avoid tapping the wrong wipe data option then so should other people. THAT IS MY POINT.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2

At this point it really does not matter who is and who is not, right ... matter to be able to start and run ok tablets ...
So I expect all of which can give you an idea
BR
Mihnea

This is a question for developers more familiar with our partition layout. My working knowledge of android is limited, but I do have background in linux. If he can see his device under ADB, shouldnt it be possible for someone to do an adb pull of their system, data, bootloader, and recovery partitions for him to push to his?
The only reason I could think of that not working is if the wipe option deletes the entire partition table and they need to be repartitioned from scratch. Its either that or the Bootloader partition is getting wiped instead of the Data partition. Just bouncing ideas in my head here. It was on a kyocera zio and on gingerbread, but this was one way I was able to help restore a device.
NVflash seems capable of repartitioning the drive........ Does adb have commands to set up partitions as well?
One would also think odin should be able to help with repartitioning. There has to be a way.
-Edit-
Ok so if you DO have fastboot, you might be able to recover. Read this post !
http://forum.xda-developers.com/showthread.php?t=2236885

Something new...
We all know that in the above case is bricked tablet that starts directly in TWRP ... even if we start trying to po fastboot (volume down + power) it will start directly in TWRP
Now to answer adb shell like this:
c: \ Adb> adb devices
List of devices attached
0123456789ABCDEF recovery
But if I try to send something to it (like a touchscreen driver) see the answer and receives information
c: \ Adb> adb push 02-3011-4820.ekt / data / local / tmp /
* Daemon not running. starting it now on port 5037 *
* Successfully started daemon *
1027 KB / s (32868 bytes in 0.031s)
In other words we can send information in tablets briked .. I think now matter what name send.
I have here 2 tablets bricked (tf300tg and TF300T) and 3 functional TF300T tablet (but with broken touchscreen). The point is that I do not know what commands to send, and how to pull information from functional and tablets to the tablets who have problem
Now comes my question logic ... We can not copy anything from a 100% functional tablet and send this information to a tablet briked?? Can only boot, or recovery?

mihnea_gsm said:
in this moment I am in this point:
in this point adb recognized my tablet
C:\adb>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0123456789ABCDEF recovery
but after I want to flash blob
C:\adb>fastboot -i 0x0B05 flash system blob
< waiting for device >
BR
Mihnea
Click to expand...
Click to collapse
Have the same problem...
fastboot stock at < waiting for device >
my device boot/reboot or power on without any touch....always boot into recovery twrp ( but can´t mount and do nothing)
Any help?

Boot your tablets up into the selection screen where you can select to wipe data, fastboot, recovery or load OS. If you have updated your bootloader and firmware to 4.2 then the fastboot option disappears and now you are already in fastboot mode when when you load the selection screen. All you will need to do is plug the USB cable into your tablet and your computer will recognize this and load the ADB interface. Btw if your having problems with TWRP 2.5, simply flash back to 2.4.4.0.. which is exactly what I did.
I updated my bootloader and firmware to 4.2 ASUS stock and then flashed TWRP 2.5... I was having issues such as split screen, coudn't mount anything and when I loaded into recovery I was asked for password. I simply flashed back 2.4.4.0 JB TWRP.
I was back to normal.

anaschillin said:
I updated my bootloader and firmware to 4.2 ASUS stock and then flashed TWRP 2.5... I was having issues such as split screen, coudn't mount anything and when I loaded into recovery I was asked for password. I simply flashed back 2.4.4.0 JB TWRP.
I was back to normal.
Click to expand...
Click to collapse
No - I think this part is wrong. Do not use JB version of TWRP with bootloader version 4.2. You must use TWRP version ending in -4.2.

bwiberg said:
No - I think this part is wrong. Do not use JB version of TWRP with bootloader version 4.2. You must use TWRP version ending in -4.2.
Click to expand...
Click to collapse
OK .. to start over ... I had Asus tf 300TG firmware version 4.1.1 and I did the OTA update to 4.2.1. After that I put some revovery TWRP 2.5.0.0 (most probably was not what I had) and broke the tablet.
Now my tablet is in this variant:
C: \ adb> adb devices
adb server is out of date. killing ...
* Successfully started daemon *
List of devices attached
0123456789ABCDEF recovery
But after I want to flash blob
C: \ adb> fastboot flash system's 0x0B05 blob
<Waiting for device>
You say that I should write: openrecovery-TWRP-2.5.0.0-TF300T tablet-4.2.blob as did the OTA update to 4.2.1 right?
* But in this moment I realize WHY I broke the tablet ... because I wrote this file: openrecovery-TWRP-2.5.0.0-tf300tg-JB.blob ...
Why I wrote this? because if you look here: http://techerrata.com/browse/twrp2/tf300t he write: If you have the 4.2 official update, choose one of the files that ends with -4.2. If you choose the wrong file you may brick your tablet.
* THIS FILE NOT EXSIT: openrecovery no-TWRP-2.5.0.0-tf300tg-4.2.blob .....exist only for tf300t not for tf 300tg
I write a post at twrp blog : http://www.teamw.in/project/twrp2/97
* Now see another file: openrecovery-TWRP-2.5.0.0-TF300T-JB.img .... what to do with this file?
OK and now...
What should I do? which file should I write?
And how (mode - fastboot, apx ???) should be the tablet to write the file?
And who would command if the tablet would be in that mode (fastboot, apx)
BR
MIHNEA

quidrick said:
a) Because it's official method to do factory reset, recommended by ASUS when you have problems with your tablet. It is working perfectly fine on stock recovery and some users are used to do this that way.
b) Because it's quite easy to do this by mistake, when you are trying to enter recovery. Please, give me fast and honest answer without checking - which button changes option, and which enters selected option?
My tablet is perfectly fine, running TWRP and custom ROM, but someone has to defend users who used wipe data.
Unless we hear sensible explanation from one of TWRP developers why this option is working fine on stock recovery and is bricking tablets on TWRP, and why it can't work correctly (or at least safe) on custom recovery, then it should be treated as a custom recovery bug.
Click to expand...
Click to collapse
I have nothing to do with twrp and certainly am no dev.
What I do know is the partition for recovery is a limited space and there is not enough room to emulate stock recovery and still have enough space to provide for the way we use twrp.
The "factory reset" recommended by Asus is located in settings. This is "wipe data" located in the bootloader. I have not heard or read of Asus suggesting use of wipe data but I have seen factory reset.
Now I don't believe in flaming anyone!
Explaining a mistake is positive, it helps the user know what not to do in the future but only if presented properly.
I'm sure the reply came from frustration of wanting to help but understanding that recoveries from wipe data are few.
No one wants to see a brick!
Sorry for taking space without providing any help for the OP!
If anyone has any suggestions for the OP please present them.
I was so slow posting I see help has arrived.

[Q] Do I have a custom ROM and is it potentially causing my battery charging problem?

Hello, I'm a new owner of the AT&T HTC One X(L), purchased just yesterday from a previous owner. I'll try and make this thorough.
The problem is, I'm having a really hard time charging the device today after I let the battery drain all the way down from yesterday from when I purchased it. I've tried charging via USB to my laptop, directly to the wall, while its shut down, sleeping/idle, etc.. and nothing seems to get it charging quick at all. I'm using the stock HTC charger it came with, the previous owner had everything in the box and it's in great cosmetic condition.
The phone does charge some, but it was literally struggling to get between 20% and 35% for most of the day, and then later increased to 50% only to then drop back down again. And I haven't been using it at all, it's just sitting there trying to charge. How long should it reasonably take to charge this phone using the wall adapter?
Is there any chance the installed Android software (is there a custom ROM on the phone perhaps?) is causing this problem? The battery usage report says that 72% has been due to Android.. is that abnormally high by chance?
I've disabled all syncing, WiFi, screen brightness is on low, airplane mode, etc. In fact, the phone isn't even activated yet on my carrier. I've only used it thus far for WiFi at home, the browsing speed of which I'm happy with.
Some other stuff...
Recovery/bootloader reads:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26,2012
On the prior screen it also says "This build is for development purposes only, do not distribute outside of HTC, etc.." and then there's this little flashing "T" logo on the next white screen which shows up briefly before the phone boots up.
Any help would be much appreciated! Thanks for your time and patience.

You mentioned the "T" logo showing up during the boot process which leads me to believe it's running the T-Mobile Germany 4.2.2 stock ROM, which is technically a custom ROM in this context. The device should take about 3-4 hours to charge from zero to full. I personally think you've got a dodgy device. Have you contacted the seller regarding the issues you're having? Whoever had it previously didn't know what they were doing, it has a mismatched radio/firmware version for the ROM that's installed.
Sent from my Evita

timmaaa said:
You mentioned the "T" logo showing up during the boot process which leads me to believe it's running the T-Mobile Germany 4.2.2 stock ROM, which is technically a custom ROM in this context. The device should take about 3-4 hours to charge from zero to full. I personally think you've got a dodgy device. Have you contacted the seller regarding the issues you're having? Whoever had it previously didn't know what they were doing, it has a mismatched radio/firmware version for the ROM that's installed.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply. 3-4 hours from 0 to full is somewhat reassuring to hear, I assumed it wouldn't take more than an hour for some reason.
It's not the T-Mo "T" logo, it's a really different looking "T" that has a circle under it and the T flashes different colors. The T almost looks the same as the T in HTC. It only appears for a second or two and then the phone boots up. I need to take a picture of it with another device since it didn't work when I tried screen capturing that boot screen from the phone.
Is there anything else you can confirm one way or another from the info I've provided?
- So this isn't a different 3rd party custom ROM, just possibly one from T-Mo eventhough it's a branded ATT phone?
- Is this bootloader "unlocked" and is that why it says that and "tampered"? From what I've read, that's the standard msg it gives when that's the case, but isn't necessarily a red flag. Am I mistaken in my understanding though?
- Is 72% battery usage allocated to Android too high? If so, what should it be?
- Should I just try factory resetting it from the recovery screen?

droydr said:
Thanks for the reply. 3-4 hours from 0 to full is somewhat reassuring to hear, I assumed it wouldn't take more than an hour for some reason.
It's not the T-Mo "T" logo, it's a really different looking "T" that has a circle under it and the T flashes different colors. The T almost looks the same as the T in HTC. It only appears for a second or two and then the phone boots up. I need to take a picture of it with another device since it didn't work when I tried screen capturing that boot screen from the phone.
Is there anything else you can confirm one way or another from the info I've provided?
- So this isn't a different 3rd party custom ROM, just possibly one from T-Mo eventhough it's a branded ATT phone?
- Is this bootloader "unlocked" and is that why it says that and "tampered"? From what I've read, that's the standard msg it gives when that's the case, but isn't necessarily a red flag. Am I mistaken in my understanding though?
- Is 72% battery usage allocated to Android too high? If so, what should it be?
- Should I just try factory resetting it from the recovery screen?
Click to expand...
Click to collapse
Oh, I'm so dumb. I failed to look at your screenshots properly. The ROM that is installed is the Kickdroid ROM, which is a fully custom ROM that's based on the official Telstra release. The flashing T is the Telstra boot splash.
-Yes, if you see "unlocked" and "tampered" in your bootloader screen it means your bootloader is unlocked and you have root privileges. That's totally normal for a modified device.
-Under normal circumstances that amount of usage attributed to Android System world be considered high, but it all depends on how the phone is being used. If it's only been charging and nothing else has been active then I wouldn't worry very much.
-Under no circumstances should you ever perform a factory reset from the bootloader, it will corrupt your sd card. A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader. At this stage I don't think you should perform a factory reset until we've determined what you want from the device.
What would you like to get out of this device? Are you wanting to use custom ROMs or do you want to return it to stock?
Sent from my Evita

timmaaa said:
Oh, I'm so dumb. I failed to look at your screenshots properly. The ROM that is installed is the Kickdroid ROM, which is a fully custom ROM that's based on the official Telstra release. The flashing T is the Telstra boot splash.
-Yes, if you see "unlocked" and "tampered" in your bootloader screen it means your bootloader is unlocked and you have root privileges. That's totally normal for a modified device.
-Under normal circumstances that amount of usage attributed to Android System world be considered high, but it all depends on how the phone is being used. If it's only been charging and nothing else has been active then I wouldn't worry very much.
-Under no circumstances should you ever perform a factory reset from the bootloader, it will corrupt your sd card. A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader. At this stage I don't think you should perform a factory reset until we've determined what you want from the device.
What would you like to get out of this device? Are you wanting to use custom ROMs or do you want to return it to stock?
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply.
- Ok cool. I searched online for the Telstra logo and their T logo is for sure the one that I'm seeing. I'm assuming you don't suspect this to be the cause of the charging issue.
- So the device is unlocked and rooted, sounds fine as long as it isn't the source of the problem.
- I know this is a dumb question, but is there an ideal way for the phone to be charged? Does it need to be shut down completely for it to charge the fastest or even fully? Or can it be sleeping/idling and charge at the same rate? I've read about a variety of battery draining issues with respect to the HOX, but most are centered around WiFi and LTE uses where people were getting connected and disconnected which then caused a massive drain and bad overheating. I've yet to read something specifically about incredibly slow charging however.
My goals with this device:
- Just for it to function well and do the basics, I'm a very simple user.. calls, texts, and mild data use. I want to be able to charge it nightly within that 3-4 hour estimate and don't want any major battery issues and overheating. Today is literally my first full day with it and the first thing I needed to do was charge it, so I feel stuck at the beginning until this is resolved.
- I want to activate it on a wireless plan so it can really become my new phone, but I don't want to start this process if there's a permanent hardware or software issue with the device.
- I don't need to be on any custom ROM or on kitkat. I'm not a developer or anywhere close to being an Android wizard. I read that 4.2.2 is the last official update the HOX will receive, so I'd be absolutely fine with that. Sure, running kitkat or later Android versions might be nice down the road, but if it becomes clear that any custom ROM (now or in the future) is doing more damage than good, then I'd just want to be able to get it back to the 4.2.2 version HTC has released. I want to have that safety measure at bare minimum.
Under no circumstances should you ever perform a factory reset from the bootloader, it will corrupt your sd card. A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader. At this stage I don't think you should perform a factory reset until we've determined what you want from the device.
Ok thanks, I won't select the factory reset option from bootloader. However, I don't have an SD card in the phone and I don't think there's an SD slot on it unless I'm totally missing something?
I need to read about what TWRP recovery is and see if it's installed on my phone. Will need to get back to you on that once the phone has had more time to charge - I just want to let it sit undisturbed for 3-4 hours in shut down mode and see if it can increase past a 50% charge rate.
I only inquired about a factory reset thinking that it might be the safest way for me to start trying to troubleshoot the charging problem. It was just a random question I threw out there. I'm willing to do anything that could potentially improve my charging situation.
Whoever had it previously didn't know what they were doing, it has a mismatched radio/firmware version for the ROM that's installed.
- After reviewing my screenshots again, do you feel this is still the case? Is there mismatched software and radios afterall? And if so, would the factory reset via TWRP be one of your first suggestions to try and fix it?
- Do you think such mismatching software could potentially be the cause of its slow battery charging?
- Finally, is there any way for me to check to see if the battery itself is in good shape or faulty? Is there an app you could recommend I download where it can give me a detailed performance report which I could then share the results?
Thank you so much for your time, help, and continued patience.. it means a lot!

droydr said:
Thanks for the reply.
- Ok cool. I searched online for the Telstra logo and their T logo is for sure the one that I'm seeing. I'm assuming you don't suspect this to be the cause of the charging issue.
- So the device is unlocked and rooted, sounds fine as long as it isn't the source of the problem.
- I know this is a dumb question, but is there an ideal way for the phone to be charged? Does it need to be shut down completely for it to charge the fastest or even fully? Or can it be sleeping/idling and charge at the same rate? I've read about a variety of battery draining issues with respect to the HOX, but most are centered around WiFi and LTE uses where people were getting connected and disconnected which then caused a massive drain and bad overheating. I've yet to read something specifically about incredibly slow charging however.
Click to expand...
Click to collapse
The phone should charge fine while powered on, in fact I probably would recommend that because that way you can periodically check the progress. The slow charging could be due to a faulty battery or charger, not usually by a ROM though. The fact that it's unlocked should have absolutely nothing to do with it.
My goals with this device:
- Just for it to function well and do the basics, I'm a very simple user.. calls, texts, and mild data use. I want to be able to charge it nightly within that 3-4 hour estimate and don't want any major battery issues and overheating. Today is literally my first full day with it and the first thing I needed to do was charge it, so I feel stuck at the beginning until this is resolved.
- I want to activate it on a wireless plan so it can really become my new phone, but I don't want to start this process if there's a permanent hardware or software issue with the device.
- I don't need to be on any custom ROM or on kitkat. I'm not a developer or anywhere close to being an Android wizard. I read that 4.2.2 is the last official update the HOX will receive, so I'd be absolutely fine with that. Sure, running kitkat or later Android versions might be nice down the road, but if it becomes clear that any custom ROM (now or in the future) is doing more damage than good, then I'd just want to be able to get it back to the 4.2.2 version HTC has released. I want to have that safety measure at bare minimum.
Click to expand...
Click to collapse
You can leave Kickdroid on the phone, it will serve your needs and then some. However, you do need to do a little work to get the firmware up to date. You'll need to get s-off, which can be done pretty easily using the Rumrunner method. Then you need to flash the 2.15 firmware found in the beginning of this thread. You will need adb/fastboot installed on your PC, the easiest way is to Google search "minimal adb and fastboot", the first result will be the thread you're looking for. In order for adb/fastboot to work you need HTC drivers installed on your PC too, you can get those by installing HTC Sync Manager.
Under no circumstances should you ever perform a factory reset from the bootloader, it will corrupt your sd card. A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader. At this stage I don't think you should perform a factory reset until we've determined what you want from the device.
Ok thanks, I won't select the factory reset option from bootloader. However, I don't have an SD card in the phone and I don't think there's an SD slot on it unless I'm totally missing something?
Click to expand...
Click to collapse
There is no physical sd card slot. When people refer to the sd card we mean the virtual sd card (or internal storage).
I need to read about what TWRP recovery is and see if it's installed on my phone. Will need to get back to you on that once the phone has had more time to charge - I just want to let it sit undisturbed for 3-4 hours in shut down mode and see if it can increase past a 50% charge rate.
I only inquired about a factory reset thinking that it might be the safest way for me to start trying to troubleshoot the charging problem. It was just a random question I threw out there. I'm willing to do anything that could potentially improve my charging situation.
Click to expand...
Click to collapse
TWRP is a custom recovery that can be used for various tasks. You can make a full backup of your current system, you can restore a backup you've made. You can wipe the entire system (a task that takes place prior to flashing a ROM), or just parts. You can install a ROM, kernel, radio, or various other things.
Whoever had it previously didn't know what they were doing, it has a mismatched radio/firmware version for the ROM that's installed.
- After reviewing my screenshots again, do you feel this is still the case? Is there mismatched software and radios afterall? And if so, would the factory reset via TWRP be one of your first suggestions to try and fix it?
Click to expand...
Click to collapse
A factory reset won't help that issue, a factory reset basically removes all user data from the device. The mismatch is happening at a much lower level and can only be remedied by flashing the 2.15 firmware I mentioned above.
- Do you think such mismatching software could potentially be the cause of its slow battery charging?
Click to expand...
Click to collapse
No, I don't believe that is the case. Have you tried using a different charger and/or cable? It might be the charger that's the issue. You should only charge from an AC outlet as charging via usb from a PC or the like takes longer due to restrictions on the output.
- Finally, is there any way for me to check to see if the battery itself is in good shape or faulty? Is there an app you could recommend I download where it can give me a detailed performance report which I could then share the results?
Thank you so much for your time, help, and continued patience.. it means a lot!
Click to expand...
Click to collapse
I'm not familiar with any apps myself but I know there are many that claim to be able to report the health of the battery.
Sent from my Evita

timmaaa said:
You can leave Kickdroid on the phone, it will serve your needs and then some. However, you do need to do a little work to get the firmware up to date. You'll need to get s-off, which can be done pretty easily using the Rumrunner method. Then you need to flash the 2.15 firmware found in the beginning of this thread. You will need adb/fastboot installed on your PC, the easiest way is to Google search "minimal adb and fastboot", the first result will be the thread you're looking for. In order for adb/fastboot to work you need HTC drivers installed on your PC too, you can get those by installing HTC Sync Manager.
Click to expand...
Click to collapse
Thanks again for the reply and all the detail. This section appears to be my 'to do' list but I've been going around in circles with it for a few hours now with no results. The first problem is that Sync Manager on my computer won't recognize my device, it says no phone is plugged in yet my computer makes that alert sound when something new is connected via USB. I'm on a new Windows 8.1 laptop and can't figure it out for the life of me. Apparently this is an issue for others, as I've found out by cross reading HTC and Android forums about it. I don't know if there's some setting on the HOX itself I'm missing in order to start the sync process with my laptop or if it's a Windows issue, but I'm not getting anywhere.
I've read and followed the other pages you listed as well to do the S-off, ADB and fastboot, and ultimately the 2.15 firmware update, but even the 2nd step (S-off) fails because I can't get the darn Sync Mgr to work.
At this point, I would just like to get it back to how it was when the device was opened for the first time with Android 4.0.3. This is an AT&T branded phone for the USA, I don't want it to have anything to do with Telstra or Australian regions. I don't want any kind of custom ROM, radios, kernels, etc.
If I'm understanding you correctly, I can't factory reboot this to the way it originally came out of the box. By it being unlocked and rooted with technically a custom ROM, apparently it's past the point of no return.. I either get it to work via custom ROM or it'll be stuck as is.
I just want it to be true stock. And then once I'm comfortable with that and it's hopefully functioning better, I can then update it to the next Android releases that come directly from ATT. It's crazy how impossible that seems to achieve at this point.

droydr said:
Thanks again for the reply and all the detail. This section appears to be my 'to do' list but I've been going around in circles with it for a few hours now with no results. The first problem is that Sync Manager on my computer won't recognize my device, it says no phone is plugged in yet my computer makes that alert sound when something new is connected via USB. I'm on a new Windows 8.1 laptop and can't figure it out for the life of me. Apparently this is an issue for others, as I've found out by cross reading HTC and Android forums about it. I don't know if there's some setting on the HOX itself I'm missing in order to start the sync process with my laptop or if it's a Windows issue, but I'm not getting anywhere.
I've read and followed the other pages you listed as well to do the S-off, ADB and fastboot, and ultimately the 2.15 firmware update, but even the 2nd step (S-off) fails because I can't get the darn Sync Mgr to work.
At this point, I would just like to get it back to how it was when the device was opened for the first time with Android 4.0.3. This is an AT&T branded phone for the USA, I don't want it to have anything to do with Telstra or Australian regions. I don't want any kind of custom ROM, radios, kernels, etc.
If I'm understanding you correctly, I can't factory reboot this to the way it originally came out of the box. By it being unlocked and rooted with technically a custom ROM, apparently it's past the point of no return.. I either get it to work via custom ROM or it'll be stuck as is.
I just want it to be true stock. And then once I'm comfortable with that and it's hopefully functioning better, I can then update it to the next Android releases that come directly from ATT. It's crazy how impossible that seems to achieve at this point.
Click to expand...
Click to collapse
I should have been more clear, you don't actually want Sync Manager to work, you only wanted to install that to get the drivers. Your main obstacle is actually Windows 8.1, it isn't compatible with fastboot drivers. If you can get access to a PC with a lower version of Windows you should be fine. Then getting s-off should be pretty easy.
Kickdroid doesn't really have anything to do with the Australian region or Telstra as such. The dev merely used a Telstra ROM as a base to build Kickdroid onto.
Are you sure you actually want an at&t release? You may not be aware but at&t releases actually have features that are missing and deliberately broken. That's the only difference between running an at&t ROM and a non at&t ROM, you'll be missing features.
You can easily flash a ROM that is an earlier Android version without having to update the firmware on the device. You don't have to go back to ICS, anything that's from 4.0 up to and including 4.1 will be perfectly fine without any further modification. Have a look through our Android Development section and find one you think will suit you. There are plenty of ROMs in our development section that range from completely stock to customised. That's about as close to stock as you can get without getting s-off first.
Sent from my Evita

timmaaa said:
A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader.
Click to expand...
Click to collapse
I forgot to mention that I checked on this. When I selected Recovery from the bootloader screen, it took me to ClockworkMod Recovery v6.0.4.6 which I imagine you're familiar with in one way or another. It has 7 different options from its menu.. "reboot system now, install zip, wipe data/factory reset, wipe cache partition, backup and restore, mounts and storage, advanced". After researching it, I know it's a different app than TWRP so I didn't do anything with it per your advice.

You can use CWM if you want to, TWRP is better but it's entirely up to you. You can easily change by using this app:
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Sent from my Evita

timmaaa said:
Kickdroid doesn't really have anything to do with the Australian region or Telstra as such. The dev merely used a Telstra ROM as a base to build Kickdroid onto.
Click to expand...
Click to collapse
Thanks for clearing that up. So it makes no difference if I have a Telstra or ATT logo on boot up. It just threw me for a loop is all because when you asked about it initially, I started thinking.. "yeah, why doesn't it have the ATT logo and does that have anything to do with my charging problem?"
timmaaa said:
Are you sure you actually want an at&t release? You may not be aware but at&t releases actually have features that are missing and deliberately broken. That's the only difference between running an at&t ROM and a non at&t ROM, you'll be missing features.
Click to expand...
Click to collapse
No, I'm not sure at all, that's why this is such a guessing game for me at this point. I'm just thinking that if I can just get things back to 'stock' first, then later I can move on and get involved in the custom ROM stuff if it sounds promising.
Ideally, I want to have freedom with my device and not be at the mercy of any carrier.. that's what interests me about Android to begin with, but right now I'm a little weary of what may be going on with my 'new' HOXL.
timmaaa said:
You can easily flash a ROM that is an earlier Android version without having to update the firmware on the device. You don't have to go back to ICS, anything that's from 4.0 up to and including 4.1 will be perfectly fine without any further modification. Have a look through our Android Development section and find one you think will suit you. There are plenty of ROMs in our development section that range from completely stock to customised. That's about as close to stock as you can get without getting s-off first.
Click to expand...
Click to collapse
Thanks, I will look at that section next. I like the idea that I can potentially get back to something earlier right now even with my current situation. I've been focused on trying to do all the steps you outlined yesterday to fix what I have currently. Of course I would like to be on the 'latest' ROM that makes the HOXL run most efficiently, but perhaps baby steps to start off with would be best.
My goal right now is to simply make sure all my software, firmware, radios, kernels match up. What you said in the beginning about my phone currently being mis-matched really stood out to me and I badly want to fix that. Logically, I absolutely must have a stable, synchronized OS at bare minimum.

droydr said:
Thanks for clearing that up. So it makes no difference if I have a Telstra or ATT logo on boot up. It just threw me for a loop is all because when you asked about it initially, I started thinking.. "yeah, why doesn't it have the ATT logo and does that have anything to do with my charging problem?"
No, I'm not sure at all, that's why this is such a guessing game for me at this point. I'm just thinking that if I can just get things back to 'stock' first, then later I can move on and get involved in the custom ROM stuff if it sounds promising.
Ideally, I want to have freedom with my device and not be at the mercy of any carrier.. that's what interests me about Android to begin with, but right now I'm a little weary of what may be going on with my 'new' HOXL.
Thanks, I will look at that section next. I like the idea that I can potentially get back to something earlier right now even with my current situation. I've been focused on trying to do all the steps you outlined yesterday to fix what I have currently. Of course I would like to be on the 'latest' ROM that makes the HOXL run most efficiently, but perhaps baby steps to start off with would be best.
My goal right now is to simply make sure all my software, firmware, radios, kernels match up. What you said in the beginning about my phone currently being mis-matched really stood out to me and I badly want to fix that. Logically, I absolutely must have a stable, synchronized OS at bare minimum.
Click to expand...
Click to collapse
The mismatch I mentioned earlier exists only for 4.2.2 ROMs, basically any 4.2.2 ROM requires a certain set of firmware to be installed otherwise the phone will suffer signal losses and random reboots.
As another easier option you could just install the Beastmode Reloaded kernel, which is also a workaround for those problems. That way you can keep the ROM that's already installed and be up to date.
Sent from my Evita

timmaaa said:
The mismatch I mentioned earlier exists only for 4.2.2 ROMs, basically any 4.2.2 ROM requires a certain set of firmware to be installed otherwise the phone will suffer signal losses and random reboots.
As another easier option you could just install the Beastmode Reloaded kernel, which is also a workaround for those problems. That way you can keep the ROM that's already installed and be up to date.
Sent from my Evita
Click to expand...
Click to collapse
I found this thread, I assume this is what you're talking about?
http://forum.xda-developers.com/showthread.php?t=2165880
I see on page 73 the link for the 3.5 version. Now I need to figure out how to install this. Do I first DL something onto my computer and then send it to the phone somehow with the USB cable, or am I suppose to do this directly on the HOXL? I've never flashed or installed anything like this before. I'll I've done thus far is install some apps from Google Play.

Yes that's the right one. You can download it directly to the phone, or download it to the PC and transfer it to the phone.
If downloading it to your PC and using TWRP recovery, you can connect your phone to the PC using a usb cable, select mount from the TWRP main menu, then select mount usb storage and your phone will show up as a removable drive on your PC. Copy the file across, eject the removable drive, unmount usb storage from the phone screen and then you can install.
Go back to the TWRP home screen and select install, navigate to the file and select it, swipe to install (at this point an aroma installer will commence, select the options you would like, don't let it reboot system at the end), select wipe cache/dalvik, swipe to wipe, hit back, hit reboot system. Now the phone will reboot into the OS again and that's it.
Sent from my Evita

timmaaa said:
Yes that's the right one. You can download it directly to the phone, or download it to the PC and transfer it to the phone.
If downloading it to your PC and using TWRP recovery, you can connect your phone to the PC using a usb cable, select mount from the TWRP main menu, then select mount usb storage and your phone will show up as a removable drive on your PC. Copy the file across, eject the removable drive, unmount usb storage from the phone screen and then you can install.
Go back to the TWRP home screen and select install, navigate to the file and select it, swipe to install (at this point an aroma installer will commence, select the options you would like, don't let it reboot system at the end), select wipe cache/dalvik, swipe to wipe, hit back, hit reboot system. Now the phone will reboot into the OS again and that's it.
Sent from my Evita
Click to expand...
Click to collapse
I downloaded the 3.5 zip file from page 73 directly to my phone.
And then I followed your install instructions exactly and now my phone keeps turning on and off without being able to boot all the way. It starts on the white "T" logo Telstra screen and then goes to the white HTC screen and then turns off again. It's been doing this nonstop for the last 20 minutes or so now. I'm assuming I have a big problem? The device is unusable at this point, it just keeps turning on and off and is getting very warm all over.

droydr said:
I downloaded the 3.5 zip file from page 73 directly to my phone.
And then I followed your install instructions exactly and now my phone keeps turning on and off without being able to boot all the way. It starts on the white "T" logo Telstra screen and then goes to the white HTC screen and then turns off again. It's been doing this nonstop for the last 10 minutes or so. I'm assuming I have a problem? The device is unusable at this point, it just keeps turning on and off.
Click to expand...
Click to collapse
There are a small number of devices for which Beastmode isn't compatible, it looks like you've lucked out and have one of those devices. Out of interest, which settings did you choose during the installer?
You can get out of the boot loop by just continuing to hold the volume down button, the next time the loop starts it should enter the bootloader.
At this point you have no choice but to flash another ROM, so I'd head to the development section I linked you to earlier and find a 4.1 ROM that you think you might like and flash that.
PS. I noticed you posted the same thing in the Beastmode thread too, duplicate posts are against the rules here on XDA.
Sent from my Evita
---------- Post added at 03:29 AM ---------- Previous post was at 03:24 AM ----------
Because you're s-on you are going to need to get access to a PC that runs a lower version of Windows, you need to have a working adb/fastboot environment. Flashing a ROM is going to require you to also flash the boot.img from the ROM zip using fastboot, this is a limitation on s-on devices with a hboot later than 1.14.
Sent from my Evita

timmaaa said:
There are a small number of devices for which Beastmode isn't compatible, it looks like you've lucked out and have one of those devices. Out of interest, which settings did you choose during the installer?
You can get out of the boot loop by just continuing to hold the volume down button, the next time the loop starts it should enter the bootloader.
At this point you have no choice but to flash another ROM, so I'd head to the development section I linked you to earlier and find a 4.1 ROM that you think you might like and flash that.
PS. I noticed you posted the same thing in the Beastmode thread too, duplicate posts are against the rules here on XDA.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply. I wasn't sure you were going to see this anytime soon, so I wanted to post it in that kernel thread as well just in case anyone was reading over there. I apologize for that.
I chose the default settings during installation.
Anyway, I've been holding down the volume button now for the last few minutes and it's not entering bootloader. The loop continues.

There's no other way to get to the bootloader apart from holding volume down or trying the volume down + power combination. I also added a little to my previous post which you'll need to read.
Sent from my Evita

timmaaa said:
There's no other way to get to the bootloader apart from holding volume down or trying the volume down + power combination. I also added a little to my previous post which you'll need to read.
Sent from my Evita
Click to expand...
Click to collapse
I saw the added parts, thanks. Problem is, this forum isn't allowing me to post or edit my previous posts until 5 mins have past, so it's a struggle trying to communicate.
I've also edited my post in the beastmode thread.
Anyway, I finally got into bootloader with the volume + power combo. Feels good to at least achieve that.
FYI, my bootloader screen looks the same as when I first got the phone a few days ago. Just wanted to include this info here.
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26,2012

Just curious, now that I'm in bootloader, would it do me any good if I selected Recovery so it can then take me to Clockwork? And from there I could try rebooting? Or one of the other menu options?
At this point you have no choice but to flash another ROM, so I'd head to the development section I linked you to earlier and find a 4.1 ROM that you think you might like and flash that.
Because you're s-on you are going to need to get access to a PC that runs a lower version of Windows, you need to have a working adb/fastboot environment. Flashing a ROM is going to require you to also flash the boot.img from the ROM zip using fastboot, this is a limitation on s-on devices with a hboot later than 1.14.
Click to expand...
Click to collapse
I've found this ROM which looks fine. I'm not picky. I'd be happy with anything as long as it can get my device to function again.
http://forum.xda-developers.com/showthread.php?t=2244445
If there's a better 4.1 ROM you'd like to suggest, please feel free to do so.