Database Develop

[Q] HP Touchpad Dual Boot webOS & Android?

Hi All,
I'm newbie to the HP Touchpad, all i've done so far is update it to the latest webOS. How do i go about dual booting? I want to leave webOS untouched and have the option to boot into Andriod. There are so many different instructions and videos, can someone point me to a good up to date guide i can follow for dual booting? Also, which is the best version on Andriod for the HP Touchpad at the moment?
Regards
Phil

There's no simple one-click installation available, so start reading the thread under Development:
[GUIDE] Written CM9 Install Instructions
Read, download, re-read... and follow instructions closely and you will be there (i.e. getting CM9 (Android 4) install as the default boot option, but leaving WebOS untouched and to be picked instead).
Works fine, but with stated Android 4 restrictions.
/Decc

I say stick to CM7 and webOS, CM9 although looking GREAT is still buggy but that is my personal opinion. Both will install just the same way, all you have to do is replace the CM7 file with CM9.
The guide is here: http://forum.xda-developers.com/showthread.php?t=1305891
Definitely read everything through a few times to feel secure about what you are doing.

Stick with cm 7 3.5 it's a good stable build cm 9 is still in its early stages
And if you do decide to do it just read all the steps and re read them and take your time and you should have no problems

Deccard said:
There's no simple one-click installation available, so start reading the thread under Development:
[GUIDE] Written CM9 Install Instructions
Read, download, re-read... and follow instructions closely and you will be there (i.e. getting CM9 (Android 4) install as the default boot option, but leaving WebOS untouched and to be picked instead).
Works fine, but with stated Android 4 restrictions.
/Decc
Click to expand...
Click to collapse
is that guide still up to date? would like to dual boot and install android, leaving webOS untouched.

Cobra281 said:
is that guide still up to date? would like to dual boot and install android, leaving webOS untouched.
Click to expand...
Click to collapse
Here is good up to date http://rootzwiki.com/topic/31548-ho...-with-sound-camera-microphone-updated-121312/
This covers CM7/9/10 with links and video tutorial.

[Q] How to Fresh install CM 10.2 on HP Touchpad

I have 2 year old Touchpad that was running Android 4.2.2 and tried to update to 4.3.1 and trashed it. I was running CM 7, upgraded to 9, then 10, then 10.1. I did everything to try and salvage it and read every article possible with NO luck.
SO, I decide to use Acme Uninstaller to remove it, but had issues seeing the Partition and it wanted to FORMAT - I did NOT FORMAT because everyone said not to.
SO then I did a factory reset on the Touchpad and erased it. This worked and allowed me to try and get back to CM 10.2.
The problem is that I cannot find a single installation method that shows the simplest steps to install CM10.2 ( Android 4.3 ) without having to install older version of CM9, or CM10.
I have tried every possible article and method and so far here is what I am stuck with.
I can install CM9 with Moboot BUT CWM and TWRP will not install so I cannot update GAPS.
I erased and then tried using the TAILOR Web OS app to increase the OS partitions from 400mb to 600 mb and that installed fine.
Then I installed CM 10 using ACMEInstaller 3 and it boot loops.
Then I tried CM 10.2 using ACMEinstaller3 and it will not install and says the package is invalid.
It seems like something do to with the partitions and that is why I cannot installed CWM, TWRP or GAPS or even an update.
The only thing I have NOT done is use WEB OS Dr. because I thought this is for when WEB OS is trashed.
I know this seems like a re-post but it really isnt
IF anyone has a simple document that details exactly how a Touchpad should be correctly erased and then install a fresh CM10.2, I would really appreciated it.
There just does not seem to be any articles or you tube videos that show this processes.
I am sure there are a lot of people that would benefit from a guide for CM9, CM10 or CM.2 by doing a complete erase and start over.
I have started writing my own documents but of course I cannot finish it.
Please help and point me in the correct direction because I am stuck with only WEB OS.

