Database Develop

[REQ] 10.1 System Dump (.img)

Hi,
Could someone please dump a system image for the 10.1? It's reeeealy easy
There are a few soft-bricks already due to people flashing the wrong image or to the wrong partition ( you know who you are, people! ) and you would be doing them a massive favour if you did.
If you already have busybox, all you have to do is run this:
Code:
dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Then you can pick it up the system.img from /sdcard
Code:
adb pull /sdcard/system.img
ZIP it and upload it somewhere ( Dropbox ) and you're done!
TIA
BC

Http://droidbasement.com/galaxy/sys-backup
The system_extra backup contains extra stuff (from the 'tools' compilation).

Thanks. There are a couple of people who will really appreciate that
OT: I just repacked your su/busybox update with the boot.img from the Voda 10.1 and it works fine. Link to the Voda boot.img is here

Would it be possible to get the original system image without the extra tools? I am trying to flash this image however I keep getting a remote error when I do so. Could it have something to do with the fact that this image is 600MB compared to other system images that are around 200 MB like for the gt 10.1v? Thanks again for posting it.

the extra stuff is not making it 600mb (maybe 10-20). It is quite big on the IO.
In order to fastboot flash it you must have an unlocked bootloader to do so (which in unlocked by default on the IO).

Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.

nadewad said:
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
Click to expand...
Click to collapse
ill retake the dump and upload it. ill do it tonight. maybe some corruption ocurred, etc.

It might be the same trick where you have to create a sparse ext4 image instead of ripping the image straight, because fastboot transfers the entire image in RAM before flashing it...
Try
Code:
make_ext4fs -l 512m -s /sdcard/system.img /system

If anyone has created a system image but isn't quite sure if it is the correct one, I'll be glad to try it out as I am one of those people who soft bricked their device. Just PM me and I'll be more than happy to flash my device and verify the stability of the system image. Thanks.
Nader

bump? Did anyone end up getting a system image? Thanks.
Nader

Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.

nadewad said:
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Run it on the device instead of using dd on the device.

ydaraishy said:
Run it on the device instead of using dd on the device.
Click to expand...
Click to collapse
He has a soft-bricked device so that's not an option unfortunately.
You can do a MD5 checksum of the file and get pershoot to check it against the original.
Otherwise, in the mean time, you can try this tool:
http://www.diskinternals.com/download/
You want the tool called "Linux Reader 2.0". It says it can only read ext2 and ext3, but I just tried it on my 10.1v system image which I created using the same method as pershoot, and it works fine.
...and see if you can mount it in Windows. If you can, the image is (probably) OK.

bcmobile said:
He has a soft-bricked device so that's not an option unfortunately.
Click to expand...
Click to collapse
Well, obviously, someone _else_ has to provide that image from a working device.

Same error here, while trying to flash the system.img. Any alternatives?
Thanks,
Eduardo.

I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome

nadewad said:
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
Click to expand...
Click to collapse
Samsung may charge you for the repair
Before you send it back, just have one more go at flashing the boot.img which smaskell provided from here. Just do a:
Code:
fastboot flash boot boot.img
The boot loop may be due to a different (incompatible) kernel if you still have the boot partition from the 10.1v
Failing that, if you're still up for it, do a:
Code:
adb logcat > %userprofile%\desktop\logcat-out.txt
...then open the locgat-out.txt file on your desktop and post the contents here or just zip and attach the file. That might give us something to work with

I am also not able to flash this system.img file. I get the same error.

I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?

nadewad said:
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
Click to expand...
Click to collapse
My tablet is showing P7100 as well. I tested with my employee's GT LE, and it shows the same. So, this is not the problem...
adb is not accessible to me as well.

Help with moto x

I tried to manually flash back to stock 4.4.2 (so I can upgrade to 4.4.3) on my moto x but whenever I type the command "mfastboot flash system system.img" I get "invalid sparse image chunk count. The rest of the commands worked. Now my phone is stuck in the unlocked bootloader screen and I don't know what else to do. Help please?

Try the latest mfastboot see if it helps
Sent from my XT1053 using XDA Free mobile app

serophia said:
Try the latest mfastboot see if it helps
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Where would I get the latest version?

http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip

KidJoe said:
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
Click to expand...
Click to collapse
Thanks for the link. I used it and I still got the same error.

