yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] freinet:
I think I know what happened. I restore a backup that I created with an older version of twrp. With new backups no error.

Sorry.for bad English, hope you understand.

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] Nando_aot:
[MENTION=5031300]blastagator[/MENTION] are you going to support the TWRP 3.1.1?

thanks
[G2 Android Development] Eselter:
What's new in 3.1.1-0:

Backups will now include adopted storage keys (Dees_Troy)

Fixed an adb restore issue (bigbiff)

Fixed rebooting when no OS is present (Dees_Troy)

Fixed line wrapping in the GUI terminal (_that)

Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
[G2 Android Development] blastagator:
May 20, 2017 (3.1.1-0)

-TWRP Change Log:
[G2 Android Development] turkishield:
İ just tried install crdroid rom 2.5 it failed.

the warning about the dates..twrp said im new version u cant install crdriod 2.5 version. cause its old version.

now back to twrp 3.0.2.1 version and i could install crdroid 2.5 version.
[G2 Android Development] JuubiV1:
So why don't you flash the newest one? :P
[G2 Android Development] turkishield:
cause of bugs

cause after crdroid 2.5 versions are not stable. there r a few bug and issue that users reporting. :D
[G2 Android Development] blastagator:
Provide logs.
[G2 Android Development] jenda.69:
I don't have any logs, sorry, but I stumbled upon this issue few days ago too and tried to find what causes that problem. So here's my two cents:

Error appears on this line in update-script in ZIP file of crdroid ROM:

