This tutorial is a english version of thread original: http://www.htcmania.com/showthread.php?t=1144550
Hello everyone, today I bring how to enable OTG to our Honor 5x by default it is disabled.
To do this, we must have unlocked the bootloader and root access
To start, we have download the kernel that I modified with OTG enabled and adb tools to install it:
Adb: https://mega.nz/#!xB9BECKL!3yY957kBAHgUgA1RgBcWxoFilrGXZMLAqJ2upglLxdM
Kernel con OTG:
---------->Lollipop (si no te funciona el wifi en el anterior usa este)
---------->Marshmallow (si no te funciona el wifi en el anterior usa este)
After downloading the above two files, we will install the kernel with the following steps (must have the USB debugging enabled):
Unzip the file adb.rar and put boot-kiwi-otg.img in the extracted folder
Get into the extracted folder, connect your phone to your PC and open a terminal on it (SHIFT + right mouse button and select Open terminal here)
In the terminal write "adb reboot bootloader" to reboot in fastboot mode
After restarting, we write "fastboot flash boot boot-kiwi-otg.img" to install the kernel
Once installed, we write "fastboot reboot" ro reboot the phone
After restarting, we have the kernel that supports OTG but we have to activate it in the build.prop because otherwise we will only detect mouses, keyboards but not USB flash drives.
To do this, with our preferred file browser, we are going to /system and open the file build.prop with the text editor and look for the line "ro.config.support_otgstorage=false", change false for true, save it, reboot and you will be able to use the OTG.
Tested in KIW-L21/L22
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks
juanro49 said:
This tutorial is a english version of thread original: http://www.htcmania.com/showthread.php?t=1144550
Hello everyone, today I bring how to enable OTG to our Honor 5x by default it is disabled.
Thanks
Click to expand...
Click to collapse
This kernel is for L21 ... does it work on the L24 ?
also my bulid.prop on the L24 doesn't include the line "ro.config.support_otgstorage=false"
clsA said:
This kernel is for L21 ... does it work on the L24 ?
also my bulid.prop on the L24 doesn't include the line "ro.config.support_otgstorage=false"
Click to expand...
Click to collapse
You can try adding the line and then boot the kernel without installing it with the command "fastboot boot boot-kiwi-otg.img"
Enviado desde mi honor 5x mediante Tapatalk
juanro49 said:
You can try adding the line and then boot the kernel without installing it with the command "fastboot boot boot-kiwi-otg.img"
Enviado desde mi honor 5x mediante Tapatalk
Click to expand...
Click to collapse
Thanks ... and Thank you for posting all your guides
I would like to see you work on the L24 as well as the L21
thnx for this awesome work its really work for me..on L22.....but my wifi does'nt work.....pls help
rohitanand1020 said:
thnx for this awesome work its really work for me..on L22
Click to expand...
Click to collapse
Thanks, I add support to L22 in the first post [emoji106]
Enviado desde mi honor 5x mediante Tapatalk
juanro49 said:
This tutorial is a english version of thread original: http://www.htcmania.com/showthread.php?t=1144550
Hello everyone, today I bring how to enable OTG to our Honor 5x by default it is disabled.
To do this, we must have unlocked the bootloader and root access
To start, we have download the kernel that I modified with OTG enabled and adb tools to install it:
Adb: https://mega.nz/#!sIsxmaTb!_cGwWv_wYFqTSJo90ccxZBM5WRKES0iR0XqNop-7kos
Kernel con OTG: https://mega.nz/#!5M1TSaxL!kpFLu9C2dFsY4NRhsBBLi03s9meVoO6v6rAYkeljJr0
After downloading the above two files, we will install the kernel with the following steps (must have the USB debugging enabled):
Unzip the file adb.rar and put boot-kiwi-otg.img in the extracted folder
Get into the extracted folder, connect your phone to your PC and open a terminal on it (SHIFT + right mouse button and select Open terminal here)
In the terminal write "adb reboot bootloader" to reboot in fastboot mode
After restarting, we write "fastboot flash boot boot-kiwi-otg.img" to install the kernel
Once installed, we write "fastboot reboot" ro reboot the phone
After restarting, we have the kernel that supports OTG but we have to activate it in the build.prop because otherwise we will only detect mouses, keyboards but not USB flash drives.
To do this, with our preferred file browser, we are going to /system and open the file build.prop with the text editor and look for the line "ro.config.support_otgstorage=false", change false for true, save it, reboot and you will be able to use the OTG.
Tested in KIW-L21/L22
Thanks
Click to expand...
Click to collapse
What did you enable in the kernel to enable OTG?
thank you fo this great tuto
please put the stock kernel to revert to it in case prob.
i hear that there is problem wih wifi
i have L21 variant
ramzidjoudi said:
thank you fo this great tuto
please put the stock kernel to revert to it in case prob.
i hear that there is problem wih wifi
i have L21 variant
Click to expand...
Click to collapse
You have russian version? for russian version try this kernel and wifi work https://mega.nz/#!hdVmQSIQ!J60bZwe8MAGpZqValkAHUMRqpjs2FCEYPVPFkFfJvAQ
ramzidjoudi said:
thank you fo this great tuto
please put the stock kernel to revert to it in case prob.
i hear that there is problem wih wifi
i have L21 variant
Click to expand...
Click to collapse
juanro49 said:
You have russian version? for russian version try this kernel and wifi work https://mega.nz/#!hdVmQSIQ!J60bZwe8MAGpZqValkAHUMRqpjs2FCEYPVPFkFfJvAQ
Click to expand...
Click to collapse
I have uploaded the L21 Stock Kernel here >> https://www.androidfilehost.com/?w=files&flid=51004
thanks to @deadman96385 for the source files
deadman96385 said:
What did you enable in the kernel to enable OTG?
Click to expand...
Click to collapse
You can view my sourcecode in github: https://github.com/juanro49/android_kernel_huawei_kiwi
To enable OTG, in arch/arm64/boot/dts/qcom in all folders huawei_msm8939_kiw_XXXX_vX change the line "qcom,hsusb-otg-mode = <1>" to "qcom,hsusb-otg-mode = <3>" in file huawei-usb.dtsi
I compile a dt.img with this change a put it in boot.img stock (I use zImage from boot.img stock, because zImage from source wifi don't work for the moment)
juanro49 said:
Thanks, I add support to L22 in the first post [emoji106]
Enviado desde mi honor 5x mediante Tapatalk
Click to expand...
Click to collapse
i appreciate all your hard work......thanks a lot , now wifi is working fine
Will this kernel break wifi or cause issue for L24? Is the kernel for each variant different? Will the modified kernel for L21 and L22 not work for L24?
cyrusalmighty said:
Will this kernel break wifi or cause issue for L24? Is the kernel for each variant different? Will the modified kernel for L21 and L22 not work for L24?
Click to expand...
Click to collapse
You can try if it works in L24, I have L21
Enviado desde mi honor 5x mediante Tapatalk
juanro49 said:
You can try adding the line and then boot the kernel without installing it with the command "fastboot boot boot-kiwi-otg.img"
Enviado desde mi honor 5x mediante Tapatalk
Click to expand...
Click to collapse
@cyrusalmighty
I Tried both kernels they don't boot from fastboot
Code:
C:\fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
GFMDU161******** device
C:\fastboot>adb reboot bootloader
C:\fastboot>fastboot boot C:\fastboot\boot-kiwi-otg.img
downloading 'boot.img'...
OKAY [ 1.667s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.713s
C:\fastboot>fastboot boot D:\Downloads\boot.img
downloading 'boot.img'...
OKAY [ 1.419s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.458s
C:\fastboot>
I also tried to flash both kernels from TWRP and the phone boots straight to the bootloader and the system won't load
hopefully @deadman96385 is working on a kernel for the L24 we can use
clsA said:
@cyrusalmighty
I Tried both kernels they don't boot from fastboot
Code:
C:\fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
GFMDU161******** device
C:\fastboot>adb reboot bootloader
C:\fastboot>fastboot boot C:\fastboot\boot-kiwi-otg.img
downloading 'boot.img'...
OKAY [ 1.667s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.713s
C:\fastboot>fastboot boot D:\Downloads\boot.img
downloading 'boot.img'...
OKAY [ 1.419s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.458s
C:\fastboot>
I also tried to flash both kernels from TWRP and the phone boots straight to the bootloader and the system won't load
hopefully @deadman96385 is working on a kernel for the L24 we can use
Click to expand...
Click to collapse
Yeah it won't work on L24 because the kernel source released does not have L24 DTS files. Currently we are using compiled ones from the ROM itself for cm.
deadman96385 said:
Yeah it won't work on L24 because the kernel source released does not have L24 DTS files. Currently we are using compiled ones from the ROM itself for cm.
Click to expand...
Click to collapse
Thanks, when i have time, I add L24 dts files to source [emoji106] [emoji6]
Enviado desde mi HUAWEI MATE 8 mediante Tapatalk
rohitanand1020 said:
i appreciate all your hard work......thanks a lot , now wifi is working fine
Click to expand...
Click to collapse
How did you solve wifi issue..
nikhildway said:
How did you solve wifi issue..
Click to expand...
Click to collapse
just flash the 2nd kernal...link in the 1st post if wifi does not work
rohitanand1020 said:
just flash this kernal if wifi does not work (https://mega.nz/#!hdVmQSIQ!J60bZwe8M...CEYPVPFkFfJvAQ)
Click to expand...
Click to collapse
Use the fist kernel (second kernel wifi does not work for me)
Enviado desde mi HUAWEI MATE 8 mediante Tapatalk
Related
One Click ROOT+TWRP Recovery for Lollipop Stock Firmware -----------------------------------------------------------------------
I recommend you to use AutoRec For Lollipop 20H from @[B]bender_007[/B]
@ingoljosh includes all version of autorec (D855, D852, D850, LS990 ...) in his post : Flash TWRP With AutoRec
First use OneClic Script ( by @avicohh ) to root your G3
Then install and use AutoRec to install the recovery custom
-----------------------------------------------------------------------Only for D855Only Lollipop (not KitKat)
(16GB/2GB and 32GB/3GB variants)Use only this tuto in case of failure with the previous quoted methodCredit
- @6ril1 for all his advice and convinced me to publish this method here
- @somboons and his post for the LG G2 : [TOOLS] One Click ROOT+TWRP Recovery for Lollipop Stock Firmware
Somboons have modified One Root Script ROOT KitKat / Lollipop firmware that for One Click ROOT+TWRP D802 firmware 30a/30d and I have updated his work for the LG G3 D855
- @avicohh for his One click script
- @thecubed for Bumps!
- @Unjustified Dev for send_command and his New Root Method for LG Devices
- @Chainfire for SuperSU
- G3 tuto on Frandroid
---------------------------------------------Download Link for Lollipop 20H:
Mega LGG3-D855-OneClickRootRecoveryV1.1.zip
Box LGG3-D855-OneClickRootRecoveryV1.1.zip
Dropbox LGG3-D855-OneClickRootRecoveryV1.1.zip
md5 : 33c50a727eecc9402ae1551e818b9615
---------------------------------------------
NEW
Download Link for Lollipop 20P:
Mega LGG3-D855-OneClickRootRecovery-V20P.zip
Dropbox LGG3-D855-OneClickRootRecovery-V20P.zip
md5 : a5f1776215dc6e9792e57efae400dcae
Download Link for Lollipop 20G:
Mega LGG3-D855-OneClickRootRecovery-V20G.zip
Dropbox LGG3-D855-OneClickRootRecovery-V20G.zip
md5 : 624a30b28037a6ed7023ea1f245c2aa8
@6ril1 thank to him for the bump of the 20P and 20G boot :good:
20P and 20G --> If you are not root having applied this tool, copy UPDATE-SuperSU-v2.46.zip on your SDCARD , restart on recovery mode and flash UPDATE-SuperSU-v2.46.zip
For those who used the LGG3-D855-OneClickRootRecoveryV1.1.zip version (for 20H) on the firmware:
- 20P download this file : Kernel fixed by @6ril1 (v20p) --> http://forum.xda-developers.com/showpost.php?p=60770468&postcount=1019
- 20G download this file : Kernel fixed by @6ril1 (v20G) --> http://forum.xda-developers.com/showpost.php?p=60940277&postcount=220
And use Flashify or your custom recovery to install this boot
For more informations see here : http://forum.xda-developers.com/showpost.php?p=60913483&postcount=23
Thank's @black_horse_88
---------------------------------------------
changelog:
http://forum.xda-developers.com/showpost.php?p=59926518&postcount=91
older version:
Mega LGG3-D855-OneClickRootRecovery.zip
Box LGG3-D855-OneClickRootRecovery.zip
Dropbox LGG3-D855-OneClickRootRecovery.zip
md5 : 9f0dfaa556e33457163cb7d57ebc6b1d
(recovery includes in LGG3-D855-OneClickRootRecovery.zip file: TWRP 2.8.6.1 w. Splash Screens/Modem/F2FS)
Backup Data on SDCARD Before doing everything
How to install
1 - Install LG drivers if they are not installed yet.
2 - Make sure you are enable USB Debuging Mode . (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3 - Connect your phone to pc on PTP mode
4 - Extract LGG3-D855-OneClickRootRecovery.zip and double click on the OneClick_ROOT_RECOVERY.bat file, to run the script.
5 - Follow the instructions.
If the phone not recognize, try to switch between MTP and PTP options.
Watch the screen of your smarphone you could see this popup asking you to access to the G3
Of course, accept
Your G3 reboot several times.
If you see this message , reboot the G3 manually into Download mode
6 - Enjoy ROOT+TWRP on Lollipop Firmware
7 - Verify if you are root, you have custom recovery and working Download Mode
Problems and solutions
1 - @somboons describes the manual procedure on his original publication for the LgG2. If you have errors during the script you can try the manual procedure.
somboons said:
Normally If doesn't work for people please checking port that connecting between device and computer or checking LG driver and Re-run script again or use Manual method
What does the automate script do ?
(For people can't use automate script we have to use manually ROOT+TWRP)
Make sure you are enable USB Debuging Mode . See this Method > Enable Debugging Mode
1. Pushing all stuff files
Run file
Command Prompt.bat
Click to expand...
Click to collapse
It will be show command DOS windows
C:\Users\M\Desktop\LGG3-D80230a-OneClickRootRecoveryV1.1>
Click to expand...
Click to collapse
Using command as below to push files to device
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp/ && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp/
adb.exe push aboot.img /data/local/tmp/aboot.img
adb.exe push laf.img /data/local/tmp/laf.img
adb.exe push boot.img /data/local/tmp/boot.img
adb.exe push recovery.img /data/local/tmp/recovery.img
Click to expand...
Click to collapse
2. Reboot to Download mode
3. When enter to Download mode successfully.We need to send command to connect device with computer
Send_Command.exe \\.\COM_PATH
Click to expand...
Click to collapse
COM_PATH . we can find with ports.bat command
Ex.
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>ports.bat
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>reg query HKLM\hardware\devicemap\SERIALCOMM
HKEY_LOCAL_MACHINE\hardware\devicemap\SERIALCOMM
\Device\LGANDNETMDM0 REG_SZ COM3
\Device\LGANDNETDIAG1 REG_SZ COM4
A command that send to device when connecting to computer with Download Mode is
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>Send_Command.exe \\.\COM4
Click to expand...
Click to collapse
4. When we see this prompt
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>Send_Command.exe \\.\COM4
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#
Click to expand...
Click to collapse
Try to use this command to ROOT+TWRP
# sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
Click to expand...
Click to collapse
5. When we see this message
ui_print - Disabling OTA survival
ui_print - Removing old files
ui_print - Placing files
ui_print - Post-installation script
ui_print - Unmounting /system and /data
ui_print - Done !
Please press Ctrl+C, and then type N and ENTER to reboot.
#
Click to expand...
Click to collapse
Try to use LEAVE command to restart device.
#LEAVE
Click to expand...
Click to collapse
6. Enjoy ROOT+TWRP
Click to expand...
Click to collapse
2- If you always have errors or blockings try this other manual method
1 - Apply this tuto : [GUIDE] New Root Method for LG Devices
2 - Then this one : http://forum.xda-developers.com/showpost.php?p=59931455&postcount=104
3 - If your G3 don't boot on system but you can go on Recovery and Download Mode
Your boot is not correctly flash and we have to make it by line of commands
Tuto here : http://forum.xda-developers.com/showpost.php?p=59962266&postcount=127
Good find, good job m8
Thanks for this solution and for the work done.
Hi, I'm currently rooted on stock lollipop but do not have recovery. Can I run this to give me custom recovery? Cheers
Smowza said:
Hi, I'm currently rooted on stock lollipop but do not have recovery. Can I run this to give me custom recovery? Cheers
Click to expand...
Click to collapse
+1
Sent from my LG-D855 using Tapatalk
Smowza said:
Hi, I'm currently rooted on stock lollipop but do not have recovery. Can I run this to give me custom recovery? Cheers
Click to expand...
Click to collapse
Yes you can
it's the twrp 2.8.6.1 version
Nice work.
Thx for the credit.
Huge Improvement!
HI @jac10000,
This is great! Way better than what I have posted.
I assume that this can be repackaged to cater to other LG G3 variants, by simply replacing aboot.img, laf.img, boot.img (users need to have this "bump'd" prior), and recovery.img (need to be "bump'd" prior as well) from those of their respective LG G3 variants, correct?
EDIT: I have promoted your approach in my how-to thread: http://forum.xda-developers.com/showpost.php?p=59897649&postcount=455
topet2k12001 said:
HI @jac10000,
This is great! Way better than what I have posted.
I assume that this can be repackaged to cater to other LG G3 variants, by simply replacing aboot.img, laf.img, boot.img (users need to have this "bump'd" prior), and recovery.img (need to be "bump'd" prior as well) from those of their respective LG G3 variants, correct?
EDIT: I have promoted your approach in my how-to thread: http://forum.xda-developers.com/showpost.php?p=59897649&postcount=455
Click to expand...
Click to collapse
Yes I think it's possible. I don't know the others models of G3 and their specific characteristics for installing custom recovery
jac10000 said:
Yes I think it's possible. I don't know the others models of G3 and their specific characteristics for installing custom recovery
Click to expand...
Click to collapse
HI @jac10000,
Great to hear.
Based on my experience in the Imageprep thread, installation of custom recovery is the same. I'll go ahead and try it out with my D858HK. Will let you know!
Does it make any difference if I have the LG G3 D855 16GB/2GB variant?
Can anyone report back?
@afilbit It work for 16go/2go and 32go/3go variants
Any other host for the file? Mega is blocked in India :/
@alsiladka Ok I do that , just a moment
https://app.box.com/s/qyquibqpnsh6tiq0kf8a7on2kyelvmf7
jac10000 said:
@alsiladka Ok I do that , just a moment
Click to expand...
Click to collapse
What would I need to provide to make this work on a f460k G3 Cat6? I have not found a bump'd boot.img to start with and don't fully understand how to make one myself.
Works great for my LG G3 D855 16GB. Big thanks! [emoji2]
Has anybody tried it on D855TR Turkish version?
BoredKender said:
What would I need to provide to make this work on a f460k G3 Cat6? I have not found a bump'd boot.img to start with and don't fully understand how to make one myself.
Click to expand...
Click to collapse
I do not know the specific obligations for the f460k. But for the D855 I extracted from kitkat Kdz the aboot.img and laf.img and copy them in the tools folder. I think you must use specific recovery Twrp for the f460k. For the bump boot, I have ever install recovery and bump boot by this method and I use here le boot.img includes in it.
Bump stock lp kernel can be made with linux :
http://forum.xda-developers.com/showthread.php?p=59806620
You need unpackbootimg and mkbootimg bin (you can compile them from source).
For the recovery, open bump in linux or the windows tool made for open bump should do the job
Success
Successfully completed process. TWRP installed and Download mode works. LG Stock OS (V20h-EUR-XX) was rooted before using "No Downgrade" method.
Details of my phone -
LGD855
32GB (European Model),
Software Version: V20h-EUR-XX
Thank you OP! You have just opened a new world for me.
Disclaimer: I am not responsible for anything bad that may occur from the use of this zip, but I will take all the credit you can give if it works for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ExtSD Fix
Download latest stable - MD5 checksumDownload latest dev - MD5 checksum
In KitKat, Lollipop and Marshmallow, policies on writing permissions for external SD cards have been changed. This flashable recovery file automatically appends the correct permissions to the file as explained in many tutorials on the web (here or here) or as what many apps do (here).
Advantages
The advantage of this flashable zip over the other methods is that:
you don't need to install any apps,
you can revert by reflashing (not tested for marshmallow),
it does not require you to have root (needs to be confirmed),
[*]you don't need a custom recovery (needs to be confirmed).
Installation
It can insert and remove the permission to write on the external sdcard. To install follow these steps:
Turn off phone,
Boot into recovery,
Backup your system and data partition,
Flash this zip file once,
Reboot phone normally.
To revert the changes, follow the same steps again. This means that flashing it twice will have no effect.
Marshmallow is not supported yet, implementation is in progress.
Note: On Marshmallow, busybox will be installed if not already present. It can also be installed as a standalone app. You should an also add init.d support to your phone if not already available using an app.
How to report a bug
Check if someone else reported that it did/didn't work,
Backup, clean flash, reinstall all apps and then flash ExtSD Fix,
Submit a bug report here with both the original and modified packages.xml and the recovery log file as suggested here.
Changelog
v2.9b - 2016-06-09
Added double flashing revert for MM.
v2.8b - 2016-06-09
Added more logging to:
during flashing: /data/ExtSD_Fix_RW_inst.log
during boot: /data/ExtSD_Fix_RW_initd.log
v2.7b - 2016-06-08
Renamed script,
Changed permissions.
v2.6b - 2016-06-07
Changed permissions.
v2.5b - 2016-06-07
Changed permissions,
Added support for limited backup files.
v2.4b - 2016-06-05
Corrected bugs.
v2.3b - 2016-06-02
Included debug messages.
v2.2b - 2016-06-02
Corrected bugs. "ERROR:2" should be fixed.
V2.1b - 2016-05-19
Implemented solution from here and here.
V1.9b - 2016-05-04
Implemented solution from here. PLEASE TEST AND REPORT.
V1.8b - 2016-02-04
Corrected bug for Marshmallow.
V1.7b - 2016-02-02
Added support for Marshmallow.
V1.6b - 2016-01-27
Added revert on second run.
V1.5b - 2016-01-26
Corrected bug in check for API version.
V1.4b - 2016-01-26
Changed format of backed up filename.
Added check for API version ( 19<= API <= 22 ).
V1.3b - 2016-01-22
Backed up file is renamed with time and date.
V1.2b - 2016-01-21
Moved code into update-binary.
V1.1b - 2016-01-19
Removed testing commands.
V1.0b - 2016-01-18
Initial submission
XDA:DevDB Information
ExtSD Fix, Tool/Utility for all devices (see above for details)
Contributors
rufus.wilson
Version Information
Status: Testing
Current Beta Version: v2.9b
Beta Release Date: 2016-06-09
Created 2016-01-18
Last Updated 2016-06-15
Tested devices and systems
When you have tested it could you report your experience with the device model and the android version you used.
I will summarize here the success and failures.
Success
OnePlus X - CM 12.1
N4 w/TW 6.0.1 MM
sony z3c concept rom(mm)
Samsung Galaxy Express 2 with CM13
Xperia M with CM13
Sony Z3 .570 stock
asus zenfone 2
Asus ZenFone 4 - Stock v7.4.4 (Lollipop) (all opened apps had FC on reboot)
asus zenfone 5 XOSP rom
Sony Xperia Z3 (Sometimes is overwritten)
SM-G910F Rom ALEXNDR COJ3 Deodexed
Samsung galaxy s5 g900f stock marshmallow
z3c with rom slimm 1.5
Galaxy S7 SM-G930FD 6.0.1 Rooted Xposed
Xiaomi Redmi 1S RR 5.6.8 which is a CM13(R28)
Sony Z3 D6653 running on RXSW Marshmallow Edition [3.0.0] [12/04/16] [6.0.1]
LG L90 D415
Redmi 1s using OctOS M ROM
xt907 JBBL- cm13, 01-05-2016
Redmi 2, CM 13.1-20160417-SNAPSHOT
z3 570 rxsw
LG G3 VS985 variant running CM 13 6.0.1 nightlies. Using 777 Kernel & TWRP 3.0.2
z3 dual d6633 running marshmallow 6.0.1 official
Oppo find 7a x9006 on 6.0.1 rooted with twrp 3.0
Failure
LG D855 32 Gb with CM13 2016-05-10 and TWRP 3.0.0.0 recovery
Sony z3 MM
g900f blisspop 6.01
Samsung N7105T, unofficial wilson3q cm 13
Reserved
not work with my device
zenfone 4
here is my recovery log
hiimpig1 said:
not work with my device
zenfone 4
here is my recovery log
Click to expand...
Click to collapse
Thank you for coming back to me.
Do you have CWM recovery or TWRP?
rufus.wilson said:
Thank you for coming back to me.
Do you have CWM recovery or TWRP?
Click to expand...
Click to collapse
im using twrp 2.8.7.0
hiimpig1 said:
im using twrp 2.8.7.0
Click to expand...
Click to collapse
I have uploaded a new version. Could you test that one?
rufus.wilson said:
I have uploaded a new version. Could you test that one?
Click to expand...
Click to collapse
i flashed, after that all my apps got FC
but its worked
I have a proble with titanium backup: no space, but i have more than enough
Is this also working?
Galaxy s5, cm13 (MM)
hiimpig1 said:
i flashed, after that all my apps got FC
but its worked
Click to expand...
Click to collapse
Was a reboot enough to solve the problem?
phoberus said:
I have a proble with titanium backup: no space, but i have more than enough
Is this also working?
Galaxy s5, cm13 (MM)
Click to expand...
Click to collapse
It should be working. You can always go back by copying back the file in a rooted shell command with the system partition mounted:
Code:
cd /system/etc/permissions
cp platform.xml-201*.bak platform.xml
chmod 0644 platform.xml
rufus.wilson said:
It should be working. You can always go back by copying back the file in a rooted shell command with the system partition mounted:
Code:
cd /system/etc/permissions
cp platform.xml-201*.bak platform.xml
Click to expand...
Click to collapse
Hey @rufus.wilson
Flashed v1.3b, but it didn't work. And then I I restored the file with this two commands. After that, almost all the apps crash (FC) when I want to start it and when I can open an app, it hasn't any internet connection.
Can I fix this or must I wipe /system and /data?
(cache and dalvik cache already wiped)
I have noew zero permission, I can't even take a screenshot :/
Galaxy s5 (G900F) => CM13 (MM)
rufus.wilson said:
Was a reboot enough to solve the problem?
Click to expand...
Click to collapse
no its not
phoberus said:
Hey @rufus.wilson
Flashed v1.3b, but it didn't work. And then I I restored the file with this two commands. After that, almost all the apps crash (FC) when I want to start it and when I can open an app, it hasn't any internet connection.
Can I fix this or must I wipe /system and /data?
(cache and dalvik cache already wiped)
I have noew zero permission, I can't even take a screenshot :/
Galaxy s5 (G900F) => CM13 (MM)
Click to expand...
Click to collapse
I edited my answer as I forgot to add a command to change the permissions of the file.
Code:
chmod 0644 /system/etc/permissions/platform.xml
hiimpig1 said:
no its not
Click to expand...
Click to collapse
Can it be a permission problem? Look here.
rufus.wilson said:
I edited my answer as I forgot to add a command to change the permissions of the file.
Code:
chmod 0644 /system/etc/permissions/platform.xml
Click to expand...
Click to collapse
Didn't work for me, but I have a backup :good:
phoberus said:
Didn't work for me, but I have a backup :good:
Click to expand...
Click to collapse
Which version of android do you use?
hiimpig1 said:
no its not
Click to expand...
Click to collapse
Which ROM are you using?
rufus.wilson said:
Which ROM are you using?
Click to expand...
Click to collapse
im using stock rom 7.4.4 from asus
hiimpig1 said:
im using stock rom 7.4.4 from asus
Click to expand...
Click to collapse
Do you still have the FC?
[GUIDE][PORT] TWRP 3.0.X for Mediatek Devices.
Requirements:
1. Windows/Linux/Mac PCs.
2. OFFICIAL CyanogenMod 13 Support
3. DSIXDA Kitchen.
4. Patience.
5. A bit of Computer Knowledge
6. Getting Recovery Partition Size of MTK Chipset (Google It)!
This Method is Universal Cross-Chipset Method means you can port Snapdragon Recoveries even to your MTK. dosen't matter 32bit or 64bit MTK Processor.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to @Dees_Troy for his Nexus Recoveries.
Step 1: Setting Up!
(i) Download your CyanogenMod Recovery from download.cyanogenmod.com.
(ii) Download DsiXDA Kitchen
(iii) If your on WINDOWS download CYGWIN to launch DSIXDA Kitchen.
(iv) Setup Done!
Step 2: Executing!
EXAMPLES YOU CAN USE OTHER RECOVERIES ALSO BUT AS SAME RESOLUTION AS YOUR DEVICE:
IF YOUR ON 480x850, 480x854 download: https://twrp.me/devices/lgnexus4.html latest TWRP 3.x Available!
IF YOUR ON 720x1280, 800x1280 download: https://twrp.me/devices/asusnexus720123g.html latest TWRP 3.x Available!
IF YOUR ON 1080x1920 download: https://twrp.me/devices/motorolanexus6.html latest TWRP 3.x Available!
Once Downloaded!
Download your CM RECOVERY from download.cyanogenmod.org/ Find your device codename and download.
Step 3: Setting Up Kitchen!
Note: In most cases of Commands Windows/Linux/Mac are same in different i will mention.
If Windows:
Code:
(i) Open Cygwin
(ii) cd <user_name>
(iii) cd kitchen
(iv) ./menu
If Linux/Mac
Code:
(i) Open Terminal
(ii) cd <kitchen_source_dir>
(iii) ./menu
Minimize The Kitchen Never Close.
Step 4: Setting up WORKING Directory
(i) Open Kitchen Installed Directory.
(ii) Make a new folder named WORKING_twrp
(iii) Copy your downloaded nexus_twrp.img to WORKING_twrp
(iv) Rename twrp.img to boot.img
Step 5: Unpacking STOCK and PORT
(i) Open DsiXDA kitchen back.
(ii) Type Options in Line:
Code:
0
12
w
press enter
(iii) Type Options in Line: If your following me as above just follow next command.
Code:
a
(iv) Now a new folder will be created in kitcher_dir named boot.img-xxxxxx (instead of xxxx some numbers) paste your downloaded cm recovery.img to boot.img-xxxxxx folder.
(v) Rename cmrecovery.img to boot.img
(vi) Open Kitchen Press Enter to continue.
NOW: BOOT-EXTRACTED = PORT
boot.img-xxxxxxxx = BASE
Copy Replace Files from BASE TO PORT and delete file in PORT:
Code:
COPY AND REPLACE FROM BASE TO PORT:
/zImage
/boot.img-ramdisk/default.prop
/boot.img-ramdisk/fstab.<codename>
/boot.img-ramdisk/uventd.rc
/boot.img-ramdisk/etc/recovery.fstab
/boot.img-ramdisk/etc/twrp.fstab (if exist no prob if it dosen't exist in PORT)
Code:
DELETE FILES FROM PORT:
/boot.img-ramdisk/fstab.<portcodename>
Step 6: Lets Repack!
Open DSIXDA Kitchen Back On!
Type Option in Line:
Code:
If you didn't close kitchen it will be minimized continue this:
[B]Option:[/B]
b
OUTPUT= /kitchen_dir/WORKING_twrp/boot.img This is your TWRP Recovery the OLD one has been replaced with REPACKED ONE
Make Sure You Provide Me PORT GUIDE Credits
I HOPE YOUR ENJOYING MY WORK :good: :laugh:
Q/A:
1. Will this Work on Above Resolution than 1080p?
A. Yes!
2. Is it mandatory to have official CM Support?
A. Yes! Because, CM and OMNI ROMS are only one which can build TWRP and CM is only one which even makes CM13 Recovery.
3. Must CM13 be based on 6.0.1 itself?
A. No, the CM Recovery Can be also on 6.0 but not 5.1 or bellow.
4. Why CM Recovery?
A. As per my knowledge CM Recovery is based on CWM as well as TWRP. so it will be easy to port TWRP for your device.
4. Bootloop?
A. Make sure you followed Step 5 Properly! and clear command line using kitchen (Options in line: 0, 12, p, press enter, press enter) if still bootloop is being faced try a different recovery!
5. Are you sure this will work? It's Not working for Me!.
A. Yes it will I am making UNOFFICIAL TWRP 3.x for my Sprout Devices: http://forum.xda-developers.com/cro.../unofffical-twrp-3-0-2-0-android-one-t3358636
Good job
Gửi từ EVA-AL00 của tôi bằng cách sử dụng Tapatalk
29y6145 said:
Good job
Gửi từ EVA-AL00 của tôi bằng cách sử dụng Tapatalk
Click to expand...
Click to collapse
Thanx
@HostZero
Err, only the sprout devices have official cyanogenmod support. You should probably change the first step to "extract the stock recovery from your device" but great work anyways! Sorry for being such a wuss over PM. My bad.
Sent from my PixelV1 using XDA Labs
MSF Jarvis said:
@HostZero
Err, only the sprout devices have official cyanogenmod support. You should probably change the first step to "extract the stock recovery from your device" but great work anyways! Sorry for being such a wuss over PM. My bad.
Sent from my PixelV1 using XDA Labs
Click to expand...
Click to collapse
No issue, I am found a new and easy way, you don't even need recovery, you can use boot.img too.. i will update Post soon.
HostZero said:
No issue, I am found a new and easy way, you don't even need recovery, you can use boot.img too.. i will update Post soon.
Click to expand...
Click to collapse
Yeah, if I remember correctly that's how stock ROMs replace the custom recoveries on first boot, by taking the boot.img, applying the recovery-from-boot.p patch on it and then flashing it as recovery.
Sent from my PixelV1 using XDA Labs
touch
im port twrp but touch no working
USB storage can't not mount on pc. Please help me to fix
No Joy in Mudville
Can not get the ported TWRP to recognize ANY storage on my device - MTK 6753. Looks very nice but that's about it. Any suggestions?
HostZero said:
No issue, I am found a new and easy way, you don't even need recovery, you can use boot.img too.. i will update Post soon.
Click to expand...
Click to collapse
please update the thread, show us the new way using boot.img
you might want to ...
If the device you are porting FROM has the same chipset and general parameters (e.g. RAM) as the device you are porting TO, try not moving ANYTHING from the ramdisk folder or sub folders. Just replace all the other stuff from the top level folder with what is in your stock recovery. You will probably need to tweak the recovery.fstab file in 'ramdisk\etc' when you are done but that seems to be a workable approach. At least it worked for me. I just removed a half-dozen or so references to things that don't exist on my unmodified device, TWRP stopped having a canary about them not being there, and I was good to go. And YES, I DID confirm that a backup and restore brought back everything I thought it should.
NOW, if we could just get all these Chinese phone makers to more or less agree on mount points and partition naming - yeah, right. Who am I kidding ??
U think this will work on a samaung device that runs on MTK6737T....GALAXY j2 prime?
hi @HostZero
Need solution ,i port 3.1.0-1 from samsung galaxy s8 on cubot dinosaur mt6735 and booted all ok ,backup worked and all worked fine but restore no ,can you tell me what is problem
error mesages is
e:Unable to find file system first (first period)
e:Unable to find file system first (first period)
e:unknown restore method for ''/system''
e:adb restore failed
thenks again
Hi,
I ported twrp to my device ,I used MTK THAI developer tool to port
I used twrp of intex aqua star power
To intex aqua speed HD
everything working fine but
Its not Detecting internal storage
It gives E:unable to mount internal storage,invalid argument
And in file manager option when I enable the mtp ,pc detecting as intex aqua star power .
When I backup boot it backup whole OS , not only boot.
Please help me ,where its gone wrong
Thank you
Does Device Need CM13 Support?
Thank you for this great post.
You wrote that you can use any recovery image that has the same resolution as your device, but then later wrote that you need to use the CM13 recovery image specific to your device. Do I need both?
I want to root a Digiland DL8006 (MTK8127, 1280x800, Android 7.0), but CM13 does not support it. I’m really hoping I don’t need the CM13 recovery file to do this.
Just a query !
JUST A QUERY :
Which image did you use from stock firmware ? (recovery.img or boot.img)
curious because i saw /boot.img-ramdisk/xxxxxxx in OP.
As far i know both recovery & boot image contains ramdisk,so i was
Again recovery.img or boot.img which one should i use from stock rom ?
Thank you very much for this tutorial !
I would like to ask please:
Usually I find in most "rooting tutorial" that 1st stage is unlocking bootloader.
Isn't that required here ?
Thanks,
ranran
ranchu-panchu said:
Thank you very much for this tutorial !
is unlocking bootloader.
Isn't that required here ?
Click to expand...
Click to collapse
Yes it is required, OP must have forgot to write it.
Android Image Kitchen works better than Android Kitchen. Just ported a TWRP, so I am saying this on experience. A few extra steps like editing recovery.fstab and twrp.fstab are required.
Xiaomi Mi Play - Nickname = Lotus twrp
Hi! I have been struggling with getting twrp recovery for Xiaomi Mi Play - Nickname = Lotus but still could not find anywhere. Can I build my own twrp with this guide? and Some links are dead. Please help if you want to!
Since huawei started to mess around with online firmwares that twrp couldn't handle I decided to create my own offline package with updated firmware(s) and i thought why not create a offline package thread with latest firmwares in it.
This case we can always keep ourself up to date (system wise) without having to restore to stock recovery etc.
However this is a "dirty" way of update firmware and it will only update following partitions:
Boot
Cust
Product
System
Vendor
Version
All other partitions will stay intact! Why? Because if we add other partitions there's a HIGH potential of hard brick the device and I mean really high!
But with official packages it updates all partitions!
Yes. And we can't (for now, or never) re create this procedure we'd have to know how the UPDATE.APP is being built and we can't re create a UPDATE.APP for now.
So far only available homebrewed package is 394 created by me.
See post 2 on how to create your own custom offline package!
Downloads:
FRD-L09C432B934
https://mega.nz/#!j0QXjJKa!i5lOMYjO_GusfzCTT6qVAR7LgzVGdpLT4i66FKCrshQ
blackbuffalo said:
Here is Offline fw for L04C567B385 thanks @blackbuffalo
Just tested on my device
https://androidfilehost.com/?fid=961840155545591339
Click to expand...
Click to collapse
Thanks @SnoopHTC
L19-C432B398
https://gofile.me/3wKsh/4wlivV41v
Nortonko said:
so coz the link from SnoopHTC is dead i made my own package for FRD-L19C432B398. Here is the link: https://webshare.cz/file/73v2t363K5/twrp-frd-l19c432b398-zip
Click to expand...
Click to collapse
How to do it yourself package.
In order to create a unofficial update package you'll need
Huaweiupdateextractor (google it)
Simg2img (google it)
This template
https://mega.nz/#!i1Y3Wa5J!VfELb8aRkA5bon_OlIRPNAS_xUAmzMq0I-rVywHbvi4
Now extract all needed partitions
Boot
System
Vendor
Product
from big update file
cust
version
from small update file *this can be found in any of the 2 extra small zips
Open cmd and navigate to the folder where you have to both simg2img and your system files. Now cd into your work directory to convert the images.
Simg2img.exe system.img s.img will give you a converted system image with the name s.img
Convert these following partitions
system
Product
Version
Cust
Vendor
Once completed check the update-script
The
c.img is cust
v.img is vendor
ve.img is version
p.img is product.
b.img is boot
s.img is system
you can change these names to its regular name like system.img for system or make it more confusing if you want [emoji14]
Make sure the partitions are exactly the same!
If you decide you want to change the name of the files from s.img to system.img make sure you do it correct!
Because system.img in updater-script is not the same as System.img in root of zip. If you have a captive letter in root and not in updater-script the zip will fail to flash.
Now simply compress the images into a zip and you're done.
Note: after you flashed your offline zip make sure to patch boot! Else it will reboot to recovery
Note you'll get result
Error: Unknown command []] this is not a issue since we're using stock huawei updater binary.
Sent from my FRD-L09 using Tapatalk
Your awesome work will save a lot :good:
Nice but it should not be in "roms etc" threads? More people will find it.
I get bootloop into eRecovery after flashing. Restored my backup of B392 and now in the phone info i have as build name FRD-L09C432B394, what can't be true, because it wasn't successfully flashed. Anyway local.prop was edited and not restored
WYPIERDAALAAC said:
Nice but it should not be in "roms etc" threads? More people will find it.
Click to expand...
Click to collapse
Because I simply put it here
extpumajl said:
I get bootloop into eRecovery after flashing. Restored my backup of B392 and now in the phone info i have as build name FRD-L09C432B394, what can't be true, because it wasn't successfully flashed. Anyway local.prop was edited and not restored
Click to expand...
Click to collapse
Hmm you might have to patch boot after flash??
PalakMi said:
Your awesome work will save a lot :good:
Click to expand...
Click to collapse
It will save a lot of time yes.
Sent from my FRD-L09 using Tapatalk
extpumajl said:
I get bootloop into eRecovery after flashing. Restored my backup of B392 and now in the phone info i have as build name FRD-L09C432B394, what can't be true, because it wasn't successfully flashed. Anyway local.prop was edited and not restored
Click to expand...
Click to collapse
I have the same problem..
Bootloop into eRecovery, restored a Backup of b389 but build is b394 [emoji28]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gesendet von meinem FRD-L09 mit Tapatalk
LastStandingDroid said:
Hmm you might have to patch boot after flash??
Click to expand...
Click to collapse
What schould i do?
Rommco05 said:
I can't find simg2img version which works on Windows 10. One version shows me only
Using STDIN as input
Using STDOUT as output is that right?
Maybe don't know how use this program
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/general/dev-simg2img-windows-t3156459
This one works just great.
I forgot you might have to use a cmd to convert images will edit post 2
Silencer3007 said:
I have the same problem..
Bootloop into eRecovery, restored a Backup of b389 but build is b394 [emoji28]
View attachment 4250767
Gesendet von meinem FRD-L09 mit Tapatalk
Click to expand...
Click to collapse
Patch boot with either Supersu or magisk.
Did the backup include version? I doubt which is why you'll get B394 in settings.
It doesn't restore the partition which contains the build number info.
extpumajl said:
What schould i do?
Click to expand...
Click to collapse
Patch boot and try again
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
Patch boot and try again
Click to expand...
Click to collapse
Thx. Now is everything fine.
Didn't work for me since the simg2img tool wouldn't let me convert the BOOT.IMG. I was getting a "no magic" message (which I didn't notice at the beginning) and a 0KB BOOT file output. Funny thing I just realized this after trying to unsuccessfully flash the custom update zip.
So after some researching and reading (a couple of hours actually) I managed to flash the L19C432_B398 update by flashing the original extracted SYSTEM, BOOT, and CUST images through Fastboot command. Then by going into TWRT recovery to flash the simg2img converted PRODUCT, VENDOR, and VERSION images through ADB push command to their appropriate dev partitions which are available inside the updater-script. Finally, I did a dalvik/cache wipe and reboot.
So far so good.:fingers-crossed:
*Forgot to mention that my device is a US L14C567 rebranded to L19C432.
Dominikrod said:
Didn't work for me since the simg2img tool wouldn't let me convert the BOOT.IMG. I was getting a "no magic" message (which I didn't notice at the beginning) and a 0KB BOOT file output. Funny thing I just realized this after trying to unsuccessfully flash the custom update zip.
So after some researching and reading (a couple of hours actually) I managed to flash the L19C432_B398 update by flashing the original extracted SYSTEM, BOOT, and CUST images through Fastboot command. Then by going into TWRT recovery to flash the simg2img converted PRODUCT, VENDOR, and VERSION images through ADB push command to their appropriate dev partitions which are available inside the updater-script. Finally, I did a dalvik/cache wipe and reboot.
So far so good.:fingers-crossed:
*Forgot to mention that my device is a US L14C567 rebranded to L19C432.
Click to expand...
Click to collapse
I'm curious but where did it say convert boot?
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
I'm curious but where did it say convert boot?
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
It's all in my head! LOL
I got confused when I saw the part where it talks about the updater-script file naming. When I saw b.img thought that BOOT needed to be converted as well.
Thanks for pointing that out. :good:
Dominikrod said:
It's all in my head! LOL
I got confused when I saw the part where it talks about the updater-script file naming. When I saw b.img thought that BOOT needed to be converted as well.
Thanks for pointing that out. :good:
Click to expand...
Click to collapse
Ah no its just that it has to flash boot as well ?
Sent from my FRD-L09 using Tapatalk
Here is Offline fw for L04C567B385
Just tested on my device
https://androidfilehost.com/?fid=961840155545591339
Dominikrod said:
It's all in my head! LOL
I got confused when I saw the part where it talks about the updater-script file naming. When I saw b.img thought that BOOT needed to be converted as well.
Thanks for pointing that out. :good:
Click to expand...
Click to collapse
No need convert Boot.img, just rename then put it into zip
blackbuffalo said:
Here is Offline fw for L04C567B385
Just tested on my device
https://androidfilehost.com/?fid=961840155545591339
No need convert Boot.img, just rename then put it into zip
Click to expand...
Click to collapse
Great that you contribute ?
Sent from my FRD-L09 using Tapatalk
blackbuffalo said:
Here is Offline fw for L04C567B385
Just tested on my device
https://androidfilehost.com/?fid=961840155545591339
No need convert Boot.img, just rename then put it into zip
Click to expand...
Click to collapse
Bro can you confirm the build number is not NRDm keys ?
venugopalu007 said:
Bro can you confirm the build number is not NRDm keys ?
Click to expand...
Click to collapse
It won't unless he packed the product files which stores the build info
Sent from my FRD-L09 using Tapatalk
venugopalu007 said:
Bro can you confirm the build number is not NRDm keys ?
Click to expand...
Click to collapse
it not imcluded
blackbuffalo said:
it not imcluded
Click to expand...
Click to collapse
Ok,then it shows build number correctly?
*It only works on ROMS with no SafetyNet that has "root debugging" in developer options, ex: LineageOS
**Also refer to post #10 if you would like a flashable version of this method. Credits to @huskydg
Requirements:
download OP8.zip
Stock OxygenOS Build Fingerprint and Model Number
ADB and Fastboot Drivers
*This step is for non-T-Mobile OnePlus 8, if you have a T-Mobile OnePlus 8 (IN2017) skip step 1 and 2.
Step 1: Get OxygenOS Build Fingerprint and Model Number
Be on OxygenOS 11 and Enable Developer Options
Enable USB Debugging and Allow USB Debugging? to ALWAYS
On your PC, go to your ADB folder and type in CMD/Powershell:
Code:
adb shell
On adb shell (OnePlus8:/ $), type and enter
Code:
adb shell
OnePlus8:/ $ getprop ro.build.fingerprint
You would then get your build fingerprint (keep in mind, build fingerprints differ from each Model Number) and store it in Notepad. For Example:
Code:
OnePlus/OnePlus8_EEA/OnePlus8:11/RP1A.201005.001/2012102310:user/release-keys
Find your Model Number in this table and store it in the same Notepad as the build fingerprint: For example, for T-Mobile is IN2017
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*AGAIN this step is for non-T-Mobile OnePlus 8, if you have a T-Mobile OnePlus 8 (IN2017) skip this step because the OP8.zip is already configured for T-Mobile OnePlus 8 (IN2017).
Step 2: Configuring the OP8.zip
Extract the OP8.zip
Open the extracted folder and go to "etc" folder
Edit ih8sn.conf using Notepad
Replace the BUILD_FINGERPRINT with the build fingerprint you did in Step 1 and the PRODUCT_NAME with the Model Number your OnePlus 8 has
Step 3: Installing it on LineageOS or Other
Fresh Install LineageOS and GApps
Go to Settings and Enable Developer Options
Enable USB Debugging and set Allow USB Debugging? to ALWAYS
Enable Rooted Debugging underneath USB Debugging
Now plug in OnePlus 8 to PC and extract OP8.zip if you haven't yet.
Open extracted folder and open CMD/PowerShell from the folder
Now run these commands one by one:
Code:
adb wait-for-device root (Allow Yes to USB Debugging? to ALWAYS)
adb wait-for-device remount
adb wait-for-device push etc/60-ih8sn.sh /system/addon.d/
adb wait-for-device push ih8sn /system/bin/
adb wait-for-device push etc/ih8sn.rc /system/etc/init/
adb wait-for-device push etc/ih8sn.conf /system/etc/
After each and every command is done, reboot device. AND KABOOOOOOM!!! DONE!!!
If SafetyNet didn't pass:
Try changing Model Number in PRODUCT_NAME=
For example: IN2017 -> OnePlus8TMO, IN2013 -> OnePlus8EEA=not sure about this one if its the same model number or not
CREDITS:- Huge thanks to @ihfandicahyo on Twitter for helping me pass it!
- Huge thanks to @_LuK1337_ for ih8sn
RESERVED
RESERVED
I am still trying this on a Motorola One Action "Troika XT2013-2" with latest 19.1 Lineage but it is not working. Double checking every thing. All files look OK, checked for weird markups and linefeed/cariageR but I cant see anything wrong.
When booting it first shows "OS Fingerprint: NA" shortly and then continues to boot. Debugging with root enabled.
Is the string for _SECURITY_PATCH_DATE and _VERSION_RELEASE relevant? What do I enter?
CK0y0TE said:
I am still trying this on a Motorola One Action "Troika XT2013-2" with latest 19.1 Lineage but it is not working. Double checking every thing. All files look OK, checked for weird markups and linefeed/cariageR but I cant see anything wrong.
When booting it first shows "OS Fingerprint: NA" shortly and then continues to boot. Debugging with root enabled.
Is the string for _SECURITY_PATCH_DATE and _VERSION_RELEASE relevant? What do I enter?
Click to expand...
Click to collapse
I have only tested this on 18.1 because no build no 19.1 build yet for OnePlus 8, however, try putting these values BUILD_SECURITY_PATCH_DATE=2021-11-02 and for BUILD_VERSION_RELEASE=11 (if latest firmware is Android 11) or BUILD_VERSION_RELEASE=12 (if latest firmware is Android 12) hope this helps
CK0y0TE said:
I am still trying this on a Motorola One Action "Troika XT2013-2" with latest 19.1 Lineage but it is not working. Double checking every thing. All files look OK, checked for weird markups and linefeed/cariageR but I cant see anything wrong.
When booting it first shows "OS Fingerprint: NA" shortly and then continues to boot. Debugging with root enabled.
Is the string for _SECURITY_PATCH_DATE and _VERSION_RELEASE relevant? What do I enter?
Click to expand...
Click to collapse
Also replace your product name with this, PRODUCT_NAME=XT2013-2
Can this method works with bootloader unlock oxygen os?
[email protected] said:
Can this method works with bootloader unlock oxygen os?
Click to expand...
Click to collapse
If there is toggle that says Root Debugging in Developer Options it might. So far as to what I am aware of, OxygenOS 11 doesn't have it.
thattechguy_69 said:
If there is toggle that says Root Debugging in Developer Options it might. So far as to what I am aware of, OxygenOS 11 doesn't have it.View attachment 5644695
Click to expand...
Click to collapse
With Magisk Root?
I have forked ih8sn repo and make flashable zip for it. You can take a look here:
injectprop
Inject Android system properties
huskydg.github.io
[email protected] said:
With Magisk Root?
Click to expand...
Click to collapse
No this method does not require root. In LineageOS, there is an option in developer settings called "Root Debugging". You can also find this option in some roms, from what I am aware of besides LineageOS that has it is HavocOS. But HavocOS already has safetynet so no need to do this guide.
huskydg said:
I have forked ih8sn repo and make flashable zip for it. You can take a look here:
injectprop
Inject Android system properties
huskydg.github.io
Click to expand...
Click to collapse
Yo this is nice man
thattechguy_69 said:
Yo this is nice man
Click to expand...
Click to collapse
As far as i knew, ih8sn is basically reset props / override read only props
huskydg said:
As far as i knew, ih8sn is basically reset props / override read only props
Click to expand...
Click to collapse
Does this work for any custom recovery or only twrp?
thattechguy_69 said:
Does this work for any custom recovery or only twrp?
Click to expand...
Click to collapse
Any Custom Recovery should work
Thanks for the work,
I tried the injectprop, I used /zFM to update the props ( I also set `inject_props=1`)
I sideload the zip using the lineage recovery and adb: it looked like it worked (it said "all done" without error message but the signature issue)
BUT
when I run Safetynet test (2022) it does find the pervious fingerprint
any idea of what could have failed ?
----
Phone; oneplus6 A6003
Rom: lineage-19.1-20220830-nightly-enchilada-signed
recovery: lineage-19.1-20220830-recovery-enchilada
props
note: the last oxygenOS is on Android 11 (so I copied the verison 11 in the props) but lineage is version 12
```
BUILD_FINGERPRINT=OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys
BUILD_DESCRIPTION=OnePlus6-user 11 RKQ1.201217.002 2111252325 release-keys
BUILD_SECURITY_PATCH_DATE=2021-11-01
BUILD_VERSION_RELEASE=11
BUILD_VERSION_RELEASE_OR_CODENAME=11
MANUFACTURER_NAME=OnePlus
PRODUCT_NAME=A6003
BUILD_TAGS=release-keys
BUILD_TYPE=user
DEBUGGABLE=0
```
pati--patou said:
Thanks for the work,
I tried the injectprop, I used /zFM to update the props ( I also set `inject_props=1`)
I sideload the zip using the lineage recovery and adb: it looked like it worked (it said "all done" without error message but the signature issue)
BUT
when I run Safetynet test (2022) it does find the pervious fingerprint
any idea of what could have failed ?
----
Phone; oneplus6 A6003
Rom: lineage-19.1-20220830-nightly-enchilada-signed
recovery: lineage-19.1-20220830-recovery-enchilada
props
note: the last oxygenOS is on Android 11 (so I copied the verison 11 in the props) but lineage is version 12
```
BUILD_FINGERPRINT=OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys
BUILD_DESCRIPTION=OnePlus6-user 11 RKQ1.201217.002 2111252325 release-keys
BUILD_SECURITY_PATCH_DATE=2021-11-01
BUILD_VERSION_RELEASE=11
BUILD_VERSION_RELEASE_OR_CODENAME=11
MANUFACTURER_NAME=OnePlus
PRODUCT_NAME=A6003
BUILD_TAGS=release-keys
BUILD_TYPE=user
DEBUGGABLE=0
```
Click to expand...
Click to collapse
Try this one ... https://forum.xda-developers.com/t/rom-official-hotdogb-12-lineageos-19.4509251/post-87666693
huskydg said:
I have forked ih8sn repo and make flashable zip for it. You can take a look here:
injectprop
Inject Android system properties
huskydg.github.io
Click to expand...
Click to collapse
Can it work on Samsung S4 GT-I9515/L Lineage 18.1? What should I edit in injectprop.sh if I have s4?
Bried said:
Can it work on Samsung S4 GT-I9515/L Lineage 18.1? What should I edit in injectprop.sh if I have s4?
Click to expand...
Click to collapse
It should work on any phone
thattechguy_69 said:
It should work on any phone
Click to expand...
Click to collapse
Do I need to edit anything in injectprop.sh if I have s4? Or should I leave everything as it is?