cmakar said:
I have 2 year old Touchpad that was running Android 4.2.2 and tried to update to 4.3.1 and trashed it. I was running CM 7, upgraded to 9, then 10, then 10.1. I did everything to try and salvage it and read every article possible with NO luck.
SO, I decide to use Acme Uninstaller to remove it, but had issues seeing the Partition and it wanted to FORMAT - I did NOT FORMAT because everyone said not to.
SO then I did a factory reset on the Touchpad and erased it. This worked and allowed me to try and get back to CM 10.2.
The problem is that I cannot find a single installation method that shows the simplest steps to install CM10.2 ( Android 4.3 ) without having to install older version of CM9, or CM10.
I have tried every possible article and method and so far here is what I am stuck with.
I can install CM9 with Moboot BUT CWM and TWRP will not install so I cannot update GAPS.
I erased and then tried using the TAILOR Web OS app to increase the OS partitions from 400mb to 600 mb and that installed fine.
Then I installed CM 10 using ACMEInstaller 3 and it boot loops.
Then I tried CM 10.2 using ACMEinstaller3 and it will not install and says the package is invalid.
It seems like something do to with the partitions and that is why I cannot installed CWM, TWRP or GAPS or even an update.
The only thing I have NOT done is use WEB OS Dr. because I thought this is for when WEB OS is trashed.
I know this seems like a re-post but it really isnt
IF anyone has a simple document that details exactly how a Touchpad should be correctly erased and then install a fresh CM10.2, I would really appreciated it.
There just does not seem to be any articles or you tube videos that show this processes.
I am sure there are a lot of people that would benefit from a guide for CM9, CM10 or CM.2 by doing a complete erase and start over.
I have started writing my own documents but of course I cannot finish it.
Please help and point me in the correct direction because I am stuck with only WEB OS.
Click to expand...
Click to collapse
I too am having a confusing time with my TP. I've tried a few ROMs and I just want to basically erase everything and install a single, fresh new ROM. I haven't touched my TP in quite a while so i've forgotten all the confusing steps it took to originally root it. Some guidance would be great.

Finally have CM 10.2 / Android 4.3.1 installed
I wanted to let you know that I was FINALLY able to get a fresh install of CM 10.2 / Android 4.3.1 installed using the NEW ACMEInstaller 5 T.
I also used the ACMEUNINSTALL2 that was re-posted.
So I plan on Factory wiping my Touchpad so that I can document the process from beginning to end and if it works, then I will post my instructions.
Of course I make no guarantees like everyone else states, but I am following pieces and parts of what everyone else posts and just trying to make a simpler guide. There are lots of guides but nothing that seems to work at all for me and lots of other people are saying the same thing.
iamdestruktor said:
I too am having a confusing time with my TP. I've tried a few ROMs and I just want to basically erase everything and install a single, fresh new ROM. I haven't touched my TP in quite a while so i've forgotten all the confusing steps it took to originally root it. Some guidance would be great.
Click to expand...
Click to collapse

Modernised ROM install

After having the HP Touchpad sitting on the shelf for one year, I decided to install a newer KitKat ROM to get rid of blacked out mail content and web pages that appeared after the initial move 2013 to KitKat 4.4
First I tried to figure out my current setup, because of what I learned a repartioning would be needed to support the current ROMS with there media/data structure that had been introduced with the newer builds.
I run CyanogenMod 11-20131118-UNOFFICIAL-tenderloin build-no. cm_tenderloin-userdebug 4.4 KRT16M 05dd1588ec test-keys with a 2.6.35 kernel on with moboot 038 and CWM 5026
SD-Card info shows 25,42 GB internal storage 1,48G
Back then I used tailor or a similiar tool to resize
A good info about the newer tools I found was lilyputing:
http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
Wasn't sure about how to proceed while no updates showed up using the built-in updtae check function and of course Roland's Tutorials had been the first place I went heading to as well:
http://rootzwiki.com/topic/179730-r...-with-jcsullins-tptoolbox-the-super-easy-way/
Now I am stuck with getting TP Toolbox to work. Novacom still installed on the windows 7 box, but not connecting to the touchpad.
I booted into WebOs recovery using the moboot selector, but...
Leaving the WebOS recovery was done then by pressing the home and power buttons simultaneously for about 20secs until the tablet rebooted.
I guess I have to move on, leaving WebOS because support ends January 2015 and even connecting to google mail is getting complicated under WebOS.
The current ROM is not working well, so I need an update. Any suggestions?
BTW: I thought to move on to JCSullins ROM, because the 20141231 build had good feedback regarding stability and number of bugs, especially energy consumption. Anyway it doesn't show up any more on the list of downloadable ROMS since yesterday.

