yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] BIG_BADASS:
As long as the partitions match 1 to 1, it should be alright.

I can think of so many reasons as to why he'd want to flash a different variant's stock firmware on his device. First and foremost: frequency bands.

If he can flash the H815 rom, he will have worldwide GSM and LTE band support, which is not the case with other stock firmwares.
[G4 Android Development] steadfasterX:
Please do us a favour and do not write things again and again you do not know about ok?

and if you do that nevertheless state clearly that you are not sure about!

keep in mind why your account gets disabled... twice.

Besides that your statement is not true. Read my answer 1 page ago. It's not that easy.

.
[G4 Android Development] BIG_BADASS:
Oh, don't tell me I don't know. I know very well, in fact, I've experienced first hand with other phones when I flashed Samsung Galaxy Avant (SM-G386T) rom over Samsung Galaxy Core LTE (SM-G386W) with locked bootloader.

Go and see the SM-G386W rooting method, it was first implemented by me. The first factor I took into consideration was the PARTITION TABLE. It matched, so I went ahead and BAM.... it worked.
[G4 Android Development] steadfasterX:
Even when this may work I made clear it isn't the partition table only which is relevant.

Rooting has nothing to do with cross flashing partitions.

This conversation is useless. stop it.

.
[G4 Android Development] BIG_BADASS:
Ok sir,

Please tell me then, why it worked previously for me? What other factor is to be considered?
[G4 Android Development] steadfasterX:
you dont have read my explanation. there is no reason to repeat everything again and again just for you. go back and read.

besides that im no one who requires everyone to be 100% strict on topic.

a little bit off-topic is ok especially when someone kindly asking as the user has done.

but this ends here. stop it and go back to topic. make an own thread asking your questions in the Help area.

.
[G4 Android Development] steadfasterX:
For all those who havent recognized it yet ;)

[MENTION=5937299]the_naxhoo[/MENTION] has found out this for you:

https://xdaforums.com/g4/general/official-nougat-g4-v10-q2-2017-t3567402/post73593044

But be aware: you will loose root (and so TWRP-in-FIsH) when you do this!

.
[G4 Android Development] Araa01:
Does anyone know what is wrong?
[G4 Android Development] steadfasterX:
yes..

I have removed busybox completely to avoid licensing issues.

the installer on Linux takes cares of this automatically and would download busybox for you but as u are trying to install on Android you have to install busybox first:

https://play.google.com/store/apps/details?id=stericson.busybox

Afterwards re-run the installer and let me know if that fixes your problem

sfX
[G4 Android Development] Araa01:
Thx mate, but fixed problem whith reinstall SuperSU and reboot. Yes busybox not installed for first time :) TY
[G4 Android Development] ardian1899:
Sorry for my ignorance my friend as I only read a few pages and my question may already asked..

Can I use it on H818P Marshmallow?

and by installing SuperSU, it means rooting the device, right?

Thank you
[G4 Android Development] steadfasterX:
no need to read all posts here.

The OP is enough (Requirements) and if you met them u can use it (H818P is proven to work if you can met the requirements)
[G4 Android Development] dextructor:
I'm having exatcally the same problem. only in the last step.Could you help me?

[IMG="Error"]https://s26.postimg.org/xldtqnz7d/Screenshot_2017-09-15-18-06-38.png[/IMG]
[G4 Android Development] steadfasterX:
no u have another issue ;)

you have to type su before like this:

su

cd /sdcard/android_FIsH

sh ./install.sh

not your fault though. I've updated the OP with this rn.

sfX
[G4 Android Development] dextructor:
Thanks for the quick reply, but not yet working. It's something wrong with my fingers?
[G4 Android Development] steadfasterX:
well is the path correct? where do you have extracted it?
[G4 Android Development] dextructor:
I have extracted through the first step on the OP... via ADB push
[G4 Android Development] steadfasterX:
well you should push the compressed file to ensure nothing get missed

adb push TWRP-in-FIsH

.tgz

/sdcard

so as stated there (I removed the other examples):

Bring TWRP-in-FIsH to your Android device

adb push TWRP-in-FIsH.tgz /sdcard (replace TWRP-in-FIsH.tgz this with the real file name)

extract it

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
[G4 Android Development] dextructor:
It fails in the step 0 with the error