(!less_than_int(1494816625, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Mon May 15 04:50:25 CEST 2017) over newer build (" + getprop("ro.build.date") + ").");

It supposedly checks date in build.prop of current ROM and if it is newer than ROM you're flashing, it returns error.

But I wiped my system&data&cache partitions before flashing (not sure this matter) so there was no build.prop file.

Date it displayed in the message was same as date in default.prop I found in recovery filesystem (is that one built in to recovery?) I don't remember exact path though.
[G2 Android Development] wq0913562:
[MENTION=5031300]blastagator[/MENTION] Will you update your TWRP version to the new LineageOS kernel? As you probably know, official LineageOS builds for the G2 were temporarily disabled because of the lack of a maintainer and because the G2 kernel is affected by several CVEs.

Luckily though, there is a new maintainer now and official builds have been re-enabled and CVEs are getting patched.

Since your TWRP version uses the LineageOS kernel (well, an old CyanogenMod 14.1 kernel even), it's affected by the same CVEs, right? So TWRP should also be updated with the latest LineageOS kernel, right?
[G2 Android Development] blastagator:
CVEs don't really matter for twrp unless related to core function of twrp (e.g. File system bug that can cause corruption). Otherwise, if someone steals your phone they can flash whatever recovery (and whatever kernel) they want. TWRP doesn't have internet connectivity or run anything that could hijack your phone, so kernel exploits don't really matter unless core function related.

I update the kernel with each build, but unless there is a specific bug or cve of concern, I see no reason to rebuild the existing version just to update the kernel.
[G2 Android Development] shiftybugger:
Is your website currently secure?

I've rooted my d802, confirmed with root checker, have installed TWRP using AutoRec, then installed your TWRP. That all works fine. However, when in install ANY OS, after rebooting I get just a black screen.

I decided to go back and check the hashes of all of the files that I am using and they are all fine except for your TWRP zips. I can't get any of the downloads to match the checksums you have. Also, copying over the .md5 files and asking TWRP to check the zip fails as well.

Any ideas?
[G2 Android Development] netscvngr:
You may have to update your bootloader. Many roms require the lollipop bootloader so you may have to use bootloader changer or similar app to change it. I had the same problem.
[G2 Android Development] eried1:
There seems to be much confusion regarding the hardware buttons.

Power + volume down, release and power + volume up brought me to the factory reset screen one time. Tried it again several times and it didn't do anything. Eventually I tried power + volume down, release and power + volume down and got to the factory reset again. I'm not even sure this is how I did it. Might also have released just the power button.

Would have been nice to sort this out once and for all.
[G2 Android Development] 60nine:
it's supposed to bring you to white factory reset screen... when you choose 'yes' there twice it won't reset your phone but it will enter recovery...

this was explained so many times all over the g2 forums...

on the other hand - if you can boot into your rom, you can use an app like Rebooter or such to reboot into recovery... or using some xposed modules which put that option in power menu...

NOTE:

this works only if you have twrp recovery installed already...
[G2 Android Development] 60nine:
[MENTION=5031300]blastagator[/MENTION]

do you know anything about this for our G2 device...

https://www.xda-developers.com/lg-root-checker-tool-slow-performance/

attached is the screenshot from my d802 running rooted [MENTION=4008653]somboons[/MENTION] stock rom
[G2 Android Development] n@vier:
On my d802 running RR 5.8.4 it's not affected:
[G2 Android Development] totofe69:
Nothing for me with last RR with magisk and lambda kernel
[G2 Android Development] 60nine:
all of you guys are running aosp roms... i wonder if someone else running stock has this thing as well... and i wonder does this affect sometimes sluggish stock rom performance (mainly in UI and opening apps)
[G2 Android Development] mostafas144:
D802 stock 30f somboons..effected too
[G2 Android Development] jeebspawnshop:
That's cuz the rctd (Root Checker Tool Daemon) only exists on stock LG firmwares.
[G2 Android Development] vagkoun83:
I have the same results with stock somboons..

Sent from my LG-D802
[G2 Android Development] 60nine:
so, are there any developers that could help on this matter?

[MENTION=5031300]blastagator[/MENTION] - sorry for a little thread "takeover", but i didn't know should this be put in a separate thread or not...
[G2 Android Development] blastagator:
What's the real question here? Can you delete the thing? Backup and try it. If it breaks something, restore. I don't use the G2 anymore, so I can't really give good feedback to effects/side-effects/drawbacks.
[G2 Android Development] ST Dog:
Supposedly started from the initial ram disk, requiring an edit to boot image to stop. But I haven't looked at the G2 closely.
[G2 Android Development] blastagator:
Presumably the binary could just be removed and then it would fail to start when it doesn't find the file. Sometimes this breaks boot, but based on the function of the file, it seems unlikely to harm anything.
[G2 Android Development] ST Dog:
Indeed, I suspect it's not as tightly ingrained on the G2 as on later devices.
[G2 Android Development] 60nine:
i'd try this if i knew what exactly to delete :D

nevertheless, i thought it was more of a developer thing to fix since the article mentions boot image...

thanks for the response
[G2 Android Development] ST Dog:
the rtcd file where ever you find it. Someone posted earlier a copy in /system/bin

Other devices showed it in /sbin
[G2 Android Development] 60nine:
thought so... thanks...

i did a full backup, reboot, deleted "rctd" file from "system/bin" folder in es file manager... rebooted... everything ok...

terminal command no longer shows any outputs

so i thank you all and sorry for all the confusion...
[G2 Android Development] blastagator:
To round this out, you can search for references within the ramdisk by using this command in linux:

grep -rnw ./ -e "/system/bin/rctd"

When I checked out the 30f ramdisk, there are two references (other than the file_contexts):

./init.g2_core.rc:99

service rctd /system/bin/rctd
class late_start
user root
group root

./init.galbi2_core.rc:673

#add RCT service
service rctd /system/bin/rctd
class late_start
user root
group root

You could delete both of these from the ramdisk and that should also stop the service from running.
[G2 Android Development] 60nine:
got me all confused now :)
[G2 Android Development] ST Dog:
Delete the calls in the ramdisk and you don't have to change /system.
[G2 Android Development] 60nine:
and you think i know how to do that? :) i don't even have linux... i'm not a dev, just a basic user...

btw already deleted that file from system/bin without any issues... do you suggest that this other ramdisk "operation" should be done as well?
[G2 Android Development] ST Dog:
I'm no dev either. Just an end user.

But other discussions of the rct mentioned the ramdisk. A Little Unix experience help when understanding the system.

Not for our devices. But some are very picky about changes to /system.
[G2 Android Development] zeka16:
I have version 3.0.2-1.

Am I good to go at installing the latest lineageOS build that came out today or should I update the recovery before proceeding?

As far as I'm aware I'm good to go, but please let me know if I'm wrong.

Thanks
[G2 Android Development] haldaios:
keep the good work!!! your edition or TWRP rocks!!!!
[G2 Android Development] ST Dog:
Is there some reason you don't want to update TWRP?
[G2 Android Development] zeka16:
I bricked my phone when trying to install TWRP the first time so the least I need to do to it again, the better! :D
[G2 Android Development] ST Dog:
Shouldn't​ be an issue updating since this is already bumped. Then again I had zero issue with either G2 I did.

Root, autorec, update TWRP, install ROM. I never ran stock after autorec.
[G2 Android Development] zeka16:
It's been a few months but my problem at the time I think was not installing blastagator's right after Autorec.

