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?

[GUIDE] How to Root T-Mobile KitKat

Hi everyone. After scouring the forums here for hours, multiple failed attempts, and tons of misery; I've finally successfully rooted my T-Mobile G2 on 4.4.2.
As many are finding, people who have bought their G2 recently are having colorful lines whenever you try to turn on your screen when on KitKat Roms. This method fixes that (with this ROM only).
This is for people who are currently running the latest firmware (D80120A_00). I assume it'll also work with newer updates, but I can't make any promises.
---
As we've all seen, IORoot does not work on 4.4.2 on Tmobile devices for some reason. To get around that, we need to downgrade our devices to stock firmware. We will be following hyelton's guide, and lrwjr1964's discovery.
--Downgrade to 4.2.2--
First, navigate to hyelton's guide. Download the 4.2.2 stock firmware, from his link. On his Storage Cow site, navigate to the TMobile G2 folder, and then download the D80120C_00.kdz file. This is our stock firmware that we will be flashing to our device. You will also need to navigate to the link to the R&D Flash tool. The file is the LGMOBILEAX file. Install the LG Mobile Support tool. Launch the tool.
Next, we will be using lrwjr1964's discovery (post 2902 in the same thread). Plug in your phone, install any drivers needed, and let it get connected. Once you're all good to go, click 'options' in the top right hand corner, and then 'upgrade recovery'. What this will do, is download the latest D80120A_00.kdz file, and install it to your phone. How the program works, is it downloads the file to your computer, then transfers the file and flashes it. What we are going to do, is interrupt that process, insert our .kdz, and let it flash for us. Pretty nifty, huh?
You'll want to watch it super closely as it downloads. As soon as it finishes, yank the usb out of your phone. (I've done this twice without consequence. I don't make any guarantees, though.) This interrupts the file transfer, and throws you an error screen. Navigate to the folder "C:\ProgramData\LGMOBILEAX' . ProgramData is a hidden folder, so you'll need to make hidden folders visible. Rename your D80120C file exactly to what the file name of the other file is. Then, copy it over. Once it's finished, replug in your phone, let it connect, and let it resume the process. When it finishes, your phone will be running 4.2.2. How sweet is that?
--Root 4.2.2--
Now, this should work just as you're used to if you've done this before. Autoprime explains how to do this really well, so take a look at his thread here
--Install TWRP--
Again, if you've done this before, you're right at home. If not, WACOMalt has a thread you should check out here Make sure you download the correct .img for your phone. The Tmobile one. There's many different methods of flashing TWRP, but using the app Flashify worked easiest for me. It's on the Google Play store, and makes flashing it a cinch.
--Install KitKat and Re-Root--
This is one step you want to be careful with. Mess this one up, and you could be back at page one. SmiLey497 has the stock rom here. Ensure you not only snag the rom itself but get the SU file in the 'attached files' section.
Copy both files onto your phone, and boot to TWRP. You can do this easily from within the Flashify app.
Within TWRP, you need to do a standard wipe. After that, flash the ROM file first, and then the SU file after. DO NOT reboot your phone in between the files. If you do, you'll have just flashed the rom you had two hours ago when you began, and still not have SU. Once you do have them both flashed, reboot your phone and you're done.
--Celebration--
Congrats!! Your phone should now be running 4.4.2, and you should have root access. Go have some fun. Watch some Community, go for a jog, take a nap, eat dinner...do something FUN! You've earned it.
-----
I hope this guide is helpful. It very possibly could not work for you, or even mess up your phone. As far as I know, only myself and lrwjr1964 has used this method. I have very limited developing knowledge, so I likely won't be able to help with any too technical problems. Still, I'll be around to help as I can.
If this works for you, comment to let others know.
The best of luck!
utesred

Exactly what I was looking for! I ended up on the G2 when my wife decided she didn't like it and I was waiting on the M8 to switch us from VZW to T-Mobile. She put it on KK in the few days she had it. I've always had HTCs and know my way around them quite well. This will go a long ways towards helping do the same on LG.
Sent from my LG-D801 using XDA Premium 4 mobile app

