Revisiting key combinations, and getting to fastbootD - OnePlus 6T Guides, News, & Discussion

[Sorry, this belongs in the Q & A area, but there's no option to delete or move it.]
Here are the hardware button combinations that work on my OnePlus 6T:
[volume up + power] hold until you see the red dot logo, then release theyour phone will boot to system.
[volume down + power] hold for a few seconds until the black and white keyboard appears (maybe the keyboard is only if you have a login PIN set up?) this will boot the phone to recovery mode.
[volume up + volume down + power] hold for a few seconds until you see the Fastboot label then release. This will put the in bootloader mode.
Starting with the phone powered off and NOT connected to your computer, press and hold [volume up + volume down] as you plug the phone into your computer. This will put the phone into EDL mode, which is required in order to use the MSM tool. The screen of the phone will be black but if you followed the procedure the Qualcomm device should appear under the Ports section of Windows Device Manager.
I was unable to get to FastbootD. Here's what happened when I tried various commands:
1.) when in regular fastboot (bootloader) mode and connected to my PC via USB, from a command prompt I typed "fastboot reboot fastboot" the phone only rebooted to the operating system and not to the fastbootD screen.
2.) when in bootloader, as above, I typed "fastboot reboot bootloader", the phone rebooted to the regular fastboot screen. However, I suspected this was not the same thing as "fastboot reboot fastboot" because why would there be 2 identical commands?
3.) the "adb reboot" command would not work when I was in bootloader mode. Duh! I needed to be in ADB mode for ADB commands to work. In bootloader mode I needed to use a Fastboot command. Still, I had downloaded and unzipped the latest adb/fastboot tools and set up the Windows PATH to point to the unzipped folder. Also, I checked the version numbers of both from the command prompt but still [fastboot reboot fastboot] only rebooted my phone to system. What the heck!?
4.) this all seemed to happen after booting into EDL mode the day before. I booted into EDL mode so I could check if I had the proper Qualcomm driver installed (incase I had to use the MSM tool --yes the driver was installed and functioning). I didn't actually need to use the MSM tool at that time so I didn't ever run it but I'd had some difficulty getting the phone to reboot to system so I assumed my trouble with fastbootD originated with that. Wrong!
SOLUTION: It turned out to be a hidden instance of outdated adb/fastboot that kept running in lieu of the newly downloaded copies, in spite of my having correctly set up the Windows PATH. (more on this below in my reply of Jan 9, 2022).

So adb reboot recovery
And
adb reboot bootloader
Dosent work?

Kenora_I said:
So adb reboot recovery
And
adb reboot bootloader
Dosent work?
Click to expand...
Click to collapse
adb reboot recovery does work. Weirdly, adb reboot bootloader will work ONCE then if I try to issue the command a second time, adb can't see my device. If I unplug the phone from USB, restart the phone then plug it back in, I can again use adb once.

Fastboot logo is showing?

Kenora_I said:
Fastboot logo is showing?
Click to expand...
Click to collapse
what would a fastboot logo look like?

The words fastboot. Will be shown

Kenora_I said:
The words fastboot. Will be shown
Click to expand...
Click to collapse
I can get to fastboot. Just not by using the volume up + power combo and I can't re-enter fastboot by using [fastboot reboot fastboot] from the command line. The command line issue is of more importance, ultimately, but I think it's reasonable to assume the root cause of both is the same since they happened at the same time.

Can you check if System>Developer Options>Advanced Reboot is enabled?

FakeGemstone said:
I can get to fastboot. Just not by using the volume up + power combo and I can't re-enter fastboot by using [fastboot reboot fastboot] from the command line. The command line issue is of more importance, ultimately, but I think it's reasonable to assume the root cause of both is the same since they happened at the same time.
Click to expand...
Click to collapse
It changed at some point and OP never updated their docs. (I think it changed when A10 hit).
To get into fastboot mode. You now have to make sure you're not connected to USB and hold vol+, vol-, and power and that will launch fastboot mode.
Also maybe semi related if it's not launching at all, is to do a factory reset from within the OS. I had a really odd issue recently with recovery mode and it not booting into recovery from fastboot, adb, or key combo press. Factory reset from within the OS somehow fixed it.