It messed up the whole process and while trying to fix it I just made it worse bricking the phone. Eventually got it working again and all is good now.
[G2 Android Development] peeenk:
I have a LG Vista how can I manually install twrp recovery? Due that I can't find my device Img? Or any other where I can install a custom rom?
[G2 Android Development] 60nine:
because this is only for LG G2 devices...

try searching in other parts of xda for your specific device only...
[G2 Android Development] DrLamok:
Is there any way to install latest TWRP on LG G2 D802 Lollipop 5.0.2 V30d without rooting phone in the first place?

I had my phone rooted for years but recently I need to use a couple of apps that fail to work on rooted phone so I had to re-flash clean image.
[G2 Android Development] Limakos:
Unfortunately no.
[G2 Android Development] runekock:
You should be able to unroot after installing twrp. Or use one of the ways to hide root from your apps.
[G2 Android Development] ST Dog:
[mention]blastigator[/mention]

Replaced lcd/glass on vs980. Appear it's a jdi screen. If it goes to sleep it wakes with white lines.

Has old 2.8.6.1 TWRP and xdabbeb vs982.5 ROM.

Try to flash TWRP 3.1.1-0 and when I swipe to flash the screen blinks and goes to white lines, just like when it sleeps.

I let it sit for 10 minutes and then forced a reboot.

Still old TWRP version.

Any suggestions?

EDIT:

Nevermind. Pulled recovery.img out of zip and manually flashed it.

Then booted to TWRP 3.1.1-0, and flashed zip. It worked and fixed TWRP.

Then I could fix the ROM. Flashed Dorimanx and lines issue solved.

Now to fix the xdabbeb boot image so the camera works.
[G2 Android Development] haldaios:
have problem with my phone I try open it and it continue reboot it self!! I try go to TWRP menu but only the logo of TWRP pops up and then it restart it self!! any help??
[G2 Android Development] runekock:
What did you do that made this happen?

Maybe you've flashed a bootstack for another model?

Anyway, the thing to do is flash KDZ back to stock. If it reboots even on stock, you may have a hardware fault.
[G2 Android Development] haldaios:
the problem is i didnt do anything new to the phone! also its the second time it happen with different rom, I flash the KDZ and now its working good again!! I installed older version of TWRP just to check. the roms I used was Resurrection remix the first time it happen and AOSP extended, now I installed lineage rom and TWRP 3.1.0-1 version.
[G2 Android Development] runekock:
Are you by any chance using f2fs or encryption? Your problem may be that the data partition becomes corrupted, and either f2fs or encryption might have such a bug.
[G2 Android Development] haldaios:
yeah im using f2fs on data and cache, the problem is on the rom or the twrp?
[G2 Android Development] runekock:
The rom performs a lot more writes, so my bet is on the kernel of the rom.

At the time the G2 was born, f2fs was very unstable. Different kernels have included more or less of the new patches for f2fs. In general, stay away from f2fs on old devices like the G2, unless the developer is highly focused on making it stable.
[G2 Android Development] haldaios:
thank you a lot!!! because now is fixed with F2FS again but with lineage now I will try my luck and if it happen again I will change it back again!!
[G2 Android Development] track21:
TWRP 3.2.0 is out!
[G2 Android Development] blastagator:
December 3, 2017 (3.2.0-0)

December 3, 2017 (3.2.0-0)

edit: Removed and replaced by 3.2.1 - see: https://xdaforums.com/showpost.php?p=74878662&postcount=2915

Some have asked if I am still around - as you can see, yes! Enjoy! :cool:
[G2 Android Development] desirexel:
Thanks man ..thanks so much
[G2 Android Development] Peregrinef:
Thank you Blastagator for the hard work but i had an issue with your latest version. I tried to make a full nandroid backup within TWRP twice and both ended up restarting into TWRP at some point (not the beginning) in the process without a success or fail message. I reverted back to previous nandroid backup only restoring the recovery partition (reverting back to your previous version of TWRP) and only after that it could complete the backup process. I have to mention that i did check checksum before flashing the new version so surely something went wrong with the new version on your side. Sorry to complain here but it's better to warn you before someone messing their phone.
[G2 Android Development] blastagator:
Backup of boot/system/data(excl storage) succeeded fine. What's your backup location? I'm using internal storage. Attach logs (include kernel log).
[G2 Android Development] Peregrinef:
I tried to backup all partitions and i also used internal storage (default directory to be precise). And i using the current Lineage OS for D802 without modifications except the official root plugin, if it's relevant. About that logs; it may take a while until i have the time, sorry.

