Database Info

HELP!! No Android Recovery option

Hey Everyone,
Im new to android, and having a small issue, I am attempting to root my wifi xoom, I get up to the part where its time to select android recovery so that I can select the root zip, however when I use the volume down key to scroll the options the only 3 available are NVflash, RSD and Fastboot, theres no android recovery option I have searched the forums and googled it, but I seem to be the only one with this issue, my xoom is running 3.1 and bought in Aus, dont know if this makes a difference? any help would be greatly appreciated, I have got an OTG cable and would like to mount my external HDD so I need to get it rooted. Should probably mention I have unlocked it too.
Cheers

ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!

djleez82 said:
ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!
Click to expand...
Click to collapse
Your post was already answered in the General section. No need to post twice.

The answer did not fix my problem however. Still stuck at the same place as before just like terreboo. Possibly theres an issue with this type of xoom? I bought mine in australia as well. According to my about tablet info it says this:
Firmware Configuration Version: GAS_ASIA_UCAHUBLWFRTIRD_P006 so im assuming this is an asian tab? Just wondering terreboo what does yours say under firmware configuration?

yeah sorry didnt mean to post it in the general section, I alerted it to the mods to delete they just havent got around to it yet, yeah mate I have the same version as you, although I doubt this is the reason, we cant be the only two in Aus trying to root them? I think the problem probably lies else where, it has been suggested I'm getting the timing wrong, so I'll try again and post back my progress or lack of.
---------- Post added at 10:01 PM ---------- Previous post was at 09:45 PM ----------
I have tried it 10+ times now, I'm confident its not the timing of pressing the down key on reboot having varied the length of time everytime I tried, possibly its because of the firmware version? Im at a loss, I have followed the instructions of the root guide to the letter and seem to be one of the only ones with this problem!
this is the guide im using
http://forum.xda-developers.com/showthread.php?t=1078019

Same problem here!
I have the same problem guys.. Any solution?? The developers some help??
Im using the same guide btw....
I've freaked out im trying this for 8 hours now and no results....

im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.

I did the long root method as opposed to the supposedly easier method and thank heavens I got through it unharmed. I was ****ting my pants the whole way through. I wish I were more savvy with this so I can offer help. If I were u guys I would PM the devs from TIAMAT. They are probably the most knowledgeable ppl here to ask.

solution
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom

DrGreem said:
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom
Click to expand...
Click to collapse
Would that be adb recovery reboot? Can you give more information?

assuming you have adb setup on your computer already. Plug your xoom into your comp and make sure its in debug mode. Settings-applications-development. Open a command prompt and type in "adb reboot recovery" without quotes. Your device will then reboot into recovery mode.
I will say I'm having the same issue. I flash the new recovery and I don't see it in the menu. I'm running a US wifi xoom.

okantomi said:
Would that be adb recovery reboot? Can you give more information?
Click to expand...
Click to collapse
Yes that's right. I followed the guide and i waited 3 seconds but i never had the option 'android recovery so i turned on the device and this guy told me to run this command from cmd.
So after that xoom rebooted into clockwork recovery state and i flashed thecostum rom.

According to the guide that were using, if you allow the xoom to boot fully into honeycomb it reinstalls the stock recovery, and you need to redo the process all over. Also, you need to be in honeycomb to use the ADB command, if your in fastboot it won't detect the xoom. This did not work for me. Anyone else try it?

no luck for me here either. I can flash recovery successfully (according to the prompt) no problems there. I just have the exact same trouble booting into it as above.
Vol Down key combo doesn't work and if you leave the OS to boot straight after install, CWM is replaced by stock recovery. No fun at all.
Any further news or suggestions on this?

autodc5 said:
im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.
Click to expand...
Click to collapse
Same as my Xoom, opened a thread just for it, but no one can help

much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _

fkofilee said:
much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _
Click to expand...
Click to collapse
Just make sure that Rom Manager doesn't trick you into flashing a non-compatible updated recovery version.
In my experience it doesn't play well with the Xoom.
If all you want is a non manual way to boot into recovery from the OS, download Quick Boot (if rooted) or if you're already on the Tiamat Moray Rom, it's something you can choose when you press the power button on the back.

the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?

aussiechris said:
the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?
Click to expand...
Click to collapse
Look, this is how I had to flash CWM image file- through adb,/fastboot just like you. No matter what you say, it comes down to a question of timing.

I'm not sure about everyone else with the no recovery option, but timing just isnt the issue for me. Without a lie i've tried to enter recovery over 50 times at various points, 95% of those attempts were at the 3 second mark that is stated in the xda guide we've been using. I'm aware of one other person here whos tried it MUCH more than me with exactly the same result.
However theres one thing that we could narrow it down with. Thus far the people having this issue are using the asian firmware xoom's. Could everyone else having this problem on this thread say whether or not theyre using the asian firmware too? Maybe the asian firmware can't be rooted this way?

Rom Manager says 2.3.3 V20d is old baseband

