Related
Hello everyone,
I have a typical problem - my device does not load, because it loops with android logo. It does that because i edited vold.fstab incorrectly, but have the correct lines copy in comments within the file. Problem is i don't have any idea how to enter recovery mode ( if one exist at all ) on the device! I tried most of popular combinations and nothing worked - the device always start to load normally, and loops. Most solutions to this situation is via abd, but abd does not see the device ( i guess because it's not started/not in recovery mode ).
Is there a way to access root or force the recovery ?
The device has label TR976V12 and 2012.06.06 on the board, but it's propably N90 model. I could use any help with making this work again.
Also i'm running windows 10 and i have some issues to make it work in fastboot mode...
Edit:
Device is running Android 4.2
ABD see the device as 0123456789ABCDEF
I managed to get the device to recovery mode by holding VOL+ and plugging in power supply.
Any help in finding vold.fstab to edit it back to the original is more than welcome !
Dear everyone,
I have an ASUS MeMoPad 10 (ME103K) here which I vowed to fix. The user wanted to revert to Factory Defaults, lost power or something like this, and ended up with a bricked device.
I can only start it with power button + volume up, into Fastboot. Secure Boot is enabled.
I have Android SDK and minimal FastBoot installed. Have the Google USB Drivers on my desktop.
I tried flashing SuperBoot (ADB), but ADB simply lists "Waiting for Device". No devices can be listed. It does show up in Windows Device Manager: ASUS Android Bootloader Interface.
I have the following files available:
- SuperBoot r5
- Kernel: l-8064-r1_V12.16.1.12-201508071139-foss.tar
- UL-K01E-WW-12.16.1.12-user
- recovery-original-me103k
There is apparently no recovery.img for this device. The boot.img is in the UL-K01E-WW-12.16.1.12-user file
Power = ASUS logo then goes black
Power + Volume up = Fastboot
Power + Volume down = /
Power + Volume up+down = /
Is this the place I should be looking? I'm honestly not sure if I can catch up with the details: android.stackexchange.com/questions/124344/trying-to-flash-a-system-img-i-took-with-dd-failing
Any help would be much appreciated!
- Al
EDIT:
fastboot devices now detects #serialnumber
Alright, fastboot now detects my device. I installed PDANet which didn't do anything, and then downloaded another adbfastboot package which hit it.
I'm able to start writing boot.img, but that's what it stays at. It's an 8MB file, so it shouldn't take half an hour, I suppose?
I'm not getting any error message either, though.
EDIT: It seems that regardless of what commands I send, they stall and don't get executed. ADB doesn't seem to find any devices, only Fastboot does.
EDIT 2: Tried the same on my laptop. Different ports. Nothing goes further than for example "Writing 'boot' - that's it.
Bump (won't bump until tomorrow late)
B0mp
kab0mp
boink
Bwamp
Recover Asus Me103k (k01e)
1) Stock recovery:
View attachment k01e_stock_recovery.zip
3) Run it without flash:
Code:
fastboot boot k01e_stock_recovery.img
3) In recovery select to install UL-K01E-WW-12.16.1.12-user.zip (early placed on microsd)
4) Also can check boot ability:
Extract boot.img from update firmware zip UL-K01E-WW-12.16.1.12-user
And run it from fastboot:
Code:
fastboot boot boot.img
If Android loaded normaly after it, but after reboot you see FASTBOOT MODE, than execute this commands:
Code:
fastboot oem reset-dev_info
fastboot reboot
Asus MeMo pad ME103K/K01E bootloader unlock
sheinbo said:
Hi,
after all these years I remembered my asus memo... Such a fine displsay but ... . I discovered an unofficial rom for another old device ( samsung gt 5830) and so I'd like to ask you whether you know any possibility to "upgrade" the MeMo or any other way to pitch / patch it. Your reply here let me think that you are very attached to asus memo, maybe you are still interested.
Click to expand...
Click to collapse
Same here, running the device on Lollipop is awfully slow, KitKat is somewhat better though but those are the only two official ROM's which can be found and installed.
Tried to unlock the bootloader to try different ROM's but bootloader is locked, despite all info here on XDA, nothing seems to work and the bootloader remains locked. Unlock APK's also give no result.
Running out of options here, any suggestions will be appreciated.
I've flashed TWRP onto an Allwinner A33 tablet (on recovery partition), and now it's stuck. No matter what I do, holding any combination of buttons, it always boots back into TWRP again. I can't get into fastboot to try to fix it. I also can't do anything in TWRP, because the touchscreen doesn't respond.
The only thing I can do is access a shell through adb, but it's not much use either. All the "twrp" commands don't work, there is no twrp executable anywhere. I can do "poweroff" and guess what, right back to TWRP again. I can't even see the NAND devices, only SD card.
Which A33 tablet do you have? I have the v11 10.1" unbranded and found a firmware PH or PHGQA33GA10H0312N102v11 that works for tablet it's a china rom but everything works, using the new Phoenix usb pro 4.0, I hope this helps
The device is Logicom M BOT TAB 100.
After a lot of research I finally discovered a way to get out of recovery mode:
Get a microSD sniffer breakout board and a 3.3V USB UART adapter
Connect the UART adapter: TX=CD/DAT3, RX=CLK, GND=GND, VCC=not connected
Plug the adapter into the PC and open the serial console (eg
Code:
screen /dev/ttyUSB0 115200
on Linux)
Hold "s" in the terminal and power on the device; you should see boot messages and enter a shell
Run command:
Code:
setenv bootcmd "run setargs_nand boot_normal"
- this resets the boot mode so it won't boot into recovery
Run command:
Code:
boot
(or just turn off and on again) and it should boot up normally!
Still I'm using the stock ROM without root, so if you know of a ROM that will work, that'd be great.
EDIT: actually that command didn't fix it (I can't seem to save the change with any command), but I was able to enter Fastboot, flash the original recovery.img, and boot normally.
Hello,
Any root and custom ROM available for the Lenovo tab m8 tb8505 variant? The stock rom feels good for the price but if something better to make the tab feel nicer..
Thanks
I managed to root it for now, using magisk_manager.apk and a boot.img, I extracted from a file named "TB-8505F_S100133_200316_BMP.zip" (which is the latest firmware for the M8-8085F)
am unable to find any TWRP for the device.
but at least: got root now.
OTG and Charge Simultaneously
Hello,
I recently purchased the Lenovo tab m8 to replace the outdated navigation system in my car. I thought that since it came with a dock station that I would be able to connect the otg cable on the micro USB port. However this does not work, if it’s charging on the dock and I connect the OTG it stops charging. Does anyone know how I can die both things simultaneously?
am24901 said:
Hello,
I recently purchased the Lenovo tab m8 to replace the outdated navigation system in my car. I thought that since it came with a dock station that I would be able to connect the otg cable on the micro USB port. However this does not work, if it’s charging on the dock and I connect the OTG it stops charging. Does anyone know how I can die both things simultaneously?
Click to expand...
Click to collapse
Look here: https://www.instructables.com/id/DIY-Cable-to-Use-OTG-and-Simultaneously-Charge-the/
Test
---------- Post added at 08:00 AM ---------- Previous post was at 07:13 AM ----------
Xenograph said:
I managed to root it for now, using magisk_manager.apk and a boot.img, I extracted from a file named "TB-8505F_S100133_200316_BMP.zip" (which is the latest firmware for the M8-8085F)
am unable to find any TWRP for the device.
but at least: got root now.
Click to expand...
Click to collapse
@Xenograph:
Hi, would you care to specify in detail the rooting process used for your tb-8505F?
That would be very much appreciated!
I aquired the tb-8505X (LTE) model myself, but was surprised by not being able to dig up the rooting method specific for this model from the internet for two weeks now.
So far, my attempts to aquire root have got stuck at the initial stage of having my W7-64bit laptop communicate with TB-8505X via (first) ADB (lists the device) and (second) fastboot (no devices or waiting for devices).
My suspicion is that while ADB has at its disposal the correct W7-driver, subsequently fastboot is unable to operate with that driver.
Internet search shows the <fastboot-waiting for devices> to be rather common, but without coherent solution.
Any thoughts welcome, thanks!
Did you enable developer options and and there USB debugging and OEM Unlock?
I only plugged in mt 8505F, typed the command "adb reboot bootloader", waited until Windows installed the drivers and I was good to go.
After this started the root process
Cheers
Tom
Xenograph said:
I managed to root it for now, using magisk_manager.apk and a boot.img, I extracted from a file named "TB-8505F_S100133_200316_BMP.zip" (which is the latest firmware for the M8-8085F)
am unable to find any TWRP for the device.
but at least: got root now.
Click to expand...
Click to collapse
How did you actually root it?
I tried patched boot.img, won't work, tried patched recoevery img the M8 is in a bootloop.
Only boot up after I flashed standard recovery again
Cheers
Tom
tom1807 said:
Did you enable developer options and and there USB debugging and OEM Unlock?
I only plugged in mt 8505F, typed the command "adb reboot bootloader", waited until Windows installed the drivers and I was good to go.
After this started the root process
Cheers
Tom
Click to expand...
Click to collapse
Yes, enabled all three of them.
Then installed the ADB/Fastboot package on W7/X64.
Then the usb driver/drivers (don't know).
Then from the admin CMD adb list devices (returns device name)
Reboot tb8505 into fastboot mode.
adb>fastboot list devices (returns waiting for devices...)
Any other subsequent fastboot command returns the same ''waiting for devices''.
Could be this is better attempted from W10,Ios or linux.
Any thoughts? cheers!
I think its a driver problem, which adb/fastboot package did you install?
When you are in fastboot and you open your device manager, any device which shows an exclamation mark?
Cheers
Tom
tom1807 said:
I think its a driver problem, which adb/fastboot package did you install?
When you are in fastboot and you open your device manager, any device which shows an exclamation mark?
Cheers
Tom
Click to expand...
Click to collapse
adb-setup-1.4.3. (okt 10th 2015)
device manager: shows as Alcatel ADB device>Lenovo Android Interface (upon usb connection). No exclamation marks.
From CMD C:\adb>adb devices -l
returns
HA12A76E device product: Lenovo TB_8505X-EEA model:Lenovo_TB_8505X device:8505X
Disconnecting usb & rebooting 8505X into fastboot mode, reconnecting usb:
device manager shows Alcatel ADB Device>Android ADB Interface (sic) (without having changed drivers manually). No exclamation marks, btw.
Subsequently
C:\adb>fastboot devices
(returns nothing)
C:\adb>fastboot reboot
returns < waiting for device >
Reboot 8505X from fastboot mode by pressing power button >20 seconds.
Device manager shows Lenovo Android Interface again.
8505X shows usb debugging options back at 'No data transfer' again, which does that every reboot, so I reselect connect as Media device or as Camera after every reboot.
Q... said:
adb-setup-1.4.3. (okt 10th 2015)
device manager: shows as Alcatel ADB device>Lenovo Android Interface (upon usb connection). No exclamation marks.
From CMD C:\adb>adb devices -l
returns
HA12A76E device product: Lenovo TB_8505X-EEA model:Lenovo_TB_8505X device:8505X
Click to expand...
Click to collapse
Haven't used these, I just used the which Windows (in my case wW10) downloaded
Disconnecting usb & rebooting 8505X into fastboot mode, reconnecting usb:
device manager shows Alcatel ADB Device>Android ADB Interface (sic) (without having changed drivers manually). No exclamation marks, btw.
Subsequently
C:\adb>fastboot devices
(returns nothing)
C:\adb>fastboot reboot
returns < waiting for device >
Click to expand...
Click to collapse
I am assuming the device shows it is in fastboot mode, its listed in Device Manager under Android Phone(?) as ADB Interface
After reboot it is listed fro me under USB Devices as ADB Interface. In fastboot boot the driver is from Mediatek, in working mode, the driver is from Microsoft
8505X shows usb debugging options back at 'No data transfer' again, which does that every reboot, so I reselect connect as Media device or as Camera after every reboot.
Click to expand...
Click to collapse
Used Developer Options to set the Default USB configuration to "File Transfer" works as I set it
Cheers
Tom
Installed mediatek drivers for fastboot, to no avail.
Despite setting the usb preferences to file transfer, the 8505X resets that at every unplugging/rebooting to charging via usb/no data transfer, which also could be the problem, as before entering fastboot mode, usb is disconnected.
In fastboot mode no listing under USB devices in my dev mgr, btw.
Dev mgr shows Alcatel ADB Device>Lenovo Android Interface (as before) and moreover Lenovo Tab M8 under Portable devices. That's in normal working mode.
I presume you are on W10?
Regards, Q.
unlocked bootloader; no root
Hi,
managed to unlock the bootloader on TB-8505X by connecting it to an apple mac instead of W7. Worked via ADB and fastboot, without need to install USB drivers manually.
What would be the next advisable step(s) to take in order to achieve root?
I had a look @ the TWRP site, but there was no TWRP recovery offered for the TB8505F/X.
Any thoughts appreciated. Cheers!
Q... said:
Hi,
managed to unlock the bootloader on TB-8505X by connecting it to an apple mac instead of W7. Worked via ADB and fastboot, without need to install USB drivers manually.
What would be the next advisable step(s) to take in order to achieve root?
I had a look @ the TWRP site, but there was no TWRP recovery offered for the TB8505F/X.
Any thoughts appreciated. Cheers!
Click to expand...
Click to collapse
1. Go to Lenovo site and download Rescue and smart assistant. Install and run.
2. On the rescue tab you can download the firmware for your tab (it needs to be connected to the PC).
3. Goto where you downloaded the firmware. In the RomFiles folder find the boot.img file. copy it to your device.
4. Install Magisk Manager on your device. Run and select install. select the option to patch a file and select the boot.img file you copied to your device.
5. markdown the location that magisk shows where it saved the patched file. Copy this file back to your PC.
6. Flash the file to your device with fastboot flash boot <patched file location>
7. reboot your device and run again magisk manager this should install the magisk zip file and you are rooted.
Is there any custom recovery and roms available? This tab is quite awsome
Leboboy19 said:
Is there any custom recovery and roms available? This tab is quite awsome
Click to expand...
Click to collapse
I'm looking for a custom recovery as well.
I am having problems with Fastboot. I tried all the drivers etc. and always end up with:
C:\adb>fastboot devices
(returns nothing)
C:\adb>fastboot reboot
returns < waiting for device >
Any ideas how to connect with Fastboot?
I want to replace my old Mediatek based tablet with one of these.
So i hope that there's a method to invoke Fastboot or Download Mode by other means than ADB.
While on all other devices i have to keep power Button plus vol up or down plus sometimes Menü Button pressed, my Mediatek tablet requires holding vol up or down while attaching the thing via usb, w/o touching power to power up into Fastboot.
lecorbusier said:
I want to replace my old Mediatek based tablet with one of these.
So i hope that there's a method to invoke Fastboot or Download Mode by other means than ADB.
While on all other devices i have to keep power Button plus vol up or down plus sometimes Menü Button pressed, my Mediatek tablet requires holding vol up or down while attaching the thing via usb, w/o touching power to power up into Fastboot.
Click to expand...
Click to collapse
Holding down the down vol while pressing power gets you to Fastboot mode.
That's the common method. Good. On my Acer you need to attach a usb cable even for accessing the stock recovery. But i will dump it anyway, a Tab M8 FHD has been ordered...
Hi to everybody,
my MI 9T Pro has black/broken screen so I need to access it and/or replicate the screen by using the ADB facility.
It has the USB Debug enabled, but I cannot authorize the access from my laptop due to the black screen and broken touch, there is any possibility to bypass the authorization process?
I have already tried to connect a mini-docking station in order to replicate the screen via the USB-C to HDMI feature, but nothing appears on the external display.
Any suggestion?
Many thanks
Roberto
P.S.: the phone works, it receives call, it is connected to the wifi network and, if it is connected via USB to the laptop, the "adb devices" command returns its serial number followed by a sad unauthorized status...
Tamagnun said:
Any suggestion?
Click to expand...
Click to collapse
Hello and good afternoon, Roberto.
Welcome to XDA! I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
Thank you Oswald, sorry for my wrong posting, I chose that thread because it was referred to ADB.
Kind Regards
Roberto
Don't know if it'll help, but the unauthorized message means a mismatch between pc and phone.
You can do this:
Go to C:/Users/<your username>/.android and delete a file called "adb key"
It's a hidden folder so activate that in folder options.
However, this will only trigger a new authorization message on the phone again.
The Android usb debugging notification gives you the option to switch the connection to be controlled from the phone to the PC side but it won't help if you can't see it.
IamTheBRAVE said:
Go to C:/Users/<your username>/.android and delete a file called "adb key"
Click to expand...
Click to collapse
Thank you very much for the useful tip!!
In this folder I found two files with the same timestamp:
- adbkey (without extension)
- adbkey.pub
Do you think it's better to delete both, isn't it?
Any idea to connect to the smartphone the USB-C data cable AND an external keyboard at the same time, using an OTG adaptor?
I need to use the data cable for ABD because I'm afraid I didn't activate the wireless debug option on the phone AND the keyboard in order to try to grant the authorization when the popup "appears" (ehm... it cannot, but if it should be possible it woold appear!! )
Anyway, many many thanks for this first step!!
Tamagnun said:
Thank you very much for the useful tip, in that directory I found two files,with the same timestamp:
- adbkey (without extension)
- adbkey.pub
Do you think it's better to delete both, isn't it?
Click to expand...
Click to collapse
Both is ok.
Any idea to connect to the smartphone the USB-C data cable AND an external keyboard, via OTG adaptor?
I need to use the data cable for ABD because on the phone I'm afraid I didn't activate the wireless debug option AND the keyboard in order to try to grant the authorization when the popup "appears" (ehm... it cannot, but if possible it wuold appear!! )
Click to expand...
Click to collapse
I don't know, maybe a wireless keyboard ? Or an usb hub like this:
https://www.amazon.com/TargetGo-Splitter-Extender-Ultra-Slim-Microphone/dp/B0957JKBHZ
So you can plug both the keyboard and the phone cable. Not sure if it would work...
Good luck
Hi Iam,
I'm performing some tests with an old phone (Note 4) in order to check your suggestion: unfortunately it's not possible to connect a keyboard (using an OTG cable, the phone is the "host" and devices are "clients") and to use ADBat the same time, because the standard data cable sets the phone like "client" and the PC like "host".
In fact in the OTG cable the pin 4 in the micro-USB connector is closed to GND, in standard data/charge cable the PIN 4 is not connected.
The idea to use a wireless keyboard is good, but with the black screen I cannot control BT connection or other.
In addition, I verified that the grant popup appears only if the phone is unlocked and also this is very hard with the black (and dead) screen.
I read in another thread (that I'm not able to find now...) that by copying the adbkey file from the PC .android folder to an internal android directory on th phone (something similiar to /data/adb/keys, but I don't remember well...) the smartphone authorizes the PC to connect via adb, do you now if this method could be a way to bypass the manual grant operation ?
Do you know a method to copy a file from PC to the phone by starting it in recovery mode?
Fastboot can help in this operation?
Thank you
Transferring files can only be done with adb push command.
I am not aware of a directory in the phone with the adbkey in it. So can't help you there...
Edit: found this
Storage location of "adb_keys"
I have a Galaxy s3 (I9300) that has a broken touch screen (display is fine). I therefore can not click the authorization dialog that pops up when I try to access the device via adb on any ROMs above
android.stackexchange.com
Hope it helps a little.
Hi Iam, thank you for your help!
On GitHub I found the cmd to copy RSA key from the PC to the smartphone, it is:
adb push %userprofile%/.android/adbkey.pub /data/misc/adb/adb_keys
but the author wrote that it works only with rooted phones... and my broken one is not!!
Anyway I'll try and I'll write here the result of the test in order to share my experience.
Nothing to do, it doesn't work...
The phone is switched on because if I connect it to the data cable on the PC I get this result:
C:\Users\rober>adb devices
List of devices attached
598261c1 unauthorized
and it is in RECOVERY MODE because I cannot find its IP address on the wifi router, but I cannot push the adbkey file:
C:\Users\rober>adb push C:\Users\rober\.android\adbkey.pub /data/misc/adb/adb_keys
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.
I don't have any idea to bypass the unauthorized state, due the host/client state it isn't possible to connect an external keyboard and the data cable at the same time, wireless keyboard cannot be paired without accessing the display so I dont' know how to proceed... sigh...
If someone has a suggestion I'll really appreciate it!
Found this. Can you try it?
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
What do you have for a screen lock? Swipe? Pattern? Numbers?
You need to tap and swipe the screen to get things done.
A plugged in mouse could do that if you only knew what you were doing.
If you have a digitizer (Wacom tablet) you can use that to do anything the screen can do.
Also, are you quite sure that the screen isn't responsive? It could be black but responsive.
I did a project to swipe patterns using a separate, rooted Android.
It works like a charm, but it's kind of a pain to set up.
See: https://forum.xda-developers.com/t/accessing-my-phone-with-a-dead-screen.4542763/post-88013171
Hmm, it's actually more complicated.
I plug in a device and the authorization popup appears.
But, if I pull the plug, the popup disappears after a second.
You won't be able to get a USB digitizer working.
You'd need a Bluetooth digitizer, but that would have to be enabled too.
So you'd need the USB digitizer to enable the BT digitizer.
(By "digitizer" I mean any absolute pointing device.)
If there is an internal UART (hardware console) you might be able to simply type in the adb_keys.
this script claims to by-pass the adb authorization by patching stock boot.img and resign with google test keys. it might work on locked bootloader (untested)
https://github.com/bkerler/android_universal
I don't know how it works, but you can hopefully write/flash partitions in EDL mode with this loader (untested)
https://forum.xda-developers.com/t/...r-qualcomm-based-phones.4368989/post-88041131
there is also a linux executeable to reboot into EDL mode from fastboot
https://github.com/bkerler/edl
Code:
$ fastboot devices
$ ./fastpwn oem edl
to install the loader
Code:
$ python3 edlclient/Tools/fhloaderparse path/to/FHLoaderDir Loaders
if you don't have linux you can try the re_livedvdV4.iso from pendrive.
there is also executeable for windows to reboot EDL and another EDL tool for windows (credits: @Renate)
the downside of this, once you rebooted phone you cannot get back to its currently (AFU) unlocked state, which means all your files are no longer decrypted (BFU). you can install apps remotely only as long as the phone is decrypted and online, so maybe there is a better way (vysor?)
alecxs said:
there is also a linux executeable to reboot into EDL mode from fastboot
Click to expand...
Click to collapse
I see that the "fastpwn" is 12 MB. Seems a bit large. No idea what's in there.
Some abl's may support fastboot commands for getting to EDL.
I've never seen it clearly listed which do have that.
The standard fastboot filters all commands except for "oem".
Code:
fastboot tickle me elmo // will not even be sent because "tickle" is not on the command list
fastboot oem ridiculous command // will be sent since oem commands get a free pass
So if your device uses an oem command to get to edl it will work with the stock fastboot.
If it uses a special "first tier" command you will have to use a modified, lenient fastboot.
IamTheBRAVE said:
Found this. Can you try it?
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
Hi Iam, I found a similar page on GitHub and I tried to input the adb pull command (see my previous msg), but because the PC is not authorized there is no way to write anything on the phone by using abd.
Many thank for your tentative to help me.
Renate said:
What do you have for a screen lock? Swipe? Pattern? Numbers?
You need to tap and swipe the screen to get things done.
A plugged in mouse could do that if you only knew what you were doing.
If you have a digitizer (Wacom tablet) you can use that to do anything the screen can do.
Also, are you quite sure that the screen isn't responsive? It could be black but responsive.
I did a project to swipe patterns using a separate, rooted Android.
It works like a charm, but it's kind of a pain to set up.
See: https://forum.xda-developers.com/t/accessing-my-phone-with-a-dead-screen.4542763/post-88013171
Hmm, it's actually more complicated.
I plug in a device and the authorization popup appears.
But, if I pull the plug, the popup disappears after a second.
You won't be able to get a USB digitizer working.
You'd need a Bluetooth digitizer, but that would have to be enabled too.
So you'd need the USB digitizer to enable the BT digitizer.
(By "digitizer" I mean any absolute pointing device.)
Click to expand...
Click to collapse
Hi Renate,
it is not possible to connect at the same time a USB keyboard (phone is the server by using an OTG cable) and a data cable (phone is the client in this situation) and as you have verified, when the data cable is disconnected, the grant message disappears...
I have a BT keyboard, but it is not possible to pair it to the smartphone working on a black screen, even if it was responsive.
Finally, I thing there isn't a way to bypass the grant message and authorize the phone "regularly", I think.
Renate said:
If there is an internal UART (hardware console) you might be able to simply type in the adb_keys.
Click to expand...
Click to collapse
Where the UART should be present? Inside the phone? Uhhmmmm.... Even if I found it your idea would be to wire it by soldering directly on the mainboard? Too much difficult for my poor experience, sorry!
Many thanks for your answer.
Before to start with replies, dear Alexc and Renate please let's apologize me because I'm absolutely newbie about these new devices, in order to clarify to you my (un)knowledge condition, let's consider that my last fw update was performed using the Odin tool on very old Samsung devices!
Thanks to your suggestions, now I know what is the fastboot and EDL (I read something on XDA and other sites), but I haven't understood if it is possible to read the userdata from one of these two boot states... anyway, I try to reply you, if you would want to continue to help me I'll be very grateful for this!
alecxs said:
this script claims to by-pass the adb authorization by patching stock boot.img and resign with google test keys. it might work on locked bootloader (untested)
https://github.com/bkerler/android_universal
Click to expand...
Click to collapse
It is written that it is tested only up to Android 10, so I prefer to avoid to test this method on a smartphone that hasm't a working screen, it isn't possible to understand what happens on it.
https://github.com/bkerler/android_universal
alecxs said:
I don't know how it works, but you can hopefully write/flash partitions in EDL mode with this loader (untested)
https://forum.xda-developers.com/t/...r-qualcomm-based-phones.4368989/post-88041131
Click to expand...
Click to collapse
I downloaded the firehose file for the chipset 855 but I'm not interested to flash a new firmware or similar...
alecxs said:
there is also a linux executeable to reboot into EDL mode from fastboot
https://github.com/bkerler/edl
Code:
$ fastboot devices
$ ./fastpwn oem edl
Click to expand...
Click to collapse
OK, the previous is clear for me: now the smartphone is booted in fastboot mode and the utility can access it:
Code:
C:\Users\rober>fastboot --version
fastboot version 34.0.0-9570255
Installed as C:\Android-Recovery\platform-tools\fastboot.exe
C:\Users\rober>fastboot devices
598261c1 fastboot
Is the fastboot utility version the right one to operate on my smartphone?
Please let's explain me: if I'll reboot the phone to EDL (using fastpwn utility, fastboot oem command or another utility or method) I risk to lose my userdata ?
alecxs said:
to install the loader
Code:
$ python3 edlclient/Tools/fhloaderparse path/to/FHLoaderDir Loaders
Click to expand...
Click to collapse
Sorry for the stupid question, but why I have to install a loader on the phone?
alecxs said:
if you don't have linux you can try the re_livedvdV4.iso from pendrive.
Click to expand...
Click to collapse
My Surface has Win10 and Ubuntu (I never use it but I have prepared a dual boot for any needs...).
alecxs said:
there is also executeable for windows to reboot EDL and another EDL tool for windows (credits: @Renate)
Click to expand...
Click to collapse
I would prefer to use Windows utilities, but it is not mandatory...
Before to try to switch to EDL I need to understand if this operation will destroy my data or not, and what I can do from this EDL boot mode, I know it is posisble to flash the phone from scratch, but is it possible to read data by mounting phone partitions or similar?
For example, I listed the fastboot options and I found the possibility to FETCH a partition from the phone and copy it to the PC, this can help to access my data?
Maybe they are encrypted?
Do you have a schema or a list of all available partitions inside a MIUI 13 device? (I need to learn something before to proceed...)
alecxs said:
the downside of this, once you rebooted phone you cannot get back to its currently (AFU) unlocked state, which means all your files are no longer decrypted (BFU). you can install apps remotely only as long as the phone is decrypted and online, so maybe there is a better way (vysor?)
Click to expand...
Click to collapse
So, the previous message is the reason I'm very carefull before to switch to EDL boot mode: is it enough to switch the phone to EDL in order to lock all data because they'll become definitively encrypted ??
Please let's try to clarify me your suggestions and how to proceed...
Many many thanks for your patience
Update: with the cmd fastboot getvar all I obtained the entire partions list, I tried to fetch one of this and the result is:
Code:
C:\Users\rober>fastboot fetch limits cache.ext4
fastboot: error: Unable to get max-fetch-size. Device does not support fetch command.
Not good, but at least I have answered to a couple of questions by myself... sigh...
@alexc: two years and seven months ago you helped someone to retrieve userdata from a bricked MI 4C by suggesting the followiing process, can i do something similar on my MI 9T PRO?
1 Obtain a programmer
To successfully acquire all of the data from EDL you need programmer.
For Mi 4c it is prog_emmc_firehose_8992_ddr.mbn that can be obtained in (first?) official image of OS. I got it from file Xiaomi_Mi_4C_V8.1.3.0.LXKCNDI_20161213_China_5.1_XFT.zip on some random site. You can find it in the archive under folder Firmware/images/.
The full path in archive would be Firmware/images/prog_emmc_firehose_8992_ddr.mbn.
2 Get working FirehorseI have got mine from repository: https://github.com/bkerler/edl.
Proceed with all instructions mentioned in the repository. (I personally used Ubuntu 20.04 as all of the stuff is easier to make work.)
3 Connect to EDLBoot phone to fastboot. In case of Mi 4c that is my case it is pushing volume down during boot.
When you enter fastboot and you can see your device with fastboot:
fastboot devices
In case of Mi 4c you can directly boot to EDL with command:
fastboot oem edl
4 Acquire data through EDLWhen device enters EDL state you can test connection with programmer (in my case prog_emmc_firehose_8992_ddr.mbn). In loader parameter you are entering path to this file.
./edl.py --loader=prog_emmc_firehose_8992_ddr.mbn printgpt
When it outputs all of the partition then you are golden!
On my phone there is one partition named userdata:
userdata: Offset 0x00000000c4000000, Length 0x0000000683bfbe00, Flags 0x00000000, UUID 07c2b899-1574-564c-2f46-e26a6378bdd8, Type 0x1b81e7e6
To acquire the partition use command:
./edl.py --loader=examples/prog_emmc_firehose_8992_ddr.mbn r userdata userdata.bin
The copy of user data just needs to be read.
5 Reading user data (userdata.bin)Luckily for the phone Mi 4c you can directly mount the dump in Linux. For some other phones the process might not be so straightforward and you might need simg2img. But I am not 100% sure.
sudo mkdir /media/userdata
sudo mount -t ext4 -o loop userdata.bin /media/userdata/
To read the data you will need to get root rights as the data belong to non-existing or different existing users and you won't get access with your user.
sudo mkdir userdata
sudo cp -r /media/userdata/media/0/* userdata/
The path to the your data might be different so take your time to look around.
Done! All the data are now completely accessible.
Click to expand...
Click to collapse
What is the "programmer"?
As I wrote before, I downloaded the file prog_ufs_firehose_sdm855_ddr.elf but it is the firehose, not the programmer, isn't it ?
Many thanks, I spent all the night to try to acquire some knowledge, but I have too many dubts again...
When your Android boots it goes PBL (in ROM) -> xbl -> abl -> Android.
A Firehose loader is a custom replacement for xbl that it can load live.
Instead of loading all the rest of the stuff it just sits on USB and awaits commands.
Firehose, programmer, loader, .bin, .elf, .mbn can all be the same things.
Using EDL will not hurt your system or data (unlike fastboot unlock).
If you read back your userdata it will still be encrypted (if it was).
One thing that you can do is read back your entire image.
Then you will in any case be able to restore your device to exactly how it is right now.