Thank you for your interest by the way. Keep up the good work.
[G2 Android Development] metteduch:
V3.2.1.0 has been out for about a week :)
[G2 Android Development] Peregrinef:
I'll try that. :highfive:

Edit: Nope, it's not. (not Blastagator's anyway)
[G2 Android Development] blastagator:
December 17, 2017 (3.2.1-0)

(Bug fixes for 3.2.0)

-TWRP Change Log:

-TWRP 3.2.0 Change Log:

Version 3.2.0 has been removed.
[G2 Android Development] Peregrinef:
This update solved my backup problem. Thanks a lot.
[G2 Android Development] xttapolatakettle:
Warning about 3.2.1-0: If you're like me with a VS980 on Verizon, flashing 3.2.1-0 removes my ability to connect to mobile data. I've tried this a half-dozen times and consistently ended up with the same issue before narrowing it down to TWRP. Restoring System, Data, Cache, and/or EFS from backup does not fix it, nor does flashing a bootstack (aboot, dbi, laf, modem, persist, rpm, sbl1, tz). Not sure if this is a TWRP issue or a blastagator issue. But if you're using a VS980, do a full backup of all filesystems before upgrading. Not sure if a restore of Sensors or Misc will fix it, though. Maybe somebody else can test.
[G2 Android Development] j-sid:
Well ive had similar issues not sure if its the TWRP 3.2.1-0 or crDroidAndroid-7.1.2-20171119-vs980-v3.8.3.zip

soon as i updated to the latest rom & TWRP the signals were lost, tried everything, changed 3 different sims of different carriers but only got the 'no service'..

went back to stock, rooted again, installed the latest twrp, tried almost every possible custom rom to no avail.

Back to stock 5.0.2 as it my daily driver :(
[G2 Android Development] Zackptg5:
You do realize what twrp does right? It is literally a recovery img -> all of it is contained in the /recovery partition and so it doesn't mess with modem or telephony or anything else. Any issues your having is likely related to the rom you're on

Crdroid has never worked on my vs980 signal wise and most multi-variant g2 devices don't work with our verizon variant as they're based on d800, d802, or some other gsm based model (vs980 is cdma). The rom I've been using that fully works for me is AOSPExtended nougat (see my signature for link)
[G2 Android Development] j-sid:
that's wht got me confused, but ive been on crdroid for more then a year, never had an issue, lost the signals only after i updated to the latest version with the latest TWRP.

will definitely try the latest AOSPExtended, although didn't had any luck with clean install of AospExtended-v4.6-vs980-20171026-2252-OFFICIAL.zip :confused:
[G2 Android Development] ST Dog:
My son is running crDroid 3.8.x (not sure which) on a vs980 w/o issues. Recent install, but would have to verify version (TWRP was the current version at the time).this was mid Nov.

Came from xdabbeb's VS982.5. Also have to check, but think he has xdabbeb's 39A bootstack (last/LP one he did).

But I agree. TWRP shouldn't matter.
[G2 Android Development] xttapolatakettle:
I should clarify: I lose mobile data once I BOOT INTO TWRP. Only fix for me is to KDZ back to stock and stick with an older build of TWRP. Yes, the recovery is a fixed firmware, but the rilunning code does have access to all sorts of partitions.
[G2 Android Development] Sly_North:
Confirmed, I now have the same issue on my VS980: on crdroid, all's going fine for months. Today I decided to replace TWRP my 2.8.5 with his 3.2: boot in recovery, flash, wipe all caches, reboot, and... No signal anymore. The SIM seems to be detected properly, yet the phone cannot connect anymore to the network. :(

And yet, it happens... :(

If you Google for TWRP no signal, you'll find lots of such stories.

I think I'll have to flash back to stock and then upgrade.

EDIT:

- Flashing another recovery didn't fix it.

- Flashing again the (hybrid) bootstack didn't fix it.

- In the end, flashing cleanly CloudyG2 fixed it.

- Now I'm back on LO14 with TWRP3.2 and all's fine.
[G2 Android Development] ST Dog:
So no issue with an older TWRP and the same ROM?

Understand it has access to all the partitions/files on the device. But it shouldn't be touching anything that would break mobile data unless you explicitly touch the bootstack partitions. For sure just starting recovery shouldn't break anything.
[G2 Android Development] Mrx65:
So... Which is the latest safe twrp version for a d802?

I' ve to update my wife phone...

Thks

Inviato dal mio ONE A2003 utilizzando Tapatalk
[G2 Android Development] elTorres:
I use TWRP 3.2.1 in AEX 7.1.2 without any problems.

Enviado desde mi LG-D802 mediante Tapatalk
[G2 Android Development] blastagator:
1) If anyone wants to play guinea pig: Get vs980 working, install newest twrp, save log files (including kernel) from first boot of twrp (the one that presumably breaks the signal) and upload the logs. Not sure if I'll find something in there, but it is at least a starting point. I don't have a vs980 so I have no way to test.

2) What was latest version that didn't cause this to happen?

