Database Develop

[Q] HELP X8 - JELLY BLUR 3.0/3.1 nAa Kernel .32 BOOT ERROR WITH LOG

I Try to install Jelly Blur with nAa .32 Kernel to my shakira with success!! No problem!
The Day after because of trouble with a2sd settings, I need to reinstall this rom ... but this time JELLY BLUR doesn't work anymore.
It stuck on Boot Logo of aAa Kernel .32. I can enter in CWM and manage my phone. I can install other bootloader and now I'm with mookeOs 1.3, but i like Jelly Blur 3.1 and i want it again on my phone
So ... wath's the problem ??? I attach CWM error reporting logo, maybe anyone can help me. I try everythig ... format /cache/data/system/dalvik/battery_stats ... reinstall original firmware for shakira by ftf with flashtool and by seus after ... but nothing work!!!
I waith for yours help ... tanks in advantage.
Sorry for my errors (i'm Italian)
This the log:
-----------------------------------------------------------------------
Starting recovery on Sun Feb 24 21:14:11 2013
framebuffer: fd 4 (320 x 480)
CWM-based Recovery v5.5.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /cache yaffs2 cache (null) 0
2 /data yaffs2 userdata (null) 0
3 /system yaffs2 system (null) 0
4 /sdcard vfat /dev/block/mmcblk0p1 (null) 0
5 /sd-ext ext4 /dev/block/mmcblk0p2 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.boot.hardware=delta
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=delta
ro.revision=0
ro.emmc=0
ro.boot.emmc=0
ro.factorytest=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.cwm.enable_key_repeat=true
ro.product.device=shakira
init.svc.ueventd=running
ro.crypto.state=unsupported
vold.post_fs_data_done=1
ro.build.id=JZO54K
ro.build.display.id=JellyBlur CM10 V3.1 4.1.2 JZ054K shakira
ro.build.version.incremental=eng.tiestobunio.20130216.124200
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Sat Feb 16 12:42:00 EET 2013
ro.build.date.utc=12420054
ro.build.type=user
ro.build.user=tiestobunio
ro.build.host=toshiba
ro.build.tags=test-keys
ro.product.model=E15i
ro.product.brand=SEMC
ro.product.name=LT30p_1269-0608
ro.product.board=shakira
ro.product.cpu.abi=armeabi-v6l
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony Ericsson
ro.wifi.channels=14
ro.board.platform=msm7x27
ro.build.product=shakira
ro.build.description=LT30p-user 4.0.4 7.0.A.3.195 PPP_xw test-keys
ro.build.fingerprint=Sony/LT30p_1269-0608/LT30p:4.0.4/7.0.A.3.195/PPP_xw:user/release-keys
ro.build.characteristics=default
ro.cm.device=shakira
ro.sf.lcd_density=160
keyguard.no_require_sim=true
ro.url.legal=
ro.url.legal.android_privacy=
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=Jelly Blur CM10
ro.modversion=Jelly Blur CM10
persist.sys.themeId=system
persist.sys.themePackageName=com.system.theme.jb
ro.media.dec.jpeg.memcap=10000000
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d/dev/smd0
ro.ril.hep=1
ro.ril.hsdpa.category=10
ro.ril.enable.dtm=1
ro.ril.enable.3g.prefix=1
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hsupa.category=6
ro.ril.disable.power.collapse=1
ro.telephony.ril_class=SemcRIL
wifi.interface=tiwlan0
wifi.supplicant_scan_interval=150
ro.ril.def.agps.mode=2
ro.ril.def.agps.feature=1
persist.sys.use_16bpp_alpha=1
persist.sys.use_dithering=2
persist.sys.force_hw_ui=true
ro.telephony.default_network=0
ro.telephony.call_ring.delay=1000
ro.telephony.call_ring.multiple=false
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.ril.enable.a52=1
ro.ril.enable.a53=1
ro.telephony.ril.v3=icccardstatus,skipbrokendatacall,signalstrength,datacall
ro.telephony.ril_skip_locked=true
ro.media.enc.file.format=3gp,mp4
ro.media.enc.vid.codec=m4v,h263
ro.media.enc.vid.h263.width=176,640
ro.media.enc.vid.h263.height=144,480
ro.media.enc.vid.h263.bps=64000,1600000
ro.media.enc.vid.h263.fps=1,30
ro.media.enc.vid.m4v.width=176,640
ro.media.enc.vid.m4v.height=144,480
ro.media.enc.vid.m4v.bps=64000,1600000
ro.media.enc.vid.m4v.fps=1,30
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
settings.display.autobacklight=1
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
windowsmgr.max_events_per_sec=150
debug.camcorder.disablemeta=1
dalvik.vm.dexopt-flags=m=y,o=v,u=y
dalvik.vm.checkjni=0
dalvik.vm.dexopt-data-only=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.execution-mode=int:jit
dalvik.vm.verify_bytecode=false
dalvik.vm.heapsize=64m
debug.sf.hw=1
debug.composition.type=cpu
debug.gr.numframebuffers=3
ro.max.fling_velocity=4000
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
hwui.render_dirty_regions=false
hwui.disable_vsync=true
debug.sf.no_hw_vsync=1
hwui.print_config=choice
debug.enabletr=false
debug.hwui.render_dirty_regions=false
debug.hwui.disable_vsync=true
com.qc.hardware=true
persist.service.zram=1
ro.zram.default=18
persist.sys.usb.config=mass_storage,adb
ro.opengles.version=131072
ro.product.locale.language=en
ro.product.locale.region=US
persist.ro.ril.sms_sync_sending=1
persist.android.strictmode=0
debug.performance.tuning=1
video.accelerate.hw=1
pm.sleep_mode=1
persist.pmem.camera=4000000
wifi.hotspot.ti=1
wifi.ap.interface=tiap0
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
net.bt.name=Android
net.change=net.tcp.buffersize.edge
dalvik.vm.stack-trace-file=/data/anr/traces.txt
persist.sys.purgeable_assets=1
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
persist.adb.notify=0
ro.kernel.android.checkjni=0
ro.FOREGROUND_APP_MEM=1280
ro.VISIBLE_APP_MEM=2560
ro.PERCEPTIBLE_APP_MEM=3840
ro.HEAVY_WEIGHT_APP_MEM=6400
ro.SECONDARY_SERVER_MEM=7680
ro.BACKUP_APP_MEM=8960
ro.HOME_APP_MEM=2048
ro.HIDDEN_APP_MEM=12800
ro.CONTENT_PROVIDER_MEM=15360
ro.EMPTY_APP_MEM=20480
ao.FOREGROUND_APP_ADJ=0
ro.VISIBLE_APP_ADJ=1
ro.PERCEPTIBLE_APP_ADJ=2
ro.HEAVY_WEIGHT_APP_ADJ=4
ro.SECONDARY_SERVER_ADJ=5
ro.BACKUP_APP_ADJ=6
ro.HOME_APP_ADJ=1
ro.HIDDEN_APP_MIN_ADJ=7
ro.EMPTY_APP_ADJ=15
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
Debug.performance.tuning=1
Video.accelerate.hw=1
media.stagefright.enable-record=false
ro.lge.proximity.delay=25
mot.proximity.delay=25
ro.config.hwfeature_wakeupkey=0
ro.FOREGROUND_APP_ADJ=0
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
---------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse

helppp
guys, i need some help, i recently unlocked bootloader, flashed kernel to ''nAa-11_2.6.29.6-nAa-11'' and tryed to install some custom roms that i've downloaded, about 5 of them. but any of them seems that doesnt work. idk what ROM to try anymore, i think that im not able to install any ROM anymore. pls i would appreciate help of experienced members here. sorry for my gramatics, im serb...

You know what you could do just format the system and then factory reset / wipe cache> wipe battery stats advanced and cache, and then the rom
Try to install the nAa jb-1 a and then flash the kernel nAa jb-02

tiestobunio said:
You know what you could do just format the system and then factory reset / wipe cache> wipe battery stats advanced and cache, and then the rom
Try to install the nAa jb-1 a and then flash the kernel nAa jb-02
Click to expand...
Click to collapse
hey, i forgot to say that my kernel is stuck, when i start the phone it just appears fot 10 seconds then reboot. i tryed to wipe cache, battery, data and cache partition but nothing happens. it still reboot to infinity...what to do next, im trying more ROM-s...

gacee016 said:
guys, i need some help, i recently unlocked bootloader, flashed kernel to ''nAa-11_2.6.29.6-nAa-11'' and tryed to install some custom roms that i've downloaded, about 5 of them. but any of them seems that doesnt work. idk what ROM to try anymore, i think that im not able to install any ROM anymore. pls i would appreciate help of experienced members here. sorry for my gramatics, im serb...
Click to expand...
Click to collapse
First of all follow this guide to go back to stock. Now tell us what rom are you trying to install? Because not any rom works with any kernel.

stamatis said:
First of all follow this guide to go back to stock. Now tell us what rom are you trying to install? Because not any rom works with any kernel.
Click to expand...
Click to collapse
i know how to back to stock, and to work with flashtool and all that stuff, but im still new in this. o tryed: GingerXperiaV20, MiniCM7-2.2.0 - shakira,
GingerDX-v030-shakira, MaxiCM V3 Crazy Apple, MaxiCM v5 Moka Final, MiniCM10-4.0.2-20121129-NIGHTLY-robyn, update-GingerDX-v028b...this is what i tryed till now, and i think i followed steps from tutorials i found about unlocking bootloader, flashing kernel and installing custom ROMs. One more thing, when i tryed to install first time some custom ROM, about 3 months ago, i didnt needed to unlock BL, flash kernel, i simply rooted phone, installed xRecovery and installed ROM (GingerXperiaV20) and it worked excellent. But now it doesnt work neather. Im sure that i screwed something up...cant figure it. sorry for my english again, im from serbia

Excuse me,
I understand you very much but many people are not aware of the proper use of the correct rom is required to follow the instructions

Have you follow the installation instructions of the rom, or you just started to download any rom you saw?
Your baseband number must be xx015.(you can see this at settings>about phone)
Make sure you are using the right kernel!
-In every rom thread it tells on what kernel it works with. If it tells "stock" then that means you dont need to flash a custom kernel so you dont need to unlock the bootloader. If it tells "*a name*" then that means you need that kernel(obviously).
Install the rom as described by the rom's thread.
-Factory reset and wipe dalvik cache before installing the rom(in some roms after)

stamatis said:
Have you follow the installation instructions of the rom, or you just started to download any rom you saw?
Your baseband number must be xx015.(you can see this at settings>about phone)
Make sure you are using the right kernel!
-In every rom thread it tells on what kernel it works with. If it tells "stock" then that means you dont need to flash a custom kernel so you dont need to unlock the bootloader. If it tells "*a name*" then that means you need that kernel(obviously).
Install the rom as described by the rom's thread.
-Factory reset and wipe dalvik cache before installing the rom(in some roms after)
Click to expand...
Click to collapse
you re right, i randomly searched for roms, but is not possible that at least one of the roms doesnt work. what do you guys would tell me to do next, im desperate, i read many of other threads and tutorials so im overbooked with links.

gacee016 said:
you re right, i randomly searched for roms, but is not possible that at least one of the roms doesnt work. what do you guys would tell me to do next, im desperate, i read many of other threads and tutorials so im overbooked with links.
Click to expand...
Click to collapse
I already told you.
stamatis said:
Your baseband number must be xx015.(you can see this at settings>about phone)
Make sure you are using the right kernel!
-In every rom thread it tells on what kernel it works with. If it tells "stock" then that means you dont need to flash a custom kernel so you dont need to unlock the bootloader. If it tells "*a name*" then that means you need that kernel(obviously).
Install the rom as described by the rom's thread.
-Factory reset and wipe dalvik cache before installing the rom(in some roms after)
Click to expand...
Click to collapse
And read the installation instructions at the thread of the rom you are trying to install!!!

ok, i will flash it to eclair and check my baseband number. but if it isnt xx015, what i should do next

gacee016 said:
ok, i will flash it to eclair and check my baseband number. but if it isnt xx015, what i should do next
Click to expand...
Click to collapse
If you flash eclair, your baseband number will be 015 so you will be ok.
Then, root, you said you have already unlocked your bootloader so flash a kernel with flashtool which works with the rom you will install next, reboot to cwm, full wipe(factory reset,wipe dalvik cache), install zip from sd card, choose the rom, reboot.
Note that this instructions may varry from rom to rom, for example if you want to install jelly bean by naa you need to do some steps more, so read the rom thread, the instruction that i described will for sure work with gb roms(gingerdx for example).

thank you very much ill read about every rom i find, all the requirements and ill follow instr. thanks again

its me again, i know im intense guy but im really confused, ive just tryed to install ginger v30 shakira, and followed instructions and read reqs, so i checked all the requirements and get them, then tryed to install it and it just doesnt work...in the end i will use stock eclair and let it go...but im confused because my ginger v20 worked before but now it doesnt. :/
---------- Post added at 08:01 PM ---------- Previous post was at 07:56 PM ----------
*but im confused cause earlier i had at least my gingerv20 and it worked properly but now cant have him neather.

gacee016 said:
its me again, i know im intense guy but im really confused, ive just tryed to install ginger v30 shakira, and followed instructions and read reqs, so i checked all the requirements and get them, then tryed to install it and it just doesnt work...in the end i will use stock eclair and let it go...but im confused because my ginger v20 worked before but now it doesnt. :/
---------- Post added at 08:01 PM ---------- Previous post was at 07:56 PM ----------
*but im confused cause earlier i had at least my gingerv20 and it worked properly but now cant have him neather.
Click to expand...
Click to collapse
I guess ginger v30 is gingerdx v30
Describe what exactly you did... and i hope we will find what is wrong:fingers-crossed:

i cant tell u step by step what exactly i did but i'll try, at the beginning, i didnt knew anything about bootloader, kernels, cause i didnt understood their function in all this, but after reading many posts and watching many videos on yt, i learned it and checked my phone's day of creation (11W22) and unlocked it and installed naa kernel 2.6, and tryed some roms that needed these two options installed. so i tryed first one, first i did full wipe, then installed rom, and again full wipe. but when i rebooted phone, logo appears for about 5 seconds and reboot again and all over again. also with other roms and in short lines thats what i did. now im on eclair and thinking what to do next.

At this point, go beyond the subject that is written in the subject line
Strange is a problem with jelly blur - my rom
and suddenly you write how to properly install the rom from scratch ...

tiestobunio said:
At this point, go beyond the subject that is written in the subject line
Strange is a problem with jelly blur - my rom
and suddenly you write how to properly install the rom from scratch ...
Click to expand...
Click to collapse
I think you didnt notice that the one that posted this thread and the one who is asking about how to install a rom are two different people.
I guess the op solved his problem as he haven't posted, so yes the topic is different.
gacee016 dont have problem with your rom, picard80 had.
:silly:

stamatis said:
I think you didnt notice that the one that posted this thread and the one who is asking about how to install a rom are two different people.
I guess the op solved his problem as he haven't posted, so yes the topic is different.
gacee016 dont have problem with your rom, picard80 had.
:silly:
Click to expand...
Click to collapse
I alwais have the same problem ... i dont know wath i need to doing ...

picard80 said:
I alwais have the same problem ... i dont know wath i need to doing ...
Click to expand...
Click to collapse
Finally I DO IT!! The problem was symlink of Memory Card
1) I do a repartizioning of Memory Card 8 GB with pc ... and I create a single partition in Fat32.
2) After i Reflash original FW of Shakir with FlashTool
3) After a Perform a Upgrade to lastest Baseband with PC companion
4) I Install directly Jb 03 Kernel .32
5) Insert Memory card
6) Turn ON and enter in CWM with back button
7) Do sequentially wipe factory reset, wipe cache, Dalvik cache, Format System
8) Install zip: JB and after GAPPS
9)Then reboot and Jelly blur finally start!!!

