Database Users

[Q] My nexus 7 went down from 16gb to 8gb

Hello to all,
I have a big problem. I own Nexus 7 (2012) version with 16gb, but when I flashed KitKat 4.4.2 (KOT49H) via Wug's Nexus Root Toolkit v1.7.9, my Nexus went down to 8gb version (actually, I got only 5.9gb free space).
How is this posible? To went from 16gb model to 8gb model and most important, how do I get back to original 16gb of storage?
edit:haha, I don't know how but solution was this: I did full wipe and format data via cwm. Then it said that I dont have OS installed. So, again I used Wug's Nexus Root Toolkit v1.7.9, only now I flashed 4.4 KRT16S. And on my biggest surprise, now I got 27gb free space. I loaded it with movies and it's real space.
I thought that I know something about android, but now I'm confused very much. Merry Christmas to me with this extra gift
P.S. And to all of you ofcourse.
P.P.S. Would somebody like to try this also? Maybe you get extra 16gb, too!

Screen shot?
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM 4.3.

Do a search. This isn't a new phenomenon; it only happens to rooters. Somehow, an undersized ext4 filesystem gets created in the userdata partition (which is substantially larger).
The exact origin of the problem is not clear, but is probably a bug in the bootloader.
The solution is always the same - to backup the entire tablet and recreate the /data filesystem (either by having the bootloader do it via a fastboot command or using "mke2fs" with a custom recovery).
While it is technically possible for a device to come from the factory this way, I highly doubt that is what occurred. And no, this isn't some kind of voodoo magic - if you can build a 29 GB filesystem on your device, that's only because there is a 32 GB flash chip in there.
In any event, if you look in the kernel log (search for messages with "mmc" in them) shortly after the tablet has booted, youll see the kernel identify the chip and it's capacity. That's a whole lot easier than speculatively unloading and reloading many GB of files.

Vepaot said:
Screen shot?
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM 4.3.
Click to expand...
Click to collapse
I'll hope that I will get screenshots available during this evening, because tablet is not with me for the moment.
bftb0 said:
Do a search. This isn't a new phenomenon; it only happens to rooters. Somehow, an undersized ext4 filesystem gets created in the userdata partition (which is substantially larger).
The exact origin of the problem is not clear, but is probably a bug in the bootloader.
The solution is always the same - to backup the entire tablet and recreate the /data filesystem (either by having the bootloader do it via a fastboot command or using "mke2fs" with a custom recovery).
While it is technically possible for a device to come from the factory this way, I highly doubt that is what occurred. And no, this isn't some kind of voodoo magic - if you can build a 29 GB filesystem on your device, that's only because there is a 32 GB flash chip in there.
In any event, if you look in the kernel log (search for messages with "mmc" in them) shortly after the tablet has booted, youll see the kernel identify the chip and it's capacity. That's a whole lot easier than speculatively unloading and reloading many GB of files.
Click to expand...
Click to collapse
I'll try this voodoo method with friend's nexus 7 which is 8gb version and post results. It is really very strange that I manage to do this. I know that somebody much smarter then me will already came up with this findings, but I live in a hope :laugh: I hope that I accidentally somehow unlocked disc space. I already got theory that all nexus 7 (wifi) devices are the same in hardware and that they are only with software locked to 8, 16 or 32gb :laugh:

[Q] Secure Erase?

I have a question. Let's say we don't want somebody to ever recover our stuff like user data and pictures on internal memory after we sell them a phone. What's the most secure and thorough way to destroy all data on the S4, making it impossible to recover, short of destroying the phone? As far as my experience..I am rooted, Ive used odin a bit, and Ive flashed several ROMs in the past. Help would be greatly appreciated!

Throw it in a fire.
Sent from my SPH-L720 using Tapatalk

Short of Daniel's suggestion, which is the best by the way to be absolutely sure of it; format your internal and externalSD cards (can be done inside of Android). Then use PC Odin to flash a stock ROM - all depending on what version your one now. Probably best to go with MK2 since you're selling it.

leaderbuilder said:
Short of Daniel's suggestion, which is the best by the way to be absolutely sure of it; format your internal and externalSD cards (can be done inside of Android). Then use PC Odin to flash a stock ROM - all depending on what version your one now. Probably best to go with MK2 since you're selling it.
Click to expand...
Click to collapse
Thanks!

Flashed a T-mobile rom

