Does anyone know how to troubleshoot fastboot oem get_unlock_data just hanging and returning nothing?
Aside from not starting with a clean Windows install, I've followed Explorer 4x4's methodology many times but cannot progress. Here's a dump of details that may help:
Windows 8.1
- removed all old and/or non-present devices from Device Manager, leaving:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- installed Android Studio
Fastboot:
ADB:
BL:
Code:
MBM-3.0-uefi-ae87908-180903
Baseband:
Code:
M660_04.07.01.46.02R EVERT_APACDSDS_CUST
Product/Variant:
Code:
evert XT1926-5 64GB PVT1
Console [NULL]:
Code:
null
Tools Mode Config:
Code:
DISABLED
Hopefully you have figured this out by now but if not I will help you with your device.
Hello.
Thanks for your offer to help. Unfortunately no the issue is ongoing. Have not unlocked the bootloader.
It seems the 'oem' function(s) in fastboot may be exactly that - down to the OEM to supply and ensure they work. Perhaps so much so that 'fastboot oem' is actually a command sent directly to the phone and if the function called, in this case get_unlock_data does not return anything, it's just black hole.
Anyway, if there's something I can do to absolutely ensure I'm starting from scratch, that might be helpful. I'm thinking something along the lines of that net command in Windows that resets the whole network stack at a low level, but in the context of adb and so forth. I've installed and uninstalled and reinstalled all the bits and pieces so many times, it doesn't seem to be doing the trick.
That or perhaps I could try a Linux live environment? Is there ADB, fastboot binaries for Linux?
Related
Hello, this a quick guide on how to get adb and fastboot working from anywhere in command promt. You might ask why this is useful? Well if you set your system up like this, you can use adb and fastboot from practically anywhere. This is very convenient and saves you having to navigate to your SDK every time you want to do something with your phone. So let's get started!
Prerequisites:
Windows 7 or Windows 8
Java JDK downloaded and installed.
Android SDK, preferred location:
Code:
C:\AndroidSDK
See note
First, right click My Computer and select Properties. From there, select Advanced system settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then, select Environment Variables
You will now get a box that looks like this. Select edit, here is the important part.
Do NOT delete any of the text in the field, simply add:
Code:
C:\AndroidSDK\platform-tools;C:\AndroidSDK\tools
to the end of the text field, like this
Note: This assumes that your Android SDK, tools and platform-tools folders are setup in the same directory as mine, if not please modify the path accordingly
After you've edited the text field, press okay, then okay again and voila. Finished!
From now on, whenever you need to use adb or fastboot simply open command prompt and type away
If you have any comments or suggestions, please feel free to leave a reply below
I would like to revert the firmware on an Asus Zenfone 3 Max (ZC520TL) to a previous one (13.1.4.43).
With the current firmware (13.1.4.69) I have PIN and fingerprint issues.
-I tried to go back to 13.1.4.43 using Asus Flash Tool but it does not allow going back.
-I tried to go back thru the Recovery but I got a security error …does not allow to go back
-I try using ADB but it does not show when sending command "adb devices" even though I installed drivers (ADB, MPT, etc.) and it does shows in the Control Panel when the phone is ON.
Also sent the command "adb reboot bootloader" the phone reboots into bootloader/fastboot mode but still does not allow to go back to previews firmware.
Device Manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What exactly is the security error you get when you try to flash that firmware in recovery? You tried flashing this file (US version) from the Asus website through stock recovery? You should be able to do it through recovery, but you may need to edit the updater-script file as mentioned here in part 1, steps 2-4.
EDIT: Looks like you won't be able to use fastboot to flash images unless your bootloader is unlocked. Is yours?
Reboot to EDL mode from FASTBOOT!
No more Test Point Method needed
Technical Details:
Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the command line and refuses to sent the command to the device. Since FastBoot command protocol is simple and text-based, it is enough to send a packet containing "reboot-edl" text over USB. The simplest way to do that is to patch Windows fastboot.exe file, replacing "reboot-bootloader" text with "reboot-edl". As "reboot-bootloader" string is found in the command line, fastboot.exe sends the same constant string to the device. So if "reboot-bootloader" is replaced with "reboot-edl", you can specify "reboot-edl" in the command line and the same text will be sent to the device.
New Update: Fastboot updated to latest version.
Tutorial:
1. Download the Fastboot_to_EDL from : https://www.mediafire.com/file/yr7csyo64e97vbu/Fastboot_to_EDL.zip/file
2. Extract the zip in your desktop
3. Open the folder and double Click on Reboot.bat
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Reboot your device to Fastboot Mode by pressing
Vol Down + Power button and connect your device with PC and Press Enter.
5. Your Device will be rebooted to EDL!
6. Now flash your Fastboot Rom with Mi Flash Tool to Unbrick your Mi Note 3.
Proof:
saved my ass
thanks a lot ahmed.....
i bricked my phone.. went to flash twrp without unlocking bootloader and it bricked..
this tool saved the phone else mom was gonna whoop my ass..
peace:good:
Can anyone tell me the best firmware that's available for my head unit Latest Firmware MCU (K2001_NWD_S212109) Preferable Rooted or am i on the latest version possible for this unit at the moment?
I have pulled hardware info and will show screenshots of my findings, i would like to root this unit so i can get to the whitelist file to allow tasker to work via a fast boot, i have tried multiple different things to get root on this device
All the software APK methods they all fail
i Trying to do it via the pc ADB method but no luck there Even though i get toADB no issues i cannot get to SU I'm stuck in User
Also trying to reach the bootloader i run the command in ADB "adb reboot recovery" it reboots successfully goes to recovery but does not give me the usual menu says something about command then takes me out of the bootloader
couple of things iv tried to work around on this car stereo is, i downloaded shortcuts to accessibility, security menus as they are stripped out i can get to Services option if i go to accessibility shortcut and lets me enable power optimization but that's had no effect on the quick boot start up, and when i attempt to access the security menu it drops me back to the home screen obviously don't have permissions to get there
Does anyone have one of these devices that they have successfully rooted or changed the firmware to allow root i hate being locked in a rom that gives me no options to customize my headhunt,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi!
I have Software- and Hardware experience, but not so Android-specific and none Huawei-specific.
A friend asked me to recover the data of a CAN-L11 stuck in a bootloop. (Stock Android 6 EMUI 4.1, OEM locked, build date Fri Nov 18 14:27:21 CST 2016)
My first thought was dumping the eMMC through SDIO - in hindsight I am so glad I didn't go this route as it would be stuck decrypting cryptfs.
I went the EDL route, dumped everything including the userdata-footer (so much easier&faster than direct SDIO).
Now I don't know how to move forward - have some questions in my head:
How to get the Masterkey from the TPM using EDL? Is that feasible? Is there an easier way? I know the PIN.
When is the TPM and userdata cleared? When I flash a signed ROM through EDL? When I flash a UPDATE.APP through fastboot? I found a stock UPDATE.APP on the internet with EMUI 4.1 for CAN-L11 - seems not to be exactly the same as currently flashed though.
Any other ideas?
If someone is interested - the knowledge I have gathered until now:
EDL-Pins for CAN-L11:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDL-Software for Linux: https://github.com/bkerler/edl
Paper about Android encryption: https://www.sciencedirect.com/science/article/pii/S266628172100007X
Regarding ISP/SDIO - mostly from a previous S4 mini recover:
the CMD-Pin seems to always have a Pull-Up
the Raspberry Pi has a unused SDIO-Port which worked flawlessly; my SD-Card-Reader attempt failed
https://www.riverloopsecurity.com/blog/2020/03/hw-101-emmc/
Thanks in advance!
Thomas131