adb: error: failed to copy 'TWRP-in-FIsH.tgz' to '/sdcard': Is a directory

Any tips?

EDIT: if I modify the command to "adb push TWRP-in-FIsH.tgz /sdcard/" works like a charm, but in step 2 the extraction i get a weird message.
[G4 Android Development] steadfasterX:
You forgot to su before

sfX
[G4 Android Development] dextructor:
Same error
[G4 Android Development] the_naxhoo:
1.- Download and unzip: TWRP-in-FIsh_4.2.zip

2.- Put the folder "fish" in the internal sd.

3.- Now in the Terminal type this:

su

sh /data/media/0/fish/install.sh

That's all! :)
[G4 Android Development] dextructor:
Worked like a charm!!! Thanks [MENTION=5545101]steadfasterX[/MENTION] for the patience on a friday night & development on G4, and [MENTION=5937299]the_naxhoo[/MENTION] for the alternative solution!
[G4 Android Development] mwahahaa:
Thank you to steadfaster and all others involved in helping to move this project along.

I have a locked, rooted G4 with xposed and am wondering what twrp-in-fish can offer me. At this stage of development, my understanding that the only extra functionality I would gain would be the ability to make nandroid backups, and to alter build.prop. The option of flashing of any kind of ROM (even without altering kernel and recovery) has not yet been implemented, correct?
[G4 Android Development] sdembiske:
The ability to back-up a system image and restore it in TWRP-in-FiSH is a great plus, particularly if any modifications have been made to an original rooted system image. As an example, refer to post #1437 with respect to an issue that was solved on an H812 in this other thread - the use of TWRP-in-FiSH made it quick and easy with the ability to backup and restore the modified system image without having to go through the whole modification process again. In the event of a corruption, soft-brick etc, it can get you back-up and running quickly to where you were before the event occurred.

steadfasterX is currently working very hard on being able to install custom roms on LG G4's with locked bootloaders. Refer to his thread [BL UNLOCK][LS991|H81x|VS986|any nonFused] *Unlock your bootloader PoC* (WIP!!) at: https://xdaforums.com/g4/general/bl-unlock-unlock-bootloader-proof-t3648288 if interested. Read the OP carefully and be fully aware of the risks and limitations.
[G4 Android Development] bravac:
are we able to replace supersu with phh or another more open source superuser method with FISH?
[G4 Android Development] steadfasterX:
In theory yes. I checked this in the early beginning of FIsH but it requires to implement the init part on my own instead of using the one of supersu.

But that's nothing which will happen as I'm focused on the unofficial unlock atm.

sfX
[G4 Android Development] steadfasterX:
still there?

... long time quiet here but there is something baking in the background for you ;)

as I switched almost everything to be fully automated I currently doing this for TWRP-in-FIsH as well.

That means expect an update of TWRP with important changes (EFS backup etc) in the near future and from then on all further TWRP releases can be much easier build.

sfX
[G4 Android Development] dillweedinc:
I am wondering if there may be some interest in getting this working on the NOTE 8 Snapdragon we have root with SAMFAIL and we almost had it running.
[G4 Android Development] steadfasterX:
Sure go over to http://tinyurl.com/FISHatXDA and begin to port ;)
[G4 Android Development] Busyboybean:
Bricked

G4 was acting up, so I restored my backup but the phone bootlooped. Now all I get is the LG logo and then the android with the spinning circle
[G4 Android Development] Camandros:
Hi all,

First of all, [MENTION=5545101]steadfasterX[/MENTION], great job man. I read what is in the FiSH bowels and it is awesome.

So, I have an H815, still with locked bootloader. Right now, I have the v29 7.0 Nougat, achieved by:

Starting on MM, downgraded to LL

Did the low effort root

Placed TWRP-in-FiSH

Used the FiSH to flash the v29

But on the fourth step, after flashing the v29, while still in TWRP-in-FiSH, could I flash SuperSU and get root on Nougat? I know that FiSH works only in LL, but with root I could use flashfire to flash other zips (e.g., xposed, magisk), right?

Thanks in advance
[G4 Android Development] steadfasterX:
if it would be that easy .... ;)

yes you can flash it but that will modify the boot partition and will make it invalid and so brick.

