----------------------- Thread MODIFICATION LOG -----------------
Shout out to Nevertells2 and DoubleStuff who both worked hard on this documentation in 2017. ( Some of which still remains )
Date:03/10/2017 Users: DoubleStuff/Nevertells2
Modification Description: Initial Release.
05/25/2019 DoubleStuff
Major changes in 2019: updated broken ROM/GApps by including HP_TOUCHPAD's master list of ROM/GApps, also fixed the YouTube broken link, made many additions to the documentation as per the changing landscape of the HP Touchpad development, most notably HP_TOUCHPAD's HpTp Universal Optimize Swap Settings and boot.img file.
07/08/2019 DoubleStuff
Created a Main Menu, with 2 options 1) Wipe All and 2) HP ToolBox.
8/3/2019 DoubleStuff
Implemented HP_TOUCHPAD's ROM_Reducer flash files.
8/27/2019 DoubleStuff
On the 2nd Post of this thread I added DoubleStuffs annotated journeys.
8/27/2019 DoubleStuff
On the 3rd Post of this thread I added HP_TOUCHPAD's advanced topic of the HP TOUCHPAD Novacom Repair Android Tool.
----------------------- Previous Zip Statistics -----------------
"The Original"
Obsoleted doubleStuff_v03.zip 3/19/2017 - 5/25/2019 ( RIP )( 797 days )( 7876 downloads )( 53306 views )
Avg. 9.87 downloads/day
"Double Stuff II"
Obsoleted DoubleStuff.2019.zip 5/25/2019 - 7/8/2019 ( RIP )( 045 days )( 372 downloads )( 3140 views )
Avg. 8.26 downloads/day
----------------------------------------------------------------------
Introduction:
In this "new" ( circa 2019 ) method of "starting from scratch", or called "clean installing", the user will flash various ZIP files depending on the ROM version user wants to install.
The actual install of Automatic_Wipe_All_and_Create_Android_with_Swap_Partition.zip ( boot.img ) will be done by the the script TPTB_WipeAll_TWRP_v02_win.bat. Wipe_All creates a 500 Mb swap partition, and re-creates the system, cache, media and data partitions with sizes of 2200 Mb, 200 Mb, 500 Mb, and "rest of memory" respectively, also automatically installs version 3.2.1-0 of TWRP which is required for the other ZIPs.
Boot partition is always 32 Mb, its a fixed size.
To be clear: this method will erase everything, even WebOS and makes the HP Touchpad 100% Android. It will also create new media, cache, data, system and SWAP partitions, and make the HP Touchpad work as a tablet ( laptop with a touch screen ), not a smartphone in Android.
Thoughts about the video:
The Video is now semi-obsolete, because alot has changed since 2017. So you must follow the instructions in this updated thread, but the video helps because if you understand the video you will understand the instructions in this thread. The Video below is Installing Nougat, but you can use this method for ALL VERSIONS of Android since 4.4 just use the proper ZIPs.
https://www.youtube.com/watch?v=KDu1bocZHqw
Assumption:
This method assumes you already loaded and have working TP Toolbox v0.42. ( w/Novacom and Java )
--- if you don't have TP Toolbox installed on your PC please watch the video in RolandDeschain79's link from 0:00 to 2:15 RolandDeschain79Link
======================================================================
Steps to success for loading any version of Android since 4.4:
Perform the following steps on a PC to prepare it for load:
I. Download the NEW DoubleStuff.7.2019.zip:( click link below )
Download DoubleStuff.7.2019.zip
DoubleStuff.7.2019.zip contains these two key files:
1. TPTB_WipeAll_TWRP_v02_win.bat
2. uImage.WIPE
Download and extract, and place both files in the same directory as your working tptb_v42_win.bat on your PC.
II. Select and Download which version of Android ROM, Gapps and other zips you want.
Locate and download the ZIPs: I will link to HP_TOUCHPAD's Master List of Zips: ( see Master list link below ), but you can also find ZIPs in other XDA HP Touchpad threads too.
Its best to put your downloaded ZIPs into a storage folder that you have created on your PC, purely for organization.
#1 ) ROM
#2) Pick one of these three Settings files for this #2 ZIP install: These files are in the "ALL files for this ROM" zip, then look under a folder of the same name, and then select the frequency zip of your choice.
-- MAX_Kernel_Ramdisk_build_prop_Settings ( Latest HpTp_MAX_Universal_Optimize_Swap )
-OR-
-- Stock_Kernel_Changed_Ramdisk_build_prop_Settings ( HpTp_Universal_Optimize_Swap )
-OR-
-- Original_ROM_Settings ( Use the Tablet with phone settings, no swap partition )
( The first two are the magic behind the performance and speed, because these settings enables Android to use the swap partition, the third is the original settings for the ROM and you will have better battery performance. )
All the Universal Optimize Swap Settings files provide the same settings and kernel, the difference is the preset CPU frequency. As per the Boost settings always start with 1674, and after that is working good, you can try to flash a higher frequency for speed like ( 1728, 1782 or 1836 ), and you don't have to re-flash all the ZIPs again, just the UOSS file from TWRP recovery. If it freezes screen, or keeps rebooting just go back and flash lower frequency, Because those symptoms are telling you that your particular HP TOUCHPAD can't handle the higher speed.
#3) ROM Reducer ( Optional ) These files are in the "ALL files for this ROM" zip, then look under the folder with name "ROM Reducer" then out of the 3 zip files in the selected folder, first go with the ROM_reducer, later if you want to permanently remove the features/apps, or restore the features/apps, you can use the "Remove" and the "Restore" zip files.
Essentially this HP Touchpad ( circa 2011 ) has around 650 MB of free RAM (Memory), this is relatively low, so the ROM Reducer flash file "removes" some Android Features and System Apps to give the old Touchpad some extra needed RAM. So in theory this will make for a faster experience.
#4) GApps
Select platform ARM and the android version that matches ROM and the variant you want, Pico is recommended. The goal is to keep the system "lean and clean", and by doing this you will get the best performance and efficiency.
#5) SuperSu v2.82 ( Optional )
ROMs have system Read and Write enabled, download and flash SuperSu v2.82 if you want root access.
#6 ) Latest TWRP ( Optional, but if you want and/or need a different version of TWRP other than 3.2.1-0, then you need to download one. )
==========HP_TOUCHPAD's Master Link: Get ZIP ( #1, #2, #3, #4 here )===========
Note: Once you click link, you have to press page down 3 times to get to the Master List of Zips.
Find all Android version: Rom, GAPPS, HpTp MAX Universal Optimize Swap Settings, and more links as per HP_TOUCHPAD here:
================Get ZIP ( #5 here )=============================
***You can Download and Flash the latest SuperSu zip to ROOT your device***
Root access with SuperSu v2.82
http://www.supersu.com/download
================Get ZIP ( #6 here )=============================
This "latest and greatest" TWRP for ALL VERSIONS OF ANDROID.
Download Permanent TWRP Recovery.
FLINTMAN-TWRP-3.2.1-0-03-15-2018.zip
Stick with the package you select, don't mix and match versions, and stay with WIFI version unless you know better.
Set all ZIPs that you have downloaded into the storage folder on your PC for now, we will need them later.
III. Touchpad/PC Execution steps:
Boot into WebOS Recovery ( giant USB symbol ) with cable connected to PC.
Run the custom script TPTB_WipeAll_TWRP_v02_win.bat:
It will give you the option of running the TPTB where you can perform some maintenance steps. Most users will select '1' to run WIPEALL from Main Menu.
III. Touchpad/PC Execution steps: continued
Most users will START here, after pressing '1' in Main Menu.
Continue ( press "c" ) with the TPTB_WipeAll_TWRP_v02_win.bat, it will then load the uImage.WIPE, you should see a quick blue flash, and an orange header with some white text. Wait until the orange header disappears, it will then automatically reboot. ( about 2 minutes ).
At reboot, select Recovery on moboot menu, then press home key.
Wait, and you will see the automatic load of 3.2.1-0 TWRP recovery.
Wait, and you will see Touchpad drive mounted on your PC.
TWRP recovery automatically creates a folder in the /data/media directory called TWRP, on the Internal SD card ( data ).
IV. TWRP Install steps:
( If screen falls asleep, and power and home buttons don't respond, tap screen )
Once in TWRP Recovery, go to your PC which is still connected via cable to TouchPad:
Locate the storage folder on your PC where you stored your ZIPs.
Copy the ZIPs: ( drag and drop )
1) ROM, 2) Universal Optimize Swap Settings 3) ROM Reducer 4) Gapps, 5) SuperSu and 6) Permanent Recovery zip files into the /Touchpad/InternalStorage/TWRP mounted Touchpad volume.
( P.S. actually you can copy the zips anywhere in 'Internal Storage' or 'Micro SDCard' Touchpad mounts, as long as you know where to find them on your Touchpad, I am just giving you the default location for simplicity sake )
2) Once copy is complete, you can disconnect the USB cable from the PC and Touchpad.
3) These zips will then show up in the /sdcard/TWRP or /data/media/TWRP directory on your Touchpad.
4) Select INSTALL from TWRP, drill to /sdcard/TWRP directory, then load in this specific order ( pressing 'add more zips' between loads )
== ROM,
== HpTp Universal Optimize Swap Settings,
== ROM Reducer,
== Gapps,
== SuperSu
== Recovery TWRP
then swipe to flash.
It will take awhile for the system to flash these zips ( about 5 mins ) until the reboot option shows up.
press reboot system button
At Moboot menu I selected "boot Evervolv" your menu item might be a different name depending on the ROM you installed.
During my experimental testing I loaded Evervolv Nougat and it took about 15 additional minutes until I got to the Android Start screen after "boot Evervolv" selected. Mileage may vary.... but soon your HP Touchpad will be in the promised land of Android with swap.
Advanced Topic #1:
DoubleStuff's Journeys to Novacom Repair Android Tool and Universal Authority: ( with annotated pictures!! )
Journey #1: How files get populated to /boot.
Journey #2: into HP RAMDISK: Using /boot from uImage
Journey #3: to Novacom Repair Android Tool: How are the icons made
Journey #4: Exploring Planet Universal Authority
Journey #5: RAM Memory Stress Test
...
..
Advanced Topic #2:
HP Touchpad Novacom Repair Android Tool
Hello Touchpad users, if you think your HP TOUCHPAD is bricked, your probably wrong and with the tools below you maybe able to fix your HP TOUCHPAD and make it like new again. Read the guide, and download the ISO file, now remember this is an advanced topic, its not for kids. Trix are for kids.
click HERE for guide
click HERE to download ISO file
...
..
Doublestuff, bringing this to this thread since I am using your instructions to get this far.
After using the 4/13 nightly and getting setup wizard has stopped I tried the 4/6 as indicated below.
The steps I have taken are to use tptb_v42_win.bat for the toolbox to wipe the data then resize volumes to
--Media: 1024 MB,
--Cache: 200 MB,
--System: 1312 MB,
--Data: the rest of the memory
Then after shutting that down and bringing up the big USB symbol using the volume and power button again to run TWRP_TmpLoad_v03_win.bat and copy the files below into the TWRP folder on the touchpad.
ev_tenderloin-7.1.2-nightly-2017.04.06.zip
open_gapps-arm-7.1-pico-20170415.zip
FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.1.0-0-3-24-17.zip
Once the files were copied over I disconnected from the PC and added to the install in the order above.
The install indicates no MD5 so a check is skipped and seems to proceed to install each of the three zips fine. When I get to the end of that there are two buttons (one to wipe cache/DavLik and the other to Reboot). I tried both with and without the wipe cache before the reboot with the same results.
After the Evervolve logo with the cycling colored letters goes for a few minutes it gets to the setup screen, clicking on either copy settings or start new setup give the error "Setup wizard has stopped, Open app again" then "Setup wizard keeps stopping, close app".
The only difference I can see I resized the Media to 1024 where your instructions indicate 1000 but I cant see that as being any problem though to be honest my knowledge here is limited.
Any ideas for something else to try are appreciated.
----------------------------------------
This part I dont think I am understanding
"but remember later on you still have to load the permanent TWRP with install."
W_three said:
Doublestuff, bringing this to this thread since I am using your instructions to get this far.
After using the 4/13 nightly and getting setup wizard has stopped I tried the 4/6 as indicated below.
The steps I have taken are to use tptb_v42_win.bat for the toolbox to wipe the data then resize volumes to
--Media: 1024 MB,
--Cache: 200 MB,
--System: 1312 MB,
--Data: the rest of the memory
Then after shutting that down and bringing up the big USB symbol using the volume and power button again to run TWRP_TmpLoad_v03_win.bat and copy the files below into the TWRP folder on the touchpad.
ev_tenderloin-7.1.2-nightly-2017.04.06.zip
open_gapps-arm-7.1-pico-20170415.zip
FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.1.0-0-3-24-17.zip
Once the files were copied over I disconnected from the PC and added to the install in the order above.
The install indicates no MD5 so a check is skipped and seems to proceed to install each of the three zips fine. When I get to the end of that there are two buttons (one to wipe cache/DavLik and the other to Reboot). I tried both with and without the wipe cache before the reboot with the same results.
After the Evervolve logo with the cycling colored letters goes for a few minutes it gets to the setup screen, clicking on either copy settings or start new setup give the error "Setup wizard has stopped, Open app again" then "Setup wizard keeps stopping, close app".
The only difference I can see I resized the Media to 1024 where your instructions indicate 1000 but I cant see that as being any problem though to be honest my knowledge here is limited.
Any ideas for something else to try are appreciated.
----------------------------------------
This part I dont think I am understanding
"but remember later on you still have to load the permanent TWRP with install."
Click to expand...
Click to collapse
Go have a read at this page in the DevsBase forum if you haven't already. It is discussed that there have been problems with the setup wizard.<Mod Edit: Link removed. Please don't redirect members to other mobile forums. Thanks!>
Also, I see in the discussion there that the nightly builds are now 4/13 so you might try that date build and see if the problem has gone away. I also saw discussed that some folks there were installing older builds that did not have the setup problems and then using TWRP to flash the newest builds. Otherwise, from what you posted, you are doing everything right.
NT
W_three said:
The only difference I can see I resized the Media to 1024 where your instructions indicate 1000 but I cant see that as being any problem though to be honest my knowledge here is limited.
This part I don't think I am understanding
"but remember later on you still have to load the permanent TWRP with install."
Click to expand...
Click to collapse
As long as the Media is greater than 1000 MB it should be OK.....
Essentially the program TWRP_TmpLoad_v03_win.bat loads TWRP temporarily by using a novacom command to load uImage.TWRP to the HP Touchpad, but you still have to download and have as one of your 3 zips something like this FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.1.0-0-3-24-17.zip, so that you can have a permanent load of TWRP after all is said and done.
Hey guys! Went through all of these steps and got it to boot! However, after it booted for quite a while, it started up the setup wizard, and immediately stops whenever you choose an option, whether it be "Set up as new" or "copy your data."
Is it something I've done wrong? Any help would be appreciated!
Seatreader said:
Hey guys! Went through all of these steps and got it to boot! However, after it booted for quite a while, it started up the setup wizard, and immediately stops whenever you choose an option, whether it be "Set up as new" or "copy your data."
Is it something I've done wrong? Any help would be appreciated!
Click to expand...
Click to collapse
No your not doing anything wrong, the new nightly builds are going through a particularly buggy phase the last few builds. I am assuming you used the 4-19 nightly. Lets try an earlier Testing build.
If you have time, just for kicks and for testing purposes can you try again but use Flintmans latest testing 3-25 ROM instead of the Evervolv Nightly.
Try this ROM and lets see if it fixes the issue:
http://evervolv.com/static/builds/testing/Queo/ev_tenderloin-7.1.1-testing-2017.03.25.zip
If you notice the user "w_three" had the same issue in an earlier post on this thread....
okay I'll give that a go tonight! I noticed on the release page forums they were talking about how you had to dirty flash the newer roms on and figured that was my problem.
=UPDATE=
Ran as per the instructions with a nice clean install and it booted fine! Takes forever to boot and get through the" finishing touches" but it looks like it's working fine!! Four days ago this tablet was bricked!
Thanks for all the help!
After letting this rest for a few days I decided to give it another go.
Used the 3/25 zip you posted above DoubleStuff and finally past the set up error. Going through it now. Thanks for posting that Rom.
W_three said:
After letting this rest for a few days I decided to give it another go.
Used the 3/25 zip you posted above DoubleStuff and finally past the set up error. Going through it now. Thanks for posting that Rom.
Click to expand...
Click to collapse
Great! W_three, that you finally got it working, from what I have been reading on devs-base, Open Gapps are only running through 7.1.1, and as of April 4th (4/4) Evervolv nightlies have switched to 7.1.2. ( see pic below ) Some people have a theory that this is causing the set-up wizard to break. To get around this issue, some people have been "clean" flashing an older 3-25 ROM see link to that in post #8 ( or in theory anything before 4/4 nightly ), then "dirty" flashing the newer ROMs on top of that. I am just reporting on what I read, not sure how accurate it is.
See in below screenshot how name changes from 7.1.1 ( green ) to 7.1.2 ( red ).....just sayin'
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just know that this Nougat ROM is still only in Beta, so there will be bugs and lagginess.
As Nevertells2 would tell anybody, JC Sullins KitKat 4.4.4 ROM is probably the most stable.
Setup Wizard fails
My Setup Wizard fails and I see the note below:
*NOTE: as of 4/4 since start of 7.1.2, if your having issues with setup wizard after the install you might want to flash this older ROM instead ( before 4/4 ), then dirty flash a newer ROM
How do I perform this?
How do I flash with a older ROM (before 4/4) and then dirty flash a newer ROM? Can you elaborate?
Thank you in advance.
xdakzhf2d said:
My Setup Wizard fails and I see the note below:
*NOTE: as of 4/4 since start of 7.1.2, if your having issues with setup wizard after the install you might want to flash this older ROM instead ( before 4/4 ), then dirty flash a newer ROM
How do I perform this?
How do I flash with a older ROM (before 4/4) and then dirty flash a newer ROM? Can you elaborate?
Thank you in advance.
Click to expand...
Click to collapse
Well underneath that red letter explanation in the Original Post, is a link to a 3-25 ROM, flash that using the alternative method described in OP. That is called a clean install.
Then once you get that going, you can dirty install the current 5-8 ROM, by selecting this once tablet is running:
Settings->About Tablet->Evervolv Updates->Nightly Tab->Refresh, then download the zip, and boot into recovery and flash it. If you don't understand this terse explanation, I have pasted RolandD's How to dirty flash and root video below ( from 1:19 to 3:17 is Dirty Flash )
Dirty Flash Instructions
Hi, Ive ran each step as instructed twice, just to be sure. both times I get only an external sd card selection, no internal card or data selection once files load and I run twerp it installa yet I get a failed to mount data invalid argument. what am I doing wrong?
deafasheck said:
Hi, Ive ran each step as instructed twice, just to be sure. both times I get only an external sd card selection, no internal card or data selection once files load and I run twerp it installa yet I get a failed to mount data invalid argument. what am I doing wrong?
Click to expand...
Click to collapse
Hello deafasheck, I have been following you on these boards for years, and you always get errors and issue that are different from the norm. LOL
In fact you even call J.C. Sullins by an unusual name ( JC Sullivan ) LOL, but I have seen Nevertells2 correct you a few times, so I think we are good to go there.
As far as your issue, did you load the 3-25 ROM first? Then try to dirty flash the latest nightly? I would like to know more details on the procedure you used. But you maybe in luck, because I think there is another thread today that has a similar ( mount and volume issues ) and RolandD gave him a answer and a few links...
Look HERE at post #1094
Missed a step.
Hi DoubleStuff, yeah I'm way out of my league, but have learned so much in forum, I found out what I done wrong. I didn't move file size in data only moved cashe and system to as close as could to instructions. it fixed right up once I put data size, I noticed cam still inverted, does new ROM resolve that? I'm going back and dirty flash that ROM I ove the size if this, it doesn't take up much space has less bloatware and I use UC browser which is so so Philz kk is best I have tried . but I'm gona toy on this one Ive almost mastered this touchpad insyallations even learning codeing, just not yet.. I do dislike the home launcher, so used to having one like the one in kk or nova. Ive not bricked mine yet! was worried for awhile. but any thing I need to know is on here . thanks for the reply..
im still learning how to post specs of tablet. JC Sullin huh? yeah, Im good on typos. dang laptop mouse jumps around.. well here we go, going to dirty flash newest rom, wish me luck.. thanks..
DoubleStuff said:
Hello deafasheck, I have been following you on these boards for years, and you always get errors and issue that are different from the norm. LOL
In fact you even call J.C. Sullins by an unusual name ( JC Sullivan ) LOL, but I have seen Nevertells2 correct you a few times, so I think we are good to go there.
As far as your issue, did you load the 3-25 ROM first? Then try to dirty flash the latest nightly? I would like to know more details on the procedure you used. But you maybe in luck, because I think there is another thread today that has a similar ( mount and volume issues ) and RolandD gave him a answer and a few links...
Look HERE at post #1094
Click to expand...
Click to collapse
deafasheck said:
Hi DoubleStuff, yeah I'm way out of my league, but have learned so much in forum, I found out what I done wrong. I didn't move file size in data only moved cashe and system to as close as could to instructions. it fixed right up once I put data size, I noticed cam still inverted, does new ROM resolve that? I'm going back and dirty flash that ROM I ove the size if this, it doesn't take up much space has less bloatware and I use UC browser which is so so Philz kk is best I have tried . but I'm gona toy on this one Ive almost mastered this touchpad insyallations even learning codeing, just not yet.. I do dislike the home launcher, so used to having one like the one in kk or nova. Ive not bricked mine yet! was worried for awhile. but any thing I need to know is on here . thanks for the reply..
im still learning how to post specs of tablet. JC Sullin huh? yeah, Im good on typos. dang laptop mouse jumps around.. well here we go, going to dirty flash newest rom, wish me luck.. thanks..
Click to expand...
Click to collapse
Hello deafasheck, I am glad your learning and taking the advice of Nevertells2 which is "read, my friend, read!!"
Yes the Stock Camera is still inverted, but haven't you heard? That if you go to google play store and download "Open Camera" app it works fine in Nougat, let me know what you think of it. I am glad you figured out your own problem that is telling me you are learning quite a bit since you were a "newbie" in 2014!! :good:
OK deafascheck I wish you luck in your dirty flash download? And your experiment with "Open Camera" and hope you learn how to code at least in BAT and VBS files, because when Oreo ( Android "O" ) comes out we will need to tweek the code for this Alternative method again!! I am doubling down that its called Oreo, hence my Avatar.
Thank you so much, yes got to learn code and terminal commands. on the subject of dirty flash, is that same as loading the via tptb as I did with the permanent files when Initial install ?
deafasheck said:
Thank you so much, yes got to learn code and terminal commands. on the subject of dirty flash, is that same as loading the via tptb as I did with the permanent files when Initial install ?
Click to expand...
Click to collapse
deafasheck, defasheck, defasheck, come on now we have been studying "dirty flashes" since you were a "newbie" in 2014, and our friend RolandD has made many videos on it....in fact in this ROM alternative thread in post #13 at the bottom of the post is a good video that explains "dirty flashes"....learn it, love it, live it!!!
Good Luck in all your learning Deafasheck!!! :highfive:
POST #13 for deafasheck learning dirty flashes.
Videos don't help much, I'm deaf as heck.. and getting lost in the steps.. from what I recasll dirty flash is asop I did one as I had in the original install ie placed in twerp flashed from twerp. that worked as far as I know? I'm trying to find the super user link I seen earlier, once I get ROM and SU I'm gonna get the camera app. thanks..
Related
Hello guys.
I just got a brand new TouchPad 32GB. WebOS is very nice, but there are not many applications, so I'm trying to intall CM9.
I have all the drivers installed correctly, I can put the touchpad in developer mode, and USB mode
Problem is, MOST of the links on the guides are outdated. I tried guides here, guides on rootwiz, guides on XDA.
So I started looking for the files myself, and now I have.
e0664157ed69f8999e1c3ee77cdc53ae ACMEInstaller2
7b49b53a9d70315c40dccde9fc20e7a9 ACMEInstaller3
7642f3f0a8090dc52445541a94ed8164 cm-9-20120816-NIGHTLY-tenderloin.zip
980139d6b46b9cbba4db0e07ad17ba5d moboot_0.3.5.zip
1308300f38685d44afde730efd9132cc update-cwm_tenderloin-1012.zip
So I copied all the files from c:\downloads\touchpad to \cminstall on my touchad.
Rebooted into recovery, and did the:
C:\DOWNLOADS\TOUCHPAD>"C:\Program Files\Palm, Inc\novacom.exe" boot mem:// < ACMEInstaller2
The touchpad did some magic, including some linux thing/scorlling, rebooted, but now I'm back at webos.
So, did i forgot something? Should I use ACMEInstaller2 or ACMEInstaller3 (or even ACMEInstaller?).
Thanks.
EDIT: OK. I just realized that the Boot menu gives you some seconds and then it boots to WebOS.
Now, when it boots, I get this options:
Boot webOS
Boot ClockworkMod
boot webOS Recovery
reboot
shutdown
NONE of the options allows me to boot into CM9. I'm missing something?
kwanbis said:
Hello guys.
I just got a brand new TouchPad 32GB. WebOS is very nice, but there are not many applications, so I'm trying to intall CM9.
I have all the drivers installed correctly, I can put the touchpad in developer mode, and USB mode
Problem is, MOST of the links on the guides are outdated. I tried guides here, guides on rootwiz, guides on XDA.
So I started looking for the files myself, and now I have.
e0664157ed69f8999e1c3ee77cdc53ae ACMEInstaller2
7b49b53a9d70315c40dccde9fc20e7a9 ACMEInstaller3
7642f3f0a8090dc52445541a94ed8164 cm-9-20120816-NIGHTLY-tenderloin.zip
980139d6b46b9cbba4db0e07ad17ba5d moboot_0.3.5.zip
1308300f38685d44afde730efd9132cc update-cwm_tenderloin-1012.zip
So I copied all the files from c:\downloads\touchpad to \cminstall on my touchad.
Rebooted into recovery, and did the:
C:\DOWNLOADS\TOUCHPAD>"C:\Program Files\Palm, Inc\novacom.exe" boot mem:// < ACMEInstaller2
The touchpad did some magic, including some linux thing/scorlling, rebooted, but now I'm back at webos.
So, did i forgot something? Should I use ACMEInstaller2 or ACMEInstaller3 (or even ACMEInstaller?).
Thanks.
EDIT: OK. I just realized that the Boot menu gives you some seconds and then it boots to WebOS.
Click to expand...
Click to collapse
Your third file should should be renamed so that it reads ,
update-cm-9-20120816-NIGHTLY-tenderloin
And yes use ACMEIinstaller2
I hope this helps
Boot into CWM and then flash the 8-16Nightly file that you have then the latest Gapps 4-29
Sent from my cm_tenderloin using XDA Premium HD app
sstar said:
Your third file should should be renamed so that it reads ,
update-cm-9-20120816-NIGHTLY-tenderloin
And yes use ACMEIinstaller2
I hope this helps
Click to expand...
Click to collapse
Yeah, I re-read one of the guides, and it mentioned that, so i'm trying again.
Thanks.
kwanbis said:
Yeah, I re-read one of the guides, and it mentioned that, so i'm trying again.
Thanks.
Click to expand...
Click to collapse
How did you get on?
i tried acmeinstaller3 and i was complaining of inode errors ? has anyone else experienced this ? is there anyway of checking the filesystems again for errors, as there was lots of inode fixes maybe it was due to partitian resizing ?
i personally used this link:
http://liliputing.com/2012/01/how-to-install-android-4-0-on-the-hp-touchpad-cyanogenmod-9-alpha.html
The only thing i did different was that i used the latest version of the files.
imeem said:
i personally used this link:
http://liliputing.com/2012/01/how-to-install-android-4-0-on-the-hp-touchpad-cyanogenmod-9-alpha.html
The only thing i did different was that i used the latest version of the files.
Click to expand...
Click to collapse
I did exactly the same.
Just wanted to say this really helped me. And for any of the noobies, if you take the OP's MD5 codes, and plug them into Goo, you will find the files very very quick. And in order for me to download the ACMEInstaller2, I had to change it to a .zip file, and download as such, and then when plugging in the CMD code, just add .zip to the file name, and you're golden. Hope this helps!
partition repair prior to ACMEinstall3
alienkidmj12 said:
i tried acmeinstaller3 and i was complaining of inode errors ? has anyone else experienced this ? is there anyway of checking the filesystems again for errors, as there was lots of inode fixes maybe it was due to partitian resizing ?
Click to expand...
Click to collapse
If you are partitioned once using ACMEinstaller2, you should ACMEuninstall to remove/repair partitions. After that you can use ACMEinstaller3. Just make sure your CM9 and Gapps file names begin "update-" as you copy them into the cminstall folder.
ACMEInstaller3 is for CM10, not CM9.
not just for CM10
ve6ay said:
ACMEInstaller3 is for CM10, not CM9.
Click to expand...
Click to collapse
As posted by Developer green, it was designed for CM10 in mind to provide a little more partition room to accomodate CM10. It can be used with no ill effects* with CM9 to get that space from the beginning flash of CM9 and then you would be CM10 ready. You are able to use the benefit of a little more system partition than what is deployed with ACMEinstaller2.
I've used ACMEinstaller3 with great success on 6 of the 15 touchpads I help support with CM9. I use ACMEinstall3 by routine now as there is no need to have either ACMEinstall or ACMEinstall2.
* - the use of a few hundred MB from the SDcard to System partition is a small sacrafice of storage space on SDcard with the potential gain of CM10 ready and more headroom for the system, even on CM9.
I picked up a 32gb TP a few weeks ago.and have just been sitting on it. I was hoping to see some updated guides to simplify my learning curve to get android on it (i know I just need to read and learn). Can't believe I'm so hesitant to do anything with it, but the op's experience seems inline with my expectations of the device at the moment.
Sent from my "Up all night, Sleep all day" EVO3D!
mpgrimm2 said:
I picked up a 32gb TP a few weeks ago.and have just been sitting on it. I was hoping to see some updated guides to simplify my learning curve to get android on it (i know I just need to read and learn). Can't believe I'm so hesitant to do anything with it, but the op's experience seems inline with my expectations of the device at the moment.
Sent from my "Up all night, Sleep all day" EVO3D!
Click to expand...
Click to collapse
I used the same lilliputing site linked above. Like another post said, just plug the md5sum into goo.im and you should find the files.
First time install instructions for CyanogenMod
If you haven't seen these posts by the original Touchpad CM dev, you might want to check em out.
Rootzwiki post by Dalingrin: http://rootzwiki.com/topic/33872-first-time-install-instructions-for-cyanogenmod/#entry947163
The "maintained" instructions list in that post point here: http://wiki.cyanogenmod.com/wiki/HP_Touchpad:_Full_Update_Guide
^^^ There are a couple small inconsistencies here. I'm not sure how to submit to have them corrected.
Overall, this is designated as the official source.
In the top section they list ACMEinstaller3 (although the lower section they list ACMEinstaller)
NOTE: CyanogenMod product designation for HP Touchpad = tenderloin
Jonas. said:
Just wanted to say this really helped me. And for any of the noobies, if you take the OP's MD5 codes, and plug them into Goo, you will find the files very very quick. And in order for me to download the ACMEInstaller2, I had to change it to a .zip file, and download as such, and then when plugging in the CMD code, just add .zip to the file name, and you're golden. Hope this helps!
Click to expand...
Click to collapse
ZedZardoz said:
If you are partitioned once using ACMEinstaller2, you should ACMEuninstall to remove/repair partitions. After that you can use ACMEinstaller3. Just make sure your CM9 and Gapps file names begin "update-" as you copy them into the cminstall folder.
Click to expand...
Click to collapse
ZedZardoz said:
If you haven't seen these posts by the original Touchpad CM dev, you might want to check em out.
Rootzwiki post by Dalingrin: http://rootzwiki.com/topic/33872-first-time-install-instructions-for-cyanogenmod/#entry947163
The "maintained" instructions list in that post point here: http://wiki.cyanogenmod.com/wiki/HP_Touchpad:_Full_Update_Guide
^^^ There are a couple small inconsistencies here. I'm not sure how to submit to have them corrected.
Overall, this is designated as the official source.
In the top section they list ACMEinstaller3 (although the lower section they list ACMEinstaller)
NOTE: CyanogenMod product designation for HP Touchpad = tenderloin
Click to expand...
Click to collapse
Thanks to everyone who posted. I plugged the MD5's in as suggested, found the liliputin, CM, and jcsullins goo.im sites for files and read/the liliputin guide. I'm sure I will have additional questions for when I get back up later tonight to attempt this, but it looks like I have all the needed files ready plus some extras (screenshot).
For now:
- Do you have to "dual boot" android & webos, vs wiping out webos and keeping only android?
- How much space is WebOS taking up on the "dual boot" setup, ie does it have it's own partitions etc separate from android?
- Can you just turn the device on and have it automatically boot android (WAF = Wife Acceptance Factor)
- When installing roms I have been used to formatting /system, /data, & /cache first. Does AcmeInstaller do this for you. If so, you can just do new rom flashes & backups "manually" through CWM or TWRP right? I keep seeing mention of only wiping "cache" beforehand?
- How would I restore the tablet to stock WebOS, AcmeUninstaller? (I plan on going with AcmeInstaller 3)
- My impression is that the latest CM9 Nightlies are the most stable/functional ICS versions currently available for the TP as a daily driver. Is this correct?
mpgrimm2 said:
Thanks to everyone who posted. I plugged the MD5's in as suggested, found the liliputin, CM, and jcsullins goo.im sites for files and read/the liliputin guide. I'm sure I will have additional questions for when I get back up later tonight to attempt this, but it looks like I have all the needed files ready plus some extras (screenshot).
For now:
- Do you have to "dual boot" android & webos, vs wiping out webos and keeping only android?
- How much space is WebOS taking up on the "dual boot" setup, ie does it have it's own partitions etc separate from android?
- Can you just turn the device on and have it automatically boot android (WAF = Wife Acceptance Factor)
- When installing roms I have been used to formatting /system, /data, & /cache first. Does AcmeInstaller do this for you. If so, you can just do new rom flashes & backups "manually" through CWM or TWRP right? I keep seeing mention of only wiping "cache" beforehand?
- How would I restore the tablet to stock WebOS, AcmeUninstaller? (I plan on going with AcmeInstaller 3)
- My impression is that the latest CM9 Nightlies are the most stable/functional ICS versions currently available for the TP as a daily driver. Is this correct?
Click to expand...
Click to collapse
Re Files: You have more than enough.
move a copy of ACMEinstall3 to your PCs Palm, Inc folder
rename gapps-20120429-signed.zip to update-gapps-20120429-signed.zip
rename cm9 ROM to update-cm-9-20121007-NIGHTLY-tenderloin.zip
From webOS / USB mode connect your PC and copy your cminstall folder to the tablet. (cminstall folder should have 4 .zip files: CWM, MoBoot, gapps, cm9) when you reboot to Novacom Bootie, you are ready for your ACMEinstall invocation command. Takes about 15 min. to flash.
CyanogenMod is dependent on webOS to be present. You cannot remove webOS. If you are that concerned for space, webDoctor to ver 3.0.0 and never OTA update. That version has the smallest footprint, you might get a couple hundred MB saved, but IMHO, not worth the effort.
The default boot order selects Android after 5 seconds. You can edit this or use a preware webOS app: CyBoot to edit the default and how long to wait in MoBoot before default is loaded.
ACMEinstaller3 handles the partition chores for you. You don't have any CM or other ROM loaded? If you did, you should ACMEuninstall first or to return it to stock webOS. wiping cache is a selection that is done from CWM or TWRP on re-flash of the ROM. You could select ClockworkMod on first boot to do this step, but I have never bothered on an initial load.
I'm currently on cm-9-20121007, the latest nightly.
Good Luck
mpgrimm2 said:
Thanks to everyone who posted. I plugged the MD5's in as suggested, found the liliputin, CM, and jcsullins goo.im sites for files and read/the liliputin guide. I'm sure I will have additional questions for when I get back up later tonight to attempt this, but it looks like I have all the needed files ready plus some extras (screenshot).
For now:
- Do you have to "dual boot" android & webos, vs wiping out webos and keeping only android?
- How much space is WebOS taking up on the "dual boot" setup, ie does it have it's own partitions etc separate from android?
- Can you just turn the device on and have it automatically boot android (WAF = Wife Acceptance Factor)
- When installing roms I have been used to formatting /system, /data, & /cache first. Does AcmeInstaller do this for you. If so, you can just do new rom flashes & backups "manually" through CWM or TWRP right? I keep seeing mention of only wiping "cache" beforehand?
- How would I restore the tablet to stock WebOS, AcmeUninstaller? (I plan on going with AcmeInstaller 3)
- My impression is that the latest CM9 Nightlies are the most stable/functional ICS versions currently available for the TP as a daily driver. Is this correct?
Click to expand...
Click to collapse
The Touchpad's hard drive will show as 27.1gig before installing Android and 25.4 after if you use ACMEInstaller 3 or 25.5 with ACMEInstaller 2 .
You should not attempt to remove webos.
After installation it will automatically boot into Cyanogen/Android with a 5 second delay. To give you the option to change . Both the boot preference and time out can be changed either by installing an app called Cyboot through preware on webos , or by editing the boot folder when running Android.
Use gapps 20120429 and if using ACMEInstaller 3 rename so that it begins update- .
Yes use the latest nightly and rename so it begins update-
Acmeuninstaller will return the tablet back to webos and running Android uninstall from preware will remove moboot .
Install it have fun then you will probably have a few more questions.
Good luck
Thanks guys. I'm up and running on latest CM9.. AWESOME!
Still would like to see someone with a guide here that has up to date links. But the Lilliputin site guide was good minus links.
Sent from my "Up all night, sleep all day" HP CM9 Touchpad
Hi all,
After spending many hours trawling the internet, and especially this forum I still am having problems getting ANY custom rom I've tried booting on this phone
I know it's old, but it's just a phone I had lying around and want to use it as a small tablet for my 6yo daughter.
I can flash any "stock" rom I've found with odin, but when flashing using an install from an SD card through CWM, it just hangs on the Samsung bootscreen.
CWM installs as the default recovery console, so something is going on the phone, but it won't boot to android.
Oh I'm also using a 5830I rom, but my research has shown this is basically the same phone?
I've used CM7 and tried lots of other custom roms with the same outcome - please can anyone help!?
My daughter is dying to use her new games machine, but the stock rom is sooooo laggy and slow it's no good at all!
Thanks in advance.
@macsbig, "About device" information from settings of your device please < home+power button for screenshots > or kindly state the full details here.
Your original CSC/PDA/MODEM parts of your device <Dial *#1234# >
Your Region /Country/ carrier you are staying please.
Thanks for the reply ehsanotaku!
PDA : S5830iXXLA4
PHONE : S5830iXXLA2
CSC : S5830iOXXLA2
I'm in the uk. This is not the original rom (that got stuck in a bootlock) and the only way to get the 'phone working again was to flash with a stock rom from the internet.
The original rom was from "Three".
During my various attempts at flashing a rom I have ticked the "re-partition" box and tried both "cooperve_0623.pit" and totoro_0623.pit
I've flashed my P5110 tablet, and a Galaxy S1 for my son with no problems - odd!
@macsbig, How come you are ended up with outdated ( 2012 ) s5830i in the first place ? Any particular problems with your s5839i original firmware ( do you know your original CSC/PDA/MODEM parts ) ? Are you absolutely sure this is not re-branded version ( "About Device" info of the original phone would be nice to see though ) Did you take any Nandroid back up of all of the original partitions of your s5839i through temporary CWM zip file ( files will be stored inside your Clockworkmod directory inside the root of the SD card )
Do you still have access to Recovery stock e3 console and Download mode ?
Another important subject in need of clarification are ".pit" files ( partition table info ) and Re-partition option. Playing around with wrong .pit file such as totoro and incorrect usage of Re-partition will lead into hard bricking of your device .
Since you already did modify partition table couple of time partially without success , I would suggest the following process :
1. Download one of the newest non wipe xxx.tar.md5 s5830i firmware from here < It is free, but registration is required > Probably 2013 xxMD1 is the right one for our experiment.
2. Make your wipe flash able zip package through splitfus2 tutorial provided here, my comment @ post 9 or simply you may use European/Russian pre-made package from here , your choice though ( I would advise the first method , but the latter also will work ) .
3.Get the following files:
3.1 - Odin3.v3.07.Cooperve.exe from either places would be fine : 1 , or any sticky post in general/development section will do ( correct cooperVe .pit file will be resided inside the package )
3.2- Get the Temp-CWM 5.0.2.6 or 5.0.2.8 zip file from here or here < put the zip file inside the root of your SD card for flashing later >
3.3- Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar from post#27 , my attachment .
3.4 - SLIM_CM7.2_Cooperve #4 Rom < put it inside the root of SD card >
3.5- This kernel is also goes into Root of SD card for later usage .
3.6- EXT4 Formatter Tool , into the root of SD card again.
4- Now , if you don't have proper drivers installed inside your Windows PC , you can get then form here .
Ok, assuming you have at least access to Download mode , provided the combo keys work (pressing Vol(+) + Vol(-) + Power Keys) Go there according to manual :
-Power off your Phone.
-Get into "Download mode" by pressing Vol(+) + Vol(-) + Power Keys.
-press volume up
-Open Odin3.v3.07.Cooperve.exe
-Connect your phone to PC via USB cable.
-Make sure that your phone is detected in "ID:COM" area.
- Put your wipe PDA/CSC/MODEM/ boot loader/pit files into their proper places , Re-partition is ticked , Factory reset and reboot selected by default >> push the START !
- DO NOT disconnected nor disturb the flashing Nand process , until the process being terminated . Now you must be out of boot loop .
For completing our partition conversion and also put some cm7.2 custom Rom into the test at the same time , do the following :
- Boot into stock e3 recovery >> wipe data and flash your Temp CWM
- CWM > wipe data > wipe cache > wipe Dalvik cache
- Flash the EXT4 Formatter tool, so whole system will be converted to EXT4. (Stock filesystem is RFS).
- Flash kernel_CM7_v4.0_cooperVe .
- When the Kernel is installed, go to the advanced menu --> "reboot recovery" (this will reboot the device, thus you will be directed into your new CWM built-in, which is implanted inside Kernel ).
- Wipe data, cache and Dalvik
- Go to "mounts and storage", and make sure /system partition is mounted (will show -unmounted ; it is like ON/OFF switch)
- Main menu > "Install zip from SD Card" > choose "zip from SD card" and install the ROM, you have already got inside your SD <SLIM_CM7.2_Cooperve #4>
- Reboot
waiting for some good news ............
It's a long story, but here goes!
I had a couple of old phones we no longer use hanging around the house, so I thought it would be good to let my (young) children use them as simple games playing deivices. It doesn't matter too much if the phone is dropped and damaged etc, as I probrably wont use them for anything else as we have new phones.
Within a couple of days - and I'm not sure what happened, my daughters phone was stuck in a boot loop (samsung and "Three" logos repeatedly). Having no experiance of "unbricking" phones I immediately reached for google, and set out on my quest to sort out her phone for her (as we had lots, and lots of tears over her new toy!). The phone has no sim card in and is on wifi for installs etc.
After searching I found a rom that would load on and make the phone good again, this one: S5839iXXLK2_S5839iH3GLC2_S5839iNELK1_HOME.tar.md5
This worked ok, but was very laggy, and irritated me imensely as I was sorting games etc for her, so I decided to to instal a custom rom. After 3 roms refused to load (just stuck on the "Samaung GALAXY Ace GT-S5839i boot screen) I decided to try flashing it to 5380i firmware and Pit file - as nearly all custom roms for the ace seem to be for the 5830i variant - I wondered if this would sort my problem!
It didn't! But now it has become a challenge, and a chance to learn something of Android and how it works - as I said in my last post I have successfully flashed an I9000 with carbon and my P5110 with CM11, I learnt how to do this by what I've learnt from reaserching about this phone, so it has been a worthwhile excercise!
But back to the point. No I don't have any back-ups of the original phone, I neither had the knowlege, or know how of having or needing to do this - it's only now I'm finding my phones/tablets so facinanting!!
Yes I am now back to the stock (e3) recovery, which I can get into.
Many thanks for your help so far - I will try your ideas and repeort back!
@macsbig, Yes do that please and after resolving your initial problems , here is a confirmed list of the games compatible with your GPU/CPU of your child's legacy device . Also you can use chainfire 3d only under stock firmware/rooted phone for the games required plugin(s) and app being activate for proper almost lag free experience . You may read theses links as well for some insight : 1 , 2 .
The ext4 formatter link doesnt work my friend
macsbig said:
The ext4 formatter link doesnt work my friend
Click to expand...
Click to collapse
Just cross-linking it ( wasn't my links to begin though ^:^ )
Attached the flash able zip file to the post body .
I will try you solution(s) later. Working late today! But wow this seems quite complicated! ! Hehe.
Sent from my GT-I9300 using XDA Free mobile app
macsbig said:
I will try you solution(s) later. Working late today! But wow this seems quite complicated! ! Hehe.
Click to expand...
Click to collapse
Well , researching a new area of knowledge ( in this case customization/rooting/bricking/moding and many more technical things inside XDA) can be a bit overwhelming.I do agree with you that the sheer wealth of material means that it can be overwhelming, but more you read and spend time @ XDA, more you will get the hang of the material presented here .
Nevertheless we are here to share/help all of the possible/working solution mate. Just ask anything you can not understand very well . I will try to depict even more detailed walk-through guidelines.
Regards
Right, I now have a custom rom on the 5839i!
I didn't have too much time last night, so what I did was flashed the phone with Odin, using the bootloader and pit file you specified. I then rebooted into the stock revovery, wiped the Data, Cache and Delvic partitions, then booted into CMW 5.0.2.6 and flashed the EXT4 Formatter tool. I then installed the kernel you specified
After that I rebooted into the CMW recovery from the new kernel and followed your instructions - and Voila! It booted into the slim rom you linked me too
Just to test it wasn't a fluke, I then installed CM9, and that went on fine too - with just the normal steps.
I now have to decide after your other advice, whether I go for a stock rom, and try and get rid of the lag, use chainfire 3D etc or go for a custom mod!
Is there a similar app for modded roms's like chainfire 3D to help game perfomance on this limited hardware? I'd really prefer to use a modded rom and build up from there, but as I stated earlier in the post, this will be used only for games and listening to music from youtube, so i'll maybe have to research some more to find out what would work the best.
Many, many thanks for your help, I've learnt alot during this project!!
Oh as a bit of an aside, got a bit worried when downloading some of the links, some of the "download managers" were causing my anti-virus and anti-malware software to give me warnings!
Thanks again
@macsbig, Glad everything worked out for you mate . To address your concerns I must say that I did not come across any working solution for accelerating your GPU with reduction [email protected] custom Roms unfortunately ( only works on stock fw/rooted device) .
For CM9 beta Rom available @ development sub forum , this is an unstable Rom with some serious problems , because of ICS bugs an other things( Read this troubleshooting session and links provided there ).
For malware's concerns they are mostly false positives . Even virus total wold miss lead you in many cases, due to nature of advertising agent implanted inside some of the app inside system directory of custom Roms . You can simply replace the app in question with another one free of adverts. However they are harmless mostly. Please read this discussion (post #472-475) (post#291-298) between me and moderators team for more information about advertisement policies. Basically we have a very good control over materials presented here , thanks to mod teams .
Hope I did help you with your quest
My apologies, when I said that I was getting anti-virus/malware warnings, that was aimed at when I was trying to download the files on "mediafire(?)" and such like. They want you to install a stupid downloader etc., which then installs some crap on your pc.
Had it when downloading splitfus2 if I recall correctly (it was late 12am!).
That's why in the end I decided to use a pre - split (is that what you mean by wiped?) rom in the end.
I'm gonna have a play with the 'phone again later when I finish work.
Hi all,
to make it plain and short: I messed up.
I have a GT-S5830i which I unrooted according to the Sticky Note in the forum, installed CWM Recovery and then 'installed from ZIP' a CM9_cooperve_Beta_05.zip that I found in one of the posts in the forum. The installation went on without error message but since then the phone does not make it beyond the initial screen "Samsung Galaxy Ace GT-S5830i". I can start recovery mode and Download mode. In reovery mode I can format cache, data, sdcard, sd-ext but *not* system. Error Message: "E: format_volume: make_ext4fs failed on /dev/block/st19"
I have tried already several methods according to the forum, e.g.
1) 'install from ZIP' older Cyanogenmod
2) the tool ext4_formatter.zip
3) re-flash with ODIN with several tar-ROMs, all failed. Odin finds the phone (since I start Odin as Admin now), but after I hit 'start' it tries to establish a connection to the phone and ends after a while with 'Failed'
I'm basically lost now, don't know what else to do. Any advise is appreciated (it's my mom's phone, she is getting impatient )
Thx, cheers!
Xala
Hi @xalarsk , So you can't format your /system partition , which is required for installation of your rom ,, you need to try this method from here mate . Follow my instruction from the line @post#4 :"1. Download one of the newest ,,," to the end of the post and please do not use CM9 beta , because it is unstable and will wreak havoc with your system eventually . ( either cm7 or cm11 is the place you should go for CyanogenMod experience for cooperVe device ).
If you fail at any level please give us your logcat ( error massage ) for better support for your Odin process you mentioned .
Cygwin not working
Hi @ehsanotaku,
thank you for your quick reply, it's appreciated!
Unfortunately I couldn't get cygwin to install all necessary packets. The ZIP-test always failed. I have a Linux system running (Linux Mint 17) though, and hope that might help. In the meantime I tried to download the already split packages as described in another of your forum posts, but the website provides only exe-files instead of zip-files. Is there another location to download them?
#UPDATE: It seems there is a SplitFUS2 version for linux somewhere but couldn't find links to download. Anybody can help? I'll also PM Doky73
Cheers, Holger
xalarsk said:
Hi @ehsanotaku,
thank you for your quick reply, it's appreciated!
Unfortunately I couldn't get cygwin to install all necessary packets. The ZIP-test always failed. I have a Linux system running (Linux Mint 17) though, and hope that might help. In the meantime I tried to download the already split packages as described in another of your forum posts, but the website provides only exe-files instead of zip-files. Is there another location to download them?
#UPDATE: It seems there is a SplitFUS2 version for linux somewhere but couldn't find links to download. Anybody can help? I'll also PM Doky73
Cheers, Holger
Click to expand...
Click to collapse
Cygwin was meant for windows platform to get the native Linux environment/command line you already got there . You can create a virtual instance of the windows 7 inside virtualbox or any kind of apps you are preferring such as Vmware/Parallel etc etc to get the job done .
Splitfus2 only supports windows platform as far as i know mate,,, either vitalization as i said or the pre-made zip package ( which is clearly not .exe file ,, push the download now and get yourself a descent downland manager,, tested and zip packaged delivered ) from here is the feasible approach for your problem .
Ok, had all the files ready, just the Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar seems to be broken. I downloaded the link provided in your post #8 several times with several download managers, also uses 7-zip and several online unrar services..result always the same: The archive is broken. Is that possible? Would you mind to check yourself?
xalarsk said:
Ok, had all the files ready, just the Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar seems to be broken. I downloaded the link provided in your post #8 several times with several download managers, also uses 7-zip and several online unrar services..result always the same: The archive is broken. Is that possible? Would you mind to check yourself?
Click to expand...
Click to collapse
Another fellow had similar issue with my attachment that was corrected here @ post#27
Unbricked, SD card not recognized
Update: Phone has been unbricked, many thanks for that!
Currently I have still issues with the external SD card, which also holds the ZIP files. Phone won't recognize it, not even format it properly. Still working on that.
Cheers, Xala
xalarsk said:
Update: Phone has been unbricked, many thanks for that!
Currently I have still issues with the external SD card, which also holds the ZIP files. Phone won't recognize it, not even format it properly. Still working on that.
Cheers, Xala
Click to expand...
Click to collapse
Mostly this happened because of the bug inside CM9 beta you used . Study this topic mate i troubleshooted while ago for a sample of the symptoms external SD card would show after unstable ICS usage .
Also as an alternative to the method i instructed there , you can format/Re-partition your SD card by putting it inside card reader and using app such as free MiniTool Partition Wizard "Gparted" tool for Linux users Or "iPartiton" for Mac users etc etc ,, to get the job done . You can find several tutorials inside XDA for this matter mate.
Phone works with CM7.2, can I upgrade to CM9?
Hi again,
first of all, props to @ehsanotaku, I will hit the 'Thanks' buttons.
Now, this is a bit beyond the topic, but I'd like to ask anyway for recommendations of CM9 roms. The one I picked from a post inside this forum bricked my phone and made me start this thread, I don't want to go down this road again. So I'd be glad for any recommendation of a stable ROM that will put my phone beyond Android 4.0.
Cheers again,
Xala
So i have a similar issue. I used to have CM11 installed, but i figured thats too slow for me. Then i went back to stock rom (XXMJ2) which works fine. But now i have a problem.
Everytime i want to flash a stock based or cm7 based rom on my phone, it gets messed up. Today i wanted to flash this
http://forum.xda-developers.com/galaxy-ace/s5830i-develop/cm-7-2-kitkat-smart-r2-t3075267
i naturally downloaded clockwork mod recovery (5.0.2.6) and tried to flash it. Flashing was done pretty quickly (10 seconds or so) and when i rebooted, i obviously got stuck at sammy logo. Now booting back to the recovery (first e3 then cwm) i got bunch of error about partritions not being able to be mounted (happens the same if i want to manually mout them or format them)...
So, what to do ?
I have a suspicion, that flashing CM11 and the latest cwm recovery for it somehow messed up partritions.
hojnikb said:
So i have a similar issue. I used to have CM11 installed, but i figured thats too slow for me. Then i went back to stock rom (XXMJ2) which works fine. But now i have a problem.
Everytime i want to flash a stock based or cm7 based rom on my phone, it gets messed up. Today i wanted to flash this
http://forum.xda-developers.com/galaxy-ace/s5830i-develop/cm-7-2-kitkat-smart-r2-t3075267
i naturally downloaded clockwork mod recovery (5.0.2.6) and tried to flash it. Flashing was done pretty quickly (10 seconds or so) and when i rebooted, i obviously got stuck at sammy logo. Now booting back to the recovery (first e3 then cwm) i got bunch of error about partritions not being able to be mounted (happens the same if i want to manually mout them or format them)...
So, what to do ?
I have a suspicion, that flashing CM11 and the latest cwm recovery for it somehow messed up partritions.
Click to expand...
Click to collapse
ok not going to excruciating details of symptoms and explaining all of your errors for now just please read my advice @ post2 of this topic and follow the procedures accordingly and finished it with formatter tools and cm7 instructions you will find there ., after that you can install Kitkat Smart R2 like you are coming from another CM7 build instruction . btw some problem regarding super user privileges and play store 492-498 infamous bug was reported for this fairly new development .
UPDATE: I was able to debrick the phone. Read my later post for details.
----------------------
Hi All,
Thank you all for having amazing community of hackers and developers here. You guys rock.
I started my search for a new rugged rootable phone recently and I settled on Poptel P60. It is a great phone though slightly bigger than what I normally get. Nontheless, the specs are excellent and the price is fair!
I've had a limited success rooting and customizing this phone. The OEM interface is almost bearable but overall the "Customized UI" felt like a downgrade from stock Oreo. It has a very annoying feature of reverting to stock launcher on startup, even when I selected Nova as my default one. The stock launcher is not that great. This, and the lack of ability to use x.flux, Titanium Backup and other root-only apps drove me to try hacking things again.
After emailing the manufacturer they provided the firmware but it is in CPB format. I tried at least 3 different converters for CPB to MTK Scatter and they all either freeze or hang. No luck.
Instead I did a rom readback with SPFlashTool and then cut up the partitions with Wwr. Now I've finally had the recovery partition! I used CarlivImageKitchen to port TWRP from a similar device, Ulefone Armor 5. The chipset and resolution are same. After some trial and error it worked! I had to use USB-OTG for input and external sd card had a weird label, but I was able to install Magisk from the SD card to root, followed by XPosed, full package. It worked! If anyone needs my ported TWRP Recovery for Poptel P60 just ask!
However, the manufacturer UI did complain a lot about the phone being rooted. Eventually, somehow, Magisk stop receiving root requests. They never showed up and timed out! Very strange, because apps that already received root continued working. I tried a lot but could not fix the issue. I was fed up. I wanted to do a manufacturer reset (in hopes of starting from scratch and then attempting to port Lineage or something) but, as I've mentioned, I have not received a firmware compatible with SPFlashTool. I tried to make one from Armor 5. The partitions were almost the same (both are MT6763 devices). One was out of order, and offsets were different and I patched all those. To be clear, I used all the partitions and layout extracted from my rom readback that was cut up by Wwr. I only used the Armor 5 scatter as a reference for file format. I edited the layout to match everythign I saw in Wwr.
This is where the horror begins. I tried flashing (Download Only) with SPFlashTool but got some error saying something changed. "Do you want to do Format & Download instead?". Being an inexperienced idiot that I am, I said yes!
Now, the phone appears bricked. No lights. No screen output. Cannot enter fastboot. Cannot enter recovery. Cannot boot.
I have a feeling the preloader got corrupted. I'm not sure this is the case because I've omitted the preloder from download. At least the first time the phone started acting bricked. The device still shows as Mediatek USB VCOM device and flashing gets initiated but all attempts to flash result in errors. MA checksum mistmatch or something along that order. I've tried a lot of things and I'm stuck! For good or for worse I've tried flashing Ulefone Armor 5 preloader but I'm getting the same error when trying to flash it.
Here is what I have...
- Stock firmware in SPB format. I can't use it and nothing I tried worked for converting it.
- ROM dump made with SPFlashTool
- Wwr was able to extract every partition except preloader. This includes nvram, etc. I'm not sure why it was not able to extract the bootloader.
- TWRP port that worked. Seems not useful if the phone does not start.
- Preloader for Ulefone Armor 5, (same chipset and resolution)
Clearly I am an idiot for using "Format & Download" option. I've found posts later suggesting against it. I am also over my head for trying to tackle a new device by myself, though I have had a marginal success with porting TWRP and installing Magisk.
Now, I feel like idiot and I am stuck! I beg you, XDA developers, if you have any advice (besides not being an idiot in the future), please share!
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
SkylinesHD said:
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
Click to expand...
Click to collapse
That wouldn't work, heh. I bought this phone on eBay and rights now it's currently sold by a handful of sites. It is on warranty but returning it back to China would be complicated. At any rate, I live on the edge outside of warranty!
I was just about ready to give up and feel like the biggest reckless loser on Earth... Days of tinkering around with nothing but a phone brick to show for it. Poptel tech support wouldn't provide me with MTK scatter. All they gave me was this SPB firmware that nobody uses and it crashes every converter I threw at it. Useless.... No fastboot. No recovery. No functional bootloader.
The amazing GOOD NEWS is I have debricked the phone... I used a bootloader from another phone's firmware: Cubot_Power_MT6763_180607_8.1.0. Unlike Ulefone Armor 5's preloader this one worked! It seems like it's the only thing I was missing because the phone starts up and everything seems to work. I must have done a good job with all other partitions but I'll try to watch for signs of anything else broken. Right now it seems fine.
I'm not sure if the bootloader was completely gone, corrupted, or an incorrect one was used. All I know is I was able to download Cubot Power's working bootloader (also MT6763) with SPFlashTool. Nothing like a feeling of unbricking your phone!
I will post more updates if that's ok... I'm hoping to port Lineage on it (I've never tried that before) or at least find a way around the manufacturer's clunky UI. The hardware is great otherwise. If anybody wants a working ported TWRP image or the scatter I used for debricking just ask! I will make a post later if I have more success with customizing the phone. The phone is debricked and I have a scatter and images to fall back on if anything goes wrong. Woot! Thank you everyone who developed these great tools.
I have the same phone been looking for info. there's a thread on 4pda with poptel p60 that has the scatter file and firmware. Any chance you could post the twrp for this phone? having trouble trying to port myself cant figure out port 6763 from the guides available.
4pda.ru/forum/index.php?showtopic=933002
Firemware:
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download
idaman0 said:
Hey man,
Was wondering if you saw my post on your thread. Looking for TWRP for the Poptel P60.
Thanks,
telegram @drmethyl
Click to expand...
Click to collapse
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
https://mega.nz/#!MNVGhaYS!63ovQeowwoP1oE3v6-_ZS8gKx_-mxOh4G4qWcKRbuiQ
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
zeromemory_wtf said:
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
Click to expand...
Click to collapse
sorry man, didn't end up using yours theres a twrp on 4pda now with a mod to flash to keep root. I'll upload for you here if you don;t have an account there.
The patch for the Light-kastomizator v.12 factory firmware.
I decided not to bother with the draining and distribution of modified firmware as a whole, easier to apply the patch, and ... you're done!
If that - the factory firmware v.12 lies with us -HERE, no problem you can return everything back, or (if there is something Kolupaev), first ask her, and then patch.
#
What is done
Будут удалены:
/system/tts
/system/app/QK_LogSystemAbroad_wm_bl
/system/app/QK_Sos
/system/app/QK_PrivacySpace
/system/app/QK_PersonalAssistScreenAbroad_V2
/system/app/BY_3RD_OperaMiniBrowser_OEMBranding
/system/app/BY_3RD_OperaNews_OEMBranding
/system/app/Drive
/system/app/Duo
/system/app/Gmail2
/system/app/GooglePrintRecommendationService
/system/app/LatinImeGoogle
/system/app/Maps
/system/app/Music2
/system/app/PartnerBookmarksProvider
/system/app/Photos
/system/app/YouTube
/system/app/Videos
/system/presetapp/BY_3RD_OperaMiniBrowser
/system/presetapp/BY_3RD_OperaNews
/ system / priv-app / MtkCellBroadcastReceiver
/ system / priv-app / ConfigUpdater
/ system / priv-app / GoogleFeedback
/ system / priv-app / FilesGo
/ system / priv-app / GooglePartnerSetup
/ system / priv-app / QK_MagazineAbroad
/ system / priv-app / Velvet
The system additionally installed:
ES_Provodnik_3.2.5.5 (graphic mode "Panatta-sport")
the SD Maid Pro - system Cleanup (Lite Mod "Breathe of fate" )
Changes:
By default the system is set to Russian language , region and time zone Russia / Moscow. Setupwizard (first assistant settings) is not cut off.
GBoard keyboard replaced by fashion Antonbeard GoogleKeyboard(with a limited access to the Internet is built dictionaries -.. English and Russian)
Google-search is replaced by the latest beta (it is possible to change the style and transparency of the widget)
have been added and changed some default sounds and ringtones, and the default there as a very sadly.
Blocked by advertising the hosts file.
Improved energy efficiency due to shutdown of background update service does not fall asleep GAPPS and downloaders (allowed these services Doze mode).
#
Setting:
1. Throws on micro SD-card this patch.
2. Downloading the last zip-installer " Magisk-v ..... the zip " and also copy it to the SD-card, turn off the phone.
3. Through the SP Flash Tool sewn recovery "TWRP" (the system can not be loaded !!!).
4. Vaypaem userdata (reset to factory settings) through better "factory mode" (volume down inc +) / select "Clear eMMC".
After reset immediately loads in the TWRP (inc + volume up), and from the sd-card in turn apply patches "LiteMod_Poptel_P60_v.12.zip" and "Magisk-v ..... zip". Reboot from the installation refuse twrp-applications.
Done, you have custom firmware!
(If twrp and Ruth is already installed,
After the completion of all the manipulations, it is desirable to flash the stock (factory) rekaveri, then no problem can be used to reset the system from the Android menu and install the firmware update OTA (over the air).
Download: LiteMod_Poptel_P60_v.12.zip
PS. Sberbank + contactless payment working properly, despite the fact that the system has been modified and installed Ruth! :derisive:
Click to expand...
Click to collapse
3.2.3 TWRP by Jemmini for "Poptel P60" ( with the phone port Blackview BV9500): Attached file recovery.img (17,27 MB)
The port used by the kernel to flash Android 8.1.0 version of "POPTEL_V12_20181030"
WARNING !! After installing recovery, subject to permit changes in the system partition, install ROOT is required, otherwise the system will not boot. if not to accept the possibility of changing the system partition and establish the patch-root subsequent restart in overwrite TWRP recovery returned drain-
Attached fileMT6763_Android_scatter.rar(1.28 kb)
#
Getting ROOT
For ROOT set out under TWRP (pre throwing off the memory card), this patch: Attached fileMagisk-v18.0.zip (3,99 MB)
#
Stokovye boot / recovery
from said EEPROM: Attached filestock.rar (22,75 MB)
#
What does not work:
1) Do not see "the internal memory" (can not decipher the "data" section and ask when starting TWRP password).
Solution:
download the patch: Attached filedisable_encryption_P60.zip (133.89 KB)
throw it on the memory card, boot into TWRP, go to the "mount" to put a checkbox on the vendor , then go to the "install" and install the patch.
After installation make data in the "cleaning" cleaning (possibly cleaning does not help but the formatting of data should definitely help)
after data manipulation TWRP be able to work with the data section
2) is not working USB / MTP mode into TWRP
#
Information for those who are "in the tank" :
When TWRP presence in the smartphone in any case and under no circumstances should you do reset through the system.
Resetting takes place only directly through TWRP (standard cleaning sections)
If you run the command via the android in the first place, it can not be executed because it does not understand the TWRP.
and secondly, you get a constant load in TWRP because it has not yet executed the command android you will always be send to recovery /
Solution for "tank": need to install flow-recovery to be completed through a reset command or cancel it.
Another solution I personally do not know
Just do not forget about gratitude : Jemmini,- for the compilation of the TWRP which served as donorUrree,- order TWRP and testing (nothing would have happened without it)Message edited Lomaster_Serg - 6.1.19, 03:02
Click to expand...
Click to collapse
rapidgator.net/file/84ccd2d612ade0256eb927895d4ed37e/LiteMod_Poptel_P60_v.12.zip.html
rapidgator.net/file/c77fec40e349f8083eda14bf7058425c/recovery.img.html
rapidgator.net/file/6621d517cef9aa10abc78b40bcdc8b26/stock.rar.html
rapidgator.net/file/7a7db29c0d35eee169b76698aac6b50b/MT6763_Android_scatter.txt.html
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download
Moto-Lite Stock Nougat ROM
Android 7.0 / NPHS25.200-23-1
Moto X Pure Edition XT1575
TWRP Flashable Installer
Rooted, Debloated, Optimized
•••••••••••••••••••••••••••••••••••••••••••••••••••••
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's Moto-Lite?
Moto-Lite is an entirely stock-based Motorola ROM, with performance optimizations, systemless root, and some moderate debloating. This ROM is intended to give users a clean, slimmed down stock experience -- via a TWRP flashable installer.
_______________________________________
DISCLAIMER:
By proceeding further, you are assuming full responsibility for your device. Although this ROM has been thoroughly tested, I assume no liability in the event you damage your device or otherwise render it inoperable. Follow the simple instructions and things should go smoothly.
_______________________________________
BUILD INFO:
•Android Version: 7.0 Nougat
•Build No. NPHS25.200-23-1
•System Version: 25.211.1
•API Level: 24
•Build Date: October 30, 2017
•Security Patch Level: October 1, 2017
•Kernel Version: 3.10.84-perf
•Bootloader Version: AO.52
_______________________________________
FEATURES:
•Rooted with Magisk 20.4-Stable
•Static BusyBox Binaries: v1.31.1
•Moderately Debloated
•Safety Net Pass (ctsProfile/basicintegrity)
•Force Encrypt Disabled (Opt Encrypt)
•dm-verity/AVB 2.0 Disabled
•Custom Moto Boot Logo
•Optimized for RAM Efficiency
•su.d Support
•Fully Odexed per Stock Config
_______________________________________
Official Motorola Firmware for XT1575:
This firmware repo encompasses official firmware packages that originated from Motorola's servers. This link includes Android 5.1.1, Android 6.0 and Android 7.0-based firmware builds, including the NPHS25.200-23-1 build upon which this Moto-Lite ROM is based.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Kernel Source Code:
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPH25.200-15
_______________________________________
PREREQUISITES:
Per the general rule of thumb, you will need an unlocked bootloader and a custom recovery such as TWRP. I recommend using the most current official TWRP build from here: https://dl.twrp.me/clark/
In order to circumvent force encryption during installation, you will need external storage such as a microSD card or an OTG USB storage device. (The /userdata partition must be formatted prior to installation; hence, all files and data stored on your device will be erased.) If you do not have, or do not wish to use, an external storage medium, alternative install instructions have been provided, for which you will need a PC or laptop computer and a good quality micro USB to USB syncing/charging cabke
NOTE: The below instructions assume that your device's firmware has been updated to the NPHS25.200-23 firmware build. It is also assumed that your device's modem/baseband version is M8992_1255331.29.01.88.09R SUPER_NA (the most current version).
_______________________________________
Instructions for installation are outlined under two separate headings: A. INSTRUCTIONS - STANDARD INSTALL, which apply to users who have an external micro SD card or an OTG supported external storage medium; and B. INSTRUCTIONS - NO EXTERNAL STORAGE, which should be used by those who do not have, or do not wish to use, a micro SD card or an OTG supported external storage device. For the latter you will need a laptop or computer and a good quality micro USB to USB syncing cable, for transferring the ROM zip file to your phone during the process
A. INSTRUCTIONS - STANDARD INSTALL:
1. Download the ROM zip from the below link and save it to external storage;
2. Boot your device into TWRP recovery mode;
3. On the TWRP home screen, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
4. Select INSTALL, select the ROM zip, and commence installation;
5. Once the ROM is installed, the installation script will patch the stock boot image via Magisk v20.4-Stable to enable systemless root. BusyBox v1.31.1 static binaries will also be installed;
6. Reboot your system once the installer indicates finished. During the first boot, it is completely normal for a single boot loop to occur. This will not occur on subsequent boot-ups;
7. Once you complete initial device setup, open the Magisk Manager app and install any updates or any additional runtime steps that may be required. The app will display prompts for any necessary actions on your part;
8. Enjoy & profit...
B. INSTRUCTIONS - NO EXTERNAL STORAGE DEVICE
1. Download the ROM zip from the below link and save it to your computer;
2. Boot your device into TWRP recovery mode;
3. On the TWRP home screen, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
4. Transfer the ROM.zip the file from its saved location on your computer to the now-formatted internal storage directory on your phone (via a micro USB to USB syncing/charging cable);
5. Reboot Recovery;
6. Select INSTALL, select the ROM zip, and commence installation ;
7. Reboot your system once the installer indicates finished. During the first boot, it is completely normal for a single boot loop to occur. This will not occur on subsequent boot-ups;
8. Once you complete initial device setup, open the Magisk Manager app and install any updates or any additional runtime steps that may be required. The app will display prompts for any necessary actions;
8. Enjoy & profit...
At the time I cooked up this ROM, the latest stable Magisk version was v20.4, so my systemless root installer encompassed within the ROM installer employs Magisk v20.4 stable. After installing the ROM, booting up and completing initial setup, open the Magisk Manager app to update Magisk to the most current version.
_______________________________________
THANK YOU:
Thanks to the amazing @osm0sis for his static BusyBox binary installer. And many thanks to @topjohnwu, the genius developer and creator of Magisk. Huge thanks to @pitflyer, who gave feedback and input on methods of install, and who revisited and outlined the steps for an alternative installation without using a micro SD or OTG supported storage device.
Thanks to @sd_shadow for his input and guidance on installation.
_______________________________________
BUGS:
Since this ROM is based entirely on an official Motorola stock firmware build, no significant bugs or instabilities should be expected. I have tested this ROM thoroughly after performing some optimizations (RAM, I/O Schedule tweaks. Entropy tweaks, etc.), moderate debloating and Magisk installation. I have noted no remarkable bugs, instabilities or performance flaws. However, please leave a comment in the event you discover flaws or bugs. I will look into the issue and try to resolve it. If possible, submit a bug report. Otherwise, list as much detail and specifics as possible regarding the issue.
_______________________________________
DOWNLOAD LINKS:
Moto-Lite XT1575 Android 7.0 ROM
**V2 updated ROM: Magisk v24.3, Busybox v1.34.1 static binaries, some additional debloating and some more RAM optimizations made on the kernel level.
V2 Moto-Lite xt1575 Android 7.0 ROM
Been running this for a week or so. It's fine - love what you took out. An issue exists with moto voice. I cannot get past the setup as I cannot record my phrase. The continual response is that the environment in which I am recording is too loud. I live in the forest - I can hear dew evaporate(/s), it's not too loud .
I run Xposed with Gravity, removed google account after I set some apps up, freeze with SDMaid, block most net action with Afwall - only hiccup on the phone is moto voice, which, I can live without. Thanks for doing your thing.
bronkish said:
Been running this for a week or so. It's fine - love what you took out. An issue exists with moto voice. I cannot get past the setup as I cannot record my phrase. The continual response is that the environment in which I am recording is too loud. I live in the forest - I can hear dew evaporate(/s), it's not too loud .
I run Xposed with Gravity, removed google account after I set some apps up, freeze with SDMaid, block most net action with Afwall - only hiccup on the phone is moto voice, which, I can live without. Thanks for doing your thing.
Click to expand...
Click to collapse
Thanks for your input on this. I'll take a look at the Moto Voice service and see if I have debloated a system app or process that is Moto Voice dependent. Did you notice the Moto Voice issue before installing Xposed & GravityBox? Yeah I absolutely love SD Maid Pro. A great system-level tweaking tool with many uses.
Gravitybox, yessir. I typically get my dumps in order, reboot to twrp, wipe it all, flash a ROM, reboot, initial setup, dev mode and those settings, airplane mode, reboot, flash xposed, reboot, set up my phone. You know, if I do it that way.
Lol, I got no time to see if your kung-fu works right before I fuk it up with xposed. I can't answer the only and perfect question that you asked me. What's even more perfect than that failure is that I bought a g power the other day and haven't used my Xpure since last week. This g power has a burn't pixel though. WTF. I had it 8 days to replace the phone I used 5 years.....sigh.
THanks for responding, sorry I can't help you help me. Probably going to return the g power and use the x pure again and wait for a sweet-ass black-friday deal to replace it. There's a 7T on craigslist winking at me, though... I probably won't reset anything on the Xpure though, runs sweet. Hard phone to replace.
Edit - yeah - been using SD maid for years - love it, use the hsit out of it. ONly realized yesterday that I can dump apks of all installed apps at one go. It just keeps on giving.
Thank you for making this! I've been running for a week with no issues. Phone feels snappy. This is a great option to flash stock without going the ADB route. Cheers!!
mddunner said:
Thank you for making this! I've been running for a week with no issues. Phone feels snappy. This is a great option to flash stock without going the ADB route. Cheers!!
Click to expand...
Click to collapse
Thank you for your feedback and kind words. Glad to hear the ROM worked well on your device.
thank you works great and its rooted.
Another report this works great. For those like me who don't like to read the directions, if you copy the file to the internal storage as you would expect it gets wiped. If you don't have external storage, you can recopy the file in TWRP afterwards -- you just have to reboot recovery to see the files. After that all is well and this ROM is working great.
EDIT: I'm an idiot. I was trying to flash the kernel source zipfile, and not the actual system image...
pitflyer said:
Another report this works great. For those like me who don't like to read the directions, if you copy the file to the internal storage as you would expect it gets wiped. If you don't have external storage, you can recopy the file in TWRP afterwards -- you just have to reboot recovery to see the files. After that all is well and this ROM is working great.
Click to expand...
Click to collapse
Thanks for your feedback. In fact, you make a very valid point regarding external storage devices -- although the /userdata partition needs to be formated in order to disable force-encrypt, some device owners simply may not have external storage mediums or, like many users, may want to expedite the installation process. I will edit the instructions to include installation of the ROM from internal storage, for users who do not own, or have access to, an OTG based external.storage device.
Since you installed from intternal storage, and thus could not format the data partition prior to install, I am assuming your /userdata partition was force encrypted during the initial boot up. Please clarify on this. Thank you.
Hodgdon said:
EDIT: I'm an idiot. I was trying to flash the kernel source zipfile, and not the actual system image...
Click to expand...
Click to collapse
Happens to the best of us. Is the ROM working ok for you?
Viva La Android said:
Thanks for your feedback. In fact, you make a very valid point regarding external storage devices -- although the /userdata partition needs to be formated in order to disable force-encrypt, some device owners simply may not own an OTG based external storage device. I will edit the instructions to include installation of the ROM from internal storage, for users who do not own, or have access to, an OTG based external.storage device.
Since you installed from intternal storage, and thus could not format the data partition prior to install, I am assuming your /userdata partition was force encrypted during the initial boot up. Please clarify on this. Thank you.
Click to expand...
Click to collapse
I'm not sure what happened, I just know that after I realized formatting user data would delete the zip file, I copied the file through TWRP back to the now empty internal storage. TWRP still did not see it, so I rebooted recovery and then it saw it (which as you expect was the only file on internal storage). And it just worked...
I'm not using this phone heavily but it seemed to work fine afterwards and I definitely like having the 'stock' experience w/ root built in and the moderate debloat. Here are my edited steps that worked w/o external storage for me:
NEW: 1. Download the ROM zip from the below link and save it to <<computer>>
SAME: 2. Boot your device into TWRP recovery mode;
SAME: 3. On TWRP, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
NEW: 4. Copy the file from <<computer>> to the now empty internal storage (via USB cable in TWRP recovery)
NEW: 5. Reboot Recovery
6. Select INSTALL, select the ROM zip, and commence installation -- the rest is the same
pitflyer said:
I'm not sure what happened, I just know that after I realized formatting user data would delete the zip file, I copied the file through TWRP back to the now empty internal storage. TWRP still did not see it, so I rebooted recovery and then it saw it (which as you expect was the only file on internal storage). And it just worked...
I'm not using this phone heavily but it seemed to work fine afterwards and I definitely like having the 'stock' experience w/ root built in and the moderate debloat. Here are my edited steps that worked w/o external storage for me:
NEW: 1. Download the ROM zip from the below link and save it to <<computer>>
SAME: 2. Boot your device into TWRP recovery mode;
SAME: 3. On TWRP, select WIPE and choose the option to format data. Select WIPE again, then ADVANCED WIPE, and wipe System and Cache;
NEW: 4. Copy the file from <<computer>> to the now empty internal storage (via USB cable in TWRP recovery)
NEW: 5. Reboot Recovery
6. Select INSTALL, select the ROM zip, and commence installation -- the rest is the same
Click to expand...
Click to collapse
Thank you for clarifying and taking the time to detail your steps. I will edit my existing instructions and add the installation method you outlined, as an alternative for members who do not have an OTG based external storage device. I will credit you with outlining the steps. Thanks again.
Viva La Android said:
Thank you for clarifying and taking the time to detail your steps. I will edit my existing instructions and add the installation method you outlined, as an alternative for members who do not have an OTG based external storage device. I will credit you with outlining the steps. Thanks again.
Click to expand...
Click to collapse
No problem and thank you for sharing the updated ROM!
This looks like the solution I need ...
Could y'all PLEASE define exactly which TWRP yer using to get this from the SDcard into the phone?
Essentially, I UL my BL via moto, fastbooted TWRP (3.1? I'd heard going past 3.2 invited a.b partition foibles) however this still gives me the "Unlocked Bootloader" BSOD, ergo cannot USE twrp - it simply reboots into a functional fone (but obviously NOT secure)
The XT1575 came (used) with stock Nougat ... can supply logcat etc if that's of any use to removing this stupid VIBRATOR screen that won't let me get into TWRP at all
TYVM
VW
You may use any version of TWRP you wish for installing this ROM. I would personally recommend the latest official TWRP v3.5.2-9.0, released just last month. TWRP for the xt1575 Clark was built using device-specific kernel source code. Thus, no matter which version of TWRP you encounter, A/B partitioning will not be a factor because the Clark does not now, nor has it ever, used the A/B partitioning scheme.
So try these steps exactly: download TWRP v3.5.2-9.0 from here https://dl.twrp.me/clark/ , rename it to twrp.img and store the image in your ADB/Fastboot directory on your PC. Also, save a copy of this renamed TWRP image on your xt1575. Boot your Moto into fastboot mode and connect the device to your PC using an adequate data sync cable. Open a command window on your PC in the path of your ADB/Fastboot directory. After confirming.a proper sync, flash TWRP by executing this command:
fastboot flash recovery twrp.img
Now boot to TWRP using:
fastboot boot twrp.img
Once booted into TWRP, select Install, tap the Install Image option in the lower-right of the display, navigate to the saved location of twrp.img you saved earlier and select it. Now, select Recovery from the partition options presented. Commence installation. When finished, TWRP should be installed properly on your /recovery partition. To ensure its persistence as properly installed, choose Reboot and Recovery.
Now you may install the ROM by the instructions outlined in this thread.
NOTE: There have been reports for years of xt1575 owners encountering difficulty with "making TWRP stick" while using the stock Android OS; i.e., TWRP being overwritten or replaced by stock recovery upon the first reboot to the Android OS following TWRP installation via fastboot. This is a common occurrence on many Motorola devices when TWRP is installed alongside the stock OS. (The best I can recall, this glitch is related to a "boot.p" script present in the stock Android ROM.) The instructions I outlined above can be used as a workaround to this issue to prevent custom recovery from being replaced or overwritten by stock recovery.
For what it is worth, I appear to be using 3.0.2-0. I see that's pretty old, but I don't seem to have any issues.
mddunner said:
For what it is worth, I appear to be using 3.0.2-0. I see that's pretty old, but I don't seem to have any issues.
Click to expand...
Click to collapse
Yeah it's an older version, but other than the upstream codebase, the newer versions for the Clark (built on the Android 9 Pie tree) are not remarkably different in terms of the GUI. For purposes of what we are doing here --installing a stock ROM archived package --pretty well any TWRP or OrangeFox custom recovery build will suffice.
For any members interested, I have updated this build to include Magisk v24.3, BusyBox v1.34.1, and I've done a bit more debloating and added some RAM tweaks on the kernel level. I'll need testers as I no longer own this device. Let me know by leaving a reply if you would like to test. I am posting a link in the downloads section for the updated ROM, but again I emphasize, this is of yet untested.