I am stuck in a strange problem. I have LG P500 which i have rooted with superoneclick and it is rooted now. I have 2.3.3 V20d (India) which i upgraded a year back.
Now the problem is that according to everyone mine is a new baseband but when i use Rom Manger to install custom recovery it shows my phone but in brackets it says 'old BB'..There were just two options,one was my phone and the other to click the box down if my device is not shown in the above list. I am stuck as can't find any solution and i am a newbie.I did ask some senior members and contributors/devs and waiting for the help,so i thought i will post it here also in case someone has faced this problem before.
Screen capture attached as well.....Just do not know where to go from here.Thanks a lot
MORE INFO: I just downloaded XDA ASSISTANT app to check and in software section it mentions about baseband also. The reading is: V07u-000-000 (MAR-23-2009). Can't say if it is of any help

kitu34 said:
I am stuck in a strange problem. I have LG P500 which i have rooted with superoneclick and it is rooted now. I have 2.3.3 V20d (India) which i upgraded a year back.
Now the problem is that according to everyone mine is a new baseband but when i use Rom Manger to install custom recovery it shows my phone but in brackets it says 'old BB'..There were just two options,one was my phone and the other to click the box down if my device is not shown in the above list. I am stuck as can't find any solution and i am a newbie.I did ask some senior members and contributors/devs and waiting for the help,so i thought i will post it here also in case someone has faced this problem before.
Screen capture attached as well.....Just do not know where to go from here.Thanks a lot
Click to expand...
Click to collapse
and yes that is your phone lg p500 old bb, it doesn't matter, RomManager doesn't discover your phone, it is just a list that you have to choose
from

Are you sure?
grigtm said:
and yes that is your phone lg p500 old bb, it doesn't matter, RomManager doesn't discover your phone, it is just a list that you have to choose
from
Click to expand...
Click to collapse
Are you sure it doesn't matter? But why would Rom Manager mention that? That means it is misleading the user and the user can think esp a newbie that his is a old baseband therefore he will not go with the new baseband and land in trouble.

More Info In Case It Is Helpful
I just downloaded XDA ASSISTANT app to check and in software section it mentions about baseband also. The reading is: V07u-000-000 (MAR-23-2009). Can't say if it is of any help

My advice: don't use Rom Manager to install a custom recovery (or even a Rom); there have been many reports of people bricking their devices that way. A safer way of installing a recovery would be to use LGMDP or adb/fastboot -- instructions should be in a sticky somewhere; I can't search for it at the moment since I'm on mobile. Anyway, good luck.
Edit: Corrected typo -- it's LGMDP.
____________________
Sent from the moon.

Thanks a lot! So kind of you
Syd_M said:
My advice: don't use Rom Manager to install a custom recovery (or even a Rom); there have been many reports of people bricking their devices that way. A safer way of installing a recovery would be to use LGDMP or adb/fastboot -- instructions should be in a sticky somewhere; I can't search for it at the moment since I'm on mobile. Anyway, good luck.
____________________
Sent from the moon.
Click to expand...
Click to collapse
OMG now i have to start all over again,and being a newbie it is not easy at all.Does rooting etc means spending half the time in the forum?Since yesterday my eyes and back are paining just coz of this hehehee
Ok i will check that brother,thanks a lot seriously.

On what basis you say that?
grigtm said:
and yes that is your phone lg p500 old bb, it doesn't matter, RomManager doesn't discover your phone, it is just a list that you have to choose
from
Click to expand...
Click to collapse
I mean you have encountered that or something yourself or any body else? We have to be sure otherwise the phone will be bricked or ruined and i am not a rich person,therefore god is great hehehe

kitu34 said:
OMG now i have to start all over again,and being a newbie it is not easy at all.Does rooting etc means spending half the time in the forum?Since yesterday my eyes and back are paining just coz of this hehehee
Ok i will check that brother,thanks a lot seriously.
Click to expand...
Click to collapse
Well, I know that I spent a few days reading the sticky threads before I rooted my phone, but even then I managed to softbrick it for a couple of days (though it was sort of my fault, since I was using Linux at the time and all the instructions were for Windows, so I had to improvise). You shouldn't need to read every thread, though -- just the stickies should do.
Anyway, regarding Rom Manager, there's a warning in this thread (post #2) not to use it to install a recovery since the CWM version isn't compatible with our devices. As for a recovery you should use, I strongly recommend AmonRa 3.0.6 for a stable and bugfree recovery.
Edit: Just FYI, I installed my recovery using ADB and fastboot. It was quick and easy, the hardest part was installing the LG drivers and ADB (via installing the Android SDK).
____________________
Sent from the moon.

