Database Users

[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?

[Guide][Treble] Install Android 9.0 Pie AOSP GSI (Windows/Mac/Linux)

Install Android 9.0 Pie AOSP GSI
Warning
You will loose all your data. Make sure to backup. You are doing this at your own risk. Neither me nor xda is responsible for any bricked devices.
Pre-Requisites
Please read carefully. Any questions which are already answered in OP will be ignored.
If you have a question, not answered in OP read last 2-3 pages. Any questions which are already answered in last 2-3 pages will also be ignored.
Not being rude, but people need to start reading.
Make sure you have unlocked the bootloader.
​Text Guide
Install Android 9.0 Pie AOSP GSI
1. Download AB Arm64 GSI from link in downloads. Unzip it. Windows users can use Winrar. Mac users can use the Unarchiver.
2. Download and unzip adb & fastboot linked in downloads section.
3. Place the extracted system image (step 1) in platform-tools folder. Rename it to system-arm64.img.
4. Power off phone.
5. Press and hold volume down and power button at the same time. You will now boot into fastboot boot.
6. Connect phone to computer.
7. Windows users open command prompt. Mac/Linux users open Terminal. Navigate to the folder where you unzipped adb & fastboot.
Windows
Code:
fastboot devices
Mac & Linux
Code:
./fastboot devices
If your device shows up, drivers were installed correctly. If not, then drivers were not installed and you need to install them.
8. Erase System
Windows
Code:
fastboot erase system
Mac & Linux
Code:
./fastboot erase system
9. Flash Android Pie GSI
Windows
Code:
fastboot flash system system-arm64.img
Mac & Linux
Code:
./fastboot flash system system-arm64.img
10. Wipe/Factory Reset
Windows
Code:
fastboot -w
Mac & Linux
Code:
./fastboot -w
11. Reboot
Windows
Code:
fastboot reboot
Mac & Linux
Code:
./fastboot reboot
11. Profit. Android 9.0 Pie. Rooting might result in broken Wi-fi. So, flash back stock boot.img if your wifi is broken after rooting.
Video Guide
Downloads
MiUnlock Tool - http://xiaomi-miui-ota-3rdrom.ks3-c...1/3.3.525.23/miflash_unlock-en-3.3.525.23.zip
Latest ADB & Fastboot :- https://developer.android.com/studio/releases/platform-tools
Setup ADB and Fastboot (if above adb & fastboot do not work) - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Android 9.0 Pie GSI Thread :- https://forum.xda-developers.com/pr...velopment/aosp-9-0-phh-treble-t3831915/page12
Android 9.0 Pie GSI Download Links :- https://github.com/phhusson/treble_experimentations/releases
Winrar (Windows) :- https://www.rarlab.com/
The Unarchiver (Mac):- https://theunarchiver.com/

@munchy_cool wow!!!, Thanks man. But sorry but i have to ask, did you try this on your A2 is it working fine without any issues?

crazykas said:
@munchy_cool wow!!!, Thanks man. But sorry but i have to ask, did you try this on your A2 is it working fine without any issues?
Click to expand...
Click to collapse
the A2 in the video is mine. I tried it for some time. Camera works, wifi works, sound works, charging works, couldnt check calls and lte as I am at work and cannot have my sim turned off for even a minute. But yes it works.

munchy_cool said:
the A2 in the video is mine. I tried it for some time. Camera works, wifi works, sound works, charging works, couldnt check calls and lte as I am at work and cannot have my sim turned off for even a minute. But yes it works.
Click to expand...
Click to collapse
much appreciated man!! Reason i asked this is i ****edup my phone before cause of that fastboot boot twrp > set active b slot thing. So my warranty covered me and gave a new phone. lol. BTW what do you mean by "cannot have my sim turned off for even a minute"? Finally it will be great if you can add how to flash back the stock rom as well.. Thanks mate :good:

crazykas said:
much appreciated man!! Reason i asked this is i ****edup my phone before cause of that fastboot boot twrp > set active b slot thing. So my warranty covered me and gave a new phone. lol. BTW what do you mean by "cannot have my sim turned off for even a minute"? Finally it will be great if you can add how to flash back the stock rom as well.. Thanks mate :good:
Click to expand...
Click to collapse
not sure how you bricked it but glad you got a new phone.
"cannot have my sim turned off"
So, I have only one sim which is in my work phone. to test LTE, data etc i will have to remove the sim from that phone and put it in the Mi A2. Now, I cannot do that as I cannot have my sim (phone number) turned off for even a minute due to work.
As for going back to stock. Download stock firmware, extract it and replace pie gsi img with system.img from factory firmware zip and you will be back to stock.

munchy_cool said:
not sure how you bricked it but glad you got a new phone.
"cannot have my sim turned off"
So, I have only one sim which is in my work phone. to test LTE, data etc i will have to remove the sim from that phone and put it in the Mi A2. Now, I cannot do that as I cannot have my sim (phone number) turned off for even a minute due to work.
As for going back to stock. Download stock firmware, extract it and replace pie gsi img with system.img from factory firmware zip and you will be back to stock.
Click to expand...
Click to collapse
How did i bricked my phone. Simple. First of all no desrepect for any dev, since i did this by my one. What i did was tried to flash unofficial twrp and fastboot set slot b did not worked. Once i reboot it got stuck on a bootloop. i couldn't flash xiaomi stock fastboot zip due to "critical partition flashing is not allowed" and before you asked yes my A2 was bootloader unlocked one. Unlock critical partition thing is not for our devices like for pixel series as far as i know. So simply i couldn't fix it, neither the software guy from my purchased center. That's why im afraid. I know you are besy, but highly appreciate if you can write down how to go back to stock guideline as well. Thanks again :good:

crazykas said:
How did i bricked my phone. Simple. First of all no desrepect for any dev, since i did this by my one. What i did was tried to flash unofficial twrp and fastboot set slot b did not worked. Once i reboot it got stuck on a bootloop. i couldn't flash xiaomi stock fastboot zip due to "critical partition flashing is not allowed" and before you asked yes my A2 was bootloader unlocked one. Unlock critical partition thing is not for our devices like for pixel series as far as i know. So simply i couldn't fix it, neither the software guy from my purchased center. That's why im afraid. I know you are besy, but highly appreciate if you can write down how to go back to stock guideline as well. Thanks again :good:
Click to expand...
Click to collapse
did you try fastboot set slot a, and then reboot? that should have fixed it.
As for a guide for going back to stock from Pie.
LIke i said.
dowload fastboot firmware from here.
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
extract the zip file. open images folder. grab system.img. put it in fasboot folder. and in step where we flash pie gsi image, flash the system.img you just pasted in fastboot folder.

munchy_cool said:
did you try fastboot set slot a, and then reboot? that should have fixed it.
As for a guide for going back to stock from Pie.
LIke i said.
dowload fastboot firmware from here.
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
extract the zip file. open images folder. grab system.img. put it in fasboot folder. and in step where we flash pie gsi image, flash the system.img you just pasted in fastboot folder.
Click to expand...
Click to collapse
Thanks man. Will try at night. Can't wait ????

MTP doesn't work.

Streect said:
MTP doesn't work.
Click to expand...
Click to collapse
It works. Enable it in Developer Tools.

Thank you very much for sharing, i will try it soon
---------- Post added at 10:02 AM ---------- Previous post was at 09:39 AM ----------
No problem on Linux? Simple adb /fastboot installed on Ubuntu
---------- Post added at 10:09 AM ---------- Previous post was at 10:02 AM ----------
Again: which one img do you choose, aonly or ab?

HTCDevil said:
Thank you very much for sharing, i will try it soon
---------- Post added at 10:02 AM ---------- Previous post was at 09:39 AM ----------
No problem on Linux? Simple adb /fastboot installed on Ubuntu
---------- Post added at 10:09 AM ---------- Previous post was at 10:02 AM ----------
Again: which one img do you choose, aonly or ab?
Click to expand...
Click to collapse
did you read the OP at all? it's mentioned step 1 which file you need.

How to install Gapps?

munchy_cool said:
[...]
Click to expand...
Click to collapse
Two things:
1) Thank you for the guide! You got yourself another subscriber on YouTube This is my first device that supports Treble. From your experience, how stable are GSI ROMs?
2) Update your signature