psychen6 said:
Can you check if System>Developer Options>Advanced Reboot is enabled?
Click to expand...
Click to collapse
Yes, I have this option enabled. Using this method is one of the ways I am able to get to fastboot. I am just not able to get to fastboot using [fastboot reboot fastboot] from a command prompt (used to work just fine) and I am not able to get to fastboot by holding the [volume up + power] (this also used to work just fine).

hartleyshc said:
It changed at some point and OP never updated their docs. (I think it changed when A10 hit).
To get into fastboot mode. You now have to make sure you're not connected to USB and hold vol+, vol-, and power and that will launch fastboot mode.
Also maybe semi related if it's not launching at all, is to do a factory reset from within the OS. I had a really odd issue recently with recovery mode and it not booting into recovery from fastboot, adb, or key combo press. Factory reset from within the OS somehow fixed it.
Click to expand...
Click to collapse
I don't know about that. A few days ago volume up + power used to work just fine. Also a few days ago, I also used to be able to issue fastboot reboot fastboot from a command line and have it work fine.
Now what happens when issue the command fastboot reboot fastboot is that my phone appears to begin the reboot cycle. A message in the command window appears, "rebooting into fastboot" then on the next line, "< waiting for any device >" and meanwhile my phone just boots into the Oxygen OS. If at that point I select "bootloader" from the advanced power button menu, the phone reboots into fastboot and the message in the command window reads, "fastboot: error: failed to boot into userspace fastboot; one or more components might be unbootable."
If I then issue the command, fastboot reboot bootloader, that reboots promptly into fastboot, but I don't believe "bootloader fastboot" is the same thing as "userspace fastboot", although the states look identical on the screen.

After revisiting this issue again and reading every post I could find I realized the only explanation was outdated fastboot, and since they're packaged together, adb also. This time I did a extra thorough search of all the drives and sure enough there was a super old instance of adb.exe & fastboot.exe in a place I'd never thought to look. So I deleted those files and now adb and fastboot work as expected.
I know, it seems obvious now. But there were references to those old files in windows system settings that took precedence over my PATH setting that I didn't realize were there. Ive since deleted those other references but I wanted to mention this in case other people are wondering why the PATH they set up isn't working.

Related