kitu34 said:
I mean you have encountered that or something yourself or any body else? We have to be sure otherwise the phone will be bricked or ruined and i am not a rich person,therefore god is great hehehe
Click to expand...
Click to collapse
I installed my first time recovery by RomManager on O1 3 years ago, I cannot realy remember how was it but it worked, but first go to settings, apps development(or something, you are on GB) and check ANDROID DEBUGGING, now use this tool from here http://forum.xda-developers.com/showthread.php?t=1827723 all credits to shinobisoft
you can find recovery's here http://forum.xda-developers.com/showthread.php?t=1523050 this are flashable zips
or search Optimus One android develepment and original android development threads
I personaly use CWM 5.0.2.7 but my favourite is TWRP (after I'll change rom I'll go back to TWRP)
---------- Post added at 09:54 PM ---------- Previous post was at 09:35 PM ----------
RomManager doesn't suport anymore old phones like O1, that's why it appears with old bb, anyway, allot of ppl flash first time recovery with RomManager, and because it is first time, there must be some fails, not all made it first time, and RomManager is to blame ?? no, worked for me, worked for milions and for a few thousants didn't, and it depends by allot of things but in most cases the people are to blame

grigtm said:
I installed my first time recovery by RomManager on O1 3 years ago, I cannot realy remember how was it but it worked, but first go to settings, apps development(or something, you are on GB) and check ANDROID DEBUGGING, now use this tool from here http://forum.xda-developers.com/showthread.php?t=1827723 all credits to shinobisoft
you can find recovery's here http://forum.xda-developers.com/showthread.php?t=1523050 this are flashable zips
or search Optimus One android develepment and original android development threads
I personaly use CWM 5.0.2.7 but my favourite is TWRP (after I'll change rom I'll go back to TWRP)
---------- Post added at 09:54 PM ---------- Previous post was at 09:35 PM ----------
RomManager doesn't suport anymore old phones like O1, that's why it appears with old bb, anyway, allot of ppl flash first time recovery with RomManager, and because it is first time, there must be some fails, not all made it first time, and RomManager is to blame ?? no, worked for me, worked for milions and for a few thousants didn't, and it depends by allot of things but in most cases the people are to blame
Click to expand...
Click to collapse
Thanks,but what am i suppose to do with this tool? What about rom manager?Shall i go with it?I am sorry i am a newbie so you can lose patience hehehe