Make sure you are using the system.img from the correct firmware. Below is a link to the Moto model firmwares. Download the right one, unzip the files until you get to the .img files and use that system.img.
Motorola Firmwares

I've used different zip extractors and it always says the system.img file is broken. =O!
Thanks for the help guys! Appreciated

n0obpr0 said:
I've used different zip extractors and it always says the system.img file is broken. =O!
Thanks for the help guys! Appreciated
Click to expand...
Click to collapse
Try the steps listed in this post:
http://forum.xda-developers.com/showpost.php?p=53228057&postcount=148
Basically, the idea here is to flash gpt (partition) and motoboot ONLY, then reboot back into bootloader. Then it should allow you to flash the rest of the items without error. Let us know if it works for you.

samwathegreat said:
Try the steps listed in this post:
http://forum.xda-developers.com/showpost.php?p=53228057&postcount=148
Basically, the idea here is to flash gpt (partition) and motoboot ONLY, then reboot back into bootloader. Then it should allow you to flash the rest of the items without error. Let us know if it works for you.
Click to expand...
Click to collapse
I followed the steps but I still get the same error. In CMD window I get:
mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (57163 KB)...
OKAY [ 3.868s]
writing 'system'...
(bootloader) Sparse image is malformatted
FAILED (remote failure)
finished. total time: 6.680s

n0obpr0 said:
I followed the steps but I still get the same error. In CMD window I get:
mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (57163 KB)...
OKAY [ 3.868s]
writing 'system'...
(bootloader) Sparse image is malformatted
FAILED (remote failure)
finished. total time: 6.680s
Click to expand...
Click to collapse
And we have your answer. 57MB is WAY too small for a system partition....it is indeed 'malformatted'/corrupt.
Two possibilities:
1. Either your download of the SBF somehow got corrupted. If so, re-download the entire SBF, and do the steps in the post I linked.
2. You are trying to flash the system.img from the OTA for some reason?? The images contained in the official OTA don't contain the entire system - just an incremental update to the existing system. If this is the case, ditch that idea, and download the official SBF from here:
http://sbf.droid-developers.org/phone.php?device=0

samwathegreat said:
And we have your answer. 57MB is WAY too small for a system partition....it is indeed 'malformatted'/corrupt.
Two possibilities:
1. Either your download of the SBF somehow got corrupted. If so, re-download the entire SBF, and do the steps in the post I linked.
2. You are trying to flash the system.img from the OTA for some reason?? The images contained in the official OTA don't contain the entire system - just an incremental update to the existing system. If this is the case, ditch that idea, and download the official SBF from here:
http://sbf.droid-developers.org/phone.php?device=0
Click to expand...
Click to collapse
That's what I thought. I actually downloaded the SBF from the link you provided. When I open the zip file, system.img is 873,450,540. I'm gonna download it from my laptop.
Edit: Thank you!!! I downloaded the file in my laptop and extracted the file and I had the right size this time. I flashed it and it worked =) Thank you everybody! Y'all made my day =)

n0obpr0 said:
That's what I thought. I actually downloaded the SBF from the link you provided. When I open the zip file, system.img is 873,450,540. I'm gonna download it from my laptop.
Edit: Thank you!!! I downloaded the file in my laptop and extracted the file and I had the right size this time. I flashed it and it worked =) Thank you everybody! Y'all made my day =)
Click to expand...
Click to collapse
That's what were here for to help others xD
Sent from my XT1053 using XDA Free mobile app

Root titan_retuaws (xt1064) from Android 5.0.2

