Problems installing Gapps on GSI Roms - Walmart Onn Tablets General

Problems installing Gapps on GSI Roms - Walmart Onn Tablets General

So currently I'm running AOSP Extended V6 on my 002. The rom itself runs great BUT I can't get Gapps to stick. Unlocked bootloader with TWRP 3.1.0. After I resize system Gapps will install and say Successful but when I clear cache and reboot I have no nothing installed. I'm new to this device so be easy if i'm missing something obvious.
EDIT: I've tried multiple version of Gapps from a few different places.

I have yet to have any GSI rom work, so I stopped trying and just ran a debloat script I wrote

It's weird how hit and miss GSI is on the exact same model. I may end up reverting back to stock and unlock/root and use your script and then just call it a day if I can't figure this out. I SO wanted AOSP Ext to work but kinda useless to me without Gapps.

razredge said:
It's weird how hit and miss GSI is on the exact same model. I may end up reverting back to stock and unlock/root and use your script and then just call it a day if I can't figure this out. I SO wanted AOSP Ext to work but kinda useless to me without Gapps.
Click to expand...
Click to collapse
I honestly even uninstalled gapps on my 10 inch because its one purpose is gonna be an in-car OBD II monitoring tablet with Torque Pro for my car.
GSI roms are so strange. I have 3 G7 Play's. 2 of them took the same GSI just fine, then the third just bricked and boot looped. I had to change the boot animation in TWRP to get it to boot. Even then, camera and bluetooth didn't work, but the other 2 were 100% functional. Reflashed quite a few times

razredge said:
It's weird how hit and miss GSI is on the exact same model. I may end up reverting back to stock and unlock/root and use your script and then just call it a day if I can't figure this out. I SO wanted AOSP Ext to work but kinda useless to me without Gapps.
Click to expand...
Click to collapse
I believe the hit and miss comes from the gsi's being developed on specific devices by different developers. They are supposed to work on any project treble enabled devices but it's just not so. This is just my thought from trying almost all available and a lot of time reading. The whole idea has slowly began a full circle movement to custom gsi's. The oxymoron of that last sentence kind of sums it up from my experience. Custom generics are what are being produced for the most part. If one looks at the different maintainers threads they will see what device it is supposed to work on. A.O.S.P should work a little better than most and the builds I have tried from ci.android.com have worked really well. Personally didn't see much point in the stock android gsi over debloated stock in this case. Much simpler to maintain device integrity by debloating the very few unwanted apps. All that said I am still running Beast ROM as I actually like it, the only issue I know of is device theme(takes forever+know-how) and I don't use gapps. So it works great on my tablet and I am not sure what options I will have in the future. All the changes have me sitting with a tablet that if flashed back to stock will not take ota's and a serial# of 0123456789ABCDEF. Happy Modding.
Don't know if you've seen them but there are a couple gsi's that have gapps installed with no other options, can't remember which they were, but may work better.

I appreciate the info and insight you always give. My 002 I actually went back to stock and just rooted and debloated it. I wanted it to be stable since it's my couch tablet lol. I picked up a 007 on Black Friday just for the hell of it. I'm gonna play with it and experience some different roms. BTW, they changed the model numbers on them. It's not with me right now but the model number is all numbers now. Looks more like the serial number.
Sent from my Pixel 2 using Tapatalk

razredge said:
I appreciate the info and insight you always give. My 002 I actually went back to stock and just rooted and debloated it. I wanted it to be stable since it's my couch tablet lol. I picked up a 007 on Black Friday just for the hell of it. I'm gonna play with it and experience some different roms. BTW, they changed the model numbers on them. It's not with me right now but the model number is all numbers now. Looks more like the serial number.
Click to expand...
Click to collapse
The model number I remember for the 8" was ONA19TB002 and 10" was ONA19TB003 and 007 was kboard model. Did they change to something other than that ? I remember a different number when looking at fccid page but it seemed shorter. When it's nearby give update if you don't mind, I'm curious it may help in search for firmware.

The new model number is 100005209. I took the back off of the new one and my old one and they are identical with the same part numbers. They're also all branded Surf now.
Sent from my Pixel 2 using Tapatalk

I am venturing to flash ohh aosp -10 v107.
Needed to flash the vanilla version, because the gapps version was too big.
All I get is stuck at the onn splash screen.
Do I need to flash anything to vbmeta to get this to boot a gsi?
Update:
Self test result
Yes. Even after unlocking bootloader, still need to flash vbmeta with --disable-verification before you can boot gsi.
Then there is a setprop that is needed to get the gsi to boot
While device is stuck on the"Android" logo bootanimation from aosp. Enter commands into ad shell.
Code:
adb shell setprop debug.stagefright.ccodec 0
This will get tablet to boot. But the setprop (which should become persistent) does not remain after a reboot. So the line needs to be added to the boot script built into phh gsi. "rw-sysyem.sh"
Code:
adb shell
su
mount -o rw,remount /
echo "setprop debug.stagefright.ccodec 0" >> /system/bin/rw-system.sh
These steps worked for me. And should work for you. But as with any modifications to your device , by you , are your responsibility to confirm are done correctly.

The main problem I've been having has not been with the ROM itself. I had a few vanillas that after resizing and installing GAPPS the actual apps don't show up. I'd go back into TWRP and reflash the GAPPS and it would respond with a success after seeing all the apps install but after a reboot none was there.

razredge said:
The main problem I've been having has not been with the ROM itself. I had a few vanillas that after resizing and installing GAPPS the actual apps don't show up. I'd go back into TWRP and reflash the GAPPS and it would respond with a success after seeing all the apps install but after a reboot none was there.
Click to expand...
Click to collapse
I just had that with gapps install I was trying. And in recovery after the gapps flash, before reboot I looked around with twrp file manager. I see all the apps installed. But they are not in the correct location.
They are getting installed in the /system-root/app folder rather than the /system-root/system/app folder.
I don't know the fix yet. I mentioned it in the twrp thread and diplomatic has said he does not know why it didn't go as it was supposed to .

mrmazak said:
I just had that with gapps install I was trying. And in recovery after the gapps flash, before reboot I looked around with twrp file manager. I see all the apps installed. But they are not in the correct location.
They are getting installed in the /system-root/app folder rather than the /system-root/system/app folder.
I don't know the fix yet. I mentioned it in the twrp thread and diplomatic has said he does not know why it didn't go as it was supposed to .
Click to expand...
Click to collapse
Interesting.... I'll have to keep an eye on that. I didn't even pay attention where they installed to. Thanks for the heads up!

mrmazak said:
I just had that with gapps install I was trying. And in recovery after the gapps flash, before reboot I looked around with twrp file manager. I see all the apps installed. But they are not in the correct location.
They are getting installed in the /system-root/app folder rather than the /system-root/system/app folder.
I don't know the fix yet. I mentioned it in the twrp thread and diplomatic has said he does not know why it didn't go as it was supposed to .
Click to expand...
Click to collapse
Are you sure that is not correct? Because I just checked on my Onn 8 with the stock rom and they are in /system/app/.
There system privileged apps in: /system/priv-app. Updates are in /data/app, I believe.