kitu34 said:
Thanks,but what am i suppose to do with this tool? What about rom manager?Shall i go with it?I am sorry i am a newbie so you can lose patience hehehe
Click to expand...
Click to collapse
No, don't use ROM Manager. 3 years ago when @grigtm used it, it was fine. These days, however, the CWM version in ROM Manager is incompatible with our device. You will risk bricking your phone if you use ROM Manager. Personally, I advise against it.
As for the Android Flash Recovery program that was linked earlier, I haven't used it personally, but it seems easy enough to use. Just
1. Download Android Flash Recovery
2. Install the LG drivers (it's packaged with the program in a subfolder called "USB")
3. Enable USB debugging on your phone (Settings > Applications > Development > check USB debugging)
4. Start your phone in Fastboot Mode.
5. Connect your phone to the PC.
6. Start Android Flash Recovery and follow the instructions.

Confused
Syd_M said:
No, don't use ROM Manager. 3 years ago when @grigtm used it, it was fine. These days, however, the CWM version in ROM Manager is incompatible with our device. You will risk bricking your phone if you use ROM Manager. Personally, I advise against it.
As for the Android Flash Recovery program that was linked earlier, I haven't used it personally, but it seems easy enough to use. Just
1. Download Android Flash Recovery
2. Install the LG drivers (it's packaged with the program in a subfolder called "USB")
3. Enable USB debugging on your phone (Settings > Applications > Development > check USB debugging)
4. Start your phone in Fastboot Mode.
5. Connect your phone to the PC.
6. Start Android Flash Recovery and follow the instructions.
Click to expand...
Click to collapse
This is the first step after rooting.Ok
Fastboot mode is Home + Power i just have to do that? Like in rom manager we could do backup of stock can we do all that also with this?
Actually i read at two places how to go step by step,when to backup,going into recovery and wiping & reset the phone then again into recovery and navigate to the zip file of the rom and extract.But i do not know if it is same with Android flash recovery.

New Words For Me...........OMG why i came here hehehe
Syd_M said:
Well, I know that I spent a few days reading the sticky threads before I rooted my phone, but even then I managed to softbrick it for a couple of days (though it was sort of my fault, since I was using Linux at the time and all the instructions were for Windows, so I had to improvise). You shouldn't need to read every thread, though -- just the stickies should do.
Anyway, regarding Rom Manager, there's a warning in this thread (post #2) not to use it to install a recovery since the CWM version isn't compatible with our devices. As for a recovery you should use, I strongly recommend AmonRa 3.0.6 for a stable and bugfree recovery.
Edit: Just FYI, I installed my recovery using ADB and fastboot. It was quick and easy, the hardest part was installing the LG drivers and ADB (via installing the Android SDK).
____________________
Sent from the moon.
Click to expand...
Click to collapse
Dear you mentioned 'FYI', 'ADB' & 'Fastboot'..... i just heard about them once twice but don't know what are they. I am sorry this can be irritating for you and for me as well heheehe.Only lucky people can go through this smoothly otherwise i do not think i will recommend this to anyone at least before 7 years lol. But seriously i am confused

One more important thing
Syd_M said:
No, don't use ROM Manager. 3 years ago when @grigtm used it, it was fine. These days, however, the CWM version in ROM Manager is incompatible with our device. You will risk bricking your phone if you use ROM Manager. Personally, I advise against it.
As for the Android Flash Recovery program that was linked earlier, I haven't used it personally, but it seems easy enough to use. Just
1. Download Android Flash Recovery
2. Install the LG drivers (it's packaged with the program in a subfolder called "USB")
3. Enable USB debugging on your phone (Settings > Applications > Development > check USB debugging)
4. Start your phone in Fastboot Mode.
5. Connect your phone to the PC.
6. Start Android Flash Recovery and follow the instructions.
Click to expand...
Click to collapse
I have LG United Mobile driver already installed,that is enough?

kitu34 said:
Dear you mentioned 'FYI', 'ADB' & 'Fastboot'..... i just heard about them once twice but don't know what are they. I am sorry this can be irritating for you and for me as well heheehe.Only lucky people can go through this smoothly otherwise i do not think i will recommend this to anyone at least before 7 years lol. But seriously i am confused
Click to expand...
Click to collapse
There is absolutely no need to learn all of the language, especially when you're just starting out. It's enough in the beginning to just follow instructions, and only go into the details of the Android environment later as you gain more experience. No one becomes an expert overnight, after all.
As for the terms I used... FYI simply means "for your information", nothing to do with Android at all. ADB is the Android Debug Bridge, and like the name implies, it's like the "bridge" that connects your PC to your phone. Any desktop-based program or tweaking tool that communicates with your phone most likely uses ADB (such as SuperOneClick, which you used previously). Fastboot is one of the debugging modes available on the P500. There's no need to concern yourself with exactly what it does (and explaining it in detail is beyond the scope of this post); you simply need to know how to enter that mode when the instructions call for it. Basically, what I'm saying is that you don't need to understand things in detail, you just need to follow instructions. All the instructions you need are in the stickies; for now, ignore anything else that's not there (it'll only confuse you).
The LG Mobile United driver should work. If it doesn't simply install the other drivers.

Thanks alot for the concern
Syd_M said:
There is absolutely no need to learn all of the language, especially when you're just starting out. It's enough in the beginning to just follow instructions, and only go into the details of the Android environment later as you gain more experience. No one becomes an expert overnight, after all.
As for the terms I used... FYI simply means "for your information", nothing to do with Android at all. ADB is the Android Debug Bridge, and like the name implies, it's like the "bridge" that connects your PC to your phone. Any desktop-based program or tweaking tool that communicates with your phone most likely uses ADB (such as SuperOneClick, which you used previously). Fastboot is one of the debugging modes available on the P500. There's no need to concern yourself with exactly what it does (and explaining it in detail is beyond the scope of this post); you simply need to know how to enter that mode when the instructions call for it. Basically, what I'm saying is that you don't need to understand things in detail, you just need to follow instructions. All the instructions you need are in the stickies; for now, ignore anything else that's not there (it'll only confuse you).
The LG Mobile United driver should work. If it doesn't simply install the other drivers.
Click to expand...
Click to collapse
I really appreciate your concern for the safety of my phone.Thanks a lot.
Actually i was to read and follow the instruction as you told but since yesterday i was having headache coz of this and it was severe this morning and still can't open one eye heheehe Anyway i went with the Rom Manager coz of this even though it showed my phone as old BB.It was flashed in less than a minute.Then i switchd off the phone to enter into recovery by holding down Home Button + Volume Down + Power Button(button to switch off) but phone just reboots normally,no recovery set up. The thread i am following for instructions at XDA's How to's says i should not boot into recovery from thr rom manager and use only the buttons combination. But it is not happening,can you help in this?
Thanks again

kitu34 said:
I really appreciate your concern for the safety of my phone.Thanks a lot.
Actually i was to read and follow the instruction as you told but since yesterday i was having headache coz of this and it was severe this morning and still can't open one eye heheehe Anyway i went with the Rom Manager coz of this even though it showed my phone as old BB.It was flashed in less than a minute.Then i switchd off the phone to enter into recovery by holding down Home Button + Volume Down + Power Button(button to switch off) but phone just reboots normally,no recovery set up. The thread i am following for instructions at XDA's How to's says i should not boot into recovery from thr rom manager and use only the buttons combination. But it is not happening,can you help in this?
Thanks again
Click to expand...
Click to collapse
open RomManager and it should detect if you have or no recovery, it says under flashing recovery, if not use that tool I was directing you to and flash recovery, it is a safe tested tool
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
and do not ever boot into recovery from RomManager, actually after you flashed recovery, uninstall RomManager
---------- Post added at 12:11 PM ---------- Previous post was at 12:09 PM ----------
maybe you did not pushed corectly the buttons, keep pressed home+vol down+power, after LG logo appears release power button

Stuck in fastboot mode
grigtm said:
open RomManager and it should detect if you have or no recovery, it says under flashing recovery, if not use that tool I was directing you to and flash recovery, it is a safe tested tool
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
and do not ever boot into recovery from RomManager, actually after you flashed recovery, uninstall RomManager
Click to expand...
Click to collapse
I pressed the buttons this time after the lg logo and it went in fastboot mode.What to do now?

kitu34 said:
I pressed the buttons this time after the lg logo and it went in fastboot mode.What to do now?
Click to expand...
Click to collapse
power off, boot into rom, and verify if recovery was flashed, if not do it again and not from RomManager

I just followed the instructions at XDA
grigtm said:
open RomManager and it should detect if you have or no recovery, it says under flashing recovery, if not use that tool I was directing you to and flash recovery, it is a safe tested tool
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
and do not ever boot into recovery from RomManager, actually after you flashed recovery, uninstall RomManager
---------- Post added at 12:11 PM ---------- Previous post was at 12:09 PM ----------
maybe you did not pushed corectly the buttons, keep pressed home+vol down+power, after LG logo appears release power button
Click to expand...
Click to collapse
Instructions said to hold these buttons that's it.Now i read somewhere here to do it after LG logo. Fastboot mode started, udc_start()

[Q] Moto G Stuck on Boot

Hi. I've got the Moto G and i decided to unlock the bootloader and then download CWM. That all worked fine but now when i switch my phone on, it gets stuck on the 'Motorola by Google' Logo. It seems like its frozen on there but the power button is able to function, not the volume buttons though. Ive tried RSD Lite but it's not finding my device. I'm 14 so im not very good using a terminal but any guidance would be fine. I've also tried flashing the Paranoid 4.4.4 zip, The Stock Firmware zips and even Gapps but they all come up with the same message,
finding update package
opening update package
verifying update package
Installation Aborted.
Please could any one help me out and explain what went wrong with the phone? THANKS!

How?
burrt said:
You could flash the factory image by Motorola through ADB so it resets everything, I'm sure you can find the link somewhere in the forums (I'm using the 4G version so my method may be different slightly). I found rooting my phone very intuitive from the guides, only problem I had was making sure I had administrative privileges and access in the command window directory.
If I remember correctly, this will probably remove CWM and if you insist on a third party recovery, give TWRP, the problem could be related to CWM.
Click to expand...
Click to collapse
Could you tell me exactly what to do? i dont have much experience but ive downloaded the 4.3 and 4.4.2 Retail zips, extracted them and then opened CMD and tried things such as 'fastboot flash .....zip or image'. Still doesnt work and sometimes i get 'hab' errors and 'image is too large'.

