Related
After seeing SO many frustrated people asking how to do this and never really getting a good answer, i decided to make a useful and easy guide.
Things you need
ADB drivers installed and working
Lenovo usb driver
MTK driver
(Windows will most likely install Lenovo and MTK drivers by itself, if not, search google for ''MTK Drivers'' and Lenovo ''USB drivers'', download and install.
Go To Needrom and download both AP and CU official roms
Same place find a TWRP recovery under one of the X2 roms
SP Flash tool (again, Google it) download and install
If any of these things make you think *Whaaat?* then do some more reading, before continuing!
And on with it!
Attention
Save everything you have on your phone you dont what to have deleted, because it will disappear!
Extract both of the Roms you downloaded previously, and for convenience put them side-by-side on your desktop.
Make sure your phone is adaquetly charged everything above ~60%
Turn your phone off and DONT choose ''fast boot up''
Make sure the phone is not plugged in the computer just yet
Open up SP Flashtool
At the top, press options -> option -> download, check both boxes.
Close the option window again
Leave the ''download agent'' be! It should look like this C:\where you installed\SP_Flash_Tool_v5.1524.00.000\MTK_AllInOne_DA.bin
Now press the button that says ''scatter loading'' And navigate to your desktop where we extracted the ROMS earlier and into the AP ROM folder from there choose ''Target_bin'' and then ''MT6595_Android_scatter.txt''
Example of How it should look like:
C:\Users\Yourname\Desktop\X2-AP_ROW_S130_150412\target_bin\MT6595_Android_scatter.txt
Critical!Make sure the next drop down menu says ''Firmware Upgrade'' if you choose ''Format all + download'' you lose you IMEI and MAC Address, if that happens prepare yourself for looong nights of google'ng :laugh:
Now we're ready to flash!
Press the big Download button with the green arrow and plug your (turned off) phone into you PC (IN THAT SPECIFIC ORDER, YES!), with some luck and driver cooperation it all works
SP flashtool should now begin to burn the new ROM to your phone, and it will take awhile so be patient.
if nothings happens at all make sure your phone was completely turned off without choosing ''Fast Bootup'' and that you installed your drivers correctly.
When The Flashing is done SP flashtool will display a ''Download OK'' or similar
After that just close all SP Flashtool windows completely and unplug your phone
Boot it up to check that its working, if not you did something wrong, try again.
Congratulations! Now you hopefully have a ROW ROM on your your phone!
Unfortunately Your Radio dosen't work, that's because the Chinese phones have a different Modem then the ROW versions.
So lets fix that!:good:
Open up SP Flashtool again
make sure the boxes in options -> option is still checked!
Press the scatter loading button again
but this time navigate to to place where you downloaded and extracted your TWRP recovery folder.
In this folder there is also Scatter loading file, choose that
notice that the only thing checked now is the recovery box
Again make sure the drop down menu says ''Firmware upgrade''"!
Now same procedure as last time, with turned off phone, press the download button and connect phone
SP Flashtool will flash the Recovery files and ultimately say ''Download OK''
Close the window and unlug phone.
Now press the power button and both volume buttons at once, when the phones vibrates and/or when the lenovo logo shows release the power button but not the volume buttons
when the recovery screen appears release at will :silly:
Now plug in your phone and navigate to your phones internal storage then to ''Download'' folder
Now from the CU Version ROM you previously downloaded navigate to:
\modemdb\mt6595k95_hspa_lwg_cu
the two files called ''catcher_filter_1_lwg_n'' and ''modem_1_lwg_n'' are our modem files.
Now move these two files to the ''download'' folder in your phones internal storage.
When done unplug the phone again and continue from TWRP
Mount -> ''Check all'' -> ''press back button''
''Advanced'' -> ''File manager'' -> sdcard -> Download -> ''click on one of the files you put there'' -> ''Move'' -> system -> etc -> firmware -> ''select'' -> ''swipe to confirm''
Now do that for the last file to, now you dont have to navigate to the ''firmware'' folder as when you press move on the next file it should be there already, so just press select.
now go back to the file manger and navigate to the ''firmware'' folder find both files you put there and select them then press ''CHMOD 755'' this tells ROOT that you have permissions to Read and Write them.
After that go all the way back and press Reboot -> system,
The recovery will then ask if you want to ROOT it, DONT Root IT! if you do the phone wont Boot!
Wait for the start up and enjoy your working phone!
If the phone tells you there is a update for it, dont install it the conventional way, as TWRP can't install the updates that way.
and if you flash Stock recovery and then update, your phone will update just fine but you'll have to move the modem files again, since the update checks the phone and sees something is wrong (the CU modem files dosen't match the checksum)
and will overwrite our CU modem files.
There's probably a lot of typos in this, bear with me, its late at night.
Disclaimer: If you dont know what your'e doing, then dont do it...
Made by Mikkel jacobsen
This is for the X2Pt5?
Thanks!
Very useful post.I've had a X2 with CU older version modified from Needrom but wasn't satisfied.
This one seems allright.
Thanks.
L.e. Still i have a problem with the radio thing.
In fact you make a mistake. Instead of ''Firmware upgrade''you must select ''Download only'' on flash tool at radio fix otherwise it will brick the phone.
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).
he everyone! i use minix neo u1 streamer at one month ,today i try to do F.O.T.A update and i get "unzip error" message,
now i try to do all of this thing:
clear the cache
delete files .. ( i have enough space)..
so ,someone have idea what i can do with that??
thanks advance!
Up ..
Someone plz
shlomi770 said:
he everyone! i use minix neo u1 streamer at one month ,today i try to do F.O.T.A update and i get "unzip error" message,
now i try to do all of this thing:
clear the cache
delete files .. ( i have enough space)..
so ,someone have idea what i can do with that??
thanks advance!
Click to expand...
Click to collapse
Here the guides in MINIX forum :
1.) Download the firmware package (.rar)
For example, FW005 full system image with PC upgrade tool:
http://www.minixforum.com/downloads/download.php?file=U1_FW010.rar
MD5 checksum: 0055D63C0EAFBF62DB5830E30E277ECB
2.) Verify the MD5 checksum of the downloaded package matches with the checksum we provided,
free tool: http://www.winmd5.com/download/winmd5free.zip
verified.jpg
3.) Extract the package, you will get the firmware image (.img) & the burning tool
4.) Install the new USB burning tool which is already included in the package (choose English at the beginning, if necessary)
install1.jpg
Choose "Install anyway" when system prompts for driver installation
install2.jpg
4a.) Launch the USB burning tool
tool1.jpg
5.) Connect the Micro USB cable supplied with the box between the OTG port of the box and your computer
(Windows based);
6.) On U1, power up the device from OFF state by pressing and holding the power button for 6 seconds ,
no other button is necessary to get into flashing (recovery) mode.
7.) Upon successful connection the "Connect success" message will be displayed inside the application
8.) Load the firmware image by selecting "File -> Import image"
9.) After loading, the 1st and 2nd box of "Configuration", "Erase flash" (Normal erase) and "Erase bootloader", should be checked by default.
If you want the machine to restart immediately after flashing, check the "Reset after success" option as well.
Then, click "Start" to start flashing
10.) The upgrade process will take approximately 2-3 minutes, the last 5-10% takes longer time to complete,
and you MUST make sure the power can NOT be disconnected during the upgrade (of course also the OTG cable) or your box could become a brick
11.) Upon successful upgrade, the application will display the message "Burning successfully"
then it's safe to unplug the power (and also the OTG! otherwise it will start to burn again after repower on if the USB burning tool is still running )
and connect your hub back to the TV for 1st start (which is also very important and takes some minutes);
So about 1st start:
It's very important that you DO NOT cut the power off from the hub during the 1st start,
since preloaded apps. will be installed in the background, if you power it off in the middle of the installation, some preloaded apps. might be missing.
NOTE: Always use the "Normal erase" option
MINIX - Ken, Jan 5, 2016 #1
Firmware and roms för Minix NEO U1
Hello...
Minixforum.com is unfortunately down. I am looking for two files
1) the latest firmwares for minix neo u1
2) the patch for the AndroidTV version according to below. First file can still be downloaded but I cant find the patch.
This is from the minixforum cached thread cc.bingj.com/cache.aspx?q=minix+u1+androidtv+custom+rom&d=50598 51169956035&mkt=sv-SE&setlang=sv-SE&w=omfsBxEJtQX89AU0VSNqj1xq24OTDmNC
Steps:
- Using the USB Burning tool, install this image: 5.1.1 Firmware V0.0.7 Android TV ext for AM2
mega.nz/#!uIwhhaTS!s37K6nZjjpi2XoAdk21rP4hGkzWDj80Kt4JQBgH A3Oo
- Boot to TWRP and create a backup *
- Power off U1
- Download my patch - mega.nz/#!ZDRSRJJC!qANz9bP6LEzV4_qJBjP5EITWE4JM7mMPX_90C_t Inwg
- Place the zip file on the root of your SD card or USB stick (DO NOT EXTRACT)
- Boot to TWRP *
- Select install
- Change storage to SD or USB
- Select U1_Patch_v3
- Install
- Reboot
Please help!
ask minix support on facebook to provide you those files
Request to Thread Mods
May I have this thread moved to the guides section for this device? Thanks!
UPDATE UPDATE UPDATE
I have made a flashable stock recovery! Select AP in Odin and load this file!
INTRODUCTION
This guide is similar to the previous root instructions posted earlier for this device, only this guide does not require debloating or blocking packages.
DISCLAIMER
This method is provided as is, without any form of insurance or responsibility if your phone grows legs and hops off a balcony. Proceed at your own risk!
PREPARATION
You will need the following:
- Samsung Galaxy On5 (SM-S550TL)
- 50% or more battery
- Kingroot version 5.0.5 (Linked at bottom)
- Permissive Boot.tar (Find it here )
- Stock ROM (Find it Here )
- Odin (Latest Version)
- Patience and a cup of coffee
PART ONE: ODIN A
You do not necessarily have to follow this first step, unless you have already been toying around with your On5. Completely power off your device. Now press and hold the [VOL DOWN] [HOME] and [POWER] keys until the warning screen for Odin mode appears. Press [VOL UP] to enter Odin Mode.
With Odin installed and running, confirm that your device has been added. Now load the file named ALL_TFN_S550TLUDU1APG1_S550TLTFN1APG1_CL8482018_QB10267860_REV00_user_low_ship.tar.md5.
Press start and wait for the PASS Signal. WARNING! YOU WILL LOSE ALL PERSONAL DATA AND FILES ON THIS DEVICE!
PART TWO: PHONE PREP
When the phone has booted, proceed through the setup while looking for Google or KNOX popups. Decline any security prompts from Google and at the end of the setup, do not install My KNOX.
Go to your settings from the launcher and select the 'About Phone' option. Look for the field labeled 'Build Number' and tap it until it says 'You are now a developer!'
Go back and you will find the development settings. Enable USB Debugging and Unlock OEM settings.
Now go to Lockscreen and Security and allow unknown sources. Power off your device and go back into Odin mode.
PART THREE: ODIN B
From the Odin window click AP and load the file boot.tar and click start. your device will flash and reboot. Your SE Linux is now set to permissive.
PART FOUR: FINALE
Now install the kingroot 5.0.5 app (kr505.apk) and run it. When the root process starts, do not touch your device unless it freezes, in which case you will pull your battery and retry. If you have adb, and would like to help me make this better, run logcat on the device while it roots. RUN LOGCAT BEFORE YOU BEGIN THE ROOT PROCESS! With luck you should be rooted. No debloating required. If Kingroot asks to disable KNOX, tell it yes.
Very informational we need guides like this more often
Error 404 for boot.tar link
Dre009 said:
Error 404 for boot.tar link
Click to expand...
Click to collapse
I have fixed the link. Google is starting to bug me. I put it on MEGA this time. Enjoy!
HitByAZinger said:
Request to Thread Mods
May I have this thread moved to the guides section for this device? Thanks!
UPDATE UPDATE UPDATE
I have made a flashable stock recovery! Select AP in Odin and load this file!
INTRODUCTION
This guide is similar to the previous root instructions posted earlier for this device, only this guide does not require debloating or blocking packages.
DISCLAIMER
This method is provided as is, without any form of insurance or responsibility if your phone grows legs and hops off a balcony. Proceed at your own risk!
PREPARATION
You will need the following:
- Samsung Galaxy On5 (SM-S550TL)
- 50% or more battery
- Kingroot version 5.0.5 (Linked at bottom)
- Permissive Boot.tar (Find it here )
- Stock ROM (Find it Here )
- Odin (Latest Version)
- Patience and a cup of coffee
PART ONE: ODIN A
You do not necessarily have to follow this first step, unless you have already been toying around with your On5. Completely power off your device. Now press and hold the [VOL DOWN] [HOME] and [POWER] keys until the warning screen for Odin mode appears. Press [VOL UP] to enter Odin Mode.
With Odin installed and running, confirm that your device has been added. Now load the file named ALL_TFN_S550TLUDU1APG1_S550TLTFN1APG1_CL8482018_QB10267860_REV00_user_low_ship.tar.md5.
Press start and wait for the PASS Signal. WARNING! YOU WILL LOSE ALL PERSONAL DATA AND FILES ON THIS DEVICE!
PART TWO: PHONE PREP
When the phone has booted, proceed through the setup while looking for Google or KNOX popups. Decline any security prompts from Google and at the end of the setup, do not install My KNOX.
Go to your settings from the launcher and select the 'About Phone' option. Look for the field labeled 'Build Number' and tap it until it says 'You are now a developer!'
Go back and you will find the development settings. Enable USB Debugging and Unlock OEM settings.
Now go to Lockscreen and Security and allow unknown sources. Power off your device and go back into Odin mode.
PART THREE: ODIN B
From the Odin window click AP and load the file boot.tar and click start. your device will flash and reboot. Your SE Linux is now set to permissive.
PART FOUR: FINALE
Now install the kingroot 5.0.5 app (kr505.apk) and run it. When the root process starts, do not touch your device unless it freezes, in which case you will pull your battery and retry. If you have adb, and would like to help me make this better, run logcat on the device while it roots. RUN LOGCAT BEFORE YOU BEGIN THE ROOT PROCESS! With luck you should be rooted. No debloating required. If Kingroot asks to disable KNOX, tell it yes.
Click to expand...
Click to collapse
The AQC4 firmware can be rooted too, if you want to add that to your post.
https://forum.xda-developers.com/showpost.php?p=74524073&postcount=102
Files are in the above linked post.
mcopeland1003` said:
The AQC4 firmware can be rooted too, if you want to add that to your post.
https://forum.xda-developers.com/showpost.php?p=74524073&postcount=102
Files are in the above linked post.
Click to expand...
Click to collapse
I can't figure out how to root the SM-G550T1 on AQC4. SELinux is permissive, but KingRoot just refuses to work. Did I trip KNOX for nothing?
Freezed at 17%. anyone has any luck?
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.