LOBBS said:
Exactly what I was looking for! I ended up on the G2 when my wife decided she didn't like it and I was waiting on the M8 to switch us from VZW to T-Mobile. She put it on KK in the few days she had it. I've always had HTCs and know my way around them quite well. This will go a long ways towards helping do the same on LG.
Sent from my LG-D801 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I hope it works out for you. I was looking at the M8 myself, but decided to go for the G2 last week. The battery combined with the cost was more than enough to sway me. I was surprised at how rough it was to root myself, coming from an HTC sensation and having rooted a Samsung Note 10.1 2014.
Let us know when you go for it, and how it goes for you.

utesred said:
I hope it works out for you. I was looking at the M8 myself, but decided to go for the G2 last week. The battery combined with the cost was more than enough to sway me. I was surprised at how rough it was to root myself, coming from an HTC sensation and having rooted a Samsung Note 10.1 2014.
Let us know when you go for it, and how it goes for you.
Click to expand...
Click to collapse
I'm loving the G2 so far. It was my back-up choice in case there was something I really didn't like about the M8 so I'm not exactly suffering here. My ultimate goal is to get on an AOSP ROM so I really just need to get back to JB so that I can get root and recovery.
Sent from my LG-D801 using XDA Premium 4 mobile app

Thank you sooo much! Just what the doctor ordered!
---------- Post added at 10:25 PM ---------- Previous post was at 09:54 PM ----------
18.4009 said:
Thank you sooo much! Just what the doctor ordered!
Click to expand...
Click to collapse
Dang it. Tried you method to the letter but it fails at 49% on the LG and 47% on the pc. once I reboot and factory reset it boots back into kitkat 4.4.2

18.4009 said:
Thank you sooo much! Just what the doctor ordered!
---------- Post added at 10:25 PM ---------- Previous post was at 09:54 PM ----------
Dang it. Tried you method to the letter but it fails at 49% on the LG and 47% on the pc. once I reboot and factory reset it boots back into kitkat 4.4.2
Click to expand...
Click to collapse
Damn, that's a bummer! I'm assuming that it's failing while flashing the .kdz, right?
Sorry I can't be of much help on this one. Only thing I could suggest is to try it again. Maybe something went wrong? Make sure you've got the correct files and everything. You probably already know all of that, though.
I hope it works for you the second time around...or at least, the IORoot gets updated to work with our devices soon.

Yeah something has changed since my flash to stock kitkat. When I attempt to boot into recovery it isn't there (that's why ioroot25 won't work) but anyways. I think for one reason or another I am stuck...But that being said I work 12 hour night shifts and its my last night off with nothing to do.. So will attempt this again in a few different scenarios.

Hello guys, for rooting back from 4.4.2 to 4.2.2 on a Tmobile d801, do you use the d80110c_00 kdz or the d80110g_00 kdz ? I am not sure what the differences are either.

deepac said:
Hello guys, for rooting back from 4.4.2 to 4.2.2 on a Tmobile d801, do you use the d80110c_00 kdz or the d80110g_00 kdz ? I am not sure what the differences are either.
Click to expand...
Click to collapse
I used the 'C' .kdz file.
The 'G' one is another update. It is still 4.2.2, I believe.

Use d80110c
deepac said:
Hello guys, for rooting back from 4.4.2 to 4.2.2 on a Tmobile d801, do you use the d80110c_00 kdz or the d80110g_00 kdz ? I am not sure what the differences are either.
Click to expand...
Click to collapse
To avoid issues, you must use the D80110C .kdz. Users reported screen artifacts (lines) when using D80110G.

missiveusa said:
To avoid issues, you must use the D80110C .kdz. Users reported screen artifacts (lines) when using D80110G.
Click to expand...
Click to collapse
I may be wrong, but I don't think that the screen artifacts are caused by the D80110G. Using the same process, I went to the 80110C and tried flashing various roms afterwards. I got the artifacts on every other rom, except for the KK stock rom I used above.
From what I've seen and read from other users with the artifacts, they appear only on KK roms, with certain TMobile G2s. It seems that all phones that came with 80110G or 80110A preinstalled have issues.
Of course...I could be completely mistaken. That's just what I've noticed.