speedunderx said:
How to install Gapps?
Click to expand...
Click to collapse
i didnt get time to check that. may have to install some apks. maybe the same apks which are needed for amazon fire tablets to get play store working.

soulicro said:
Two things:
1) Thank you for the guide! You got yourself another subscriber on YouTube This is my first device that supports Treble. From your experience, how stable are GSI ROMs?
2) Update your signature
Click to expand...
Click to collapse
gsi's are pretty stable, check xda thread for bugs. will update signature soon

munchy_cool said:
did you read the OP at all? it's mentioned step 1 which file you need.
Click to expand...
Click to collapse
About my last question ok, i see on YouTube it is ab. Other question not answered yet. Thanks.

HTCDevil said:
About my last question ok, i see on YouTube it is ab. Other question not answered yet. Let him answer by itself. Thanks.
Click to expand...
Click to collapse
no problem on Linux.

munchy_cool said:
no problem on Linux.
Click to expand...
Click to collapse
Great, hope gapps work and camera is mostly Stable. Thank you

HTCDevil said:
Great, hope gapps work and camera is mostly Stable. Thank you
Click to expand...
Click to collapse
it does not have gapps. you may have to manually install some apks. try with apks needed for Play Store on amazon fire tablets.
if you figure those out, please let us know.

Barnes & Noble Nook Tablet 10.1" BNTV650, working!