need help, installing ota zip to my nexus 6

Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help
hendyanto said:
Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help
Click to expand...
Click to collapse
Where does it say this and at what point? Your phone is 100% stock then, correct? You set up adb correctly?
We'll need more information than supplied. You should walk us through step by step
hendyanto said:
Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help
Click to expand...
Click to collapse
I was having the exact same problem last night, following the same instructions. I still could not figure out how to sideload the OTA, so I ended up just flashing the update and starting from fresh. Wish I had the answer for you.
Here was my thread asking pretty much the same thing: http://forum.xda-developers.com/nexus-6/help/disconnects-computer-entering-bootloader-t3230705
danarama said:
Where does it say this and at what point? Your phone is 100% stock then, correct? You set up adb correctly?
We'll need more information than supplied. You should walk us through step by step
Click to expand...
Click to collapse
100% Stock, yes! 1 week old.
Yes i have set up ADB
I have followed the instruction until this part (i cannot post any link sorry, not authorized by xda)
The following ADB commands are for Windows machines. If you’re using a Mac, just add “./” before each command, for example: “./adb reboot bootloader”.
Assuming you device is already connected to your computer via USB and USB Debugging is enabled, you need to re-start it in fastboot mode. Follow one of the two methods below. Option A may be preferable because it’s another confirmation that your computer recognizes your Nexus device.
A) Type “adb reboot bootloader”
B) Turn your device off, then turn it back on while holding down the relevant key combinations for your device. For many devices it’s Volume Up + Volume Down + Power. You can see what your device’s key combinations are here.
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
In the command window — make sure you are in the directory where ADB and Fastboot reside — type: “adb sideload [the full name of the file].zip” without the brackets around the file name.
The update will install and reach 100 percent.
Reboot and enjoy the latest version of Android Marshmallow.
Click to expand...
Click to collapse
(red arrow) and then the cmd says the null error, i am trying this now
I had the same problem. Turned MTP on and then it worked. You're told to turn it off but don't... Its in Settings-Storage-touch the ... Menu top right corner, USB settings and turn ON MTP mode. It worked well for me. I also used the Nexus Root Toolkit - makes things much easier!
Click to expand...
Click to collapse
My phone is able to rebooot (the options comes out sometimes after i did not do anything) and now optimising app (like it usually did after an OTA update)
hendyanto said:
100% Stock, yes! 1 week old.
Yes i have set up ADB
I have followed the instruction until this part (i cannot post any link sorry, not authorized by xda)
(red arrow) and then the cmd says the null error, i am trying this now
My phone is able to rebooot (the options comes out sometimes after i did not do anything) and now optimising app (like it usually did after an OTA update)
Click to expand...
Click to collapse
There are lots of additional steps in that guide and not always the simplest way of doing it.
First thing to do is boot into recovery.
- Turn off the phone.
- Hold volume down + power
- At the bootloader screen, use volume keys to navigate to recovery and press power to select#
- At the Red warning triangle, hold power then press volume up.
At this stage, type "adb devices" in your command prompt and see if it returns your serial number or not. If it does, you can follow the steps to use adb to flash the update.
Please note, the guide talks about USB debugging. This only works in android. Nothing you need to do needs to be done via android so this is nonsense. Also the MTP option only works in android, so setting this in settings as a fix is also nonsense.
danarama said:
There are lots of additional steps in that guide and not always the simplest way of doing it.
First thing to do is boot into recovery.
- Turn off the phone.
- Hold volume down + power
- At the bootloader screen, use volume keys to navigate to recovery and press power to select#
- At the Red warning triangle, hold power then press volume up.
At this stage, type "adb devices" in your command prompt and see if it returns your serial number or not. If it does, you can follow the steps to use adb to flash the update.
Please note, the guide talks about USB debugging. This only works in android. Nothing you need to do needs to be done via android so this is nonsense. Also the MTP option only works in android, so setting this in settings as a fix is also nonsense.
Click to expand...
Click to collapse
I cannot get my windows to detect the phone during recovery mode, it always disconnected at that point.
I'll try again when i have the time, thank you all.
hendyanto said:
I cannot get my windows to detect the phone during recovery mode, it always disconnected at that point.
I'll try again when i have the time, thank you all.
Click to expand...
Click to collapse
Could be a driver issue. You'll need to check device manager. Perhaps uninstall the existing drivers and let it auto detect.
Failing that, install the Naked driver from my adb and fastboot thread (Nexus 6 general > Sticky roll-up thread > Adb and fastboot. What is it?)
I had the same issue with you until i did the following: I used wugfresh's nexus utility. Then I downloaded the respective file from XDA and saved it in the same folder as the Wugfresh's tool. Restarted in Recovery mode and chose 'update from adb'. Connected the phone with the usb having USB debugging on from before going to recovery. Started the CMD window from Wugfresh's tool (Advanced Utilities -> Launch) and check that the phone is connected (I think "adb devices") . Then "adb sideload xxxx.zip" and waited for the process to finish.
Instruction here: androidpolice 2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/
You do not have to install the full Android utility. Just use wugfresh;s cmd screen. Good luck!
danarama said:
Could be a driver issue. You'll need to check device manager. Perhaps uninstall the existing drivers and let it auto detect.
Failing that, install the Naked driver from my adb and fastboot thread (Nexus 6 general > Sticky roll-up thread > Adb and fastboot. What is it?)
Click to expand...
Click to collapse
qwerty1gr said:
I had the same issue with you until i did the following: I used wugfresh's nexus utility. Then I downloaded the respective file from XDA and saved it in the same folder as the Wugfresh's tool. Restarted in Recovery mode and chose 'update from adb'. Connected the phone with the usb having USB debugging on from before going to recovery. Started the CMD window from Wugfresh's tool (Advanced Utilities -> Launch) and check that the phone is connected (I think "adb devices") . Then "adb sideload xxxx.zip" and waited for the process to finish.
Instruction here: androidpolice 2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/
You do not have to install the full Android utility. Just use wugfresh;s cmd screen. Good luck!
Click to expand...
Click to collapse
Thank you guys! But after this "happy"night, i woke up to the OTA for marshmallow arrived on my phone, so see you guys on the rooting section instead, Thank you thank you for the help

[SOLVED] Can't enter safe mode

