Related
ADVICE, THIS IS A HARD HOW-TO AND YOU LOST ALL DATA ON YOUR DEVICE, THE RISK OF BRICK IS LOWWelcome to a V1 Version of th tutorial for convert the Single-SIM to Dual-SIM on Huawei P10+, based on experience of Huawei P9 Lite and researching for Huawei P10/P10+/Mate9
Requirements:
Pacience, more, more, pacience
BOOTLOADER Unlocked
Custom Recovery
Have a Unlock CODE (its needed for re-unlock the bootloader, for any mistake the bootloader relock after this how-to)
READ ALL HOW-TO
How-To:
First download the L29 ROM: THERE
Download OEMINFO DualSIM.zip from THERE
Download the Custom eRecovery without online comprobation of Firmware/Version of device (this can open the possibility of install any ROM for this Device with 3 Buttons of VKY-) : THERE
Copy the ROM of the L29, in External SD in the HWOTA folder, entire .zip files downloaded previusly
Extract .zip OEMINFO file and go to External SD TWRP/Backups/NUMEROSERIENUESTRODISPOSITIVO/ *and copy in this the folder of DualSIM*
Backup all data with Huawei Backup Utility
Reboot in RECOVERY and Backup all data
In recovery go to "restore" and select: VKY-L29C432DualSIM
Via Fastboot flash the erecoverycustom.img file with this commands:
fastboot flash recovery erecoverycustom.img
fastboot flash recovery2 erecoverycustom.img
REINSTALL Firmware (L29C432):
With the ROM on HWOTA of External SD Card
PowerOFF the device
Press simultanius VOL+, VOL- and POWER, you see the installation process, release the buttons
After the REINSTALATION, in SETTINGS, before Wi-Fi you seed "Setting Dual-Card" this is the important, its de Magic MENU! all finished
AVOID DONT RESTORE FROM RECOVERY BACKUP O YOU LOST ALL RELATED WITH DUAL-SIM
Only restore with the Huawei Backup app.
REGARDS!!
Thanks for the guide, but can anyone please explain the benefit in performing such a hack, for a phone to 'think' its another model if it doesn't have all the same features as the one it is imitating?
RoOSTA
Link for L29 ROM for convert to DUAL-SIM uploaded: https://mega.nz/#!dQ1XjTLR!c4bOE-GUs25WvLfb89VKXOwFJT5DqEX6wq7idOI-JBE
roosta said:
Thanks for the guide, but can anyone please explain the benefit in performing such a hack, for a phone to 'think' its another model if it doesn't have all the same features as the one it is imitating?
RoOSTA
Click to expand...
Click to collapse
The benefit is that it BECOMES dual SIM as it is only disabled in software not hardware.
---------- Post added at 03:42 PM ---------- Previous post was at 03:32 PM ----------
Great you have posted this How To BadWolfYe - only bits i am not sure of are the 'unlock boto loader' as see no instructions for this (unless i am being completely dim, which is possible!) and where to find an unlock code in case we need to relock the bootloader... or do we have to re-lock it after to get OTA? Actually if we do get OTA will be get the dual or single SIM OTA once upgradng to this?
Thank you for the guide.
Will it work for the P10 also?
Thank you
ioannis
Has anyone got this to work? This is my first Hauwei device so I wasn't 100% sure how to complete some of the steps. What I have a the moment is a phone that reports as having 2GB of RAM, 16GB of storage space and running Android 5.1. Could anyone please expand on this guide or let me know where I went wrong?
Okay, I don't really know how I managed to do it but I've managed to change the software of my L09 to that of an L29 and it works fine. So thanks for this guide.
After stumbling through this guide I ended up with a device that had some weird software with ndr90m test keys (whatever that means0. However he Dual SIM worked. So then I followed the guide from here with the firmware from this post and now I have phone that correctly (or should that be incorrectly as strictly speaking it was originally an L09) identifies a P10 Plus L29.
dave852 said:
Okay, I don't really know how I managed to do it but I've managed to change the software of my L09 to that of an L29 and it works fine. So thanks for this guide.
After stumbling through this guide I ended up with a device that had some weird software with ndr90m test keys (whatever that means0. However he Dual SIM worked. So then I followed the guide from here with the firmware from this post and now I have phone that correctly (or should that be incorrectly as strictly speaking it was originally an L09) identifies a P10 Plus L29.
Click to expand...
Click to collapse
Which one of the guides did you follow on that page? First or second?
Also... Just to confirm that all you did was use the 29 rom from here rather than the 09 from there?
Plus (sorry for all questions).... Your second sim now works ok?
Thanks
Adam
Sent from my VKY-L09 using Tapatalk
Hi all,
First of all: BadWolfYe! Thank you the guide!
So yesterday I got my new P10 plus, but I became really upset when I realized it is only one SIM version, so decided to make it 2
But!
OK, I did not do anything like this in the last few years, but I am not totally amateur. But I had problem wit it...
I did everything as written.
I restored the VKY-L29C432DualSIM and now I do not know what to do...
I know, next point, but my pc doesn't recognize the phone. And ADB doesn't either.
When I turn it on, it goes to Huawei erecovery, wants wifi and download something to recover.
It was TWRP recovery before on it, but it seems it disappeared after VKY-L29C432DualSIM...
Unfortunately I had to come to work, so could not play with it and to be honest I am too tired after this to think clearly.
Does anybody know how can I do the next step? (Via Fastboot flash the erecoverycustom.img file with this commands
Thanks.
adamelphick said:
Which one of the guides did you follow on that page? First or second?
Also... Just to confirm that all you did was use the 29 rom from here rather than the 09 from there?
Plus (sorry for all questions).... Your second sim now works ok?
Thanks
Adam
Sent from my VKY-L09 using Tapatalk
Click to expand...
Click to collapse
I used method 1 and the 29 ROM from here.
---------- Post added at 07:38 PM ---------- Previous post was at 06:57 PM ----------
I'll attempt a guide here that's maybe not the quickest way of doing it but it's the way that works for me. The guide also assumes you can manage to download a quick adb setup and use adb from the command line. Bear in mind that BadWolfYe has written guides on what I'm about to cover below and that's how I learnt. TWRP install by BadWolfYe.
0) Take working L09 phone and bootloader unlock code (I put the details of my phone into the Huawei website and got a code in return)
1) Enable developer options by going to Settings>About phone and tapping 'Build number' a bunch of times until it says you have enabled developer options.
2)Now go to Settings>Developer options and select 'enable OEM unlock'. Also enable USB debugging and ADB etc.
3)Download and rename twrp to twrp.img from the link in the BadWolfYe thread here
4)ADB reboot bootloader' from the command line and enter 'fastboot flash recovery twrp.img'
5)Press and hold volume up and power until you are in TWRP and then back up your OEM partition. (if you can't get into TWRP then you may need to repeat step 4 and also do 'fastboot flash recovery2 twrp.img).
6)Use the File manager in TWRP to replace the OEM files with files from the zip file download link in this thread above.
7)Restore OEM partition and then use the Shutdown option in TWRP.
8)Download the ROM from above This BadWolfYe link and unzip to find 3 files.
9)Place files in a folder called HWOTA on a microSD card and place card into phone
10) Download this file from this guide and extract to your computers hard drive.
11) run update.bat from that extracted contents as an administrator and follow the on screen instructions. The on screen instructions basically take you through from step four on the stechguide.com method 1 through to the end of the guide. I think I remember you get some options and I just use option 1 twice, from SD card and not rebrand.
If you can follow the guides they should work fine and you'll end up with a completely stock dual SIM phone with a locked bootloader.
From that point on I unlock the bootloader on mine again, install TWRP again and use it to flash Magisk 12 for root. Using root and Titanium Backup I restore my old device ID and a bunch of apps and settings and things are fine. However on the next reboot the launcher refuses to run and I'm left with an unusable phone (I don't know how to launch apps without the launcher) and I get error messages about running short of space as something has filled the internal memory with what appears to be junk files. I then start from step 8 in my guide and get a phone with a locked bootloader and no root but the device ID I want and all my apps and data.
If someone could offer me any help with regards to this last part I'd be grateful. I don't understand what causes the launcher issue.
Fixed...
Device ID, I think same - unfortunately my PC was stupid (nooo, not me) and I make the note in it so I lost it
2 SIM works - however only EE ones so the phone is locked. (Testing the online unlock code sellers )
Bootloader locked
Met "ndr90m test keys" as dave852, but hes linked page and 1. method helped. Oh, and could not install L29 ROM with volume + - and power, only with the linked method. I think that method could do everything after you opened bootloader, but will not test it. I am happy with my L29
But the important, there is a way to make L29 from L09
resch13 said:
Fixed...
Device ID, I think same - unfortunately my PC was stupid (nooo, not me) and I make the note in it so I lost it
2 SIM works - however only EE ones so the phone is locked. (Testing the online unlock code sellers )
Bootloader locked
Met "ndr90m test keys" as dave852, but hes linked page and 1. method helped. Oh, and could not install L29 ROM with volume + - and power, only with the linked method. I think that method could do everything after you opened bootloader, but will not test it. I am happy with my L29
But the important, there is a way to make L29 from L09
Click to expand...
Click to collapse
I would guess it would be possible using the files from the OEM backup you made (if you kept them) and a downloaded L09 ROM (available in a few places) but I'm not 100% sure and I'm not going to try it.
dave852 said:
I would guess it would be possible using the files from the OEM backup you made (if you kept them) and a downloaded L09 ROM (available in a few places) but I'm not 100% sure and I'm not going to try it.
Click to expand...
Click to collapse
No, I have not any backup. I forgot to made any so I am lucky that I did not need it
I somehow managed to convert my single sim to dual-sim but unfortunately i cannot modify nor set any ringtone to the 2nd sim. Any ideas of how i can fix it ?
LOL. I gave this several attempts, alas, without success. I kept ending up with the test keys / strange device ID (ION something).
So I decided to skip my rebranding attempt and go back to L09. After "rebranding" it to L09 again and after flashing B130 for L09 I ended up with dual SIM support anyway. Eveything seems to be checking out as far as I can tell. Not sure if OTA will work though, time will tell I guess. Safety net etc. also checks out.
The options for dual SIM are showing and I've tested it. Everything just works.
Can anyone confirm that after enabling the second SIM slot that their phone now has 2 x IMEI numbers?
I just recently purchased p10 plus . for 3days the Fone was working fine both sims 3/virgin then suddenly emergency calls only on 2nd sim. I tried to deactivate activate ect ect . until I lost both sims. Soft hard reset sim 1/working sim2 emergency calls only. If I swap the sims around in the tray same issue . then with only one sim either 3/virgin full teceotuin if I make or receive a call after the call I have no reception I wil l need to swap the sim from tray1 to tray 2 . and the funny thing is both sims will receive and send texts all day long with no issues
Any ideas
Thanks in advance
Has anybody done this and checked warranty status in Huawei Hi Care app?
I can confirm this works 100%. Dualsim working. Serial, imei all still the same. Recovery back to original too
Sent from my VKY-L29 using Tapatalk
Hello and THX for the HowTo whch worked well!!!
My Phone is shoing that there is an update (VKY-L29C432B133-FULL 2.76GB) which i try to install via the regular updater, however the updates always failes. I already installed the default recovery image.
Any Idears?
ERROR: Package Checksum
... Never mind - it was a network error on my e1000 :fingers-crossed:
This is the official FunkyHuawei support thread.
FunkyHuawei is a (mostly) paid service which allows you to do the following:
1. Install the latest system software, even before it's released by OTA.
2. Install beta/prerelease system software, without needing to be a beta tester.
3. Recover a bricked phone.
4. Rebranding / Change the region of your phone (China -> Europe, for example, to get Google and so on.)
5. Root your EMUI 8 phone, even with stock recovery (This feature is free)
Except for rooting, all of these features are supported even if you cannot unlock your phone's bootloader.
We are pleased to announce FHUnbrickFlashTool -- You can now repair any recent Huawei phone via fastboot, even if you cannot access eRecovery or boot the phone! Even if it doesn't show the Huawei logo, as long as you can get a fastboot connection to your computer, you can recover the phone! Google FHUnbrickFlashTool or check FunkyHuawei's reddit for details.
To find FunkyHuawei, please Google it. Or you can find a link to the service within the following XDA Portal article.
https://www.xda-developers.com/android-oreo-emui-6-huawei-mate-9/
In cooperation with XDA, FunkyHuawei is offering a free credit to Recognized Developers and Recognized Contributers on XDA.
Please PM me for more details.
We will continue posting in this thread with updates regarding new software versions and releases regarding this device.
We will also be monitoring it so we can help anyone who has issues.
For device-specific information, please see the next post.
P10 Plus Device-Specific Information
The P10 Plus now has a relatively mature community with many methods to do many things.
However, there are still some things only possible with FunkyHuawei, so it would be most useful for:
1. Installing updates on bootloader-locked devices, even if the update is not approved by Huawei for your device.
2. Rebranding bootloader-locked devices, or rebranding to obscure carrier brandings.
3. Restoring bricked devices.
Note that even though the Mate 10 Root tool is designed for the Mate 10, it works perfectly on the P10 Plus running Android O betas.
This tool is FREE, and might be easier than installing TWRP and rooting that way.
Frequently Asked Questions
Q: How much does FunkyHuawei cost?
A: You need to buy credits on the FunkyHuawei website. The price per credit varies depending on the number of credits you buy. Different operations cost different amounts of credits. However, the Root feature of the Mate 10 tool is free, and as mentioned above, Recognized Developers/Contributors of XDA can ask for a free credit.
Q: My phone is bootloader locked, and FRP locked. My bootloader unlock code dosen't work. It won't boot. eRecovery doesn't work. Can you help?
A: Yes. With the Mate 10 this is now a common situation. Contact FunkyHuawei for help in this situation. We'll need to access your computer remotely and the procedure is a little bit complicated, but the phone can be unbricked.
Q: I can't get my bootloader unlock code/don't want to unlock my bootloader, but I want to change my phone to something other than Chinese. Can you help?
A: Yes. Our new FunkyHuawei Rebrand Tool works on ALL recent Huawei phones, to rebrand them to another region even when the bootloader is locked.
Q: I'm not seeing the latest version listed on FunkyHuawei or elsewhere as an OTA. Why not?
A: Huawei has a very odd and unpredictable way of rolling out OTA updates. You can use FunkyHuawei to install the new version immediately, or can wait for the update to be rolled out. It might be a month or more after release until the update reaches your device from Huawei directly. We have no idea why.
Q: Why isn't FunkyHuawei free?
A: Because many of FunkyHuawei's features cost FunkyHuawei money to provide. Features that don't cost FunkyHuawei money to provide, like rooting the Mate 10 or our TWRP build for Mate 9/Oreo, for example, are generally made available for free. There are also bills to pay, kids to put through school, and so on.
Q: I noticed FunkyHuawei in an XDA Portal article!
A: FunkyHuawei loves XDA, and is cooperating with them as much as possible. Recognized Developers and Contributors on the XDA forums are welcome to claim a free credit from FunkyHuawei as well.
Q: I have a different question.
A: This is what this thread is for! Post away!
I thought "official" FunkyHuawei threads violated XDa's terms an conditions due it being a paid service?
VKY-L29C432B177 coming. Changes are addition of VoLTE and VoWifi (carrier dependent).
Will be available on FunkyHuawei shortly.
UPDATE: Available now.
P10 plus stuck on fastboot. Black screen, no led.
Follow the rebranding manual result in brand new p10+ hard bricked.
Now the pone is completly dead black screen, no led when plugs the usb, no vibration. I had lost all hope until after it stayed connected for a long time to the pc I realized that windows was detecting somthing.
adb doesn't detect the device but fastboot detecs it.
I have tried to reboot in bootloader or flashing recovery without success. The commads apparently work and end with ok but after a reset the phone only load in fastboot mode without any other life signals. Bootloader is unlocked.
is there any solution to fix this?
Elinexsa said:
Follow the rebranding manual result in brand new p10+ hard bricked.
Now the pone is completly dead black screen, no led when plugs the usb, no vibration. I had lost all hope until after it stayed connected for a long time to the pc I realized that windows was detecting somthing.
adb doesn't detect the device but fastboot detecs it.
I have tried to reboot in bootloader or flashing recovery without success. The commads apparently work and end with ok but after a reset the phone only load in fastboot mode without any other life signals. Bootloader is unlocked.
is there any solution to fix this?
Click to expand...
Click to collapse
Based on the email we received from you, it looks like you didn't use our service to rebrand.
Still, we can help you unbrick it if you have this situation, as long as you can access fastboot.
We are pleased to announce FHUnbrickFlashTool -- You can now repair any recent Huawei phone via fastboot, even if you cannot access eRecovery or boot the phone! Even if it doesn't show the Huawei logo, as long as you can get a fastboot connection to your computer, you can recover the phone! Google FHUnbrickFlashTool or check FunkyHuawei's reddit for details.
We now have Android O for International P10 and P10 Plus.
Check FunkyHuawei reddit for install instructions, or google for "Android O Builds for International P10 and P10 Plus now available! Instructions inside"
duraaraa said:
We are pleased to announce FHUnbrickFlashTool -- You can now repair any recent Huawei phone via fastboot, even if you cannot access eRecovery or boot the phone! Even if it doesn't show the Huawei logo, as long as you can get a fastboot connection to your computer, you can recover the phone! Google FHUnbrickFlashTool or check FunkyHuawei's reddit for details.
Click to expand...
Click to collapse
Thanks to this tool I could revive my P10+
It works like a charm
Thank you!
will i be able receive and install ota updates if i root my device and have twrp installed
I backed up my device using TWRP, I excluded the data partition since it is not working in TWRP. After I restored my device my bootanimation changed from Huawei animation to an "android" logo and when the device booted, I tried to open settings and the app instantly closes and same with the camera app. The camera app shows the name com.huawei.camera instead of saying "Camera" and all other apps started crashing. So, I wiped everything except my internal storage and restored my backup and now when I boot the device everything is black and I can only see the navigation keys and when I hold my power button I can see the restart and power off option. After like 2-3 minutes I get this message "You have run out of storage space" and when I press ok it takes me to a screen which shows 64/64 GB used. I have 0 space left on device
ajituchiha said:
I backed up my device using TWRP, I excluded the data partition since it is not working in TWRP. After I restored my device my bootanimation changed from Huawei animation to an "android" logo and when the device booted, I tried to open settings and the app instantly closes and same with the camera app. The camera app shows the name com.huawei.camera instead of saying "Camera" and all other apps started crashing. So, I wiped everything except my internal storage and restored my backup and now when I boot the device everything is black and I can only see the navigation keys and when I hold my power button I can see the restart and power off option. After like 2-3 minutes I get this message "You have run out of storage space" and when I press ok it takes me to a screen which shows 64/64 GB used. I have 0 space left on device
Click to expand...
Click to collapse
You can probably recover by using FHUnbrickFlashTool. If you contact FunkyHuawei support we can ask you for some more information to confirm exactly what the problem is.
Good work. I'll be more impressed when we finally work out a systemless root, i've lost count of the many OTA updates from Huawei - meaning their OS must be full of bugs and glitches for commonly used apps and typical use. Will we ever get there?
RoOSTA
Do not use this service. SCAM!
Warning !!!ALP-L29 C636 users should avoid updating or rebranding to ALP-L29C636B134 firmware, dated 16/04.And if they already updated, to stay on that firmware (at least for now).
BLA-L29 C636 users should avoid updating or rebranding to BLA-L29C636B137 firmware, dated 16/04.And if they already updated, to stay on that firmware (at least for now).
Please also read this thread made by @ante0 - >https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241 <- you will also find a tool that will help you check the xloader.img
Considering that lately there were quite a few hard-bricks, i invite the users that experienced such bricks to post more details here.
Please use this model when you post :
1) Device = device codename (BLA-L29, ALP-L29, etc)
2) Firmware and Region before Brick = exact firmware and region (B134 C636, B141 C432)
3) Firmware that lead to brick = The firmware version that lead to bricking
4) You were trying to just update your device or you were also trying to rebrand
5) Your device was rebranded or used stock region?
6) Other infos of modifications, update procedures, etc that you did before bricking
Thank you and please stay on topic!
ALP29-C636 on B129 (I believe). Just wanted to update to B134 (non-noxloader) and get face unlock. No rebranding. Tried it with HurUpdater first (which I had never used before). Had TWRP 0.3 installed and included it as a recovery.img when flashing. Ended up in a boot loop, so I turned off and entered download mode and went back to mankindtw's tools. But, thinking maybe something was wrong with my B134 download, I downloaded and repacked B134 noxloader this time around. The update all went well, including exiting out of the final CMD window, but then, in the automatic reboot, the phone just died.
1) ALP-L29
2) Worked just fine with ALP-L29C636B134
3) ALP-L29C636B135
4) update with HWOTA8_Mate10
5) Original ALP-AL00C00 rebranded to ALP-L29
6) nothing else
But I do remember one strange thing, when I updated to ALP-L29C636B134. The zip files I downloaded from hicloud, the repack.bat told me they already were repacked even though I did not do it, yet it updated just fine.
Then the ALP-L29C636B135 zips repacked as usual, and after that I updated with ota.bat and it bricked.
erzbengel said:
1) ALP-L29
2) Worked just fine with ALP-L29C636B134
3) ALP-L29C636B135
4) update with HWOTA8_Mate10
5) Original ALP-AL00C00 rebranded to ALP-L29
6) nothing else
But I do remember one strange thing, when I updated to ALP-L29C636B134. The zip files I downloaded from hicloud, the repack.bat told me they already were repacked even though I did not do it, yet it updated just fine.
Then the ALP-L29C636B135 zips repacked as usual, and after that I updated with ota.bat and it bricked.
Click to expand...
Click to collapse
134 with or without the noxloader version attached to the name??
royhanks3 said:
134 with or without the noxloader version attached to the name??
Click to expand...
Click to collapse
Without the noxloader.
erzbengel said:
Without the noxloader.
Click to expand...
Click to collapse
When I flashed 135 without repacking it flashed fine. Maybe there's an issue with repacking the latest roms and flashing then on our devices
Sent from my ALP-L29 using Tapatalk
) Device = ALPL29
2) Firmware C636B134
3) Firmware that lead to brick C636B134 NO XLOADER
4) Just trying to update wanted to see what the difference was
5) Stock region
6) Just followed HWOTA10 instructions repacked install complete 100% then it rebooted then it took me to the black screen
I sent it back to huawei and they gave me a brand new device but this time i will just be installing magisk
1) Device = BLA-L29
2) Firmware and Region before Brick = B137 C636
3) Firmware that lead to brick = B141 noxloader C432
4) Rebrand
5) My device was rebranded from stock BLA-L09 C34 to L29 C636
6) Just follow HWOTA8's guide. The process was no problem. But after reboot, my phone turned to black screen. It was totally dead.
1- device= bla-l29
2- c636 137
3- i use 2 weak c636 137 i use hwota update to 138 and now brick
4- rebrand and update only hwota for mate 10
5- my orjinal phone bla-al00
6- only use hwota update c636 138 and now brick my phone. Now my phone Black Scren and pc device manager see usb ser.
I use dc phonix al00 board software but not install bootloader.
http://www.imgim.com/68incib2496565.jpg
ooemir said:
1- device= bla-l29
2- c636 137
3- i use 2 weak c636 137 i use hwota update to 138 and now brick
4- rebrand and update only hwota for mate 10
5- my orjinal phone bla-al00
6- only use hwota update c636 138 and now brick my phone. Now my phone Black Scren and pc device manager see usb ser.
I use dc phonix al00 board software but not install bootloader.
http://www.imgim.com/68incib2496565.jpg
Click to expand...
Click to collapse
DC Phoenix or HDE Flasher is used to flash the Board Firmware. But in the case of mate 10 with latest firmware bricked phones, DC Phoenix and HDE Flasher are not capable to flash the Board Firmware even the phone is detected as HUAWEI USB COM 1.0 . So for all those who are trying to install the latest and pre-release builds should avoid this to let their phones alive.
PS: The developers should look into the latest firmware what is causing hard bricks.
Regards
k4fari said:
DC Phoenix or HDE Flasher is used to flash the Board Firmware. But in the case of mate 10 with latest firmware bricked phones, DC Phoenix and HDE Flasher are not capable to flash the Board Firmware even the phone is detected as HUAWEI USB COM 1.0 . So for all those who are trying to install the latest and pre-release builds should avoid this to let their phones alive.
PS: The developers should look into the latest firmware what is causing hard bricks.
Regards
Click to expand...
Click to collapse
This means that Phoenix can't use its "backdoor" anymore.
When phone is bricked DC flashes in factory mode (USB COM 1.0) while backdoor is used in fastboot mode.
k4fari said:
When phone is bricked DC flashes in factory mode (USB COM 1.0) while backdoor is used in fastboot mode.
Click to expand...
Click to collapse
This means USB COM 1.0 is useless without actually connecting the test points, which unfortunately are not available for Mate 10.
1- bla-l29
2- c636 142
3- /////////c432 142///////////
4- update packing instally %50 closed on screen
5- my orjinal phone bla-l29 so rebrand
6- device manager see usb ser.
Pretoriano80 said:
This means USB COM 1.0 is useless without actually connecting the test points, which unfortunately are not available for Mate 10.
Click to expand...
Click to collapse
No, you are not getting the point. The hard bricked phones having no connectivity with Pc need test points, i.e to detect phone as Huawei USB Com 1.0 known as Factory Mode.
HUAWEI Phones have 3 flashing modes: i.e., 1)Fastboot mode, 2) Upgrade Mode (by pressing vol +, vol- and pluging in usb cable), and 3) Factory Mode (Usb Com 1.0).
To flash board firmware phone must be detected in any of three modes . The phone which is already detected and visible as USB SER in Pc doesn't need any test points. USB SER drivers are available to put phone in USB Com 1.0 (factory mode).
The main issue is flashing board firmware as new firmware installation via HWOTA or other HrUpdater are hard bricking the phones. Even though the phone is detect-able as Factory Mode without disassembly and test points , DC Phoenix is unable to flash board firmware.
Hope many things and points are now clear to many of the readers.
did anyone solve the black screen problem ? (hard bric)
how long will we wait
ooemir said:
did anyone solve the black screen problem ? (hard bric)
how long will we wait
Click to expand...
Click to collapse
In all honesty, I do not think we'll be able to solve this issue on our own. The latest updates are seemingly removing the bootloader, or access to it which means we currently don't have the necessary tools to flash board software to the device. More people need to either complain or contact Huawei so we can all get this solved as a community.
Sent from my ALP-L29 using Tapatalk
k4fari said:
No, you are not getting the point. The hard bricked phones having no connectivity with Pc need test points, i.e to detect phone as Huawei USB Com 1.0 known as Factory Mode.
HUAWEI Phones have 3 flashing modes: i.e., 1)Fastboot mode, 2) Upgrade Mode (by pressing vol +, vol- and pluging in usb cable), and 3) Factory Mode (Usb Com 1.0).
To flash board firmware phone must be detected in any of three modes . The phone which is already detected and visible as USB SER in Pc doesn't need any test points. USB SER drivers are available to put phone in USB Com 1.0 (factory mode).
The main issue is flashing board firmware as new firmware installation via HWOTA or other HrUpdater are hard bricking the phones. Even though the phone is detect-able as Factory Mode without disassembly and test points , DC Phoenix is unable to flash board firmware.
Hope many things and points are now clear to many of the readers.
Click to expand...
Click to collapse
I know how Phoenix work, that's why i said that maybe you still need to actually connect test points. The fact that USB Com is available without test points doesn't mean you will be able to flash the board software.And the fact that it doesn't work with kirin970 proves it.
Clearly, these bricks are not hardware failures so if Phoenix cannot flash it in USB Com mode, makes me think that:
1) Test points are needed no matter the port is showing or not
2) Something is wrong with GPT
3) Kirin970 works differently and Phoenix doesn't work in USB Com mode
These are only speculations, obviously.
What Phoenix guys told you when you talked to them, they have any idea why their tool fails?
And regarding to the purpose of this thread, so far my opinion is that the culprits are the firmwares from 16/04 , no the "noxloader" ones. Here's my examples based on the info I've got about these bricks.
1) B132C636 - > B134(noxloader) C636 - > B135 C636 = no brick
2) B132C636 - > B134C636 (16/04)-> B135 C636 = brick
3)B132636 - > B134C636 (16/04) - > B134(noxloader) C636 = brick
So far the only common point (beside C636 brand) is that all those that bricked, at some point they updated to a firmware from 16/04/2018.
Pretoriano80 said:
And regarding to the purpose of this thread, so far my opinion is that the culprits are the firmwares from 16/04 , no the "noxloader" ones. Here's my examples based on the info I've got about these bricks.
1) B132C636 - > B134(noxloader) C636 - > B135 C636 = no brick
2) B132C636 - > B134C636 (16/04)-> B135 C636 = brick
3)B132636 - > B134C636 (16/04) - > B134(noxloader) C636 = brick
So far the only common point (beside C636 brand) is that all those that bricked, at some point they updated to a firmware from 16/04/2018.
Click to expand...
Click to collapse
The support team of Phoenix has clearly said that they dont know whats the issue with their tool and can not give any time frame to make Phoenix working with Mate 10 Board Firmware. Further more , i was on C636B312, i updated to B134 noxloader , Phone was showing NRD90-test , i downgraded to B132 and phone gone dead (black screen i.e USB SER)
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
Damn, it's been a while since I was here. Back then it was mostly about Windows PDAs.
Disclaimer:
Your warranty after this process is void and your phone will tell you it can not be trusted because it's unlocked.
This is what worked for me. I did it on Windows 10. I just went through the process and it was a bit of mixing and matching various guides.
I'm not your tech support, the only one responsible for following this is you.
If any part of this guide doesn't work for you: too bad. Maybe Google or other users can help you with your problem.
Needed:
An internet-enabled PC
Huawei P10 Lite phone
USB to Micro-USB cable
HiSuite https://consumer.huawei.com/en/support/hisuite/
DC-Unlocker (comes with abd & fastboot) https://www.dc-unlocker.com/
Optional: Huawei Driver Tools https://mega.nz/file/qrpBUIKA#zaI8Th0ovgyK48VzFUFAzMNWF2r_R12lNc-uJZsIx4w
Note: I recommend not to buy credits until you've come to the part in my guide which says buy credits.
Install HiSuite
Unzip and install HiSuite on your PC
Start it at the end of the installation (it should show a button with "Start")
Connect the phone to your computer with the USB cable and follow the instructions in HiSuite to install HiSuite on your phone
At the bottom of the (Windows) HiSuite there's an option to do a System Upgrade, mine had the option to install an older version (Android 7 with EMUI 5.1) Install this. (This will take some time)
Note: I've read that some people couldn't downgrade because of modern security fixes. It's possible I didn't run the latest updates, but as far as I'm aware everything was up to date.
The following part might be annoying because HiSuite tries to connect to the phone. I uninstalled it at this point, but I had the Driver Tools installed (and did the Install within said tools).
Phone
Once the phone restarted, go through the set-up as quickly as possible (skip WiFi-setup, decline all optional things and skip account creation)
Go to Settings > System > About Phone > Keep tapping the "Build Number" until you're told you're a developer
Find the developer options (Usually in Settings > System and enable USB/ADB debugging
Open the telephone app and type: *#*#2846579#*#* (it should open a menu automatically after the last *)
Click Background Settings > USB Port Settings and select Manufacture Mode
Once Manufacture Mode is selected, leave the phone untouched
DC-Unlocker, part 1
Unzip the contents of the DC-unlocker zip
Start dc-unlocker2client.exe
In the top left, under "Select manufacturer" change "Huawei modems" to "Huawei phones"
Click the button with the magnifying glass, if you did the previous step hovering should say "Detect phone" on hover
Example out put (this might differ for you, but triple-check a port is detected):
Code:
DC - Unlocker 2 Client 1.00.1431
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM3
Model : Huawei HiSilicon Kirin Android phone
Serial NR. : [redacted]
Firmware : System 5.1.0.78(0VVV)
DC-Unlocker, part 2
Check again if a model and port is shown in both the output and above the big buttons.
In the top right, click About > Buy Credits
DC-Unlocker site
Select your payment processor
By default it creates a new account, unless you've used this service before, you probably want to keep it this way.
Fill in a username and an email address
You need 4 credits (€4 for me) at the time of writing this, but do check the link "How much do I need?"
Hit confirm and go through the payment process, wait until everything is processed (if you use a script blocker, you might want to temporarily disable it).
At the end you should get confirmation page with your username, a password and 4 credits. (Username and password will be mailed too.)
DC-Unlocker, part 3
Go back to DC-Unlocker
In the top right, click "Server" and enter the details you've gotten
Click "Check login" and see if the output window shows your username and the credits you have left (which should be 4 at the time of writing)
In the top right, click "Unlocking" and then click "Read bootloader code"
The output should show you the bootloader code once it's done. Copy this to a textfile and save it (and keep it in the memory).
You can close DC unlocker once you've saved the code.
Don't be lazy and try to copy/paste the commands following in the next section, since you want to keep the code in your memory, as seen in step 6. Besides, I'll show you some shortcuts anyway! Keep in mind that our example code is 1111222233334444 (yours most likely isn't, mine sure wasn't) and that [tab] will mean the tab-key on your keyboard.
PowerShell/Command Prompt
In the folder where you unzipped dc-unlocker2client.exe to, press [shift] on your keyboard and hold it while right-clicking in an empty area underneath the files, then click "Open PowerShell (or command prompt) here".
Whatever command-line you started will open, type ad[tab] and adb.exe should be appear (shows up as .\adb.exe in PowerShell)
Follow this by typing reboot bootloader. So it should show as
Code:
./adb.exe reboot bootloader
(no ./ in command prompt)
Hit [enter] and the phone should reboot to a screen with a white background
Once the bootloader screen shows (white background with the android mascot) type fast[tab] in PowerShell/Command prompt and follow it up by oem unlock[space]
If you still have the bootloader code in memory, right-click in PowerShell/Command prompt to paste it. Your entire line should be
Code:
./fastboot.exe oem unlock 1111222233334444
Hit [enter], the unlocking will start and factory reset your phone. My output was:
Code:
(bootloader) The device will reboot and do factory reset...
OKAY [ 10.330s]
If everything went right you'll see the Huawei/Android bootscreen and then a warning that the phone is "unlocked and can not be trusted" to use or something like that. It'll boot into the OS after that.
I'd like to remind you of the disclaimers at the top, but hopefully this will help some of you going through the process.
Edits
Forgot about USB debugging
Added the warning you get after a successful unlock
Changed the build number tapping sentence
Rewrote a sentence for clarity
Very nice guide, if ppl ask about unlocking we just link this from now on...
This is a very helpful guide, thank you so much! My question is, if I wanted to flash twrp when the bootloader is unlocked, is there a way to upgrade it to Oreo once again without locking the bootloader again? I can't seem to find a twrp tutorial where they use Nougat/Emui 5 to flash twrp, and all the tutorials to upgrade to Oreo/Emui 8 look like they're locking the bootloader once again and I don't really want to waste 4 euros to go back to the start.
A bootloader unlock should be permanent? I've been moving between Android 7 (EMUI 5), Android 8 (Emui 8) and Android 10 myself in all kinds of directions.
Besides, I think the code is tied to your device, so you should be able to use it again. (But I'm not sure about this!)
Syrion said:
A bootloader unlock should be permanent? I've been moving between Android 7 (EMUI 5), Android 8 (Emui 8) and Android 10 myself in all kinds of directions.
Besides, I think the code is tied to your device, so you should be able to use it again. (But I'm not sure about this!)
Click to expand...
Click to collapse
Thank you for your quick reply! So after the bootloader unlock, did you flash twrp on Android 7? or did you upgrade your phone to Android 8 and flash twrp then? How did you manage to upgrade it to Android 8?
I really appreciate your help with the previous tutorial, I've done everything until the buy credits part (I'm waiting a bit for that part) and I'm planning on getting to the end of the tutorial at least before August. My idea is to upgrade to Android 8 + flash twrp and Magisk, hopefully I'll be able to do all of that!
I did the above procedure on an up to date, official stock Huawei android. Both EMUI & Android are 8. I'm in the Netherlands, so it'should be the same model as in Spain. (WAS-LX1A)
The HiSuite step is to downgrade from EMUI 8 (Android 8) to EMUI 5 (Android 7), since that seems to have less securities to make it easier to unlock the bootloader.
Oh, I understand now! One more question (sorry if I'm being annoying, it's my first time playing with a Huawei, I must say that Samsungs are far easier to root/unlock lol): If I follow your method, but after getting the bootloader unlock code and right before unlocking the bootloader, I use HiSuite to upgrade back to Android 8/Emui 8, would the procedure be fine? like, it's totally fine to unlock the bootloader either with android 7 or 8, the only time I need android 7 is to get my code because DC unlocker supports them better, right?
Again, thank you so much!!!
I'm not sure to be honest. But I reverted to 7/EMUI 5 because I read around here on the board that's better for trying to unlock.
Thank you,
Only fastboot.exe oem unlock xxxxx failed with the following error: FAILED (remote: Command not allowed)
finished. total time: 0.022s
This was resolved by going back to settings, developer options and check 'enable oem unlocking'. I didn't read that in your guide.
Syrion said:
I did the above procedure on an up to date, official stock Huawei android. Both EMUI & Android are 8. I'm in the Netherlands, so it'should be the same model as in Spain. (WAS-LX1A)
The HiSuite step is to downgrade from EMUI 8 (Android 8) to EMUI 5 (Android 7), since that seems to have less securities to make it easier to unlock the bootloader.
Click to expand...
Click to collapse
Hi, I have the same model. But I can't figure out how to update to EMUI8 again (or which custom recovery works). It doesn't find the update in HiSuite and it doesn't find it via System update. Do you happen to know how? Thank you.
What should I do next?
I did manage to unlock the bootloader thanks to this very clear post. I did downgrade to Android 7 / Emui 5.1.1 and have a working rooted system but he is trying to upgrade again to android 8 / Emui 8. I know by experience that it will lock again with the higher version (the unlock code can be used several time fortunately).
I did try to flash some roms on it, going for instance to Lineage OS 14 but it was all a disaster and I think that I need some guidance now..
I am not a newbee for rooting and flashing but do not understand yet the Huawei system; is that so that I have to choose a new ROM with caution, especially with the Emui version? Looking at the old posts, I find some old ROM's even with Emui 5 version but do not understand the path that I should follow to progressively upgrade.
Thanks in advance for your orientations!
Syrion said:
A bootloader unlock should be permanent? I've been moving between Android 7 (EMUI 5), Android 8 (Emui 8) and Android 10 myself in all kinds of directions.
Besides, I think the code is tied to your device, so you should be able to use it again. (But I'm not sure about this!)
Click to expand...
Click to collapse
For me, I did get to relock by accident but I confirm that the unlock code is permanent (at least, I did use it 3 times with no problem!)
P10 lite Pinout
I would like to know if they have tried to unlock the bootloader with the Pinout method.
Correcaminos604 said:
I did manage to unlock the bootloader thanks to this very clear post. I did downgrade to Android 7 / Emui 5.1.1 and have a working rooted system but he is trying to upgrade again to android 8 / Emui 8. I know by experience that it will lock again with the higher version (the unlock code can be used several time fortunately).
I did try to flash some roms on it, going for instance to Lineage OS 14 but it was all a disaster and I think that I need some guidance now..
I am not a newbee for rooting and flashing but do not understand yet the Huawei system; is that so that I have to choose a new ROM with caution, especially with the Emui version? Looking at the old posts, I find some old ROM's even with Emui 5 version but do not understand the path that I should follow to progressively upgrade.
Thanks in advance for your orientations!
Click to expand...
Click to collapse
I ran into the same problem. Did you find a solution?
I followed this guide, downgraded to EMUI 5.1.1 and tried to install several custom ROMs. But none of them will boot. It is always stuck on the splash screen with the "bootloader unlocked" warning and doesn't get any further.
I tried installing LineageOS 17.1, 15.1, and RR on Android 9 but no luck on any of these. Also, is it possible to revert back to the stock ROM? Maybe that will help...
Thank you all for any help
Nothing unfortunately, I did finally reinstall Android 7 with HWOTA https://www.******.com/huawei-hwota-tool-for-huawei-devices/ and managed to have a working Android 7 / Emui 5 that works perfectly if you do not forget to make a complete wipe/reset when rebooting. The bootloader is still unlocked.
Strange enough this system is upgradable through the normal update system (parameter/system/update) and keeps the unlocked bootloader. Today, I did upgrade to a very last built today - 394(C432) - without problem. Apparently I just have to re-root it through trwp.
I keep it like this now, finally, the Huawei system is not bad! and it is yet rooted
be-rty said:
I ran into the same problem. Did you find a solution?
I followed this guide, downgraded to EMUI 5.1.1 and tried to install several custom ROMs. But none of them will boot. It is always stuck on the splash screen with the "bootloader unlocked" warning and doesn't get any further.
I tried installing LineageOS 17.1, 15.1, and RR on Android 9 but no luck on any of these. Also, is it possible to revert back to the stock ROM? Maybe that will help...
Thank you all for any help
Click to expand...
Click to collapse
Correcaminos604 said:
Nothing unfortunately, I did finally reinstall Android 7 with HWOTA https://www.******.com/huawei-hwota-tool-for-huawei-devices/ and managed to have a working Android 7 / Emui 5 that works perfectly if you do not forget to make a complete wipe/reset when rebooting. The bootloader is still unlocked.
Strange enough this system is upgradable through the normal update system (parameter/system/update) and keeps the unlocked bootloader. Today, I did upgrade to a very last built today - 394(C432) - without problem. Apparently I just have to re-root it through trwp.
I keep it like this now, finally, the Huawei system is not bad! and it is yet rooted
Click to expand...
Click to collapse
Is 394(C432) finally coming as OTA? Back in July I had to download it via firmware finder and flash it with HWOTA after unlocking the bootloader... lol just to relock after updating... However even Huawei support didn't know about 394 and denied it would even exist, not too surprising in hindsight! Still eversince I was wondering if it ever comes as simple OTA, which indeed seems the case eventually!
Sent from my Google Pixel 3 XL using XDA Labs
Yes, WASLX1A 8.0.0.0394(C432) did arrive as OTA around the end of October. I was surprised as I did not expect any new update on this phone!
Sam Nakamura said:
Is 394(C432) finally coming as OTA? Back in July I had to download it via firmware finder and flash it with HWOTA after unlocking the bootloader... lol just to relock after updating... However even Huawei support didn't know about 394 and denied it would even exist, not too surprising in hindsight! Still eversince I was wondering if it ever comes as simple OTA, which indeed seems the case eventually!
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
DC-Unlocker can't find my phone
I followed your instructions, but when I click the magnifying glass on DC-unlocker it says
===================================================================
DC - Unlocker 2 Client 1.00.1431
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM6
===================================================================
But then nothing else is listed .....
My model is WAS-LX1
Correcaminos604 said:
Yes, WASLX1A 8.0.0.0394(C432) did arrive as OTA around the end of October. I was surprised as I did not expect any new update on this phone!
Click to expand...
Click to collapse
Yeah, it's actually crazy cool that it was patched after all this years, I however read it was primary updated to support the coronavirus warning App framework! That's actually the reason for Huawei to push another last update!
Sounds like a crazy conspiracy theory but was written on their Homepage...
Sent from my Google Pixel 3 XL using XDA Labs
Downgrade option doesn't exist for me in Hisuite. My phone is WAS-LX2 8.0.0.370(C185). The last update I got was on 13 February 2019 with the 2019 Feb security patches. Is there a free way to unlock bootloader?