Just picked one of these up last week, and it has no restrictions on unlocking the bootloader. Boots AOSP 8.1 Phh-Treble almost perfectly. The boot animation was missing, but the wifi, bluetooth, and camera all seem to work just fine.
It doesn't seem to boot AOSP 9, though. Something about keymaster version mismatches, it seems like.

izzy84075 said:
Just picked one of these up last week, and it has no restrictions on unlocking the bootloader. Boots AOSP 8.1 Phh-Treble almost perfectly. The boot animation was missing, but the wifi, bluetooth, and camera all seem to work just fine.
It doesn't seem to boot AOSP 9, though. Something about keymaster version mismatches, it seems like.
Click to expand...
Click to collapse
Make sure that Your kernel is using same security patch date as GSI. I think Phh GSI is supposed to adjust itself to any security patch but if it's not happening then open system.img (Phh Pie) and check security patch. Then use Android Image Kitchen (AIK) to unpack stock boot image and go to.. I literally forgot the name of that folder lol.. there should be 2 folders, ramdisk and something else. So open that "something else" folder then edit oslevel and change security patch to the one that's in Phh Pie.
Now flash image-new.img and system.img and Phh Pie should boot now :fingers-crossed:.

whats the default os version on these puppies ?

Could someone post steps to unlock/root? I've not used a custom ROM since KitKat. The default B&N software is trash.

senselocke said:
Could someone post steps to unlock/root? I've not used a custom ROM since KitKat. The default B&N software is trash.
Click to expand...
Click to collapse
I unlocked the boot loader of the Nook Tablet 10.1”, I installed Project Treble 8.1.0 and Project Treble 9.0, they both had WiFi connection problems.

I installed the most recent version of PHH's Pi GSI and it works flawlessly, even boots up quire quickly after the initial flash. To my knowledge everything works, boot animation, bluetooth, wifi, all of it. Very simple process, just unlock bootloader, get the GSI, flash, and go. Painless, simple, and flawless thus far.

I'm a huge noob to flashing and the thought of bricking scares me, but I'm trying to setup a guide I just don't have the gal to actually test it. I want to backup everything, rom and recovery included and be able to put everything back to stock I just don't know if TWRP works with it. If this is wrong, someone please correct me and I'll edit this post.
1. open developer options via tapping build in about tablet until it opens. Enable usb debugging and oem unlock.
2. install 15 second adb onto your pc, plug your tablet in via usb and with it off, hold volume up and power to go into recovery. select "reboot into bootloader". you'll see "fastboot enabled" on the bottom left of the screen. In a command prompt run "fastboot devices" to make sure its there (you should see a string of numbers popup) then run "fastboot oem unlock". on the tablet you'll see a "do you want to unlock your bootloader?" press volume up for yes. then "fastboot reboot" to go back to your tablet.
3. google for "frama root" and put it on the root of your sdcard. Use the boromir or whichever until root is successful. (you'll probably have to reboot)
4. (the part I'm not sure will work) install twrp manager from the play store and backup everything to your sdcard. partitions, etc.
5. get a gsi image, put it on your SD card, boot into twrp and flash.
To go back to stock
restore your twrp backup, run frama root to unroot your tablet, use adb and fastboot to run "fastboot oem lock" to lock the bootloader and uncheck the stuff in dev options .

I picked up one of these things a few months ago. I'm thinking about unlocking the bootloader, rooting it, etc. I did some work on previous Android versions (think KitKat), but 8.x is pretty new to me.
Regarding TWRP -- someone needs to actually port it for this device. At least that is how it worked prior to 8.x. I haven't seen one for the BNTV650 so far. Looks like the "Flash GSI without TWRP" steps apply.

alyxnsac said:
I installed the most recent version of PHH's Pi GSI
Click to expand...
Click to collapse
Which one? AOSP 9 I presume, but can you confirm? I'm getting one of these babies and the first thing I will do is to try to install a good, alternate ROM on it (I never use the manufacturer's ROM if I can avoid it).

Problems installing Gapps on GSI Roms

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

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.