Hi Folks,
Model number: Moto G (2nd Generation)
System Version: 22.46.12.titan_retuaws.retuaws.en.US retus
Build number: LXB22.99-24.12
Android version: 5.0.2
I've spent a couple hours so far trying to root this thing. Lots of guides that claim that they cover this device either don't really (the xt1064 isn't actually listed once you get into the guts of the how-to), or they just don't work.
The bootloader is unlocked, but I haven't found a working recovery. They're all too big, apparently. I've tried these, for instance:
openrecovery-twrp-2.8.5.0-titan.img
TWRP2.7.1.1-titan-motog-2014.img
twrp-2.8.3.0-titan.img
twrp-2.8.6.0-titan.img
twrp-2.8.4.0-titan.img
This is what happens:
Code:
[email protected] ~/Downloads $ sudo fastboot flash recovery twrp-2.8.3.0-titan.img
target reported max download size of 536870912 bytes
sending 'recovery' (9674 KB)...
FAILED (data transfer failure (Value too large for defined data type))
finished. total time: 0.011s
Does anybody know of an actual working recovery for this thing?
Also, is there a special SuperSU, once I get it rooted?
Thanks,
Jamie

Actually, many of them work very well with the XT1064. Make sure everything (adb, fastboot, the TWRP image) are in the same directory on your computer. I've literally flashed my XT1064 dozens of times using the directions posted all over XDA.
You should be able to open up a cmd prompt in the directory with your files and type, fastboot flash recovery twrp.img, then fastboot reboot.
BTW, I believe TWRP is up to 2.8.7 now.

I'm on linux (Mint), and adb/fastboot are installed via package management, and they're on my path. I don't remember having to install a second set of tools and put the image in the same directory as the tools before (when flashing other devices). My output from above shows that the img file is found (it's just too big). Since I can't test it now (machine's at home), what's the rationale for having to put the image in the same directory as the fastboot executable?
FWIW, as of this writing, the downloads page only shows up to twrp-2.8.6.0-titan.img.

Jamie Jackson said:
I'm on linux (Mint), and adb/fastboot are installed via package management, and they're on my path. I don't remember having to install a second set of tools and put the image in the same directory as the tools before (when flashing other devices). My output from above shows that the img file is found (it's just too big). Since I can't test it now (machine's at home), what's the rationale for having to put the image in the same directory as the fastboot executable?
FWIW, as of this writing, the downloads page only shows up to twrp-2.8.6.0-titan.img.
Click to expand...
Click to collapse
https://twrp.me/
Hmmm, I see a newer version but I doubt that's your problem.
Sent from my SM-T530NU using Tapatalk

Try philiz recovery it will solve ur pblm i already tried it in 2 moto g phones

vaisakmct said:
Try philiz recovery it will solve ur pblm i already tried it in 2 moto g phones
Click to expand...
Click to collapse
Is this the one you're talking about, and have you rooted a titan, specifically?

Tel864 said:
https://twrp.me/
Hmmm, I see a newer version but I doubt that's your problem.
Sent from my SM-T530NU using Tapatalk
Click to expand...
Click to collapse
That's just the home page. When you drill into the titan download page, the versions aren't as new as the home page would suggest.

Jamie Jackson said:
Is this the one you're talking about, and have you rooted a titan, specifically?
Click to expand...
Click to collapse
sure many titan phones

How to restore to stock ROM 5.0.2 GB?

I have a locked bootloader, and want to restore my phone to stock ROM so I can download OTA updates. I have downloaded the restore to 5.0.2 windows tool, but I need the correct firmware for my phone. Where can I download from. Could you provide a download link? My system version is 22.41.24.thea_retgb.retgball.en.GB retgb
Build number is LXB22.99-24. My phone is XT1072 I am running android 5.0.2
Many thanks.

This will work fine unless you want 5.0.2
Just a note, DO NOT USE that bat script from the general forum, is not complete, everything you need is in my sign, script and mfastboot

Thanks for the links. Where can I find the script and mfastboot?

orbitingful said:
Thanks for the links. Where can I find the script and mfastboot?
Click to expand...
Click to collapse
Look at my sign.

Found it. Is your BAT file compatible with my XT1072 GB phone, because it says RETLA? Also, do I just place the contents of the ROM zip in the same folder as your script?
Thanks.

