Database Users

[D855] [GUIDE] One Click ROOT+TWRP Recovery for Lollipop Stock Firmware [20H/20P/20G]

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 D855​Only Lollipop (not KitKat)
(16GB/2GB and 32GB/3GB variants)​Use only this tuto in case of failure with the previous quoted method​Credit
- @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.

[FIX][ExtSD] ExtSD Fix (v2.9b - 2016-06-09)

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 checksum​Download 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.

[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!

[ROM][FINAL][OFFICIAL]Resurrection Remix v6.0.0 [8.1.0]Jalebi][11/13]

{
"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"
}
Resurrection Remix Oreo​
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Resurrection Remix the ROM has been based on CM,slim.omni and original Remix ROM builds, this creates an awesome combination of performance, customization, power and the most new features, brought directly to your Device​
Special thanks to, the CM team,OMNI team ,SLIMROMS and of course to all the supporters​
-INSTALLATION INSTRUCTIONS-​
Code:
[CENTER][B]- Download the latest build
- Download Gapps (ARM 8.1 Pico/Nano/Other)
- Take a nandroid backup
- Recommended - Full wipe and factory reset
- Flash ROM using latest TWRP 3.x Recovery
- Flash Gapps
- Reboot.
- Enjoy![/B][/CENTER]
DOWNLOADS
RR OFFICIAL
Gapps Link :- OpenGapps ( Use Pico/Nano)​
SOURCES
Device Tree
Kernel Source (LineageOS)
CREDITS
Maaz Muzammil
theHari08
Special Thanks to Mah bruh @dev_harsh1998:highfive:​
XDA:DevDB Information
[ROM][FINAL][OFFICIAL]Resurrection Remix v6.0.0 [8.1.0]Jalebi][11/13], ROM for the Yu Yunique
Contributors
iamsj7
Source Code: https://github.com/ResurrectionRemix/
ROM OS Version: 8.x Oreo
Version Information
Status: Stable
Current Stable Version: v6.0.0
Stable Release Date: 2018-05-13
Created 2018-05-13
Last Updated 2018-11-12

Smart pixel option is available?

Rup_R said:
Smart pixel option is available?
Click to expand...
Click to collapse
yes

prabhjot368 said:
yes
Click to expand...
Click to collapse
Yeah.. i found it.. but still battery draining too much
---------- Post added at 05:43 AM ---------- Previous post was at 05:41 AM ----------
Can you provide any kernel for this problem?

Flashing ends with Error 7 in Twrp 3.0.3.0
I tried to flash the New RR-O-V6.0.0 yesterday in my phone ( Yu Yunique) through Twrp latest version but the flashing ends with an error code "error 7".
I also tried deleting the asserts file from update-script and then another error pops up saying corrupt file.
Please help .
Current ROM - RR-N-v5.8.5 Final.

remove lines from Update script
No.1708 said:
I tried to flash the New RR-O-V6.0.0 yesterday in my phone ( Yu Yunique) through Twrp latest version but the flashing ends with an error code "error 7".
I also tried deleting the asserts file from update-script and then another error pops up saying corrupt file.
Please help .
Current ROM - RR-N-v5.8.5 Final.
Click to expand...
Click to collapse
To Fix:
Open the Lineage OS ROM zip using any archiving software like 7zip, WinRAR, etc… You can also open it on your device.
Now, you need to navigate to this path: META-INF » com » google » android » updater-script.
Open the file updater-script in a text editor. You’ll see a bunch of lines with the command assert and the model name of the device next to it.
updater script lineage os
If there’s a mismatch with the codename of the device in the script, you’ll get Error 7 while flashing.
So, just either edit the code to match your device’s codename or delete all the lines having the code “assert & getprop”
Save the file.
Try to install the ROM now.
http://www.lineageosdownloads.com/fix-error-7-lineage-os/

No.1708 said:
I tried to flash the New RR-O-V6.0.0 yesterday in my phone ( Yu Yunique) through Twrp latest version but the flashing ends with an error code "error 7".
I also tried deleting the asserts file from update-script and then another error pops up saying corrupt file.
Please help .
Current ROM - RR-N-v5.8.5 Final.
Click to expand...
Click to collapse
Extract rom in a folder . go to META-INF , com , google , android , updater script.
open updater script using Notepad ++ , ( because other apps like word pad does not detect line numbers and you get error while flashing, so use notepad++), delete the first line and compress again.

