Hi guys,
I've flashed my Nexus 6 with Stock Lite without encryption and the phone is working very well. I was hoping to find stock like for the nexus 9 but it seems there is no version of it for Nexus 9.
What firmware would you guys recommend that is the closest to stock android, of the less bloated without encryption enforced that I can put on my nexus 9?
My model is the 16GB WIFI only
Thanks!
My AOSP is closest to stock, followed closely by Noobbuilds and Pure Nexus - all excellent, but there are other good ROMs worth checking out too. I recommend Fire-ice kernel
Hmm, I'm having problems trying to install twrp on the nexus. I unlocked the bootloader, then flashed using fastboot flash recovery twrp.img but when I press power and volume up, I can't get to twrp, it keeps booting to the normal android bootloader.
Am I missing something? :/
Mephisto_POA said:
Hmm, I'm having problems trying to install twrp on the nexus. I unlocked the bootloader, then flashed using fastboot flash recovery twrp.img but when I press power and volume up, I can't get to twrp, it keeps booting to the normal android bootloader.
Am I missing something? :/
Click to expand...
Click to collapse
You have to reboot straight into recovery after installing, or it'll be overwritten
I just got myself a Nexus 9 – have been meaning to get one for a while to tinker with, and found one in mint condition for relatively cheap. Got it with stock 7.1.1, but it didn't feel as snappy as I'd hoped, so I flashed Lineage OS and that left me with the same feeling. I'm now running decrypted stock 7.1.1 with magisk for root, and it's pretty much as snappy as my OnePlus 3. Haven't tried any other ROMs decrypted, but I'm pretty sure the same applies. Lacking encryption hardware acceleration, the Nexus 9 just isn't meant for encryption.
To disable forced encryption in stock 7.1.1, I used xda user gladiac's FED-Patcher (should work for any ROM): https://forum.xda-developers.com/android/software-hacking/fix-fed-patcher-v8-forceencrypt-disable-t3234422
Choochter said:
You have to reboot straight into recovery after installing, or it'll be overwritten
Click to expand...
Click to collapse
yep, that was it, thanks!
olapel said:
I just got myself a Nexus 9 – have been meaning to get one for a while to tinker with, and found one in mint condition for relatively cheap. Got it with stock 7.1.1, but it didn't feel as snappy as I'd hoped, so I flashed Lineage OS and that left me with the same feeling. I'm now running decrypted stock 7.1.1 with magisk for root, and it's pretty much as snappy as my OnePlus 3. Haven't tried any other ROMs decrypted, but I'm pretty sure the same applies. Lacking encryption hardware acceleration, the Nexus 9 just isn't meant for encryption.
To disable forced encryption in stock 7.1.1, I used xda user gladiac's FED-Patcher (should work for any ROM): https://forum.xda-developers.com/android/software-hacking/fix-fed-patcher-v8-forceencrypt-disable-t3234422
Click to expand...
Click to collapse
But it says 7.1.1 is not supported?
somebody tell how to disable encryption on nougat 1 CM/linage roms. I used WUG toolkit to flash no-encrypt kernel and got twrp bootloop instead, unable to mount storage, system, data
Related
Hello!
I tried flashing my Nexus 9 for the first time today. I have done this before on other devices, just been a while since last!
I first tried Dirty Unicorns. I installed TWRP, wiped the device and installed the rom but when booting the device get stuck at the Google logo. How long "should" it stay there?
Same thing wehn tring AICP rom.
Between flashing these roms i went back to stock with Nexus Root Toolkit and it booted as normal, just about 10s-20s(?) at the Google logo..
What am i doing wrong??????
Thanks,
Eric
Did you unlock the bootloader?
Verstuurd vanaf mijn Nexus 9 met Tapatalk
Yes ofc! (can I install twrp without unlocking?)
I'm pretty sure It says unlocked in the boot menu.
It's those roms. They are based on a version of cyanogen that has a loooong boot problem. It takes about 7 or 8 minutes on the Google logo. Cyanogen has since fixed the issue, but those 2 roms have not.
Same thing happened to me, and I didn't try to flash a CM based, I tried Pure Nexus which is AOSP and it hung at the Google logo for a good 10 minutes before I decided to flash-all.bat back to stock, now I'm stock MM, not-encrypted, not rooted with TWRP recovery installed, stock is pretty good and haven't really feel the need to root, but that's no fix for the flash addicted type.
Erik
I'm not flash-addicted, I just want a smooth nexus 9. So much stutter, loading the keyboard etc in the original rom. I was hoping it would be better in dirty unicorns.
Sent from my Nexus 9 using Tapatalk
If you want smooth go with MM. Never realized how slow lolli was until I installed MM.
Sent from my Nexus 9 using Tapatalk
Does it help to go unencrypted? I dont know about you guys but its often my nexus 9 thinks several seconds before opening an app or the multitasking window or going to the homescreen...
I always go unencrypted when I can. When I encrypted my M7 for use of work apps and WiFi access. It made my phone more sluggish. I have no secrets on my tablet unless you count the porn? Lol. I always disable it.
Sent from my Nexus 9 using Tapatalk
So, I flashed the beta firmware 9.2.18 and it actually went well. I didn't wipe anything after the flash and I am currently using the Nitrogen OS ROM. Anyway, after I flashed the firmware, it encrypted my device. Is this normal behavior? I did check my TWRP to see that it still works, but the loading time is increased dramatically (like before, it loaded within 10 seconds. After the flash, it needs to load twice the amount of time).
To reiterate:
1. Is it normal behavior that the phone "encrypts" after flashing new beta firmware?
2. What does this encryption do exactly?
3. Is it normal for TWRP to load slower?
P.S. I also believe that I flashed the TWRP version with the working encryption or something. I can't really remember. -_-
BenParz said:
So, I flashed the beta firmware 9.2.18 and it actually went well. I didn't wipe anything after the flash and I am currently using the Nitrogen OS ROM. Anyway, after I flashed the firmware, it encrypted my device. Is this normal behavior? I did check my TWRP to see that it still works, but the loading time is increased dramatically (like before, it loaded within 10 seconds. After the flash, it needs to load twice the amount of time).
To reiterate:
1. Is it normal behavior that the phone "encrypts" after flashing new beta firmware?
2. What does this encryption do exactly?
3. Is it normal for TWRP to load slower?
P.S. I also believe that I flashed the TWRP version with the working encryption or something. I can't really remember. -_-
Click to expand...
Click to collapse
If you came from a custom ROM to the stock, whether beta or stable, it will encrypt your phone. It is normal.
Encryption relates to security and your phone is now more secure than before.
Because of the encryption, TWRP will load slower. This is also normal.
Hi,
last week I bought myself a Huawei P20 Lite as this one seems to be good comprise between size, speed and price and all together I find this device quite nice.
However I'm not a big fan of this ROMs, it's bloated and you have to confirm on each and everyhting, so I tried to reduce this dramatically and I began a long journey....
Unlock the bootloader
When I bought the device I wasn't aware about the issues that I may face (Downgrad, additional 4 Euro to spend) but OK, I thought it would be worth....
Installing Recovery
..but I couldn't be more wrong. It seems that there's no working TWRP for this device out there. I tried a lot, both on 8.0 and 9.1 but each time I tried to
wipe cache/dalvik the whole system got stucked and wasn't able to show the boot animation. So, assuming that there's really no working recovery out there, I continued to
directly flash different ROMs and try out my luck.
Rooting
This wasn't as hard as I though first, at least, as long as the ROM I've used had an advanced Reboot-Menu with the possibilty to boot to recovery, otherwise you end up somewhere in the desert and
may not be able to restart with boot.
The problem is, that this device required to patch the RECOVERY_RAMDISK partition, so in order to have Magisk booted, you required to use the Recovery. No big deal: just Power up
using VolUp and Power until the Huawei logo appears... normally.. It didnt work in more than 50% of the times...
Gapps (or Magisk)
OK, as I already indicated, I tried lots of them, but to be honest, none of them really convinced me (all was done on EMUI9.1 "AB" and not EMUI8 "A only")
GSI Phh Treble: nice, but this is one of thinks I did not checked in depth, as almost all (?) are based on this one...
OmniRom from OpenKirin: works perfectly out of the box, SafeteNet is working, Magisk can be installed, but no advanced boot menu and I find it a little bit overloaded...
MicroG ufOffical: I would go with it, everyhting worked, it's slim BUT I couldn't get my Banking-App working, not even after appliying multiple MagiskHide Prop-Settings...
Descendant: This one was by far my favorite... Really slim, advanced reboot-menu, but I couldn't flash Gapps. OK, so I tried MicroG: this can be installed using Magisk. After some trouble (e.g. you have to install DroidGuardHelper so that the OS recognizes an "Update") I got MicroG working, but I coulnd't get it with my Banking-App. In this ROM I couldn't even apply any MagiskProp Hide-Settings. Only Post-FS worked. OK, as I'Ve failed using this approach, I thought: maybe I can use Gapps with this image.... but as I stated at the beginning: I do not have any working Recovery.
So my questions:
Is there any working Recovery out there? TWRP 3.3.x supports to be flashed in RECOVERY_RAMDISK (and there's also offical support for P20 Pro) As of now I wouldn't even care about decrypted data, but at least be able to wipe and do a factory reset....
Or: Is it possible to install Gapps from a running (rooted) system?
Or: can I patch system.img with Gapps before flashing it to the phone?
But perfectly: did anyone get Descendant running with MagiskHideProp? Maybe even got MicroG running on it?
I'm currently out of ideas, did someone else had such a trouble with that device?
Best regards,
Peter
Well, yes. Kinda the same as you but I didn't try that many roms. I tried a fair bunch of twrp versions though. And I managed to use twrp to flash roms and if I remember well even do a dalvik/cache wipe with one of them - but I might be imagining that one. It is worth noting that you can actually use some twrp versions for other huawei devices on the p20 lite. Try at your own risk. There is a lot more development going on for the p8 lite (2017) for example. I tried the lineageos version that was posted herefor that device and it worked quite well.
Hey everyone,
I am very new to the OP7TP, comming from an HTC U11 which is.. old and very different.
Anyhow on to my problem:
When I got my new device I decided to get rooted, and then chose to use reseruction rom.
Which was a pretty nice experience, but I also wanted to see what else was being released, and Havoc came along.
I flashed Havoc according to the instructions on telegram, using fastbootd..
But when I went to boot it just kept rebooting to Bootloader mode
I restored my device using MSM, and triedagain, with the same result
But now, for the real trouble: reseruction rom does the same!
When flashing it, it will just reboot to bootloader every time.
It seems I can't flash custom roms anymore?
The stock OOS rom seems to be fastbootd and MSM flashable and boots without issue.
Has anyone encountered this before? any advice on how to proceed?
I am using the European OP7TP HD1913 with latest stable OOS 10.0.9 HD01BA
Solution:
Well I do feel silly now..
I flashed Reseruction Remix using my Desktop
Flashed Havoc (and all other attempts) using my notebook
And even tho I installed, which I thought were the correct fastboot drivers, evidently they are not..
When I tried flashing Havoc using my desktop it worked instantly..
It was just fastboot.. no errors during flashing, wiping, erasing and such... but it did something wrong..
Giblet-dono said:
Hey everyone,
I am very new to the OP7TP, comming from an HTC U11 which is.. old and very different.
Anyhow on to my problem:
When I got my new device I decided to get rooted, and then chose to use reseruction rom.
Which was a pretty nice experience, but I also wanted to see what else was being released, and Havoc came along.
I flashed Havoc according to the instructions on telegram, using fastbootd..
But when I went to boot it just kept rebooting to Bootloader mode
I restored my device using MSM, and triedagain, with the same result
But now, for the real trouble: reseruction rom does the same!
When flashing it, it will just reboot to bootloader every time.
It seems I can't flash custom roms anymore?
The stock OOS rom seems to be fastbootd and MSM flashable and boots without issue.
Has anyone encountered this before? any advice on how to proceed?
I am using the European OP7TP HD1913 with latest stable OOS 10.0.9 HD01BA
Solution:
Well I do feel silly now..
I flashed Reseruction Remix using my Desktop
Flashed Havoc (and all other attempts) using my notebook
And even tho I installed, which I thought were the correct fastboot drivers, evidently they are not..
When I tried flashing Havoc using my desktop it worked instantly..
It was just fastboot.. no errors during flashing, wiping, erasing and such... but it did something wrong..
Click to expand...
Click to collapse
Everytime I flashed havok I had to wipe data after flashing the ROM when it was in boitloop I held all buttons. Then went to recovery and wiped data then it booted fine
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