Database Info

[Q] Bootloader locked after OTA XNPH05Q

Hi all,
I just installed the OTA update for XNPH05Q. My bootloader was previously unlocked, TWRP installed and rooted.
Now that the OTA is installed I wanted to re-root (SuperSU Pro Survival didn't work), but when I boot into recovery mode I only get the default 'Cyanogen Recovery' and trying to flash the SuperSU binary fails with 'Signature File unavailable' error.
Any idea what went wrong? My phone was heavily customized and I would really try to avoid the hassle of going through the full process to unlock the bootloader again... It will take several hours to restore everything, and since I'm using some sideloaded apps I don't even know if I will find them again - and now I can't even use Titanium anymore to backup them, the OTA happened already
Thanks for your input!

Your bootloader is still unlocked, it only restored stock recovery. So you only need to flash twrp, you won't lose any data doing that. And to stop the stock recovery getting flashed when installing OTA, go to Settings > Developer options. Then disable the 'Update recovery with system updates' option.

Thanks, that made my day! I'm currently travelling and have no access to a computer, but I'll flash TWRP again as soon as I'm back home and proceed from there.

Viking84 said:
Thanks, that made my day! I'm currently travelling and have no access to a computer, but I'll flash TWRP again as soon as I'm back home and proceed from there.
Click to expand...
Click to collapse
You can use Flashify to flash TWRP directly from your phone.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Transmitted via Bacon

timmaaa said:
You can use Flashify to flash TWRP directly from your phone.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Transmitted via Bacon
Click to expand...
Click to collapse
That requires root though which he doesn't have.

Gryphie said:
That requires root though which he doesn't have.
Click to expand...
Click to collapse
Yeah, I didn't really think that one through.
Transmitted via Bacon

If you have fastboot set-up you can run the command for oem unlock again and it shouldn't wipe anything. Happened with me After going to XNPH05Q my bootlocked got relocked as well and I was trying to flash cm12 and I couldnt figure out for the life of me why it would keep booting to fastboot and recovery wasnt working. So when all else failed and I said eff it I dont care if it wipes, I re-ran the command (after checking bootloader status and seeing that it got locked) and I was able to boot up just fine without any data loss.
That's just my personal experience though.
I did that because even after flashing different version of TWRP recovery and different ROMs my phone kept booting straight to fastboot.

I just arrived back home (literally stepped out of the airport 45 minutes ago) and as of this moment, my OPO is up & rooted again, with all data intact. Thanks for your great support!!!

Viking84 said:
I just arrived back home (literally stepped out of the airport 45 minutes ago) and as of this moment, my OPO is up & rooted again, with all data intact. Thanks for your great support!!!
Click to expand...
Click to collapse
Can you please tell how did you flashed TWRP again, as I have the same issue as you had.

Sure. I first had to tell my PC to use the correct drivers again - basically after installing the OTA, Windows recognized the phone anew and used the default drivers. So go to your device manager (Windows-Key + 'Break' -> device manager), search for your phone (I don't remember in which category it showed up, but just browse all until you find 'A00001'. Right klick, select 'change driver'. Go to 'have disk' and select 'ADB' from the list on the left, then on the right you should find the driver that is already installed [given that you had an ADB driver already, otherwise check this site for the driver download: http://twrp.me/devices/oneplusone.html].
To check if it worked, open a command line [Windows-Key + R, write cmd in the field and hit enter]. Now type "adb devices" [enter] and if [device ID] (some random numbers) is listed in the menu, all is fine.
Download the most recent TWRP image file from http://dl.twrp.me/bacon/ and save it somewhere.
Now, in the same command line enter "adb reboot bootloader", this will put your phone in fastboot mode.
Once this is done, check if the driver is still recognizing your phone by entering "fastboot devices", and check if the device is still listed.
If this checks out, enter "fastboot flash recovery [FULL PATH TO RECOVERY FILE]" -> e.g. "fastboot flash recovery c:\Users\viking84\Desktop\twrp-2.8.6.0-bacon.img"
This will take a couple minutes (3-4 for me).
Once it's done, enter "fastboot reboot" in the console, and your phone will reboot into recovery (if it doesn't, just switch it back of and restart it with power + volume up to enter the recovery menu). From there you can just install the SuperSU binary as you're used to.

Thx for the detailed step guide... Will perform these steps today.
Sent from my Oneplus One

Viking84 said:
Sure. I first had to tell my PC to use the correct drivers again - basically after installing the OTA, Windows recognized the phone anew and used the default drivers. So go to your device manager (Windows-Key + 'Break' -> device manager), search for your phone (I don't remember in which category it showed up, but just browse all until you find 'A00001'. Right klick, select 'change driver'. Go to 'have disk' and select 'ADB' from the list on the left, then on the right you should find the driver that is already installed [given that you had an ADB driver already, otherwise check this site for the driver download: http://twrp.me/devices/oneplusone.html].
To check if it worked, open a command line [Windows-Key + R, write cmd in the field and hit enter]. Now type "adb devices" [enter] and if [device ID] (some random numbers) is listed in the menu, all is fine.
Download the most recent TWRP image file from http://dl.twrp.me/bacon/ and save it somewhere.
Now, in the same command line enter "adb reboot bootloader", this will put your phone in fastboot mode.
Once this is done, check if the driver is still recognizing your phone by entering "fastboot devices", and check if the device is still listed.
If this checks out, enter "fastboot flash recovery [FULL PATH TO RECOVERY FILE]" -> e.g. "fastboot flash recovery c:\Users\viking84\Desktop\twrp-2.8.6.0-bacon.img"
This will take a couple minutes (3-4 for me).
Once it's done, enter "fastboot reboot" in the console, and your phone will reboot into recovery (if it doesn't, just switch it back of and restart it with power + volume up to enter the recovery menu). From there you can just install the SuperSU binary as you're used to.
Click to expand...
Click to collapse
I have successfully re-rooted by device using the above procedure. The only difference was even after flashing recovery and installing SuperSU through TWRP I was not able to see SuperSU app in phone, but then I went to Playstore and downloaded it from there and it worked!
So thank you for your help and detailed procedure!

[HOW-TO] Root BNTV450 Nook 7 (ST16C7BNN) using Magisk.

Root your "Barns & Noble Nook 7" BNTV450 using Magisk's Patch Boot Image File option.
BE CAREFUL!
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start flashing partitions. (In this case boot.)
Disclaimer
I am not responsible for your non-working "bricked" devices.
I have a few of my own.
Requirements
Barns & Noble Nook 7" BNTV450
A computer with working adb and fastboot
USB cable
WiFi connection
Magisk Manager (Link below)
Stock boot image (Link below)
Tested on:
BNTV450-v1.0.2-20161230 Security patch October 5, 2016
BNTV450-v2.0.4-20170927 Security patch August 5, 2017
BNTV450-v2.0.5-20170110 Security patch November 5, 2017 ota update
macOS 10.13.x
Windows 7 Pro
Steps
Unlock bootloader
Boot Magisk patched boot image
Pull stock boot and recovery images from device
Use Magisk to patch pulled stock image
Test and flash new patched boot image
Notes:
Google updates were needed to get everything working correctly.
PlayServices and WebView
Mac users. As with some other devices, I had to unplug and plugin the USB cable between some of the fastboot commands.
fastboot flash boot patched_boot.img and fastboot boot bntv4-recovery.img
Magisk:
There have been a lot of changes in Magisk since I originally used it to root.
Way too many to mention so, just the basics that apply to this device.
Newer versions of Magisk use the Download directory instead of creating and using the MagiskManager directory.
Some apps search for this directory and used it to determine if the device is rooted.
If you previously used Magisk to root and have a MagiskManager directory, you will want to delete it.
To update Magisk Manager.
Use the update option, it will download and install the newest version.
To update Magisk.
The safest way is to patch the boot image again. Test and flash.
The Direct Install option works but, may lead to a non-desirable outcome.
To uninstall Magisk.
Test boot your original boot image to make sure it works.
Check with Magisk Manager, it should say Magisk not installed.
If so, then flash your stock boot image back using fastboot.
If your stock boot image will not boot, then you are stuck with Magisk patched boot images.
Hardware Keys:
Power and Volume Up = Recovery Mode
Power and Volume Down = Factory Mode
It will show on the bottom Left (Sideways on the top left) Detecting boot mode. With bootloader unlocked it flashes this message very fast so you might not see it.
I still can not produce the same results continuously across mine. The newer ones, that came with v2.0.5 seem to work but, the older ones still it's a 50 % chance if I can get it to work. The bricked ones, do not seem to register the key combo on boot.
Files Needed
Magisk
xda Magisk forum. Link
Magisk and MagiskManager Official github downloads. Link
Boot Images
Magisk patched boot image downloads. Link
Stock recovery and boot image downloads. Link
Credits and Thank You:
@topjohnwu - The creator and brilliant mind behind Magisk.
Everyone who has helped me learn through the years.
Last edited 23.Sep.2018

"QUICK" Guide - BNTV450 Nook 7
Unlock Bootloader
THIS WILL VOID YOUR WARRANTY.
Unlocking the bootloader WILL wipe and Factory Reset your device. Make sure to copy, backup and logout of everything before you begin.
Note: adb and fastboot need to be installed and working.
On device
Go to Settings - About and tap on the build number seven times to enable Developer options.
Go to Settings - Developer options and Enable OEM unlocking and USB debugging
Connect to computer and Allow USB debugging?
On computer
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot flashing unlock
On device
Follow the prompts on the device.
Unlock bootloader?
If you unlock the bootloader,you will be able to install custom operating system software on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data,unlocking the bootloader will also delete all personal data from your phone(a "factory data reset").
Press the Volume UP/Down buttons to select Yes or No.
Yes (Volume UP):Unlocking(may void warranty).
No (Volume Down): Do not unlock bootloader.
After it returns to fastboot mode, use the power button to turn off, unplug it from computer and then turn on.
It will reboot a few times, including an Erasing... screen.
Once device reboots, run through the initial setup.
Note: Sometimes mine would get stuck on the nook .... animation screen. Give it a few minutes (I wait at least 5 minuets) then power off and power back on.
Note: You will now have the annoying boot delay and "Orange State" message.
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds

"QUICK" Guide - BNTV450 Nook 7
Root using Magisk.
MagiskManager 6.0.0 Download
Magisk 17.2 patched v2.0.5 Download
Using Magisk Manager and the provided Magisk patched boot image.
Note: When booting an image from "fastboot", you should not see the initial "orange boot" screen.
Make sure to grant permission if and when prompted on device.
Some of the adb and fastboot commands may require input on the device.
On device
Go to Settings - About and tap on the build number seven times to enable Developer options.
Go to Settings - Developer options and Enable USB debugging
Connect to computer and Allow USB debugging?
On computer
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot m172_v205_boot.img
Wait for device to boot then.
Reminder. Make sure to grant permission if and when prompted on device.
Code:
adb install -r MagiskManager-v6.0.0.apk
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/bntv4-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/bntv4-recovery.img"
adb pull /sdcard/bntv4-boot.img
adb pull /sdcard/bntv4-recovery.img
Test the images you just made.
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot bntv4-recovery.img
Wait for device to boot into recovery mode then.
On device
In Stock Recovery use the volume down key to highlight Reboot to bootloader and press the power button.
Wait for device to boot into fastboot mode then.
On computer
Code:
fastboot boot bntv4-boot.img
Wait for device to boot then.
On device:
If you haven't setup WiFi, do so now.
Open MagiskManager
Tap on Install
Select Install
Select Patch Boot Image File
Tap on Internal storage
- Note: If Internal storage is not displayed. Tap on the 3-dot menu (upper right corner) and select Show SD card.
Scroll down and tap on bntv4-boot.img
When Magisk is done patching the image file, select CLOSE
You can close MagiskManager as well.
Copy and test your Magisk patched boot image.
On computer
Code:
adb pull /sdcard/download/patched_boot.img
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot patched_boot.img
On device
Open MagiskManager
Note: You should see that Magisk is installed and active.
To do a quick check.
On Computer
Code:
adb shell
[email protected]:/ $su
[email protected]:/ #exit
[email protected]:/ $exit
If it worked, and you are ready to say goodbye to stock Non-root.
Code:
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot boot bntv4-recovery.img
Once it's booted into Recovery, unplug the device.
On device
In Stock Recovery use the volume down key to highlight Wipe cache partition and press the power button.
-- Wiping /cache...
Formatting /cache...
Cache wipe complete.
Then with Reboot system now highlighted press the power button.
You are now rooted and running Magisk.
Last edited 23.Sep.2018
Links to my shell logs.
Unlock bootloader. Pastbin
Root. Pastbin

volume button does not react
Hi
unlocking does not work
As mentioned in the other discussion, the volume up button does not seem to react and so the unlocking does not work. Also one user suggested using the reset button after pressing the volume up button for the unlock; that also does not work for me
Do u have any other suggestions to unlock ?;

arrmusic said:
Hi
unlocking does not work
As mentioned in the other discussion, the volume up button does not seem to react and so the unlocking does not work. Also one user suggested using the reset button after pressing the volume up button for the unlock; that also does not work for me
Do u have any other suggestions to unlock ?;
Click to expand...
Click to collapse
I never ran into this problem. So short answer - No.
Can you point me to that other discussion?
What do you get if you run fastboot oem lks
fastboot oem unlock is supported on this device. You could give that command a try and see if there is a difference.
Not sure what you have tried.
I would start with "Factory Reset" in stock recovery. Skip through the initial setup and try again.
Note: Developer option menu has a toggle at the top, make sure it is turned On.
Sent from my BNTV450 using XDA Labs

Volume up button not recognised while fastboot unlock
Hi
Here is the discussion thread that I was referring to where people are stuck with unresponsive volume up button for fastboot unlock
https://forum.xda-developers.com/nook-7/help/nook-rootable-t3510289
I didn't do the factory reset. So maybe I will do that and see if it works.

unlock not working
Hi
Just to further update you on your reply; i did a factory reset and tried to unlock the bootloader but i get to the same problem; the volume button does not respond; so stuck with the message 'press the volume up button to unlock the bootloader'
I did the fastboot oem lks and that commands executes well and it gives me a OK output.
Cheers & New year greetings!

Any update on the unlock issue
Hi
Is there any update on the unlock issue i reported some time back? My last update on this was executing the command => 'I did the fastboot oem lks and that commands executes well and it gives me OK output.'
not sure if my last update was interpreted in the right way; it does nothing when i type fastboot oem lks except saying it is OK (which i suppose is the expected output of fastboot oem lks). So i do not know how to get around the volume keys not being recognised to go further in unlocking
I still can not use the volume keys for the unlock as it does not seem to react. just stuck a bit on this

@arrmusic I guessed it it looked more like this.
Code:
fastboot oem lks
...
(bootloader) lks = 1
OKAY [ 0.000s]
finished. total time: 0.000s
lks = 0 would be unlocked.
I am looking for a way to un-brick these. I think that may be the best way to correct the button problem also.
What os version are you running? (BNTV450-vx.x.x-20xxxxx)
What do you get when you run fastboot flashing get_unlock_ability ?
Tested a few things tonight.
I was NOT able to re-lock the bootloader on either of my rooted devices.(BNTV450-v2.0.4)
Found some more inconsistencies with power and volume key boot combinations. (Among other things.)
"FAILED (remote: not support on security)" apparently is not just for unlocked devices.
Sent from my BNTV450 using XDA Labs

not able to unlock yet
Hi
Many thanks for your reply.
I seem to have the software version v1.0.2;
I tried to find by googling v2.0.4 but i am not able to find that security update anywhere to download; do you have the v2.0.4 file? can i have it somehow?
I ran the commands u had mentioned in your previous reply.
fastboot flashing get_unlock_ability
...
(bootloader) unlock_ability = 16777216
OKAY [ 0.012s]
finished. total time: 0.012s
fastboot oem lks
...
(bootloader) lks = 1
OKAY [ 0.004s]
finished. total time: 0.008s

What is the origin of the boot.img?
What is the origin of the boot.img? I'd rather not just flash something without knowing where its come from.

74178951237895321 said:
What is the origin of the boot.img? I'd rather not just flash something without knowing where its come from.
Click to expand...
Click to collapse
v2.0.3 boot came from a supposed "N" rom for this device and was the first boot image I was able to make bootable. It was still API 23 "M" by the way.
I would have to find and unpack the original file to see what I edited to make it bootable.
All others are "dd" copies from my own device(s).
I am working on updating the OP and the "Quick Guide"
Boot Images
Download Magisk 15.3 patched v2.0.5 (Preferred and current boot image.)
Sent from my ford using XDA Labs

Scatter file for Mediatek MT8163, opening the tablet
Can you post the scatter file for the Mediatek MT8163?
I've been trying to make my own image dumps for the Nook 7, but have run into an issue where the device won't stay in a readable mode for SP Flash Tools long enough while the battery is still connected. So, the solution for most phones is to disconnect the battery and have it powered over USB only so that it won't go past the preloader and into the charging mode.
But I can't get the darned thing open! My phone has a similar style housing and I had to use a suction cup on the glass while prying at the edges to gain access. But for the Nook 7 its just not working.
Edit: This started while trying to soft load TWRP to make the image dumps. When I do
Code:
fastboot boot twrp.img
It tells me that the kernel address lies outside of memory. Its possible to supply an address to load it at with the fastboot command which you are supposed to learn from the scatter file. I found what I thought was a valid MT8163 scatter file but using the address found within did not fix the issue.
I forgot you mentioned that you didn't pull the original image from your device yourself. I've been trying to root this without relying on images from others. Your latest guide to pulling and modifying your own boot.img is a decent enough middle ground for me to use. Thanks.

@74178951237895321
Sent from my Nexus 7 (2013) using XDA Labs

I was able to get a successful root by following the steps in this thread in combination with those mentioned in this one. ipdev, just to satisfy my curiosity, where did you find this "N rom" image?

ipdev said:
So we hit a snag using Magisk 15.4+ to patch a stock boot image on this device.
Click to expand...
Click to collapse
So, I was dumb and went through with updating Magisk without checking this thread first, and now my tablet's stuck in a bootloop that I can't seem to get out of. @ipdev, do you have any ideas on how this happened/how to get out of it? The tablet can't get past the "Orange state your device has been unlocked etc. etc." screen, and I can't get it to boot into recovery either (using Power+Volume Down, is the combination something else on this tablet?). fastboot won't discover it either, probably because it reboots within seconds and never gets to a point where it could be recognized. I'm thinking of letting it bleed out until its battery dies (unfortunately, the battery is soldered and glued in, so I can't just disconnect it), and checking on it in the morning to see if it will be cooperative enough to let me flash the modified Magisk image.

@saagarjha
I have a few in the same condition. As you noticed, the battery is soldered in so the best you can do is disconnect the screen. (Connector to the right of battery.)
One of these days, I was going to try sp flashtools to see if I could recover one of mine. (I'm not sure if it works with these.)
Sent from my Nexus 5 using XDA Labs

I let the tablet run out of battery and then plugged it back in again and it immediately got stuck in the same bootloop, so it looks like it's actually bricked rather than just pretending. I think SP Flash Tools is the way to go at this point; we'd have to find a functioning preloader driver and scatter file to do that, however. It might be possible to simulate disconnecting the battery by shorting the battery's leads, but I'm not sure if this would work (or is even safe to do).

I was having trouble with unlocking the boot loader on my v1 launch version of this Nook. Recently I dropped it and got a new one via the replacement plan - this one was marked 'v2', came with a 2.x firmware that I wasn't able to even get on my launch Nook 7.
Anyway, this one unlocked without any problems. Thought this might be helpful to anybody having trouble unlocking the bootloader. Consider the revision of the Nook you have. Maybe the solution here is flashing the v2 firmwares to the v1? Hard to say.

unable to unlock
So I did "adb reboot bootloader" and the tablet rebooted and says "=> FASTBOOT mode..." on the screen.
I then did "fastboot flashing unlock" on the computer. Nothing happened on the device and my computer says "< waiting for device >". Could anyone please let me know what I did wrong? Thank you very much.

[UNOFFICIAL][DECRYPTION WORKS] TWRP 3.3.1 for UMIDIGI F1 [20191103]

Introduction
This is an UNOFFICIAL TWRP port for UMIDIGI F1 that works properly with encrypted /data partition in official ROM. I am aware that the UMIDIGI F1 already has TWRP built for it, but none of them seem to have decryption working properly. In fact, every single TWRP, even official ones, for any MT6771 device, seem to have non-functional decryption support. Through some digging I managed to fix decryption at least for UMIDIGI F1, so here is my version of TWRP for the device.
Known Bugs
- Screen may flash on the password-input UI. Anything else is fine though.
This TWRP has been tested with official ROM and my LineageOS 17 port (https://forum.xda-developers.com/android/development/unofficial-lineageos-17-0-umidigi-f1-t3997827) and it works fine.
This is UNTESTED on the F1 Play. ONLY TESTED on regular F1.
Why Bother
Because security matters. Using a cheap device should not mean giving up security, and more importantly, privacy.
Instructions
1. Unlock bootloader
2. Enable ADB debugging in system
3. Execute "adb reboot bootloader" while having your phone connected to PC
4. Execute "fastboot flash recovery <your_downloaded_recovery>.img"
5. Reboot phone while holding Volume Up + Power buttons
Note: The official ROM may overwrite the recovery, so you may need to re-flash the recovery if this behavior isn't prevented either by TWRP or manually.
Downlaods & Sources
20191103: https://github.com/PeterCxy/android_device_umidigi_F1/releases/tag/20191103-twrp
- Fixed issues with Magisk and OpenGAPPS
20191102: https://github.com/PeterCxy/android_device_umidigi_F1/releases/tag/20191102-twrp
Device Tree: https://github.com/PeterCxy/android_device_umidigi_F1/tree/twrp-9.0
Modified TWRP (Required for decryption to work): https://github.com/PeterCxy/android_bootable_recovery

Updated to 20191103

I appreciate your sharing this. I have added "system_image emmc" to the fstab file, so I can flash and backup the system.img
This works good on my F1,
But I tried to make this decrypt work for my other phone with 6771(Bold N1), but couldn't find all same files added to recovery/root from stock firmware.

mrmazak said:
I appreciate your sharing this. I have added "system_image emmc" to the fstab file, so I can flash and backup the system.img
This works good on my F1,
But I tried to make this decrypt work for my other phone with 6771(Bold N1), but couldn't find all same files added to recovery/root from stock firmware.
Click to expand...
Click to collapse
Those files are extracted from vendor.img, but it can be different on different devices, e.g. keymaster version might be different. Also you will need to patch them using `patchelf` to make them use `/sbin/linker64` instead of `/system/bin/linker64`

hello
im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???
thanks

Shadow Of Leaf said:
hello
im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???
thanks
Click to expand...
Click to collapse
on other releases, no change was needed to boot on both. I would try as is first.
as long as you have working sp flash tool in case of issue.

mrmazak said:
on other releases, no change was needed to boot on both. I would try as is first.
as long as you have working sp flash tool in case of issue.
Click to expand...
Click to collapse
Cause i test it without changes , it reboot to system
I think because they have different kernels

I am unable to install twrp.
When I run the "fasthboot flash recovery" command, cmd aparace "waiting for de ice" and nothing happens on my phone ...
Am I doing something wrong?

no fastboot response
for some reason (most likely pilot error, lol) the phone doesn't show when I do "fastboot devices" - even though the F1's screen shows "fastboot mode" in very tiny letters on the bottom-left.
probably something stupid I'm doing wrong, will keep trying...

tarvoke said:
for some reason (most likely pilot error, lol) the phone doesn't show when I do "fastboot devices" - even though the F1's screen shows "fastboot mode" in very tiny letters on the bottom-left.
probably something stupid I'm doing wrong, will keep trying...
Click to expand...
Click to collapse
You can operate from adb/fastboot folder and device can stay on fastboot mode but if drivers were not properly installed then no connection with pc.
Try installing:
- https://androidmtk.com/download-15-seconds-adb-installer
- https://androidmtk.com/download-mtk-usb-all-drivers
- https://www.androidweblog.com/download-mediatek-usb-vcom-drivers/
Start the process from device on using adb commands to always allow access to the pc. I mean:
Code:
adb devices
and then if device is detected you will see a screen warning to "always allow...." then tap on yes; this suppress future conflicts, then
Code:
adb reboot bootloader
while on fastboot follow with
Code:
fastboot devices

SubwayChamp said:
You can operate from adb/fastboot folder and device can stay on fastboot mode but if drivers were not properly installed then no connection with pc.
Click to expand...
Click to collapse
thanks!
adb was already working (is how I made the thing reboot to bootloader, and yes I did tell it to permanently accept the computer I'm using.
this is on linux, so the drivers shouldn't be a problem... although SMH I never put USB IDs into the udev rules. which is interesting, because regular adb already worked fine without it - I have had phones in the past that some did, some did not, require the computer to know about vendor/hardware ID.
(and I know that the adb USB IDs are usually different than the ID for fastboot, as well.)
like I said, pilot error lol. but thank you again for the reply!

I have done the following:
Enabled Developer Options
Enabled USB Debugging
Enabled OEM Unlocking
Unlocked the bootloader with:
Code:
adb reboot bootloader
fastboot flashing unlock
Rebooted and Enabled USB Debugging again.
Then after downloading your recovery
Code:
adb reboot bootloader
fastboot boot ~/Downloads/recovery.img
But nothing happened.
I rebooted and thought I would try flashing
Code:
adb reboot bootloader
fastboot flash recovery ~/Downloads/recovery.img
It just paused on the boot screen saying "Your device has been unlocked and can't be trusted".
If I reboot then try to go direct to recovery:
Code:
adb reboot recovery
I end up with the broken android screen and "No command"
What am I missing?

opticyclic said:
I have done the following:
Enabled Developer Options
Enabled USB Debugging
Enabled OEM Unlocking
Unlocked the bootloader with:
Code:
adb reboot bootloader
fastboot flashing unlock
Rebooted and Enabled USB Debugging again.
Then after downloading your recovery
Code:
adb reboot bootloader
fastboot boot ~/Downloads/recovery.img
But nothing happened.
I rebooted and thought I would try flashing
Code:
adb reboot bootloader
fastboot flash recovery ~/Downloads/recovery.img
It just paused on the boot screen saying "Your device has been unlocked and can't be trusted".
If I reboot then try to go direct to recovery:
Code:
adb reboot recovery
I end up with the broken android screen and "No command"
What am I missing?
Click to expand...
Click to collapse
While in fastboot the first you should do is see if device is detected by pc with
Code:
fastboot devices
It looks like something is wrong with your path, I ever avoid path copying or moving the file/image to the adb/fastboot directory but anyway if you don´t want to do it you can copy the path from the bar where your recovery file is allocated, for example, if the file is in Downloads directory like it seems actually is, no matter what unit/drive you are in you can set an absolute value to avoid errors, look at this example: C:\Users\your_user\Downloads
If your device is detected then you can flash the recovery as you were trying to do it with
Code:
fastboot flash recovery recovery.img
and then you can reboot directly to it without need to reboot to system previously and this will prevent TWRP from being overwritten, with
Code:
fastboot boot recovery.img

hmm, so when I checked the udev rules, it already had one for MTK/mediatek - and the USB vendor is '08ed' in fastboot as well as in regular adb, so it wasn't a problem with udev/plugdev.
which I guess may mean the lunix generic android drivers for fastboot might be... "lacking" - I'll have to scrounge up a win7 laptop and try the recommended windows drivers.

SubwayChamp said:
...
It looks like something is wrong with your path, I ever avoid path copying or moving the file/image to the adb/fastboot directory but anyway if you don´t want to do it you can copy the path from the bar where your recovery file is allocated, for example, if the file is in Downloads directory like it seems actually is, no matter what unit/drive you are in you can set an absolute value to avoid errors, look at this example: C:\Users\your_user\Downloads
...
Click to expand...
Click to collapse
I don't think it was anything to do with the path as it output the file transfer size.
I think it was a combination of the following:
I wasn't pressing the right combinations of buttons after flashing.
i.e. holding VOL UP and pressing POWER on the screen saying "Your device has been unlocked and can't be trusted".
Rebooting might (?) have been reverting the recovery.
I was originally trying this on the firmware that was shipped 2019012414 but after flashing 2019090418 with SPFlashTool I had more success.
I also able to reboot to recovery directly after flashing with fastboot with the following:
Code:
fastboot oem reboot-recovery
Whichever was the key I can now reboot to recovery from adb too.
:good:

Your twrp eliminates fingerprint authentication.
I discovered something interesting, your twrp only works on my device, no other twrp works, but when I install it, I lose my fingerprint, it doesn't work at all.
Simply put, I must choose between the fingerprint or the root.

LyrielAlk said:
No other twrp works, but when I install it, I lose my fingerprint, it doesn't work at all.
Simply put, I must choose between the fingerprint or the root.
Click to expand...
Click to collapse
Try to clean flash last vendor build with spflash tool. First boot need stock recovery.
You don't need custom recovery to achieve root.
Maybe give a try to SNwriter (I never needed it though and can't help here).

Both of those twrp are not sticking. I have flashed with spoken flash tool v5 1944 win and I fastboot cmd with the same results.

Thanks
Gracias for this master ?

good
Shadow Of Leaf said:
hello
im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???
thanks
Click to expand...
Click to collapse
good idea

Help: OTA Update bricked my rooted phone

;Just going to spell out exactly what I've done and what's happening, partly to get my own story straight.
KB2005 running Android version 11.0.9.9.KB055A
Rooted with Magisk, TWRP not installed
This morning, got OP8T Security update for 11.0.10.10.KB05AA
I read the instructions on how to OTA update rooted phones, and followed them carefully:
Spoiler: Step-by-step description of my actions
Restored Stock Boot Image in Magisk
Pressed "Uninstall Magisk" button
Selected "Restore images"
Installed OTA Update, but did not reboot
Restored Root in Magisk Manager
Pressed "Install" button
Selected "Install" option
Selected "Install to Inactive Slot (After OTA)"
Selected "Let's Go" to confirm
Once complete, selected "Reboot" button
After rebooting, my wifi no longer worked.
Checked Settings > System
Still said 11.0.10.10 Update available
Checked Magisk
Don't recall exactly what I did next
I may have restored stock image in Magisk to retry the OTA update
Then the OTA Update rebooted my phone
What's happening now:​Phone boots to recovery:
Boot reason:
Boot reason: fs_mgr_mount_all
Unable to parse kernel log. For more debug information,
adb pull /mnt/vendor/op2/rbr_log
or pull op2.img
>adb devices
List of devices attached
e0260e42 unauthorized
>adb pull /mnt/vendor/op2/rbr_log
adb: error: failed to get feature set: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
When I reboot to fastboot, the screen says:
FastBoot Mode
PRODUCT_NAME - kona
VARIANT - SMB UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - e0260e42
SECURE BOOT - yes
DEVICE STATE - unlocked
>fastboot devices
returns no response
Halp!

cheshyre said:
;Just going to spell out exactly what I've done and what's happening, partly to get my own story straight.
KB2005 running Android version 11.0.9.9.KB055A
Rooted with Magisk, TWRP not installed
This morning, got OP8T Security update for 11.0.10.10.KB05AA
I read the instructions on how to OTA update rooted phones, and followed them carefully:
Spoiler: Step-by-step description of my actions
Restored Stock Boot Image in Magisk
Pressed "Uninstall Magisk" button
Selected "Restore images"
Installed OTA Update, but did not reboot
Restored Root in Magisk Manager
Pressed "Install" button
Selected "Install" option
Selected "Install to Inactive Slot (After OTA)"
Selected "Let's Go" to confirm
Once complete, selected "Reboot" button
After rebooting, my wifi no longer worked.
Checked Settings > System
Still said 11.0.10.10 Update available
Checked Magisk
Don't recall exactly what I did next
I may have restored stock image in Magisk to retry the OTA update
Then the OTA Update rebooted my phone
What's happening now:​Phone boots to recovery:
Boot reason:
Boot reason: fs_mgr_mount_all
Unable to parse kernel log. For more debug information,
adb pull /mnt/vendor/op2/rbr_log
or pull op2.img
>adb devices
List of devices attached
e0260e42 unauthorized
>adb pull /mnt/vendor/op2/rbr_log
adb: error: failed to get feature set: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
When I reboot to fastboot, the screen says:
FastBoot Mode
PRODUCT_NAME - kona
VARIANT - SMB UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - e0260e42
SECURE BOOT - yes
DEVICE STATE - unlocked
>fastboot devices
returns no response
Halp!
Click to expand...
Click to collapse
For future reference: https://forum.xda-developers.com/t/updates-thread.4188149/post-85517871
Comments:
- stock recovery doesn't support adb connectivity
- I also lost bootloader/fastboot connectivity after the 10.10 update, but it was a simple matter of updating the driver in Windows (Device Manager>Update driver for the device>Browse my computer>Let pick from list>Android bootloader interface).
- you may be able to get the phone to start if you restore the stock 10.10 boot image (attached, md5: 6fa5cc81a8e7e2878ac220e4216d4a52)
- otherwise you may need to use the MSM tool.

BillGoss said:
- I also lost bootloader/fastboot connectivity after the 10.10 update, but it was a simple matter of updating the driver in Windows (Device Manager>Update driver for the device>Browse my computer>Let pick from list>Android bootloader interface).
Click to expand...
Click to collapse
Because I'm now double- and triple-checking everything before I make a change...
Driver version is 11.0.0.0 - is that the latest? And, if not, where can I get the update?
[Also, the driver says manufacturer is "LeMobile" -- is that correct?]

Oh thank gd - fastboot devices is now listing my device...
(I also noticed an new release of platform-tools on developer.android.com which I installed)
I feel so much more hopeful

cheshyre said:
Because I'm now double- and triple-checking everything before I make a change...
Driver version is 11.0.0.0 - is that the latest? And, if not, where can I get the update?
[Also, the driver says manufacturer is "LeMobile" -- is that correct?]
Click to expand...
Click to collapse
I have the Google USB drivers installed. See https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/

Hokay, so, I've been proceeding very deliberately, trying to look at all the options before taking action...
After updating my PC's driver & adb, I was able to
Code:
fastboot boot twrp.img
Poking around at the various menu options, without (yet) making any changes (I think)
Thru TWRP's terminal, I grabbed md5sums for the various boot.imgs on my devivce, and compared them to the ones previously pulled or downloaded to my PC:
/dev/block/by-name/boot_a matched 11.0.9.9.KB055A patched by Magisk
/dev/block/by-name/boot_b matched the stock 10.10 boot image attached above
/dev/block/bootdevice/by-name/boot same as boot_a
Also, TWRP's Reboot menu said Current Slot = A
Following BillGoss's advice above (which hasn't led me astray yet), Reboot > Slot B seems like the logical next step. Right?
(What does "Fix Recovery Bootloop" under Advanced do?)

cheshyre said:
Hokay, so, I've been proceeding very deliberately, trying to look at all the options before taking action...
After updating my PC's driver & adb, I was able to
Code:
fastboot boot twrp.img
Poking around at the various menu options, without (yet) making any changes (I think)
Thru TWRP's terminal, I grabbed md5sums for the various boot.imgs on my devivce, and compared them to the ones previously pulled or downloaded to my PC:
/dev/block/by-name/boot_a matched 11.0.9.9.KB055A patched by Magisk
/dev/block/by-name/boot_b matched the stock 10.10 boot image attached above
/dev/block/bootdevice/by-name/boot same as boot_a
Also, TWRP's Reboot menu said Current Slot = A
Following BillGoss's advice above (which hasn't led me astray yet), Reboot > Slot B seems like the logical next step. Right?
(What does "Fix Recovery Bootloop" under Advanced do?)
Click to expand...
Click to collapse
(done) Can anyone share 11.0.8.12.KB05AA boot.img
Boot loop after incremental OTA (magisk restore image and repatch). So... can someone Success upgraded share the boot.img ? Thanks.
forum.xda-developers.com
I have exact same experience when update to 11.0.8.12.
Incremental OTA will not install if your system are modified, but your boot_a is patched, i guess you magisk patch inactive slot before OTA reboot, some how it patched current slot, maybe flash stock 11.0.9.9 boot.img to slot_a can solve it.

cheshyre said:
Hokay, so, I've been proceeding very deliberately, trying to look at all the options before taking action...
After updating my PC's driver & adb, I was able to
Code:
fastboot boot twrp.img
Poking around at the various menu options, without (yet) making any changes (I think)
Thru TWRP's terminal, I grabbed md5sums for the various boot.imgs on my devivce, and compared them to the ones previously pulled or downloaded to my PC:
/dev/block/by-name/boot_a matched 11.0.9.9.KB055A patched by Magisk
/dev/block/by-name/boot_b matched the stock 10.10 boot image attached above
/dev/block/bootdevice/by-name/boot same as boot_a
Also, TWRP's Reboot menu said Current Slot = A
Following BillGoss's advice above (which hasn't led me astray yet), Reboot > Slot B seems like the logical next step. Right?
(What does "Fix Recovery Bootloop" under Advanced do?)
Click to expand...
Click to collapse
I have no idea what "Fix Recovery Bootloop" does. I've never had a recovery bootloop and that option wasn't present on my old phone.
Anyway, two things you can try:
- boot slot b and see if the system comes up cleanly now that it has stock 10.10 boot image.
- if that fails see if booting slot a comes up on 9.9 again.
If neither work it's back to MSM to reset things.

@cheshyre, you keep writing "11.0.9.9.KB055A" which I've assumed to be
"11.0.9.9.KB05AA". Can you please confirm what version you are actually running?

You're correct, my original notes did say 11.0.9.9.KB05AA;
I must've transcribed it incorrectly somewhere along the line and then kept recopying the truncated number.
I think I'm going to try booting to Slot B, which appears to have stock 11.0.10.10.KB05AA, unless somebody tells me not to very soon...

I dealt with this issue on my 3T by simply never updating it; still running build A3000_28_170104;
If AT&T hadn't forced me to update my device so they can retire 3G, I'd prolly still be using it

Changed the situation, at least...
As I said I was going to do above, I fastbooted into TWRP and selected Reboot Slot B
Now I'm stuck on a screen which says
QUALCOMM CrashDump Mode
--------------------------
de-verity device corrupted Force Dump
kernel_restart
Even long-pressing the power button won't turn it off.
(Optimistically) Next steps?

(Finally managed to power off my phone by holding both power and volume-up)

cheshyre said:
(Finally managed to power off my phone by holding both power and volume-up)
Click to expand...
Click to collapse
Yep, power+vol up gets you out of CrashDump.
You could try booting slot a.

So far, every reboot takes me back to QUALCOMM CrashDump, even with vol buttons pressed.
adb devices & fastboot devices show nothing.
I have a PC utility called USBLogView which shows all Plug & Unplug events.
My "Device Description" is no longer "OnePlus 8T" or "ADB Device" -- it's listed as "QUSB_BULK_SN:989F2271"
However, the device serial # is still being listed.
Going to try some other driver tests, but I'm nearly out of spoons for tonight.
Thanks for all your help so far, and any further suggestions are more than welcome.

cheshyre said:
So far, every reboot takes me back to QUALCOMM CrashDump, even with vol buttons pressed.
adb devices & fastboot devices show nothing.
I have a PC utility called USBLogView which shows all Plug & Unplug events.
My "Device Description" is no longer "OnePlus 8T" or "ADB Device" -- it's listed as "QUSB_BULK_SN:989F2271"
However, the device serial # is still being listed.
Going to try some other driver tests, but I'm nearly out of spoons for tonight.
Thanks for all your help so far, and any further suggestions are more than welcome.
Click to expand...
Click to collapse
One procedural "suggestion": use the reply button to respond to posts. That way the author receives a notification of your reply. Also use @ in front of user names so that they get notified when mentioned.
The other: you'll need to install the Qualcomm USB driver to use the MSM tool. That will allow the PC to recognise your phone in EDL mode and the MSM tool can reset your phone.
Go to the MSM Tool thread for all the details.

Thank you so much for all your help.
Trying to find the correct firmware version right now (most links & repos only have older builds)
Which do you think I should use, since 1 slot had 9.9, and the other had 10.10?

cheshyre said:
Thank you so much for all your help.
Trying to find the correct firmware version right now (most links & repos only have older builds)
Which do you think I should use, since 1 slot had 9.9, and the other had 10.10?
Click to expand...
Click to collapse
What you're running now has no bearing on MSM as it gets completely overwritten. I use the latest KB05AA MSM Tool.
And, you are still not using the Reply button

BillGoss said:
What you're running now has no bearing on MSM as it gets completely overwritten. I use the latest KB05AA MSM Tool.
And, you are still not using the Reply button
Click to expand...
Click to collapse
*sigh*
Automatic detection of DDR failed
Waiting for device
I'll take this over to the other thread, I suppose
(and fwiw, I did press "reply" that last time, but deleted the quoted text - that must've invalidated the "reply" tagging)

cheshyre said:
...
(and fwiw, I did press "reply" that last time, but deleted the quoted text - that must've invalidated the "reply" tagging)
Click to expand...
Click to collapse
It's not the button pressing that creates the notification, but the inclusion of the user name in the Quote tag. Ditto for the use of User tag when mentioning people with @+username.
See https://forum.xda-developers.com/help/bb-codes/

ASUS TF201 - issues getting any OS to boot (though TWRP works fine).

Hello folks.
In my months-long quest to avoid turning an ASUS TF201 tablet into e-waste ...
I've searched, searched again, searched some more, and while I've found answers (none of which have worked), a lot of them seem to be dated, or depend on files that are no longer available for download, so I turn to you for suggestions.
Current state:
The tablet will not boot Android.
TWRP works fine.
The problem(s):
I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails.
I have tried Chrombi-KK, following the directions step by step, but a few strange things occur:
1. When flashing through TWRP (.zip images sitting on an SD card), everything completes with no errors, but on reboot, the tablet displays its ASUS logo, but does not boot into Android. I let it sit there for three hours today, and it just sat there, displaying the logo.
2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine.
Now, I'm at a loss. The hardware seems fine, but I'm stuck ... and this is after months of trying, giving up, trying again etc.
Is this a lost cause?
Any help at all would be much appreciated. I've tried so many things, so many online "solutions," to no avail. So I turn to the experts as my Hail Mary pass before sending this to the eco centre.
Thanks for reading, and hopefully ... just maybe ... someone will have the magical set of instructions to get this thing working again.

The only command to verify whether an ADB / Fastboot connection got successfully established is
Code:
adb devices OR fastboot devices
The command
Code:
adb reboot
simply in Android's system file called build.prop (re-)sets flag ro.bootmode to normal what is read by bootloader when Android boots up.

jwoegerbauer said:
The only command to verify whether an ADB / Fastboot connection got successfully established is
Code:
adb devices OR fastboot devices
The command
Code:
adb reboot
simply in Android's system file called build.prop (re-)sets flag ro.bootmode to normal what is read by bootloader when Android boots up.
Click to expand...
Click to collapse
As it turns out, I had already stumbled upon your your "ADB-FASTBOOT-Installer" during a trip down one of the many rabbit holes trying to get this tablet working again.
adb devices returns:
List of devices attached​0123456789ABCDEF recovery​
adb reboot restarts the tablet, which I assume means the ASUS tablet driver is working.
I can't seem to do anything else with adb, however, such as push a new TWRP version, etc. This may be a key point, as it seems likely the version I have of TWRP may be too old to support upgrade using something like Chrombi-KK.
Is this a likely theory?

I would re-flash phone's Stock ROM to get rid off of all mofications applied so far to check for phone is working as expected.

NotTheLips said:
Hello folks.
In my months-long quest to avoid turning an ASUS TF201 tablet into e-waste ...
I've searched, searched again, searched some more, and while I've found answers (none of which have worked), a lot of them seem to be dated, or depend on files that are no longer available for download, so I turn to you for suggestions.
Current state:
The tablet will not boot Android.
TWRP works fine.
The problem(s):
I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails.
I have tried Chrombi-KK, following the directions step by step, but a few strange things occur:
1. When flashing through TWRP (.zip images sitting on an SD card), everything completes with no errors, but on reboot, the tablet displays its ASUS logo, but does not boot into Android. I let it sit there for three hours today, and it just sat there, displaying the logo.
2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine.
Now, I'm at a loss. The hardware seems fine, but I'm stuck ... and this is after months of trying, giving up, trying again etc.
Is this a lost cause?
Any help at all would be much appreciated. I've tried so many things, so many online "solutions," to no avail. So I turn to the experts as my Hail Mary pass before sending this to the eco centre.
Thanks for reading, and hopefully ... just maybe ... someone will have the magical set of instructions to get this thing working again.
Click to expand...
Click to collapse
ok, so good thing is twrp boots, now again if you have box with wich the tablet come try to get correct model number and search for official frimware to flash through adb using flashall.cmd
again, if official rom is not installing don't worry flash THIS custom rom using TWRP make sure to wipe all before flashing.

jwoegerbauer said:
I would re-flash phone's Stock ROM to get rid off of all mofications applied so far to check for phone is working as expected.
Click to expand...
Click to collapse
As I mentioned: "I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails."
This is exactly what I'm trying to find a solution on how to do.

[email protected] said:
ok, so good thing is twrp boots, now again if you have box with wich the tablet come try to get correct model number and search for official frimware to flash through adb using flashall.cmd
again, if official rom is not installing don't worry flash THIS custom rom using TWRP make sure to wipe all before flashing.
Click to expand...
Click to collapse
Yes, thank goodness it's not completely bricked, haha.
I think the version of TWRP that's on there may be too old, and I'm having trouble pushing a newer version through ADB ... so this is the current hurdle I'm trying to overcome.
Might you happen to have a link to the ASUS TF201 drivers known to work in Windows 10, so I can rule that out? If I can't get ADB to push a newer TWRP version from Windows, I may give it a go in Linux too ... but I'm trying not to open up new avenues of complexity, so I've restricted all my efforts to Windows as that's where most of the online help I can find tends to take place.
Thanks!
Edit: Unfortunately, the download link to [ROM][N 7.1] KatKiss Nougat [TF201] no longer works:
404 Not Found
This has been another constant obstacle, i.e., recommended files to download are no longer available.

NotTheLips said:
As I mentioned: "I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails."
This is exactly what I'm trying to find a solution on how to do.
Click to expand...
Click to collapse
Nobody needs TWRP to re-flash a device's Stock ROM.
It's typically done via ADB Sideload method.

NotTheLips said:
Yes, thank goodness it's not completely bricked, haha.
I think the version of TWRP that's on there may be too old, and I'm having trouble pushing a newer version through ADB ... so this is the current hurdle I'm trying to overcome.
Might you happen to have a link to the ASUS TF201 drivers known to work in Windows 10, so I can rule that out? If I can't get ADB to push a newer TWRP version from Windows, I may give it a go in Linux too ... but I'm trying not to open up new avenues of complexity, so I've restricted all my efforts to Windows as that's where most of the online help I can find tends to take place.
Thanks!
Edit: Unfortunately, the download link to [ROM][N 7.1] KatKiss Nougat [TF201] no longer works:
404 Not Found
This has been another constant obstacle, i.e., recommended files to download are no longer available.
Click to expand...
Click to collapse
how you tried to flash stock rom, i mean do you boot into fastboot after booting into twrp or not?

jwoegerbauer said:
Nobody needs TWRP to re-flash a device's Stock ROM.
It's typically done via ADB Sideload method.
Click to expand...
Click to collapse
As I mentioned before, "2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine."

[email protected] said:
how you tried to flash stock rom, i mean do you boot into fastboot after booting into twrp or not?
Click to expand...
Click to collapse
I've tried two methods.
The first is to try to flash it from TWRP, but this fails with an error. The stock ROM appears to be checking for dependencies, and it fails this check.
The second is to use ADB (fastboot) while the tablet is sitting in TRWP. It stalls at "< waiting for any device >".
So this the problem. Neither of those two methods work for the stock ROM.
With a third party ROM, TWRP appears to flash the device successfully (no errors or stalls). When I reboot the device, it will not boot Android, and gets stuck at the ASUS boot logo indefinitely.
I'm not sure what do next to get past these two problems.

NotTheLips said:
I've tried two methods.
The first is to try to flash it from TWRP, but this fails with an error. The stock ROM appears to be checking for dependencies, and it fails this check.
The second is to use ADB (fastboot) while the tablet is sitting in TRWP. It stalls at "< waiting for any device >".
So this the problem. Neither of those two methods work for the stock ROM.
With a third party ROM, TWRP appears to flash the device successfully (no errors or stalls). When I reboot the device, it will not boot Android, and gets stuck at the ASUS boot logo indefinitely.
I'm not sure what do next to get past these two problems.
Click to expand...
Click to collapse
here is the problem, ok so follow the steps carefully,
boot into twrp
then connect your phone to your pc
type "adb devices",
if some thing like 1234567890 -recovery shows up proceed else start-over,
after successfully detected by adb typed "adb reboot bootloader"
then after booting into fastboot mode type "fastboot device"
if something shows up proceed else tell me
make sure you have installed adb and fastboot properly,
after all this run the cmd file in stock rom, to automatically flash it.

[email protected] said:
here is the problem, ok so follow the steps carefully,
boot into twrp
then connect your phone to your pc
type "adb devices",
if some thing like 1234567890 -recovery shows up proceed else start-over,
after successfully detected by adb typed "adb reboot bootloader"
then after booting into fastboot mode type "fastboot device"
if something shows up proceed else tell me
make sure you have installed adb and fastboot properly,
after all this run the cmd file in stock rom, to automatically flash it.
Click to expand...
Click to collapse
Here's what happened:
C:\Windows\system32>adb devices​List of devices attached​0123456789ABCDEF recovery​​C:\Windows\system32>adb reboot bootloader​​C:\Windows\system32>fastboot device​< waiting for any device >​​It sits at < waiting for any device > indefinitely, until I reboot the device.

NotTheLips said:
Here's what happened:
C:\Windows\system32>adb devices​List of devices attached​0123456789ABCDEF recovery​​C:\Windows\system32>adb reboot bootloader​​C:\Windows\system32>fastboot device​< waiting for any device >​​It sits at < waiting for any device > indefinitely, until I reboot the device.
Click to expand...
Click to collapse
the problem is your pc does not have adb and fastboot properly installed

try this one https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/

also, use this official driver https://www.asus.com/SupportOnly/Eee_Pad_Transformer_Prime_TF201/HelpDesk_Download/
if your pc is 64 bit use win764bit version

NotTheLips said:
Here's what happened:
C:\Windows\system32>adb devices​List of devices attached​0123456789ABCDEF recovery​​C:\Windows\system32>adb reboot bootloader​​C:\Windows\system32>fastboot device​< waiting for any device >​​It sits at < waiting for any device > indefinitely, until I reboot the device.
Click to expand...
Click to collapse
This "waiting for device" problem happens when the USB device node is not accessible to your current user. The USB id is different in Fastboot mode, so you can easily have permission to it in ADB but not in Fastboot.
Each manufacturer implements Fastboot differently. So, if not already done yet, download and install the suitable "Android USB Driver" provided by ASUS. Then Fastboot should work.
BTW: Your device actually stucks in recovery mode.

Is OEM Unlock got enabled in Android settings? If not, Fastboot never will work.