[RECOVERY] [TWRP 2.8.0.0] [v500] [9-11-2014]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
{
"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"
}
Tablet look:
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DISCLAIMER:
I nor anyone else is responsible for what you do to your device.
but if something goes wrong I will do my best to help
DOWNLOAD:
GooManager won't work for this device so please see Below for download links.
You can find more information and download links on our website!
Updated TWRP 2.6.3.1 for cm/aosp 3 versions
please check the software version in your: settings/ about tablet / software information / software version
and grab the one that matches yours
Click to expand...
Click to collapse
V50010a (<--V50010b use this one)
V50010c
V50010e
Archived builds
Flashable zip (works on any version if you already have a custom recovery installed just flash in recovery)
Flashable zip v2.6.3.2 ( ** updated with 1200x1920 theme works on any version if you already have a custom recovery installed just flash in recovery)
Flashable zip v2.6.3.3 ( ** updated with brightness slider works on any version if you already have a custom recovery installed just flash in recovery) credit goes to aicjofs
Flashable zip 2.7.0.0
Flashable zip 2.7.0.0B (added back option to backup recovery)
Flashable zip 2.7.0.0 with USB OTG
v500-TWRP_2.7.1.0-recovery.zip (just flash in recovery)
Current build
v500-TWRP_2.8.0.0-recovery.zip (just flash in recovery)
These builds are for the 4.4.2 bootloader
If you are on the 4.4.2 OTA this is the build you want:
just flash it in recovery
4.4.2-v500-TWRP_2.7.0.1-recovery.zip
New version 2.7.1.0
4.4.2-v500-TWRP_2.7.1.0-recovery.zip
New Version 2.8.0.0
4.4.2-v500-TWRP_2.8.0.0-recovery.zip (just flash in recovery)
If you don't have twrp on your device already
use the script from this thread scroll down to step 3 http://forum.xda-developers.com/showthread.php?t=2698267
then flash the above build in twrp
Credits:
@aicjofs for mentioning the kernel from the ota and all around help
@id10terror - for all the work he has done on the ota
@autoprime- for his 4.4.2 root
@annoyingduck- for testing
Click to expand...
Click to collapse
Don't forget to checkout the themes in post 2
loki : https://github.com/djrbliss/loki (click download zip on the right side)
These instructions are for 4.2.2 Only!!
Instructions:
Code:
you must be rooted
you must have fastboot and adb installed on your pc
download twrp
download loki
unzip loki
place twrp in bin folder of loki
connect your tablet to pc
open a terminal and cd to that bin folder
then run these commands:
adb push twrp.lok /data/local/tmp
adb push loki_tool /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/loki_tool
/data/local/tmp/loki_tool flash recovery /data/local/tmp/twrp.lok
exit
exit
adb reboot recovery
That is it you will now be in recovery
cheers
CREDITS:
@djrbliss for his bootloader patch LOKI this wouldn't be possible without it
@Dees_Troy and team win for this wonderful recovery
@mustbepbs for getting started with building recovery
@nycbjr and cmb roms
if I forgot someone please let me know