3) If you break the signal - extract the kdz and try restoring each partition one by one (not data/system/boot/recovery, but the other pieces). If you're able to figure out the one that brings signal back, report that as well.
[G2 Android Development] ST Dog:
I can't do any testing right now, but I did install crDroid on my vs980 over the weekend and it works fine*.

TWRP-3.2.1 blastigator

Xdabbeb 39a boot stack

crDroid 3.8.2

Magisk 14.0

* well except LTE reports as using Band 1 instead of 4 or 13. Just noticed that and started looking into it. May be Magisk related as I didn't notice until I installed it.
[G2 Android Development] Sly_North:
After a few weeks on Lineageos 14.1, I decided to give it a go. And of course TWRP 3.2 broke again the phone network signal.

Unfortunately I cannot read /dev/kmsg as this rom is not rooted by default. And I don't see anything useful in the normal logcat.

EDIT - Still, one weird thing: if I set the network to use GSM only or LTE only, the phone network status will be only "Emergency only"; if I set it to Global or any of the CDMA mode, it will show "No service|my operator name". What's weird here is I'm using a SIM to connect to my operator, none of the CDMA should be able to display its name, and only the SIM modes should. Yet the opposite is true: selecting a CDMA mode will display the SIM operator name. It's as if there was a mismatch between the O/S and the modem as to which of CDMA or GSM should be used.

So far the only way to restore the phone signal is to do a full reinstall of Android 4 or 5 (I flash Clougy G2 to do so).

2.8.7.3 worked fine. And I'm not too willing to try every versions in between as this is my daily phone.
[G2 Android Development] homa06:
I have the same network problems after updating to 3.2.1.0. Now there is a custom firmware on 5 android and there is one bugs - after rebooting in recovery mode and then rebooting the system, the network is unavailable. I'm ready to help you test the error, tell me what you need to do because it already has twrp 3.2.1.0 installed
[G2 Android Development] wyns01:
My wifi is disconnected in the hidden menu,how can i turn it on. Pls help
[G2 Android Development] 60nine:
and why would this be a twrp problem?
[G2 Android Development] Mrkblo:
Hi there. I have a jellybean D805 that has no USB connectivity (any PC shows as unknown device, and it's not a drivers problem). Anyway, I've managed to root and twrp it (2.7.0.0) and flashed a kitkat rom (slimkat) with no problems. I'm hoping to flash a newer rom on it, Cm12. 1 or Cm13 at least, and I'm wondering if under my conditions (phone never stock updated to kitkat or lollipop) I can update straight from twrp 2.7.0.0 to this version. Thanks in advance.
[G2 Android Development] BaschtlWaschtl:
I think you can update twrp.

It's just recovery, not Rom.
[G2 Android Development] yjgfikl:
Hey guys, I just updated from TWRP 2.8x (2.8.6 maybe? I forgot) to blastagator's 3.2.1-0 and also experienced the inability to connect to data. Though, as [MENTION=4856305]xttapolatakettle[/MENTION] mentioned it only happened once I booted back into TWRP after booting system and re-initializing all the apps. That first boot into the system I had data as normal. I only updated TWRP foolishly hoping I could have ROM slots like my older phones so I could flash Lineage 14.1 and keep the stock ROM.

Believe it or not, I ended up getting data back by simply pulling the SIM card with the phone on, waiting a few minutes, re-inserting it, and rebooting again back to system. I didn't re-flash anything or really do anything software-wise. I'll just avoid booting into TWRP unless I really need to I guess. Can't guarantee if this will work for anybody else but that's what I did.

[MENTION=5031300]blastagator[/MENTION], I didn't get the chance to pull the logs when I did it as I was kind of doing it on the go. Not sure if anything I said above helps.

I'm on a VS980 on stock rooted SW VS9803AA 5.0.2. build LRX22G. Hope this helps someone!