Thanks
burrt said:
I'm not too sure about your problems, were you on Stock 4.4.4 running fine? I'm going to assume you are using the Moto G 3G version.
Although I haven't personally tried this guide myself, from what I see, it is reliable:
[GUIDE] Moto G - Restore stock firmware
Just a helpful tip when you open a terminal (took me a while to figure out when I first rooted my phone), located to the folder where they wan't the terminal and hold Shift + Right Click. This will give you an option "Open command window here", look carefully. Once again, make sure you are downloading the correct files for your device and read the steps carefully, you can minimise a lot of headaches and realise some shortcuts. It is also an 'old' guide so be sure to verify links etc.
Click to expand...
Click to collapse
Thanks so much for helping but i've done that, probably over 5 times. I am on Moto G 4.4.4 and whenever i flash stuff it gives 'hab' warnings and 'invalid piv' and 'image size too big'

[Completed] [Q] HTC One X+ (AT&T) -TWRP issues/ ROM issues

First of all I did check other forums, etc. before coming here. I also spent countless hours researching the rooting process. Here is my problem:
I'm attempting to root an HTC One x+ (AT&T) that I purchased on amazon. I'm using a Windows 8.1 system, and The latest Windroid tool (v2.3). With the tool I was able to unlock bootloader. The next step (flash a recovery) is where I believe I made my mistake. For my phone there was 2 choices (global and AT&T). I hence learned that my phone is evitare-ul, so I should have used the AT&T version, but I flashed it with the Global TWRP. I also made some errors in that I somehow wiped out the stock ROM (still don't know how that happened). I posted a question in the HTC One x+ forum, and was answered by LLoir (Thank you). The response was:
"You need TWRP for the EVITAREUL and then use the sideload function to put a rom on, also you need to manually flash the boot.img in fastboot. There's no MTP for TWRP Evitareul hence the reason for sideload."
Being new to "rooting" I wasn't sure what Llior was saying, ergo all the research. OK, so I found the TWRP-evitare-ul, but it WON'T FLASH! (Via Windroid). Windroid says it worked, but there is no recovery installed. I am however able to flash and remove the "global TWRP". Lloir answer also referenced 'NO MTP for TWRP evitareul", so I assume it is indeed the global TRWP I had flashed (it does has MTP wish I can enable or disable). When "enabled" my windows computer sees my phone, when "disabled" it doesn't see anything connected. I Need Help in Finding a way to Flash the "TWRP - evitareul" onto my phone.
A related issue is that after each Flash attempt when I attempt to reboot The screen on my phone changes from the "bootloader" screen to the "htc" screen And nothing more. Windroid is waiting and waiting and waiting. I end up pressing the power and volume down button combo to get back to bootloader. With the "global TWRP" I can boot to recovery, but I am in limbo when I try to flash with the "TWRP evitareul". It never installs! I'm guessing I have a booting issue.
Based on various forum articles I believe I'm to get the "Boot.img" to flash when I exe the rom file? I really rather just have the "zip" version I can use with Windroid. I'll need guidance and help there.
As it stands right now I have unlocked bootloader and apparently have the wrong TWRP installed. I have issues with my phone being recognized by my computer, and at various times my computer states there is a problem with windroid (when phone connected via usb). Is using a windows 8.1 system an issue. I can go to my old XP
In summary I need:
1) Find a way to flash the correct TWRP into my HTC One x+
2)be able to flash a ROM (MagioRom).
3)Flash the boot/img.
Guidance and help is appreciated. At least point me in the right direction. This is why I posted here. Please excuse my ignorance. Thanks