also found some nice themes you guys might like
http://forum.xda-developers.com/showthread.php?t=2675649 credit goes to @z31s1g
just grab the ones from the 1200 themes dropbox folder that is labled 2700
they have a configurable navbar and status bar and such
als here is a nice theme by @aicjofs http://forum.xda-developers.com/showpost.php?p=49969043&postcount=203

Drgravy said:
for science
Click to expand...
Click to collapse
Thanks Man. Did you use the Kingo root method ? What are your opinions on it in terms of safety ? How did you go about it ?

naruto.ninjakid said:
Thanks Man. Did you use the Kingo root method ? What are your opinions on it in terms of safety ? How did you go about it ?
Click to expand...
Click to collapse
yes I used kingo
personally I think its safe but I tend not to worry about that stuff
I just connected my tab and followed the directions

Warranty lose when installing?

Alexey71 said:
Warranty lose when installing?
Click to expand...
Click to collapse
It's great to see this kind of action around here.
Thanks a lot

Drgravy said:
I just connected my tab and followed the directions
Click to expand...
Click to collapse
@Drgravy
hi, just to be safe, this procedure for ADB and FastBoot is correct, right?
http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
because with windows 8.1 I have not done modding on my N7000 and I do not remember a beep
anyway thanks for the work done

Palux said:
@Drgravy
hi, just to be safe, this procedure for ADB and FastBoot is correct, right?
http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
because with windows 8.1 I have not done modding on my N7000 and I do not remember a beep
anyway thanks for the work done
Click to expand...
Click to collapse
Yes is perfect!

any help? i cant install it
loki aboot version does not match device

Alexey71 said:
Warranty lose when installing?
Click to expand...
Click to collapse
truthfully i am not sure
Palux said:
@Drgravy
hi, just to be safe, this procedure for ADB and FastBoot is correct, right?
http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
because with windows 8.1 I have not done modding on my N7000 and I do not remember a beep
anyway thanks for the work done
Click to expand...
Click to collapse
I am not up on windows
I have one old windows machine that I keep around just in case it is running vista
sugaritos said:
any help? i cant install it
loki aboot version does not match device
Click to expand...
Click to collapse
well I'll need some values from your: build.prop
so use your favorite root browser and navigate to system/build.prop and tell me these values:
Code:
ro.product.model=
ro.product.brand=
ro.product.name=
ro.product.device=
ro.product.board=
ro.build.version.incremental=
ro.build.version.sdk=
ro.build.version.codename=
ro.build.version.release=
ro.build.description=
ro.build.fingerprint=

Drgravy here is the info from my build.pop. i managed to pull the aboot.img from my device but i cannot use loki patch..
Code:
ro.product.model=LG-V500
ro.product.brand=lge
ro.product.name=awifi_open_kr
ro.product.device=awifi
ro.product.board=MSM8960
ro.build.version.incremental=V50010c.1379452672
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.description=awifi_open_kr-user 4.2.2 JDQ39B V50010c.1379452672 release-keys
ro.build.fingerprint=lge/awifi_open_kr/awifi:4.2.2/JDQ39B/V50010c.1379452672:user/release-keys

sugaritos said:
Drgravy here is the info from my build.pop. i managed to pull the aboot.img from my device but i cannot use loki patch..
Code:
ro.product.model=LG-V500
ro.product.brand=lge
ro.product.name=awifi_open_kr
ro.product.device=awifi
ro.product.board=MSM8960
ro.build.version.incremental=V50010c.1379452672
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.description=awifi_open_kr-user 4.2.2 JDQ39B V50010c.1379452672 release-keys
ro.build.fingerprint=lge/awifi_open_kr/awifi:4.2.2/JDQ39B/V50010c.1379452672:user/release-keys
Click to expand...
Click to collapse
ok i see the difference
to make this work you will need to open a new issue here : https://github.com/djrbliss/loki/issues?page=1&state=open
and provide this info and also provide your aboot.img
he should be able to update loki for your device

yesterday a new firmware update has come. when i update i must open again a new issue? (this update will come to all devices lg said. it may fixes the blue line issue)

sugaritos said:
yesterday a new firmware update has come. when i update i must open again a new issue? (this update will come to all devices lg said. it may fixes the blue line issue)
Click to expand...
Click to collapse
possibly
any time we take a update from lg we risk loki not working anymore

sugaritos said:
yesterday a new firmware update has come. when i update i must open again a new issue? (this update will come to all devices lg said. it may fixes the blue line issue)
Click to expand...
Click to collapse
Can you post what the new firmware identifier is? Does anybody know what changed?

But on my Tablet installed TWRP?
ro.product.model=LG-V500
ro.product.brand=lge
ro.product.name=awifi_open_cis
ro.product.device=awifi
ro.product.board=MSM8960
ro.build.version.incremental=V50010a.1380630039
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.description=awifi_open_cis-user 4.2.2 JDQ39B V50010a.1380630039 release-keys
ro.build.fingerprint=lge/awifi_open_cis/awifi:4.2.2/JDQ39B/V50010a.1380630039:user/release-keys
Click to expand...
Click to collapse

Alexey71 said:
But on my Tablet installed TWRP?
Click to expand...
Click to collapse
as long as it is V50010a.xxxxxxxxx
you should be fine

