Hello all,
First of all I looked for a (sub) forum for the P10 Lite, but I can't seem to find it. If a admin/mod thinks this post should be placed elsewhere, feel free to move it.
Ok, now on to the problem I'm having with my P10 Lite (WAS-LX1A model)...
The phone is running the stock B102 firmware, I've unlocked the bootloader with the code I got from Huawei, installed TWRP and rooted the phone, all was working just fine.
Then, last saturday (June 24, 2017) there was an OTA update to B131 available, tried to install it but it failed (nothing was installed btw, it never got to then point where the OTA did anything, phone would just reboot).
So after some searching and in a lapse of judgement I decided to (re)lock the bootloader thinking that was what kept the update from installing (command: sudo fastboot oem relock <code>).
And that's where my problem gets in.
Now I have a phone which only can only get into:
1.) Huawei eRecovery: Only options I have in eRecovery are: "Download latest version and recovery", "Reboot" and "Shutdown". No option to reset to factory or anything like that. "Download latest version and recovery" fails everytime, stating: "Failed to get package info from server". Gave my phone a static DHCP lease and even put it in DMZ on the router (just in case NAT/firewall was interfering), but that didn't help at all. Rebooting or shutdown will just put the phone back into eRecovery as soon as it's booted.
2.) Emergency/EDL: This is the mode where you're supposed to put the firmware you want to flash in the "dload" folder on sd-card. Tried that too, but it gets to about 5% and fails (tried B120, B123 and B131 update files, none work). When the phone gets into this mode it's also available to ADB. However, something seems to have changed dramaticly as I no longer seem to have any permissions on the phone. "adb devices" shows my phone but it also says "unauthorised". As soon as I try to do anything that requires root priviledges (like: "adb root" or "adb shell") I get an error stating: "This adb server's $ADB_VENDOR_KEYS is not set". Clearly that means there's an issue regarding the .pub keys on client/host side not being the same. Since I cannot pull anything from, or push anything to, my phone I don't know how I can fix this... And since I'm getting this message on the same machine that I used to flash TWRP on the phone earlier (which worked just fine), it seems to me this problem exists on the phone-side.
3.) Fastboot & rescue: fastboot finds my phone just fine, yet it flatout refuses all meaningful commands (only basic commands like reboot work) with the error: "FAILED (remote: Command not allowed)". Some searching tells me this is because the bootloader is locked and that's exactly what my phone shows on it's screen when it's in fastboot mode: "PHONE Relocked" and "FRP Lock". However fastboot command: "fastboot oem get-bootinfo" returns: "(bootloader) unlocked". This confuses me, a lot; if the bootloader is unlocked then what is preventing me from flashing anything? Trying to unlock the bootloader again through fastboot (fastboot oem unlock <code> / fastboot oem unlock "<code>") gives the "FAILED (remote: Command not allowed)" error. Trying to lock the bootloader again (fastboot oem relock <code> / fastboot oem relock "<code>") gives error: "FAILED (remote: stat not match)". Obviously I cannot flash anything from fastboot anymore.
Tried all I can think of on 2 linux machines and 1 Windows 7 machine, all 64-bit, allthough 1 of the linux machine is multi-architecture so it runs 32-bit too (not related to this issue, needed 32-bit for WINE). This just to rule out an issue with my machine. All 3 machines act exactly the same though which makes me (strongly) believe the issue resides on the phone.
Trying to recovery in HiSuite (newest version) doesn't work either, it just tells my my phone isn't supported, even though it does detect my phone when it's in fastboot mode.
Nothing has been flashed, so this is not a case of a flash gone wrong, it just looks like I'm locked out of my own phone and for the life of me I cannot figure out how to get back in. And there's no way to boot into system anymore, so I cannot check/change "OEM Unlock" and "ADB Debugging" settings in the phone developers options
.
Any help/advice would be greatly appreciated! I'm stuck, Huawei customer service only tells me to do a factory reset, which I can't, and when I tell them that's not possible all becomes awfully quiet on their end (they don't respond to my mails anymore). I simply can't think of anything I could try to fix this, spend the last 5 days searching the web but nothing seems to work. Maybe some Android-guru's have some suggestions (I'm certainly open to suggestions! ).
Thanks in advance.
Info:
- phone: Hauwei P10 Lite, model: WAS-LX1A, firmware: WAS-LX1AC432B102
- (main) laptop: HP Probook running Arch linux (64bit), uname: "Linux probook 4.11.6-3-ARCH #1 SMP PREEMPT Thu Jun 22 12:21:46 CEST 2017 x86_64 GNU/Linux".
- Android SDK version 26. Package named: "aur/android-sdk-platform-tools r26.0.0-1 (1155, 9.20)" Which can be found on Arch's AUR. (I am aware I need to run fastboot as "sudo", fastboot cannot do anything without sudo priviledges).
Edit: Tried some fastboot commands with regards to "FRP Unlock", command: "sudo fastboot oem frp-unlock" returns: "FAILED (remote: oem_frp_check_password failed! Error = -1)" not sure what password is required here to be honest and "sudo fastboot oem frp-erase" returns: "FAILED (remote: Command not allowed!)".
OTA update didn't install because of custom recovery, not because bootloader was unlocked. You can unlock bootloader again and try again.. Dload for some reason won't work anymore on newer firmwares.. At the end you can always restore phone with DC-Phoenix tool, just flash stock firmware you had on the phone.
MobileTechArena said:
OTA update didn't install because of custom recovery, not because bootloader was unlocked. You can unlock bootloader again and try again.. Dload for some reason won't work anymore on newer firmwares.. At the end you can always restore phone with <snip> cannot post URL's yet <snip> tool, just flash stock firmware you had on the phone.
Click to expand...
Click to collapse
Thank you, MobileTechArena, for your time/effort,
That's what I thought regarding bootloader/recovery, however I thought of it too late.
Unlocking to bootloader again doesn't work (command: sudo fastboot oem unlock "16-digit-code"), I get the "FAILED (remote: Command not allowed)" error. Tried it with bootloader code as a string, and as "code". Both don't work, on the same machine I used previously to unlock the bootloader in the first place. The unlocking working but after giving the relock command everything seems to get blocked, even though "sudo fastboot oem get-bootinfo" still tells me the bootloader is unlocked.
With regards to DC-Unlocker, I don't have a stock B102 firmware, it simply cannot be found anywhere online. I managed to get a full TWRP backup of the B102 firmware from some helpful people on this site (on someone else's thread), but seeing as how I'm no longer able to boot into TWRP, I don't think that TWRP backup is going to do me any good. Oldest firmware I can find online is B120, which is newer than the firmware on my phone.
Read somewhere on Huawei Q&A section that they removed the "dload" method because of security risks, so yeah that method is DOA. Really sad they did this, feels like that could've saved me.
Also gave Huawei's Fastboot erase tool (version: 1006) a try. It detects my phone just fine but it cannot unlock FRP. If I use the tool to erase FRP it reboots the phone -> fails. doesn't make any changes.
Am I right in thinking it's Huawei's FRP that's preventing fastboot/adb commands?
GuessThisIsMe said:
Thank you, MobileTechArena, for your time/effort,
That's what I thought regarding bootloader/recovery, however I thought of it too late.
Unlocking to bootloader again doesn't work (command: sudo fastboot oem unlock "16-digit-code"), I get the "FAILED (remote: Command not allowed)" error. Tried it with bootloader code as a string, and as "code". Both don't work, on the same machine I used previously to unlock the bootloader in the first place. The unlocking working but after giving the relock command everything seems to get blocked, even though "sudo fastboot oem get-bootinfo" still tells me the bootloader is unlocked.
With regards to DC-Unlocker, I don't have a stock B102 firmware, it simply cannot be found anywhere online. I managed to get a full TWRP backup of the B102 firmware from some helpful people on this site (on someone else's thread), but seeing as how I'm no longer able to boot into TWRP, I don't think that TWRP backup is going to do me any good. Oldest firmware I can find online is B120, which is newer than the firmware on my phone.
Read somewhere on Huawei Q&A section that they removed the "dload" method because of security risks, so yeah that method is DOA. Really sad they did this, feels like that could've saved me.
Also gave Huawei's Fastboot erase tool (version: 1006) a try. It detects my phone just fine but it cannot unlock FRP. If I use the tool to erase FRP it reboots the phone -> fails. doesn't make any changes.
Am I right in thinking it's Huawei's FRP that's preventing fastboot/adb commands?
Click to expand...
Click to collapse
I think it is because of locked FRP, you can still try with DC-Phoenix with newer firmware. I had the same problem on P8 Lite 2017, Couldn't find B106 that i had on the phone anywhere, but successfully flashed B110.
EDIT: also check under filelist of the firmware that firmware for sure is for your region.
MobileTechArena said:
I think it is because of locked FRP, you can still try with DC-Phoenix with newer firmware. I had the same problem on P8 Lite 2017, Couldn't find B106 that i had on the phone anywhere, but successfully flashed B110.
EDIT: also check under filelist of the firmware that firmware for sure is for your region.
Click to expand...
Click to collapse
Thank you for the info, shall have another look at the firmware (or more precisely, it's region). It's the EU version I'll need that much I know.
Also did some looking into why Huawei's eRecovery isn't working, so I turned on my Kali Linux machine and did some 'wiresharking'.
Seems eRecovery is looking for something at ip: 54.229.89.249.
A Whois query shows this ip belongs to Amazon's AWS.
However, pinging the IP shows that it's not online, so no wonder why eRecovery isn't working (nice one Huawei! ).
GuessThisIsMe said:
Thank you for the info, shall have another look at the firmware (or more precisely, it's region). It's the EU version I'll need that much I know.
Also did some looking into why Huawei's eRecovery isn't working, so I turned on my Kali Linux machine and did some 'wiresharking'.
Seems eRecovery is looking for something at ip: 54.229.89.249.
A Whois query shows this ip belongs to Amazon's AWS.
However, pinging the IP shows that it's not online, so no wonder why eRecovery isn't working (nice one Huawei! ).
Click to expand...
Click to collapse
Yes, if it's eu then eu firmware is what you need. As for the eRecovery i have no idea why its looking for something on that ip. Huawei definitely need's to make restoring devices simpler.
---------- Post added at 09:36 PM ---------- Previous post was at 09:19 PM ----------
Can you connect device with HiSuite in fastboot mode? You could use this REDLOTUS tool to bypass eRecovery and flash firmware.
MobileTechArena said:
Yes, if it's eu then eu firmware is what you need. As for the eRecovery i have no idea why its looking for something on that ip. Huawei definitely need's to make restoring devices simpler.
---------- Post added at 09:36 PM ---------- Previous post was at 09:19 PM ----------
Can you connect device with HiSuite in fastboot mode? You could use this <snip> tool to bypass eRecovery and flash firmware.
Click to expand...
Click to collapse
Ok, l did get the right firmware (EU region), so that wasn't the issue.
Tried the REDLOTUS tool (thanks for that link btw, seems like a promising project), but alas it doesn't seem to work for me.
Got node js/npm installed just fine, it works, manages to get the firmware and everything, listens for HiSuite and manages to point HiSuite to local host to look for firmware there (like it should according to REDLOTUS' Readme).
Unfortunately, HiSuite doesn't give me the option to update firmware, only the systemrecovery button isn't greyed out, and systemrecovery tells me my device isn't supported. I can see on my phone's screen "rescue mode enter..." when I select systemrecovery in HiSuite, but nothing else happens.
Seems like REDLOTUS might work for me once the author manages to get it to work with eRecovery instead of HiSuite (apparantly that's being worked on atm).
hi i'm from france and i have exactly the same problem as you
the only difference is that i've "PHONE Unlocked" and "FRP Unlock" but not all of the fastboot commands works
i'm trying just right now to flash BOOT.img, RECOVERY.img and SYSTEM.img
hope it will work, sorry for my bad english
Radnaksi98 said:
hi i'm from france and i have exactly the same problem as you
the only difference is that i've "PHONE Unlocked" and "FRP Unlock" but not all of the fastboot commands works
i'm trying just right now to flash BOOT.img, RECOVERY.img and SYSTEM.img
hope it will work, sorry for my bad english
Click to expand...
Click to collapse
If your phone reads "PHONE Unlocked" and "FRP Unlock", then lucky for you, you don't have anything near my problem.
First of, if you do a: 'fastboot devices' command, does it show your phone?
Can you tell me if the following commands work, and what they return?
- fastboot oem get-bootinfo
- fastboot oem get-lock-state
- fastboot oem lock-state info
If you run Linux you'll need to "sudo" the fastboot commands.
You have enabled ADB-debugging on the phone right?
Edit: Can you still get into the stock recovery? To get there first turn the phone completely off. Then hold Volume Down (-) and Power buttons till you see the Huawei logo, then release both buttons. From stock recovery you could try a factory reset (DO NOT DO THIS IF YOU HAVE TWRP INSTALLED!!!).
hi, the phone shows me "FRP Unlock", but when i've done all the commands u gave me and there's an FB Lockstate on: LOCKED
Idk what it is
EDIT: ADB-debugging isn't enabled because i can't boot the phone, and when it started to bootloop that was when i've unlocked the bootloader and someone told me to factory reset the phone, so i think the ADB-debugging isn't enabled anymore
EDIT2: Stock recovery is working
does anyone have a twrp backup for the p10 lite ? it would be faster ....
oh and i have installed the revolution recovery, now i have the mtp and adb functionning, adb shell too, but i still cannot mount /data or /system
looks like /data is empty and unmoutable idk what to do
i can't change fs or wipe the partition pls help
Radnaksi98 said:
does anyone have a twrp backup for the p10 lite ? it would be faster ....
oh and i have installed the revolution recovery, now i have the mtp and adb functionning, adb shell too, but i still cannot mount /data or /system
looks like /data is empty and unmoutable idk what to do
i can't change fs or wipe the partition pls help
Click to expand...
Click to collapse
You can find a full TWRP backup of the B102 firmware in the thread called -> Root p10 "lite" , on page 11 user: stefanwe92 posted a link to it.
Good luck!
Thank you for answering me !
But i've the LX1A, so can i use it ?
Radnaksi98 said:
Thank you for answering me !
But i've the LX1A, so can i use it ?
Click to expand...
Click to collapse
Did/does it have a firmware like: WAS-LX1AC432B102? (the C432 is the important part). If so, then yes you should be fine.
Now beware I base this solely on the fact that there isn't any firmware on HWMT's site for the WAS-LX1C*, only for the WAS-LX1AC*. Google "hwmt" and have a look for yourself (it's in russian, so Google translate will definately help).
If you want to be absolutely sure, I'd suggest contacting user "stefanwe92", he has the phone and has uploaded the firmware, so he should be able to give you the information you need.
I wish I could've tried the TWRP myself, but my phone refuses to load the bootloader, so I can't :crying:
GuessThisIsMe said:
Did/does it have a firmware like: WAS-LX1AC432B102? (the C432 is the important part). If so, then yes you should be fine.
Now beware I base this solely on the fact that there isn't any firmware on HWMT's site for the WAS-LX1C*, only for the WAS-LX1AC*. Google "hwmt" and have a look for yourself (it's in russian, so Google translate will definately help).
If you want to be absolutely sure, I'd suggest contacting user "stefanwe92", he has the phone and has uploaded the firmware, so he should be able to give you the information you need.
I wish I could've tried the TWRP myself, but my phone refuses to load the bootloader, so I can't :crying:
Click to expand...
Click to collapse
I don't really know, on the box it's written WAS-LX1A
But i'm gonna make a backup first with twrp (yes i've successfully unbricked the phone by myself ! It work by half but man it Was hard ! I will try to makes a tutorial for you in french as soon as i can because it's hard for me to speak in english lol, so use a translator !) and then flash the backup you gave me !
I will do this tomorrow because it's late in France and it took me an entier afternoon to semi-unbrick this phone ^^
I will contact you tomorrow with good news i hope !
Radnaksi98 said:
I don't really know, on the box it's written WAS-LX1A
But i'm gonna make a backup first with twrp (yes i've successfully unbricked the phone by myself ! It work by half but man it Was hard ! I will try to makes a tutorial for you in french as soon as i can because it's hard for me to speak in english lol, so use a translator !) and then flash the backup you gave me !
I will do this tomorrow because it's late in France and it took me an entier afternoon to semi-unbrick this phone ^^
I will contact you tomorrow with good news i hope !
Click to expand...
Click to collapse
command: "fastboot oem get-build-number" should tell you exactly which firmware your phone is running.
Congrats on your success!
Regarding your English, it seems just fine to me, I understand you well. And for sure it's better than my French (dropped that subject as quickly as I could in high school ).
Hope to hear from you soon, with a working phone!
Sleep well, btw I live in the same timezone as you (I'm Dutch).
Phone has been brought back to life with the excellent help from the DC-Unlocker team.
MobileTechArena was absolutely right, only DC-Phoenix can save you in a circumstance such as the one I found myself in.
15 bucks well spent, can definately recommend it!!!
Problem solved
GuessThisIsMe said:
Phone has been brought back to life with the excellent help from the DC-Unlocker team.
MobileTechArena was absolutely right, only DC-Phoenix can save you in a circumstance such as the one I found myself in.
15 bucks well spent, can definately recommend it!!!
Problem solved
Click to expand...
Click to collapse
I fixed my bootloop that lasted for almost an month with help of MobileTechArena without DC-Phoenix so I guess we both gonna thank him :laugh:
Carkai said:
I fixed my bootloop that lasted for almost an month with help of MobileTechArena without DC-Phoenix so I guess we both gonna thank him :laugh:
Click to expand...
Click to collapse
Agreed!
Nice people those Irish, some of them like their whiskey a bit too much , but all of the Irish folk I've met in my life have been nothing but kind human beings.
Knew one Irish lad who thought nothing of starting to drink at 8 in the morning, I tell you the drive back home was very interesting (and not at all dangerous :silly.
Radnaksi98 said:
does anyone have a twrp backup for the p10 lite ? it would be faster ....
oh and i have installed the revolution recovery, now i have the mtp and adb functionning, adb shell too, but i still cannot mount /data or /system
looks like /data is empty and unmoutable idk what to do
i can't change fs or wipe the partition pls help
Click to expand...
Click to collapse
I have a identical problem... my phone is stuck in "Huawei eRecovery" screen. Same situation that you had reported (connection fail).
I found a solution to enter in FASTBOOT & RESCUE MODE and i posted in:
https://forum.xda-developers.com/general/general/solution-huawei-p10-lite-alternative-to-t3637311
I also have a TWRP backup... but my problem started when i used it to restore my phone. So i believe that it will not help you. But if you want I can send it to you. My model is a WAS-LX1A (Portugal).
Have you found a solution to your problem?
Related
My phone connects fine with adb. I tooted with towelroot, i have the D415 (see screenshot) i have run the commands on a pc several time with no errors. I tried it with my terminal emulator severaIm times and it says "decixe not found) HAHHA its just funny to me. I want to unlock this bootloader i even tried a factory cable (for kindle and only once) no dice. I get download mode and thats it. I know I must be doing somethimg wrong but damned if i can figure what. Pc is windows 764 bit. I like to have a custom rexovery and i have heard i can put onw like this (locked) but i did that to another device and to make it short it sits in a drawer being brand new and broken. Apparently those instructioms are correct because there are many success stories. I followed the directions like this is my last phone for a whi
PHP:
le. Can someone help me out please? Thank you
Holy....... 64bit! Im not futureman!!!!
Do you need to unlock the bootloader on d415? I taught you could flash a custom recovery without unlocking... (I don't own one!)
I ave twrp on it. So far i havent been able to do anything but a nandroid and restore with it. I am now at a pc so i can dl from devhost. We shall see, (i doubt it,)
whodisname said:
I ave twrp on it. So far i havent been able to do anything but a nandroid and restore with it. I am now at a pc so i can dl from devhost. We shall see, (i doubt it,)
Click to expand...
Click to collapse
The bootloader on the LG-D415 is unlocked out of the box.
Wow, and all these instructions!! I figured after i put twrp on it it was cool but it didnt flash the rom, omly had one cuz dev host doesnt dl on cell phones so well,
whodisname said:
My phone connects fine with adb. I tooted with towelroot, i have the D415 (see screenshot) i have run the commands on a pc several time with no errors. I tried it with my terminal emulator severaIm times and it says "decixe not found) HAHHA its just funny to me. I want to unlock this bootloader i even tried a factory cable (for kindle and only once) no dice. I get download mode and thats it. I know I must be doing somethimg wrong but damned if i can figure what. Pc is windows 764 bit. I like to have a custom rexovery and i have heard i can put onw like this (locked) but i did that to another device and to make it short it sits in a drawer being brand new and broken. Apparently those instructioms are correct because there are many success stories. I followed the directions like this is my last phone for a while. Can someone help me out please? Thank you
Click to expand...
Click to collapse
For starters, you need the fastboot executable for Windows to unlock the device, not ADB. The minimal ADB version, also applies to fastboot, is 1.0.31. Secondly, you must enable fastboot mode on the device beforehand. Thirdly, unless LG has changed things in the last month or so, the bootloader on the LG-D415 is unlocked.
To enable fastboot mode, see http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
To unlock the bootloader, see http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457. Shouldn't be necessary tho . Won't hurt anything to go thru the process however.
Thank you, i have fastboot and adb (fixed a bricked kindle last week!!) I wasnt sure about the bootloader and iwasnt gunna be without a recovery like i was with my lg lucud!!!
And excuse my unintelligible post above. New size screen?
Brand new here, looking to unlock, root and then flash a standard Android build or custom DeGoogled ROM for my new device. I was looking to find a way to unlock the bootloader to start and found that Huawei have stopped giving out unlock codes and that the info around unlocking wasn't great so I made a note of all my steps as below.
Please let me know if this works for you and if you have any issues, please also read and follow the guidelines carefully as there are lots of things like using all the applications as an administator and changing directories that are important.
I am also looking for a way to install TWRP or another recovery thing on this device so I don't brick it, as I want to root the tablet and muck around with it. Has anyone got any experience of doing this successfully and does anyone have links to methods to create a cloned backup of the standard OS?
This was done on a brand new Mediapad M3 Lite 8 (the Wifi version, not LTE) with Android 7.0, EMUI 5.1, CPN-W09, build CPN-W09C100B251 - BUT will probably work on the LTE version, the non-lite version and the 7 and 10 inch models.
IMPORTANT: This costs money and is done through the DC Unlocker tool, it costs 4 credits (4 euros/dollars) for the Mediapad M3 Lite 8 (Wifi, not LTE) as Huawei now do not offer the bootloader code AT ALL . I have copied/streamlined the steps below that were found as guides originally at the dc unlocker website, check their site guides to find originals.
Step 1 - Developer Options enable
Go to settings, about tablet, tap build number 7 times to unlock developer options
Go to developer options, enable OEM unlock, enable USB debugging
Step 2 - Enable manufacture mode
If your phone has a dialpad, enter dial pad code *#*#2846579#*#*
IF your phone doesn't have a dialpad, go to calculator and enter ()()2846579()()=
This willl take you to a developer menu, select "Project Menu", "Background settings", "USB ports settings", "Manufacture mode".
Step 3 - Install drivers
Connect your Android device to your PC with a usb cable and either install Hisuite from the connected drive that will attach, or download it from the Huawei website by searching for Huawei Hisuite and going to their official website.
To check this has worked, go to Device Manager on your PC and look for Modems - there should be an entry called Android Adapter Modem - if this is not present try disconnecting/reconnecting your device and restarting Hisuite.
Step 4 - Read bootloader code
Download the latest DC Unlocker tool from dc-unlocker dot com and extract it, then AS AN ADMINISTRATOR (right click and Run as Administrator) run the client.exe (was called dc-unlockerclient2.exe)
Click Select Manufacturer dropdown and change to Huawei Phones, not Modems, press the magnifier/search icon at bottom left and your phone info should be found. This should also
Step 5 - Buy credits from the dc unlocker site as a new user, try 4 credits first and then login with these new user details in the dc unlocker application on your PC, this will show your credits and the phone connected as well as the cost. Click the Unlocking icon on the top right and click Read botloader code to get your code. Make a note of this/copy it somewhere.
Step 6 - Go back to the folder that dc unlocker is in
Go into the unzipped folder and then copy the location of this folder by clicking on the address bar in File Explorer and copying this location, you'll have something similar to
C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403
Step 7 - Turn off your phone and turn it back on holding the Vol down and Power buttons to enter fastboot mode, connect your device to your PC
Step 8 - Open cmd by searching for cmd in windows, right click cmd and open it as administrator, you'll get the black and white windows terminal
In the terminal type "cd C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403" (or the path for the latest version of the dc unlocker you have downloaded) without the quotation marks and with YOUR directory path as described above. The command cd just changes directory to the one you give. Your terminal should now show the above directory as the path in which it now sends commands, i.e the > mark is now displayed after the directory path we copied
Step 9 - Type "adb devices" without quotation marks to start the adb daemon
Step 10 - Type "fastboot devices" without quotation marks and you should see a device number with the word fastboot next to it.
Step 11 - Now type "fastboot oem unlock" without the quotation marks, followed by a space and then your bootloader unlock code i.e
fastboot oem unlock XYZ123456789
Step 12 - Your device should show a screen asking you to accept the unlock, then onto another screen where you should press the power key to continue onto booting your factory reset unlocked device.
Step 13 - You might have to disconnect the USB cable and reboot your device now, and you'll set up the device from scratch again - but now the bootloader unlocked, allowing you to load stuff like TWRP if you can find the right version - which I can't right now! :good:
I have also now been able to install TWRP by using the TWRP image specifically for BAH-W09 found on page 17 of the "TWRP (greatslon mod)" in the link provided by pitapart
thread. I can't post links yet which is why I'm typing to source....
I have been trying to flash SuperSU using the latest 2.82 zip but keep getting the error "Extracting Ramdisk - Failure, aborting", which is the same error I'm getting when trying to root using SRKtool, both the 2.1 universal version and the 2.0 Huawei version, using option 1 for Mate P8 or option 6 for systemless.
I've downloaded a system root version of SuperSU (google "supersu system mode", first XDA thread) and flashed using TWRP, it says it has installed but the SuperSU app doesn't show root, and typing "su" in TWRP console doesn't show I can do commands in superuser mode. Can anyone help?
I recently have been purchased the LTE version of this device. Although I cannot try this out currently, I probably will in the future so please keep us updated about your experiments for reference!
avkjbl5bak said:
I have also now been able to install TWRP by using the TWRP image specifically for BAH-W09 found on page 17 of the "TWRP (greatslon mod)" in the link provided by pitapart
thread. I can't post links yet which is why I'm typing to source....
I have been trying to flash SuperSU using the latest 2.82 zip but keep getting the error "Extracting Ramdisk - Failure, aborting", which is the same error I'm getting when trying to root using SRKtool, both the 2.1 universal version and the 2.0 Huawei version, using option 1 for Mate P8 or option 6 for systemless.
I've downloaded a system root version of SuperSU (google "supersu system mode", first XDA thread) and flashed using TWRP, it says it has installed but the SuperSU app doesn't show root, and typing "su" in TWRP console doesn't show I can do commands in superuser mode. Can anyone help?
Click to expand...
Click to collapse
Hi,
Were you ever able to get your Mediapad M3 Lite 8 rooted? I really like this tablet but, need the 5 Ghz wifi band which requires root from everything I have read.
Thanks
howgies said:
Hi,
Were you ever able to get your Mediapad M3 Lite 8 rooted? I really like this tablet but, need the 5 Ghz wifi band which requires root from everything I have read.
Thanks
Click to expand...
Click to collapse
I have my Mediapad M3 Lite rooted by magisk.
I followed the unlock guide and unlocked the bootloader.
I couldn't find my exact firmware I downloaded the most recent one I could find.
I extracted the boot.img with Huawei Update extractor and copied it to my phone.
I download and installed latest magisk app.
I opened the magic app-> install -> install -> patch the boot image file which I then flashed through fastboot.
I then opened magisk -> install -> Direct install.
Everything works but like me you take a risk in not using the exact boot.img.
I tried and installed TWRP which worked but the volume keys would let me run the script I was trying to rebrand the phone. In the end it isn't necessary to root the phone.
sd26 said:
I followed the unlock guide and unlocked the bootloader.
I couldn't find my exact firmware I downloaded the most recent one I could find.
I extracted the boot.img with Huawei Update extractor and copied it to my phone.
Click to expand...
Click to collapse
Very bad idea and advice:
- people often uses wrong firmware or wrong version;
- a boot from a different version can be incompatible, you can be sure only too late!
The right thing is to boot to TWRP then in the console, using "dd" command do a copy of original boot!
nicolap8 said:
Very bad idea and advice:
- people often uses wrong firmware or wrong version;
- a boot from a different version can be incompatible, you can be sure only too late!
The right thing is to boot to TWRP then in the console, using "dd" command do a copy of original boot!
Click to expand...
Click to collapse
Very poor reply, you did not read my post properly, just jumped in to demonstrate your superciliousness. No advice was given and you missed the word risk. More productive use of replying would have been to include the actual command required anyway which is:
dd if=/dev/block/boot-device/by-name/boot of=boot.img
Helping wasn't the point your trying to make.
sd26 said:
Very poor reply, you did not read my post properly, just jumped in to demonstrate your superciliousness. No advice was given and you missed the word risk. More productive use of replying would have been to include the actual command required anyway which is:
dd if=/dev/block/boot-device/by-name/boot of=boot.img
Helping wasn't the point your trying to make.
Click to expand...
Click to collapse
if my reply is too poor, report it to mods...
A post like your IS an advice because people read and follow it. What is wrong is not that you write or my opinion but people behaviour
I read the "risk" word but a lot of people would not. This is also the reason I don't wrote the dd command: search and learn! Most of the messages you read here are of people who have broken their own terminal because just followed a post like your, without knowing what are doing.
N
sd26 said:
Everything works but like me you take a risk in not using the exact boot.img.
Click to expand...
Click to collapse
I see in your first screenshot the fingerprint-id menuentry is gone.... does your fingerprint-sensor working properly ?
I rooted my mediapad m3 lite 10 in the same way, but my boot-image is the right version. ( installed is BAH-W09C100B257, firmware downloaded with the huawei firmware finder app is exactly BAH-W09C100B257) . My fingerprint menuentry is gone too.....and the sensor doesnt work (with the working registered fingerprint before the rooting)
Marc
#marcg# said:
I see in your first screenshot the fingerprint-id menuentry is gone.... does your fingerprint-sensor working properly ?
I rooted my mediapad m3 lite 10 in the same way, but my boot-image is the right version. ( installed is BAH-W09C100B257, firmware downloaded with the huawei firmware finder app is exactly BAH-W09C100B257) . My fingerprint menuentry is gone too.....and the sensor doesnt work (with the working registered fingerprint before the rooting)
Marc
Click to expand...
Click to collapse
I did not have the fingerprint option activated so I checked it and found my sensor also does not work with the patched boot.img on. I could search and find the fingerprint menu entry but could not get it to operate. Reflashing the stock boot.img returned the sensor menu and fingerprint to normal but of course you lose root. More searching for solutions required.
Also I'm using the TWRP-3.2.1-bah-20180627.img recovery. The volume keys don't work so the hurupdater script I'd like to use aborts. Anyone got any other recovery for a CPN-W09C128B006?.
sd26 said:
I did not have the fingerprint option activated so I checked it and found my sensor also does not work with the patched boot.img on. I could search and find the fingerprint menu entry but could not get it to operate. Reflashing the stock boot.img returned the sensor menu and fingerprint to normal but of course you lose root. More searching for solutions required.
Also I'm using the TWRP-3.2.1-bah-20180627.img recovery. The volume keys don't work so the hurupdater script I'd like to use aborts. Anyone got any other recovery for a CPN-W09C128B006?.
Click to expand...
Click to collapse
I have
avkjbl5bak said:
Brand new here, looking to unlock, root and then flash a standard Android build or custom DeGoogled ROM for my new device. I was looking to find a way to unlock the bootloader to start and found that Huawei have stopped giving out unlock codes and that the info around unlocking wasn't great so I made a note of all my steps as below.
Please let me know if this works for you and if you have any issues, please also read and follow the guidelines carefully as there are lots of things like using all the applications as an administator and changing directories that are important.
I am also looking for a way to install TWRP or another recovery thing on this device so I don't brick it, as I want to root the tablet and muck around with it. Has anyone got any experience of doing this successfully and does anyone have links to methods to create a cloned backup of the standard OS?
This was done on a brand new Mediapad M3 Lite 8 (the Wifi version, not LTE) with Android 7.0, EMUI 5.1, CPN-W09, build CPN-W09C100B251 - BUT will probably work on the LTE version, the non-lite version and the 7 and 10 inch models.
IMPORTANT: This costs money and is done through the DC Unlocker tool, it costs 4 credits (4 euros/dollars) for the Mediapad M3 Lite 8 (Wifi, not LTE) as Huawei now do not offer the bootloader code AT ALL . I have copied/streamlined the steps below that were found as guides originally at the dc unlocker website, check their site guides to find originals.
Step 1 - Developer Options enable
Go to settings, about tablet, tap build number 7 times to unlock developer options
Go to developer options, enable OEM unlock, enable USB debugging
Step 2 - Enable manufacture mode
If your phone has a dialpad, enter dial pad code *#*#2846579#*#*
IF your phone doesn't have a dialpad, go to calculator and enter ()()2846579()()=
This willl take you to a developer menu, select "Project Menu", "Background settings", "USB ports settings", "Manufacture mode".
Step 3 - Install drivers
Connect your Android device to your PC with a usb cable and either install Hisuite from the connected drive that will attach, or download it from the Huawei website by searching for Huawei Hisuite and going to their official website.
To check this has worked, go to Device Manager on your PC and look for Modems - there should be an entry called Android Adapter Modem - if this is not present try disconnecting/reconnecting your device and restarting Hisuite.
Step 4 - Read bootloader code
Download the latest DC Unlocker tool from dc-unlocker dot com and extract it, then AS AN ADMINISTRATOR (right click and Run as Administrator) run the client.exe (was called dc-unlockerclient2.exe)
Click Select Manufacturer dropdown and change to Huawei Phones, not Modems, press the magnifier/search icon at bottom left and your phone info should be found. This should also
Step 5 - Buy credits from the dc unlocker site as a new user, try 4 credits first and then login with these new user details in the dc unlocker application on your PC, this will show your credits and the phone connected as well as the cost. Click the Unlocking icon on the top right and click Read botloader code to get your code. Make a note of this/copy it somewhere.
Step 6 - Go back to the folder that dc unlocker is in
Go into the unzipped folder and then copy the location of this folder by clicking on the address bar in File Explorer and copying this location, you'll have something similar to
C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403
Step 7 - Turn off your phone and turn it back on holding the Vol down and Power buttons to enter fastboot mode, connect your device to your PC
Step 8 - Open cmd by searching for cmd in windows, right click cmd and open it as administrator, you'll get the black and white windows terminal
In the terminal type "cd C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403" (or the path for the latest version of the dc unlocker you have downloaded) without the quotation marks and with YOUR directory path as described above. The command cd just changes directory to the one you give. Your terminal should now show the above directory as the path in which it now sends commands, i.e the > mark is now displayed after the directory path we copied
Step 9 - Type "adb devices" without quotation marks to start the adb daemon
Step 10 - Type "fastboot devices" without quotation marks and you should see a device number with the word fastboot next to it.
Step 11 - Now type "fastboot oem unlock" without the quotation marks, followed by a space and then your bootloader unlock code i.e
fastboot oem unlock XYZ123456789
Step 12 - Your device should show a screen asking you to accept the unlock, then onto another screen where you should press the power key to continue onto booting your factory reset unlocked device.
Step 13 - You might have to disconnect the USB cable and reboot your device now, and you'll set up the device from scratch again - but now the bootloader unlocked, allowing you to load stuff like TWRP if you can find the right version - which I can't right now! :good:
Click to expand...
Click to collapse
Did you ever get and answer to your question about cloning or getting the original factory images. I've been trying on and off for 9months. I have unlocked the bootloader and backed up using TWRP (from the 10inch model), but when I relocked the bootloader everything fell apart... unstable boot loops, etc. not sure if I had to wipe recovery I burned with TWRP or what. Also TWRP does not back-up the data partition I think due to encryption (from other posts I read). My goal was to rebrand a pile of the Chinese version tablets I have to US because we use them in our product, and the US are not available, so rebranding would give me more time before to find a replacement. Any clues would help!!!
sd26 said:
I did not have the fingerprint option activated so I checked it and found my sensor also does not work with the patched boot.img on. I could search and find the fingerprint menu entry but could not get it to operate. Reflashing the stock boot.img returned the sensor menu and fingerprint to normal but of course you lose root. More searching for solutions required.
Also I'm using the TWRP-3.2.1-bah-20180627.img recovery. The volume keys don't work so the hurupdater script I'd like to use aborts. Anyone got any other recovery for a CPN-W09C128B006?.
Click to expand...
Click to collapse
I successfully rooted my CPN-L09 without loosing fp sensor, have a look here: https://forum.xda-developers.com/mediapad-m3/help/to-patch-boot-img-magisk-v17-3-t3938629
Hi
im a new member but have been using the site for ages.
my mediapad m3 is also wifi only and im trying to get the code for the bootloader to be unlocked except for the fact that my calculator app isn't scientific enough (lol) to include brackets.
what do I do to get the code or update my calc app?
alex
bigprat9 said:
Hi
im a new member but have been using the site for ages.
my mediapad m3 is also wifi only and im trying to get the code for the bootloader to be unlocked except for the fact that my calculator app isn't scientific enough (lol) to include brackets.
what do I do to get the code or update my calc app?
alex
Click to expand...
Click to collapse
You have to use the calculator in landscape mode (turn on auto-rotate) and then the bracket buttons will appear.
So I finally got around to installing this on my stock version. I found 16GB was too limiting and I was hoping to use the SD card to expand the space so I could use it for a few more years. I purchased the code from DC_unlocker.
A couple of things I noticed while following the guide. To enter fastboot mode, holding down the volume down and power button doesn't seem to work. What you to do is while it's off, hold down the volume down button and plug in the microusb cable, while continuing to hold it down. You could also enter fastboot using an ADB command.
Also I couldn't wipe anything before installing the new roms, I got error messages. I'm not sure what that means. Anyways after installing android 9, it seemed to take a very long time to first boot. The graphic animation is going, but I wasn't sure if it was working so I hard reset once, tried to boot again and then waited again, hard reset again and put it down thinking I would have to look into the error messages and when I came back it was up and running.
Hi, I'm hoping someone can help me out here.
A few days ago, I followed the instructions unlocking the bootloader of my Mediapad M3 lite 8 (CPN-W09) and sure enough, I successfully unlocked the bootloader. However I've now run into another problem - I cannot get the FRP on the tablet to be unlocked!
Nothing I've tried seems to get it to unlock. The (only) Google account used on the tablet has been my own, and it's been no problem signing back into my account when factory resetting the tablet. One time when investigating it, after a factory reset it did say that it was "restricted" but again, adding my Google account details on the setup was no issue, but even after then deleting the account (which, if I'm right, should set FRP to "unlocked") when I enter into fastboot mode it still shows FRP as locked! And it shows it no matter what I do, wherever the Google account is "active" on the tablet or not, and the last four or five times I've did a factory reset with both data and cache partition wipes done and nothing budges. I think I'm at a lost cause here - the "OEM Unlock" option in the developer settings is totally greyed out. ?
Of course, the tablet is still "usable" but there is no way to carry out special functions after unlocking the bootloader, like rooting, install TWRP, custom ROM etc. and it just kinds of stands in a limbo.
I've tried searching here on XDA and the web in general, high and low, to see if this problem has affected anyone else, and strangely it doesn't seem to happen to anyone else!
For the record, I've also tried hardreset.info's FRP unlock tool which claimed to be successful, but it clearly wasn't!
I hope someone out there might have a solution to my woe - as I think I've partially crippled by M3 Lite 8 otherwise by trying to unlock the bootloader.
lawhec said:
Hi, I'm hoping someone can help me out here.
A few days ago, I followed the instructions unlocking the bootloader of my Mediapad M3 lite 8 (CPN-W09) and sure enough, I successfully unlocked the bootloader. However I've now run into another problem - I cannot get the FRP on the tablet to be unlocked!
Nothing I've tried seems to get it to unlock. The (only) Google account used on the tablet has been my own, and it's been no problem signing back into my account when factory resetting the tablet. One time when investigating it, after a factory reset it did say that it was "restricted" but again, adding my Google account details on the setup was no issue, but even after then deleting the account (which, if I'm right, should set FRP to "unlocked") when I enter into fastboot mode it still shows FRP as locked! And it shows it no matter what I do, wherever the Google account is "active" on the tablet or not, and the last four or five times I've did a factory reset with both data and cache partition wipes done and nothing budges. I think I'm at a lost cause here - the "OEM Unlock" option in the developer settings is totally greyed out. ?
Of course, the tablet is still "usable" but there is no way to carry out special functions after unlocking the bootloader, like rooting, install TWRP, custom ROM etc. and it just kinds of stands in a limbo.
I've tried searching here on XDA and the web in general, high and low, to see if this problem has affected anyone else, and strangely it doesn't seem to happen to anyone else!
For the record, I've also tried hardreset.info's FRP unlock tool which claimed to be successful, but it clearly wasn't!
I hope someone out there might have a solution to my woe - as I think I've partially crippled by M3 Lite 8 otherwise by trying to unlock the bootloader.
Click to expand...
Click to collapse
You could try to lock bootloader back, and before to unlock bootloader again, first just unlock OEM .
surdu_petru said:
You could try to lock bootloader back, and before to unlock bootloader again, first just unlock OEM .
Click to expand...
Click to collapse
I did try this at the time, and I couldn't get it to work. But I had another try at it yesterday and I managed to get the bootloader locked again, toggle OEM unlock to "off" and unlocked the bootloader once more and it worked!
So after doing this, I tried to get TWRP 3.3.1-1 flashed but it would stay frozen on the screen - I then read that I needed to install TWRP 3.2.0-0 first, install the August 2019 Lineage 16 firmware, then go back to the bootloader, flash TWRP 3.3.1-0, check everything was OK and then return to bootloader to finally flash TWRP 3.3.1-1. Success! I then flashed the latest Lineage OS 17.1 firmware along with Open Gapps (ARM64, Android 10, nano) and so far everything has worked OK. I just need to download all my apps again, but I'm sure it will give my CPN-W09 a new lease of life!
I used to do some rooting previously with Android handsets in the past, but the last time was two years ago (rooting & upgrading an Alcatel handset to Android 6.0) and FRP was new to me, throwing me off.
I've donated some Euros to you as an appreciation for your work & advice. Merci beaucoup!
lawhec said:
I did try this at the time, and I couldn't get it to work. But I had another try at it yesterday and I managed to get the bootloader locked again, toggle OEM unlock to "off" and unlocked the bootloader once more and it worked!
So after doing this, I tried to get TWRP 3.3.1-1 flashed but it would stay frozen on the screen - I then read that I needed to install TWRP 3.2.0-0 first, install the August 2019 Lineage 16 firmware, then go back to the bootloader, flash TWRP 3.3.1-0, check everything was OK and then return to bootloader to finally flash TWRP 3.3.1-1. Success! I then flashed the latest Lineage OS 17.1 firmware along with Open Gapps (ARM64, Android 10, nano) and so far everything has worked OK. I just need to download all my apps again, but I'm sure it will give my CPN-W09 a new lease of life!
I used to do some rooting previously with Android handsets in the past, but the last time was two years ago (rooting & upgrading an Alcatel handset to Android 6.0) and FRP was new to me, throwing me off.
I've donated some Euros to you as an appreciation for your work & advice. Merci beaucoup!
Click to expand...
Click to collapse
Thank you very much too
Hello
I followed the steps here to unlock the bootloader with my btv-dl09, that worked fine even its not lite.. :fingers-crossed:
but now, any clues? may i ll try the way of lawhec with
lawhec said:
So after doing this, I tried to get TWRP 3.3.1-1 flashed but it would stay frozen on the screen - I then read that I needed to install TWRP 3.2.0-0 first, install the August 2019 Lineage 16 firmware, then go back to the bootloader, flash TWRP 3.3.1-0, check everything was OK and then return to bootloader to finally flash TWRP 3.3.1-1. Success! I then flashed the latest Lineage OS 17.1 firmware along with Open Gapps (ARM64, Android 10, nano) and so far everything has worked OK. I just need to download all my apps again, but I'm sure it will give my CPN-W09 a new lease of life!
Click to expand...
Click to collapse
but cant find the TWRP 3.3.1-1?
may u Mean
[Recovery][Official] TWRP 3.3.1-10 [G97*0][Snap][3.Jan.20]
[Recovery][Official] TWRP 3.3.1-12 Snapdragon [N97x0][10.Nov.19]
[RECOVERY][ROOT]TWRP 3.3.1-1 Galaxy J6+/J610F/FN/G/DS
???
if so, why u choose one of these? No Clue for me^^ plz let me know
greetz
ADD: just found
Developed By :letschky
twrp-3.1.1-1-next.img
Jul 13, 2017 | 03:32PM
maybe these? looks pretty old but still working? Oo
So.. My Huawei P10 won't boot neither into system nor recovery, the screen is off and there's no LED indication.
It is recognized in fastboot, I can erase and flash both system and recovery, though rebooting the device does nothing, it just shows up in fastboot again, still with screen off.
Is there any way to save this phone? I installed a new battery too.
dc pheonix and hcu client did not help either.
:crying:
I have the same issue. Hard brick, doesnt turn on after I upgraded to oreo.
Guys, I have this issue, too and worked a bit with DC Phoenix support.
The reason why my P10 didn't boot anymore is simple: I just flashed the wrong firmware files for rolling back from Pie to Oreo.
Now I have a shiny black piece of junk.
I tried to flash with DC Phoenix, also with test point. The device was recognized as serial device, so the test point was working. But DC Phoenix failed at flashing.
DC support says, that Dec 18 security patches are preventing to flash old firmwares but DC needs to flash the original factory firmware, OTA isn't working.
So at the end of an 8 hour day trying to fix my P10 my result was a nice chat and a fast refund of my 19€ for DC pheonix.
If you can't get it working even with test point method, your phone is is a piece of junk.
Mostly it's caused by doing something wrong at downloading firmwares or flashing them, also while flashing wrong Magisk modules, Xposed or wrong boot images.
Since Pie don't have a boot partition anymore it's important to download a rollback firmware (2 files instead of 3) so the recovery is able to reformat before flashing.
Jannomag said:
Guys, I have this issue, too and worked a bit with DC Phoenix support.
The reason why my P10 didn't boot anymore is simple: I just flashed the wrong firmware files for rolling back from Pie to Oreo.
Now I have a shiny black piece of junk.
I tried to flash with DC Phoenix, also with test point. The device was recognized as serial device, so the test point was working. But DC Phoenix failed at flashing.
DC support says, that Dec 18 security patches are preventing to flash old firmwares but DC needs to flash the original factory firmware, OTA isn't working.
So at the end of an 8 hour day trying to fix my P10 my result was a nice chat and a fast refund of my 19€ for DC pheonix.
If you can't get it working even with test point method, your phone is is a piece of junk.
Mostly it's caused by doing something wrong at downloading firmwares or flashing them, also while flashing wrong Magisk modules, Xposed or wrong boot images.
Since Pie don't have a boot partition anymore it's important to download a rollback firmware (2 files instead of 3) so the recovery is able to reformat before flashing.
Click to expand...
Click to collapse
were you able to send flash erecovery through adb ? or did it show success read and failed write?
thank you
NowLearn said:
were you able to send flash erecovery through adb ? or did it show success read and failed write?
thank you
Click to expand...
Click to collapse
For adb it’s needed that the phone starts completely into system or twrp - both not possible for me.
With fastboot it’s not possible to flash eRecovery, just recovery.
Jannomag said:
Guys, I have this issue, too and worked a bit with DC Phoenix support.
The reason why my P10 didn't boot anymore is simple: I just flashed the wrong firmware files for rolling back from Pie to Oreo.
Now I have a shiny black piece of junk.
I tried to flash with DC Phoenix, also with test point. The device was recognized as serial device, so the test point was working. But DC Phoenix failed at flashing.
DC support says, that Dec 18 security patches are preventing to flash old firmwares but DC needs to flash the original factory firmware, OTA isn't working.
So at the end of an 8 hour day trying to fix my P10 my result was a nice chat and a fast refund of my 19€ for DC pheonix.
If you can't get it working even with test point method, your phone is is a piece of junk.
Mostly it's caused by doing something wrong at downloading firmwares or flashing them, also while flashing wrong Magisk modules, Xposed or wrong boot images.
Since Pie don't have a boot partition anymore it's important to download a rollback firmware (2 files instead of 3) so the recovery is able to reformat before flashing.
Click to expand...
Click to collapse
Yes, I tried the same, and also got the security patch warning, though little did I know I could get a refund. I did not try the 'test point' method. Not sure if I get it, do you connect/solder usb-cable onto the phone's motherboard?
You need to connect the test point to ground, you can use the shielding right beside of it. Take a small wire or tweezers for it.
I did it like this:
- connect the phone to pc, it should be recognized as fastboot device
- Short test point with ground
- hold down the power button until the computer recognizes the device again
- install the serial driver
DC should work now. But if it doesn’t, write it in the dc forums and you’ll get refund
Huawei P10 Successfully Recovered from Fastboot black screen on latest Security 9.
Alham Do Lillah With the help of Allah Almighty today I successfully recovered my p10 from black display stuck in fastboot mode on latest Security 9..
I used 2 tools
1: Dc phoenix
2: chimera
chsaim said:
Alham Do Lillah With the help of Allah Almighty today I successfully recovered my p10 from black display stuck in fastboot mode on latest Security 9..
I used 2 tools
1: Dc phoenix
2: chimera
Click to expand...
Click to collapse
Can you explain exactly how?
Jannomag said:
Can you explain exactly how?[/QUOTE
you need to know exactly build number and flash latest firmware according to build number with chimera tool.
make sure that phone is in fastboot mode... am sorry if i cant explained well ... for more details write me at [email protected]
Click to expand...
Click to collapse
Yes, please share some information how can we recover our dead p10. It would greatly help the community. Thank you
I tried it with DC and Chimera. Both aren't working for me, because of the security patches. Huawei did some deep changes between October and December 2018 and made it very hard to flash even with test points - another reason for me to leave Huawei to my alltime smartphone enemy Samsung...
The DC-Phoenix and Chimera teams are working hard on a solution, take a look at their forums and you'll notice that many people have this problems, just because Huawei ****ed it up.
I mean, we did all something wrong, otherwise this threat won't exist. But Huawei made it hard for us to revive the devices and this reminds me of Apples politics. Huawei doesn't need to give support to unlocked phones but it's very unfair to prevent their customers from doing what they want including unlocking.
Back to topic:
Follow the forums of DC and Chimera. If you found any solution or fix, please post it here.
My device, also bricked while flashing the wrong firmware for rolling back from pie, shows just black screen and fastboot is working.
Test point didn't work, also Chimera couldn't flash anything.
My device gets quiet warm while in fastboot, so I disconnected the battery to prevent deep discharging.
Dear the same situation was happened with my p10 but i recovered... So if you want to recover your phone then give ultra view id and pass....... If you have chimera and dc phoenix you can make it possible.. But remember you must need to know exactly build number
If any one needs my help here is my WhatsApp contact me anytime... +923007969629
If you can share the steps. It would help the community thank you @chsaim
Yes, please share the steps to help the community.
Thanks!
There's absolutely no reason for not sharing the steps in a simple tutorial. Instead @chsaim is begging for remote access to our computers, I don't know why.
I chatted a lot with Chimera support and they told me that there's currently not way to recover, with faulty partitions caused by flashing, with the Dec.2018 security patches and newer. This included the firmware 382, on some 380 devices it doesn't work either.
They also want to send me an E-Mail when they find a solution for this. For now I got my money back from them - great support, also the DC team.
I'm happy to get a used mainboard from local market and now have my P10 as spare phone.
yeap.same **** again with Huawei phones.ı want to try pie rom and when ı try rollback oreo phones turn off and not open again.this is not like a other hard or soft brick problem because I have a experiance about other problems.phone cant charge or pc can't see the device ı cant see red led too.just dead.ı use this phone 2 years but never buying huawei again neverrrr.anybody found a solition ?
Jannomag said:
You need to connect the test point to ground...
- connect the phone to pc, it should be recognized as fastboot device
- Short test point with ground
- hold down the power button until the computer recognizes the device again
- install the serial driver
...
Click to expand...
Click to collapse
Testpoint should be connected till pc recognize it properly or connected all the time during flashing? Do you have any logs at what point dc crashed in your case?
lukastob said:
Testpoint should be connected till pc recognize it properly or connected all the time during flashing? Do you have any logs at what point dc crashed in your case?
Click to expand...
Click to collapse
I can access fastboot with dc-phoenix. Once I tried to send erecovery, recovery, or kernel w
Through cmd. It reads but it can't write. That's where I get stuck. If dc it's able to write then I would be able to recover my dead phone. Thank you
lukastob said:
Testpoint should be connected till pc recognize it properly or connected all the time during flashing? Do you have any logs at what point dc crashed in your case?
Click to expand...
Click to collapse
Test point needs to be shorted until the computer recognizes the P10 as an USB serial device. You need drivers for this, which you can get from DC Phoenix.
DC couldn't flash the bootloader:
Code:
BOOTLOADER File to update: Kirin960_T0_A7.0_V1
20.02.2019 21:34:26 Starting to write device...
Writing bootloader...
Error writing Bootloader
20.02.2019 21:35:36 Writing device finished - INCOMPLETE
Hello Developers!
I have found an easy way to unlock the bootloader of our Huawei Nova 2 Plus. No need to use Testpoint or pay for software to unlock. it is an Python Script which would brute force the code through the IMEI number you have entered
IMPORTANT: MAKE SURE THE PHONE IS CONNECTED TO ADB OR THIS TOOL WILL NOT WORK AS IT WILL RESTART INTO FASTBOOT AND TRY ALL THE CODES IT GENERATED!!!!!!!.
THIS TOOL WORKS FOR Linux and Windows. the guide is for windows but the script would work for linux completely fine.
REQUIREMENTS
Download The Tool from the thread
Install Python From Microsoft Store Or The Python Website
Run Powershell as Admin
Run the Command:- python unlock.py
Enter Your IMEI Number
MAKE SURE YOUR PHONE IS CONNECTED TO ADB!!!!!
Wait for the code to be found
If your phone reboot into EMUI reboot back into bootloader mode and the tool will start the bootloader unlocking process
The Phone May Reboot Several Times.
If you get an warning about unlocking the bootloader you have succeeded to unlock the bootloader
Special Thanks To KASHIFALIKHAN For the tool . the download will be down below
Hello does unlocking bootloader resets my data? As in will it factory reset?
Yes it would reset your data. It happens on all phones for security reason
deleted
Hello..could you please explain more about the process and what should we do about attached file?
you have to extract the ZIP and run the unlock script and enter your imei number make sure you have python installed on your PC
TMHAKIM said:
you have to extract the ZIP and run the unlock script and enter your imei number make sure you have python installed on your PC
Click to expand...
Click to collapse
Thank you for your answer..
So ,unlocking bootloader resets my data..
My phone is nova 3i android 9 LX2..
Is this procedure safe for my phone?
Have you tried it on this model?
Hello,
I have a chinese Honor 9x (bought from alieExpress). I currently have the HarmonyOS installed that doesn't allow me to run any google-apps, so I'm trying to unlock the bootloader. Out of desperation I tried to use this program to try bruteforce the unlock code. However as I start running it (USB debug enabled and all in options), after the first reboot it arrives in fastboot mode (as I believe should be expected), but then it gives the error that no devices have been found, and therefore remains hanging at 10% / first code tried.
I have a feeling that somehow after the reboot the usb debugging/OEM mode is not on anymore and therefore the python program doesn't identify the phone. I feel this has to do with the setting "enable OEM mode" not being available in any of the settings in my phone (probably a little chinese easter egg to make all this more difficult?). I don't really know how to tackle this issue tho, any advice is appreciated.
honorable9x said:
Hello,
I have a chinese Honor 9x (bought from alieExpress). I currently have the HarmonyOS installed that doesn't allow me to run any google-apps, so I'm trying to unlock the bootloader. Out of desperation I tried to use this program to try bruteforce the unlock code. However as I start running it (USB debug enabled and all in options), after the first reboot it arrives in fastboot mode (as I believe should be expected), but then it gives the error that no devices have been found, and therefore remains hanging at 10% / first code tried.
I have a feeling that somehow after the reboot the usb debugging/OEM mode is not on anymore and therefore the python program doesn't identify the phone. I feel this has to do with the setting "enable OEM mode" not being available in any of the settings in my phone (probably a little chinese easter egg to make all this more difficult?). I don't really know how to tackle this issue tho, any advice is appreciated.
Click to expand...
Click to collapse
Have you installed Hisuite drivers? And check device manager when you boot into fastboot if it shows Android bootloader interface then you're good to go if not then try installing Hisuite drivers
honorable9x said:
Hello,
I have a chinese Honor 9x (bought from alieExpress). I currently have the HarmonyOS installed that doesn't allow me to run any google-apps, so I'm trying to unlock the bootloader. Out of desperation I tried to use this program to try bruteforce the unlock code. However as I start running it (USB debug enabled and all in options), after the first reboot it arrives in fastboot mode (as I believe should be expected), but then it gives the error that no devices have been found, and therefore remains hanging at 10% / first code tried.
I have a feeling that somehow after the reboot the usb debugging/OEM mode is not on anymore and therefore the python program doesn't identify the phone. I feel this has to do with the setting "enable OEM mode" not being available in any of the settings in my phone (probably a little chinese easter egg to make all this more difficult?). I don't really know how to tackle this issue tho, any advice is appreciated.
Click to expand...
Click to collapse
Since you could enter the bootloader when you first trying, I'm guess it might be the Harmony OS. You can try use Hisuite to roll back your HarmonyOS to EMUI, then try to unlock the bootloader. Most of modified Android OS removed the OEM mode to make you have a hard time on unlock bootloader. These will be really easy if you use some phones like Google's Pixel.
I have an old Huawei Nova 3i and it's updated into the Harmony OS, which is not what I want, I'd like to have a more cleaner OS that not with so much preinstalled apps. Then I roll back to EMUI as the first step to install other ROM, and that script it's working now. It's still trying get the password so I can't say it worked or some thing else.
And alter is that, if you just want install some google-apps, you may just roll back to EMUI, it should worked fine. And I'm not really suggest you have any phone from Huawei now since they really push their Harmony OS as a thing (at least, in China) and not really friendly towards people not in China (since lots of popular apps' depended G-apps). I'm annoyed even I'm Chinese though.
I need help too. So, I own a Moto G5s plus sanders. I unlocked its bootloader the day I got it. Didn't keep any backup and rooted it. I Also installed dot os based on android 11. But my 4G Volte connection was finicky. So, I decided to use a Volte zip patch. But, anyways I flashed the zip via TWRP and tried to reboot. But the phone didn't turn on after that. After a few minutes to my shock I understood that I hardbricked my mobile. No button combos, nothing worked. Anyways in my desperation I found a YouTube video showing the use of blankflash to revive a phone and lo and behold I used the procedure to again restore my device. It booted to the fastboot interface. But my happiness was short lived. My baseband was unknown at this point and the bootloader was I dunno downgraded to 0.5 inplace of 2.12. But, more importantly the unlock status was lost. I unlocked it again and all went well. I could even flashed TWRP. but then I realised I couldn't upgrade my bootloader. I couldn’t do anything. It's always gives a "security downgrade", "preflash validation failed" and "permission denied" error. I even tried RSA official rescue tool from Lenovo but even it was unsuccessful. It was never unsuccessful before that. Not even with a unlocked bootloader. I researched for days and tried custom ROMs. I flashed stock images. Nothing brought back my baseband and IMEI. When I type "fastboot oem unlock critical" it gives me permission denied error with a message. "Need OEM signed bootloader." I think the blankflash bootloader is the root of all evil. I need to change it and therefore I need to enter the edl mode. I have tried all adb commands and fastboot commands. The phone reboots okay after those commands but never goes into edl mode whatsoever. I am also ready to do a controlled hardbrick of my device to go into the edl mode so that I can use my device again with a proper bootloader and a properly working fastboot. Please help
i think this vid will help
Greetings everyone. Sorry if I posted this in the wrong forum. Please move this in appropriate forum if I made a mistake. Believe me, for the last 7 days I have searched all of xda and internet, followed innumerable guides, FAQs and workarounds and none worked. So, as a last resort I am starting this thread
Device: Motorola Moto G5s Plus XT1804 ......4GB _64GB variant
Problem: 1) Baseband not found (unknown) Original Baseband: M8953_52.61.07.98R SANDERS_INDIADSDS_CUST
2) IMEI 0 (Sim cards are not detected).
I bought this refurbished phone about an week ago after my last LG went kaput. I was happy by the build quality of the phone. But it only ran Android 8.1 Oreo. So, I decided to put a custom ROM in it. I am not exactly a newbie to the world of CyanogenMods, Lineage OSes and Pixel Experiences. Or, so I thought. Anyways, after a lot of searching I finally decided on Dot OS 5.2 Official Android 11 version. The ROM looked very pleasing and the reviews looked positive. So, I got the unlock key from Motorola website, unlocked the bootloader, put in official TWRP recovery in it. Everything went like a breeze and in all that excitement I forgot to take a backup of the persist, efs and other partitions. A very costly mistake it seems. DotOS booted fine and looked really fresh till I found that there is a small cross near the SIM card network signal triangle up righthand side corner and the signal is only LTE and not VOLTE. I was using a Vodafone Sim card at the time. Although VOLTE option was enabled in SIM settings. To confirm my doubts regarding VOLTE I switched to a JIO Simcard and alas I was not able to make a call without redirecting through the horrid JIO calling app. VOLTE was indeed not working. So, I looked up for a fix and I found a Volte ZIP file from here https://www.google.com/url?sa=t&sou...0QFnoECBAQAQ&usg=AOvVaw0YgJvCjQWXXV8WQSJkxBOK . This was the starting of my troubles. I flashed the universal VOLTE fix zip from TWRP and it flashed fine. On rebooting, I found to my shock that my phone was not turning on. I pressed and held the power key and there was no sign of life. I couldn’t go to the fastboot bootloader or recovery. Only the white led blinked at the top when connected to the charger. My phone was apparently hard bricked. I searched frantically for a solution in this forum and YouTube wherein I found that one can bring it back to life by doing a blankflash. Found the blankflash file here https://www.google.com/url?sa=t&sou...wQFnoECAsQAQ&usg=AOvVaw1eVdBWGVFr8aiqLdP-ZkeT followed the instructions and it flashed my bricked device back to fastboot. I was relieved for a moment but the next I found that the Bootloader version has downgraded from BL C2 07 to BL C0 05. I knew something was wrong as bootloader downgrade shouldn't be possible. Also the unlock and rooted status were also lost and the baseband was unknown at this point. Anyways the device was recognised as a fastboot device and I tried to flash the stock ROM latest version using the fastboot. But, only then I realised there was something wrong with the bootloader. It gave errors like security downgrade, permission denied, preflash validation failed, remote command failed. At this point I was truly confused and worried. Why would it think the latest bootloader to be a security downgrade to a supposedly old bootloader and prevent me from flashing it. However it did flash the other files like gpt.bin for partition, oem.img, boot.img, system.img sparsechunks and everything else. I booted back to Android 8.1 Oreo and everything seemed working except my IMEI now read zero and my Simcard was not recognised by the device. After that I again unlocked my bootloader. Somehow the original unlock key worked and the bootloader screen said flashing unlocked but the bootloader didn't behave like an unlocked bootloader. The TWRP installed fine but couldn’t install the latest Pixel Experience. The flash screen said PE 11 was for Sanders and my device is (blank no name). I tried both the normal and plus and both behaved similarly. Lineage OS unofficial builds behaved similarly. I again tried Dot OS and Arrow OS and both installed fine except there was no signal. For a moment I tried to forget about the bootloader but concentrated on recovering my IMEI and Baseband but I couldn’t. For nearly 5 days I tried different guides including a detailed guide using Validus Sanders ROM but none worked. My EFS folder has files around 12 megabytes but my Persist seems deleted at zero bytes. The IMEI keeps changing between null, zero and unknown depending on the 20 something ROMs I tasted on this device. At this point, I am at a loss. This was to be my main phone and I am financially crunched. I can't buy another phone right now. I think that blankflash bootloader is corrupted and it is giving me permission denied errors. Even Magisk won't work properly. I even tried using the official rescue and smart assistant tool by Lenovo and it failed at 47 percent. I tried in different computers and Win7 to Win 11 OSes but it was of no use. I also tried getting a QCN file but I couldn’t get one for the device to recover the IMEI. Please suggest something if anyone of you can save this poor device of mine. Thanks in advance
Raghaov said:
i think this vid will help
Click to expand...
Click to collapse
Thanks for the quick reply but my phone is soft bricked now. It was hardbricked and I uses a faulty blankflash bootloader to bring it back to life. My device is softbricked now. I have lost my baseband and I have no IMEI. I cannot take calls and no mobile data. Can you show me a way to go to edl mode in my device. Thanks again.
can your phone turn on if yes can you root it with magisk
if yes then pls tell me i will tell you
I can do everything except calling and mobile data. Yes, I have rooted with Magisk and have root access. But my baseband is unknown and my IMEI is showing zero. I can't call or access mobile data. Although I can use wifi
I have tried what is shown in this video already. Didn't work
I think the blank flash bootloader was corrupt or of a different region.
so go to magisk manager and on top-right corner you will see setting click the button right next to it and click on reboot to edl
I didn't even knew that. Trying asap. Will update
Doesn’t work. Reboots back to system.
Updated Magisk to latest and tried both edl and download mode like you said brother. Everytime boots back to system. Am I missing something. The phone was not connected to the PC at the time
I am on stock Oreo now. Rooted and twrp installed
An interesting observation while installing Xposed, it gave an error that the device is not rooted properly
I have an untouched dump file for my model. The whole thing. Could you please guide me how I can restore my smartphone from that.
can you flash it through adb sideload fastboot twrp etc
I don't know but I sold the device. I bought a new one. Thanks @Raggaov for the help.
you're welcome