I'm just going to leave this here in case anyone of you encounters this problem after modifying files in the system or after flashing custom ROMs. Do note that this fix does not remove the error, but instead bypasses it (for those without EFS backup) and enables the system to boot up normally (installs SuperSU as well). Also, as this requires the use of Odin, devices running MacOS or OSX are not supported.
An alternative (and easier) method has been discovered (refer to post #4 for more details)
Prerequisites:
1) TWRP recovery (https://drive.google.com/open?id=0B6QXDUz9wzc9YWcyZklybmZLc0k)
2) dm-verity bypass (https://drive.google.com/open?id=0B6QXDUz9wzc9Wk1ra0hKYVJtT1k)
3) Odin (https://drive.google.com/open?id=0B6QXDUz9wzc9c3BxYzdBNXhvbnc)
Steps (please follow the steps accordingly in order):
1) Place your phone in D/L mode
- Ensure device is fully turned off by pressing the volume down and power button
- Hold the volume down, home, and power button until a blue warning screen appears
- Press once on the volume up button
- Connect your device to your computer
2) Flash TWRP onto your device
- Open Odin and click on the "AP" tab, and then directing to the location of the TWRP recovery (TWRP_3.0.2.tar)
- Click on the "Options" tab and untick the option "Auto Reboot" [DO NOT TICK ANYTHING ELSE]
- Click on "Start" until Odin says "PASS!"
3) Reboot device into TWRP and flash the bypass zip
- Hold the volume down and power down button until the screen turns off
- Then, hold the volume up, home, and power button until "Set Warranty Bit : recovery" appears at the top of the screen
- Click on "Advanced", followed by "ADB Sideload" and ensure that "Wipe Dalvik Cache" and "Wipe Cache" is ticked, then swipe the bar at the bottom to start sideload
- Using the command prompt, type "adb sideload dm-verity bypass.zip" and wait till it completes
- Click on "Reboot System" after it completes, and your system should be able to boot
Possible errors which you may have encountered:
1) Odin does not detect my device
-- [You will need to install the device driver]
> Download the driver at https://drive.google.com/open?id=0B6QXDUz9wzc9LU9FclQ5WjNWRFk and install it.
2) My device does not boot into recovery after flashing via Odin
-- [System was trying to boot instead of recovery and had ignored the custom recovery after that]
> Go back to step 1) and repeat again
What is ADB and where can I get it?
> The installer is available for download at https://drive.google.com/open?id=0B0MKgCbUM0itNVB1elljU2NPR0k
> Run the installer and type "Y" for every prompt
> Open the command prompt (On your keyboard, press the windows key followed by the "R" key, then type "cmd" in the window and press enter
> Type "cd C:\adb" and you may continue with the steps (do note that C: is the mounted letter of your root drive which may be different from yours)
"* cannot read 'dm-verity bypass.zip *" appears after I entered the command
-- [ADB cannot read the file as the file cannot be found]
> Copy the dm-verity bypass.zip into your ADB folder, or after typing "adb sideload ", drag the dm-verity bypass.zip into your command prompt window and then pressing enter.
Do notify me immediately if there are any errors. Thank you and good luck!
Thanks to @KingWilliams for the dm-verity bypass zip which was present in one of your ROMs.
Q&A
Will OTA updates still work?
> No, the phone will detect that files has been modified and thus OTA updates are stopped. Updates will have to be carried out manually.
NIce Info Thanks, btw is it work on Marshmallow or Lollipop j500f ?
NIce Info Thanks, btw is it work on Marshmallow or Lollipop j500f
Click to expand...
Click to collapse
Should work on both versions but would you mind trying out a simpler and better method instead? It works fine on my device but I am unsure if it works on other models/variants. This method keeps the system status official and even enables OTA updates.
The guide below encompasses the updated method. Do note that as the guide is still being tested and is not an official method, I am assuming that all necessary drivers are installed correctly on your computer and that you have the knowledge and experience to work through the steps as these prerequisites are not included in this guide.
1) Download SamFirm (https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462), extract and then run the application.
2) After checking the "Auto" and "Binary Nature" box, type in your model (in your case, SM-J500F) and your region (refer to http://samsung-updates.com/device/?id=SM-J500F if you need help identifying your region) before clicking on "Check Update".
2.1) The application should now be able to detect a firmware saying (for example)
Code:
SamFirm v0.3.6.0
Checking firmware for SM-J500F/TGY/J500FZHU1API2/J500FZZH1API2/J500FZHU1API2/J500FZHU1API2
Model: SM-J500F
Version: J500FZHU1API2/J500FZZH1API2/J500FZHU1API2/J500FZHU1API2
OS: Lollipop(Android 5.1.1)
Filename: SM-J500F_1_20161018133014_hz4nve666g_fac.zip.enc4
Size: 1060126192 bytes
LogicValue: 0us57tdgetwzs2jy
3) Before clicking on "Download", ensure that the option "Decrypt automatically" is checked. The "Check CRC32" option is optional.
4) Once the application is done downloading and decrypting the firmware image, extract it.
5) Using Odin, flash BL, AP, CP, CSC and once it reboots and the error pops up, boot the phone back to the Download Mode.
6) Using Odin, flash AP only (untick BL, CP and CSC checkboxes).
The phone should now boot up normally into the system. Do report the results here for further analysis. Thank you!
Thanks mate, i'll try it :highfive:
Rizzed said:
Should work on both versions but would you mind trying out a simpler and better method instead? It works fine on my device but I am unsure if it works on other models/variants. This method keeps the system status official and even enables OTA updates.
The guide below encompasses the updated method. Do note that as the guide is still being tested and is not an official method, I am assuming that all necessary drivers are installed correctly on your computer and that you have the knowledge and experience to work through the steps as these prerequisites are not included in this guide.
1) Download SamFirm (https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462), extract and then run the application.
2) After checking the "Auto" and "Binary Nature" box, type in your model (in your case, SM-J500F) and your region (refer to http://samsung-updates.com/device/?id=SM-J500F if you need help identifying your region) before clicking on "Check Update".
2.1) The application should now be able to detect a firmware saying (for example)
Code:
SamFirm v0.3.6.0
Checking firmware for SM-J500F/TGY/J500FZHU1API2/J500FZZH1API2/J500FZHU1API2/J500FZHU1API2
Model: SM-J500F
Version: J500FZHU1API2/J500FZZH1API2/J500FZHU1API2/J500FZHU1API2
OS: Lollipop(Android 5.1.1)
Filename: SM-J500F_1_20161018133014_hz4nve666g_fac.zip.enc4
Size: 1060126192 bytes
LogicValue: 0us57tdgetwzs2jy
3) Before clicking on "Download", ensure that the option "Decrypt automatically" is checked. The "Check CRC32" option is optional.
4) Once the application is done downloading and decrypting the firmware image, extract it.
5) Using Odin, flash BL, AP, CP, CSC and once it reboots and the error pops up, boot the phone back to the Download Mode.
6) Using Odin, flash AP only (untick BL, CP and CSC checkboxes).
The phone should now boot up normally into the system. Do report the results here for further analysis. Thank you!
Click to expand...
Click to collapse
excuse me, i've tried this method but when i boot the phone to the recovery mode, an error message still show (Device does nit have DRK (Device Root Key), contact to SW PL please flash ENG binary then install DRK), any suggestion ?
dv6661 said:
excuse me, i've tried this method but when i boot the phone to the recovery mode, an error message still show (Device does nit have DRK (Device Root Key), contact to SW PL please flash ENG binary then install DRK), any suggestion ?
Click to expand...
Click to collapse
Sorry about that and for wasting your time. In my original thread, I stated that this method does not eradicate the problem completely but simply bypasses it. The guide that I had requested you to try had two differences - sets the system status to official and enables OTA updates. Now that I think of it, this method is only useful for devices that does not have a workable TWRP/CWM recovery yet, or to give people a peace of mind that their system is official and unmodified. Since entering the recovery mode resurfaces this problem , this method is more or less useless as OTA updates are installed in recovery mode. All updates would need to be done manually via Odin/Smart Switch.
You got to admit this method is simpler and easier though! Could I ask does this method work? Did your phone boot up normally? Thank you.
Rizzed said:
Sorry about that and for wasting your time. In my original thread, I stated that this method does not eradicate the problem completely but simply bypasses it. The guide that I had requested you to try had two differences - sets the system status to official and enables OTA updates. Now that I think of it, this method is only useful for devices that does not have a workable TWRP/CWM recovery yet, or to give people a peace of mind that their system is official and unmodified. Since entering the recovery mode resurfaces this problem , this method is more or less useless as OTA updates are installed in recovery mode. All updates would need to be done manually via Odin/Smart Switch.
You got to admit this method is simpler and easier though! Could I ask does this method work? Did your phone boot up normally? Thank you.
Click to expand...
Click to collapse
yes my phone just boot up normally, the only problem is when i entering recovery mode there's a message "dm-verity need to check verification failed drk first"
i fixed it by mount /system and it worked on j500f .
s10gopal said:
i fixed it by mount /system and it worked on j500f .
Click to expand...
Click to collapse
Are you sure about that? This error only appears when the /efs partition is corrupted.
100%
https://source.android.com/security/verifiedboot/
s10gopal said:
100%
https://source.android.com/security/verifiedboot/
Click to expand...
Click to collapse
Will test it out later on my device.
I have a question. Can I take a DRK backup from one phone and repair another? I have a working Galaxy S6 64gb, and a Galaxy S6128GB that has DRK issue.
Can't Flash TWRP, FRP lock :/
Hi, I have the dm-verification failed problem, but I can't flash twrp because of the FRP lock. Any solution? thanks
_ale33_ said:
Hi, I have the dm-verification failed problem, but I can't flash twrp because of the FRP lock. Any solution? thanks
Click to expand...
Click to collapse
Got to developer settings and tap oem lock on and it should fix your problem.
Hello.
My phone is a Samsung Note 5. 64gb, SM-N9208 ( Taiwan ).
Many many thanks for this post! I have trawled the net for weeks and weeks to find a solution for this ridiculous dm-verity, DRK missing fiasco. I have managed to fix it thanks to your instructions. I understand that this is a work around, don't mind that one bit! But should anyone have a solution to get rid of the problem permanently, you will be an even bigger hero. Let me know if anyone does. Best Regards. Ian.
JaanZZ said:
Got to developer settings and tap oem lock on and it should fix your problem.
Click to expand...
Click to collapse
there's a problem, a mobile go backup sent the device in bootloop, can't boot, only stock recovery or download mode available and i need to backup sensible data.
witty2309 said:
Hello.
My phone is a Samsung Note 5. 64gb, SM-N9208 ( Taiwan ).
Many many thanks for this post! I have trawled the net for weeks and weeks to find a solution for this ridiculous dm-verity, DRK missing fiasco. I have managed to fix it thanks to your instructions. I understand that this is a work around, don't mind that one bit! But should anyone have a solution to get rid of the problem permanently, you will be an even bigger hero. Let me know if anyone does. Best Regards. Ian.
Click to expand...
Click to collapse
Glad that I could help. I suppose you used the TWRP method to recover your device?
_ale33_ said:
there's a problem, a mobile go backup sent the device in bootloop, can't boot, only stock recovery or download mode available and i need to backup sensible data.
Click to expand...
Click to collapse
Perhaps the system files are corrupted. Try flashing the AP file (not HOME file) in Odin and you should be good to go.
Jamessr79 said:
I have a question. Can I take a DRK backup from one phone and repair another? I have a working Galaxy S6 64gb, and a Galaxy S6128GB that has DRK issue.
Click to expand...
Click to collapse
Really sorry for the late reply but in case you have not found an answer yet, no it's not possible (even if it is possible it would be considered illegal - duplicate IMEI).
Related
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.
<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
[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.
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step
lets get to it
place the magisk.apk and the stock boot.img
in the internal memory of your phone (downloads)
if you like to keep stuff organized :good:
3-step
follow the vídeo tutorial and use magisk manager
to patch your stock boot.img it will output a new
boot.img that includes magisk Root (patched_boot.img)
https://www.youtube.com/watch?v=BF4_hnKgjFA
ps: major ty to hovatek team for this great tutorial
step-4 use Google drive or usb OTG to get the patched_
boot.img to your PC and place it in the ADB folder
once you have oem(bootloader) unlocked just
rename the patched_boot.img to boot.img
step-5
unlock oem, these qilive devices wont unlock
the bootloader even if you enable it in DEV options
enable USB debug in dev options
you will need to use ADB commands
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot oem unlock
(MAJOR WARNING the fastboot
oem unlock will wipe/reset/factoryreset/delete your data)
after you give the command small letters will appear
on the phone screen(yes or no) hard to read dont be hasty plz
use VOLUME+ to select and VOLUME - to confirm
note: when my phone ended the unlock it whent back to
that black screen where you choose fastboot-recovery-restart
and was stuck there, side keys did nothing if this happens
just long press the power key for 10 sec it will shutdown
then press power again to turn on
first boot after unlock will take longer then normal dont freakout
after you unlock small letters will appear during boot up saying the device
is not safe unlocked ,you can later use ( fastboot oem lock )
step-6
flash the patched boot.img with ADB
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot flash boot boot.img
finished/ok
command- fastboot reboot
and voila you should now have magisk
installed in the app drawer, open it!!
step-7 run the install one final time from the
magisk manager and install magisk V16 using
recomended option it will verify/patch the boot image
Do NOT select the AVB 2.0 BOX it will bootloop the phone
and your done, enjoy your qilive rooted phone.
from this point on you can use the fastboot
command- fastboot oem lock
to remove the letters in boot up about the
device not safe unlocked
WARNING oem lock
will WIPE/FACTORY RESET again (god damn it!!)
ps: i had to install twice in a row,major pain in the ....
Repeat step 7 after Wipe/Reset
here is the stock boot for 2 qilive models
you can get the stock firmware for any qilive
at this site www.doc-doapi.com/EM/qilive/smartph...te_3m-fdd-cs_mul_20170818-110645_songlixin_PC
and get the recovery or boot from the unpacked firmware file
ps:my phone is the Q8SIN4GP AND ITS WORKING FINE
A VERY SPECIAL TY to topjohnwu (magisk creator), this man is nothing
short of a God damn genius!! , and if you can donate to him.
hope this helps other qilive users to root:highfive:
quick note on the qilive models, they have two model names
the cliente name in my case Q8SIN4GP
and the factory name in my model its 882912
in order to download the right firmware for your model
you need the factory model witch is what appears in the qilive
site above, it will be in the back of the phone or the original
box on a sticker just bellow the bar code, full model exempl
:Q8SIN4GP/882912 my firmware serves several models,
these Q8 models all start with 88xxxx WARNING
dont try this using the wrong firmware/boot file or you will DAMAGE your phone
Help with BOOTLOOP problems, if you find your self stuck in a bootloop
the phone wont go past the qilive logo and just stays there, dont freak out
you will loose your data but there is a way out
just keep pressing power + Volume up until a black screen with 3 options appears
when it does let go, use Volume + to select option and Volume - to confirm
select Fastboot or alternative select recovery and then select reboot to bootloader
both option will place your phone in Fastboot mode, once in fastboot mode
connect your phone to PC and use ADB commands to fix/bootloop
command- fastboot devices
serial appears
command- fastboot oem unlock (skip this if you use phone unlocked)
a confirm action option appears on the phones screen
use Volume up to say YES / or Volume Down to say NO
Warning oem unlock will WIPE/Factory reset your phone
once it finishes the phone will be stuck on the
Recovery/fastboot/restart screen just long press the power key
until the phone shuts down
start the phone again using Power + Volume up when the black
screen with the 3 options come up, let go and use Volume up to
select Fastboot mode and confirm using Volume Down
Once in fastboot connect your phone to PC and use ADB commands
command- fastboot devices
serial apears
Here you will flash the magisk patched_boot.img
the same image you used to root your phone
command- fastboot flash boot boot.img
it will say finished-ok (or similar)
command- fastboot reboot
the boot up time will be longer than normal
but the phone should now complete the boot
and present the inicial setup screen, select language
enter your mail, the usual bla bla...
any way at this point just repeat step 7
to get root running again
sp flash tools v5.1716.
phonedriller said:
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step....
Click to expand...
Click to collapse
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
Awsome work congrats, as for the recovery so far no luck so try not to go 2 crazy until a working recovery is up and working , install stericsons busy box this is always the first root app i install
If possible buy sterics busybox pro and titaniumbackup pro if you want to install apps to sd card apps2sd pro all of these can be tested in free
Version,again nice work congrats enjoy you rooted phone :highfive:
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
phonedriller said:
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
Click to expand...
Click to collapse
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
xdacktheresianum said:
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
Click to expand...
Click to collapse
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
phonedriller said:
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
Click to expand...
Click to collapse
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
xdacktheresianum said:
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
phonedriller said:
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
Click to expand...
Click to collapse
thank you, phonedriller
everything worked perfectly via SPFlash Tool.
and, referring back to our above questions re the possibility of getting TWRP onto the phones, a developer friend of mine writes me this:
>try to flash TWRP:
>Download following files from this link:
>https://mega.nz/#F!qZIgnJRK!5apBfYo1je0ytg-wmA6JMQ
>- Odin3 v3.12.3 (Complete folder)
>- twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>1. Start your Phone into download mode
>2. Start Odin (Odin3 v3.12.3\Odin3.exe)
>3. Click on Options and unmark Auto Reboot
>4. Click AP and select twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>5. Press Start and wait until finished (Reset or OK!)
>6. Restart your phone immediatly to recovery mode
>7. In TWRP Recovery click on mount
>8. Set the checkbox checked at system (that system is mounted)
>9. go back and click on advanced
>10. Open file manager
>11. navigate to system/build.prop and click on build.prop
>12. Click on chmod
>13. type: 0644 and hit the accept button on screen or at the virtual
>keyboard on your phone
>14. restart your phone
i haven't tried this, but am wondering whether it might seem "reasonably possible" when reading through it.
thanks
ckth
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
tommo1982 said:
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
Click to expand...
Click to collapse
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
I had issues with adds being displayed at home screen and I was not able to close them. I had to use NetGuard to find that FOTA talks to 'adsup' and it is a known malware provider. I learned that some of the system apps try to talk with Alibaba servers and AdOppo (whatever it's called). Kaspersky might not be wrong, actually.
I'm trying to download stock firmware, but I don't know the file name. The website with it is locked, so unless I know exactly what I need, I cannot download it.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
phonedriller said:
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
Click to expand...
Click to collapse
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
Ps use root + apps2sd or titaniumbackup to stop/disable the bad apps and replace them with playS app,not possible on all apps of course
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
tommo1982 said:
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
Click to expand...
Click to collapse
Flashing is super easy use spflashtools or. Odin compiling a Rom is not , were you able to get the original firmware? You will need the original firware to get the boot and partition info from what i read so far
Unfortunately not. I will ask at the shop where I bought it how to contact tech. It should be freely available. I don't understand why Qilive restricted access to firmware.
I'll post when I learn anything.
Well, you can download the firmware if you know the file name. The bad news is, it seems the stock firmware has malware preinstalled. If there is anyone who could help confirm it. I have the ROM, and I can upload it to Google Drive if needed.
Hi all,
I'm coming back to a question lingering since the very first post here and mentioned again in post #9:
Is there a successful way to install TWRP on this Qilive model?
Re this topic:
- has anybody tried/has anybody been successful with the procedure described in post #9?
and
- has anybody seen the following TWRP builders' version (do an in-page search on Q8S55IN4G2)
https://twrpbuilder.github.io/fr/downloads/twrp/
with the download belonging to it
https://androidfilehost.com/?fid=890129502657591798
???
any successful installations to report???
Wouldn't THAT be great!!??
thanks
xdack
Hi All,
With the recent launch of LineageOS 18.1 I decided to take the plunge and get it installed on my fully stock Videotron/Freedom H915. Since I had to smash together info from a half dozen other threads, I figured I'd gather it all together here for folks with a Canadian phone trying to make this work.
Since I knew absolutely nothing coming into this, I'm going to go a little more detailed on this write-up. If you've been flashing ROMs since the old days of Cyanogenmod you can probably skim half of this.
Disclaimer : I'm not responsible for any bricked phones or other negative outcomes. This is what worked for me, but I'm far from being an expert. If you continue past this point you agree to take your time, do your reading, be responsible for your own device/actions and not hold me or the forum accountable for anything that might go wrong. You've been warned.
IMPORTANT NOTE #1
If you've picked up an H915 on ebay and you are intending to use it on a network other than the one it's SIM locked on, make sure you do the whole SIM unlock process on the stock ROM either before you get started at all, or once you've reverted to the vulnerable stock ROM after Step 1 below.
I actually use Telus as my provider and I wasted a bunch of time trying to figure out why I couldn't get signal because only the stock ROM will prompt you for a SIM Unlock code. Lineage will just sit there dumbly and not allow you to enable data.
Once you've unlocked the SIM it will stay unlocked from that point forward, just make sure to unlock it and verify your SIM is working with LTE on the stock ROM before you get started.
IMPORTANT NOTE #2
Use LGUP's "DUMP" feature to take a backup of ALL partitions on your phone before you start. If you're reading this thinking "I just bought this phone off ebay, there's nothing on it I care about", take the backup anyway. You never know when you might need a copy of the modem partitions or other things from your phone's original build. It came in super handy for me in troubleshooting the process. So go do a backup!
Current Issues:
If signal is too weak to connect to a tower (or non-existent), the OS tends to crash with a modem error. Still trying to figure this one out.
I think I can get this working without first jumping to US996 but haven't had a chance to verify that. If I do I'll update the thread.
Download Prerequisites
Links working as of 2021-06-29
LGUP with patch
Link
Working adb/fastboot environment
Instructions
Download
Fastboot Drivers
Link
Universal ADB Driver
Link
Videotron/Freedom H915 Android 7 (Nougat) version E - H91510e_00_VTR_CA_OP_1205.kdz
Link
USA General US996 Android 7 (Nougat) version F - US99610f_00_1205.kdz
Link
APK for Terminal Emulator
Link or Alternate Link
LG V20 Root Package Original (v4?)
Link
Old TWRP for Root Package
Link
Videotron/Freedom H915 Modem Partition Image
Link
Lineage Install Zip for H910 (grab the latest, I'm using lineage-18.1-20210506-nightly-h910-signed.zip which is already out of date)
Link
MindTheGapps
Link
(Optional, for rooting) Magisk
Link
Different Boot Modes
For those not familiar with these phones, there are three different "modes" the phone can boot into. Here's a quick reference on how to boot into each one.
Download Mode
This mode is used for pushing KDZ files or individual partition backups using LGUP
Turn Off Phone
Hold the Up-Volume Button
Insert USB-C Cable with other end already plugged into PC
Bootloader (aka Fastboot) Mode
The H915 doesn't come with this mode by default. If you try it, you'll just get battery charging. We'll be temporarily converting the phone to a US996 in order to use the DirtySanta exploit to replace the bootloader partition with a leaked Engineering aboot.
This mode is used with the fastboot tool to load the TWRP utility into the Recovery partition.
Turn Off Phone
Hold the Down-Volume Button
Insert USB-C Cable with other end already plugged into PC
Recovery Mode
The recovery mode on a stock phone is used to perform a factory reset. We will be using the Factory Reset a couple times with the stock ROMs, then replacing the contents of the recovery partition with the TWRP tool that allows us to format partitions, load partition images, and sideload apps and LineageOS itself.
Turn Off Phone
Hold the Down-Volume Button
Press and hold Power-On (rear fingerprint sensor/button). When LG Logo appears, release power button for 1 second then press and hold again
When "Factory Data Reset" appears, release all buttons
Press Volume Down to highlight "Yes" then press power button to select the option
Repeat for the confirmation
Note about flashing KDZ files using LGUP
You can flash KDZ files onto the phone using LGUP from two places - either with the phone in "Download Mode", or with the phone booted into the OS with the USB Options set to "File Transfer" and USB Debugging turned on.
The difference between these two is when it performs the OS compatibility check.
In Download Mode it's the code of the Download Mode partition that does the check. In the OS, it's the OS that does the check before booting to Download Mode and bypassing Download Mode's check.
Why is this important? Because when converting from one phone to another (Say, an H915 to a US996 like we do below), you initially can't flash the KDZ using LGUP's "Upgrade" function. You can only use "Partition DL" to replace the contents of partitions with the contents of the KDZ. This kind of works, but ends up with a phone that will sometimes identify as a H915 (in Download Mode) but sometimes identify as a US996 (in the OS). To clean it up, once you've done the Partition DL method, you can do it again from the OS and use the Upgrade method to get a really clean install.
It works going back the other way as well when you want to return to stock.
If this doesn't make sense, don't worry. You don't need to fully understand it to follow the instructions below, I just found it to be interesting info that didn't seem to appear in other threads.
Process Overview
Revert the phone to an old/vulnerable stock Nougat ROM for Videotron/Freedom Mobile
Enable Dev Options
Dump contents of US996 KDZ partitions over top of existing partitions
Cleanup by re-flashing US996 KDZ partitions over top of existing partitions
Transfer files to the SDCard and install Terminal Emulator
Unlock the Bootloader using the DirtySanta exploit
Boot to old TWRP and install new TWRP
Boot to new TWRP, install LineageOS, Google Apps, and flash modem partition image
Reboot to LineageOS
Actual Process
1 - Revert the phone to an old/vulnerable stock Nougat ROM for Videotron/Freedom Mobile
We need to be on Nougat for this to work, so if you're on Oreo you have to downgrade to Nougat before we begin. I chose a Nougat ROM for the H915 that's vulnerable to the DirtySanta exploit because I know it works and because I'm hoping in the future to be able to skip converting the phone to a US996 if possible.
Boot phone into Download Mode
Launch LGUP with Patch
Select "Upgrade" radio button
Select bin file : H91510e_00_VTR_CA_OP_1205.kdz
Click Start
When finished phone will reboot
1.5 - Do this if Step 1 Failed... Otherwise continue to Step 2
Depending on what's loaded on your phone when you start, it might complain about doing Step 1. This should allow us to bypass the issue and allow Step 1 to work. You can use this step if you've already converted the phone to another model as long as it's not bricked.
Boot phone into download mode
Launch LGIP with Patch
Select "PartitionDL" radio button
Select bin file : H91510e_00_VTR_CA_OP_1205.kdz
Click Start
Click the "Select All" partitions checkbox and click OK. When done it will reboot.
If it hangs or loops on reboot, boot into "Recovery Mode" (which at this point will Factory Reset the OS)
The phone boots into the OS
Quickly go through setup wizard. Skip as many things as possible.
Go Settings - General - About Phone - Software Info - Make sure it identifies as H91510e
Change the USB Option mode to "File Transfer"
Then repeat Step 1, but from inside the OS instead of in Download Mode
2 - Enable Dev Options and File Transfer Mode
We need these enabled after every time we flash the OS so that our LGUP and adb commands will work. You'll get used to doing these steps a bunch.
Quickly go through setup wizard. Skip as many things as possible.
Unplug USB-C cable
Swipe down from the top and change from USB Charging mode to File Transfer mode
Settings - General - About Phone - Software Info
Tap on Build Number many times until it unlocks Developer Mode
Go back 2 menus and enter the new "Developer Options" menus
Make sure "Enable OEM Unlock" is enabled
Enable "USB Debugging" (will be greyed out if USB-C cable is still attached)
Go back to main screen
Plug USB-C cable back in.
A pop-up will appear asking to Allow USB Debugging. Check the "Always Allow" box and tap OK
3 - Dump contents of US996 KDZ partitions over top of existing partition
The Videotron/Freedom KDZ has no Bootloader/Fastboot mode. If you try to enter bootloader mode you'll just end up charging the battery. So we have to cross-flash the US996 KDZ to get a phone with a bootloader which we can then replace with the engineering version using the DirtySanta exploit.
Boot phone into download mode
Launch LGUP with Patch
Select "PartitionDL" radio button
Select bin file : US99610f_00_1205.kdz
Click Start
Click the "Select All" partitions checkbox and click OK
When the phone boots back into the OS, repeat all of Step 2.
Note: If it asks for a password on startup, follow the "Boot to Recovery" steps and since
we don't have anything loaded in the recovery partition it will wipe/erase the phone
and remove the password.
4 - Cleanup by re-flashing US996 KDZ partitions over top of existing partitions
As mentioned in the "Note about flashing KDZ files using LGUP" section above, after you use the PartitionDL method you get a kind of dirty phone image that doesn't always identify as its new model. To clean up, we repeat the process in Upgrade Mode, taking advantage of the fact that at least the OS now identifies as US996 even if Download Mode doesn't. After this, Download Mode will also identify as US996.
Starting booted into the OS with a USB-C cable attached (File Transfer mode, USB Debugging on):
Launch LGUP with Patch
Select "Upgrade" radio button
Select bin file : US99610f_00_1205.kdz
Click Start
When the phone boots back into the OS, repeat all of Step 2.
5 - Transfer files to the SDCard and install Terminal Emulator
We will need some files on the SDCard in the phone in order to install them, either inside the OS (in the case of Terminal Emulator), or later on from TWRP. The Terminal Emulator will be used for the DirtySanta exploit so we need to get that installed now.
Make sure the USB Connection is set to Data Transfer mode and copy the following files to the SDCard:
APK for Terminal Emulator
twrp-3.5.1_9-0-us996.img
h915freedommobilemodem.img
Enable installing apps from unknown sources by:
Settings - General - Fingerprints and Security - Unknown sources (turn it On)
Install Terminal Emulator:
Tools - File Manager
Choose "Allow" when prompted
Click the up-arrow next to "Internal Storage"
Choose SD Card
Scroll down and tap on jackpal.androidterm-1.0.70-71-minAPI4.apk
Install
6 - Unlock the Bootloader using the DirtySanta exploit
The US996 KDZ has a bootloader but it's locked. In order to unlock it we need to use the DirtySanta exploit to give us permissions to replace the Bootloader/Fastboot with a leaked engineering version.
Starting booted into the OS with a USB-C cable attached (File Transfer mode, USB Debugging on):
Settings - General - About Phone - Software Info
Verify that Software Version lists as US99610f
Copy the twrp-3.0.2-1-us996.img file into the folder containing the LG V20 Root Package
Open a command prompt window and change to the folder containing the LG V20 Root Package and run "Step1.bat"
It will push multiple files to the phone and apply some patches/exploits.
This proces will take 5 minutes and put you out at an "elsa:/ $" prompt
At this "elsa:/ $" prompt in your command prompt window type the following:
run-as con
chmod 0777 /storage/emulated/0/*
On the phone, launch Terminal Emulator and run the following:
id
Verify that the string which comes back contains the string "context-u:r:untrusted_app".
If not, run Step1.bat again, else continue forward
Enter the follosing command into Terminal Emulator (be very careful to type it properly):
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
If that command came back with an error, close and re-open Terminal Emulator and try again
The command should begin to patch another file. This will take 5 minutes and will return you to the "elsa:/ $" prompt in Terminal Emulator when it has finished
Open another command prompt to the same folder and run "Step2.bat"
This step will download backup copies of the boot and aboot partitions from the phone then boot the phone into bootloader/fastboot mode.
You'll know it worked if the first line at the top of the phone screen appears in red
In the command prompt window, run Step3.bat
It will flash boot1.img and the TWRP Recovery image multiple times then restart the phone
The phone will hang, no matter how long it's left. Wait 5 minutes (at least until the logo re-loads once) then do the following:
Unplug the USB-C cable
Remove the battery from the phone to turn it off
Replace the battery
Boot into Fastboot mode and run the following commands in your command prompt:
fastboot flash boot bootbackup.img
Remove the USB-C cable and battery to turn off the phone. Then replace the battery and enter Recovery Mode
The phone will show a big red exclamation mark saying "Your device is corrupt". This is normal. It will go away after a few seconds then boot into recovery. This error screen is the result of the engineering "aboot" image that was flashed to give us an unlocked bootloader and will always happen on boot.
7 - Boot to old TWRP and install new TWRP
The old version of TWRP recovery will load. Don't ask me why we can't just go straight to new TWRP above, it didn't work well when I tried it.
If it asks for a password to decrypt data, click Cancel
Swipe to allow modifications
Install - Select Storage - MicroSD Card - OK
Install Image - Scroll down and tap the "twrp-3.5.1_9-0-us996.img"
Select the Recovery partition and swipe to confirm flash
Back to main menu
Reboot - Recovery
8 - Boot to new TWRP, install LineageOS, Google Apps, and flash modem partition image
The new version of TWRP will load:
Check the "Never show this screen during boot again" box
Swipe to allow modifications
Wipe - Format Data - type "yes" to continue
This is likely to fail the first time. Repeat it to properly format the data partition.
Go back to Main Menu - Wipe - Advanced Wipe - Select "Dalvik / ART Cache", "System", and "Cache"
Swipe to wipe
Back to main menu
Advanced - ADB Sideload
Plug in USB-C cable
Swipe to start sideload
In command prompt window on PC type the following:
adb sideload lineage-18.1-20210506-nightly-h910-signed.zip
When complete tap "back" and "ADB Sideload" and swipe again to apply another file:
adb sideload MindTheGapps-11.0.0-arm64-20210412_124247.zip
If you want to root the phone (completely optional, not necessary for this process), now is the time to do it. Tap "back" and "ADB Sideload" and swipe again to apply another file:
adb sideload Magisk-v23.zip
Go back to main menu - Install - Install Image - tap the h915freedommobilemodem.img file
Select the Modem partition and swipe to confirm flash
Remove USB-C cable
9. Reboot to LineageOS
Go back to main menu - Reboot - System - Swipe to reboot
References where I got the info to make this tutorial
Official Lineage 18.1 for LG V20 Release Thread
LineageOS Wiki for H910
DirtySanta Bootloader Unlock and Root Guide (Original)
H910 Rooting Thread (Cross-flash H915 then DirtySanta to US996)
H915 Root, TWRP using DirtySanta [WorkingSignals]
Noob Friendly Root TWRP using DirtySanta
General info about Modem Hardware, Firmware, Radio Interface Layer
[Reserved]
thank you so much. i need it
Great job for writing a complete how-to guide!
Thank You, You saved my old V20 H915
hi have you been able to find a better modem?
btw i'm not able to decrypt under twrp, can you?
Just want to confirm, it's only guide wich works for me. But I have issues with modem:
1. When I tried to change mode of modem, "prefered network type", phone stayed in the loop of the kernel panic "modem crash"
2. It were difficult to revert changes back. Finally, safe mode (in order to get it, you need to press volume up and volume down in the same time, during LinageOS booting process) helped me - when I disabled airplan mode, I had 2-10 seconds until next kernel panic. And in ~10 attempts, I were able to finally switch modem's mode to GSM/WDCMA/LTE
3. I used this phone 3 days, and once the kernel panic (because of modem) happened again
Any ideas what to do with modem? Also, the picture "Your phone is corrupt" is not fan Any ideas how to change it?
I did my best to follow all the instructions but after step 7's reboot I just get blocks full of static. I can tell it's trying to do fresh install setup though from what's peeking through the blocks.
Riot54 said:
I did my best to follow all the instructions but after step 7's reboot I just get blocks full of static. I can tell it's trying to do fresh install setup though from what's peeking through the blocks.
Click to expand...
Click to collapse
This is normal. Flash a kernel that's patched for dirty santa OR, cover the proximity sensor on boot and keep it covered until boot is complete.
That worked, thanks.
After multiple attempts going back and forth with step 6, I finally did it! I might switch to Lighthouse or Arros but I wouldn't have gotten this far without your guide.