I've been working with Dees_troy to make this official

can i flash twp.img with any toolkit?

When trying the first method always get this message:
/data/local/tmp/loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.0-awifi.img
sh: recovery: not found..
so googled a little and found this APP, at XDA forum... worked like a charm http://forum.xda-developers.com/showthread.php?t=2349847.

[GUIDE][Noob Friendly] How to make custom rom for Infinix Hot 2

Hi,
This is a all in one guide for making custom roms for Infinix Hot 2.
The guide will have 3 parts:
1) Normal porting
2) Crossporting => Click here
3) Bug fixing => Click here
Disclaimer:
Code:
I, XDA or anyone else involved in the making of this guide
can NEVER be held for any damage to your device if you
follow an even small part of this guide. We won't bear
any responsability for dead sdcards, thermonuclear
explosions, fried mother, your device gave birth to a
dragon or goes to mars!
If anything happens, bad or good, consider it as fate and
live with it.
Basics & Terms:
Terms:
Stock ROM: This is your original ROM. Can also be called Stock.
Port ROM: This is the ROM you want to port. Can also be called Port.
Boot.img: This is the kernel and the ramdisk.
BootP.img: This should be Port ROM Boot.img
BootS.img: This should be Stock ROM Boot.img
Normal Porting: This is for porting from the same Chipset (MT6580 to MT6580)
Crossporting: This is for porting from a different but close Chipset (MT6582 to MT6580 or MT6592 to MT6580). These chipsets have Mali-400MP GPU with different cores.
Basics:
What is porting ?
Porting is simply making another device's software work on yours.
Benefits ?
Well, you can enjoy many custom UI beside the stock ROM's UI such as:
- Amigo OS
- HTC Sense
- Samsung Touchwiz
- Freeme OS
- Flyme OS
- Asus Zen UI
- Etc
Porting rules: PORTING ONLY WORK WITH SAME ANDROID VERSION. YOU CAN NOT PORT KITKAT ROM TO HOT 2. YOU CAN'T PORT MARSHMALLOW ROM WITH LOLLIPOP BOOT.IMG
Click to expand...
Click to collapse
Part 1: Normal porting
Fast and Automatic Porting Tool:
Update:
The XDA user @RendyAK created an awesome tool that will automate this process for you!
All you just need is Port ROM system.img and Boot.img
If your ROM comes in Recovery format, go to "Get Port ROM ready" section, because this tool requires a system.img
Download here Fastport v1.zip (Google Drive)
I. Get Stock ROM ready
A- Method 1:
1) Connect your phone to your PC.
- Make sure it's rooted and you're on stock rom.
- Make sure you have installed all necessary drivers including ADB, Fastboot, Vcom PreLoader etc.
- Make sure you have enabled "USB Debugging" in "Developer Options"
2) Create a folder on your desktop and name it "System". Open it and click on "Shift" on your keyboard now click "Open command window here"
3) Now type in the following command:
Code:
adb devices
adb pull /system
Once done, you should find your files in system folder you created in step 2.
4) Now time to extract stock boot.img. Type the following commands (press enter after each command):
Code:
adb shell
su
cd /sdcard
mkdir dd.out
dd if=/dev/block/platform/mtk-msdc.0/by-name/boot of=/sdcard/dd.out/boot.img
exit
adb pull sdcard/dd.out/boot.img
Now you should have boot.img inside system folder. Create a new folder and name it "Stock". Move boot.img from system folder created in step 2 to the newly created "Stock" folder. Move the system folder itself to "Stock" folder.
B- Method 2:
If for some reasons that doesn't work, then follow these.
1) Get a Stock ROM for your Hot 2 (Infinix 5.1 recommended).
2) Extract it, you'll get a folder with a bunch of files inside it. We just need boot.img and system.img
3) Download and extract this file Extract_System.rar
4) Open the extracted folder, open ext4_unpacker.exe and click on the little folder near the Exit button.
5) Locate the system.img file of the stock rom you extracted in step 2.
6) Wait till it loads, now select all the files on the right column. Right click and select "Extract", point it to the system (guide by Nonta, stolen by Nayan Deka) folder inside the extracted archive (extracted in step 3).
7) When done, move the system folder from the extracted archive to a new folder (name that new folder "Stock"). Copy boot.img from the extracted folder in step 2.
II. Get Port ROM ready
The Port ROM will come in either Recovery flashable or SP Flash tool flashable format. Procedure is different for each.
A- Recovery version:
If the ROM comes in Recovery version, you'll see system.new.dat inside the archive instead of system.img Follow these to get it extracted.
1) Download and extract the ROM
2) Download the this file Extract_System.rar and extract it somewhere.
3) Move everything except META-INF from the extracted folder in step 1 to the extracted folder in step 2.
4) Do "Shift" and right click to open CMD here. Now read the IMPORTANT.txt file. Open README.txt, copy one of the command and paste it in the CMD terminal. Press enter.
5) When done, you should see a new file named "new_system.ext4"
6) Open ext2explore.exe Click file and then Open Image, locate the "new_system.ext4" file.
7) When it's loaded, right click on the file on the right column and then save, point it to the "system" folder inside the extracted folder (extracted on step 2). When done move it to a new folder (name that folder "Port"). Also copy boot.img from the Port ROM to that folder.
B- SPFT version:
If the ROM is in SPFT format, then you'll see system.img and many other .img files.
Just follow Method 2 of Stock ROM extraction :cyclops:
If for some reasons it doesn't work, Follow these:
1) Download this program ImgExtractor.rarand extract it in the Port ROM folder alongside all the .img and .bin files.
2) Drag and drop system.img into the ImgExtractor.exe file. Wait till the end. You'll find the extracted system.img inside system_ folder.
3) Done! So easy
III. Porting
Once you have Stock ROM and Port ROM ready. You can now start to port.
A- Porting system:
1) Open Stock ROM and Port ROM folders side-by-side
2) Copy these files from Stock/system/lib: libcamalgo.so , libcameracustom.so . Paste them in Port ROM/system/lib folder, replace when prompted.
3) Go to Port/system/etc and delete "firmware" folder. Now go to Stock/system/etc and copy "firmware" folder from there to Port/system/etc
4) Open build.prop of port ROM with a text editor. Search for "qemu.hw.mainkeys" and set its value to "0". If it doesn't exist then add it at the end of build.prop. It should look like this qemu.hw.mainkeys=0 Sometimes the 0 value doesn't work, (guide by Nonta, stolen by Nayan Deka) you'll have to try with 1 (qemu.hw.mainkeys=1). If it still doesn't, then you'll have to use third-party navbars like "Simple Control" from Play Store.
5) Still inside build.prop, make sure that ro.sf.lcd_density value is 320. Save and exit.
A- Porting kernel:
1) Download Carliv Image Kitchen from this thread Extract it somewhere
2) Copy Stock boot.img to the extracted Carliv Image Kitchen/boot-ressources. Rename it to BootS.img
3) Move (yes, move) boot.img of Port ROM to Carliv Image Kitchen/boot-ressources. Rename it to BootP.img
4) Double click "Carliv.bat" and follow steps to extract both img files.
5) Now, open BootS folder, copy all the 9 files (not the ramdisk folder). Paste them in BootP folder. Replace when prompted.
6) Go back to Carliv Image Kitchen CMD window, make sure that BootP.img is selected. Now press "2" to repack the kernel.
7) When done, go to Carliv Image Kitchen/Output and copy the repacked boot.img (should be named boot_201x_xxx.img). Paste it in the Port ROM folder.
8) Copy the META-INF folder from "Extract_System.rar" archive. Paste it in Port ROM folder so that you have META-INF, system and boot.img.
9) Select all the files and zip them. Copy them to your Hot 2. Boot to recovery. Wipe data and factory reset. Click advanced wipe and select cache, dalvik-cache, system and slide to wipe. Go back and select your created ROM. Install!
10) Congratulations! You just ported a ROM to your Hot 2 :laugh:
Alternatively, you can simply follow these steps (only if Port ROM comes in SPFT format).
1) Extract both ROMs
2) Port Kernel using the above guide
3) Open SPFT, load the scatter file of your Stock ROM.
4) Uncheck everything. Click on boot column and load the ported kernel from step 2.
5) Click on system column and select system.img of the Port ROM
Flash your device with these two files.
!!! WARNING !!!
NEVER USE ANOTHER DEVICE'S SCATTER FILE.
THIS METHOD IS KNOWN TO EASILY CORRUPT SYSTEM PARTITION. YOU WILL HAVE TO MANUALLY FORMAT IT IN RECOVERY IF THAT HAPPENS.
Credits:
- xpirt
- Carliv
- And_PDA
Anyone is free to use my work. You are even free to give credits. But before doing so, remember that Android is about sharing. Open source is what makes Android's beauty. Many people work on MTK but they never expose all their porting secrets. Using this guide doesn't give you the right to port someone else's ROM without their permission.

