{
"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"
}
Infinity Kernel 3.0 - Download
Galaxy Tab A 2019 (SM-T510)
Code:
[B]DISCLAIMER:[/B]
I'm not responsible if you brick your device, etc. Use common sense. Don't try to flash this on any other device.
Features:
+ Built on BTFN source
+ Big Cores Overclocked 2.2 GHz
+ Little Cores Overclocked 1.7 GHz
+ Additional governors
+ Additional schedulers
+ zRAM enabled
+ dm-verity disabled
+ exFAT support on GSI
+ GSI and Stock versions
+ No-knox on GSI version
Changelog:
3.0
- Rebase to BTFN (10.0)
2.0
- Rebase to ATB4
- Experimental ExFAT for GSI roms
1.2.2
- Disable CONFIG_SEC_FACTORY to avoid 80% charging cap on GSI roms
1.2.1
- Implement MTP fix for GSI roms
1.2
- First public release
Source:
https://github.com/ibanezbass/gta3xlwifi-infinity-kernel
Thanks to @Magendanz for his No Knox code and GSI contributions.
RESERVED
Thanks for the kernel!
---------- Post added at 07:35 PM ---------- Previous post was at 07:05 PM ----------
what type of gsi roms should be flashed a64ab or arm64? or arm 32?
Battery won't charge
I have two T510 tablets with the Nexus ROM installed. I flashed the GSI kernel on both of them and everything appeared to work quite well. Checked with Antutu and results were impressive and showed the increased clock. But then I plugged them in to recharge but when I checked them sometime later, they had LOST charge. Ran the Ampere app on both, and it showed them as being plugged in but with a negative charge rate. Restored from backup and both are charging normally.
lewmur said:
I have two T510 tablets with the Nexus ROM installed. I flashed the GSI kernel on both of them and everything appeared to work quite well. Checked with Antutu and results were impressive and showed the increased clock. But then I plugged them in to recharge but when I checked them sometime later, they had LOST charge. Ran the Ampere app on both, and it showed them as being plugged in but with a negative charge rate. Restored from backup and both are charging normally.
Click to expand...
Click to collapse
Hmm. This issue is not present on the stock rom. I’ll do some research and get back to you.
ibanezbass said:
Hmm. This issue is not present on the stock rom. I’ll do some research and get back to you.
Click to expand...
Click to collapse
To check if this was a "smart chrager" problem, I re-installed the kernel and tried a regular charger. Discharge rate was even higher.
Fine for me
lewmur said:
I have two T510 tablets with the Nexus ROM installed. I flashed the GSI kernel on both of them and everything appeared to work quite well. Checked with Antutu and results were impressive and showed the increased clock. But then I plugged them in to recharge but when I checked them sometime later, they had LOST charge. Ran the Ampere app on both, and it showed them as being plugged in but with a negative charge rate. Restored from backup and both are charging normally.
Click to expand...
Click to collapse
I don't know but the kernel working fine for me no charging issues currently on the Nexus rom.
Tried on other random gsi's too works well!?
dylanmurzello said:
I don't know but the kernel working fine for me no charging issues currently on the Nexus rom.
Tried on other random gsi's too works well!?
Click to expand...
Click to collapse
Nexus_Stock_LOS_T510XXU2ASI4-20191109.tar.md5 is this the ROM you have installed? With two T510s, I can't see it as me being the only one with a problem.
edit: oops. It seems I have this build 2020-01-03-16-10-34_treble_a64_bvN-userdebug_9_PQ3A190801002_en but I don't remember where I got it.
lewmur said:
Nexus_Stock_LOS_T510XXU2ASI4-20191109.tar.md5 is this the ROM you have installed? With two T510s, I can't see it as me being the only one with a problem.
Click to expand...
Click to collapse
Yep that's the only time I installed and some magisk mod nfs injector and stuff,
I checked with ampere it's charging normally,I have 2gb variant btw.
dylanmurzello said:
Yep that's the only time I installed and some magisk mod nfs injector and stuff,
I checked with ampere it's charging normally,I have 2gb variant btw.
Click to expand...
Click to collapse
Hmmm!! I also have the 2gb version. I started from scratch with one of my tablets, but this time I skipped copying on startup so that I'd only have standard apps installed. The only app I installed is Ampere. Flashed the kernel and checked charging with Ampere. STILL DISCHARGING!!! Restored from backup and charging is back to normal.
lewmur said:
Hmmm!! I also have the 2gb version. I started from scratch with one of my tablets, but this time I skipped copying on startup so that I'd only have standard apps installed. The only app I installed is Ampere. Flashed the kernel and checked charging with Ampere. STILL DISCHARGING!!! Restored from backup and charging is back to normal.
Click to expand...
Click to collapse
I installed kernel with francokernel manager but I don't think that should make a difference?
dylanmurzello said:
I installed kernel with francokernel manager but I don't think that should make a difference?
Click to expand...
Click to collapse
When you installed the Nexus ROM, did you use the Odin or TWRP version? I used Odin.
lewmur said:
When you installed the Nexus ROM, did you use the Odin or TWRP version? I used Odin.
Click to expand...
Click to collapse
I used Odin too!
I don't know what's wrong then ,same setup.
Did you flash the gsi or normal kernel?
dylanmurzello said:
I used Odin too!
I don't know what's wrong then ,same setup.
Did you flash the gsi or normal kernel?
Click to expand...
Click to collapse
The GSI. I tried the normal one but that bootloop.
lewmur said:
The GSI. I tried the normal one but that bootloop.
Click to expand...
Click to collapse
Then did you flash the stock one?
Gsi one works good for me
dylanmurzello said:
Then did you flash the stock one?
Gsi one works good for me
Click to expand...
Click to collapse
Howcan I state more plainly. I TRIED BOTH!!!!!!! The stock one bootloops. The GSI one works except for the charging problem.
I updated to the Nexus ASK1 ROM and didn't copy any apps from previous install. Install only Antutu and Ampere as apps. Everything appears to work. So I tried again with the Infinity GSI kernel. Antutu didn't improve very much and, again, the battery wouldn't charge so I had to restore from my TWRP backup.
BTW: I also downloaded the kernel zip again to make sure my copy wasn't corrupted.
I got a problem! After installing the kernel, my tablet won't charge to more than 80%
DKzVeNgEnS said:
I got a problem! After installing the kernel, my tablet won't charge to more than 80%
Click to expand...
Click to collapse
I was begining to think I was the only one with this problem. When I tested my two, they were already above 80%, so they appeared to not be charging at all. But I just re-installed the kernel on one of them at let it stream a movie till the battery dropped to 70%. Then it did start to take a charge, but it only reached 79%. I seem to recall people having this problem on other ROMs.
DKzVeNgEnS said:
I got a problem! After installing the kernel, my tablet won't charge to more than 80%
Click to expand...
Click to collapse
After a little research, I think I've found the source of the problem but not the solution. It seems Samung has a feature called "Battery Life Extender" that prevents the battery from charging past 80%. This is supposed to extend the life cycles of the battery. There is supposed to be a setting to turn this feature off so that the battery can be fully charged, but I can't find it. It may require an edit to the build.prop.
Related
Yesterday I flashed the Cyanogenmod 7 Rom on my girlfriends P500.
Actually, everything seemed to work fine, but after some time device crashes and following error screen appears:
{
"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"
}
After a reboot everything is fine again, but after some time, the error appears another time. Happend 3 times now
I have never seen this screen on any device, so I don't know what to do
Does anyone have an idea?
Information:
Optimus One P500
[stable build: beta6.3] CyanogenMod 7.0.2 by mik_os
latest darktremors app2sd
Che123 said:
Yesterday I flashed the Cyanogenmod 7 Rom on my girlfriends P500.
Actually, everything seemed to work fine, but after some time device crashes and following error screen appears:
After a reboot everything is fine again, but after some time, the error appears another time. Happend 3 times now
I have never seen this screen on any device, so I don't know what to do
Does anyone have an idea?
Information:
Optimus One P500
[stable build: beta6.3] CyanogenMod 7.0.2 by mik_os
latest darktremors app2sd
Click to expand...
Click to collapse
this might help u http://code.google.com/p/openetna/issues/detail?id=292
go for a clean install use the zip provided by mik for bootloop it will erase the system properly or use adb instead to wipe then procede with the installation of cm 7 latest built 2.4.2
shhbz said:
this might help u http://code.google.com/p/openetna/issues/detail?id=292
go for a clean install use the zip provided by mik for bootloop it will erase the system properly or use adb instead to wipe then procede with the installation of cm 7 latest built 2.4.2
Click to expand...
Click to collapse
Thanks for that link. I am going to have a look at this.
Actually I don't think, that it's the bug with the /system wipe which is causing this problem, since everything else works fine.
But if I am going to reflash everything, I gonna give that a try
The device is fresh rooted - do I need a custom radio or other prerequisites, to run this rom?
Che123 said:
Thanks for that link. I am going to have a look at this.
Actually I don't think, that it's the bug with the /system wipe which is causing this problem, since everything else works fine.
But if I am going to reflash everything, I gonna give that a try
The device is fresh rooted - do I need a custom radio or other prerequisites, to run this rom?
Click to expand...
Click to collapse
which recovery are you using and u dont need any radio etc
shhbz said:
which recovery are you using and u dont need any radio etc
Click to expand...
Click to collapse
ok, nice
I flashed this recovery: recovery-RA-GNM-thunderg - i think it's version 1.1.0
I don't have the phone here now, so I cant say it for sure
Che123 said:
ok, nice
I flashed this recovery: recovery-RA-GNM-thunderg - i think it's version 1.1.0
I don't have the phone here now, so I cant say it for sure
Click to expand...
Click to collapse
why dont u try the latest one http://androidforums.com/getitnowmarketing/330813-all-one-recovery-thread.html
here it is orelse go for clockwork its great i like it better than thunderg but it doesnt support flashing all roms at this point but cm7 works with it any many others 2 but cant name them all and avoid using a2sd if u dont have a class 4 sd card atleast as it works great without a2sd some users find difficulties even after using a good sd card
shhbz said:
why dont u try the latest one http://androidforums.com/getitnowmarketing/330813-all-one-recovery-thread.html
here it is
Click to expand...
Click to collapse
ah damn
i didn't see that one. I don't really know much about this device, since I own another one - so thanks for your help
This evenning, I gonna flash the new recovery, and reflash everything again. I will report back
Thanks again for your help
edit: I have the same problem with clockwork recovery on my desire - I had to switch back to an older version. So I am not really satisfied with this recovery atm
Che123 said:
ah damn
i didn't see that one. I don't really know much about this device, since I own another one - so thanks for your help
This evenning, I gonna flash the new recovery, and reflash everything again. I will report back
Thanks again for your help
edit: I have the same problem with clockwork recovery on my desire - I had to switch back to an older version. So I am not really satisfied with this recovery atm
Click to expand...
Click to collapse
i will make it easier for u flash this http://forum.xda-developers.com/showthread.php?t=1065197
or clockwork http://forum.xda-developers.com/showthread.php?t=1024838
both are working so need to go through the process again just flash remember if u choose to flash the first 1 just select toggle signature option before flashing the file
Are you overclocking it? If yes then try to lower you max frequency.
shhbz said:
i will make it easier for u flash this http://forum.xda-developers.com/showthread.php?t=1065197
or clockwork http://forum.xda-developers.com/showthread.php?t=1024838
both are working so need to go through the process again just flash remember if u choose to flash the first 1 just select toggle signature option before flashing the file
Click to expand...
Click to collapse
I am not new to android - i am only new to the p500
but thanks for that links - makes it a bit more comfortable
I think I gonna give that first one a try.
verification is already deactivated
ungaze said:
Are you overclocking it? If yes then try to lower you max frequency.
Click to expand...
Click to collapse
Nope. No overclocking - everything stock so far.
Che123 said:
I am not new to android - i am only new to the p500
but thanks for that links - makes it a bit more comfortable
I think I gonna give that first one a try.
verification is already deactivated
Click to expand...
Click to collapse
same here old to hd 2 ,new for p500
shhbz said:
same here old to hd 2 ,new for p500
Click to expand...
Click to collapse
since it's not my own phone, I am not so enthusiastic anyway
Let's just hope, everything works fine this evening
Bad news
Just spent the last couple of hours installing everything once again:
- updated to latest recovery
- wiped everything (even wiped /system manually via adb)
- flashed cm7
- flashed gapps
- reboot
- flashed latest darktremor apps2sd
- restore apps and setup rom
everything worked fine again, but after playing around with it, the keys started to flash again, screen freezes and system crashes (for now without the black screen from first post) - I'm not able to obtain the systemlog, so I can't even get a direction.
Any further suggestions please?
Edit:
In the logcat i get this line every 3 seconds:
D - 1776 - WifiService - ACTION_BATTERY_CHANGED pluggedType:2
Even if there is nothing plugged in - but only when wifi is turned on.
But the device also crashes, if wifi is not activated
I got exactly the same error screen from the first page this morning again
Another thing I noticed: The battery behaviour is very strange. I had 100% - crashed after 10 min -> 19% after reboot - but counting slowly up again. Now I am @ 46%.
edit2:
After removing app2sd and fix connection issues for gapps, everything went fine for a while. But once again: error screen appears >.<
I am going to flash .void now - and hope the issues were rom-based and not an error in the device
{
"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"
}
* Your warranty is now void.
Untested build. I don't have the device. Someone with some balls please make a back up and give this a try and get back to me.
Any root issues http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
ROM: pulled
GAPPS: http://goo.im/devs/BaNkS/GApps%204.3
Thanks to the guys over at cyanogen, google, and uXylon.
Will have to give it a shot tonight
Sent from my SGH-I777 using Tapatalk 2
I flashed it, it booted into android fine but every time I selected start on the first setup screen it would reboot. Now I can't get into recovery, however I have a broken power button which might be causing complications. I'm working on getting back into recovery but this is an old phone so if I don't get it working, its no big deal.
s33d1ing said:
I flashed it, it booted into android fine but every time I selected start on the first setup screen it would reboot. Now I can't get into recovery, however I have a broken power button which might be causing complications. I'm working on getting back into recovery but this is an old phone so if I don't get it working, its no big deal.
Click to expand...
Click to collapse
Damn that is horrible. Power button doesn't work at all? Have you trye taking it apart and cleaning the contactors? What recovery do you have? Is there only one option? can you op to setup gapps later? You can always try using fastboot to get in there.
RBMacGregor said:
Damn that is horrible. Power button doesn't work at all? Have you trye taking it apart and cleaning the contactors? What recovery do you have? Is there only one option? can you op to setup gapps later? You can always try using fastboot to get in there.
Click to expand...
Click to collapse
I have taken the phone apart but I still couldn't get the power button to work. Anyhow, I just got everything restored and I'm going to try flashing it again. :laugh:
Okay, I just flashed the rom this time. It boots into android but when I try to open any app, the phone reboots.
s33d1ing said:
I have taken the phone apart but I still couldn't get the power button to work. Anyhow, I just got everything restored and I'm going to try flashing it again. :laugh:
Okay, I just flashed the rom this time. It boots into android but when I try to open any app, the phone reboots.
Click to expand...
Click to collapse
haha you have balls Ill give you that! Had me worried hate to brick someones device. Could you possibly logcat it? I think I need to change the tool chain compiling the kernel googles using 4.7 now and I'm not sure cyanogen is ready out of the box for it. Ill try with 4.6 tomorrow.
RBMacGregor said:
haha you have balls Ill give you that! Had me worried hate to brick someones device. Could you possibly logcat it? I think I need to change the tool chain compiling the kernel googles using 4.7 now and I'm not sure cyanogen is ready out of the box for it. Ill try with 4.6 tomorrow.
Click to expand...
Click to collapse
I cant get into settings to turn on usb debugging because the phone restarts every time I open settings. Is there any way to make a logcat in this situation?
s33d1ing said:
I cant get into settings to turn on usb debugging because the phone restarts every time I open settings. Is there any way to make a logcat in this situation?
Click to expand...
Click to collapse
See if you can download catlog and get the log that way for him.
Good luck.
Sent from the i777
I got a soft brick. Good thing I had a Jtag because I could not even get into download by button combination.
You may want to check and see if the i777 repo has even been updated to a useable state, as it had not been a few days ago when I last checked.
The kernel works but the ROM itself doesn't do much.
I have ported the CM 10.2 unofficial build pulled from GT-I9100 forum and I flashed it. All I can say is it worked fine but still is unstable..highly unstable. I used d default kernel and changed the modules and keypad script. It booted well and was fast. But phone heating issue and couple of FC's us what I encountered. And battery life issues.
Sent from my SGH-I777 using xda premium
AJ Newkirk said:
You may want to check and see if the i777 repo has even been updated to a useable state, as it had not been a few days ago when I last checked.
The kernel works but the ROM itself doesn't do much.
Click to expand...
Click to collapse
I had to make some changes to the i777 device tree to get it to build. Im gonna give it another go after work today.
twcobra said:
I got a soft brick. Good thing I had a Jtag because I could not even get into download by button combination.
Click to expand...
Click to collapse
**** soft brick? How the hell did that happen. Boot loader went off without a hitch.
RBMacGregor said:
**** soft brick? How the hell did that happen. Boot loader went off without a hitch.
Click to expand...
Click to collapse
Not sure what caused it. I had installed GAPPS with all the extras. Next time I try I will just install the ROM and the GAPPS core. Then the extra stuff one at a time. Believe me I started getting nervious when I could not get into download by button combo. I started breathing easy when I found my Jtag pluged it in and went rite to download on power up.
Anyone know why the rom was pulled?
Spinergy02 said:
Anyone know why the rom was pulled?
Click to expand...
Click to collapse
4.3.3 versions have TRIM Implementation ....and our devices aren't design for SSD overwrite deleted blocks
Sent from my SGH-M919 using xda premium
samprocat said:
4.3.3 versions have TRIM Implementation ....and our devices aren't design for SSD overwrite deleted blocks
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
TRIM would not be implemented on anything for our device. The SII version of CM10.2 and anything based off of CM10.2 trees would not contain TRIM.
I haven't made any calls but I sure hope I'm not having mic issues on 4.0 because voltage control is a really big deal to me and I don't want to upgrade.
Could someone explain why TRIM wouldn't be good for our devices?
RBMacGregor said:
**** soft brick? How the hell did that happen. Boot loader went off without a hitch.
Click to expand...
Click to collapse
I've had the same thing, doing pretty much nothing!
Fresh install, wiped everything, from system to memory card, plugged into USB transferring some files and BOOM, brick. Wipe again, reinstall, continue copying some files and brick again.
Needless to say I am sticking to 10.1 for a while longer.
Hi Fellas.
I've got recently Galaxy s2.
It has old OS (2.3.5)
I would like to install CianogenMod10.2 or something similar.
The problem with this phone - It has completely broken usb socket. I charge the battery exernally.
I cannot use built-in bootloader, which works with Odin - because , again, usb is not working.
It also has some other bootloader (Powerup +Select button +volume UP) - which looks like CWM - but it's not CWM - because phone has stock firmware from Orange mobile company. This loader has even option to install zip from SD card - But when I try to install cm-10.2-20130824-NIGHTLY-i9100.zip ( latest cianogenmod) - it gives an error - that image is NOT SIGNED.
Is there anything I can do ?
Please advice
junglemike said:
Hi Fellas.
I've got recently Galaxy s2.
It has old OS (2.3.5)
I would like to install CianogenMod10.2 or something similar.
The problem with this phone - It has completely broken usb socket. I charge the battery exernally.
I cannot use built-in bootloader, which works with Odin - because , again, usb is not working.
It also has some other bootloader (Powerup +Select button +volume UP) - which looks like CWM - but it's not CWM - because phone has stock firmware from Orange mobile company. This loader has even option to install zip from SD card - But when I try to install cm-10.2-20130824-NIGHTLY-i9100.zip ( latest cianogenmod) - it gives an error - that image is NOT SIGNED.
Is there anything I can do ?
Please advice
Click to expand...
Click to collapse
you can try to flash philz kernel. search in original android development section
Sent from my GT-I9100 using xda app-developers app
@junglemike - if u have a broken usb ...i seriously suggest u not to try cm10.2
if recovery doesnt works (like 2 nightlies before) u will be doomed.
I will check this out.
This is a boot loader that I have apart from stock recovery mode:
{
"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"
}
I'm not sure what it is.
Not sure if this helps.
junglemike said:
I will check this out.
This is a boot loader that I have apart from stock recovery mode:
I'm not sure what it is.
Not sure if this helps.
Click to expand...
Click to collapse
this is the stock android recovery present only wid stock roms.. not present in cm..it will be overwritten by cwm recovery
doctor_droid said:
this is the stock android recovery present only wid stock roms.. not present in cm..it will be overwritten by cwm recovery
Click to expand...
Click to collapse
Thanks.
I understand the risks, I could install stable CM 10 version, or some other stable version.
If only I could figure out hot to install CWM...
junglemike said:
Thanks.
I understand the risks, I could install stable CM 10 version, or some other stable version.
If only I could figure out hot to install CWM...
Click to expand...
Click to collapse
just find the philz kernel zip that can be flashed from stock recovery then flash neatrom. reboot. than flash cm10 or whatever you want
Sent from my GT-I9100 using xda app-developers app
hacklana said:
just find the philz kernel zip that can be flashed from stock recovery then flash neatrom. reboot. than flash cm10 or whatever you want
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I have tried what you suggested:
I downloaded and tried to flash PhilZ touch 3.0.0 temporary flash (file: philz-touch_3.00_i9100-signed.zip)
But it gives me same error: cannot verify the signature.
What I am missing.
Some more questions, sorry if they are too basic
1) PhilZ-cwm6 - Safe Stock Based Kernel - there are many kernels. Which one to choose? This is kernel info of my phone, if it helps:
2) Suppose I succeed to flash PhiZ, why do you suggest to flash neatrom first? why not CM10 right away?
Dear @junglemike,
There is no Philz kernel for gingerbread. Nor will any temporary CWM work on GB!
The way I see it, messing with a phone having a bad USB port is like playing with fire. If something goes wrong, you will have to resort to flashing via Odin (which u can't).
So I suggest you repair the USB port (you can do it yourself too) first.
"To err is human, to forgive is divine."
Sent from my SGS II
Yep. You're nuts messing with your phone with a busted USB port. If anything goes even slightly badly, and it does for almost everyone at some stage, you won't be fixing it.
I am starting to think that you are right.
By the way, friend gave me this phone, because he dropped it in a water, and USB never worked after that. I verified that it is not a bad contact issue. I checked with a tester that all 4 contacts are getting through to the motherboard. Probably some chip got burned when when that friend connected charger when phone was still wet.
I just wanted to upgrade because this jingerbread looks really ugly.
I guess I will stay with that anyway.
Is there any app to replace that ugly unlock screen at least? With something similar to jb4.2 ? I mean a enter point that you move from the. Enter to the right to unlock the phone
Sent from my Galaxy Nexus using Tapatalk 2
I've used widgetlocker before with success. Buy the app and then look on xda for widgetlocker themes, there's literally hundreds
Sent from a galaxy far, far away
junglemike said:
I am starting to think that you are right.
By the way, friend gave me this phone, because he dropped it in a water, and USB never worked after that. I verified that it is not a bad contact issue. I checked with a tester that all 4 contacts are getting through to the motherboard. Probably some chip got burned when when that friend connected charger when phone was still wet.
I just wanted to upgrade because this jingerbread looks really ugly.
I guess I will stay with that anyway.
Is there any app to replace that ugly unlock screen at least? With something similar to jb4.2 ? I mean a enter point that you move from the. Enter to the right to unlock the phone
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
why not update OTA?
ZVA-Lollipop!
Brought to you by
{
"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"
}
This is BONE STOCK. It only has Root, Kernel, and Modem/Radio
See post #2 for some important info
See post #3 for extra files/fixes
Install instructions:
1. Flash this in TWRP - MAKE SURE YOU CLEAN FLASH THIS!
In TWRP, select Wipe>Advanced>then select cache, dalvic, data,and system. DO NOT select int or ext SD.
2. Flash Rom
3. Profit!
After install:
Go to Settings>System Updates> and update profile/prl. You can also go to "Activate this device".
If you do not have Sprint bootani or Wifi Calling
You will need your MSL number and do the dialer reset. So in the Dialer ##786#. This will wipe your int SD!! And everthing else, so you will be starting fresh.
Bugs:
None that I know of.
Downloads:
Stock_ZVA_Odexed
Stock_ZVA-Odexed-using-updater-script - This has root, busybox, init.d, and Selinux permissive, only. NO MODEM.
If you use this one, pattern unlock will lockup the phone requiring a battery pull!!!
You do not need to flash this if you're already updated. This is just for those that want to modify the zip before installing. Actually, either one will update you to ZVA.
Deodexed System files only
XDA:DevDB Information
Stock_ZVA_L_Odexed, ROM for the Sprint LG G3
Contributors
engine95, HPTesla, seanskiT!
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Stable Release Date: 2015-06-25
Created 2015-06-26
Last Updated 2015-06-25
Hints, Tips and stuff
You will more than likely need to follow the steps above to get WIFI Calling. I would suggest doing this in the beginning so you don't lose all your work!!!!! I haven't gotten this far yet, but I think it wipes your SD. Make sure to back it up first!!
It didn't wipe internal SD!!! But better safe than sorry
Backup your EFS first!!! Just to be safe - In the FAQ
A dialer reset may be required for a lot of the issues. In order, easy to most invasive.....
##UPDATE#
or
##SCRTN#
or the biggie - which fixes bootani and Wifi calling
##RTN# - requires your MSL. You will need to either call Sprint. Or, follow THIS
Files and fixes
Sd Card fix
Increased mixer paths
Stock kernel with init.d support and Selinux permissive - you must have busybox installed for this to work.
Deodexed files only Not flashable
Do you know if your Navel Kernel works on it?
Jimmy50941 said:
Do you know if your Navel Kernel works on it?
Click to expand...
Click to collapse
I haven't tried that yet. Still experimenting with this new rom.
I know I need to modify for the ext sd though. But that's not a big deal.
engine95 said:
I haven't tried that yet. Still experimenting with this new rom.
I know I need to modify for the ext sd though. But that's not a big deal.
Click to expand...
Click to collapse
Do you think that would cause problems trying it? I dont even use external SD right now.
I almost have the rom downloaded. its slowly downloading at 1.3mbps :-/ lol
---------- Post added at 06:47 PM ---------- Previous post was at 06:45 PM ----------
Jimmy50941 said:
Do you think that would cause problems trying it? I dont even use external SD right now.
I almost have the rom downloaded. its slowly downloading at 1.3mbps :-/ lol
Click to expand...
Click to collapse
edit: Its done downloading, but phone isn't charged enough at the moment for me to feel like flashing. ill give it an hour or so.
Jimmy50941 said:
Do you think that would cause problems trying it? I dont even use external SD right now.
I almost have the rom downloaded. its slowly downloading at 1.3mbps :-/ lol
---------- Post added at 06:47 PM ---------- Previous post was at 06:45 PM ----------
edit: Its done downloading, but phone isn't charged enough at the moment for me to feel like flashing. ill give it an hour or so.
Click to expand...
Click to collapse
Make a backup first. Then try it. I'll try it tomorrow just cuz I'm curious too.
If you get slow dl from there, just pick another server. That usually works.
Navel kernel doesn't work for this rom. Just flashed it and got a security error on boot
See post #3 for files and fixes. All flashable in TWRP
What changes in ZVA?
Nav-bar and status bar are missing, don't know what happened. Came from [ROM][GSM/[Stock 5.0.1]PRIMEGSM (V3.1), full wiped including internal.
Lurien said:
What changes in ZVA?
Click to expand...
Click to collapse
Just little things really. Nothing major.
Mostly I've noticed the WiFi calling just has the icon now.
scorpic1978 said:
Nav-bar and status bar are missing, don't know what happened. Came from [ROM][GSM/[Stock 5.0.1]PRIMEGSM (V3.1), full wiped including internal.
Click to expand...
Click to collapse
You probably need to do one of the dialer codes I've posted in other threads.
##UPDATE#
##SCRTN#
or the biggie
##RTN# - you need your msl for that one
@engine95 so this will
Not give me security error on boot because of autorec is already installed? Also Is it possible to get this deodexed i am running barepops zv8 deodexed now.
Sent from my LGLS990 using Tapatalk
Just wondering, Im new to LG and just wondering if this will include the modem when i flash it or will i flash this and still have ZV8 modem?
galaxyhero said:
@engine95 so this will
Not give me security error on boot because of autorec is already installed? Also Is it possible to get this deodexed i am running barepops zv8 deodexed now.
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
I don't know about autorec. Make a backup then flash this rom. It should work.
Gimme some time. I just put this out yesterday.
JG96EVO said:
Just wondering, Im new to LG and just wondering if this will include the modem when i flash it or will i flash this and still have ZV8 modem?
Click to expand...
Click to collapse
Sorry, forget to say, kernel, modem and system are in the zip. But the modem has the same number, just a tiny bit smaller.
So this will not give lg security error on reboot?can anyone confirm.
Sent from my LGLS990 using Tapatalk
engine95 said:
Just little things really. Nothing major.
Mostly I've noticed the WiFi calling just has the icon now.
You probably need to do one of the dialer codes I've posted in other threads.
##UPDATE#
##SCRTN#
or the biggie
##RTN# - you need your msl for that one
Click to expand...
Click to collapse
Ok.. But does it feel or run better than ZV8 at all?? I downloaded this morning but haven't had time to flash yet. Thanks..
@engine95 how did you bump the kernel. I tried bumping the kernel and it would not boot. Is it okay for me to just take your kernel out of the zip file? I assume that you had to keep the padding. Is there a new bump tool because the one that I use breaks stuff.
l33tlinuxh4x0r said:
@engine95 how did you bump the kernel. I tried bumping the kernel and it would not boot. Is it okay for me to just take your kernel out of the zip file? I assume that you had to keep the padding. Is there a new bump tool because the one that I use breaks stuff.
Click to expand...
Click to collapse
You're more than welcome to use it. Just give credit.
I had to unpack and repack it a different way. Sneaky LG/Sprint. Try using "Android Image Kitchen." mkbootimg tools didn't work as the compression is different.
Your bump should work this way.
I haven't got the fixes/kernel, but this rom feels a lot faster for me. only problem, which might be attributed to the kernel, is my battery died today after 4 hours (died before noon) of sitting in my pocket lol but i work in a building with absolutely no cell service, but usually my phone lasts all day at work, and i have to charge when i get home, or on the way home.
And i did try the Bare Navel Kernel last night before i went to bed, and got the LG Security error trying to boot up.
Removes Lockscreen wallpaper dimming tint and Notification pulldown also. Flash in TWRP. For stock roms.
Pie uploaded 9-5-18
Magisk version
https://www.androidfilehost.com/?fid=1322778262903998215
Regular version
https://www.androidfilehost.com/?fid=1322778262903998217
-------------------------------------
DP4
https://www.androidfilehost.com/?fid=5862345805528052635
DP4 Magisk version
https://www.androidfilehost.com/?fid=5862345805528053142
8.1 July update
https://www.androidfilehost.com/?fid=5862345805528052638
8.1 July update Magisk version
https://www.androidfilehost.com/?fid=5862345805528053118
{
"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"
}
Magisk installer causes bootloop. Module not listet in Magisk (using Magisk Manager for Recovery Mode) = can't remove / uninstall. You don't happen to have a way to revert this, do you?
EDIT: Nevermind. Going to reflash stock image.
EDIT 2: Well, I'm stuck. Flashed a factory image without wiping (removed -w from flash-all.bat) and now it won't boot at all. Stuck on splash screen.
"Your device is corrupt. It can't be trusted and may not work properly."
nitrous² said:
Magisk installer causes bootloop. Module not listet in Magisk (using Magisk Manager for Recovery Mode) = can't remove / uninstall. You don't happen to have a way to revert this, do you?
EDIT: Nevermind. Going to reflash stock image.
EDIT 2: Well, I'm stuck. Flashed a factory image without wiping (removed -w from flash-all.bat) and now it won't boot at all. Stuck on splash screen.
"Your device is corrupt. It can't be trusted and may not work properly."
Click to expand...
Click to collapse
You need to clean flash i guess
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
You need to clean flash i guess
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Clean flash a theme? For real? Whatever. Don't care anymore. Had to factory reset and wipe the internal storage, since, well, encrypted. *Sarcasm on* My fast German internet connection will restore my apps in no time and I don't mind the lost data at all *sarcasm off*.
nitrous² said:
Clean flash a theme? For real? Whatever. Don't care anymore. Had to factory reset and wipe the internal storage, since, well, encrypted. *Sarcasm on* My fast German internet connection will restore my apps in not time and I don't mind the lost data at all *sarcasm off*.
Click to expand...
Click to collapse
No i meant you need to clean flash stock image which you did
Sent from my Google Pixel 2 XL using XDA Labs
nitrous² said:
Clean flash a theme? For real? Whatever. Don't care anymore. Had to factory reset and wipe the internal storage, since, well, encrypted. *Sarcasm on* My fast German internet connection will restore my apps in no time and I don't mind the lost data at all *sarcasm off*.
Click to expand...
Click to collapse
Always try a factory reset in TWRP first. You have to set your phone up as new but you don't lose internal data. We're you bone stock? Did you flash in TWRP?
Tulsadiver said:
Always try a factory reset in TWRP first. You have to set your phone up as new but you don't lose internal data. We're you bone stock? Did you flash in TWRP?
Click to expand...
Click to collapse
AHH! GOD F***ING DAMMIT!! Should've thought about a factory reset in TWRP. I was able to boot into it.
Yes, stock ROM, stock Kernel. Only modification was Magisk 16.7 and a user certificate installed into the system store (AdGuard).
nitrous² said:
AHH! GOD F***ING DAMMIT!! Should've thought about a factory reset in TWRP. I was able to boot into it.
Yes, stock ROM, stock Kernel. Only modification was Magisk 16.7 and a user certificate installed into the system store (AdGuard).
Click to expand...
Click to collapse
I went back to stock, rerooted, installed Magisk and flashed this on my pixel and it worked fine.
Tulsadiver said:
I went back to stock, rerooted, installed Magisk and flashed this on my pixel and it worked fine.
Click to expand...
Click to collapse
Ok, I just noticed it says "for the Google Pixel(sailfish)" on AFH and I also noticed you saying "flashed this on my pixel". Any chance this mod is meant for the Pixel 1 / XL and not the Pixel 2 / XL (Taimen)?
I've attached a log from an attempted Magisk install.
nitrous² said:
Ok, I just noticed it says "for the Google Pixel(sailfish)" on AFH and I also noticed you saying "flashed this on my pixel". Any chance this mod is meant for the Pixel 1 / XL and not the Pixel 2 / XL (Taimen)?
I've attached a log from an attempted Magisk install.
Click to expand...
Click to collapse
It says that because it is located in the root folder for my pixel phones. Inside that they all have their own folders.
Log says it installed but config file failed to inflate but it worked fine on mine.
The pixel phones are so much alike you can often flash a whole systemuigoogle.apk and framework-res.apk if you omit the meta-inf and Android manifest. Not always though.
Tulsadiver said:
It says that because it is located in the root folder for my pixel phones. Inside that they all have their own folders.
Log says it installed but config file failed to inflate but it worked fine on mine.
The pixel phones are so much alike you can often flash a whole systemuigoogle.apk and framework-res.apk if you omit the meta-inf and Android manifest. Not always though.
Click to expand...
Click to collapse
Ok, I see. Yeah, not sure what to tell you. The install via TWRP for both the Magisk and standard install variant seemed to work fine. I first tried the regular installer and after the phone was bootlooping I tried installing the Magisk version. I don't want to risk a bootloop for the sake of a test. It took me close to 10 hours to redownload my apps and restore my WhatsApp backup. That's thanks to our glorious German internet #neuland.
nitrous² said:
Ok, I see. Yeah, not sure what to tell you. The install via TWRP for both the Magisk and standard install variant seemed to work fine. I first tried the regular installer and after the phone was bootlooping I tried installing the Magisk version. I don't want to risk a bootloop for the sake of a test. It took me close to 10 hours to redownload my apps and restore my WhatsApp backup. That's thanks to our glorious German internet #neuland.
Click to expand...
Click to collapse
Sorry to hear that. If by bootlooping you mean stuck on Google, I have gotten past that by simply rebooting my phone. Magisk is always a problem child. This is not a module but a vrthemer capable of installing to the Magisk image. I suggest to people that they uninstall Magisk, reroot, use the regular installer to get their phone like they like, then install and use Magisk manager. My Aroma installer has this mod, all the way at the bottom, and others as well and is edge sense capable. Just install the app, not the module.
Tulsadiver said:
Sorry to hear that. If by bootlooping you mean stuck on Google, I have gotten past that by simply rebooting my phone. Magisk is always a problem child. This is not a module but a vrthemer capable of installing to the Magisk image. I suggest to people that they uninstall Magisk, reroot, use the regular installer to get their phone like they like, then install and use Magisk manager. My Aroma installer has this mod, all the way at the bottom, and others as well and is edge sense capable. Just install the app, not the module.
Click to expand...
Click to collapse
Bootlooping as in; Startup > G Logo loading screen > Black screen (abrupt power off) > Startup > G Logo loading screen > Black screen (abrupt power off) > ∞
Reflashing a factory image (same ASB version) interrupted the loop by booting into some sort of recovery where it said that my device is corrupted and may not work properly and suggested I make a data wipe/factory reset.
nitrous² said:
Bootlooping as in; Startup > G Logo loading screen > Black screen (abrupt power off) > Startup > G Logo loading screen > Black screen (abrupt power off) > ∞
Reflashing a factory image (same ASB version) interrupted the loop by booting into some sort of recovery where it said that my device is corrupted and may not work properly and suggested I make a data wipe/factory reset.
Click to expand...
Click to collapse
The mod is definitely for Pixel 2XL. My pixel had rounded corners on the statusbar that goes with the curved display of pixel 2 xl. If you can upload your SystemUIGoogle.apk I'll try and make one for your phone. Maybe yours is different from the system image I extracted.
Tulsadiver said:
The mod is definitely for Pixel 2XL. My pixel had rounded corners on the statusbar that goes with the curved display of pixel 2 xl. If you can upload your SystemUIGoogle.apk I'll try and make one for your phone. Maybe yours is different from the system image I extracted.
Click to expand...
Click to collapse
Oh, man! That's so nice of you =) But I have to decline. I need a working phone by tomorrow and can't risk it.
nitrous² said:
Oh, man! That's so nice of you =) But I have to decline. I need a working phone by tomorrow and can't risk it.
Click to expand...
Click to collapse
Maybe later.
Tulsadiver said:
Maybe later.
Click to expand...
Click to collapse
No, I meant like; Here is my SystemUIGoogle.apk but I can't report back if it did work until next weekend.
nitrous² said:
No, I meant like; Here is my SystemUIGoogle.apk but I can't report back if it did work until next weekend.
Click to expand...
Click to collapse
Your framework-res apk must be different than what I show it should be. You will need to upload yours. That might be the problem.
Edit: never mind. I was thinking you were on DP5 but you are on 8.1. I used the wrong framework.
Tulsadiver said:
Your framework-res apk must be different than what I show it should be. You will need to upload yours. That might be the problem.
Edit: never mind. I was thinking you were on DP5 but you are on 8.1. I used the wrong framework.
Click to expand...
Click to collapse
So you no longer need my framework-res.apk?
nitrous² said:
No, I meant like; Here is my SystemUIGoogle.apk but I can't report back if it did work until next weekend.
Click to expand...
Click to collapse
Here is a regular version and Magisk version.