Related
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
Hi guys,
A while back I rooted my Galaxy S3 gt-i9300 international and loaded the S4 Revolutionairy ROM onto it which worked perfectly.
This weekend I decided to flash a new ROM since I have a new phone now and I want to give this one to my girlfriend to replace her old S2.
First I had to upgrade CWM to flash a 4.4 ROM and so I did via Odin. No problems here.
If I perform a wipe data/factory reset it says it can't mount the data partition. A manual mount also gives back an error. If I do load a ZIP file from the external SD card it gives back an error that it can't access data partition, error 7
Looking around I find dozens of people with similar problems but not exactly the same. So I'm a little afraid I make the wrong decision here. The phone keeps booting fine in the S4 Revolutionary ROM but of course the factory reset part did work so every time I have to log into my Google account.
I think I have to flash a factory ROM via Odin first, so basically revert it back to stock completely. Anyone out there who can point me in the right direction or has a better idea?? Thanks!
Did you tried to flash TWRP recovery 2.7.x and then try to install a new rom.Download the latest version of recovery directly from TWRP website
Sent from my GT-I9300 powered by ArchiDroid+ArchiKernel
No. Since the galaxy s1 I use cwm.
But it's worth a shot. I'll keep you posted.will try this later on.
Verstuurd vanaf mijn GT-I8190 met Tapatalk
vinz3nt said:
No. Since the galaxy s1 I use cwm.
But it's worth a shot. I'll keep you posted.will try this later on.
Verstuurd vanaf mijn GT-I8190 met Tapatalk
Click to expand...
Click to collapse
Flash latest Cwm but i am afraid that Odin and stock rom will only work. More work but not that much
Sent from my GT-I9300 using XDA Free mobile app
I don't like to flash with CWM. There's no way to flash with Philz Touch? Use it, way better. When people ask me to flash a custom ROM, I use Philz. It's prepared make a factory reset and prepare your phone to a new ROM without problems.
But if you're going through with CWM, I suggest to get the lastest version and try again.
It worked fine with TWRP 2.7.1.0
I really love it, looks very good, lots of options and just really working fine!
I just flashed the Liquid Smooth ROM with Android 4.4.4. My phone is really really fast now!
Thanks a lot
Hi,
I flashed Carbon ROM 4.4.4 you can find it here
Or dowload directly from here.
The Google Apps can be download from here, I used the Nano version, only the Google base, Google services and Google search are incorporated so byebye Google+ and al unwanted stuff, Google Now is in there though but the complete package comes in at only 57 MB which saves a lot of space, Gmail and YouTube can be downloaded from the Play store.
I'm really impressed by this ROM, it's really fast, everything works including both camera's, bluetooth in my car works flawlessly (connects faster then ever), battery life is also really good so far, took it from the charger 7.30 this morning and used it quite a bit till now (15:00) and still at 77%. Wifi is working fine and GPS connection is really fast (had to figure out first they use another icon for GPS now and it's on the right on the taskbar now).
A lot can be customized as well but I also installed Xposed now for even more freedom.
I can really recommend it, I like it more than CM (which I also really like) but that's personal.
PS I'm a big fan of the TWRP recovery now. It's really so much better than CWM and much much more intuitive.
Hi to everyone!
I have a problem to share because I hope anyone can help me to fix it.
My OnePlus 2 with the stock ROM of OxygenOS 3.1.0 (never unlocked bootloader or installed custom roms... always with the original system) has a problem: since 2 weeks he started rebooting randomly... it may happen from 1 up to 3 times a day (in my situation). These reboots are not caused by apps I think because a lot of them happens when the phone is with screen looked and it is in my poket or on the table (on charge and withoutcharge also, is indifferent). Sometimes happened also while using it (it could be a browsing session, a photo.... it's random!).
I also noticed that before the restart the phone freezes, expecially when its screen is turned off, you can't turn it on and all gestures or phisical key (also the fingerprint) doesn't work.
I noticed the first time that the phone rebooted exactly for the fingerprint sensor, because I tryed to unlock it and it said that after reboot I need to first insert the unlock sequence.
I tried (in this oreder):
- to make a cache and data wipe from recovery (with no result);
- to make an hard reset from the recory installed into the phone (with no result);
- to make another FULL wipe and reinstall the OxygenOS from the zip installer on the official download section of the oneplus website (with no result).
Now, I beg to all of you to help me if you have any suggestion or know a fix for this problem.
Thanks in advance to all people that will help me
Hi...
U will need to upgrade to the latest oxygen os 3.5.6/3.5.6 or flash a custom ROM like cm.
In order to do that u will need to unlock bootloader and install twrp and then flash zip.
Ensure u take a nandroid backup in twrp before flashing roms
Everything can be found on google. [emoji4]
Hope it solve the problem
Sent from my ONE A2005 using Tapatalk
But the phone worked well for months... why now there is this problem? And anyway there is no update by OTA and I don't want to unlock the bootloader for an update that I have to recive by official way...
claudio.94 said:
But the phone worked well for months... why now there is this problem? And anyway there is no update by OTA and I don't want to unlock the bootloader for an update that I have to recive by official way...
Click to expand...
Click to collapse
It's probably caused by a google app running in the background.
If u can get a logcat of the the device before reboot without root would have an idea.
Sent from my ONE A2005 using Tapatalk
How can I take a logcat? and anyway I don't know when the phone will reboot... and when I discover it is too late because like I said it freezes for 10-15 seconds and I can't make anything...
Well if u are looking for ota, check out this: https://forum.xda-developers.com/oneplus-2/general/hot-fix-3-5-6-oneplus-2-official-update-t3528911
since u don't want to unlock bootloader n stuff.
Sent from my ONE A2005 using Tapatalk
Oh thanks... but why I didn't recived it by OTA?
Well idk but I think it is released in some country or not quite official yet.
Tbh I'm using custom Roms so I never checked it.
As they say, it fixed random boots and use a VPN and select Germany or Canada to download the zip via ota or can manually flash in stock recovery.
I recommend the ota it's more safe.[emoji2]
Sent from my ONE A2005 using Tapatalk
Ok... I will try it
Are their any projects related to the Oukitel K9 phone? I purchased one and use it on the AT&T network here in the USA.
The phone is decent but the built in Android is very generic and buggy.
I would love to unlock the potential of this phone with a custom ROM.
Let me know if this isn't the right place to ask and point me in the right direction!
Lannie
No custom roms at this time, why bother when you can custom Android 9 using Magisk , Xposed and Substratum. Although having a Lineage 17 would be nice.
I ask because the Android on this phone is so buggy and lacking features. I don't see how the options you gave will add features I need. They might as I'm new to these apps and don't know much about them.
lschafroth2 said:
I ask because the Android on this phone is so buggy and lacking features. I don't see how the options you gave will add features I need. They might as I'm new to these apps and don't know much about them.
Click to expand...
Click to collapse
If you private message me I cannot get to the messages here. If I click on messages it takes me to the register or reset password every time. I have no way to read them.
At this point it's useless to try since the mediatek drivers no longer work on Windows 10. Not a single guide on installing on Windows 10 64 bit work anymore. If anyone knows how to get the Oukitel drivers to work, let me know. No amount of driver sign or advanced boot works. Every time I plug in the phone it says the previous device malfunctioned.
It worked once and I have never connected the phone since. Will not work.
lschafroth2 said:
At this point it's useless to try since the mediatek drivers no longer work on Windows 10. Not a single guide on installing on Windows 10 64 bit work anymore. If anyone knows how to get the Oukitel drivers to work, let me know. No amount of driver sign or advanced boot works. Every time I plug in the phone it says the previous device malfunctioned.
It worked once and I have never connected the phone since. Will not work.
Click to expand...
Click to collapse
This might seem obvious, but could never get my PC (Windows10 64bit) to even recognize my Oukitel K9 until I (out of desperation, and to try to prove a point to someone) reinstalled Minimal ADB & Fastboot 1.4.3 from here:
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
It's the same thing I had previously installed, and I didn't expect it to suddenly/miraculously start working, but it did.
I'll pm you.
lschafroth2 said:
Are their any projects related to the Oukitel K9 phone? I purchased one and use it on the AT&T network here in the USA.
The phone is decent but the built in Android is very generic and buggy.
I would love to unlock the potential of this phone with a custom ROM.
Let me know if this isn't the right place to ask and point me in the right direction!
Lannie
Click to expand...
Click to collapse
Best rom floss october edition with buildprop tweaks transformed this phone into next level. Thanks to phherguson
nation888888 said:
Best rom floss october edition with buildprop tweaks transformed this phone into next level. Thanks to phherguson
Click to expand...
Click to collapse
Thanks, but I sold this phone and went to a Pixel 4 XL. I needed something reliable and InTune refused to work on the old Oukitel.
Has anyone worked out ramdisk partition for Magisk?
Discovery,
Thanks to Phh has developed the perfect ROM for the Oukitel K9. Strangely I have had to try many ROMs to find the perfect one. The Lineage ROM; I had GPS issues, the Recent app button not working, and signal loss. Wanted the latest OS and this one is the winner below.
https://github.com/phhusson/treble_experimentations/releases/download/v400.e/system-squeak-arm64-ab-vndklite-gapps-secure.img.xz
Llevo un par de semanas probando la rom y no funciona el detector de huellas,se puede mejorar?hay alguna rom(Android 12) mas estable y que todo funcione?,gracias
MOD Edit: I've been testing the rom for a couple of weeks and the fingerprint sensor doesn't work, can it be improved? Is there a more stable rom (Android 12) that makes everything work? Thanks
Try the updated version https://github.com/phhusson/treble_experimentations/releases/tag/v402
Should resolve the fingerprint issue. I have also tried the AOSP 12.1 v410 and the result is the phone goes into a boot loop. Not sure why when the previous version installs so easily. I have built a custom TWRP 3.6.1 and will be trying it soon. The reason why we need to update; that the TWRP 3.3.1 version is limited and could be the reason why there are install issues with some GSIs out there. The encryption keeps reactivating even if I use scripts, flash no verify-verity. Hopefully, this will work. I'm enjoying the new version too much to start again I will keep you posted.
This one is supreme V411 and distracts me away from my Note 20 Ultra. https://github.com/phhusson/treble_experimentations/releases/tag/v411 .Works well with the Oukitel K9, recommend to use swapram module for boosting memory 4gb to 8gb. Searching for a working TWRP 3.6.
nation888888 said:
This one is supreme V411 and distracts me away from my Note 20 Ultra. https://github.com/phhusson/treble_experimentations/releases/tag/v411 .Works well with the Oukitel K9, recommend to use swapram module for boosting memory 4gb to 8gb. Searching for a working TWRP 3.6.
Click to expand...
Click to collapse
Have you found better rom for k9? I've used several gsi images but system is very laggy. Yet to find a good fast custom rom for k9.
[email protected]@ said:
Have you found better rom for k9? I've used several gsi images but system is very laggy. Yet to find a good fast custom rom for k9.
Click to expand...
Click to collapse
I found this one is the best;
https://www.mediafire.com/file/74b5bgfu0vsjcvg/CherishOS_A13-arm64-bgS-slim_20221121.img.xz/file
nation888888 said:
I found this one is the best;
https://www.mediafire.com/file/74b5bgfu0vsjcvg/CherishOS_A13-arm64-bgS-slim_20221121.img.xz/file
Click to expand...
Click to collapse
Thanks a lot. I will give it a try!
nation888888 said:
I found this one is the best;
https://www.mediafire.com/file/74b5bgfu0vsjcvg/CherishOS_A13-arm64-bgS-slim_20221121.img.xz/file
Click to expand...
Click to collapse
I've flashed this one and found it is as laggy as CrDroid. I thought it might be due to not wiping data before flashing. Decided to reboot to recovery to wipe data. And.. phone stuck at twrp logo. No go further. Do you have any better TWRP than mine 3.3.1?
Try using the "Yet another Kernel Tweaker" module in Magisk. Through all my searches I could only find the TWRP 3.3.1. Tried building using kitchen but failed. Sometimes the TWRP will take up to 5 to 10 minutes, remember it is trying to decrypt. If it takes longer then SPflash, assuming done correctly with vbmeta. After the initial install the updates and synchronization starts processing. This causes a slow-down. I thought the same. Leave the device for a day to update and synchronize then should be faster.
nation888888 said:
Try using the "Yet another Kernel Tweaker" module in Magisk. Through all my searches I could only find the TWRP 3.3.1. Tried building using kitchen but failed. Sometimes the TWRP will take up to 5 to 10 minutes, remember it is trying to decrypt. If it takes longer then SPflash, assuming done correctly with vbmeta. After the initial install the updates and synchronization starts processing. This causes a slow-down. I thought the same. Leave the device for a day to update and synchronize then should be faster.
Click to expand...
Click to collapse
TWRP logo is for hours here.
Now I can't even enter fastboot after I've chosen reboot to recovery from cherishos power menu.
I hit volup+pwr and boot menu doesn't even show up. Tried 20+ times already.
I'm stuck. The last hope is to wait for it to discharge on twrp logo and try my luck with fastboot menu again.
Otherwise I have no idea. Now I question myself why on Earth I would even try to better something that works at least average ))))
nation888888 said:
Try using the "Yet another Kernel Tweaker" module in Magisk. Through all my searches I could only find the TWRP 3.3.1. Tried building using kitchen but failed. Sometimes the TWRP will take up to 5 to 10 minutes, remember it is trying to decrypt. If it takes longer then SPflash, assuming done correctly with vbmeta. After the initial install the updates and synchronization starts processing. This causes a slow-down. I thought the same. Leave the device for a day to update and synchronize then should be faster.
Click to expand...
Click to collapse
I've managed to revive it. But still on cherishos and few other A13 roms screen is flickering. Have you got something like that?
Build in the works. Going to release the BETA as soon as I can do testing on my own device before release.
IMO this is a necessity as there are literally no good roms for this right now. I tried the port of the Nexus stock CR rom and it was not great. Playstore was unusable due to an issue were the app thinks the system is out of storage space, even though it is almost empty. Chrome crashes instantly, the search on the page home screen flickers up/down without control.
I am a far bigger fan of LineageOS thus why I am working on this build.
More to come.
SniperFox22 said:
Build in the works. Going to release the BETA as soon as I can do testing on my own device before release.
IMO this is a necessity as there are literally no good roms for this right now. I tried the port of the Nexus stock CR rom and it was not great. Playstore was unusable due to an issue were the app thinks the system is out of storage space, even though it is almost empty. Chrome crashes instantly, the search on the page home screen flickers up/down without control.
I am a far bigger fan of LineageOS thus why I am working on this build.
More to come.
Click to expand...
Click to collapse
YES! Thank you very much for supporting this tablet!
SniperFox22 said:
Build in the works. Going to release the BETA as soon as I can do testing on my own device before release.
IMO this is a necessity as there are literally no good roms for this right now. I tried the port of the Nexus stock CR rom and it was not great. Playstore was unusable due to an issue were the app thinks the system is out of storage space, even though it is almost empty. Chrome crashes instantly, the search on the page home screen flickers up/down without control.
I am a far bigger fan of LineageOS thus why I am working on this build.
More to come.
Click to expand...
Click to collapse
As a follow up to my original post I wanted to mention that for anyone who wants a new ROM on their SM-T290 until this is finished development, use the Nexus Rom by Magendanz. I was able to do a fresh stock firmware install and retry the rom and my opinion has changed. I have noticed that these Tab A 8.0 tablets have been used a lot for like Uber/Door Dash and other POS terminals. I am pretty sure a lot of them have modified or customized firmware for these reasons and when I mine second hand it was from a pizza store. I think that messed up the upgrade.
Overall Magendanz did a great job, when you install it properly. I have zero issues with functionality now, TWRP recovery set up, as well as Magisk installed and everything is running extremely well.
As far as instruction on how to install. Take a look at some of the comments further down on the Nexus thread. That is what I did this time around and it worked perfectly. Last thing I did was copy Magisk.Apk to my SD, change extension from .APK to .ZIP, then boot into TWRP and install that ZIP.
Going to update progression on a monthly basis as far as the LineageOS 18.0 build
SniperFox22 said:
Build in the works. Going to release the BETA as soon as I can do testing on my own device before release.
Click to expand...
Click to collapse
Do you have a github with your source code and manifest? I just got this tablet (used) yesterday and I would like to see if I can help. I have built LineageOS roms for a number of older Samsung Tab A devices, but will have to do some research on the "new to me" T290. Thanks.
Just got this tablet, how's the beta coming along? And what can I do to help?
Thank you my guy I had lost all hope for custom roms on this tablet. It's quite relieving to know that I'm not alone.
Also, has anyone experienced severe lag on one ui 3 while doing basic tasks? The thing literally gets 5 fps while watching youtube and surfing the web but it plays 3d games at 20 fps on low settings. wtf
HaveSomeRubicon said:
Thank you my guy I had lost all hope for custom roms on this tablet. It's quite relieving to know that I'm not alone.
Click to expand...
Click to collapse
Hey Guys,
I didnt end up building a custom rom, because I was able to get the GSI version of Lineage 19 working fairly easily. Just use the correct image and flash the same as the Nexus post. Android 12 with Lineage 19 so i felt it wasnt worth it as everything works. I had trouble at first with a boot loop but that was because I had installed Magisk BEFORE the GSI rom and not AFTER. So dont make my mistake.
As per the Nexus Post;
Unlock Bootloader
flash TWRP
Wipe data
Install Andy Yan's Lineage OS 19 GSI
Andy Yan's personal builds // GSI - Browse /lineage-19.x at SourceForge.net
sourceforge.net
Install Magisk
Reboot
Cheers!
SniperFox
SniperFox22 said:
Hey Guys,
I didnt end up building a custom rom, because I was able to get the GSI version of Lineage 19 working fairly easily. Just use the correct image and flash the same as the Nexus post. Android 12 with Lineage 19 so i felt it wasnt worth it as everything works. I had trouble at first with a boot loop but that was because I had installed Magisk BEFORE the GSI rom and not AFTER. So dont make my mistake.
...
SniperFox
Click to expand...
Click to collapse
Good advice But which of Andy's GSIs did you use exactly ?
Thanks so much dude
The GSI is a .img.xz will it work or does it need to be .gsi
HaveSomeRubicon said:
The GSI is a .img.xz will it work or does it need to be .gsi
Click to expand...
Click to collapse
You download the .img.xz file and unzip it.
Inside this will be the .img file
This is what you need to flash (.img)
2faraway2 said:
Good advice But which of Andy's GSIs did you use exactly ?
Click to expand...
Click to collapse
Sorry
Use this one
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS.img.xz
It has Gapps built in as well as super user through SSH, dont install Magisk as it will error that there is already SU tool installed.
@SniperFox22 , did you make a github for the code or didn't even start since you are happy with GSI?
SniperFox22 said:
You download the .img.xz file and unzip it.
Inside this will be the .img file
This is what you need to flash (.img)
Sorry
Use this one
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS.img.xz
It has Gapps built in as well as super user through SSH, dont install Magisk as it will error that there is already SU tool installed.
Click to expand...
Click to collapse
My OS didn't have an option to unzip it at first glance. I haven't been able to install gapps so I'm gonna try that gsi. Also, am I supposed to wipe internal storage before flashing or not?
I got it working but games just crash which is worse than before
Came across this while trying to root my sm-t290. Just want to add that Andy Yan has upgraded to a 19.1 version that appears to work just fine. Flashed to system partition using twrp after I had flashed the Nexus rom. Wifi works, sound works, sd card, bluetooth keyboard works just fine.
SunSlide said:
Came across this while trying to root my sm-t290. Just want to add that Andy Yan has upgraded to a 19.1 version that appears to work just fine. Flashed to system partition using twrp after I had flashed the Nexus rom. Wifi works, sound works, sd card, bluetooth keyboard works just fine.
Click to expand...
Click to collapse
Link to it???
I like the link above because it has all the versions but lineage-19.1-20220320-UNOFFICIAL-arm64_bgS.img.xz is the one that I used. The page has the naming convention. Ill mention that even though it says that it's supposed to be rooted, I couldn't get it to work right. The nexus rom had an option in the 'phh treble' menu to activate root and this lineage image should also but the option wasn't there. It kept saying the supersu binary was busy but that was after I flashed a supersu.zip(it may have worked before then i don't know). I played with it a little bit but ended up just flashing back to the Nexus rom.
Hey guys!
Installed "lineage-19.1-20220320-UNOFFICIAL-arm64_bgS.img"
Everything starts up, but something is weird with my installation and my storage, it freezes when i go into storage and i cant download anything without apps start to crash.
Im not sure if i flashed it correctly, i did a wipe in TWRP before installation.
Really hope i can get this to work since it waaaaay faster then the bloat samsung ships
Edit:
Tried flashing another rom (nexus) and had the same issue!
trying to reflash and wipe everything except internal storage.
Where should i flash image? i get: "select partition to flash image", never seen that before (might be because you flash img and not zip)
SniperFox22 said:
Hey Guys,
I didnt end up building a custom rom, because I was able to get the GSI version of Lineage 19 working fairly easily. Just use the correct image and flash the same as the Nexus post. Android 12 with Lineage 19 so i felt it wasnt worth it as everything works. I had trouble at first with a boot loop but that was because I had installed Magisk BEFORE the GSI rom and not AFTER. So dont make my mistake.
As per the Nexus Post;
Unlock Bootloader
flash TWRP
Wipe data
Install Andy Yan's Lineage OS 19 GSI
Andy Yan's personal builds // GSI - Browse /lineage-19.x at SourceForge.net
sourceforge.net
Install Magisk
Reboot
Cheers!
SniperFox
Click to expand...
Click to collapse
Hi Sniperfox,
could you please provide a link to the correct Nexus post, I would like to make sure i follow the correct one as I have a tab A (2019) and want to nstall lineage.
thanks in advance
rgds Acsum