Give it time, root will happen for KitKat on T-Mobile.

I hope so, I spent all day yesterday trying until I just gave up. Guess its the waiting game for me.

For anyone having trouble downgrading using the KDZ method, just use the TOT method instead. It works perfect.

2strokenut said:
For anyone having trouble downgrading using the KDZ method, just use the TOT method instead. It works perfect.
Click to expand...
Click to collapse
Can you please direct me toward a tutorial that has the TOT method? I tried to find one online but was not able to. I have a D801. The KDZ method doesn't work for me.

I've tried your method, replaced the file it was loaded onto phone and the phone is now stock in boot load. It displays T-mobile icon and keeps resetting itself.

The biggest issue I have had in this whole downgrade, root, twrp, flash, is loosing twrp. I have tried multiple ways, but every single time I upgrade to 4.4.2 I lose custom recovery.
I even flashed twrp 2.7.0.0 over 2.3.6.2, but I have had no luck.
I have yet to try Flashify, but that will be my next move. I am Loki'd out lol
Help
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
utesred said:
Hi everyone. After scouring the forums here for hours, multiple failed attempts, and tons of misery; I've finally successfully rooted my T-Mobile G2 on 4.4.2.
As many are finding, people who have bought their G2 recently are having colorful lines whenever you try to turn on your screen when on KitKat Roms. This method fixes that (with this ROM only).
This is for people who are currently running the latest firmware (D80120A_00). I assume it'll also work with newer updates, but I can't make any promises.
---
As we've all seen, IORoot does not work on 4.4.2 on Tmobile devices for some reason. To get around that, we need to downgrade our devices to stock firmware. We will be following hyelton's guide, and lrwjr1964's discovery.
--Downgrade to 4.2.2--
First, navigate to hyelton's guide. Download the 4.2.2 stock firmware, from his link. On his Storage Cow site, navigate to the TMobile G2 folder, and then download the D80120C_00.kdz file. This is our stock firmware that we will be flashing to our device. You will also need to navigate to the link to the R&D Flash tool. The file is the LGMOBILEAX file. Install the LG Mobile Support tool. Launch the tool.
Next, we will be using lrwjr1964's discovery (post 2902 in the same thread). Plug in your phone, install any drivers needed, and let it get connected. Once you're all good to go, click 'options' in the top right hand corner, and then 'upgrade recovery'. What this will do, is download the latest D80120A_00.kdz file, and install it to your phone. How the program works, is it downloads the file to your computer, then transfers the file and flashes it. What we are going to do, is interrupt that process, insert our .kdz, and let it flash for us. Pretty nifty, huh?
You'll want to watch it super closely as it downloads. As soon as it finishes, yank the usb out of your phone. (I've done this twice without consequence. I don't make any guarantees, though.) This interrupts the file transfer, and throws you an error screen. Navigate to the folder "C:\ProgramData\LGMOBILEAX' . ProgramData is a hidden folder, so you'll need to make hidden folders visible. Rename your D80120C file exactly to what the file name of the other file is. Then, copy it over. Once it's finished, replug in your phone, let it connect, and let it resume the process. When it finishes, your phone will be running 4.2.2. How sweet is that?
--Root 4.2.2--
Now, this should work just as you're used to if you've done this before. Autoprime explains how to do this really well, so take a look at his thread here
--Install TWRP--
Again, if you've done this before, you're right at home. If not, WACOMalt has a thread you should check out here Make sure you download the correct .img for your phone. The Tmobile one. There's many different methods of flashing TWRP, but using the app Flashify worked easiest for me. It's on the Google Play store, and makes flashing it a cinch.
--Install KitKat and Re-Root--
This is one step you want to be careful with. Mess this one up, and you could be back at page one. SmiLey497 has the stock rom here. Ensure you not only snag the rom itself but get the SU file in the 'attached files' section.
Copy both files onto your phone, and boot to TWRP. You can do this easily from within the Flashify app.
Within TWRP, you need to do a standard wipe. After that, flash the ROM file first, and then the SU file after. DO NOT reboot your phone in between the files. If you do, you'll have just flashed the rom you had two hours ago when you began, and still not have SU. Once you do have them both flashed, reboot your phone and you're done.
--Celebration--
Congrats!! Your phone should now be running 4.4.2, and you should have root access. Go have some fun. Watch some Community, go for a jog, take a nap, eat dinner...do something FUN! You've earned it.
-----
I hope this guide is helpful. It very possibly could not work for you, or even mess up your phone. As far as I know, only myself and lrwjr1964 has used this method. I have very limited developing knowledge, so I likely won't be able to help with any too technical problems. Still, I'll be around to help as I can.
If this works for you, comment to let others know.
The best of luck!
utesred
Click to expand...
Click to collapse
The problem I think I am having, is in the Flashing TWRP guide, the t-mobile version, even though it states ver 2.6.3.3, its actually 2.6.3.2. I can not get TWRP to stick for the life of me.
---------- Post added at 03:48 PM ---------- Previous post was at 03:41 PM ----------
tpaxadpom said:
I've tried your method, replaced the file it was loaded onto phone and the phone is now stock in boot load. It displays T-mobile icon and keeps resetting itself.
Click to expand...
Click to collapse
hold the power button down until the screen goes blank, then press and hold the power and volume rocker down. when the LG logo appears release both buttons and quickly press and hold both power and volume rocker down. This will allow a factory (hard reset) and will get you out of the boot loop.

