Related
Hello All,
I am able to flash my phone to any other rom so I was looking for some help to get ICM up and running.
If I flash my phone with beta 0.4.3 or 0.4.4 cwm flashable i reboot my phone and it sits in the "unlocked" Motorola Dual Core Technology screen and won't boot. Any ideas or can I get you information off my phone to assist?
Thanks,
Olsookie
olsookie said:
Hello All,
I am able to flash my phone to any other rom so I was looking for some help to get ICM up and running.
If I flash my phone with beta 0.4.3 or 0.4.4 cwm flashable i reboot my phone and it sits in the "unlocked" Motorola Dual Core Technology screen and won't boot. Any ideas or can I get you information off my phone to assist?
Thanks,
Olsookie
Click to expand...
Click to collapse
Make sure to use Joker's Clockworkmod recovery, named cwm-v3, here.
Thanks gollyzila, I am using the Jokersax CWMv3 recovery image at this time. I meant to mention that earlier in my first post.
Thanks,
Olsookie
olsookie said:
Hello All,
I am able to flash my phone to any other rom so I was looking for some help to get ICM up and running.
If I flash my phone with beta 0.4.3 or 0.4.4 cwm flashable i reboot my phone and it sits in the "unlocked" Motorola Dual Core Technology screen and won't boot. Any ideas or can I get you information off my phone to assist?
Thanks,
Olsookie
Click to expand...
Click to collapse
I would recommend flashing 0.4.0 first, then Gapps if you want it, then boot up. Then wipe cache and flash to 0.4.4 and re-flash Gapps. This method has been posted for the previous couple versions to avoid problems and seems to resolve a lot of issues. Might give it a shot and at least see if 0.4.0 will boot. Also check to make sure your download is the correct size and not corrupted.
try pulling the battery and then booting again. if that doesn't work flash 0.4.0 first like ccallahan suggested
CCallahan said:
I would recommend flashing 0.4.0 first, then Gapps if you want it, then boot up. Then wipe cache and flash to 0.4.4 and re-flash Gapps. This method has been posted for the previous couple versions to avoid problems and seems to resolve a lot of issues. Might give it a shot and at least see if 0.4.0 will boot. Also check to make sure your download is the correct size and not corrupted.
Click to expand...
Click to collapse
wala! that worked. thank you very much CCallahan. much appreciated.
i was having the same problem heres what i did i factory reset cleared cache/dalvic installed 3.1 then reboot wipe cache/dalvic then i flashed 4.4 over it
when you first flash any cm9 fresh, not over a backup, you must flash twice. Joker has mentioned this many times that the scripts he has for the install have to run twice in order to fully install.
1. Flash cm9 (whatever beta you want)
2. Reboot recovery (in advanced in cwm)
3. Flash rom again
4. Flash gapps
5. Boot to system
You should be good to go now
sent from my Kick Ass MIUI MoPho using XDA premium
Lately i'm experiencing problems with flashing custom roms (i.e. UltimaROM , Xperianze, whatever)
What i did is:
1: flash the latest CWM , touch and non -touch with Odin
2: download ROM of choice , copy to internal SD-card
3: reboot recovery, fact-reset, wipe cache + dalvik
4: flash rom ( with aroma installer )
5: boot phone
with booting it keeps hanging on the Samsung i9300 logo txt. It doesnt matter which rom i flash. it always keeps hanging.
I've tried alternative methods like flashing TWRP and do the same as above but again, no success. I also tried factory-reset after flash, cache wipe etc. no success.
The weirdest thing is: when i try to flash CM or MIUI ( current running MIUI ) , it works like a charm, but normal "custom" roms are not approved it seems.
does anyone have a suggestion for me what to do? or explain what i am doing wrong , or even better, can explain why CM-based ROMS work?
Have you checked the MD5 of your downloaded ROMs when they are on your SD card? Format system, data and pre-load before flashing? Tried flashing an alternative kernel/radio before you boot the first time?
If only stock based ROMs are a problem then it maybe something that is unique to them, probably a direct hardware hit via the kernel.
Try returning completely to stock to test, flashing Samsung's vanilla EMB5 via Odin - including stock recovery and full wipe. If that doesn't work then you may have a hardware issue that CM or MIUI doesn't use.
yeah good idea to return to stock and try all over again.
to your other questions: no i didnt flash another kernel after i flashed the custom rom. i've tried with several kernels which options were given to me in aroma installer ( boeffla, syah, stock )
md5: did that
format system and data: nope. kinda relied on the fact-reset + cache/dalvik
what do u mean with pre-load?
if I were you I would format data & system again manually after the fac. reset thing, or even more clean use the mega wipe flashable zip to have a clean slate to start from (it will format anything but the ext. sd-card). Then flash the rom from your ext. sd-card and see how it goes.
additional possibly helpful hints
hi there,
i'm not entirely sure if this will help you but generally speaking i came made a few observations about the fact that some people, mostly repeatingly the same users, encounter problems with their custom roms and/or flashing them, while others don't, albeit they are using the same devices.
i my selfe use 3 different devices, all rooted and running on pac 4.3, always lates nightly, as there are GT-N7100 - GT-I9100 - Nexus 4
not to the point
a) other than most other users i usually clean cache and dalvik cache as well before and after flashing the new rom and/or new nightly
and never encountrer any problems except those which everybody, using the same rom and nightly encounters.
b) whenever i flash an totally different rom and/or upgrade and/or downgrade to another level of android os, i.e. from 4.2.2 to 4.3, i perform
a clean install, including not only a factory reset, but as well a format sd-card, format cache and format system etc., again i cannot proof
which of these steps make a or the differnce but however, i never have problems others than thosw which everyone has with a version.
c) when using cusome kernels and due to the fact that some roms come with a kernel included, as well as with a custom recovery included,
it is strongly recommended not to forget to flas the kernel again after each flashing the new rom. one good example ist dorimanx kernel
for GT-I9100 which will not boot into recovery and reluctantly boot at all after a new flash of a pac nightly without reflashing the kernel.
d) try to fix permissions on reboot instead of doing it from recovery. one reason is that not every recovery has this option and further i
found that when fixing permissions before the first boot after flashing a new rom, there might be bootloops, albeit i cannot explain exactly
why that should, but however, sometimes it's better to be on the safe sid.
e) try to run whether the lastes version of custom recovery for your device, and or the use the included custom recovery of the rom or the
kernel. this again is one thing that can help to avoid some unexpected and hard to explain bootproblems and/or fc's etc.
hope that i could give you some new ideas how to avoid trouble while using custom roms and other hacks
magnamentis said:
try to fix permissions on reboot instead of doing it from recovery. one reason is that not every recovery has this option and further i
found that when fixing permissions before the first boot after flashing a new rom, there might be bootloops, albeit i cannot explain exactly
Click to expand...
Click to collapse
Fix permissions was removed because its useless. All permissions are set when flashing by way of updater-script. Fix permissions via recovery "guesses" the permissions which causes issues...
If permissions need fixing, then the updater-script is poor which means you should probably avoid flashing it.
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Fix permissions was removed because its useless. All permissions are set when flashing by way of updater-script. Fix permissions via recovery "guesses" the permissions which causes issues...
If permissions need fixing, then the updater-script is poor which means you should probably avoid flashing it.
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
thanks for the explanation which makes totally sense, so my feeling which i could not explain was right always better to learn exactly why than just guessing
no thanks button found in your post however, so i want to thank you this way.
regards
I searched the internet and threads on XDA for this problem but couldn't really find one!
The problem is- My Galaxy S3 (GT-I9300) doesn't boot any AOSP/AOKP/CM ROMs! It's just the bootanimation and DONE! For hours and hours the bootanimation only! But I can flash any Sammy 4.3 / 4.4 ROMs! They boot! They work properly!
I used to change to AOSP to Sammy and vice versa so many times with no issues. One day I downloaded the UltimaAOSP Valhalla ROM and flashed it. This was the first time my S3 didn't boot. I flashed custom Kernels like boeffla on it but all in vain. It was stuck on the bootanimation. I flashed NeatROM AOSP on top of it, which worked properly. Then it was with the fusion sp ROM that it didn't boot again. Again I flashed NeatROM AOSP on top of it (it's my favorite ROM), which I used just to copy some other ROM from my PC to my phone.
Now, I'm on my Stock ROM which came with my phone since so long! I'm shocked to see now NO AOSP ROMs are booting! I've used C-ROM, NeatROM, Resurrection Remix and SOKP Milestone. I have the ROMs' ZIP files and also a Nandroid Backup which I made when I changed to other ROMs. Not the ZIP files neither the Nandroid Backups are helping! ZIP files get flashed succesfully (I wipe the data & cache & dalvik-cache every time) and the Nandroid Backups get restored successfully! But always the phone gets stuck on the bootanimation!
I always moved to AOSP from Sammy (never Sammy to Sammy) but this time I gave it a shot.
Result : All the Samsung ROMs are flashing, working properly, even the Nandroid restores boot. I flashed my newly downloaded FlashingDroid Sammy 4.4 ROM which also works.
BUT I CAN'T GET THE AOSP ROMs onto my phone!
My thought (it could be wrong) : Is it to do something with the data in a partition other than system, data, and cache? Some partition which has stored files needed to boot Sammy ROMs and is preventing AOSP ROMs to start?
HELP!
:crying:
MORE UPDATED INFO ON POST #6
::ROBLEM SOLVED:::
Wipe system, data, cache and preload partitions manually in mounts and storage in CWM Recovery.
DONE! AOSP Working!
Suggests something is being left behind that aosp objects to. Try the rescue firmware in general forum, wipe internal sd and preload.
boomboomer said:
Suggests something is being left behind that aosp objects to. Try the rescue firmware in general forum, wipe internal sd and preload.
Click to expand...
Click to collapse
Have lots of data on my internal memory! Still I deleted lots of unwanted files. Any other way to wipe the hidden preload partition other than using Philz Recovery? I remember I flashed Philz after which I couldn't restore any of my Nandroid Backups backed up with CWM Recovery..
Sent from my GT-I9300 using XDA Premium 4 mobile app
In cwm mounts and storage wipe preload
Press thanx if i helped you in anyway...
Update - Got More Info
Update : Just noticed that when it's the bootanimation on the screen after flashing an AOSP ROM, pressing any of the buttons on the phone vibrates the phone vigorously 2 times.. why??
Also, I want to ask about the connection between a kernel and a bootanimation without starting a new thread 'cause I think it's the solution to my problem here.. The data which I probably suspect that prevents AOSP ROMs from booting is some different bootanimation file? I mean when I'm on a Sammy ROM, I started to flash different bootanimations after flashing some CWM Custom Bootanimation ZIP file. The bootanimation changes on all Kernels on Sammy ROMs -except 1 that is the boeffla kernel. The strange thing is that the first custom bootanimation I had flashed (after flashing Boeffla's Sammy Kernel) when I switched to Sammy from my last AOSP was the hTC One Bootanimation which worked fine (the bootanimation successfully changed). After that, it never changed. My phone always booted up showing the hTC One Bootanimation no matter how many times I flashed another bootanimation ZIP or the CWM ZIPs which enable/disable Custom bootanimations. But! When I changed to any other kernel (the stock that came with the ROM/GoogyMax 2/AGNi), the bootanimation was the last one flashed by me before changing the kernel. I could change the bootanimations successfuly every time after that. Now, I flashed Android Revolution HD ROM and was on Stock Kernel. As soon as I changed to boeffla kernel (without flashing any other ZIP), the bootanimation changed! (automatically!) And it was again the same old hTC One Bootanimation.
Can someone please tell me WHERE is this bootanimation data and the data that prevents AOSP ROMs to boot is stored? Certainly not in the data or system or cache partition...
Update 2 : Just figured out where the automatic htc bootanimation magic happened. The hTC bootanimation.zip file was found in data/local . However, I always knew the bootanimation directory as system/media.. So now, is it safe for me to delete all files in data/local 'cause it seems it is the problem for AOSP ROMs?
Sent from my GT-I9300 using XDA Premium 4 mobile app
the main thing i can think of is your trying to go back to jb roms which you cant do as far as i know try flashing kitkat based roms
jimbobpro87 said:
the main thing i can think of is your trying to go back to jb roms which you cant do as far as i know try flashing kitkat based roms
Click to expand...
Click to collapse
I'm not trying to go back to Jelly Bean! I'm flashing AOSP based ROMs of KitKat 4.4.2 which don't boot!
SOLVED!
Yayy!
I guess I got a solution!
Wiped system, data, cache and preload partitions manually in mounts and storage in my CWM Recovery.
DONE! AOSP Working!
:victory:
THANKS TO ALL WHO HELPED! :angel:
Thank you for your post.
I am having the same problem, phone not booting past boot animations using aosp ROMs. Haven't tried Sammy ROM to test the theory yet but will try soon.
How do you wipe preload? In mounts and storage, I get an error when trying to mount or format preload using CWM 6.0.4.7
I don't see an option to wipe anything other than data, cache, or dalvic.
alaska_ryder said:
How do you wipe preload? In mounts and storage, I get an error when trying to mount or format preload using CWM 6.0.4.7
I don't see an option to wipe anything other than data, cache, or dalvic.
Click to expand...
Click to collapse
Strange- it happened that day but not now. Even I get an error formatting preload. But! I guess the problem is the system partition! There IS an option to format /system in mounts and storage option on the first screen.
Sent from my GT-I9300 using XDA Premium 4 mobile app
This is really an old post i think.
But, can someone answer me please, ive been searching for This maybe for more than a year. Can someone please help me? @Paresh Kalinani
I have the exact same issue.
My device: Grand Prime (G530FXXU1AOJI baseband)
Stock android: 5.0.2
Recovery: TWRP 3.1.0.0
I have booted many Samsung roms and also ported many of them like J5's 5.1.1 , On7's 5.1.1 rom and many other 5.1.1 and 5.0.2 roms and all of them work perfectly. But when it comes to AOSP ROMS each of them keeps loading at the booting animation screen. Ive tried many roms like RR, AOSP Extended, Cyanogenmod, LINEAGEOS, All of these 5.1.1 , 7.1.1.
It booted for others with the exact Same variant as mine too.
Please help me?
Id been really grateful.
Thanks,
Eden532
Eden532 said:
This is really an old post i think.
But, can someone answer me please, ive been searching for This maybe for more than a year. Can someone please help me? @Paresh Kalinani
I have the exact same issue.
My device: Grand Prime (G530FXXU1AOJI baseband)
Stock android: 5.0.2
Recovery: TWRP 3.1.0.0
I have booted many Samsung roms and also ported many of them like J5's 5.1.1 , On7's 5.1.1 rom and many other 5.1.1 and 5.0.2 roms and all of them work perfectly. But when it comes to AOSP ROMS each of them keeps loading at the booting animation screen. Ive tried many roms like RR, AOSP Extended, Cyanogenmod, LINEAGEOS, All of these 5.1.1 , 7.1.1.
It booted for others with the exact Same variant as mine too.
Please help me?
Id been really grateful.
Thanks,
Eden532
Click to expand...
Click to collapse
Have you flashed the rom then factory reset?
Beamed in by telepathy.
shivadow said:
Have you flashed the rom then factory reset?
Beamed in by telepathy.
Click to expand...
Click to collapse
Nope.
I wiped system, data, cache and dalvik cache the flashed the rom and the rebooted?
Do I have to do a factory reset then?
Thanks a lot for the immediate response.
Eden532 said:
Nope.
I wiped system, data, cache and dalvik cache the flashed the rom and the rebooted?
Do I have to do a factory reset then?
Thanks a lot for the immediate response.
Click to expand...
Click to collapse
Well, what you did was butter than a factory reset.
Factory reset means wiping data, cache and dalvik cache.
I would like you to do something first, try downloading the latest stock firmware for your phone from sammobile, and then flash it with Odin, then try flash AOSP roms again, maybe you have an old bootloader.
MigoMujahid said:
Well, what you did was butter than a factory reset.
Factory reset means wiping data, cache and dalvik cache.
I would like you to do something first, try downloading the latest stock firmware for your phone from sammobile, and then flash it with Odin, then try flash AOSP roms again, maybe you have an old bootloader.
Click to expand...
Click to collapse
Im running the latest firmware which id flashed through odin.
AOSP roms still not booting.
I had wiped those partitions before i flashed the rom. I did not wipe after i flashed them.
Eden532 said:
Im running the latest firmware which id flashed through odin.
AOSP roms still not booting.
I had wiped those partitions before i flashed the rom. I did not wipe after i flashed them.
Click to expand...
Click to collapse
Are you sure it's the latest one?
Did you check Sammobile.com?
The latest one was released in 1st Feb 2017.
Also please check the IMEI of your phone by typing *#06#, because if you've a problem with efs partition you may not be able to flash any AOSP Rom (happened to a friend before..he had sim working without IMEI!!)
Also what is your country code?
As stated above, check your imei is still OK then from a working stock state:
Root it.
Flash custom recovery.
Flash the custom rom twice and then wipe data/cache. Do not wipe system!.
If that doesn't work then try the above but instead of wipe data/cache do a factory reset.
Beamed in by telepathy.
MigoMujahid said:
Are you sure it's the latest one?
Did you check Sammobile.com?
The latest one was released in 1st Feb 2017.
Also please check the IMEI of your phone by typing *#06#, because if you've a problem with efs partition you may not be able to flash any AOSP Rom (happened to a friend before..he had sim working without IMEI!!)
Also what is your country code?
Click to expand...
Click to collapse
My country code is XSG but ill try flashing the THL latest version and again report.
I was trying to check my IMEI number it shows UNKNOWN APPLICATION but sim and other modem related stuff works really fine.
Is it something to do with this?
shivadow said:
As stated above, check your imei is still OK then from a working stock state:
Root it.
Flash custom recovery.
Flash the custom rom twice and then wipe data/cache. Do not wipe system!.
If that doesn't work then try the above but instead of wipe data/cache do a factory reset.
Beamed in by telepathy.
Click to expand...
Click to collapse
I did flash the custom rom twice but still no good.
(And also i checked the IMEI via a custom Sammy rom)
Eden532 said:
My country code is XSG but ill try flashing the THL latest version and again report.
I was trying to check my IMEI number it shows UNKNOWN APPLICATION but sim and other modem related stuff works really fine.
Is it something to do with this?
Click to expand...
Click to collapse
This is the latest firmware for United Arab Emirates:
https://androidfilehost.com/?fid=385035244224412750
Flash it and see if the problem solved :good:
MigoMujahid said:
This is the latest firmware for United Arab Emirates:
https://androidfilehost.com/?fid=385035244224412750
Flash it and see if the problem solved :good:
Click to expand...
Click to collapse
Thank you so much for sending the link, Its really difficult to download from sammobile.com . Ill check it right away and report. Thanks.
Hi;
So i recently installed CyanogenMod 13.0 on to my Samsung S4 GT-I9505 using the first download link on:
https://download.cyanogenmod.org/?device=jfltexx --> cm-13.0-20160102-NIGHTLY-jfltexx.zip
That all installed fine, but i wanted to get the Google apps installed aswell, which is where i am having some issues.
I have been trying to install the following package:
http://opengapps.org/?api=6.0&variant=nano
but have also tried to install quite a few others as well, and all have exactly the same issue. Basically after the apps have been installed and i boot the device up, i get various error messages like:
unfortunately, Setup Wizard has stopped
unfortunately, google play services has stopped
Any help on fixing this would be much appreciated, as nothing seems to download from the play store thats included in Cyanogen, they just say "your download will begin shortly" but never does.
Thanks in advance
I am a total noob, but I had exactly this problem. The issue appears to be that you have to flash gapps *before* rebooting after flashing CM. In my case since I had already flashed CM before I flashed gapps I had to put the gapps file on the phone (I did this by push with adb, you might find an easier way), re-flash CM, wipe cache/dalvik, flash gapps, wipe cache/dalvik, reboot. It worked.
The easiest guide I found was on androiding.how, called "how to install cm13 (cyanogenmod13)." (The forum won't let me post a link, just google it, it should come up).
Hope that helps. I'm on a galaxy s5 and used twrp recovery if that matters.
audacityandrouge said:
I am a total noob, but I had exactly this problem. The issue appears to be that you have to flash gapps *before* rebooting after flashing CM. In my case since I had already flashed CM before I flashed gapps I had to put the gapps file on the phone (I did this by push with adb, you might find an easier way), re-flash CM, wipe cache/dalvik, flash gapps, wipe cache/dalvik, reboot. It worked.
The easiest guide I found was on androiding.how, called "how to install cm13 (cyanogenmod13)." (The forum won't let me post a link, just google it, it should come up).
Hope that helps. I'm on a galaxy s5 and used twrp recovery if that matters.
Click to expand...
Click to collapse
Thanks for the reply, i gave that a try and it seems to be stuck on a loop now with "installing app # of 22" . it completes the installation and then reboots, after about 5 minutes on the Cyanogen boot screen, it goes back to installing apps again.
Hm, did you do a factory reset in your recovery before re-flashing CM and gapps? If not, that might be necessary.
audacityandrouge said:
Hm, did you do a factory reset in your recovery before re-flashing CM and gapps? If not, that might be necessary.
Click to expand...
Click to collapse
Yeah, i did. Tried it multiple times now
That's about the limit of my ability right there, hopefully someone with more experience than me can point you in the right direction. Good luck.
Boot to recovery (preferably TWRP)
Wipe cache / dalvik cache / data / system
Flash CM13 and the gapps you were trying first
Reboot
Profit!
Since you keep flashing different gapps on top of the system, this is probably causing some issues. Once you fully wipe and reflash everything, it should work.
es0tericcha0s said:
Boot to recovery (preferably TWRP)
Wipe cache / dalvik cache / data / system
Flash CM13 and the gapps you were trying first
Reboot
Profit!
Since you keep flashing different gapps on top of the system, this is probably causing some issues. Once you fully wipe and reflash everything, it should work.
Click to expand...
Click to collapse
Ive tried that multiple times using twrp (i always wipe everything before i flash CM13 and gapps), i still get the exact same issue. The second the phone boots, i get all these "unfortunately ******** has stopped".
Perhaps try installing 12.1 with gapps, get it all updated then upgrade to 13. I did the accidental upgrade to 13 but have had no issues whatsoever.
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.