you can even configure supersu to not touch the boot partition but it will still fail to boot.

so no my friend. absolutely no way to get root on MM or N for you unless you unlock.

.
[G4 Android Development] Camandros:
Ah damn... It was worth a shot ;)

Thanks
[G4 Android Development] Busyboybean:
[MENTION=5545101]steadfasterX[/MENTION] can this be fixed
[G4 Android Development] steadfasterX:
I guess you may haven't wiped cache after restoring?

The first thing you should try is a factory reset if you can't boot into TWRP anymore.

If that does not solve the issues you can go into the download mode and flashing a kdz should do it.
[G4 Android Development] Busyboybean:
Tried a factory reset, and flashed a new KDZ end up at the same place:(
[G4 Android Development] steadfasterX:
Then it was not a faulty restore but it sounds like the ilapo. Check my signature for the bootloop fix it list.
[G4 Android Development] steadfasterX:
Long awaited version published: TWRP-in-FIsH-v5.0-72_lge-g4_LP

But most important 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

All details about the new release here:

--> Changelog <--

Unfortunately I have not the time to test this new release so pls report any issues and provide the fish logs when you find an issue!

Preparing yourself and taking a full backup with

SALT

is a very good idea before trying this version and every nightly version in the future!

Have fun

steadfasterX

PS: TBH I dunno if this here still matters anyone as so many are on Nougat now ;)

.
[G4 Android Development] Rahulgur:
hey please can you provide bootlood LG H630d

hey please can you provide bootlood LG H630d please
[G4 Android Development] steadfasterX:
What's bootlood? and the h630d seems to be not a LG g4.
[G4 Android Development] fil3s:
Btw I got this mod to work on a clean flash

Don't know why my comment was deleted :confused:
[G4 Android Development] steadfasterX:
You're right and I don't know what happened.. Thx for pointing and reposting!
[G4 Android Development] glenrocks:
Installed TWRP 4.2 and 5+

I finally was able to get to this option to revive H812 as I have corrupted my system files - after trying stock, rooted images, modules from version H81210n and H81210o. I messed up Audio on phone too by overwriting audio files under /system/etc../bin../lib now. This is in addition to Modem dropping calls and external SD Mount problem.

Now I got TWRPinFish using FWUL in VMBox Windows 10. Does that mean that I can request you for twrp backup of H81210n/o system image which I can try??

Also, I see option of FWUL option of reading KDZ partitions- I have not read enough to understand how to overwrite partitions.

So my question is which option is cleaner for me?? Restore TWRPinFish system image (excluding boot and recovery) which is already injected with root or...??

While installing TWRPinFiSH, I had to go to /data/media/0 instead of sdcard using su as it threw me an error too, not recognizing sdcard folder. I was able to take backup of data and system successfully with 4.2 ver.

I also updated to ver 5 by simply running install.sh... hope it didnt require cleaning 4.2 to upgrade. I really liked the simple option of pressing vol down on Green led to enter twrp (nice feature)
[G4 Android Development] sdembiske:
First of all, my carrier version is Rogers/Fido.

Your best option is to flash a clean stock 5.1 kdz for your carrier (Telus/Koodo?) with LGUP-NEW, followed by flashing the rooted version of the same carrier kdz. Failing that, I can direct you to clean versions of both Rogers/Fido kdz's. If you have a recent Titanium backup you should be able to get back most of your set-up together with your Google account syncs.

I don't believe flashing a TWRP-in-FiSH backup of my system partition will solve all your problems as some of then have probably arisen from flashing the rooted 5.1 over the 4.2, if I understand you correctly. For the modem issue, one solution might be to wipe your modemst1 and modemst2 partitions followed by rebooting to see if the problem with calls is helped. They are different partitions from the system partition. If that works, you could try a TWRP-in-FiSH backup of my system partition (not the system image), but, as I stated, I don't believe that it will solve all your problems ...
[G4 Android Development] glenrocks:
1. / 3. My problem was always there when I got this used phone running MM but still no connection to US GSM ATT Carrier... strange thing was with APN fix + Data ON, SMS/Internet worked..... so I started playing with LP and rooted versions... Now I am at that state, I will try every option to fix this H812...

2. I do not have any clean tested working backup