frigginmike said:
hold the power button down until the screen goes blank, then press and hold the power and volume rocker down. when the LG logo appears release both buttons and quickly press and hold both power and volume rocker down. This will allow a factory (hard reset) and will get you out of the boot loop.
Click to expand...
Click to collapse
I've tried your method but it doesn't work. Thanks for suggestion though. I had to put the phone in download mode (volume button down and then plug the usb), then I used LGLauncher.exe to recover it. I have tried the method described by OP twice. Both times I ended up with t-mobile logo played in the infinite loop.
I've renamed t-mobile USA D80110C_00.kdz to D80120A_00.kdz and overwritten the file. In the original instructions it says D80120C_00.kdz file but I believe OP meant D80110C_00.kdz as D80120C_00.kdz is not available at the posted link.

tpaxadpom said:
I've tried your method but it doesn't work. Thanks for suggestion though. I had to put the phone in download mode (volume button down and then plug the usb), then I used LGLauncher.exe to recover it. I have tried the method described by OP twice. Both times I ended up with t-mobile logo playe in the infinity loop.
I've renamed t-mobile USA D80110C_00.kdz to D80120A_00.kdz and overwritten the file. In the original instructions it says D80120C_00.kdz file but I believe OP meant D80110C_00.kdz as D80120C_00.kdz is not available at the posted link.
Click to expand...
Click to collapse
its sort of tricky due to the weird button placement, but that method works, 100%. May have to do it multiple times. I only know this, because I have returned to stock on this device about 25 times trying to get TWRP and root to stick when upgrading to KitKat. lol

frigginmike said:
its sort of tricky due to the weird button placement, but that method works, 100%. May have to do it multiple times. I only know this, because I have returned to stock on this device about 25 times trying to get TWRP and root to stick when upgrading to KitKat. lol
Click to expand...
Click to collapse
So I've looked on the related thread post 2901 (not 2902 as it says in OP), the reset is required. I've tried your method to reset and also one mentioned here but the phone continues to stay in the boot loop. This LG G2 is a PITA to get rooted.
Never mind. You are right. I've tried again your method and it worked. Performing reset now...

[Q] Can't Unlock Bootloader?

