These are some hopefully simple instructions to unlock the bootloader for this phone. There are many instructions sets about but none make it particularly easy, or explain how to use DC Unlocker. Everything I know is in this post, asking me questions you probably won't get any more information, but I'll help if I can.
Download and install / unzip
Android Platform Tools https://developer.android.com/studio/releases/platform-tools
HiSuite https://consumer.huawei.com/en/support/hisuite/
USB drivers (I think you need these) https://www.getdroidtips.com/android-usb-drivers-for-windows-and-mac/
You might need Huawei_Mobile_Driver (not really sure but I installed it) https://androidfilehost.com/?fid=4349826312261774199
{Mod edit}
If it doesn't work read some other guides for software you might need. I tried all sorts of things.
Plug phone into computer using USB3 cord. I used a USB3 socket on my Windows 10 PC.
Run DC Unlocker. Select "Huawei Phones" top left then leave it at autodetect - don't select your phone. Follow the instructions to type *#*#2846579#*#* into the dialer then select 'ProjectMenu' -> 'Background settings' -> 'USB ports settings' -> 'Manufacture mode' then hit close. Go back in and check "manufacturer mode" is still set.
In DC unlocker, hit the magnifying glass button to search for your phone. Make sure the pane below says it finds the phone. If not try again a few times, then reboot the phone, reboot the computer, try a few times. The DC Unlocker software doesn't seem very reliable. It should look something like the screenshot below. If you get "server not found" or similar wait, or try again, or reboot.
{
"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"
}
Next hit "server" and enter your user and password and hit "check login". It should come up with your credits. If it says "server error" or similar try a dozen times before rebooting both phone and PC and trying again. If it still doesn't work post on the DC unlocker forums and they might help you.
Next hit "unlocking" on the top right. Hit the "read bootloader code" button to get the bootloader unlock code. Hit it until it gives you the code. DO NOT hit the other buttons unless you really need to. I hit the wrong one and had to pay an extra 4 euro to try again.
Save that Bootloader code somewhere you won't lose it! Emailing it to yourself might be a good way to do that.
Open a powershell window in the same folder as you unzipped the Android platform tools. adb.exe should be in that folder. Type the following commands in
adb reboot bootloader
(wait for the phone / hit ok if required)
fastboot oem unlock yourcodehere
Once you've done this the phone will factory reset. Next step for me another day will be install TWRP and LineageOS. If I find a good method I might post that.
@commandonz Thread has been moved out of development as your thread doesn't qualify for that section. For further information, please refer to the sticked threads in the sections.
Additionally, I've removed the references to paid services from your OP. Paid services are not compliant with the XDA Forum Rules especially rules no. 11 and 13.
Regards
Oswald Boelcke
Senior Moderator
Ok thanks Oswald. I'll post it somewhere else.
Related
I'm trying to flash a new ROM and can't get past the USPL stage
I run the 'uspl_116_jockyw.bat' and pause it on the "start MTTY [or whatever] or RUU" and I then try to the run the ROMUpdateUtilitiy.exe.
All goes well, but at 100%, it says "Image file is corrupt" and then that's it, it restarts.
I've tried different versions of the file with no success
Is it to do with my Application unlock? When I run that is says something along the lines of "SDA [or phone] is not unlockable" but I click unlock, and it instantly says "unlock successful"
At the moment I've only been able to install Opera. WIFIRouter and Messenger won't install.
Thanks
first unlock with the sda unlock. then flash uspl. run rom update utility.exe. after that run flash.exe on whichever rom it is that u wish to flash. if this doesnt work, do a hard reset and repeat all the steps. 100% it will work. when u get to the final prompt asking u to start mtty or whatever, dont press any key to continue the process. instead run ruu.exe. itll work
So is it normal for the Application Unlock utility to say "This device is not unlockable" [or something along those lines].
I can't install any programs on the deivce either. It says they don't have the correct permissions. Is that not what the app unlocker is meant to do?
EDIT:
OK, so this is what I am doing:
1) hard reset the phone [hold soft keys, turn on, press end etc]
2) connect to ActiveSync
3) Run SDA_ApplicationUnlock.exe
{
"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) I click OK and it claims to have unlocked.
5) remove SD card and turn phone off then on.
6) Run uspl_116_jockyw.bat. I hit enter a few times,my phone then asks me to confirm running an app. It does this twice, the last being harat.exe. Screen goes black with Tux the Penguin.
I halt on this screen [Ignore the error - I screen capped this on a later attempt without hard reset]
I then run ROMUpdateUtility.exe check the boxes, and click next etc. It goes to RGB bars, then a grey screen with a progress bar. The bar gets to 100% then I get this error
and the phone resets?
What am I doing wrong?
Any help is appreciate. I can't stand the Orange crippled ROM.
Thanks
Right HERE is the solution for any Orange SPV e650 users wanting to unlock and flash.
These 3 files are crucial:
MoDaCo_SPV_E650_de_Brand___Fix_Pack.PREP.CAB
MoDaCo_SPV_E650_de_Brand___Fix_Pack_0.5.CAB
RemoveSecurity.CAB
Only once those have been run can you follow the steps found on the wiki page.
Thanks to everyone who works on these ROMs. It's is simply awesome the work you do.
I salute you!
So I have a small problem that has giving me a headache the past few days. I got an old Nokia 6.1 from my mom & was asked to get the pictures & documents from it. I removed her pattern lock, because I was annoyed to use it all the time. A couple of days later, the phone has out of the blue a security pin. Which obviously no one knows, because no one configured it...
I spent hours looking different ways to extract the data or to bypass the lock & sofar I think I ran out of all the options.
Here is my current state & I would really appreciate some advice how to proceed.
1. Find my device:
The phone is on the list. But it shows that the last activity was on the 10th january & can't be reached it even though it's connected to the internet via my mobile data. Furthermore it seems that I wouldn't be able to unlock it anyways because it only gives me two options "Call the Phone" & "Set up secure & delete".
2. Installing Aroma to extract the data/remove lock files:
I can't do that because there is no custom recovery installed on the phone. Just the stock.
3. Installing a custom recovery:
I can't install/flash anything on the phone because the developer options, usb debugging & bootloader are not unlocked/enabled.
I came as far as being able to see my dive with adb on my pc, but I couldn't flash anything of it, because the signature fails.
I'm now posting this threar, to see if anybody has some advice for me, how I could get the pictures from the phone.
Thank you all in advance~
Push
The door to any Android device is ADB.
You say
came as far as being able to see my dive with adb on my pc,
Click to expand...
Click to collapse
hence ADB obviously is fullly working, means it should be possible to pull out the data in question by means of ADB.
Hi, thank you for your answer, I have expressed myself wrong/mixed adb & fastboot up. What I wanted to say, is that I can see the device via fastboot. Unfortunately not over adb.
{
"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"
}
as you can also see in the screen
If I understood what I read, there is no way to access the phone like this, is that correct?
Is there anything else I can do?
The Phone itself gives me an option to "Apply Update from ADB". My knowledge about this stuff is barely anything. But is there a way for example I could install/update an android version/new system without losing the internal data? At that point I don't care about the phone working properly, as I would like to get the pictures from it & root + wipe everything from it.
push
As "Apply Update from ADB" implies this option is used to flash an OS's update provided by OEM/carrier: updating an OS doesn't affect user data stored on phone.
Have you ever tried to exit phone's fastboot mode by running Fastboot commands
Code:
fastboot devices
fastboot reboot
I ended up factory resetting the phone. This Thread can be closed
If you have usb debugging on. Then you can use ADB. You can try to mount user partition and you can copy that partition.
Hi All,
I bought a ROG phone 5s (ZS676KS) direct from ASUS and I've been trying to root it all week. The firmware version is WW_18.1220.2111.160.
So far, I have been able to unlock the bootloader using Asus' app. My phone displays the unlocked bootloader warning on every boot.
I can't make fastboot work... the "adb reboot bootloader" command does work. I can also boot using the power + volume up button. But the "fastboot devices" command always comes up empty.
I found two possible reasons why fastboot doesn't work. So far I failed to fix either one.
First, the "OEM unlocking" option is missing in my developer options menu. I have the "USB debugging" option checked off. But many of the guides I read online say to allow OEM unlocking and I can't do that. But I've also seen people say that it doesn't matter. So, I don't know if this is a real problem. I can't find any reference to this problem except in Samsung phones. I tried the recommended fix but it didn't work.
Second, something's wrong with the fastboot driver on my computer. When get my phone into fastboot mode and plug it into the computer, device manager shows a device called "ASUS_I005D" with an orange caution icon on it. The error message in the properties menu says "The drivers for this device are not installed. (code 28)". This is probably the real problem.
{
"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"
}
Windows isn't finding a driver with its online driver search. I spent a few hours playing with Windows drivers to no avail. But maybe I missed something. I did find "ASUS_Android_USB_drivers_for_Windows_20150212" online and it didn't help.
I have tried different wires and USB ports and I'm using the side port of the phone instead of the bottom (although I tried the bottom port too). I tried another computer and that didn't work. But this was before I realized what was happening with windows drivers so I didn't check the device manager. I'm away from home now so I just have access to the one computer for now.
Does anyone know where I can find the correct driver? Or is there another approach I haven't considered? I hope there's nothing fundamentally wrong with the phone. I kind of just bought it without explicitly verifying, assuming the 5s is rootable since the 5 is...
Thanks Everybody,
Success is disgusted by some people, and will not share any files for free in the future.
It's not your device but likely Win 10 playing games with you. First completely uninstall the device driver to clean things up. Reboot your pc into Safe Mode. Plug in your phone from the side connector with a good data capable USB cable. From Device Manager choose "Add Legacy Hardware" from the menu and point the location to where you have saved the latest official Android USB drivers and install. Reboot Windows normally. If things have gone well, you should be able to both ADB & Fastboot into your device.
What a relief.
I am now able to flash my patched boot.img.
Thanks to both of you. I'm off to the races...
For me I just get a Ubuntu iso, boot your computer off a USB stick, install adb and fastboot via apt, and boom, no crappy drivers needed
Hi!
This is my first post here, I hope I won't make many mistakes and troubles...
A friend of mine asked me to help him with his car Android based mirror.
The mirror is a "4G Adas Mirror" which is now stucked on the boot screen/logo.
Android version on the device is 8.1.
I've tried to reset through the hard reset button, without success.
I tried to connect the device on my PC to try to get access with adb, no success.
Adb cant see the device, the device list is empty.
When I check in the device manager on my PC I can see under "Portable Devices" installed,
with the name "MTP USB Device".
I also downloaded several drivers but can't install them, not for my device.
And now I'm out of ideas.
If somebody have any idea what could I still try to bring back the device into live, I would really appreciate.
Thank you.
Btw.:
My PC is running win10 x64 Pro
You're probably stuck with only the MTP interface (and not a composite device with MTP and ADB) but it might be worthwhile to double check.
Is the MTP interface active? Can you see any files in Windows File Explorer?
You can check with UsbView.exe to see if there is only one interface, the MTP.
The next step is to try various buttons on boot to see if you can get to recovery, fastboot or ROM bootloader.
Thanks for the fast replay, I cant access the device throug any file manager, as you mentioned, I checked with UsbView.exe already, just to be sure.
The MTP is active.
I've tried many many times the switch combination with the reset button, to try to get into any recovery or whatever cmd line mode, but without success.
The device hase only two buttons:
1. Power button
2. Reset button
{
"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"
}
Well, there's many ways to skin a cat.
If you open it up there could be a UART with a rooted hardware console.
There could be pushbuttons or test points to get into some other mode.
Good photos will tell us.
So, here we are....
the mirror crashed until I tried to open it.
However, if somebody is interested to hack and poke around this device, I'm familiar to open the device,
make schematics, pictures and try to hack into the device to try to make it alive again.
If somebody is willing to be a part to this pls. let me know and let's get started.
Open it up and take photos.
I'm trying and searching for a way how to open it but not fully crack the mirror, which is actually also a monitor...
I hope I will open the device soo and be back...
Hey all,
after trying to flash images from a private build
[
1) REPO: repo init -u https://android.googlesource.com/platform/manifest -b android-13.0.0_r11
2) LUNCH: aosp_cheetah-userdebug
3) fastboot flashall -w for the out directory
]
the Pixel was stuck on a boot loop, showing the google screen but nothing more.
after battery drained, tried to put it on fastboot mode, unsucessfully
right now, the device is in this state, with black screen showing nothing.
{
"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"
}
Does someone know what tools are needed to save the device and guide to do it?
and second question - something in the process I described above is wrong about the flashing that caused it to fail?
Wow...where to begin...?!
I completely don't know to what end you were attempting to get to or how you were trying to get there, but looking at such an unconventional method of flashing and unconventional "private build" (so I assume not the full factory images Google publishes on their dev page), I wouldn't be surprised if you didn't permanently brick your device -- especially considering the outcome is a weird "USB Serial Device" and black screen/no fastboot mode...
But what I suggest is powering on using the button combination (I believe it is PWR & VOL+Down), sometimes it takes 1-2+ minutes holding it down.
I would suggest correcting the driver, but I'm unsure if that will lead anywhere if you cannot get into fastboot mode and/or the screen stays black. But, if you think it will help; download the Google USB Drivers (can be found HERE), unzip it, uninstall (and MOST IMPORTANTLY tick the box that says delete the driver software if it pops up) the "USB Serial Device", Scan for New Hardware, if the new driver does not identify as "Android Bootloader Interface" then -- right click the new driver -- click update driver -- and either Browse to the folder where you unzipped the Google USB Drivers or manually "Let Me Pick from available drivers" and manually select the .inf file to install the driver as. That should correct your driver issue, though I don't know how helpful it will be without the screen or being able to get into fastboot mode...
And, if you don't want to risk breaking your P7P, I would suggest from now on sticking with traditional methods of flashing (platform tools or recovery mode) and Google Full Factory Images or established ROMs....
Or maybe research considerably more in the unconventional method you are trying to attempt...
Good luck to you, seems you will need it...
it's basically flashing from here
Pixel Phones as Development Platforms | Android Open Source Project
source.android.com
which I assumed will be no problems
I have tried the combinations to fastboot, but unsuccessfully, all I see is black screen.
thanks for reply.