4. I did use SALT to delete modemst1/2 partitions once but I suspect that this LG G4 H812 is one <persistent> phone which loads modules, never wiping old corrupt files.... it only created more problems with locked B/L.... so now I have TWRPinFiSH, I am open to Rogers system/firmware partition backup too.
[G4 Android Development] sdembiske:
I pm'd you a link to one of my system image backup files.
[G4 Android Development] glenrocks:
Error:

I had to reinstall the whole cycle of stock-root-twrpfish due to mistake and now I get this error on install:

Installer is running on Android

Installer is running in REAL-INSTALLATION mode!

############# Checking for busybox

Android Debug Bridge version 1.0.32

############# checking Android version

-> Good. Matching exact the required Android SDK: 22

############# checking SuperSU version

-> Matching required SuperSU version: 282

############# temporary disable SELinux

-> command ended successfully (err=0)

SELinux mode: Permissive

############# remount /system

############# cleaning

-> command ended successfully (err=0)

-> command ended successfully (err=0)

-> command ended successfully (err=0)

-> command ended successfully (err=0)

############# creating temporary directory

-> command ended successfully (err=0)

-> command ended successfully (err=0)

############# pushing files

--> ERROR!! ABORTED WITH ERROR 10! Check the above output!

find: fishing/: Value too large for defined data type

Unable to open /data/local/tmpfish/gofishing.sh: No such file or directory

Is it available for H812?

---------- Post added at 12:00 PM ---------- Previous post was at 11:50 AM ----------

Thanks... Will try to restore once I resolve this install error twrpinFish.

If not, then will switch to SALT to match the partitions... I always have problems with SALT connecting to phone w/ download mode somehow.
[G4 Android Development] sdembiske:
Before going off half-clocked with SALT - suggest you post to steadfasterX first to see what he suggests.

Boot into TWRP-IN-FiSH recovery, mount all and select storage as internal and restore for the system image. Once installed, clean your cache before exiting and then unplug and reboot your phone.

Note: You may have to re-install TWRP-in-FiSH with a clean install with your latest issue with it.

