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?
Related
Hi, my friends.
Great news . The new official update Leeco that has come in Indian web finally brings everything to their phones sold worldwide:
- Multilanguage. But, really. All are translated (I only tried Spanish, I assume that the other languages also). In Europe only translate to Spanish, English and French. The rest are Asian languages.
- Leeco Account. Integrated with Google account, as it should be. Leeco access to the entire EUI universe. Synchronization of our contacts, photos, etc.
- All active applications, including Leeco LIVE, Levidi, Leview ...
- Google for Works integrated with Gmail Exchange account, Play Music, Play Video, Google+, Yotube .
Only rest check battery perfomance, but ROM it´s smooth and powerful.
Download links:
Official: http://g3.letv.cn/209/7/47/letv-hdtv/0/upload/tmp/20160706171018829/LE_X2_X820-OS-OP-FGXOSOP5801507066S-5.8.015S.zip?b=123456&platid=5&splatid=500
Mega: https://mega.nz/#!wtplFRIQ!l5V9p8PtpmqEznqQjkm9vFNG6LCgM-KrpEDbTShiwn0
Enjoy ¡¡¡
yes, it's a good one. just installed no problems so far.
I had a problem with previous stock versions that 4G speed had some hickups....when I was downloading (for example from google store) it paused for 30 seconds..sometimes longer.
tried SIM in slot 2 and vice versa..but problem remains.
now it goes smoothly without pauses (so far)
also had the CM13 which is almost the best, apart from the sound bug...definitely one I want on this phone for a long time..if sound thingy is fixed.
thanks!
Recommendation Do Not Use India version
This version apparently has data encryption enabled and will not show a viable data partition. This will cause TWRP to fail and subsequent attempts at root or installation of other roms.
jim262 said:
This version apparently has data encryption enabled and will not show a viable data partition. This will cause TWRP to fail and subsequent attempts at root or installation of other roms.
Click to expand...
Click to collapse
Hmm..Ok! phone is encrypted indeed..do you know if there's as a way to decrypt or turn it off.?twrp is asking for a password when going onto recovery now...in previous roms the encrypt option was not greyed out.
or is only way to get in twrp and wipe everything.
Thanks !
jim262 said:
This version apparently has data encryption enabled and will not show a viable data partition. This will cause TWRP to fail and subsequent attempts at root or installation of other roms.
Click to expand...
Click to collapse
What is the way around the issue of encryption? So we can never install TWRP ever?
sanke1 said:
What is the way around the issue of encryption? So we can never install TWRP ever?
Click to expand...
Click to collapse
Under TWRP data it´s encrypted. But under Windows not. Copy to your computer all files that you need save (photos, music, etc.), and then format data in TWRP.
jim262 said:
This version apparently has data encryption enabled and will not show a viable data partition. This will cause TWRP to fail and subsequent attempts at root or installation of other roms.
Click to expand...
Click to collapse
Under windows DATA partition works properly, copy all your files (photos, music, etc.) into computer and then enter TWRP and format DATA.
This ROM it´s better that anyone, I think that worth trying. It´s awesome.
STEVE_MARS said:
Under windows DATA partition works properly, copy all your files (photos, music, etc.) into computer and then enter TWRP and format DATA.
This ROM it´s better that anyone, I think that worth trying. It´s awesome.
Click to expand...
Click to collapse
I wold'n say that his rom is better than others, here is still missing the multilingual support and so on. I'm atm with "Revolution 15s EUI 5.8 by TeaMSpaiN" alsolutely happy, just litte fine tuned and see my benchmark with over 143.000 points (first run). And yes the rom is smooth as hell.
Antutu proof pic:
http://www.pic-upload.de/view-31202011/Screenshot_20160714-071230.jpg.html
NU_User said:
I wold'n say that his rom is better than others, here is still missing the multilingual support and so on. I'm atm with "Revolution 15s EUI 5.8 by TeaMSpaiN" alsolutely happy, just litte fine tuned and see my benchmark with over 143.000 points (first run). And yes the rom is smooth as hell.
Antutu proof pic:
http://www.pic-upload.de/view-31202011/Screenshot_20160714-071230.jpg.html
Click to expand...
Click to collapse
:angel: yes, we developed Revolution series :good:. But I recommended you that try this Indian version .
STEVE_MARS said:
:angel: yes, we developed Revolution series :good:. But I recommended you that try this Indian version .
Click to expand...
Click to collapse
no
---------- Post added at 10:53 AM ---------- Previous post was at 10:25 AM ----------
@STEVE
if you want help you can try to fix the CM13 rom, THIS one, if would been fixed where of course the ultimare rom for our little beast.
STEVE_MARS said:
Under windows DATA partition works properly, copy all your files (photos, music, etc.) into computer and then enter TWRP and format DATA.
This ROM it´s better that anyone, I think that worth trying. It´s awesome.
Click to expand...
Click to collapse
You did not understand my question properly.
Right now, there is absolutely NO way to install TWRP on Indian X821 model. I cannot format DATA without installing TWRP.
All the TWRPs available on this forum give a BLOD (Blue Led of Death) The screen remains blank but powered on. The Blue LED light remains. There is another guy who is having the same problem and he has created a separate topic for it.
We can restart the phone normally but the installed TWRP gets overwritten with stock recovery.
atm here is no solution for your device, you need to wait until a developer create a TWRP compatible for your device.
sanke1 said:
You did not understand my question properly.
Right now, there is absolutely NO way to install TWRP on Indian X821 model. I cannot format DATA without installing TWRP.
All the TWRPs available on this forum give a BLOD (Blue Led of Death) The screen remains blank but powered on. The Blue LED light remains. There is another guy who is having the same problem and he has created a separate topic for it.
We can restart the phone normally but the installed TWRP gets overwritten with stock recovery.
Click to expand...
Click to collapse
What I did was to go into settings -> fingerprint -> -> other security options -> trusted credentials and disabled the credentials. You have to do this one by one as the clear all option is grayed out. From there I went into and fast boot and flashed TWRP recovery. I rebooted immediately to RECOVERY wiped everything on internal storage. I then transfered a ROM to storage and flashed normally. All is working again and TWRP and root are functioning.
WTF, ok it is a security related issue?
jim262 said:
What I did was to go into settings -> fingerprint -> -> other security options -> trusted credentials and disabled the credentials. You have to do this one by one as the clear all option is grayed out. From there I went into and fast boot and flashed TWRP recovery. I rebooted immediately to RECOVERY wiped everything on internal storage. I then transfered a ROM to storage and flashed normally. All is working again and TWRP and root are functioning.
Click to expand...
Click to collapse
I flashed old 14S Chinese ROM and then flashed recovery. My phone shows X820 now. I guess X820 and X821 may be just the same. It's the Chinese Roms show X820 and Indian Rom shows X821.
BTW I am on TeamSpain's CM Rom. Working good except charging.
If I used my Aukey QC 3.0 charger, the LED flashed like crazy and Ampere current measuring App showed 4680 mAh charging current and was climbing. (QC 3.0 shouldn't exceed 3000 mAh) So I immediately disconected it. Gave me a scare for a moment. Normal charging is slow but no LED blinking and feels safer.
NU_User said:
WTF, ok it is a security related issue?
Click to expand...
Click to collapse
Not a security. Just a way for Indian Dev's to prevent users from messing with their OS and to keep users on 100% stock.
STEVE_MARS said:
Hi, my friends.
Great news . The new official update Leeco that has come in Indian web finally brings everything to their phones sold worldwide:
Enjoy ¡¡¡
Click to expand...
Click to collapse
So can someone clarify if there's a way to clean install this ROM on a Chinese version of the phone and have a) TWRP b) ROOT working or is that impossible for now?
Exactly the same way as you install any other ROM. I have a Chinese phone and installed this ROM and uninstalled it because of its encrypted. Yes, the le-bloat is gone, but you will be unable to install TWRP or root because of the encryption.
jim262 said:
Exactly the same way as you install any other ROM. I have a Chinese phone and installed this ROM and uninstalled it because of its encrypted. Yes, the le-bloat is gone, but you will be unable to install TWRP or root because of the encryption.
Click to expand...
Click to collapse
Copy all your files (photos, videos, music, etc.) under Windows and enter TWRP, format DATA, reboot system, configure setupwizard, reboot TWRP again and copy supersu. zip and flash it.
I have the resurrection 5.8.0 installed (30 Dec build) and my phone takes about 5 minutes to boot. Initially it is stuck in the MI logo for about 4 minutes before the animation starts. I have used several ROMS and kernals and they all seem to do the same thing. I never had this issue with MIUI. Once the phone has booted, the phone is totally fine however I would prefer to identify and fix the problem. Any suggestions? I have already done a complete wipe, and tried various verions of TWRP with no joy. Thanks
I suggest you to flash the latest version of MIUI latest china dev, then from fastboot flash twrp, then clean flash rom + kernel. It takes about 30 minutes if you know what you're doing.
So basically restore then start from scratch? That did cross my mind... I will give it a go. Thanks. I will report back here.
ginohabibi said:
So basically restore then start from scratch? That did cross my mind... I will give it a go. Thanks. I will report back here.
Click to expand...
Click to collapse
Hi if you find a fix for this problem please share it with me, I tried latest china dev rom, latest global dev rom and latest global stable rom with all versions the boot time goes to 4-5 minutes...
ufoshop said:
Hi if you find a fix for this problem please share it with me, I tried latest china dev rom, latest global dev rom and latest global stable rom with all versions the boot time goes to 4-5 minutes...
Click to expand...
Click to collapse
Try method in my signature.. it should work for you
khajiit said:
Try method in my signature.. it should work for you
Click to expand...
Click to collapse
Where do i find that method?
https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
Alright, im going to try that method and i will report my results here.
Followed all the steps within your guide, but that guide didnt work and has nothing to do with our slowboot issue.
Hardware related then
ginohabibi said:
I have the resurrection 5.8.0 installed (30 Dec build) and my phone takes about 5 minutes to boot. Initially it is stuck in the MI logo for about 4 minutes before the animation starts. I have used several ROMS and kernals and they all seem to do the same thing. I never had this issue with MIUI. Once the phone has booted, the phone is totally fine however I would prefer to identify and fix the problem. Any suggestions? I have already done a complete wipe, and tried various verions of TWRP with no joy. Thanks
Click to expand...
Click to collapse
Didnt you change recently some parts of the phone? Like display/baterry and so...?
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
paladzin said:
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
Click to expand...
Click to collapse
So you say there is no solution to run the official rom without waiting 4-5 mins on boot, I have the phone from fastcardtech and maybe is a refurbished unit because they have very low prices compared to other resellers...the phone came in sealed box...
Dwnld links plzz..
Hay anybody here ...is there any other kernal for andriold n ROMs...
paladzin said:
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
Click to expand...
Click to collapse
Mine to, it 2 time I had to replace screen. I'll give a test right now and report back.
Im not using the device anymore, but i think i had to replace the screen like 3-4 times, its very fragile, even a drop from small height makes it crack. Also without case its very slippy device, but none of that matters. From the 4 displays i used, which all have been touchscreen + lcd + the frame (as i dont like to glue the display, i pay 10 dollars more and its better) had that exact same problem, which is very long waiting for the device to boot. The custom kernel solved it, but another (probably better quality) display does solve it too.
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2
The last weeks I had my fair share of geek awesomeness with my shiny brand new POCO F1 and, in my own right, installed many (a dozen) custom-roms and another bunch of vendor and firmware versions, all of them specifically for the Poco F1.
I was using Havoc OS 2.5 and did an OTA update to version 2.6. Everything normal, ok, but I decided to get back to MIUI because two camera related APPs didn't work well with any of the custom roms I've installed and "ok, I'll get back to MIUI, is not bad afterall and the screenrecorder is WAY better than any of the others I tried".
Recovery, wipe, format, flashed MIUI 10.3.4 no problems or error messages like always, reboot, recovery, magisk, reboot, let the system do its stuff, Miui account, google account, the whole thing is ok, play store recovering my cloud backup, ok. Everything works really ok until the first reboot. After the reboot the "Find my device" halts repeteadly, running the system inoperable. "Find my device has crashed and bla bla bla" forever. As long as i use the system first boot, is ok, but eventually, I need to reboot and after that, "find my device has crashed". I've got back to Havoc OS 2.6 and is, like always, running like a charm.
I've tried to get back to MIUI 10.2.2 (whice came pre-installed) to try an OTA update to 10.3.4, but in 10.2.2 also the find my device crashes every time.
What kind of sorcery is happening here? Any thoughts?
Flash fastboot room
Flash fastboot rom
always flash miui with mi flasher
[SOLVED]
alfarhaannizam said:
Flash fastboot rom
Click to expand...
Click to collapse
Worked like a charm. Downloaded MIUI 10.2.3 fastboot rom and flashed using Xiaomi Adb/Fastboot Tools. And then updated to MIUI 10.3.4 via system updater.
Thanks for the heads up. It was really helpful.
mendax99 said:
always flash miui with mi flasher
Click to expand...
Click to collapse
Mi Flasher don't work allright in my computer, since I only have USB 3.0 on my windows device and it seems MI Flasher doesn't work with USB 3.0
I'm using, usually command line abd and fastboot on windows. Today I've downloaded Xiaomi ADb/Fastboot Tolls and it was very useful.
I can't post links yet since I'm new on the forum. But search for Xiaomi ADB/Fastboot Tools GitHub. it is powerful.
otaodofino said:
The last weeks I had my fair share of geek awesomeness with my shiny brand new POCO F1 and, in my own right, installed many (a dozen) custom-roms and another bunch of vendor and firmware versions, all of them specifically for the Poco F1.
I was using Havoc OS 2.5 and did an OTA update to version 2.6. Everything normal, ok, but I decided to get back to MIUI because two camera related APPs didn't work well with any of the custom roms I've installed and "ok, I'll get back to MIUI, is not bad afterall and the screenrecorder is WAY better than any of the others I tried".
Recovery, wipe, format, flashed MIUI 10.3.4 no problems or error messages like always, reboot, recovery, magisk, reboot, let the system do its stuff, Miui account, google account, the whole thing is ok, play store recovering my cloud backup, ok. Everything works really ok until the first reboot. After the reboot the "Find my device" halts repeteadly, running the system inoperable. "Find my device has crashed and bla bla bla" forever. As long as i use the system first boot, is ok, but eventually, I need to reboot and after that, "find my device has crashed". I've got back to Havoc OS 2.6 and is, like always, running like a charm.
I've tried to get back to MIUI 10.2.2 (whice came pre-installed) to try an OTA update to 10.3.4, but in 10.2.2 also the find my device crashes every time.
What kind of sorcery is happening here? Any thoughts?
Click to expand...
Click to collapse
Why just not just freeze the app/ service ? That's what I did.
MasterFURQAN said:
Why just not just freeze the app/ service ? That's what I did.
Click to expand...
Click to collapse
Because the service was broken. Yes, maybe I could adb and freeze the service, but the service would still be broken, probably due to many different firmware/vendor versions installed on the last couple weeks.
The fastboot rom is more comprehensive in terms of background images (cust/dsp/persist) and flashing it totally nailed the error.
otaodofino said:
Because the service was broken. Yes, maybe I could adb and freeze the service, but the service would still be broken, probably due to many different firmware/vendor versions installed on the last couple weeks.
The fastboot rom is more comprehensive in terms of background images (cust/dsp/persist) and flashing it totally nailed the error.
Click to expand...
Click to collapse
Yeah. I know that flashing a fastboot ROM is the best way to repair corrupt partitions but it also resets the phone and I'm too lazy to restore everything back. Lol.
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