Database Develop

Usb Driver Problems

Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying

magma9495 said:
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
Click to expand...
Click to collapse
I'm having the same issue myself i think.
Look under N1 Q&A and find the topic "N1 Bricked"
Glad to know im not the only one

I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
I have a tutorial called ADB 4 Dummies that will walk you through installing the android sdk 2.2(froyo) and setting up your environments. Step by step for every system.
First thing, unplug your Phone from computer, uninstall ALL drivers and try from scratch.
Also, if you're using windows, when you're done and you plug in your phone, don't choose to "automatically find drivers" instead manually point it to the drivers folder in the SDK.
Don't worry, it's not bricked. lol.

mrandroid said:
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
Click to expand...
Click to collapse
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up

magma9495 said:
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
Click to expand...
Click to collapse
Hmmmm....
There are 2 modes to the bootloader HBOOT and Fastboot.
Make sure you're phone is in fastboot mode... it should say FASTBOOT USB highlighted in red on top. If it doesn't, use the volume down key, select Fastboot and hit the power button once to switch the phone to fastboot.
Remember, "adb devices" works while your phone is turned on regular. If your phone is in Fastboot mode use "fastboot devices"
Ok, are you using windows? If you are;
Turn off your phone and boot it back up in Bootloader mode. (trackball+pwr, or volume down+pwr)
Once it's on bootloader, plug it in to the computer.
See if the computer asks for any drivers, etc. If it does point it to the Drivers folder in the SDK. If it doesn't... go into your Device Manager. (Right click on MY COMPUTER, click on MANAGE and when computer management opens up, go to Device manager from the list on the left). Look to see if there are any icons with an Exclamation mark and yellow background. If there is, right click on it, select update driver and point it to the drivers folder in the sdk.
Basically there should be a menu on top that says "Android Phone" and when you expand that selection you'll see "Android Bootloader Interface".

nope, no luck with that either, I tried it both on windows XP and windows 7. same error each time. Could it be a problem with my device? because Snow Leopard doesn't recognize the nexus as a storage device or anything

