I was always able to ADB shell into my phone after i installed the proper USB drivers as well as Pull up ADB DEVICES no problem and i SAW ADB DEVICE in my device manager
Ok i have finally got to the steps where i have flashed my sappimag.zip file to my Mytouch successfully. that ROM has been flashed and now when i boot the phone up it says VODAFONE and i can get intot he phone fully
I have turned the device off and hold the BACK and POWER button and the FASTBOOT screen comes up. i plug in the USB cable an FASTBOOT changes to FASTBOOT USB ok great.
i pull up CMD and type in ADB SHELL and it says DEVICE NOT FOUND. i type in ADB DEVICES and its blank.
I power down and power back up fully and same thing (but it was working before the flash of sappimg.zip)
i downloaded and installed HTC SYNC which supopsedly has updated XP drivers and it did.
i power down phone and power back up as normal and pull up CMD ADB SHELL works fine and ADB DEVICES shows my serial number. ok making progress.
I have turned the device off and hold the BACK and POWER button and the FASTBOOT screen comes up. i plug in the USB cable an FASTBOOT changes to FASTBOOT USB ok great.
i pull up CMD and type in ADB SHELL and it says DEVICE NOT FOUND. i type in ADB DEVICES and its blank still again.
what gives? why does this only work now with phone fully booted and not in fastboot mode?
also note my device manager no longer has ADB DEVICE anymore its gone.
adb doesn't work in fastboot mode.
edit for clarity: When you boot the phone in fastboot mode, adb isn't supposed to work. You have to boot fully, or boot into one of the recovery images that supports adb for it to work, fastboot doesn't support adb at all.
Deicist said:
adb doesn't work in fastboot mode.
edit for clarity: When you boot the phone in fastboot mode, adb isn't supposed to work. You have to boot fully, or boot into one of the recovery images that supports adb for it to work, fastboot doesn't support adb at all.
Click to expand...
Click to collapse
ok so what does this mean in the directions then? how am i supposed to perform the below directions in red then?
FLASH your T-Mobile myTouch 3G
Make sure are using fastboot from the latest SDK (release 3) !
- Power-off your device
- Insert the goldcard
- Power on while holding volume down (of fastboot your device and then press volume down)
- It should pick up the sappimg.zip and you should be able to flash it.
- Once the flashing is FULLY finished power off your device.
- Remove the goldcard and insert the SD (with update.zip)
- Power on while holding back (=fastboot) and connect the USB cable
- Download my RAv1.2.0H recovery and fastboot it :
Code:
fastboot boot recovery-RAv1.2.0H.img
it means exactly what it says:
Download the recovery image to your computer then, from your computer, run the command:
"fastboot boot recovery-image-name.img"
fastboot is a command line utility that comes with the android sdk. It allows you to push recovery images to the phone while it's in fastboot mode and boot them.
adb is used to communicate with the phone while it's running an android image, NOT while it's in fastboot mode.
Deicist said:
it means exactly what it says:
Download the recovery image to your computer then, from your computer, run the command:
"fastboot boot recovery-image-name.img"
fastboot is a command line utility that comes with the android sdk. It allows you to push recovery images to the phone while it's in fastboot mode and boot them.
adb is used to communicate with the phone while it's running an android image, NOT while it's in fastboot mode.
Click to expand...
Click to collapse
ok i understand what you mean and say BUT look at the directions and it clearly says:
POWER ON WHILE HOLDING BACK (FASTBOOT) and then CONNECT USB
when i read that it makes me thnk think literal and to hold the Back button my my device and hold power and watch it come into fas boot mode and then when itmentions connect USB it makes me think im supposed to go into ADB shell commadn and then type that command in.
so im definately not trying to argue with you just trying to get you to se my point of view on why i am confused thats all.
i really apreciate your help on this.
Deicist said:
it means exactly what it says:
Download the recovery image to your computer then, from your computer, run the command:
"fastboot boot recovery-image-name.img"
fastboot is a command line utility that comes with the android sdk. It allows you to push recovery images to the phone while it's in fastboot mode and boot them.
adb is used to communicate with the phone while it's running an android image, NOT while it's in fastboot mode.
Click to expand...
Click to collapse
ok one thing that again is confusing is that you say ADB can not recognize the phone while in fastboot mode but then you said i use the fastboot command line to push recovery images to the phone while its in fastboot mode.
how am i suppose to do that if the ADB shell (where i run the fastboot command line from) does not work if the phone is in fastboot mode (the mode it has to be in to accept recovery images)
see what i mean very confusing.
i just rebooted my phone normal. connected it to USB and went into CMD and ADB shell comes up fine
i typed in ADB SHELL
and then :
# fastboot boot recovery-RAv1.2.0H.img
and it says:
C:\>adb shell
# fastboot boot recovery-RAv1.2.0H.img
fastboot boot recovery-RAv1.2.0H.img
fastboot: not found
fastboot is different from adb........
2 different programs. adb.exe and fastboot.exe
just place the fastboot.exe file from the sdk into system32.
and try to put the recovery file in to the sdcard.
rename it to recovery.img to prevent misspelling .
Deicist said:
it means exactly what it says:
Download the recovery image to your computer then, from your computer, run the command:
"fastboot boot recovery-image-name.img"
fastboot is a command line utility that comes with the android sdk. It allows you to push recovery images to the phone while it's in fastboot mode and boot them.
adb is used to communicate with the phone while it's running an android image, NOT while it's in fastboot mode.
Click to expand...
Click to collapse
fadedmicrobe said:
fastboot is different from adb........
2 different programs. adb.exe and fastboot.exe
just place the fastboot.exe file from the sdk into system32.
and try to put the recovery file in to the sdcard.
rename it to recovery.img to prevent misspelling .
Click to expand...
Click to collapse
ok i see what it is now.
in my CMD prompt i typed in:
C:\fastboot boot recovery-RAv1.2.0H.img
and it says:
can not load 'recovery-RAv1.2.0H.img'
i have made sure that my recovery-RAv1.2.0H.img file is in C:\AndroidSDK folder where everythign else is.
currently i have my spare 4 GB card in my Device and it contains the 1.33.2005 hboot file renamed to UPDATE.ZIP
and im following the directions in red and it sjust not working
FLASH your T-Mobile myTouch 3G
Make sure are using fastboot from the latest SDK (release 3) !
- Power-off your device
- Insert the goldcard
- Power on while holding volume down (of fastboot your device and then press volume down)
- It should pick up the sappimg.zip and you should be able to flash it.
- Once the flashing is FULLY finished power off your device.
- Remove the goldcard and insert the SD (with update.zip)
- Power on while holding back (=fastboot) and connect the USB cable
- Download my RAv1.2.0H recovery and fastboot it :
copy "recovery-RAv1.2.0H.img" to C:\ (the same directory that you are running fastboot.exe from)
ok thanks everyone i got everything i wanted above.
I guess my Mytouch is now rooted? but wth a 32A radio?
i want to flash a 32B cyanogen 3.9.10 rom onto this device and using the directions below:
For Daredevils : Perform the following steps only if you want to revert to a 32B based radio and ROM.
Revert to 32B Radio and ROM :
- Download your favorite 32B ROM and copy it to your sdcard
- Download the Ion radio image from the HTC site.
- Extract radio.img from ota-radio-2_22_19_26I.zip using your favorite rar/zip program.
- Download my 32B RAv1.2.0G recovery.
- Fastboot your mobile and connect it via USB :
where it says copy your favorite ROM to your SD card well the ROM name i want is called "update-cm-3.9.10-signed.zip"
do i need to rename it to anything? or just leave it as it is?
do i literally just copy that file to my clean empty SD card no renaming to UPDATE or something like that?
Hi everybody, it's my first message here for a big promblem to solve.
First of all my Sapphire version is 32A SHIP S-ON H
I tried to install a Hero version on my Magic by following a recent tutorial.
- I tried to use ecovery-RAv1.2.0H.img (and older version) without success.
- After copying a JACxHERO version (and rename --> update.zip on the SD Card), I lauched the update with daldroid-recovery.img.
- The phone doesn't start (blocked with HTC Magic on the screen)
Problems:
- The backup I did with daldroid doesn't work
- My phone doesn't boot normally anymore
- I can't access the SD Card anymore (with Windows | Dos )
- The USB drivers are correctly installed
What is THE solution to reset the phone (by putting an original version of android on it)???
Thanks a lot for your help!
Fabrice
nextelbuddy said:
ok thanks everyone i got everything i wanted above.
I guess my Mytouch is now rooted? but wth a 32A radio?
i want to flash a 32B cyanogen 3.9.10 rom onto this device and using the directions below:
For Daredevils : Perform the following steps only if you want to revert to a 32B based radio and ROM.
Revert to 32B Radio and ROM :
- Download your favorite 32B ROM and copy it to your sdcard
- Download the Ion radio image from the HTC site.
- Extract radio.img from ota-radio-2_22_19_26I.zip using your favorite rar/zip program.
- Download my 32B RAv1.2.0G recovery.
- Fastboot your mobile and connect it via USB :
where it says copy your favorite ROM to your SD card well the ROM name i want is called "update-cm-3.9.10-signed.zip"
do i need to rename it to anything? or just leave it as it is?
do i literally just copy that file to my clean empty SD card no renaming to UPDATE or something like that?
Click to expand...
Click to collapse
"update-cm-3.9.10-signed.zip" is perfect. Copy it to the SD, but rename to update.zip JIC.
wdelisi said:
"update-cm-3.9.10-signed.zip" is perfect. Copy it to the SD, but rename to update.zip JIC.
Click to expand...
Click to collapse
thank you
With Amon_RA's RAv1.2.0 recovery you don't need to rename . I keep my favourite roms in my sd card and switch back and forth all the time
You just select (when fastbooted into recovery) Flash - Choose .zip, and you get a list with all .zip files on sd card root Sweeeet
Start asking your questions in the right sub-forum (Q&A) (Theme) or even in (General), or i will be forced to ban you for 3 days or till you learn.
Thanks
Thread Trashed!!
Related
Hi everyone,
I have looked everywhere on google and have been at this for over 5 hours now. I have tried rooting my phone from 3 different PCs (XP SP3, SP2 and 7). With all of them i have managed to get the drivers for adb installed (after many problems) and got all the way to the fastboot part of the rooting.
Once i get there, i have the same problem on all 3 PCs. ADB can no longer find my phone! Following the instructions, i checked for the device before i powered it off and found it by doing abd devices in cmd prompt. The moment the device is powered off and then back on, bam! No more device!
I am at my wits end at this point and just don't know what else I could possibly do! I would be immensely grateful for ANY advice.
I did check that my device allowed USB debug so that's not it either.
Also, my phone is a Rogers phone and I have just put through the upgrade they sent this morning.
adb cant find your phone in fastboot mode but fastboot can
Try writing fastboot devices instead of adb devices
All the comands in fastboot mode start with fastboot...e.g fastboot flash xxx xxx.img
I ran into this problem as well on my attempt, I forgot to re-enable (or enable) depending on where I was at "usb debugging" which is in:
settings> applications > development > check the usb debugging box.
After that, when you do abd devices in your shell, it should surely list after that. Good luck!
edit-- woops scratch that.. sorry I just read back that you made sure of that.
Thank you for that!
Now, i see it in fastboot, but when i try typing fastboot boot recovery.img i get a "cannot load recovery.img"
Sorry, apparently i need a lot more hand holding than i though!
(this is where I am getting the instructions from HowardForums. I'd post the link but I can't do that yet on this forum...
Basically, these are the instructions i am following:
If the phone you have is an HTC Magic (no hardware keyboard), the method is pretty much the same. I modified Haykuro's zip with files that were meant for the Magic. You can grab it here:
*link*
Again, open another command prompt as steps 2, and 6-8 are entered in the command prompt.
Quote:
Originally Posted by Haykuro-ish
0. Place update.zip on SD card.
1. power off the phone and boot into fastboot (hold back and power)
2. fastboot boot recovery.img
3 [optional]. make a backup with nandroid
3. apply update. (LET IT FINISH, DO NOT TOUCH ANYTHING UNTIL YOUR PHONE IS COMPLETELY IDLE. DO NOT TOUCH AFTER FIRST REBOOT (WHEN CHIP APPEARS) UNLESS YOU LIKE A BRICK. )
4. reboot out of recovery mode.
5. power off phone, hold back button and power to boot into fastboot again
6. fastboot flash boot boot.img
7. fastboot flash recovery recovery.img
8. fastboot reboot
enjoy!
These are pretty much the Haykuro instructions for the Dream, which I modified to apply to the Magic. The boot and recovery images were made by Amon_RA. Happy Rooting!
Just like with the Dream, the first part flashes a good SPL, the second flashes a rooted boot and recovery. The easiest way to test if the device is rooted is to open another command prompt in the tools dir and type
Code:
adb root
If it returns that adb is already running in root, then you're all set.
Click to expand...
Click to collapse
Am i doing something wrong?
Thanks so much!
You need to navigate to the folder where you saved your recovery.img
For example if you put it on d:/Android dev. you will need to do (inside cmd)
d: (switches to drive d
cd d:/Android dev. (changes the folder to android dev.)
and then issue the fastboot command
without the brackets of course...
eyegor said:
You need to navigate to the folder where you saved your recovery.img
For example if you put it on d:/Android dev. you will need to do (inside cmd)
d: (switches to drive d
cd d:/Android dev. (changes the folder to android dev.)
and then issue the fastboot command
without the brackets of course...
Click to expand...
Click to collapse
Again, thank you so much! It seems I am still having issues as now I'm being told that "remote not allow".... is this a rogers thing?
Again i do apologize for all the hand-holding necessary here
yes, i am getting this <remote:not allow> message too. I was able to fix my other magic (purchased in october) via fastboot boot recovery.img but not this new one i have (purchased in Dec).
Anyone have any ideas how to bypass this block of 'remote, not allowed"?
While trying to unlock xoom, after the 3.1 update, I'm now stuck at the Dual Core screen.
Can anyone guide me to resolution?
Thanks in Advance.
what steps did you take?
I just followed the steps of:
This will ERASE your Xoom.
1) Get the Motorola USB drivers MOTODEV > Documentation & Tools > USB Drivers (you need to sign up on their but maybe you can google this and find it as well)
2) Get the Android SDK Android SDK | Android Developers (you only really need the fastboot executable file for your host OS)
2.5) - I will soon put together a windows pack for usb drivers & fastboot so you don't have to download all this stuff just to do one task.
3) Power off your Xoom
4) Press and hold the volume down button while pressing the power button
Even after the Xoom turns back on keep it pressed down and you'll see some starting fastboot protocol text on the top left of the screen.
5) Open a command window in your sdk\tools folder (not platform tools and depending on when you get the SDK you may need to copy over some DLL files)
6) type:
fastboot oem unlock
7) read the warning on your Xoom's screen, hit volume up if you wish.
You're now free to put whatever data you want on your tablet. Cheers.
robbiev80 said:
what steps did you take?
Click to expand...
Click to collapse
Did I miss anything?
Can anyone help me get back on track?
I was able to get my xoom restore with the following steps:
: This will wipe your Xoom
You're going to need to have the Android SDK installed. You can download it here.
Download the official HRI39 build from Motorola here.
Unzip the files in MZ600_HRI39.zip and move or copy them to the /platform-tools folder in your SDK folder.
Connect your Xoom to your computer.
Type adb reboot bootloader. Wait for it to reboot into the bootloader.
Type the following commands, waiting for each to finish before continuing:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
You've now successfully flashed your Xoom back to stock. Now it's time to relock the device.
Type fastboot oem lock, wait for the menu, the press the volume-down button. Then press the volume up button. It'll take a minute or so, then reboot. You're now completely back to stock and ready for the update.
Hey folks,
I´ve ran my MZ601 xoom on EOS builds over the last 1,5 years.
Obviously its unlocked and rooted. Currently its running CWM Recovery 4.0.0.4
Now I want to go back to stock to install the latest official updates to get the updated drivers for the UMTS radio/modem module.
After that I want to unlock and get root again to use any of the lastest custom Roms again.
Switching to a touch based recovery would be nice too.
I surfed around a bit and I´m rather confused which steps I need to perform in order to do this.
I guess I need to remove root and lock the bootloader again before I can install official updates ?
Could someone please toss me in the right direction? Maybe some step-by step list?
You'll presumably want Build H.6.1-38-1 for Retail Europe from here.
Returning to stock:
Extract the files from the link above to your adb/fastboot directory if you have one. If you don't have one I've uploaded them for you here.
Connect your Xoom to your PC then open command prompt from your adb folder. (Hold shift > right click on adb-fastboot folder > click Open Command Window Here)
Type adb devices and hit enter, if no devices are listed then ensure USB debugging is switched on in Settings > Development > and tick USB Debugging, then try again.
If it still doesn't appear then download Motorola USB drivers here and try again.
If fine then run:
adb reboot bootloaderThen run the following to flash the stock image:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Flashing userdata.img is going to remove all your files so back everything up first.
This should unroot your Xoom anyway, not entirely sure if the lock is required to receive updates, but it's simple to unlock again.
Once booted and through initial setup you should receive several over the air updates. (I believe the stock image is Android 3.2)
Unlock:
Connect your Xoom again and open command window in the adb-fastboot folder as before.
Run:
adb reboot bootloader
fastboot oem unlock
fastboot rebootYou'll now be unlocked.
Install Touch Recovery and Root:
Next download ClockworkMod Touch recovery from here, rename it to just recovery.img for simplicity, and copy the image to the adb-fasboot folder.
Download Xoom Universal Root from here.
Copy that file to your sdcard.
Then run:
adb reboot bootloader
fastboot flash recovery recovery.img(assuming you renamed it)
Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Important: When you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery.
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldThen select reboot in ClockworkMod recovery and boot as normal.
If you are unable to use adb in recovery, then you can enable this through Windows by doing the following:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Finally, run:
adb reboot recoveryIf ClockworkMod touch recovery is still there then all is good!
Hopefully I've made sense! Any questions, just ask.
Repeat of downloads:
Download Motorola USB Drivers (Device Manager) here.
Download ClockworkMod Touch recovery here.
Download Xoom Universal Root here.
Wow, what a detailed guide
Thank you sir
No problem!
Let me know how it goes, hopefully shouldn't have any problems.
Resetting worked great :good:
Right now I´m in an OTA marathon
all that unlock, root and recovery stuff sounds familiar so I don´t expect any problems.
Thanks so far :good:
alecbond said:
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldThen select reboot in ClockworkMod recovery and boot as normal.
Finally, run:
adb reboot recoveryIf ClockworkMod touch recovery is still there then all is good!
Click to expand...
Click to collapse
Ok, so this is not working
after I flash touch recovery and do thta reboot thing I can enter touch recovery, thats fine.
Flashing universal root, fine.
THEN,
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
gives me error since in recovery mode there ist no adb connection
Whatever when I choose to reboot the system, recovery warns me that it will get overwritten by boot and ask me to disable this.
Shall I do this?
EDIT: Nevermind, I decided to be a little brave and just confirmed that message.
Now touch clockwork seems to be persistent and I´m a happy Xoomer again
Sorry, I had meant to reply during my lunch break.
Edit: Realised the time on the second of your posts, so wouldn't have been much help on my lunch anyway
Well I believe I just learned something new!
Either that or I'd forgotten it asked.
I assume it disables the action rather than deletes those files.
My method was just so you can use the reverse rename in future to re-enable the overwrite on boot.
In future, not that you'll necessarily ever need this information, you can enable adb in recovery through windows by doing the following
When in recovery and connected to your PC, open Device Manager, find your phone, usually under 'Other Devices'.
Then right click > Update driver > Browse my computer > Let me pick from list > Pick your phone (either one if there's two shown)
Should confirm driver installed then adb should work.
I didn't include the above previously as I couldn't remember having to do it personally.
Glad to hear all is well though!
alecbond said:
You'll presumably want Build H.6.1-38-1 for Retail Europe from here.
Returning to stock:
Extract the files from the link above to your adb/fastboot directory if you have one. If you don't have one I've uploaded them for you here.
Connect your Xoom to your PC then open command prompt from your adb folder. (Hold shift > right click on adb-fastboot folder > click Open Command Window Here)
Type adb devices and hit enter, if no devices are listed then ensure USB debugging is switched on in Settings > Development > and tick USB Debugging, then try again.
If it still doesn't appear then download Motorola USB drivers here and try again.
If fine then run:
adb reboot bootloaderThen run the following to flash the stock image:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Flashing userdata.img is going to remove all your files so back everything up first.
This should unroot your Xoom anyway, not entirely sure if the lock is required to receive updates, but it's simple to unlock again.
Once booted and through initial setup you should receive several over the air updates. (I believe the stock image is Android 3.2)
Unlock:
Connect your Xoom again and open command window in the adb-fastboot folder as before.
Run:
adb reboot bootloader
fastboot oem unlock
fastboot rebootYou'll now be unlocked.
Install Touch Recovery and Root:
Next download ClockworkMod Touch recovery from here, rename it to just recovery.img for simplicity, and copy the image to the adb-fasboot folder.
Download Xoom Universal Root from here.
Copy that file to your sdcard.
Then run:
adb reboot bootloader
fastboot flash recovery recovery.img(assuming you renamed it)
Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Important: When you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery.
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldThen select reboot in ClockworkMod recovery and boot as normal.
Finally, run:
adb reboot recoveryIf ClockworkMod touch recovery is still there then all is good!
Hopefully I've made sense! Any questions, just ask.
Repeat of downloads:
Download Motorola USB Drivers (Device Manager) here.
Download ClockworkMod Touch recovery here.
Download Xoom Universal Root here.
Click to expand...
Click to collapse
Hey, you did a great guide! Would you mind if I put that in the FAQ Thread?
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
XxLordxX said:
Hey, you did a great guide! Would you mind if I put that in the FAQ Thread?
Click to expand...
Click to collapse
No problem, I'd be honored!
Download
Search for TWRP recovery for LG V10 H901 (File: twrp-2.8.7.0-h901.img (31.7 MB))
Backup Apps and Data
While this process should not wipe any of your data, a backup is highly recommended. Once you install a custom recovery like TWRP, make sure you backup your system, data,etc. from the recovery. It will be helpful in case anything goes wrong.
Prerequisites
This guide is compatible with LG V10 H901 only. Do not try it on any other devices or variants.
Unlocked bootloader is required to install a custom recovery like TWRP on your device. Click here.
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here.
Install Motorola USB Drivers on your computer.
Open Settings> Developer options and enable USB Debugging on your device.
Go to Developer options and enable Allow oem unlock.
How to Install TWRP Recovery on LG V10 H901
Download the recovery image file. Extract if in case a zip file. Now transfer the file to your PC where you can easily locate it.
Make sure you have setup ADB and fastboot on your PC. Also accept Always allow from this computer when you plug in the device for first time to enable USB Debugging.
Now power off your device and unplug it from your PC.
Boot into the bootloader or fastboot mode. To do so, press and hold volume down and the power button simultaneously for 5-6 seconds. When you see the bootloader screen, connect your device to the PC using a USB cable.(Choose fasboot if option is available) Alternatively, you can also issue the following command through your cmd or terminal, while connected to the PC in order to boot into the bootloader.
"adb reboot bootloader"
Navigate to the location where you have placed the recovery file. Rename the recovery file to a simple one, like recovery.img. While the folder with recovery.img file is open, hold shift key on keyboard and right-click on an empty space and select “Open command window here” option to launch a cmd window.
Now issue the following command in the command prompt to check your device connectivity
"fastboot devices"
Now flash custom recovery. Issue the following command for that.
"fastboot flash recovery recovery.img"
Custom recovery will now be installed on your device. Now boot your phone in recovery mode. You can do this by turning your device off and then press and hold volume down and power keys at the same time. Or you can simply enter the following command.
"fastboot boot recovery.img"
Once into the recovery, you can backup your current ROM, data, EFS and more.
Once you have installed TWRP, you are all set to install custom packages onto the device’s system. Alternatively, while on Linux or Mac OS, you can issue “./fastboot flash recovery recovery.img” command to flash the TWRP recovery.
Root
As you already have TWRP, simply flash the SuperSU file (version 2.56) to gain root access
@TheJesus @KAsp3rd, thanks guys for everything you've done over the past few days. no shade to @joe01gun but if people are going to use these instructions make sure you search the rest of the forum for what thejesus and kasp3rd put together to get us to this point - definitely appreciated. thanks @joe01gun for putting these additional instructions together.
Your post says the following:
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here.
yet, there's no link to the necessary files to "unzip" them. Any suggestions?
Thank you for the help, but where do we get fastboot set up on our PCs? Yes, this is getting confusing with the steps outlined above. I followed the first step and had to take out the battery because I was stuck in fastboot screen with small tiny text in the top left that didn't respond to any manipulation with the volume keys on the back of the device and wouldn't restart any way until I took out the battery.
sanjsrik said:
Your post says the following:
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here.
yet, there's no link to the necessary files to "unzip" them. Any suggestions?
Click to expand...
Click to collapse
I think it's cause he's not allowed to post links yet cause he's too new. I followed this guide http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
You can get twrp from the development forum.
Why
Intended to put the information condensed....
Yep....new
Links could not be uploaded.
joe01gun said:
Intended to put the information condensed....
Yep....new
Links could not be uploaded.
Click to expand...
Click to collapse
Your condensed thread is more convoluted than the actual development thread which also includes the links to everything.
I'm still wondering why you have install Motorola USB drivers for an LG phone..
Understood
Understood
The one on development is straightforward and I managed to make it done.
If you don't lock the bootloader back, you will see bootloader unlocked when starting up.
If you have root enabled file explorer, you should remove /system/priv-app/adaptclient folder to avoid annoying root request from adapt.
Please use the main dev thread for instructions on what to do, found below. Having duplicates for what is essentially the same thing can cause confusion and just takes up unnecessary space. So I have closed the thread.
[Recovery][LG-H901] Unofficial TWRP
Forum moderator,
matt4321
Update: When you flash the recovery and supersu files make sure to have the remove encryption file on sd card aswell and add it to the list and flash and if you hang at boot screen.. boot into recovery and wipe cache.. reboot.
WINDOWS USERS ONLY.... USE AT YOUR OWN RISK
Make sure you have the proper drivers and make sure you have a real good usb cable... This rar has the usb drivers and the files already in the folder just drop onto desktop and run cmd.exe
Files Needed: http://www.filedropper.com/nocturnaladbfastboot
http://www.filedropper.com/removeencryption
DO NOT FORMAT SYSTEM!!!!!!!!!!!!!
Make sure you are in bootloader or this will not work..
Key combo to get into bootloader or recovery via hard keys.
power off
volume up + power = recovery
volume down + power = bootloader
from bootloader you have several choices to boot, just pres volume down to choose, power to select.
1. To make sure you are connected run command (adb devices) enter
2. Once you see your device run command (adb reboot bootloader) Then..
3. Run command (fastboot boot boot.img) wait for downloading dialog...
4. Then run command (fastboot flash recovery twrp_recovery.img) and make sure you have the proper files on sd card.. i put all files in the folder on my sd card to make sure...
5. once the screen says okay on tablet.. push the vol down button until you see recovery mode and then push power to start twrp recovery..
6. Once in twrp flash SuperSU246.zip and recovery.zip remove_encryption.zip then reboot... you should have root on reboot:good:
Instructions
I think I understand your instructions but I have a few questions.
Am I typing all of the commands on my pc? (- SuperSU)
Step 3 has “Run command “(fastboot boot boot.img)” I see 2 files and so those are two separate commands to run correct?
Step 4 Then run command (fastboot flash recovery twrp_recovery.img) and make sure you have the proper files on sd card.. i put all files in the folder on my sd card to make sure... Again is this 2 commands to run? I see the twrp_recovery.img file but no fastboot flash recovery file?
In step 4 should I be using theses 2 commannds;
fastboot flash boot boot.img
fastboot flash recovery recovery.img
ahunter said:
I think I understand your instructions but I have a few questions.
Am I typing all of the commands on my pc? (- SuperSU)
Step 3 has “Run command “(fastboot boot boot.img)” I see 2 files and so those are two separate commands to run correct?
Step 4 Then run command (fastboot flash recovery twrp_recovery.img) and make sure you have the proper files on sd card.. i put all files in the folder on my sd card to make sure... Again is this 2 commands to run? I see the twrp_recovery.img file but no fastboot flash recovery file?
In step 4 should I be using theses 2 commannds;
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
run them just as there posted make sure all files on the sd card and you should be fine..
Thanks for your reply. Those commands are run on the PC in the cmd window right? and I copied the files in the directory to my SD card I installed on the nextbook should that be a problem. Shoul this be the SD card or internal memory? I didn't run the commands the way they were written last night & didn't have success. I am getting hung up on 3. Run command (fastboot boot boot.img) wait for downloading dialog...
My pc and tablet are seeing eachother but they both say waiting, I don't think my files are being seen.
ahunter said:
Thanks for your reply. Those commands are run on the PC in the cmd window right? and I copied the files in the directory to my SD card I installed on the nextbook should that be a problem. Shoul this be the SD card or internal memory? I didn't run the commands the way they were written last night & didn't have success. I am getting hung up on 3. Run command (fastboot boot boot.img) wait for downloading dialog...
My pc and tablet are seeing eachother but they both say waiting, I don't think my files are being seen.
Click to expand...
Click to collapse
Make sure you uninstall and reinstall the usb drivers in the folder and run the cmd from the folder and if still nothing try a new cable and usb port... when you run command adb devices do you see your listed as numbers and some letters?
After the adv devices command it gives me; listed devices YFGV0815002950 device. That should be the tablet, it’s the only thing attached w/usb & it also shows up in explorer.
After the adb reboot bootloader cmd the tablet reboots into bootloader with “Fastboot CMD WAITING “ at the bottom of the screen.
After the fastboot boot boot.img cmd my pc cmd rompt says <waiting for device> and my tablet stillhas the Fastboot screen mode & FASTBOOT CMD WAITING at the bottom of the screen
That is as far as I get. I copied all of the files in your download link in the .rar format and to a directory on my internal tablet storage. It seems like the tablet is waiting for a file but I don't understand why.
ahunter said:
After the adv devices command it gives me; listed devices YFGV0815002950 device. That should be the tablet, it’s the only thing attached w/usb & it also shows up in explorer.
After the adb reboot bootloader cmd the tablet reboots into bootloader with “Fastboot CMD WAITING “ at the bottom of the screen.
After the fastboot boot boot.img cmd my pc cmd rompt says <waiting for device> and my tablet stillhas the Fastboot screen mode & FASTBOOT CMD WAITING at the bottom of the screen
That is as far as I get. I copied all of the files in your download link in the .rar format and to a directory on my internal tablet storage. It seems like the tablet is waiting for a file but I don't understand why.
Click to expand...
Click to collapse
there is a problem after you boot into bootloader i had the same problem for days.. i just played with cables and drivers use the ones inside the folder they worked for me...
I'll keep trying. It has be the drivers.
I followed these directions to a T, but for some reason the device can not read the SD card while in recovery. Any clues as to why this is happening?
So I was online shopping for my first tablet when I came across this thread. . . It led me down to the local WALMART and I picked one up. I successfully completed the process, or so I thought. I went to reboot after flashing everything, and twrp says " no OS installed! Are you sure you want to reboot?"
What did I do wrong?
I have tried several times to download the remove encryption file must be a bad link or something. Is there another download site or can someone send to me plz
Nvm I ran it over with my car because I couldn't get the download link to work. If anyone wants it for parts send me a message. Its brand new only been used maybe 2 weeks. The most wear and tear on it was my Buick regal hitting it at about 45 mph in a pissed off rage. don't think all the insides are smashed tho. Possibly a good fixer upper
Is this fastboot and adb custom versions?
I have adb and fastboot in my path (runable from anywhere)..
ADB says the version release is the same number.
do I need to use your versions for the tablet?
http://www.filedropper.com/removeencryption
does not work, link changes to http://www.filedropper.com
and asks me to upload a file?
Link working sorry...
http://www.filedropper.com/roottwrpremoveencryption
TWRP 3.0
http://www.filedropper.com/twrp3recovery
C:\Users\Fuzzy\Desktop\root_twrp_remove_encryption>fastboot flash recovery twrp_
recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (15558 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 0.320s]
finished. total time: 0.830s
C:\Users\Fuzzy\Desktop\root_twrp_remove_encryption>
Copied the two zip files to both a 4gb fat32 formatted microsdhc
and internal storage via MTP to the device then ran ADB 1.0.32
and rebooted to bootloader. (adb finds device fine)
fastboot devices reported device number fastboot.
flashed TWRP in package you uploaded yesterday.
it says both internal and external cards are empty?
internal card has files that the manufacturer put there,
but TWRP can't see them?
What am I doing wrong?
Any ideas how to fix?
log says 'unable to find crypto file'
and it couldn't mount /data or /storage filesystems
>>>
installed TWRP3 that allowed the installs although it still
could not open /data. It did find the external card installed
from there.
I am guessing the forced encryption made /data unreadable.
hopefully now with the encryption removed the /data
partition will be readable.
>>>
I reran recovery to check and log now has no failures!!!
I'm guessing the changed boot.img fixed the issues it was having.
*smiles*
cant get files. takes me to a site to sign up. can you dropbox link them please?
I just won this tablet in a contest. Anyone have the remove_encryption.zip file? I managed to find all of the other required files but none of the links in this thread work anymore.
whats the problem with the links? site says free but wants me to pay. losing my head here, and it seems im not the only one
Bad filedropper links
Filedroper no links available, asks us to register and pay for stuff that's not there anymore
can you like put them on Google drive, SendSpace, DropBox, Mega.nz and/or ZippyShare