Hi,
I am attempting to foray into flashing roms and such, and have been trying to unlock my bootloader to that end.
-Method:Official LG ADB command line
-Issue: after entering the "adb reboot oem-unlock" command, the phone simply shuts off, and the "battery-charging" icon appears.
Phone: stock unrooted LG P500h
The ADB toolkit appears to be working, at least simple commands such as "adb devices" works just fine.
What I have tried:
-with and without sim.
-directly after boot, and several hours after boot.
-semi and fully charged battery
-usb debugging mode on
-running command line as a sudo
-any combination of the above I could think of.
Everything gives the same result, what am I missing here?
I can't seem to find anything relevant to unlocking this model's bootloader on google.
Desktop based applications appear to not be an option because I use mac, and I can't seem to turn up any mac-native freeware unlockers.
Any ideas?
cheers.

cryo22 said:
Hi,
I am attempting to foray into flashing roms and such, and have been trying to unlock my bootloader to that end.
-Method:Official LG ADB command line
-Issue: after entering the "adb reboot oem-unlock" command, the phone simply shuts off, and the "battery-charging" icon appears.
Phone: stock unrooted LG P500h
The ADB toolkit appears to be working, at least simple commands such as "adb devices" works just fine.
What I have tried:
-with and without sim.
-directly after boot, and several hours after boot.
-semi and fully charged battery
-usb debugging mode on
-running command line as a sudo
-any combination of the above I could think of.
Everything gives the same result, what am I missing here?
I can't seem to find anything relevant to unlocking this model's bootloader on google.
Desktop based applications appear to not be an option because I use mac, and I can't seem to turn up any mac-native freeware unlockers.
Any ideas?
cheers.
Click to expand...
Click to collapse
The P500, and it's variants, don't have a locked bootloader, that's why it's failing. All that's needed is a custom recovery, not installed with ROM Manager ( it has the tendency to soft brick the Optimus One and variants ).

The P500, and it's variants, don't have a locked bootloader, that's why it's failing. All that's needed is a custom recovery, not installed with ROM Manager ( it has the tendency to soft brick the Optimus One and variants ).
Click to expand...
Click to collapse
ahhhh, that makes sense....
Could you point me in the direction of a guide to flashing roms on the p500 then? Most of the guides i've found so far involve a rom manager...
thanks for the reply!

cryo22 said:
ahhhh, that makes sense....
Could you point me in the direction of a guide to flashing roms on the p500 then? Most of the guides i've found so far involve a rom manager...
thanks for the reply!
Click to expand...
Click to collapse
You will need to locate a custom recovery first. Which recovery will depend on what version of Android you want to flash. For KitKat, CWM 6.0.4.6 or newer is required. For older Android versions I'd recommend CWM 5.0.2.7 Touch by @vivekkalady. ROMs are then flashed via recovery. I don't have the link available at the moment, but I'd also suggest checking out the "LG Optimus One FAQ" thread.
Sent from my LG-P769 using Tapatalk
---------- Post added at 09:27 AM ---------- Previous post was at 09:12 AM ----------
I only have a few minutes before I have to leave for work but here's some links...
General Info - LG Optimus One FAQ
Recovery Flashing without ROM Manager - Android Flash Recovery
CWM 5.0.2.7 Touch - CWM 5.0.2.7 Touch ( modified by @Notonlyeyes )
There's tons of information available here at XDA, just use the sites search feature. This should get you started in the right direction.

shinobisoft said:
You will need to locate a custom recovery first. Which recovery will depend on what version of Android you want to flash. For KitKat, CWM 6.0.4.6 or newer is required. For older Android versions I'd recommend CWM 5.0.2.7 Touch by @vivekkalady. ROMs are then flashed via recovery. I don't have the link available at the moment, but I'd also suggest checking out the "LG Optimus One FAQ" thread.
Sent from my LG-P769 using Tapatalk
---------- Post added at 09:27 AM ---------- Previous post was at 09:12 AM ----------
I only have a few minutes before I have to leave for work but here's some links...
General Info - LG Optimus One FAQ
Recovery Flashing without ROM Manager - Android Flash Recovery
CWM 5.0.2.7 Touch - CWM 5.0.2.7 Touch ( modified by @Notonlyeyes )
There's tons of information available here at XDA, just use the sites search feature. This should get you started in the right direction.
Click to expand...
Click to collapse
Much appreciated! I will read through all of that later today.