dpsrams said:
First of all I did check other forums, etc. before coming here. I also spent countless hours researching the rooting process. Here is my problem:
I'm attempting to root an HTC One x+ (AT&T) that I purchased on amazon. I'm using a Windows 8.1 system, and The latest Windroid tool (v2.3). With the tool I was able to unlock bootloader. The next step (flash a recovery) is where I believe I made my mistake. For my phone there was 2 choices (global and AT&T). I hence learned that my phone is evitare-ul, so I should have used the AT&T version, but I flashed it with the Global TWRP. I also made some errors in that I somehow wiped out the stock ROM (still don't know how that happened). I posted a question in the HTC One x+ forum, and was answered by LLoir (Thank you). The response was:
"You need TWRP for the EVITAREUL and then use the sideload function to put a rom on, also you need to manually flash the boot.img in fastboot. There's no MTP for TWRP Evitareul hence the reason for sideload."
Being new to "rooting" I wasn't sure what Llior was saying, ergo all the research. OK, so I found the TWRP-evitare-ul, but it WON'T FLASH! (Via Windroid). Windroid says it worked, but there is no recovery installed. I am however able to flash and remove the "global TWRP". Lloir answer also referenced 'NO MTP for TWRP evitareul", so I assume it is indeed the global TRWP I had flashed (it does has MTP wish I can enable or disable). When "enabled" my windows computer sees my phone, when "disabled" it doesn't see anything connected. I Need Help in Finding a way to Flash the "TWRP - evitareul" onto my phone.
A related issue is that after each Flash attempt when I attempt to reboot The screen on my phone changes from the "bootloader" screen to the "htc" screen And nothing more. Windroid is waiting and waiting and waiting. I end up pressing the power and volume down button combo to get back to bootloader. With the "global TWRP" I can boot to recovery, but I am in limbo when I try to flash with the "TWRP evitareul". It never installs! I'm guessing I have a booting issue.
Based on various forum articles I believe I'm to get the "Boot.img" to flash when I exe the rom file? I really rather just have the "zip" version I can use with Windroid. I'll need guidance and help there.
As it stands right now I have unlocked bootloader and apparently have the wrong TWRP installed. I have issues with my phone being recognized by my computer, and at various times my computer states there is a problem with windroid (when phone connected via usb). Is using a windows 8.1 system an issue. I can go to my old XP
In summary I need:
1) Find a way to flash the correct TWRP into my HTC One x+
2)be able to flash a ROM (MagioRom).
3)Flash the boot/img.
Guidance and help is appreciated. At least point me in the right direction. This is why I posted here. Please excuse my ignorance. Thanks
Click to expand...
Click to collapse
you should continue ask your question in http://forum.xda-developers.com/htc-one-x2/help/htc-one-x-stuck-twrp-v2-8-5-0-os-t3071068
also see HOX+ Tutorial for Unlocking, Rooting & installing a custom ROM [BEGINNERS FRIENDLY ]

No reply, thread will be closed.

Anyone Wanna make $10? I'm stuck at a problem

Ok so here's the situation: I originally modded the K1 tablet years ago and completely forgot what i did, everything was fine until yesterday when for some reason it was off, when I went to turn it on it loaded into the OS but would immediately power off. I went into TWRP (version 2.8.7.0) and made a backup of my OS in that state. Dumped onto my computer (where I have a backup from 2015 as well), wiped my tablet (Dalvik Cache, System, Cache, Data) and grabbed a bunch of different ROMs from here to give a shot..... Here's where the problem is: The only bloody roms I actually got to install are Cyanogen mod from this guide:
https://forum.xda-developers.com/sh...-cyanogenmod-12-shield-tablet-lte-na-t3055043
and this stock rom from: https://forum.xda-developers.com/sh...rom-hyperstock-mra58k-shield-k1-v1-5-t3522897
however my tablet just indefinitely hung at the nvidia shield splash screen.
Honestly ive been at this for 4 hours and I just want a working tablet. I've gotten lost in firmware updates and some "blob" which i still don't fully understand. I've reached a level of frustration where i'm willing to just throw money at the problem (despite being fairly poor). If anyone wants to make $10 PM me your discord information and if you get a working OS the money is yours I'm sure we can work out some transfer or something. (preferably Lineage because I've read good things but I'll settle for a working tablet at this time)