PS: reboot your linux version in virtualbox (not the machine just the linux version you're running), while phone is plugged in in download mode (make sure it is checked in devices - USB and in the controller setting for USB 2 before rebooting linux - I have problems as well and this way works every time.
[G4 Android Development] steadfasterX:
You try to install TWRP in FIsH directly on android it seems? What are the exact steps you have taken?

When you have issues with SALT:

You may have to wait 60 sec after you booted into download mode before SALT is able to detect your device. If not press the SKIP button open the advanced menu and copy and paste the debug log. My signature here has a paste service link you can use.
[G4 Android Development] nguyenvantuc:
When i installed twrp on my h818p

Can i install any rom CM or any rom ?

Or which rom i can install?
[G4 Android Development] fil3s:
No only stockbased lollipop ROMs . Try this one
[G4 Android Development] glenrocks:
I used FWUL terminal to (un)tar the file and adb push folder to phone.. and then executed install.sh using su from /data/media/0 (as sdcard is not accessable thru su).

For now as I wanted to test new system image restore, I got TWRPinFiSH back using system image <sdembiske> posted when he solved his exfat SD issue. Sadly my issues still remain unsolved.

I will try connecting phone in download before launching VM FWUL and post the issue when I get to SALT. Do you have tutorial or post for me to read how to read STOCK KDZ option under SALT and how to overwrite Phone Partitions?? Would be helpful.

---------- Post added at 09:26 PM ---------- Previous post was at 09:13 PM ----------

Firstly, Special thanks to you for uploading huge file and devoting ur time to help me.

Secondly, Restore did not resolve my issues of Lost Audio/Lost SD (tried both exfat/ext4). So back to two options: start from stock KDZ files using SALT or new LGUP .

I will have to think of nickname for myself after your soft brick ... lol
[G4 Android Development] steadfasterX:
Why such complicated?

Just start. /install.sh from the FWUL terminal as written in the install guide.. The option to install from within android is just an alternative way when the regular method does not work..

Read stock kdz in SALT? uhm.. click the extract kdz button..??!

As mentioned atm it is not possible to WRITE partitions with SALT. This WILL come but I need to do make it work first.
[G4 Android Development] glenrocks:
I used untar from FWUL cuz it didn't work the way it was in guide.. so I made it work then and tried both options in FWUL and Phone terminal emulator too.

I had to change USB settings to USB 3 to make it work... and it worked..... now when I do FULL backup, it tends to sleep on 53rd system partition out of 56 partitions on the phone... probably bug on the phone?? Can I delete unneeded partitions to correct the issue??

I did update SALT to your develop changes, and saw KDZ option and thought it was working, as you mentioned in other threads.... guess I might need to run shell script instead??? I read bits and pieces but then assumed that your SALT solution is becoming ultimate help...without realizing that its still not implemented. My mistake.

I still believe that H812 got corrupted before and after I got it and its software issue only for MODEM/SDCARD/AUDIO, so if you can guide me through replacing firmware through SALT or shell scripts... it would be helpful or I can wait if you are not comfortable sharing it in open thread.

I am always open to Teamviewer option under FWUL (if implemented).

Also wanted to ask- How does FWUL map shared folders automatically or it has to mapped manually??
[G4 Android Development] steadfasterX:
This is the userdata, cache or system partition (depending on your GPT). This can take up to several hours! but it fails silently atm when you have not enough free disk space!! (a full backup requires ~ 33 GB!)

well. tbh SALT is able to write on LP and also some MM versions.

Switch SALT to the TESTING version (click update, select develop everywhere, update, restart SALT) and tell me what you see in the field "LAF protocol" - when the device is connected ofc.

you need to configure virtualbox for that (auto map). then a reboot should automap them (requires FWUL v2.5 or higher)
[G4 Android Development] fil3s:
Forgive my ignorance but is it possible to boot multi-rom with twrpinfish ? It said at begging of op that it was possible. I haven't been keeping up with this thread (only the downloads section ;))

That would be cool. I also remember reading a post that there is a SuperSU Wip that can root mm without touching boot image
[G4 Android Development] steadfasterX:
rooting MM is not possible without unlock.

Multirom is in theory possible but I abandoned this due to my work on UsU.

Wait for UsU to unleash your device..
[G4 Android Development] fil3s:
Thx. I hope we can flash magisk in future builds. (I'm a noob) :svetius:
[G4 Android Development] steadfasterX:
With UsU yes.
[G4 Android Development] fil3s:
I'm getting 'failed to mount system - device or resource busy' even though I have mounted system. Is this normal?

Steps I took to install:

(I set supersu to grant automatically,and in terminal I type -

cd /sdcard/android_FIsH

sh ./install.sh

Thx for the work. Hopeing for a 6.0 FIsH update! ;)
[G4 Android Development] xdauser9675:
[MENTION=5545101]steadfasterX[/MENTION]

So here is one more H818 device got twrp booted. Thanks to you.

Then I wanted to flash a custom ROM. And as you have already mentioned no normal custom ROM will work except if it does not modify the boot partition so I went trying and deleted boot.img from a CynogenMod Rom 12 which was of the same time as v10D(rooted image).

I wiped cache/dalvik/system :( and flashed it. It got to the screen as

Security Error authentication failed. #3

I recovered it through LGUP though :o

Can you please make such a ROM which will work with this TWRP. It will be of a lot of help. Asking you since I saw a thread where you released a Cynogen or Lineage ROM.

I am ready to brick my device to testing if that's what it takes.

Thank You.
[G4 Android Development] steadfasterX:
Locked devices can only boot stock. Nothing else. This is not TWRP related.
[G4 Android Development] Cedlad:
hello, following this, can i install Pixel Experience Plus on my LG G4 H815P ?
[G4 Android Development] steadfasterX:
Yes but that requires you to unlock first
[G4 Android Development] Cedlad:
i unlocked my H815P with your UsU method, is Pixel Experience Plus compatible with UsU?
[G4 Android Development] glecko:
Thank you for all this work! I was able to breathe some new life into my G4. But recently, I flashed another recovery SHRP? and while it booted it obviously screwed up everything. I re-read the first post and realized that I messed up.

So now the phone just stops at the LG Logo. Is there anything that can be done? If you can give me some general tips, I'm sure I can manage, just need a first step to start.

Thank you for any help.
[G4 Android Development] TheMadScientist:
Thank you