Has anyone had success in installing opengapps on one of these tablets? Also, has anyone tried installing it with System mounted in TWRP? Even if it doesn't work in TWRP, I believe the install script supports running on Android too.

How has anyone been able to flash a gsi. Ive even tried disabling avb but cant get it to boot. After reboot twrp dosent even recognize an os installed
Sent from my SM-G975U1 using XDA Labs

diplomatic said:
Has anyone had success in installing opengapps on one of these tablets? Also, has anyone tried installing it with System mounted in TWRP? Even if it doesn't work in TWRP, I believe the install script supports running on Android too.
Click to expand...
Click to collapse
I haven't so far. I'll try with mounting system and post the results.

razredge said:
I haven't so far. I'll try with mounting system and post the results.
Click to expand...
Click to collapse
Fast forward 20 days... any progress?

diplomatic said:
Fast forward 20 days... any progress?
Click to expand...
Click to collapse
Woops.... No it still doesn't work. Actually it made one of my 8's bootloop after.

I found this solution in another thread:
- Format data partition and reboot recovery.
- Open terminal in twrp without system, data, and cache mounted.
- Enter the following commands:
e2fsck -y /dev/block/by-name/system
e2fsck -f /dev/block/by-name/system
resize2fs /dev/block/by-name/system
- Then reboot twrp
- Flash system img reboot recovery
- After that flash pico gapps without system mounted
Thats how i was able to successfully flash gapps on aosp phh 10. You may need to try a couple times but it should work.
Sent from my SM-G975U1 using XDA Labs

jwarrior319 said:
I found this solution in another thread:
- Format data partition and reboot recovery.
- Open terminal in twrp without system, data, and cache mounted.
- Enter the following commands:
e2fsck -y /dev/block/by-name/system
e2fsck -f /dev/block/by-name/system
resize2fs /dev/block/by-name/system
- Then reboot twrp
- Flash system img reboot recovery
- After that flash pico gapps without system mounted
Thats how i was able to successfully flash gapps on aosp phh 10. You may need to try a couple times but it should work.
Click to expand...
Click to collapse
So you got phh 10 to boot? How does it run any major bugs? Thanks

Related

Download KitKat CM11 4.4.2 for Nook HD+ Here

Time to get the Nook HD+ rolling on Kitkat! XDA forum member succulent (aka Iamafanof) has given me permission to post a link to his blog with all the necessary info that you need, plus the all important links to download his CM11 4.4.2 roms.
I had previously been running his CM 10.2 builds with sgt7 and they were great. Now, been running his CM11 builds since 12/16 and they are very functional and run extremely well.
It is highly recommended that you read over his blog to get the info you need to properly flash it. It's likely that your current recovery, be it CWM or TWRP will be unable to flash 4.4. You can try and if it fails, download the zip recoveries for either CWM 6.0.4.5.x or TWRP 2.6.3.0 on succulent's website listed below. Succulent recommends CWM but I've had great success with both of them. If you have a problem flashing the recovery zip, extract the image file from the zip and flash either through ADB or the PS app flashify from within your OS. EDIT: You do need to update your recovery to one of the above-mentioned recoveries.
Note: succulent's 4.4 builds are scripted to automatically install CWM 6.0.4.5b when installing the rom. But, the catch-22 is that you need to already have CWM 6.0.4.5.x or TWRP 2.6.3.0 to install 4.4 roms. EDIT 01/14/14: Currently, succulent's builds are now scripted to automatically install TWRP 2.6.3.0 instead of CWM 6.0.4.5b.
New TWRP 2.6.3.0 and CWM 6.0.4.5.x recoveries: http://goo.im/devs/succulent/ovation/recovery If you choose CWM, 6.0.4.5b is preferred as it supports both internal and ext sdcard.
Needless to say, make a nandoid backup before proceeding and if you're not comfortable doing this...DON'T!
Link to succulent's blogsite with download links: http://iamafanof.wordpress.com/2013/12/20/cm11-0-kitkat-android-4-4-2-for-nook-hd-xx-20dec2013/
Note: There are two different builds, one for internal (eMMc) and one for sdcard, be sure to download and install the correct one. I am using the eMMc build,so I don't have any knowledge of how the sdcard build is working.
Additional link to succulent's rom builds on Goo: http://goo.im/devs/succulent/ovation/cyanogenmod/internal
On the Goo site, he also has his CM 10.2 builds that might be of interest to some of you. Note: His CM10.2 rom builds automatically install TWRP 2.6.3.0.
You must use KitKat 4.4 gapps. A gapps link is provided on succulent's blog site. Either use those gapps or the PA zero day gapps linked below. If you are going to use ART, it's recommended that you do use the PA zero day gapps for best compatibility. If you don't know what ART runtime is, google it!
All credit for the rom builds, as well as the new recovery images goes to succulent (aka Iamafanof). I am just spreading the news so we can all finally have KitKat on our devices.
EDIT: Just a reminder regarding the newer recoveries, CWM 6.0.4.5.x and TWRP 2.6.3.0, they are in flashable zip form on succulent's blogsite linked above. If you run into a problem flashing the zip, one of the simplest ways to get the job done is with Flashify. Just unzip the recovery zip to get the image file. Put the image file on your device and flash it with Flashify. Play Store link: https://play.google.com/store/apps/details?id=com.cgollner.flashify
Regarding ART runtime: Since it's still "experimental", YMMV with the results you get. Google may decide ART isn't feasible and dump it going forward.
Note: Not all gapps packages are ART compatible, at this time it is probably best to use the Paranoid Android zero day gapps. Link for PA gapps: http://forum.xda-developers.com/showthread.php?t=2397942 Be sure to choose the current 4.4 gapps.
With ART runtime, it is generally better to initiate it on a fresh rom install and before you install all of your user apps. Btw, it's normal for it to take a long time to initialize on the first reboot. , I found that it generally takes a while to "settle in" and should become more fluid/speedier over time.
Always be sure to have a nandroid backup so you can easily go back to dalvik if ART isn't your thing.
One last thing about ART, Xposed Framework does not yet support it. It will appear to work but it does not. Matter of fact, with Xposed installed on your device, it will revert ART runtime back to Dalvik. Since I love using Xposed, this has kept me from using ART except to test it.
EDIT: Hey guys, just posting as new stuff comes up. Here's another possible alternative for those that may have a problem with either of the internal recoveries. XDA member sandsofmyst has put together a bootable TWRP 2.6.3.0 sdcard installer. If you use it, please post your results here and don't forget to give sandsofmyst a thanks click.
http://forum.xda-developers.com/showthread.php?p=48549135#post48549135
Enjoy!
Mike T

I'm in my kitkat glory right now. happy, happy, joy, joy.
Makes sure to update CWM BEFORE flashing CM11. Trust me, I lost 30 minutes trying to ungoober my Nook HD+.

supergroverthm said:
I'm in my kitkat glory right now. happy, happy, joy, joy.
Makes sure to update CWM BEFORE flashing CM11. Trust me, I lost 30 minutes trying to ungoober my Nook HD+.
Click to expand...
Click to collapse
Good tip and we always learn by trying. :laugh: I already had TWRP 2.6.3.0 from a previous rom, so my install of 4.4 was quick and painless. LOL
If you haven't already, hook this baby up with Xposed module by rovo89. Some really cool extra features without bogging things down with stuff you don't want or need.
Mike T