Alright, my original question has been answered, but I have another one. I'm pretty sure this qualifies as off-topic, but the question is so petty I don't think it's worth cluttering up the forum with another thread...
So....how do I root my p500?......ok, slightly more complicated than that. I'm now trying to root it, but z4root says it roots and then root checker says the phone isn't rooted, and gingerbreak gets stuck at "running exploit". I've tried both multiple times. I can't use superoneclick because I only use/have access to mac Are there any surefire methods of rooting a p500 running 2.3.3 that either work with mac, or are a standard apk file?

[Guide][How to][Root] LYF Wind 1

I just bought the LYF Wind 1 Smartphone and couldn't find a proper way to root it, so I made up my weird way, which works perfectly fine and I'm sharing it with you guys..
Steps :-
Download Wind1Root.zip (mod edit: Please use the blue download button and not the green one.)
Extract it
Enable USB Debugging and connect the phone
Run unlock.bat
Enable USB Debugging again after reset
Run root.bat
UPDATE - Recovery replaced. Touch works now. Using Redmi 2 Recovery.
For any help, watch this video
or read the noob friendly guide at - http://www.ugeeky.com/how-to-root-lyf-wind-1/

i have unlocked bootloader.....and when i execute root.bat my lyf wind 1 shows twrp but in cmd it shows no device error....i have installed fastboot and adb

If anybody know how to replace Kinguser with SuperSU...
I tried installing Supersu-me and Superuser from playstore but none worked.
Supersu doesnt open. It stucks giving a black screen.
Its happening in my LYF wind 4.
If any custom recovery working, please do reply.

This worked well on my Lyf Wind 1 well. Not it is rooted with SU, But when i boot into recovery mode the TWRP has a bug and it shows only a blur screen after swipe to unlock. I need to power of and on again...

Bro can you please provide a root method for LYF flame 1 ? It will help me a lot !!

Need stock ROM and flasher for my Wind 1
What if something goes wrong when trying something new & attractive but UNSAFE?
If it's not available, then how to backup whole stock OS present in the phone right now?

Namashkaar ,
Thanks Harkunwar for sharing with us your brilliant work.
Can you be kind enough to confirm that
Build number and Base Band LYF_LS-5010_01_05_15
Kernel ver 3.10.49-perf [email protected] #1 sun may 15 00:51:15 cst 206
Android security patch 2016-05-01
is fit and qualifies for your script cause it seems that nothing happens on my device, can you plz help me in identifying in what I might be doing wrong ?

ibm_chandan said:
Namashkaar ,
Thanks Harkunwar for sharing with us your brilliant work.
Can you be kind enough to confirm that
Build number and Base Band LYF_LS-5010_01_05_15
Kernel ver 3.10.49-perf [email protected] #1 sun may 15 00:51:15 cst 206
Android security patch 2016-05-01
is fit and qualifies for your script cause it seems that nothing happens on my device, can you plz help me in identifying in what I might be doing wrong ?
Click to expand...
Click to collapse
That thing is working on that build number, I can personally confirm that, and as far as I know, it doesn't depend on that either. Check that fastboot is working properly
---------- Post added at 08:09 PM ---------- Previous post was at 08:06 PM ----------
Harkunwar said:
I just bought the LYF Wind 1 Smartphone and couldn't find a proper way to root it, so I made up my weird way, which works perfectly fine and I'm sharing it with you guys..
Steps :-
Download Wind1Root.zip
Extract it
Enable USB Debugging and connect the phone
Run unlock.bat
Enable USB Debugging again after reset
Run root.bat
For any help, watch this video
or read the noob friendly guide at - http://www.ugeeky.com/how-to-root-lyf-wind-1/
Click to expand...
Click to collapse
Which phone's recovery did you use? I want to port the rom for wind 1

@ Akash : Thanks for your input. Would you kind enough to post a link to fastboot , as ugeeky hosting sever is down. and I dont think the fastboot that I have is working properly. My Laptop is running Windows 10 Insider Preview 10.0.14393 64 bit . I hope it is not a problem .
Thanks again.

