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.
Related
June 02, 2015
Edit: If anyone has a link to the stock ROM for the Ascend G7, please let me know. I would love to make a custom ROM that doesn't take up 98% of all resources 99% of the time.
Hello everyone.
Before I get started, here is everything you need to know about this post.
- This root works as of June 29, 2015
- This is a rooting process for the Huawei Ascend G7
- I did not make this, so please consider supporting all mentioned sources
- I am a new user to XDA, but I've been developing for over a decade. I will regularly check this post if enough people who view it have questions
There are two parts to this process.
First, we unlock the bootloader
Second, we flash a recovery, and subsequently, SU (root)
Let's get started. This will take at least 16 hours. User interaction 5 minutes, and about a 16 hour wait for an email response from Huawei.
Also, I have a new account, so I cannot post links. So please bear with me. I will upload photos in as best order as I can.
Before we get started, please note that your phone will factory reset in this process.
First thing's first. The Ascend G7 requires an unlocked bootloader, before any root can take place. This is obviously temporary, until someone finds a circumvention. But for now, this is how this needs to be done.
Send an email to [email protected], with this format:
Dear Sir/Madam
Please may I request the bootloader unlock code for my Huawei Ascend G7?
Here are some Details:
Serial Number: (Found under Settings --> About phone --> Status)
IMEI: (Found under Settings --> About phone --> Status)
Baseband version: (Found under Settings --> About phone)
Please could you send me the code directly, as I cannot access the product ID on my device.
Thank You
Your name
This part is important. Sometimes, they do not even reply to your email(s). It is recommended - nay, required - for you to put "URGENT" in the subject field of the email. Something along the lines of "URGENT Request Bootloader Unlock Code." It would also be best if you mark your email as urgent/high priority, as well.
Meanwhile, while you wait for the email from them with your unlock code, (expect it to arrive the day after), download the Android SDK and the Java JDK, if you haven't already. What you need most are the SDK tools, which you can also download by typing in "SDK tools android" in Google and finding a download for the stand-alone tools.
Make sure Android Studio is updated, if you already have it. To make sure you have everything you need, open up command prompt in platform-tools, by holding shift and right clicking somewhere on the white, in the folder, (explained in attached picture).
Then, plug in your phone. Make sure USB debugging is enabled. To do so, go to Settings --> About phone --> Tap "Build Number" 7 times in a row. Then go back, and you will see "Developer options." Click on that, and enable USB debugging. Also, this optional, but I like to enable the "Stay Awake" function.
Make sure to accept any prompts that your phone will ask.
Then, go to the command prompt and type in "adb devices" without the quotations.
If you've done everything correctly so far, you should see something similar to the attached command prompt image file.
If everything checks out, let's proceed. If not, post below, and I, or fellow XDA users, will help you out.
Proceed to type in, "adb reboot bootloader" without the quotations, into the command prompt window that you opened. Your Ascend G7 should reboot into fastboot, where you will see something like the attached picture below, of the bootloader screen.
Except, it will say Phone Locked instead of Phone Unlocked.
Now, go back to your command line, and type in "fastboot reboot," to have access to your phone and its functions, while you wait for the email from Huawei.
`````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````
Everything below this line should be done AFTER receiving a reply email from Huawei, with your unlock code.
Now, download the "PHILZ-TOUCH-6.rar" file. I cannot attach it here because it exceed file size limit. No virus, no surveys, here's the link, https/goo.gl/sxPv7I. Just add a colon and a forward slash after https. It is not a virus, in case your firewall or antivirus software brings up red flags. I will post the whole ZIP that I've downloaded from another website. There's a bunch of redundant elements in the folder, but just in case you know what you're doing and might need the tools, I'll keep them there. But all you will need are 2 things from the folder. They're mentioned next.
Go to where you extracted PHILZ to, and hold shift and right click and open a command window in that directory, and type in "adb devices" one more time to make sure your device is listed and connected. Then, type in "adb reboot bootloader," give it a second, and then when fastboot loads up, type in,
fastboot oem unlock 123456789123
Replace "123456789123" with the unlock code provided to you from the Huawei email. Give it a second, and then you should be good. It should now say "Phone Unlocked" in red. Now, type
"fastboot reboot"
in the command line (that was opened in the PHILZ folder), without quotations. Then type,
adb reboot bootloader, one more time, and then,
Navigate to the PHILZ folder, and run "install-windows.bat" as administrator, if using Windows.
If using Linux, run "Install-Linux.sh," and if using a Mac, run "Install-Max.sh"
Now, in CMD type,
fastboot boot recovery.img
Then, again type in
fastboot reboot
Your phone will reboot.
`````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````
Aaaaaaand that's it! You should now be rooted. I recommend going to play store, and downloading a Root Checker to ascertain root access.
The last picture, where it says I have root access now, is a program called Root Genius. It's a one click tool to root any android device - obviously except the Ascend G7, (knowing my luck). But it does work as a root checker as well, if you want to ascertain root access. You can also download Root Checker from the play store; works more or less the same way.
Any questions, feel free to ask. Re-reading this, I could see if the instructions bring confusion to some. I will be glad to clarify any questions.
Works
Root confirmed G7-L01
some point that I did not understood
dear wertywhy,
your guide is really well done, but there are some points not clear to me
1) open up command prompt in platform-tools
what is platform-tools? A specific folder? I was not able to find it
2) if I open the command prompt from any forlder using the shift+right button as you said and then write adb devices I get this message:
'adb' is not recognized as in internal or external command operable progrma or batch file. What should I do?
3) when I connect the phone by usb cable, should I do something more (like enabling device file manager, pc suite or other options) or just connect it in charge only mode?
thank you for your time!
and... by the way, I'm really impressed that I got the anwer from Huawei with the code, that's really cool! Thank you!!
---------- Post added at 04:09 PM ---------- Previous post was at 03:19 PM ----------
I found the platform-tools folder, now if I type adb devices from a prompt open from that folder I don't get the error message anymore, but I get nothing, just the flashing prompt line (the huawei phone is on and usb connected to pc)
dear wertywhy,
your guide is really well done, but there are some points not clear to me
1) I had to install hi-suite to let the command adb work (before that adb was not finding the phone)
2) the file names of adb inside PHILZ_TOUCH is adb-windows and fastboot is fastboot-windows
3) when I input the command adb-windows devices inside the prompt inside the PHILZ folder the result is device offline, I could unlock the phone running the command from platform-tools directory (phone is unlocked now) but I can't run the command to root the phone until I have this "device offline"
Point 1 and 2 are not problem, just something that happened to me, but point 3 is stopping me, any idea how to solve point 3?
Frankleoni said:
3) when I input the command adb-windows devices inside the prompt inside the PHILZ folder the result is device offline, I could unlock the phone running the command from platform-tools directory (phone is unlocked now) but I can't run the command to root the phone until I have this "device offline"?
Click to expand...
Click to collapse
I'm having the same problem. I tried toggling usb debugging off and back on, tried another usb port and another PC (WIN 7 and 8) but none of that helped.
<device offline>
Frankleoni said:
dear wertywhy,
your guide is really well done, but there are some points not clear to me
1) I had to install hi-suite to let the command adb work (before that adb was not finding the phone)
2) the file names of adb inside PHILZ_TOUCH is adb-windows and fastboot is fastboot-windows
3) when I input the command adb-windows devices inside the prompt inside the PHILZ folder the result is device offline, I could unlock the phone running the command from platform-tools directory (phone is unlocked now) but I can't run the command to root the phone until I have this "device offline"
Point 1 and 2 are not problem, just something that happened to me, but point 3 is stopping me, any idea how to solve point 3?
Click to expand...
Click to collapse
Hi Frank,
Let's troubleshoot,
If it lists your device as offline, open up cmd (Run --> cmd), and type in,
taskkill /f /im adb.exe
Then, restart your G7; when it boots up, turn off and then on USB debugging, then find PHILZ, and retry point 3. If device is still offline, please let me know. The issue sounds like it's within the phone, not within ADB.
Alternatively, if that doesn't work, please delete PHILZ off your computer, and wherever it says "PHILZ" in my guide, replace it with the attached folder, (attached with this reply).
Cheers
PS, please make sure to check that your phone is not only in USB debugging mode, but that you've approved/allowed your computer access to your phone, (a prompt will show up on the Ascend G7 that asks you whether or not you trust your PC). And also make sure your phone isn't just set to "charge" when plugged in - activate/select MTP when you connect your phone to computer.
<device offline>
lume12 said:
I'm having the same problem. I tried toggling usb debugging off and back on, tried another usb port and another PC (WIN 7 and 8) but none of that helped.
Click to expand...
Click to collapse
Please refer to my reply to Frankleoni below.
Thank you for replying chy_vak,
I tried your solution in both the PHILZ folder and the new folder you attached. The device shows offline in both of them. However in the build-tools folder it shows online. The command line taskkill /f /im adb.exe terminated adb but the device still shows offline. I did everything in the exact order you wrote.
offline
search Kings Root via Google Chrome, install it and run it Easy and without chat with Huawei support
Kingroot Works like a charm !
@chy_vak, Thank you for your Work. 1st Part works great. 2nd Part went wrong, i dunno why i`ve tried every thing. I hate this Kingroot think, don`t touch it you never will leave it.
I have connect my G7 because unlock works. When i use CMD from Adb Tool it is connected, when i use command prompt from Philz he cant see and find the mobile?? Something for you absolute clearly, isn`t for other. Sry cant do screenshot with notebook and Win 10. have fun
Another Working Method to Root Huawei Ascend G7-L01/L03
Greetings!
I got an Ascend G7 Recently and I needed to Root it as soon as I got it. That's why I kind of broke my head looking for the current methods to do it. I found this one very promising so I started working. I followed the steps that were given to us one by one. Everything was alright until I tried to install the Windos-Installer.bat as administrator, I tried to many ways to this method work, but as much as I tried, I couldn't go with it, that's why I started working for 11 hours until I got it. This Worked for me, and I want to share it with you.
Please read the following notes before you start by rooting your device:
-As usually, do it at your own risk, I'm not responsable of any brick, or issue that damaged your device.
-This Method is working great on Windows 10
-This Method is working at 04/08/2015
-This Method, was tried by me, the directions I give to you, are based on my work by rooting my device and my experience, the software and files included were made and posted by someone else including the person who wrote this post: http://forum.xda-developers.com/gen...-confirmed-t3125621/post61122491#post61122491
-You can find screenshots of the procedure below
-You will need a microSD
-I strongly recommend you to have at least 80% of battery to avoid risks of bricks
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Here begins the directions:
1.- As has been said, you will need to unlock your device bootloader in order to root your phone. So as they said, you will need to write an email to Huawei. The mail you will send should look like this:
To: [email protected],
[email protected]
Subject: (URGENT) Unlock Bootloader
Model: Huawei G7-L03/L01 (Depends on your version)
Serial Number: (The one that comes in your Huawei's box)
IMEI: (You can get it on your box or in the info included on Configuration->About the phone->State
Product ID: (You can get it by typing on the Dial the next code: *#*#1357946#*#*)
I appreciate your concern of reading this. Waiting for a response.
Sincerely: (Your name)
After a while (Could take between 15 minutes and 16 hours depending on their time) A Huawei worker will answer you something like this:
Dear Customer,
Thank you for supporting Huawei device. My working number is ****. Your unlock code :************** , please keeping your unlock code properly.Thank you!
Huawei Terminal Company limited
1.1.- (OPTIONAL) As we are going to unlock the bootloader, we are going to make a factory reset, so I strongly recomend you to make a backup with the official huawei backup app in order to restore our settings, apps, and files.
1.2.- Once Again, as has been said, you will need to download the whole Android suite (Android Studio) the last version, update your java version, and download the last drivers for your device (A good way to do the last is by installing the HiSuite of Huawei).
1.3.- You need to activate the debug mode. You can find it in: Configuration->Developer Options->USB Debug (If you dont have the Developer options enabled, you have to go to Configuration->About the phone->Compilation And tap this last one 7 times)
2.- Download the .rar a the end of the page and extract it where you want, includes everything we are going to need. [You must put the file ''superuser.zip'' on your microSD (In the root of the microSD)]. After Downloading it, you must open a cmd window, running it as administrator. After that you will write:
cd (Here you should paste the ubication of your extracted File Ex: C:\Users\Josh\Downloads\Root Ascend G7)
Now you are in this ubication that includes adb. Write:
adb devices
You should see: List of devices attached, a code and the word device (There is a capture below). If you do, we can proceed.
3.- Type :
adb reboot bootloader
It should load a white page with the Android pet and the words FASTBOOT&RESCUE MODE Below there is the phrase ''PHONE LOCKED'' in color. Now type:
fastboot oem unlock *********** (The code Huawei gave to you)
Now your phone will make a factory reset. You will see how it reboots by itself and back to the default settings. You will need to activate the debug USB mode again. By this point its supposed your bootloader is now unlocked, to probe it, we will type again:
adb devices (To check it is correctly plugged)
Then we will type:
adb reboot bootloader
And now at the end of the page it should say: ''PHONE UNLOCKED''. If you do, we can proceed.
4.- At this point, you have two options: You can replace your stock recovery mode by a ClockWorkMod Recovery (I strongly recomend you to do that) or you can just ROOT the phone whithout replacing your stock recovery.
If you decided by replacing your stock recovery follow the next directions: We still have our CMD window opened and running adb while the phone it is on the bootloader mode. So now what you have to do it's to type:
fastboot flash recovery recoveryP.img (CMD will work and show a few commands)
And after that type:
fastboot reboot
Your phone will reboot again normally and we can proceed.
If you decided not to replace your stock recovery instead of typing ''fastboot flash recovery recoveryP.img'' you have to type:
fastboot boot recoveryP.img (This will send you directly to CWM recovery)
5.- You must acces to CWM Recovery.
If you installed it on your phone, turn off your device and then press the power button and vol+ until the Huawei logo appears, you should be in the recovery mode by now.
If you didn't install it, you already are in CWM recovery.
6.- With the vol and power buttons or the touch buttons at the end you should be able to navigate on the recovery. We go to:
Advanced Functions->Re-root System (SuperSu)->Yes-Apply SuperSu (You will see a few code at the end of the screen)
7.- Without leaving the recovery mode, go to the main screen and now we go to:
Install Zip->Choose zip from /sdcard->superuser.zip (The one that you previously putted on your microSD)->Yes-Install superuser.zip
(You will see again a few code at the end of the page) We go back to the main screen and Select:
Reboot System now
8.- It's supposed we are ROOT now. At first you will see the ''superuser'' app installed. To probe that works, Install ''android-terminal-emulator-1-0-70-multi-android.apk'' that it is included on the folder ''Terminal'' form the file you downloaded. Now open a new terminal window and type
su (If everything worked, superuser will ask for permissions)
8.1.- Restore your data with the Huawei Backup App
And that is all we have superuser acces now. If you have any question or issue let me know and I will help you.
https://mega.co.nz/#!Al9FxDBY!QHkljnnIbjURX01A59tJPNkAVQd3LbKTqRJHD_nNxrs
Thank you!
Cant boot into recovery
Hey guys so i tried following this procedure but it never works :/ if i flash the custom recovery and try boot into it, the phone directly goes to fastboot and rescue mood so cant boot into recovery, not even the stock recovery. if i try directly booting into the custom recovery it says dtb not found :/ can someone please help me?
the model is G7-L11 and the bootloader is unlocked
Engineer Mode Huawei Ascend G7 L03
Huawei Ascend G7 L03
Hi,
I have tried every thing to go into Engineer Mode.... Even Mobile Uncle Does not do that!
Please some one Help....
Huawei Ascend G7 L03
thanks for the translated philz touch
Hello everyone, I have a big problem with a Huawei G7. I did Philz Touch and Root. How can I go back to stock rom?
I've emailed Huawei 3 times now, left a week in between emails, and still haven't received my unlock code. Has anyone else had this issue?
Thanks
1.- As has been said, you will need to unlock your device bootloader in order to root your phone. So as they said, you will need to write an email to Huawei. The mail you will send should look like this:
To: [email protected],
[email protected]
Subject: (URGENT) Unlock Bootloader
Model: Huawei G7-L03/L01 (Depends on your version)
Serial Number: (The one that comes in your Huawei's box)
IMEI: (You can get it on your box or in the info included on Configuration->About the phone->State
Product ID: (You can get it by typing on the Dial the next code: *#*#1357946#*#*)
I appreciate your concern of reading this. Waiting for a response.
Sincerely: (Your name)
Does anyone have a good tutorial on how to flash twrp on the phone ? I've tried different things but it never works
any other method exept this email method? they wont answer me.
I’ve been lurking on these forums for a while and I have decided that I’m willing to take the risk to unlock my Thor’s potential. I have made sure to read through advised reading materials, and searching through other posts before posting. (I tried figuring out how to quote multiple posts to make this thread easier to navigate but I couldn't, sorry)
Device: Kindle Fire HDX 7” 3rd Generation running Fire OS 4.5.5.3
I will be using a Windows 10 Home machine to do this.
Purpose: Allow for the device to work well in Google’s ecosystem so I can have a useful device for medical school.
I am currently trying to learn the steps outlined here, but I have some concerns:
Does it matter whether or not I factory reset my device before I begin?
Will my computer’s OS cause any issues? According to this, there might be some driver issues? Should I download the “Motorola Device manager”?
Where is the “aboot_vuln.mbn” file? Do I obtain it once I follow the steps in order?
I want to use “Minimal ADB and Fastboot” instead of the attached “15 seconds ADB Installer v1.4.3” because the later has not been updated in a while and the former was updated this month. According to the install instructions for the former, I need to have my device already plugged in and the “kindle fire USB driver” already installed. Will this affect step 4 of the procedure or anything else?
On step 5, am I correct in my assumption that changing the driver will be a simple few click process?
On step 6, do I follow the directions as they are quoted, or the ones on the original forum? If the later, does “change to the directory with the extracted dd.exe” mean to type the directory or something else? Also, a poster here stated that he got error message on the second 2 commands instead of the first, is the concerning at all? Should I take any precautionary measures?
Once step 9 is completed, can the kindle run as normal if I don’t flash anything? And what does it mean “get into the TWRP”? I’ll simply be in the recovery menu on the kindle? How do I flash my chosen ROM using TWRP?
What ROM do you recommend for my needs? And could you provide me a link to the correct download/discussion board? I would prefer a ROM running at least Nougat that has long-term support planned. I read that “Fire Nexus ROM” is pretty basic, so I don’t think I want it. As of now, I’m looking at CM/Lineage 14.1, but I don’t know what ROM would work on my device from the website. AospExtended seems like a good option but apparently, there are wi-fi issues which are a deal-breaker.
Thank you so much for reading through this. Hopefully all my research and proves to be useful for anyone trying to help. If I’m able to get this working cleanly, I would be willing to make a cleaned up guide for this version and device to better aid future people.
hwwof said:
I’ve been lurking on these forums for a while and I have decided that I’m willing to take the risk to unlock my Thor’s potential. I have made sure to read through advised reading materials, and searching through other posts before posting. (I tried figuring out how to quote multiple posts to make this thread easier to navigate but I couldn't, sorry)
Device: Kindle Fire HDX 7” 3rd Generation running Fire OS 4.5.5.3
I will be using a Windows 10 Home machine to do this.
Purpose: Allow for the device to work well in Google’s ecosystem so I can have a useful device for medical school.
Click to expand...
Click to collapse
Hello @hwwof -
You have done your homework (thank you!) and presented reasonable questions. I'm going to answer the first five 'in-line' below. Responses will be brief to keep the thread serviceable for those accessing XDA content on small screens; don't read anything into that. Bounce back on any items that need further elaboration.
hwwof said:
I am currently trying to learn the steps outlined here, but I have some concerns:
Does it matter whether or not I factory reset my device before I begin?
Click to expand...
Click to collapse
No; however, it would be better if you did NOT reset the device.
hwwof said:
Will my computer’s OS cause any issues? According to this, there might be some driver issues? Should I download the “Motorola Device manager”?
Click to expand...
Click to collapse
Nope. Drivers installed via the Motorola Device manager are properly signed which mitigates any potential issues on 64-bit Win 10 builds (yet another reason to use the Moto drivers vs others that have been posted)
hwwof said:
Where is the “aboot_vuln.mbn” file? Do I obtain it once I follow the steps in order?
Click to expand...
Click to collapse
It's contained within aboot-13-thor.zip; just named differently.
hwwof said:
I want to use “Minimal ADB and Fastboot” instead of the attached “15 seconds ADB Installer v1.4.3” because the later has not been updated in a while and the former was updated this month. According to the install instructions for the former, I need to have my device already plugged in and the “kindle fire USB driver” already installed. Will this affect step 4 of the procedure or anything else?
Click to expand...
Click to collapse
Good idea. Your device does not need to be tethered while installing Minimal ADB and Fastboot. Take note of where the package is installed (typically "C:\Program Files (x86)\Minimal ADB and Fastboot") and practice opening a command window focused in that folder. To make life simpler you can direct the installer to place the files in "c:\work" which is a lot easier to type.
hwwof said:
On step 5, am I correct in my assumption that changing the driver will be a simple few click process?
Click to expand...
Click to collapse
Yes - but here's were it gets interesting and a bit frustrating. Even with the Moto drivers Windows can be very fussy communicating with HDX devices. To complicate matters there are two modes to deal with: ADB and Fastboot. You'll learn which is which as time goes on and will likely have to switch Windows drivers for each mode. Sometimes a reboot is needed to get everyone talking. Note there is no danger involved simply tethering your device and issuing basic queries.
To test basic ADB communications:
- execute step #2 (only) from the linked procedure
- open a Windows command prompt as outlined above
- boot HDX into FireOS and move past the screen lock
- tether device to windows; take note of any noises and/or confirmation messages
- in the window command prompt issue the command "adb devices" and press Enter. What happens?
Post back results and we'll go from there.
Thank you @Davey126 . I appreciate you taking the time to help me out. Answers to the other questions would be very appreciated as well!
Here are my results that you requested:
The kindle beeped, and the internal storage popped up on my computer. I ran the minimal adb and fastboot program, and got this output:
Code:
C:\adb>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
D0FBA0A0351401GB unauthorized
C:\adb>
And on the kindle, I got a “Allow USV debugging” popup on the kindle and it showed my computer’s RSA Fingerprint. I then pressed allow. I took note of the fingerprint just in case. I then tried ejecting my device but it wouldn’t let me because a program was still using it. I ran “adb devices” again and got this output:
Code:
C:\adb>adb devices
List of devices attached
D0FBA0A0351401GB device
C:\adb>
hwwof said:
Thank you @Davey126 . I appreciate you taking the time to help me out. Answers to the other questions would be very appreciated as well!
Click to expand...
Click to collapse
Second response is positive. Next issue the following command: 'adb reboot bootloader'. This will place your device in fastboot mode. If you are very lucky a 'Ready' prompt will appear on the device below the word 'fastboot'. Most likely you will need to head to Windows Device Manager, identify which entry is associated with the tethered HDX and then change the device driver to 'Moto Composite' or something similar (might not have the wording exactly right). Once you get a 'Ready' prompt issue the following command: 'fastboot devices'. If you get a response similar to 'adb devices' then you are good to go.
Hints/tips:
- to help determine which entry(s) are associated with your HDX tether/untether your device while Windows Device Manager is open
- right click an entry to change the device driver; navigate 'Browse my computer ...' -> 'Let me pick ...'; do not choose any of the automated options
- if you can't get a Ready prompt and/or an response to 'fastboot devices' reboot both devices and try again
- if still no joy change USB ports and cables; the latter are especially problematic (people never believe that until trying 1821 other things - ugh!)
Report back and we'll go from there. I know you prefer the rest of your questions answered up front. Experience suggests an incremental approach is more productive - for you, me and future readers.
Davey126 said:
Second response is positive. Next issue the following command: 'adb reboot bootloader'. This will place your device in fastboot mode. If you are very lucky a 'Ready' prompt will appear on the device below the word 'fastboot'. Most likely you will need to head to Windows Device Manager, identify which entry is associated with the tethered HDX and then change the device driver to 'Moto Composite' or something similar (might not have the wording exactly right). Once you get a 'Ready' prompt issue the following command: 'fastboot devices'. If you get a response similar to 'adb devices' then you are good to go.
Hints/tips:
- to help determine which entry(s) are associated with your HDX tether/untether your device while Windows Device Manager is open
- right click an entry to change the device driver; navigate 'Browse my computer ...' -> 'Let me pick ...'; do not choose any of the automated options
- if you can't get a Ready prompt and/or an response to 'fastboot devices' reboot both devices and try again
- if still no joy change USB ports and cables; the latter are especially problematic (people never believe that until trying 1821 other things - ugh!)
Report back and we'll go from there. I know you prefer the rest of your questions answered up front. Experience suggests an incremental approach is more productive - for you, me and future readers.
Click to expand...
Click to collapse
Thank you! Now it says "ready" but I'm concerned about how to unplug it without messing anything up. here's the output:
Code:
Microsoft Windows [Version 10.0.16299.248]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\adb>adb reboot bootloader
C:\adb>fastboot devices
D0FBA0A0351401GB fastboot
C:\adb>
You are correct that I would prefer having all the answers upfront, but it's only so I can then question the answers to get a better understanding before messing with the device. A quick reply would be appreciated!
hwwof said:
Thank you! Now it says "ready" but I'm concerned about how to unplug it without messing anything up. here's the output:
{content removed}
You are correct that I would prefer having all the answers upfront, but it's only so I can then question the answers to get a better understanding before messing with the device. A quick reply would be appreciated!
Click to expand...
Click to collapse
Great!! The purpose of this exercise was to validate connectivity in two different modes and, if needed, provide a safe 'test' environment for remediation. No worries about breaking the tether if there is no active data transfer taking place. Simply unplug and then long press <power> until the device shuts down.
In response to your other questions:
Q: On step 6, do I follow the directions as they are quoted, or the ones on the original forum? If the later, does “change to the directory with the extracted dd.exe” mean to type the directory or something else? Also, a poster here stated that he got error message on the second 2 commands instead of the first, is the concerning at all? Should I take any precautionary measures?
A: Follow the steps as quoted
Q: Once step 9 is completed, can the kindle run as normal if I don’t flash anything? And what does it mean “get into the TWRP”? I’ll simply be in the recovery menu on the kindle? How do I flash my chosen ROM using TWRP?
A1: You should assume all content on your device will be erased following completion of Step #9 (although it will likely remain intact)
A2: The two files you will be 'flashing' with the dd command should be located in the same folder as "Minimal ADB and Fastboot"
A3: Deal with that later (flashing ROM)
Q: ROMs:
A: All of the Nougat based custom ROMs for HDX are stable and feature complete. Nuances are subtle and probably not worth worrying about now; you can always change later. My personal preference is AEX (AospExtended). That said, Lineage 14.1 and Slim 7 are both excellent alternatives.
Davey126 said:
Great!! The purpose of this exercise was to validate connectivity in two different modes and, if needed, provide a safe 'test' environment for remediation. No worries about breaking the tether if there is no active data transfer taking place. Simply unplug and then long press <power> until the device shuts down.
In response to your other questions:
Q: On step 6, do I follow the directions as they are quoted, or the ones on the original forum? If the later, does “change to the directory with the extracted dd.exe” mean to type the directory or something else? Also, a poster here stated that he got error message on the second 2 commands instead of the first, is the concerning at all? Should I take any precautionary measures?
A: Follow the steps as quoted
Q: Once step 9 is completed, can the kindle run as normal if I don’t flash anything? And what does it mean “get into the TWRP”? I’ll simply be in the recovery menu on the kindle? How do I flash my chosen ROM using TWRP?
A1: You should assume all content on your device will be erased following completion of Step #9 (although it will likely remain intact)
A2: The two files you will be 'flashing' with the dd command should be located in the same folder as "Minimal ADB and Fastboot"
A3: Deal with that later (flashing ROM)
Q: ROMs:
A: All of the Nougat based custom ROMs for HDX are stable and feature complete. Nuances are subtle and probably not worth worrying about now; you can always change later. My personal preference is AEX (AospExtended). That said, Lineage 14.1 and Slim 7 are both excellent alternatives.
Click to expand...
Click to collapse
So I completed the instructions, booted to TWRP, turned it off, booted up, did the unlock batch, but I didn't get "unlock code is correct". I got a lot of green lines "getvar slot-count...OK getvar:slot-suffixes...OK getvar:has-slot:unlock...OK getvarartition-type:unlock...OK getvar:max-download-size...[[0x20000000 ]] download:00000000..." Here's the cmd when I try running unlock.bat https://gyazo.com/a041dc49c786f9846d706c049eacbbf3
Did I mess something up or am I unlocked? I'm not sure what to do from here. I was still able to get back to TWRP. It's telling me to swipe to allow modifications or to keep read only. Where do I proceed from here? I'm reading in some places to wipe before installing, and a lot of other conflicting information. I downlaoded the AEX november build and would like to flash it. Do I have any need for rooting or SuperSU?
Again, Thank you so much for all your help
*deleted*
*deleted*
hwwof said:
So I completed the instructions, booted to TWRP, turned it off, booted up, did the unlock batch, but I didn't get "unlock code is correct". I got a lot of green lines "getvar slot-count...OK getvar:slot-suffixes...OK getvar:has-slot:unlock...OK getvarartition-type:unlock...OK getvar:max-download-size...[[0x20000000 ]] download:00000000..." Here's the cmd when I try running unlock.bat https://gyazo.com/a041dc49c786f9846d706c049eacbbf3
Did I mess something up or am I unlocked? I'm not sure what to do from here. I was still able to get back to TWRP. It's telling me to swipe to allow modifications or to keep read only. Where do I proceed from here? I'm reading in some places to wipe before installing, and a lot of other conflicting information. I downlaoded the AEX november build and would like to flash it. Do I have any need for rooting or SuperSU?
Again, Thank you so much for all your help
Click to expand...
Click to collapse
Device is NOT unlocked. Tied up for the next hour or two; will respond then. Do not wipe or attempt to flash anything. Sorry for wait ...
Davey126 said:
Device is NOT unlocked. Tied up for the next hour or two; will respond then. Do not wipe or attempt to flash anything. Sorry for wait ...
Click to expand...
Click to collapse
Thank you for being on top of this! I'm glad I was patient and didn't immediately try flashing anything. I'll try to wait up! I apologize if I fall asleep.
hwwof said:
Thank you for being on top of this! I'm glad I was patient and didn't immediately try flashing anything. I'll try to wait up! I apologize if I fall asleep.
Click to expand...
Click to collapse
Quick activity while you wait:
- boot into TWRP (power down; press <power>+<vol-up> for ~3 sec then release)
- swipe to allow modifications
- tap the backup option, select all partitions except cache, swipe to execute
- when complete tether device; should connect in adb mode
- from look for a new device/drive in Windows File Explorer
- click <device ID> -> Internal Storage; should see a folder named TWRP
- drag or right-click folder to a storage location on your Win 10 machine
- congrats! You have just made a backup of your device -and- placed a reserve copy on your Windows machine
Comment: prior to backing up you had completed the most risky tasks (stuff that could have yielded a soft/hard brick). It's all downhill from here. Will post more info on unlocking and installing a new ROM in a bit; real-life is calling . Fully understand if you need to sleep; post will be waiting in the morning. Penning this from Northeast USA; timezone UTC-5.
Davey126 said:
Quick activity while you wait:
- boot into TWRP (power down; press <power>+<vol-up> for ~3 sec then release)
- swipe to allow modifications
- tap the backup option, select all partitions except cache, swipe to execute
- when complete tether device; should connect in adb mode
- from look for a new device/drive in Windows File Explorer
- click <device ID> -> Internal Storage; should see a folder named TWRP
- drag or right-click folder to a storage location on your Win 10 machine
- congrats! You have just made a backup of your device -and- placed a reserve copy on your Windows machine
Comment: prior to backing up you had completed the most risky tasks (stuff that could have yielded a soft/hard brick). It's all downhill from here. Will post more info on unlocking and installing a new ROM in a bit; real-life is calling . Fully understand if you need to sleep; post will be waiting in the morning. Penning this from Northeast USA; timezone UTC-5.
Click to expand...
Click to collapse
I appreciate you so much! And I completely understand. I hope everything you're working on gets resolved!
I have backed it up as you suggested! Since the back-up is also on the internal drive, it will be deleted later, correct? It's 5gbs out of the already small storage space.
hwwof said:
I appreciate you so much! And I completely understand. I hope everything you're working on gets resolved!
I have backed it up as you suggested! Since the back-up is also on the internal drive, it will be deleted later, correct? It's 5gbs out of the already small storage space.
Click to expand...
Click to collapse
With the 5GB TWRP backup folder safely copied off-device you can delete the local copy at any time...although there is no immediate reason to do so.
Next step is to unlock the bootloader:
- verify 'get_code.bat' & 'unlock.bat' reside in the same folder as adb.exe and fastboot.exe
- look around to see if you have a file called 'unlock.code' from a previous run of 'get_code.bat'; if so place it in the same folder
- tether device and boot into fastboot (easiest way: boot into TWRP and then use reboot menu to boot the bootloader) [<--what an awkward sentence!]
- enter 'fastboot devices' to validate communication between host and device
- execute unlock.bat; if you get a green 'OK' the bootloader is unlocked!
- if not boot into FireOS (get past unlock screen), tether, verify adb communication is working and then run 'get_code.bat' to (re)create the 'unlock.code' file
- repeat steps 2-4 (above)
If that doesn't work and/or you are unable to boot into TWRP then a bit of extra work will be needed to generate a valid unlock code. Brief outline:
- download legacy Fire Nexus ROM from here (it does NOT require an unlocked bootloader)
- tether device and into TWRP
- from Windows copy downloaded ROM to a folder on the device (suggest creating a new folder with your initials as the name)
- from the TWRP main menu tap Wipe then swipe to perform a 'factory reset'
- from the TWRP main menu tap Install
- navigate to the folder where you stored the downloaded ROM
- select the ROM zip and then click to install
- when complete allow the device to restart; after a 3-5 min it should boot into Fire Nexus; skip the Google config (not needed)
- enable developer options and adb bridge
- tether device and verify adb connectivity
- run 'get_code.bat' to generate a fresh unlock.code file
I will be traveling much of Sunday with irregular network access. I'll try to respond to an questions/problems as time permits. Apologies in advance for any delays.
Davey126 said:
With the 5GB TWRP backup folder safely copied off-device you can delete the local copy at any time...although there is no immediate reason to do so.
Next step is to unlock the bootloader:
- verify 'get_code.bat' & 'unlock.bat' reside in the same folder as adb.exe and fastboot.exe
- look around to see if you have a file called 'unlock.code' from a previous run of 'get_code.bat'; if so place it in the same folder
- tether device and boot into fastboot (easiest way: boot into TWRP and then use reboot menu to boot the bootloader) [<--what an awkward sentence!]
- enter 'fastboot devices' to validate communication between host and device
- execute unlock.bat; if you get a green 'OK' the bootloader is unlocked!
- if not boot into FireOS (get past unlock screen), tether, verify adb communication is working and then run 'get_code.bat' to (re)create the 'unlock.code' file
- repeat steps 2-4 (above)
If that doesn't work and/or you are unable to boot into TWRP then a bit of extra work will be needed to generate a valid unlock code. Brief outline:
- download legacy Fire Nexus ROM from here (it does NOT require an unlocked bootloader)
- tether device and into TWRP
- from Windows copy downloaded ROM to a folder on the device (suggest creating a new folder with your initials as the name)
- from the TWRP main menu tap Wipe then swipe to perform a 'factory reset'
- from the TWRP main menu tap Install
- navigate to the folder where you stored the downloaded ROM
- select the ROM zip and then click to install
- when complete allow the device to restart; after a 3-5 min it should boot into Fire Nexus; skip the Google config (not needed)
- enable developer options and adb bridge
- tether device and verify adb connectivity
- run 'get_code.bat' to generate a fresh unlock.code file
I will be traveling much of Sunday with irregular network access. I'll try to respond to an questions/problems as time permits. Apologies in advance for any delays.
Click to expand...
Click to collapse
Welp, device won't boot into FireOS. It boots straight to Fastboot. I tried Installing nexus ROM but I got "can't install this package over newer build updater process ended with error:7".
hwwof said:
Welp, device won't boot into FireOS. It boots straight to Fastboot. I tried Installing nexus ROM but I got "can't install this package over newer build updater process ended with error:7".
Click to expand...
Click to collapse
Error 7 is pretty generic and can be due to a conflict between install package and TWRP or an issue with the system partition. It's a solvable issue without too much work. They the following in the order listed.
1) In TWRP tap wipe -> advanced. Tick system, data, dalvik and cache; leave internal storage unticked. Tap the appropriate button to execute. Return to main menu and reboot back into recovery. Then try to install the Nexus ROM.
2) Download an older build of TWRP from here and transfer to adb/fastboot folder on Windows. Boot device into fastboot mode and issue the following command to install:
sudo fastboot -i 0x1949 flash recovery <recovery-image>
Will check back in 5-6 hours on progress.
Davey126 said:
Error 7 is pretty generic and can be due to a conflict between install package and TWRP or an issue with the system partition. It's a solvable issue without too much work. They the following in the order listed.
1) In TWRP tap wipe -> advanced. Tick system, data, dalvik and cache; leave internal storage unticked. Tap the appropriate button to execute. Return to main menu and reboot back into recovery. Then try to install the Nexus ROM.
2) Download an older build of TWRP from here and transfer to adb/fastboot folder on Windows. Boot device into fastboot mode and issue the following command to install:
sudo fastboot -i 0x1949 flash recovery <recovery-image>
Will check back in 5-6 hours on progress.
Click to expand...
Click to collapse
First one didn't work, second one put this out:
C:\adb>sudo fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
'sudo' is not recognized as an internal or external command,
operable program or batch file.
hwwof said:
First one didn't work, second one put this out:
C:\adb>sudo fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
'sudo' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Drop the sudo prefix ...
Davey126 said:
Drop the sudo prefix ...
Click to expand...
Click to collapse
"
C:\adb>fastboot devices
D0FBA0A0351401GB fastboot
C:\adb>fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
target reported max download size of 536870912 bytes
sending 'recovery' (9220 KB)...
OKAY [ 0.361s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.424s
C:\adb>
"
hwwof said:
"
C:\adb>fastboot devices
D0FBA0A0351401GB fastboot
C:\adb>fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
target reported max download size of 536870912 bytes
sending 'recovery' (9220 KB)...
OKAY [ 0.361s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.424s
C:\adb>
"
Click to expand...
Click to collapse
This suggest the vulnerable bootloader was not properly installed. You will probably need to repeat the installation procedure from the point of placing the device in 'bulk' mode. Be sure to pay attention to file indexes and file identifiers that follow "if=".
@draxie - would you agree with this assessment? Poster is following this guide and using the files attached to that post.
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...
Not sure if this is the proper place for this question; if not, please move. I picked up an Irulu Expro No. X9 Android tablet on eBay. It seems to work fine, except I can't get past the login screen. I tried many times the various key combinations to get it into recovery mode but none worked. Other suggestions had me putting it in debug mode first, but how to do that if you can't get logged in? I'm not concerned about saving any data, I would just like to be able to use it. I would appreciate any help to solve my problem. Thanx.
@jrockow
Have you ever tried to check whether the device is accessable by means of ADB?
Code:
adb devices
If it's accessable then you easily can remove the password lock. You do this by launching Android Settings via ADB as shown next:
Code:
adb devices
adb shell am start -a android.settings.SETTINGS
jwoegerbauer said:
@jrockow
Have you ever tried to check whether the device is accessable by means of ADB?
Code:
adb devices
If it's accessable then you easily can remove the password lock. You do this by launching Android Settings via ADB as shown next:
Code:
adb devices
adb shell am start -a android.settings.SETTINGS
Click to expand...
Click to collapse
Thanx for your quick reply.
adb devices doesn't list anything.
I thought you needed to enable USB debugging for ADB to work?
Don't know how to do that if I can't log in.
jrockow said:
Thanx for your quick reply.
adb devices doesn't list anything.
I thought you needed to enable USB debugging for ADB to work?
Don't know how to do that if I can't log in.
Click to expand...
Click to collapse
OK, so I'm somewhat of a rookie when it comes to ADB and FASTBOOT.
I'm not sure I have everything correct. I'm using an app called "Minimal ADB and Fastboot".
I have another tablet, same as the one I can't access, and I have turned on the developer options.
Even with that, I still can't see any devices when I run ADB.
FYI: When I look at devices in my PC it shows up as X9, which I believe is correct.
With my no password tablet, I can actually see all the directories of my Android on my PC.
If I try that with the other one don't see any directories.
jrockow said:
With my no password tablet, I can actually see all the directories of my Android on my PC.
Click to expand...
Click to collapse
Android's USB in that case is set to MTP mode, not ADB mode. MTP operates at the file level. Your Android device doesn’t expose its entire storage device to Windows computer. Instead, when you connect a device to your computer, the computer queries the device and the device responds with a list of files and directories it offers.
When Andoid's USB is in ADB mode, device can completely get controlled from Windows computer.
jrockow said:
I'm using an app called "Minimal ADB and Fastboot".
Click to expand...
Click to collapse
Serious Android device owners use the USB-driver ( AKA ADB ) as provided by device's OEM/Carrier.
jwoegerbauer said:
Android's USB in that case is set to MTP mode, not ADB mode. MTP operates at the file level. Your Android device doesn’t expose its entire storage device to Windows computer. Instead, when you connect a device to your computer, the computer queries the device and the device responds with a list of files and directories it offers.
When Andoid's USB is in ADB mode, device can completely get controlled from Windows computer.
Serious Android device owners use the USB-driver ( AKA ADB ) as provided by device's OEM/Carrier.
Click to expand...
Click to collapse
I was incorrect in my earlier post, when I said I turned on the developer mode on my "good" tablet and I still couldn't access it thru ADB.
I found out I really didn't have it turned on, and when I did I was able to execute the ADB commands.
That gets me back to my earlier post about not being able to turn on the developer mode on my "bad" tablet if I can't log in.
I would think with all the guys working on this stuff someone has come up with a way to get around a lost password?
I remind you, I tried the power+volume sequence many times, many ways, so I need a different approach; if there is one?
Thanx.
@jrockow
Because the tablet can't connect with PC via ADB then wondering why you don't contact seller of the tablet? Unlock Screen Password always can be done with Google Account Android device initially was bound to.
jwoegerbauer said:
@jrockow
Because the tablet can't connect with PC via ADB then wondering why you don't contact seller of the tablet? Unlock Screen Password always can be done with Google Account Android device initially was bound to.
Click to expand...
Click to collapse
I have already reached out to the seller. However, he knows nothing of the history of the tablet. He's just a guy who collects tons of electronics and sells them on eBay.
What really frustrates me is I can quite easily get my "good" tablet to enter recovery mode with the power+vol combination. I have tried many, many times to duplicate the same combo on the "bad" tablet and it just jumps over the recovery mode and boots to the logon screen.
Is it possible someone made some change to the tablet that won't allow it to go into recovery?
jrockow said:
I have already reached out to the seller. However, he knows nothing of the history of the tablet. He's just a guy who collects tons of electronics and sells them on eBay.
What really frustrates me is I can quite easily get my "good" tablet to enter recovery mode with the power+vol combination. I have tried many, many times to duplicate the same combo on the "bad" tablet and it just jumps over the recovery mode and boots to the logon screen.
Is it possible someone made some change to the tablet that won't allow it to go into recovery?
Click to expand...
Click to collapse
So, I've come to the conclusion that what I'm asking for just can't be done.
Can't enter reset with any key combo I've tried; can't use ADB because debugging not on; can't go to Google because I don't know who owned the phone before me.
If this were a PC device, there are multiple apps available to get around a lost password. I've done it many times.
I was really hoping there would be some Android genius out there who could help.
What a shame to realize that a perfectly good working device might as well be thrown in the trash.
jrockow said:
So, I've come to the conclusion that what I'm asking for just can't be done.
Can't enter reset with any key combo I've tried; can't use ADB because debugging not on; can't go to Google because I don't know who owned the phone before me.
If this were a PC device, there are multiple apps available to get around a lost password. I've done it many times.
I was really hoping there would be some Android genius out there who could help.
What a shame to realize that a perfectly good working device might as well be thrown in the trash.
Click to expand...
Click to collapse
If you know that the phone basically supports ADB, if the phone has a slot for external SD-card, if you can boot into Recovery Mode, if the Recovery Mode allows you to "apply update from sd-card" then you by means of an OTA can enable USB-debugging, then you can access the phone via ADB.
Currently I'm working on such an UPDATE.ZIP and will, if it's bug free, it publish here on XDA.
Personally don't own a phone what supports ADB: it's a HUAWEI Y7 2019. If you are willing to become a tester let me know it. I'll then PM you the link to the UPDATE.ZIP.
jwoegerbauer said:
If you know that the phone basically supports ADB, if the phone has a slot for external SD-card, if you can boot into Recovery Mode, if the Recovery Mode allows you to "apply update from sd-card" then you by means of an OTA can enable USB-debugging, then you can access the phone via ADB.
Currently I'm working on such an UPDATE.ZIP and will, if it's bug free, it publish here on XDA.
Personally don't own a phone what supports ADB: it's a HUAWEI Y7 2019. If you are willing to become a tester let me know it. I'll then PM you the link to the UPDATE.ZIP.
Click to expand...
Click to collapse
If I could boot into Recovery Mode my problem would be solved.
Hello everyone.
I've got Samsung Galaxy s9+ and I forgot the pattern. I would like to unlock it without losing the data, what is important for me is the photos and videos. I've tried every method on youtube but unfortunately none is working. I bought several programs like Dr.Fone and 4ukey but they don't support this model. Is there anyway to unlock it without Factory Reset? I'm willing to pay for this.
Thank you
If you can get it into fastboot, you can copy the files to your pc using adb and some commands.
Look for a tutorial on this
PhotonIce said:
If you can get it into fastboot, you can copy the files to your pc using adb and some commands.
Look for a tutorial on this
Click to expand...
Click to collapse
Thank you for your reply. is fastboot same as recovery mood? sorry but I'm so noob in tech
Get the android studio adb tools zip, unzip it. Install fastboot and normal drivers for your phone. Enter adb, plug in your phone using a data cable. Now, type adb devices. Boot your phone into recovery mode first, your device should show up. If it doesn't, then once in recovery mode, there should be an option to enter fastboot. Select that. If your device still won't appear, try entering download mode (I think download mode is the one you should try first).
Once your device appears in the adb command window, google the command for copying files using adb. Use this command to copy all the files to either an sd card inserted in the phone, or directly onto your pc (if possible).
If none of this is working out for you, and you are willing to pay, take it to a data recovery shop/centre. They should be able to extract the data from the device at a reasonable price.
PhotonIce said:
Get the android studio adb tools zip, unzip it. Install fastboot and normal drivers for your phone. Enter adb, plug in your phone using a data cable. Now, type adb devices. Boot your phone into recovery mode first, your device should show up. If it doesn't, then once in recovery mode, there should be an option to enter fastboot. Select that. If your device still won't appear, try entering download mode (I think download mode is the one you should try first).
Once your device appears in the adb command window, google the command for copying files using adb. Use this command to copy all the files to either an sd card inserted in the phone, or directly onto your pc (if possible).
If none of this is working out for you, and you are willing to pay, take it to a data recovery shop/centre. They should be able to extract the data from the device at a reasonable price.
Click to expand...
Click to collapse
I'm speechless for your kind help. I'll try to do all these steps.
I tried to search for "android studio adb tools" but I can't find it's download link. Sorry, but can you please to share me download link for the zip file, I'll really appreciate that so much, then I'll follow your steps.
I took the phone to several phone shops but they couldn't do it. They just telling me they can factory reset which I can do it but I don't want to lose the photos and videos.
Once again, Thank you so much
Here's the link, (sorry, its called platform tools not adb tools, my bad).
Downloading Platform Tools…
Get the Platform Tools to discharge the ADB and fastboot commands that permit the users to perform several incredible benefits and unlock the system settings
magiskupdate.com
Try taking the phone to a data recovery shop, instead of some regular phone/repair shop.
pickasfu said:
Hello everyone.
I've got Samsung Galaxy s9+ and I forgot the pattern. I would like to unlock it without losing the data, what is important for me is the photos and videos. I've tried every method on youtube but unfortunately none is working. I bought several programs like Dr.Fone and 4ukey but they don't support this model. Is there anyway to unlock it without Factory Reset? I'm willing to pay for this.
Thank you
Click to expand...
Click to collapse
Doesn't the S9+ have a fingerpritn reader though? Just use that to unlock it..
PhotonIce said:
Here's the link, (sorry, its called platform tools not adb tools, my bad).
Downloading Platform Tools…
Get the Platform Tools to discharge the ADB and fastboot commands that permit the users to perform several incredible benefits and unlock the system settings
magiskupdate.com
Try taking the phone to a data recovery shop, instead of some regular phone/repair shop.
Click to expand...
Click to collapse
Thank you for your reply. I'll try this method and let's hope it will success, I'll keep you updated.
===
There are several data recovery shops I contacted after your advice, but unfortunately they deal with laptops, external memory cards and hard drives.
PhotonIce said:
Doesn't the S9+ have a fingerpritn reader though? Just use that to unlock it..
Click to expand...
Click to collapse
It does. But if device restarted you are forced to enter the pattern or the password and there will be no option for fingerprints.
PhotonIce said:
Get the android studio adb tools zip, unzip it. Install fastboot and normal drivers for your phone. Enter adb, plug in your phone using a data cable. Now, type adb devices. Boot your phone into recovery mode first, your device should show up. If it doesn't, then once in recovery mode, there should be an option to enter fastboot. Select that. If your device still won't appear, try entering download mode (I think download mode is the one you should try first).
Once your device appears in the adb command window, google the command for copying files using adb. Use this command to copy all the files to either an sd card inserted in the phone, or directly onto your pc (if possible).
If none of this is working out for you, and you are willing to pay, take it to a data recovery shop/centre. They should be able to extract the data from the device at a reasonable price.
Click to expand...
Click to collapse
Hi,
I downloaded the platform tools and I unzipped it, I installed Samsung dex and the drivers for on the PC, when I plugin the cable I can see there is Galaxy S9+ driver but it's empty because the phone is locked. When I try to open adb.exe it's not doing anything. all the exe doesn't work except sqlite3.exe. Attached is the screen
Is it possible for you to help me via teamviewr? If it success I would pay you. Even if it's not success I'll pay you. I don't mind to pay upfront, Thank you for your help sir