Well after trying tg to follow the simple advice of "update TWRP" I somehow broke it and now it hangs at the nivdia screen when I try to do that too... I feel like i'm having a huge problem finding files for the original shield tablet (the one they sent out the replacement for due to the battery problem) or something because everything i touch is making this worse. I need an idiot proof step by step on how to fix this....

WhenSuddenly said:
grabbed a bunch of different ROMs from here to give a shot..... Here's where the problem is: The only bloody roms I actually got to install are Cyanogen mod
Click to expand...
Click to collapse
What happens when you try to flash other ROMs? Is there an error message (if so, what is the specific error?) or otherwise what is the result?
What ROMs did you try (other than the ones named). Were they stock based ROMs, or AOSP? If AOSP, did you flash gapps as required?
WhenSuddenly said:
I've gotten lost in firmware updates and some "blob" which i still don't fully understand.
Click to expand...
Click to collapse
Not sure what this means. Did you try to flash a stock recovery. If so, what happened, or where did you get stuck?
Or is this related to one of the custom ROMs you tried to flash?
WhenSuddenly said:
I've reached a level of frustration where i'm willing to just throw money at the problem (despite being fairly poor). If anyone wants to make $10 PM me your discord information and if you get a working OS the money is yours I'm sure we can work out some transfer or something.
Click to expand...
Click to collapse
Don't really expect or need the money. Sounds like you need it more! The whole point of these forums, is for folks to share and help each other. Most often, without the exchange of money. Many of us (myself included) have benefitted from the free contribution of others. So I'm happy to "pay it forward" and help (if I can), without compensation.
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
WhenSuddenly said:
Well after trying tg to follow the simple advice of "update TWRP" I somehow broke it and now it hangs at the nivdia screen when I try to do that too
Click to expand...
Click to collapse
What happened exactly? You tried to flash TWRP by fastboot (or otherwise?). Did it say the process was successful, or no (if there was an error message, what did it say?).
So when you try to boot to recovery, it just hangs on the logo screen? Can you still get to bootloader?
WhenSuddenly said:
I feel like i'm having a huge problem finding files for the original shield tablet (the one they sent out the replacement for due to the battery problem)
Click to expand...
Click to collapse
What kinds of files are you looking for (the lack of specifics is killing me - and my attempt to help you - can you tell?)? Custom ROMs and TWRP, there is no difference between the "pyro" original Shield tablet, and the (2nd gen) K1.