Oohh, I'm very very interested in this. Kept saying about memory optimizations for lower end device, have you noticed much performance differences? Pretty stable? Bluetooth, hdmi and everything work?
Sent from my HTC One using Tapatalk

Wow. Just wow
So now that you built it, can we expect it to become an official release soonish?
Thanks a lot for your work!

Hi, I just bought two nook hd+ one for me and one for my parents as a christmas present.
Beautiful devices, the only problem is that it does not provide italian as interface language,also all the appdownloaded from the play store are in english and I can't find a way to change that. My parents reallyneed the italian language sadly they don'tspeak a word of english....
So now I'm here wondering if this cyanogenmods have the italian language.
Saluti
Luca

superanima said:
Hi, I just bought two nook hd+ one for me and one for my parents as a christmas present.
Beautiful devices, the only problem is that it does not provide italian as interface language,also all the appdownloaded from the play store are in english and I can't find a way to change that. My parents reallyneed the italian language sadly they don'tspeak a word of english....
So now I'm here wondering if this cyanogenmods have the italian language.
Saluti
Luca
Click to expand...
Click to collapse
Well, I looked in the Language+input section under settings and Italiano (Italia) and Italiano (Svizzera) are in there. I was able to switch to them and then...not be able to read anything so I'm assuming it's right. haha. Going into the Play Store all of the app names are still english but their descriptions changed so, it seems like it mostly works. I believe language support is an app-to-app basis though, so if the app developer didn't include Italian tranlations then it's going to be in English or whatever native language the App is in. I'm not totally sure how the language support works. Maybe someone else with more info can fill in my blanks.
On to this ROM as a whole, I've been playing with it, coming from CarbonRom 10.2 and haven't noticed much difference but I dig it none-the-less. I've tested Bluetooth headphones and my HDMI adapter and both work just fine. If anyone is wanting me to test anything let me know.

Have you enabled ART?
Sent from my GT-N7105 using XDA Premium 4 mobile app

aedgington said:
Have you enabled ART?
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Going into Settings>Dev Options and changing the runtime to ART and then rebooting...it doesn't get stuck in a bootloop, but going back into the Dev options shows that the Runtime option is still Dalvik and not ART so... I don't think that is there yet.

Wow, I have 342mb RAM Aavailable with GAPPS installed according to cool tool!
I've enabled ART and its showing on dev options. What's the deal with this new method? Is it better, faster, etc?

felacio said:
Going into Settings>Dev Options and changing the runtime to ART and then rebooting...it doesn't get stuck in a bootloop, but going back into the Dev options shows that the Runtime option is still Dalvik and not ART so... I don't think that is there yet.
Click to expand...
Click to collapse
Awesome, thanks for checking. I think that may be where we'll see some performance increase, but if it's not implemented yet, there's no rush for me to install

aedgington said:
Awesome, thanks for checking. I think that may be where we'll see some performance increase, but if it's not implemented yet, there's no rush for me to install
Click to expand...
Click to collapse
Mine is showing ART in dev option after reboot...

supergroverthm said:
Mine is showing ART in dev option after reboot...
Click to expand...
Click to collapse
Have you noticed any difference between ART and Dalvik?

aedgington;4872557[LEFT said:
[/LEFT]0]Have you noticed any difference between ART and Dalvik?
Click to expand...
Click to collapse
Only that more RAM is available. Now showing 390mb RAM available.

Flashing CWM
Sorry for the bit of a newb question, but how are you getting the CWM update in there? My prior ROM flashing, I had just used the bootable SD card image that verygreen had setup. I don't know how to update the version of CWM on that image currently.
When I put CWM on my phone, I had used fastboot to install it, but I can't get fastboot to recognize my nook for some reason (adb works fine). Did you use this method (from cwm site)?:
EDIT: This doesn't work... flash_image seems to be scanning for some partition that's not available:
"error scanning partitions: No such file or directory"
Code:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img

Nook HD Kitkat
chili81 said:
Sorry for the bit of a newb question, but how are you getting the CWM update in there? My prior ROM flashing, I had just used the bootable SD card image that verygreen had setup. I don't know how to update the version of CWM on that image currently.
When I put CWM on my phone, I had used fastboot to install it, but I can't get fastboot to recognize my nook for some reason (adb works fine). Did you use this method (from cwm site)?:
Code:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
I placed the files on my internal SDCard/Download and TWRP could see them and I installed.
Went here to get the zip file http://www.mediafire.com/download/c32pw4qf1l9a0mu/flash_recovery_TWRP_2.6.3.0_internal.zip
After installing the new TWRP and reboot I reset the old ROM then installed the new ROM and GAPPS.
norm883

That did the trick, thanks... I was thinking the older CWM would have same problem updating to newer CWM as it would KitKat.

Flashed TWRP 2.6.3, rebooted then tried to install 4.4 and got a mount/data1 error.
I'll guess I'll try with the new CWM.
Does anyone know if the new CWM can read and restore TWRP back-ups?
EDIT: rebooted then booted back into TWRP 2.6.3.
So far so good, flashing GAPPS now.
All good.

Decided to put some extra notes here for those that only read the last page. Also put this in the OP.
Just a reminder regarding the newer recoveries, CWM 6.0.4.5 and TWRP 2.6.3.0, they are in flashable zip form on succulent's blogsite linked above. You should be reading his blog info anyway, so just scroll untill you see the links for those recoveries. If you run into a problem flashing the zip, one of the simplest ways to get the job done is with Flashify. Just unzip the recovery zip to get the image file. Put the image file on your device and flash it with Flashify right from within you current OS, ie; CM10.2 etc.
Regarding ART runtime: Since it's still "experimental", YMMV with the results you get. Also, Google may decide ART isn't feasible and dump it going forward.
A couple of things to note, not all gapps packages are ART compatible, the gapps I linked from 1209 do work, I'm not sure about the ones linked on succulent's blogsite from 1208. I believe the PA zero day gapps are also ART compatible.
With ART runtime, it is generally better to initiate it on a fresh rom install and before you install all of your user apps. Btw, it's normal for it to take a long time to initialize on the first reboot. I found that it generally takes a while to "settle in" and should become more fluid/speedier overtime.
Always be sure to have a nandroid backup so you can easily go back to dalvik if ART isn't your thing.
One last thing about ART, Xposed Framework does not yet support it. It will appear to work but it does not. Matter of fact, with Xposed installed on your device, it will revert ART runtime back to Dalvik. Since I love using Xposed, this has kept me from using ART except to test it.
Mike T

FirePsych said:
Flashed TWRP 2.6.3, rebooted then tried to install 4.4 and got a mount/data1 error.
I'll guess I'll try with the new CWM.
Does anyone know if the new CWM can read and restore TWRP back-ups?
EDIT: rebooted then booted back into TWRP 2.6.3.
So far so good, flashing GAPPS now.
All good.
Click to expand...
Click to collapse
CWM and TWRP backups are not compatible, probably never will be unless some third party dev figures something out.
Mike T

