Related
Hi,
My mom has an Asus TF300T running JB 4.2.1. She tried to root and flash OmniROM by herself and borked it somehow. Unfortunately, she didn't do any backup...
She entered the fastboot screen and there she selected wipe. Then she flashed openrecovery-twrp-2.6.3.0-tf300tg-JB.blob using fastboot.
Now I am trying to help her rescue it.
It's operational, the OS loads up fine and she can use it, install apps etc.
I can get to the fastboot screen and from there to the TWRP no problem, but TWRP can't mount anything besides system.
No dalvik partition, no data partition, not even the SD or external SD.
Naturally, I can't flash another rom...
Tried executing "fix permissions" from the TWRP menu, it didn't help.
Downloaded the latest official Asus blob file TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip and flashed it using fastboot, hoping it will restore the missing partitions but it didn't make any difference.
Also tried CWM - same issue.
Any ideas?
Thanks,
Sefi
chompy18 said:
Hi,
My mom has an Asus TF300T running JB 4.2.1. She tried to root and flash OmniROM by herself and borked it somehow. Unfortunately, she didn't do any backup...
She entered the fastboot screen and there she selected wipe. Then she flashed openrecovery-twrp-2.6.3.0-tf300tg-JB.blob using fastboot.
Now I am trying to help her rescue it.
It's operational, the OS loads up fine and she can use it, install apps etc.
I can get to the fastboot screen and from there to the TWRP no problem, but TWRP can't mount anything besides system.
No dalvik partition, no data partition, not even the SD or external SD.
Naturally, I can't flash another rom...
Tried executing "fix permissions" from the TWRP menu, it didn't help.
Downloaded the latest official Asus blob file TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip and flashed it using fastboot, hoping it will restore the missing partitions but it didn't make any difference.
Also tried CWM - same issue.
Any ideas?
Thanks,
Sefi
Click to expand...
Click to collapse
That sounds pretty bad. The factory blob flashed successfully? If it did, did it just bootloop and then you tried another custom recovery? I'm thinking if the factory blob flashed successfully and it didn't work, your only hope beyond sending it in to them would be to use NVflash. However, pretty sure you had to set up NVflash before anything else or an older update for it to work, can't remember off the top of my head. Props to your mom trying to install Omni though. Hope this doesn't deter her from trying on something else. These tablets are a little different than most devices and I had to read a lot to make sure I had everything lined up properly when I've worked on them for customers.
es0tericcha0s said:
That sounds pretty bad. The factory blob flashed successfully? If it did, did it just bootloop and then you tried another custom recovery? I'm thinking if the factory blob flashed successfully and it didn't work, your only hope beyond sending it in to them would be to use NVflash. However, pretty sure you had to set up NVflash before anything else or an older update for it to work, can't remember off the top of my head. Props to your mom trying to install Omni though. Hope this doesn't deter her from trying on something else. These tablets are a little different than most devices and I had to read a lot to make sure I had everything lined up properly when I've worked on them for customers.
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
Yeah the factory blob flashed fine. I can use the device (the OS loads up), I can get into fastboot and from there to TWRP.
There is no backup, and from what I'v read about NVflash, you need to set it up before anything else...
I was hoping the factory blob would recover the partitions...
Is there a way to repartition it?
Maybe using fastboot erase for the data partition?
I guess maybe I am not sure of the exact nature of the issue. If /data was not mounted, you would not be able to install apps. Does it show the proper info in Settings / Storage? Have never seen a device that had the data partition unmount and still be able to use normally while booted.
This is just stock LineageOS for the vs985 with no modifications (except baked in root in one edition) built daily from their source code. It's not terribly useful to anyone but people who want to be on the bleeding edge of development for whatever reason (like me), but I figured I'd share. I'll be doing these daily builds for the foreseeable future as long as I own the device or don't change OSes personally.
To install, do one of the following:
If you want to start fresh (or are coming from a non-Lineage based rom):
1.) In TWRP, wipe system, cache, dalvik, and data. Install the standard build (or the standard build with root). Do not install a migration build. Now Install open-gapps if desired. Reboot.
If you want to keep your data (and are coming from a Lineage based rom, official most likely)
1.) In TWRP, wipe system, cache, and dalvik. Install the migration build first, and then an open gapps build if desired. Reboot (it may take a bit). Once you are at your homescreen, reboot back to TWRP, and AGAIN wipe system, cache, and dalvik. Now flash a NORMAL build (with or without root) of your choosing. Again, flash open-gapps. Reboot. All done.
To upgrade, you simply wipe system/cache/dalvik and flash a non-migration build and appropriate gapps.
A warning about migration builds
Migration builds only need to be used once, but they appear to be a one way street. Once you are on my build, you can't "migration-build" your way back to official builds (or at least, I was not able to). You will need to data wipe to go back there. So, caveat emptor. Be sure this is what you want.
Find my dailies (along with build dates) here:
https://www.androidfilehost.com/?w=files&flid=164143
Open-gapps can be downloaded here: http://opengapps.org/
LineageOS Source can be found from the LineageOS github. It was compiled unmodified from this repo:
https://github.com/lineageos
Please, although these are stock code based, they are UNOFFICIAL BUILDS. Please do not bother the LineageOS project for support of these unless you can confirm the issue in an official build.
Thanks for looking! I'll most likely have a new build up tomorrow.
EDIT: Please make sure you are on the 35B bootstack prior to install:
Just flash this via TWRP if you are not sure: https://www.androidfilehost.com/?fid=24052804347843993
Has anyone installed this yet and can confirm compatibility?
I use them daily so they are compatible (if you can trust my word that is).
That said, they are not exactly bug free, but no LineageOS build bleeding edge ever can be.
The build server was thrashing it's disk space for a few days due to a build script failing to clean up after itself... this means a few days of builds were missed. This has been fixed, and we should have daily builds again.
Not sure if anyone uses this, but hey, just an update.
Hands down best ROM I've used on the G3. Everything works, very little FC if ever and I've even gotten Dolby Atmos to work with it. Never going back to anything else.
Glad to hear it. My build server had issues again yesterday, but it appears to be related to a bad stick of ram. I hope to have daily builds moving again tonight.
I wiped system, cache, dalvik and data, on my rooted, VS985 with TWRP 3.0.2-0.and got an "error 7: error installing zip file" when I tried to install the lineage-14.1-20170402-UNOFFICIAL_WROOT-vs985.zip. "Checking for baseband 35B. Error: It appears you are running an unsupported baseband. assert failed: g3.verify_baseband(35B:2.0.1C1.13.4-00005) =="1""
Android Version; 5.0.1
Baseband; VS985-MPSS.DI.2.0.1.c1.13.00073-M8974AAAANPZM-1
Kernel; 3.4.0-perf-g2d182d3
Build number; LRX21Y
Software Version; VS98524B
Any hints would help. I would really like to see this work on my phone.
dweezle said:
I wiped system, cache, dalvik and data, on my rooted, VS985 with TWRP 3.0.2-0.and got an "error 7: error installing zip file" when I tried to install the lineage-14.1-20170402-UNOFFICIAL_WROOT-vs985.zip. "Checking for baseband 35B. Error: It appears you are running an unsupported baseband. assert failed: g3.verify_baseband(35B:2.0.1C1.13.4-00005) =="1""
Android Version; 5.0.1
Baseband; VS985-MPSS.DI.2.0.1.c1.13.00073-M8974AAAANPZM-1
Kernel; 3.4.0-perf-g2d182d3
Build number; LRX21Y
Software Version; VS98524B
Any hints would help. I would really like to see this work on my phone.
Click to expand...
Click to collapse
You'll need to flash the bump-friendly 35B bootstack first. You can get it here:
https://www.androidfilehost.com/?fid=24052804347843993
Forgot to mention that, will edit it in.
R-T-B said:
You'll need to flash the bump-friendly 35B bootstack first. You can get it here:
https://www.androidfilehost.com/?fid=24052804347843993
Forgot to mention that, will edit it in.
Click to expand...
Click to collapse
Do you know if the "updater-script" fix would also work in this case?
If I do choose to flash the 35B bootstack, will I be able to get back to the backup of my current configuration simply by restoring it in TWRP or would I need to flash back the existing 24B then restore?
Lastly, how is your build different from the official LineageOS version for the VS985?
Thanks for your work with this. I think my VS985 still has lots of life in it, your ROM should give it even more.
Question please.
What's different about this "unofficial" stock Lineage from the "official" Lineage that is avail for VS985?
Why would one want this one vs that one?
It is just built more frequently from source to get more daily changes. Otherwise it is identical. It's mainly for those who like to track bleeding edge changes.
dweezle said:
Do you know if the "updater-script" fix would also work in this case?
If I do choose to flash the 35B bootstack, will I be able to get back to the backup of my current configuration simply by restoring it in TWRP or would I need to flash back the existing 24B then restore?
Lastly, how is your build different from the official LineageOS version for the VS985?
Thanks for your work with this. I think my VS985 still has lots of life in it, your ROM should give it even more.
Click to expand...
Click to collapse
A twrp restore should work regardless of the bootstack flash.
I just Flashed lineage-14.1-20170623-nightly-vs985-signed and open_gapps-arm-7.1-mini-20170707 it all went ok but it don't find my SIM card on boot, so how am I gonna get my sim card active. plz otherewise I would have to withdraw my choice of this Namely Custom ROM.
Please helpp!! I was using Lineage OS on my LG G3 VS985 it doesn't come with prebuilt root so I was rooting through SuperSU. I reboot my phone into twrp recovery and installed SuperSU.zip and then reboot my phone but now it is showing Secure Boot Error, boot certification failed. Please tell me how to fix this issue
and how is the camera quality of this rom as compared to stock and other aosp/cm based rom?
I flash the 35B bootstack before all and my phone goes wrong.. It is on power off, there's just 2 flicking red and blue led. When I go to the recovery mode, I can choose any proposition, my phone come back to this condition.. Can someone help me please ?^^ I was on Fulmics Rom
This rom hasn't been updated in some time as I no longer have the phone, so I am unsure how to help.
I finally managed to find a working fix for this issue after having found this post. The origin of the problem is TWRP:
gordonthegopher said:
Formatting /data in TWRP uses up all the blocks, but encryption from Lineage needs 16kb of free space at the end of the partition to store the headers.
Click to expand...
Click to collapse
Fix
You have at least two solutions to fix this issue:
Resize your /data partition to free up the needed space. Here and here are guides how to do it. I haven't give it a try, so I can't confirm it's working, but several other guys reported this fix working.
If you're not comfortable to resize your partition, you can use an old version of TWRP. Beginning with version 3.2.0.0 TWRP seems to use up all blocks for /data. So you need a version prior to this one. I've used TWRP 3.1.0.0, but 3.1.1.0 should also work. Step by step:
Download and flash TWRP 3.1.0.0.
Boot into recovery and do a factory reset: Main menu -> Wipe -> Format Data (confirm with "yes"). I also wiped Cache and System (Main menu -> Wipe -> Advanced Wipe).
If you're going to flash a Nougat based ROM you can stop reading and start flashing and encrypting
If you're going to flash an Oreo based ROM you now need to update your TWRP version as anything prior to 3.2.0.0 doesn't support flashing Android 8.1. The official TWPR version sucks because you won't be able to decrypt your phone when booting in recovery. I've used the TWRP provided in this post.
Install your preferred ROM and encrypt it.
I haven't tested it, but dirty flashing a ROM (without a factory reset) might also work. But this usually leads to some random ****ups.
Also the TWRP alternative "Orange Fox" was mentioned as a solution in this thread. I actually can't remember if I've used Orange Fox to factory reset my phone or if I've flashed it only after having performed a factory reset using TWRP. For me Orange Fox didn't work (= encryption didn't work). But you might give it a try...
Original post
Hi guys,
I'm kind of stuck right now because I cannot encrypt my phone anymore and I don't know why. I got my phone last year and installed LOS 14.1 right away. For security reasons I also encrypted it - without any issues whatsoever. When LOS 15.1 came out, I upgraded my phone, with encryption still working. A couple of days back for some reason I decided to do a factory reset. Obviously, the device wasn't encrypted anymore after the reset. I then installed the new nightly of LOS (20180807) and tried to encrypt my phone once again. When I select "Encrypt phone", I need to enter my PIN, the phone restarts and reboots without encryption being started.
What I've done so far:
I've flashed two different TWRP versions: 3.2.3.0 and a customized one (https://forum.xda-developers.com/re...other-development/rom-lineageos-15-0-t3690465).
I've clean installed different LOS versions (unofficial LOS 14.1 and LOS 15.1 starting from the 20180710 release)
I've clean installed Omnirom (current release and a release from 20180107).
I've even flashed MIUI 9 and reinstalled LOS thereafter because some guy in the above mentioned LOS thread wrote, that this did the trick for him.
I've disabled WI-FI and mobile data before trying to encrypt my phone, because I found a blog article stating that this might help.
Nothing helped. The phone just reboots and stays unencrypted.
Do you guys have any additional hints or ideas how I can manage to encrypt my phone once again? Could another TWRP version do the trick? Is TWRP even involved in any kind when it comes to encryption of the OS? Do you think another ROM could be helpful?
Click to expand...
Click to collapse
Try orangewolf recovery ....
Sent from my Redmi Note 4 using Tapatalk
I'm also having trouble with this. Many days ago, someone told they had successfully encrypted their phone. I tried to replicate what he did, got miui.eu and flashed LOS afterwards.
After tons of restarting, reflashing, all kind of stuff, the encryption still doesn't work. Pfff.
shakil002 said:
Try orangewolf recovery ....
Click to expand...
Click to collapse
Thanks for the advice. But I'm afraid it didn't help
CanBostanci said:
I'm also having trouble with this. Many days ago, someone told they had successfully encrypted their phone. I tried to replicate what he did, got miui.eu and flashed LOS afterwards.
After tons of restarting, reflashing, all kind of stuff, the encryption still doesn't work. Pfff.
Click to expand...
Click to collapse
That's the most ****ed up part. For some people it does work, for some not.
There surely must be some ridiculous small detail we're not getting. Like disabling WI-FI while Bluetooth is enabled.
Things I've also tried:
installed a new kernel: ElectraBlue (https://forum.xda-developers.com/re...rnel-electrablue-kernel-redmi-note-4-t3655651)
flashed an old LOS 14.1 with kernel 3.18.31 which I found here
used different screen lock types (PIN, password, pattern, swipe)
charged my battery up to 100%
reformatted my data partition with f2f
Of course, my device is still unencrypted...
Has anyone any idea why encryption might fail? I mean, it did work in the past with LOS 14.1. So why does it even fail with an old release of LOS 14.1? I don't do knowingly anything different to all the times I've successfully encrypted my phone in the past.
Does the factory reset still leave some files untouched?
parkbank said:
Things I've also tried:
installed a new kernel: ElectraBlue (https://forum.xda-developers.com/re...rnel-electrablue-kernel-redmi-note-4-t3655651)
flashed an old LOS 14.1 with kernel 3.18.31 which I found here
used different screen lock types (PIN, password, pattern, swipe)
charged my battery up to 100%
reformatted my data partition with f2f
Of course, my device is still unencrypted...
Has anyone any idea why encryption might fail? I mean, it did work in the past with LOS 14.1. So why does it even fail with an old release of LOS 14.1? I don't do knowingly anything different to all the times I've successfully encrypted my phone in the past.
Does the factory reset still leave some files untouched?
Click to expand...
Click to collapse
Mmm, maybe it's about the firmware? I was almost going to try lineageos 14.1...
CanBostanci said:
Mmm, maybe it's about the firmware? I was almost going to try lineageos 14.1...
Click to expand...
Click to collapse
Huh... I didn't even think about the firmware. That would explain why the one user who flashed MIUI before installing LOS could actually encrypt his phone. I'll definitely give it a try.
parkbank said:
Huh... I didn't even think about the firmware. That would explain why the one user who flashed MIUI before installing LOS could actually encrypt his phone. I'll definitely give it a try.
Click to expand...
Click to collapse
I'm looking forward to hear the results. I'm about to become insane because of this encryption issue.
I've flashed both the dev and stable firmware found in this thread. No success
By flashing I mean factory reset, flashing the firmware and then installing LOS. I noticed, that flashing a new firmware while a ROM is still installed leads to some random ****ups.
After a couple of days of flashing, factory resetting, re-flashing, reading and a lot of cursing I finally found a working solution. I've added the fix to my initial post. Hopefully this helps
I was looking for solutions for quite a while and nothing else worked but did this and my device is encrypted again.
Thank you!
parkbank said:
I finally managed to find a working fix for this issue after having found this post. The origin of the problem is TWRP:
Fix
You have at least two solutions to fix this issue:
Resize your /data partition to free up the needed space. Here and here are guides how to do it. I haven't give it a try, so I can't confirm it's working, but several other guys reported this fix working.
If you're not comfortable to resize your partition, you can use an old version of TWRP. Beginning with version 3.2.0.0 TWRP seems to use up all blocks for /data. So you need a version prior to this one. I've used TWRP 3.1.0.0, but 3.1.1.0 should also work. Step by step:
Download and flash TWRP 3.1.0.0.
Boot into recovery and do a factory reset: Main menu -> Wipe -> Format Data (confirm with "yes"). I also wiped Cache and System (Main menu -> Wipe -> Advanced Wipe).
If you're going to flash a Nougat based ROM you can stop reading and start flashing and encrypting
If you're going to flash an Oreo based ROM you now need to update your TWRP version as anything prior to 3.2.0.0 doesn't support flashing Android 8.1. The official TWPR version sucks because you won't be able to decrypt your phone when booting in recovery. I've used the TWRP provided in this post.
Install your preferred ROM and encrypt it.
I haven't tested it, but dirty flashing a ROM (without a factory reset) might also work. But this usually leads to some random ****ups.
Also the TWRP alternative "Orange Fox" was mentioned as a solution in this thread. I actually can't remember if I've used Orange Fox to factory reset my phone or if I've flashed it only after having performed a factory reset using TWRP. For me Orange Fox didn't work (= encryption didn't work). But you might give it a try...
Original post
Click to expand...
Click to collapse
You have save my day "my MIDO" hehehehe
After the 1st PIE Rom the encryption was broken.
Your Step by Step save this and now Syberia 9 was able to encrypt with success :good:
Thank you one more time for sharing.
Thx!
---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------
Orangefox worked
is there any plan to fix twrp itself?? thx
Thank you. It worked for me to get Havoc OS 9.0 with hardware encryption on my Redmi Note 3 SE.
I bypassed unlocking the bootloader by doing this. Then I installed TWRP 3.1.0.0 from the recovery, did the reset and everything as instructed here, updated it to 3.3.1.0, rebooted, then flashed the Pie ROM and latest gapps without any further wiping.
I use the first link, I've modified the partition size -> did the trick wihtout formating nor loosing datas
Great, thank-You.
Hi, I want to ask, what is this encryption features you been using? can u tell me?
Today i wanted to upgrade from Nitrogen OS android 9 to PixelExperience android 10 and it didn't work at all...
At first i wiped:
Dalivik / ART Cache
cache
system
Data
And now I just don't know what to do, because after flashing PixelExperience, I got the message: "No OS installed! Are you sure you wish to reboot?".
After that I flashed disable force encryption and rebooted anyway just to see the fastboot screen.
Then i wiped everything again and tried flashing my old ROM without any success (error 7) after that message,
I wiped everything once more and flashed vendor-firmware (it was an old version the name of the file is: "fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIX")
and it still didn't work...
Now I searched online for any solutions and just downloaded a new firmware (filename: beryllium-9.4.1-9.0-vendor-firmware.zip) flashed it,
and after trying to install any of the above mentioned ROM's i got the same results.
I'm kind of desperate right now and don't know what to do. I though that i could maybe format my phone,
I saved all my important files on my PC so that isn't really a problem.
Please help me! (Please let me know if you need to know more info, I hope I didn't forget anything)
xueru said:
Today i wanted to upgrade from Nitrogen OS android 9 to PixelExperience android 10 and it didn't work at all...
At first i wiped:
Dalivik / ART Cache
cache
system
Data
And now I just don't know what to do, because after flashing PixelExperience, I got the message: "No OS installed! Are you sure you wish to reboot?".
After that I flashed disable force encryption and rebooted anyway just to see the fastboot screen.
Then i wiped everything again and tried flashing my old ROM without any success (error 7) after that message,
I wiped everything once more and flashed vendor-firmware (it was an old version the name of the file is: "fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIX")
and it still didn't work...
Now I searched online for any solutions and just downloaded a new firmware (filename: beryllium-9.4.1-9.0-vendor-firmware.zip) flashed it,
and after trying to install any of the above mentioned ROM's i got the same results.
I'm kind of desperate right now and don't know what to do. I though that i could maybe format my phone,
I saved all my important files on my PC so that isn't really a problem.
Please help me! (Please let me know if you need to know more info, I hope I didn't forget anything)
Click to expand...
Click to collapse
I found a old backup, that i made in twrp and after loading that, i was able to flash stuff again, sorry if i inconvenienced anyone
Same happened with me when i flashed PE 10 from PE 9 PIE..
So i flashed Letest Miui 11 (pie) via fastboot then
Installed PE 10 via twrp..
so this is the fix.
Hi. This is my ROM #4.
It's stable as LOS 14.1.
Tested:
Camera;
USB-OTG;
NFC;
FMRadio;
etc.
Bugs:
- The same as LOS14;
- NFC-HCE(in LOS14.1 that doesn't work either);
- something I haven't found.
How to install:
1) use TWRP 3.5.0.
2) wipe all except internal storage
3) Flash the gapps , magisk.
4) You may also need to reformat sdcard.
5) If gaaps taking too much time for checking for updates, just reboot the tablet.
Change log:
20210316 - initial build.
20210317 - build for karin windy.
Last builds (mirror) are here.
I'm also very grateful to sabar_op for guiding me to build me ROMs in the right way.
If you want to get stock back use Emma than flashtool.
Sources
https://github.com/ResurrectionRemix
https://github.com/LineageOS/android_device_sony_karin_windy
https://github.com/LineageOS/android_device_sony_karin
https://github.com/LineageOS/android_device_sony_kitakami-common
https://github.com/LineageOS/android_kernel_sony_msm8994
The next ROMs I'm gonna build is dotos, viperos and crdroid. If no own wish to test it on karin windy I will build it only for on my own karin.
I got some error when I try use "adb push" to push the ROM file into my SGP712 with TWRP 3.5.
I use TWRP 3.4 instead and installed the ROM successfully.
But after I boot in the system, it will show the error message "Process system isn't responding".
It seems work fine after I reboot.
I usually got device shutdown and reboot issue when I use LineageOS before.
I will test this ROM and see if it would happened.
Thanks for your sharing.
aaa646123 said:
I got some error when I try use "adb push" to push the ROM file into my SGP712 with TWRP 3.5.
I use TWRP 3.4 instead and installed the ROM successfully.
But after I boot in the system, it will show the error message "Process system isn't responding".
It seems work fine after I reboot.
I usually got device shutdown and reboot issue when I use LineageOS before.
I will test this ROM and see if it would happened.
Thanks for your sharing.
Click to expand...
Click to collapse
Have you wiped system dalvik cashe user data? I don't use adb push.
alex009988 said:
Have you wiped system dalvik cashe user data? I don't use adb push.
Click to expand...
Click to collapse
yes, I wiped them before I push the file.
Anyways I tried the ROM but shutdown and reboot issue still exist.
aaa646123 said:
yes, I wiped them before I push the file.
Anyways I tried the ROM but shutdown and reboot issue still exist.
Click to expand...
Click to collapse
And you 100% sure that there are problems with shut down and reboot with my ROM and the lineage 14.1? It doesn't work completely? Can you log issue? I don't have ones with karin.
alex009988 said:
And you 100% sure that there are problems with shut down and reboot with my ROM and the lineage 14.1? It doesn't work completely? Can you log issue? I don't have ones with karin.
Click to expand...
Click to collapse
It shut down and reboot after I used the ROM about 20 minutes.
Just the same as I used LingeageOS18/17.
I send the log to @sabar_op before, but seems not fix issue after.
aaa646123 said:
It shut down and reboot after I used the ROM about 20 minutes.
Just the same as I used LingeageOS18/17.
I send the log to @sabar_op before, but seems not fix issue after.
Click to expand...
Click to collapse
What about los15? My advice to you is to restore the latest stock with Emma(not flashtool) than try again custom ROM. Perhaps you have something broken with mounting partitions. I have another problem with Karin(downloading big game call of duty).
I need someone else to confirm your problem on sgp712.
alex009988 said:
What about los15? My advice to you is to restore the latest stock with Emma(not flashtool) than try again custom ROM. Perhaps you have something broken with mounting partitions. I have another problem with Karin(downloading big game call of duty).
I need someone else to confirm your problem on sgp712.
Click to expand...
Click to collapse
I restore with Emma every time. I don't remember if I tried the los15, is there any special with los15?
aaa646123 said:
I restore with Emma every time. I don't remember if I tried the los15, is there any special with los15?
Click to expand...
Click to collapse
I saw your messages you have that problem since 2018.
Nougat ROMs are the most stable roms for our tablet, based on my experiance with karin at least. I can say that kernelpanics are possible everywhere where root is, both stock and custom. I also faced it on los14 but it happens so rarely, usually when many apps are lunched.
If you have that problem on los14, you'll have it with any my noutgat rom too as I use the same los kernel and edit device and vendor and other stuff if neccessary.
The problem is that I haven't found another sgp712 user who has 20 minute reboot problem on sgp712. I don't know maybe something in the sources are broken for your device or it's hardware problem.
So do you have that problem without gapps installed?
Do you have that problem without root?
Did you try different versions of magisk/supersu?
It's better you to try los15, maybe this one is without the issue for you.
If all above-listed you tried you should take adb log by pc with kernel panic. At least we can identify what cause the problem.