RoHiTkUmArShArMa said:
Extract rom in a folder . go to META-INF , com , google , android , updater script.
open updater script using Notepad ++ , ( because other apps like word pad does not detect line numbers and you get error while flashing, so use notepad++), delete the first line and compress again.
Click to expand...
Click to collapse
How to do all this without PC ??

Is their offline charging problem in this rom?

Guys I successfully flashed rom RR V6 and gaaps 8.1 without any error but phone is stuck at boot animation and boots to recovery after some time. I upgraded from cm13 and facing this problem for every rom I install,but if I revert to cm13 everything works fine.kindy suggest a solution.

download rom again, or make sure you delet all words before this, ui_print("Target
download rom again, or make sure you delet all words before this, ui_print("Target

stuck at google logo...

RoHiTkUmArShArMa said:
Extract rom in a folder . go to META-INF , com , google , android , updater script.
open updater script using Notepad ++ , ( because other apps like word pad does not detect line numbers and you get error while flashing, so use notepad++), delete the first line and compress again.
Click to expand...
Click to collapse
It shows invalid file format every time .. i tried it on several other roms too. Any sol. or specific compressor to use??

ShivamNagi said:
It shows invalid file format every time .. i tried it on several other roms too. Any sol. or specific compressor to use??
Click to expand...
Click to collapse
You use Notepad++ for this or not.
Because only Notepad++ is detecting the lines correctly.
Extract the zip in separate folder.
Now select updater script from META-INF , com , google , android , updater script.
Delete the first line and go to start of 2nd line and hit backspace .Now your 2nd line now first line .
Now go to folder where to extract the ROM files .
Select all files and folders such as Install,META-INF,boot.img,system.bat,etc, (select everything ) , Right click , and compress these files to zip.
i think you are compressing the folder which contain these extracted files, thats why you are getting the error.

RoHiTkUmArShArMa said:
You use Notepad++ for this or not.
Because only Notepad++ is detecting the lines correctly.
Extract the zip in separate folder.
Now select updater script from META-INF , com , google , android , updater script.
Delete the first line and go to start of 2nd line and hit backspace .Now your 2nd line now first line .
Now go to folder where to extract the ROM files .
Select all files and folders such as Install,META-INF,boot.img,system.bat,etc, (select everything ) , Right click , and compress these files to zip.
i think you are compressing the folder which contain these extracted files, thats why you are getting the error.
Click to expand...
Click to collapse
Thanks for the help. I was zipping the folder because when i compressed the files by selecting them my mac's default will make different zips for each file/folder. I used winrar and it went fine..

Update 2018-11-13
ROM : \RR-O-v6.2.1-20181112-jalebi-OFFICIAL.zip
-merged Nov patches
-merged kernel cve pathes
-added device Network types
-kernel compiled on gcc linaro 7.1.2
-update gps overlays
-moved configs to vendor
-gps: Enable GLONASS
- add textclassifier's smart selection
- cleaned up sepolicy
- added all recording
- and source updates

unable to download bro.. site says secure connection failed

iamsj7 said:
Update 2018-11-13
ROM : \RR-O-v6.2.1-20181112-jalebi-OFFICIAL.zip
-merged Nov patches
-merged kernel cve pathes
-added device Network types
-kernel compiled on gcc linaro 7.1.2
-update gps overlays
-moved configs to vendor
-gps: Enable GLONASS
- add textclassifier's smart selection
- cleaned up sepolicy
- added all recording
- and source updates
Click to expand...
Click to collapse
Thanks for still keeping this device alive.

Hey Thank you for this ROM .
Will you be able to provide me with a link for installation guide for this ROM.
I'll be grateful.
Keep up the good work.

battery stats + screenshots
The AndroidGuy said:
Thanks for still keeping this device alive.
Click to expand...
Click to collapse
.......
.

[TOOL][DEV][1.0][OFFICIAL] Kernel Building - Essentials | Build a Kernel Easily!

{
"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"
}
This software will ask for sudo permissions in your machine to download and install all required tools for this program to run correctly, also, it'll execute chmod and chown to this program files and ~/.megarc (if exists) for the correct functioning of all the code, I'm not responsable if this program breaks your Machine (which it shouldn't be able by no ways). When you run for the first time this program, it will proceed to his first run configuration after the user authorization.
Welcome, I've been developing this program a long time ago with my free time after college, this is my first project made in Bash, the main purpose of all this software is to make a lot easier the process of building a Kernel, no matter which device you're building to (excluding MTK and those without source). This program will automatically download all required tools for Kernel building (~1.5GB), including the CrossCompiler (GCC arm/arm64) and other misc tools. You don't need a lot of knowledge to build your kernel with this software and it has all the tools for automatically build everything in just one command!
Requeriments:
A machine with Linux
Git
This program
Once you've downloaded the program to your Machine, you have to cd with Terminal to where you downloaded all the files and execute "core.sh" (bash core.sh or . core.sh) (Like this Example), this is indispensable every time you want to run the program, because it sets the program paths (Otherwise it'll not work)
Now, How it works?
Once you run the program, if it's for the first time then it'll automatically download all required tools and install them, after this it's time to setup your environment. You'll see a folder named "source", you have to put there the folder with the Kernel source contents like this and another folder named "templates" where you can set your AnyKernel (only AnyKernel for now) templates for different devices (Or just use the local one).
That's all, this program only needs you to set the Kernel source, now you've to run again core.sh and it'll prompt to you all the data needed for that session, like the name of the kernel, target android, version, kernel source folder, etc... When you've to select the architecture of your device, arm or arm64 and it'll download the correspondent CrossCompiler (GCC 4.9), after this, it'll promt to you how to set Kernel Installer template, the first option is to extract the local AnyKernel source into "./out/ak_template/" (Thanks to @osm0sis), second option is for select a user template from "./templates/" folder and the third option requires you to set manually the installer template inside "./out/ak_template/" similar or like this (Remember to configure it).
When it promt to you the variant, you've to put preferably the codename of your device (For example: Oneplus One codename is "bacon") and then select a defconfig for that device (For example: For Oneplus One it would be "lineageos_bacon_defconfig"), now that the program knows for which device It's going to compile, (You can add more variants) then, you can enable the KernelDebug option to enable the creation of the Device tree image (Applies for arm devices only) and allow the kernel source cleaning on every compiling process...
Now, let's get into the commands:
Command: "essentials <flag>": Here is where you start once you finish setting all the configs, 'essentials' is the main command of this program, but it only works with flags, otherwise it'll display the flags information that I'm gonna show right now:
Flags:
--kernel (Start the process of compiling your kernel)
--dtb (Generates the device tree image, applies to arm devices only)
--anykernel (Builds a installer for your kernel based on Anykernel by @osm0sis)
--upload (Uploads your Kernel installer to the root of your MEGA storage)
--all (This flag does all processes mentioned above)
You can combine all the flags except for "--all", because this one already does everything, also, no matter in which order, all the functions are going to be done in order to prevent an error (For example: 'essentials --anykernel --kernel' will build the kernel and then build the installer).
Also, after the first run, theres a file named: "defaultsettings.sh", it has a variable inside named "DSENABLED", if you set it to 1, the program instead of prompt you for information when you run "core.sh", it'll take all the config directly from that file, just make sure you've configured it first. :good:
Command: "auto <device> <flag>": This command allows you to make pre-configured files for a specified device, it requires that you have executed the program core.sh for the first time because it stores some config in your ~/.bashrc file, then, you can turn on or restart your machine and this command will still be available for it's use.
When you run 'auto' and next to it you specify the device (for example: auto oneplus), if the device (oneplus) doesn't exist in the device database (./resources/devices/) then, it'll promt to you all the data required for kernel, dtb (if applies), anykernel and upload process.
Once you have configured your device it'll be stored and when you run again the command 'auto' followed by the device name you configured before, (for example: auto oneplus) it'll load that device config file and build everything automatically (Kernel, dtb if applies, anykernel and upload if its enabled).
The Flags for this commands are:
--edit (Opens you the <device> config file for editing with nano)
--remove (Simply removes the <device> config file)
For more information I highly recommend to read the README.md in this program source on Github (It contains a more datailed and complete information).
This program has been tested and used on the following Linux distributions:
Ubuntu
Debian
I will really appreciate any feedback about how it performs on other Linux distributions
You can contact me with a PM (private message) here or in my Telegram group! (I'm @ArtxDev)
Me, @Stayn (Artx)
@osm0sis for his AnyKernel
This project on Github is open to pull requests, I will not hesitate to dedicate you a space here if you contribute for this project :good:
I'll be updating this program fixing bugs and bringing new features :good:
If you like it and want to do a small donation it for sure is gonna help me a lot and keep me motivated! :laugh:
Thank you and enjoy it!
XDA:DevDB Information
Kernel Building - Essentials, Tool/Utility for all devices (see above for details)
Contributors
Stayn
Source Code: https://github.com/KB-E
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-07-30
Created 2018-07-09
Last Updated 2018-07-30

In progress...

Mini Guides for absolutely newbies in progress...

Thanks

I just tried it and I get an error:
./core.sh: line 125: .: defaultsettings.sh: file not found
This file exists in Kernelbuilding-essentials directory though.
EDIT:
I tried to change ". defaultsettings.sh" with the full path of this file in line 125 and then I get another error on line 126
err: unary operator expected

dancer_69 said:
I just tried it and I get an error:
./core.sh: line 125: .: defaultsettings.sh: file not found
This file exists in Kernelbuilding-essentials directory though.
EDIT:
I tried to change ". defaultsettings.sh" with the full path of this file in line 125 and then I get another error on line 126
err: unary operator expected
Click to expand...
Click to collapse
Don't use sh to execute core.sh, use ". core.sh" or "bash core.sh"

Stayn said:
Don't use sh to execute core.sh, use ". core.sh" or "bash core.sh"
Click to expand...
Click to collapse
Thanks, I'm using arch linux and zsh as default. With "bash core.sh" the script runs fine.

dancer_69 said:
Thanks, I'm using arch linux and zsh as default. With "bash core.sh" the script runs fine.
Click to expand...
Click to collapse
Thanks for the feedback! If you have any other problem tell me

Cool project! You should specify bash in the shebang (normally the first line of a shell script) to fix issues where bash isn't default:
Code:
#!/bin/bash

osm0sis said:
Cool project! You should specify bash in the shebang (normally the first line of a shell script) to fix issues where bash isn't default:
Code:
#!/bin/bash
Click to expand...
Click to collapse
Done! Thanks

Hey guys, now Kernel Building - Essentials it's stable!
I've been working on fixing a lot of bugs and updating the program structure, now that the structure is totally defined and I don't need to change it anymore, I'll upload the first release at GitHub, version 1.0 and the next versions will be coming with a file to update your old version on KB-E (In this way there's no need to clone the repo again and again and merging your devices or configuration...)
There is all the updates and changes:
- Added a folder for Multiple Installers Templates: I've been thinking that anyone could have various kernel projects for different devices, so this means, that the templates for the installers needs to be different, so, now you can trow all the templates you want inside "templates" folder and the program will prompt to you which one you'll use for the current session (using core.sh "essentials" command) or a pre-configured device (using auto.sh "auto" command)
- Replaced option 2 in the program installer template config method, removed the ability to download the template from your MEGA Cloud and replaced by a selection of user templates inside "./templates/" folder
- Changed the "setuptools.sh" file name to "programtools.sh" because, all program misc functions are going to be stored there and "programtools" makes more sense
- Fixed a bug that happened when you didn't gave to the program the device variant (or codename) and then, "essentials" and "auto" command were not working, now the program forces you to set it (You can set your device name as device variant but it's preferably the device codename)
- Now when the program downloads the correspondent crosscompiler, it shows you the process
- Added the package "device-tree-compiler" into the download list of the function "installtools" (Executed when you run the program for the first time), this package is necessary for some arm64 sources to build device tree
- Fixed a annoying bug that cd's you to your "~/" directory instead of the current directory you were after executing "essentials" or "auto" command
- Now core.sh doesn't change the whole file permissions of your sources (sorry for this)
- Added a boost functionality for "auto" command that sums 2 threads to the compiling jobs when compiling the kernel (Recommended for machines with more than 2 real cores)
- Updated README.md
I would really apreciate some feedback guys, if you have any problems or you need help, feel free to contact me via my Telegram Group, enjoy!

Hi, it looks good so far...I have an MT6580 that I play around with but it's been stuck on kernel 3.10 for a long time. I've spent weeks trying port kernel from other MT6580 devices but haven't gotten any success yet. I got through the core.sh part. Is the essentials commands next ? I don't see it anywhere in the program.

Now I know how you automatically upload kernel to Mega Drive using code.. Unfortunately my G3 was Died...:crying:

Anyone know how to remove unwanted feature from a cooked/compiled kernel?

Excuse me, does this work on Ubuntu that runs on Windows Subsystem for linux?
By the way, thank you for the amazing artx-powered TWRP on my G3.