So using safe strap, I successfully flashed http://forum.xda-developers.com/showthread.php?t=2468083 From the T-mobile thread. The Phone fired up, the only thing I havent gotten to work yet is WIFI.
Now Kies is recognizing the phone as a T-mobile phone.
Does that mean i can use Kies to flash the T-mobile Bootloader on it, and make it a T-mobile phone with unlocked bootloader ?
Or will this result in a complete Hard brick ?

jmichaels1982 said:
So using safe strap, I successfully flashed http://forum.xda-developers.com/showthread.php?t=2468083 From the T-mobile thread. The Phone fired up, the only thing I havent gotten to work yet is WIFI.
Now Kies is recognizing the phone as a T-mobile phone.
Does that mean i can use Kies to flash the T-mobile Bootloader on it, and make it a T-mobile phone with unlocked bootloader ?
Or will this result in a complete Hard brick ?
Click to expand...
Click to collapse
Kies talks to the O/S (at first, at least), not the bootloader - so that is why it thinks the phone is a T-Mobile version. It probably does not even check the bootloader version.
Note that the way Safestrap works, flashing of a kernel appears to work, but only because Safestrap has replaced the /dev/block/mmc* filesystem entry that normally points to the (flash memory) boot partition with a symbolic link to the null device (/dev/null); so /system (the "ROM") gets flashed, but the the flashing of the kernel never actually happens - that data is literally thrown away (the Verizon kernel is left untouched). That's the way Safestrap is supposed to behave ... so that ROM devs don't need to prepare a normal ROM and also a "Safestrap Version". The kernels get thrown away when using Safestrap even though the recovery will shown them as having been flashed.
So, what you have now on your phone is T-Mobile /system + VZW kernel (boot). That's probably why WiFi isn't working (for instance if WiFi was implemented as a loadable kernel module in the T-Mobile case ... kernel modules can only rarely be interchanged between different kernels.)
I do not believe it is safe to believe that because Kies sees "T-Mobile" that you have found a gateway for converting a SM-N900V into a SM-N900T.
iirc, the partitioning layout is different between the VZW version and the Tmo version; since even a full Odin flash does not replace all the original partitions (efs and others), I'm pretty skeptical that what you suggest will work the way you want it to. I don't think Kies ever does re-partitioning (not to mention that neither Kies nor Odin can replace information that doesn't exist in the flash imaging files).
What you are suggesting is completely uncharted territory; if you take the plunge I think you should assume that it is at least as likely that you will have a hard brick as any other possible alternative... ... and that a hard-brick outcome is probably the most likely.
If you are feeling bold with your money, take all the usual precautions - in addition to backing up all your files do a
# dd if=/dev/block/mmcblk0 bs=8192 count=256000 of=/sdcard/200mb_mmcblk0_dump.bin
on the off chance that a "SD card unbricking" method would work. (afaik, that method has not been reported to work successfully on a SM-N900V to date).
.

Thank you
bftb0 said:
Kies talks to the O/S (at first, at least), not the bootloader - so that is why it thinks the phone is a T-Mobile version. It probably does not even check the bootloader version.
Note that the way Safestrap works, flashing of a kernel appears to work, but only because Safestrap has replaced the /dev/block/mmc* filesystem entry that normally points to the (flash memory) boot partition with a symbolic link to the null device (/dev/null); so /system (the "ROM") gets flashed, but the the flashing of the kernel never actually happens - that data is literally thrown away (the Verizon kernel is left untouched). That's the way Safestrap is supposed to behave ... so that ROM devs don't need to prepare a normal ROM and also a "Safestrap Version". The kernels get thrown away when using Safestrap even though the recovery will shown them as having been flashed.
So, what you have now on your phone is T-Mobile /system + VZW kernel (boot). That's probably why WiFi isn't working (for instance if WiFi was implemented as a loadable kernel module in the T-Mobile case ... kernel modules can only rarely be interchanged between different kernels.)
I do not believe it is safe to believe that because Kies sees "T-Mobile" that you have found a gateway for converting a SM-N900V into a SM-N900T.
iirc, the partitioning layout is different between the VZW version and the Tmo version; since even a full Odin flash does not replace all the original partitions (efs and others), I'm pretty skeptical that what you suggest will work the way you want it to. I don't think Kies ever does re-partitioning (not to mention that neither Kies nor Odin can replace information that doesn't exist in the flash imaging files).
What you are suggesting is completely uncharted territory; if you take the plunge I think you should assume that it is at least as likely that you will have a hard brick as any other possible alternative... ... and that a hard-brick outcome is probably the most likely.
If you are feeling bold with your money, take all the usual precautions - in addition to backing up all your files do a
# dd if=/dev/block/mmcblk0 bs=8192 count=256000 of=/sdcard/200mb_mmcblk0_dump.bin
on the off chance that a "SD card unbricking" method would work. (afaik, that method has not been reported to work successfully on a SM-N900V to date).
.
Click to expand...
Click to collapse
Thank you for your very thorough & patient explanation. I used to have a DEV ED. phone, and used Kies on it, that resulted in flashing retail edition bootloader on mine & locked the phone up. It no longer says Developer mode on the phone.
I finally got through to Samsung, and for now they have agreed to re-flash it with Developer Edition bootloader after a lot of talk.
But as it stands I have no warranty on the phone, so I cant attempt it.
The idea came to me when I used Kies and it converted my Dev Edition to Retain edition.
I did know that safe strap will not flash the kernel, but I also do know that T-mobile kernels are compatible with Verizons. So I was looking for T-mobile rom that has no Aroma in it, because I am thinking about joining t-mobile.
With a locked bootloader, i figured as long as the rom does not have Aroma in it, every thing should work and boot up, and i was right, except for the wifi thing.
Didnt know all the technical details though, so thank you for shedding light. I did lose my efs partition many times when my phone was DEV ED, but lucky I used TWRP to back up my efs, so I restored it, and it fired right up. It saved me from many bootloops, but your point did remind me, that odin does not restore efs, I think.
Not sure how kies is any different than odin.
Thanks again !
EDIT: NVM about wifi not working, I flashed http://forum.xda-developers.com/showthread.php?t=2588075 and now everything works, just waiting on my SIM to see if wifi calling and T-mobile data will work.

@jmichaels1982
Hey I mis-spoke ... sort of ... about the partitioning difference between the T-mobile (SM-N900T) and the VZW variant (SM-N900V). I wasn't absolutely sure, and saw a thread where someone said "I thought they were the same", so I did a little checking around.
I went over into the T-Mobile forum and found a thread where someone was providing a big "SD card unbrick image" for that phone (SM-N900T). The front end of that thing contains the partition table for the SM-N900T, so I compared it to the partition table in my (VZW SM-N900V) phone (using "gdisk" on linux - it will report the partition table from the primary GPT even though the secondary GPT is missing. You only need about 33 512-byte blocks from the beginning of the device /dev/block/mmcblk0 to get this info.)
Turns out that all the low level stuff - partitions 1 through 22 - have the exact partitioning on the Tmobile phone as on the VZW phone. (But that is no guarantee of identical contents of course). But the last three partitions are different, starting with the /system partition. The /system partition is a different size (even though it starts at the same LBA/sector offset), and the /cache and /data partitions are not only different sizes but start at different LBA block offsets, as well.
Code:
$ diff vzwpart.txt tmopart.txt | more
1c1
< Disk vzw-GPT.img: 8192 sectors, 4.0 MiB
---
> Disk Tmo-GPT.img: 8192 sectors, 4.0 MiB
[color=green]Number Start (sector) End (sector) Size Code Name[/color]
32,34c32,34
< 23 376832 5931007 2.6 GiB 8300 system
< 24 5931008 8028159 1024.0 MiB 8300 cache
< 25 8028160 61071326 25.3 GiB 8300 userdata
---
> 23 376832 5414911 2.4 GiB 8300 system
> 24 5414912 6438911 500.0 MiB 8300 cache
> 25 6438912 61071326 26.1 GiB 8300 userdata
So, this is where it gets a little interesting. The stuff which is sized identically in the device parititioning is all the low-level stuff (apnhlos, modem, sbl1, dbi, ddr, aboot, rpm, tz, pad, param, efs, modemst1, modemst2, boot, recovery, fota, backup, fsg, fsc, ssd, persist, persdata).
If it were possible to do what you suggested - flash the low-level Tmobile bootloader without completely bricking the phone - then the phone would not boot to the OS correctly, but it might be able to take a re-partitioning operation in Odin and actually repartition the device with the T-mobile layout. I don't know if the Kies images are the same as the Odin images - it is possible that Kies never performs PIT re-partitioning.
Still, this is highly highly speculative. And again it is worth nothing that full Odin flashes don't provide data for any of the partitions highlighted in red above. So all sorts of stuff could go wrong.
I think you are to be congratulated if you are able to get Sammy to re-flash your DE phone. That's an achievement given Samsung's DE support policy, which appears to be "none whatsoever". And it is certainly likely to be much safer than what is discussed above.
Just out of curiousity, do you remember what it was that happened to you in the past that bolluxed up your EFS partition?
cheers

That was very interesting. I'm hoping the story will complete.
SM-N900V DE

jmichaels1982 said:
Thank you for your very thorough & patient explanation. I used to have a DEV ED. phone, and used Kies on it, that resulted in flashing retail edition bootloader on mine & locked the phone up. It no longer says Developer mode on the phone.
I finally got through to Samsung, and for now they have agreed to re-flash it with Developer Edition bootloader after a lot of talk.
But as it stands I have no warranty on the phone, so I cant attempt it.
The idea came to me when I used Kies and it converted my Dev Edition to Retain edition.
I did know that safe strap will not flash the kernel, but I also do know that T-mobile kernels are compatible with Verizons. So I was looking for T-mobile rom that has no Aroma in it, because I am thinking about joining t-mobile.
With a locked bootloader, i figured as long as the rom does not have Aroma in it, every thing should work and boot up, and i was right, except for the wifi thing.
Didnt know all the technical details though, so thank you for shedding light. I did lose my efs partition many times when my phone was DEV ED, but lucky I used TWRP to back up my efs, so I restored it, and it fired right up. It saved me from many bootloops, but your point did remind me, that odin does not restore efs, I think.
Not sure how kies is any different than odin.
Thanks again !
EDIT: NVM about wifi not working, I flashed http://forum.xda-developers.com/showthread.php?t=2588075 and now everything works, just waiting on my SIM to see if wifi calling and T-mobile data will work.
Click to expand...
Click to collapse
I am using a Verizon Note 3 (retail version) and I am using it on Tmobile network. I would love to have a working tmobile rom on my note3 (wit hwifi calling).
Any reason why you didn't try 4.4.2 version of tmobile rom? http://forum.xda-developers.com/showthread.php?t=2468083
From tweaked, which zip file did you flash?
One more thing, did you change the updater-script from the Tmobile rom?
If you share you steps (noob version) I will follow them and report back asap.
Thanks

WiFi Keeps Shutting Off

I'm currently running 4.4.2 and biggins ROM. been running flawlessly since I put it on it when it came out. Now, for about the last month or 2 my WiFi Keeps Shutting off on its own, forgets WiFi passwords, won't connect hardly when it does come in. It's also been randomly rebooting on its own, sometimes 3 or 4 times in a row. Anyone have any suggestions on how to fix it. I've had the phone since the note 3 came out.
Sent from my SM-N900V using Tapatalk

Frankly that sounds more like hardware troubles than software.
(Q) Are you overclocking or undervolting? Using kernel tuning apps? If so, temporarily stop doing that to see if the problem goes away, and if not then there's two approaches for resolving this:
(A) Throw the phone away and get a new one.
(B) Wipe and and install a conservative ROM e.g. Jasmine, retaining the stock kernel. If the same problems continue, then you have verified it is a hardware problem; see (A)

bftb0 said:
Frankly that sounds more like hardware troubles than software.
(Q) Are you overclocking or undervolting? Using kernel tuning apps? If so, temporarily stop doing that to see if the problem goes away, and if not then there's two approaches for resolving this:
(A) Throw the phone away and get a new one.
(B) Wipe and and install a conservative ROM e.g. Jasmine, retaining the stock kernel. If the same problems continue, then you have verified it is a hardware problem; see (A)
Click to expand...
Click to collapse
I'm not overclocked or anything. It's been on Biggins ROM since he came out with it last year. And I haven't done anything since. It's got me baffled as to why it just randomly started doing it.
Sent from my SM-N900V using Tapatalk

donelam304 said:
I'm not overclocked or anything. It's been on Biggins ROM since he came out with it last year. And I haven't done anything since. It's got me baffled as to why it just randomly started doing it.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Actually I guess I wasn't familiar with the Biggins ROM but then I remembered that you said "last year", so (just now I figured that) you were either on a DevEd phone, or it was a "stock kernel" ROM.
So I looked at the Biggins thread. I guess it is actually just a very heavily themed stock-kernel ROM, and you are using Safestrap? And don't have an unlocked bootloader? And don't have a "real" version of TWRP in the recovery partition?
If that's what you did, then you don't have a trivial way of stock reversion short of going back to Odin and starting over with rooting.
Unless you were diligent and backed up the stock slot with Safestrap-twrp right after you flashed Biggins.. Or even better, you also did the same thing right after you installed Safestrap, even before you installed Biggens[/b] Then you could try and dirty-flash the Biggens backup and see if that changes anything. And if that didn't work, restore the original (Safestrapped, pre-Biggens) ROM along with a factory reset and see if that does anything.
But that would only rectify problems that were due to flash memory bit-rot problems (progressive wear & eMMC flash memory pages slowly going bad). And even if that were the case, it's a sign of more of it yet to come.
If you didn't make those backups, then I suppose you have a trip to Odin and re-rooting, re-installation of Biggins - on a phone that might have failing hardware. Either that or you could take the plunge and unlock your bootloader. Then you would have more options.
Are you on NC4?
Hardware does go bad. It happens at a low probability, so usually it doesn't affect most people before the time they would retire their hardware. Although I have to say - based on my experience with other devices - use of MLC flash memory probably does imply a pretty short product lifetime. (It's sort of ridiculous, buying a device that costs $700 and expecting it to be dead in 3 years. OTOH, in those three years most VZW subscribers have spent another $2500+ on service fees for their first line, so it's not the longest pole in the tent.)

bftb0 said:
Actually I guess I wasn't familiar with the Biggins ROM but then I remembered that you said "last year", so (just now I figured that) you were either on a DevEd phone, or it was a "stock kernel" ROM.
So I looked at the Biggins thread. I guess it is actually just a very heavily themed stock-kernel ROM, and you are using Safestrap? And don't have an unlocked bootloader? And don't have a "real" version of TWRP in the recovery partition?
If that's what you did, then you don't have a trivial way of stock reversion short of going back to Odin and starting over with rooting.
Unless you were diligent and backed up the stock slot with Safestrap-twrp right after you flashed Biggins.. Or even better, you also did the same thing right after you installed Safestrap, even before you installed Biggens[/b] Then you could try and dirty-flash the Biggens backup and see if that changes anything. And if that didn't work, restore the original (Safestrapped, pre-Biggens) ROM along with a factory reset and see if that does anything.
But that would only rectify problems that were due to flash memory bit-rot problems (progressive wear & eMMC flash memory pages slowly going bad). And even if that were the case, it's a sign of more of it yet to come.
If you didn't make those backups, then I suppose you have a trip to Odin and re-rooting, re-installation of Biggins - on a phone that might have failing hardware. Either that or you could take the plunge and unlock your bootloader. Then you would have more options.
Are you on NC4?
Hardware does go bad. It happens at a low probability, so usually it doesn't affect most people before the time they would retire their hardware. Although I have to say - based on my experience with other devices - use of MLC flash memory probably does imply a pretty short product lifetime. (It's sort of ridiculous, buying a device that costs $700 and expecting it to be dead in 3 years. OTOH, in those three years most VZW subscribers have spent another $2500+ on service fees for their first line, so it's not the longest pole in the tent.)
Click to expand...
Click to collapse
Here is my current build. I am on NC4.
Sent from my SM-N900V using Tapatalk

Well,
What do you plan on doing? It's not like there's a toggle button in Settings labeled "Act strange and reboot randomly mode" that we can just go in and turn off.
Do you have any Safestrap backups?
How about the NC4 factory Odin firmware file, do you have that? A copy of Odin somewhere & a PC it will run on?
That's how these things go - you need to create a fault hypothesis, and then try something that will hopefully do something to remedy that type of fault... which might or might not work.
The "bit rot" hypothesis assumes that flashing the same software you already have on the phone will correct eMMC memory pages that have gone bad, both by refreshing the data and also through page replacements by the Flash memory controller doing wear leveling. But that's only one hypothesis out of many that are possible. There's no guarantees that this will fix the problems you are having if the origin of the problem has nothing to do with this mechanism.
If it were me I'd probably make TiBu backups of my most frequently used apps, back up the internal SDcard, and start from scratch by Odin flashing NC4 stock*. Its more effort, but pretty much everything gets re-written that way, and if you continue to have issues then you know it is time to move on to a new phone, rather than continuing to diddle with it.
good luck
* I believe that the TowelRoot app works on NC4, does it not?

Yes, towelroot is what I use to root it. I have a backup, but I'm not sure what it is. The Daye on it is 1970. Lol.
Sent from my SM-N900V using Tapatalk

donelam304 said:
Yes, towelroot is what I use to root it. I have a backup, but I'm not sure what it is. The Daye on it is 1970. Lol.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
If you do a "tar tvf filename" on those .win00x files the dates of the files listed will give you a better idea. (I suppose that some widows archive programs also understand .tar file formats, but I can't give you a reccomendation)
Also I sort of recall that the Safestrap version of (twrp) recovery adds the name of the slot from which the backup was made.
You actually have lots of choices. You could unlock the bootloader, install a custom recovery, and try a different ROM. Or when faced with Odin flashing, bite the bullet and upgrade to OF1. (As near as I can tell, using towelroot on NC4 is far less of a hassle then that Yemen tool appears to be with OB6/OF1 ... that sort of argues for flashing NC4 instead of more recent firmware.)
Well anyway. If it's failing hardware none of this will make a whit of difference and your phone will still lockup/reboot/drop WiFi.
good luck

reflashed to stock, sd size changed and no access to /data

hey guys
Been messing around with tablet to find best setup then to find netflix wont work. I have reflashed back to stock rom from lineage os. but now my sd card size is showing 16gb under storage space but if I look at it elsewhere its like 6gb, when it should be 64gb, I read this is to do with userdata but I cant find any userdata files to flash.
other issue is attempting to factory reset using twrp getting alot of /data/.... (permission Denied)
how can I solve these issues? and the streaming apps (netflix and disneyplus)
thanks guys

Your data partition is encrypted. I had the same issue and found this thread:
https://forum.xda-developers.com/doogee-mix/how-to/fixed-how-to-remove-data-encryption-twrp-t3757595
Seems to have worked, TWRP sees the full storage amount, but still trying to get Lineage loaded...

Elysian893 said:
Seems to have worked, TWRP sees the full storage amount, but still trying to get Lineage loaded...
Click to expand...
Click to collapse
Having had this same issue recently TWRP will be your saving grace but before you go through the process in the link you should at least look at (while in TWRP) the WIPE section. Go through each of the listed options individually and hit the "repair or change File system option." What happened with mine is that the act of flashing stock changed The /DATA partition from EXT4 to NTFS and I Needed to change it back.
Regarding the Stock image you flashed double check to make sure its the one intended for your particular device storage size. Apparently there are different variants of the same stock ROM but with different PIT files (the file that sets your device partition.
One last piece of advise that may seem like a captain obvious is thing but I admittedly overlooked is when you flash your stock ROM, make sure to include not just the AP file, but also BL and CSC as well whwhenever you flash

Seems to have worked, TWRP sees the full storage amount, but still trying to get Lineage loaded...
[/QUOTE]
I tried flashing Lineage and Havoc and was never able to get either working for this device which I'm sure is likely user error but I gave up either way lol

Mekzul said:
I tried flashing Lineage and Havoc and was never able to get either working for this device which I'm sure is likely user error but I gave up either way lol
Click to expand...
Click to collapse
I actually got Lineage working fine on it. Once I got the data partition figured out I believe it was smooth sailing, though it was a while ago now.

Elysian893 said:
I actually got Lineage working fine on it. Once I got the data partition figured out I believe it was smooth sailing, though it was a while ago now.
Click to expand...
Click to collapse
Hey so I was able to get it up and running eventually as well but in the end wound up just running stock rom on this device as I was getting these weird "screen shatter" type glitches on bootup and so it wasnt really worth the hassle lol. Does rooting really even provide that much of a benefit for this device?

Mekzul said:
Hey so I was able to get it up and running eventually as well but in the end wound up just running stock rom on this device as I was getting these weird "screen shatter" type glitches on bootup and so it wasnt really worth the hassle lol. Does rooting really even provide that much of a benefit for this device?
Click to expand...
Click to collapse
Why in the world would you go back to stock just because of these "screen glitches" when booting up? They are gone after Boot and don't cause any issues .... Also this might be caused by you being on an old (or newer but it's rather unlikely as I fixed this "issue" for newer ones) firmware (bootloader matters)
Stock is laggy and bloated while lineage is not.
Edit: Btw, which model and firmware are you on?
If it's P615 with BTK2 firmware I might need to update dtbo sources again and this "issue" will be gone