[DISCUSSION] Remix OS 3.0 Out for Pixel C!

Title says it all. Post your experiences!

Here are the download links and the tutorial on how to flash:
Pixel C: http://www.jide.com/remixos/devices/pixelc
Nexus 9: http://www.jide.com/remixos/devices/nexus9
Tutorial on how to flash onto your device:
https://jide.zendesk.com/knowledge/articles/224316468/en-us?brand_id=449827
Thanks!

Aaand... up and running!
I came from Nougat DP5. At first, I removed the -w flag from the update script to keep my apps, but as usual this was not a good idea as the Play Store kept on force closing. After a clean flash everything worked as expected. I paired the Pixel C keyboard and a BT mouse.
The apps I use the most on my Pixel C are Firefox Beta and Kodi.
- Firefox crashes as often as it does on the Nougat Previews when it is put into windowed mode. As this got better with new Firefox and Nougat Versions, I am confident that this will improve further.
- Kodi starts in windowed mode and can be used as normal. This is a first for me as Kodi could not be windowed on stock Android N!
Unfortunately, it lacks the top bar so it can not be resized. Are there any keyboard shortcuts for maximizing/minimizing windows?
Overall, I can only recommend giving Remix OS a try on the Pixel C!
(Written on the Pixel C with Remix 3.0!)

Can we get a video of your experience?
Mustkeg said:
Aaand... up and running!
I came from Nougat DP5. At first, I removed the -w flag from the update script to keep my apps, but as usual this was not a good idea as the Play Store kept on force closing. After a clean flash everything worked as expected. I paired the Pixel C keyboard and a BT mouse.
The apps I use the most on my Pixel C are Firefox Beta and Kodi.
- Firefox crashes as often as it does on the Nougat Previews when it is put into windowed mode. As this got better with new Firefox and Nougat Versions, I am confident that this will improve further.
- Kodi starts in windowed mode and can be used as normal. This is a first for me as Kodi could not be windowed on stock Android N!
Unfortunately, it lacks the top bar so it can not be resized. Are there any keyboard shortcuts for maximizing/minimizing windows?
Overall, I can only recommend giving Remix OS a try on the Pixel C!
(Written on the Pixel C with Remix 3.0!)
Click to expand...
Click to collapse

went to give this a try and totally forgot about the 30sec delay.....ugh
Okay first thoughts It's actually very solid for a first build but the main reason i'm rolling back and this may just be me but I hate having all the icons on the desktop....unless there's something i'm missing to get rid of them and have a clean desktop?

Been running Remix for the afternoon, everything works flawlessly so far including all of my usual apps. Very smooth and stable! I plan on running this as my daily driver for a while, so if anyone has any questions about my experience with Remix OS, feel free to ask. Also, if anyone can get it rooted, I'd love to hear from you Couldn't get it to boot using the modified stock kernel and had to reflash. TWRP installs with no problems, though!