Damn. I think i'm out of options. Last thing to try:
- Turn on phone regular.
- Plug in through USB to computer (try a different USB cable, even if that one worked with the CLIQ, try a different USB port also.)
- On Phone: GO to settings, Application Settings, Development, USB Debugging, (if it's checked on, check it off then on again) make sure it's ON.
Go into your Android SDK folder, go into the TOOLS folder. Now click on DDMS. See if it lists your device...
Last thing would be to go back through the Device Manager, and click on SCAN HARDWARE while your phone is plugged in... It has to be on that list somewhere, whether it's a bad driver, etc, it should still appear in your device manager somehow.

alright that didnt work, but, i got it, i just kept unplugging and plugging back in my phone until adb recognized it. then i got fastboot to run and now i have superuser . But now im stuck at another point. I'm trying to do the recovery.img file. I tried in mobile terminal "flash_image recovery /sdcard/recovery.img" but it told me something like "flash_image not found" I saw that i could do this via fast boot but i dont know how to do that. how would i do fastboot on Mac?

http://www.myhangoutonline.com/tutorials/nexus-one/6-upgrade-nexus-one-recovery

when i try to do the fastboot command i get "-bash: fastboot: command not found" i dont think i have fastboot set up right

have you tried typing in "./" before the command? I found that that was one of my mistakes I did when I first rooted my phone

tried that, entered "./fastboot-mac flash recovery recovery.img" and i just get "waiting for device"

I believe you can also try "./fastboot-mac flash recovery ./recovery.img"

Alright I flashed a clockwork recovery through the app manager in the market. Is there any way I can apply the other recovery with an update.zip?
Also, thanks so much for all the help guys!!!!!!!!!!

you can do it through terminal emulator, if you go to amonra's recovery thread he tells you how.
this is the link http://forum.xda-developers.com/showthread.php?t=611829

fastboot somtimes doesn't come in the SDK... download the version for your system from here: http://www.myhangoutonline.com/tutorials/nexus-one/5-unlock-nexus-one-bootloader
place it in your androidsdk/tools folder

Dell Streak 7 Fastboot

Just wanted to share for those who were unsure about how to get the Streak 7 into Fastboot, hold down power+vol down while powering up - hold until you get text on the screen saying in white text
"Starting Fastboot USB download protocol"
HTH...

Stuck in Fastboot
I did vital mistake by going into Fastboot without enabling USB debugging and now I can not get out!
I tried holding down the power button for minutes and also reversed the the method in how how got into this mess [holding Power+Volume(-)] with no success.
The worst part is I just bought it and played with it for no more than one hour!!
Please help!!!

Just use the pinhole reset by the sd card.

I woke up this morning to a dead battery, I plugged the charger and let is sit for ten minutes. Then, It powered up...relief!!
Thanks for the tip on the reset pin hole button.

fastboot devices, does not see the dell streak 7, drivers are installed properly, adb works fine.

spinn9000 said:
Just wanted to share for those who were unsure about how to get the Streak 7 into Fastboot, hold down power+vol down while powering up - hold until you get text on the screen saying in white text
"Starting Fastboot USB download protocol"
HTH...
Click to expand...
Click to collapse
Thanks, but when I do that I get 5 choices :
0 - Boot Up
1. Factory Reset
2. Software upgrade via upadte.pkg
3. Factory Reset
4. Power Off
If I keep on holding it says :
"Please release power key before selecting function!!!"
What's the trick to get into fastboot mode? Thanks!

Power button plus - volume gets you into fastboot
sent from my re-engineered dInc

Duh...the + had me think it was "volume +", works now, thanks !

My apologies for the lack of clarity, I should have said to press and hold the power and volume - at the same time to get into fastboot..
Sent from my Dell Streak 7 using XDA App

Fastboot Commands
Where do I type them in? If I launch Fastboot.exe (after resolving the adbwinapi.dll not found issue) it pops up in a command console but then immediately disappears. Do I have to use a standard command prompt? (cmd.exe) and if so, what directory do I need to be in?
Thanks.
Lol, this post seems funny now after all i've been through. How quick we learn.

Run then cmd. Enter. You should be at a command window. If you have the device on plug it up and type adb devices. Enter. should pull up your serial number. Whatever path you created should read after the c:/ whatever path you created.
Sent from Re-Engineered dInc

If I use 'adb' i get command not recognized. If I do 'fastboot reboot' I get <waiting for device>. If I do 'fastboot devices' it just reproduces the command prompt with no other response. Am I not properly mounted to the device?
Device in fastboot mode
Debugging enabled

Your missing drivers then. Or you didn't create a path when installing sdk. I suggest a fresh install of sdk with this guide.
addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Sent from Re-Engineered dInc

Hellzya said:
Your missing drivers then. Or you didn't create a path when installing sdk. I suggest a fresh install of sdk with this guide.
addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Sent from Re-Engineered dInc
Click to expand...
Click to collapse
I have not checked this link, but assuming it's a good one, could we get the moderator to set it as a sticky?
I think a lot of us could use the adb walk-through on the first page of this forum...
Sent from my ADR6300 using Tapatalk

Hmm. So i have used fastboot many times before and I can't seem to make it work for this device. 2 machines, sdk installed propperly and still no go. It can't find the device... any ideas?
Sent from my Nexus S using XDA App

The drivers for the device are stored on the sd card. Mount your internal sd to your pc and pull the drivers. Install the driver for your os. That should fix it. If you installed sdk and the latest platform tools along with the google drivers you should be set once the drivers are installed. Also when you put your device into fastboot and plug it into the pc does it ask to install new hardware? Mine did. But seems like your missing the drivers.
Sent from Re-Engineered dInc

nope. drivers were installed. i see the device in the device manager. i tried version 2 of the drivers that comes with the streak and also tried version 4 that comes with the sdk. nothing

Does adb work?
Sent from Re-Engineered dInc

adb devices shows the device when it is booted in android.

Can you run commands through adb with a command window? If so then fastboot technically should work. What's it list in device manager under android phone? Something composite. When I get home ill see what mine says when Im in fastboot.
Sent from Re-Engineered dInc

[Q] Unlock Bootloader Problem

Hi guys, I have a problem.
I want to flash my N1 with the Cyanogenmod, but I have a problem with Bootloader unlocking. I do exactly what here is written (in the N1 guide from wiki.cyanogenmod), but when I open CMD (win XP) and write "fastboot oem unlock", it just doesn't works, but "adb devices" works and shows my phone. What can I do ? Any ideas ?

You need to boot into bootloader to work with fastboot. And if "adb devices" shows your phone - you obviously didn't boot.
adb reboot bootloader
Click to expand...
Click to collapse
Also, for a more comprehensive guide, please read the Wiki.

Code:
C:\fastboot>fastboot oem unlock
'fastboot' is not recognized as a
operable program or batch file.
This is what it shows in bootloader mode.
P.S. I have already re-installed my drivers. I have to notice that when I try to reinstall the drivers (in fastboot mode), they always auto-install themselves and when I try to update them, they say that there isn't newer version.

Fastboot executable isn't in the same directory as ADB executable, and isn't in the path you're executing it from (which is C:\fastboot).
Check, what is the actual executable you're trying to run, and if you have one. It might be called fastboot-windows.exe, if you didn't get it from downloading the Android SDK.

There is a executable file named "fastboot-windows.exe", but when I try to run it, it just open and close for 1 second. Any ideas ?

I thought the message would be clear by now... Oh well.
Open command prompt.
Run:
fastboot-windows oem unlock
Click to expand...
Click to collapse

I think It's done but my computer shows this message (see attached) 5 mins and I don't know it's ready or not ? Could I turn on the phone ? (Sry for the easy questions but I'm a real noob, because that's my 1st Android phone.)

The "too many links" message doesn't look good.
Reboot your computer.
Reboot the phone.
Use different USB port in your computer.

Ok well if you want my input try "fastboot devices" this should return your S/N (starting with "HT") if it gives you the same error then I would reinstall the SDK.

How to update firmware to support newer ROM

HI..I'm a complete noob when it comes to this. Somebody helped me install an older ROM 4.1.2, sense 5, 1.31.651.2 to use on another network and I want to install a newer ROM with better firmware...mostly because 3g is really slow here, sometimes doesnt even register and I think the radio can be better.
Can i use TWRP thats on my phone to flash a newer firmware before I flash the ROM? If so, do i have to wipe before I do that? How else may I update the firmware?
Thanks for your help.

You should always wipe before flashing a new ROM, but you only need to wipe system, data and cache (dalvik cache as wll if you have that option) - NEVER wipe internal storage or you will lose the rom file and likely have to RUU.
Here http://forum.xda-developers.com/showthread.php?t=2795856 is a link to the most recent firmware which comes with a brief tutorial as to how to flash the firmware using fastboot. If you are a noob, you will want the one that says "modified firmware with hboot and recovery removed" since you want to keep TWRP.
You will need to connect your phone to your pc while it is in the bootloader. You can get into the bootloader by turning your phone off, then holding volume down and the power key until a while screen comes up that says "Hboot" near the top. If you don't have ADB and/or the android sdk on your computer, you will need to get that first and then you will need to open a command prompt in the same folder where "fastboot.exe" is after installing the android sdk.
So again, you will download the extracted firmware, and also download the android sdk. Once android sdk is installed, navigate to the folder on your computer called "adb" and ensure that you can find "fastboot.exe". Once you have found this folder, copy the firmware file into the adb folder and rename it "firmware". Then hold shift and right click in the folder and select "open a command prompt here". After that, reboot your phone to the bootloader and plug in your phone to your computer. Then follow the instructions for flashing firmware at the link I posted.
You do not need to wipe prior to installing firmware. You should flash the new firmware before you flash a new rom since the firmware will work with any rom but the new roms only work with the new firmware. Wouldn't want to install a new rom only to find out you can't figure out how to install firmware.

Thank you very much for your reply The_mamba. I appreciate the time you took to write that all out. Can't wait to give it a shot.

[email protected] said:
Thank you very much for your reply The_mamba. I appreciate the time you took to write that all out. Can't wait to give it a shot.
Click to expand...
Click to collapse
No problem, I wouldn't know what I know if not for people taking the time to explain it. Let me know if you run into any problems or you need me to elaborate on any instructions.

The_mamba said:
No problem, I wouldn't know what I know if not for people taking the time to explain it. Let me know if you run into any problems or you need me to elaborate on any instructions.
Click to expand...
Click to collapse
So I downloaded adb, found fastboot.exe and tried following the directions but once I typed the command it just said "waiting on device". I extracted and renamed the folder and even tried it compressed...reason being the directions said to rename it firmware.zip but after it was extracted it's not a zip file anymore. I don't even know if that's the issue just something I wanted to bring up.
I also made sure my device said fastboot usb as well.
Other notes
I didn't download sdk, just an abbreviated adb. My computer says it doesn't recognize the device as soon as I get to fastboot usb. Under file name it says compressed file then .zip...can the command be wrong? Lastly, I hold shift and open a command within the folder that houses fastboot.exe and firmware among a few other files correct?

[email protected] said:
So I downloaded adb, found fastboot.exe and tried following the directions but once I typed the command it just said "waiting on device". I extracted and renamed the folder and even tried it compressed...reason being the directions said to rename it firmware.zip but after it was extracted it's not a zip file anymore. I don't even know if that's the issue just something I wanted to bring up.
I also made sure my device said fastboot usb as well.
Other notes
I didn't download sdk, just an abbreviated adb. My computer says it doesn't recognize the device as soon as I get to fastboot usb. Under file name it says compressed file then .zip...can the command be wrong? Lastly, I hold shift and open a command within the folder that houses fastboot.exe and firmware among a few other files correct?
Click to expand...
Click to collapse
Couple things: The abridged adb should be fine, it sounds like your computer is not recognizing the phone. Things to try for that is use a different USB port (sounds stupid but this often works) and make sure you have the most updated HTC drivers for the phone installed on your computer. You may want to ensure that your abridged ADB came with the adb and fastboot drivers as well. Also, you do not need to extract the firmware zip file that you download, just rename it. Literally just copy the downloaded firmware to the adb folder, rename it, and flash. You are correct about the command prompt window, you just want to open the command prompt from that folder so you don't have to navigate to the adb folder once in command prompt. As long as you open the command prompt from the folder it should say something like "C:\adb>" with a blinking underscore. Obviously if you didn't install adb to the root of your C:/ drive then it will say wherever you installed it.
Commands in order (once phone is in fastboot mode and recognized) should be:
fastboot oem rebootRUU (this will reboot the phone to a black screen with silver htc logo)
fastboot flash zip firmware.zip
(then it will run several lines of code and hopefully say "Success!")
fastboot reboot
Be cognizant of spaces and such.
Let me know if you still can't get it to work.

The_mamba said:
Couple things: The abridged adb should be fine, it sounds like your computer is not recognizing the phone. Things to try for that is use a different USB port (sounds stupid but this often works) and make sure you have the most updated HTC drivers for the phone installed on your computer. You may want to ensure that your abridged ADB came with the adb and fastboot drivers as well. Also, you do not need to extract the firmware zip file that you download, just rename it. Literally just copy the downloaded firmware to the adb folder, rename it, and flash. You are correct about the command prompt window, you just want to open the command prompt from that folder so you don't have to navigate to the adb folder once in command prompt. As long as you open the command prompt from the folder it should say something like "C:\adb>" with a blinking underscore. Obviously if you didn't install adb to the root of your C:/ drive then it will say wherever you installed it.
Commands in order (once phone is in fastboot mode and recognized) should be:
fastboot oem rebootRUU (this will reboot the phone to a black screen with silver htc logo)
fastboot flash zip firmware.zip
(then it will run several lines of code and hopefully say "Success!")
fastboot reboot
Be cognizant of spaces and such.
Let me know if you still can't get it to work.
Click to expand...
Click to collapse
Hey. Thanks for the last reply. I did everything you recommended but it still didn't work. I used two different usb cables, 3 different ports, and I keep getting the message I attached. However, htc sync worked albeit it gave me a warning message and said I needed a different driver and it downloaded it before it registered. Do you think my version is too outdated to be supported? I tried this HTC-Mobile-Driver_v4.16.0.001.exe and HTC-Mobile-Driver-v4.17.0.001 (1).zip and a website recommended this HTC_BMP_USB_Driver_x64_1.0.5375.msi but none helped.
I do get a noise every time I plug in and unplug the usb, so that seems to be working. USB debugging should be enabled correct?
Lastly and hopefully this is the main problem: when I turn off the phone and plug it in to the computer, I receive a message that say "The connected charger will take longer to charge. To charge faster, use the original charger and cable that were provided with this phone." I'm not sure if that's because its low voltage being delivered from the usb or the cable is actually not adequate, I will google that.
Also failed to mention my computer is running on Windows 10

[email protected] said:
Hey. Thanks for the last reply. I did everything you recommended but it still didn't work. I used two different usb cables, 3 different ports, and I keep getting the message I attached. However, htc sync worked albeit it gave me a warning message and said I needed a different driver and it downloaded it before it registered. Do you think my version is too outdated to be supported? I tried this HTC-Mobile-Driver_v4.16.0.001.exe and HTC-Mobile-Driver-v4.17.0.001 (1).zip and a website recommended this HTC_BMP_USB_Driver_x64_1.0.5375.msi but none helped.
I do get a noise every time I plug in and unplug the usb, so that seems to be working. USB debugging should be enabled correct?
Lastly and hopefully this is the main problem: when I turn off the phone and plug it in to the computer, I receive a message that say "The connected charger will take longer to charge. To charge faster, use the original charger and cable that were provided with this phone." I'm not sure if that's because its low voltage being delivered from the usb or the cable is actually not adequate, I will google that.
Click to expand...
Click to collapse
Hmmmm, interesting. Are you using usb ports on the front of the computer or the back? Sometimes the ones on the front aren't as good as the ones directly on the mainboard so if you haven't already then you could try the back ones. Also, despite using two cables, I guess there is still a chance that your cables are to blame. It concerns me that you are still getting driver errors even after updating sync so you may want to keep trying to solve the driver aspect. Here is an excerpt from a post on another forum I found that may be relevant:
"If you have the full AndroidSDK installed, check your device manager for an unknown device. If you find one that's supposed to be your phone, update the driver and use the driver in SDK directory\extras\google\usb_driver . If that still doesn't work, make sure you don't have HTC Sync running on your computer. It will hose the entire deal."
So try checking out your device manager regarding the driver and also be sure to close HTC sync completely (including the system tray icon if applicable) before plugging your phone in with bootloader up.
Check out the whole tread in general for some good tips: http://forums.androidcentral.com/rezound-rooting-roms-hacks/209934-stuck-waiting-device-after-fastboot-command.html
Keep me posted, I'm invested now, haha.

How To Guide [GUIDE] Unbrick Lenovo Y700 tablet

Windows guide, might work for other aswell.
I finally solved my problem with my Lenovo Y700 tablet being stuck in bootloop mode due to trying to flash Magisk boot with a mismatched firmware version. This resulted in the UI constantly crashing, and I could not connect to Wi-Fi, and other problems...
I tried flashing back to stock with QFIL, which put the device in a bootloop. I will explain why later on.
I also lost recovery mode due to trying to solve the problem, and now I was stuck with either showing the bootloader screen, or restarting the tablet, which brought me back to the bootloader.
So the tablet was now genuinely useless. This is what I did to bring back the stock ROM and later flash to crDroid 8.10.
Flashing boot.img, system.img or recovery.img was no luck.
First off, there is no need to have unlocked "USB debugging" before your tablet bricked.
Second, you don't need to have your "sn.img" file from Lenovo, you can unlock the bootloader using fastboot commands.
Fastboot commands works on the bootloader screen, without having ADB connection.
Start by downloading these four files:
Platform tools r33.0.2
QPST_2.7.496
Qualcomm_USB_Driver_v1.0
Lenovo Y700 tablet stock ROM
We'll start by unlocking your bootloader. You can do this from the bootloader screen. If you for some reason can enter recovery mode, enter fastboot.
1. Connect your tablet to your PC.
2. Open a terminal windows in the ADB folder. On Windows 11 this can be done by right-clicking inside the ADB folder and select "Open in terminal". If you don't have that option, try Shift + Right-click. If that doesn't work, you can always start the terminal by pressing Win + R, and type in "cmd" without citations. Now you have to navigate to your ADB folder by typing
Code:
cd (here you'll type in the location of your ADB folder)
Without the brackets.
3. When located, type in
Code:
fastboot devices
You should see your tablet in the list.
If not, try using another cable or USB port on your PC.
4. Now type in
Code:
fastboot oem unlock-go
Restart your tablet, and it should now say "unlocked" under "DEVICE STATE" in the bootloader.
5. Now you can start by installing the programs on your PC, QTPS, Qualcomm driver and platform tools.
6. Extract ALL files from your stock ROM to the "bin" folder in QTPS location (usually C:\Program Files (x86)\Qualcomm\QPST).
This will help with Sahara errors in QFIL.
7. Open QFIL from your QTPS bin folder, it installs with QTPS. Don't worry if it shows "No Port Available", we'll get to that. Your configuration should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your main window should look like this:
Don't worry about the "status" window.
Hit "browse" in the "Programmer Path" window, and navigate to your QTPS bin folder. Select "prog_firehose_ddr.elf"
Hit "Load XML", and navigate to your QTPS bin folder. Now, select ALL of the "rawprogram" files (my first mistake, I only selected the "rawprogram_unsparse0.xml" file on first flash)
In the next window, select ALL of the "patch" files (my second mistake, I only selected the "patch0.xml file" on first flash).
Without doing this, you will only flash a portion of the ROM, and not all of the partitions needed.
8. Now it's time to reboot you tablet into EDL mode to be able to flash. Start your tablet by pressing VolUp + Power button.
If you can't turn off your tablet when connected to PC, just select "Power off", and just hold the VolUp button as soon as the device vibrates and reboots, keep holding until the screen flickers and turns off.
9. Now QFIL should detect the Qualcomm 9008 port. If not, hit "Select Port" and select the Qualcomm 9008 port.
10. Hit the now available "Download" button, and the flashing should begin. Allow it to run its course, and it should reboot the tablet when done. Might take a while.
If flashing won't start properly, you might have waited too long between entering EDL mode and hitting the "Download" button.
If so, disconnect your device, which might now be "dead".
Don't worry, you can fix this be holding VolUp + VolDown + Power button for a long time, say about a minute to be sure. Release the Volume keys some second before releasing the Power button.
Hit the power button again, and the tablet should boot to bootloader screen again.
Repeat the steps to enter EDL mode, and now hit the "Download" button in QFIL when it becomes available, don't wait too long.
You're done! ​I recommend opening "Settings", enable "Developer" option, by pressing the "Build number" on the "About tablet" screen repeatedly until a pop-up appears saying "You are now a developer".
Open "Developer options" and hit "Enable USB debugging", it will allow you to run ADB commands from your platform tools folder.
If you want, you can again open the terminal in the platform tools folder and type
Code:
adb devices
It should now show your device in the list.
Now you can uncheck the "OEM unlocking" in the "Developer options" which should let you get OTA updates when available.
There are plenty of guides on how to flash different GSI's like crDroid, so I won't cover that here.
Enjoy your tablet!

For whatever reason, my devices isn't showing up when writing "fastboot devices" but shows up in QFIL. Any suggestions?

Joncka said:
Windows guide, might work for other aswell.
I finally solved my problem with my Lenovo Y700 tablet being stuck in bootloop mode due to trying to flash Magisk boot with a mismatched firmware version. This resulted in the UI constantly crashing, and I could not connect to Wi-Fi, and other problems...
I tried flashing back to stock with QFIL, which put the device in a bootloop. I will explain why later on.
I also lost recovery mode due to trying to solve the problem, and now I was stuck with either showing the bootloader screen, or restarting the tablet, which brought me back to the bootloader.
So the tablet was now genuinely useless. This is what I did to bring back the stock ROM and later flash to crDroid 8.10.
Flashing boot.img, system.img or recovery.img was no luck.
First off, there is no need to have unlocked "USB debugging" before your tablet bricked.
Second, you don't need to have your "sn.img" file from Lenovo, you can unlock the bootloader using fastboot commands.
Fastboot commands works on the bootloader screen, without having ADB connection.
Start by downloading these four files:
Platform tools r33.0.2
QPST_2.7.496
Qualcomm_USB_Driver_v1.0
Lenovo Y700 tablet stock ROM
We'll start by unlocking your bootloader. You can do this from the bootloader screen. If you for some reason can enter recovery mode, enter fastboot.
1. Connect your tablet to your PC.
2. Open a terminal windows in the ADB folder. On Windows 11 this can be done by right-clicking inside the ADB folder and select "Open in terminal". If you don't have that option, try Shift + Right-click. If that doesn't work, you can always start the terminal by pressing Win + R, and type in "cmd" without citations. Now you have to navigate to your ADB folder by typing
Code:
cd (here you'll type in the location of your ADB folder)
Without the brackets.
3. When located, type in
Code:
fastboot devices
You should see your tablet in the list.
If not, try using another cable or USB port on your PC.
4. Now type in
Code:
fastboot oem unlock-go
Restart your tablet, and it should now say "unlocked" under "DEVICE STATE" in the bootloader.
5. Now you can start by installing the programs on your PC, QTPS, Qualcomm driver and platform tools.
6. Extract ALL files from your stock ROM to the "bin" folder in QTPS location (usually C:\Program Files (x86)\Qualcomm\QPST).
This will help with Sahara errors in QFIL.
7. Open QFIL from your QTPS bin folder, it installs with QTPS. Don't worry if it shows "No Port Available", we'll get to that. Your configuration should look like this:
View attachment 5741653
Your main window should look like this:
View attachment 5741651
Don't worry about the "status" window.
Hit "browse" in the "Programmer Path" window, and navigate to your QTPS bin folder. Select "prog_firehose_ddr.elf"
Hit "Load XML", and navigate to your QTPS bin folder. Now, select ALL of the "rawprogram" files (my first mistake, I only selected the "rawprogram_unsparse0.xml" file on first flash)
In the next window, select ALL of the "patch" files (my second mistake, I only selected the "patch0.xml file" on first flash).
Without doing this, you will only flash a portion of the ROM, and not all of the partitions needed.
8. Now it's time to reboot you tablet into EDL mode to be able to flash. Start your tablet by pressing VolUp + Power button.
If you can't turn off your tablet when connected to PC, just select "Power off", and just hold the VolUp button as soon as the device vibrates and reboots, keep holding until the screen flickers and turns off.
9. Now QFIL should detect the Qualcomm 9008 port. If not, hit "Select Port" and select the Qualcomm 9008 port.
10. Hit the now available "Download" button, and the flashing should begin. Allow it to run its course, and it should reboot the tablet when done. Might take a while.
If flashing won't start properly, you might have waited too long between entering EDL mode and hitting the "Download" button.
If so, disconnect your device, which might now be "dead".
Don't worry, you can fix this be holding VolUp + VolDown + Power button for a long time, say about a minute to be sure. Release the Volume keys some second before releasing the Power button.
Hit the power button again, and the tablet should boot to bootloader screen again.
Repeat the steps to enter EDL mode, and now hit the "Download" button in QFIL when it becomes available, don't wait too long.
You're done! ​I recommend opening "Settings", enable "Developer" option, by pressing the "Build number" on the "About tablet" screen repeatedly until a pop-up appears saying "You are now a developer".
Open "Developer options" and hit "Enable USB debugging", it will allow you to run ADB commands from your platform tools folder.
If you want, you can again open the terminal in the platform tools folder and type
Code:
adb devices
It should now show your device in the list.
Now you can uncheck the "OEM unlocking" in the "Developer options" which should let you get OTA updates when available.
There are plenty of guides on how to flash different GSI's like crDroid, so I won't cover that here.
Enjoy your tablet!
Click to expand...
Click to collapse
I got one with the "GLOBAL ROM" which miss a lot of feature so I follow this tutorial to flash the stock rom and works like a charm.
The only question is why I can't get any OTA?
Due to te unlocked bootloader?
I tried to relock it but when it's done it say "device corrupted" on bootup so I had to unlock again and reflash all again.

Ale_ax said:
I got one with the "GLOBAL ROM" which miss a lot of feature so I follow this tutorial to flash the stock rom and works like a charm.
The only question is why I can't get any OTA?
Due to te unlocked bootloader?
I tried to relock it but when it's done it say "device corrupted" on bootup so I had to unlock again and reflash all again.
Click to expand...
Click to collapse
Yes, this one is weird. Some people are able to lock it, and some are not.
To my understanding you need to lock it to get OTA's. It's still possible to update, though, through downloading the newer update and installing the update in .zip format on stock ROM.

Is possible to find the update package? I find 2 in the other y700 thread but they are incremental from an above version of mine and won’t install
Also searched a day on Chinese forum but no succes…
Which version do you have installed?

Ale_ax said:
Is possible to find the update package? I find 2 in the other y700 thread but they are incremental from an above version of mine and won’t install
Also searched a day on Chinese forum but no succes…
Which version do you have installed?
Click to expand...
Click to collapse
See if you can find the right incremental updates here: https://drive.google.com/drive/u/0/mobile/folders/1BZuFF4ZwYHCjIWua-INiEFe1YItjAYz2
I'm on crDroid, I just flashed from the standard 13.0.586 ROM.

Joncka said:
See if you can find the right incremental updates here: https://drive.google.com/drive/u/0/mobile/folders/1BZuFF4ZwYHCjIWua-INiEFe1YItjAYz2
I'm on crDroid, I just flashed from the standard 13.0.586 ROM.
Click to expand...
Click to collapse
Thank you, btw they are for the "TB-J716F" Xiaoxin pad pro 2021n, Legion Y700 is "TB-9707F"

Ale_ax said:
Is possible to find the update package? I find 2 in the other y700 thread but they are incremental from an above version of mine and won’t install
Also searched a day on Chinese forum but no succes…
Which version do you have installed?
Click to expand...
Click to collapse
hi, in my case after fresh flash to zui 13 official i can use ota to zui 14 even the tablet in unlocked state, someone in xiaoxin pad pro thread suggested using vpn 'returness' set to china (shanghai 11) i think... and ota did works, zui 14 is about 3 half gig so i ended up using link from y700 thread to install manually

Just for anyone else having trouble getting into EDL mode (my Y700 wasn't bricked, I just wanted to restore stock rom):
When the tablet is running normally, go to developer options, enable USB debugging, then go to the platform-tools folder on your PC and open a command prompt there, then type "adb reboot edl". Then you'll see the "Qualcomm HS-USB QDloader 9008 (COMxx)" Port under Ports in Device Manager.
To re-lock, I believe you can use these instructions. The command "fastboot flashing lock" brought up the menu on the Y700 screen to re-lock, but I didn't do it because I didn't want to delete my user data (I'd just spent time setting up all my apps!)
When I was in fastboot, the tablet was showing up with an exclamation point and just called, "Android device" in Device manager, I used the drivers from here to get it to show up as "Android Bootloader Interface".

Don't do what I just wrote!! I did it and now I'm stuck and it won't boot, and I can't get to EDL mode.
I don't have time to work on it now but my tablet is effectively bricked.
I'm in a bootloop to the fastboot screen, and it shows up in Device Manager as "Android Bootloader Interface". I can't flash in QFIL as described above because it just says "No Port Available". I can't get to EDL mode as I did before because I can't boot the tablet as usual to enter the "adb reboot edl" command.
"adb devices" doesn't show the Y700.
Can anyone tell me how to get to EDL mode when I can't get adb to work?

Ale_ax said:
I tried to relock it but when it's done it say "device corrupted" on bootup so I had to unlock again and reflash all again.
Click to expand...
Click to collapse
That's what happened to me! How did you get it back into EDL mode after unlocking?
Mine isn't showing the Qualcomm device under Ports in Device Manager anymore, so I can't get the port to show in QFIL!!

Got it to work getting to EDL mode, phew!
If you can't turn off your tablet when connected to PC, just select "Power off", and just hold the VolUp button as soon as the device vibrates and reboots, keep holding until the screen flickers and turns off.
Click to expand...
Click to collapse
This got the Qualcomm port to show up again.
So I'm now running the stock rom but still unlocked so no OTA. What a waste of time that was.
Hoping someone can work out how to re-lock.

shahrul5689 said:
hi, in my case after fresh flash to zui 13 official i can use ota to zui 14 even the tablet in unlocked state, someone in xiaoxin pad pro thread suggested using vpn 'returness' set to china (shanghai 11) i think... and ota did works, zui 14 is about 3 half gig so i ended up using link from y700 thread to install manually
Click to expand...
Click to collapse
Yep, I can get ota with that vpn
gnoted said:
Got it to work getting to EDL mode, phew!
This got the Qualcomm port to show up again.
So I'm now running the stock rom but still unlocked so no OTA. What a waste of time that was.
Hoping someone can work out how to re-lock.
Click to expand...
Click to collapse
you have to use Chinese vpn, it’s not because of unlocked booloader, I will link you the one I used later, btw no need to relock bootloader, for getting ota

Ale_ax said:
Yep, I can get ota with that vpn
you have to use Chinese vpn, it’s not because of unlocked booloader, I will link you the one I used later, btw no need to relock bootloader, for getting ota
Click to expand...
Click to collapse
Haha, maybe I should read more of the comments before assuming things.

Hic, I just got a second hand Y700, it had an original Zui 13 chinese rom, and I started to OTA update upto ZUI 14. Then the Google Play disappeared, also the PC mode. I tried to downgrade to ZUI 13 with this guide WITHOUT enabling usb debugging nor oem unlock. The flashing process succeeded, but when the tablet reboots, it shows for the first time "Your device is corrupt, It can't be trusted and will not boot", after that keeps showing bootloader menu.
Please help me what to do from this step?

I'm in a different state from others here, I think; my Y700 appears to be totally bricked. It's plugged in to charge and nothing's happening at all. I originally installed crDroid on it, but ran into Widevine issues and was going to revert. I don't remember the last steps I took on it (it was a month or so ago), but when I picked it up again a few days ago, turning it on showed only a black screen (only detectable by seeing the backlight), so I let it discharge the battery entirely planning to try and fix it via reflash later. Now, however, it's doing... nothing.
I'm going to let it charge overnight and see if that changes anything, but if anybody has ideas what might have happened or things to try to get out of this, I'd appreciate it!

Hi, I'm stuck after flashing the Chinese stock rom on my legion y700. I was first successful except for upgrades which were proposed and installed but wouldn't show after reboot. I decided to flash again hoping that would solve the problem. But now my tablet remains in EDM mode and won't start. The final message in Qfil was 'download successful'. It is fully charged
Any idea on how to solve this issue?

I am in yet another state. I only run Linux (Mint 21), and have not been able to get any version of wine working, so I cannot use QPST or QFIL (windows .exe's). I CAN access my Y700 via adb or fastboot, and it is now unlocked. It was unsealed when it arrived, but does NOT have any google stuff on it.
I have downloaded all of the components needed from apkmirror, and followed instructions in the Y700 topic to activate them, to no avail.
Sadly, since I do not read Chinese, and the use requirement needs google, it might as well be a brick.
Further, despite more than 40 years doing technical support on all sorts of computers, I have never yet flashed an android device. Can it be done from adb or fastboot? If so, how do I specify which partition to flash? Does anyone have a guide to help me get started? I wish to put cdroid on it, do I use the .xz file or extract the .img?

OK, I've just found something I missed, but it doesn't work for me. My terminal is in the same folder as the .img
fastboot flash boot crDroid-8.10-arm64_bgN-Unofficial.img
Sending sparse 'boot_b' 1/15 (262088 KB) OKAY [ 8.186s]
Writing 'boot_b' FAILED (remote: 'Value too large for defined data type')
fastboot: error: Command failed
What am I missing (apart from a brain!) is this the correct partition to write crDroid to? is there an option to set the data type size? if so what?

Joncka said:
Windows guide, might work for other aswell.
I finally solved my problem with my Lenovo Y700 tablet being stuck in bootloop mode due to trying to flash Magisk boot with a mismatched firmware version. This resulted in the UI constantly crashing, and I could not connect to Wi-Fi, and other problems...
I tried flashing back to stock with QFIL, which put the device in a bootloop. I will explain why later on.
I also lost recovery mode due to trying to solve the problem, and now I was stuck with either showing the bootloader screen, or restarting the tablet, which brought me back to the bootloader.
So the tablet was now genuinely useless. This is what I did to bring back the stock ROM and later flash to crDroid 8.10.
Flashing boot.img, system.img or recovery.img was no luck.
First off, there is no need to have unlocked "USB debugging" before your tablet bricked.
Second, you don't need to have your "sn.img" file from Lenovo, you can unlock the bootloader using fastboot commands.
Fastboot commands works on the bootloader screen, without having ADB connection.
Start by downloading these four files:
Platform tools r33.0.2
QPST_2.7.496
Qualcomm_USB_Driver_v1.0
Lenovo Y700 tablet stock ROM
We'll start by unlocking your bootloader. You can do this from the bootloader screen. If you for some reason can enter recovery mode, enter fastboot.
1. Connect your tablet to your PC.
2. Open a terminal windows in the ADB folder. On Windows 11 this can be done by right-clicking inside the ADB folder and select "Open in terminal". If you don't have that option, try Shift + Right-click. If that doesn't work, you can always start the terminal by pressing Win + R, and type in "cmd" without citations. Now you have to navigate to your ADB folder by typing
Code:
cd (here you'll type in the location of your ADB folder)
Without the brackets.
3. When located, type in
Code:
fastboot devices
You should see your tablet in the list.
If not, try using another cable or USB port on your PC.
4. Now type in
Code:
fastboot oem unlock-go
Restart your tablet, and it should now say "unlocked" under "DEVICE STATE" in the bootloader.
5. Now you can start by installing the programs on your PC, QTPS, Qualcomm driver and platform tools.
6. Extract ALL files from your stock ROM to the "bin" folder in QTPS location (usually C:\Program Files (x86)\Qualcomm\QPST).
This will help with Sahara errors in QFIL.
7. Open QFIL from your QTPS bin folder, it installs with QTPS. Don't worry if it shows "No Port Available", we'll get to that. Your configuration should look like this:
View attachment 5741653
Your main window should look like this:
View attachment 5741651
Don't worry about the "status" window.
Hit "browse" in the "Programmer Path" window, and navigate to your QTPS bin folder. Select "prog_firehose_ddr.elf"
Hit "Load XML", and navigate to your QTPS bin folder. Now, select ALL of the "rawprogram" files (my first mistake, I only selected the "rawprogram_unsparse0.xml" file on first flash)
In the next window, select ALL of the "patch" files (my second mistake, I only selected the "patch0.xml file" on first flash).
Without doing this, you will only flash a portion of the ROM, and not all of the partitions needed.
8. Now it's time to reboot you tablet into EDL mode to be able to flash. Start your tablet by pressing VolUp + Power button.
If you can't turn off your tablet when connected to PC, just select "Power off", and just hold the VolUp button as soon as the device vibrates and reboots, keep holding until the screen flickers and turns off.
9. Now QFIL should detect the Qualcomm 9008 port. If not, hit "Select Port" and select the Qualcomm 9008 port.
10. Hit the now available "Download" button, and the flashing should begin. Allow it to run its course, and it should reboot the tablet when done. Might take a while.
If flashing won't start properly, you might have waited too long between entering EDL mode and hitting the "Download" button.
If so, disconnect your device, which might now be "dead".
Don't worry, you can fix this be holding VolUp + VolDown + Power button for a long time, say about a minute to be sure. Release the Volume keys some second before releasing the Power button.
Hit the power button again, and the tablet should boot to bootloader screen again.
Repeat the steps to enter EDL mode, and now hit the "Download" button in QFIL when it becomes available, don't wait too long.
You're done! ​I recommend opening "Settings", enable "Developer" option, by pressing the "Build number" on the "About tablet" screen repeatedly until a pop-up appears saying "You are now a developer".
Open "Developer options" and hit "Enable USB debugging", it will allow you to run ADB commands from your platform tools folder.
If you want, you can again open the terminal in the platform tools folder and type
Code:
adb devices
It should now show your device in the list.
Now you can uncheck the "OEM unlocking" in the "Developer options" which should let you get OTA updates when available.
There are plenty of guides on how to flash different GSI's like crDroid, so I won't cover that here.
Enjoy your tablet!
Click to expand...
Click to collapse
A lot of this does not seem to work on Linux (Mint 20.3).
fastboot flashing unlock
worked for me, and while I have no problem getting into recovery or fastboot modes on my Y700, I never see anything I recognize as EDL. On a machine with 'wine' installed and working, QTSP installs and appears to run OK, as also does QFIL. I can select the "rawprogram" and "patch" files OK, but it cannot find a port.
Both adb devices and fastboot devices report the correct device when it is in the appropriate mode, and
fastboot flash system crDroid-8.10-arm64_bgN-Unofficial.img appears to have successfully flashed correctly, but it is still unable to communicate with Google servers. All good (tear hair out type) fun!