OFFICIAL ONEPLUS 2 STOCK RESET
SOURCE : OnePlus L2 Support Team
VERSION : OxygenOS 3.0.2
DOWNLOADS
1. OnePlus2 Stock Reset Oxygen 3.0.2 Google Drive | Mediafire
2. Qualcomm Drivers Version 1.00.14 Google Drive | Mediafire
INSTRUCTIONS
You are doing this on your own responsibility. I take no responsibility whatsoever.
(THIS WILL WIPE YOUR ONEPLUS INCLUDING INTERNAL SD)
Download both the files from above and extract them (WinRAR, WinZIP, 7ZIP etc). You should have 2 folders: "OnePlus2_14_A.19_160604" and "qc"
A. Install the Certificates followed by the Qualcomm drivers.
1. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
2. Run the Qualcomm setup wizard (also located in the qc folder)
3. When setup completes, launch Command Prompt as an Administrator and type bcdedit /set testsigning on
4. Restart your computer. (Once it gets on, you should see a watermark stating Test Mode in the bottom right corner. If not, type bcdedit in Command Prompt as an Administrator to check if testsigning shows on. If not, repeat step 3.)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.19_160604 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 3).
3. First click the right square Chinese button. This will perform an integrity check on the downloaded files by verifying the MD5 hash values.
4. The system will seem to hang for a bit but should give you a pop up with the results of the above verification. When everything is ok. Press the start button. and let the progress finish. (If something is not ok, you will have to re-download the images. Google Drive can help extract only the necessary files.)
5. When it's done. Disconnect the USB cable and turn on the device.
6. Launch Command Prompt as an Administrator and type bcdedit /set testsigning off and reboot. Your system should no longer be in Test Mode.
C. Reset TAMPER Flag (Optional)
(This may potentially change your SmartPhone to a rather large paperweight and I will just laugh at you bearing no responsibility)
+ This part of the guide is not an Official Procedure and is in no way affiliated to OnePlus.
+ It is advisable to do this before any of the above mentioned operations.
+ Prerequisites:
Root
HEX Editor with root features
Root File Manager
+ BEWARE: You are modifying partitions which cannot be restored regardless of what you flash. You have been warned AGAIN
1. In File Manager browse to the devinfo partition (dev/block/bootdevice/by-name/)
2. Open devinfo using the HEX Editor.
3. Modify the TamperBit (attached screenshot) from 01 to 00.
4. Save and reboot to fastboot.
5. Type fastboot oem device-info to confirm.
CREDITS
OnePlus Team for the Files.
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Finally Managed to get a hand on this after a late night session with OnePlus. Great that we now have the MM Stock Reset which should theoretically help to get back to stock regardless of the ROM, customizations etc.
I believe this is the best option to use to return to stock from CM.
fareed_xtreme said:
OFFICIAL ONEPLUS 2 STOCK RESET
CREDITS
OnePlus Team for the Files.
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Click to expand...
Click to collapse
Thank you for mentioning me, Great Work
Is it recommended to do this to make sure that the installation is well made?
I installed 3.0.2 via OTA but my battery life is mediocre(3 hours). I know that in my Samsung devices it was better to clean flash the room yourself rather than doing it via OTA but I don't know about oneplus 2.
Should I just factory reset it or maybe do this whole procedure ?(except step C)
mantiyeah said:
Is it recommended to do this to make sure that the installation is well made?
I installed 3.0.2 via OTA but my battery life is mediocre(3 hours). I know that in my Samsung devices it was better to clean flash the room yourself rather than doing it via OTA but I don't know about oneplus 2.
Should I just factory reset it or maybe do this whole procedure ?(except step C)
Click to expand...
Click to collapse
You have a few options.
1. This threads Stock Reset option guarantees your phone will be Stock OnePlus, just as a new phone (Bootloader Locked, Recovery Stock, Kernel Stock etc). However, it requires some time and effort. [Recommended]
2. Factory Reset may fix your Battery issue (not sure) but it is the quickest method.
3. You could use @Spannaa 's Fastboot images to flash all the images in this thread but via fastboot which is quicker and requires minimal setup. [Recommended]
Hello , after b3 command of the tools I FAILED appears . Tips ?
---------- Post added at 02:43 PM ---------- Previous post was at 02:14 PM ----------
Thank you. Solved !!
fareed_xtreme said:
You have a few options.
1. This threads Stock Reset option guarantees your phone will be Stock OnePlus, just as a new phone (Bootloader Locked, Recovery Stock, Kernel Stock etc). However, it requires some time and effort. [Recommended]
2. Factory Reset may fix your Battery issue (not sure) but it is the quickest method.
3. You could use @Spannaa 's Fastboot images to flash all the images in this thread but via fastboot which is quicker and requires minimal setup. [Recommended]
Click to expand...
Click to collapse
Hello again,
When you say ''to flash all the images in this thread'' do you mean the 1. OnePlus2 Stock Reset Oxygen OS 3.0.2 and the 2. Qualcomm Drivers Version 1.00.14 ???
Or does it mean that flashing via fastboot the spanna image I am flashing everything at once?
Thank you very much
mantiyeah said:
Hello again,
When you say ''to flash all the images in this thread'' do you mean the 1. OnePlus2 Stock Reset Oxygen OS 3.0.2 and the 2. Qualcomm Drivers Version 1.00.14 ???
Or does it mean that flashing via fastboot the spanna image I am flashing everything at once?
Thank you very much
Click to expand...
Click to collapse
My Friend, you need to do any one of the above 3 mentioned methods. You could:
1. Follow this guide, the first post which has all the details. This is the method used by OnePlus to restore your phone when you have issues.
3. You could alternatively flash via Fastboot using the images from the mentioned thread.
You chose either one of the above mentioned procedures. Not both. If you run into issues do let is know. The procedure is detailed and if you follow my guide to the dot, you should be all set in the first attempt itself (for Flashing method 1)
Thanks fareed_xtreme, everything went well. Good job !
Sim and wifi not detected!!
fareed_xtreme said:
OFFICIAL ONEPLUS 2 STOCK RESET
SOURCE : OnePlus L2 Support Team
VERSION : OxygenOS 3.0.2
DOWNLOADS
1. OnePlus2 Stock Reset Oxygen 3.0.2 Google Drive | Mediafire
2. Qualcomm Drivers Version 1.00.14 Google Drive | Mediafire
INSTRUCTIONS
You are doing this on your own responsibility. I take no responsibility whatsoever.
(THIS WILL WIPE YOUR ONEPLUS INCLUDING INTERNAL SD)
Download both the files from above and extract them (WinRAR, WinZIP, 7ZIP etc). You should have 2 folders: "OnePlus2_14_A.19_160604" and "qc"
A. Install the Certificates followed by the Qualcomm drivers.
1. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
2. Run the Qualcomm setup wizard (also located in the qc folder)
3. When setup completes, launch Command Prompt as an Administrator and type bcdedit /set testsigning on
4. Restart your computer. (Once it gets on, you should see a watermark stating Test Mode in the bottom right corner. If not, type bcdedit in Command Prompt as an Administrator to check if testsigning shows on. If not, repeat step 3.)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.19_160604 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 3).
3. First click the right square Chinese button. This will perform an integrity check on the downloaded files by verifying the MD5 hash values.
4. The system will seem to hang for a bit but should give you a pop up with the results of the above verification. When everything is ok. Press the start button. and let the progress finish. (If something is not ok, you will have to re-download the images. Google Drive can help extract only the necessary files.)
5. When it's done. Disconnect the USB cable and turn on the device.
6. Launch Command Prompt as an Administrator and type bcdedit /set testsigning off and reboot. Your system should no longer be in Test Mode.
C. Reset TAMPER Flag (Optional)
(This may potentially change your SmartPhone to a rather large paperweight and I will just laugh at you bearing no responsibility)
+ This part of the guide is not an Official Procedure and is in no way affiliated to OnePlus.
+ It is advisable to do this before any of the above mentioned operations.
+ Prerequisites:
Root
HEX Editor with root features
Root File Manager
+ BEWARE: You are modifying partitions which cannot be restored regardless of what you flash. You have been warned AGAIN
1. In File Manager browse to the devinfo partition (dev/block/bootdevice/by-name/)
2. Open devinfo using the HEX Editor.
3. Modify the TamperBit (attached screenshot) from 01 to 00.
4. Save and reboot to fastboot.
5. Type fastboot oem device-info to confirm.
CREDITS
OnePlus Team for the Files.
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Click to expand...
Click to collapse
I did as told and was able to boot up successfully. But unfortunately the sim and wifi are not getting detected...do you have any solution for this? Also the phone keeps rebooting at random...would be really thankful for a quick solution to this.
Thx!! My OnePlus 2 is almost dead. Fastboot recovery only works for CM recovery, and there is no ROM inside sdcard. I flash TWRP, but no working. ADB sideload, TZ version problem - no luck. Thank you for sharing this thread.
Now is back and alive again
muthukumarc said:
I did as told and was able to boot up successfully. But unfortunately the sim and wifi are not getting detected...do you have any solution for this? Also the phone keeps rebooting at random...would be really thankful for a quick solution to this.
Click to expand...
Click to collapse
Which version of OnePlus 2 do you have? I have tested this on the European version.
Try this, Re-Flash the whole package AGAIN. After the first boot, reboot into recovery and reset to factory defaults. If it still does not work out, then let me know.
fareed_xtreme said:
Which version of OnePlus 2 do you have? I have tested this on the European version.
Try this, Re-Flash the whole package AGAIN. After the first boot, reboot into recovery and reset to factory defaults. If it still does not work out, then let me know.
Click to expand...
Click to collapse
Thank you for the fast response...i have the A2003 that i bought in india...I am still having the same problem...flashed the os again and did a hard reset...but still sim and wifi are not detected.
Tryed this one but when i upgrade to 3.0.2or clean flash this my camera stays black. Any help for this?
muthukumarc said:
Thank you for the fast response...i have the A2003 that i bought in india...I am still having the same problem...flashed the os again and did a hard reset...but still sim and wifi are not detected.
Click to expand...
Click to collapse
Even I have an A2003, European version and Indian version are the same. Have you pressed the square button to verify if the Package you have downloaded is in good shape and not corrupted? Do check that.
Alternatively head over to this thread and try flashing through TWRP using the Fastboot package of 3.0.2.
Or you could flash the modem file manually if you know how it's done.
Also as a last resort, try flashing an older version of the stock reset (there will be a version 2.2.0 in the general section or through Fastboot using the thread provided above).
If after all this it still does not work, please open a ticket with OnePlus. Sorry for the inconvenience.
C.H.T.J. said:
Tryed this one but when i upgrade to 3.0.2or clean flash this my camera stays black. Any help for this?
Click to expand...
Click to collapse
Do follow the above recommendations. However, if it did not work for you with other ROMs, Resets or Fastboot Zips, then I am very sure, none of the above steps will be of much use. Maybe CM might help but again, it's a longshot. Best option for you is to open a Ticket with OnePlus as this looks more inclined towards a driver or hardware issue.
fareed_xtreme said:
Even I have an A2003, European version and Indian version are the same. Have you pressed the square button to verify if the Package you have downloaded is in good shape and not corrupted? Do check that.
Alternatively head over to this thread and try flashing through TWRP using the Fastboot package of 3.0.2.
Or you could flash the modem file manually if you know how it's done.
Also as a last resort, try flashing an older version of the stock reset (there will be a version 2.2.0 in the general section or through Fastboot using the thread provided above).
If after all this it still does not work, please open a ticket with OnePlus. Sorry for the inconvenience.
Do follow the above recommendations. However, if it did not work for you with other ROMs, Resets or Fastboot Zips, then I am very sure, none of the above steps will be of much use. Maybe CM might help but again, it's a longshot. Best option for you is to open a Ticket with OnePlus as this looks more inclined towards a driver or hardware issue.
Click to expand...
Click to collapse
Sorry for the delayed response...i tried the fastboot method as well i have wifi now but no sim yet... i think i found out the problem. The IMEI number seems to be missing... and i read that would be the case for sim not detected.... i tried lots of methods (trying to get into engineering mode & using terminal emulator) to rectify it but was unsuccessful... I think the methods i saw were all for mediatek phones...couldnt find one for qualcomm....do you know any right way for fixing the IMEI issue? Thank you so much for your help so far on this.
muthukumarc said:
Sorry for the delayed response...i tried the fastboot method as well i have wifi now but no sim yet... i think i found out the problem. The IMEI number seems to be missing... and i read that would be the case for sim not detected.... i tried lots of methods (trying to get into engineering mode & using terminal emulator) to rectify it but was unsuccessful... I think the methods i saw were all for mediatek phones...couldnt find one for qualcomm....do you know any right way for fixing the IMEI issue? Thank you so much for your help so far on this.
Click to expand...
Click to collapse
I don't have much information on this. If your IMEI doesn't show, it means that one of your device specific partition is corrupted (I guess it's EFS, not sure). If you have a nandroid backup of all your partitions, then you could use them to recover. Else, your options are limited and your only friend is Google search. This doesn't usually happen.
When everything is ok. Press the start button. and let the progress finish.
Click to expand...
Click to collapse
How much time it can take? Mine is going on for almost two hours now
Only Stop button is clickable and the square button too. Start,Enum, Exit are grayed out.(not clickable)
Btw i did press the stop button after getting frustrated for more than half an hour.
And then again performed integrity check. And then again pressed the start button.
When it finish, does it show some notification?
Chhatrapal said:
When everything is ok. Press the start button. and let the progress finish.
How much time it can take? Mine is going on for almost two hours now
Only Stop button is clickable and the square button too. Start,Enum, Exit are grayed out.(not clickable)
Btw i did press the stop button after getting frustrated for more than half an hour.
And then again performed integrity check. And then again pressed the start button.
When it finish, does it show some notification?
Click to expand...
Click to collapse
This could mean that it is still waiting for your device to connect. Have you double checked your drivers and have you found the different line in the flashing app? You will need to restart the process and follow it step by step again.
It will usually take between 8 - 12 minutes max to finish flashing in the app. Also once it's done, in the app all lines will turn green (if I recall correctly).
So i've tried this and various other methods along similar lines. The flashing tool finishes and goes green but then also goes red.
On the reboot, recovery is still missing and i have fastboot.
If i use 'fastboot continue', I boot into the rom for setup and everything starts to work. However, I don't have any recovery, so the phone does not boot. Bootloader is now locked too so I can't try to flash recovery.
Related
<disclaimer> I take no credit for anything in this guide. A BIG Thanks goes out to @tennear, @Unjustified Dev, @DrakenFX and @Starvirus. They are the ones who figured out the process described below and provided the excellent LineageOS 14.1 ROM. I just wrote this all-in-one-guide because I think the information is way too cluttered and spread over these forums.</disclamer>
<disclaimer> If you're not 100% sure what you're about to do, please first scroll down to the bottom of this post to see a list of DON'T's, a few things you SHOULD ABSOLUTELY NOT DO if you want to keep using your device.</disclaimer>
After having had quite some phones (Moto Defy +, Oneplus One, Nexus 5x,...) and having flashed a lot of ROMs on them, I thought I had quite some experience in these matters. Alas. Unlike Oneplus, ZTE would rather not have users fiddling with their devices. There are also three versions of the Axon 7 called the A2017 (China), A2017G (Global) and A2017U (USA), each with some minute differences from the others. This makes unlocking BL, flashing a custom recovery and installing custom ROMs not so easy on this device.
The following guide describes how to go from a stock, not rooted, locked bootloader A2017G on Marshmallow Firmwares (B03 to B10) to an unlocked bootloader TWRP recovery LineageOS 14.1 A2017G. A2017U users, this guide should work for you too, but I hear there's an alternative, easier process exclusively for A2017U users. A2017 users do not proceed, this guide won't work for you. Users on stock Nougat, do not proceed, this guide won't work for you. You need to downgrade to Marshmallow first. Even A2017G or A2017U Marshmallow users must proceed with caution. There's always a tiny chance this process bricks your device. By following this guide, you will lose all your data on your internal memory. Please backup before proceeding. The data on your SD card should be safe.
A) Flashing TWRP Recovery to your device.
Q: Why do I need TWRP?
A: TWRP is a custom recovery system. It lets your backup your system in case anything goes wrong. It also lets you flash custom ROMs and zip files containing patches like viper4android or A.R.I.S.E. (audio) and root your device via SuperSU.
0) Boot up a windows computer with a 64bits processor. Verify your Axon 7 is charged at least 75%. Temporarily disable your antivirus software to allow axon7tool to work.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4UVMBVpYdVwcnlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery"
21) Wait until it finishes
22) Your phone should reboot
23) Shut down your phone and boot it to TWRP by holding both the power and volume up button to verify you have TWRP
24) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
NOTE: if you have problems connecting to your phone as QUSB_BULK, download Zadig and replace your drivers with WinUSB ones. If axon7tool doesn't recignise your device even when connected as QUSB_BULK, try killing adb.exe via task manager before retrying.
B) Unlock the bootloader
Q: Why do I need to unlock the bootloader?
A: With an unlocked bootloader, you can install custom ROMs.
1) Go to https://mega.nz/#F!rcFCQZ7C!vn457hU1zDwc0uVpvm5otw and download the aboot.img file from there (1024Kb). Put it in the same folder you used in the previous process
2) Download this file: https://www.androidfilehost.com/?fid=529152257862665656
3) Unzip the file and copy/cut the file called "fastboot_unlock.img"
4) Paste that file in the folder where "adb.exe", "axon7tool.exe", "recovery.img", "recovery.bin" and "aboot.img" are located
5) If there's none open, open a new command window in that folder again (Shift + right-click and "open command window here")
6) Type "adb push aboot.img /sdcard/" and hit enter
7) Type "adb push fastboot_unlock.img /sdcard/" and hit enter
8) Type "adb shell dd if=/dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img" and hit enter
9) Type "adb shell dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot_lock.img" and hit enter
10) Type "adb pull /sdcard/fbop_lock.img" and hit enter
11) Type "adb pull /sdcard/aboot_lock.img" and hit enter
12) Type "adb shell dd if=/sdcard/fastboot_unlock.img of=/dev/block/bootdevice/by-name/fbop" and hit enter
13) Type "adb shell dd if=/sdcard/aboot.img of=/dev/block/bootdevice/by-name/aboot" and hit enter
14) Type "Adb reboot bootloader" and hit enter to go to the bootloader
15) Type "Fastboot oem unlock" and hit enter
16) Follow the instructions on your phone and use the volume and power buttons to confirm you want to unlock your bootloader
17) Boot into TWRP by holding both power and volume up button
18) Type "Wipe" and choose "Format Data"
NOTE: If you get a permissions denied issue, try doing these steps while your device is in TWRP.
C) Update bootstack, Install LineageOS 14.1 and update your TWRP to latest version
Q: Why do I need Lineage OS 14.1?
A: It's a custom ROM that's a lot smoother than any available stock rom for any of the Axon 7 versions. Aside from an audio bug (the speakers make a rattling noise when the volume is turned higher than 80-90%) it's perfect. You can however find quite some other decent ROMS here.
Q: Why do I need the latest TWRP?
A: Tenfar's signed TWRP version is the only one that will be accepted by a locked phone, so you need to flash that version first to unlock your bootloader. You should however not use it for backing up and restoring, since it contains fatal flaws that can lead to bricking your phone. Update it using the steps below.
1) Download the latest unofficial Lineage OS 14.1 ROM from here: https://www.androidfilehost.com/?fid=457095661767134540
2) Download the A2017G Nougat bootstack from here: https://www.androidfilehost.com/?fid=673368273298930583 (A2017U users: your bootstack is here
3) Download the latest TWRP .img from here: https://build.nethunter.com/twrp/zte/twrp-3.0.4-1-ailsa_ii.img
4) Download a Google Apps version from here: http://opengapps.org/?arch=arm64&api=7.1/ .You must use an ARM64 file since that is the type of the CPU in the Axon 7. You must use 7.1 Gapps since that's the android version Lineage OS 14.1. is based on. Which one you choose is up to you, the "smaller" you go the less google apps will be installed as stock. You can always download the ones you miss via the play store after having installed LineageOS
5) Put the bootstack, the LineageOS and the chosen Gapps zips on your MicroSD card. Also put the TWRP.img on there
6) Flash the A2017G Nougat bootstack: Flash -> select the bootstack file on the microSD card
7) Flash LineageOS 14.1, then flash the Gapps zip file (again via TWRP)
8) Update your TWRP recovery by choosing "Install" and then clicking "Install Image" (bottom right) and selecting the TWRP .img file
9) Wipe dalvik, cache and data
10) Reboot
11) Enjoy your phone
In the unlikely case that you're greeted by a screen that asks you for a password because your system is somehow encrypted, reboot to TWRP and format your data partition to ext4 instead of f2fs (wipe -> advanced)
If your phone doesn't pop up as QUSB_BULK in EDL, you probably installed the driver that came with the phone. The device will pop up below Ports (COM & LPT) on Device Manager as Qualcomm something-something USB device. Uninstall that driver and reinstall winUSB drivers through Zadig.
If axon7tool fails with a what() and STD-exception and whatnot - if you installed the Zadig driver
Go to Device Manager, right click QUSB__BULK and Uninstall, then use the "adb reboot edl" command. Install the winUSB driver via Zadig. Reboot the phone by holding the power button about 10 seconds. Enter the command adb reboot edl again. Enter "axon7tool -r gpt boot recovery" in command.
If LOS refuses to install and you get the error axon7.verify_trustzone, install the universal bootloader (A2017X_B15_UniversalBootloader) before the N Modem.
So, the steps after you get access to TWRO are: 1) Install univ. BL (A2017X_B15_... .zip); 2) Install A2017G_N_modem.zip; 3) Install LOS14.1 zip; 4) Optionally, install Gapps; 5) Flash TWRP img
DON'T's:
- DO NOT use the signed TWRP (3.0.2) to backup or restore, it might brick your device
- DO NOT use this guide when you're on locked stock nougat, you need to downgrade to Marshmallow first
- DO NOT flash the wrong N bootstack. There's a different version for G and U devices
- DO NOT use this guide if you're on an A2017 (Chinese) device
- DO NOT unplug your cable from your PC or Axon while axon7tool is doing it's magic
- DO NOT make a mistake or typo, it can be fatal
- DO NOT try flashing random zips or files or formatting this and that when your device doesn't act according to the guide, post your issue instead
- DO NOT wipe anything else than Data, Dalvik and Cache in TWRP
ADDITIONAL STEPS:
- You can opt to root your device by flashing the latest SuperSU zip file
- You can opt to upgrade your unofficial LineageOS to the latest official version to receive weekly OTA updates
First of all, thanks a lot for this guide! But I saw the TWRP image is actually for the A2017U version. I read in the forum that flashing this on the G-version could soft brick your phone.
So the question is, can I just flash this on my A2017G or is there even a version for the european model?
PsyJoe said:
First of all, thanks a lot for this guide! But I saw the TWRP image is actually for the A2017U version. I read in the forum that flashing this on the G-version could soft brick your phone.
So the question is, can I just flash this on my A2017G or is there even a version for the european model?
Click to expand...
Click to collapse
Both the aboot.img and the TWRP.img come from A2017U versions. For the moment, we do not know if there is any difference in the aboot file between A2017U and A2017G, but it's highly unlikely. @tennear sent me a tool to read the partitions on my A2017G and the result showed the partitions were the same as those in the A2017U model.
For the moment, there's only one TWRP version, made for A2017U, but it seems to work on all models. I quote tennear here:
tennear said:
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.
Click to expand...
Click to collapse
I suspect nearly all bricks on A2017G devices happen when A2017G users use tenfar's tool to unlock the BL. There's a lot of margin for error, for example with the whole COM ports shizzle. I advise not to go down that route. I also advise against trying to flash a rooted image through TWRP without unlocking your bootloader. Especially the command "axon7root.exe -p 4 -b -r" (flashing both boot.img and recovery.img at the same time) seems to kill specifically A2017G devices, that seem to have an extra "DFU" mode, which the A2017 and A2017U devices don't seem to have. A2017G devices get stuck in that mode and there's no way to get them out again.
TL;DR I think the risk isn't in flashing TWRP, but in flashing both boot and recovery at the same time, in the axon7root tool and in flashing a rooted stock rom without unlocking BL.
Thank you for this one thread guide. Should make it a lot easier.
Maybe you can add a few words and links to the B03 files that allow a downgrade from higher versions.
You have a typo in step 14), should be adb not ab
Controllerboy said:
30) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
Click to expand...
Click to collapse
Hi,
So, the backup can be restored, even if we cancel the password? Isn't the backup encrypted than?
Also, when we do swipe to agree to modify the system partition, is flashing SuperSU enough to gain root?
I'm not so much interested in installing a custom ROM (yet) but do want a safe way to gain root.
Thanks for your time and efford,
Edit: And all this is safe (step A) when on B08?
Cheers,
/Cacti
For twrp. It work fine, i just flash it on my 2017G and everything is good.
Just the lastest version of SuperSU didn't work. I use 2.65
Znuf said:
For twrp. It work fine, i just flash it on my 2017G and everything is good.
Just the lastest version of SuperSU didn't work. I use 2.65
Click to expand...
Click to collapse
Hi,
Thanks Znuf, I'll give it a go then.
Cheerz,
/Cacti
Controllerboy said:
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QDL_BULK"
16) In command, type "axon7tool -r gpt" and hit enter
Click to expand...
Click to collapse
*sigh*
My device manager (Win7 x64) lists my A2017G as QUSB_BULK (and no red led, just a black screen) after reboot to EDL and the axon7tool sais not connected.
Anyone knows whats up with that and how to solve that?
TIA,
Cheerz,
/Cacti
le_cactus said:
*sigh*
My device manager (Win7 x64) lists my A2017G as QUSB_BULK (and no red led, just a black screen) after reboot to EDL and the axon7tool sais not connected.
Anyone knows whats up with that and how to solve that?
TIA,
Cheerz,
/Cacti
Click to expand...
Click to collapse
Hi
I don't think "QUSB_BULK" is bad, nor the lack of the red LED. When I did the process on my device it also showed different states at different attempts. I also had to try multiple times before axon7tool detected it.
If I were you, I would try to shut down your device completely, restart and try to boot to EDL again by using command "adb reboot edl". Alternatively, you could try removing your device from USB, then shutting it down, then holding both volume buttons while connecting it to your PC. Some G devices don't boot to EDL this way, but some do.
Just keep trying multiple times. Axon7tool doesn't work in any other mode than EDL, so you can't do any damage by using the tool in a wrong mode.
Controllerboy said:
Hi
I don't think "QUSB_BULK" is bad, nor the lack of the red LED. When I did the process on my device it also showed different states at different attempts. I also had to try multiple times before axon7tool detected it.
If I were you, I would try to shut down your device completely, restart and try to boot to EDL again by using command "adb reboot edl". Alternatively, you could try removing your device from USB, then shutting it down, then holding both volume buttons while connecting it to your PC. Some G devices don't boot to EDL this way, but some do.
Just keep trying multiple times. Axon7tool doesn't work in any other mode than EDL, so you can't do any damage by using the tool in a wrong mode.
Click to expand...
Click to collapse
Thanks for the tips, I'll keep trying both methods.
Cheers,
/Cacti
le_cactus said:
Thanks for the tips, I'll keep trying both methods.
Cheers,
/Cacti
Click to expand...
Click to collapse
I give up. Or at least at this computer.
Just to be sure, the QDL_BULK/QUSB__BULK, shoild it be an unknown device, one with a yellow exclamation mark? Or should I install a driver for it, and if so where do i find it? Google didn't help me out today
I'll try another pc, see if that does work.
Cheers,
/Cacti
I think we've found your problem. There shouldn't be a yellow exclamation mark, your PC should really have drivers for your device. On my PC, this wasn't needed, but can you try to download and open Zadig?
When connected in EDL mode, search for your device by ticking the box "show all devices" (in one of the options dropout links in the top bar). You should see "QUSB_BULK" again. Select "WinUSB drivers" and install those. See if your PC recognises your device in EDL after doing that and try finding it with axon7tool. A reboot of your phone might be needed.
Hi,
i unlock my A2017G b06 with a slightly different way (Starvirus + draken FX TWRP) but i forgot to make a backup of stock rom before flash cm13.
Can you please make a clean one and share it.
Thanks in advance
Thanks for the description.
For your information. As you can see in tennears thread, you can short cut steps 16 - 22 to "axon7tool -r gpt recovery boot". This saves a lot of time and reboots.
Also, in the BL unlock steps, "wipe data" most commonly not enough. You need "format data".
Killerdog said:
I unlock my A2017G b06 with a slightly different way (Starvirus + draken FX TWRP) but i forgot to make a backup of stock rom before flash cm13.
Can you please make a clean one and share it.
Click to expand...
Click to collapse
Here's the file from DrakenFX: http://forum.xda-developers.com/showpost.php?p=68873485&postcount=3
Flash bootstack only once, then flash BO6 stock ZIP. In my experience it doesn't replace TWRP with stock recovery, even when you're not rooted.
DeJe63 said:
Thanks for the description.
For your information. As you can see in tennears thread, you can short cut steps 16 - 22 to "axon7tool -r gpt recovery boot". This saves a lot of time and reboots.
Also, in the BL unlock steps, "wipe data" most commonly not enough. You need "format data".
Click to expand...
Click to collapse
Thanks for the tricks. I didn't know you could do all three commands at once. I'll update my guide.
Will this work for B08 or should I go all the way back to "B03 (or others)" ??
Tutorial looks good and simple, big thanks!
In general it works.
For some reason I was not able to update from DragenFX B06 to OTA B08. So I flashed stock recovery, stock B06, OTA B08 and just flashed back TWRP with axon7tool...and it worked. But it may be that I make some mistakes on the way to B08.
I was at BL unlock before.
Controllerboy said:
I think we've found your problem. There shouldn't be a yellow exclamation mark, your PC should really have drivers for your device. On my PC, this wasn't needed, but can you try to download and open Zadig?
When connected in EDL mode, search for your device by ticking the box "show all devices" (in one of the options dropout links in the top bar). You should see "QUSB_BULK" again. Select "WinUSB drivers" and install those. See if your PC recognises your device in EDL after doing that and try finding it with axon7tool. A reboot of your phone might be needed.
Click to expand...
Click to collapse
Hi,
That worked flawlessly on my Win7 box, but I have general USB problems on that device. Got timeouts a few times during the axon7tool -r commands, so I don't dare doing a axon7tool -w command on that machine. So I stepped over to my Win10 x64 machine, but that machine it keeps identifying it as a "Qualcomm HS-USB QDLoader 9008 (COM3) device." :crying: axon7tool -r gives my a "Failed to connect"
Thanks for the help though, much appreciated.
Cheers,
/Cacti
I would agree that it's not a wise idea to write a custom recovery to a phone when the connection between the phone and the PC is unstable.
However, that doesn't solve your problem. Seems like your PC decided to install some drivers that are incompatible with the axon7tool.
Did you already try to uninstall the Qualcomm drivers via device manager and reconnect your device to pc? Did you try Zadig on your win10 machine?
There's a guide on the internet to (temporarily) disable automatic driver installation for new USB devices. Perhaps you could do that and then use Zadig to install WinUSB?
To be honest, if that doesn't work I don't really know other things to try. Except visiting someone you know with a Win7 64bit PC, that is
Controllerboy said:
I would agree that it's not a wise idea to write a custom recovery to a phone when the connection between the phone and the PC is unstable.
However, that doesn't solve your problem. Seems like your PC decided to install some drivers that are incompatible with the axon7tool.
Did you already try to uninstall the Qualcomm drivers via device manager and reconnect your device to pc? Did you try Zadig on your win10 machine?
There's a guide on the internet to (temporarily) disable automatic driver installation for new USB devices. Perhaps you could do that and then use Zadig to install WinUSB?
To be honest, if that doesn't work I don't really know other things to try. Except visiting someone you know with a Win7 64bit PC, that is
Click to expand...
Click to collapse
Thanks for the tips. I'll let you know how things work out.
Cheers,
/cacti
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
All you will need link, at the end of the post. I don't know for how long it will be up, but you can use it for now.
By the way.... Should you find something useful here... please hit the thanks button in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00 (or any latest version).
Steps:
1. Install the windows drivers you downloaded
Note : If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
2. Open the folder you extracted SP Flashtool and run it as administrator.
3. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet. (should work with holding the power key down for a little longer than 10 seconds. If not hold down volume key and power button for the same amount of time - tested and working)
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a. adb reboot bootloader
b. fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10. Choose reboot to system and allow complete boot cycle! Essential!
11. Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version).
12. Once installed back to the windows terminal and issue:
a. adb reboot bootloader
b. fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note : Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
All you will need and credits:
https://drive.google.com/drive/fold...ourcekey=0-SDvJaXtWWk-TY9B53ct8dw&usp=sharing (thanks button, thanks button, thanks button!!! )
Results:
(it is in Greek, but you get the idea )
Hope I have helped! Happy playing with the commands and whole process! :good:
Lastly, if you get stuck at any point, you can either use this thread or PM me for further advice, explanation and/or any kind of assistance.
Note: Special thanks to @MotoJunkie01 for actually taking the time to further help people on this thread, as unfortunately I do not currently have the time to do so myself. It is worth checking out @MotoJunkie01 's threads also. There, you can find very useful and updated information.
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
If you find it useful, just hit thanks in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00
Steps:
1. Install the windows drivers you downloaded
2. Open the folder you extracted SP Flashtool and run it as administrator.
4. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet.
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a.adb reboot bootloader
b.fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10.Choose reboot to system and allow complete boot cycle! Essential!
11.Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version.
12.Once installed back to the windows terminal and issue:
a.adb reboot bootloader
b.fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note 1: Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
Note 2: If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
I apologize for not being able to post links, but I believe the required software is not particularly hard to find.
Hope I have helped! Happy playing with the commands and whole process! I will continue to help as much as I can :good:
Click to expand...
Click to collapse
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
MotoJunkie01 said:
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
Click to expand...
Click to collapse
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
r&xp said:
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
Click to expand...
Click to collapse
Thank you for the encouragement. I am in hopes that we can eventually get a dedicated device forum for the tb3-850f. I truly believe this tablet has the potential for plenty of future development.
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Rimmir said:
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Click to expand...
Click to collapse
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
r&xp said:
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Click to expand...
Click to collapse
Lol yessir, thanked!
MotoJunkie01 said:
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
Click to expand...
Click to collapse
Looking forward to it. I picked mine up from walmart just yesterday for using as a google maps/car media center
My Lenovo Tab 3 replacement finally arrived in the mail. I'll be picking up where I left off on compiling both unmodified stock and custom stock-based ROMs for this tablet.
On my modified stock based ROM, I'm considering the implementation of Substratum (Root Ver) for theming, but I would like to get the input of other device owners first. So far, I have debloated, deodexed and zipaligned the OS. I am including the modified/patched boot image with SuperSU v2.79 SR3 binaries installed for systemless root, Nova Launcher, Pixel Icon Pack, BusyBox v1.26.2 binaries pre-injected in /su/xbin/, and Kernel Adiutor-Mod installed in /system/apps/ for user defined adjustments to the stock kernel and governors.
You guys please give me input on what you would like included in the ROM. Thanks
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
Click to expand...
Click to collapse
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
chienfou said:
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
Click to expand...
Click to collapse
Really glad it worked for you!!!
Thumbs up! :good::good:
load the scatter file .txt in SP Flashrom is OK ... it show me purple color until finish loading the file.
but how come when I hit the green button Download, it seems like nothing downloading,
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
yiukiang said:
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
Click to expand...
Click to collapse
Try again to get TWRP installed to your /recovery partition or, alternatively, try to simply boot into TWRP from fastboot with the fastboot boot twrp.img command. It is common for members to experience some difficulty in installing custom recovery on this device. It has been my experience that most members are successful the second time around.
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
yiukiang said:
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
Click to expand...
Click to collapse
System updates (OTAs) won't install on rooted operating systems. To install an OTA, you must have unmodified stock /boot, /system, and /recovery partitions installed. On the GPS issue, go to Settings, Apps, and ensure Google Maps has been granted location access permission.
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
xavier234 said:
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
Click to expand...
Click to collapse
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
MotoJunkie01 said:
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
Click to expand...
Click to collapse
Hello, I'll weigh in on this one. There are multiple threads above the TB3-850F on this forum and also another forum.
I initially followed a different thread and instructions which caused my problem. Notably do not allow TWRP write access !!! This mistake caused the soft-brick.
Anyone following any other advice about TB3-850F or downloading any other image BEWARe. Only follow the advice in this thread by r&xp:
https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
Following this advice I now restored original image and then rooted in just a few hours.. Thank you r&xp for the good advice. :laugh:
hi folks,
tomorow should be getting my hands on the Ulephone power 2.
its the 5.5 screen 4gb ram 64gb rom.
all looks good until i have seen that the normal duel sim is one is hybrid for sdcard which is the norm right,
ant
but............
usually its sim 1 is for 4g cards and the hybrid is for 2g/3g/sdcard. yeah?
well the power 2 looks like its sim slot 1 is a 2g/3g slot and the hybrid is 4g or sdcard??????????
so will have to choose 4g or sdcard??? that cant be right?
I don't try this device with sim.
I know you can use the older power (1) have a sim 4g and SD card
So i believe the power 2 have the same method.
My first steps: How to root this device? i don't find a twrp.
I try to root with kingroot kingoroot, no results
Please?
The power 2 is the same as the power wrt the sim/memory card tray; both sim slots support 4g, but only one at a time. So if you put two 4g sims in, only one of them will have 4g (you choose which one), with a sim and a memory card the 4g should default to the inserted sim, but you might have to check this in settings.
Received my power 2 a couple of weeks ago after having it on pre-order for a month and I love it (sold the original power towards the cost).
I haven't tried rooting it yet, but was thinking of trying to flash twrp for the original power and seeing if that works. The great thing about these phones is that they're very hard to brick as you can always flash them as long as they still switch on.
Slàinte
mmidders
Hello my friends. I just bought the ulefone power 2 and i try to root it. Can anyone help me pls ???
mmidders said:
The power 2 is the same as the power wrt the sim/memory card tray; both sim slots support 4g, but only one at a time. So if you put two 4g sims in, only one of them will have 4g (you choose which one), with a sim and a memory card the 4g should default to the inserted sim, but you might have to check this in settings.
Received my power 2 a couple of weeks ago after having it on pre-order for a month and I love it (sold the original power towards the cost).
I haven't tried rooting it yet, but was thinking of trying to flash twrp for the original power and seeing if that works. The great thing about these phones is that they're very hard to brick as you can always flash them as long as they still switch on.
Slàinte
mmidders
Click to expand...
Click to collapse
I'm sure it's not working the twrp from the power (1).
If you have troubles with bootloops you can flash again the facatory rom and SP flash tools.
Press the power volume + and - and SP flash tools gonna flash.
The only way is to made a twrp from the k6000 http://fvknl.pro/k6000-plus-root-guide/
I don't know how, that device is almost the same...
There has been 2 ulefone Updates since launch
Android 8.0 is scheduled for end of the year.
Updates are fine, who can create a TWRP? So we can finally root the device
geheimke said:
Updates are fine, who can create a TWRP? So we can finally root the device
Click to expand...
Click to collapse
up
TWRP please!
Not so easy to do it. It will take very long time to port or build twrp
It sucks that power 2 still doesn't have root or twrp. I refuse to touch unrooted phones. I just received it as gift. I will keep it in a drawer and check next month or so.
I find that it lacks optimisation, kinda laggy in 3D/games ..
On Antutu, scores is 44000. I tested a galaxy S5 of a friend, it was 72000. For a phone that is several years older than Power 2.
I understand that it comes not with high end cpu/gpu but still..
I will copy my post from needrom website.
I have successfully rooted my two Power 2 phones. I had to port the TWRP recovery from Oukitel k6000 plus using Carliv Image Kitchen and following some online tutorials.
The only issue is, TWRP is semi functional, that is, touch doesn't work. I had to connect a mouse to my phone via OTG usb port and using some dongle to make USB smaller to fit the port. Also it comes with Russian language as default, but can be changed to English or any other as the original TWRP from Oukitel k6000+ (3rd button from second column, then click on Globe tab at the top right then choose English and the only button at the bottom to accept the change).
I am trying to fix this with no luck so far. But at least I am rooted and I was able to flash "SR1-SuperSU-v2.82-SR1-20170608224931.zip" which is the latest as of writing this. SuperSu functions properly and I am able to use AdAway.
If anyone is interested in the recovery image, I will post it. I flashed it using fastboot though after unlocking the bootloader using "fastboot oem unlock"
Click to expand...
Click to collapse
Rebel_X said:
I will copy my post from needrom website.
Click to expand...
Click to collapse
I would very much like to give this a go with my ulefone power 2!
Here you go, TWRP for Ulefone Power 2
What you need to do before you start flashing:
0) You need to have ADB installed on your computer, if you have Windows, the easiest way is by using 15 Seconds ADB Installer v1.4.3.
1) Your bootloader must be unlocked, otherwise flashing recovery will fail using fastboot command. PLEASE NOTE: When unlocking the bootloader, your phone will do a factory reset automatically, so backup all your important files beforehand.
To unlock the bootloader:
a) Go to Settings -> About Phone -> Build number (tap on it 7 times to unlock Developer Options) -> Tap on back to Settings menu then Developer Options.
b) Now move the slider for "OEM Unlocking" to enable it, say yes to the warning message.
c) Enable "USB Debugging"
d) Connect your phone to your computer via USB cable, say Yes for the dialog on your phone to trust your computer for debugging using USB.
e) Run command prompt and type
Code:
adb reboot bootloader
Then press enter
f) Once in bootloader, type
Code:
fastboot oem unlock
Then press Volume UP on your phone to allow OEM Unlock. It shouldn't take long, just few seconds and a message will appear on command prompt saying success or OK.
g) Type
Code:
fastboot reboot
To reboot your phone, it might reboot twice, it will do a factory reset and you will have to "Enable Developer Options and USB Debugging" again. As a side note, you will also notice that OEM Unlocking is grayed out. It will remain like that unless you do "fastboot oem lock" or erase the entire phone (might erase imei, but can be restored using SN Writer Tool) and/or flash bootloader using SP_FLASH_TOOL, but I digress.
2) Before you flash TWRP recovery, you must have SuperSu zip file on your phone beforehand, otherwise, your phone will not boot to Android. It has to do with something about the original TWRP for Oukitel k6000+, since the author of that TWRP port said so in the instructions about how to flash the recovery.
So download SR1-SuperSU-v2.82-SR1-20170608224931.zip from this link or the original SuperSu thread on XDA, and copy the file into your phone, say inside the Download folder in the internal memory of your phone.
3) Open command prompt again if it is not already open, type
Code:
adb reboot bootloader
4) Once in bootloader, type
Code:
fastboot flash recovery C:\TWRP-recovery-20170618-1340.img
Note: You replace the path for the TWRP recovery to where you have the file, to make it easier, just put it in the root of C drive.
Also, if you don't already know, while in command prompt, you can type C:\TWRP then press TAB to auto-complete the file name for you, so you don't have to type lengthy file names. Keep pressing TAB to cycle between similar occurrences, that is, if you have more than one file that their names start with TWRP
5) Press power button until phone shuts down. Then press Volume UP + Power and keep holding until you see super tiny text with 3 options to cycle between. Release your fingers from Volume Up + Power, then cycle between the options using Volume Up only, choose "RECOVERY" which is the first in the menu, then press Volume DOWN to select.
6) Wait a few seconds, you will be inside TWRP, connect your phone with a mouse since touch doesn't work here. Once you do, you will see a mouse pointer appear. I used a wireless mouse with bluetooth dongle, with an adapter to change USB port size.
7) Slide the slider to the right, to enable modifications to System partition. Don't press anything else, unless you know Russian, I don't .
8) To change the language to English or your own language, click on the third button of the second column. Then click on the Globe tab on the top right corner, change language, then press the only button at the bottom to accept. Language of the UI is changed.
9) Click "Install", browse for the SuperSu zip file you have downloaded to your phone, for example inside the Download folder. And then select it.
10) Slide to the right to flash SuperSu.
11) From the TWRP menus, you can reboot your phone.
12) Enjoy your rooted Power 2 phone. :good:
---------- Post added at 04:47 AM ---------- Previous post was at 04:47 AM ----------
alpsayin said:
I would very much like to give this a go with my ulefone power 2!
Click to expand...
Click to collapse
Check the post above :good:
hello , i got a ulefone power 2 but unfortunately its not powering on. As i am from india and returning or replacing is costly and timetaking process, i need you guys to help me. I tried to flash it with software available on the website but stuck. I need some checksum.ini file which is not there in the firmware file provided. So anyone please help me. the phone doesnt even show the ulefone logo. i can just see the charging percentage when the charger is connected, then keeping it connected i tried to turn on but didnt work. keeping the charger connected ,after some time the display goes off and no mater how long you press the power button , the display doesnt show up. I can only see the notification bulb.
Soft bricked :laugh: trying to recover the phone, official ulefone guide is useless. Getting some error about a missing checksum.ini file. Will keep this thread updated
All went well until step 9, where I realised factory reset deleted the supersu zip. So I tried to reboot into system to download it again. It never booted. Doesnt even go into adb mode.
Fastboot mode and TWRP intact (TWRP needs a mouse). I was able to flash original recovery via fastboot, getting "cannot load system.img" error when I try to flash system (it appears I might need to update my adb/fastboot version).
UPDATE: was able to flash the stock rom. And tried to follow the guide again, and faced the same symptoms. If i have working TWRP, then the system doesnt boot. And vice-versa. Will keep updated, i'm a persistent mf
Rebel_X said:
Here you go, TWRP for Ulefone Power 2
What you need to do before you start flashing:
0) You need to have ADB installed on your computer, if you have Windows, the easiest way is by using 15 Seconds ADB Installer v1.4.3.
1) Your bootloader must be unlocked, otherwise flashing recovery will fail using fastboot command. PLEASE NOTE: When unlocking the bootloader, your phone will do a factory reset automatically, so backup all your important files beforehand.
To unlock the bootloader:
a) Go to Settings -> About Phone -> Build number (tap on it 7 times to unlock Developer Options) -> Tap on back to Settings menu then Developer Options.
b) Now move the slider for "OEM Unlocking" to enable it, say yes to the warning message.
c) Enable "USB Debugging"
d) Connect your phone to your computer via USB cable, say Yes for the dialog on your phone to trust your computer for debugging using USB.
e) Run command prompt and type
Code:
adb reboot bootloader
Then press enter
f) Once in bootloader, type
Code:
fastboot oem unlock
Then press Volume UP on your phone to allow OEM Unlock. It shouldn't take long, just few seconds and a message will appear on command prompt saying success or OK.
g) Type
Code:
fastboot reboot
To reboot your phone, it might reboot twice, it will do a factory reset and you will have to "Enable Developer Options and USB Debugging" again. As a side note, you will also notice that OEM Unlocking is grayed out. It will remain like that unless you do "fastboot oem lock" or erase the entire phone (might erase imei, but can be restored using SN Writer Tool) and/or flash bootloader using SP_FLASH_TOOL, but I digress.
2) Before you flash TWRP recovery, you must have SuperSu zip file on your phone beforehand, otherwise, your phone will not boot to Android. It has to do with something about the original TWRP for Oukitel k6000+, since the author of that TWRP port said so in the instructions about how to flash the recovery.
So download SR1-SuperSU-v2.82-SR1-20170608224931.zip from this link or the original SuperSu thread on XDA, and copy the file into your phone, say inside the Download folder in the internal memory of your phone.
3) Open command prompt again if it is not already open, type
Code:
adb reboot bootloader
4) Once in bootloader, type
Code:
fastboot flash recovery C:\TWRP-recovery-20170618-1340.img
Note: You replace the path for the TWRP recovery to where you have the file, to make it easier, just put it in the root of C drive.
Also, if you don't already know, while in command prompt, you can type C:\TWRP then press TAB to auto-complete the file name for you, so you don't have to type lengthy file names. Keep pressing TAB to cycle between similar occurrences, that is, if you have more than one file that their names start with TWRP
5) Press power button until phone shuts down. Then press Volume UP + Power and keep holding until you see super tiny text with 3 options to cycle between. Release your fingers from Volume Up + Power, then cycle between the options using Volume Up only, choose "RECOVERY" which is the first in the menu, then press Volume DOWN to select.
6) Wait a few seconds, you will be inside TWRP, connect your phone with a mouse since touch doesn't work here. Once you do, you will see a mouse pointer appear. I used a wireless mouse with bluetooth dongle, with an adapter to change USB port size.
7) Slide the slider to the right, to enable modifications to System partition. Don't press anything else, unless you know Russian, I don't .
8) To change the language to English or your own language, click on the third button of the second column. Then click on the Globe tab on the top right corner, change language, then press the only button at the bottom to accept. Language of the UI is changed.
9) Click "Install", browse for the SuperSu zip file you have downloaded to your phone, for example inside the Download folder. And then select it.
10) Slide to the right to flash SuperSu.
11) From the TWRP menus, you can reboot your phone.
12) Enjoy your rooted Power 2 phone. :good:
---------- Post added at 04:47 AM ---------- Previous post was at 04:47 AM ----------
Check the post above :good:
Click to expand...
Click to collapse
mbs.yaswanth said:
hello , i got a ulefone power 2 but unfortunately its not powering on. As i am from india and returning or replacing is costly and timetaking process, i need you guys to help me. I tried to flash it with software available on the website but stuck. I need some checksum.ini file which is not there in the firmware file provided. So anyone please help me. the phone doesnt even show the ulefone logo. i can just see the charging percentage when the charger is connected, then keeping it connected i tried to turn on but didnt work. keeping the charger connected ,after some time the display goes off and no mater how long you press the power button , the display doesnt show up. I can only see the notification bulb.
Click to expand...
Click to collapse
Yeah, I had the same issue with the software that comes from Ulefone, it was asking for Checksum Generator that I have to download separately, it was like 150kb stand alone executable, you put it in the same folder of your stock ROM and wait forever for it to build the Checksum, which unfortunately didn't work since it complains about multiple RECOVRY images. So scratch that.
What you need to do, is as I did, download SP FLASH TOOL, it works great, no shinanigans or bullsh!t. It flashed the stock ROM in less than 2 minutes (around 1:30 seconds, to be exact) and revived my phone. There are plenty of youtube tutorials on how to use it. It is easy, just load the scatter file, for the other file, you can use the same all in one mtk file that comes with SP FLash Tool (I did this) or use the one from your STOCK ROM.
I hope that helps :good:
---------- Post added at 02:33 PM ---------- Previous post was at 02:27 PM ----------
alpsayin said:
Soft bricked :laugh: trying to recover the phone, official ulefone guide is useless. Getting some error about a missing checksum.ini file. Will keep this thread updated
All went well until step 9, where I realised factory reset deleted the supersu zip. So I tried to reboot into system to download it again. It never booted. Doesnt even go into adb mode.
Fastboot mode and TWRP intact (TWRP needs a mouse). I was able to flash original recovery via fastboot, getting "cannot load system.img" error when I try to flash system (it appears I might need to update my adb/fastboot version).
UPDATE: was able to flash the stock rom. And tried to follow the guide again, and faced the same symptoms. If i have working TWRP, then the system doesnt boot. And vice-versa. Will keep updated, i'm a persistent mf
Click to expand...
Click to collapse
All I can think of, you did something wrong. Initially, while I was trying to port TWRP, I had the same issue, I was trying to save some steps by flashing the recovery after I unlocked the bootloader without rebooting, the result was TWRP was not able to see any partitions.
Flash Stock-ROM and redo the steps. If you flash the preloader you might have to OEM Unlock your phone again.
I mentioned that if you "do not flash SuperSu, the system will NOT boot to Android". Also mentioned that after you unlock the bootloader, you have to RE-ENABLE USB Debugging, and while you are at it, check to see if your bootloader is unlocked inside Developer Options.
Edit: BTW, try not to unlock the bootloader if it is already unlocked. If it is unlocked, then skip the steps for unlocking the bootloader. It might cause an issue.
These are the steps I used to flash TWRP and I was able to flash SuperSu, all rooted apps are working fine, AdAway, Lucky Patcher...etc!
This:
Rebel_X said:
Here you go, TWRP for Ulefone Power 2
2) Before you flash TWRP recovery, you must have SuperSu zip file on your phone beforehand, otherwise, your phone will not boot to Android. It has to do with something about the original TWRP for Oukitel k6000+, since the author of that TWRP port said so in the instructions about how to flash the recovery.
Click to expand...
Click to collapse
And this combined:
Rebel_X said:
Here you go, TWRP for Ulefone Power 2
9) Click "Install", browse for the SuperSu zip file you have downloaded to your phone, for example inside the Download folder. And then select it.
Click to expand...
Click to collapse
Apparently if you dont flash the supersu first time you go into TWRP then it gets messy. Got the root working now. Thank you for the help and of course for the TWRP build!
Also if anyone's wondering it's possible to restore the system via fastboot. Extract the rom zip (can be downloaded from http:/ulefone.com/download/power2.html ) and flash boot, recovery and system;
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
link for sp flash tool u used.
Rebel_X said:
Yeah, I had the same issue with the software that comes from Ulefone, it was asking for Checksum Generator that I have to download separately, it was like 150kb stand alone executable, you put it in the same folder of your stock ROM and wait forever for it to build the Checksum, which unfortunately didn't work since it complains about multiple RECOVRY images. So scratch that.
What you need to do, is as I did, download SP FLASH TOOL, it works great, no shinanigans or bullsh!t. It flashed the stock ROM in less than 2 minutes (around 1:30 seconds, to be exact) and revived my phone. There are plenty of youtube tutorials on how to use it. It is easy, just load the scatter file, for the other file, you can use the same all in one mtk file that comes with SP FLash Tool (I did this) or use the one from your STOCK ROM.
I hope that helps :good:
---------- Post added at 02:33 PM ---------- Previous post was at 02:27 PM ----------
All I can think of, you did something wrong. Initially, while I was trying to port TWRP, I had the same issue, I was trying to save some steps by flashing the recovery after I unlocked the bootloader without rebooting, the result was TWRP was not able to see any partitions.
Flash Stock-ROM and redo the steps. If you flash the preloader you might have to OEM Unlock your phone again.
I mentioned that if you "do not flash SuperSu, the system will NOT boot to Android". Also mentioned that after you unlock the bootloader, you have to RE-ENABLE USB Debugging, and while you are at it, check to see if your bootloader is unlocked inside Developer Options.
Edit: BTW, try not to unlock the bootloader if it is already unlocked. If it is unlocked, then skip the steps for unlocking the bootloader. It might cause an issue.
These are the steps I used to flash TWRP and I was able to flash SuperSu, all rooted apps are working fine, AdAway, Lucky Patcher...etc!
Click to expand...
Click to collapse
ok what should i select there? formal all+download or download only or firmware upgarade???
[GUIDE] Huawei P10 Debrand/Rebrand/Update for Nougat&Oreo "Updated_19.5.2018"
Huawei P10 debrand/rebrand/update GUIDE
This thread will be discontinued, because Huawei refuses to provide unlock codes in the future, because of security reasons.
A shame that after the support end of the device it will be quite useless, cause you don´t get any security updates and have no chance to make secure again, by flashing something else.
I recommend you not buy any Huaweidevices in the future cause of that.
Disclaimer:
Before you do anything (stupid), backup your data!!!! Don´t make me or others responsible, i warned you!!!!!
If you wan´t to go back to your orginial version some day, you have to backup your OEMinfo!!! Best way to that is via TWRP before the rebranding ( see details of STEP 1)
When using the follwing script, take your time and drink a cup of coffee/tea!!!! First rule, don´t panic!!! Don´t do any (unnecessary) extra steps, while using the script!!!
Be aware that the phone sometimes takes longer for a step to finish, or you get stuck on a certain procedure (maybe depending on your branding). Key is to what to do at this point e.g. how to boot manually into fastboot.
If for some reason you must restart the procedure and factory reset appeared for the step, remember to look for the debugsettings and other mandatory settings.
Please use the orginal cable that came with the device for the rebranding and not some cheap aftermarket stuff. Also make sure you USB-Port has enough power (Might be the case on some notebooks)
70% of the posts/questions here are answered, if you read the gude carefully. So do you´re job and read!!!! Yes, i know it´s a lot to read, but details will maybe save your a**
Make sure you removed security pin from the device and also remove the google-account from the device itself, so you are not triggering googlesecuritysystem on nougat or oreo.
If you have a carrier version of the singleSIM P10 (VTR-L09xxxx) and you want rebrand or debrand it, you have to use the firmware for DualSIM (VTR-L29xxxx), or you SIM won´t be recognized anymore!
The good thing is, after that, you´ll be able to use both SIM or SIM and microSD. The provided HWOTA rom is mainly for the L29. If you want the L09 you have to replace the "update_all_hw.zip" in the update folder. If you not sure how to get, take a look in the Huawei-Forums
From Oreo to Oreo:
1. Download: @AndroidFilehost: HWOTA8_P10_B369a (Oreo) (MD5-Hash: fd330a74d22d2ef55a02bfcfdcea33ee )
All important files are inside this package!!
2. The steps for the this procedure are described here:
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
From Nougat To Oreo (or Nougat to Nougat, if you use the older files):
STEP 1 (optional steps for the oeminfo backup are cursive)
1. Unlock your bootloader: (There´s no way around it (unfortnuately), but after the procedure your device will be locked again, so don´t worry!)
The device will make a factory reset, so once again, BACKUP your files!!!!!!!!!!
If you already unlocked your bootloader with installed twrp you can go to step 2. You don´t have to install TWRP in the following miniguide. the script installs it automatically.
But if you want to backup your system or the OEMinfo you have to do this step.
1. Request an unlock code: https://docs.google.com/forms/d/e/1FAIpQLSeGwoQ44zqykuTfjCQrVP07JOHBYnBcAxAbz9SAVxPTFqMh9g/viewform or contact Huawei via live chat on their site.
It may take some time till you get the code. Hopefully they revamp their old unlocksite in the future, cause using a googleform seems to be temporary solutions anyways.
I also found a nice handy tool, but haven´t testet it yet on the p10 and officially it isn´t yet supported (for now only P20): https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711 If can prove that it´s working for the P10 just leave a comment in the thread here or in the orginal thread.
2 Download Hisuite and install: HiSuite
3. Enable ‘USB debugging’ and ‘OEM Unlock’ option from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
4. Install the ADB Minimal Installer or ADB and Fastboot for Mac and then restart if you already have the driver installed then skip this step.
5. Download TWRP for the P10
6. Now go to ADB and Fastboot installation directory open ADB folder and open the command window as an administrator
7. Connect your phone to PC and reboot the device into fastboot mode by typing “adb reboot bootloader”.
8. Type “fastboot devices” in command prompt and hit enter, it gives you serial numbers in return means your phone connected properly.
10. To unlock bootloader, type fastboot oem unlock yourunlockkey. Here replace unlock key with the key you got. For example “fastboot oem unlock 1234567890″.
11. If you want TWRP at this point you have to copy the downloaded twrp.img-file into the adb directory and type fastboot flash recovery twrpimage.img If you already have oreo running on your device, you must use this updatepackage and follow the guide <.--instead of twrpimage.img type in the exact filename you´ve downloaded.
12. To restart the system type “fastboot reboot”
13. Boot into TWRP and make a Backup of the "OEMinfo" and/or the system. You should be able to that without any guide, otherwise it´s a big mistake keep reading and following this guide!!!
STEP 2
1. Depending on your variant (You can check with the app firmwarefinder and imei, if the update is approved) use:
@AndroidFilehost: HWOTA_P10_B369a (Oreo) (MD5-Hash: b935a84180565fb1717a46d7337f2d43 )
@AndroidFilehost: HWOTA_P10_B365 (Oreo) (MD5-Hash: dbcd30e157625fc6d709b26d49421bb6 )
@MegaUpload: HWOTA_P10_B360 (Oreo) (MD5-Hash: E75DCD3950517E517865878DF8F21679 )
Be aware, it takes some modifications to the script if you wan´t to rollback to nougat. You´ll find guides here on xda for that. So really be sure if you want the new oreo version.
Also you bootloader may stay unlocked after using the script to update to oreo. You have to relock it manually. Boot in fastboot mode and use: fastboot relock INSERTYOURUNLOCKKEYHERE. After relocking your device will once again do a factory reset.
@MegaUpload: HWOTA_P10_B180 (Nougat) (MD5-Hash: 7E11EE56E83AB98DA4DE03273A6A7633 )
@MegaUpload: HWOTA_P10_B179 (Nougat) (MD5-Hash: 7D133B7484E7B4AABA84BA1284D148EC )
some older versions of the hwota:
@MegaUpload: HWOTA_P10_B164
@MegaUpload: HWOTA_P10_B130
and extract it on your PC or your device SD Card. I recommend using 7zip.
2. Run the update.bat file from a preopended CMD with adminrights, It will ask you if you copied the files. Press any key to continue.
3. Now connect your device and Reboot into Bootloader mode using “Volume Down + Power” or just use “adb reboot bootloader” then press any key.
4. The above step will install TWRP in your device.
5. Now Disconnect USB Cable and turn off your device and use “Volume Up + Power” to enter TWRP.
6. Once you’re in TWRP mode, plug in the USB cable again and press the Enter key on your computer.
7. If your files are saved in the HWOTA folder on the SD card, type 1 and press ENTER and if files are saved in the HWOTA/Update folder on your PC, type 2 and press ENTER. I recommend using the sdcard, cause you avoid problems with cheap cables, driverproblems, etc. Make sure you sdcard is fully working and has no errors.
8. It’ll ask you the update type, again type 1 and press the Enter button twice.
9 Done! Be patient an let it do it thing.
10. If you have any problems booting, i recommend doing an low-level factory reset after.
11. Run the update.bat file as an administrator, It will ask you if you copied the files. Press any key to continue.
12. Now connect your device and Reboot into Bootloader mode using “Volume Down + Power” or just use “adb reboot bootloader” then press any key.
13. The above step will install TWRP in your device.
14. Now Disconnect USB Cable and turn off your device and use “Volume Up + Power” to enter TWRP.
15. Once you’re in TWRP mode, plug in the USB cable again and press the Enter key on your computer.
16. If your files are saved in the HWOTA folder on the SD card, type 1 and press ENTER and if files are saved in the HWOTA/Update folder on your PC, type 2 and press ENTER. I recommend using the harddrive of the pc
17. It’ll ask you the update type, again type 1 and press the Enter button twice.
18. Done! Be patient an let it do it´s thing.
19. If you have any problems booting, i recommend doing an low-level factory reset after.
20. If you are rebranding your device with this method, you have to do the whole "STEP 2" again in order to flash the new system files correctly. Also sometimes the device gets stuck on installing the new system after pushing the big updatefiles via adb. Wait 10min and if nothings happens you have to longpress the power key in order to complete.
21. After the new firmwarefiles have been pushed the device will make a factory reset, if it fails, restart the device while pressing Power+Volume up and factory reset the device from the orginal recovery. If enter TWRP at this point, something went wrong.
After that, you´ll be able to get updates directly from huawei via systemupdate or use the awesome firmware finder from the playstore.
If you wondering how to use the firmware finder, watch this guide and do it step by step: Firmware Finder Tutorial If you don´t want to rebrand/debrand this maybe enough for you!
STEP 3 (Optional Update Method 1)
If you have already unlocked your bootloader und installed TWRP, you can also use this method to install the new system update (Don´t try it if you are running oreo or wan´t to install it!! There is no stable und fully functioning version of TWRP for Oreo yet!!!):
1. Make a complete backup of your current system via twrp and save the backup to sd or your pc.
2. Download one of the Huawei P10_HWOTA files from above, save it on your device and unzip it
3. Navigate to the update folder in the HWOTA-folder and copy the 3 files to your device (sdcard recommended)
4. Now Boot your device into TWRP
5. In TWRP flash "update.zip" and don´t reboot!!!
6. Flash "update_all_hw.zip" and don´t reboot!!!
7. Flash "update_data_public.zip"
6. Wait until all files are flashed
7. Done! Reboot TWRP
STEP 4 (Optional Update Method 2):
1. download and install Firmware Finder
2. start the app and search for the exact model you want to update for example VTR-L29C432
3. Look for an FullOTA package and check with your IMEI if the device is approved, otherwise it won´t install cause huawei hasn´t signed the update for your device (IMEI) yet.
3. hit the button "inapp proxy" and setup the proxy with localhost and port 8080 in your phone´s wifi settings.
4. check for the update in systemupdate-app from huawei on your phone, start the update and pause it quickly (at 1-3%).
5. delete the proxy in your wifi settings.
6. resume the update
7. After successful download your device will reboot and install the update
If it fails there actually 3 reasons:
1. your Wifi is crap
2. you didn´t do the steps correctly
3. the firmware isn´t approved for your device, so be sure to check with imei before
(Maybe) Useful Links:
Team MT
Team MT Firmware Database for VTR-L29C432
New Huawei Multi Tool from TeamMT (Be sure to check it out, it´ll soon support the P10)
Guide for firmware finder (made by Firicel69)
OEMInfo Collections
My Other P10 Plus Thread
[TOOL] TOOL ALL IN ONE (No P10 Support yet, but you can request it)
Tips:
Pressing Power + Volume Down will launch the Fastboot Mode
Pressing Power + Volume Up will launch the Recovery Mode
Pressing Power + Volume Down with connected USB will launch the Fastboot Mode in forcemode (might useful if you can´t boot to the bootloader)
Pressing Power + Volume Down+Up will launch the forced firmwareupdate if you have the suitable updatefiles on your sdcard in a folder named "dload"
Turning your phone off and then pressing Volume Down while pluging in your USB-Cable will launch the Fastboot Mode
This whole thing was only possible because of the hard work of other heros here on xda!!
Mainly its based on the method from mankindtw [Guide] Mate 9 Flash Update Package and Rebrand
Big THX to mankindtw for the script!! Please send him some money, if you can!
Thanks a lot.
I plan to use your method.
Can I change the Chinese version (VTR-AL00) to VTR-L29 version in this way?
sangsaby said:
Thanks a lot.
I plan to use your method.
Can I change the Chinese version (VTR-AL00) to VTR-L29 version in this way?
Click to expand...
Click to collapse
I´m not 100% sure, but in my opionion your VTR-AL00 (should be the china version with playstore) has exactly the same hardware as the VTR-L29. Be sure to backup you system or at least only your oeminfo.
In case you rebranding doesn´t function you can revert back to your orginal version via TWRP. Maybe you should try the 636 instead of the 432, depending on your location.
sangsaby said:
Thanks a lot.
I plan to use your method.
Can I change the Chinese version (VTR-AL00) to VTR-L29 version in this way?
Click to expand...
Click to collapse
Hi, i would like to rebrand to VTR-AL00, can you please send me the oem info of vtr-AL00?
Thank you
yangsong2000 said:
Hi, i would like to rebrand to VTR-AL00, can you please send me the oem info of vtr-AL00?
Thank you
Click to expand...
Click to collapse
Really sure, think about it twice, most people want rebrand their phone to L09 or L29. I makes no sense to rebrand to VTR-L00, the only advantage i see, is that you get updates earlier, but in fact the other variants get really often updates too.
People with VTR-L00 bought their device cheap in china and want to rebrand because of the missing playstore, or thr missing LTE bands.
Here you can see the differences between the variants:
http://consumer.huawei.com/en/phones/p10/specs/
I´m sorry i can´t provide yoo a oeminfo for the VTR-L00.
LwannaCM said:
Really sure, think about it twice, most people want rebrand their phone to L09 or L29. I makes no sense to rebrand to VTR-L00, the only advantage i see, is that you get updates earlier, but in fact the other variants get really often updates too.
People with VTR-L00 bought their device cheap in china and want to rebrand because of the missing playstore, or thr missing LTE bands.
Here you can see the differences between the variants:
http://consumer.huawei.com/en/phones/p10/specs/
I´m sorry i can´t provide yoo a oeminfo for the VTR-L00.
Click to expand...
Click to collapse
Actually in VTR-AL00 you have more features and the updates are faster. Moreover, you can install play store
By the way in case I don't like it, I can go back to European version. But at the moment I want to try VTR-AL00!
Do you know where I can download it or do you know someone who has it?
Thank you
Good day.. i am using this method.. i have one question..
what is this firmware provided?? HWOTA_P10_B164.zip
is it VTR-L29C432 or C636??
thanks!
francisac3 said:
good day.. I am using this method.. I have one question..
What is this firmware provided?? Hwota_p10_b164.zip
is it vtr-l29c432 or c636??
Thanks!
Click to expand...
Click to collapse
vtr-l29c432
Be sure to stick exactly to the steps! After its finished wait at least 15min.
If the device won´t reboot itself, you have to switch it off and maybe make a low level reset via orginal recovery, if you´re stuck in a boot loop.
Happened to me on 1 of 5 flashes.
yangsong2000 said:
Actually in VTR-AL00 you have more features and the updates are faster. Moreover, you can install play store
By the way in case I don't like it, I can go back to European version. But at the moment I want to try VTR-AL00!
Do you know where I can download it or do you know someone who has it?
Thank you
Click to expand...
Click to collapse
Sorry, i couldn´t find a oeminfo for the VTR-AL00
LwannaCM said:
vtr-l29c432
Be sure to stick exactly to the steps! After its finished wait at least 15min.
If the device won´t reboot itself, you have to switch it off and maybe make a low level reset via orginal recovery, if you´re stuck in a boot loop.
Happened to me on 1 of 5 flashes.
Click to expand...
Click to collapse
thanks.. will try this on my vtr-tl00 chinese version.. downloading the file now
Rebrand p10
Hi I have VTR-L29C738B150. It is brand Polish mobile Polkomtel. I want to change to open Europe software. I try to do this like in this post but nothing happened after I am in TWRP and click enter. Please help me.
what happened to the update.bat?? i cant use this.. when i open the update.bat... it only pops up then immediately close
DiMeteo24 said:
Hi I have VTR-L29C738B150. It is brand Polish mobile Polkomtel. I want to change to open Europe software. I try to do this like in this post but nothing happened after I am in TWRP and click enter. Please help me.
Click to expand...
Click to collapse
Maybe you forgot to unplug the cable. Just repeat the steps to this point. If you however get stuck, try to flash a custom rom for the p10 from this section, at least you get your device working again.
Maybe you find a solution here: [Guide] Mate 9 Flash Update Package and Rebrand it´s the same batch from mankindtw, only with files for the p10.
francisac3 said:
what happened to the update.bat?? i cant use this.. when i open the update.bat... it only pops up then immediately close
Click to expand...
Click to collapse
Maybe the update.bat hates you, just kiddin Open a CMD as admin run the update.bat from there. What you describe is a common problem and relates to a lot of other batchfiles
Rebrand P10
LwannaCM said:
Maybe you forgot to unplug the cable. Just repeat the steps to this point. If you however get stuck, try to flash a custom rom for the p10 from this section, at least you get your device working again.
Maybe you find a solution here: [Guide] Mate 9 Flash Update Package and Rebrand it´s the same batch from mankindtw, only with files for the p10.
Click to expand...
Click to collapse
I do all like You say. But I have a problem (I can't do backup in TWRP and while I install TWRP on the end there is a error). Maybe I shoud set something in developer option?
DiMeteo24 said:
I do all like You say. But I have a problem (I can't do backup in TWRP and while I install TWRP on the end there is a error). Maybe I shoud set something in developer option?
Click to expand...
Click to collapse
Please read again everything in Step 1, there lies your answer how to get your TWRP and what to activate in developersettings. This step has nothing to do with the update.bat and is absolutely crucial and mandatory.
After installing TWRP the official way, make a backup and continue.
Rebrand P10
LwannaCM said:
Please read again everything in Step 1, there lies your answer how to get your TWRP and what to activate in developersettings. This step has nothing to do with the update.bat and is absolutely crucial and mandatory.
After installing TWRP the official way, make a backup and continue.
Click to expand...
Click to collapse
I will show you where is the problem.
when I boot in fastboot I see something like this:
replace recovery to TVRP
target reported........
sending recovery........
OKEY
writing recovery.....
FAILED <remote:Command not allowed>
finished
after this I do all with volume up+power and nothing happened
DiMeteo24 said:
I will show you where is the problem.
when I boot in fastboot I see something like this:
replace recovery to TVRP
target reported........
sending recovery........
OKEY
writing recovery.....
FAILED <remote:Command not allowed>
finished
after this I do all with volume up+power and nothing happened
Click to expand...
Click to collapse
O.K. now i understand, did you set OEM-Unlocking in Developer Options? It seems like you have a locked FRP and your device doesn´t allow flashing the custom recovery.
Someone already had this problem on the Mate 9:
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page56
LwannaCM said:
O.K. now i understand, did you set OEM-Unlocking in Developer Options? It seems like you have a locked FRP and your device doesn´t allow flashing the custom recovery.
Someone already had this problem on the Mate 9:
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page56
Click to expand...
Click to collapse
I have FRP lock but I cant set OEM unlocking in developer option because it is grey (non active)
DiMeteo24 said:
I have FRP lock but I cant set OEM unlocking in developer option because it is grey (non active)
Click to expand...
Click to collapse
K, now we are talking. Only thing you can do is flash your rom back to stock the semi-official way:
Download the firmware finder from the playstore.
Search for your device (not the one you want rebrand to) and check with IMEI in Firmware Finder just to be sure. Here you have a guide: Firmware Finder Tutorial
If you prefer reading, you can also follow this: https://forum.xda-developers.com/p10/how-to/guide-update-p10-via-firmware-finder-app-t3674477
Then you should be back to normal. When it´s finished you can try again, just be really sure following the steps and do no extra steps!! ....for Instance wiping something after you installed TWRP
You can try the dload method instead, but i recommend doing it via firmwarefinder, simply cause it will work.
Hi all, i have a problem that i can't solve, is the oem unlocking on my blu life one x2. I downloaded adb and fastboot (windows user), phone and adb drivers, and when i put the phone on bootloader mode, i run the "fastboot oem unlock" command, and the command prompt say: "need user wipe data, do fastboot oem unlock-go", so i put these command, and the oem is not unlocked yet, so I repeat those steps and the command prompt keeps showing me the same message (need user wipe data, do fastboot oem unlock-go). At this point, I have no idea what I'm doing wrong, I made the factory format many times, and I cannot unlock the OEM.
Can help me pls? I want to root my device, but because of this problem, I can not go to other steps :crying: :crying:
Thanks
Jonsonrocky said:
Hi all, i have a problem that i can't solve, is the oem unlocking on my blu life one x2. I downloaded adb and fastboot (windows user), phone and adb drivers, and when i put the phone on bootloader mode, i run the "fastboot oem unlock" command, and the command prompt say: "need user wipe data, do fastboot oem unlock-go", so i put these command, and the oem is not unlocked yet, so I repeat those steps and the command prompt keeps showing me the same message (need user wipe data, do fastboot oem unlock-go). At this point, I have no idea what I'm doing wrong, I made the factory format many times, and I cannot unlock the OEM.
Can help me pls? I want to root my device, but because of this problem, I can not go to other steps :crying: :crying:
Thanks
Click to expand...
Click to collapse
any here? ...
Jonsonrocky said:
any here? ...
Click to expand...
Click to collapse
Hi there, I have THE VERY SAME PROBLEM. Done the same, with same lame results... BOOTLOADER STILL UNLOCKED!!
It is really frustrating... been through many posts and guides but can't finish them... fastboot OEM unlock with the user data eraser switch didn't work out well in any case.
IS THERE ANYBODY OUT THERE WITH A COMPLETE WORKING GUIDE WILLING TO SHARE IT?
Thanks in advance.
J.
I have the same problem also, I have posted on another thread but no responses. here is my error:
"FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
finished. total time: 0.003s"
Has anyone figured out how to onlock the NEW BOOTLOADER?
I have a new life one x2 that BLU sent me.
pvkid said:
I have the same problem also, I have posted on another thread but no responses. here is my error:
"FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
finished. total time: 0.003s"
Has anyone figured out how to onlock the NEW BOOTLOADER?
I have a new life one x2 that BLU sent me.
Click to expand...
Click to collapse
I guess no one knows the answer to this problem. This phone used to be rootable but I guess Blu changed something in their latest release of the Life One X2
How to root a Blu life one X2
I actually still use this device and should be able to get you through this.
I'm not sure where are you on the device i.e. partly unlocked ect.
I'll start you from the top and I'll let you pickup wherever you like.
First, let's get our links ready (because I had these ready to go for myself).
I just checked it now, the device specific links still work.
ADB: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
TWRP: https://drive.google.com/file/d/0B6_iuhJQH7aGM0JkOXJkUHdlRHM
MAGISK: https://www.apkmirror.com/apk/topjohnwu/magisk-manager/
STOCK: https://drive.google.com/file/d/0B6_iuhJQH7aGUFdVVkkzUk8yYWs
DRIVER: https://drive.google.com/file/d/0B6_iuhJQH7aGa3Q1cmN3eHI3QUE
DOWNLOAD: https://drive.google.com/file/d/0B6_iuhJQH7aGR05CSnlhWm1HWWc
1) Download The driver, download program, and stock ROM.
2) Install the first two files.
3) Go to: C:\Program Files (x86)\Qualcomm\QPST\bin
4) When your device is off; Hold down the vol up AND down while turning on the device and wait until the text disappears
5) Plug in the phone to the PC and a red light should start blinking
5) Unzip the stock rom (when done, it can take a while).
6) Open QFIL.exe
7) You should see "(COM8)" on the top for the connection
8) Click on the first Browse button and select the mbn file from the extracted stock ROM folder
9) Click on LOAD XML and click rawprogram_unsparse_upgrade and then patch0
10) Click download until the phone reboots into test mode; click reboot to start the 'new' phone
-----------------------------------------------------------------------------------------------------------------------
1) Do the generic phone stuff to unlock the bootloader by enabling dev options and then enable BOTH OEM unlocking AND USB debugging
2) Download and install magisk from the link above and then download the zip file it gives you to flash
3) Download the TWRP image and ADB files listed above and do whatever you need/want to do (boot, flash, or both)
4) Flash the magisk zip file and your done
-----------------------------------------------------------------------------------------------------------------------
Delete the folders fota, fota-updater, and fire from the system partition in TWRP as these are the spyware/adware that BLU added
If you want to disable and other apps that BLU added, you can just rename the file from *.apk to *.ap
I'll try to be around if you have any questions
Thank you for this. I just left on vacation and will not be able to try this till next week, hope you are around then as I am sure I will have questions.
dougo007 said:
I actually still use this device and should be able to get you through this.
I'm not sure where are you on the device i.e. partly unlocked ect.
I'll start you from the top and I'll let you pickup wherever you like.
First, let's get our links ready (because I had these ready to go for myself).
I just checked it now, the device specific links still work.
ADB: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
TWRP: https://drive.google.com/file/d/0B6_iuhJQH7aGM0JkOXJkUHdlRHM
MAGISK: https://www.apkmirror.com/apk/topjohnwu/magisk-manager/
STOCK: https://drive.google.com/file/d/0B6_iuhJQH7aGUFdVVkkzUk8yYWs
DRIVER: https://drive.google.com/file/d/0B6_iuhJQH7aGa3Q1cmN3eHI3QUE
DOWNLOAD: https://drive.google.com/file/d/0B6_iuhJQH7aGR05CSnlhWm1HWWc
1) Download The driver, download program, and stock ROM.
2) Install the first two files.
3) Go to: C:\Program Files (x86)\Qualcomm\QPST\bin
4) When your device is off; Hold down the vol up AND down while turning on the device and wait until the text disappears
5) Plug in the phone to the PC and a red light should start blinking
5) Unzip the stock rom (when done, it can take a while).
6) Open QFIL.exe
7) You should see "(COM8)" on the top for the connection
8) Click on the first Browse button and select the mbn file from the extracted stock ROM folder
9) Click on LOAD XML and click rawprogram_unsparse_upgrade and then patch0
10) Click download until the phone reboots into test mode; click reboot to start the 'new' phone
-----------------------------------------------------------------------------------------------------------------------
1) Do the generic phone stuff to unlock the bootloader by enabling dev options and then enable BOTH OEM unlocking AND USB debugging
2) Download and install magisk from the link above and then download the zip file it gives you to flash
3) Download the TWRP image and ADB files listed above and do whatever you need/want to do (boot, flash, or both)
4) Flash the magisk zip file and your done
-----------------------------------------------------------------------------------------------------------------------
Delete the folders fota, fota-updater, and fire from the system partition in TWRP as these are the spyware/adware that BLU added
If you want to disable and other apps that BLU added, you can just rename the file from *.apk to *.ap
I'll try to be around if you have any questions
Click to expand...
Click to collapse
Any luck?
We have ROOT in BLU Life One X2
dougo007 said:
Any luck?
Click to expand...
Click to collapse
Sorry it has taken so long for me to get back to you but I have been traveling out of the county and have not had time to try this.
I have been successful in rooting 2 Life One X2 phones with this prosses. One was new out of the box and the second one was an older one about 2 years old.
Thank you for all your help when no one ele knew the answer.
My next project is to root an Oukitel OK6000, there does not seem to be much information on this phone. If you hear of anything please let me know.
Links aren't working
dougo007 said:
I actually still use this device and should be able to get you through this.
I'm not sure where are you on the device i.e. partly unlocked ect.
I'll start you from the top and I'll let you pickup wherever you like.
First, let's get our links ready (because I had these ready to go for myself).
I just checked it now, the device specific links still work.
ADB: Link works
TWRP: Link does not work
MAGISK: Link works
STOCK: Link does not work
DRIVER: Link does not work
DOWNLOAD: Link does not work
1) Download The driver, download program, and stock ROM.
2) Install the first two files.
3) Go to: C:\Program Files (x86)\Qualcomm\QPST\bin
4) When your device is off; Hold down the vol up AND down while turning on the device and wait until the text disappears
5) Plug in the phone to the PC and a red light should start blinking
5) Unzip the stock rom (when done, it can take a while).
6) Open QFIL.exe
7) You should see "(COM8)" on the top for the connection
8) Click on the first Browse button and select the mbn file from the extracted stock ROM folder
9) Click on LOAD XML and click rawprogram_unsparse_upgrade and then patch0
10) Click download until the phone reboots into test mode; click reboot to start the 'new' phone
-----------------------------------------------------------------------------------------------------------------------
1) Do the generic phone stuff to unlock the bootloader by enabling dev options and then enable BOTH OEM unlocking AND USB debugging
2) Download and install magisk from the link above and then download the zip file it gives you to flash
3) Download the TWRP image and ADB files listed above and do whatever you need/want to do (boot, flash, or both)
4) Flash the magisk zip file and your done
-----------------------------------------------------------------------------------------------------------------------
Delete the folders fota, fota-updater, and fire from the system partition in TWRP as these are the spyware/adware that BLU added
If you want to disable and other apps that BLU added, you can just rename the file from *.apk to *.ap
I'll try to be around if you have any questions
Click to expand...
Click to collapse
Hello dougo007,
Some of the links are dead and I am stuck and cannot figure out how to get passed the failed error on OEM unlock. It just keeps saying try unlock go.
Could you please provide new links or point me to someplace that I can use to oem unlock my BLU Life ONE X2. I searched and can't seem to find anything.
Having the same issue as you were and the links don't work
pvkid said:
Sorry it has taken so long for me to get back to you but I have been traveling out of the county and have not had time to try this.
I have been successful in rooting 2 Life One X2 phones with this prosses. One was new out of the box and the second one was an older one about 2 years old.
Thank you for all your help when no one ele knew the answer.
My next project is to root an Oukitel OK6000, there does not seem to be much information on this phone. If you hear of anything please let me know.
Click to expand...
Click to collapse
Hi pvkid, do you happen to have the files from the link? or new places I can find them I am stuck in the same place you were and can't for the life of me find anything anywhere else that helps.