Hi,
I was installing ARHD 7.4 on my HTC one and the install did not fully complete and now my phone will not boot. If i try to go into recovery cwm shows for a quick second and then the phone goes into an endless loop until i go back into bootloader. The drivers were installed just fine on my win 8 machine and I was able to use adb and fastboot previously but now it does not seem to work. I tried searching the forum and cannot seem to find the answer to my issue.
Any help you can provide would be much appreciated as I really do not want a paperweight.
update: for some reason when I plugged my phone into laptop instead of my desktop, my phone was detected through fastboot and I was able to clear the cache and reinstall the recovery.
Then:
Try with a flash of CWM, maybe the latest version and make an erase cache (fastboot erase cache).
After this, see if the CWM will boot and you can use it.
If yes, reflash the rom, and if that will not boot, try with flashing the boot.img from fastboot.
[Fixed] very same problem
Yeah! I had the very same problem. My phone restarted after i installed the proximity fixer for my HTC One (M7) and after that i rebooted my phone into recovery, and that was it. an endless reboot. till the splash screen and reboot.
This is what I did:
Step 1 : when its about to reboot, ignore the power button, just hit the volume down button and you will be in the bootloader section.
Step 2: highlight 'Fastboot' and select it by pressing the power button.
Step 3: connect your phone using the data cable.(P.S - make sure all your ADB drivers and etc are installed. also the fastboot in your pc).
Step 4: open the location where you have installed the fastboot (usually C:\fastboot or could be something else) in your pc and open a cmd there (hold shift and right click, select open command prompt here)
Step 5: type
Code:
fastboot erase cache
Step 6: after it has erased the cache, go download a custom recovery. (CWM/TWRP)
Step 7: copy the recovery.img file into the fastboot directory and open a cmd again (shift+ right click)
Step 8: type
Code:
fastboot flash recovery recover.img
Step 9: now just give restart bootloader on your phone.
Step 10: Now you should be able to go into recovery n reflash the ROM.
Step 11: Next time be very careful, there are some cases where in which you cant fix it back.
All the best
Hit thanks if I helped you Ciao.
Yeah... To the op I had a similar issue as your edit suggested.. I think it's residual electricity on the MoBo preventing a read on the port.
Sent from my SPH-L720 using xda premium
Related
Here's a guide to unlocking the bootloader, flash a recovery image, and install a custom ROM on your Incredible s.
If you're not experienced with this sort of thing I advise you get help or not do it at all. I'm not responsible for anything that happens to your phone, but it is highly rare that anything will go wrong
1. Go to www.htcdev.com and log in/create an account. When logged in, click on 'Unlock Bootloader'
Now simply follow the on screen instructions provided by HTC. Some of the process requires getting some files from the Android SDK and you will needs the HTC drivers which come with HTC Sync, but this will all be explained through the process.
Now as I said, you need some files from the SDK which you can get here:
http://dl.dropbox.com/u/4263022/HTC Dev Tools.zip
I recommend putting these somewhere easy like the root of your C: drive in a folder called 'Android' like I will for the tutori. If you're still sure, select yes, and the process will complete.
2) you should see a little message pop up now asking if you'd like to go ahead and unlock the boot loader. Select yes.
3. Once done, your phone's bootloader will be unlocked, this will enable you to flash a recovery image.
4. Go to
http://download2.clockworkmod.com/re...0.2.0-vivo.img
and download the recovery image for the Incredible S. Put it in the "android" folder with the other files needed for the unlock process. This file is the ClockWorkMod recovery for the incredible s.
5. Shut down your phone. Plug it in via USB to your PC which you set up during the HTC unlock process. Hold volume down, and press power and the phone will boot into the bootloader. Wait for it to scan your SD card, then ensure "Fastboot" is highlighted and press power.
6. On your PC, load up a command prompt - open the Start menu, go to Run, and type "cmd".
7. In the command prompt window, type the following, assuming the HTC unlock files are all in C:android.
Code:
cd c:android
Then type:
Code:
fastboot flash recovery <recovery_name.img>
Don't forget the .img on the end, and replace "recovery_name" with the specific name of the recovery image you want to use. For ClockWorkMod linked to in step 4, you'd type:
Code:
fastboot flash recovery cwm-4.0.1.4-vivo.img
After a few seconds, ClockWordMod will have been flashed to your phone.
8. Reboot your phone, there should be an option in the fastboot menu (volume up and down to navigate, power to select). It should boot as per normal. Put it into USB disk mode, and download a ROM that you'd like to use. CyanogenMod is what I'm going to use: http://www.cyanogenmod.com/devices/htc-incredible-s
Download the ROM and place it in the root of your SD card
9. Power off the phone. Hold volume down and press power to boot back into the bootloader. Use volume down to select "Recovery" and press power. ClockWorkMod recovery will load.
10. Using volume up/down and power to select, go down to Backup/Restore. Select it, then click backup. ClockWorkMod will backup your stock ROM in case there are any needs to switch back.
11. After that (takes about 5 minutes), go back to the main menu. Select wipe data/factory reset and confirm. Go back to the main menu, select Advanced > Wipe Dalvik cache
12. Go to the main menu, and select "Install zip from sdcard". Next choose "Select Zip from SD card" and select the ROM you'd like to install. Confirm this action, and ClockWorkMod will install your new ROM. When done, shut down your phone.
13. Ordinarily you'd be done after that, and you could boot into your new ROM. However HBOOT 1.16 does some random stuff and tends to cause problems. I think it interferes with the installation of the boot.img that ordinarily would be flashed with the ROM. Get the ROM that you downloaded earlier (CyanogenMod in this tutorial), and on your computer, unzip the file somewhere. Once done, inside you'll see a file called "boot.img". Put this in the same folder as your other Android tools that you used earlier. Power your phone on, hold volume down, but don't choose "recovery", choose "usb fastboot".
14. Open up your command prompt again (Start > Run > "cmd"), and type (using the "android" folder for this example):
Code:
cd c:android
fastboot flash boot boot.img
This will flash the boot.img to your phone.
Power off the phone, reboot it, and that should be it!
If this helps please leave a thank you.
Good luck
Sent from my HTC Incredible S using xda premium
Bad download URL for CWM...
The URL you have documented for CWM recovery image is giving an "Access denied" response.
Thanks a lot!
It's very useful for me :good:
This is a duplicate thread and copied too.... the actual guide is at http://forum.xda-developers.com/showthread.php?t=1337105
Closed
What he said
Please help!
I am currently trying to root my TF701t on Jellybean but I appear to have corrupted my bootloader. I can boot into the bootloader and do a system wipe and boot Andoid, but when I select the RCK option I end up with the Android image on its back.
I have downloaded CWM 6.0.4.6 and tried to apply the recovery.img file via Minimal ADB and Fastboot command prompt only to be greeted with "cannot load "recovery.img" Result too large".
To be clear the system boots normally and fuctions perfectly - this is strictly a bootloader issue which has been unlocked successfully.
Any help would be greatly appreciated and apologies in advance if either the solution to this has been posted elsewhere or I have not given you the information you require to help.
Many thanks,
East
You need to fastboot recovery from the bootloader.
When you reboot into the bootloader do not select RCK. RCK is the recovery, I don't think the default one can do anything, you just get the android on it's back.
So it should be reboot into bootloader and then don't touch your tablet.
Then from your pc fastboot flash recovery recovery.img
Make sure you are also on a 4.3 bootloader before you fastboot flash CWM 6.0.4.6.
The instructions above are correct
To flash a recovery you need to have the fastboot.exe file and cwm recovery.img file in the same folder.
Right click + shift on the folder they are in and choose open command prompt here
Boot into the Bootloader by either booting with the Power and Volume Down Buttons held down until you get the 3 icons or by typing the following into the command prompt.
Code:
adb reboot bootloader
Then type the following commands to flash the recovery image:
Code:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Start the recovery by making sure the RCK icon is highlighted (use volume down to move) and push volume up to select.
sbdags said:
Right click + shift on the folder they are in and choose open command prompt here.
Click to expand...
Click to collapse
In Windows 7 you can just navigate to the folder with explorer and in the address bar type cmd and hit enter
Opens a command prompt in the correct folder
Doh!
Thank You
Well.......this is very embarrassing.
I have rooted and installed custom roms on my last 3 phones including the my new Nexus 5 without any problems at all. I simply followed the instructions posted by the developers. At the same time I used to take the piss out of the other posters who raised queries because they hadn't followed the instructions. What do I do? Exactly that.
Please accept my apologies sbdags as it is your rom I am installing and thank you to You & Sleeepy2 for posting polite and prompt replys without having a go at me for not following your instructions.
Problem solved I am now rooted!
Thank you again.
East
I know this one has been answered a few times in pieces, and somewhat understandable manner. However, I wanted to decrypt this for everyone to be able to understand how to do it and to overcome this particular issue.
Issue: You have a custom recovery installed and your LG G2 prompts you to install the new OTA (i.e. KitKat update). You then accidentally/unknowing of consequences accept the update. Your phone restarts and keeps going to the custom recovery which you had installed, instead of booting to the update. You endlessly try to boot to your phone, but it just keeps going back to your custom recovery.
Things to do ahead:
1. Have LG G2 drivers installed on computer you will be using. You can get those from the LG website easily by searching LG G2.
2. Obtain ADB and fastboot files from HERE
3. Obtain working TWRP vs 2.7.0 from HERE if you don't have the TWRP recovery installed (i.e. if you're using CWM or Philz recovery).
Recovery Procedure:
1. If you have TWRP recovery installed, proceed from step 9
2. If you have CWM or Philz recovery installed, follow these next steps.
3. When inside CWM/Philz recovery, click on option to install zip.
4. Have your phone connected to a computer which has the LG G2 drivers installed, found on LG's site. Make sure to install drivers without phone connected to computer first. After installing, restart computer, and then plug phone to computer USB port.
5. Now that you have the phone plugged to comp, and that the comp has recognized your phone, open up CMD and navigate to the folder where you have your ADB file located and workable TWRP recovery zip file.
6. Once there, click on install using sideload on your phone's custom recovery which should be located inside the install zip option.
7. Then type in CMD on computer this: ADB sideload TWRP-file-name.zip
Note. Replace TWRP-file-name.zip with whatever the TWRP zip file on your computer is named to the letter.
8. Your phone will install TWRP recovery at this point. Once it finishes, restart your phone by rebooting recovery (should be an option somewhere there in the main level of the recovery)
9. TWRP should boot now. Once inside TWRP, click on Advance
10. Then click on Terminal Command
11. Next click on Select
Note: Do not navigate to any other folder. Just click on Select. You'll know what I mean once your in Terminal Command.
11. Type this command in the space provided in your phone (NOT in CMD) which should be now in Terminal Command mode exactly to the last letter. I'm not kidding; don't miss a character or replace a number. You risk nuking your phone. Double check your typing.
Type this: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Note: You should note that there is a space between dd and if=/dev, and another space between /zero and of=/dev
12. Once the command finishes running, about 30 seconds or less, restart phone. And voila. Your phone should boot back to your pre-selecting update with OTA mode.
In my case, I wiped everything and tried restoring one of my nandroids. That did not help me boot my phone. However, when I did the above mentioned steps, my phone booted to my backed up state which I installed prior.
Hopefully you don't end up being a victim of this. But if you are, now you can confidently bring yourself back :good:
Good luck and share your progress. Thanks!
Cheers,
~Atrio
Terminal Command didn't work ...
AtriosM3 said:
I know this one has been answered a few times in pieces, and somewhat understandable manner. However, I wanted to decrypt this for everyone to be able to understand how to do it and to overcome this particular issue.
Issue: You have a custom recovery installed and your LG G2 prompts you to install the new OTA (i.e. KitKat update). You then accidentally/unknowing of consequences accept the update. Your phone restarts and keeps going to the custom recovery which you had installed, instead of booting to the update. You endlessly try to boot to your phone, but it just keeps going back to your custom recovery.
Things to do ahead:
1. Have LG G2 drivers installed on computer you will be using. You can get those from the LG website easily by searching LG G2.
2. Obtain ADB and fastboot files from HERE
3. Obtain working TWRP vs 2.7.0 from HERE if you don't have the TWRP recovery installed (i.e. if you're using CWM or Philz recovery).
Recovery Procedure:
1. If you have TWRP recovery installed, proceed from step 9
2. If you have CWM or Philz recovery installed, follow these next steps.
3. When inside CWM/Philz recovery, click on option to install zip.
4. Have your phone connected to a computer which has the LG G2 drivers installed, found on LG's site. Make sure to install drivers without phone connected to computer first. After installing, restart computer, and then plug phone to computer USB port.
5. Now that you have the phone plugged to comp, and that the comp has recognized your phone, open up CMD and navigate to the folder where you have your ADB file located and workable TWRP recovery zip file.
6. Once there, click on install using sideload on your phone's custom recovery which should be located inside the install zip option.
7. Then type in CMD on computer this: ADB sideload TWRP-file-name.zip
Note. Replace TWRP-file-name.zip with whatever the TWRP zip file on your computer is named to the letter.
8. Your phone will install TWRP recovery at this point. Once it finishes, restart your phone by rebooting recovery (should be an option somewhere there in the main level of the recovery)
9. TWRP should boot now. Once inside TWRP, click on Advance
10. Then click on Terminal Command
11. Next click on Select
Note: Do not navigate to any other folder. Just click on Select. You'll know what I mean once your in Terminal Command.
11. Type this command in the space provided in your phone (NOT in CMD) which should be now in Terminal Command mode exactly to the last letter. I'm not kidding; don't miss a character or replace a number. You risk nuking your phone. Double check your typing.
Type this: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Note: You should note that there is a space between dd and if=/dev, and another space between /zero and of=/dev
12. Once the command finishes running, about 30 seconds or less, restart phone. And voila. Your phone should boot back to your pre-selecting update with OTA mode.
In my case, I wiped everything and tried restoring one of my nandroids. That did not help me boot my phone. However, when I did the above mentioned steps, my phone booted to my backed up state which I installed prior.
Hopefully you don't end up being a victim of this. But if you are, now you can confidently bring yourself back :good:
Good luck and share your progress. Thanks!
Cheers,
~Atrio
Click to expand...
Click to collapse
I repeated this three times, and no luck... any suggestions?
I did it a tad differently. I am running Windows 7.
First I downloaded these universal drivers so my phone was recognized under Device Manager, went to my adb directory with command prompt and typed the following:
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
I just preferred using the keyboard, but your directions will work, too.
secure booting error
got the OTA update ...after that boots to Logo with a "secure booting error" message then a black screen, can't go to download mode, phone is recognized as QHSUSB in device manager, factory recovery doesn't work.
what can be done in this case??
eddie 2t said:
got the OTA update ...after that boots to Logo with a "secure booting error" message then a black screen, can't go to download mode, phone is recognized as QHSUSB in device manager, factory recovery doesn't work.
what can be done in this case??
Click to expand...
Click to collapse
U had a custom recovery flashed correct? To me it sounds like your on stock recovery
bleedingthru said:
U had a custom recovery flashed correct? To me it sounds like your on stock recovery
Click to expand...
Click to collapse
I rooted the phone, tried to install clockwork but didn't succeed so I forgot about it, then the update totally screwed me.
eddie 2t said:
I rooted the phone, tried to install clockwork but didn't succeed so I forgot about it, then the update totally screwed me.
Click to expand...
Click to collapse
Ive never used cwm on this device only twrp so i dont know about that recovery
boot
I have philz touch and all my phone will do is boot to philz?
Hi all,
I have an HTC One M8. I bought it used and run a AT&T sim on Straight Talk. Previous owner had rooted it. I was trying to get the 4.4 updates and Sense 6.0.
The phone was already running HD Revolution 12.1 and Android 4.2.2 with TeamWin Recovery Partition v2.5.0.0
I downloaded and installed Android_Revolution_HD-One_71.1.zip.
I've run it several ways:
1. First w/o wiping from TWRP. (Factory reset settings)
2. Installed w/o "Wiping Userdata Partition" and then tried "Wiping Userdata Partition" from the HD Revolution installer.
3. SuperUser by Koush checked.
4. Stops at setting permissions "set_metsdata_recusrsive: some changes failed."
5. Finish
6, Zip Install details say "no MD5 file found".
7. Reboot System and it tells me "Root permissions appear to be lost. Fix root permissions now?" Yes....
Then reboots into white Bootloader screen. Anything selected here takes me to the Recovery page. Anything selected from the REBOOT menu in TWRP takes me to the Bootloader screen.
When this is done it reboots into the white bootloader screen. Any option I pick there takes me to the TWRP recovery.
I'm stumped. Any help /bread crumbs would be appreciated.
Bootloader shows:
**TAMPERED**
**UNLOCKED **
M7_UL pvt ship s-on rh
HBOOT-1.44.0000
RADIO-4A.14.3250.15
OPENDSP-v26.120.274.0202
eMMC-BOOT
May 3 2013, 20:01:28-1
Thanks
TJB
fastboot erase cache
Then flash TWRP 2.6.3.3
Then reflash the ROM.
TWRP 2.6
BenPope said:
fastboot erase cache
Then flash TWRP 2.6.3.3
Click to expand...
Click to collapse
I'm actually trying to mount the phone so I can see it from the PC update the TWRP. I downloaded openrecovery-twrp-2.7.1.1-m7.img but can't see how to load it to the phone.
PC sees the phone from Device Manager as a Disk Drive but it doesn't show up as a drive under My Computer.
I have Minimal ADB and Fastboot. Am I on the right track?
TJB
BenPope said:
fastboot erase cache
Then flash TWRP 2.6.3.3
Then reflash the ROM.
Click to expand...
Click to collapse
I tried to install openrecovery-twrp-2.7.1.1-m7.img but I can't see HTC from my PC. It shows up as in Device Manager but there's no way to write to it. I have Minimal ADB and Fastboot. Do I need a USB OTG cable. What else can I do from the PC side to see the phone?
Right now I'm just trying to get files to the phone. Am I on the right track?
THB
teebright said:
I tried to install openrecovery-twrp-2.7.1.1-m7.img but I can't see HTC from my PC. It shows up as in Device Manager but there's no way to write to it. I have Minimal ADB and Fastboot. Do I need a USB OTG cable. What else can I do from the PC side to see the phone?
Right now I'm just trying to get files to the phone. Am I on the right track?
THB
Click to expand...
Click to collapse
You cannot install like that, they have to be flashed via bootloader.
Do you have ABD installed on your PC?
If not you have two options.
OPTION 1
This guide for Windows 7 machine, this is the quickest way IMHO
Download the adb files for your respective PC from here : http://developer.android.com/sdk/index.html
Once you have downloaded the correct one for your PC (i.e. 32 or 64bit) you will be left with a zip FOLDER named something like this adt-bundle-windows-x86_64-20130522.zip (this is for 64 bit machine), Unzip it somewhere on your pc
Locate the unzipped folder and you should have/see the following inside
• Eclipse
• Sdk
• SDFK manager .exe
Open up the sdk folder and you will find 6 folders inside, cut the 'platform-tools’ folder , then double click my computer and then enter the C: drive of your PC. Paste this folder here in the C: drive and rename it Andriod-adb.
Then right mouse click my computer and go properties, then go and click Advance system settings located on left hand side this will bring up system properties box, click the Environment Variables… tab (it will open further details) and locate the Environment Variables list scroll down until you find path, highlight this then click edit.
Click mouse in here and scroll right to the end after the last entry
Type the following ;C:\Android-adb (noting only adding the first ; if not already there), if it is already there just type C:\Android-adb. Then hit Ok then OK again and your ADB should now be successfully setup.
To test this
From the windows start button, and in the search programs and files box type cmd and enter, this should bring up a command window.
Plug in your device and type adb devices, you should see it locate your phone
OPTION 2
Or try this, extract the attached file to your desk. place your recovery img in here and in a blank spot here hold the shift key down and right mouse click this should bring up list allowing you to "open command prompt here" then follow instructions below..View attachment 2850273
------------------------------------------------------------------------------------------------------------------------------------------------------
Once you have ADB working via either of the above sorted from a
1. Command prompt you should be able to type adb reboot boatloader, if you phone reboots into bootloader go to next step
2. Place the recovery image "openrecovery-twrp-2.7.1.1-m7.img " in the same adb folder as downloaded in option 2
3. Open a command prompt from within this folder and then type fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img
4. Once sent it should com back to prompt
5. Type fastboot erase cache, then when completed type fastboot reboot
Good luck
fixed!
I fixed it! Per the recommendation I was trying to upgrade TWRP to 2.6.3.3.
I plugged in the phone to the PC via USB and made sure the phone is in FASTBOOT USB mode from the bootloader menu.
I installed "Minimal ADB and Fastboot" on the PC. Running that from the command line (cmd.exe) you type "fastboot flash recovery " then drag the file in. (watch the youtube video "How to install TWRP recovery on the HTC One M8" by ROOTJUNKIE-it will make more sense). In my case it was the 2.6.3 TWRP.img file. That pushes the update to the phone. I already had the HD 71.1 zip on the phone. I installed that via the TWRP install and from there it booted up normally. Had to setup the phone again but my music/pics were still there. Thanks all for the help!
Root Lenovo Tab 10 TB-X103F (Tested)
1. activate developer options on the Tablet
2. enable Bootloader-Unlock on the Tablet
3. download and install ADB und fastboot
4. latest usb driver on your PC
5. download TWRP TWRP-3.0.2_TB-X103F-beta.img
https://forum.xda-developers.com/showpost.php?p=70228684&postcount=65
6. download SuperSu zip file
Steps:
1.) boot to fastboot -> shutdown your device -> press on/off + "+" Volumekey → device restarts to fastboot mode
2.) connect to your pc via usb cable
3.) start command shell (cmd) in the fastboot instalation folder on your PC and check for the device connection with the command:
"fastboot devices"
4.) do the unlocking
"fastboot oem unlock-go"
5.) boot TWRP image file in the command line, showing the pathway to the .img file (if not in the same folder):
fastboot boot TWRP-3.0.2_TB-X103F-beta.img
6.) Put SuperSu zip file in the device memory and flash SuperSu zip with TWRP, then restart the device. Done!!!!
Stock recovery remains
RooterLeopold said:
Root Lenovo Tab 10 TB-X103F (Tested)
1. activate developer options on the Tablet
2. enable Bootloader-Unlock on the Tablet
3. download and install ADB und fastboot
4. latest usb driver on your PC
5. download TWRP TWRP-3.0.2_TB-X103F-beta.img
https://forum.xda-developers.com/showpost.php?p=70228684&postcount=65
6. download SuperSu zip file
Steps:
1.) boot to fastboot -> shutdown your device -> press on/off + "+" Volumekey → device restarts to fastboot mode
2.) connect to your pc via usb cable
3.) start command shell (cmd) in the fastboot instalation folder on your PC and check for the device connection with the command:
"fastboot devices"
4.) do the unlocking
"fastboot oem unlock-go"
5.) boot TWRP image file in the command line, showing the pathway to the file:
TWRP-3.0.2_TB-X103F-beta.img
6.) Put SuperSu zip file in the device memory and flash SuperSu zip with TWRP, then restart the device. Done!!!!
Click to expand...
Click to collapse
I have done all the steps but For some reason twrp is not installed and i still have the stock recovery. Please help
That's because the above only boots TWRP to root but does not install it. To install TWRP, when in booted with TWRP, you need to transfer the TWRP img to the tablet storage and then install it while in TWRP.
it is important to show the pathway to the file TWRP-3.0.2_TB-X103F-beta.img in the command line, like:
C:\Users\Public\Documents\My Videos\TWRP-3.0.2_TB-X103F-beta.img
Sorry for this newbie question.
Which part of the above rooting steps is rooting my tablet, what is TWRP doing and why do I need to install the SuperSU app?
During my first try I didn't boot the TWRP image rather I flashed it. But that didn't help at all.
After booting the TWRP image I was able to flash the SuperSU app.
The stock recovery is still in use.
Thanks in advance.
Read the steps carefully and follow the steps, it is a tested successfull strategy. To get deep knowlege about the background processes, please read the threads elsewhere in Web.
Yow how do you enter Fastboot on the tablet and i haved tied avery button on the tablet and i dont see the fastboot option
Entering Fastboot on Lenovo TB-X103F tablet
ShottaDopey said:
Yow how do you enter Fastboot on the tablet and i haved tied avery button on the tablet and i dont see the fastboot option
Click to expand...
Click to collapse
Hi everyone. I just want to clarify something about this procedure There's a lot of people being confused on how to get into FASTBOOT on some things, and that's stopping them getting anywhere from the beginning.
The Lenovo TB-X103F tablet doesn't have a way of booting directly into FASTBOOT. Turning the tablet On while holding either volume key and the On button doesn't do it directly. . . . . Firstly, there's 3 buttons on the tablet, I call them VOL- VOL+ PWR (again, that's just to clarify things 100%)
here's what must be done (well it's this way on the 3 I have on my desk, so I assume all TB-X103F tablets are the same) . . . . .
1) Turn the tablet off completely.
2) Press & hold the VOL+ button (the middle of the 3 buttons).
3) Press & hold the PWR button, release the PWR button as soon as anything appears on screen - Keep holding VOL+ button.
4) After about 8 seconds the familiar green android lay down will appear. Then, your recovery menu will appear.
5) Release the VOL+ button anytime now.
6) Press either VOL button to select BOOTLOADER on the menu (Bootloader is the same as FASTBOOT on this menu, that's where the confusion lies for many users).
7) Got Bootloader selected? now press PWR and let the tablet reboot itself.
8) it will show the LENOVO logo, and appear to be stuck - it isn't It's in Fastboot mode.
9) Plug in your USB to PC cable, and it'll install appropriate drivers on the PC (hopefully eh?).
10) Once the drivers are installed, test it by getting a Command Prompt in your ADB/FASTBOOT folder on your PC . . . .
11) type the command FASTBOOT DEVICES It should show you that your device is connected, if it shows no devices then either it didn't install the drivers, or something
else is wrong (there's about 30 things that can have gone wrong here, too many to go through in this quick guide).
12) The tablet will stay in FASTBOOT/BOOTLOADER mode until you turn it off (or the battery goes flat lol). So stay calm, there's no rush
I've mentioned about there being no rush, because if you choose ADB connecting from the recovery menu, it disconnects automatically after about 5 minutes -
This is Important to know because it can disconnect while you're pushing/pulling files from the tablet, and cause really nasty problems. Bad design eh?
But we're in Fastboot mode, so nothing to worry about like that
Deleted
Successful root
It was hard, but I had finally had done it. I had figured it out it is easier just to go to the command prompt (I ran it under admin) and "cd C:/adb" (where you installed the adb fastboot software) while having the TWRP image file being placed there. I only wished that I had done it sooner. And for those who are new to the custom recovery it can be overwealming, but with patience and going through the files in the file explorer to find your main storage would lead you to the SuperSU file and successfully root your device.
I flashed TWRP...now what? I can't find any instructions on how to reboot into TWRP. I got into some sort of Chinese menu (PWR + VOL-) but I'm pretty sure this is the device test menu.
So I did the "fastboot oem unlock-go" command and adb said ok but my tablet just went to a black screen and won't turn on now and I'm not sure why. I also heard the Windows USB disconnect sound when i did it.
Would this work with the TB-X104F running 8.1?
Since a few months my tablet is stuck with the 'password changed, wait....' message. I had hoped that I could overcome this with the steps mentioned here. But unfortunately not
I can't start it anymore, so I'm not sure if it is in developers mode or not. Also, plugging the device in my mac didn't let it download the drivers.
Too bad, because when it was working it was a great tablet, now it's just a expensive drawer filler
SynGamer said:
I flashed TWRP...now what? I can't find any instructions on how to reboot into TWRP. I got into some sort of Chinese menu (PWR + VOL-) but I'm pretty sure this is the device test menu.
Click to expand...
Click to collapse
its the vol+ not - you need to press with the power button
Steridroid said:
I have done all the steps but For some reason twrp is not installed and i still have the stock recovery. Please help
Click to expand...
Click to collapse
so what exactly do i have to type at the command prompt to run twrp?,ive put the twrp img file in the same folder as the adb stuff.
3.) start command shell (cmd) in the fastboot instalation folder on your PC and check for the device connection with the command:
"fastboot devices"
fastboot shows notting
lenovo seems to have killed these tablets from the old lady next doors experience.. no wifi, no adb, no fastboot, no qualcomm, just unknown device, which loads NOTHING, no drivers work!!!