[email protected] said:
After having the HP Touchpad sitting on the shelf for one year, I decided to install a newer KitKat ROM to get rid of blacked out mail content and web pages that appeared after the initial move 2013 to KitKat 4.4
First I tried to figure out my current setup, because of what I learned a repartioning would be needed to support the current ROMS with there media/data structure that had been introduced with the newer builds.
I run CyanogenMod 11-20131118-UNOFFICIAL-tenderloin build-no. cm_tenderloin-userdebug 4.4 KRT16M 05dd1588ec test-keys with a 2.6.35 kernel on with moboot 038 and CWM 5026
SD-Card info shows 25,42 GB internal storage 1,48G
Back then I used tailor or a similiar tool to resize
A good info about the newer tools I found was lilyputing:
http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
Wasn't sure about how to proceed while no updates showed up using the built-in updtae check function and of course Roland's Tutorials had been the first place I went heading to as well:
http://rootzwiki.com/topic/179730-r...-with-jcsullins-tptoolbox-the-super-easy-way/
Now I am stuck with getting TP Toolbox to work. Novacom still installed on the windows 7 box, but not connecting to the touchpad.
I booted into WebOs recovery using the moboot selector, but...
Leaving the WebOS recovery was done then by pressing the home and power buttons simultaneously for about 20secs until the tablet rebooted.
I guess I have to move on, leaving WebOS because support ends January 2015 and even connecting to google mail is getting complicated under WebOS.
The current ROM is not working well, so I need an update. Any suggestions?
BTW: I thought to move on to JCSullins ROM, because the 20141231 build had good feedback regarding stability and number of bugs, especially energy consumption. Anyway it doesn't show up any more on the list of downloadable ROMS since yesterday.
Click to expand...
Click to collapse
Maybe ask in proper thread and not development. http://forum.xda-developers.com/showthread.php?t=1431949

Assuming at some time soon a mod will lock this or move it...but until then...
Might want to check out the Evervolv 5 (Lollipop) ROM. It's the latest version of Android, and for the most part works well on the Touchpad. Otherwise, jcusllins, milaq and a few others have sustainable builds that are worth using if you want to stay on Kit Kat.
Been using Evervolv 5 for everything but work e-mail due to missing encryption, but otherwise I have no real issues with the builds.
--McBean

Could solve the install task. The novacom service had to be enabled first.
I'm wondering why some guides claim to use ACMEuninstaller to uninstall Android first. Tptoolbox will wipe cache and data anyway, right?

[email protected] said:
Could solve the install task. The novacom service had to be enabled first.
I'm wondering why some guides claim to use ACMEuninstaller to uninstall Android first. Tptoolbox will wipe cache and data anyway, right?
Click to expand...
Click to collapse
Thats the only way we had until tp toolbox was released with that capability.

Ah, I see.
Novacom provides similar functions like ADB more (or) less.
TPTOOLBOX needs to be pushed first. After initial setup the recovery mods do the job to install other ROMs, right?
I got Philz CWRM on the tablet. Is TWRP preferable?
With the jcsullins from november I cant get bluetooth to work and battery drain is high. Especially compared to WebOS which let me have the tablet in sleep mode for a week or so.
Now battery is going down in half a day. I think I give the A6 flush from TPTOOLBOX a try as soon as the december ROM from jcsullins is back online again to solve the bluetooth issue.

Is there any OS that works ?

Hello .... I'm finding whatever OS I'm trying becoming unstable to use . So, I'm asking if there is any OS that is actually stable enough to use . I don't care whether it's an old version or what . I'm not using the tablet for games, just something I can browser the internet with . TIA