Part 2: Crossporting
Before you continue, please understand these:
This section is intended for advanced users only. If you never ported a rom, please stop here!
- This Method is NOT fail-proof. Your device will simply bootloop even if you follow this guide.
- It does NOT work with AOSP based ROMs. Always bootloop.
- Only Cyanogenmod 12.1 ROMs are supported. CM-13 ROMs give black screen.
- It does NOT work if you port from sprout (4/8)
Click to expand...
Click to collapse
1) Get a stable CM-12.1 ROM for Hot 2. You can grab one here This will be called "Stock"
2) Get a CM-12.1 or based ROM for MT6582 or MT6592. This will be called "Port"
3) Extract both. Follow one of the methods in part 1 if needed.
4) Open both "Stock" and "Port" folders side-by-side.
5) Go to Stock/system delete (Guide by Nonta, Stolen by Nayan Deka) these: app, fonts, framework, media, priv-app, build.prop
6) Go to Port/system and copy app, fonts, framework, media, priv-app, build.prop from there to Stock/system. Copy any extra folder from Port/system to Stock/system (only extra folders. It's extra if it doesn't exist in stock rom).
7) Go to Port/system/bin and copy everything , paste them in Stock/system/bin. Skip when prompted! DO NOT REPLACE EXISTING ONES.
8) Repeat previous steps but this time copy from lib folder. Don't copy folders inside lib folder. Just .so files. Also do the same with files inside etc folder (copy just files inside "etc" folder) and xml files inside etc/permissions. Finally copy any extra folder that is in Port/system/etc folder and paste in Stock/system/etc.
9) Now go to Port/system/lib and copy these: libandroid.so, libandroid_runtime.so, libandroid_server.so, libandroidfw.so, libmedia_jni.so, libwebviewchromium.so, libwebviewchromium_loader.so, libwebviewchromium_plat_support.so now paste them in Stock/system/lib and replace the existing ones.
10) Repeat Step 7 with permissions folder, xbin folder and (Guide by Nonta, Stolen by Nayan Deka) vendor folder (including vendor subfolders).
11) Edit build.prop file in Stock/system and replace all MT6582 or MT6592 or sprout with MT6580. Also add the qemu.hw.mainkeys=0 line and make sure ro.sf.lcd_density value is 320
12) Now zip Stock folder and flash it.
If it doesn't boot then go to Part 3 for bug fixing.
Credits:
Special thanks to
@RendyAK
@Besik_13

Part 3: Fixing bugs
If your ROM boots, you'll likely get some bugs such as camera, sound, RIL etc.
For Stock or stock based ROMs
Audio fix:
Copy libaudio.primary.default from Stock ROM.
Camera fix:
If camera can't connect or force close
Copy libcamalgo.so and libcameracustom.so from stock ROM
If it still doesn't work, then copy all files with libcam from Stock ROM.
If it still persists, edit unpack boot.img using the method in Part 1. Compare both init.rc files and add extra lines from BootP/ramdisk/init.rc to BootS/ramdisk/init.rc
If camera size is wrong or swapped
Copy libcam.paramsmgr.so from Stock ROM
SIM card detection fix:
- Use Stock ROM's firmware folder
- Compare both build.prop files and make changes according (Guide by Nonta, stolen y Nayan Deka) to what is in Stock build.prop starting from # ADDITIONAL_BUILD_PROPERTIES DON'T TOUCH RINGTONE AND NOTIFICATIONS SETTINGS.
- Also think about restoring your IMEI or rewriting it using for example ToolHero.apk
For CM-12.1 or based ROMs
Bootloop fix:
- Unpack both BootS.img and BootP.img following the steps provided in Part 1.
- Compare init.environ.rc files and make changes according to what is in BootP init.environ.rc file. Only compare BOOTCLASSPATH section!
- Compare both init.rc files and add extra lines from BootP.
Shared by Rendy
RendyAK said:
Some more thing.
Fix bootloops:
After compare init.environ.rc.
Compare init.rc.
If some apps still FC after replace libwebchromexxx.so
Check the port updater-script/.img and check if there are some symlinks that arent in base one
Click to expand...
Click to collapse
If it still doesn't work, then sorry! I can't help further :fingers-crossed:
Sdcard detection fix:
If SD Card doesn't appear in file manager, follow these:
- Open Stock/system/framework/framework-res.apk file with 7-zip and go to res/xml. Extract storage_list.xml somewhere.
- Open Port/system/framework/framework-res.apk file with 7-zip and go to res/xml. Delete storage_list.xml. Drag and drop the storage_list.xml file you extracted in step (Guide by Nonta, stolen y Nayan Deka) one into 7-zip window.
RIL fix:
To fix RIL in cm-12.1 or based ROMs, follow:
- Unpack boot.img of your cm-12.1 or based ROM using the steps provided in Part 1. Let assume you named it BootS
- Go to BootS/ramdisk and edit init.modem.rc. Delete everything inside that file and copy paste the lines below.
Code:
# Copyright (C) 2012 The Android Open Source Project
#
# IMPORTANT: Do not create world writable files or directories.
# This is a common source of Android security bugs.
#
on post-fs-data
write /proc/bootprof "post-fs-data: on modem start"
# Modem related device nodes
mkdir /data/nvram/md 0770 root system
mkdir /data/nvram/md2 0770 root system
# Build-in Modified - S
# insmod /system/lib/modules/ccci_plat.ko
# insmod /system/lib/modules/ccci.ko
# Build-in Modified - E
# chown radio radio /sys/class/BOOT/BOOT/boot/md
chown radio radio /sys/kernel/ccci/boot
# xplod: this is not in the original mtk file... But I have no
# idea what kind of sorcery normally sets them
chown radio radio /dev/ccci_fs
chown radio radio /dev/ccci_ioctl0
chown radio radio /dev/ccci_ioctl1
chown radio radio /dev/ccci_ipc_1220_0
chown radio radio /dev/ccci_md_log_rx
chown radio radio /dev/ccci_md_log_tx
chown radio radio /dev/ccci_monitor
chown radio radio /dev/ccci_pcm_rx
chown radio radio /dev/ccci_pcm_tx
(Guide by Nonta, stolen y Nayan Deka)
chown radio radio /dev/ccci_uem_rx
chown radio radio /dev/ccci_uem_tx
#SeLinux
mkdir /data/ccci_cfg 0770 system radio
restorecon /data/ccci_cfg
restorecon_recursive /protect_f
restorecon_recursive /protect_s
# Encrypt phone function
setprop vold.post_fs_data_done 1
service gsm0710muxd /system/bin/gsm0710muxd -s /dev/ttyC0 -f 512 -n 8 -m basic
class core
user root
group radio cache inet misc
disabled
oneshot
service gsm0710muxdmd2 /system/bin/gsm0710muxdmd2 -s /dev/ccci2_tty0 -f 512 -n 8 -m basic
class core
user root
group radio cache inet misc
disabled
oneshot
service muxreport-daemon /system/bin/muxreport
class core
user radio
group radio cache inet misc
disabled
oneshot
service ril-daemon /system/bin/rild
class core
socket rild stream 660 root radio
socket rild2 stream 660 root radio
socket rild3 stream 660 root radio
socket rild4 stream 660 root radio
socket rild-ims stream 660 root radio
socket rild-debug stream 660 radio system
socket rild-oem stream 660 radio system
socket rild-mtk-ut stream 660 radio net_bt
socket rild-mtk-ut-2 stream 660 radio net_bt
socket rild-mtk-modem stream 660 radio system
socket rild-atci stream 660 root radio
user root
group radio cache inet misc audio sdcard_r sdcard_rw log system
disabled
oneshot
service ril-daemon-md2 /system/bin/rildmd2
class core
socket rild-md2 stream 660 root radio
socket rild2-md2 stream 660 root radio
socket rild-debug-md2 stream 660 radio system
socket rild-oem-md2 stream 660 radio system
socket rild-mtk-ut-md2 stream 660 radio net_bt
socket rild-mtk-ut-2-md2 stream 660 radio net_bt
socket rild-mtk-modem-md2 stream 660 radio system
socket rild-atci-md2 stream 660 root radio
user root
group radio cache inet misc audio sdcard_r sdcard_rw log system
disabled
oneshot
service md_minilog_util /system/bin/md_minilog_util
user radio
disabled
oneshot
#
# Modem related services (Begin)
#
service permission_check /system/bin/permission_check
class main
user root
group nvram
group system radio
oneshot
service ccci_fsd /system/bin/ccci_fsd 0
user root
user radio
group radio system
class core
oneshot
service ccci2_fsd /system/bin/ccci_fsd 1
user root
user radio
group radio system
class core
oneshot
service ccci_mdinit /system/bin/logwrapper /system/xbin/strace -s 1024 /system/bin/ccci_mdinit 0
user root
user system
group radio system
class core
oneshot
service ccci2_mdinit /system/bin/ccci_mdinit 1
user root
user system
group radio system
class core
oneshot
service ccci_rpcd /system/bin/ccci_rpcd 0
user radio
group radio system
class core
oneshot
service ccci2_rpcd /system/bin/ccci_rpcd 1
user radio
group radio system
class core
oneshot
service pppd_gprs /system/bin/pppd_dt /dev/ttyACM0 debug noauth refuse-eap usepeerdns nodetach
user root
group radio cache inet misc
disabled
oneshot
#Add by T.Zh for ppp daemon
service pppd /system/bin/pppd file /data/misc/ppp/ppp_options
user root
disabled
oneshot
#
#
# Modem related services (End)
#
#Add by hp.chen for
#
# Telephony Early Read service
#
service terservice /system/bin/terservice
class core
(Guide by Nonta, stolen y Nayan Deka)
user radio
group radio cache inet misc
oneshot
on property:ril.muxreport=1
start muxreport-daemon
- Repack the BootS.img and flash it.
- Download this file Fix_RIL_CM12.1.zip and flash it in recovery.
- Reboot your device, RIL should start to work. If not, try restoring or rewriting your IMEI.
Other bugs can be fixed using stock rom bug fixing methods as well
Credits:
Special thanks to
@RendyAK
@Besik_13