orbitingful said:
Found it. Is your BAT file compatible with my XT1072 GB phone, because it says RETLA? Also, do I just place the contents of the ROM zip in the same folder as your script?
Thanks.
Click to expand...
Click to collapse
Those bats are made for XT1072, so yes, they should work on any moto g gen2 i think.
I don't know where you read retLA, i have linked you the latest builds of 5.0.2 retGB and 6.0 retGB
Follow this simple step-by-step guide
1- Check if you have MotoDeviceManager installed for the usb drivers
2- Download this XT1072_THEA_RETGB_6.0_MPB24.65-34_cid7_subsidy-DEFAULT_CFC.xml.zip (GDrive mirror from Hemphiz) or from Filefactory
3- Download this https://mega.nz/#!flMFxT7a!uKLcNK_Ge6CsVxjSFDU06YRO3GMZFj39Zl-vVNbEVzo
4- Download the script for MM https://mega.nz/#!Od1i0I4a!3Oz4Wp4iYf_w5C0NLK438h-Ea1mXvUkHTDFzl7ie7cc
5- Extract the content of the rom zip in a folder (ex c:\rom)
6- Extract the content of Fastboot&mastbootV2.zip in the same folder of the rom files
7- Move the bat script in the same folder as step 5-6
8- Now you should have 22 files and 0 folders in c:\rom
9- reboot to bootloader and connect the phone
10- Doubleclick the bat script and wait for the phone to flash, it will self-reboot once done
First boot on 6.0 can take 20/25 minutes, so unless it's bootlooping don't panic and wait.
I know you asked for 5.0.2 but 6.0 is not bad, if you want 5.0.2 at step 2 dl this zip and on step 4 use XT1072 *.bat Flash Script for LP(5.0.2)

Hello, can you help me?
I did everything in the order to downgrade to 5.0.2, but the script tells me following:
Code:
C:\rom>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (261758 KB)...
OKAY [ 8.254s]
writing 'system'...
[B](bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)[/B]
finished. total time: 8.633s
My phone is atm on 6.0 24.41.34.thea_retde

dasgnu said:
Hello, can you help me?
I did everything in the order to downgrade to 5.0.2, but the script tells me following:
Code:
C:\rom>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (261758 KB)...
OKAY [ 8.254s]
writing 'system'...
[B](bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)[/B]
finished. total time: 8.633s
My phone is atm on 6.0 24.41.34.thea_retde
Click to expand...
Click to collapse
Assuming you have the same model as the OP (XT1072 )
You used the retDE fw ? I'm not aware of any troubles downgrading this phone from MM to LL
XT1072_THEA_RETDE_5.0.2_LXB22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
XT1072_THEA_RETDE_6.0_MPB24.65-34_cid7_subsidy-DEFAULT_CFC.xml.zip

dr.nic said:
Those bats are made for XT1072, so yes, they should work on any moto g gen2 i think.
I don't know where you read retLA, i have linked you the latest builds of 5.0.2 retGB and 6.0 retGB
Follow this simple step-by-step guide
1- Check if you have MotoDeviceManager installed for the usb drivers
2- Download this XT1072_THEA_RETGB_6.0_MPB24.65-34_cid7_subsidy-DEFAULT_CFC.xml.zip (GDrive mirror from Hemphiz) or from Filefactory
3- Download this https://mega.nz/#!flMFxT7a!uKLcNK_Ge6CsVxjSFDU06YRO3GMZFj39Zl-vVNbEVzo
4- Download the script for MM https://mega.nz/#!Od1i0I4a!3Oz4Wp4iYf_w5C0NLK438h-Ea1mXvUkHTDFzl7ie7cc
5- Extract the content of the rom zip in a folder (ex c:\rom)
6- Extract the content of Fastboot&mastbootV2.zip in the same folder of the rom files
7- Move the bat script in the same folder as step 5-6
8- Now you should have 22 files and 0 folders in c:\rom
9- reboot to bootloader and connect the phone
10- Doubleclick the bat script and wait for the phone to flash, it will self-reboot once done
First boot on 6.0 can take 20/25 minutes, so unless it's bootlooping don't panic and wait.
I know you asked for 5.0.2 but 6.0 is not bad, if you want 5.0.2 at step 2 dl this zip and on step 4 use XT1072 *.bat Flash Script for LP(5.0.2)
Click to expand...
Click to collapse
Thanks for your step by step guide. I wanted to know your opinion on the success of a dirty flash. This would involve editing the script so that:
"mfastboot erase userdata"
and "mfastboot flash recovery recovery.img"
are removed.

how to get NVME file (bootloader code) unofficially