esthornhill said:
Been running Remix for the afternoon, everything works flawlessly so far including all of my usual apps. Very smooth and stable! I plan on running this as my daily driver for a while, so if anyone has any questions about my experience with Remix OS, feel free to ask. Also, if anyone can get it rooted, I'd love to hear from you Couldn't get it to boot using the modified stock kernel and had to reflash. TWRP installs with no problems, though!
Click to expand...
Click to collapse
I flashed UPDATE-SuperSU-v2.76-20160630161323.zip via TWRP. Rooted without problems.
I did not try changing kernels.
---------- Post added at 07:35 AM ---------- Previous post was at 07:18 AM ----------
Roxas598 said:
went to give this a try and totally forgot about the 30sec delay.....ugh
Okay first thoughts It's actually very solid for a first build but the main reason i'm rolling back and this may just be me but I hate having all the icons on the desktop....unless there's something i'm missing to get rid of them and have a clean desktop?
Click to expand...
Click to collapse
You can change the default launcher, but you need root for this.
1. Install a 3rd party launcher. I use Nova Launcher.
2. Open a terminal emulator.
3. Type "su".
4. Type "pm disable com.android.launcher3".
To re-enable the default launcher, type "pm enable com.android.launcher3" (didn't try this).

can anyone make a video showing Remix OS 3.0 on Pixel C for other users who would like to see how it performs.

esthornhill said:
Been running Remix for the afternoon, everything works flawlessly so far including all of my usual apps. Very smooth and stable! I plan on running this as my daily driver for a while, so if anyone has any questions about my experience with Remix OS, feel free to ask. Also, if anyone can get it rooted, I'd love to hear from you Couldn't get it to boot using the modified stock kernel and had to reflash. TWRP installs with no problems, though!
Click to expand...
Click to collapse
I need help flashing it. I keep getting an error.

@TAINA333 Are you flashing it via ADB? What kind of error are you getting?

TAINA333 said:
I need help flashing it. I keep getting an error.
Click to expand...
Click to collapse
I had an issue using the flash-all.sh as well. I just flashed each partition manually. If you're using Linux, make sure you're running fastboot as root.

It's ok but not something I'd use long term. I flashed it, played around for about five minutes and went back to stock. Too many annoyances such as huge padding on the left and right of the desktop (wasted space drives me nuts), can't remove icons from the desktop or move items from the menu to the desktop which is annoying. It might be good for beginners but not something I'd be interested in using. I'll wait for someone to get Chrome OS on this thing.

cmscritic said:
It's ok but not something I'd use long term. I flashed it, played around for about five minutes and went back to stock. Too many annoyances such as huge padding on the left and right of the desktop (wasted space drives me nuts), can't remove icons from the desktop or move items from the menu to the desktop which is annoying. It might be good for beginners but not something I'd be interested in using. I'll wait for someone to get Chrome OS on this thing.
Click to expand...
Click to collapse
Replace the launcher as I described above. But otherwise I feel the same. Freeform windows are the only plus compared to Nougat.

Yes I am flashing thru adb. At first it was telling me something about the zip file. Then I restarted all over and when I used flash.bat it said it was missing some files, but the files are there.

TAINA333 said:
Yes I am flashing thru adb. At first it was telling me something about the zip file. Then I restarted all over and when I used flash.bat it said it was missing some files, but the files are there.
Click to expand...
Click to collapse
Yeah, using the flash all scripts rarely works for me either. I had to unzip "images-aosp_dragon...," move all the .img files into the root of my platform-tools folder and flash the images manually. I had previously formatted the device, and with the device in fastboot mode I then flashed the files with the following commands:
fastboot flash bootloader bootloader-dragon-google_smaug.7132.295.0.img
adb reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
fastboot reboot
After this it booted up and everything worked perfectly!

Mustkeg said:
I flashed UPDATE-SuperSU-v2.76-20160630161323.zip via TWRP. Rooted without problems.
I did not try changing kernels.
---------- Post added at 07:35 AM ---------- Previous post was at 07:18 AM ----------
You can change the default launcher, but you need root for this.
1. Install a 3rd party launcher. I use Nova Launcher.
2. Open a terminal emulator.
3. Type "su".
4. Type "pm disable com.android.launcher3".
To re-enable the default launcher, type "pm enable com.android.launcher3" (didn't try this).
Click to expand...
Click to collapse
Which recovery did you use? I can't even get that far, I install remixOS, flash over TWRP via fastboot, that installs just fine but the OS refuses to boot after that.... Just reboots back into recovery
EDIT: Nevermind, I got it. Not sure what I was doing wrong earlier, but yeah flashing TWRP, pushing SU2.76 and installing it works just fine. Thanks!

esthornhill said:
Yeah, using the flash all scripts rarely works for me either. I had to unzip "images-aosp_dragon...," move all the .img files into the root of my platform-tools folder and flash the images manually. I had previously formatted the device, and with the device in fastboot mode I then flashed the files with the following commands:
fastboot flash bootloader bootloader-dragon-google_smaug.7132.295.0.img
adb reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
fastboot reboot
After this it booted up and everything worked perfectly!
Click to expand...
Click to collapse
So I did everything you said, it looked like it was going to boot up just fine, it said android apps starting and then it bootlooped.

TAINA333 said:
So I did everything you said, it looked like it was going to boot up just fine, it said android apps starting and then it bootlooped.
Click to expand...
Click to collapse
Sorry to hear that! Were you doing a clean install or writing Remix over your existing OS? I would also recommend redownloading the files before you try again to make sure that their being corrupted is not an issue.

esthornhill said:
Sorry to hear that! Were you doing a clean install or writing Remix over your existing OS? I would also recommend redownloading the files before you try again to make sure that their being corrupted is not an issue.
Click to expand...
Click to collapse
Clean but I'll reinstall just in case.

What is the best way to change the screen resolution DPI on my Pixel C while running Remix OS 3.0 ? any suggestion guys ?
did you guys flash TWRP_dragon_3.0.2-21.img ??
http://forum.xda-developers.com/pixel-c/development/twrp-3-0-2-0v16-t3400503
any cool Apps and Kernel suggestion to install while running Remix OS 3.0 on Pixel C please ??

[REQ] ZIP to install TWRP to ramdisk

Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!

starcms said:
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
Click to expand...
Click to collapse
It's definitely possible but I don't know how many Devs would want to take this up. I'm all for the idea, I really miss having TWRP permanently, but you kinda get used to the whole PC flashing thang.
I don't know how different the Pixel 2 is in comparison to the Essential phone, but they both share A/B partitions, so it wouldn't be too outlandish if someone were able to port something like this over to our Mata's down the road.
?

starcms said:
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
Click to expand...
Click to collapse
MoistPicklez said:
It's definitely possible but I don't know how many Devs would want to take this up. I'm all for the idea, I really miss having TWRP permanently, but you kinda get used to the whole PC flashing thang.
I don't know how different the Pixel 2 is in comparison to the Essential phone, but they both share A/B partitions, so it wouldn't be too outlandish if someone were able to port something like this over to our Mata's down the road.
?
Click to expand...
Click to collapse
The problem lies in the way our touch driver is implemented. For lack of a better explanation, what good would it do to need to carry a type c mouse around to use twrp if touch doesn't work. Many many people have tried and failed getting touch to work on Oreo source, let alone P. That is why twrp resides on a nougat kernel meant for LOS. Someone I know even rewrote the driver in c, no go. It's gonna be tough sledding.

Does it have to be touch though? Could it be more old school clockworkmod recovery where you use the buttons or really like default recovery. I don't know enough about it but just a thought. You definitely get use to just downloading and flashing in twrp and it would be cool to find that with the PH-1.

Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.

Gundabolu SC said:
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Click to expand...
Click to collapse
Been waiting for someone to share this for 6 months.. thanks lol

aer0zer0 said:
The problem lies in the way our touch driver is implemented. For lack of a better explanation, what good would it do to need to carry a type c mouse around to use twrp if touch doesn't work. Many many people have tried and failed getting touch to work on Oreo source, let alone P. That is why twrp resides on a nougat kernel meant for LOS. Someone I know even rewrote the driver in c, no go. It's gonna be tough sledding.
Click to expand...
Click to collapse
Thanks for the explanation. Now I understand why it hasn't been done before.
But why the issue with touch in TWRP with an Oreo kernel in the first place? What's so special/different/difficult about the touch driver that the Essential uses? And why does it work fine with TWRP with a Nougat kernel? No other devices (to my knowledge) have this issue.
Edit: I wonder if since TWRP worked with the touch driver from the Nougat kernel, if it could work with the P kernel? Maybe whatever was changed in Oreo that prevented it from working has been fixed?

starcms said:
Thanks for the explanation. Now I understand why it hasn't been done before.
But why the issue with touch in TWRP with an Oreo kernel in the first place? What's so special/different/difficult about the touch driver that the Essential uses? And why does it work fine with TWRP with a Nougat kernel? No other devices (to my knowledge) have this issue.
Click to expand...
Click to collapse
Hbtp_daemon (touchscreen) doesn't work in twrp on 8.x and newer sources.
Hbtp_daemon runs in userspace iirc, which is the problem. So an entire driver needs to be hogged together in order to get twrp to work. same process that worked on N doesn't work now.

aer0zer0 said:
Hbtp_daemon (touchscreen) doesn't work in twrp on 8.x and newer sources.
Hbtp_daemon runs in userspace iirc, which is the problem. So an entire driver needs to be hogged together in order to get twrp to work. same process that worked on N doesn't work now.
Click to expand...
Click to collapse
Not possible to use the driver in userspace after TWRP decrypts the device (userspace) using the default password (after any patterns or pins are removed from the lockscreen)?
Edit: And what the heck is the driver doing in userspace anyway? Shouldn't it be in /vendor? If the driver is in userspace, then how can the touchscreen work after a factory reset?

The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.

galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
It doesn't after you lets say flash magisk and gapps they create a script in /system/addon....and when updatting lineage it runs the scripts in the addon folder which is how gapps and magisk get installed to the new updated system and boot.....first magisk and gapps have to be flashed in twrp....after that u shudnt need it on dirty flashes

galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
@aer0zer0
This seems like the easiest solution to getting TWRP working on the Oreo and P boot images and being able to keep it permanently installed in ramdisk. Make TWRP use the volume up/down keys for scrolling and the power key to select. If the touchscreen is soooo difficult to get working, forget it. If someone really wants to use the touchscreen, they can use the existing TWRP version built on the Nougat boot image.

galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
What can you do in Lineage recovery if you can't flash zips? Can you make backups? What else can you do? If you have it installed, could you attach a pic (assuming you have another phone/camera)?

Has anyone looked in the stock P kernel? I was poking around and noticed some twrp residual files. This was straight from the images zip from essential. I didn't touch it.Wth are they in there for? Could they have a better twrp on the back burner for kernel development purposes for Essential? It was in the ramdisk, ill look again tomorrow when I unpack the boot.img. it would make sense to have it in ramdisk, pixel 2 has it like that. Ill post screenshots after work. But, the conversation looks good folks, you are on to something. We could always bust out some phillz recovery, or clockwork mod.

starcms said:
What can you do in Lineage recovery if you can't flash zips? Can you make backups? What else can you do? If you have it installed, could you attach a pic (assuming you have another phone/camera)?
Click to expand...
Click to collapse
I would say it is more stock-ish as far as recoverys go. It's a stock LOS recovery. You can factory reset, flash or sideload update.zips or signed zips no regular custom ROM zips or magisk. It is meant to run on LOS, it only runs on LOS actually and not made for the flashaholics out there. It's a good start though.
Sorry, out right now and no other phone/camera handy.

Gundabolu SC said:
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Click to expand...
Click to collapse
Just wanted to mention this works perfectly, tried it last night was able to get into TWRP and then back into my P Beta 3 with root, no issues. Thanks for this!

One could also theoretically copy a copy of the twrp boot. Img to the ex kernel manager backup file, and while booted into the system, hit restore kernel and since its in the boot partition it will flash it then reboot into recovery. Then from there flash your normal kernel and boot back to system/android.. i backup all my kernels after rooting them so after flashing otas, i can just flash my prerooted kernel and reboot without having to flash magisk
Edit. This works, i just did it, but u must make it reboot to bootloader to then tell it to reboot recovery. I dont know if flashify is the same

MoistPicklez said:
Just wanted to mention this works perfectly, tried it last night was able to get into TWRP and then back into my P Beta 3 with root, no issues. Thanks for this!
Click to expand...
Click to collapse
Hey, I'm just curious, before I try it, anyway when using flashify and selecting flash zip - does a recovery other than stock need to be present?

dirtyreturn said:
Hey, I'm just curious, before I try it, anyway when using flashify and selecting flash zip - does a recovery other than stock need to be present?
Click to expand...
Click to collapse
Not sure what you mean by that but to be honest all I did was take the TWRP11.img, and flashed it to boot (kernel) using Rashr, Flashify didn't load up oddly, then reboot to bootloader, select Recovery and bam, there was TWRP. Then to get back I just flashed my boot.img, and Magisk and all my modules and everything were all good to go. No issues at all. ?
Edit: as long as you have TWRP.img, your boot.img, and Magisk, you can easily get to TWRP and back, just make sure you have the img's you need and boom we all got TWRP on the fly.
Wish I had tried this sooner.

MoistPicklez said:
Not sure what you mean by that but to be honest all I did was take the TWRP11.img, and flashed it to boot (kernel) using Rashr, Flashify didn't load up oddly, then reboot to bootloader, select Recovery and bam, there was TWRP. Then to get back I just flashed my boot.img, and Magisk and all my modules and everything were all good to go. No issues at all. ?
Edit: as long as you have TWRP.img, your boot.img, and Magisk, you can easily get to TWRP and back, just make sure you have the img's you need and boom we all got TWRP on the fly.
Wish I had tried this sooner.
Click to expand...
Click to collapse
Hey, Rashr doesn't support this device(phone). I get a reboot to recovery option and if I tap cancel the app just closes. Did the app identify what it needed to?
In Flashify there are 3 options ,Flash - kernel,boot, and zip. What I'm curious about is , when choosing just the zip option - would twrp first need to be flashed to the boot partition?

I keep loosing root after reboot, Pls help.

Hey guys,
first time posting here so i dont kow how to style the text, so sorry about that.
last time i rooted a phone was on my sony xperia sp , where all i had to do was to go to towelroot .com and click to root.
I tryed to root my OP6T yesterday, after some setbacks i managed to sucessfully do it.
I did it like this:
1. Downloaded full ROM of OOS 10.3.2,
2. copied the payload to a program called payload dumper that extracted the boot image.
3. Copied the boot image to the phone
4. opened Magisk manager and selected install from source where i chose the boot.img
5. it created a copy called magisk_patched.img
6. booted in fastboot
7. on my pc used the command prompt to "fastboot boot magisk_patched.img"
booted normally and i had root.
but then problem appeared
#Problem 1
everytime i rebooted my phone i would loose root and it would say Magisk not installed. To get it back i would need to perform step 7 again and it was not ideal to do that everytime i turned off my phone.
#Problem 2
While tryng to solve problem 1 i read that i needed to open magisk manager and "Install to Inactive Slot (After OTA)."
After doing that it rebooted but now it wont boot at all, even if i try to "fastboot boot magisk_patched.img" the cmd gives me error:
fastboot boot magisk_patched.img
downloading 'boot.img'...
OKAY [ 0.838s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.845s
now my phone is just sitting there i dont want to reset it again. it would be the 4th time that i need to set up my phone in 2 days, so im trying to see if there are alternatives.
If reset is really the only way, i read that with root you can make a full backup of your phone and then restore it. How to do that? can i do it in the situation im in?
How can i root my OP6T running OOS10.3.2, and keep it? Whats the right method bc the one i followed seemed flawed.
I also tried one that had TWRP but maybe i did something wrong bc it didnt work., also there is no official one working for 10.3.2.

What is happening is normal with those instructions (they aren't right).
All you need to do is install TWRP. Do not use the official one, it is out of date. Use TWRP from this thread Link here. The TWRP from that thread is from the official maintainer. It works fine with OOS 10.
- You need to get the phone in fully working order again. Which may mean you need to use the fastboot ROM, as you've probably "goofed" something up at this point. (no offense meant). Make sure your phone boots and such after this.
- For OOS 10 with the phone in fastboot, fastboot boot recoveryimgfilename.img (<-- For OOS 10 you will need TWRP 3.3.1-32 Q Unofficial by mauronofrio from the thread I linked to above) This will boot to TWRP.
- Now run TWRP 3.3.1-32 Unofficial Installer by mauronofrio this will install TWRP. The installer is the same for Android 9 and 10, doesn't matter.
- Once the installer runs, click back, choose reboot to recovery. If you boot to the system, you have to start over. Reboot to recovery!
- Install Magisk 20.3 <-- The current version. The official download page. After that you can reboot to the system. You should now have a rooted, phone with Magisk, and TWRP installed.
Any questions ask.

OhioYJ said:
What is happening is normal with those instructions (they aren't right).
All you need to do is install TWRP. Do not use the official one, it is out of date. Use TWRP from this thread Link here. The TWRP from that thread is from the official maintainer. It works fine with OOS 10.
- You need to get the phone in fully working order again. Which may mean you need to use the fastboot ROM, as you've probably "goofed" something up at this point. (no offense meant). Make sure your phone boots and such after this.
- For OOS 10 with the phone in fastboot, fastboot boot recoveryimgfilename.img (<-- For OOS 10 you will need TWRP 3.3.1-32 Q Unofficial by mauronofrio from the thread I linked to above) This will boot to TWRP.
- Now run TWRP 3.3.1-32 Unofficial Installer by mauronofrio this will install TWRP. The installer is the same for Android 9 and 10, doesn't matter.
- Once the installer runs, click back, choose reboot to recovery. If you boot to the system, you have to start over. Reboot to recovery!
- Install Magisk 20.3 <-- The current version. The official download page. After that you can reboot to the system. You should now have a rooted, phone with Magisk, and TWRP installed.
Any questions ask.
Click to expand...
Click to collapse
So getting it straight, i need to first reset my phone and then do the steps you described.
Can i backup the data first with TWRP to restore it later and avoid setting up everything again?

Davide1713 said:
So getting it straight, i need to first reset my phone and then do the steps you described.
Can i backup the data first with TWRP to restore it later and avoid setting up everything again?
Click to expand...
Click to collapse
Supposedly. I've never used that function of TWRP. Some people have luck with, some people restore things that shouldn't be restored and end up having to wipe the phone again. Personally I just use TitaniumBackup like I always have. I would search for information on that in the TWRP thread if you want to try method. I don't know enough on that to provide solid information.

OhioYJ said:
Supposedly. I've never used that function of TWRP. Some people have luck with, some people restore things that shouldn't be restored and end up having to wipe the phone again. Personally I just use TitaniumBackup like I always have. I would search for information on that in the TWRP thread if you want to try method. I don't know enough on that to provide solid information.
Click to expand...
Click to collapse
Hey man,
Thank you so much. It worked and i stay rooted even after reboot.
May i ask how you use the Titanium Backup, i think back in the days all i used it for was uninstalling system apps. Or if you know some nice guides. If you know other good things to checkout now that i have root i would appreciate it, i have been far away from rooting for too long.
Once again thank you so much

Davide1713 said:
Hey man,
Thank you so much. It worked and i stay rooted even after reboot.
May i ask how you use the Titanium Backup, i think back in the days all i used it for was uninstalling system apps. Or if you know some nice guides. If you know other good things to checkout now that i have root i would appreciate it, i have been far away from rooting for too long.
Click to expand...
Click to collapse
I use it to back up app and app data primarily. It allows me to restore data to apps after a clean install. Since I have the Pro version it's just a batch action (one click essentially). There is also a way to create a flashable .zip you can use in TWRP, although I haven't tried that method, as I'm typically not restoring apps, just data. I also use it remove apps from time to time.

OhioYJ said:
I use it to back up app and app data primarily. It allows me to restore data to apps after a clean install. Since I have the Pro version it's just a batch action (one click essentially). There is also a way to create a flashable .zip you can use in TWRP, although I haven't tried that method, as I'm typically not restoring apps, just data. I also use it remove apps from time to time.
Click to expand...
Click to collapse
Hey man, im sorry i am once again in need.
Idk why but at first i can reboot the system normally without issues. but after a while once i set up everything it just doesnt boot anymore. Am i missing something? do i have to do anything with magisk? download a module or something?
Could it be that google security update is the fault?

Davide1713 said:
Hey man, im sorry i am once again in need.
Idk why but at first i can reboot the system normally without issues. but after a while once i set up everything it just doesnt boot anymore. Am i missing something? do i have to do anything with magisk? download a module or something?
Could it be that google security update is the fault?
Click to expand...
Click to collapse
When you installed everything originally did you fix everything with a clean install? Both slots are the same version of Android? (Like you don't have something weird going on like Android 9 on one and Android 10 on another?)
You definitely have something abnormal going on. There shouldn't be anything in Magisk that you have to do, at least not to prevent crashing. I normally hide it, but that has to do with keeping apps from detecting root.

OhioYJ said:
When you installed everything originally did you fix everything with a clean install? Both slots are the same version of Android? (Like you don't have something weird going on like Android 9 on one and Android 10 on another?)
You definitely have something abnormal going on. There shouldn't be anything in Magisk that you have to do, at least not to prevent crashing. I normally hide it, but that has to do with keeping apps from detecting root.
Click to expand...
Click to collapse
I got it to boot by uninstalling magisk,
I am 100% sure i dont have two different version of android in different slots, bc yesterday i was in big trouble and nothing was working and i flashed on both slots the same version of android 10(dont remember exactly wich one as i tried a couple, but they were the same).
Today when i couldnt boot anymore i went into stock recovery, factory reset -> when it booted i placed the stockOS.zip file in the phone and applied update from local file -> after that i factory reset again from the system settings, so i think the phone should have installed it properly.
Only after that i did what you told me and installed TWRP and Magisk. and as i said it worked and i could restart my device etc..
After a while when i restarted i couldnt boot anymore and went to bootloader. Removing Magisk fixed it,apperantly on install magisk creates a copy of the boot.img that it restores on uninstall, and i booted to system.
Now i can use my phone but dont have root.
Im very thankful for you being there and helping me out trough this, i cant thank you enough

GuestD2272 said:
I got it to boot by uninstalling magisk,
I am 100% sure i dont have two different version of android in different slots, bc yesterday i was in big trouble and nothing was working and i flashed on both slots the same version of android 10(dont remember exactly wich one as i tried a couple, but they were the same).
Today when i couldnt boot anymore i went into stock recovery, factory reset -> when it booted i placed the stockOS.zip file in the phone and applied update from local file -> after that i factory reset again from the system settings, so i think the phone should have installed it properly.
Only after that i did what you told me and installed TWRP and Magisk. and as i said it worked and i could restart my device etc..
After a while when i restarted i couldnt boot anymore and went to bootloader. Removing Magisk fixed it,apperantly on install magisk creates a copy of the boot.img that it restores on uninstall, and i booted to system.
Now i can use my phone but dont have root.
Im very thankful for you being there and helping me out trough this, i cant thank you enough
Click to expand...
Click to collapse
Not sure if you're still having this issue but I'll post the solution just in case anyone gets stumped, does a google search, and comes across this post. You were using the wrong command.
"fastboot boot" just lets you boot with the img so you can verify that root works.
"fastboot FLASH boot" will flash it and root will stick after reboot.
No need to jump through hoops with TWRP and such.

[GUIDE] [TB-X606F] [Lenovo M10 Plus FHD] How to flash TWRP, Generic System Image (Android 11, Android 12), and Root with Magisk

Hi, I'm a long-time lurker on these forums but recently had some success flashing a GSI and rooting the Lenovo Tab M10 Plus (FHD) (X606F) with TWRP, and wanted to share my exact steps here. This device is awesome for the price point but unfortunately not popular enough to have many guides available. The tablet is Project Treble compatible and uses A/B roms (although it is not an A/B device in terms of OTA updates). You can use the Treble Info app to confirm that the devices uses an ARM64 A/B operating system. This was tested with the CAOS 11 GSI based on Android 11; it may work on other GSIs and other Android versions but I have not tested those (NOTE: user below confirms working on Android 12). I've written this guide at a bird's-eye-view meant for users familiar with flashing.
A couple useful notes before we begin:
- Hardware force off: hold down both volume buttons + power button
- Hardware boot into bootloader: while powered off, hold volume down + power button
- Hardware boot into recovery: hold down both volume buttons + power button
- While in fastboot mode, the command `fastboot reboot recovery` does not work for me on this device. You may have to hardware boot into recovery using the hardware steps above (power off completely then hardware boot). [This command may work for some people. It does not work for my device.]
Obviously, make sure your bootloader is unlocked before starting.
1. I used Ubuntu since Windows was having trouble recognizing the device in fastboot mode; linux drivers seem to be better developed for this particular device. I used `sudo apt install android-sdk` to get the drivers. Much easier than the nonsense that you have to do on Windows to get this device to work. Unfortunately, the Lenovo rescue app is available only for Windows, so you'll need access to Windows to gain access to vbmeta.img for installing TWRP (below).
2. Install TWRP following this guide: https://forum.xda-developers.com/t/...rp-3-5-x-for-lenovo-tab-m10-fhd-plus.4222887/. It is important that you follow all these steps. After flashing the recovery, you must reboot into recovery to ensure that TWRP permanently installs. If the `fastboot reboot recovery` command does not work for you, hold down the power button to power off the device, then hardware boot into TWRP by holding down both volume buttons + power button to boot into TWRP. If you do not perform this step, the device will boot normally and TWRP will be erased. After booting into TWRP, wipe -> format data.
3. In TWRP, flash CAOS 11 GSI: https://forum.xda-developers.com/t/official-aosp-r-mod-caos11.4265059/. You can try with other GSIs - it will probably work - but I've only tested this particular one, and can attest for the stability of CAOS 11 on this device. The image you'll want is named with -arm64-bgZ. If you use another GSI, make sure to use the A/B arm64 image. CAOS 11 has gapps included, so no need to flash here; if you use another GSI that does not have, you'll need to flash the appropriate gapps yourself. You can also opt for the non-gapps download if you don't want Google spying on you.
4. (Optional/No longer necessary) In TWRP, flash to disable dm-versity: https://zackptg5.com/android.php#disverfe.
5. (Optional - many GSIs come with root) In TWRP, flash standard Magisk.zip: https://github.com/topjohnwu/Magisk. I didn't need to use Magisk-Phh.
6. Reboot system.
7. You may or may not get errors from Google Play saying that the device is not certified. Follow these steps:
- Sign into Google account on device via settings
- Download and install the Get ID app: https://f-droid.org/en/packages/makeinfo.com.getid/
- Open the app and Copy Google Service Framework Key
- Go to https://www.google.com/android/uncertified/
- Sign in and paste the copied value to it, register
- Reboot (this actually took me a few tries to get working, I believe the key is to make sure you're signed into your Google account)
- Google Play should be working
Feel free to ask any questions here.

I got this working with the PHH android 12 pre-release version. So far everything seems to be working. There are a couple things I have to sort out still like it passes safetynet but some apps still don't show up in the play store.

dpn982 said:
I got this working with the PHH android 12 pre-release version. So far everything seems to be working. There are a couple things I have to sort out still like it passes safetynet but some apps still don't show up in the play store.
Click to expand...
Click to collapse
Good to know that Android 12 works. What apps aren't showing up for you? Maybe they are simply incompatible with Android 12.

shnioob said:
Good to know that Android 12 works. What apps aren't showing up for you? Maybe they are simply incompatible with Android 12.
Click to expand...
Click to collapse
Netflix is one, maybe Disney plus too. It could be that I just need to restart cause I haven't done that since I got safetynet passing. I was waiting for the bulk of the apps to restore first.

dpn982 said:
Netflix is one, maybe Disney plus too. It could be that I just need to restart cause I haven't done that since I got safetynet passing. I was waiting for the bulk of the apps to restore first.
Click to expand...
Click to collapse
I think this tablet has always had an issue with Netflix due to lack of DRM or something of that nature - I wasn't able to get Netflix on the stock version. Disney+ is probably the same issue.
If you have some free time, it would be great if you can outline your steps for getting safetynet to pass. I haven't bothered with it.

Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.

Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
Thanks!
By the way, about point number 7, which roms are like this? I have tried: Phhusson Android 12 latest version, PE 12 latest version and Lineage OS by AndyYan, all with gapps but I get the error

emilio666 said:
Thanks!
By the way, about point number 7, which roms are like this? I have tried: Phhusson Android 12 latest version, PE 12 latest version and Lineage OS by AndyYan, all with gapps but I get the error
Click to expand...
Click to collapse
NEVERMIND, it got solved by just waiting a couple of hours after using the Google website: https://www.google.com/android/uncertified/

Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.

Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
Thanks for the clarifying info, updated the OP a bit. And thanks for providing us with a TWRP to make this possible. Otherwise this awesome tablet would be stuck on Android 10 forever.
vladilog said:
Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.
Click to expand...
Click to collapse
Happy to help, glad it worked for you. I tried installing some other GSIs with and without flashing Magisk - LineageOS 12 boots but is very buggy, after reboot I was unable to get past the lockscreen. PixelExperience 11 and 12 cause a bootloop. If anyone has had success with PixelExperience I would love to get your input.

Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
So i can flash the official google GSI using these steps?
Branch Grid
ci.android.com
I don't need root and want to be stock as possible.

jebise101 said:
So i can flash the official google GSI using these steps?
Branch Grid
ci.android.com
I don't need root and want to be stock as possible.
Click to expand...
Click to collapse
Give it a try and let us know. I think some GSIs are more stable than others. I've had trouble with LOS and PE on this device.

shnioob said:
Give it a try and let us know. I think some GSIs are more stable than others. I've had trouble with LOS and PE on this device.
Click to expand...
Click to collapse
How do you go back to stock in case this does not work?
Is there a factory image?

jebise101 said:
How do you go back to stock in case this does not work?
Is there a factory image?
Click to expand...
Click to collapse
you can download the stock ROM from LMSA

I also have Lenovo tab m10 fhd plus but it is tb-x606v. Can I flash x606f rom on this device and flash twrp after.i don't want my device to be bricked.

vladilog said:
Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.
Click to expand...
Click to collapse
Hi, I'm trying to follow what you did, but I'm having issues with the Gapps, do you have some pointers to solve it? Thank you in advance

Hello everybody!
I finally installed CAOS 11 and it's working like a charm. Gapps are definitely working as excpected and system seems to be stable as possible.
I have two question to those that installed it to :
Is anyone kow why some widgets on X606F are not clickable, an do not actualize till reboot?
Am I the only one that lost double tap to wake on CAOS?
Thank you all

I tried AOSP V412 12L too, we lost fingerprint sensor and face unlock, widevine DRM. There is some troubles on wifi, beside of this it is pleasant. Of course this not as smooth as android 10. I do not recommend it for daily basis.

I have tb-X606X. I’ve tried AOSP 11 and AOSP 12, Pixel Exp 11 and 12, LineageOS 11 and 12, but finally I stay with CAOS11, which is from all I tried, the most stable, smooth and bug free.
Btw, I do not have any issue with widgets on CAOS.
And yes, the double tap to wake is lost. I think it is not because of CAOS, it is because of Android 11 and above.

garconblair said:
I have tb-X606X. I’ve tried AOSP 11 and AOSP 12, Pixel Exp 11 and 12, LineageOS 11 and 12, but finally I stay with CAOS11, which is from all I tried, the most stable, smooth and bug free.
Btw, I do not have any issue with widgets on CAOS.
And yes, the double tap to wake is lost. I think it is not because of CAOS, it is because of Android 11 and above.
Click to expand...
Click to collapse
Thanks for the feedback. What about Widevine L1 and SafetyNet test with CAOS11? Are you able to play content at 1080p resolution with the Netflix App?

Database Users

welcome