Ladies and gentlemen, fosseperme present
{
"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"
}
I made the first Android TV 7 port rom for our T95MAX, but I think it should works well on any Allwinner H6. I have entered a big number of optimizations for the processor, there is also Magisk, but it does not work, even if there is a classic root and Youtube and many others apps work at 1080p. Otherwise, everything seems to be going well. The ROM is in TWRP backup format.
HERE THE LINK
https://drive.google.com/file/d/10_xQEyIsTYXVZ4qYf5FOeNiN02HA4RCc/view
FEATURES
- Android ATV 7 with full fake emulation of a device Android Sony Bravia TV 4K 2015
- Stock Root
Magisk implemented but not work
- Netflix latest version full working - only SD but quality near to HD - Youtube, Disney+ and others streaming apps work at 1080p
- Deezer Mod Android TV
- Amazon PrimeVideo in HDR with possibility to buy movies in store with UHD quality
- Many optimizations of CPU and GPU, rom is very fast and stable
- Chromecast seems works in some situation, vocal search not works
- Unlock core frequencies to 1,8GHz / need to execute two scripts includes in app called SH Script Runner at every boot
- DRM Level 3
and many other things...
INSTALLATION
Install by PC with PhoenixUSBPro this clean stock Android 7 Rom, then go to stock recovery. From here launch this TWRP for Tanix TX6 version 7 and restore the entire backup of my ATV ROM, reboot and enjoy it!
ATV7 port for H616
Is it working for H616?
tun9elty said:
Is it working for H616?
Click to expand...
Click to collapse
different SoC so no it won't work.
Hi,
I have a tx6 the sp6330 wif/bt chip.
cant postm the PCB's photo link atm because of message post limitations,
so let me try to work around it.
h t t p s : / / adz3bw.am.files.1drv.com/y4mSlCcD8bJvcZK1XV2H8Z3f4ApxLfx_d5nTmSFNz7weZIvqGfRT7ddeeE_fjPjIA37Dv2adSe0v37cQaKHHYD7MnaVnAOtOzke6woqyFpe30hSDn1FjHz486Zcrevw-SFhnAfAmSN0wLENKhk4nuJN4RTXy7iEsWlNF4J6qRMEwpxW3-EVuSIXbzh-NX5toXa2ETCS1Gh_ThxAZvebIBJlvA?width=256&height=144&cropmode=none
tried these firmwares,
Code:
20190819-Pendoo_x6_pro_4GB_Allwinner_H6_20190819_AndroidPC - LC-X6PRO-4Gddr-20190819 - working wifi bt - video very jerky.img
20191118-Transpeed_6K_H6_4_648M_20191118_1809 - and 9 - working wifi, bt not pair - video very jerky.img
20190722-H6_9_4Gddr_20190722 - tanix logo - And9 -working wifi - video very Jerky.img
were able to flash correctly with wifi/bt and everything ok, however the video playback on all firmwares, there was occasional frameskips that distract you off the content so i am trying anything h6 related... the videoplayback seemed like 12 fps instead of 30.
UPDATE:
I just flashed this rom "T95 MAX-SCV2.img" and I can SAFELY say that this has been the best FW for my TX6 so far!
I tried all these roms and they were all terrible!
20191118-Transpeed_6K_H6_4_648M_20191118_1809 - and 9 - working wifi, bt not pair - video very jerky.img
20200415- TX6S-4G-20200415 - NO FLASH.img 20181219 - Tanix_TX6-SCV1 - and7 no wifi - jerky.img
20181219-TX6_release_H6_7.0_20181219 - android 7 - smooth no wifi bt.img
20181222-TX6_TANIX_H6_7.0_20181222 - and7 no wifi - less jerky.img
20190123- TANIX-TX6_H6_7.0_20190123 - And 7 - no wifi jerky.img
20190228-Tanix_H6_4Gddr_8822bs_20190228 - And 9 - no wifi - jerky playback.img
20190228-TX6_H6_9_4Gddr_8822bs_20190228.img 20190323-Tanix_H6_4Gddr_8822bs_20190323 - and9 no wifi - jerky.img 20190507-Tanix_H6_4Gddr_20190507 - Andv9 - no wifi bt - jerky.img
20190718-H6_7.0_3Gddr_LAGD_20190718 - no wifi portugese.img
20190722-H6_9_4Gddr_20190722 - tanix logo - And9 -working wifi - video very Jerky.img
20190819-Pendoo_x6_pro_4GB_Allwinner_H6_20190819_AndroidPC - LC-X6PRO-4Gddr-20190819 - working wifi bt - video very jerky.img
20191115 - 04 - H6_4_32_20191114_1620_2019111504 - NO FLASH.img 20191118 - Sunvell_boot_package_fex_mod - and 8.1 - no bt wifi - jerky.img
Click to expand...
Click to collapse
Unlike all those firmwares up there...
Wifi/BT works!
DS4 pairs !
Youtube playback is 6 x times better. These videos on youtube played awfully the "motion video test" video from youtube, that video is awesome for device stability testing i tell ya!
Mouse cursor is working correctly, there are no misaligned clicks!.
As far as i could tell, there is no "Hic'Up" effect that drops a frame
No AliceUX BS!
Omg, i am so lucky to come across your post or i would never be able find this so happy already.
Today i am going to test it further by actually watching from it with this new firmware and tomorrow i am eager to restore your TWRP back up on to it. which i have no clue how to do about...
Update 2:
PROS:
So far so far good!
The ultra annoying "100" ms frame freezes are now gone, youtube plays brilliantly and the framepacing is what you would expect for a tighly optimized stream box, as good as Mi Tv Stick minus the sluggishness.
Dualshock 4 did never pair up among those 20 other firmwares however , this FW gets the job done.
Framepacing is almost perfect, a night and day difference.
Not a single annoyance from that dreaded Alice UX notifications (you know it still spammed notifications eventhough not be set the default launcher)
CONS so far:
The device's Ddram is 3gb instead of 4( no big deal)
In Stremio, i hear no sound from most of the sources, are dts 5.1 files supposed to be downmixed to stereo in this box? i am not sure about what has changed.
update : there is something a miss with the codecs installed to this firmware, in stremio, it is nearly impossible to find a source with a working sound... i used to be able to play most x264 files. now none has sound.
I am Curious:
about restoring your ATV TWRP back up... So you saying that the 5mb zip file of yours if going to change the whole OS into a an ATV? I flashed the T95 MAX-SCV2.img already, should keep pushing you say?
"then go to stock recovery. From here launch this TWRP for Tanix TX6 version 7 and restore the entire backup of my ATV ROM, r"
Can you be more newbie-specific? @fosseperme
where is this TWRP app? is this the "Official TWRP app" on play store the correct one?
Where do we put the zip file"TWRP_TX6.zip" to SD card?
does it have to be unzipped to sd card?
how have you flashed it if it wasn't by the OP's method ? if you're using it to be listing it's pros and cons then you've already flashed it.
the OP intended you to flash TWRP (a custom recovery app) from the stock recovery app and then restore the downloaded file as a backup when you're in TWRP.
you might have a menu option that let's you reboot the box or reboot into recovery, bootloader or fastboot. if not you'd need a root app to do that for you (reboot into recovery mode).
from the stock recovery the option you want is most likely install update (I don't know what your recovery looks like), then you'd select the TWRP zip as you've downloaded it. that will eventually open as a new (probably temporary) recovery app TWRP (Team Win Recovery Project) which has much more features than the stock recovery. from there you were intended to select restore backup and choose the downloaded file from google drive. let that run it's course and then when it's finished reboot your device via TWRP.
3mel said:
how have you flashed it if it wasn't by the OP's method ? if you're using it to be listing it's pros and cons then you've already flashed it.
the OP intended you to flash TWRP (a custom recovery app) from the stock recovery app and then restore the downloaded file as a backup when you're in TWRP.
you might have a menu option that let's you reboot the box or reboot into recovery, bootloader or fastboot. if not you'd need a root app to do that for you (reboot into recovery mode).
from the stock recovery the option you want is most likely install update (I don't know what your recovery looks like), then you'd select the TWRP zip as you've downloaded it. that will eventually open as a new (probably temporary) recovery app TWRP (Team Win Recovery Project) which has much more features than the stock recovery. from there you were intended to select restore backup and choose the downloaded file from google drive. let that run it's course and then when it's finished reboot your device via TWRP.
Click to expand...
Click to collapse
the firmware i flashed is the OP's first link that he refers to as "clean rom"
All the pros/cons come out of that.
I mean, the firmware that comes iwth my tx6 was in such a garbage state that i was amazed by just the starting step of the whole his post.
ps: oh i see the "power menu" has that recovery menu
app in the app drawer now, it also has bunch of options other than the power off. (like recovery mode)
i also noticed that by updating the magisk manager, it seems to be working, grating or denying root access to apps.
Anyways
I didn't read fully myself.
the clean link is just an android 7 stock rom and not actually his modified version. once you've flashed that you complete the process as described by going into recovery and flashing TWRP and from TWRP flashing the first link as a backup file.
I could not restore the zipped ATV recovery.
I booted into recovery mode by using this app that came with the fw.
next:
Tried to install from external
But it was just looking at a specific directory for the TWRP zip file.
So i copied the TWRP zip file to where the dir path was targeting.
So i was finally at the TWRP screen.
i copied the 2.5gb zip file (T95_MAX_ATV7FULL_20190112_test-keys.zip) to the root of the SD Card
Next, i chose "recover" ,
but it did not see the zip file.
I unzipped the file , but this time to a bigger SDCARD but again not finding it....
Then i though maybe i should choose the "install option here:
I checed the tickboxes for zip fie verificaion signature before swiping to install
but it gave up errors
and did not continue so i stopped and
now asking , what i am doing wrong.
OK getting into the TWRP menu is where you want to be. look inside the zip file to see if it has folders starting with TWRP and inside that BACKUP and more. if it does copy the whole TWRP folder to your memory card. then when you flash TWRP you should be able to select storage (internal or external) and restore from the external TWRP folder.
I am just going off guesses here, I'm not downloading 2.5gb to find out exactly what's in there. a TWRP backup will normally be a dated folder with lots of individual archives and files, not just one zip file.
Either way , it does not show up.
The sdcard has inside:
The zip file 2.5gb
And an extracted version of it. (Folder with files and folders). Theproblem is when i click thr restore , it ask for what to recover but dont show anything to let me select.
None are visible on the recovery load screen. They are visible on in "install" screen.
you need to answer the question I asked you.
what is the name of the first folder inside the zip file ?
TWRP will only restore files from it's own backups folder
if it's a date and model number and something like release keys xxyyzz then you need to create two folders on the root of your memory card
the 1st one called TWRP in capitals, then inside that another called BACKUPS also in capital letters. then copy the extracted zip folders into it.
it might start with a folder that's the model number of the device, do the same with that (make those folders and copy files to the second folder (backups).
after you've clicked on restore in TWRP near the bottom of the screen there will be an option to select storage. you must select your external storage or you won't see anything.
don't bother trying to use the install option, THAT IS NOT WHAT YOU WANT.
3mel said:
you need to answer the question I asked you.
what is the name of the first folder inside the zip file ?
TWRP will only restore files from it's own backups folder
if it's a date and model number and something like release keys xxyyzz then you need to create two folders on the root of your memory card
the 1st one called TWRP in capitals, then inside that another called BACKUPS also in capital letters. then copy the extracted zip folders into it.
it might start with a folder that's the model number of the device, do the same with that (make those folders and copy files to the second folder (backups).
after you've clicked on restore in TWRP near the bottom of the screen there will be an option to select storage. you must select your external storage or you won't see anything.
don't bother trying to use the install option, THAT IS NOT WHAT YOU WANT.
Click to expand...
Click to collapse
Well, i could not stay patient and decided to make a mini TWRP back up of my current rom, and noticed that it creates a TWRP folder and inside A serliased folder Name, inside the newly created back up. SO i moved the OP's backfile zip file extracter next to that folder and now i was able to restore the ATV rom.
congratulations, you have succeeded at your mission... enjoy!
@fosseperme
I finally used the TWRP back up and realised that the WIFI and BT were not working anymore eventhough the stock firmware that we flashed onto was just fine...
i was too put off by the lack of wifi/bt support of this ATV modification that i had to roll back to the nice and clean stock firmware.
At least i have a proper firmware for the junkbox that Tanix TX6
3mel said:
congratulations, you have succeeded at your mission... enjoy!
Click to expand...
Click to collapse
did not i click "send"?
anyway, thanks for the company btw, thought i did already
i am wondering how he was able to remove the wifi/bt chip support?
The stock rom was able to recognize the wifi/bt chip but the TWRP back up he gave was not, so did he dive into some android OS folders and delete the unnecessary (for his box) drivers manually?
IF so , then it should be possible to reverse that action so that i can add those files to another good ROM that lacks them.
recovery mode
Guys I have stupid question. How to navigate in android recovery mode without volume keys. Because of mine tvbox does not have it.
CheshireZP said:
Guys I have stupid question. How to navigate in android recovery mode without volume keys. Because of mine tvbox does not have it.
Click to expand...
Click to collapse
does mouse mode work on your remote in recovery ? TWRP is a touch based recovery so mouse mode or volume keys on the remote if it's not TWRP. if the recovery wasn't made specifically for your device you probably shouldn't use it.
For the "clean stock Android 7 Rom", is it already in ATV? what is the launcher?
what is the difference between the clean stock and restoration of the TWRP backup rom? The features in OP is available in clean stock?
It would be great to share some screenshots if anyone flashed this.
Thanks fosseperme for porting this.
Related
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Device specific page with install instructions and download links for all current and past versions.
Note: You must be bootloader unlocked to use TWRP.
I realize that someone else already posted TWRP for this device, but this thread means that the Ascend Mate 2 has official support from Team Win and will be included in future updates.
I am having a few issues with MTP and USB Storage modes. We'll try to get those sorted out. I think it's somewhat kernel related.
Dees_Troy said:
Device specific page with install instructions and download links for all current and past versions.
Note: You must be bootloader unlocked to use TWRP.
I realize that someone else already posted TWRP for this device, but this thread means that the Ascend Mate 2 has official support from Team Win and will be included in future updates.
I am having a few issues with MTP and USB Storage modes. We'll try to get those sorted out. I think it's somewhat kernel related.
Click to expand...
Click to collapse
hey Awesome
thanks a lot ..
@modding.MyMind is the one that made the much appreciated alternative but an official channel is very much appreciated indeed
gierso said:
@modding.MyMind is the one that made the much appreciated alternative but an official channel is very much appreciated indeed
Click to expand...
Click to collapse
Yes, thanks to all. (Timestamp on backups appear accurate now. )
Dees_Troy said:
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
Click to expand...
Click to collapse
FYI, The TWRP Manager app doesn't have an "advanced" option in settings and MT2L03 isn't in the device name list yet so the program doesn't work to install the image. Installing via ADB works fine though. I'm sure it's just a matter of updating the app on the Play Store until it does list it though Many thanks for the official support! Even off-mode charging works! Very cool
One question: Are the backups that were created with the unofficial version of TWRP still compatible with this version if I want to restore a backup created in the other twrp with this one will it work?
arcadesdude said:
FYI, The TWRP Manager app doesn't have an "advanced" option in settings and MT2L03 isn't in the device name list yet so the program doesn't work to install the image. Installing via ADB works fine though. I'm sure it's just a matter of updating the app on the Play Store until it does list it though Many thanks for the official support! Even off-mode charging works! Very cool
One question: Are the backups that were created with the unofficial version of TWRP still compatible with this version if I want to restore a backup created in the other twrp with this one will it work?
Click to expand...
Click to collapse
Flashify works very well though. You don't need a computer or ADB after the bootloader is unlocked.
Sent from my MT2L03
What's the difference between this and http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t2885144 ???
unofficial made before the official one got thru
15 devs got mt2l03s at the big android BBQ
So they are the same thing? Or do we need to flash this new one? And how do we get rid of the old one if we do? Sorry too many questions I'm a noob.
Sent from my MT2L03
hope there would be one for mt02-l01/2 too.
Dees_Troy said:
Device specific page with install instructions and download links for all current and past versions.
Note: You must be bootloader unlocked to use TWRP.
I realize that someone else already posted TWRP for this device, but this thread means that the Ascend Mate 2 has official support from Team Win and will be included in future updates.
I am having a few issues with MTP and USB Storage modes. We'll try to get those sorted out. I think it's somewhat kernel related.
Click to expand...
Click to collapse
Thanks for support the device into official TWRP build.
I just submitted an issue regarding the adb, hopefully the working adb can make the MTP/Storage troubleshooting easier.
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/305
EDIT: 2015/01/17, please dis-regards above issue, today, I tested again the adb actually works fine.
Thanks again
xordos.
xordos said:
Thanks for support the device into official TWRP build.
I just submitted an issue regarding the adb, hopefully the working adb can make the MTP/Storage troubleshooting easier.
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/305
Thanks again
xordos.
Click to expand...
Click to collapse
You are a life saver!!! I already did thank you so I will thank you again. I also used google drive so that really helps. I cannot save my backup to my external SD drive. Hope that will be solved in the near future.
husky55 said:
You are a life saver!!! I already did thank you so I will thank you again. I also used google drive so that really helps. I cannot save my backup to my external SD drive. Hope that will be solved in the near future.
Click to expand...
Click to collapse
There are 2 different twrp build/thread in this forum, so please be clear which one you are using. And actually both version support save backup to external sd.
The adb/mtp issue i mentioned above is related to PC connection. The twrp main functions are fully working already
xordos said:
There are 2 different twrp build/thread in this forum, so please be clear which one you are using. And actually both version support save backup to external sd.
The adb/mtp issue i mentioned above is related to PC connection. The twrp main functions are fully working already
Click to expand...
Click to collapse
I used the TWRP manager to install. However when it downloaded and installed it crashed. Something about if this is the folder in your HAM2, yes or no, when clicked no it exited, clicked yes and it crashed. So I rebooted the phone into recovery and lo and behold, TWRP is there for the very first time. I had no idea what version that is.
Prior to all this I used the TWRP installer from the Play Store. It installed some version of TWRP but when rebooted into recovery, it was the Android recovery which showed up and allowed no backup at all. I also have the ROM manager installed. That installed some version of TWRP also.
I spent lots of time trying to backup to my 32GB external SD but I do not see it as an option. I used TWRP before on my Samsung S3 so I am somewhat familiar with it and CWM. I was able to make a copy of the backup file into the external SD using ES file manager. Not sure I can restore from it. I really like to save the internal memory for other things.
I am tempted to flash the twrp.img version 2.8 from your google drive again but I am not sure how it's going to workout.
One last note, I read both threads you referred to and lots more. But for some reason I have a hell of a time for something so simple.
husky55 said:
I used the TWRP manager to install. However when it downloaded and installed it crashed. Something about if this is the folder in your HAM2, yes or no, when clicked no it exited, clicked yes and it crashed. So I rebooted the phone into recovery and lo and behold, TWRP is there for the very first time. I had no idea what version that is.
Prior to all this I used the TWRP installer from the Play Store. It installed some version of TWRP but when rebooted into recovery, it was the Android recovery which showed up and allowed no backup at all. I also have the ROM manager installed. That installed some version of TWRP also.
I spent lots of time trying to backup to my 32GB external SD but I do not see it as an option. I used TWRP before on my Samsung S3 so I am somewhat familiar with it and CWM. I was able to make a copy of the backup file into the external SD using ES file manager. Not sure I can restore from it. I really like to save the internal memory for other things.
I am tempted to flash the twrp.img version 2.8 from your google drive again but I am not sure how it's going to workout.
One last note, I read both threads you referred to and lots more. But for some reason I have a hell of a time for something so simple.
Click to expand...
Click to collapse
OK...Got you. So, I would suggest use the "fastboot flash recovery" command in ModdingMyMind thread, both image file can be used, but I prefer the fastboot way, so we can see what's the output.
Some people has issue re-install TWRP after upgrade to B148, that's why I refer you to
yeah, I forgot that, after update, twrp install may have issues, check this thread around post 169:
http://forum.xda-developers.com/show....php?t=2897452
Click to expand...
Click to collapse
which pretty much says this:
Originally Posted by Kid_Ding View Post
For anyone having issues flashing TWRP after udpate, boot into stock recovery and install update from external SD. The path is above. Then reboot and then reboot to bootloader and flash twrp. Thank @foltz61
Click to expand...
Click to collapse
So, basically you need re-install the B148 update using above particular method, then afterwards, re-flash the TWRP.
We can continue discuss in the other thread.
Cheers.
I installed the TWRP.img latest release from the TWRP web site using ADB fastboot. The file is 14.300 kb in size. TWRP is working properly. I made a recovery backup and restored it. I also had Xposed Installed and some modules installed. When the HAM2 is on and charging everything is normal. i.e working properly.
The problem is when the HAM2 is off and charging, suddenly TWRP started. I got the slide to Unlock from TWRP. There was nothing that I could pinpoint on that would cause this. I installed Boot Manager but it did not show TWRP as being a application which should or will start at boot up.
I know this is a minor annoyance but being trained technically it bothers me. Is there anything I can do to prevent TWRP from starting when plugging in the micro usb connector to a HAM2 in the shut down state.
yes, this is a known issue about off mode charging. we have v2 fixed it (it is in the google drive i shared) but we never release it. because the official twrp team build released in this thread and it works fine.
So now that school is over (for now), I finally downloaded this installer and the correct recovery for the phone, and now it is asking me this:
{
"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"
}
Is it just asking me to verify that the path exists?
Sorry I installed twrp so long ago I don't remember. Are you sure you got the 2.8.0 for the right version? The 2.8.1 is for the 05's and not the USA 03's.
oncouch1 said:
Sorry I installed twrp so long ago I don't remember. Are you sure you got the 2.8.0 for the right version? The 2.8.1 is for the 05's and not the USA 03's.
Click to expand...
Click to collapse
There are 2 versions available for the MT2L03: 2.8.0 and 2.8.3. Both give me that same warning message. Can anyone help?
I just got this Huawei HUAWEI Y550-L01 for a great price and it's a massive improvement on my G300 (which actually cost me about double what I paid for the Y550 a couple of years ago!)
There doesn't seem to be any custom ROMs available for it yet but I was wondering if it's possible to just root it, as there's quite a few apps I like to use that require root?
I've e-mailed Huawei and they've sent me my bootloader unlock code but unless I can root it, there's probably not much point doing that at the moment.
Thread Index
Rooting, CWM & TWRP Instructions LINK
Latest TWRP
TWRP 2.8.7.0 21/8/15 - CM12 compatible
2.8.7.0 Final 25/1/16
Older TWRP TWRP 2.8.4.1 31/1/14 - CM11 compatible
Latest CWM 9/12/14
Latest Superuser 9/12/14
Latest Slim SDK 9/12/14
Stock Rom Recovery Link (Install through fastboot - fastboot flash recovery recovery_y550.img)
Updated LInk Here
Latest Y550 (L01) Stock Rom
5/11/14 Western Europe
16/1/2015 Eastern Europe & Scandinavia
Normal upgrade/reinstall using in built updater Link
Forced upgrade/reinstall procedure Link
Upgrade/Reinstall using Fastboot Link
Google Stock Apps Link
All Huawei y550 related apps and files (thanks to klaidone) Link
Alternate unlock code methods Link Link
And another Link
L02 Files
All At this URL
Files:
Update.zip - the latest OTA update for L02 Region Phones - Applied using inbuilt updater
Y550-L02 Stock - CWM backup of the original L02 Stock Rom Link
Y550-L02 (Build 346) - CWM Backup of the most up to date L02 Rom Link
Credits to Happychappy on the Whirpool Forum
Y550 (Prob L02) TWRP Stock Backup
Faq/Tips
Will the L01 rooting method work on my L02 Yes
Can I change the Boot Animation? Link (And the following post)
Can I use L01 firmware on my L02? Link
Can I change the status bar and carrier logo? Link
Does Exposed framework work on this phone? Link
How do i remove the Kitkat write restrictions? Link
Roms from HB72K
Stable and suitable for everyday use. More information, install instructions, root etc from user @HB72K in This post
AOSP Based Roms
Carbon Rom from Hb72k Link & Install instructions - Known Bugs: Phone only rings once then mutes
Stock Based Roms
Y550 Stock Rom by Hb72k Link
Y550 Stock Lite by Hb72k Link
Y550 Stock (Gstock 2) by Hb72k Link
Y550 Stock (Gamer 2) by Hb72k Link
MIUI Based Roms
MIUI 7 by Hb72k Link
MIUI 6 by Hb72k Link
CM Roms
CM11 - Final XDA Build by Hb72k link
Hecaex Build - 11 June 2015 Link Doesnt include Static Mac Address fix
Hecaex Build - 30 May 2015 Link This is based on Patrick's march build with Camera modifications. Working Wifi (Random Mac), Camera working (But flash not working)
Patrick KT Build - 11 March 2015 (CM11) Link - Wifi working but with random Mac. Camera not working
Hecaex Build - 10 February 2015 (CM11) Link - Camera flakey, superuser and torch not working
Patrick KT Build - 1 February 2015 (CM11) Link - Wifi and Camera not working
Static Mac Address Fix Link
Camera Patch Only Link
2016 Roms
Modded EMUI 3.0 https://mega.nz/#!Dt4gGQCD!zEvIGHsuZURN7Xl9F3LnAdRDviTo-BLzC0n42YH9ZjM
Modded Miui 7.0 (Twrp backup) https://drive.google.com/folderview?id=0BzJ-jN4Pv2baSXFwRFpqcGoySUE&usp=sharing
CM Patches/Fixes
EMUI (Hb72k) http://forum.xda-developers.com/showpost.php?p=65241854&postcount=2268
Pacman (hb72k) http://forum.xda-developers.com/showpost.php?p=65327203&postcount=2281
Pacrom (Jeffta) http://forum.xda-developers.com/showpost.php?p=65353386&postcount=2284
Miui7 (Dabi01 almost final) http://forum.xda-developers.com/showpost.php?p=65702075&postcount=2334
Other Files
Walkman (Zip) for Stock and Custom Roms Link
IVE BRICKED MY PHONE!
Download the full Huawei Y550 rom from Here (You want the penultimate file - y550 build 239
Download the Huawei update extractor from the same link
Run update extractor and extract the rom
Copy the entire folder "dload" to the root of your sdcard (so there is a folder on your sd card called dload containing the update file)
Hold down all physical buttons on your phone - volume up, volume down and power at once
dimspace said:
Im still waiting for my unlock code, once i get it will look at it. pretty sure rootgenius will do it as it does most Huawei's. Then i will put something together, as well as bit of review and impressions of the phone
Click to expand...
Click to collapse
That'll be great, thanks :good:
doveman said:
That'll be great, thanks :good:
Click to expand...
Click to collapse
Root Genius didnt work
Framaroot didnt work
Eroot didnt work
SRS One Click didnt work
Vroot didnt work
Kingoroot didnt work
For now i dont think we have root on Y550
Apart from anti virus, theres not much i need root for, but the two key things changing the dpi (because the resolution isnt good enough), and full link 2 sd (because of the lack of storage space) are kinda important
Its a pretty new phone though, pretty sure root will be around soon enough.
BTW.. can you change title to Y550 rather than 500.. help people using the search function.
dimspace said:
Root Genius didnt work
Framaroot didnt work
Eroot didnt work
SRS One Click didnt work
Vroot didnt work
Kingoroot didnt work
For now i dont think we have root on Y550
Apart from anti virus, theres not much i need root for, but the two key things changing the dpi (because the resolution isnt good enough), and full link 2 sd (because of the lack of storage space) are kinda important
Its a pretty new phone though, pretty sure root will be around soon enough.
BTW.. can you change title to Y550 rather than 500.. help people using the search function.
Click to expand...
Click to collapse
Woops, yep done.
Oh well, thanks for trying.
Yeah, lack of space and inability to use link2sd was the main reason I wanted root, although there's quite a few apps I use that need it too. Apart from that though, the missing encryption feature kills it for me. I e-mailed Huawei asking why it was missing but they haven't replied!
I have filled out the email response form on a couple of the root methods asking for Y550 to be added if possible. It was only launched in October, and November for most of UK so its pretty new, but generally there is root out there for most Huawei phones.
Most apps can be moved to SD the native way using app manager or similar but its the space hogging ones like Facebook that cant be.
For those passing by this thread, make sure you set SD as default in settings>Storage and then select defaut storage location as SD
and for ref:
CPU: Qualcomm MSM8974 (think this is a misidentifiation. meant to be MSM8916) Snapdragon 800 x 4 on Elpida (Krait 400 Arm 7)
GPU: Adreno 330
Overall, on the phone its not a bad bit of kit, was bought to replace a dying Galaxy S2 and the specs are pretty much the same as the S2, more CPU but less Storage.
Negatives:
Lack of storage space, about 1.3gb at stock
Screen Resolution: Is fairly low but actually looks pretty good. Just needs the DPI dropping down a bit.
The Huwai stock launcher is pants (but easily replaced)
The Good:
Battery life at the moment seems pretty good. Using it all day, whatsapp, twitter, music player (but no games), ive not come close to having to worry about a charge
Included apps: You can actually remove the bulk of the bloatware and most of the included apps are reasonable. The backup program is functional (but let down by lack of scheduled backups), the messaging and contacts replacements are passable (but lacking merge contacts), the power management is actualy fair good with good contral of which apps are shut down to save battery and which stay open, good control of which apps are allowed to push notifications etc so that aspect of it is good.
Camera: average, but fast and functional. Good enough for snaps, but lacks obviously from only being 5mp
Mobile internet is snappy as hell
The Meh..
Not totally convinced about the settings, drop downs etc with the MIUI styling on them,
Benchmarking
i got
12147 with quadrant
19454 with Antutu (let down by cat 4 SD)
Which to be honest, for a £100 phone aint bad.
dimspace said:
Benchmarking
i got
12147 with quadrant
19454 with Antutu (let down by cat 4 SD)
Which to be honest, for a £100 phone aint bad.
Click to expand...
Click to collapse
Down now to £69.99 on O2 Paygo
£1.47 on Ebay to unlock.
this phone is £49.95 on PAYG upgrade from carphonewarehouse.
The Ascend y550-L02 is now available in Australia through Vodafone PAYG for $99 AUD (including some pretty sweet extras), making it perhaps the cheapest 4g LTE option in OZ. All the standard one click root methods already mentioned don't work with this sub model either. A new root would be very appreciated! Unfortunately I'm not a developer, but I do like to reward those who are smarter than me and allow me to tweak my devices. Thanks in advance!
There's a cwm boot image been put on German forums. Not at pc now. Will post info tomorrow
dimspace said:
There's a cwm boot image been put on German forums. Not at pc now. Will post info tomorrow
Click to expand...
Click to collapse
Looking forward to it. Would you post step by step instructions? Thanks!
DISCLAIMER - THIS CWM AND ROOT METHOD IS DESIGNED FOR THE G620 - IT IS ESSENTIALLY THE SAME PHONE BUT LIKE ANYTHING THERE ARE ALWAYS RISKS WITH INSTALLING CWM AND ROOTING YOUR PHONE. IT WORKED FOR ME, BUT I BEAR NO RESPONSIBILTY IF IT DOESNT WORK FOR YOU, BRICKS YOUR PHONE, OR TURNS YOU INTO A PUMPKIN.
Ok, rooting the Huawei Y550..
Source Credits Here and Here
Originally this is the boot image for the G620 but it has the same partition table as the Y550
Three step method - first you need your bootloader unlocked, then CWM installed, then superuser installed.
First you will need your bootloader unlocked. You can get this by emailing Huawei
to get your unlock email Huawei on [email protected]
Send them a request for bootloader unlock with the following info:
Serial Number: under battery
IMEI: under battery
Product ID: call * # * # 1357946 # * # * to get it
Model: HUAWEI Y550-L01
Once you have your code...
switch device off
boot into fastboot mode "volume down and power"
connect by usb to your PC
wait for drivers to install (just install the huawei app to get the drivers)
download and install ADB toolkit from google (or Android SDK Slim which ive attached as a zip)
open the directory adb toolkit is in, shift and right click and select open command window
type in... fastboot oem unlock 1234567812345678 where the number is your unlock code
Your bootloader will now be unlocked. Source and more info
Update: Alternate way to get the unlock code Link
UPDATE - TRWP RECOVERY
We now have TWRP thanks to patrik.KT. Source
1) Download the TWRP Image file Link
2) Place the image file in the same directory as fastbook.exe from the previous step
3) Connect phone in fastbook mode
4) Check compatability by booting only initially.
Code:
fastboot boot TWRP_y550_20150130.img
5) if boots correctly go back into fastbook mode and run in the dos window
Code:
fastboot flash recovery TWRP_y550_20150130.img
CWM Recovery
Zip file download Link
Extract zip file to computer
Put phone in fastboot mode (Down volume and power button)
Connect phone to PC and run the file - install-windows.bat
This will install a CWM boot to your phone and then reboot it
Contents of zip showed up clean with McAfee
{
"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"
}
Superuser
Dowloaded superuser.zip from HERE
(Do not use Super-SU it doesnt work with stock roms)
copy superuser.zip to your SD card.
Boot into CWM (Volume up and power key)
select english language if prompted
install zip from SD card and install superuser.zip
Boom....
Phone has CWM and Root.
Only downside is parts of the CWM (notably the backup section) are in chinese
Translation for backup section is:
backup image to internal SD
restore image from internal SD
delete image from internal SD
restore image with options from internal SD
backup image to external SD
restore image from external SD
delete image from external SD
restore image with options from external SD
Note: I tested on L01 model, not tested on L02 etc.
Wonder if this will work for the Huawei Y536A1 (At&t Tribute) as it is almost the same phone as the Y550?
aross6 said:
Wonder if this will work for the Huawei Y536A1 (At&t Tribute) as it is almost the same phone as the Y550?
Click to expand...
Click to collapse
Well theres one way to find out.
Joking aside, I dont know, would be a risk trying it (but then me trying g620 method on my y550 was a risk)..
Hard to find specs on the Tribute but all i can find...
1.2ghz quad core - the same
screen 480 x 854 pixels, 4.5 inches - the same
internal storage looks to be the same or similar, i have 1.6 gig on my y550, ive seen 1.62 reported for the y536, but it would need the partitions to be the same.
Y536 specs Link
Y550 specs Link
Pretty much all the specs are the same, slightly different size and weight.
Would be a gamble... but if you only paid $40 from walmart not a very expensive gamble.
Word of Warning - there are various stories that AT&T dont sell phones with unlockable bootloaders or dont allow them on their network. Not sure how reliable these rumours are
No problem with the unlocked bootoader on At&t's network on my Mom's Y536... just my $.02
Nice one dimspace. It seems to have worked on my Y01, at least CWM is installed and so is SuperUser.
I'm having a bit of trouble verifying though, as I don't really want to setup my Google Account on this phone (I already spent a while before erasing the storage). I downloaded this root checker http://forum.xda-developers.com/showthread.php?t=2472076 which shows
"Application Superuser found"
and then in red
"Terminal does rooted
Busybox not installed"
so do I need busybox installed to check root? If so, which of these zips should I install:
http://forum.xda-developers.com/showthread.php?p=44175626#post44175626
http://forum.xda-developers.com/showthread.php?t=1929852
or maybe there's a newer version I need to install? Do I need to install it from CWM?
I use Jrummy Rootchecker..
You can download the apk without play store and just sideload it from SD.
use APK Downloader
just put the apps id in the box and generate download link, and you can download the apk direct.
The Jrummy rootchecker address is com.jrummyapps.rootchecker
For busybox, again just install busybox installer from play store (or download apk as above) id is com.jrummy.busybox.installer - then run it and follow the instructions to install busybox
For terminal - use terminal emulator - id is jackpal.androidterm
all three of those working fine with me and i have full root, busybox and terminal.
the busybox installer will automatically check root, and download the applicable busybox for you, terminal installs as a normal apk. but you dont NEED them as long as your root is working. some applications do need busybox, but you dont have to have terminal.
---------- Post added at 02:16 AM ---------- Previous post was at 02:13 AM ----------
aross6 said:
No problem with the unlocked bootoader on At&t's network on my Mom's Y536... just my $.02
Click to expand...
Click to collapse
yeh, id heard stories of At&t phones not allowing unlocked bootloaders, i was just covering myself really
After reboot. Busybox installed.
----------------------- 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..
Hi,
Recently i purchased Cube iWork10 Ultimate 64GB Intel Atom x5 Z8300 Quad Core 10.1 Inch Dual OS Tablet and something wrong went with android side, I am not able to use it so i search for official firmware and did not find. I found firmware for tablet SN number start as i15TC,i15TD and i15T.
http://www.cube-tablet.com/download
http://www.51cube.com/ch/DownList.asp?SortID=7
I installed following img on my device
https://forum.xda-developers.com/android/development/rom-stock-cube-iwork-10-flagship-i15-t-t3372281
Camera did not work at all. Second problem i can not change Auto rotate when i want (with game work like it should).
I resize partition by using Phone Flash Tool and X98 serie GPT file
https://4pda.ru/forum/index.php?showtopic=725568
https://techtablets.com/forum/topic/resize-android-partition-the-easy-way-for-x98-serie/
I contact resller (banggood) to provide me official firmware and unfortunately they ignore my email. Then I create new topic in thier site to ask about firmware and got link for firmware but i think i need password in order to download firmware. Here is my topic
http://forum.banggood.com/forum-topic-307419.html
Then i went to http://www.51cube.com/ to check if there is any email to contact them about firmware and i sent couple emails to most of them and unfortunately they ignore my email. I resent the same email and got answer from Eddy with official firmware ( i told Eddy that reseller ignore my email then he provided me link for official firmware).
https://pan.baidu.com/share/link?shareid=467329010&uk=3474489303#list/path=/
to download from pan.baidu.com i follow these step:
https://www.gizdev.com/download-files-pan-baidu-com/
Details about my device:
{
"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"
}
Anyone have idea how to root firmware for i15-TFL?
I think the correct place for my thread is to put it in xda-developers iwork-10
https://forum.xda-developers.com/t/iwork-10
but i am not able to do that because rules of this forum (to prevent spam, you must have a higher post count in order to make a new thread in this development section.�But feel free to make new thread in the non-development sections like General, Q&A, etc. Thanks for your understanding! )
Thanks in advance
Hello, I`ve met the same problem with same device with unknown revision serial "i15TFL": I`d flashed TWRP and Android stop starting proper.
Have you managed to restore the original Android on your device? Please give me instruction how to do this, and, if you could, post firmware files to Google Drive (Baidoo cloud speed really low).
nm101 said:
Hello, I`ve met the same problem with same device with unknown revision serial "i15TFL": I`d flashed TWRP and Android stop starting proper.
Have you managed to restore the original Android on your device? Please give me instruction how to do this, and, if you could, post firmware files to Google Drive (Baidoo cloud speed really low).
Click to expand...
Click to collapse
I resize partitions and restore the original firmware on my device by using Phone Flash Tool 5.3.4.1 and X98 serie GPT file ( i have chosen gpt_20g_org)& TWRP Boot.
In the android firmware, replace the file gpt.bin
On the computer, install and run the Intel Phone Flash Tool . Click Browse ... , select the flash.json file, in the Configuration: field , set the recover option .
We translate the tablet into DNX FASTBOOT MODE , for this, on the off tablet simultaneously press and hold the On and both volume buttons . USB-cable connect it to the computer, make sure that the program saw it and click Start to flash
The first launch will take a lot of time, be patient
Then i installed window.
Everything worked like it should but without root
I can upload firmware to Google Drive but can not post link coz (To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!)
All data will be deleted. Everything you do, you do at your own risk.
Mathias31 said:
I resize partitions and restore the original firmware on my device by using Phone Flash Tool 5.3.4.1 and X98 serie GPT file ( i have chosen gpt_20g_org)& TWRP Boot.
In the android firmware, replace the file gpt.bin
On the computer, install and run the Intel Phone Flash Tool . Click Browse ... , select the flash.json file, in the Configuration: field , set the recover option .
We translate the tablet into DNX FASTBOOT MODE , for this, on the off tablet simultaneously press and hold the On and both volume buttons . USB-cable connect it to the computer, make sure that the program saw it and click Start to flash
The first launch will take a lot of time, be patient
Then i installed window.
Everything worked like it should but without root
I can upload firmware to Google Drive but can not post link coz (To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!)
All data will be deleted. Everything you do, you do at your own risk.
Click to expand...
Click to collapse
Thanks.
Please send me link to firmware and utilities using PM or email: "m e l n i k o v s m 2 @ g m a i l . c o m" without spaces. I have no time to wait until it will be downloaded with Baidoo speed (~10kbps). Thanks in advance, you'll seriously help me.
Mathias31 said:
All data will be deleted. Everything you do, you do at your own risk.
Click to expand...
Click to collapse
Even Windows 10 installation will be wiped?
P.S. Send me firmwares GDrive links pleeeaasee.
nm101 said:
Thanks.
Please send me link to firmware and utilities using PM or email: "m e l n i k o v s m 2 @ g m a i l . c o m" without spaces. I have no time to wait until it will be downloaded with Baidoo speed (~10kbps). Thanks in advance, you'll seriously help me.
Click to expand...
Click to collapse
I have sent pm to you with sharing link (android firmware for i15-TFL). Sorry for delayed response
nm101 said:
Even Windows 10 installation will be wiped?
P.S. Send me firmwares GDrive links pleeeaasee.
Click to expand...
Click to collapse
Yea even win 10 will be wiped, you have to re install it. I have sent pm with android firmware link for i15-TFL. I had uploaded to google drive
Thank you wery much. I am even managed to get working Remix OS and Rooted stock Android (I don`t test it, but it should work) images.
How to install:
1. Download this firmware and flash via Intel Platform Flash Tool.
2. Put Rooted stock Android or Remix OS zip into internal memory or sd card.
3. Make sure you had activated "Enable OEM Unlock" in Android Developer`s menu.
4. Boot into recovery (choose android boot then hold Volume Down, in appeared menu choose recovery, device will reboot, then again choose android.. welcome to TWRP).
5. Install zip via TWRP.
Notice: Never never ever upgrade SuperSU APK. After upgrade it`s unable to update binary and stop functioning at all.
Notice: At RemixOS cameras does not work at all.
nm101 said:
Thank you wery much. I am even managed to get working Remix OS and Rooted stock Android (I don`t test it, but it should work) images.
How to install:
1. Download this firmware and flash via Intel Platform Flash Tool.
2. Put Rooted stock Android or Remix OS zip into internal memory or sd card.
3. Make sure you had activated "Enable OEM Unlock" in Android Developer`s menu.
4. Boot into recovery (choose android boot then hold Volume Down, in appeared menu choose recovery, device will reboot, then again choose android.. welcome to TWRP).
5. Install zip via TWRP.
Notice: Never never ever upgrade SuperSU APK. After upgrade it`s unable to update binary and stop functioning at all.
Notice: At RemixOS cameras does not work at all.
Click to expand...
Click to collapse
Np. Thank you for sharing your experience. I knew this method and its for re install android firmware but still have 2 problems I have mentioned it(check out first post) Camera did not work at all. Second problem you can not change Auto rotate when you want (with game work like it should). Also there is video showing how to install RemixOS in our devices, search in youtube ([SL] 043 Cube Iwork 10 Ultimate: How to flash ROM + root + MIUI + play.google + 512mb videocard - YouTube). You can follow the same step to install different img. I tried 6 different img and all of them have the same problem with auto rotate and camera. I resized partions coz android side have just 8 GB and its not enough for my games.
all imgs which i found and img which you provided not for i15-TFL . Its for iWork10_V1 and i15-T
But at rooted android image everything ok with camera and autorotation, after 1 day of RemixOS usage I decided it's better for me to return to stock os, but I also need root permissions. So, my experience is successful, everything still unresolved is sd card unmount during device sleep. But I detected it even on stock image.
nm101 said:
But at rooted android image everything ok with camera and autorotation, after 1 day of RemixOS usage I decided it's better for me to return to stock os, but I also need root permissions. So, my experience is successful, everything still unresolved is sd card unmount during device sleep. But I detected it even on stock image.
Click to expand...
Click to collapse
For me with rooted android img camera & auto rotation. I had problem with sd card mount and unmount and i fixed it by uninstall supersu and install just busybox. Then i decided to resized partions ( 20 GB for android and rest for win) and i used sd in win side to install program&game. To do that search in youtube (Install any Windows programs or applications on microsd card Tech Guy Charlie).
Hello thank you for your Help.
The Root is there and the auto rototion is working.
But i have one problem there, the canera is not working after installing the rom via TWRP.
Is it a bug?
Mathias31 said:
For me with rooted android img camera & auto rotation. I had problem with sd card mount and unmount and i fixed it by uninstall supersu and install just busybox. Then i decided to resized partions ( 20 GB for android and rest for win) and i used sd in win side to install program&game. To do that search in youtube (Install any Windows programs or applications on microsd card Tech Guy Charlie).
Click to expand...
Click to collapse
Do either @Mathias31 or @nm101 have links to the firmware and ROMs which you used to resolve the rotation and camera issues you experienced? I tried the previous links and it looks like they have expired....
denndsd said:
Hello thank you for your Help.
The Root is there and the auto rototion is working.
But i have one problem there, the canera is not working after installing the rom via TWRP.
Is it a bug?
Click to expand...
Click to collapse
Did you get your camera to work? My rotation and camera are not working...
OEM Win10 and Android both (GDrive)
I'd uploaded this one year ago at 4pda (russian forum), but totally forget about this thread.
Also, as I noticed, camera and rotation sensor works right on original firmware only.
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.