The phone doesn't start after installing EdXposed and the Riru Core Magisk module.
I want to enter Safe mode, but it doesn't work. I somehow managed to enter safe mode previously out of pure coincidence (no idea what I did, I pressed some buttons and i got there during a boot sequence, but it was nothing like the tutorial that Google gives you on how to do it properly).
So, I read you can do it like this:
https://support.google.com/pixelphone/answer/2852139?hl=en
However, this doesn't work for me, here's my boot process:
Power on
Unlocked bootloader warning (I skip it)
Google logo shows up
Screen color calibration changes slightly
Google animation starts (i press volume down)
Google animation ends
Normal Google logo stays there for a few seconds
Loading bar appears
Loading bar stayed there overnight (phone doesn't get hot or anything)
Is there any way to:
Enter safe mode properly
Start a terminal in recovery mode (like TWRP) to use the mm module to disable Magisk
Have an on device file manager (like TWRP) to manually delete the app
Delete files using adb
Get a normal adb shell (not sideload)
EDIT 1:
Starting "rescue mode" via fastboot shows the bootloader warning again, then the Google logo and then it's stuck (no color shift, no animation). Same for "recovery mode".
I cannot connect via adb/fastboot while the Logo is showing.
EDIT 2:
I managed to start "rescue mode" by doing the following:
Press power button
Press power button again (Entry selected: "Start")
Press both volume buttons and don't release them (I'm getting desperate here lol)
Bootloader warning (not skipped)
Rescue mode shows up (opened up Android, says "No command")
I can connect via adb, but "adb shell" or any other useful command says "error: closed"
EDIT 3:
Wtf, I got an adb shell by doing the following inside rescue mode:
"adb shell" -> Error
"adb pull /system/" -> Error
"adb pull /etc/hosts" -> Error
Phone restarted
Bootloader warning (skipped it)
Google logo, Animation & loading bar
adb connected
EDIT 4:
I entered the adb shell and used "setprop persist.sys.safemode 1" (source) (which registered correctly), but after rebooting, the phone still loads forever.
EDIT 5:
Turns out Safe mode didn't work because of Magisk/Riru/EdExposed or whatever, so I disabled Magisk by "touch /cache/.disable_magisk" (source) and now I successfully booted into safe mode.
Can you type up a more coherent guide to what you did? I'm facing the same problem and hoping to fix it without having to wipe my phone again! Thanks!
cubsrule93 said:
Can you type up a more coherent guide to what you did? I'm facing the same problem and hoping to fix it without having to wipe my phone again! Thanks!
Click to expand...
Click to collapse
Using this will most likely get you booted up to fix what you need...
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
cubsrule93 said:
Can you type up a more coherent guide to what you did? I'm facing the same problem and hoping to fix it without having to wipe my phone again! Thanks!
Click to expand...
Click to collapse
Where are you stuck?

(Lenovo Smart Display 8" & 10") (Amber & Blueberry) AVB/Bootloader Unlock, Firmware