this is not working when i start root.bat it stucks up with a blur black screen and nothing happens I had to power off the device and power it back on. but the root did not happen, pls inform me what is the problem.

LeHarkunwar, A Big Thank You for coming up with the Root !! Have got rid of a lot of crap ware and unwanted stuff.
However, the points raised by "Java Baba" and "davinashgandi" deserve some attention. There has to be a tutorial/instructions for flashing stock firmware and stock recovery in the event that things go a little awry. A link to stock firmware and stock recovery with instructions for flashing the same is necessary and would decorate this wonderful work of yours.
Secondly, the twrp recovery is not at all functional when booted into. In such a case, applying incremental updates ( This Morning there is a new 37 MB update available) can soft brick the device.
The Wind 1 community will really appreciate if you can do something about this.
Again, Many Thanks for your superb work !!!

ibm_chandan said:
@ Akash : Thanks for your input. Would you kind enough to post a link to fastboot , as ugeeky hosting sever is down. and I dont think the fastboot that I have is working properly. My Laptop is running Windows 10 Insider Preview 10.0.14393 64 bit . I hope it is not a problem .
Thanks again.
Click to expand...
Click to collapse
you can visit this thread for downloading fastboot and adb drivers:
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
---------- Post added at 03:02 PM ---------- Previous post was at 02:56 PM ----------
siddharth14 said:
LeHarkunwar, A Big Thank You for coming up with the Root !! Have got rid of a lot of crap ware and unwanted stuff.
However, the points raised by "Java Baba" and "davinashgandi" deserve some attention. There has to be a tutorial/instructions for flashing stock firmware and stock recovery in the event that things go a little awry. A link to stock firmware and stock recovery with instructions for flashing the same is necessary and would decorate this wonderful work of yours.
Secondly, the twrp recovery is not at all functional when booted into. In such a case, applying incremental updates ( This Morning there is a new 37 MB update available) can soft brick the device.
The Wind 1 community will really appreciate if you can do something about this.
Again, Many Thanks for your superb work !!!
Click to expand...
Click to collapse
Stock firmware is not modified by this method, and there's no way to backup the stock recovery until we get the factory firmware, for installing any zips to the system, you can always replace the update.zip with the file you want to flash( remember to rename the file you want to flash as update.zip) in the files folder and then run the root.bat file.

Thanks Aakash. Yes, I'm aware that this method doesn't modify stock firmware. The suggestion was made so that people with soft bricked device would be able to revert to stock firmware if anything went wrong.
As for recovery, I managed to download the stock firmware and extracted the stock recovery. I also successfully flashed the stock recovery over twrp. However, the 37 Mb update was aborted due to some mismatch. No idea how to get around this with stock recovery. Yes, it's possible over twrp like you said but I would prefer to apply it through stock recovery.
If only we had a functional custom recovery, things would be even better.
On a side note, has anybody been able to figure the rebranded model and company of Wind 1 ?
---------- Post added at 01:28 PM ---------- Previous post was at 01:15 PM ----------
Ok. I have tried flashing the downloaded update.zip via stock recovery and twrp but no success. I guess the only option left now is via sideload method. And if i'm not wrong then i would lose root if i installed it via adb sideload.
Slightly off topic, the voice Volume of Wind 1 appears low and somewhat muffled. It's not clear and loud like its in my MOTO G. Can fellow users please confirm this. I have also tried the *#4636#* code which opens the testing menu but it's of no use. Need some application or code to access the engineering menu via which we could increase the voice volume.

Hey bro,i am same version of Android on my Lyf wind 1,n I'm glad to have a solution that you came with, I want to upgrade my mobile to marshmallow(stock version), can you please instruct me how can I do that, I'll waiting 4 ur response, thank you

I humble request to help me in rooting lyf flame 2/!,
,plz plz just begging
Sent from my LS-4004 using Tapatalk

