Hi All,
I have a mediapad X2 that I would like to root. The first step in all the guides is to obviously unlock the bootloader.
I went through the Huawei page, and also emailed Huawei, and both returned the same 16-digit unlock code. Great right? Not quite.
The Setup:
1.) ADB and Fastboot BOTH detect the phone just fine and "adb setup 1.42" drivers are installed. No issues here
2.) I Did try on 3 different windows machines (One Desktop, 2 laptops)
3.) I Did try on different USB ports
4.) USB Debugging is enabled
5.) I tried the following root methods. ALL HAVE FAILED (varying behavior and error messages)
Chainfire
Super-Root
Towel Root
RootGenius
iRoot (warning: This installs a CRAPLOAD of malware and spyware) and it worked to root the X1 I had but not the X2
6.) The phone had not previously been tampered with, or rooted in any way. The bootloader still shows "PHONE LOCKED"
7.) Build Number: GEM-703LV100R001C233B013
The Issue:
I keep getting the following error:
Without specifying the code:
C:\Users\BPCS\Desktop\root>fastboot oem unlock
...
FAILED (status malformed (1 bytes))
finished. total time: 0.016s
Click to expand...
Click to collapse
With specifying the code
C:\Windows\system32>fastboot oem unlock <code_removed_for_privacy_but_typed_here>
...
FAILED (remote: password wrong)
finished. total time: 0.016s
Click to expand...
Click to collapse
Can someone please help?
Use Official-Unlock-Bootloader-by-Alkalinorap-v4 from.....
https://www.dropbox.com/s/68me4nwh0boktsr/Official-Unlock-Bootloader-by-Alkalinorap-v4.zip?dl=0
shassouneh said:
Hi All,
I have a mediapad X2 that I would like to root. The first step in all the guides is to obviously unlock the bootloader.
I went through the Huawei page, and also emailed Huawei, and both returned the same 16-digit unlock code. Great right? Not quite.
The Setup:
1.) ADB and Fastboot BOTH detect the phone just fine and "adb setup 1.42" drivers are installed. No issues here
2.) I Did try on 3 different windows machines (One Desktop, 2 laptops)
3.) I Did try on different USB ports
4.) USB Debugging is enabled
5.) I tried the following root methods. ALL HAVE FAILED (varying behavior and error messages)
Chainfire
Super-Root
Towel Root
RootGenius
iRoot (warning: This installs a CRAPLOAD of malware and spyware) and it worked to root the X1 I had but not the X2
6.) The phone had not previously been tampered with, or rooted in any way. The bootloader still shows "PHONE LOCKED"
7.) Build Number: GEM-703LV100R001C233B013
The Issue:
I keep getting the following error:
Without specifying the code:
With specifying the code
Can someone please help?
Click to expand...
Click to collapse
I forgot to ask, what system are you on? B012 or B013?
My phone stopped working all of a sudden, and when I restarted it entered the fast boot mode iteratively.
If I select recovery or normal boot, or whatever it says the same msg, "recovery image not valid".
The phone was unrooted, so I thought of rooting it.
I dont remember the status of usb debugging in my phone was on/off, now no chance to check it either.
But i could run the commands from the cmd to get the unlock data code, as well i received the code from Motorola to unlock.
When I tried the fastboot oem unlock (20 digit Unlock code)
I used to get a reply: Unlock data invalid!
Failed (failed remotely)
And some time info of time ~10s.
I also ran the getvar all command & noted the cid= 0x0007 (I dont remember count of 0's but ending was 7 which I found the device is unlockable)
I live in India & the device is not network restricted and I have bought it from flipkart.com which was sole retailer of Moto devices in India.
Can someone plz help....
Thanks,
Swapneel
XDA Visitor said:
My phone stopped working all of a sudden, and when I restarted it entered the fast boot mode iteratively.
If I select recovery or normal boot, or whatever it says the same msg, "recovery image not valid".
The phone was unrooted, so I thought of rooting it.
I dont remember the status of usb debugging in my phone was on/off, now no chance to check it either.
But i could run the commands from the cmd to get the unlock data code, as well i received the code from Motorola to unlock.
When I tried the fastboot oem unlock (20 digit Unlock code)
I used to get a reply: Unlock data invalid!
Failed (failed remotely)
And some time info of time ~10s.
I also ran the getvar all command & noted the cid= 0x0007 (I dont remember count of 0's but ending was 7 which I found the device is unlockable)
I live in India & the device is not network restricted and I have bought it from flipkart.com which was sole retailer of Moto devices in India.
Can someone plz help....
Thanks,
Swapneel
Click to expand...
Click to collapse
Hello,
You may register for a XDA account so that we could help you move this thread to right Q&A section in order to get expertise help.
-Vatsal
I have a thread going on all ready but cannot add to post. I have a Huawei Y6 Pro (locked) but I have (FRP Unlocked) via Developers Options. This is a phone I bough from ebay/china. I would like to throw in that the phone was supposed to be the "Huawei Enjoy-7, but the Y6 Pro is what they sent me and it is unlocked. How am I sure it is a Y6 you may question, well I checked it in settings/about phone.
Here is the link so you know what the phone is.
https://www.ebay.com/itm/HUAWEI-Enjoy-7-Unlocked-5-0-inch-2GB-16GB-Android-7-0-Quad-Core-4G-Smartphone/202146351761?hash=item2f10dc8a91:m:m_vN-35KH1iZuchUqi7_dpA
I need to have the phone "unlocked". It was supposed to be if u look at stats but I got the shaft of china here and it upsets me for I have never been ripped from there yet till now. Seller is of no help but with a run around. Huawei support does have a site to "unlock" but there has to be a flaw in their page for I can not get it to show me a unlock code. I can get to "fastboot" via a terminal via windows. But until I get a unlock code I can do nothing.
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
3UQBB17B08504698 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock 123456781234
5678
...
FAILED (remote: Invalid key,unlock fail, error num: 8)
finished. total time: 0.218s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock 3UQBB17B0850
4698
...
FAILED (remote: Invalid key,unlock fail, error num: 8)
finished. total time: 0.234s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Does anyone have any suggestions on how to unlock the phone. I will remind that Huawei gives no help on a unlock code and this phone is legit, no bad IMEI number verified.
In Developers Options, have you enabled, OEM Unlock and USB Debugging ?
Oscar Martin said:
In Developers Options, have you enabled, OEM Unlock and USB Debugging ?
Click to expand...
Click to collapse
Oscar, Yes that is correct as you ask.
Not Unlocked but [Closed]
Shipper decided this morn to issue me a PrePaid Shipping Label for a "full refund"
Per what Huawei told me this model can No Longer be Unlocked. I'm tried of trying to blow my brain out on this anymore. So that is that and be aware of the seller on ebay please. I went thru alot to get a refund.
Hi there, is there any way to put Pixel 3 in emergency download mode?
For now I have: 1 hard-bricked out-of-warranty Pixel 3 in disassembly state, locked bootloader and not working (really, not working) recovery. RMA is not an option (not based in any Google Store or support) countries, only hardcore.
For now I've tried to put phone in EDL via cable (D+ on GND, D- on GND), but it seems not an option. On PCB there are no marks, so, are here any people, who were successful in putting Pixel 3 in 9008 or so?
Thanks in advance, and sorry for my bad english.
llorephie said:
Hi there, is there any way to put Pixel 3 in emergency download mode?
For now I have: 1 hard-bricked out-of-warranty Pixel 3 in disassembly state, locked bootloader and not working (really, not working) recovery. RMA is not an option (not based in any Google Store or support) countries, only hardcore.
For now I've tried to put phone in EDL via cable (D+ on GND, D- on GND), but it seems not an option. On PCB there are no marks, so, are here any people, who were successful in putting Pixel 3 in 9008 or so?
Thanks in advance, and sorry for my bad english.
Click to expand...
Click to collapse
what happens to the phone can u boot up in fadtboot mode?
jalado said:
what happens to the phone can u boot up in fadtboot mode?
Click to expand...
Click to collapse
Fastboot available, but useless: bootloader in locked state.
that doesn't matter. is it just a boot loop then? that's an easy fix
---------- Post added at 03:00 PM ---------- Previous post was at 02:58 PM ----------
jalado said:
that doesn't matter. is it just a boot loop then? that's an easy fix
Click to expand...
Click to collapse
all a locked bootloader does is open the authentication for cooked ROMs. you can install a regular factory image to restore your phone
jalado said:
that doesn't matter. is it just a boot loop then? that's an easy fix
---------- Post added at 03:00 PM ---------- Previous post was at 02:58 PM ----------
all a locked bootloader does is open the authentication for cooked ROMs. you can install a regular factory image to restore your phone
Click to expand...
Click to collapse
Disclaimer: sorry for broken links, newbie on this forum, so remove whitespaces.
I can't do it, any downloaded for blueline from here: https: //devel opers.google. com/android/images
Causes:
Code:
Sending 'bootloader_b' (8521 KB) OKAY [ 0.340s]
Writing 'bootloader_b' FAILED (remote: 'Fastboot command (flash:) is not allowed when locked')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.015s]
Finished. Total time: 0.065s
Sending 'radio_b' (71404 KB) OKAY [ 2.057s]
Writing 'radio_b' FAILED (remote: 'Fastboot command (flash:) is not allowed when locked')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.012s]
Finished. Total time: 0.062s
--------------------------------------------
Bootloader Version...: b1c1-0.2-5672671
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 891X0497G
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.056s]
Checking 'version-bootloader' OKAY [ 0.052s]
Checking 'version-baseband' OKAY [ 0.052s]
Setting current slot to 'b' FAILED (remote: 'Fastboot command (set_active:) is not allowed when locked')
fastboot: error: Command failed
Bootloader photo: https: //i. im gur. com/r4PSb7z.png
Trying to reach OS or recovery: https: //i. im gur. com/Te9nswf.png
Also I've tried to reach 9008 Emergency download by this instruction: https ://forum .gsmdevelopers. com/hardware-cable-modification-tricks/10684-guides-qualcomm-edl-cable-9008-com-9008-xiaomi-lg-etc.html
But it looks like not an option for this phone, or maybe there is different combo.
Also I've found D+ and D- USB-C testpoints on motherboard under screen connector (photo of mb: https: //i. im gur. com/NGEKO54.png), but shorting on GND looks like not working. 5 testpoints cluster on top-left corner looks like modem, but I don't sure.
RMA is not an option: https: //i. im gur. com/2XKUwC9.png
Mail-in starting from 411$ + mail out of RU around 100$, new phone available in ~250$. So, any suggestions?
llorephie said:
Disclaimer: sorry for broken links, newbie on this forum, so remove whitespaces.
I can't do it, any downloaded for blueline from here: https: //devel opers.google. com/android/images
Causes:
Code:
Sending 'bootloader_b' (8521 KB) OKAY [ 0.340s]
Writing 'bootloader_b' FAILED (remote: 'Fastboot command (flash:) is not allowed when locked')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.015s]
Finished. Total time: 0.065s
Sending 'radio_b' (71404 KB) OKAY [ 2.057s]
Writing 'radio_b' FAILED (remote: 'Fastboot command (flash:) is not allowed when locked')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.012s]
Finished. Total time: 0.062s
--------------------------------------------
Bootloader Version...: b1c1-0.2-5672671
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 891X0497G
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.056s]
Checking 'version-bootloader' OKAY [ 0.052s]
Checking 'version-baseband' OKAY [ 0.052s]
Setting current slot to 'b' FAILED (remote: 'Fastboot command (set_active:) is not allowed when locked')
fastboot: error: Command failed
Bootloader photo: https: //i. im gur. com/r4PSb7z.png
Trying to reach OS or recovery: https: //i. im gur. com/Te9nswf.png
Also I've tried to reach 9008 Emergency download by this instruction: https ://forum .gsmdevelopers. com/hardware-cable-modification-tricks/10684-guides-qualcomm-edl-cable-9008-com-9008-xiaomi-lg-etc.html
But it looks like not an option for this phone, or maybe there is different combo.
Also I've found D+ and D- USB-C testpoints on motherboard under screen connector (photo of mb: https: //i. im gur. com/NGEKO54.png), but shorting on GND looks like not working. 5 testpoints cluster on top-left corner looks like modem, but I don't sure.
RMA is not an option: https: //i. im gur. com/2XKUwC9.png
Mail-in starting from 411$ + mail out of RU around 100$, new phone available in ~250$. So, any suggestions?
Click to expand...
Click to collapse
what about side loading it?
new phone is a good idea
jalado said:
what about side loading it?
new phone is a good idea
Click to expand...
Click to collapse
He said recovery is not working. Device is toast sadly.
Did you get the UFS chip corrupted somehow? Seems like your only way is to do blow the UFS chip off and reimage it somehow, or get a working chip to replace it... Good luck
Hi !
I think I know what happened to you because something very similar happened to me ( bootlooping for nothing while I was in android 10 , and I had like a 1/4 chance to not get bootlooped in FASTBOOT mode )
Try this video :
https://youtu.be/zQmK5KwN5dk
Yea it's pixel 2 but it works the same as pixel 3 , just do this with your files step by step and maybe it can work, use the 2nd method of the video ( which is the harder one but it worked for me ) , good luck mate!
Tool all in one. download. flash factory image.
zhtlancer said:
Did you get the UFS chip corrupted somehow? Seems like your only way is to do blow the UFS chip off and reimage it somehow, or get a working chip to replace it... Good luck
Click to expand...
Click to collapse
I don't think it's corrupted, but it needs to be reflashed in boot partition. Currently trying to find any programmator(flasher, hw flash tool, something about, I'm not very good in english) and util for it. Maybe I will have luck with this option.
Dexcellium said:
Hi !
I think I know what happened to you because something very similar happened to me ( bootlooping for nothing while I was in android 10 , and I had like a 1/4 chance to not get bootlooped in FASTBOOT mode )
Try this video :
https://youtu.be/zQmK5KwN5dk
Yea it's pixel 2 but it works the same as pixel 3 , just do this with your files step by step and maybe it can work, use the 2nd method of the video ( which is the harder one but it worked for me ) , good luck mate!
Click to expand...
Click to collapse
Sorry, but one more time: bootloader is locked, so I need to go deeper. Please, re-read entry condition for this thread.
bmw9651 said:
Tool all in one. download. flash factory image.
Click to expand...
Click to collapse
Err... What?
Btw, looks like it is first recovery thread for Pixel 3 in out-of-warranty state, currently I'm trying to find some options to get emergency download, or something else. Looking forward for any other suggestions, and, of course, if I will kinda lucky, will post own solution
llorephie said:
Hi there, is there any way to put Pixel 3 in emergency download mode?
For now I have: 1 hard-bricked out-of-warranty Pixel 3 in disassembly state, locked bootloader and not working (really, not working) recovery. RMA is not an option (not based in any Google Store or support) countries, only hardcore.
For now I've tried to put phone in EDL via cable (D+ on GND, D- on GND), but it seems not an option. On PCB there are no marks, so, are here any people, who were successful in putting Pixel 3 in 9008 or so?
Thanks in advance, and sorry for my bad english.
Click to expand...
Click to collapse
Same problem here, hows the update of your device?
rzhr999 said:
Same problem here, hows the update of your device?
Click to expand...
Click to collapse
Bought new phone
Hi,
Trying to install Lineage on my old pixel 2.
The phone was bought directly from Google. When in Fastboot mode, it says on the screen that the boot loader is locked. When I run "fastboot flashing unlock" in a shell from a connected Mac, is says:
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
So I went into the settings on the phone and the OEM unlocking option is greyed out and says "Connect to the internet or contact your carrier". It is connected to the internet, however.
Thanks for any help,
A
Same problem here. Does anyone have a solution?
Same problem too. Hard reset is supposed to solve this.... but not for me. oem unlocking option is ungreyed then , but unlocking bootloader is still impossible.
Have you connected to the Internet with the device?
Try dialing this: *#*#CHECKIN#*#* (*#*#2432546#*#*), you should get a notification that says "checkin successful" or something like that. If OEM unlocking is still greyed out, reboot the phone and check again.
V0latyle said:
Have you connected to the Internet with the device?
Try dialing this: *#*#CHECKIN#*#* (*#*#2432546#*#*), you should get a notification that says "checkin successful" or something like that. If OEM unlocking is still greyed out, reboot the phone and check again.
Click to expand...
Click to collapse
Still having problems even after doing this.
Goe11 said:
Still having problems even after doing this.
Click to expand...
Click to collapse
I don't have any other suggestions, then.
When the device connects to the internet, it's supposed to check the IMEI against a whitelist to determine whether OEM unlocking is allowed. If it doesn't do this, it's possible that the device is either defective, or is actually a carrier branded device. The latter is more likely with older phones like the Pixel 2 that have been out of production for quite some time.