Develop Bugs

[17.12.2011][CF-Root v5.1] ICL53F - su+bb

This rooted kernel is for the "rooting beginners" and those who want to keep as close to stock as possible. CF-Root takes the kernel from an original firmware, and just adds root and busybox.
THIS IS NOT A ROM - it is only a modified kernel. You need to have the relevant firmware already on your device. You do NOT need to wipe anything for this patch. You DO need to read the instructions. PLEASE READ THE ENTIRE FIRST FEW POSTS!
Donate
There have now been nearly 1.000.000 downloads of CF-Root for various devices (see for example Galaxy S1, Galaxy Tab 7", and Galaxy S2), and many more if you include ROMs, kernels, etc that use it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user had donated me $1...
Main features
- The kernel is fully stock and taken from the original firmware, with just the following added:
- Superuser v3
- Busybox v1.19
- Custom boot / init scripts
- Insecure
Installation instructions
Please see the next post !
Recovery
Unlike CF-Root for various other devices, CF-Root for the Galaxy Nexus does not include any recovery, due to kernel and recovery being separate partitions on the device. This means you don't need to flash a recovery with your kernel.
Custom boot / init scripts
CF-Root will execute the following scripts if present, in the order listed:
- /system/etc/init.d/* (there can be many files here, no extensions! use "#!/system/bin/sh")
- /system/bin/customboot.sh
- /system/xbin/customboot.sh
- /data/local/customboot.sh
Please make sure you chown / chmod the scripts correctly so they can be executed. Pretty much root:root / 755.
Busybox
Busybox by default creates symlinks in /sbin. You can turn this off by executing the following:
adb shell setprop persist.busybox.nosymlink 1
And reboot your device.
Installing busybox over the included version
It is possible to install a custom busybox over CF-Root. However, this is not without risk. CF-Root makes heavy use of scripting, and many CF-Root scripts rely on the internal busybox version. If you do install a seperate busybox version (always use "stericson" installer!), install it to /system/xbin. Installing it to /system/bin will mess things up for sure. Even if you do that part right, it may still break CF-Root, so make sure to make a backup before trying.
How ?
I wrote my own toolchain to ease patching of initramfs, and that is what all this is based on. It is now used to make CF-Root for many devices!
Help! Which file do I use ?
Check Settings -> About phone -> Build number and find the matching download. YAKJU downloads are for GSM, MYSID downloads are for LTE.
Download
These are general-purpose downloads. See the posts following this one for the kernels.

Instructions
IMPORTANT: If your device is not yet OEM unlocked, both methods WILL WIPE your data ! If you are already OEM unlocked, this does not happen.
Flashing with ODIN
ODIN: Short
- Flash CF-Root-xxx-vX.X.tar (from the attached zip) as PDA in ODIN, without repartition. Done.
ODIN: Long
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached CF-Root-xxx-vX.X.zip
- (USB) Disconnect your phone from your computer
- Start ODIN
- Click the PDA button, and select CF-Root-xxx-vX.X.tar
- Put your phone in download mode (turn off phone, then hold volume-down + power to boot)
- (USB) Connect the phone to your computer
- Make sure repartition is NOT checked
- Click the START button
- Wait for the phone to reboot
- Done (if it took you more than 30 seconds, you need practise!)
Flashing with FASTBOOT
Fastboot: Short
- Flash boot.img (inside the tar inside the attached zip) as boot. Done.
Fastboot: Long
- Unzip the attached CF-Root-xxx-vX.X.zip
- Untar the CF-Root-xxx-vX.X.tar (found inside the zip)
- Find the boot.img file that you extracted
- (USB) Disconnect your phone from your computer
- Put your phone in fastboot mode (turn off phone, then hold volume-up + volume-down + power to boot)
- (USB) Connect the phone to your computer
- If your device is not yet OEM unlocked - NOTE: This wipes your data!
fastboot oem unlock
- (1) Flash the kernel (permanent):
fastboot flash boot boot.img
- Press the power button to boot
- or (2) Flash the kernel (temporary, applies root only):
fastboot boot boot.img

Downloads
Remember: I only have the GSM version, so the LTE versions are not tested by me !
CF-Root-GGN_YAKJU_ICL53F-v5.1.zip
CF-Root-GGN_MYSID_ICL53F-v5.1.zip

-- reserving yet another post --

I have the LTE SGN and my build number is ICL53F, not MYSID

theboo7 said:
I have the LTE SGN and my build number is ICL53F, not MYSID
Click to expand...
Click to collapse
And thus you should use:
CF-Root-GGN_MYSID_ICL53F-v5.1
and specifically not:
CF-Root-GGN_YAKJU_ICL53F-v5.1

omanomanom, tastes like bacon.
*installs*

finally the greatness has arrived on the galaxy nexus

So this changes/modifies the kernal to add root? What about OTA updates?
Sent from my Galaxy Nexus using XDA App

@chainfire
if my device is ITL41F and what can i do?
can i flash your other thread ICL53F rom via odin
and then flash cf-root kernel via odin again?

kangxi said:
So this changes/modifies the kernal to add root? What about OTA updates?
Click to expand...
Click to collapse
It should not interfere with OTA updates ...
leamoor said:
@chainfire
if my device is ITL41F and what can i do?
Click to expand...
Click to collapse
There's no ITL41F version yet, not sure if I'm making one. 53F is out already ...

Chainfire said:
It should not interfere with OTA updates ...
There's no ITL41F version yet, not sure if I'm making one. 53F is out already ...
Click to expand...
Click to collapse
Thanks for the quick response. Gonna try it when I get home.
Sent from my Galaxy Nexus using XDA App

Thanks for the quick response，but i'm not get the ITL53F yet
if my version is ICL53F,how can i made oem unlock？

leamoor said:
Thanks for the quick response，but i'm not get the ITL53F yet
if my version is ICL53F,how can i made oem unlock？
Click to expand...
Click to collapse
Use this command :
fastboot oem unlock
Also, @Chainfire, you should add a warning stating that "fastboot oem unlock" wipes data

Chainfire i knew you would come with a cr-root kernel...thanks!!!
Sent from my Galaxy Nexus using xda premium

Okay i did this, but my phone is now stuck on the Google Screen with a lock on the bottom that is unlocked.
When i go back to the bootloader and select Recovery Mode.
I get an Android with a "!"
Reboots back to the Google and nothing happens =(
The only way to start my Device is in CMD and using Superboot =S
Help!

Glad to see Odin works. I like having that safety net for when ROMs attack.

chainfire, je bent een baas! grtz uit haarlem.
pitje

cdesai said:
Use this command :
fastboot oem unlock
Also, @Chainfire, you should add a warning stating that "fastboot oem unlock" wipes data
Click to expand...
Click to collapse
get out noob this thread is sacred

Will this work with buildnumber ITL41F?
If not what should I do to make use of this kernel?
Many THanks in advance

Micromax a65 rooted!!

MICROMAX A65 ROOTED!!
[Sorry Guys!!!!]
As my father always says creating something is much less difficult that maintaining it,well this happened once again for me!!!.
I found maintaining this thread difficult I am officially announcing that you may stop expecting updates on this thread.Hats off to sssomnath474 to giving a new life to it!!!And it looks more informative as well!!
To add salt to injury A65 which my wife was holding is having issues with front speaker.Even after its trip back from the service centre gurus,it again managed to holdon the issue.I have given up on the micromax guys as of now.
GUYS,PLEASE FOLLOW THE BELOW THREAD BY sssomnath474 HENCEFORTH
http://forum.xda-developers.com/showthread.php?t=2501464
Recent activities as on 07 Aug 2013
--------------------------------------------------------------------------------------
1.Unlocked boot image and rooted it.
2.Install CWM.
3.Flashed firmware
4.sssomnath474 installed xloud,beats,bravia and confirmed it is working.
5.sssomnath474 also made few modification with UOT and came up with update.zip.
6.Right now we have unlocked V4 boot img which according to sssomnath474 has battery life updation.
7.I am studing as much time i can extract for an OC kernel and sssomnath474 is working on a rom.
8.As update by sssomnath474 this boot.img can have a better battery backup
http://www.mediafire.com/download/opweg2nwd0hk5dw/new_boot.img
let me know if you guys have access issues with any of the links or any of the link appears to be dead
9.Added a user guide how to flash the firmware.Hope it helps
http://www.mediafire.com/download/h2q51j8ovn1m1pc/Flash_firmware_config.pptx
10.you can use windows 7(you have to boot it in test mode and run the research downloader in administrator)
Thanks to sssomnath474 for the info
11.you can use unlock root as confirmed by sssomnath474
Thanks to sssomnath474 for this info
12.LIST OF STOCK IMAGES/PAC FILES FOR ALL MICROMAX MODELS
http://www.moulnisky.com/index.php?dir=Micromax
Thanks to sssomnath474 for this info
13.Heard from sssomnath474 that somebody has bumped imei while flashing.If any of you is stuck with the same issue i would suggest a complete firware flash following this tutorial,ONLY difference in this case will be DONT use my modified boot.img just flash the pac file as it is.
14.WoW! guys never thought this thread will get mushroomed like this....thanks to sssomnath474 ,shubhamym21 ,J.E.abhishek kumar and others for keeping things rolling
15.Some of you are facing weird problems with sims as my quick scan through the posts suggested,any updates on this guys?
I made changes to OP what sssomnath474 suggested, i am saying again all you need to do in the research downloader is select the pac file,uncheck calibration.
16.pradipkunwar51 has reported issue with docomo sim after flashing,i believe shubhamym21 already found a solution to it.Will Update the OP as soon as he comes back with comments
17.Critical Update:Tutorial & Tool if you messed up your EMI
Tutorial can be found here : China spd adnroid phone imei change just one click
& here is the download link : Android SPD IMEI Writing Tool_R1.5.3001 - Download - 4shared - maroof azam
Thanks to shubhamym21 for sharing the link and tutorial
18.Moved all updates under this activity section for better clarity
19.Adding Bravia engine zip
http://forum.xda-developers.com/showpost.php?p=44487763&postcount=138
Thanks to sssomnath474 for the link
--------------------------------------------------------------------------------------
Finally rooted my Micromax A65.Follow the guide carefully to avoid mistakes.I am not responsible for any physical/logical damage to you and your device .
Thanks to authors and their posts
http://forum.xda-developers.com/showthread.php?t=2165554 ElectronikHeart(Guru of spreadtrum)
http://forum.xda-developers.com/showthread.php?p=42693514#post42693514 Yekdall (confirming me unlocking the boot.img is key)
http://forum.xda-developers.com/showthread.php?p=42776196#post42776196 Intex12345(calibartion tabs needs to be unckecked in RD)
http://whiteboard.ping.se/Android/Rooting (for unlocking the boot.img)
Foreground
A Chaina re-branned phone
A fastboot mode
A useless recovery mode
A locked boot.img (thats why even chmod or simply pushing a su will not root the phone)
A IMEI number(which if you mess up after flashing,you will not get any radio signals)
1)First Unlock the Boot IMG
Before you proceed I will strongly recommend to download the tutorial guide ppt that you will find in Recent Activity list at the top of this post
You need to tamper permission after extracting the boot.img for this.No worry guys i have already done that for you .Just download the below file
Unsecured Boot Image
Now a bit critical part,read carefully .This unlocked image needed to be flashed to your device.For that you need research download and firmware pac file.
Download this to files from the below links
PAC versions & Tools Download
(pac file,driver,research download all included)
Download this drivers and install,after successfull installtion you will have(under device manager)
1.ABD interface
2.two COM ports
3.two emulators
If any of this having yellow sign it will not work.
Open research download
click on first button and load pac file
click on second button change baudrate to 115200,in calibration tab uncheck all.
For BOOT_IMG option browse and select the unlockedboot.img that you downloaded now.
plugin the usb cable(DON'T plugin the phone now)
click on play button
PRESS & HOLD VOLUME UP KEY and insert the usb cable,don't release the key.
Download should starts within 3 secs.If it doesn't then check the drivers carefully or reply to this thread with failures.
Once done unplug your phone and remove battery for 3 second
Reinsert battery and restart your phone.
YES!! you have successfully unlocked the boot.img
2)WiseMen Backup!!
First thing you should do before any tweaking and twisting save your back!!.Install CMW using the below method straight away and save your back.
1.Download .andriod.zip,extract it and save it under C:\Users\<computer name>\<paste it here>
http://www.mediafire.com/download/ga5tk2h89m41ddk/.android.zip
2.From your phone got to application-->developer option-->enable usb debugging
3.Now plugin your phone through micro usb cable.
4.Download this zip ,extract and place in under c:/<paste it here>
http://www.mediafire.com/download/s2as5grqceqtqq3/Android_Multi_tool.zip
5.Open a command prompt type
Code:
cd C:\Android Multi tool
C:\Android Multi tool>fastboot devices
20080823 fastboot
Note:you will NOT be able to proceed further if this doesnt shows up.Double check the andriod.zip has adb_usb.ini file.
Now we will flash a custom recovery image in fastboot mode.
Code:
C:\Android Multi tool>fastboot flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 10.487s]
writing 'recovery'...
OKAY [ 3.425s]
finished. total time: 13.918s
7.Reboot your phone.
8.Now got to CMW using Volume up + power button and do a backup.
3)Push superuser zip & ROOT!!!
This the easiest step among all of them.Download the below file,put it under sdcard and flash it through CMW.
http://www.mediafire.com/download/t55b6ebzvx9yf1f/update.zip
THAT'S IT you are rooted!!!
REMEMBER,PROBABILITY OF BRICKING IS MINIMUM AS I HAVE ALREADY DONE ALL THE TEST FOR YOU GUYS !!!.STILL IF ANYTHING GOES WRONG DONT PANIC,JUST FLASH A FIRMWARE AS MENTIONED ABOVE(point 1) EVENIF YOUR PHONE IS
TOTALLY DEAD .
----------------------------------------------------------------------------------------------
Please hit thanks if i you find this useful

No body tested it yet ?

question
sayannayas said:
No body tested it yet ?
Click to expand...
Click to collapse
what if i flash it with fastboot
---------- Post added at 01:07 PM ---------- Previous post was at 12:48 PM ----------
beacuse i just flashed it with fastboot and its not booting
waiting for 10 mints

recovery.img error
sayannayas said:
MICROMAX A65 ROOTED!!
Finally rooted my Micromax A65.Follow the guide carefully to avoid mistakes.I am not responsible for any physcial/logical damage to you and your device .
Thanks to authors and their posts
http://forum.xda-developers.com/showthread.php?t=2165554 ElectronikHeart(Guru of spreadtrum)
http://forum.xda-developers.com/showthread.php?p=42693514#post42693514 Yekdall (confirming me unlocking the boot.img is key)
http://forum.xda-developers.com/showthread.php?p=42776196#post42776196 Intex12345(calibartion tabs needs to be unckecked in RD)
http://whiteboard.ping.se/Android/Rooting (for unlocking the boot.img)
Foreground
A Chaina rebranned phone
A fastboot mode
A useless recovery mode
A locked boot.img (thats why even chmod or simply pushing a su will not root the phone)
A IMEI number(which if you mess up after flashing,you will not get any radio signals)
1)))First Unlock the Boot IMG
You need to tamper permssion after extracting the boot.img for this.No worry guys i have already done that for you .Just download the below file
http://www.mediafire.com/download/1c6r9cu9iwc3769/boot.zip
Now a bit critical part,read carefully .This unlocked image needed to be NAND flashed to your device.For that you need research download and firmware pac file.
Download this to files from the below links
http://forum.gsmhosting.com/vbb/f811/guide-all-micromax-root-clockworkrecovery-1627895/
(pac file,driver,research download all included)
<IT WILL ONLY WORK IN 32 BIT WINDOWS XP,VM ALSO FINE>
Download this drivers and install,after successfull installtion you will have(under device manager)
1.ABD inteface
2.two COM ports
3.two emulators
If any of this having yellow sign it will not work.
Open research download
click on first button and load pac file
click on second button change baudrate to 115200,in calibaration tab uncheck all.
For BOOT_IMG option browse and select the unlockedboot.img that you downloaded now.
plugin the usb cable(DONT plugin the phone now)
click on play button
PRESS & HOLD VOLUME UP KEY and insert the usb cable,dont release the key.
Download should starts within 3 secs.If it doesnt then check the drivers carefully or reply to this thread with failuers.
Once done unplugg your phone and remove battery for 3 second
Reinsert battery and restart your phone.
YES!! you have sucessfully unlocked the boot.img
2)))WiseMen Backup!!
First thing you should do before any tweaking and twisting save your back!!.Install CMW using the below method straight away and save your back.
1.Download .andriod.zip,extract it and save it under C:\Users\<computer name>\<paste it here>
http://www.mediafire.com/download/ga5tk2h89m41ddk/.android.zip
2.From your phone got to application-->developer option-->enable usb debugging
3.Now plugin your phone through micro usb cable.
4.Download this zip ,extract and place in under c:/<paste it here>
http://www.mediafire.com/download/s2as5grqceqtqq3/Android_Multi_tool.zip
5.Open a command prompt type
Code:
cd C:\Android Multi tool
C:\Android Multi tool>fastboot devices
20080823 fastboot
Note:you will NOT be able to proceed further if this doesnt shows up.Double check the andriod.zip has adb_usb.ini file.
Now we will flash a custom recovery image in fastboot mode.REMEMBER,PROBABILITY OF BRICKING IS MINIMUM AS I HAVE ALREADY DONE ALL THE TEST FOR YOU GUYS !!!.STILL IF ANYTHING GOES WRONG DONT PANIC,JUST FLASH A FIRMWARE AS MENTIONED ABOVE(point 1) EVENIF YOUR PHONE IS TOTALLY DEAD .
Code:
C:\Android Multi tool>fastboot flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 10.487s]
writing 'recovery'...
OKAY [ 3.425s]
finished. total time: 13.918s
7.Reboot your phone.
8.Now got to CMW using Volume up + power button and do a backup.
3))Push superuser zip & ROOT!!!
This the easiest step among all of them.Download the below file,put it under sdcard and flash it through CMW.
http://www.mediafire.com/download/t55b6ebzvx9yf1f/update.zip
THATS IT you are rooted!!!
REMEMBER,PROBABILITY OF BRICKING IS MINIMUM AS I HAVE ALREADY DONE ALL THE TEST FOR YOU GUYS !!!.STILL IF ANYTHING GOES WRONG DONT PANIC,JUST FLASH A FIRMWARE AS MENTIONED ABOVE(point 1) EVENIF YOUR PHONE IS
TOTALLY DEAD .
Please hit thanks if i you find this useful.:good:
Click to expand...
Click to collapse
finally i rooted my cellphone thank u guys n thank u xda

sssomnath474 said:
what if i flash it with fastboot
---------- Post added at 01:07 PM ---------- Previous post was at 12:48 PM ----------
beacuse i just flashed it with fastboot and its not booting
waiting for 10 mints
Click to expand...
Click to collapse
You should not flash anything before you have unlocked the boot.img.It comes with a locked boot so flashing through fastboot may not work.
First thing that you should do now is stage up a windows xp with the drivers that i have linked here.connect your phone with research download and do a firmware flash.This will recovery your phone to its orginal state.Then follow my steps from the start(pls dont skip)

navi_5886 said:
i have done the same but when i go to recovery option it says cannot mount e:
Click to expand...
Click to collapse
you should have micro sd card,and it should be in fat32 formatted.Better if you backup your data in sdcard,format it with fat32 and then place only the update.zip

sayannayas said:
You should not flash anything before you have unlocked the boot.img.It comes with a locked boot so flashing through fastboot may not work.
First thing that you should do now is stage up a windows xp with the drivers that i have linked here.connect your phone with research download and do a firmware flash.This will recovery your phone to its orginal state.Then follow my steps from the start(pls dont skip)
Click to expand...
Click to collapse
ok downloading windows xp..good thing is i'm not scared
well do u have facebook id?

sssomnath474 said:
ok downloading windows xp..good thing is i'm not scared
well do u have facebook id?
Click to expand...
Click to collapse
Dont get me wrong but i think it is better to log your errors here as it might help others as well as me to correct the OP.
Once you have the setup use exact set of drivers and pac file that i linked in this thread.remember if you have a successful driver installation then you will have at least(under device manager)
2 new COM ports
2 emulators
I am working on capturing few snapshots or a demonstration guide,it will take time as i recently lost my bag-pack,will update with videos once i stage up.

sayannayas said:
Dont get me wrong but i think it is better to log your errors here as it might help others as well as me to correct the OP.
Once you have the setup use exact set of drivers and pac file that i linked in this thread.remember if you have a successful driver installation then you will have at least(under device manager)
2 new COM ports
2 emulators
I am working on capturing few snapshots or a demonstration guide,it will take time as i recently lost my bag-pack,will update with videos once i stage up.
Click to expand...
Click to collapse
thankx bro..it will help more if you give screenshots

sayannayas said:
Dont get me wrong but i think it is better to log your errors here as it might help others as well as me to correct the OP.
Once you have the setup use exact set of drivers and pac file that i linked in this thread.remember if you have a successful driver installation then you will have at least(under device manager)
2 new COM ports
2 emulators
I am working on capturing few snapshots or a demonstration guide,it will take time as i recently lost my bag-pack,will update with videos once i stage up.
Click to expand...
Click to collapse
need a help do i only check boot_img or i check all files?

sssomnath474 said:
need a help do i only check boot_img or i check all files?
Click to expand...
Click to collapse
check all files in main page,but for boot_img browse a select the unlocked boot.img that i have linked in this thread.The idea is to flash the unlocked boot.img instead of stock boot.img. Uncheck all in calibration page.Keep baudrate 115200
Also download the ppt that i just added.It may help you. Don't give up,setting the drivers will take trails & errors but i guarantee you the success

sssomnath474 said:
need a help do i only check boot_img or i check all files?
Click to expand...
Click to collapse
sucsessfully flashed with origianal system file..and one thing more it worked in windows 7 64 bit too

sssomnath474 said:
sucsessfully flashed with origianal system file..and one thing more it worked in windows 7 64 bit too
Click to expand...
Click to collapse
Great news buddy.If you have used my unlocked boot.img while flashing then rest of the steps will be a breeze to you.Install CWM and take a full back up.Then flash the update.zip,thats it.

sayannayas said:
Great news buddy.If you have used my unlocked boot.img while flashing then rest of the steps will be a breeze to you.Install CWM and take a full back up.Then flash the update.zip,thats it.
Click to expand...
Click to collapse
well thankx for boot image and help device is rooted
but this can be done in other way to
1.you can use windows 7(u have to boot it in testmood and run the research downloader in adminstor)
2.just use unlock root
thats it
thankx man.pls give ur facebook id

sssomnath474 said:
well thankx for boot image and help device is rooted
but this can be done in other way to
1.you can use windows 7(u have to boot it in testmood and run the research downloader in adminstor)
2.just use unlock root
thats it
thankx man.pls give ur facebook id
Click to expand...
Click to collapse
Mentioned your updates in OP.Hope you dont mind

sayannayas said:
Mentioned your updates in OP.Hope you dont mind
Click to expand...
Click to collapse
ok ok
well making some customizing themes in UOT cooked kitchen.hope it will work

sssomnath474 said:
ok ok
well making some customizing themes in UOT cooked kitchen.hope it will work
Click to expand...
Click to collapse
Wow! that will be really nice...hope you will share those with us

sayannayas said:
Wow! that will be really nice...hope you will share those with us
Click to expand...
Click to collapse
check it out

need pac file...!!!!
sssomnath474 said:
thankx bro..it will help more if you give screenshots
Click to expand...
Click to collapse
can anyone upload only pac file for mmx a65 !!!!! please......!!!!""

sssomnath474 said:
check it out
Click to expand...
Click to collapse
WOW looking nice...waiting for the release
Also if you are maintaining your own a65 thread for customs roms,suggest you to cross link with mine(vice versa) and keep track for both the threads

[TWRP][any G4][BL LOCKED] TWRP-in-FIsH for all LOCKED G4 devices

TWRP on locked devices is impossible right?
Oh no wait there are hacks up to KK which work but I couldn't find anything for LL (sorry if I missed something) and so nothing for the G4
Here is where the FIsH steps in
{
"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"
}
FIsH: [F]luffy [i]ncredible [s]teadfasterX [H]ijack​
FIsH is different from Safestrap or other hijacks because it should be understood as a kind of framework for any boot image you want to boot.
FIsH will not harm the Android boot chain!
It is NOT multirom
It is NOT efidroid
It is NOT Safestrap
It is NOT twrp.
.... but FIsH can boot any of the above. U got it? FIsH is the hack to boot whatever you want.
Will FIsH void your warranty? Not more or less then rooting your device.
Will FIsH unlock your bootloader? No read again.
Is there a risk with FIsH? For example could it soft-brick my device? Well.. absolutely! Safe is the death only. There are always risks especially for untested devices. I do all I can to keep this risk as low as possible and I provided a way to get out of bootloops but again you will get no guarantees here and elsewhere.
.. and it is more then just a hack for the G4 (any model) it is a hack for ALL devices of ANY vendor! wtf? yes.
Sure you have to met the pre-requirements and there has to be done some things to get it ported but those are straight forward.
Go to IRC channel #androidfish if u can't wait but I will publish a public porting guide when it is ready.
Are there plans to make more out of it for the G4? Absolutely. I'm currently working on an "efidroid in FIsH" version which will let you flash & boot (hopefully) any custom ROM u like.
ALL DETAILS ABOUT HOW FIsH WORKS HAVE BEEN RELEASED IN ANOTHER THREAD (check my signature).
So going back to topic. This is:
TWRP in FIsH for the LG G4 (any model) - Bootloader LOCKED
Do you have a bootloader unlocked device?
If the answer is YES: you don't need it
Do you have a bootloader locked device and want TWRP?
If the answer to BOTH is YES. you need it. you can't install TWRP on a locked device.. up to now. FIsH allows you to do so.
If your question is: Can this ENABLE root for my device?
NO! you actually NEED root to activate TWRP for your device with this method.
Important: Here are the pre-requirements you have to met!
If you can't get them:
Close this page and FORGET it (until the day you may met those reqs)!
Requirements!
root by SuperSU >=v2.76 (greater or equal v2.76) (atm this means you have to downgrade/install LL. It also means that you have to upgrade your SuperSU to this version by e.g. FlashFire if you have a lower version installed!)
you have to be able to disable SELinux in your booted Android (which should be the case when you have a full rooted device)
Those above are hard facts so it may never work with MM. That also means if MM can get fully rooted by SuperSU and you can use "setenforce 0" the method should work there as well!
Before you think about downgrading to LL read about ANTI-ROLLBACK protection some LG devices and MM versions may have!
Anti-Rollback means you CAN NOT downgrade - it would brick your device.
I will NOT provide downgrading guides there are plenty of them so search and read.
If you can not meet ALL of the above 2 requirements lay down and cry. For the others: calm down and read on!
You can test requirement 2 (disable SELinux) by:
adb shell
su
setenforce 0
getenforce
-> you should see "Permissive" as a result. If you see "Enforcing" or error messages you may doing something wrong or it just do not work for you.
Limitations!
Keep in mind what I said above: FIsH does NOT unlock your bootloader.
That means with TWRPinFIsH you can NOT:
Install a custom ROM like CM/Lineage (this will modify boot = soft brick. for this u need "efidroid in FIsH" - coming soon)
Install a custom Kernel (this will modify boot = soft brick)
Install a custom recovery (this will modify recovery = may soft brick)
In short: nothing which modifies boot or recovery partitions.
You can of course flash everything which is modifying /system /data only (e.g. xposed,...)
That means you could install even a custom ROM which works with the stock kernel so with unmodified boot image. Let's say the creator of imperium or genisys provide a release without the containing boot image. You could flash it..
State / Roadmap
FULL takeover/hijack of boot -> DONE (the modifications required are not voiding the Android boot signing chain!)
replace RAM disk -> DONE
boot own RAM disk (TWRP!) -> DONE (atm TWRP 2.8.7-0) <-- TWRP-in-FIsH v1.0 private BETA
Upgrade bundled TWRP to latest version -> DONE (TWRP 3.1.0-0) <-- TWRP-in-FIsH v1.0 final release
Download
READ THE REQUIREMENTS above before proceeding!
Then UNDERSTAND the requirements before proceeding! <-- omg this is crucial important!!!! Ensure that you really do not skip this step!
READ THE LIMITATIONS above before proceeding!
Then UNDERSTAND the limitations before proceeding! <-- omg this is crucial important!!!! Ensure that you really do not skip this step!
... and NEVER ask for ETA's!
if you can say:
Yes! I have read and totally understood the limitations AND the requirements!
then proceed. Otherwise read again until you got it.
Keep in mind that this is a HACK. It may soft-brick your device. you have been warned!
The concept is the same for all models but again no guarantees here for anything.
There is ALWAYS a risk and you should better backup what you do not want to loose before starting downloading this.
Go to the DOWNLOADS tab in this thread.
TWRP-in-FIsH is now integrated into my TWRP build server and so whenever a new change happens in TWRP you will get the same automatically on next build. This way it is much easier to release new TWRP versions made for FIsH.
From now on you will find nightlies (untested automatic builds) here:
Jenkins build status
Nightlies download server
Installation (Linux)
You can just install any newer version over an old one.
boot Android and connect USB cable
download the newest version to your PC and open a terminal in that directory
tar xzf TWRPinFIsH*.tgz (tar xzf TWRP-in-FIsH*.tgz since v2.0)
cd openFIsH (cd android_FIsH since v2.0)
./install.sh
check the output of that script. you should not see any errors there (hopefully)
Installation (Android / no PC)
Requirements:
TWRP-in-FIsH v4.2 or higher!
BusyBox pre-installed (e.g.: with this app )
You can just install any newer version over an old one.
Thanks to @ReeS86 starting from v4.2 on TWRP-in-FIsH has an enhanced installer which can run without any PC - directly on your Android device!
It would be nice if you could give him a thx click (here) for his contribution !
Bring TWRP-in-FIsH to your Android device
Example-1 with any PC (windows, linux, ...): adb push TWRP-in-FIsH.tgz /sdcard (replace TWRP-in-FIsH.tgz this with the real file name)
Example-2 within an Android Terminal:
cd /sdcard
wget http://full-URL-to-file (replace full-URL-to-file with the real direct download link)
Example-3 with just a browser: well just download it.. but remember where it gets saved!
extract it
Example from within Android Terminal:
cd /sdcard (or the folder where you have downloaded TWRP-in-FIsH)
tar xzf TWRP-in-FIsH.tgz (replace TWRP-in-FIsH.tgz this with the real file name)
run the installer (but do it correctly)
Example from within Android Terminal:
su
cd /sdcard/android_FIsH
sh ./install.sh (using sh is absolutely important otherwise it will fail)
done
Installation (Windows)
If none of the above methods is working for you: use FWUL
First run (no PC required)
This FIsH gets installed PERMANENTLY! That means:
You can boot up TWRP the same way as described here again without re-installing.
If you re-install your STOCK image you have to re-install TWRPinFIsH as well.
reboot Android
you should now see: LED goes from blue to GREEN
NOW directly when u see this GREEN LED press VOLUME DOWN and do NOT release
wait until the device vibrates and the LED changed to RED. Then release the Volume Down button.
Wait until FIsH completed and TWRP should be shown --> This means FIsH has done it's job well!
This is a good time to do a full backup isn't it ? Manually mount the SYSTEM partition as it gets not auto mounted atm and do a full backup
reboot from here (safely ignore the msg "no OS installed" and reboot anyways) and you should see Android booting (hopefully ... if not see bottom)
Daily Usage (no PC required)
reboot Android
you should now see: LED goes from blue to GREEN
NOW directly when u see this GREEN LED press VOLUME DOWN and do NOT release
wait until the device vibrates and the LED changed to RED. Then release the Volume Down button.
Wait until FIsH completed and TWRP should be shown --> This means FIsH is doing it's job still very well
AGAIN: keep your mind up! You HAVE to ensure that whatever you do and whatever you flash -> NEVER TOUCH BOOT/RECOVERY! If you flash a ZIP ensure first that it do not modify them! Otherwise you WILL softbrick. You have been warned (several times now)
FIsH helpers
If you just want to reboot directly from within Android check out these:
Thanks to @sdembiske who has onboarded the developer @AntaresOne we have an option to reboot into FIsH very comfortable now!
Check it out here: QuickReboot App
Trouble / Bootloop fix
if you encounter a bootloop (should never happen but who knows) you have 3 choices at least:
Option 1a: (TWRP-Bootloop) Within TWRP open Advanced -> File Manager -> Goto: /system/su.d and click "select" button -> Delete
Option 1b: (TWRP-Bootloop) From your PC: adb shell rm -rf /system/su.d/
Important: Catch the fish log (see next topic)
Option 2 (this works also for a bootloop without twrp): boot into download mode and use LGLaf to get a shell
then:
setenforce 0 <-- if that doesn't work you may have to do a FULL restore to stock
mount -oremount,rw /system
rm -rf /system/su.d/
reboot. You are out of the bootloop.
Important: Catch the fish log (see next topic)
Option 3: Last resort: Reflash STOCK. sorry.. there is always a risk..
Catch the FIsH logs
reboot back to Android and catch the fish log (IMPORTANT!):
adb shell "su -c cat /cache/fish/fish.log"
adb shell "su -c cat /cache/fish/fish.log.old"
Upload it to https://paste.omnirom.org and paste the link in the IRC channel (see next topic)
Support / IRC Channel
IRC means Internet Relay Chat and you will get best support there only.
Choose how to get in:
PC (HexChat and Pidgin are only 2 of them! This list is not complete!)
Android (Yaaic, AndChat, HoloIRC, AndroIRC are only a few of them! This list is not complete!)
Web (KiwiIRC-Web,FreenodeWebchat])
When you have to choose a channel it is: #Carbon-user
When you be asked for a server network choose: freenode
Known issues (may never get fixed)
Due to the fact that TWRPinFIsH is a brutal hijack of the booting process several things may not work as expected.
This will normally not harm anything but you have to know about.
System IMAGE backup:
Using this new option is a bulletproof method to backup and restore in TWRP-in-FIsH because you have to keep in mind that FIsH is a giant and brutal hack and even when a usual backup & restore is proven to work fine I would recommend to use both backup methods - if you can.
HINT: This method requires an ext4 or exfat partition on your external SD card otherwise image backups will fail due to the file size.
@sdembiske reports success using the internal storage as target for the backup but if you do this keep in mind that you have to move that backup to your PC manually to ensure you have it by hand for the worst case.
ZIP / ROM flashing:
omg really you wanna hear that again? OK: DON'T TOUCH BOOT / RECOVERY. And you be safe.
When you try to install a ROM it will modify at least BOOT. That means soft-brick!
When you try to install a custom Kernel.. omg really? It will definitively SOFT-BRICK! Maybe you should read the limitations again??
When you try to install a ZIP like xposed, supersu, Vipermod and others ensure that those are not modifying BOOT or RECOVERY partitions. For those mentioned it would be very unlikely but who knows.
When you find a stock based ROM which is not modifying boot you can flash it. But ensure that it does not modify anything on boot!!! You could ask the devs of imperium etc if they can provide such a zip..
SYSTEM partition (since v2.0: may be not a restriction on your device model!):
when you boot into TWRPinFIsH you may see an error message regarding the fact that /system cannot be mounted.
you can mount /system manually without a problem - BUT - it will work only if you do NOT select "mount system read-only". It has to be unchecked to work.
after you have mounted /system manually and you want to take a backup you may see "0 bytes". Just press refresh and the size will be updated. If not: Do you have mounted it correctly (see above).
FIRMWARE partition (since v2.0: may be not a restriction on your device model!):
cannot be mounted - even not manually. You have to live with it.
Double Tap to wakeup (in TWRP):
You may heave seen/heard that this works in the official / usual TWRP for the G4 for unlocked devices. Unfortunately this cannot work in TWRP-in-FIsH due to the nature of this hijack. You have to live with it.
Installing more than 1 ZIP at a time (may be not a restriction on your device model!):
It is not possible to install more than 1 ZIP at the same time. TWRP gives you the option to install multiple ZIP files but the problem is you have to re-mount /system after each ZIP flashing. This is due to a problem with mounting /system readonly and most ZIPs will exactly try to do this when they finished their work - leaving you with an unmounted /system.
This will be not the case for every ZIP combination - so it is possible that you can flash some ZIPs at the same time while others not.
atm I believe you have to live with it.
Credits (without them - no TWRP-in-FIsH!!!)
If you feel that someone / you is missing on this list lemme know!
Chainfire for SuperSU! This is the main part of FIsH!
TeamWin for TWRP of course!
@cray_Doze, @dssmex and @KeiranFTW for their hijack implementations which given me many input (e.g. https://forum.xda-developers.com/showthread.php?t=2608408)
@Aaahh for his great first steps to a G4 hijack -> His work had given me the motivation back to continue when I was about to stop all this
@dibbled for creating the android FIsH logo
steadfasterX for being steadfast!
@jasonlindholm for your donation it was highly appreciated!
XDA:DevDB Information
TWRP-in-FIsH_LGG4, Tool/Utility for the LG G4
Contributors
steadfasterX, Aaahh, TheMadScientist420, KeiranFTW, cray_Doze, dssmex, TeamWin, ChainFire, the_naxhoo, SimoxTav, Rees86, uio88, sdembiske, jasonlindholm, ... and all new other contributors who gave me feedback for this!
Source Code: https://github.com/Carbon-Fusion/android_FIsH
Version Information
Status: Stable
Current Stable Version: 4.2
Stable Release Date: 2017-06-21
Current Beta Version: 5.0
Beta Release Date: 2017-12-19
Created 2017-03-14
Last Updated 2017-12-19

List of confirmed devices (as of 2017-06-04)
If you own a device missing on this list - let me know and I will add it here.
F500L Korean variant - locked (Thanks @Syntist)
H810 - locked (Thanks @shane87)
H812 - locked (Thanks @ReeS86)
H815 International - unlocked (Thanks @steadfasterX yea its mine and i have no locked device to test with That's why i needed ur help. but i test with PURE stock and without touching the boot chain so its similar to locked devices.)
H815 EUR - locked (Thanks @uio88)
H815P - locked (Thanks @KnightOdin)
H815T - locked (Thanks @the_naxhoo)
H815L - locked (Thanks @foxyfoxyblah)
H818P - locked (Thanks @SimoxTav, @alitavas)
LS991 Sprint - locked (Thanks @TheMadScientist420)
VS986 - locked (Thanks @g_ding84)
List of confirmed flashing experiences (as of 2017-05-19)
If you tested a ZIP missing or unknown on this list - let me know and I will add/update it here. Write the exact version tested would be helpful as well.
Xposed - confirmed to work (tested: Xposed version 87 (SDK 21). THANKS for your report @g_ding84, @the_naxhoo, @KnightOdin, @shane87)
Viper4Android - confirmed to work (tested: Viper4Android 5.4 stock zip with Dolby Atmos. THANKS for your report @g_ding84 , @the_naxhoo, @SimoxTav)
SuperSU - confirmed to work (tested: v2.79. Thanks for reporting @g_ding84)
A.R.I.S.E - confirmed to work (tested: v.2.94 -> Am3d Eq, Viper4arise, Viper4Android Xhifi, Esira. Thanks for your report @alitavas
Android O emoji package - confirmed to work (thanks for your report @alitavas)
Editing system/build.prop - confirmed to work --> read carefully HOW (thanks for the howto & report @sdembiske )
Xtreme music 9.2 - confirmed to work (thanks for your report @jason_l367)
ANY OTHER ZIP - unknown ----> Please report back if you have flashed one missing here

Releases
TWRP-in-FIsH v5 (5.0)
Released: 2017-12-19
Download: Go to the Downloads tab
Changelog for FIsH: previously used version <---> this version
Changelog for TWRP-in-FIsH device tree: previously used version <---> this version
Changelog for:
- TWRP v3.2.0-0
- TWRP v3.2.1-0
Summary changelog (read the above FULL changelogs for details!):
new TWRP version
all important fixes from the main TWRP releases like corrected time and EFS backup, added Bootloader backups etc.
Many enhancements and fixes in FIsH, e.g. enhanced and fixes issues in the installer and qseecomd (device encryption) added to the brand new exclude service option
Everything is better now
Old releases:
TWRP-in-FIsH v4 (4.2)
Released: 2017-06-21
Download: Go to the Downloads tab
Changelog for FIsH: previously used version <---> this version
Changelog for TWRP-in-FIsH device tree: previously used version <---> this version
Changelog for TWRP: v3.1.1-0
Summary changelog (read the above FULL changelogs for details!):
Installer is now able to detect and run from within Android* (read the NOTES in the OP - topic "Installation (Android / no PC)"!)
Added the option to backup /system as an IMAGE* (read the following HINT!)
Using this new option is a bulletproof method to backup and restore in TWRP-in-FIsH because you have to keep in mind that FIsH is a giant and brutal hack and even when a usual backup & restore is proven to work fine I would recommend to use both backup methods - if you can.
HINT: This method requires an ext4 or exfat partition on your external SD card otherwise image backups will fail due to the file size.
@sdembiske reports success using the internal storage as target for the backup but keep in mind that if you do this you have to move that backup to your PC manually to ensure you have it by hand for the worst case.
Everything is better now
(.... TWRP updated, many FIsH improvements, added an option to backup /system as image,... read ALL the above changelogs!)
TWRP-in-FIsH-v3_LGG4_LL
Released: 2017-04-16
Download: here
Changelog: on github
Summary:
Big speed improvements
adding model detection as property (ro.product.detection -> should be "success")
fixing unify detection
adding all known devices to unification
- these both above will fix issues where your device was not detected correctly in TWRP and fails to install a ZIP which requires this!
Installer:
./install.sh --check will give you the option to check if TWRP-in-FIsH works for your or not - without changing anything on your device.
TWRP-in-FIsH-v2.0_LGG4_LL
(as far as im able to remember.. i have changed so many things inside..)
Released: 2017-03-24
Changelog: on github
Summary:
TWRP-in-FIsH now has a meaningful package name (TWRP-in-FIsH-v2.0-BETA1_LGG4_LL.tgz) which reflects all required information
The installer is checking for the SDK level now instead of the Android release version! This means ANY Lollipop version will work without modifications of the installer
new: completely overworked WIDE parts of FIsH
In order to be more easy portable all variables users may need to adjust are moved to FIsH.porting
while FIsH.me contains global variables for FIsH a user/dev normally would NOT change.
The log has been enriched with some more useful information
The stopping of android services is now more aggressive
Apropos aggressive: now we use fuser to kill ALL processes before trying to unmount a disk (excluding init and ourself)
Another porting stuff was added: we extract the FISHFOOD but WITHOUT a possibly existing file </init>. When you prepare your own ramdisk it may or may not contain a file /init but we do not want to overwrite the current running /init by just cpio yet.
The reason is: it makes a difference in the Linux world to use cp or mv or cpio > to overwrite!
The short version: using mv is the best choice here. So we extract first without /init (if there is one) and then extract /init ONLY but to a different directory. Afterwards we use mv to overwrite the current /init with either an extracted /init or your own init name configured by the new FOODBIN variable.
Unfortunately this has not that positive effect I hoped but I leave it there because it is the way it should be done nevertheless.
Now FIsH also:
- checks the exec bit before it tries to start it! Im still thinking of adding a reboot if not.. but this could cause bootloops.. on the other hand doing nothing will leave the device in a unusuable state.. well it should more or less never happen though but..
- save the current SELinux mode
- trying to restore the saved SELinux mode when something goes wrong (at the end this will make no sense but it doesnt hurt)
- umounts when a mount point is mounted ONLY
Besides that FIsH now comes with callmeFIsH - a caller script which gets executed at very first.
The only task callmeFIsH has is to prepare the whole FIsH to get started out of /system and then starting FIsH from /res. After this it immediately exists to not keep open tasks on /system.
Also new are some parts of the installer e.g. starting adb server first and then wait for a connected device before continue the installation.
The installer is keeping track of an older FIsH install and removes the previous one before as well
The installer also now giving a hint that you may have to change to PTP mode on your G4 to get detected
For completeness: Same TWRP version inside so nothing changed here..
During these changes I have renamed the package folder from openFIsH to android_FIsH. Please keep this in mind when you extract the FIsH
So after you extract the BETA package you have to do
"cd android_FIsH"
instead.
TWRPinFIsH_v1.0
Released: 2017-03-18
Changelog:
first public release
.

As current. To further op. When released remeber bl is still locked do not modify recovery and or boot partitions. Will throw secure boot errors done tried and found out. Was able to restore orig boot and recovery images.
On ls991.
So lets get our flash on. I wanna see some good clean flashing and no hits below the bootloader

TheMadScientist420 said:
As current. To further op. When released remeber bl is still locked do not modify recovery and or boot partitions. Will throw secure boot errors done tried and found out. Was able to restore orig boot and recovery images.
On ls991.
So lets get our flash on. I wanna see some good clean flashing and no hits below the bootloader
Click to expand...
Click to collapse
Well .. Correct. For me it is totally clear but this will be not for the average user maybe.. I will add it to the OP. Thx
Sent from my LG-H815 using XDA Labs

Thanks for all your effort with this development. So, i understand that we can boot into TWRP and we can backup and restore our system, right? But we can also flash roms, mods or kernels without unlock BL?
Again, thanks for your time on this project, this are really big news for our device!

Jkmoran said:
Thanks for all your effort with this development. So, i understand that we can boot into TWRP and we can backup and restore our system, right? But we can also flash roms, mods or kernels without unlock BL?
Again, thanks for your time on this project, this are really big news for our device!
Click to expand...
Click to collapse
2 posts up.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
Jkmoran said:
Thanks for all your effort with this development. So, i understand that we can boot into TWRP and we can backup and restore our system, right? But we can also flash roms, mods or kernels without unlock BL?
Again, thanks for your time on this project, this are really big news for our device!
Click to expand...
Click to collapse
Yes and no. I flashed viper 4 android. But because of signed bl. Any recovery or modified boot image will not work just yet. Still a wip.

Reserved. I hope to install this in my H815p soon...

TheMadScientist420 said:
2 posts up.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
Yes and no. I flashed viper 4 android. But because of signed bl. Any recovery or modified boot image will not work just yet. Still a wip.
Click to expand...
Click to collapse
Hey i just want to say thanks for acknowledging thqt i helped you more than what happens in the sprint thread. I have a post 2400 views where i tore my g4 down 3 days after purchase to show a thermal paste mod. 2400 views and 1 thanks. Id thank u properly but unfort ive hit my 8 thanks a day limit
---------- Post added at 07:25 PM ---------- Previous post was at 07:22 PM ----------
Newmak said:
Reserved. I hope to install this in my H815p soon...
Click to expand...
Click to collapse
It will come in due time. The third release was sent out in one day. Progress is moving rite along my friend.
Some of us have been waiting since day one. I have about 15 months. Or nov 15 we are all anxious for offic release. And please make sure to give the man his cr3dit where due. Took time out of his day to do a team view session to test on mine at like 5 am this mornin. Some of the greatest minds have not been able to do this. And now look. Lol all the nay sayers
---------- Post added at 07:30 PM ---------- Previous post was at 07:25 PM ----------
Newmak said:
Reserved. I hope to install this in my H815p soon...
Click to expand...
Click to collapse
sorry i didnt actually answer ure ?
this should work on all g4s and possibly many other lgs and or devices

I have only one question. Will this TWRP be able to modify boot partition as well? Isn't that the whole point of the locked bootloader? If it will be able to modify any partition, it is a big, big win for us.

tmihai20 said:
I have only one question. Will this TWRP be able to modify boot partition as well? Isn't that the whole point of the locked bootloader? If it will be able to modify any partition, it is a big, big win for us.
Click to expand...
Click to collapse
No read the OP again (wait for efidroid-in-FIsH).

tmihai20 said:
I have only one question. Will this TWRP be able to modify boot partition as well? Isn't that the whole point of the locked bootloader? If it will be able to modify any partition, it is a big, big win for us.
Click to expand...
Click to collapse
Lol op and about 4 or 5 posts up. Same ? Just asked.
Either was locked bl or not this is a majpr victory for the g4. They said it couldnt be done and

Hopefully You could port this also to G Flex 2?

dadaa1 said:
Hopefully You could port this also to G Flex 2?
Click to expand...
Click to collapse
he has stated should work on any android device running loli as long as u meet the prequisites
root and kernal set to permissive if he doesnt some one probly could adapt it from here no prob once its offic released
---------- Post added at 06:36 AM ---------- Previous post was at 06:04 AM ----------
dont know how much feed back uve been gettin but figured id chime in again
so after all night playing lol still sick as a dog cant sleep about 4 hours on 2 days feel high and drunk lol
ive do have to mount system everytime i load twrp to backup restore or flash but i flashed viper flashed xposed again just to check it out
bricked about 10 times and have restored perfectly everytime.
bricks my own fault trying and testing most def incompatible mods and fixes but so far through every brick recovery is holding strong and steady havnt installed the beta 3 yet
should i is much changed from there?

TheMadScientist420 said:
he has stated should work on any android device running loli as long as u meet the prequisites
root and kernal set to permissive if he doesnt some one probly could adapt it from here no prob once its offic released
---------- Post added at 06:36 AM ---------- Previous post was at 06:04 AM ----------
dont know how much feed back uve been gettin but figured id chime in again
so after all night playing lol still sick as a dog cant sleep about 4 hours on 2 days feel high and drunk lol
ive do have to mount system everytime i load twrp to backup restore or flash but i flashed viper flashed xposed again just to check it out
bricked about 10 times and have restored perfectly everytime.
bricks my own fault trying and testing most def incompatible mods and fixes but so far through every brick recovery is holding strong and steady havnt installed the beta 3 yet
should i is much changed from there?
Click to expand...
Click to collapse
Thanks for ur ongoing support here. please always go to IRC if possible:
PC (HexChat and Pidgin are only 2 of them! This list is not complete!)
Android (Yaaic, AndChat, HoloIRC, AndroIRC are only a few of them! This list is not complete!)
Web (KiwiIRC-Web,http://webchat.freenode.net/?channels=androidfish)
Whenever you have to choose a channel it is: #androidfish
When you be asked for a server network choose: freenode
.

Just wanted to let you know the current device list.
If you own a device missing in this list send me a PM with subject FIsH !
Please do not write me if your device is shown here already!
List of confirmed devices (as of 2017-03-15)
H815 International - unlocked (Thanks @steadfasterX yea its mine and i have no locked device to test with That's why i needed ur help. but i test without touching the boot chain so its similar to locked devices.)
LS991 Sprint - locked (Thanks @TheMadScientist420)
H815T - locked (Thanks @the_naxhoo)
H818P - locked (Thanks @SimoxTav)
H812 - locked (Thanks @ReeS86)

steadfasterX said:
Just wanted to let you know the current device list.
If you own a device missing in this list send me a PM with subject FIsH !
Please do not write me if your device is shown here already!
List of confirmed devices (as of 2017-03-15)
H815 International - unlocked (Thanks @steadfasterX yea its mine and i have no locked device to test with That's why i needed ur help. but i test without touching the boot chain so its similar to locked devices.)
LS991 Sprint - locked (Thanks @TheMadScientist420)
H815T - locked (Thanks @the_naxhoo)
H818P - locked (Thanks @SimoxTav)
H812 - locked (Thanks @ReeS86)
Click to expand...
Click to collapse
Nice work Waiting my Flex 2 LGH955 to arrive from warranty, I hope this can be ported to "LG Damed" locked flex 2 also

With efidroid in FIsH, will we able to install any custom rom such as android 7.0 based roms?

nikomedes said:
With efidroid in FIsH, will we able to install any custom rom such as android 7.0 based roms?
Click to expand...
Click to collapse
Limitations!
Keep in mind what I said above: FIsH does NOT unlock your bootloader.
That means with TWRPinFIsH you can NOT:
Install a custom ROM like CM/Lineage (this will modify boot = soft brick. for this u need "efidroid in FIsH" - coming soon)
Install a custom Kernel (this will modify boot = soft brick)
Install a custom recovery (this will modify recovery = may soft brick)
In short: nothing which modifies boot or recovery partitions.
You can of course flash everything which is modifying /system /data only (e.g. xposed,...)

nikomedes said:
With efidroid in FIsH, will we able to install any custom rom such as android 7.0 based roms?
Click to expand...
Click to collapse
Yes, with Efidroid you should be able to flash Custom ROM.
You can search about efidroid if you want to know more.
and thank you very much @steadfasterX , Good job bro ! :good:

Huawei P20 Lite root

Just for Info :angel:
DISCLAIMER
I only write, what i am doing on my Phone. What ever you do on your Phone - you doing at your own Risk !
RISK AT THIS MOMENT
Phone is new on Market. By my last Phone after 3 month not firmware by Huawei downloadable ! Continue to wait
Hi, this is my way to root HP20L.
My Build is ANE-LX1 8.0.0.108(C432)
By this way is UserData erased ! Make Backup bevor you go this way !
I found FHMate10Tool.
This is a "DOS-Prompt" program.
- Phone has bootloader-unlock.
- Phone is in bootloader-mode.
- I am start FHMate10Tool as admin. Use point 1 (rooting).
- 4..5 seconds Tool write "phone is rooted" ; Phone reboot; make userdata format lowlevel; reboot
- only your work: beginning by zero (configure: google ...)
- risk to break Phone is minimal.
BUT i have Backup with "dd" from factory-system and factory-recovery-ramdisk. "not tested at this moment"
(test next days, then i make append here)
My THANK'S to @aveemashfaq for inspiration : https://forum.xda-developers.com/9-lite/how-to/guide-backup-partition-using-dd-t3767613
Attention : "dd" is Powerful. Any error by typing and the consequences can be catastrophic ! Nothing for beginners !!!
Check "SuperSU". Install Titanium Backup or what ever you need.
If you wish TWRP, wait ! I am next days testing.
SuperSU is for me full-ok. If you need Magisk - look in forum.
I hope this help you & have fun !
Append 20180415 :
Now we have a good Chance for TWRP(any device !)
Look https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
Download this APP, install on your Phone, follow the instruction
You need from your Phone your "recovery.img" (Nougat) or "recovery_ramdis.img" (Oreo) for upload in APP and a little bit wait-time
TWRP-Builder = the best idea from last 5 year's : :good: :laugh:
Append 20181223 :
First we need BL-unlock. Huawei give us NO BL-unlock-code more. The only that's work is CD-Unlocker. Use DC-Unlocker for reed BL-unlock-code.
If DC-Unlocker not work on your Device - sorry ! Huawei is more and more "closed source" (Example : iPhone)
If you have your BL-unlock-code : unlock the BL (Attention ! This format data. On the End of BL-unlock your Device is "New". NO App's, NO Settings)
The good Way to root your Device is "Magisk". You need on your PC actual Firmware (look in Device Menu/System/Over the Device) as Full-Update Download.
Extract with HuaweiUpdateExtractor "ramdisk.img" (inside is "boot").
Copy the "ramdisk.img" to Device (Example in "Download") and the Same with "MagiskManager.app".
Install "MagiskManager.app" [MM] in Device, start MM, let it create "patched_boot.img", copy "patched_boot.img" to PC inside your ADB-Folder (Example "C:\ADB").
Open DOS-Prompt on your PC, change inside ADB-Folder (Example "cd C:\ADB").
Go with your Device in "bootloader-mode" with
- adb reboot bootloader
Flash "patched_boot.img" in your Device with
- fastboot flash ramdisk patched_boot.img
Reboot your Device with
- fastboot reboot
If Device run open MM, let MM self-update doing (it is need) and check if Device rootet (Example : Play-Store "RootChecker").
With this Way we have root AND Stock-ROM AND OTA-Updates work.
We can restore the Stock-Ramdisk (and have original Stock-ROM without root)
If you need you can TWRP install.

JamesBott said:
Just for Info :angel:
DISCLAIMER
I only write, what i am doing on my Phone. What ever you do on your Phone - you doing at your own Risk !
RISK AT THIS MOMENT
Phone is new on Market. By my last Phone after 3 month not firmware by Huawei downloadable ! Continue to wait
Hi, this is my way to root HP20L.
My Build is ANE-LX1 8.0.0.108(C432)
By this way is UserData erased ! Make Backup bevor you go this way !
I found FHMate10Tool.
This is a "DOS-Prompt" program.
- Phone has bootloader-unlock.
- Phone is in bootloader-mode.
- I am start FHMate10Tool as admin. Use point 1 (rooting).
- 4..5 seconds Tool write "phone is rooted" ; Phone reboot; make userdata format lowlevel; reboot
- only your work: beginning by zero (configure: google ...)
- risk to break Phone is minimal.
BUT i have Backup with "dd" from factory-system and factory-recovery-ramdisk. "not tested at this moment"
(test next days, then i make append here)
My THANK'S to @aveemashfaq for inspiration : https://forum.xda-developers.com/9-lite/how-to/guide-backup-partition-using-dd-t3767613
Attention : "dd" is Powerful. Any error by typing and the consequences can be catastrophic ! Nothing for beginners !!!
Check "SuperSU". Install Titanium Backup or what ever you need.
If you wish TWRP, wait ! I am next days testing.
SuperSU is for me full-ok. If you need Magisk - look in forum.
I hope this help you & have fun !
Click to expand...
Click to collapse
Tool worked for me. Now having access to all root features! Thanks for sharing! :good:

@r00terb3y
thank's for your test and response. :good:
all : if you give thanks, i am happy :laugh:
- if you click on thanks-button : i am very happy :laugh::laugh:

My Test, my phone, my risk !!!
First test with TWRP 3.2.1-0 (Huawei P smart).
TWRP flash + run = ok.
backup : folder (/data/media/0/TWRP) not created (Permission denied)
that's no big surprise : build for other device
Now my question : if here any twrp-developer how give me answer "how much work is it to build twrp for this device ?" 2 hour? 5 hour?
I have no idea, I do not have any twrp build.
if i can help for build (info from inside device, test new build ...) i do it !
a little bit risk is good for my brain : new phone, day 1 : bootloader unlock (warranty : bye - bye), see about twrp.
with extracted "recovery" form https://forum.xda-developers.com/hu...om-official-emui-8-0-huawei-p20-lite-t3773999
no risk to test twrp (thank's to @kilroystyx), switch stock-recovery to twrp and return - all ways work.
Warning for beginner : do you want to do such experiments - a paperweight for 1 € or $ is much cheaper than such this nice phone to turn into one

@JamesBott, the reason that you cannot backup data partition should be other, i suspect that your data partition is encrypted and that might be the reason.
If you are ok testing TWRP's I can try do one for P20 lite

@kilroystyx
if i test twrp:
- flash twrp
- twrp /wipe/format data
- reboot twrp to twrp
- twrp backup data
the twrp for Huawei P smart work on my Honor 9 Lite, not on HP20L.
if you found twrp : i test (give me download link) & if any work : i write here for ALL how need twrp!
with your recovery_ramdis.img(extract from update.app) i can test all twrp.
i flash recovery_ramdis.img and phone is in "delivery state" : work as a "new phone" . it's only my time [flash, test, reflash ...] . problem : for me not

sorry - double save #6
i use this for general info
i am not developer.. i am service. i am learn by doing and help other with my experience

@JamesBott, when I have something to test I'll let you know.
By the way, are you also interested to test CallRecorder MOD?

TWRP backups does not work because the P20 has a different partition layout than previous Huawei phones.

@kilroystyx
sorry : CallRecorder not need. i use my Phone first for Whatsapp (family and friends) and Telegram (special friends).

@mchtt
i think the same. twrp on H9L work, by install and twrp/format data work and msg "need restart for write function-changes". on HP20L : twrp/format data work, but no msg.
test was only a "shot in to the blue". i think, we are to fast. phone is new on market - very new.
my interest is technology : what works, what not.
for me a good phone : bootloader open - twrp - root - adaware. the follow other is secondary.

JamesBott said:
@mchtt
i think the same. twrp on H9L work, by install and twrp/format data work and msg "need restart for write function-changes". on HP20L : twrp/format data work, but no msg.
test was only a "shot in to the blue". i think, we are to fast. phone is new on market - very new.
my interest is technology : what works, what not.
for me a good phone : bootloader open - twrp - root - adaware. the follow other is secondary.
Click to expand...
Click to collapse
Yes but at least we have treble out of the box!
You tried flashing .GSI ?
It flashed flawlessly but the notch is not supported for the moment ?

@mchtt
excuse my question : what you mean "You tried flashing .GSI ?"

My Build is ANE-LX1 8.0.0.108(C432).
I used FHMate10Tool_201711115 to root and I can confirm this is working.

JamesBott said:
@mchtt
excuse my question : what you mean "You tried flashing .GSI ?"
Click to expand...
Click to collapse
.gsi is a system.img you can flash on treble enabled phones.
So you can easily flash LOS, RR or AOSP...
---------- Post added at 11:17 AM ---------- Previous post was at 10:57 AM ----------
JamesBott said:
@mchtt
excuse my question : what you mean "You tried flashing .GSI ?"
Click to expand...
Click to collapse
.gsi is a system.img you can flash on treble enabled phones.
So you can easily flash LOS, RR or AOSP...

@mchtt
i am extracted from full-update.app "recovery_ramdis.img" . test : flash recovery_ramdisk twrp.img and for return flash recovery_ramdis.img.
on H9L test developer-ROM's : flash system dev-sys.img. for return flash system system.img (extract from my own full-update.app)
that's all. never other (boot ...)

damn - double save #16 / is this my guilt ?

@Reversedhex
thank's for you msg. have fun

Reversedhex said:
My Build is ANE-LX1 8.0.0.108(C432).
I used FHMate10Tool_201711115 to root and I can confirm this is working.
Click to expand...
Click to collapse
Just run as admin and press 1 and everything ok?

Just bought the phone, waiting for a RIL and Wi-Fi working AOSP/LOS ROM (I'm a dev but I don't have any idea about Kirin). EMUI doesn't make me miss root.

Teclast M40 Pro Discoveries

Teclast M40 Pro Discoveries​Various helpful points of knowledge to unlock your bootloader, to root, and use your tablet.
Problem: Where can I obtain the official firmware?
Solution: Teclast Website
Usage: type M1A3 in search
Problem How can I unpack "pac" files?
Solution: Build C utility divinebird / pacextractor
Solution: Download pre built Linux executable pacextractor.zip
Usage: >./pacextractor Firmware.pac
Bash:
git clone https://github.com/divinebird/pacextractor
cd pacextractor
make
Problem: I need tools to flash my device
Solution: Download the latest SPD Upgrade Flash Tool SPD_Upgrade_Tool
Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools
Solution: Download and install 2010 Visual C++ Distribution
Problem: I want to unlock my bootloader. (Window and Linux kit)
Solution: Download TeclastM40Pro_Unisoc_UnlockTools.zip
Usage: Read readme file.
Problem: How can I remove the dm_verify warning on boot up after unlocking the bootloader?
Untested Solution: digitally sign the vbmeta partition and write it back. See [Tutorial] How to create a custom signed vbmeta.img
Problem: I want to root my device.
Solution: Modify boot.img with Magisk, then sign.
Usage: Upload to your device's download directory, the current boot.img read from your device, or from the same version firmware. Then install Magisk app from here. Use Magisk to patch the boot.img. Sign the partition. Then flash back the signed magisk version of boot.img to "boot_a" partition. Guide to flashing single partition at Hovatek Website
Problem: I need to emergency flash my device?
Solution: Currently only from Windows, use SPD Upgrade Tools to reflash firmware.
Usage: From the tablet powered off, or if boot looping. Hold down the power-button and volume-down for five seconds, release the power-button, and keep the volume-down button still held for another five seconds, then release or release if the detected earlier. Windows and SPD tools should then detect your device to flash.
Problem: I want to improve my Telcast M40 Pro
Solution: List of suggested apps below;
FDroid App Store F-Droid Website
Aurora > via FDroid. App store allowing the direct download from Google Playstore, without your own account.
Lawnchair > via FDroid. Fast open source sophisticated launcher.
AdAway > via FDroid. Removes adverts whilst using apps.
TrackerControl > via FDroid. Manages apps access to internet, and blocks spyware and trackers.
.

Problem: I want root mode without the effort of hacking a rom partition.
Solution: For those with World version Teclast M40 Pro device, here is a signed rooted boot partition I created. Read the readme file inside the zip. You will require an unlocked device, windows setup with USB drivers for Teclast, the complete firmware from Teclast website, and SPD Update Tools installed. If you're successful, then on rooting you will need to install Magisk app to get root active. Magisk will reboot once to finalise.
Download : TeclastM40Pro_ROW__v1p0_signedboot_magiskrooted.zip
Download : TeclastM40Pro_ROW__v1p2_signedboot_magiskrooted.zip

SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?

laurorual said:
SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?
Click to expand...
Click to collapse
Sorry for replying late. I got no indication of the response. To the problem, I can only suggest getting a different version of SPD or m aking sure your computer system is properly updated. I hope you've already solved the issue!
Maybe you're experiencing, "Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools" See above for solution.

I've noticed a new ROM for world edition, "M40 Pro(M1A3)_Android 11.0_ROW V1.02_20220525", but not getting any system update options for OTA. People flashing their systems may want the latest firmware!

Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Is there any way to install Magisk modules?
Thanks for your post, it helped me a lot to unlock my tablet.
Edit: My version is the M1A1 firmware V1.03_20210804
Edit 2: Finally, when updating my tablet with the root file that is in the post, it did not allow me to install any Magisk module, the solution is to download version 24.3, and update automatically, without changing to a higher version of Magisk

Glad you worked it out Miny !!! Sorry the warning emails for new posts have been going to a gmail account I no longer use.
Also your hardware maybe different and require it's own unique firmware and boot images. It seems the cracking in similar though.

Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?

Hi there.
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked?
Thanks in advance

rubsbcn said:
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked? Thanks in advance
Click to expand...
Click to collapse
To tell you the truth, not sure. Most SoC are impossible or near impossible to brick. They usually allow for an injection or have a read only boot section. Other words you could test. Also research difference in hardware between models, and that may indlicate if something may not work. The kernel/drivers are the improtant aspect.

jorkusjorkus said:
Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?
Click to expand...
Click to collapse
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical

minyfriki said:
Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Click to expand...
Click to collapse
What I found works, is when using SPD Research Tool, load up the firmware.pac and then go into settings and click "Select All Files" and again to unselect, which leaves the default required items.
Then manually change BOOT to the Magisk img. Then click on all VBMETA types, and UBOOT_LOADER (may not be required though). Then flash.
You should get bootable tablet (no looping). Warning: UserData partition is written over.
I'll share my Magisk image for v1.2

e8hffff said:
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
I'm using the same version as you on the same OS. After some research it seems like unlock_bootloader was removed in this commit from 2018. From what I can tell, unlock_critical does something else (unlock_bootloader runs
Code:
fb_queue_download("unlock_message", data, sz); fb_queue_command("flashing unlock_bootloader", "unlocking bootloader");
while unlock_critical runs
Code:
do_oem_command("flashing", "unlock_critical" and doesn't take the signature argument);
)
I'll see if I can compile the older version with the needed command.
What about my other questions?

Issue: Android not starting. I had the infinite restart when plugged in the usb. I tried to reload the installation package (succeeded), but didn't fixed the issue. Battery was not charging yet. When I started the Teclast M40 pro, the logo showed up, but the tablet turned off again.
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.

dougcwb said:
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.
Click to expand...
Click to collapse
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!

e8hffff said:
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!
Click to expand...
Click to collapse
I did the installation package process that the Teclast sent me. The last thing they told me to do was keep trying to install the package (wft?). Well, I just open the tablet, unplugged the battery for a while and after that it worked.
Maybe this resolved 2 things:
1-the battery was not properly connected in the first place, so when I plugged the 5 pin to the board it connected as it should.
2- Maybe there is a "memory" in the board attached to the battery that was bricked (or something like that) when I pulled off the plug, this memory was reseted.
BTW, when the tablet came to life again, the battery was at 87%.