yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] sdembiske:
TWRP-in-FIsH-v3-BETA2_LGG4_LL - Successful backup and restore!

How curious ... No problems here with both backup and restore with TWRP-in-FIsH-v3-BETA2_LGG4_LL installed.

I did the new backup and then rebooted back into android - no problems at all there.

I then re-booted into TWRP-in-FisH and restored that same new backup. Booted right back up - no dead android robot.

FisH logs and TWRP Recovery files pasted to Gist with link sent to you on FreenodeWebchat.

Questions: Did both users reboot fully into android after doing a new backup and did they then reboot back into TWRP-in-FisH and restore that same new backup? One other thing I noticed was that my USB connection was still set to PTP if that might make a difference (I don't see why it would but ...). The only other thing I can think of is the rooted software version they're on could be an issue. I'm on H81210N.

Thanks again steadfasterX. Very much appreciate all you're doing.

Best, S.
[G4 Android Development] steadfasterX:
Great thx for your feedback and testing!

Another proof that the food is fine and its all about FIsH. I have to find out what of my changes produces the issue.

If you want to help me finding out the reason I need to revert some changes step by step which means trying a couple of testbuilds.

If that is ok for you start with the next BETA-3 provided here: https://www.androidfilehost.com/?fid=457095661767152523

Do a clean as described above first. (will be done automatically on next beta..)

Hi sdembiske.

sorry out of thx clicks for today ;) but u know that I appreciate your feedback as for all the other ones ;)

I dont think it is something on their site. It's definitively FIsH. I have made big changes in v3 and well they seem to cause the issue.

Do u still see firmware partition? I hope so..

BTW: You can paste your paste.omnirom or gists links here as well - if you like.

IRC is when we need to chat because it is easier then posting here but for the links feel free to add them here instead ;)

Thx again for testing. When I've found the issue for the other users i need your help again ;)

.
[G4 Android Development] ReeS86:
I've tried Beta-3 and still no luck booting - here's the log: https://paste.omnirom.org/view/7be7fa64

I can post a log from a booting version 2.0 FIsH for comparison if you need it as well.

Edit: here's the clean log from 2.0 FIsH: https://paste.omnirom.org/view/d592e830
[G4 Android Development] sdembiske:
No problem.

Firmware partition has been missing in both V3 Beta 1 and 2 - didn't bring it up as I presumed it was one of the changes you made.

The reason I brought up the idea of firmware version is that ReeS86 is on the same phone model and carrier as I am, so the only difference that came to mind was the rooted software version he might be on.

Cheers. S.
[G4 Android Development] ReeS86:
I'm on H81210h software version - Rogers firmware version (minor differences to enable VoLTE as far as I'm aware).
[G4 Android Development] sdembiske:
One notable difference between H & N ...

Thanks. One notable difference between Rogers/Fido H81210H & N ... is that N was the later version and included the last stagefright vulnerability patch that was pushed through. The H version did not have that final patch and IMO is not as secure an operating system. I know because I originally installed H and when I checked it with Stagefright Detector (free on Play Store) discovered it was vulnerable whereas the N that I then installed was not. So I went with N for that reason and have been happy with it.

steadfasterX doesn't feel that the problem with the lastest TWRP-in-FisH Beta versions resides on your side but I'm having trouble getting my head around why they work for me but not for you.

Another possibility is maybe another Xposed app you've installed or some other app requiring root is interfering with the latest Beta versions but I'll leave it to you and steadfasterX to figure it out.

S.
[G4 Android Development] steadfasterX:
Thx to the logs of [MENTION=1258758]ReeS86[/MENTION] I have identified an issue. Maybe it is the cause for this behaviour and I will release a new beta after getting some hours of sleep..

sfX

.
[G4 Android Development] steadfasterX:
ok [MENTION=1258758]ReeS86[/MENTION] , please try the next BETA: https://www.androidfilehost.com/?fid=673368273298946284

I saw a dramatically decrease of speed in v3 which may explain your problems. I have improved the complete process in the newest BETA and hope it will work again for you.

if it still

fails

please try the following command on your PC:

adb shell "su -c touch /cache/recovery/boot"

adb reboot

changes in FIsH:

- improving the speed of killing, unmounting and overall experience (in my case this decreases FIsH execution from ~45 seconds to ~11 ! After FIsH has finished TWRP needs ~ 5 seconds to boot then another 5-6 seconds to show the splash screen. That means in sum ~21-22 seconds (+3 sec when using key press instead of boot flag) from activating FIsH up to showing TWRP.)

- removed wait time when boot flag is set

changes in FIsHFOOD (TWRP):

- let u backup firmware again

changes in installer:

- fixing cleanup on newer releases ( u dont need to manually clean anymore)

- extra option: install.sh --clean which let u uninstall TWRP-in-FIsH completely (this option is NOT necessary when u upgrade! cleanups will be executed on each installation automatically!!)
[G4 Android Development] Fobos531:
may I ask how's the EFIDroid in FIsH port going?
[G4 Android Development] fates13:
V3 beta 4 is finally working on my Verizon G4, thanks steadfaster!
[G4 Android Development] steadfasterX:
Great to hear! Then it was all about speed..

.
[G4 Android Development] steadfasterX:
Stalled. I had to fix FIsH first (see above). Keep in mind that without a good swimming FIsH no tasty FIsHFOOD... ;)

.
[G4 Android Development] ReeS86:
Thanks the latest Beta4 is booting on my G4 now too!
[G4 Android Development] sdembiske:
V3 Beta 4 working (still) on mine as well ...

steadfasterX: V3 Beta 4 working (still) on mine as well ... Successful install, backup and recovery with ability to backup firmware present again. Thanks again, looks like your almost there ... Congrats & Cheers, S.
[G4 Android Development] steadfasterX:
Many thanks for your both feedback. Highly appreciated.

Time is very important here and this makes totally sense.

sdembiske : the installer before beta4 was not strict enough in cleaning before installing. That means you may had parts of another beta active even when you installed the latest! That may explain why it worked for you the whole time.

V3 Beta4 ensures that you really start clean before installing.

---

Now I can go on with my efidroid port for unlocked (!) devices. This has to fully work first. So expect a (for you useless) efidroid release next.

When efidroid works as it should I will continue porting efidroid as fishfood for locked devices.

That's the way it goes.

.
[G4 Android Development] TheMadScientist:
You know mines up for testin and brickin. A mbn was just released for ls991 and i can restore mine hard bricked now. Lol heck yea
[G4 Android Development] sdembiske:
... at the back of the bus and use ...

steadfasterX: Thank you for the explanation regarding the cleaning of prior installations - makes sense now. I hope all goes quickly and well with the efidroid port to unlocked devices first. Feel that those of us with locked devices are forced to sit at the back of the bus and use different washrooms ... we await the day we can proclaim, Free, Free at last! from the chains LG and our carriers have bound us with ... I for one wish you the best of luck in this very much appreciated endeavour. Best, S.
[G4 Android Development] steadfasterX:
[MENTION=4976963]SimoxTav[/MENTION] or [MENTION=5178091]alitavas[/MENTION] (or anyone else having a h818..)

could one of you paste here the output of the following command please (while in running Android):

adb shell

getprop | grep product

thanks!

.
[G4 Android Development] Engelm:
shell@p1:/ $ getprop | grep product

[ro.build.product]: [p1]

[ro.product.board]: [msm8992]

[ro.product.brand]: [lge]

[ro.product.cpu.abi]: [arm64-v8a]

[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]

[ro.product.cpu.abilist64]: [arm64-v8a]

[ro.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]

[ro.product.device]: [p1]

[ro.product.locale.language]: [en]

[ro.product.locale.region]: [GB]

[ro.product.manufacturer]: [LGE]

[ro.product.model]: [LG-H818]

[ro.product.name]: [p1_global_com]
[G4 Android Development] steadfasterX:
that was amazing fast, thx ;)

.
[G4 Android Development] alitavas:
Sorry for late reporting because I'm in midterm exam :(

Microsoft Windows [Version 10.0.10586]