If uou dont know what you are doing,dont ask me
i will try to explain as far as i can.but dont ask stupid questions
-------------- Responsibility for your bricks I do not take over. Everyone does at their own peril and risk .--------------
Click to expand...
Click to collapse
Download this
1) Install the driver for the phone (download);
2) Install a special driver, find it in the Unlock_BootLoader \ Driver for Winwos \ DriverSetup.exe folder;
3) It is necessary to unwind the phone, remove the cover;
4) Open application and press start
5) Test point and connect the phone
6) it will start flashing then stop the proces in betwin the flash
7) wait for 30 sec your device will be in temporary unlocked bootloader mode
8) then flash TWRP (link ) by this command
Code:
fastboot flash recovery_ramdisk XXXXX.img
fastboot flash erecovery_ramdisk xxxxx.img
9) Done. Now you have TWRP_Mod installed in the Recovery section.
10) Then within twrp open adb connect phone to pc
11)type
Code:
adb shell
rm data -r
12)restart device
13) then type
Code:
adb pull /dev/block/sdd4
14) alternatively you can take nvme backup from twrp if u can extract that
you have the NVME file
Reference of nvme

Code: JH3KZQA0XD7G2KOZ
File from unlocked by the code phone is attached
Now somebody should look through binary code I guess trying to find the code or something pattern

S0bes said:
Code: JH3KZQA0XD7G2KOZ
File from unlocked by the code phone is attached
Now somebody should look through binary code I guess trying to find the code or something pattern
Click to expand...
Click to collapse
Remove the attachment. Dont nake it public. Its harmful
Check the refence try if that work

rajit said:
Remove the attachment. Dont nake it public. Its harmful
Is this twrp backup? Or u pulled via adb?
Click to expand...
Click to collapse
It's not mine and have been already published on 4pda for someone to find the spot in img file
I don't know how it had been pulled. I guess the person bought the code, unlocked the phone and made twrp backup

S0bes said:
Code: JH3KZQA0XD7G2KOZ
File from unlocked by the code phone is attached
Now somebody should look through binary code I guess trying to find the code or something pattern
Click to expand...
Click to collapse
An idea: How about backing up your nvme, then flashing this nvme and unlock the bootloader using this code, then restoring your backup

mehdi554 said:
An idea: How about backing up your nvme, then flashing this nvme and unlock the bootloader using this code, then restoring your backup
Click to expand...
Click to collapse
The img has been taken from another huawei device. not honor play

@rajit have you tried to force unlock boot? Without code just editing nvme file?
https://forum.xda-developers.com/9-lite/how-to/unlock-bootloader-code-t3859685 - step 5

please help me !
please help me !
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk TWRP_Mod.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.700s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.712s

Where is the test point?
And can i flash magisk file after unlocked bootloader temporar?

mohad2399 said:
please help me !
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk TWRP_Mod.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.700s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.712s
Click to expand...
Click to collapse
Do you connect the test point??

What's the point of unlocking bootloader if there aren't custom rom for this device yet

devilyuri said:
What's the point of unlocking bootloader if there aren't custom rom for this device yet
Click to expand...
Click to collapse
Custom rom isnt issue if you know how to what! Besides who asked you to take some interest here??
You can ignore! :fingers-crossed:

then how did this end? anyone managed to root using nvme honor play COR-L29 EMUI 9.1 ????

rajit said:
If uou dont know what you are doing,dont ask me
i will try to explain as far as i can.but dont ask stupid questions
Download this
1) Install the driver for the phone (download);
2) Install a special driver, find it in the Unlock_BootLoader \ Driver for Winwos \ DriverSetup.exe folder;
3) It is necessary to unwind the phone, remove the cover;
4) Open application and press start
5) Test point and connect the phone
6) it will start flashing then stop the proces in betwin the flash
7) wait for 30 sec your device will be in temporary unlocked bootloader mode
8) then flash TWRP (link ) by this command
9) Done. Now you have TWRP_Mod installed in the Recovery section.
10) Then within twrp open adb connect phone to pc
11)type
12)restart device
13) then type
14) alternatively you can take nvme backup from twrp if u can extract that
you have the NVME file
Reference of nvme
Click to expand...
Click to collapse
This is really work ?

[/COLOR]
Neverhopless said:
This is really work ?
Click to expand...
Click to collapse
It works but there's no code inside nvme

This method works on Emui 9 ?

What do you mean by "Unwind the phone"?

I have made a simple windows program to help parse a file to possibly find an unlock code.
You simply put exe with the file in the same dirrectory and run.
The program will ask for the file name to parse and then will show any character sequences that follow the pattern rules:
*Length >=16
* A-Z, a-z, 0-9 symbols
See pic example
In case of missing MSVCR120.dll error install https://www.microsoft.com/en-US/download/details.aspx?id=40784
.cpp file is just a source code

Can you fix the tools ?. Google Drive is not available

Link not working