The one that has given me the fewest issues is https://forum.xda-developers.com/showthread.php?t=2712680 [ROM] [4.4.4] [CyanogenMod 11 by Jcsullins] [DM] [06/12/15]
everything works extremely well except the DSP manager when adjusting audio settings for the built in speakers where changes beyond the defaults do not have any effect on the audio.
Sadly many of the links are dead for things like gapps.
The ROM I use is cm-11-20151116-SNAPSHOT-jcsullins-tenderloin.zip
The gapps I use is: gapps-444-base-20160802-1-signed.zip
If needed, I can upload the gapps that I use though I am unsure if the forum has any rules surrounding it if I were to upload them to something like dropbox.
I try the others from time to time (easier for me since I really only use BSplayer and chrome in order to watch videos in a hover window while surfing the web (occasionally using my Bluetooth speakers or headphones).
Anyway, the main reason why I keep coming back to it, is the memory management. For many newer ROMs, you have issues such as the google calendar widget not working,or chrome not working properly, or when it is working, frequeny memory issues, especially if you want to upload an image to a site where it switches to the gallery app. by the time you select an image, it would fail to attach it because it will complain that the previous action could not be completed due to low memory.
With android 4.4, I do not have that issue. I don't know why it keeps happening for me since there are times when there will be over 100MB of free RAM, and chrome will still fail to do things with that error message.
Beyond that, the home screen under android 7.1.1 does not hold as many icons or widgets, even if you set the screen size to small, or adjust the dpi to 120. the home screen holds fewer icons and fewer widgets.
Overall, while it si great that newer versions of android are being supported, I feel that from a hardware standpoint then tablet has reached its limit with android 4.4
While there is also an evervolve version of android 4.4, for some reason it does not perform as well, even with more kernel features such as being able to overclock past 1.78GHz. it takes longer to boot, and some widgets do not work, along with issues with chrome.

https://forum.xda-developers.com/showpost.php?p=71176374&postcount=937
Check out the Nougat Evervolv thread. I've been using it, and it's fantastic.

Thanks for your input Razor512 .... And crazyates : Has this been updated since its first release, because when I gave it a go it was very unstable

Dude905 said:
Thanks for your input Razor512 .... And crazyates : Has this been updated since its first release, because when I gave it a go it was very unstable
Click to expand...
Click to collapse
Yes it has, but you need to download the nightly from their website. The XDA thread has an older version.
http://evervolv.com/devices/tenderloin

Ok, great news there crazyates. I installed evervolv from the YouTube guide, Do you know whether it still will work with those methods in the guide just as long I replace it with
ev_tenderloin-7.1.1-nightly-2017.03.03.zip and I believe you are using gapps-511-base-20161007-1-signed.zip , yes ? Thanks
YouTube >>> https://www.youtube.com/watch?v=ISWZ0c48gNA

Dude905 said:
Ok, great news there crazyates. I installed evervolv from the YouTube guide, Do you know whether it still will work with those methods in the guide just as long I replace it with
ev_tenderloin-7.1.1-nightly-2017.03.03.zip and I believe you are using gapps-511-base-20161007-1-signed.zip , yes ? Thanks
YouTube >>> https://www.youtube.com/watch?v=ISWZ0c48gNA
Click to expand...
Click to collapse
I'm not sure about the Youtube instructions, and I followed the written instructions on the forums.
Also, IIRC, if you're using a 7.1.1 ROM, you can't use a 5.1.1 Gapps. I would recommend downloading the newest 7.1.1 Gapps.
Here are the instructions I followed:
AlwaysLucky said:
If you end up having to start from scratch in TP Toolbox v0.42, follow these steps:
- Download a TP Toolbox Compatible ROM
- Download a TP Toolbox Compatible GApps
- Download a TP Toolbox Compatible TWRP
1. In the TP Toolbox v0.42 main menu, do a 'Complete Data Reset' to start from scratch
2. Select the 'Install Android' option from the main menu
3. Copy the 3 above files to the install folder after the TP is mounted
4. When given the option to adjust partition sizes, increase the System partition to at least 1312mb
5. Finish install, and reboot to TWRP
6. While in TWRP, flash the 9/6/16 TWRP 3.0.2.0 or the smaller 9/11/16 TWRP 3.0.2.0
7. Reboot into the new TWRP that you just flashed
8. In TWRP advanced wipe menu, wipe the System partition
9. While still in TWRP, flash the ROM from the OP along with some OpenGapps
10. Worship @jcsullins and @flintman, as they are your gods.
Click to expand...
Click to collapse
Here are the changes/differences I made/noticed:
crazyates said:
Step 3: While you're copying the older ROM/Gapps/TWRP into the "ttinstall" folder, I also copied everything you need for the new install into an "evervolv" folder. This way you can copy everything at once, and formatting a volume in TWRP doesn't destroy your install files.
Step 4: I have a 32GB TP, and don't use hardly any of it, so I increased the System to ~2GB, and the Cache to ~1GB. I figured going on the big side couldn't hurt.
Step 6: There's a newer version of Flintmans TWRP, 3.0.3.0(12/22/16).
Step 8: After you wipe the System, reformat the Data and Cache volumes as F2FS. Because your install files are on the External_SD instead of the Data, you can do this without recopying your install zips back again. I installed the system twice, once with Ext4 and once with F2FS. It feels snappier, and runs a lot better with F2FS.
Step 9: I used the Nightly build for the ROM, which is working great. Then the newest Gapps. Then I also flashed the SKZ overclock kernel at the same time.
Few other notes: Changing the Governor to LionHeart and Scheduler to Tripndroid made a noticeable difference for me. Also, because this doesn't have a lot of RAM, I gotta be careful with what I install, and how much I try to use it. Do NOT install Chrome from the app store. It will eat every bit of RAM available, and slow the whole thing down. I also use Greenify (with root permissions) to hibernate any app I can so it saves a lot of RAM that was as well. I'm using ~329MB (40%) for the system, with ~500MB (60%) available for apps.
Click to expand...
Click to collapse

@crazyates Did you try Evervolv 7.1 nightlies? I'm curious to read your experience feedback because I'm on it and getting tired of always having a non-responsive tablet. I might go back to 4.4 as I'll go mad otherwise.

bobcote said:
@crazyates Did you try Evervolv 7.1 nightlies? I'm curious to read your experience feedback because I'm on it and getting tired of always having a non-responsive tablet. I might go back to 4.4 as I'll go mad otherwise.
Click to expand...
Click to collapse
I am running the 7.1.1 nightlies. I haven't had any problems, and it's running very smooth. I'll randomly update it to the newest nightly, and haven't noticed any issues.
I do remember the time I first installed Evervolv 6.0 nightly last year. I installed it, and the touchscreen didn't work. At all. Looked into it, and it was a problem with that specific nightly build, so I went and reflashed everything with the one from the day before, and it worked great.
Anyways, all that to say it's working great, but it's still a nightly, so sometimes things go wonky.

I am still running a really old ICS build, and I noticed i can't update all my apps no more... what is the best Android version to run on the TP. Bluetooth is a must, but Camera isn't. Heard good things about 4.4.4 and 7.1.1, which one would you guys say runns smoother?

wprpalmeida said:
I am still running a really old ICS build, and I noticed i can't update all my apps no more... what is the best Android version to run on the TP. Bluetooth is a must, but Camera isn't. Heard good things about 4.4.4 and 7.1.1, which one would you guys say runns smoother?
Click to expand...
Click to collapse
Can't say much for 4.4.4, but I'm using 7.1.1 and it's great!
The only argument I could see making for 4.4.4 is if it runs a bit lighter than 7.1.1. These only have 1GB of RAM, so if 4.4.4 is capable of using less RAM for the android system, that means more RAM for apps. On the flip side, 7.1.1 uses such things as zRAM and KSM for better memory management, so it may be a wash.

crazyates said:
Can't say much for 4.4.4, but I'm using 7.1.1 and it's great!
The only argument I could see making for 4.4.4 is if it runs a bit lighter than 7.1.1. These only have 1GB of RAM, so if 4.4.4 is capable of using less RAM for the android system, that means more RAM for apps. On the flip side, 7.1.1 uses such things as zRAM and KSM for better memory management, so it may be a wash.
Click to expand...
Click to collapse
yeah, this is what I want to figure out. The developments in the Android codebase were quite extensive between these two releases, and the huge influx of budget phones in some markets (like mine for example) lead me to believe memory management would have been a key point in developing versions after 4.4.4. I'll give 7.1.1 a whirl and see how it goes.

Here are the instructions I followed:
...
Here are the changes/differences I made/noticed:
Click to expand...
Click to collapse
I tried to follow your instructions, but I get error messages like:
Error: unrecognized/unsopported zip 'FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.3.0-1-23-17.zip'
Error: Incompatible GAPPS/ROM versions None/7.0
I used the latest nightly (ev_tenderloin-7.1.1-nightly-2017.03.08.zip) and tried both open_gapps-arm-7.1-pico-20170312.zip and open_gapps-arm-7.1-pico-20170312, also I tried some of the TWRP-Versions you linked. I'm using TPToolbox v42 2015-01-08). So I wonder how you can figure out which versions fit together, I can remember this nagged me last time until I found a combination that worked...

AlwaysLucky said:
If you end up having to start from scratch in TP Toolbox v0.42, follow these steps:
- Download a TP Toolbox Compatible ROM
- Download a TP Toolbox Compatible GApps
- Download a TP Toolbox Compatible TWRP
1. In the TP Toolbox v0.42 main menu, do a 'Complete Data Reset' to start from scratch
2. Select the 'Install Android' option from the main menu
3. Copy the 3 above files to the install folder after the TP is mounted
Click to expand...
Click to collapse
Flexmaen said:
I tried to follow your instructions, but I get error messages like:
Error: unrecognized/unsopported zip 'FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.3.0-1-23-17.zip'
Error: Incompatible GAPPS/ROM versions None/7.0
Click to expand...
Click to collapse
Was that error message from TP Toolbox, or from TWRP? TP Toolbox won't recognize the newer TWRP images, nor will it recognize any 7.1 ROM/Gapps, so you need to use an older version to get things started. Once the older TWRP is installed, then you can use it to update to a newer version.
All in all, I had 8 ZIP files on my HP Touchpad to get a complete 7.1.1 install, but you can do it with as few as 6:
OLD ROM: CM 12.1
OLD Gapps: 5.1
OLD TWRP: 2.8.3.0
NEW ROM: Evervolv Nightly
NEW Gapps: 7.1
NEW TWRP: 3.0.3.0 F2FS
SKZ Kernel (Optional)
SuperSU (Optional)

Thank you! I installed the latest nightly, and it works fine so far.
The only thing I noticed that some apps now are blocking the device. This was also the case with the Android 4.4 Pac-Rom I used before. So it seems that some apps are using recources that aren't working well on the Touchpad at all, or that there is a general problem in several CM-versions.
For example the current version of Google Maps is so slow, you won't use it. I installend an older version (7.7.0), and this one works very fine. Also the new version of Maps lost the WiFi connection, which didn't cause any problem with the older version. So I wonder if there is some kind of incompatibility.
Another example: Fake GPS Location is much quicker than GPS-Emulator which also got stuck from time to time. Also the current Amazon App store was slooow.
Summary: Android 7.x runs fine so far, but you have to make sure that you get rid of the apps which block the device for some reason.

7.x is very slow some times.
Flexmaen said:
Thank you! I installed the latest nightly, and it works fine so far.
The only thing I noticed that some apps now are blocking the device. This was also the case with the Android 4.4 Pac-Rom I used before. So it seems that some apps are using recources that aren't working well on the Touchpad at all, or that there is a general problem in several CM-versions.
For example the current version of Google Maps is so slow, you won't use it. I installend an older version (7.7.0), and this one works very fine. Also the new version of Maps lost the WiFi connection, which didn't cause any problem with the older version. So I wonder if there is some kind of incompatibility.
Another example: Fake GPS Location is much quicker than GPS-Emulator which also got stuck from time to time. Also the current Amazon App store was slooow.
Summary: Android 7.x runs fine so far, but you have to make sure that you get rid of the apps which block the device for some reason.
Click to expand...
Click to collapse
When you say "blocking" you mean very slow? Since I uptaded from 4.4 to 7.x I've noticed that lots of apps are very slow. Some freezes for seconds and returns only when I block the device and turn on again. I dont know if its only on mine or its normal because of the old hardware. Is there any version that run real smooth? Or other system?

giolc90 said:
When you say "blocking" you mean very slow? Since I uptaded from 4.4 to 7.x I've noticed that lots of apps are very slow. Some freezes for seconds and returns only when I block the device and turn on again. I dont know if its only on mine or its normal because of the old hardware. Is there any version that run real smooth? Or other system?
Click to expand...
Click to collapse
Yes I mean very slow. Often so slow that it takes a minute until you can change to another app.
The Problem also existed on my 4.4 Pac Rom, so I guess it's rather caused by new apps who might expect some feature, like multicore, etc. Or it is some fault, that already existed in older custom roms. Not sure. However, I can recommend downgrading apps in this case, older versions often work like normal.

Flexmaen said:
Yes I mean very slow. Often so slow that it takes a minute until you can change to another app.
The Problem also existed on my 4.4 Pac Rom, so I guess it's rather caused by new apps who might expect some feature, like multicore, etc. Or it is some fault, that already existed in older custom roms. Not sure. However, I can recommend downgrading apps in this case, older versions often work like normal.
Click to expand...
Click to collapse
Perhaps using F2FS could help, if not currently using it?

crazyates said:
Was that error message from TP Toolbox, or from TWRP? TP Toolbox won't recognize the newer TWRP images, nor will it recognize any 7.1 ROM/Gapps, so you need to use an older version to get things started. Once the older TWRP is installed, then you can use it to update to a newer version.
All in all, I had 8 ZIP files on my HP Touchpad to get a complete 7.1.1 install, but you can do it with as few as 6:
OLD ROM: CM 12.1
OLD Gapps: 5.1
OLD TWRP: 2.8.3.0
NEW ROM: Evervolv Nightly
NEW Gapps: 7.1
NEW TWRP: 3.0.3.0 F2FS
SKZ Kernel (Optional)
SuperSU (Optional)
Click to expand...
Click to collapse
I guess there is a "new" method out there that can install Nougat 7.1.1 in as little as 3 zip files!!!
check it out, it comes with instructions and a new video...
I can name that tune in 3 zips!!

DoubleStuff said:
I guess there is a "new" method out there that can install Nougat 7.1.1 in as little as 3 zip files!!!
check it out, it comes with instructions and a new video...
I can name that tune in 3 zips!!
Click to expand...
Click to collapse
It doesn't work for me ... I'm having issues . First off I like to ask why he didn't use the latest Rom ? And the part with go to the PC Mounted Touchpad internal drive for the TWRP ? When I open the TWRP folder I don't see twrps file, why not ? There nothing in this folder, its empty . What I done was just placed those zip files in the TWRP folder . Afterwards once I do the final reboot to Evervolv it will just show those Evervolv lights flashing like its trying to load up but it doesn't, it just keeps continuously trying to load but it never does

[Sofia(p)(r)][Recovery][WIP] TWRP 3.4.0.0

vache said:
Here you go : https://drive.google.com/file/d/1x4t6ca8TLf1bNHrQa-jjCN_AhdV2W78u/view?usp=drivesdk
Boots on sofia (g power), sofiar (g8 power), sofiap (g stylus), sofiap_ao (g pro)
Click to expand...
Click to collapse
I started the thread, but did not make this build. Everything should work. Thank @vache.

Quick update I did get TWRP to build successfully. Unfortunately it just sits on the boot logo but doesn't go back to fastboot, but that was just a quick see what happens build. I haven't added everything I need to yet. Will work on it more tonight, but progress is good so far.

@CodyF86 thanks for taking the lead on porting TWRP to the G Power. The G Power appears to be the best "bang for the buck" phone on the market currently, and has been widely covered by the media so far. I expect that the Moto G Power sub will grow steadily in the upcoming months, leading to custom rom development for the G Power. Having TWRP ported would be a start to paving way for custom rom development.

So another quick little update. I have the device repo basically where it should be...give or take heh. It's changed a bit from what is on my github, but it's pretty close. The only issue i'm having is that compiling it with the minimal manifest isn't going to work. It doesn't compile right. It compiles, but it doesn't copy things over correctly and/or at all depending on what it is.
My repo is pretty close to what the moto one power and the g8 power have, at least for their android 9 device tree, and I can get TWRP to boot, if I use the moto one power image and just dump the moto g power kernel into it.
So short version is i'm downloading the full manifest, basically all of Omni, which should hopefully sort it out. It's downloading right now.
EDIT:
Actually it helps to read the documentation I guess lol.
https://source.android.com/devices/bootloader/system-as-root#using-vendor-overlay
Will keep playing with it.

This is exciting! Thanks for your hard work.

CodyF86 said:
Will keep playing with it.
Click to expand...
Click to collapse
Thank you for taking this on! Having TWRP recovery for "sofia" will really make this phone great!

GoodOlDan said:
Thank you for taking this on! Having TWRP recovery for "sofia" will really make this phone great!
Click to expand...
Click to collapse
I "should" have it working in a day or two...(or even tonight...) The Code Aurora repos have been helping greatly.
https://source.codeaurora.org/quic/la/platform/vendor/qcom/trinket/tree/BoardConfig.mk?h=LA.UM.8.11.r1-03800-NICOBAR.0

Quick question, is the Moto g power the same as Moto g8 power? If they get custom Rom they'll unified? From what I know, the g power is the us variant release of the g8 power, right?. Thx in advance

Been making changes and even trying to repack some files from our devices into chef from when I got chef to boot with a repacked kernel but the touch screen wouldnt work and it couldnt see any partitions really.
Part of the problem seems to be the build system. It's not populating the output image fully. It's not even putting the TWRP directory in there lol.....
Going to keep trying. Going to try to find a native android 10 device that has twrp working unless there isnt one yet. Also our device is a little different it actually puts certain things in /system where in android 9 they went into /vendor. Spent about 3-4 hours on it today, but not going to give up.
I think there is an issue with the OMNI build system though also.

CodyF86 said:
Been making changes and even trying to repack some files from our devices into chef from when I got chef to boot with a repacked kernel but the touch screen wouldnt work and it couldnt see any partitions really.
Part of the problem seems to be the build system. It's not populating the output image fully. It's not even putting the TWRP directory in there lol.....
Click to expand...
Click to collapse
HI, I'd be willing to help with this, I'm a developer, I worked with @tecknight on TWRP for a phone called the Wiko Ride. We never quite got a working TWRP but learned quite a bit about AVB and such. I've already got my Sofia (US unlocked retail, running on Boost Mobile) rooted and could use a new challenge.
I too have been quite baffled by the Android build process at times - the docs that exist seem to assume a LOT of prior knowledge - the barrier to entry seems higher than ordinary Linux kernel hacking by quite a bit.

rlrevell said:
HI, I'd be willing to help with this, I'm a developer, I worked with @tecknight on TWRP for a phone called the Wiko Ride. We never quite got a working TWRP but learned quite a bit about AVB and such. I've already got my Sofia (US unlocked retail, running on Boost Mobile) rooted and could use a new challenge.
I too have been quite baffled by the Android build process at times - the docs that exist seem to assume a LOT of prior knowledge - the barrier to entry seems higher than ordinary Linux kernel hacking by quite a bit.
Click to expand...
Click to collapse
Look at my github you can see the cluster ef of changes I made to at least get to a console. Ironically if you repack the kernel into the chef version of TWRP it boots to the GUI but the touch screen doesnt work.. Our device is weird although it is android 10 native but it has a /system folder. Also on android 10 you can just add things to the vendor partition without using the product partition as an overlay.
Unpack the stock recovery. I went back to the basics and am basically going to mirror the stock recovery then inject the twrp binary, but its weird, the omni build system isnt doing some things correctly it seems also.
This will be your greatest resource. Code Aurora has the answers.
https://source.codeaurora.org/quic/la
https://source.codeaurora.org/quic/la/platform/vendor/qcom/trinket/tree/?h=LA.UM.8.11.r1-03800-NICOBAR.0
https://github.com/codyf86/device_motorola_sofia
LA.UM.8.11.r1-03800-NICOBAR.0 is our current CAF version tree.
Actually I just started the repo over the commits were nasty. Everything important and pertinent is in the initial commit now.
Ive been compiling and hacking kernels for 10 years, building Android for probably the same and this switch to the new partition layout + TWRP has so far been the... I don't want to say hardest but longest thing i've tried to do without any forward movement.
Like I said I got farther just by repacking the our kernel into the moto chef kernel, but they have a system_root directory and we dont. We just have system.
Theyre lib64 goes in /vendor ours goes in /system.
unpack the stock recovery image to start also TWRP uses init.qcom.recovery.rc to do things on the init and init.rc hand off where as stock recovery version of that file is different.

Actually I know partially why it wont boot. I have the paths in the init.recvoery.qcom.rc messed up, but also [email protected] doesn't exist in our lib64/hw directories, but there is a [email protected] file in the stock recovery so going to try that, plus were building bootctrl.trinket.

Nm i found the -service binaries for the boot gatekeeper keymaster libraries etc. think I made some progress but I have to build it and make sure everything gets in the right spot. will keep on keeping on.

The current code I have on my github will boot the stock recovery lol (the build system is being weird)....the build system isn't putting things in the right spot still. I was able to get TWRP to boot by rearranging some things manually, but it isn't pretty. So there is some progress, but the build system is part of the problem at this point at least for android 10. I'm still working on it.

CodyF86 said:
The current code I have on my github will boot the stock recovery lol (the build system is being weird)....the build system isn't putting things in the right spot still. I was able to get TWRP to boot by rearranging some things manually, but it isn't pretty. So there is some progress, but the build system is part of the problem at this point at least for android 10. I'm still working on it.
Click to expand...
Click to collapse
Hey, do you have a telegram account for easier conversing? I feel we might be able to help each other here?(I'm working on sofiar)

Dark98 said:
Hey, do you have a telegram account for easier conversing? I feel we might be able to help each other here(I'm working on sofiar)
Click to expand...
Click to collapse
I can make one and ill dm you.
Here are my questions so far / some observations.
The init.rc that the twrp build system puts in the build is incorrect. It needs to be manually added...I think there is a flag for that actually, but I had to change it once it was built. (I was able to make it boot to the first screen by dropping in things in /sbin from https://github.com/TeamWin/android_device_motorola_chef)
The build system doesn't add the twrpres folder to the built image lol; or the twrp binaries to /sbin.
I literally had to copy them over from chef.
Also for example servicemanager and hardwaremanager aren't in the chef repo but they are in /sbin when you unpack the recovery image (chef), is the build system building them or putting them in from somewhere or are the repos not actually the final product and they had to hack the image a bit too.
I had ours added in then took it out when I couldnt find them in anyones device tree but they are there when you unpack all of the recovery images lol.
edit: It's actually putting most of the stuff (adbd) and symlinks in /system/bin including the recovery bin which is twrp, so let me readjust the init scripts.
our device is different it still has /system and not system_root.
another edit: Looking at android_bootable_recovery/crypto/ex4crypt I think im missing some libraries still.

Okay, if/when you do message me on there please, I hardly check XDA other than when I'm updating a Rom I maintain? @Dark998 is my username

@CodyF86
Interested and surprised to see that twrp for native android 10 is in the works.
After reading Dees Troy's article in late 2019 regarding twrp on android 10, I had resigned myself to the notion that twrp is more or less dead for android 10+...
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Hope you're able to get it working!

Q9Nap said:
@CodyF86
Interested and surprised to see that twrp for native android 10 is in the works.
After reading Dees Troy's article in late 2019 regarding twrp on android 10, I had resigned myself to the notion that twrp is more or less dead for android 10+...
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Hope you're able to get it working!
Click to expand...
Click to collapse
I was absolutely able to get it to boot with adb up but with no touch screen and it couldn't see any paritions, but ive adjusted the fstab file.
Also slightly embarassed to say I repo synced and forgot to drop twrp 10 back in, but i need a libinit with twrp 10 and it actually gave me a couple solutions to that accidentally doing that, accidentally building aosp recovery once time lol xD

CodyF86 said:
I was absolutely able to get it to boot with adb up but with no touch screen and it couldn't see any paritions, but ive adjusted the fstab file.
Also slightly embarassed to say I repo synced and forgot to drop twrp 10 back in, but i need a libinit with twrp 10 and it actually gave me a couple solutions to that accidentally doing that, accidentally building aosp recovery once time lol xD
Click to expand...
Click to collapse
I was thinking that if twrp isn't possible, how difficult would it be to modify stock recovery to remove signature verification?
With stock recovery signature verification disabled, at least side loading would be possible. Thoughts?
Also, I'm willing to help test if needed