(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\andph>adb shell

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

shell@p1:/ $ getprop | grep product

[ro.build.product]: [p1]

[ro.product.board]: [msm8992]

[ro.product.brand]: [lge]

[ro.product.cpu.abi]: [arm64-v8a]

[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]

[ro.product.cpu.abilist64]: [arm64-v8a]

[ro.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]

[ro.product.device]: [p1]

[ro.product.locale.language]: [ru_RU]

[ro.product.locale.region]: [EU]

[ro.product.manufacturer]: [LGE]

[ro.product.model]: [LG-H818]

[ro.product.name]: [p1_global_com]

shell@p1:/ $
[G4 Android Development] steadfasterX:
new v3 BETA

changes to the previous BETA:

- fixing unify detection

- adding all known devices to unification

- these above fixes issues where your device was not detected correctly in TWRP and fails to install a ZIP which requires this!

You can check this by booting into TWRP-in-FIsH and then on your PC:

adb shell

getprop | grep prod

it should give you several lines of output where

ro.product.detection -> should be "success"

ro.product.model, name etc -> should be your device

If ro.product.detection -> is "unknown_model" please boot into Android and exec the above command here again. Paste me the output here so i can add your device to unification.

Download

.
[G4 Android Development] sdembiske:
Urgent: Heads Up ... Big Problem! DO NOT USE THIS BETA

Install, backup no issues but issue now with restore

resulting in a brick on reboot

- phone just shuts off, every time and gives a security error (Authentication Fail - #9) on reboot retry - no ability to get into download (NOTE: Finally able to get into download mode - instead of down volume button press and inserting USB cable, had to press UP volume button - a complete reversal, almost as if a different phone model), TWRP etc -- DO NOT USE until issue solved . On system restore: extractTarFork() process ended with ERROR 255. Heads Up: Backup storage location has to be reset if backing up to SD card, otherwise you will default to internal storage (this was not the case with V3 Beta4 from what I remember). Backup took noticeably longer: 700 + seconds vs 400+. Changes to initial TWRP boot-up screen etc..
[G4 Android Development] steadfasterX:
I'm sorry this comes unexpected because there were no changes within FIsH and not it in TWRP which should cause this.. Very strange.

Please tell me you have a recovery log from the restore error??!

.
[G4 Android Development] TheMadScientist:
Ive always had to hold vol up and plug usb for download mode. Vol down was always for recovery.
[G4 Android Development] sdembiske:
Will do ... once back up and running fully.

Just in the process of getting up and running - will post recovery log when available here. Totally unexpected but manure happens, to the best of us, eh ....? I'll go back to prior Beta and restore.

Cheers, S.
[G4 Android Development] raptorddd:
same VOL UP usb download mode.... how is that reversed.?
[G4 Android Development] steadfasterX:
Thx..

What are you both trying to tell me? You have installed the latest beta and now you can't get into download mode anymore or what?

.
[G4 Android Development] sdembiske:
Go figure ...

Yes, well you have a different phone model .... mine's an H812 ... I.E., It's different for different phone models. I do know what mine was originally.

S.
[G4 Android Development] TheMadScientist:
No he was trying to enter dl mode wrong

---------- Post added at 02:45 PM ---------- Previous post was at 02:43 PM ----------

Every lg ive ever owned has been vol up and plug for dl mode
[G4 Android Development] sdembiske:
See post # 214

See post # 214
[G4 Android Development] TheMadScientist:
If what u say is correct. Twrp never worked for you. as he has programmed this to enter recovery by holding vol down. If u were ever plugged into pc u wouldve entered dl mode instead. Basicly. Unless he wrote a special one for u to enter recov by holding vol up the whole time and dl mode by vol down. Just sounds weird if it was like that means he overwrote deep in the kernal to enter recov by vol down therefore overiding dl mode thus modifying kernal. Key storke he uses to enter recovery in unused by any thing so not overiding kernal functions. If i u derstand what he has done correctly.
[G4 Android Development] sdembiske:
Oh ... your H812 TOO .........................
[G4 Android Development] steadfasterX:
The trick is to press vol down when the green led is shown first not earlier. Then it works even with USB cable connected
[G4 Android Development] TheMadScientist:
I kinda take this post as rude and snobbish. If im reading it properly.

Were all here trying to help. No need for the rudeness

Why is it y

You seem to be the only one here having major issues?

Everyone else for the most part seems to be ok what are you

u doing thats causing so many issues?

---------- Post added at 03:01 PM ---------- Previous post was at 02:59 PM ----------

Exactly he is saying his vol down dl mode and basiy vol up is recovery

Or how he made it sound

---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------

Halfway through his op on this issue he says his button combo is reveresed.
[G4 Android Development] sdembiske:
You don't know what you're talking about ...

You don't know what you're talking about ... quit wasting space
[G4 Android Development] TheMadScientist:
http://www.hardreset.info/devices/lg/lg-g4-h818p/download-mode/

Google how to enter dl mode buddy i just did its the same on all g4s
[G4 Android Development] steadfasterX:
Oh just read the post again and now saw the note..

No S. it was always vol up to go into download mode. That's the main reason why I choosen vol down for FIsH ;)

[MENTION=6302635]sdembiske[/MENTION]

I think this all is a little misunderstanding but I hope you can get all fixed
[G4 Android Development] TheMadScientist:
Thats what i assumed
[G4 Android Development] sdembiske:
All I can tell u is when it bricked, I could not get into LGUP to re-flash stock except by pushing the up volume and then plugging in the USB cable. Prior to this I had to push the down volume. Other people have noted this as well with this particular model and this carrier. To get into TWRP-in-FisH, yes the down button always has worked. I don't know what more I can tell you ...

S
[G4 Android Development] steadfasterX:
Sure. The thing is.. The key combo to go into download mode is handled by the bootloader afaik and this one get never touched neither by backup nor restore. Don't get me wrong if u say it is like u described I believe u. But it is a strange behavior which I can't explain.

.
[G4 Android Development] sdembiske:
TWRP Recovery log from the restore error ...

Here u go. Something I screwed up no doubt.

https://gist.github.com/sdembis/448a2cbb1debfabedab137ca7cf7f316
[G4 Android Development] steadfasterX:
Thx but it seems to be cut?!..

.
[G4 Android Development] sdembiske:
Here is the untouched TWRP Recovery file ...

Try this: https://www.dropbox.com/s/yu935qt58wdbkt6/recovery.log?dl=0

If it is still cut, then it is what it is ...

I'll repeat: On restore it failed during with this note: extractTarFork() process ended with ERROR 255. End of story there. On reboot it generated the Security error # 9 (certainly wasn't a Love Potion) .One thing I noticed, many of the tick marks that had been there on TWRP backup and restore screens for the different partititions were not there whereas they had been before.

I have tested restore on every version and not had this particular issue. On reboot it gets to Logo screen, no blue lite at all, then generates the security error. End of story there.

That's all I can tell you.

S.
[G4 Android Development] ReeS86:
I can try to restore on my H812 just to verify it's not a freak occurance. I should find a block of time early this week in case I have to recover from a soft brick.
[G4 Android Development] azyx3:
You Are Number 1!!! If you ever come to Greece Let me Know;)

