Related
Note :- THESE GUIDE IS EXCLUSIVELY FOR ANDROID ONE DEVICE's. & Of course A Rooted Android Device To Flash zip
& EVERY TIME YOU FLASH A ROM ie: Format /System Then IMEI WILL BE GONE SO i MADE FLASHABLE ZIP TO Flash everytime you loose your IMEI [ its better to flash a zip rather than going to "\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001" & Fixing Permissions Manually
You Can Use It Too, On Your Device If Your Partition Is Like This
"\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001"
Here "MP0B_001" Is The IMEI File And Its Corrupt [GENERALLY AFTER FLASHING STOCK ROM]
Then Follow This Guide To Rectify That Problem.
LETS BEGIN
First Download These Files
IMEI MAKER.zip
SCREENSHOT
https://www.dropbox.com/s/9pzf18wxtj7i40l/IMEI MAKER.zip?dl=0
& IMEI REPAIR.zip
SCREENSHOT
https://www.dropbox.com/s/4p2rwoi5oxpth15/IMEI REPAIR.zip?dl=0
So After Downloading The Above Files
Extract IMEI MAKER.ZIP
SCREENSHOT
https://www.dropbox.com/s/o0vs89lob4yf4pv/vlcsnap-2015-01-03-22h23m53s216.png?dl=0
Open IMEI MAKER FOLDER , HOLD "SHIFT & RIGHT CLICK" , Click On "Open Command Window Here"
SCREENSHOT
https://www.dropbox.com/s/lbdzp9ko0t9yons/vlcsnap-2015-01-03-22h24m10s140.png?dl=0
Now In Command prompt (CMD)
-Enter the following text:
imei.exe <15digit_IMEI_1> <15digit_IMEI_2>
(eg: imei.exe 123456789111111 123456789111111)
Then Press ENTER
SCREENSHOT
https://www.dropbox.com/s/j0uss286iv94red/vlcsnap-2015-01-03-22h24m48s31.png?dl=0
NOW YOU WILL SEE A FILE CALLED "MP0B_001_NEW"
Now Rename & Remove "_NEW" From It .
SCREENSHOT
http://www.dropbox.com/s/femtg309chk147v/vlcsnap-2015-01-03-22h25m03s169.png?dl=0
NOW OPEN IMEI REPAIR.ZIP Using Winrar [Software For Pc] [ recommended ]
Inside That Archive Navigate To
data/nvram/md/NVRAM/NVD_IMEI
& DRAG-&-DROP The MP0B_001 File There, Which We Just Created [using IMEI Repair]
Now It Should Look Like This
"/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001"
SCREENSHOTS
https://www.dropbox.com/s/y1ign53lmqrwubs/vlcsnap-2015-01-03-22h26m03s7.png?dl=0
https://www.dropbox.com/s/bsbd0s1jhjt4eww/vlcsnap-2015-01-03-22h26m07s44.png?dl=0
Now Copy The Zip To Your SD CARD [REMEMBER NOT TO PUT IT DEEP INSIDE]
& FLASH IT USING ANY RECOVERY BUT CWM RECOVERY IS RECOMMENDED
& REMEMBER THIS TUTORIAL IS ONLY FOR ANDROID ONE DEVICES AND SIMILAR DEVICES HAVING PARTITION LIKE THIS
/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001
I Uploaded A Video On Youtube For This,
Its only [2:19] Minutes So People Confused Can Watch This Video
http://youtu.be/8DT-32tPbMY
Please Like This Video & Suscribe To My Channel
Share This Video
& Thnx For Watching [If Watched] LOL
DONT PRESS THNX IF I HELPED YOU :laugh:
Sagar Kapasi said:
Note :- THESE GUIDE IS EXCLUSIVELY FOR ANDROID ONE DEVICE's. & Of course A Rooted Android Device To Flash zip
& EVERY TIME YOU FLASH A ROM ie: Format /System Then IMEI WILL BE GONE SO i MADE FLASHABLE ZIP TO Flash everytime you loose your IMEI [ its better to flash a zip rather than going to "\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001" & Fixing Permissions Manually
You Can Use It Too, On Your Device If Your Partition Is Like This
"\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001"
Here "MP0B_001" Is The IMEI File And Its Corrupt [GENERALLY AFTER FLASHING STOCK ROM]
Then Follow This Guide To Rectify That Problem.
LETS BEGIN
First Download These Files
IMEI MAKER.zip
SCREENSHOT
https://www.dropbox.com/s/9pzf18wxtj7i40l/IMEI MAKER.zip?dl=0
& IMEI REPAIR.zip
SCREENSHOT
https://www.dropbox.com/s/4p2rwoi5oxpth15/IMEI REPAIR.zip?dl=0
So After Downloading The Above Files
Extract IMEI MAKER.ZIP
SCREENSHOT
https://www.dropbox.com/s/o0vs89lob4yf4pv/vlcsnap-2015-01-03-22h23m53s216.png?dl=0
Open IMEI MAKER FOLDER , HOLD "SHIFT & RIGHT CLICK" , Click On "Open Command Window Here"
SCREENSHOT
https://www.dropbox.com/s/lbdzp9ko0t9yons/vlcsnap-2015-01-03-22h24m10s140.png?dl=0
Now In Command prompt (CMD)
-Enter the following text:
imei.exe <15digit_IMEI_1> <15digit_IMEI_2>
(eg: imei.exe 123456789111111 123456789111111)
Then Press ENTER
SCREENSHOT
https://www.dropbox.com/s/j0uss286iv94red/vlcsnap-2015-01-03-22h24m48s31.png?dl=0
NOW YOU WILL SEE A FILE CALLED "MP0B_001_NEW"
Now Rename & Remove "_NEW" From It .
SCREENSHOT
http://www.dropbox.com/s/femtg309chk147v/vlcsnap-2015-01-03-22h25m03s169.png?dl=0
NOW OPEN IMEI REPAIR.ZIP Using Winrar [Software For Pc] [ recommended ]
Inside That Archive Navigate To
data/nvram/md/NVRAM/NVD_IMEI
& DRAG-&-DROP The MP0B_001 File There, Which We Just Created [using IMEI Repair]
Now It Should Look Like This
"/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001"
SCREENSHOTS
https://www.dropbox.com/s/y1ign53lmqrwubs/vlcsnap-2015-01-03-22h26m03s7.png?dl=0
https://www.dropbox.com/s/bsbd0s1jhjt4eww/vlcsnap-2015-01-03-22h26m07s44.png?dl=0
Now Copy The Zip To Your SD CARD [REMEMBER NOT TO PUT IT DEEP INSIDE]
& FLASH IT USING ANY RECOVERY BUT CWM RECOVERY IS RECOMMENDED
& REMEMBER THIS TUTORIAL IS ONLY FOR ANDROID ONE DEVICES AND SIMILAR DEVICES HAVING PARTITION LIKE THIS
/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001
I Uploaded A Video On Youtube For This,
Its only [2:19] Minutes So People Confused Can Watch This Video
http://youtu.be/8DT-32tPbMY
Please Like This Video & Suscribe To My Channel
Share This Video
& Thnx For Watching [If Watched] LOL
DONT PRESS THNX IF I HELPED YOU :laugh:
Click to expand...
Click to collapse
didnt help..it didnt work
Wait wait wait... The IMEI is gone?? how can the IMEI be gone? it is how the telecom directorate (Govt.) monitors each phone... thats the reason a couple of years ago all cellular devices without an IMEI (chinese imports mainly) stopped working (they could no longer make calls, but it could be used as a media player).
What You Did
How it didn't helped
Can you say something about it?
-Adarsh- said:
didnt help..it didnt work
Click to expand...
Click to collapse
Here We Are Taking About An Error Which Occurs Mainly After flashing stock Rom On Android One Devices And Yes We Cannot make phone calls in this situation too, So here a Guide to fix it
my imei was also gone that's why this guide
the_prodigal_coder said:
Wait wait wait... The IMEI is gone?? how can the IMEI be gone? it is how the telecom directorate (Govt.) monitors each phone... thats the reason a couple of years ago all cellular devices without an IMEI (chinese imports mainly) stopped working (they could no longer make calls, but it could be used as a media player).
Click to expand...
Click to collapse
Got an error:
set_perm: some changes failed
E:Error in IMEI Repair.zip
(Status 7)
Installation Aborted
the_prodigal_coder said:
Wait wait wait... The IMEI is gone?? how can the IMEI be gone? it is how the telecom directorate (Govt.) monitors each phone... thats the reason a couple of years ago all cellular devices without an IMEI (chinese imports mainly) stopped working (they could no longer make calls, but it could be used as a media player).
Click to expand...
Click to collapse
I accidentally restored the EFS partition from one Nexus 5 to another and ended up with an IMEI of all zeros. It can happen. I was able to repair it with Qualcomm software, but the phone still doesn't see the network. Possibly an antenna issue...
Anyway, it can definitely happen. Also, it is illegal to change your IMEI (in the US at least). I would think it's OK to repair one however. I think the OP should specify that this method should only be used to restore an IMEI to the numbers listed on the device. These can usually be found inside the back cover and on the SIM tray. Check documentation for your model.
Help Needed !! IMEI Fix for Android One not working for me...
I was using CM11 sprout earlier and tried moving back to Stock. I lost my IMEI during this time. I have moved to stock kitkat by doing scatter loading of stock firmware. I have rooted my Android one with CWM recovery. I have used the above tools and generated the MTB_001 and created a zip and installed it with recovery. But, still i have my IMEI as invalid. I even tried replacing the MTB_001 file manually using ES_File explorer and giving permissions 777. Still no luck.
Can someone help me out on how to load proper IMEI as am completely blocked :crying::crying::crying::crying:
Thanks in Advance.
Great Guide! Liked it..Step by Step guide!
But i dont understand why people flash so much..where there is Official Lollipop & CM12 Available for us! Flash Freaking People! :/
You Should Tick All W-R-T All The 9 Then Only It Will Work & Dont Forget To Reboot
SpiceAndroidOne said:
I was using CM11 sprout earlier and tried moving back to Stock. I lost my IMEI during this time. I have moved to stock kitkat by doing scatter loading of stock firmware. I have rooted my Android one with CWM recovery. I have used the above tools and generated the MTB_001 and created a zip and installed it with recovery. But, still i have my IMEI as invalid. I even tried replacing the MTB_001 file manually using ES_File explorer and giving permissions 777. Still no luck.
Can someone help me out on how to load proper IMEI as am completely blocked :crying::crying::crying::crying:
Thanks in Advance.
Click to expand...
Click to collapse
Installation aborted in canvas A1.
When i m flashing the zip file it says installation aborted in canvas A1.:crying::crying::crying::crying::crying:
aryan9090 said:
When i m flashing the zip file it says installation aborted in canvas A1.:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Try to copy paste the IMEI file you just made manually to the directory which is in the main post. It works on my Sparkle V everytime(the copy-paste method).
Does not work for me... please help.....
Sagar Kapasi said:
Note :- THESE GUIDE IS EXCLUSIVELY FOR ANDROID ONE DEVICE's. & Of course A Rooted Android Device To Flash zip
& EVERY TIME YOU FLASH A ROM ie: Format /System Then IMEI WILL BE GONE SO i MADE FLASHABLE ZIP TO Flash everytime you loose your IMEI [ its better to flash a zip rather than going to "\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001" & Fixing Permissions Manually
You Can Use It Too, On Your Device If Your Partition Is Like This
"\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001"
Here "MP0B_001" Is The IMEI File And Its Corrupt [GENERALLY AFTER FLASHING STOCK ROM]
Then Follow This Guide To Rectify That Problem.
LETS BEGIN
First Download These Files
IMEI MAKER.zip
SCREENSHOT
& IMEI REPAIR.zip
SCREENSHOT
So After Downloading The Above Files
Extract IMEI MAKER.ZIP
SCREENSHOT
Open IMEI MAKER FOLDER , HOLD "SHIFT & RIGHT CLICK" , Click On "Open Command Window Here"
SCREENSHOT
Now In Command prompt (CMD)
-Enter the following text:
imei.exe <15digit_IMEI_1> <15digit_IMEI_2>
(eg: imei.exe 123456789111111 123456789111111)
Then Press ENTER
SCREENSHOT
NOW YOU WILL SEE A FILE CALLED "MP0B_001_NEW"
Now Rename & Remove "_NEW" From It .
SCREENSHOT
NOW OPEN IMEI REPAIR.ZIP Using Winrar [Software For Pc] [ recommended ]
Inside That Archive Navigate To
data/nvram/md/NVRAM/NVD_IMEI
& DRAG-&-DROP The MP0B_001 File There, Which We Just Created [using IMEI Repair]
Now It Should Look Like This
"/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001"
SCREENSHOTS
Now Copy The Zip To Your SD CARD [REMEMBER NOT TO PUT IT DEEP INSIDE]
& FLASH IT USING ANY RECOVERY BUT CWM RECOVERY IS RECOMMENDED
& REMEMBER THIS TUTORIAL IS ONLY FOR ANDROID ONE DEVICES AND SIMILAR DEVICES HAVING PARTITION LIKE THIS
/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001
I Uploaded A Video On Youtube For This,
Its only [2:19] Minutes So People Confused Can Watch This Video
Please Like This Video & Suscribe To My Channel
Share This Video
& Thnx For Watching [If Watched] LOL
DONT PRESS THNX IF I HELPED YOU :laugh:
Click to expand...
Click to collapse
I followed complete steps and it got installed successfully but the IMEI is still 0 !! Does this even works on Nexus 5? Please help.
deepak21 said:
I followed complete steps and it got installed successfully but the IMEI is still 0 !! Does this even works on Nexus 5? Please help.
Click to expand...
Click to collapse
did you replace the file and rename it (just asking).
Saurabh K said:
did you replace the file and rename it (just asking).
Click to expand...
Click to collapse
Yes, I did... I followed every step very carefully and there were no error message at all.. everything was successful.
deepak21 said:
Yes, I did... I followed every step very carefully and there were no error message at all.. everything was successful.
Click to expand...
Click to collapse
Is your IMEI back ???? If not.......
try to flash the nvram.img using:
fastboot flash nvram nvram.img
I think that nvram partition may have some problem, just give it a try..and reply
Saurabh K said:
Is your IMEI back ???? If not.......
try to flash the nvram.img using:
fastboot flash nvram nvram.img
I think that nvram partition may have some problem, just give it a try..and reply
Click to expand...
Click to collapse
So far nothing worked, will try anything to get it back. Do I need to clear the cache as well ? Will I lose my data? Just asking
---------- Post added at 08:55 AM ---------- Previous post was at 08:00 AM ----------
Saurabh K said:
Is your IMEI back ???? If not.......
try to flash the nvram.img using:
fastboot flash nvram nvram.img
I think that nvram partition may have some problem, just give it a try..and reply
Click to expand...
Click to collapse
Also, I don't have any nv backup with me... could you please share any nvram image or let me know where can I get it?
deepak21 said:
So far nothing worked, will try anything to get it back. Do I need to clear the cache as well ? Will I lose my data? Just asking
---------- Post added at 08:55 AM ---------- Previous post was at 08:00 AM ----------
Also, I don't have any nv backup with me... could you please share any nvram image or let me know where can I get it?
Click to expand...
Click to collapse
I have the stock KITKAT 4.4.4 nvram image, but I dont know will it work. I will try to extract the image from stock 5.1 and reply soon...
---------- Post added at 09:09 AM ---------- Previous post was at 08:56 AM ----------
deepak21 said:
So far nothing worked, will try anything to get it back. Do I need to clear the cache as well ? Will I lose my data? Just asking
---------- Post added at 08:55 AM ---------- Previous post was at 08:00 AM ----------
Also, I don't have any nv backup with me... could you please share any nvram image or let me know where can I get it?
Click to expand...
Click to collapse
sorry, but i couldn't backup the 5.1 stock nvram but i will send you nvram.img from stock kitkat ROM. Flash and redo the procedure from scratch...and tell your device model also..
First point to note is that only full formatting makes the device lose IMEI,not normal data,system,cache formatting which is required for installing custom roms.When your partition table is messed up you get lots of errors when trying to wipe or mount any partition from custom recoveries,thus leaving you with only option to format before flashing stock rom through sp flash tools.It is after this flash that nvram loses your unique IMEI number.In my case I had backed up my stock rom through cwm recovery,now to restore my IMEI, I just extract the contents of /data/nvram/.....NVD_IMEI from my backup( three files in total) and push it to my to the same directory using adb push command,and it works for me.There is no need to push three cos only one file is relevant .But this is only temporary solution,cos after every reset you will lose your IMEI. It is better to backup the nvram partiton using dd command so that it could be flashed later,which would persist through installs.
tealio said:
I accidentally restored the EFS partition from one Nexus 5 to another and ended up with an IMEI of all zeros. It can happen. I was able to repair it with Qualcomm software, but the phone still doesn't see the network. Possibly an antenna issue...
Anyway, it can definitely happen. Also, it is illegal to change your IMEI (in the US at least). I would think it's OK to repair one however. I think the OP should specify that this method should only be used to restore an IMEI to the numbers listed on the device. These can usually be found inside the back cover and on the SIM tray. Check documentation for your model.
Click to expand...
Click to collapse
please brother how did you "repair it with Qualcomm software to restore an IMEI to the numbers listed on the device. These can usually be found inside the back cover and on the SIM tray"? please can you pm me or email: [email protected] the software and guide pleeeeeeeeeeeeeeeeeeeeaaaaaaasssssssssssseeeeeee
need to fix my htc mytouch 4G and my LG vu II
Thanks
DISCLAIMER: I am not responsible for anything that happens while/after flashing these files. Your device's fate is your own responsibility. Proceed at your own risk.
WARNING: Your device's warranty WILL BE void after this.
This thread and all its contents are meant solely for the ROW variant: X3a40.
Starting from S217 you can unlock the bootloader directly using Fastboot commands without modifying any file.
I will assume that you are aware of the basics of fastboot, flashing, TWRP, etc.
Supported stock ROMs: S217
UNLOCKING BOOTLOADER & ROOTING VIA TWRP
WARNING: Everything apart from data in external SD card will be wiped. Make sure to backup everything.
Make sure you read this post completely and carefully before implementing the steps.
Make sure you have backed up your data (everything apart from external SD card) on a PC or other storage.
Run this Fastboot command:
Code:
fastboot oem unlock-go
(Of course you need to put the phone in Fastboot mode to run a Fastboot command. Refer this if you don't know key combinations for X3a40)
Display turns off. That's all, you have unlocked the bootloader.
Hold power button for sometime to power off, release and hold again to power on.
No data gets wiped till this stage.
In theory(not tested all possibilities yet): Now if you make any modification to the filesystem or boot anything directly or after flashing via Fastboot, data gets wiped(first time only).
Confirmed behaviour:
If you boot TWRP directly (one-time TWRP) [fastboot boot twrp.img], it will boot, wipe and restart the device normally.
If you flash TWRP [fastboot flash recovery twrp.img] and reboot to recovery, TWRP will be overwritten by stock recovery, stock recovery will boot, wipe and restart the device normally.
Once restarted, you can setup the phone as there won't be any more wipes.
If you want to make any changes to the device's filesystem (e.g. get root access), you need to patch the boot image otherwise you will be stuck on Lenovo logo after making any changes and restarting.
The easiest way to do this is to flash the latest SuperSU zip which can always be grabbed from here: http://download.chainfire.eu/supersu-stable
To flash the zip you need TWRP. Either directly boot(one-time TWRP) or flash and reboot to TWRP (it won't be overwritten now).
On first TWRP boot you will be asked whether to allow modifications to system. Choose any option according to your needs and then install the SuperSU zip.
If you chose to allow modifications to system or made any changes manually, make sure you flash the SuperSU zip before restarting else device will get stuck on Lenovo logo.
If you somehow still somehow forget to implement the above step, and are stuck on Lenovo logo, don't worry. You can simply go to TWRP, flash SuperSU and reboot.
Once SuperSU is installed (more appropriately, boot image is patched by SuperSU zip), you can make any modifications you feel like. Good luck ! :highfive:
NOTE:
You don't need to unlock bootloader again if you have done it earlier. It stays unlocked until you manually lock it (via fastboot oem lock command). You can always check current status using this command: fastboot oem device-info
Data wipe will happen only if you unlock while on S217.
DOWNLOADS
ADB Kit + TWRP v2.8.7.7 by SevenMaxs (RECOMMENDED)
TWRP v3.0.2 by arpit_nnd (Material Theme) (EXPERIMENTAL; needs to let the the display timeout and awakened once to work)
Drivers + QFIL (UPDATED: 5/4/16)
Reserved.
Reserved.
Hey that's great. Can you please provide details for rooting
broto1988 said:
Finally rooted it !
Click to expand...
Click to collapse
How? U installed SU binaries from twrp?? just guessing..
Cool : AWESOME : we are waiting for
Now XDA has to provide us a dedicated forum for Vibe X3
---------- Post added at 02:15 PM ---------- Previous post was at 02:15 PM ----------
prathmesh01 said:
How? U installed SU binaries from twrp?? just guessing..
Click to expand...
Click to collapse
root.zip contains everything , just needs to install using twrp
insanelydeepak said:
Cool : AWESOME : we are waiting for
Now XDA has to provide us a dedicated forum for Vibe X3
---------- Post added at 02:15 PM ---------- Previous post was at 02:15 PM ----------
root.zip contains everything , just needs to install using twrp
Click to expand...
Click to collapse
i installed supersu.zip and bricked my device(unbricked by qfil method). can u give me the link for root.zip u installed.
edit: i saw the freshly edited post now
---------- Post added at 02:54 PM ---------- Previous post was at 02:36 PM ----------
can i install this twrp in r/w mode?
---------- Post added at 03:29 PM ---------- Previous post was at 02:54 PM ----------
can i install twrp in r/w mode?
---------- Post added at 03:49 PM ---------- Previous post was at 03:29 PM ----------
error while flashing modified files by qfil
Start Download
Program Path:C:\Users\Prathmesh\Downloads\Modified Bootloader Images for QFIL\Modded Images for QFIL\prog_emmc_firehose_8992_ddr.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM3 -s 13:C:\Users\Prathmesh\Downloads\Modified Bootloader Images for QFIL\Modded Images for QFIL\prog_emmc_firehose_8992_ddr.mbn 'Current working dir: C:\Users\Prathmesh\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Users\Prathmesh\Downloads\Modified
20:17:28: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
20:17:28: ERROR: function: sahara_main:854 Sahara protocol error
20:17:28: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
edit: solved after i moved the folder in root on other drive
@arpit_nnd You said to "Download the ZIP corresponding to your current stock firmware version from 'Secure Boot Disabled Boot Images' ". The thing is I have downloaded for 138 which I am currently on. But the QFIL package given in your other thread is 130. So this part is confusing me.
zTweaked said:
@arpit_nnd You said to "Download the ZIP corresponding to your current stock firmware version from 'Secure Boot Disabled Boot Images' ". The thing is I have downloaded for 138 which I am currently on. But the QFIL package given in your other thread is 130. So this part is confusing me.
Click to expand...
Click to collapse
You don't have to download the QFIL package. Sorry about that, Step 1 of PC Flashing guide isn't needed for rooting, just follow Step 2-10.
Thanks for the feedback.
When I try this step "Go to the folder where the drivers were installed ('C:/Program Files(x86)/LenovoUsbDriver' by default), get inside each folder one-by-one, right-click on the '.inf' file and click 'Install'."
It says " the Inf file you selected doesn't support this type of installation".
Fix?
arpit_nnd said:
You don't have to download the QFIL package. Sorry about that, Step 1 of PC Flashing guide isn't needed for rooting, just follow Step 2-10.
Thanks for the feedback.
Click to expand...
Click to collapse
damn! already downloaded it on mobile data
essentialblend said:
When I try this step "Go to the folder where the drivers were installed ('C:/Program Files(x86)/LenovoUsbDriver' by default), get inside each folder one-by-one, right-click on the '.inf' file and click 'Install'."
It says " the Inf file you selected doesn't support this type of installation".
Fix?
Click to expand...
Click to collapse
Which Windows version ?
Did you disable driver signature enforcement?
zTweaked said:
damn! already downloaded it on mobile data
Click to expand...
Click to collapse
Don't delete it, you might need it sometime later.
arpit_nnd said:
Which Windows version ?
Did you disable driver signature enforcement?
Click to expand...
Click to collapse
I'm on Win 7 x64 .I skipped steps 3 to 5 as it was written below. So I have to do the 'restart windows to advanced mode thing' ?
arpit_nnd said:
Don't delete it, you might need it sometime later.
Click to expand...
Click to collapse
Yes, of course I won't delete it! Anyway, will unlocking bootloader or flashing twrp wipe internal storage? Just need a final confimartion before proceeding.
zTweaked said:
Yes, of course I won't delete it! Anyway, will unlocking bootloader or flashing twrp wipe internal storage? Just need a final confimartion before proceeding.
Click to expand...
Click to collapse
Read the OP carefully, it's all there.
essentialblend said:
I'm on Win 7 x64 .I skipped steps 3 to 5 as it was written below. So I have to do the 'restart windows to advanced mode thing' ?
Click to expand...
Click to collapse
No, you don't have to, rather it isn't available in Windows 7.
Look up the web for installing drivers.
One thing that I can suggest is to do is to boot into Qualcomm Diagnostic Mode, connect to PC, open Device Manager in Windows, select each of unknown devices related to the phone (there will be 3), go into Properties for each and install driver by browsing to Lenovo driver folder.
@arpit_nnd Installing Lenovo_adb.inf doesn't show a confirmation or failure dialog. Installing Lenovo_vcom.inf gives me "The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering." The other 3 infs install nicely.
zTweaked said:
@arpit_nnd Installing Lenovo_adb.inf doesn't show a confirmation or failure dialog. Installing Lenovo_vcom.inf gives me "The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering." The other 3 infs install nicely.
Click to expand...
Click to collapse
You can skip the VCOM one...
arpit_nnd said:
You can skip the VCOM one...
Click to expand...
Click to collapse
What about the adb? Idk much but I had once tried simple adb commands and they worked in x3.
---------- Post added at 01:17 AM ---------- Previous post was at 12:47 AM ----------
prathmesh01 said:
20:17:28: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
20:17:28: ERROR: function: sahara_main:854 Sahara protocol error
20:17:28: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
edit: solved after i moved the folder in root on other drive
Click to expand...
Click to collapse
How did you solve it exactly/ I am getting the same error
Hello, I am the owner of a p10 with VTR-L09C02B155, I have not been able to unblock the official bootloader but I have seen that the firmware finder application offers me the possibility to install the official version of VTR-L09C432B162 (as shown by IMEI verification). My question is someone else trying this rebranding method? Thank you.
Hey, it's not quite that simple. I just did this with my p10. You need the full firmware files as well as the oem. File. Have you got the bootloader unlock code from Huawei? You need that first. I'll try and do a write-up as there isn't a p10 specific one yet
---------- Post added at 07:01 PM ---------- Previous post was at 06:41 PM ----------
Here are the steps I took to debrand my VTR-L09C706 to a VTR-L29C636 (29 is dual sim, not needed but good to have). 636 is the asia global which gets quite a few updates.
Caution: This is a guide of what I did and am not responsible if anything happens to your phone!
Thank you to @mankindtw for his writeup.
1. Navigate to https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Download the files for "Base", OS ( I had windows), and Model (P10). These are all .zip files with the same top folder of HWOTA, you need to extract them all where you want them, but take off the last folder (mine wanted to extract to \Desktop\HWOTA_2017050101_Windows, but I modified to extract to \Desktop\). This ensures they build the right folder structure.
2. Using Firmware finder (I used on PC). Locate the VTR-L29C636B166 Rom that is 2.971GB. you will need to download all 3 zip files for this
update.zip
update_data_full_public.zip" download file, and rename it to "update_data_public.zip"
update_full_hw_spcseas.zip" download file, and rename it to "update_all_hw.zip"
3. Put all 3 zip files in your \HWOTA\update folder you should now have
4. now in \HWOTA run update.bat and follow instructions. you will need to select Rebrand, and select VTR-L29C636
5. once its completed your phone will go through an update process, mine ended up hanging when finsished and said "phone will reboot". ended holding power button to restart. once I had the phone booted up I went back into recovery and did a factory reset and wipe cache to be sure things were cleaned up.
Hello,
I am stuck at "Please wait for upload files and do not press any key". It is stuck on this step since long time.
Quintman said:
Hey, it's not quite that simple. I just did this with my p10. You need the full firmware files as well as the oem. File. Have you got the bootloader unlock code from Huawei? You need that first. I'll try and do a write-up as there isn't a p10 specific one yet
---------- Post added at 07:01 PM ---------- Previous post was at 06:41 PM ----------
Here are the steps I took to debrand my VTR-L09C706 to a VTR-L29C636 (29 is dual sim, not needed but good to have). 636 is the asia global which gets quite a few updates.
Caution: This is a guide of what I did and am not responsible if anything happens to your phone!
Thank you to @mankindtw for his writeup.
1. Navigate to https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Download the files for "Base", OS ( I had windows), and Model (P10). These are all .zip files with the same top folder of HWOTA, you need to extract them all where you want them, but take off the last folder (mine wanted to extract to \Desktop\HWOTA_2017050101_Windows, but I modified to extract to \Desktop\). This ensures they build the right folder structure.
2. Using Firmware finder (I used on PC). Locate the VTR-L29C636B166 Rom that is 2.971GB. you will need to download all 3 zip files for this
update.zip
update_data_full_public.zip" download file, and rename it to "update_data_public.zip"
update_full_hw_spcseas.zip" download file, and rename it to "update_all_hw.zip"
3. Put all 3 zip files in your \HWOTA\update folder you should now have
4. now in \HWOTA run update.bat and follow instructions. you will need to select Rebrand, and select VTR-L29C636
5. once its completed your phone will go through an update process, mine ended up hanging when finsished and said "phone will reboot". ended holding power button to restart. once I had the phone booted up I went back into recovery and did a factory reset and wipe cache to be sure things were cleaned up.
Click to expand...
Click to collapse
--- Please don't quote this entire post ---
I have, with the help of two people who's XDA I don't know, just unlocked an Honor 9 Lite without an unlock code!:angel: The method follows:
Initial revision
0. Prepare adb and fastboot. On windows, change all
Code:
fastboot
commands to
Code:
.\fastboot
and similarly for
Code:
adb
(skip to step 2 if you have the June 2018 patch or earlier)
1a. Downgrade firmware to 8.0.0.xxx (June patch) via androidhost.ru - search for your device, get a C432 version.
1b. Downgrade, instructions are in the 'ReleaseDoc' folder. Use the forced install method
(do not reboot the phone until step 3a is complete)
2a. Enter
Code:
fastboot
2b. Enter powershell or terminal and type:
Code:
fastboot oem hwdog certify begin;fastboot oem get-product-model
2c. Send the result to @huaweihax telegram group or in this thread (telegram will have faster response times)
2d. We will send you your slock when we gets a chance. Please be patient, we have real lives. Download it on the same pc as you have fastboot on.
2e. Copy the slock to your working directory
2f. Type in your shell:
Code:
fastboot flash slock <slock_filename>
(Download twrp on the pc that has fastboot, copy to working directory)
3a.
Code:
fastboot flash erecovery_ramdisk <twrp filename>
3b. Read step 3c and 3d
3c.
Code:
fastboot reboot
3d. Hold volume up AFTER the phone vibrates
3e. Twrp should boot up. If not, reboot it and try 3d again
(Each reboot until step 4 is complete, you will restart step 4)
4a. Connect usb
4b.
Code:
adb shell dd if=/dev/block/bootdevice/by-name/nvme of=/tmp/nvme
4c.
Code:
adb pull /tmp/nvme
You may now reboot the device, if you want.
5a. Open the nvme file in a hex editor. Find 'FBLOCK' in the file. There should be '8' shortly before the fblock. Move down exactly one line from '8' and you will see 01. Change that to 00 and repeat for all instances of fblock in the file. Save the file.
5c.
Code:
adb push nvme /tmp/nvme
5d.
Code:
adb shell dd if=/tmp/nvme of=/dev/block/bootdevice/by-name/nvme
6. Reboot!
CONGRATS! YOUR DEVICE IS NOW UNLOCKED!
Latest revision:
0. Prepare adb and fastboot. On windows, change all fastboot commands to ./fastboot and similarly for adb
Skip to step 2 if you have the June 2018 patch or earlier
1a. Downgrade firmware to June patch via androidhost.ru - search for your device, any C number should work.
1b. Downgrade, instructions are in the 'ReleaseDoc' folder. Use the forced install method
2a. Enter fastboot
2b. DO NOT REBOOT THE PHONE UNTIL STEP 3a is complete!!! Failing to follow this will result in anger!
2c. Enter powershell or terminal and type:
Code:
fastboot oem hwdog certify begin;fastboot oem get-product-model;fastboot oem get-build-number
2c. Send the result in the telegram group @huaweiHax (link to the public group is at the start of the channel), or, if that's entirely impossible, PM @OldDroid on XDA.
2d. A nice guy will send you your slock. Please be patient, they have real lives. Download it on the same pc as you have fastboot on.
2e. Copy the slock to your working directory
2f.
Code:
fastboot flash slock <slock_filename>
(Download twrp on the pc that has fastboot, copy to working directory)
3a.
Code:
fastboot flash erecovery_ramdisk <twrp filename>
3b. Read step 3c and 3d
3c.
Code:
fastboot reboot
3d. Hold volume up AFTER the phone vibrates
3e. Twrp should boot up. If not, reboot it and try 3d again
4a. Connect usb
4b.
Code:
adb shell dd if=/dev/block/bootdevice/by-name/nvme of=/tmp/nvme
4c.
Code:
adb pull /tmp/nvme
WARNING: FOLLOW THESE STEPS VERY CAREFULLY AND DOUBLE-CHECK EVERYTHING!
5a. Open the nvme file with a hex editor. Repeat step 5b until you have done all the instances of FBLOCK.
5b. Search the file for FBLOCK. For each instance, you should see the character 8 shortly before. Go down exactly one line from the 8. Select the .. You should see 01 become highlighted in the hex area. Change the 01 to 00 and repeat 6 more times (7 in total). Save the file as nvmepatched
5c.
Code:
adb push nvmepatched /tmp/nvme
5d.
Code:
adb shell dd if=/tmp/nvme of=/dev/block/bootdevice/by-name/nvme
6. Reboot!
CONGRATS! YOUR DEVICE IS NOW UNLOCKED!
----------------------------------------------------------------
Files you might find useful:
nvme.zip: a twrp flashable zip that automates step 5 of the instructions. I have tested it and it works fine for me. If TWRP crashes and restarts, that's fine, but idk why it happens. If it happens to you, please send /tmp/recovery.log to me in pm or here, or in telegram
autoroot.zip: a zip file containing a python script and related files to automatically unlock Huawei's. To use it, put a twrp file called 'twrp-kirin.img' in the 'files' subfolder. I cannot upload that file due to XDA file size restrictions.
https://www.androidfilehost.com/?w=files&flid=285583: thanks to @mrmazak, this is a windows batch tool version of autoroot.zip
In the attached photos you will see correct and incorrect converted "slock files"
When you follow the guide from above. Between 2-C and 2-D.
If the you get just a long string of letters and numbers (512 characters to be exact). That string of numbers it that state is "text" it needs to be "HEX". , to do this there are command line tools to do it. But it can be done in a user friendly way in a hex editor program. But this needs to done as hex and not text. The photos show both examples.
In the correct edited photo the long string is written to the left side (the hex area)
In the incorrect edited photo the long string is written to the right side (the text area).
SLOCK CONVERSION
FOR command line use
Copy the long string of text as regular txt file NO EXTRA SPACES -- for this example name it slock.txt
Command line code for linux: Needs "XDD" It should already be installed on most systems.(inside VIM)
Code:
cat slock.txt | xxd -r -p > binary-slock.bin
Command line code for Windows: Needs "XDD.exe" It canbe found inside VIM http://www.vim.org/
Code:
type slock.txt | xxd.exe -r -p > binary-slock.bin
NVME EDITS
Linux terminal
Code:
sed 's/\x46 \x42 \x4C \x4F \x43 \x4B \x00 \x00 \x01 \x00 \x00 \x00 \x01/\x46 \x42 \x4C \x4F \x43 \x4B \x00 \x00 \x01 \x00 \x00 \x00 \x00/g' nvme > temp
Windows cmd version needs GNU-SED
OR
reg-expression-tool LIKE "jrepl.bat" (one of my favorite little tools)
Code:
files\JREPL.BAT "\x46\x42\x4C\x4F\x43\x4B\x00\x00\x01\x00\x00\x00\x01" "\x46\x42\x4C\x4F\x43\x4B\x00\x00\x01\x00\x00\x00\x00" /m /x /f modified-nvme /o -
Scripted method
Windows batch file tool
Use newest version in the folder. And allow tool to update, when first ran.
.
.
mrmazak said:
this sounds like great news for continuing custom roms on Huawei.
Just want to ask about the above section.
Are you saying just the sending of data will be rolled into an app, or the whole thing will be self contained in an app?
Click to expand...
Click to collapse
Just the second stage of sending data, olddroid is 'thinking' about making them both automated, but right now, neither is.
hackintosh5 said:
Just the second stage of sending data, olddroid is 'thinking' about making them both automated, but right now, neither is.
Click to expand...
Click to collapse
It'd be really helpful if he did that. And by the way thanks for sharing.
Hi my phone version is c185 what should i do?
moonknight01 said:
Hi my phone version is c185 what should i do?
Click to expand...
Click to collapse
Try to use the c00 firmware, it may or may not dload. If it fails, theres not much you can do.
hackintosh5 said:
Try to use the c00 firmware, it may or may not dload. If it fails, theres not much you can do.
Click to expand...
Click to collapse
In c185 wouldnt work?
Sent from my LLD-L21 using Tapatalk
moonknight01 said:
In c185 wouldnt work?
Click to expand...
Click to collapse
There's no c185 dloadfirmware, so try c432. It may fail the install, it might not. I just don't know.
Honor 9 lite c636
Can C636 work?
aldinista said:
Can C636 work?
Click to expand...
Click to collapse
Again, try another firmware like c432 or c00, but it all depends on whether the dload works or not. If it doesn't install, you'll have to find one that does. If it installs you'll be ok. Just flash the correct model firmware after completing the exploit
hackintosh5 said:
Again, try another firmware like c432 or c00, but it all depends on whether the dload works or not. If it doesn't install, you'll have to find one that does. If it installs you'll be ok. Just flash the correct model firmware after completing the exploit
Click to expand...
Click to collapse
Oke i try.. ?
Hehehe, sorry because I'm not yet so familiar.
I'm still a beginner ??
@hackintosh5
My LLD-L21 (C636) bricked with Bootloader is Relocked & FRP Locked, but has been solved now with the help of your tutorial.
Thanks you so much sir. :good::good::good:
Wait but how can you flash something from fastboot if the bootloader is locked?
Fredin_ said:
Wait but how can you flash something from fastboot if the bootloader is unlocked?
Click to expand...
Click to collapse
Please unquote the entire post... Then I'll respond.
It beggars belief sometimes..........I mean its the very FIRST line in the bloody post.........???
What more can you do, even it was in BIG RED CAPITALS it would still happen.
Sparkrite said:
It beggars belief sometimes..........I mean its the very FIRST line in the bloody post.........???
What more can you do, even it was in BIG RED CAPITALS it would still happen.
Click to expand...
Click to collapse
Dude chill......... was a mistake sorry ?
---------- Post added at 06:12 PM ---------- Previous post was at 06:12 PM ----------
hackintosh5 said:
Please unquote the entire post... Then I'll respond.
Click to expand...
Click to collapse
Sorry forgot that part ?
Fredin_ said:
Dude chill......... was a mistake sorry ?
---------- Post added at 06:12 PM ---------- Previous post was at 06:12 PM ----------
Sorry forgot that part ?
Click to expand...
Click to collapse
Okay
Fredin_ said:
Wait but how can you flash something from fastboot if the bootloader is locked?
Click to expand...
Click to collapse
Slock and rescue_recovery can be flashed without unlocking. Don't ask me why, ask Wavei.
hackintosh5 said:
Slock and rescue_recovery can be flashed without unlocking. Don't ask me why, ask Wavei.
Click to expand...
Click to collapse
K thanks man?
SeenThings said:
@hackintosh5
My LLD-L21 (C636) bricked with Bootloader is Relocked & FRP Locked, but has been solved now with the help of your tutorial.
Thanks you so much sir. :good::good::good:
Click to expand...
Click to collapse
Hi bro did you get unlock boot loader?
Sent from my LLD-L21 using Tapatalk
Hey guys, i have a problem with the K20 Pro, i tried a gps module from magisk but it didn't work properly and now when i try to format data, factory reset this error appears: "Failed to mount /persist" (Invalid argoument). How can i fix this? I Was on EU Android Q Rom. I Can still boot up but things as Pop up camera are buggy
I think if someone with TWRP do a Backup of persist and upload somewhere for me i can back it up from twrp!
Youshouldsmile said:
Hey guys, i have a problem with the K20 Pro, i tried a gps module from magisk but it didn't work properly and now when i try to format data, factory reset this error appears: "Failed to mount /persist" (Invalid argoument). How can i fix this? I Was on EU Android Q Rom. I Can still boot up but things as Pop up camera are buggy
I think if someone with TWRP do a Backup of persist and upload somewhere for me i can back it up from twrp!
Click to expand...
Click to collapse
You can extract the persist.img file from the MIUI Q beta fastboot ROM
i have the same problem
tried doing fastboot erase persist , but no luck ( write protected)
using twrp or fox recovery both giving me the same error ( failed to mount persist, invalid argiument..
any help ?
---------- Post added at 10:54 PM ---------- Previous post was at 10:48 PM ----------
also the problem happened after a module install using magisk.. i really dont know how persist partition got damaged when it is write protected !
sar78mad said:
i have the same problem
tried doing fastboot erase persist , but no luck ( write protected)
using twrp or fox recovery both giving me the same error ( failed to mount persist, invalid argiument..
any help ?
---------- Post added at 10:54 PM ---------- Previous post was at 10:48 PM ----------
also the problem happened after a module install using magisk.. i really dont know how persist partition got damaged when it is write protected !
Click to expand...
Click to collapse
Fix: Just extract persist.img from your fastboot rom then use LR.Team TWRP to flash it in the persist partition after that when you boot to system open the camera app several times until a message apperars to calibrate, tick on it and you will see a popup message tell calibration successful.
Done.
i've managed to fix the problem with persist partition
i used persist.img form stock 10.3.3 global fastboot rom , and copied it to sdcard. then did the adb shell command with (dd if=/sdcard/perist.img of=/dev/block/"add here persist partition dir")
worked and my device now is working like a charm..
sar78mad said:
i've managed to fix the problem with persist partition
i used persist.img form stock 10.3.3 global fastboot rom , and copied it to sdcard. then did the adb shell command with (dd if=/sdcard/perist.img of=/dev/block/"add here persist partition dir")
worked and my device now is working like a charm..
Click to expand...
Click to collapse
Bro could please tell us step by step ? i am getting mad. please
Eng.Raman said:
Fix: Just extract persist.img from your fastboot rom then use LR.Team TWRP to flash it in the persist partition after that when you boot to system open the camera app several times until a message apperars to calibrate, tick on it and you will see a popup message tell calibration successful.
Done.
Click to expand...
Click to collapse
perfect
I read my computer partitions. After finding the number of the block that corresponds to my team, copy the persist of the rom stock to my internal memory in twrp and then flash with your command and add my block.
in my case note 10 pro (sweet)
dd if=/sdcard/persist.img of=/dev/block/sdf7
VERY CAREFUL NOT TO USE THIS COMMAND ON ANOTHER computer. each person must read the exact block that corresponds to your mobile reference.
I guess your problem is more of hardware issue ,but have to test to know.
I come to this conclusion because magisk does not modify partitions nor system files , I would start with a clean fastboot flash of the phone (be careful of the lock checkbox).
Then judge from there , if phone still presents anomalies then my first assumption is true.