Introduction
THIS METHOD IS NOT FREE. I HAVE NO IDEA HOW TO DO THIS FOR FREE, EXCEPT MAYBE WITH THIS : https://forum.dc-unlocker.com/forum/modems-and-phones/huawei/162196-free-hcu-license-offer
Oh my god. I just come out of 3 days of trying to get this to work, non-stop. I feel the need to write this guide so people in the exact same configuration as me won't have to go through what I did.
Yes there are many tutorials about unbricking your Honor 9, but few are very detailed, and I couldn't make them to work for my european STF-L09. Plus, very few of them have a solution for updating to the very latest version (9.1.0 as the time of writing). So here we go.
The device I did this with, and the situation I was in.
There are so many variants of the Honor 9, and I've tried tutorials that weren't the same model as me, they just wouldn't work.
Honor 9 STF-L09, Europe version, Kirin960.
Previous installed ROM before brick was Oreo (the Pie update I tried to make bricked the phone), but I think you can do that on any previous version.
After the brick, I had a completely dead Honor 9 : no reaction at all, whether I plugged it in or tried any buttons combination.
What you need
- The correct Drivers
- A HCU Client Timed License, which is 19 EUR for 72h, and is going to give you access to the main software we need, DC-Phoenix.
- The correct .dgtks Repair File
- The correct ROM file to flash
- HiSuite
- Tools to open the back of your phone
- A metal object to connect the testpoints (anything will do : tweezers, copper cable, paperclip, sim-tool...)
- Read these two tutorials from www.dc-unlocker.com :
https://www.dc-unlocker.com/dc-phoenix-flash-repair-tutorial
https://www.dc-unlocker.com/flash-bricked-huawei-phones-in-huawei-1-mode
Step 1 - Connect the testpoints
Then open the back of your phone to reveal the testpoints that you can see on the image below (thanks to the user 4r44444 for the picture).
Then, open the Device Manager on Windows, and reveal the COM and LPT Ports (so you can see if you failed at connecting the testpoints or not).
You don't need to connect the two testpoints shown in the picture : you only need to connect the bottom one with anything else that's metal inside the phone.
It will take you some trial and error but eventually, your Device Manager should refresh and show you an unknown device called "SER".
Step 2 - Install the drivers
First, install the latest version of HiSuite to get the basic drivers. Make sure to close it completely (taskbar) and disable the fact that it opens itself when you plug your phone, or it might screw things up.
Then, install the two drivers that are on both dc-unlocker.com tutorials I've linked above.
https://files.dc-unlocker.com/share.html?v=share/984CE114852148B5B9A9CDD918BEC235
https://files.dc-unlocker.com/share.html?v=share/18B15B9D02C945A79B1967234CECB423
The first one "Huawei_Android_phone_drivers.rar" was not useful for me, but the second one, "Huawei drivers testpoint.rar", is to make your COM port recognizable instead of this unknown "SER" in device manager.
In Device Manager, right click on "SER", "Update driver", and locate the extracted folder on your computer.
This is all you need I think, but I installed so many random drivers (which I would not recommend) that I'm not even sure anymore.
Step 3 - Repair the phone with DC-Phoenix
Following "Method 3" from this link, but with some differences : https://www.dc-unlocker.com/dc-phoenix-flash-repair-tutorial
As I said, this method is not free. You can buy credits to make DC-Phoenix work for 72 hours (you need 15 of them for that I think), but since we need HCU, you're better off buying a timed license which gives access to DC-Phoenix.
Open DC-Phoenix, and click on the "Download files" button on top. There, search for the file "STF-Full-Repair-NV-included-Board-A051-7.0.0_r1.dgtks" and download it, it's the Repair File.
https://get-file.org/search#q|STF-Full-Repair-NV-included-Board-A051-7.0.0_r1|1
With your phone connected via testpoints (it has to appear in the Device Manager in the COM Ports, and I recommend changing the COM Port to 1 (right click, Port settings, advanced,...)), go to the "Update OEMINFO" tab, and check "Use BOOTLOADER". There, choose "Kirin960_T2_A7.0_V4" (maybe it's a different one for you, but for me only this one worked).
Then check "Update OEMINFO and unlock Huawei ID", and choose "STF-L09". Click Update, and this should run without errors. If it doesn't recognize your device, that means that it's not turned off and connected via testpoints.
Once that is done, your device may show a sign of life by booting into fastboot mode (or sometimes not). Anyway, you can go directly to the "Update Firmware" tab, and in the "Update file" field, choose the file "STF-Full-Repair-NV-included-Board-A051-7.0.0_r1", check "Rescue Revovery" and "Old slow algo", and click "Update".
After completion, your phone should be able to boot (after a very long press) into a chinese test ROM.
Step 4 - Repair the phone infos with DCU
Follow this tutorial : http://hcu-client.com/huawei-phone-repair-as-empty-board/
Don't forget to change your phone to Manufactured mode (as explained) so you can read your phone info.
In the Step 4, they let you choose between Repair UMTS or CDMA tab, I chose CDMA because I think the phone has a MEID.
Then, when they tell you that you just have to click on "Repair as empty board" to make everything fill in automatically, for me this was complete bs : only my IMEIs were added.
So what you have to do is fill your original SN, WiFi and BT MAC adresses, and so on. But since your phone is bricked and you probably dumped the box that states the SN, you're outta luck like me. It seems like it's illegal to change a MAC or SN number, so I can't recommend it, but I personally just chose random numbers (that have the same number of digits).
For model I entered "STF-L09", for vendor "hw", and for country "eu". Don't check "Erase restricted ver.", since it's only for Qualcomm CPUs. Click on Repair.
Once this is done, your phone should be resetting, and able to boot in the same ROM as before, except in english.
Step 5 - Upgrade to the latest Android 9.1.0
Normally you'd have to do this step with DC-Phoenix : just flash one of their Full Stock Roms they have on their file database (click Download Files on DC-Phoenix, and search for "STF-L09").
You can try that (don't forget that you have to be in fastboot mode (Vol down + plug USB) to install), but it really didn't work for me, and even if it did, I don't know how you'd update after it, because your phone probably won't receive OTAs.
So the solution I found was this one : https://www.reddit.com/r/Huawei/comments/az4bl7/finally_managed_to_update_my_mate10_pro_to_pie/
First, uninstall your latest version of HiSuite to be able to follow this tutorial and install the old version.
Then, the file I chose in Firmware Finder was this one :
STF-L09 9.0.1.175(C432E2R1P5)
STF-L09C432E2R1P5B175 (9.0.1.175)
STF-L09C432E2R1P5T8B175 (9.0.1.175)
I chose the "full" version, which gave me this link :
http://update.dbankcdn.com/TDS/data/files/p3/s15/G3757/g1699/v260353/f1/full/update.zip
After following this tutorial, your phone should boot normally. You can then installs OTAs to update to 9.1.0. I'd recommend resetting the phone after this last step, to have a clean install.
If it doesn't work for you, you can also try this method : https://www.getdroidtips.com/full-guide-install-stock-firmware-huawei-smartphone/
I'll try to answer as many questions as fast as possible (since the Timed License is quite stressful), so feel free to ask !
Does the HCU Client unblock the network after doing the full repair?
Hello , Is this solution still works for honor 9 ?
I can't find stock rom on official website also.
Related
I won't follow this thread anymore since i have sold my Boston. Anyway you can find more informations on htcmania.com (use google translate if you don't speak spanish)
EDIT: Upgrade to CMLMod 1.5 based on Muchtel ROM (below outdated CML 1.4)
With this tutorial you sould be able to unlock your Orange Boston (aka GigaByte G1305 Codfish, Apanda A60, WellcoM A88, Vibo A688, Cincinnati Bell Blaze f800, Commtiva Z71, Muchtel A1, Chinavision Excalibur, Motorola Greco, Nexian A890) and install CMLMod 1.5.1 (or 1.4) (by c.martinez.lozano) based on the ROM Muchtel 2.1 (eclair)
Main advantages/disadvantages of CMLMod 1.5.1:
+Unlocked device (can use any SIM)
+Android 2.1 (Eclair)
+Root access with Superuser permissions
+Preinstalled programms and other features
+Easy SD partitioning and more features thanks to the new recovery
+Optional App2SD
+Processor speed adjustable in a range between 122 and 600MHz (with the possibility to set variable processor speed to have performance and longer battery life at the same time)
+Other features: 3 different launchers, flash light, setcpu, app2SD in one click, other preinstalled apps and tweaks
=Camera autofocus not working (like on stock ROM)
=Different UserInterface (in my opinion better, but that's subjective)
-You may loose the warranty on your device
-IMEI may change, to restore your original IMEI use the tutorial in my second post
-Languages not fully implemented (english is working fully, other languages settable with LocaleSwitch but not fully integrated )
Important!!! There may be the risk of damaging your phone in an irreparable way! Be aware also by installing this ROM you will loose your warranty! I do not take any responsability for the status of your device!
I translated the tutorials on htcmania.com
All credits to c.martinez.lozano and pindemon from htcmania.com
Requirements
Hardware requirements:
-Phone model: Orange Boston (aka GigaByte G1305 Codfish, Apanda A60, WellcoM A88, Vibo A688, Cincinnati Bell Blaze f800, Commtiva Z71, Muchtel A1, Chinavision Excalibur, Motorola Greco, Nexian A890)
Edit: never seen a phone with so many different names!!!
-PC operating system: Windows XP 32 bit with SP3 and .NET Framework 2.0 and Winrar installed. Do not try with Windows XP working on a virtual machine!!!. Seems to work also on other Windows 32 bit operating. Does NOT work with Windows7 64 bit
-USB to micro USB cable (comes with the phone)
Software requirements For CMLMod 1.5.1:
Firmware Apanda A60 1.6.2
Firmware CMLMod 1.5.1 (this file already contains RUT 1.2.2 and the Phone drivers)
Additional for CMLMod 1.4 (Outdated):
RUT 1.2.2
Phone drivers
Firmware Apanda A60 2.1.9
Firmware CMLMod 1.4
Tools like adb, fastboot, etc
Ready to start! make sure you have enough battery left (at least 30%)
PART 1: Installing Apanda 1.6.2
Unpack the file Phone drivers on your desktop, or another place, but remember where
install RUT_V1_2_2. At the end you will have to reboot your pc. Reboot it
[*]Unpack the firmware 1.6.2 from the archive Hipi1_6_2.rar and you get a file ending with .nb0
[*]Execute RUT (the shortcut should be on your desktop). The program reminds us to prepare the USB cable and to have all the drivers installed. (For Vista or Seven 32 bit: right click on the RUT shortcut. on the menu select Properties-->Compatibility check Run this program in compatibility mode for: and select Windows XP (Service Pack 3) then press OK, then right click on the Rut shortcut and select Run as administrator)
[*]In the next window, look for the firmware just to unpacked (the .nb0 file) and select it.
[*]The instructions tell you what to do: disconnect the phone from your pc (if connected), remove and reinsert the battery to your phone
[*]Hold the camera button and the volume up button pressed and then press the power button to enter recovery menu.
[*]Once the recovery menu, connect your phone to your computer. If we never connected in recovery, it requires new drivers. They are in the inside the Folder we unpacked in step 1 inside the subfolder AndroidX32 for 32 bit operating systems (if it later asks for drivers again, select the same folder again).
[*]The installer will detect your phone. If not, enter the Device Manager and check that all devices are correctly installed.
[*]From now on, follow the on-screen instructions and wait, it takes a while.
[*]Once complete, we have the new firmware installed. Our phone will restart and (after a while) show us something in chinese. Touch the right on-screen button to select the english language.
[*]When your phone is on check your IMEI by dialing *#06# and then press the call button and write it down. Now check the IMEI written on the phone under the battery. If the IMEI is the same, go on with PART 2. if the IMEI changes, use the tutorial in my second post to restore the original IMEI.
Now your phone is unlocked but you have the chinese version of Android 1.6
PART 2: Installing CMLMod 1.5.1 (for CMLMod 1.4 skip this and go to PART 2 OLD)
Unpack the file CMLMod1.5.rar
Run the programm RUT once again, and select the newCMLMod1.5.nb0 file you got
Repeat the same steps described in PART 1: 6.-10.
Now on your phone open the main menu and then CMLMod1.5 to configure App2SD select Configurar Apps2sd, then partitionar SD the phone will restart into recovery mode.
Now select Partition sdcard, Partition SD and confirm with the Home key. set swap=0, Ext2=512 (is more then enough! you can also set less) and Confirm twice again.
Then press the back button and select APP2SD if you want your apps being installed on your sd in the Ext2 partition.
Attention!!! if after you want your apps being installed on your phone memory you have to make a Wipe, that means, your data will be lost.
Always in CMLMod1.5 you can select a launcher, install flash lite and install setcpu to set the speed of the phone's processor with the possibility of variable speed.
FINISH!!!
PART 2 OLD: Installing Apanda 2.1.9
Unpack the file Hipi_2_1_9GMS.rar and you get the file Hipi2_1_9_GMS版.nb0. Rename this file in Hipi2_1_9_GMS.nb0 (the chinese symbol can make problems)
Run the programm RUT once again, and select the new Hipi2_1_9_GMS.nb0 file you got
Repeat the same steps described in PART 1: 6.-10.
Now you have the chinese version of Android 2.1
PART 3 OLD: Installing CMLMod 1.4
Unzip the archive CMLMod1.4zip copy the 3 files inside and paste them into the folder A688
Remove and reinsert the battery of your phone
Press and hold the volume down and the end call buttons and then press the power button
Now your phone starts in fastboot mode. Connect it to your PC
Press on your keyboard Windows+R in the pop up window type "cmd" and press Enter
In the dos window type "cd.." (off course without ") and press Enter, until you are in C:\
Now type "cd A688" Enter, then "fastboot getvar version" Enter. If the answer is "0:5" procede, otherwise control if your drivers are correctly installed
Type "fasboot -w" Enter
Type "fastboot flash system system.img" Enter (wait 2-3 min. until it finishes)
Type "fastboot reboot"
Tutorial: Restore your original IMEI
Wrong IMEI seems to lead to a lot of different strange problems while using the phone. So if your IMEI changed after flashing an other ROM it might be better to restore the original one.
All Credits to c.martinez.lozano
Attention!!! this process is delicated!!! I have no responsability for any damages to your phone!
Dowload this File: and Unpack it to "C:\IMEI"
Go into C:\IMEI and execute setup. This will install PSAS
Execute MadEdit (answer NO), in MadEdit click File-->Open and choose NVList.nvr and we see a lot of numbers
Scroll down until on the left grey side you see "000020C0" and on the same line in the white part you see the numbers ".. .. .. .. 1A 23 45 67 89 AB CD EF...." this is the BAD IMEI
Now open notepad (on your pc) and write down your correct IMEI (found under your battery) putting in front "A" and separing every 2 characters (E.g. if your IMEI is "324867523906130" write "A3 24 86 75 23 90 61 30") and now invert every coupe of letters (in this case you would have "3A 42 68 57 32 09 16 03") *NOTE: thanks to jhonburton for better example
In MadEdit instead of the BAD IMEI "1A 23 45 67 89 AB CD EF" write (replace it) the number you got (in this case "3A 42 68 57 32 09 16 03")
Save the file and close MadEdit
Disconnect from your PC and turn off your phone and restart it into Recovery mode (Camera+Vol. up+Power). Reconnect it to your PC and if necessary install the drivers
Run PSAS (you installed it before) and choose Hardware Forensics-->Use Mobile Ports
Right to Serial Com Port select COM? - Smartphone 2009 Wireless USB Moden. The ? stands for a number. So very important!!! remember for Example if ?=3, remember COM3
Go to the tab Codes (QC) and click on Send SPC
Go to the tab Dialog Port (QC) and on the second drop down menu left to the button Lets go select Restore NVItems (Binary) and then press Lets go
Select the NVList.nrv (we have changed before) and click Open
IMPORTANT Once the process is complete, closed PSAS
Download and install QPST
Launch QPST Configuration
Click on the tab Ports and select Add New Port... and there you write the COM? port you had to remember before (in my example write "COM3") and click OK
In the tab Active Phones now you should see your phone. If not something went wrong.
Click on Start Clients-->SERVICE PROGRAMMING
A window with our phone will pop up. We select OK
Select Load from file and choose the 00000000_sp.qcn inside the folder c:\IMEI and click Open
Click Write to Phone and wait until your phone restarts, with your new IMEI.
Check your IMEI again by dialing *#06# now it should be correct
If your IMEI is still wrong, check accurately if you did everything right (correct number in NRV file etc etc...) if nothing helps procede with following steps:
Turn on the phone in download mode ( Hang up + Vol. Up + Power) and flash Apanda 1.6.2 again
Repeat all the steps of the Tutorial to restore your IMEI
If this didn't help install Apanda 1.6.1 always with the phone in download mode
Repeat all the steps of the Tutorial to restore your IMEI
If you still have problems, try to find another PC with WindowsXP SP3 32bit where you can try again.
Sooner or later you will be able to get you IMEI right (i think so)
thanx a ton suriya I've unlocked my blaze f800
You forget to explain how to use app2sd on CMLMod1.4
Thank's about your translate!!.
Sorry about my bad english
thanks alot. really good tutorial!
i didnt encounter any problems at all, not even those specified by you in the tutorial. as for the underclocked cpu, i see that as an advantage: this android version is faster with lower cpu frequency then the original one (at least for me), and thus, less battery is consumed.
if u dont care about ur phone's warranty (i dont), i really recommend this upgrade.
so far seems stable, but the bug when u place a call and u don't here ringing, persists.
Thanks alot, again!
Is it possible to flash the phone with this room using ROM Manager?
And if following your method do we have to do PART1 of the tutorial? i allready have my phone unlocked and have Android 1.6 for example.
thanks!
I have problem with Imei. After flash it is chaged. And i use this tutorial for restore imei but it didn´t work and my imei is still different thet under battery. And i have problem whit wifi. Maybe bad IMEI is reason for don´t working Wifi
Sorry for my poor english
c.martinez.lozano said:
You forget to explain how to use app2sd on CMLMod1.4
Click to expand...
Click to collapse
I will do as soon as i have my sd (i think it will arrive this week) and i will also translate how to bring it back to 600MHz. By the way, THANKS TO YOU!!!!
floroiu.andrew said:
but the bug when u place a call and u don't here ringing, persists.
Click to expand...
Click to collapse
Explain me better. Do you mean, when you call someone you don't hear this "tuuut-tuuut"? cause if it's that i don't have this bug
by the way if you didn't read it look here, about battery optimization.
nuno_mdj said:
Is it possible to flash the phone with this room using ROM Manager?
And if following your method do we have to do PART1 of the tutorial?
Click to expand...
Click to collapse
ROM Manager doesn't support our phone as far as i know.
I wouldn't skip that part! seems strange but i think i have red that people got trouble if skipping PART 1
gru15 said:
I have problem with Imei. Maybe bad IMEI is reason for don´t working Wifi
Click to expand...
Click to collapse
Try once again step by step. start with PART 1 again. be careful you don't forget anything. Use this version of QPST and a new .nrv file this time. if this does not help we will find a solution together looking step by step (in case c.martinez.lozano is an expert).
By the way wich kind of phone do you have, and from wich country? And wich operating system has your computer?
So i have Orange Boston from Slovakia and i am using WIN vista 32-bit. I read original post on htcmania but it is spanish so i dont understand everything, but some people write there that this tutorial must be use whe RUT is in download mode while i am installing 1.6.2 rom. I don´t know when is RUT in download mode...
And your qpst want serail !!!!
gru15 said:
So i have Orange Boston from Slovakia and i am using WIN vista 32-bit. I read original post on htcmania but it is spanish so i dont understand everything, but some people write there that this tutorial must be use whe RUT is in download mode while i am installing 1.6.2 rom. I don´t know when is RUT in download mode...
And your qpst want serail !!!!
Click to expand...
Click to collapse
Sorry i replaced the qpst links.
ok... not download mode but compatibility mode.
you right click on tha RUT shortcut. on the menu select Properties-->Compatibility check Run this program in compatibility mode for: and select Windows XP (Service Pack 3) then press OK
Now right click on the RUT shortcut again and select Run as administrator.
Try that way. then try that imei stuff again!
cheers
P.S. Anyway if you know where you can use an XP (32 bit) with SP3 i am confident everything will work if you do it step by step
ok IMEI is correct now. But i have a problem with wifi. On any 2.1 rom cant find any network but when i flash 1.6.2 it find. So i dont know where is a problem.
gru15 said:
ok IMEI is correct now. But i have a problem with wifi. On any 2.1 rom cant find any network but when i flash 1.6.2 it find. So i dont know where is a problem.
Click to expand...
Click to collapse
Ok good you restored your IMEI. About WIFI. Best thing is if you ask on htcmania because i don't know what to do.
When you have an answer and corrected your problem please post it here. So i add it to first post cuz other people may have the same issue.
CMLMod 1.5 with some nice new features is on the way!!!
there is in italian version too?
gru15 said:
So i have Orange Boston from Slovakia and i am using WIN vista 32-bit. I read original post on htcmania but it is spanish so i dont understand everything, but some people write there that this tutorial must be use whe RUT is in download mode while i am installing 1.6.2 rom. I don´t know when is RUT in download mode...
And your qpst want serail !!!!
Click to expand...
Click to collapse
dont remember exactly, but in some parts of the tutorial, you have to "Run as administrator" the given applications (RUT, etc). i used win7 32bit, and no problem.
ady_uaic said:
there is in italian version too?
Click to expand...
Click to collapse
No. But with LocaleSwitch you can select italian then most things are in italian. Settings (impostazioni) is still in English, and no italian dictionary on the stock keyboard. you can install another keyboard, to solve this. But wait for CML 1.5. Maybe some better.
floroiu.andrew said:
dont remember exactly, but in some parts of the tutorial, you have to "Run as administrator" the given applications (RUT, etc). i used win7 32bit, and no problem.
Click to expand...
Click to collapse
Yeah thanks for your confirmation. I wrote it on the first page.
cheers suriya
oki..thx for info. but, what does exactly that locale switch app? what are the changes?
Please add Nexian A890 (Indonesian version of this device) on the list too. Here, in Indonesia, we can bring it to the official service center to upgrade it.
ady_uaic said:
oki..thx for info. but, what does exactly that locale switch app? what are the changes?
Click to expand...
Click to collapse
with it you can select languages wich are present in the phone. Italian is also partially present. most things then are in italian. except the settings menu, the camera menu, the date on the lockscreen and maybe something else
minori_aoi said:
Please add Nexian A890 (Indonesian version of this device) on the list too.
Click to expand...
Click to collapse
thanks mate. added
It worked on my Cincinnati bell Blaze,but I can't get the IMEI to change. all works but
the Internet connection, WIFI does work.
Thanks for the 2.1 Upgrade
Today I Present You with My new Software the Asus Flash Tool 2.0.
By Uisng this Software You Can Flash Your Asus Phone Without any difficulty.
Step 1
Open the ASUS Flashtool, AFT will automatically detect mobile devices (if not automatically detect, please re-plug the USB cable)
Step 2
Automatically detect the serial number (for example: DCATCY141082), State representatives connection status bar turns blue. Not connected display. Detected inconsistent with the actual SN possible, but does not affect the refresh firmware.
Step 3
Manually select the correct model, there is no drop-down menu, and on behalf of Asus Flashtool is not supported; model forget if elected, you will be prompted
Step 4
*Select whether empty user data, Yes on behalf empty, No representative of any default No, please choose according to the actual situation.
*Click on the box icon, select the path to the firmware raw file. DownLoad Raw File From here
*Click again, you need to update the machine, serial number, and blue State status bar.
*The start point Start icon to start the firmware update.
Step 5
*Flash process, the phone will appear black, is a normal, over a period of time will automatically display
*Success, Asus Flashtool will show below, the system will automatically reboot into the phone (entire process takes about 6.5 minutes)
XDA:DevDB Information
ASUS FLASH TOOL 2.0, Tool/Utility for all devices (see above for details)
Contributors
adithyan25
Version Information
Status: Beta
Created 2016-03-04
Last Updated 2016-03-04
Program runtime error
My phone model is ze601kl, connected to the computer to open the Asus Flash Tool 2.0, the error message when run the program.
can't build adb commander!
fake?
ifreenet said:
My phone model is ze601kl, connected to the computer to open the Asus Flash Tool 2.0, the error message when run the program.
can't build adb commander!
Click to expand...
Click to collapse
probabbly is a fake
ifreenet said:
My phone model is ze601kl, connected to the computer to open the Asus Flash Tool 2.0, the error message when run the program.
can't build adb commander!
Click to expand...
Click to collapse
did u installed adb and is your debugging mode on?? and also use given raw file
jokruger said:
probabbly is a fake
Click to expand...
Click to collapse
never judge with out trying... i tried it on Zenfone4 5 6 and wrked like charm
serial number failure
i've done all the instructions but my serial number detected is 123456789ABCDEF (its same to the handphone). Whe i hit the START i got notice that : Check the detected serial number failure (the system cannot find the path specified)
need help please
thank you
Excuse me if I am mistaken, but the tool provided in this thread seems bogus. The linked setup.rar contains Asus Flash Tool 1.0, not 2.0, and it does not autodetect the phone type, and the pulldown menu has only about 6 choices, and does not modern phones like ze551ml. The other Asusu Flash Tool 1.0.0.45 as linked in the below thread seems much more modern! COrrect me if I am wrong.
The download link is for version 1.00 not 2.0 as already posted so I'm closing this up to save anymore confusion
Regards
Sawdoctor
None of the methods in this thread are my own work. I struggled with getting my phone rooted for a long time and spend 10s of hours on the process. I had never rooted before and was therefore unfamiliar with all the terms, unfamiliar with how to complete all the recommended checks to ensure one had the right model, etc. There were several helpful threads but most approach the subject with the assumption that one knows something about the process. In this post I lay out what worked for me in a step-by-step way and what you have to do to achieve my results.
#1 Ensure you have a H-901 motherboard and not the Korean F600 motherboard by checking the sticker, and checking “About Phone” -> “Hardware Info” -> “Model number” in settings. These must both be LG-H901…from what I can tell the community has only developed technique for the H-901 variant.
#2 Get a micro SD card and load it with Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 , and if you have Marshmallow or Lollipop and want Nougat (much better experience IMHO), load the files in this thread: https://forum.xda-developers.com/tmobile-lg-v10/development/h901-t-mobile-nougat-v30b-twrp-t3639203 And maybe this thread as well (read both and then decide): https://forum.xda-developers.com/tm.../h901-t-mobile-nougat-v30c-flashable-t3744648
#3 Ensure you have unlocked your bootloader. (apparently only for T-mobile LG v10s since other carriers lock the bootloader) The FWUL virtual machine root method will not work if you have not done so. This is an entire process in itself. The following 2 videos which show how to root android 6.0 or earlier (process will not work with Nougat, 7.0, since some fastboot commands are missing). https://youtu.be/OtXlokk6JkQ , https://youtu.be/PPLwFGxLQA4
Also, this thread may be helpful. https://forum.xda-developers.com/tm...t-mobile-bootloader-factory-unlocked-t3236224 , download the nexus root toolkit here for easy ADB command entry http://www.wugfresh.com/nrt/ —we will only use the “Advanced Utilities” -> ”Manual Input” -> ”Launch CMD Prompt”. When it prompts you to select a phone, select the first option and then for android version select Android *** Any. Don’t use any of the other commands because they are not configured for your device.
If you get a “waiting for device” error while attempting the fastboot oem unlock command in the above thread, see: https://forum.xda-developers.com/tmobile-g4/help/fastboot-waiting-device-t3489789 Great video which shows how to change drivers. You will need to do this, I found a number of drivers that were already on my PC from google and Samsung worked although I didn’t have the specific one mentioned in the above thread. Don’t be afraid to experiment… you can always try another driver. And don’t require it to be hardware compatible. Ignore the warning message: https://youtu.be/nQjg6ePnGAc
---------------------------------------------
NOW that you have your bootloader unlocked you can proceed to actually flash the TWRP image as per this thread: https://forum.xda-developers.com/tmobile-lg-v10/general/root-h901-nougat-t3773942
Notes before beginning:
-To enter download mode to begin: Plug a USB cable into your phone with your phone powered off, hold down on the Vol Up button and plug the USB cord into your computer. It should immediately boot into download mode. Exiting Download mode after flash: pull battery…no damage will be done.
-To enter recovery after flashing TWRP: power off the phone then hold both the down volume and power at the same time. When you see the black LG screen briefly release the power button and then press it again while not letting the volume down up. You will see a screen asking if you want to delete all user settings. Say YES (via the volume and power keys—no touch input). You will see a screen asking if you want to delete all user data. Say YES (the data is only deleted if TWRP loads successfully) You will briefly see the black LG bootup screen. TWRP or factory recovery will load. Or if you did not unlock your bootloader, it will say recovery is corrupted and cannot be trusted, and then boot normally without changing your settings or deleting files.
-Additional note: as of 7-23-18 some commands had changed:
From V20 forum, Brian (runningnak3d) has moved to gitlab.com. So instead of github.com, we have to use a new git repository that Brian created in gitlab.com.
cd
mv lglaf lglaf_BAK
git clone https://gitlab.com/runningnak3d/lglaf
cd lglaf
git pull
git checkout v10-miscwrte
There are additional comments in the thread. Some timeout errors may be solved by: 1 - Download the VirtualBox extension pack: https://download.virtualbox.org/vir..._VirtualBox_Extension_Pack-5.2.8.vbox-extpack
2 - Go to File / Preferences / Extensions / click the + and browse to where you downloaded it.
3 - Once installed, with the VM off, right click on the VM, and go to settings. Click on USB, and pick USB 3.0. If your machine doesn't have a USB 3 port, pick 2.0.
But frankly, simply up arrow after a timeout error to load the last command on the command line and hit enter again. Simply keep doing this until it works. You know it works because no dialog appears for several minutes before informing one of success.
**Upgrade to Nougat after Flashing TWRP and booting to Recovery steps: (I did a full wipe as suggested by this thread: https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594 before flashing the v30b upgrade then full Nougat zip, and then flashing Magisk. I flashed the 3 zips sequentially. I was afraid Nougat would not boot successfully because the zip files are less than 2 gb combined but success! You may want to also flash the 30c upgrade before flashing Magisk for a total of 4 zip flashes. I did not try this. However doing all this means no backups are done so if there is a problem you may have to flash a KDZ with the LG UP tool (don’t ask me how).
As a final note, I cannot answer specific questions about the various processes provided or errors you may encounter that I have not listed in this write up since I have not experienced them. A bit of research on your part may be required, but this post should provide you with a huge head start compared to where I started. Good luck!
Methods to get unlimited mobile hotspot, very useful if you're on the $50 MetroPCs (owned by T-mobile) unlimited plan. All you $70 T-mobile plan suckazzz! https://forum.xda-developers.com/tm...ited-tetherting-hotspot-t3825144#post77249285
I would actually recommend using a USB tether client and forgoing root access if tethering is your only objective and you are trying to be efficient with your time. However, with root you can install all these cool apps!: https://www.digitaltrends.com/mobile/best-android-root-apps/
The following caught my eye:
-Rec: screen record
-liveboot: boot animation (does not work with Magisk)
-Servicely: checks to see which apps are using a lot of battery and lets you suppress them
-Adblock Plus
-Titanium backup: very powerful phone backup application & bloatware remover look into for quickly switching over to a different lg v10
-Greenify: put apps into hibernation
-System tuner: get lots of info about you phone but be careful making changes
-ES file explorer: dig into the android system
-Disk digger: recovers deleted files (photos only?)
Hi there,
So After seen many tutorials I wanted to proceed to unlock the bootloader of my Huawei Mediapad T5 , here are the specs
```
Model: AGS2-W09
Build No: AGS2-W09 8.0.0.360(OCEC431)
CPU : Hisilicon Kirin 659
Android Version: 8.0
```
I have downloaded the last build of `potatoNV` along with the SER Drivers ,
I have booted in untrusted driver mode (on Win10) and have installed `usbser.sys` as far as I recall
I proceed opening the Tablet from inside and shorting the "short point" and I get connection with the Computer , I installed the drivers , and tried on `potatoNV` with `Kirin 65x (A)` .
I get to the end of the progress bar , and then I get the problem as there is no confirmation that the process has been performed correctly. The connection dissapears , and If I try to boot on rescue mode and I do `.\fastboot.exe devices` or `fastbook.exe oem device info` it doesnt show no device at all.
Also the `rescue mode` menu says `Phone locked , FRP Unlocked` So I guess I had no luck
Please see the video on the link (note that the 2 takes are not synchronized)
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
What I may be possibly doing wrong ? May it be the USB connection (cables or connectors) ? or the drivers I downloaded?
Please any assitance will be appreciated.
Thanks
Maybe I can help you with this. Recently rooted this tab myself. Please give me a reminder tomorrow
Hey there I just saw the message . Please if you can guide me a bit of what I may be doing wrong? Also If there is a way to share the Drivers files that you used that would be great (I'm not sure if it was a matter of drivers or general clumsiness , please If you have a minute to check the video tell me what may be wrong on my "Technique") Thank you!!
freddieventura said:
Hey there I just saw the message . Please if you can guide me a bit of what I may be doing wrong? Also If there is a way to share the Drivers files that you used that would be great (I'm not sure if it was a matter of drivers or general clumsiness , please If you have a minute to check the video tell me what may be wrong on my "Technique") Thank you!!
Click to expand...
Click to collapse
Just saw your responce now (please use reply next time, I will get an notification then ).
The "Kirin 65x (A)" you've used is the correct bootloader. So guess it would have been something going on with the drivers or the procedure.
I recently (about 1 month ago) rooted this tab myself so I think I will have quite recent files for doing so. Maybe I can send them to you if you like. But I should have save the websites where I got them from too. But need to check it up for you then.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you have used the settings above?
You did had recieved the "New unlock code" message?
I have to go to work now, but I could help you further later this evening if you need further assistance
Rockel said:
Just saw your responce now (please use reply next time, I will get an notification then ).
The "Kirin 65x (A)" you've used is the correct bootloader. So guess it would have been something going on with the drivers or the procedure.
I recently (about 1 month ago) rooted this tab myself so I think I will have quite recent files for doing so. Maybe I can send them to you if you like. But I should have save the websites where I got them from too. But need to check it up for you then.
View attachment 5391207
Did you have used the settings above?
You did had recieved the "New unlock code" message?
I have to go to work now, but I could help you further later this evening if you need further assistance
Click to expand...
Click to collapse
Hi, thanks for assisting me. Yeah well, the version I used of PotatoNV(the last build) just had the option of Disable FBlock so I did that.
Also I tried wth a previous build that was showing both versions as you are showing and it happened the same thing.
My guess are more focused on 2 probable mistakes by my side either:
- When shorting the short point Im not doing it correctly. (not sure if this, as the device gets detected by PotatoNV and initiates the process)
- (Most likely thisone). Wrong drivers, I have downloaded them through a link found in a youtube video, and the video was not specific about this Tablet. Also there were a bunch of drivers within the same file so I installed one that looked like the correct one (but not 100% sure)
Anyways thanks for taking your time really and appreciate a reply but always whenever you find free time obviously. Take it easy today at work
freddieventura said:
Hi, thanks for assisting me. Yeah well, the version I used of PotatoNV(the last build) just had the option of Disable FBlock so I did that.
Also I tried wth a previous build that was showing both versions as you are showing and it happened the same thing.
My guess are more focused on 2 probable mistakes by my side either:
- When shorting the short point Im not doing it correctly. (not sure if this, as the device gets detected by PotatoNV and initiates the process)
- (Most likely thisone). Wrong drivers, I have downloaded them through a link found in a youtube video, and the video was not specific about this Tablet. Also there were a bunch of drivers within the same file so I installed one that looked like the correct one (but not 100% sure)
Anyways thanks for taking your time really and appreciate a reply but always whenever you find free time obviously. Take it easy today at work
Click to expand...
Click to collapse
Not sure, I should get into it again, but I'm not sure of potato is able to start the procesure or finding the divice if not shorted correctly.
Do you have a screenshot of your potato output/ results?
How are you performing the shorting procedure?
I can see if I can look for you for the right drivers tonight.
Rockel said:
Not sure, I should get into it again, but I'm not sure of potato is able to start the procesure or finding the divice if not shorted correctly.
Do you have a screenshot of your potato output/ results?
How are you performing the shorting procedure?
I can see if I can look for you for the right drivers tonight.
Click to expand...
Click to collapse
I hve uploaded the video which shows all the output and how Im shorting the point. The video though is composed by two takes and are not synced in time but that is how I do it.
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
Let me know if you can watch it on there. Thanks
freddieventura said:
I hve uploaded the video which shows all the output and how Im shorting the point. The video though is composed by two takes and are not synced in time but that is how I do it.
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
Let me know if you can watch it on there. Thanks
Click to expand...
Click to collapse
Oh yes, forgot about the video in the OP...
Seems you're folowing the wrong procedure with the shorting proces.
And seems your potato version is a bit outdated. But don't think this will be much of an issue.
- Your tablet needs to be turned off.
- cable removed from the tab.
- start potato
- then short the circuit (tab turned off).
- keep it shorted and insert the usb cabel (the other end should be in the computer already)
- the tablet starts (i believe in somekind of flash mode. And i believe you should not be able to see the Huawei logo in this procedure).
- after 2 or 3 seconds after booting, release the shorted circuit.
- i believe it should display you now some info about the tab itself in potato when you press start.
P.s. Don't forget to make a screenshot of the results or write down the newly given unlock code. So you can use it afterwards to lock or unlock your bootloader at a later moment, without opening the tab again.
P.s. 2 I just read in your comment that the recordings are not synchronised. So it's possible you were following the correct steps above. Correct me if I'm wrong please
freddieventura said:
I hve uploaded the video which shows all the output and how Im shorting the point. The video though is composed by two takes and are not synced in time but that is how I do it.
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
Let me know if you can watch it on there. Thanks
Click to expand...
Click to collapse
I'm home (finally)...
If the steps mentioned above didn't worked out, I would like to ask you to do axactly as I did. Just unlocked my Mediapad T5 just 1 month ago or so, so everything I've used should be recent enough I guess.
First:
- Un-install your potato version.
- Un-install your Mediapad T5 USB drivers.
So we can begin from scratch
Also:
- turn on OEM-unlock and USB-debugmode in developer settings.
I asume you have a decent and working ADB version installed on your PC?
If not, or when you're not sure, uninstall it too.
I was using the Minimal ADB and Fastboot from here:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Then:
1) Install the Huawei USB drivers from here:
Support area | files.dc-unlocker.com
(this) or (this) are the "official" sites I got this from.
2) Install the latest version of PotatoNV from here:
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
Open potatoNV and use these settings marked in red:
3) Plug the USB-cable into your PC already, but don't connect the other side to the tablet. And make sure your tablet is turned off.
4) Now short the testingpoint with a shielded part. I just used a thick copper wire and used it between testingpoint and metalshield just next to it. Metal pliers as used in your video should work too ofcourse.
P.S. I see that you also disconnected your screen in the video? It seems that it's verry important not to see a charging icon in the next step, so maybe it's better to connect it again for this step.
5) While still shorting the testingpoint with the shield, connect the USB cable to your tablet and be sure no charging icon pops up (This can be a bit difficult doing on your own. Easiest way is to have someone around te help in this step). After a few secconds when connected (without seeing an charging icon) remove the shorting between testingpoint and shield.
6) Make sure that the Huawei USB COM is selected in PotatoNV (and that the other settings are the same as the screenshot)
7) And pres "Start!"
8) You should get similar results now:
PotatoNV v2.2.1
User manual: https://kutt.it/pnv-en
Verifying images...
Uploading hisi65x_a...
- xloader
- fastboot
Waiting for any device...
Connecting...
Serial number: FQB***************
Board ID: FQB*************
Model: AGS2-W09
Build number: AGS2-W09 8.0.0.360(OCEC431)
FBLOCK state: unlocked
Saved key: 6BN**************
Writing FBLOCK...
Writing WVLOCK...
Writing USRKEY...
Rebooting...
New unlock code: 3BS*************
p.s. In your video it seemed your device got disconnected somehow while uploading. You should not see that "timeout" message here now annymore.
9) Make a screenshot of your results, copy them to a text file or write down at least your "new unlock code"
So you won't have to open your tablet annymore in the future. You can use this newly obtained unlock code now to lock and unlock your tablet without opening again.
10) You should now see a warning screen everytime you reboot the tab. It warns you about that the device can't be trusted annymore because of the unlocked bootloader.
You can also enter Fastboot to check it
Fastboot/ Bootloader mode:
1. Turn off the device by holding the Power key for a few seconds.
2. Connect tablet to PC/laptop using the USB-cable.
3. Hold down Volume-Down.
4. Hold down the Power button until device starts (while still holding Volume-Down and USB connected).
4. Tablet boots now into Fastboot-mode.
You should see the following screen then (pay attention on the 2 red lines at the bottom):
You can close your tablet now!
Rockel said:
I'm home (finally)...
If the steps mentioned above didn't worked out, I would like to ask you to do axactly as I did. Just unlocked my Mediapad T5 just 1 month ago or so, so everything I've used should be recent enough I guess.
First:
- Un-install your potato version.
- Un-install your Mediapad T5 USB drivers.
So we can begin from scratch
Also:
- turn on OEM-unlock and USB-debugmode in developer settings.
I asume you have a decent and working ADB version installed on your PC?
If not, or when you're not sure, uninstall it too.
I was using the Minimal ADB and Fastboot from here:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Then:
1) Install the Huawei USB drivers from here:
Support area | files.dc-unlocker.com
(this) or (this) are the "official" sites I got this from.
2) Install the latest version of PotatoNV from here:
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
Open potatoNV and use these settings marked in red:
View attachment 5391609
3) Plug the USB-cable into your PC already, but don't connect the other side to the tablet. And make sure your tablet is turned off.
4) Now short the testingpoint with a shielded part. I just used a thick copper wire and used it between testingpoint and metalshield just next to it. Metal pliers as used in your video should work too ofcourse.
View attachment 5391623
P.S. I see that you also disconnected your screen in the video? It seems that it's verry important not to see a charging icon in the next step, so maybe it's better to connect it again for this step.
5) While still shorting the testingpoint with the shield, connect the USB cable to your tablet and be sure no charging icon pops up (This can be a bit difficult doing on your own. Easiest way is to have someone around te help in this step). After a few secconds when connected (without seeing an charging icon) remove the shorting between testingpoint and shield.
6) Make sure that the Huawei USB COM is selected in PotatoNV (and that the other settings are the same as the screenshot)
7) And pres "Start!"
8) You should get similar results now:
PotatoNV v2.2.1
User manual: https://kutt.it/pnv-en
Verifying images...
Uploading hisi65x_a...
- xloader
- fastboot
Waiting for any device...
Connecting...
Serial number: FQB***************
Board ID: FQB*************
Model: AGS2-W09
Build number: AGS2-W09 8.0.0.360(OCEC431)
FBLOCK state: unlocked
Saved key: 6BN**************
Writing FBLOCK...
Writing WVLOCK...
Writing USRKEY...
Rebooting...
New unlock code: 3BS*************
p.s. In your video it seemed your device got disconnected somehow while uploading. You should not see that "timeout" message here now annymore.
9) Make a screenshot of your results, copy them to a text file or write down at least your "new unlock code"
So you won't have to open your tablet annymore in the future. You can use this newly obtained unlock code now to lock and unlock your tablet without opening again.
10) You should now see a warning screen everytime you reboot the tab. It warns you about that the device can't be trusted annymore because of the unlocked bootloader.
You can also enter Fastboot to check it
Fastboot/ Bootloader mode:
1. Turn off the device by holding the Power key for a few seconds.
2. Connect tablet to PC/laptop using the USB-cable.
3. Hold down Volume-Down.
4. Hold down the Power button until device starts (while still holding Volume-Down and USB connected).
4. Tablet boots now into Fastboot-mode.
You should see the following screen then (pay attention on the 2 red lines at the bottom):
View attachment 5391639
You can close your tablet now!
Click to expand...
Click to collapse
Thanks very much for your explanation , I will do this when I am back at home and let you know .
Cheers!!
freddieventura said:
Thanks very much for your explanation , I will do this when I am back at home and let you know .
Cheers!!
Click to expand...
Click to collapse
Are you btw sure that the pliers you used in in the video are making a circuit from one point to the other? Maybe worthwile to measure the resistance first?
I just used a thick copper wire and bended it to an easy to use U-shape.
Rockel said:
Are you btw sure that the pliers you used in in the video are making a circuit from one point to the other? Maybe worthwile to measure the resistance first?
I just used a thick copper wire and bended it to an easy to use U-shape.
Click to expand...
Click to collapse
Sorry Rockel I have been very busy this week , I'm gonna try and find a little bit of time to get this done this weekend . Thank you!!
freddieventura said:
Sorry Rockel I have been very busy this week , I'm gonna try and find a little bit of time to get this done this weekend . Thank you!!
Click to expand...
Click to collapse
No problem, take your time. Hope these steps wil solve your problem. Please keep me informed when you have time
Rockel said:
No problem, take your time. Hope these steps wil solve your problem. Please keep me informed when you have time
Click to expand...
Click to collapse
Do angels wear capes? because I haven't seen yours .
Much much much appreciate your help with this, I have just done it perfectly it didn't take me much time to do it.
Whatever I was doing wrong (probably the drivers , probably the shorting point thing not doing it properly) , whatever who cares!!.
I was also a bit not confident to do it that's why it took me time to get into doing it , but you definitely coached me with your messages .
Really thanks very much Rockel . For anything we keep in touch mate
freddieventura said:
Do angels wear capes? because I haven't seen yours .
Much much much appreciate your help with this, I have just done it perfectly it didn't take me much time to do it.
Whatever I was doing wrong (probably the drivers , probably the shorting point thing not doing it properly) , whatever who cares!!.
I was also a bit not confident to do it that's why it took me time to get into doing it , but you definitely coached me with your messages .
Really thanks very much Rockel . For anything we keep in touch mate
Click to expand...
Click to collapse
Hehehehe, thanks for your nice responce!
So I asume You've managed to root unlock the device now!
It was a pleasure assisting you in this.
If you need anny other information regarding this rooted device, please let me know. I'm not a pro with this. But had to solve a few problems myself. And came there with the help of others aswell.
What is the use of New unlock code?
do anyone have system, boot, cust, recovery, userdata.img with you i want to try with multi-tool to unbrick my tab
The unlock code can be used to unlock bootloader (using something like "adb oem unlock <code>" from PC)
I have saved the OTA folder form huawei system update app just before updating from 8.0.0.320(C432) to 8.0.0.371(C432), it can be found in /data/HwOUC folder after updater finished downloading. This version cannot be found on HuaweiFirmwareFinder site but I have temporary shared then here. Perhaps we could contact the authors to upload this version.
You can later use HuaweiFirmwareExtractor to extract different images from the zip files (no clue why there are 3 of them).
You need to disable "Verify Header checksums" in the "Settings" to open the extracted update.app files from the zips.
Good luck!
denzelcris said:
The unlock code can be used to unlock bootloader (using something like "adb oem unlock <code>" from PC)
I have saved the OTA folder form huawei system update app just before updating from 8.0.0.320(C432) to 8.0.0.371(C432), it can be found in /data/HwOUC folder after updater finished downloading. This version cannot be found on HuaweiFirmwareFinder site but I have temporary shared then here. Perhaps we could contact the authors to upload this version.
You can later use HuaweiFirmwareExtractor to extract different images from the zip files (no clue why there are 3 of them).
You need to disable "Verify Header checksums" in the "Settings" to open the extracted update.app files from the zips.
Good luck!
Click to expand...
Click to collapse
thank you .. but i extract app didnt uderstand which img file to install there no exact name for boot.img, recovery.img, cust.img, can you plz tell me which file equal to those file..
I don't think Huawei has boot.img or recovery.img, they may have a different layout and names (someone correct me if I'm wrong). I know the equivalent of boot.img is ramdisk.img or kernel.img (I flash both when restoring to be sure) and recovery should be recovery_ramdisk.img. The names from HuaweiExtractor should match with the images. Cust.img can be found in the other zip: update_full_AGS2-W09_hw_eu.
There is also this partition layout table which I don't know how it works for Huawei but I know that it may change for different firmwares so it is usefull to have remembered what version you had previously or use a safe tool to flash that also.
This thread will go over restoring the IMEI number if you cleared the NVRAM (or fully formatted your phone). The official tool to use is the SN Writer tool from Mediatek but as the P60 processor is not compatible with that, I had to search for alternative ways.
First the legal blerb:
IT IS ILLEGAL TO FLASH A DIFFERENT IMEI NUMBER THAN THE ONE IT CAME WITH (AS FOUND ON THE SIM TRAY OR BOX).
I AM NOT RESPONSIBLE FOR ANY DAMAGE OR LEGAL AFFAIRS CAUSED BY USING THIS GUIDE. IF YOU DO BLAME IT ON ME THEN I WILL LAUGH AT YOU!
Now the guide.
You will need:
- The phone
- A USB cable
- A Windows computer (I used Windows XP, I will get to that later.)
- The drivers linked below (no other drivers seem to work properly or at all.)
- MauiMETA (linked below.)
Part 1: driver installation
These are essential to get the phone to be recognized
- Remove the phone if it's plugged in.
- If using Windows Vista or newer, disable driver signature enforcing (look up online if you don't know how to). For Windows XP there is no such limitation, you can just click a "continue anyway" button.
- Download and extract the drivers (linked below).
- Run "Install Drivers.bat" and follow instructions.
- Reboot the computer to be sure.
Part 2: installing MauiMETA
You will need this tool to start the phone to META mode and write the IMEI numbers.
- Download the setup program.
- Install the software by following on-screen instructions.
Part 3: getting the phone to go into meta mode
- Turn off the phone completely.
- REMOVE THE SIM CARD JUST IN CASE!
- Open the MauiMETA program on your computer.
- Check if the device select is set to "Smartphone" and if the drop-down in the top left is set to "IMEI Download"
- Click "reconnect" and plug in the phone.
- Wait until the phone displays "=> Meta mode" and the application either says "connected" or displays an error box.
Don't be scared of the error box. Just close it. Another may pop up, close that too. If the MauiMETA program displays a few boxes that say something with 6771, it's been detected and the IMEI Download tool is about to open.
Part 4: downloading an IMEI number to the phone
I would again like to warn you that flashing the non-original IMEI is illegal!
If the tool asks if it should find the database itself, click yes. There is no database you can load yourself, so the built-in one will work fine.
- Find your IMEI number(s). They should start with "35".
- Put in the IMEI number to the tool. The middle box is where you start typing. The very last number will need to go in the small box to the right. If you have a dual SIM model, there will be a submenu called "SIM_2" which you can find at the top of the tool.
- Click the "Download to phone" button and it should flash the IMEI numbers.
- When everything is done, hold the power button of the phone for about 10 seconds until it boots into the OS.
If everything went right, you should have a working phone now. I still need to figure out how to restore WiFi and BlueTooth MAC addresses, but the random ones the OS give you should do fine. Also ignore the NVRAM Error 0x10 wifi network, it indicates both are gone. Also some UI bits and pieces might be wrong on the latest Android because for example the notch values were loaded into device-specific partitions.
My device is oneplus nord 2 . When i am using the maui meta software , my phone is always connected on COM6 port and in the maui meta software i can only see COM1 , USB COM and DIAG COM . When i connect the phone the COM6 is displayed and after that when i click on reconnect the maui meta software says please connect cable to target and power on when the phone is already in meta mode. Can you please help me with that ?
BennoMP said:
This thread will go over restoring the IMEI number if you cleared the NVRAM (or fully formatted your phone). The official tool to use is the SN Writer tool from Mediatek but as the P60 processor is not compatible with that, I had to search for alternative ways.
First the legal blerb:
IT IS ILLEGAL TO FLASH A DIFFERENT IMEI NUMBER THAN THE ONE IT CAME WITH (AS FOUND ON THE SIM TRAY OR BOX).
I AM NOT RESPONSIBLE FOR ANY DAMAGE OR LEGAL AFFAIRS CAUSED BY USING THIS GUIDE. IF YOU DO BLAME IT ON ME THEN I WILL LAUGH AT YOU!
Now the guide.
You will need:
- The phone
- A USB cable
- A Windows computer (I used Windows XP, I will get to that later.)
- The drivers linked below (no other drivers seem to work properly or at all.)
- MauiMETA (linked below.)
Part 1: driver installation
These are essential to get the phone to be recognized
- Remove the phone if it's plugged in.
- If using Windows Vista or newer, disable driver signature enforcing (look up online if you don't know how to). For Windows XP there is no such limitation, you can just click a "continue anyway" button.
- Download and extract the drivers (linked below).
- Run "Install Drivers.bat" and follow instructions.
- Reboot the computer to be sure.
Part 2: installing MauiMETA
You will need this tool to start the phone to META mode and write the IMEI numbers.
- Download the setup program.
- Install the software by following on-screen instructions.
Part 3: getting the phone to go into meta mode
- Turn off the phone completely.
- REMOVE THE SIM CARD JUST IN CASE!
- Open the MauiMETA program on your computer.
- Check if the device select is set to "Smartphone" and if the drop-down in the top left is set to "IMEI Download"
- Click "reconnect" and plug in the phone.
- Wait until the phone displays "=> Meta mode" and the application either says "connected" or displays an error box.
Don't be scared of the error box. Just close it. Another may pop up, close that too. If the MauiMETA program displays a few boxes that say something with 6771, it's been detected and the IMEI Download tool is about to open.
Part 4: downloading an IMEI number to the phone
I would again like to warn you that flashing the non-original IMEI is illegal!
If the tool asks if it should find the database itself, click yes. There is no database you can load yourself, so the built-in one will work fine.
- Find your IMEI number(s). They should start with "35".
- Put in the IMEI number to the tool. The middle box is where you start typing. The very last number will need to go in the small box to the right. If you have a dual SIM model, there will be a submenu called "SIM_2" which you can find at the top of the tool.
- Click the "Download to phone" button and it should flash the IMEI numbers.
- When everything is done, hold the power button of the phone for about 10 seconds until it boots into the OS.
If everything went right, you should have a working phone now. I still need to figure out how to restore WiFi and BlueTooth MAC addresses, but the random ones the OS give you should do fine. Also ignore the NVRAM Error 0x10 wifi network, it indicates both are gone. Also some UI bits and pieces might be wrong on the latest Android because for example the notch values were loaded into device-specific partitions.
Click to expand...
Click to collapse
My device is oneplus nord 2 . When i am using the maui meta software , my phone is always connected on COM6 port and in the maui meta software i can only see COM1 , USB COM and DIAG COM . When i connect the phone the COM6 is displayed and after that when i click on reconnect the maui meta software says please connect cable to target and power on when the phone is already in meta mode. Can you please help me with that ?