redpoint73 said:
What happens when you try to flash other ROMs? Is there an error message (if so, what is the specific error?) or otherwise what is the result?
What ROMs did you try (other than the ones named). Were they stock based ROMs, or AOSP? If AOSP, did you flash gapps as required?
Not sure what this means. Did you try to flash a stock recovery. If so, what happened, or where did you get stuck?
Or is this related to one of the custom ROMs you tried to flash?
Don't really expect or need the money. Sounds like you need it more! The whole point of these forums, is for folks to share and help each other. Most often, without the exchange of money. Many of us (myself included) have benefitted from the free contribution of others. So I'm happy to "pay it forward" and help (if I can), without compensation.
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
What happened exactly? You tried to flash TWRP by fastboot (or otherwise?). Did it say the process was successful, or no (if there was an error message, what did it say?).
So when you try to boot to recovery, it just hangs on the logo screen? Can you still get to bootloader?
What kinds of files are you looking for (the lack of specifics is killing me - and my attempt to help you - can you tell?)? Custom ROMs and TWRP, there is no difference between the "pyro" original Shield tablet, and the (2nd gen) K1.
Click to expand...
Click to collapse
Lol ok Sorry for the lacking in specifics so I'll try again from the top to answer all your questions: Regarding the ROMs I tried I just went down the list of all the popular ones on the xda form as it is presently (so Bliss, CM13, Resurrection Remix, Lineage, and a modified version of the stock rom which I can't find anymore)
when I tried to flash these through TWRP they all bounced back with an error (this was after a clean wipe). I can't elaborate further on that as I can't access TWRP any longer on the device but the only thing that said was flashed correctly was CM13. Technically speaking this CM13 should still be flashed to the device but I was getting help in a reddit post from Lineage OS (I'll link below) that gave me the advice to update TWRP to the latest version. I got the image file to install through my current TWRP and it said it was installed correctly. However when I tried to reboot my tablet into TWRP it just hung at the Nvidia screen. It also does this when I try to access the OS which should be running CM13. So to recap when in the recovery menu whenever I access OS or bootloader I just get it hanging on the Nvidia screen, and when I hit fastboot it just takes me back to the same 4 option menu. On my PC end (running windows 7) when I plug in the tablet I can see fastboot in device manager but I tried accessing it through the command menu and couldn't find the device.
Sorry for the brief spastic posting I got very frustrated the other day with the tablet but can now look at it with fresh eyes.
Link to the reddit: https://www.reddit.com/r/LineageOS/...d_tablet_original_lineage_failing_to/eh71q5t/

WhenSuddenly said:
the only thing that said was flashed correctly was CM13. Technically speaking this CM13 should still be flashed to the device but I was getting help in a reddit post from Lineage OS (I'll link below) that gave me the advice to update TWRP to the latest version. I got the image file to install through my current TWRP and it said it was installed correctly. However when I tried to reboot my tablet into TWRP it just hung at the Nvidia screen. It also does this when I try to access the OS which should be running CM13.
Click to expand...
Click to collapse
Updating TWRP is good advice. Some of the newer ROMs will often not be compatible with older versions TWRP (and can very well be the cause of the errors when flashing the ROMs). And v2.8.7 is a few years old, at this point.
When you flashed CM13, did you also remember to flash gapps (Google apps) in TWRP immediately after? This is mandatory for most AOSP type ROMs (such as CM13). And not booting to OS is an expected result after forgetting to flash gapps.
My recommendation at this point, would be to flash current version TWRP again using fastboot. Of course, you need to connect the PC by fastboot to accomplish that. Which brings us to your related issue:
WhenSuddenly said:
when I plug in the tablet I can see fastboot in device manager but I tried accessing it through the command menu and couldn't find the device.
Click to expand...
Click to collapse
So what is the exact response when you enter the command: fastboot devices
Does it just hang, or some error message (tell us the specific error message, if there is one).
Make sure your tablet is in bootloader-fastboot mode ("fastboot" should be highlighted or selected - I forget exactly what that looks like on this device, but it is sometimes portrayed with the word FASTBOOT highlighted in red, at the top of the bootloader screen).
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
WhenSuddenly said:
So to recap when in the recovery menu whenever I access OS or bootloader I just get it hanging on the Nvidia screen, and when I hit fastboot it just takes me back to the same 4 option menu.
Click to expand...
Click to collapse
I think you mean: "in the bootloader menu whenever I access OS or recovery I just get it hanging"
Without bootloader, the screen would not even come on. It would be a paperweight.

redpoint73 said:
Updating TWRP is good advice. Some of the newer ROMs will often not be compatible with older versions TWRP (and can very well be the cause of the errors when flashing the ROMs). And v2.8.7 is a few years old, at this point.
When you flashed CM13, did you also remember to flash gapps (Google apps) in TWRP immediately after? This is mandatory for most AOSP type ROMs (such as CM13). And not booting to OS is an expected result after forgetting to flash gapps.
My recommendation at this point, would be to flash current version TWRP again using fastboot. Of course, you need to connect the PC by fastboot to accomplish that. Which brings us to your related issue:
So what is the exact response when you enter the command: fastboot devices
Does it just hang, or some error message (tell us the specific error message, if there is one).
Make sure your tablet is in bootloader-fastboot mode ("fastboot" should be highlighted or selected - I forget exactly what that looks like on this device, but it is sometimes portrayed with the word FASTBOOT highlighted in red, at the top of the bootloader screen).
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
I think you mean: "in the bootloader menu whenever I access OS or recovery I just get it hanging"
Without bootloader, the screen would not even come on. It would be a paperweight.
Click to expand...
Click to collapse
Sorry for the incorrect terminology its been a while since I've been in the android modding scene.
Anyway when I access the bootloader on my tablet I get the 5 option menu of continue, fastboot protocol, recovery mode, reboot, poweroff. When I hit fastboot protocol on the menu it loops back to the same bootloader menu, I have no determinable way of telling if this is fastboot receptive or not. Now on the windows end of things this is what I'm seeing
https://drive.google.com/open?id=1zS7FjUB754iSnWal18ch4EiFtHykM0fD
(clearly seeing that I'm having trouble uploading a picture to this website you can tell how far my skill level has degraded in 5 years)

WhenSuddenly said:
When I hit fastboot protocol on the menu it loops back to the same bootloader menu, I have no determinable way of telling if this is fastboot receptive or not. Now on the windows end of things this is what I'm seeing
Click to expand...
Click to collapse
Selecting fastboot shouldn't change much, as to the appearance of the screen. It should be the same bootloader screen (with options) but should have some indication of "fastboot" being the selected mode. Usually near the top of the screen. I can't say exactly what it should look like, as I haven't used my Shield in a long time (since last summer, when I broke the screen).
If you can confirm the tablet is indeed in fastboot mode (take a photo, and post if, if you like) and still no response to the command "fastboot devices" (no quotes), then something may be wrong with the connection. Try another USB port on the computer, or try another cable.

Also, make sure you have the drivers installed on your PC (first item on the following webpage): https://developer.nvidia.com/gameworksdownload#?search=shield tablet