This guide supports the following devices: SD-8501F, SD-X701B, SD-X501F
How to Bootloader Unlock (Part 1 of 2):
1. You will need a USB A to USB C cable
2. You will need fastboot drivers on your PC
3. Unplug the power cable from your device
4. Remove the silicone cover from the bottom right of your device (Might be hard it has adhesive on the back)
5. Plug the USB C cable into the now revealed USB-C port
6. Hold the volume - button and plug in the power cord keep holding volume - for about 10-15 seconds (It is slow to boot to fastboot) Smart plugs or switches help so you don't damage the ports by replugging them constantly.
7. Keep holding volume - for about 10-15 seconds (It is slow to boot to fastboot)
8. Once the device shows up on your computer in a terminal run the following command:
Code:
fastboot flashing unlock
AVB/DM-Verity Unlock (Part 2 of 2)
Unlocking the bootloader really does not give a lot to us because all the partitions are still being verified and the device will not boot if they don't match. Word of warning doing this causes the stock OS not to boot fully.
If you are coming from part 1 you can start right away, if not you need to reboot to fastboot again.
1. Extract the downloaded AVB unlock zip
2. Run either the avb-unlock.bat or this command in a terminal
Code:
at_auth_unlock.exe creds\
3. Wait till it finishes
4. Keep in mind the stock system does not boot properly with AVB off (It is weird some UI elements work but the boot animation never goes away)
5. To relock AVB in the future run the following command or the Avb_lock.bat:
Code:
fastboot oem at-lock-vboot!
Now that you are AVB unlocked you can flash the firmware/partitions from fastboot using the flash-all scripts located in the firmware zips.
Blueberry 10" Firmware:
Spoiler
Stock Debug firmware (Allows you to OTA to latest firmware if on the user slot and avb locked, but adb is unauthorized so you can't edit files on this one. ADB is intact on the other slot if you change over to it)
Android 8.1 Debug Firmware (Do not AVB lock on this firmware it uses different keys but you can fastboot/edl flash other firmware to recover if you do):
Android 7.0 Debug firmware (Select the Legacy unlock option if avb unlocking)
Amber 8" Firmware:
Spoiler
UNTESTED FLASH AT YOUR OWN RISK (But should be fine report back if it works)
Stock Debug Firmware
Unified 8" and 10" Debug/Development firmware (Only tested on Blueberry/10" but these should work on Amber/8" as well)
Spoiler
Android 8.1 Debug Firmware (Do not AVB lock on this firmware it uses different keys but you can fastboot/edl flash other firmware to recover if you do):
Android 7.0 Debug firmware (Select the Legacy unlock option if avb unlocking):
AVB Unlock tool:
Here
Amber and Blueberry EDL Firehose:
Here
The firmware provided allows you to have adb and adb root on either debug or user. But the downside is with avb off the device can't access its Tee keys so the user firmware will not finish setup. But you can still install other apps and use root which allows you to fully turn off the security restrictions to allow you to edit files on the device. The commands you need to run are these:
Spoiler
Code:
adb root
adb disable-verity
adb reboot
adb root
adb remount
adb shell setenforce 0
Disable-verity will last until you factory reset or run adb enable-verity
Useful adb and android things commands:
Spoiler
Brings up the default launcher selector screen (If a launcher you try opens and then closes it is not supported by Android Things. You will need one that does not have Widget support. Like KISS Launcher)
Code:
adb shell am start -a android.intent.action.MAIN -c android.intent.category.HOME
Lists installed app package names
Code:
adb shell pm list packages
Change the -p to whichever package name you want to launch it emulates clicking the apps icon in launcher so some system apps don't support it.
Code:
adb shell monkey -p PACKAGE_NAME -c android.intent.category.LAUNCHER 1
Will launch the android things settings page
Code:
adb shell monkey -p com.android.iotlauncher -c android.intent.category.HOME 1
This will launch the google setupwizard/launcher
Code:
adb shell monkey -p com.google.assistant.core -c android.intent.category.LAUNCHER 1
Seems to soft reboot the android things system, but not actually reboot the device proper
Code:
adb shell monkey -p com.google.android.apps.quartz -c android.intent.category.LAUNCHER 1
Launches camera app
Code:
adb shell am start -n com.android.camera2/com.android.camera.CameraActivity
Various Screenshots:
Spoiler
{
"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"
}
Is there another forum, or talk about what exactly we can do with this fw?? Thanks. Also my comp not seeing the device in fastboot. Yes I have adb and fastboot tools.
Also not seeing the device in fastboot while holding Vol + and plugging in the power. Tried Vol -, and got the new USB device notification, but holding Vol - doesn't seem to get to fastboot, and it'll just boot to the normal OS.
agentdr8 said:
Also not seeing the device in fastboot while holding Vol + and plugging in the power. Tried Vol -, and got the new USB device notification, but holding Vol - doesn't seem to get to fastboot, and it'll just boot to the normal OS.
Click to expand...
Click to collapse
I can see other phones in fastboot, just not this smart display. WTF? I think this is a BS thread.
bs3pro said:
Is there another forum, or talk about what exactly we can do with this fw?? Thanks. Also my comp not seeing the device in fastboot. Yes I have adb and fastboot tools.
Click to expand...
Click to collapse
agentdr8 said:
Also not seeing the device in fastboot while holding Vol + and plugging in the power. Tried Vol -, and got the new USB device notification, but holding Vol - doesn't seem to get to fastboot, and it'll just boot to the normal OS.
Click to expand...
Click to collapse
bs3pro said:
I can see other phones in fastboot, just not this smart display. WTF? I think this is a BS thread.
Click to expand...
Click to collapse
Very sorry about the delay, it seems I made a minor typo in the instructions. I said to do Vol+ for fastboot when it is really Vol-. If you do not get a fastboot device after doing that open up device manager and install the google usb driver on the missing driver device. This method very much does work, I had someone test it on the 8" as well as a few people on their 10" and 7" devices before I released it on XDA.
deadman96385 said:
Very sorry about the delay, it seems I made a minor typo in the instructions. I said to do Vol+ for fastboot when it is really Vol-. If you do not get a fastboot device after doing that open up device manager and install the google usb driver on the missing driver device. This method very much does work, I had someone test it on the 8" as well as a few people on their 10" and 7" devices before I released it on XDA.
Click to expand...
Click to collapse
Will give it another go. Thanks for the reply.
deadman96385 said:
Very sorry about the delay, it seems I made a minor typo in the instructions. I said to do Vol+ for fastboot when it is really Vol-. If you do not get a fastboot device after doing that open up device manager and install the google usb driver on the missing driver device. This method very much does work, I had someone test it on the 8" as well as a few people on their 10" and 7" devices before I released it on XDA.
Click to expand...
Click to collapse
ok, im in fastboot!
AND....I get this. ugh
C:\Users\Owner>fastboot flashing unlock FAILED (remote: 'oem unlock is not allowed') fastboot: error: Command failed
bs3pro said:
ok, im in fastboot!
AND....I get this. ugh
C:\Users\Owner>fastboot flashing unlock FAILED (remote: 'oem unlock is not allowed') fastboot: error: Command failed
Click to expand...
Click to collapse
Try and just doing the avb part, it seems on some newer firmware's its tied into avb unlock/lock so when that is unlocked it unlocks the BL.
deadman96385 said:
If you do not get a fastboot device after doing that open up device manager and install the google usb driver on the missing driver device.
Click to expand...
Click to collapse
Holding Vol- makes a QUSB_BULK (VID 05C6, PID 9008) device show up in Device Manager, which I think is EDL mode and not bootloader? I tried changing it to the Android Bootloader Interface driver but fastboot never seems to find it.
Holding Vol+ makes it boot to what seems to be a missing recovery mode, with the "dead" Android and the red exclamation point icon, but that doesn't lead to any USB devices being seen.
Any thoughts?
agentdr8 said:
Holding Vol- makes a QUSB_BULK (VID 05C6, PID 9008) device show up in Device Manager, which I think is EDL mode and not bootloader? I tried changing it to the Android Bootloader Interface driver but fastboot never seems to find it.
Holding Vol+ makes it boot to what seems to be a missing recovery mode, with the "dead" Android and the red exclamation point icon, but that doesn't lead to any USB devices being seen.
Any thoughts?
Click to expand...
Click to collapse
You don't have bootloader drivers installed
i unlocked, and flashed the universal fw to my 8inch. Now i just have black screen. It always just reboots to fastboot.
EDIT!! The flashall.bat file is corrupt!!!!!!! Need to edit out the format userdata line, otherwise the flash fails!!!
When try to flash the firmware fail with error mke2fs: invalid option -- 'b'
Error: Unknown option ?
If I coment the lines:
#if [[ "${WIPE_USER_DATA}" = true ]]; then
# ARGS+=( format userdata )
#fi
Don't fail, apparently it works fine, I can set it up, connect to google home app.
After this, the update screen appears, when it reaches 100% it restarts and starts the update screen again. And this in an infinite loop.
Any idea how I can fix it? Or just install any linux ?
Can I perform this on Linux PC? I guess not since it requires running .exe file.
I have SD8501F I was able to get it into fastboot mode on both linux and windows pc, but that's about it.
On linux it was recognized right away, on windows I had to manually install google android bootloader driver once it popped in device manager.
It failed to unlock.
fastboot devices return this:
HUA0777K fastboot
--------------------------------------
fastboot flashing unlock:
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.012s
----------------------------------------------------
at_auth_unlock.exe creds\
...
FAILED (status read failed (Too many links))
finished. total time: 0.000s
Command 'fastboot oem at-get-vboot-unlock-challenge' returned non-zero exit status 1
No matter what I try, I can't get to the fastboot from neither linux nor windows. I have fastboot drivers installed on windows, I also used fastboot on linux recently with other device. I can get to that broken bootloader while holding vol up without an issue. But holding vol down does not do anything, it just boots to system as usual
CatBug said:
No matter what I try, I can't get to the fastboot from neither linux nor windows. I have fastboot drivers installed on windows, I also used fastboot on linux recently with other device. I can get to that broken bootloader while holding vol up without an issue. But holding vol down does not do anything, it just boots to system as usual
Click to expand...
Click to collapse
I figured at least on my device 10-15sec holding vol down is too much it goes into recovery and leaves it and continue normal boot.
Screen is complete black in fastboot mode, so it's hard to tell when it in.
It's easier on windows as you can see sound when usb is recognized. Then you release vol down.
Basically connecting usb cable hold vol down and plug power, in 2-5sec you will hear usb recognized on windows. Release vol down. And now on windows i had to go to device manager and install driver. On linux it just worked.
Trick is to not hold vol down for too long
bg.stefan90 said:
I figured at least on my device 10-15sec holding vol down is too much it goes into recovery and leaves it and continue normal boot.
Screen is complete black in fastboot mode, so it's hard to tell when it in.
It's easier on windows as you can see sound when usb is recognized. Then you release vol down.
Basically connecting usb cable hold vol down and plug power, in 2-5sec you will hear usb recognized on windows. Release vol down. And now on windows i had to go to device manager and install driver. On linux it just worked.
Trick is to not hold vol down for too long
Click to expand...
Click to collapse
That was a perfect advice, mate, thx a lot!
As for other people, fastboot flashing unlock failed but I managed to run at_auth_unlock.exe creds\ successfuly. Then I commented that format user data line and ran the flash all script.
Now the device boots to fastboot everytime. What should I do now?
Hello, I've flashed firmware with "success" but my device (SmartDisplay 10'') is not reconized by the command adb devices... I'm stuck there after many tries !
I use fastboot and ADB with linuxMint.
Any ideas ?
Axh3ll said:
Hello, I've flashed firmware with "success" but my device (SmartDisplay 10'') is not reconized by the command adb devices... I'm stuck there after many tries !
I use fastboot and ADB with linuxMint.
Any ideas ?
Click to expand...
Click to collapse
Does it get recognized by "fastboot devices"? If so then your device is booting to bootloader after flashing the firmware. Just like mine.
CatBug said:
Does it get recognized by "fastboot devices"? If so then your device is booting to bootloader after flashing the firmware. Just like mine.
Click to expand...
Click to collapse
Yes it is reconized in fastboot devices, I never success to have it in ADB...

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!

Broken screen, Authorize ADB device for recovery

Hello,
I've got a Mi 9 that apparently works, but the screen is pretty much fully busted.
All black, it seems only parts of the touchscreen work, so it's not very reliable.
Thankfully it has ADB Debugging enabled, but without a screen I cannot authorize it when the authorization prompt comes up on the phone.
So when using ADB I get a Device Unauthorized error.
Apparently I can push a ADB Key to the phone using the command line, but I would have to put the phone in recovery mode.
The mode I've been able to access is Sideload mode (As detected by adb devices command) but I don't think I can push the ADB key using this mode.
This sideload mode came up after navigating using the hardware keys (Power + Volume up, then Volume Down twice, then Power)
This is apparently the "Connect to MiAssistant" Menu on the Recovery menu, but I'm not sure.
This phone has stock MIUI 12 or 13, I believe.
How can I enter Recovery mode/push the RSA key to the phone so that I can proceed with other recovery options, like scrcpy?
Eriolp said:
Hello,
I've got a Mi 9 that apparently works, but the screen is pretty much fully busted.
All black, it seems only parts of the touchscreen work, so it's not very reliable.
Thankfully it has ADB Debugging enabled, but without a screen I cannot authorize it when the authorization prompt comes up on the phone.
So when using ADB I get a Device Unauthorized error.
Apparently I can push a ADB Key to the phone using the command line, but I would have to put the phone in recovery mode.
The mode I've been able to access is Sideload mode (As detected by adb devices command) but I don't think I can push the ADB key using this mode.
This sideload mode came up after navigating using the hardware keys (Power + Volume up, then Volume Down twice, then Power)
This is apparently the "Connect to MiAssistant" Menu on the Recovery menu, but I'm not sure.
This phone has stock MIUI 12 or 13, I believe.
How can I enter Recovery mode/push the RSA key to the phone so that I can proceed with other recovery options, like scrcpy?
Click to expand...
Click to collapse
try power and volume down on powerup

Categories

Resources