One more ...

good work,hope u will port more rom for our device :good:

Anything specific for 6.0

AonSyed said:
Anything specific for 6.0
Click to expand...
Click to collapse
This guide should apply without problem.

Some more thing.
Fix bootloops:
After compare init.environ.rc.
Compare init.rc.
If some apps still FC after replace libwebchromexxx.so
Check the port updater-script/.img and check if there are some symlinks that arent in base one

Can rendy tool be used to port Hot 3 firmware automatically?
Sent from my Infinix X510 using XDA-Developers mobile app

Mysteryagr said:
Can rendy tool be used to port Hot 3 firmware automatically?
Sent from my Infinix X510 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm not sure
Plus it doesn't seem to be stable.
You need to use the crossporting method for the Hot 3 ROM to work

Nonta72 said:
I'm not sure
Plus it doesn't seem to be stable.
You need to use the crossporting method for the Hot 3 ROM to work
Click to expand...
Click to collapse
Okay, I'm waiting for XUI version 2
Then I will give it a try
Sent from my Infinix X510 using XDA-Developers mobile app
---------- Post added at 12:03 PM ---------- Previous post was at 11:39 AM ----------
I know it is a stupid question, but how to edit "updater-script" cause always when I try to edit it I get flashing errors in recovery
Sent from my Infinix X510 using XDA-Developers mobile app

Mysteryagr said:
Okay, I'm waiting for XUI version 2
Then I will give it a try
Sent from my Infinix X510 using XDA-Developers mobile app
---------- Post added at 12:03 PM ---------- Previous post was at 11:39 AM ----------
I know it is a stupid question, but how to edit "updater-script" cause always when I try to edit it I get flashing errors in recovery
Sent from my Infinix X510 using XDA-Developers mobile app
Click to expand...
Click to collapse
Edit with Notepad ++ program
Make sure every line ends with an " ; " (without the quotes)

Nonta72 said:
Edit with Notepad ++ program
Make sure every line ends with an " ; " (without the quotes)
Click to expand...
Click to collapse
Thanks, btw I noticed that there are two roms for Hot 3 (3G Version) one with A1 in its name and the second has A2 in its name, do you know what's the difference?
Sent from my Infinix X510 using XDA-Developers mobile app

Mysteryagr said:
Thanks, btw I noticed that there are two roms for Hot 3 (3G Version) one with A1 in its name and the second has A2 in its name, do you know what's the difference?
Sent from my Infinix X510 using XDA-Developers mobile app
Click to expand...
Click to collapse
Nope
But I assume they are same

Tried porting Hot 3 using cross porting method and as my previous attempted, ended in bootloop :/
Sent from my Infinix X510 using XDA-Developers mobile app

Mysteryagr said:
Tried porting Hot 3 using cross porting method and as my previous attempted, ended in bootloop :/
Sent from my Infinix X510 using XDA-Developers mobile app
Click to expand...
Click to collapse
I will get back to you soon.

Nonta72 said:
I will get back to you soon.
Click to expand...
Click to collapse
Okay, take your time
Sent from my Infinix X510 using XDA-Developers mobile app

@Nonta72 there is something not clear for me in cross porting method, after step 7, any existing matching file should be skipped, as we do in step 7?
I mean in permission, xbin, vendor.. etc
Or they should be replaced?
Thanks in advance ^^
Sent from my Infinix X510 using XDA-Developers mobile app

Mysteryagr said:
@Nonta72 there is something not clear for me in cross porting method, after step 7, any existing files should be skipped!?
I mean in permission, xbin, vendor.. etc
Or they should be replaced?
Thanks in advance ^^
Sent from my Infinix X510 using XDA-Developers mobile app
Click to expand...
Click to collapse
Seemed clear to me
You shouldn't replace them. They should be skipped.
And something is wrong with your XUI porting.
You also need to port the kernel. I noticed that using the stock boot.img or boot.img from XUI (Note port) won't make it boot.
So follow kernel porting step too. I just applied crossporting method and kernel porting method, they worked.
USE XUI FROM HOT NOTE AS BASE! DON'T USE INFINIX 5.1 OR ANDROID ONE 5.1
:good:

Thanks for the tips, will try again today ??
Sent from my Infinix X510 using XDA-Developers mobile app

[RECOVERY][ROOT]TWRP 3.1.0-1 Samsung Galaxy A7 SM-A720F/DS