works on h815;) sorry i cant post videos or images coz xda said i am new or spamer because i had under 10posts:P

andreas.zam @ FB

---------- Post added at 05:56 AM ---------- Previous post was at 05:24 AM ----------

watch?v=VgLIWwlMiW0 @ youtube
[G4 Android Development] steadfasterX:
Hmm. The log is cut while doing the BACKUP! I expected to see the full backup plus the restore. How do you pulled the log? It seems it was too big.

The log file size requires to use adb pull..

Yea the error message alone is not enough though.. Without the full log it is impossible to find the cause. :(

When u see a security error it can be only a corrupt boot image and that is even more strange because this will be backuped and restored as image which doesn't make sense together with the error message regarding tar..

I will test asap to reproduce this issue..

.
[G4 Android Development] steadfasterX:
you may wanna try backup and restore as well? It could soft brick but u know how to recover..

.
[G4 Android Development] TheMadScientist:
I have. Works great. I never updated my fish. Im still on well was. The one u setup that night then i updated once. I wiped my g4 cause i thought a friend needed a loaner til her inssuarance got her new one to her
[G4 Android Development] steadfasterX:
So you have no g4 atm?

Or do you have upgraded to the latest beta and tested and it works?

.
[G4 Android Development] sdembiske:
In the first instance ...

In the first instance ... I opened the TWRP backup recovery file inside the SD card with Notepad,selected all, copied it and then pasted it to Gist.

In the second instance I right clicked on the whole file, copied it and pasted to dropbox.

I have since cut that file and pasted into my backup files on my laptop.

If you want me to try anything else, let me know.

S
[G4 Android Development] steadfasterX:
Hm. Strange.

The only thing would be to actually try it again and this time get the log with adb.. Until it contains what we need (the full log including the error message you saw in the GUI).

For me it will be easier to test than for u because I can more easily recover from a soft brick. I will just do the backup & restore tomorrow on my device and then using :

adb pull /tmp/recovery.log

to get the log file while in TWRP . Then we will know more...

.
[G4 Android Development] sdembiske:
Heads Up! - Power Menu app with TWRP-in-FisH recovery reboot!

AntaresOne, Recognized Developer, has done us a big one, incorporating the ability to reboot into TWRP-in-FisH recovery into his latest Quick Reboot app, version 1.4.3 available now on Play Store (https://play.google.com/store/apps/details?id=com.antaresone.quickreboot&hl=en). He went out of his way to help us here and did a great job on it, so please head over to his post at https://xdaforums.com/android/apps-games/app-quick-reboot-t3313667 and give him your Thanks. He is a stand-up guy and the app works like a charm.

I recommend upgrading to the Pro version for the added flexibility in being able to have only the reboot options you want showing on the screen and the ability to integrate with Smart Bulletin. In the near future, the Pro version will be able to synchronize with the power button long press for an added benefit.

Screenshots attached.

Cheers,

S.
[G4 Android Development] TheMadScientist:
Yea i actually put my note 5 up for a little while.

I had it restored stock. But i never installed fish back on it.

Im pretty it was the latest beta. I still had to manually mount system partition. The one it still said system 0 mb. But most def backing up and restoring

---------- Post added at 12:52 PM ---------- Previous post was at 12:50 PM ----------

Also thank you for this. A big help too
[G4 Android Development] ReeS86:
So using the latest Version 3 Beta 5 on my LG H812 I was able to do the following operations:

1. Backup in TWRP - all paritions, no compression

2. Wipe system, cache and data partitions

3. Restore system, cache and data partitions from backup

I did have to manually mount the system partition to restore though since it threw up an error about it not being mounted on restore. I pulled the recovery.log but it's 22mb since it lists every file that was backed up and restored from what I can tell.
[G4 Android Development] sdembiske:
Stranger than Pulp Fiction ... Now a successful restore with V3B5

Damn the soft bricks - full speed ahead?

Decided to try again, first incorporating ReeS86 note about mounting the system partition - I did this for both backup and restore (taking no chances) but also backed up firmware this time which I didn't on the prior failure (and didn't seem to have to on V3B4). Restored everything (i.e., all available partitions), no error generated and no brick this time on reboot ...

BUT ... an interesting development on reboot after both Backup AND Restore, each occurring separately. Link2SD Plus threw up a warning immediately that the 2nd partition (ext4 in my case) was not mounted at boot. This has not occurred with any prior version. Hmm ... - no real problem though, as recreating the mount script and rebooting again, takes care of it with it not recurring in normal operation again after that.

Here's the link to the TWRP Recovery file, pulled the way you wanted it to be within TWRP.

https://gist.github.com/sdembis/b8202333378c6bf11697dfd770464319

Best,

S.
[G4 Android Development] steadfasterX:
thx for trying again.

stupid question:

when do you have pulled the logfile? before or after doing the backup&restore?

you have to pull it after doing all the backup and restore (without leavin TWRP) and it will be usual several megabytes big then ... yours is so small like just TWRP has started and thats it..

.
[G4 Android Development] sdembiske:
Not a stupid question ...

Not a stupid question, just a stupid answer, I guess. I pulled it from TWRP after rebooting following the restore and then rebooting into TWRP and pulling it. I have never had to do this before, so excuse my ignorance in this regard. I know now.

In the meantime, I have opened the recovery file in the SD card this time, selected all, copied and posted it to gist this time. Here is the link for this one: https://gist.github.com/sdembis/551d1681e77c7419866f993bcebf093e

If this doesn't do the job and you require the adb pull method in the way you have described, I will do another install, backup and restore and pull it the way you suggest. Let me know.

Thanks,

S.
[G4 Android Development] steadfasterX:
ok :)

the gist is showing now what I expect (full backup log) thanks.

so now do the same after a restore and thumbs pressed without soft-bricking ;)

.