I m using windows 10 ...and when I try to open unload.bat file my Lyf wind 1 is rebooting and show android icon and stuck at there.... And cmd show's that waiting for device .....I have to open the bettry and re connect it for start my Lyf wind 1 and ... nothing happens

please can someone give me flashing tutorial for lyf wind 1 , my set is dead , its not powering on now ,

@harshad
Please ensure that you have properly installed drivers for LYF Wind 1. To check this, enable USB-Debugging and connect your LYF Wind 1 to PC. You will also get a message on your phone regarding granting authorization to your computer. Click on Yes. If you don't click on yes then you are bound to get the device not found or device offline errors !
While flashing, i got the device not found error a couple of times and i noticed that i hadn't granted authorization to my computer for USB debugging. The authorization window had popped on my mobile and i was too busy looking at my computer screen.
Now, open Device manager on your computer. Click on Scan for Hardware changes. If the drivers are not installed properly then you will see Yellow exclamation marks against your Android phone. Please install the USB drivers for LYF Wind 1. ( Google if you don't have the drivers)
You need to have;
1) ADB and Fastboot installed as Administrator
2) USB drivers for LYF Wind 1 installed
3) Allow OEM Unlocking , enabled via developer options.
4) Enable USB debugging , enabled via developer options.
If all the above things are in order then you shouldn't have any problems rooting LYF Wind 1 with Le Harkunwar's excellent tutorial.
---------- Post added at 04:19 PM ---------- Previous post was at 04:13 PM ----------
Amit2310 said:
please can someone give me flashing tutorial for lyf wind 1 , my set is dead , its not powering on now ,
Click to expand...
Click to collapse
Try a battery pull. Take out the battery and wait for 5-10 seconds. Insert the battery and now try powering up the device.

found this for stock rom installation incase something goes wrong http://giveawaytricks.in/install-stock-rom-on-lyf-wind-1-lyf-ls-5010/

Amit2310 said:
please can someone give me flashing tutorial for lyf wind 1 , my set is dead , its not powering on now ,
Click to expand...
Click to collapse
you need to download stock rom and flash that to make your phone work again. I found this site, zeon22 has also listed a site, but i found this to be more user friendly in downloading files.
http://repairmymobile.in/flash/lyf-wind-1-ls-5010-stock-rom/
---------- Post added at 04:36 AM ---------- Previous post was at 04:26 AM ----------
siddharth14 said:
Thanks Aakash. Yes, I'm aware that this method doesn't modify stock firmware. The suggestion was made so that people with soft bricked device would be able to revert to stock firmware if anything went wrong.
As for recovery, I managed to download the stock firmware and extracted the stock recovery. I also successfully flashed the stock recovery over twrp. However, the 37 Mb update was aborted due to some mismatch. No idea how to get around this with stock recovery. Yes, it's possible over twrp like you said but I would prefer to apply it through stock recovery.
If only we had a functional custom recovery, things would be even better.
On a side note, has anybody been able to figure the rebranded model and company of Wind 1 ?
---------- Post added at 01:28 PM ---------- Previous post was at 01:15 PM ----------
Ok. I have tried flashing the downloaded update.zip via stock recovery and twrp but no success. I guess the only option left now is via sideload method. And if i'm not wrong then i would lose root if i installed it via adb sideload.
Slightly off topic, the voice Volume of Wind 1 appears low and somewhat muffled. It's not clear and loud like its in my MOTO G. Can fellow users please confirm this. I have also tried the *#4636#* code which opens the testing menu but it's of no use. Need some application or code to access the engineering menu via which we could increase the voice volume.
Click to expand...
Click to collapse
I also received the update but I'm not interested in updating since my phone is running fine just now, I don't want to loose root or brick my phone while updating which will most probably be more bloatware(few more apps from reliance jio). I will wait if marshmallow arrives for flashing stock rom if it arrives (although chances are pretty slim). Meanwhile I'm working on a port of cyanogenmod for this device form Yu Yunique, the device from which harkunwar got this twrp from, but I'm still not able to resolve touchscreen driver issue. Info on this device is really limited, and i don't know anything except that this device is from zte.

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