Unofficial release -TWRP recovery for the Galaxy A7 - SM-A720F/DS, Exynos 7880
{
"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"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
INSTRUCTIONS FOR ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
Update 12/4/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
NOTE: THIS IS CURRENTLY IN THE TESTING STAGE, THERE MAYBE BUGS, IT MAY NOT BOOT AT ALL. I DON'T OWN THIS DEVICE. I CAN'T FIX ISSUES IF PEOPLE DON'T POST RECOVERY LOGS OR PROPERLY DESCRIBE THE ISSUE. STOCK RECOVERY IS PROVIDED BELOW IF NEEDED.
Features:
MTP working > to be confirmed
ADB working > to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
TWRP: twrp_3.1.0-1_sm-a720f_12417
Stock recovery: A720FXXU1AQC5_stock_recovery
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.

Hands off.

As usual nobody can find the time to report back.

Thanks!
Successfully flashed TWRP but cannot flash SuperSU. TWRP reboots when superSU installer is doing "Extracting files"

moistcity said:
Thanks!
Successfully flashed TWRP but cannot flash SuperSU. TWRP reboots when superSU installer is doing "Extracting files"
Click to expand...
Click to collapse
Can you save and post the recovery.log file.

ashyx said:
Can you save and post the recovery.log file.
Click to expand...
Click to collapse
Hmm... I don't know how to attach files and xda doesnt let me post outside links
I have it on a google drive, I could email it.

moistcity said:
Hmm... I don't know how to attach files and xda doesnt let me post outside links
I have it on a google drive, I could email it.
Click to expand...
Click to collapse
Just put it on pastebin.com and just post the link without the https://pastebin.com

OK just looked at the log and I don't see any issues or reason why SuperSU would fail.
Maybe try a different version of SuperSU?

ashyx said:
OK just looked at the log and I don't see any issues or reason why SuperSU would fail.
Maybe try a different version of SuperSU?
Click to expand...
Click to collapse
Tried 2.79 sr2 but still nothing.
Trying 2.78 to see if it works or not
---------- Post added at 06:44 AM ---------- Previous post was at 06:26 AM ----------
Tested 2.78 and 2.77 beta.
2.78 reboots back to twrp.
2.77 reboots back to system.
I think it can't log what happened cause it just reboots on the process of flashing superSU.

moistcity said:
Tried 2.79 sr2 but still nothing.
Trying 2.78 to see if it works or not
---------- Post added at 06:44 AM ---------- Previous post was at 06:26 AM ----------
Tested 2.78 and 2.77 beta.
2.78 reboots back to twrp.
2.77 reboots back to system.
I think it can't log what happened cause it just reboots on the process of flashing superSU.
Click to expand...
Click to collapse
Everything else works fine? Backup, restore etc?
Can you see if /tmp exists in TWRP file manager.
Can you install the no-verity-no-encrypt_ashyx OK?

ashyx said:
Everything else works fine? Backup, restore etc?
Can you see if /tmp exists in TWRP file manager.
Can you install the no-verity-no-encrypt_ashyx OK?
Click to expand...
Click to collapse
Backup and restore works.
didn't check on that one but pretty sure /tmp is there.
I have installed no-verity-no-encrypt_ashyx just as the instructions said.
Resetting phone firmware with Smart Switch and trying it again.
Recovery.log before installing no-verity-no-encrypt_ashyx and SuperSU
pastebin.com/5VexMze8
Recovery.log after attempting to install SuperSU (Same problem happened again, fresh firmware)
pastebin.com/diY9xGP0
Recovery.log after successfully installing no-verity-no-encrypt_ashyx and attempting to install SuperSU
pastebin.com/SL4xyYRY

moistcity said:
Backup and restore works.
didn't check on that one but pretty sure /tmp is there.
I have installed no-verity-no-encrypt_ashyx just as the instructions said.
Resetting phone firmware with Smart Switch and trying it again.
Recovery.log before installing no-verity-no-encrypt_ashyx and SuperSU
pastebin.com/5VexMze8
Recovery.log after attempting to install SuperSU (Same problem happened again, fresh firmware)
pastebin.com/diY9xGP0
Recovery.log after successfully installing no-verity-no-encrypt_ashyx and attempting to install SuperSU
pastebin.com/SL4xyYRY
Click to expand...
Click to collapse
So it seems the issue is with SuperSU and may be one for Chainfire to look at.
Considering the boot image patcher installs fine, proves that zips are working.
I'm going to have a look at the supersu install script before I raise it as a bug.

ashyx said:
So it seems the issue is with SuperSU and may be one for Chainfire to look at.
Considering the boot image patcher installs fine, proves that zips are working.
I'm going to have a look at the supersu install script before I raise it as a bug.
Click to expand...
Click to collapse
Please do. I'd want to root my A720F and remove these annoying bloat.

moistcity said:
Please do. I'd want to root my A720F and remove these annoying bloat.
Click to expand...
Click to collapse
You can try installing system mode supersu. It may install, but I will need to manually patch the boot image .
Make a backup of your boot and system partition then install the version of SuperSU below.
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Flash the patched boot image with ODIN or TWRP. If your device had encrption disabled you will need to flash no-verity-no-encrypt_ashyx again afterwards to disable encryption.
A720FXXU1AQC5_patched_root_boot
.

ashyx said:
You can try installing system mode supersu. It may install, but I will need to manually patch the boot image .
Make a backup of your boot and system partition then install the version of SuperSU below.
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Flash the patched boot image with ODIN or TWRP. If your device had encrption disabled you will need to flash no-verity-no-encrypt_ashyx again afterwards to disable encryption.
A720FXXU1AQC5_patched_root_boot
.
Click to expand...
Click to collapse
System mode SuperSU tries to install a lot shorter now, stops and reboots at "Installing" or something, too fast I can't read it.
I have also flashed the patched boot image and for some reason flashed no-verity-no-encrypt_ashyx again.
This is the recovery.log
pastebin.com/5JHqasFP

moistcity said:
System mode SuperSU tries to install a lot shorter now, stops and reboots at "Installing" or something, too fast I can't read it.
I have also flashed the patched boot image and for some reason flashed no-verity-no-encrypt_ashyx again.
This is the recovery.log
pastebin.com/5JHqasFP
Click to expand...
Click to collapse
That log contains nothing regarding supersu. You should go to ADVANCED> SAVE LOG after running supersu or does twrp automatically reboot?
Can you also open TWRP terminal and see if you get the ~# prompt then type getenforce and report the output.

ashyx said:
That log contains nothing regarding supersu. You should go to ADVANCED> SAVE LOG after running supersu or does twrp automatically reboot?
Can you also open TWRP terminal and see if you get the ~# prompt then type getenforce and report the output.
Click to expand...
Click to collapse
After typing getenforce, the terminal outputted "Permissive".
Does the recovery log overwrite itself when turning on the phone? If I can pull the recovery log right before it automatically reboots, is it possible to see the problem?

moistcity said:
After typing getenforce, the terminal outputted "Permissive".
Does the recovery log overwrite itself when turning on the phone? If I can pull the recovery log right before it automatically reboots, is it possible to see the problem?
Click to expand...
Click to collapse
The recovery log changes each time recovery is booted into.
If it's auto rebooting it would be difficult to catch it as it may not catch the error.
You can use the command below with ADB to try and grab it before it reboots.
Disable MTP then do:
adb devices
adb pull /tmp/recovery.log
There are also alternatives to get root.
You can try PHH Superuser.
https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
or MAGISK
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Managed to pull the recovery log before the phone reboots itself.
Code:
*****************
SuperSU installer
*****************
- Mounting /system, /data and rootfs
mount: mounting /dev/block/mmcblk0p25 on /data failed: Device or resource busy
2+0 records in
2+0 records out
2 bytes (2B) copied, 0.002642 seconds, 757B/s
3+0 records in
3+0 records out
3 bytes (3B) copied, 0.000393 seconds, 7.5KB/s
10+0 records in
10+0 records out
10 bytes (10B) copied, 0.000563 seconds, 17.3KB/s
0+0 records in
0+0 records out
0 bytes (0B) copied, 0.001912 seconds, 0B/s
/tmp/updater: line 971: /system/toolbox: not found
- Extracting files
Then it reboots back to twrp
---------- Post added at 07:10 AM ---------- Previous post was at 06:43 AM ----------
ashyx said:
There are also alternatives to get root.
You can try PHH Superuser.
https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
or MAGISK
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Rooted my phone at last using Magisk. Finally!
Magisk Manager confirms that the device is properly rooted and I have backed it up by using Root Checker Basic and by
Code:
adb shell
[email protected]:/ $ su
[email protected]:/ #
Thank you very much.
I am wondering however what are the differences between PHH and Magisk, it seems that Magisk is more popular so I strongly went for that first. Being someone who only knows SuperSU, how do these installers differ?
At this point do I still need to install the patched-root-boot and no-verity-no-encryption? I have installed no-verity-no-encryption before doing the root.

moistcity said:
Managed to pull the recovery log before the phone reboots itself.
Then it reboots back to twrp
---------- Post added at 07:10 AM ---------- Previous post was at 06:43 AM ----------
Rooted my phone at last using Magisk. Finally!
Magisk Manager confirms that the device is properly rooted and I have backed it up by using Root Checker Basic and by
Thank you very much.
I am wondering however what are the differences between PHH and Magisk, it seems that Magisk is more popular so I strongly went for that first. Being someone who only knows SuperSU, how do these installers differ?
At this point do I still need to install the patched-root-boot and no-verity-no-encryption? I have installed no-verity-no-encryption before doing the root.
Click to expand...
Click to collapse
Magisk and phh are both open source.
You don't need the root patch. If you want to keep your data unencrypted then you will need to flash the no-verity-no-encrypt_ashyx patch.

[PORT][UNOFFICIAL][TWRP Recovery][3.2.3]TWRP for ASUS Zenfone Max M2

Hii Guys, Please Read The Whole Thread
I'm Glad to Share my work with you all. This is port of TWRP for Max M2 from ASUS Nexus 7 3g
This is a First Build With minor Bugs.Max M2 Firmware has Forced Encryption so Each time you'll Wipe Data from TWRP It'll Again Become Encrypted. That's Why You Have to Flash Forced_encryption file.
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 this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Requirements:
ASUS Zenfone Max M2 with Unlocked Bootlader(You Can Unlock Bootloader Using This Tool https://forum.xda-developers.com/max-m2/development/unlook-bootloader-asus-zenfone-max-m2-t3886206
Windows/Linux
TWRP: TWRP 3.2.3
Decryption File: https://drive.google.com/open?id=1NhBSCbk4RHEqbo_zRrAvxkYyQO4oH80O
I Have Updated Decryption File Please Use The Updated One
Copy Decryption File to MicroSD or OTG
Please make a backup of you device
Instructions:
1.Reboot In Fastboot Mode
2.Flash Using This Command
Code:
fastboot flash recovery twrp.img
3.Boot into Twrp
4.Wipe Data
5.Flash the Forced_decryption.zip
3.Done
Known Bugs:
Touch Work Madly After Booting in TWRP (You Have to Lock And Unlock Twrp Using Power Key and It'll Work Flawlessly)fixed
ADB not Working
MTP not Working
You Tell Me

ashu7073 said:
Hii Guys, Please Read The Whole Thread
I'm Glad to Share my work with you all. This is port of TWRP for Max M2 from ASUS Nexus 7 3g
This is a First Build With minor Bugs.Max M2 Firmware has Forced Encryption so Each time you'll Wipe Data from TWRP It'll Again Become Encrypted. That's Why You Have to Flash Forced_encryption file.
Requirements:
ASUS Zenfone Max M2 with Unlocked Bootlader(You Can Unlock Bootloader Using This Tool https://forum.xda-developers.com/max-m2/development/unlook-bootloader-asus-zenfone-max-m2-t3886206
Windows/Linux
TWRP: https://drive.google.com/open?id=1NpI5NmQkmJcf9VnsOO9ouGAGAF7QVhwH
Decryption File: https://drive.google.com/open?id=1NhBSCbk4RHEqbo_zRrAvxkYyQO4oH80O
I Have Updated Decryption File Please Use The Updated One
Copy Decryption File to MicroSD or OTG
Please make a backup of you device
Instructions:
1.Reboot In Fastboot Mode
2.Flash Using This Command
3.Boot into Twrp
4.Wipe Data
5.Flash the Forced_decryption.zip
3.Done
Known Bugs:
Touch Work Madly After Booting in TWRP (You Have to Lock And Unlock Twrp Using Power Key and It'll Work Flawlessly)
ADB not Working
MTP not Working
You Tell Me
NOTE: Touch Don't Work Properly After Booting into Twrp So Immediately Lock And Unlock Twrp and it Will Work Flawlessly
Click to expand...
Click to collapse
I think you should move this thread to roms and recoveries section!!

Thanks bro..
Tested, all working fine except mentioned bugs.
Enjoying root & etc in my ASUS_X01AD.
---------- Post added at 03:26 PM ---------- Previous post was at 02:53 PM ----------
I am giving you a similer device default prop whose twrp is working fine with me.
you may rebuild twrp following this one.
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
ro.zygote=zygote32
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
ro.dalvik.vm.native.bridge=0
persist.sys.usb.config=adb
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LYZ28N
ro.build.display.id=omni_rimo02a-eng 5.1.1 LYZ28N eng.androidlover5842.20180325.003402 test-keys
ro.build.version.incremental=eng.androidlover5842.20180325.003402
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1.1
ro.build.version.security_patch=2015-11-01
ro.build.version.base_os=
ro.build.date=sun mar 25 00:34:33 IST 2018
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=androidlover5842
ro.build.host=androidlover5842-pc
ro.build.tags=test-keys
ro.build.flavor=omni_rimo02a-eng
ro.product.brand=Smartron
ro.product.board=rimo02a
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=Smartron
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8952
# ro.build.product is obsolete; use ro.product.device
ro.build.product=rimo02a
ro.product.model=T5524
ro.product.name=omni_rimo02a
ro.product.device=rimo02a
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=omni_rimo02a-eng 5.1.1 LYZ28N eng.androidlover5842.20180325.003402 test-keys
ro.build.fingerprint=Smartron/omni_rimo02a/rimo02a:5.1.1/LYZ28N/androidlover584203250034:eng/test-keys
ro.build.characteristics=default
ro.omni.device=rimo02a
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.alarm_alert=Argon.ogg
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.features=default
ro.kernel.android.checkjni=1
dalvik.vm.image-dex2oat-filter=verify-none
dalvik.vm.dex2oat-filter=interpret-only
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

Bug: Cannot boot to twrp. Can only flash it!

Soul Spark said:
Bug: Cannot boot to twrp. Can only flash it!
Click to expand...
Click to collapse
Are you stuck at asus splash screen or twrp?

ashu7073 said:
Hii Guys, Please Read The Whole Thread
Known Bugs:
Touch Work Madly After Booting in TWRP (You Have to Lock And Unlock Twrp Using Power Key and It'll Work Flawlessly)
ADB not Working
MTP not Working
You Tell Me
NOTE: Touch Don't Work Properly After Booting into Twrp So Immediately Lock And Unlock Twrp and it Will Work Flawlessly
Click to expand...
Click to collapse
Bug: Cannot boot to twrp. Can only flash it!
Bug: Cannot apply OTA update via TWRP.

Soul Spark said:
Bug: Cannot boot to twrp. Can only flash it!
Bug: Cannot apply OTA update via TWRP.
Click to expand...
Click to collapse
You can't apply OTA through TWRP

ashu7073 said:
Are you stuck at asus splash screen or twrp?
Click to expand...
Click to collapse
After entering
fastboot boot recovery.img
It stay stuck on booting and the phone remains in fastboot.
---------- Post added at 03:05 PM ---------- Previous post was at 03:03 PM ----------
ashu7073 said:
You can't apply OTA through TWRP
Click to expand...
Click to collapse
In some custom recoveries there are options to apply OTA via custom recovery. Example Red Wolf and PBRP for Zenfone Max Pro M2

Soul Spark said:
After entering
fastboot boot recovery.img
It stay stuck on booting and the phone remains in fastboot.
Click to expand...
Click to collapse
I also tried booting in twrp first but it didn't happen don't know why
But You can flash it using fastboot and it'll work
---------- Post added at 03:05 PM ---------- Previous post was at 03:03 PM ----------
In some custom recoveries there are options to apply OTA via custom recovery. Example Red Wolf and PBRP for Zenfone Max Pro M2
Click to expand...
Click to collapse
It's TWRP. Applying OTA update overwrite some files and root and twrp will break
I Have Updated TWRP touch is fixed now

I have put decryption.zip and magisk.zip inside twrp image.
Now no need of a otg and usb,
just
flash twrp, go to recovery
flash those two files which will be available from inside twrp.
enjoy root etc.

Thread Moved To Development Section

Thread closed at OP request