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
Related
Note: This is an inherently dangerous tool. I have made every effort to make it as safe as possible. But there is always a risk of bricking your device. You assume all responsibility for the consequences. Proceed with caution.
Warning: To avoid bricking your device, NEVER write both boot and recovery in one session. ALWAYS write one partition, test, then write the other. This is why the tool will only write one partition at a time.
Warning: There are versions of TWRP for the Axon 7 that are known to erase your IMEI when doing a restore. Do NOT do a TWRP restore unless your are SURE that you have a good version of TWRP!
This tool will allow you to:
Backup your boot and recovery partitions.
Flash a boot or recovery image (including the signed TWRP image).
See following posts for operating system specific setup instructions.
Once your setup is complete, enter EDL mode:
1. Power off phone.
2. Hold both volume buttons.
3. Plug phone into computer.
4. For G models, you must "adb reboot edl" (see other threads).
Usage:
axon7tool <mode> <partition(s)>
Note: The tool name will vary depending on your operating system.
<mode> is -r for read, -w for write.
For read mode, <partition> is one or more of gpt, boot, recovery. Files will be created as <partition>-backup.bin
For write mode, <partition> is boot or recovery. File will be read from <partition>.bin
Examples:
To backup everything on Linux:
./axon7tool-1.5-linux -r gpt boot recovery
To write recovery on Win64:
Place file as recovery.bin
axon7tool-1.5-win64 -w recovery
Links to axon7tool:
axon7tool-1.5-linux (main)
axon7tool-1.5-linux (alternate)
axon7tool-1.5-win64.exe (main)
axon7tool-1.5-win64.exe (alternate)
Link to signed TWRP removed.
FAQ:
Q: Can you provide a signed boot image with root?
A: No. I do not have the ZTE signing key, and tenfar's images are not current.
Q: Can I have the source code for the tool?
A: No.
Q: Can you provide the programmer?
A: No.
Q: Do you accept donations?
A: No, all work is provided freely for community use.
Setup instructions for Linux:
1. Ensure your login user is in the "plugdev" group.
$ id
You should see plugdev in the list. If not, add yourself to the group and logout/login to take effect.
2. Ensure your udev rules are setup.
Create a file eg. /etc/udev/rules.d/qcom.rules that contains:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", GROUP="plugdev"
3. All done!
Setup instructions for Win64:
1. Download zadig from http://zadig.akeo.ie/
2. Put device in EDL mode.
3. Run zadig. Select the WinUSB driver. If you have installed the Qualcomm EDL driver, you may need to tick "Edit" and find the device in the list.
4. All done!
Reserved for Mac instructions.
Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?
kgptzac said:
Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?
Click to expand...
Click to collapse
1- No this doesn't work like backing up with TWRP, This tool is more powerful than Custom Recovery (TWRP), and you should be very careful on how to use it.
Like @tennear mention about try first by using -r (read) then just flash the sign TWRP.
I personally recommend just flash TWRP and DON'T mess with Boot image.
2- the Sign TWRP is not provided by ZTE, ZTE will NEVER release a Custom Recovery for us users.
kgptzac said:
Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?
Click to expand...
Click to collapse
1. The tool writes the raw partitions to your PC. Whatever you have in the partition is written out, whether it is stock recovery or TWRP or whatever.
2. The signed TWRP image is copied from the zip that tenfar provided in his post. I did not create it, and I cannot create signed images.
Forgive me my noobiness, but here’s a step-by-step-instruction list. Am I thinking right? I want to minimise the risk when I try your tool tomorrow.
Step 1: Enable Developer options in phone by tapping the build number
Step 2: Enable OEM Unlock in phone (is this needed?)
Step 3: Enable debugging (for adb)
Step 4: Connect phone to PC
Step 5: Download Zadig
Step 6: Install Zadig
Step 7: Open command in the folder in which you downloaded adb.exe (and the rest of the files that come with it) (Richt click while holding shift to get the option to open CMD in a folder)
Step 8: Enter the command “Adb Devices” to reassure your device is detected
Step 9: Enter the command “Adb reboot edl” to reboot the phone to EDL mode
Step 10: After phone has rebooted to EDL mode, run Zadig, select WInUSB driver and install it for your device
Step 11: Rename “axon7tool-1.5-win64.exe” to “axon7tool.exe”
Step 12: Download “axon7-2017u-twrp-signed.img” to the folder where axon7tool.exe is located
Step 13: Open command in the folder in which you have downloaded axon7tool-1.5-win64.exe (renamed to axon7tool.exe)
Step 14: Enter command “axon7tool -r gpt”.
Step 15: Enter command “axon7tool -r boot”
Step 16: Enter command “axon7tool -r recovery”
Step 17: Verify if the tool has created “gpt-backup.bin”, “boot-backup.bin”, “recovery-backup.bin”.
Step 18 (unsure): rename “axon7-2017u-twrp-signed.img” to “recovery.bin” ?
Step 19: enter “axon7tool -w recovery recovery.bin
Step 20: Wait for the command to finish
Step 21: Place the .zip file for Z.A.D. Mix7 or CM13 on your SD card via your PC or Axon 7. Also download Gapps.zip of your choice and place on SD card.
Step 22: Boot your Axon 7 to TWRP Recovery by holding the power button simultaneously with volume down (or is it volume up?)
Step 23: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 24: Flash the .zip of your custom ROM of choice in TWRP
Step 25: Flash the .zip of your Google Apps of choice in TWRP
Step 26: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 27: Reboot your phone, enjoy the custom ROM of your choice.
Is this the correct procedure?
I’m a bit unsure of step 18. Am I doing it right? Or do you need to unzip that .img somehow to find a recovery.bin file? Or do you need to get that file from somewhere else? Or do you need to rename “axon7-2017u-twrp-signed.zip” to “recovery.img”?
For Z.A.D. MIX7, I suppose you still need to flash a SuperSU version seperately? I heard in CM it's baked-in.
Thanks for the help.
Jan
@Controllerboy close, but not quite. I'll attempt to provide detailed feedback on your step by step list tomorrow. Time for sleep now.
Controllerboy said:
Step 1: Enable Developer options in phone by tapping the build number
Step 2: Enable OEM Unlock in phone (is this needed?)
Step 3: Enable debugging (for adb)
Click to expand...
Click to collapse
None of these steps should be necessary.
Controllerboy said:
Step 4: Connect phone to PC
Step 5: Download Zadig
Step 6: Install Zadig
Click to expand...
Click to collapse
I believe you just run zadig, I don't remember an installer.
Controllerboy said:
Step 7: Open command in the folder in which you downloaded adb.exe (and the rest of the files that come with it) (Richt click while holding shift to get the option to open CMD in a folder)
Step 8: Enter the command “Adb Devices” to reassure your device is detected
Step 9: Enter the command “Adb reboot edl” to reboot the phone to EDL mode
Step 10: After phone has rebooted to EDL mode, run Zadig, select WInUSB driver and install it for your device
Step 11: Rename “axon7tool-1.5-win64.exe” to “axon7tool.exe”
Click to expand...
Click to collapse
Renaming the tool is optional.
Controllerboy said:
Step 12: Download “axon7-2017u-twrp-signed.img” to the folder where axon7tool.exe is located
Step 13: Open command in the folder in which you have downloaded axon7tool-1.5-win64.exe (renamed to axon7tool.exe)
Step 14: Enter command “axon7tool -r gpt”.
Step 15: Enter command “axon7tool -r boot”
Step 16: Enter command “axon7tool -r recovery”
Click to expand...
Click to collapse
The tool is "one shot". You can read any combination of gpt, boot, and recovery in one session, then the tool will restart the phone.
Controllerboy said:
Step 17: Verify if the tool has created “gpt-backup.bin”, “boot-backup.bin”, “recovery-backup.bin”.
Step 18 (unsure): rename “axon7-2017u-twrp-signed.img” to “recovery.bin” ?
Click to expand...
Click to collapse
Yes, this is correct.
Controllerboy said:
Step 19: enter “axon7tool -w recovery recovery.bin
Step 20: Wait for the command to finish
Click to expand...
Click to collapse
Yes, this is correct. Writing boot or recovery takes about 30 seconds. Then the tool will reboot your phone. Be sure to hold the Vol+Up button to reboot into recovery.
Controllerboy said:
Step 21: Place the .zip file for Z.A.D. Mix7 or CM13 on your SD card via your PC or Axon 7. Also download Gapps.zip of your choice and place on SD card.
Step 22: Boot your Axon 7 to TWRP Recovery by holding the power button simultaneously with volume down (or is it volume up?)
Step 23: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 24: Flash the .zip of your custom ROM of choice in TWRP
Step 25: Flash the .zip of your Google Apps of choice in TWRP
Step 26: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 27: Reboot your phone, enjoy the custom ROM of your choice.
Click to expand...
Click to collapse
Everything past step 20 is up to you.
Controllerboy said:
Is this the correct procedure?
I’m a bit unsure of step 18. Am I doing it right? Or do you need to unzip that .img somehow to find a recovery.bin file? Or do you need to get that file from somewhere else? Or do you need to rename “axon7-2017u-twrp-signed.zip” to “recovery.img”?
For Z.A.D. MIX7, I suppose you still need to flash a SuperSU version seperately? I heard in CM it's baked-in.
Thanks for the help.
Jan
Click to expand...
Click to collapse
You cannot unzip an img file.
The TWRP image provided is just as tenfar provided for 2017u users. You only need to rename it to recovery.img for using the tool.
If someone has the 2017g TWRP file, I can upload and link it. The links in the tenfar post have been removed.
Folks who are able to use this new tool/method successfully, please report back with your variant. I can't test this myself, so I'm relying on some verification before I update the newbie guide to point here instead of tenfar's thread (which is outdated and no longer updated as tenfar is now inactive).
tennear said:
<-- SNIP -->
If someone has the 2017g TWRP file, I can upload and link it. The links in the tenfar post have been removed.
Click to expand...
Click to collapse
I found this on the 65th page of Tenfar's thread (http://forum.xda-developers.com/showpost.php?p=69215285&postcount=642)
khaino said:
Step 1: Download the zip file and extract to your local disk. a2017 for Chinese model,and a2017u for US model,a2017g for HK & EU model
a2017u :B20_blunlockedhttp://d-h.st/KaaQ
a2017u B20 http://d-h.st/LqR5 (modified from @rczrider�s backup real stock b20 boot.img)
a2017u B27 http://d-h.st/kRgq
a2017 B06:http://d-h.st/ztXw
a2017 B07:http://d-h.st/VVlf
a2017 B08: http://d-h.st/bT6r
a2017 B09:http://d-h.st/sBjo
a2017 B10:http://d-h.st/cBOE(wifi not working) http://d-h.st/aceq (from official update.zip)
a2017g B02 :http://d-h.st/aPiC
a2017g B03:http://d-h.st/r3Z4
TWRP recovery 3.0.2-2 : http://d-h.st/dgWW
latest tools:http://d-h.st/Ienb with dump function
Click to expand...
Click to collapse
So I just use the file from http://d-h.st/r3Z4 (axon7root-a2017g-b03.zip), unzip and rename the .img file to recovery.img?
The issue here is that the hosting used is so crappy I can't even download the file...
Controllerboy said:
So I just use the file from http://d-h.st/r3Z4 (axon7root-a2017g-b03.zip), unzip and rename the .img file to recovery.img?
The issue here is that the hosting used is so crappy I can't even download the file...
Click to expand...
Click to collapse
That is correct.
d-h.st seems to be down for the past few days. I guess it will come back at some point, and you can download the zip file to extract the recovery image. Or maybe someone else has a copy of it...
@tennear
As far as u know TWRP is the same for every A7, sign or not.
DrakenFX said:
@tennear
As far as u know TWRP is the same for every A7, sign or not.
Click to expand...
Click to collapse
Unpacking the TWRP image for A2017U, it says:
ro.product.model=A2017U
So this recovery seems to be specific to A2017U.
But unpacking the TWRP image for A2017 (China), it says:
ro.product.model=ZTE A2017U
Hmm, different but still A2017U.
I don't have the TWRP image for A2017G (yet), so I can't tell what it says. But given the above, and that the G and U models are almost identical, I am thinking the A2017U image will run on all devices.
tennear said:
Reserved for Mac instructions.
Click to expand...
Click to collapse
So can the Linux tool be used on Mac?
nuserame said:
So can the Linux tool be used on Mac?
Click to expand...
Click to collapse
No. I have not built the tool on Mac yet. I will try to do that soon.
I wouldnt say I was a newbie but how do you get the file to run. Even with Antivrus off, the computer just wont run it.
Thank you for the time and support.
The .exe file isn't meant to be ran on it's own. Double-clicking it won't do a thing. You need to use cmd (command) to execute commands to the file. If you look at my post on the first page of this thread, you'll get an idea of how the process works. But please don't follow my post as of now, since it's not detailed nor 100% correct yet.
It's my intention to try my luck tomorrow and I'll post a detailed and 100% correct step-by-step-process.
Excuse me for my ignorance, but how does this tool differ from tenfars tool? Beside not being able to write two partitions at the same time that is.
TIA,
Cheerz,
/Cacti
First of all, I would like to say thanks to @DrakenFX, @tenfar, @rczrider, and @tennear for their work on the Axon 7.
Code:
/* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or any other mishaps that may occur. YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
*/
This guide is intended to help anyone wishing to return to stock B20 firmware on the A2017U for the purposes of re-locking the bootloader (either for sending a device in for an RMA or whatever you may need). After much trial and error, I have finally come up with a guide and attached all necessary files to do this. I performed the following steps on my Axon 7 2017U on the B29 firmware and successfully downgraded to the B20 firmware with a re-locked bootloader.
Here are the files you will need:
Stock system
Stock boot stack
Stock fastboot
Stock recovery
TWRP
Make sure you have ADB and fastboot set up properly on your computer.
Use the TWRP linked in this post. I know for sure that this version works towards the end of this process when your bootloader is locked again.
After you have the zip files, you will need to move them to your phone to flash in TWRP. Follow these steps:
1. Make a backup of all of your important data. EVERYTHING will be wiped in this process, including internal storage.
2. Power off the phone.
3. Download the the axon7tool executable file from this link: Here Check the post for instructions pertaining to drivers needed.
4. Boot the phone into EDL mode. Do this by holding down the Volume Up and Volume Down keys simultaneously and then plugging the phone in to your computer while keeping these keys pressed. (The phone's screen will be completely black and it will appear like nothing is happening. This is EDL mode.)
5. Open a command prompt in the directory with the axon7tool executable. (Windows: right click while holding shift and select "Open command window here." Linux: Open a terminal and cd into the directory)
6. Dump your gpt with the tool. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -r gpt
Linux: ./axon7tool-1.5-linux -r gpt
7. The axon7tool will automatically reboot you. Reboot to TWRP.
8. Make a backup of your EFS partition by going to "Backup" with only the EFS box checked.
9. Copy the "TWRP" folder from your internal storage to your computer. This folder contains the EFS backup.
10. Go to "Wipe" -> "Advanced" -> "Format Data." Type "yes." WARNING: THIS DELETES ALL DATA. MAKE SURE YOU HAVE A BACKUP.
11. Reboot back into TWRP. Ignore anything TWRP says or asks you to do upon a reboot.
12. Copy the "B20_stock_system," B20_stock_bootstack," and "B20_stock_fastboot" zip files to your internal storage.
13. Flash the stock system zip first, then the boot stack zip, and finally the fastboot zip.
14. At this point you are on the stock B20 system, but with an unlocked bootloader. TWRP will probably be overwritten, so follow these next steps regardless.
15. Reboot the phone and let it get to the set up screen. This step can take a while; my Axon took almost a minute to get off of the ZTE splash screen initially.
16. As soon as you see that the phone boots, power off the phone and reboot to EDL mode.
17. Flash TWRP again with the axon7tool as it has been overwritten at this point and will be necessary soon. Download the linked TWRP recovery image and rename the file to "recovery.bin" Place it in the same folder as the axon7tool. Flash the recovery. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -w recovery
Linux: ./axon7tool-1.5-linux -w recovery
18. Reboot the phone into the bootloader. You can do this by going to TWRP and by choosing reboot to bootloader or by manually doing so.
19. Type "fastboot oem lock" into a command prompt. This will lock your bootloader.
20. After I did this, I thought I was done. However, when I rebooted my phone, I saw that /data required a password to be decrypted upon a reboot. This is why we flashed TWRP. Go into TWRP and format data again.
21. Copy the "TWRP" phone from earlier back onto your internal storage. Restore your EFS in case anything has happened to your IMEI in this process.
22. At this point your phone is completely locked but with a custom recovery. To restore the stock recovery, reboot into EDL mode and replace the TWRP recovery.bin file from a few steps ago with the B20_stock_recovery.bin file you downloaded. Rename the B20_stock_recovery.bin file to recovery.bin and make sure it's in the same folder as the axon7tool.
23. Flash the stock recovery with the same commands for the axon7tool as listed earlier for TWRP.
24. Profit
As tennear has noted, do NOT backup or restore the EFS partition.
Never restore EFS using TWRP. You will lose its contents and probably your IMEI.
@tennear Thanks for the heads up. I'll remove that part from my guide.
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
mortkarg5 said:
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
Click to expand...
Click to collapse
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Yoshi_Guy said:
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Click to expand...
Click to collapse
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
mortkarg5 said:
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
Click to expand...
Click to collapse
You can try, but I'm not sure if it would work. The recovery is for stock b20 so try it at your own discretion.
Every time I try to do the fastboot oem lock it fails, I have the twrp you mentioned in the post and followed the steps as listed. Did you run into this issue?
Sent from my ZTE A2017U using Tapatalk
i can't found same file u can upload again?
Yeah.... most links are dead. Does anyone else have them?
Flapjack said:
Yeah.... most links are dead. Does anyone else have them?
Click to expand...
Click to collapse
I'll fix them.
Yoshi_Guy said:
I'll fix them.
Click to expand...
Click to collapse
Thanks, brotha.
Flapjack said:
Thanks, brotha.
Click to expand...
Click to collapse
Try again, they should be working now.
Yoshi_Guy said:
Try again, they should be working now.
Click to expand...
Click to collapse
Thanks... but holy f*ck... this MEGA bs. What a piece of garbage. Why do I need to create an account?
I'm getting the following error (Win 10). Others have gotten the same error in various versions of linux, as well. The only one who resolved the error had forgot to elevate his terminal (which I've done):
Code:
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
@Yoshi_Guy
In step 22) where stock recovery has to be restored, instead of reusing axon7tool in EDL mode, maybe it would be easier to flash stock recovery by the signed tenfar TWRP itself (by using TWRP Install/flash image option, boot partition). This is a kind of "hara-kiri" (current TWRP destroys itself) but it should work.
Flapjack said:
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
Click to expand...
Click to collapse
That's quite odd, what version of Linux are you using? Also, are you able to try the Windows version of the tool? I've used the tool on Arch Linux and had no problems. Also, the program does need to be run as root, as you mentioned. The signature verification probably failed because you are trying to downgrade your version, I wouldn't recommend using the official ZTE zips entirely. I would take what you need and flash just that, downgrading is rather complex.
Thanks for the guide, but wish you would've used androidfilehost. I hit MEGA quota at 80%, so I'll have to wait til late tonight to give this a shot.
nvm: using megadownloader now
I must note: I use linux. I only used Windows because SPFT Linux version gave me a chip mismatch error I couldn't fix easily.
1: Please read. It explains what problems might arise. Especially post #6 and #13.
2: There are 2 versions of the scatter file. The MT6735 version is what I used successfully. The MT6737Tmod version is what comes from post #6 & #13.
3: Please use each scatter file to Readback your boot and recovery partitions first, renaming as fit, so you can have a backup BEFORE ANYTHING. Then test unpacking them to see if everything went correctly. Then readback every partition in the scatter file so you don't have to depend on the stock ROM for a backup. I didn't and it led me to take this route.
3: Seem to be a difference in the naming of the scatter file and sizes of system, cache, and userdata inside from the stock ROM and what works..
4: DO NOT choose Format+Download until you know which scatter file works, unless you want to chance a Hard Brick.
5: Wiping the dalvik and cache in stock recovery before flashing TWRP seems to be the best thing to do to avoid boot loops or a hung boot.
THIS ROOT PROCESS WAS DONE OVER THREE DAYS OF CAR WORK, DRIVING, FAMILY, AND COMPUTER WORK. MOST OF THE TIME SPENT WAS THIS MORNING TRYING TO GO TO SLEEP. DIDN'T HAVE TIME TO DOCUMENT AND TAKE PICTURES. THIS WRITE-UP IS FROM WHAT I REMEMBER DURING THIS PROCESS. IF I CAN REMEMBER SOME VAGUE DETAIL THAT YOU NEED, GOOD. IF NOT, DON'T STRESS ME. THE HARD PART IS DONE. A GOOGLE SEARCH OF SOME OF THESE PROGRAMS WILL GET QUICKER RESULTS IF YOU DON'T HAVE THEM. THE MAIN THING NEEDED FROM MY RESEARCH WAS THE SCATTER FILE. LINKS FOR SCATTER FILE AND RECOVERY IMAGE ARE BELOW.
Looking for a way to root first day getting this phone in February. Read this post last Tuesday about MT67xx rooting, thanks lsemprini. Spent two days finding which versions of the programs work with this phone, already had the ROMs, drivers, and tools. Dove right in.
I downloaded the ROM from needrom. Scatter file was unusable. Wrong chip error. Phone reads MT6735 scatter file read MT6737. Did a manual diff. Used SP Flash Tool v5.1524 to flash, formatted instead of downloading by mistake, cord got pulled, Hard brick. Fought with Windows7 to get drivers to recognize a hard brick. Still don't know how I did it but it read then flashed. Looked like another hard brick but SPFT would recognize it for the Memory Test. I just held power+vol_down with just charging block power to get it to come on. Sometimes just one of the buttons was enough to get it to power on and start a bootloop. Took two minutes sometimes. Flashing the wrong recovery led to bootloops. Starting SP Flash Tool and plugging in the USB to the phone as soon as it powers off during a loop will let the preloader "register" and the images to be flashed. Flashing from a stock ROM will lead to IMEI being erased. Used SN Write Tool v1.1716 to write the IMEI numbers. Got them from the side of the box. The MD1_DB and AP_DB files needed are in the stock rom.
Ported TWRP, credit to jemmini for the post https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601. Used that recovery as a base. Ported according to the myriad of guides that I have been reading over the past few days. None of them worked as instructed, had to modify trial and error style. Finally got TWRP to read the internal partitions AND remain after a reboot. A lot was going on when I did this. Not sure if I formatted before, I remember flashing a lot of because of something. I mounted the system just in case & flashed SuperSu from chainfire's website, no formatting afterwards. Rebooted and installed SuperUser and BusyBox. I tried adb and fastboot. They work but not for everything. Hooked phone up to computer with debugging enabled.
Code:
adb root
gives a shell, no errors unlike before. Edit: ADB won't let me start as root anymore.
Needed files
Blu Vivo XL2 TWRP 3 Recovery
MT6735 Scatter File
MT6737T Scatter File
BLU Vivo XL2 V0070UU Stock ROM if you don't have a backup of your partition images.
Step 1
Install Minimal ADB and Fastboot and USB VCOM drivers.
Download SP Flash Tool, SN Write Tool, scatter file, and twrp3.0 to a working folder.
Download SuperSu zip & SuperUser apk then put them on your SD Card.
Install SD card into phone.
Step 1.A For Full ROM Flash and IMEI Write
Download Stock ROM and extract to working folder.
Move twrp3.0 to ROM folder.
Step 2
Install SP Flash Tool and SN Write Tool and run.
Step 3 To flash TWRP only
Reboot phone to recovery then wipe cache and dalvik. Can't remember if it is a dalvik option in the stock recovery now.
Power off phone. Make sure it is not plugged up to the computer.
IN SP Flash Tool:
Load scatter file that works from working folder.
Make sure download only is selected in drop down menu.
Check only the recovery partition box and click the name of the recovery file on the same line.
Browse to TWRP recovery image and select.
Click the Download button with the green arrow.
Plug phone into computer and wait until window with OK pops up. Success.
Step 3.B OPTIONAL
Select format and flash all using stock ROM or images backed up from your phone.
Stock ROM must be extracted and custom recover put into same folder and renamed to "recovery.img" to make
everything automatically load.
Click the Download button with the green arrow.
Plug phone into computer and wait until window with OK pops up. Success
Step 4 Only needed when formating+downloading ROM
With phone still powered off and unplugged, write IMEI numbers using SN Write Tool.
Step 4.A
Click System Config.
Select IMEI in Write Option Area.
Make sure IMEI Checksum and Dual IMEI are checked.
Load MD1_DB and AP_DB files from ROM folder.
Click Load Modem DB from DUT box.
Click Save.
Step 4.B
Click Start.
Input your IMEI numbers from box.
Click OK. Success
Step 5
Boot to recovery.
Swipe to make permanent.
Wipe dalvik and cache.
Flash SuperSu..
Reboot.
Install SuperUser apk and BusyBox of your choice.
Step 5.A
If SuperUser apk or any app that ask for root permission cannot get it, reboot to recovery.
Mount system partition: Shouldn't matter but it worked for me.
Flash SuperSu zip again.
Reboot.
Install SuperUser apk and BusyBox of your choice.
ENJOY
When i connect the device after clicking download, it says "CHIP TYPE NOT match!"
mind you the device is off, i tried to troubleshoot but still getting the same error.
any help would be appreciated
UPDATE: Im thinking it has to be the scatter file, but im not sure.
UPDATE: I got it to work, after flashing superSU, my phone wont boot past the initial white Blu start screen.
[QUOTEUPDATE: I got it to work, after flashing superSU, my phone wont boot past the initial white Blu start screen.[/QUOTE]
Try powering it off, booting to recovery and then wiping dalvik and cache.
The longest it took to get past that logo was 15 minutes. It is either encrypting or decrypting. Didn't get any type of messages until after root, and those were optimizing messages. Only one came through before rooting when I interrupted the boot process and that was about encrypting the phone. Phone was encrypted before root, now it is decrypted. Could have something to do with that. Try wiping the cache and dalvik after flashing. I actually flashed it three times in a row. The third was after mounting storage then flashing the SuperSu zip. Once you see the next logo with the colorful circles and hear the sound it might be another wait. That is where it let me know it was optimizing.
I must note: Please use scatter file to Readback your partitions so you can have a backup BEFORE ANYTHING. I didn't and it led me to take this route.
=smith901;72841007][QUOTEUPDATE: I got it to work, after flashing superSU, my phone wont boot past the initial white Blu start screen.
Click to expand...
Click to collapse
Try powering it off, booting to recovery and then wiping dalvik and cache.
The longest it took to get past that logo was 15 minutes. It is either encrypting or decrypting. Didn't get any type of messages until after root, and those were optimizing messages. Only one came through before rooting when I interrupted the boot process and that was about encrypting the phone. Phone was encrypted before root, now it is decrypted. Could have something to do with that. Try wiping the cache and dalvik after flashing. I actually flashed it three times in a row. The third was after mounting storage then flashing the SuperSu zip. Once you see the next logo with the colorful circles and hear the sound it might be another wait. That is where it let me know it was optimizing.
I must note: Please use scatter file to Readback your partitions so you can have a backup BEFORE ANYTHING. I didn't and it led me to take this route.[/QUOTE]
chip type not match. pls help
---------- Post added at 10:46 AM ---------- Previous post was at 10:41 AM ----------
ANJIII said:
chip type not match. pls help
Click to expand...
Click to collapse
what version of stock rom did you use? there are 3 versions in needrom; v7, v11, and v12. i use v11 cause of automatic update
ANJIII said:
chip type not match. pls help
---------- Post added at 10:46 AM ---------- Previous post was at 10:41 AM ----------
what version of stock rom did you use? there are 3 versions in needrom; v7, v11, and v12. i use v11 cause of automatic update
Click to expand...
Click to collapse
i solved my own problem hahaha. just rename the file to mt6737t instead of mt6735. also edit the platform in scatter file. change it to mt6737t too then install your supersu with the use of twrp then wipe dalvic then its done
ANJIII said:
i solved my own problem hahaha. just rename the file to mt6737t instead of mt6735. also edit the platform in scatter file. change it to mt6737t too then install your supersu with the use of twrp then wipe dalvic then its done
Click to expand...
Click to collapse
Good. I had to name it that because of the chip mismatch error. It was from the V7 ROM. The other two are updates. I also messed up big time along the way. My phone always read MT6735 but it does have MT6737T in different files. I always wondered about that. I got it to work without buying another phone.
It seem that the phone boot logo never goes away. What should I do now?
Alexis96312 said:
It seem that the phone boot logo never goes away. What should I do now?
Click to expand...
Click to collapse
Hope you Readback your original recovery and other partitions. I didn't and worked hard to get it back. When I just flashed the recovery and something went wrong, it reverted back to the stock recovery.
Try doing this:
1. Start SPFT with the reçovery you want to flash.
2. Hold down the power button. AS SOON AS IT VIBRATES, PLUG THE USB CORD IN.
3. Hopefully you timed it right and it will flash and boot.
Sometimes it took 15 minutes to get past the boot logo.
Here what I did so far
1. Format using SP Flash Tool
2. Download /// By Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) Which it check all the boxes AUTO ///// It works but I didn't change the recovery.img like TWRP.img
Download it
It works normal.
___________________________________
But I want TRWP.img to be my recovery for root (SuperSU)
I try SP Flash Tool to change the recovery img to TRWP.img /// Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) I UNCHECK ALL BUT RECOVERY.IMG
Before this happen I didn't factory reset or Format anything yet.
It work to Recovery.img but THE BLU LOGO IS STILL LONG
I feel like it not working
Help Help Help ME
Please
Alexis96312 said:
Here what I did so far
1. Format using SP Flash Tool
2. Download /// By Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) Which it check all the boxes AUTO ///// It works but I didn't change the recovery.img like TWRP.img
Download it
It works normal.
___________________________________
But I want TRWP.img to be my recovery for root (SuperSU)
I try SP Flash Tool to change the recovery img to TRWP.img /// Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) I UNCHECK ALL BUT RECOVERY.IMG
Before this happen I didn't factory reset or Format anything yet.
It work to Recovery.img but THE BLU LOGO IS STILL LONG
I feel like it not working
Help Help Help ME
Please
Click to expand...
Click to collapse
Try flashing stock ROM, wipe data in stock recovery, then flashing TWRP, wipe dalvik.
If that don't work, wipe data then flash stock ROM with TWRP recovery, wipe dalvik.
The scatter file from the stock ROM gave me problems. Had to modify mine.
Don't forget to restore your IMEI afterwards since you formatted+flashed.
I will try
---------- Post added at 08:33 PM ---------- Previous post was at 08:23 PM ----------
I did try it but it seem not to do anything
Can you be so kind to upload the mod Scatter File Please
Alexis96312 said:
I will try
---------- Post added at 08:33 PM ---------- Previous post was at 08:23 PM ----------
I did try it but it seem not to do anything
Can you be so kind to upload the mod Scatter File Please
Click to expand...
Click to collapse
The one I attatched on the first post #1 is my modified scatter file. The mods included changing the size to the system, cache, and userdata. Just compared all three. The stock MT6737T scatter file and the V12 ota scatter are the same. The one I changed, MT6735, have the file name, platform name, and partition changes. I don't know why I had to modify it., especially the size parts. It all worked when I did that. I basically gave up on it because of a hard brick. Then I remembered reading MT6735 in some file a few months back while roaming the file system. Made the changes and was back in business. Maybe you need the stock scatter file, here it is.
It's what the end result of this post @ANJIII did minus the size changes..
He just did the name changes and it worked for him. Ya'll seem 180° from where I was.
The second one is from the V12 OTA update. It is very minimal, must be all that is needed for a scatter file. Not really sure tho. Hope it is just scatter file issues.
As long as SPFT is reading your phone, it's still a chance on it all working out. That is how I viewed it.
@andromedaXVIII Don't know if you got it working. This might be a potential solution.
Unable to find partition for path '/sdcard'
Unable to find partition for path '/sdcard'
Unable to find partition for path '/sdcard'
Updating partition details...
Failed to mount '/protect_f'(Invalid argument)
Failed to mount '/protect_s'(Invalid argument)
Failed to mount '/nvdata' (Invalid argument)
...done
Full SELinux support is persent,
MTP Enable
Wiping Dalvik Cache Directories...
--Dalvik Cache Directories Wipe Complete!
Formatting Cache using make_ext4fs..
Updating partition details...
Failed to mount '/protect_f'(Invalid argument)
Failed to mount '/protect_s'(Invalid argument)
Failed to mount '/nvdata' (Invalid argument)
..done
Is this good or bad? This is in Twrp recovery
Alexis96312 said:
Unable to find partition for path '/sdcard'
Is this good or bad? This is in Twrp recovery
Click to expand...
Click to collapse
I take it TWRP flashed successfully, it is having a problem reading those four partitons. Possibly encryption is stopping you. Try flashing this in TWRP before anything else to remove the encryption.
I didn't get any errors. I know the userdata partition was different in the scatter files. That could be the reason for /sdcard not being recognized. Must be a difference in the layout of phones, not really sure. My protect_s, protect_f, and nvdata partitions and /sdcard all mount fine, pictures attached. I am able to do a backup in TWRP. I have been playing around with porting different ROMs and came across an issue similar to this. Had to change some lines in updater-script.
I checked fstab.mt6735 file in the stock recovery, the modded twrp3 recovery, and stock boot recovery to make sure I didn't make any typos or leave anything out. They all have the same lines. Had to do this:
Code:
("ext4", "EMMC", "/dev/block/mmcblk0p5", "/system")
in the updater-script I was working on. I got ahead of myself flashing a ROM and was stuck on the 1st logo screen. Held power+vol_down to get it unstuck. Yes I was all calling myself kind of names like I'm sure some people have done following this guide.
Which scatter file you used? Did you do a readback in SPFT with the WORKING scatter file and mount one of those images to check if you can read and write the files. I mounted system.img from the stock ROM to make sure I could read and write the files before I started with flashing. I'm thinking there is are internal differences in the XL2s. You might have to reflash using the stock ROM with TWRP as the recovery with the Format+Download option since you got TWRP installed.
Once I get through playing around with trying to flash this ROM, I will restore and try to find all the partition mappings and update TWRP to work with the format from the updater-script and see if that work. Will let you know what happened.
Alexis96312 said:
Unable to find partition for path '/sdcard'
Unable to find partition for path '/sdcard'
Unable to find partition for path '/sdcard'
Updating partition details...
Failed to mount '/protect_f'(Invalid argument)
Failed to mount '/protect_s'(Invalid argument)
Failed to mount '/nvdata' (Invalid argument)
...done
Full SELinux support is persent,
MTP Enable
Wiping Dalvik Cache Directories...
--Dalvik Cache Directories Wipe Complete!
Formatting Cache using make_ext4fs..
Updating partition details...
Failed to mount '/protect_f'(Invalid argument)
Failed to mount '/protect_s'(Invalid argument)
Failed to mount '/nvdata' (Invalid argument)
..done
Is this good or bad? This is in Twrp recovery
Click to expand...
Click to collapse
can you send us your vivo xl2 specs because there are two versions of xl2, V0070UU and V0070EE. Mine is V0070UU. I just did some renaming and editing in the scatter file of MT6735 and it bootloop once after I installed the twrp. I restarted my phone during the bootloop by holding the power button. After that, I opened the twrp to install the supersu then wipe dalvic cache. You may now boot up the phone and it took 10-15mins to use it because the system shows that it optimizes 205 apps(in my case, maybe because I have installed numerous apps). After that my phone is usefull again and I installed V4A because that's the only reason why I wanted to root this phone.
Here is all the information I have pulled so far from the phone. Have a screenshot attached from About device in settings. The attached zip file is all the information I could think to pull using adb . The attached file is my partitionlayout. I just ran cat against every file to see what it would give me and redirected the output. Using adb while the phone is in recovery let me pull and read the files I couldn't while the phone was booted.
@Alexis96312, try to run this command in terminal to get your partition map:
Code:
adb shell "su -c 'ls -l /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/'" > someFileName.txt
I have mine listed in the zip file as partitionLayout.txt It will list which names go to what device in /dev and save it in your current directory. The file can be used to get the correct partition layout on your phone. Post the results and I will repack the recovery to see if it will work for you. You can do it also with Carliv Image Kitchen, it has a menu :good:. You will have to modify the fstab files in the ramdisk folder of the extracted image to what the partition map specifies. I went thru all of them to be sure when I first ported TWRP.
@ANJIII is correct about the different versions, nice catch. I forgot about that. I assumed you had the V0070UU version like mine, fault on me for not asking. Mine specifically says BLU_V0070UU_V07_GENERIC 25-11-2016 09:46. I'm thinking the GENERIC part comes from me having to flash the stock ROM. I think it had BLU_V0070UU_V07 with user/keys before I bricked it and had to flash the stock ROM. Got three extra apps that I instantly removed. Seems like the stock ROM function the same as before bricking flashing stock.
ScreenShot
ANJIII said:
can you send us your vivo xl2 specs because there are two versions of xl2, V0070UU and V0070EE. Mine is V0070UU. I just did some renaming and editing in the scatter file of MT6735 and it bootloop once after I installed the twrp. I restarted my phone during the bootloop by holding the power button. After that, I opened the twrp to install the supersu then wipe dalvic cache. You may now boot up the phone and it took 10-15mins to use it because the system shows that it optimizes 205 apps(in my case, maybe because I have installed numerous apps). After that my phone is usefull again and I installed V4A because that's the only reason why I wanted to root this phone.
Click to expand...
Click to collapse
Answer in pictures
ADB USB
It seem that the computer can't find it what now
Do I need to install the ADB driver again?
I'm trying to do it on stock recovery
Do I have to do it on TWRP recovery?
Alexis96312 said:
It seem that the computer can't find it what now
Do I need to install the ADB driver again
Click to expand...
Click to collapse
It look like the pid:vid aren't recognized correctly. Usually a reboot will help.
Are you connect using adb while in recovery? If so, see if Windows will install new drivers for you. My Linux box read mine as a Samsung at one point. Try running the ls part of the command in TWRP terminal.
This is where I fought with windows when the cord got pulled during flashing. I never got an error like the 2 at the top, always like the bottom one. I kept adding legacy hardware in device manager until one of them worked. The Linux version of SPFT always give a chip mismatch error. Wish it worked so I won't have to boot to Windows.
I kept doing format+download and and plugging the phone in until Windows recognized it because it was in a bootloop when that happened. You need the preloader to be recognized.
Both stock ROMs are on needrom.com. I downloaded the UU version, the EE version is what you might need. I'll pm you a link to my backups from TWRP to see if they will work for you. Same thing happened to me playing with the new ROM. Restoring my boot and system got it back working.
Hey everyone,
I know most of you guys flashed android oreo stable build on top of android n and got stuck in bootloop.
If you haven't made backup of your data, no need to worry, this guide will help you recover your data before you move on for a clean flash.
Requirements:
1. PC
2. ADB/Fastboot work environment
3. Patience
Steps:
1. Download this Chinese TWRP (click here)
2. Boot your phone to fastboot.
3. Boot your phone through fastboot to recovery using command "fastboot boot Chinese_TWRP_recovery.img"
4. Now download OOS N (4.5.15)
—> Full Zip (Official): http://bit.ly/2iWHloM
—> Full Zip (AFH Mirror): http://bit.ly/2l2IgIo
5. Push your OOS N zip to your device with this command "adb push -p name_of_that_file.zip /sideload". -p will show you the progress. If it doesn't work, try the same command without -p.
6. MOUNT SYSTEM PARTITION!!!
7. Install/flash OOS N zip. After you are done, DO NOT TRY TO BOOT TO OOS!
8. Boot your phone to fastboot.
9. Boot your phone through fastboot to recovery using command "fastboot boot Chinese_TWRP_recovery.img"
10. TWRP asks for your password now. Type it to decrypt the data.
11. Get your data from your device using "adb pull" or "adb backup" command. I haven't found any way to boot to OOS for now, so i don't recommend doing that. Only way I've been able to recover my data, is this method .
12. Format every partition after your files are in safe place.
13. Flash whatever ROM you want.
Have fun!
-jocx
Hello! Which of the checkboxes do i have to press in the Mount section? the 2 that say "System"?
---------- Post added at 02:14 AM ---------- Previous post was at 02:06 AM ----------
Nvm, i figured it out, but the method did not work! I did reset "System settings" using Oxygen Recovery. I hope that is not the reason i will not be able to get my data back ;(
When i run this command "fastboot boot Chinese_TWRP_recovery.img" it tells that it is waiting for the device
punit.pi said:
When i run this command "fastboot boot Chinese_TWRP_recovery.img" it tells that it is waiting for the device
Click to expand...
Click to collapse
Your drivers for fastboot may not be installed and thus the device in fastboot mode is showing up as unknown in windows/OS.
https://forum.xda-developers.com/showthread.php?t=2588979
Use to link above to install fastboot drivers
It didn't work with the Chinese TWRP but got it to work with blu_spark TWRP thanks again for the post!
This does not work for me. After installing OOS N and booting into the chinese recovery it does not ask me for my decryption key. It doesnt work with blu_spark either.
This is extremely annoying. Does anyone know if there is any other way to decrypt the data?
This is super annoying, why twrp dont ask for decryption pass?
OK, rebooted into system after installing 4.5.15 and got it to work
@Joocx, you are my hero.
I was able to do it with the Chinese_TWRP_recovery.img with -p on sideload.
However, the first time I tried to flash OOS 4.5.15 it gave me an error and didn't finished.
After, I just went back to Mount menu and I enable Cache, System, Data and Firmware.
I tried again to flash and it worked. Then I just restart to bootloader, "fastboot boot Chinese_TWRP_recovery.img" and voilá.
(now I'm restoring my Nandroid backup to see if I was able to full recover)
Thanks again.
---------- Post added at 05:52 PM ---------- Previous post was at 05:34 PM ----------
I was just able to restore my Nandroid backup with twrp-3.2.1-x_blu_spark_v8.61-op5_op5t (same I did the backup).
However, after boot I saw my lock screen with my wallpaper, but after unlock the phone soft reboots...
I'm trying to check what is the issue.
---------- Post added at 05:58 PM ---------- Previous post was at 05:52 PM ----------
Just wiped cache and dalvik-cache and now it is now rebooting.
Phone fully restored with no data loss.
PandaKiller said:
@Joocx, you are my hero.
I was able to do it with the Chinese_TWRP_recovery.img with -p on sideload.
However, the first time I tried to flash OOS 4.5.15 it gave me an error and didn't finished.
After, I just went back to Mount menu and I enable Cache, System, Data and Firmware.
I tried again to flash and it worked. Then I just restart to bootloader, "fastboot boot Chinese_TWRP_recovery.img" and voilá.
(now I'm restoring my Nandroid backup to see if I was able to full recover)
Thanks again.
---------- Post added at 05:52 PM ---------- Previous post was at 05:34 PM ----------
I was just able to restore my Nandroid backup with twrp-3.2.1-x_blu_spark_v8.61-op5_op5t (same I did the backup).
However, after boot I saw my lock screen with my wallpaper, but after unlock the phone soft reboots...
I'm trying to check what is the issue.
---------- Post added at 05:58 PM ---------- Previous post was at 05:52 PM ----------
Just wiped cache and dalvik-cache and now it is now rebooting.
Phone fully restored with no data loss.
Click to expand...
Click to collapse
Ssup bro!
Nice to hear that this helped you!
-jocx
You, sir, are a champ, I'm now decrypted and backing up for next 4 hours. I thought this would be a simple OTA, so didn't backup, but OnePlus, is full of surprises. They can't figure out the encryption update process.
Perfect thanks a lot...
Just to stress this...
NEVER REBOOT AFTER FLASHING
The new flash will trigger the generation of new keys and the old keys will be lost and with them all the "old" encrypted data...
YOU HAVE TO BY ALL MEANS BOOT INTO RECOVERY IF YOU HAVE TWRP INSTALLED OR BOOT INTO BOOTLOADER AND fastboot boot <twrp.img>
Make really sure, you do not mess this points up as there are dragons out there...
I can't get adb sideload to work, it says "error: device not found". i have the lastest ADB drivers installed. in TWRP, in the "advanced" tab when i try to use sideload it just says "starting ADB sideload feature" indefinitely.
My phone doesn't bootloop though, it just doesn't boot. all i have is a blue led lighting up and that's it.
Same. This is f!cked
Bigred065 said:
I can't get adb sideload to work, it says "error: device not found". i have the lastest ADB drivers installed. in TWRP, in the "advanced" tab when i try to use sideload it just says "starting ADB sideload feature" indefinitely.
My phone doesn't bootloop though, it just doesn't boot. all i have is a blue led lighting up and that's it.
Click to expand...
Click to collapse
In TWRP, go into 'Mount' and then disable MTP, should work now.
Followed steps, but when flashing Nougat zip I get error E1001 Failed to update system image
when i try to push the oss via sideload i got an error " error: closed" can somebody please helpe me :/
On the phone are all my pictures from my son from christmas -.-
What do you mean by "install/flash" oos zip ?
where did we push oos? @Joocx
Thank you very much for the guide, it worked flawlessly. Your guide saved the memories of my nephews first Christmas. (which are now backed up on three different places).
The only thing is that after backing up data to PC, you need to format data and start fresh. But that's kinda nice. Starting a new year with a refreshed phone.
How do I mount system partitiom?
YDsoundboost said:
What do you mean by "install/flash" oos zip ?
where did we push oos? @Joocx
Click to expand...
Click to collapse
Hi!
After pushing the zip to /sideload, go to twrp home page and select "install" and press go to device root and there should be folder called "sideload". There is the zip you've pushed.
-jocx
*DON'T FLASH BACK TO NOUGAT IF YOU ENJOY USING YOUR PHONE*
Ok guys ive made my return and im happy to bring the oreo ota with me.!
Steps to install if your on a rom.
1. Use this flash all link Here
2. After finished and setup your going to need a pc and sideload knowledge
3. Download these ota files
Latest August https://drive.google.com/file/d/1OhWZPTWcuo7zRu9bjiezjKEZxreOk6v7/view OREO
4. Get your phone into recovery mode.
4.a the file is gonna have a lot of letters please do not rename or it wont work
4.b before you get into recovery you will see a dead Android. This IS normal. Your going to want to hold power and push volume up. It's a split second kinda thing. Not something you guys forever. Hot that a few times if it doesn't work the first time.
5 your going to want to go to in recovery to apply update via adb for the August one
6. run the command adb sideload (now drag the file to the command prompt and press enter)
7 if all good you will see a verifiying update the step 1/2 when you see that your fine.
8 Let it do its thing and at the end you may see and error about a drive disregard that.
9 now follow steps 4-7 again but with Oreo ota
10 reboot your system and now you should have oreo!
If your stock locked and never been cocked you can try to install the same method above without using the flash all and if it works congrats if not unlock your bootloader and use the method above.
if any help is needed contact me @ [email protected]
HOW TO ROOT
1. DOWNLOAD THIS. https://drive.google.com/file/d/1zz3Fl9m4-_ozWW1U3ww_e6K_cHPPEMSv/view?usp=drivesdk
2. FASTBOOT BOOT OR FLASH IT RUNNING "FASTBOOT BOOT /PATH/TO/BOOT.IMG" OR FASTBOOT FLASH /PATH/TO/BOOT.IMG
3. REBOOT AND PROFIT.
TWRP 3.2.1-0 Bootable and Permanent
Bootable Fastboot boot this *ONLY FOR OREO*
*Permanent is broken* Use boot able
Unencryption for oreo
Encryption Remover *FOR OREO ONLY*
*Must format then flash*
OREO FLASH ALL OREO *YOU CAN ONLY FLASH THIS AFTER YOU HAVE TAKEN THE OTA* *IF YOU FLASH THIS AND YOU HAVENT AND YOUR PHONE BLOWS UP PLEASE VIDEO IT SO I CAN POST IT ON HERE AND SHOW WHAT NOT TO DO*
Thank to @XirXes for the ota files
There is no root available as of yet we need a boot image to get root once there is one we will have roms and root coming.
Screenies
Here you go
Installation went smooth. thanks for the OTA.
now towait for the root and all will be set
wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?
Amd4life said:
wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?
Click to expand...
Click to collapse
No. As of right now Oreo starts you clean when you do this
Amd4life said:
wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?
Click to expand...
Click to collapse
I recommend (from experience) not trying that.
Making a test twrp real quick
Damn...thanks for your work
joemossjr said:
Making a test twrp real quick
Click to expand...
Click to collapse
Looking to this!
Oreo build is almost as fastest as the Flash [emoji3][emoji16]
Sent from my Moto Z (2) using Tapatalk
Thanks, @joemossjr ! It installed for me too. In my case, for some reason, I had to rename it to update.zip before adb sideload would work, but I'm not sure why. Oreo, yayyyy!
can someone please pull a system backup not image? i have a twrp that you can boot not flash and pull the stuff
where's the TWRP, so only use a fastboot flash boot image.zip?
joemossjr said:
can someone please pull a system backup not image? i have a twrp that you can boot not flash and pull the stuff
Click to expand...
Click to collapse
I could, do you have the TWRP link?
---------- Post added at 12:55 PM ---------- Previous post was at 12:47 PM ----------
What I wanted to do was boot slot _b rooted 7.1.1 and copy slot _a stock Oreo, but it nagged me about potentially bricking in fastboot after fastboot set_active _b (i.e., due to invalid bootloader, etc.). A bootable TWRP straight to recovery would solve the issue. All I wanted to do was get a copy of Oreo boot_a, but adb as non-root user does not have permission to dd copy /dev/block/bootdevice/by-name/boot_a . So, yay for bootable TWRP!
@jhofseth please write me on hagnouts
please message me on hangouts people who want to help [email protected]
When you brick and have to go to a leaked 8.0 image
Unable to flash update
For whatever reason i'm unable to flash the update, and i'm currently left with a soft-bricked device. When trying to flash the update via recovery gives me
Code:
E:failed to unmount /
E:failed to set up expected mounts for install; aborting
failed to open driver control: no such file or directory
installation aborted
also when selecting install from ADB it says
Code:
Supported API: 3
stopping adbd...
failed to open driver control: no such file or directory
failed to open driver control: no such file or directory
is there something i can do to remedy this??
forgot to mention that yes i did install the first package and properly executed the flashall command from the first zip folder, and i did try sideloading the second package as it was and as an update.zip file to no success.
Shiro12 said:
For whatever reason i'm unable to flash the update, and i'm currently left with a soft-bricked device. When trying to flash the update via recovery gives me
also when selecting install from ADB it says
is there something i can do to remedy this??
forgot to mention that yes i did install the first package and properly executed the flashall command from the first zip folder, and i did try sideloading the second package as it was and as an update.zip file to no success.
Click to expand...
Click to collapse
Do you go completely stock?