Related
[SIZE=+3]Heisenberg's How-To Guide For Beginners[/SIZE]
{
"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"
}
[SIZE=+2]Moto X Pure[/SIZE]
[SIZE=+1]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Moto X Pure. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
[size=+1]Prerequisites[/size]:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You'll find Motorla drivers here, download it and install, then reboot your PC.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
[SIZE=+1]Index[/SIZE]
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
[SIZE=+1]1. How To Unlock Your Bootloader[/SIZE]
Go into About Phone in Settings, click on Build Number 7 or 8 times until it says you have enabled Developer Options. Go back to Settings and enter the newly opened Developer Options section, scroll and click on the Enable OEM Unlock option.
Power off your phone then boot into fastboot mode (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem get_unlock_data
It should return something like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy that code (with no spaces between the characters) and paste it somewhere for safekeeping, you'll use it in a minute.
Go to the Motorola bootloader unlocking page. You'll need to create an account with Motorola if you don't already have one. Once you're signed in you can scroll down to step 6 and paste the above code into the text field and hit the “can my device be unlocked” button.
Read the terms and conditions and accept them if you agree (you can't continue unless you accept).
Click the “request unlock key” button and an email with your unlock token will be sent to the email account that you signed up with.
Once you have retrieved the token from the email you can use it within the following command to unlock your bootloader:
Code:
fastboot oem unlock xxxxxxxxxx
(Replace the xxxxxxxx with your unique unlock token)
Your bootloader is now unlocked!
Reboot with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
[SIZE=+1]2. How To Install A Custom Recovery On Your Device[/SIZE]
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery <filename>.img
(Replace <filename> with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
[SIZE=+1]3. How To Make A Nandroid Backup With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
[SIZE=+1]4. How To Root Your Stock Rom[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Please note: this method is only valid for Lollipop, do not use this method on Marshmallow. You can find a systemless root method for Marshmallow here, big thanks to @ivcarlos!
Download SuperSU to your phone.
Boot into TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to where you have SuperSU stored on your sd card and select it.
Swipe to install.
Once you've installed SuperSU you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
[SIZE=+1]5. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
[SIZE=+1]6. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+1]7. How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
There may come a time when you accidentally wipe your OS while trying to perform a basic cache wipe in recovery. Don't laugh, it can happen to the best of us. The best way to insure yourself against being stuck in recovery is to keep a ROM zip or a TWRP/CWM backup (a nandroid backup) on your sd card at all times.
This solution seems like common sense but apparently there are quite a few people out there who don't store a ROM or backup on their phone. You might think it's easy to just mount the OTG storage and copy a ROM across to your phone from your PC (which is definitely an option), but there's always a chance that you won't be near your HDD or sd card at the time, or it won't recognise your phone properly. Basically you need to insure yourself against Murphy's law.
Donate To Me
This will be very helpful to many thanks for taking the time to put this together!
Sent from my XT1575 using Tapatalk
Thank you so much for taking the time on the guide. There will be many who will use it in the years to come! I'm just about at the verge of needing to root so I can get some insight into my battery life woes
This is much appreciated. All I did on my LG G2 was root as I did not see any roms that interested me since the bootloader is locked. I haven't used TWRP in a couple of years, so all this will help me clear the old cobwebs in my head.
Thank you so much for this! Exactly the kind of information I need. Can I trouble you to maybe add one more section to your guide: What to do when there's an OTA update from the manufacturer (Motorola)? I have concerns like:
- Would being rooted prevent OTA updates? (Assuming stock ROM).
- Would I need to "unroot" the phone to get the update? If so, how to unroot the the phone?
- Is the process to root the phone again after the the update the same, or could it possibly change?
- Would I need to wait until root is confirmed for the new version before attempting to re-root?
You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
elitemeat said:
You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?
Click to expand...
Click to collapse
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.
Oops
emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
Thanks for your suggestions.
1. This info has been added.
2. This section is in the same place in all of my guides, I see no problem (and have had no problems) with its location. Anyone following a guide should read it first before attempting it anyway.
3. I've added inductions to download the zip directly to the phone, less mess.
emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
This is already covered here:
http://forum.xda-developers.com/moto-x-style/help/root-to-updates-t3200588
Oaklands said:
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.
Click to expand...
Click to collapse
If you're on Windows, I highly recommend this one, I've been using it for ages: http://code.kliu.org/hashcheck/
I flashed SU and it didn't give me root, any suggestions?
mxpxboi said:
I flashed SU and it didn't give me root, any suggestions?
Click to expand...
Click to collapse
Have you enabled root for apps (and adb if you wish) in Developer Options?
Heisenberg said:
Have you enabled root for apps (and adb if you wish) in Developer Options?
Click to expand...
Click to collapse
I don't see root for apps in Developer Options.
mxpxboi said:
I don't see root for apps in Developer Options.
Click to expand...
Click to collapse
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.
Heisenberg said:
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.
Click to expand...
Click to collapse
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.
mxpxboi said:
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.
Click to expand...
Click to collapse
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?
Heisenberg said:
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?
Click to expand...
Click to collapse
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.
mxpxboi said:
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.
Click to expand...
Click to collapse
Cool, I've updated the link. There's a thread discussing how to remove that boot screen in the q&a or general section. Not sure about your Titanium problem, if you have root access it should work.
This is a very nice budget tablet from Tablet Express. I found mine on eBay for $93.00, new + free shipping, and have been very pleased with it. I love that it came with Developer Options already on, had USB Debugging enabled right out of the box, and has a screen protector installed by the manufacturer. Add the fact that the bootloader isn't even locked, and you really can't go wrong with this device.
I used the AIO TWRP Compiler script by @yuweng, to build this recovery, it's a very efficient tool to work with and he put a lot of work into it. Many, many thanks there!!
Well, enough rambling, lets get started...
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR TABLET!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!! (Or ask for help, there's a lot of friendly people around here)
Verify Partition Scheme
Over the past few months, it seems some devices have different names for the partition scheme, either "nand" or "mmcblk". So, the first step will be to check which type you have before installing TWRP and rooting the device. Here's how you check:
1) Connect the device to your PC, and open a terminal
2) Type the following:
Code:
# to make sure the device is recognized:
adb devices
# result should be:
List of devices attached
00000000000000000000 device
# Now type:
adb shell
# followed by:
ls -al /dev/block/by-name
# First Line should be 1 of the 2:
# This is a "mmcblk" device
lrwxrwxrwx root root 2016-07-20 00:08 UDISK -> /dev/block/mmcblk0p1
# This is a "nand" device
lrwxrwxrwx root root 2016-07-20 00:36 UDISK -> /dev/block/nandk
Once you know which device type you have, follow the below directions accordingly.
Root (Works for Android 4.4.4 and 5.1.1)
Rooting the device is easy, there are two methods that I know work:
1) Install TWRP, then flash Chainfires current SuperSu zip, find it Here (<-- recommend method)
2) Using Kingo Root for PC, find it Here (Use the Root Again option)
Install TWRP
You should already have ADB installed on your PC, or BusyBox and Terminal Emulator installed on your tablet, I will not cover installation of either of those. And you should know which type of mount partitions your device is using. To get the TWRP recovery on your device, you have a few options:
1) Use ADB to "push" the image (Android 4.4.4 and 5.1.1)
2) Use the included shell script, via BusyBox and Terminal Emulator (Android 5.1.1 and the device must already be rooted to use this option)
Download the appropriate zip for your device, located below, under Downloads, and extract it to a convenient location on your PC. If using your Tablet, the shell scripts and TWRP image must be in the root directory ( / ) to work properly.
Using ADB (Android 5.1.1) on "nand" partitions
Put the X10_twrp3.0.2.img file in the same directory as your working ADB, then enter the following:
Code:
adb push X10_twrp3.0.2.img /dev/block/nandf
#After it finishes:
adb reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That was easy, yes?
Using ADB (Android 5.1.1) on "mmcblk" partitions
Put the X10_twrp3.0.2.img file in the same directory as your working ADB, then enter the following:
Code:
adb push x10_twrp_mmc.img /dev/block/mmcblk0p9
#After it finishes:
adb reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That was easy, yes?
Using ADB (Android 4.4.4)*As of now, KK uses "nand" ONLY
This is the only way I could get it to work right on KitKat, sorry, no Terminal Emulator for this one...
Put the X10_twrp2.8.7.0.img file in the same directory as your working ADB, then enter the following, one line at a time:
Code:
adb push X10_twrp2.8.7.0.img /data/local/tmp
# Wait for it, then type:
adb shell
#Followed by:
dd if=/data/local/tmp/X10_twrp2.8.7.0.img of=/dev/block/nandf
#After it finishes:
reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That wasn't too bad, was it?
Using Terminal Emulator (Android 5.1.1 using "nand" ONLY)
Put the X10_twrp3.0.2.img and twrp.sh files in the root ( / ) folder of your tablet, then open the Terminal Emulator, enter the following, one line at a time:
Code:
su
sh twrp.sh
The script will tell you when it's done, now, power off the tablet. Boot into recovery by pressing and holding the Volume Down and Power Buttons. When the Dragon Touch logo appears, release the Power Button but continue to hold Volume Down until TWRP boots.
I hope you enjoy my work, and keep in mind that I like to keep things up to date, when a new version of TWRP comes out, I'll build it and post it here.
Downloads
X10 TWRP for "nand" devices
X10 TWRP for "mmcblk" devices
~ Also see Extras Section Below ~
Credits
@yuweng (bunch of help there)
@MSF Jarvis
@trillwizzard (for mmc fix)
@amw2320 (for modified firmware)
TeamWin
Extras
Themes for TWRP
TWRP 3.x Themes for Tablets (Landscape Devices)
Factory Firmware
TabletExpress.com
Modified Firmware
X10-V2-5.1-amw-TWRP_SuperSU.img (Created by: @amw2320, has TWRP (nand) and SuperSu already installed)
Using PhoenixUSBPro
My "short" guide on using the PhoenixUSBPro tool can be found here
X10 Device Tree (For Android 5.1.1)
GitHub
Change Log
Change Log (Newest First)
Added modified stock firmware (8-20-16)
Added info about devices using "mmcblk" instead of "nand", provided TWRP for each (7-23-16)
Added TWRP 2.8.7.0 for KitKat (Android 4.4.4) users and flash instructions (5-19-16)
@NepoRood, great work! One suggestion, instead if using the PRODUCT_COPY_FILES, you can simply add DEVICE_RAMDISK_(DIRS|FOLDERS) += rootdir
I am sure the flag has dir rather than folder in its name, but you can easily confirm that from the thread and you have to use an absolute path for folder name, so include the device/vendor/codename also, before rootdir.
MSF Jarvis said:
One suggestion, instead if using the PRODUCT_COPY_FILES, you can simply add DEVICE_RAMDISK_(DIRS|FOLDERS) += rootdir
Click to expand...
Click to collapse
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
NepoRood said:
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
Click to expand...
Click to collapse
That's what I'm here for, no?
Great job tested with backup and cache cleaning and it worked great now I just need to find a custom rom any of you know of any?
Sent from my SM-G530T1 using Tapatalk
Franzferdinan51 said:
Great job tested with backup and cache cleaning and it worked great now I just need to find a custom rom any of you know of any?
Sent from my SM-G530T1 using Tapatalk
Click to expand...
Click to collapse
Unfortunately, no, I've never had any luck building a ROM. However, I'm going to give it a shot with this tab (I might as well try, lol) IF, I come up with anything, it will be posted here.
NepoRood said:
Unfortunately, no, I've never had any luck building a ROM. However, I'm going to give it a shot with this tab (I might as well try, lol) IF, I come up with anything, it will be posted here.
Click to expand...
Click to collapse
I can lend you my Jenkins server if that's what is bothering you. I'll even fix errors occasionally when I get time
MSF Jarvis said:
I can lend you my Jenkins server if that's what is bothering you. I'll even fix errors occasionally when I get time
Click to expand...
Click to collapse
Thank you for the offer my friend!
I've only tried to build for one device, well 2 actually, both RCA (MT8127), both failed miserably. Even though I got a "successful" build (ie: no errors/make completed) CM12.1 wouldn't boot. Come to find out, the zip and system.img had limited files, I can't remember which, but not enough for a complete rom
So, I decided to learn everything I could about building TWRP (thanks for your help with that too )
I'll pull all the vendor blobs from the X10 and try to put together the device tree for rom building and get back to you.
Thanks Again,
Nepo
marshmallow
you think this tablet is able to be upgraded to marshmallow?
i found a rom for 6.0.1 that has the same processor A83T
it has the same processor so do you think it would flash?
Thanks!
the firmware is
A83T_N106_N1061L6BC_20160309
NepoRood said:
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
Click to expand...
Click to collapse
The flag is actually this
Code:
RECOVERY_RAMDISK_DIRS += device/<vendor>/<codename>/ramdisk
As seen in this reverted commit
stickz42o said:
the firmware is
A83T_N106_N1061L6BC_20160309
Click to expand...
Click to collapse
I think it may work, post a link and I'll test it. Or, you can try it and let us know if it works. Do you have the current firmware already? If not, get it here
PS, you can also use Phoenix Card to boot from External SD just to test
Ahhh Please Help?
@NepoRood
All images from TabletExpress Dragon Touch X10 10'' Android 5.1.
X10-HT-PW-V1-AL-5.1-A83T_N106_N1061L2BC_20151126
X10-HT-PW-V1-AL-4.4-20151104
X10-HT-PW-V2-AL-5.1-20150115
X10-HT-PW-V2-AL-4.4-20160116
A83T_N106_N1061L6BC_20160309-ok NOT WORKING. RED/WHITE BOOT SCREEN.
I have downloaded and flashed all these images and I cannot get TWRP to work? I have installed Via Adb and Terminal, but it will not flash the recovery.
All I get is the factory recovery. I can confirm it pushed it to device, but will not work.
Can someone else verify.
Regards
Paxster
For Users: The Best and Easy App to use is the PhoenixSuit (Just Google lol)
I'm using this one:
Paxster said:
X10-HT-PW-V2-AL-5.1-20150115
Click to expand...
Click to collapse
If all you have is 3e recovery, then you're doing something wrong somewhere. Make sure the TWRP image is in the proper directory.
PC: should be in the same folder as your adb.exe file
Tablet: should be in root directory, which is just a backslash " / "
Please let me know how it goes
NepoRood said:
I think it may work, post a link and I'll test it. Or, you can try it and let us know if it works. Do you have the current firmware already? If not, get it
PS, you can also use Phoenix Card[/URL] to boot from External SD just to test
Click to expand...
Click to collapse
I am going to try it tonight. I didn't know about the phoenixcard boot to test it. I will try that method and post my results if someone doesn't beat me to it
thanks for the info about the phoenixcard
I can't post a link till 10 posts for the firmware btw :/ i'll try to message it to you.
NepoRood said:
I'm using this one:
If all you have is 3e recovery, then you're doing something wrong somewhere. Make sure the TWRP image is in the proper directory.
PC: should be in the same folder as your adb.exe file
Tablet: should be in root directory, which is just a backslash " / "
Please let me know how it goes
Click to expand...
Click to collapse
{
"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"
}
Yes Recovery is in the same Dir as ADB. It confirms being sent in the Adb Window to my booted Tablet.
Also if I use a Terminal app, it is also confirmed as being flashed, but I still get a 3e recovery? So strange.
Its driving me nuts lol..
Q:Should it work with any V5.1 Android Firm? I am using X10-HT-PW-V2-AL-5.1-20150115 from tabletexpress.
Can you confirm what version yours is working on please.
UPDATE... 5 Hours later.. I managed to flash the TWRP on Android V4.4 using Rashr. and when in recovery the screen is corrupted, unable to use? and Twrp is in Landscape mode. Shall try this method on V5.1.
Regards
Paxster
PS: @stickz42o A83T_N106_N1061L6BC_20160309 Does not work. I posted above.. Red/White Stuck Boot.
@NepoRood
Ok.. I used RASHR to install TWRP. A lot less hassle for people i recon matey. Plus it worked.....ADB refused to install lol...
It works ok on the Android V5,1, (X10-HT-PW-V2-AL-5.1-20150115) but unable to backup any partitions. The Twrp Log reports Unable to mount or find the partitions?
Plus you cannot boot the tablet again after rebooting out of twrp hehe..
Here is a Log File after Flashing a Image from PhoenixUSBPro. The Partitions are there View attachment PAXSTER.LOG So maybe TWRP does not know where they are ekk? Maybe it will help from the log file to sort his out? Im new to creating a Twrp File.
Regards
Paxster
Paxster said:
@NepoRood
Ok.. I used RASHR to install TWRP. A lot less hassle for people i recon matey. Plus it worked.....ADB refused to install lol...
It works ok on the Android V5,1, (X10-HT-PW-V2-AL-5.1-20150115) but unable to backup any partitions. The Twrp Log reports Unable to mount or find the partitions?
Plus you cannot boot the tablet again after rebooting out of twrp hehe..
Here is a Log File after Flashing a Image from PhoenixUSBPro. The Partitions are there View attachment 3747215 So maybe TWRP does not know where they are ekk? Maybe it will help from the log file to sort his out? Im new to creating a Twrp File.
Regards
Paxster
Click to expand...
Click to collapse
When building, I ran into problems of only TWRP booting, turns out it was an init.rc and recovery.fstab issue. But, I had that fixed for the final release I'm using the exact same firmware as you are, and TWRP works perfectly.
Could you attach your TWRP log?
UPDATE: Please read the updated information at the bottom of this post, on my new recommendation to use the easier method, SuperSU systemless, to patch your original boot.img. This is in my quick start guide at the end of it, also. You still need to read my info on getting setup, also.
{
"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 have started this thread as a place to post a working root solution for this tablet.
https://www.walmart.com/ip/Nextbook...-System/122137749?variantFieldId=actual_color
This is a great Android tablet for the price. It features an updated Intel Cherry Trail quad core 1.92 GHz processor, 1gb RAM, 16gb internal storage. and Android 6.0.1 Marshmallow.
UPDATE: There is a newer version of the tablet with a manufacturing sticker date of September, 2017. Despite retaining the 8A model number, it has a slower, ARM processor and Android Nougat 7.1.1. Although it is quite snappy, It shows much slower benchmarks in AnTuTu and has a much smaller battery, about half the size. Also the boxes are about 2/3 the thickness of the older, 6.0.1 tablets.
The chances of rooting it are very slim. My solution will not work for it. Fastboot mode appears to be disabled on this and one other Nougat tablet that I own. I am returning the one I tested.
UPDATE: I now have root, a custom TWRP recovery and modified boot images for the Android 6.0.1 version of this device.
I would like to thank @vampirefo for his TWRP and original boot images, for without his work, this would not be possible.
PLEASE DO NOT CONTACT HIM ABOUT THIS HE WILL NOT PROVIDE ANY SUPPORT FOR IT, THAT WILL BE PROVIDED BY ME AND OTHER GENEROUS FORUM MEMBERS.
I strongly recommend, though that you donate to him, in his signature, for all of his hard work on this, even if it is a small amount. I asked him twice about this and he never responded, so please donate to him.
His original boot.imgs are modified to remove encryption and make the kernel permissive.
I unpacked them and removed dm_verity to remove the failed verification message, on boot then repacked them.
FILES ARE UP ON ANDROID FILE HOST
https://www.androidfilehost.com/?w=files&flid=197521
Choose the version of the tablet that you own. Go to settings, about tablet and scroll to the bottom and look at the first few numbers of the build number. For example: V1.2.0.
Do not use this on the 1.0.8 version of the tablet or you will loose sound, wifi and maybe bluetooth. If you have this version of the tablet and can provide me a twrp, backed up, original boot.img, I can modify it to work with your tablet. You can temp boot twrp, to do this (see below). As of yet no one has provided one to me for the 1.0.8 tablet version.
UPDATE 10/24/2017: I now have a I now have a 1.0.8 modified boot.img up on android file host:
https://www.androidfilehost.com/?fid=962021903579487577
Here is a twrp backup of the 1.2.0 rom, with userdata deleted to start fresh. It will boot to the Android setup screen. If you have any major, unexplained problems, I recommend starting fresh with this. It works great on either tablet version: 1.1.1 and 1.2.0.
https://www.androidfilehost.com/?fid=673368273298970542
UPDATE 12/15/2017: I have uploaded a pre-rooted TWRP backup of my original V1.1.1 tablet
https://www.androidfilehost.com/?w=files&flid=235141
TO PREPARE YOUR DEVICE:
UPDATED 12/3/2017: I now have found a Version 2.1.5 of the tablet and have uploaded an unrooted, TWRP backed up version of it. It also contains the original recovery so do not check that box when flashing it in TWRP unless you intend to replace TWRP with the stock recovery
https://www.androidfilehost.com/?fid=673791459329065002
This will be long and thorough, because I see so many people who have trouble with this because they don't have their computer setup properly from the get go.
This will help you get ready to be successful in applying this.
First and foremost, unlocking your bootloader will delete all userdata on the tablet so you need a good backup of important files. If you backup to an external sd card, I strongly recommend also copying the files to an external source such as your computer. You can do that through mtp or remove the card and place it in an sd card adapter and insert it into an sd card reader. I did not do this, even though I knew better and my sd card was corrupted in the process, so I lost the original twrp backup of the virgin, untouched system partition.
Secondly, if you are on windows you need the proper drivers for adb and fastboot installed on your system. Proper drivers are the number one issue I see with windows users. For this Intel device get them here:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Here are the steps to install adb and Intel drivers, in the proper order:
The best way to to set up adb and fastboot in windows is to install it system wide. Here is an installer to do this that works well:
https://forum.xda-developers.com/showthread.php?t=2588979
Install process for 15 sec adb:
1. Run it (Require administrator privileges)
2. Press Y/Yes to install ADB and Fastboot
3. Press Y/Yes to install ADB system-wide
4. Press N/No to skip installing Drivers
5. 15 seconds passed - finished!
6. Now install the Intel drivers listed above and here, again:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Third, enable developer options by going to settings, about tablet, and tap on the build number seven times to enable it.
Then go to developer options and make sure usb debugging is enabled. watch on the tablet screen for a popup dialog the approve usb debugging. check the box to always allow for this computer and hit ok.
Now, with the proper drivers installed, adb and fastboot properly installed, You need to test that it is functioning properly. This is done with the tablet booted into Android. If you used the adb I recommended, go to my computer, C drive and open the newly created adb folder. Left click in an open area of the folder to select it. then shift right click to open a contextual menu, then select: open a command prompt here. Once the command window is open, type:
Code:
adb devices
and hit enter:
you should see the device serial number listed. I am now doing this from linux, so it may differ,slightly:
adb devices
List of devices attached
YFGV1216059870 device
Sometimes you get starting daemon on port... and you have to type it again to see the device listed. If you don't see this, then your drivers or adb/fastboot aren't properly installed.
If you see your device, then type:
Code:
adb reboot bootloader
and hit enter. your device should now reboot to bootloader mode. once in bootloader mode, type:
Code:
fastboot devices
enter and you device should once again be listed.
the next step, is to unlock your bootloader. Warning: ALL OF YOUR USERDATA WILL BE DELETED, HENCE THE BACKUP CREATED EARLIER. YOU HAVE BEEN WARNED!
It has come to my attention that this is not clear: after unlocking the bootloader, all userdata will be deleted, like doing a factory reset.
Go into developer options and select OEM unlocking. This does not unlock your bootloader, it only enables the ability to do it from a fastboot prompt.
Now jump to the Quick Start guide for updated instructions:
Older, system mode method hidden, please use the instructions in the Quick Start Guide
Now, while still booted into bootloader mode, type:
Code:
fastboot flashing unlock
and hit enter to unlock your bootloader. All data will be deleted and the tablet will be re-encrypted upon boot, without encryption option removed from the bootloader. Now type
Code:
fastboot reboot
t, to reboot the tablet and you should reboot to the android setup screen, You can set it up again if you want, but you will be deleting userdata later when you flash the modified boot.img, so keep this in mind.
So you may want to wait to unlock until I release twrp and the boot.img, so you can continue using the tablet.
UPDATE: The files are now live.
To summarize, the above steps are to prepare you for the next exciting adventure to come and to realize the full potential that a rooted device offers..................
To be continued.
THE FILES ARE NOW ON ANDROID FILE HOST. DOWNLOAD HERE:
https://www.androidfilehost.com/?w=files&flid=197521
Boot or flash TWRP Recovery and flash boot.img
These instructions are for Windows, for Linux you must type sudo before fastboot commands
Instructions: first make sure you read the instructions above to be sure you have the proper drivers and adb and fastboot are installed and tested before proceeding. Unlock your bootloader per above instructions. WARNING! DANGER WILL ROBINSON! THIS PROCEDURE WILL DELETE ALL USERDATA ON YOUR TABLET SO BE SURE YOU HAVE A BACKUP OF ANY IMPORTANT DATA.
First, unzip the files to a directory. I usually do it in C:\adb, and leave the SR2-SuperSU-v2.82-SYSTEMMODE.zip, zipped.
Now, left click in that folder in an empty spot, or where ever you unzipped it and select it. Now right click and choose open a command prompt here from the contextual menu. once the command window is open type
Code:
adb devices
, hit enter, to confirm your device is listed. Now type
Code:
adb reboot bootloader
and it should reboot to bootloader mode.
I recommend booting into twrp temp first so you can backup your original boot, recovery and system.
now:
Code:
fastboot boot Ares8A_recovery_twrp.img
enter and it should reboot to twrp temp. Don't choose read only after it boots. Once in twrp choose backup and hit select storage and choose micro sdcard. now swipe to backup. You can later install twrp permanently if you want to. To flash permanently:
From bootloader mode:
Code:
fastboot flash recovery Ares8A_recovery_twrp.img
UPDATE: See the the end of my updated quick start guide for updated info on a simpler method to patch your original boot.img with either systemless SuperSU or Magisk. I no longer recommend flashing my patched boot.imgs, but instructions are still provided here for historical reference and for the few who still want SuperSu in the unofficial, system mode.
I have hidden the older method here, but is still here for those who still want system mode SuperSU:
Now
Code:
fastboot flash boot Ares8A_111_boot.img
enter, for the 1.1.1 version, or
Code:
fastboot flash boot Ares8A_120_boot.img
enter, for the 1.2.0 version, to flash the appropriate boot.img
For the newer 2.1.5 version of the table:
Code:
fastboot flash boot unsigned-new.img
hit the enter key, to flash.
Next, again in bootloader mode issue:
Code:
fastboot format userdata
enter, and wait for a successful message in the command window and on the tablet. it will take a little while.
Next
Code:
fastboot format cache
enter, wait. Now
Code:
fastboot reboot
hit enter, and the tablet should reboot to the android setup screen where you can set it up. It will take some extra time to reboot, so be patient. You may see the boot animation for awhile. This will be booted unencrypted now without root. I recommend doing a backup again in twrp before rooting.
There has been some misunderstanding about the above. Your data is encrypted and will not be accessible it twrp, hence, the backup before you do anything with this tablet.
You must wipe the userdata, so a new, clean data partition can be created that is unencrypted. A factory reset is not enough. You will have problems if you don't format userdata in the above step to created a decrypted data partition.
Flashing SuperSu for root
For the v1.1.1 and v1.2.0 tablets:
Make sure you have the SR1-SuperSU-v2.82-SYSTEMMODE.zip on your ext sd card.
For the newer 2.1.5 you need a systemless version of SuperSU:
SuperSU-v2.82-201705271822.zip Get it at:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip Copy it to your external SD card.
When flashed, this systemless version will also patch your boot image for sytemless mode.
Furthermore, to install SR1-SuperSU-v2.82-SYSTEMMODE.zip, or SuperSU-v2.82-201705271822.zip, either boot twrp temp again, from bootloader mode issue:
Code:
fastboot boot Ares8A_recovery_twrp.img
, or if you already have it installed permanently and you are booted normally, issue
Code:
adb reboot recovery
enter to boot to it.
Next hit the install button in twrp and choose SR1-SuperSU-v2.82-SYSTEMMODE.zip or SuperSU-v2.82-201705271822.zip and swipe to confirm flash. after it is complete, go back to the main menu and choose reboot system. I choose not to install the twrp app before reboot.
Once rebooted, open the supersu app, making sure the following are selected in settings enable superuser, default access prompt or grant, enable su during boot, trust system user and enable pro, then go back and enable full content in logging. Next download a root check app to confirm root.
congratulations you should now be rooted! Now download a desired app that requires root and test to confirm you have no problems with root.
If you want an app that makes it easy to reboot in the various modes, I recommend Simple Reboot by Francisco Franco. It works great with this device and android version.
I was using Easy Reboot [ROOT] by Simone Luconi with my older, ares 8 with 5.1.1 and it had worked well.
Apparently it is not compatible with this device or rom. when I rebooted to recovery with it, I was not able to mount my external sd card and the card was corrupted on reboot. That is why I don't have a virgin, unrooted, copy of my system image now.
Good luck!
Here is a quick start guide for the already initiated:
https://forum.xda-developers.com/showpost.php?p=72970060&postcount=82
Here is a link to my post for some apps I personally find useful:
https://forum.xda-developers.com/showpost.php?p=72995672&postcount=112
Please report successes and problems on this thread, not to @vampirefo.
Thanks
@vampirefo has a solution, but has not released it. I'm not sure if it needs more work or testing before release? He has been quiet in this regard. It is my hope that he will reply with more relevant information about this.
I and maybe others, would be willing to give a donation, if that would help.
Thanks
Bootloader unlocking
WARNING! UNLOCKING THE BOOTLOADER WILL DELETE ALL OF YOUR DATA!
DON'T DO THE UNLOCKING UNTIL WE CAN REMOVE ENCRYPTION AND HAVE TWRP FOR BACKUP. YOU HAVE BEEN WARNED!
You can enable the ability for the bootloader to be unlocked with a setting in the developer options. Like I stated, it enables the ability to unlock it, but does not unlock it. On must use the command in adb, through a computer. make sure usb debugging is enabled in the developer options. In a command prompt issue adb devices to make sure your device is showing up. There will be a prompt on your tablet to allow this. Confirm this.
Now with the tablet off, boot into fastboot by hold the volume key down button and the power button at the same time. Also, you can type: adb reboot bootloader then hit enter to get into bootloader or fastboot mode.
Once in fastboot mode, open a command prompt in windows and type fastboot devices to confirm your device is still showing up. If my memory serves me correctly there will also be a security confirmation on the tablet, to approve.
To unlock the bootloader type: fastboot flashing unlock. All data will be deleted and (I believe,) the tablet will be re-encrypted upon boot, without encryption option removed from the bootloader.
I HAVE NOT TESTED THIS, AS I DON'T WANT TO DELETE DATA, UNTIL WE HAVE TWRP TO BACKUP AND ROOT.
6/7/2017 UPDATE: I HAVE UPDATED THE UNLOCK COMMAND. I HAVE UNLOCKED MY BOOTLOADER. AS I THOUGHT, ALL USER DATA IS DELETED (FACTORY RESET). I USED THE FIRST:
"fastboot flashing unlock" Unlocks the device. Allows flashing any
partition except bootloader-related
partitions
"flashing unlock_critical" Enables flashing bootloader-relate partitions.
all fastboot commands are listed by just typing fastboot, while booted into bootloader mode. My tablet is still running great with my bootloader unlocked. One more tiny step toward gaining root, however, there is still a long way to go.
Please post any additional info if I have something wrong, or left out any important steps.
Thanks
Geenify: How to grant permissions required by some features on non-root device?
I am currently using Greenify on my non-rooted device and it is working very well.
By using adb, one can grant it additional permission so it performs almost as well on an unrooted device. Here is a link for this:
https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
I copied and pasted each command, one at a time, in the command prompt then hit enter, to enable each one.
In Greenify settings, I also have aggressive doze enabled, Automated hibernation enabled, Wakeup Tracker enabled and Quick action Notification enabled.
How to boot into stock recovery mode
To boot to the stock recovery through adb:
adb reboot recovery
You will see "no command" on the tablet.
Hold the power button and volume up for about 4sec then release the volume up, where you should go to the stock recovery screen.
You can also get to it without a computer. With the tablet shut down, hold the volume down power button until it boots to bootloader or fastboot mode.
Use the volume up or down button to toggle through the options: normal boot, restart bootloader, recovery mode, reboot, power off and ftm mode. Choose recovery and use the volume up and power button as before.
In addition you can get to the efi bootmanager by holding the volume up, power button when the device has been shutdown first.
adb security confirmation
Unlike my Nextbook Ares 8 with 5.1.1, with this newer tablet which has 6.0.1, I have to reaffirm the security prompt on the device each time, despite checking the box: "Always allow from this computer".
Maybe this is because of the tightened security in Android Marshmallow? I'm not sure.
If there is a way around this each time, please let me know
Thanks
UPDATE: After I unlocked the bootloader and the tablet was factory reset, I no longer have to re-approve each time after checking the box: "Always allow from this computer"
Would love to see some break throughs with this device aswell. Cheers to any one working in it.
Is this relevant? It would seem they are the same device. twitter.com/srsroot/status/846663673645010944?lang=en
Giftlift said:
Is this relevant? It would seem they are the same device. twitter.com/srsroot/status/846663673645010944?lang=en
Click to expand...
Click to collapse
Don't try any of these one click root solutions. none work to my knowledge on android 6.01, (at least on this device) , and may install malware or pups on your host computer.
martyfender said:
Don't try any of these one click root solutions. none work to my knowledge on android 6.01, (at least on this device) , and may install malware or pups on your host computer.
Click to expand...
Click to collapse
:good::good:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
vampirefo said:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
@vampirefo Thanks for taking the time to post this.
To familiarize myself with Linux, I created a persistent linux Mint 17.2 Mate 64 bit on a 32 gb usb thumb drive before I decide to commit my windows machine for a linux install.
I installed oracle jdk and android studio thinking this was the build environment needed to do this. the twrp compile forum makes no mention of what to do in this case. I must have been wrong? I don't think I need this to download and build android kernel sources and twrp source?
I'm now very doubtful about even tempting to do this. Yes, a lot of work just learning the basics of linux, let alone following the steps you give in your basic outline. I don't want to give up so easily, but the learning curve is steep.
So one just uses terminal commands to setup and download aosp and twrp git repositories and to make them? Also, is there any way to backup my device system, boot and recovery without root in linux or windows? I have used the adb pull command to backup the system directories to my windows computer, but don't know how to do it for other partitions, if possible.
I found this kernel building guide for arm and mediatek devices. would this be similar for Intel using the right repositories?
https://forum.xda-developers.com/android/software/guide-easy-kernel-building-tutorial-t3581057
Thanks
Click to expand...
Click to collapse
martyfender said:
vampirefo said:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
@vampirefo Thanks for taking the time to post this.
To familiarize myself with Linux, I created a persistent linux Mint 17.2 Mate 64 bit on a 32 gb usb thumb drive before I decide to commit my windows machine for a linux install.
I installed oracle jdk and android studio thinking this was the build environment needed to do this. the twrp compile forum makes no mention of what to do in this case. I must have been wrong? I don't think I need this to download and build android kernel sources and twrp source?
I'm now very doubtful about even tempting to do this. Yes, a lot of work just learning the basics of linux, let alone following the steps you give in your basic outline. I don't want to give up so easily, but the learning curve is steep.
So one just uses terminal commands to setup and download aosp and twrp git repositories and to make them? Also, is there any way to backup my device system, boot and recovery without root in linux or windows? I have used the adb pull command to backup the system directories to my windows computer, but don't know how to do it for other partitions, if possible.
Thanks
Click to expand...
Click to collapse
All work is done in terminal, root is required to make backups.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
vampirefo said:
martyfender said:
All work is done in terminal, root is required to make backups.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
So I could uninstall android studio. Should I also revert back to openjdk? I see it mentioned in google docs on setting up a build environment.
UPDATE: I think I have now setup properly. Reverted to openjdk 8
I downloaded this: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8
I found this: https://github.com/CM-CHT/android_device_intel_cherrytrail-common Would this be useful?
Thanks
Click to expand...
Click to collapse
martyfender said:
vampirefo said:
So I could uninstall android studio. Should I also revert back to openjdk? I see it mentioned in google docs on setting up a build environment.
UPDATE: I think I have now setup properly. Reverted to openjdk 8
I downloaded this: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8
I found this: https://github.com/CM-CHT/android_device_intel_cherrytrail-common Would this be useful?
Thanks
Click to expand...
Click to collapse
No ideal, try it and see.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
What would it take to interest @vampirefo in rooting this tablet and providing a nice clean ROM for the Ares 8A???
cjhudson101 said:
What would it take to interest @vampirefo in rooting this tablet and providing a nice clean ROM for the Ares 8A???
Click to expand...
Click to collapse
For me to root and provide TWRP recovery, I would need the tablet.
Sent from my Life Max using Tapatalk
vampirefo said:
For me to root and provide TWRP recovery, I would need the tablet.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
My bad, I guess I misunderstood one of your posts where you said you successfully rooted the tablet, but were withholding the method...
What if I sent you one?
cjhudson101 said:
My bad, I guess I misunderstood one of your posts where you said you successfully rooted the tablet, but were withholding the method...
What if I sent you one?
Click to expand...
Click to collapse
You didn't misread, I rooted my son's, he doesn't live near me, he is in college. He is using my laptop that I used, so all my source files are with him.
I need tablet to start over, I already know what to do but without tablet, I can't do it.
Sent from my Life Max using Tapatalk
Check your zip in the link, lets get vamp an 8a!
I just got one of these for $35, but now the closest walmart with it in stock is an hour away. Ill totaly send you one if I drive that way for any reason. Check your zip on brickseek ..... anyone?
slickdeals.net/f/10189248-nextbook-ares-8a-16gb-tablet-android-6-ymmv-35-bm?src=SiteSearchV2_SearchBarV2Algo1
it came with 6.0.1 on it
IM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE.
Hello there. I own bp2 since last year. So in order to avoid lags and poor battery performance im gonna write this guide.
So thanks to this i achieved a new phone, without battery drain, a very good battery and cpu temp, and almost root access.
These modifications are made on 3.0.14 ROM, I dont know if this works if your blackphone runs another version.
You can install 3.0.14 here
1. First of all you need to flash TWRP. Download and instructions here
2. Once flashed do not reboot system, type
HTML:
fastboot reboot
and press vol+ to enter twrp.
3. Now it will asks you to allow modifications, NEVER do that, always press "Keep Read Only" because you will get bootloop if you mount system as rw.
More info about that here
4. Now flash magisk, then reboot and install magisk apk. Download from here
NOTE: I dont know why but you need a microsd card in order to flash files, because twrp cant mount /data
NOTE 2: At this point you dont have su BUT you can install magisk modules (yes, xposed too).
Now lets give BP2 Pixel's style.
5. Download this script to remove all Google stuff, yes, just do it. I recommend the EXTREME one.
6. Flash it trough recovery and wipe chache/dalvik. do not reboot yet.
7. Now lets flash Gapps again, updated and modular. Just go to this page and select your desired package. I recommend AROMA not only because you install what you need, but you can remove stock apps (calculator, fmradio, stock email, etc). http://opengapps.org/
8. Now, yes, you can boot system.
9. I also made this script to remove all SilentCircle stuff. Just flash it.
NOTE 3: I wrote this script before removing gapps and that things i explained, so let me know wichs apps still get installed and i will add to the script. Also let me know what apps you want to remove.
Screenshots:
Updating...
Nice work.
Does this stop the phone checking update servers?
loaded2107 said:
Nice work.
Does this stop the phone checking update servers?
Click to expand...
Click to collapse
Yeah It removes all blackphone apps, but you can modify the script
great work although I have encountered a problem in the pixel laucher that gives me error
script not ok
hello. when i flash your script my phone goes on bootloop
i flash it trought TWRP cause my phone cant see any microsd card
i thing the sd slot of my phone have problem
but my phone goes bootloop after flash BP2_Bloatware
can you sent me any sugestion? Thanks a lot
But how is the phone?
About to spring for a BP2 but ... just out of curiosity:
The reason to own this phone is for the sandboxing and some of the applications that monitor and block application permissions. If you're removing those just to have a fast android phone ... not sure why you bought this one. The camera isn't even any good.
I just want to run basically unmodified. 2 years and many updates have passed since @polartux talked about battery draining Apps and just curious how the latest OS is? Also if I want to install applications I have developed myself (or get a couple off of the google app store) can I assume that's possible? Preciously LITTLE information about those things online. And I have emailed sales multiple times never got a single response. Kind of scary lol.
So :
-can I do ADK dev on this thing?
-has the stock OS gotten better?
-Can I install pandora (or whatever)?
Cheers!
carlosinf said:
great work although I have encountered a problem in the pixel laucher that gives me error
Click to expand...
Click to collapse
Hi, I actually move to another phone, I had Lawnchair installed on bp2
Enviado desde mi PRO 5 mediante Tapatalk
notelinos said:
hello. when i flash your script my phone goes on bootloop
i flash it trought TWRP cause my phone cant see any microsd card
i thing the sd slot of my phone have problem
but my phone goes bootloop after flash BP2_Bloatware
can you sent me any sugestion? Thanks a lot
Click to expand...
Click to collapse
Hello, that's a big problem. You must flash files from SD card instead of internal, if you flash from internal storage youll get boot loop and I don't know how to solve that
Enviado desde mi PRO 5 mediante Tapatalk
storkinsj said:
About to spring for a BP2 but ... just out of curiosity:
The reason to own this phone is for the sandboxing and some of the applications that monitor and block application permissions. If you're removing those just to have a fast android phone ... not sure why you bought this one. The camera isn't even any good.
I just want to run basically unmodified. 2 years and many updates have passed since @polartux talked about battery draining Apps and just curious how the latest OS is? Also if I want to install applications I have developed myself (or get a couple off of the google app store) can I assume that's possible? Preciously LITTLE information about those things online. And I have emailed sales multiple times never got a single response. Kind of scary lol.
So :
-can I do ADK dev on this thing?
-has the stock OS gotten better?
-Can I install pandora (or whatever)?
Cheers!
Click to expand...
Click to collapse
Sorry mate but I don't know, I'm not a dev. I only posted this to help.
Enviado desde mi PRO 5 mediante Tapatalk
chape199 said:
IM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE.
Hello there. I own bp2 since last year. So in order to avoid lags and poor battery performance im gonna write this guide.
So thanks to this i achieved a new phone, without battery drain, a very good battery and cpu temp, and almost root access.
These modifications are made on 3.0.14 ROM, I dont know if this works if your blackphone runs another version.
You can install 3.0.14 here
1. First of all you need to flash TWRP. Download and instructions here
2. Once flashed do not reboot system, type
HTML:
fastboot reboot
and press vol+ to enter twrp.
3. Now it will asks you to allow modifications, NEVER do that, always press "Keep Read Only" because you will get bootloop if you mount system as rw.
More info about that here
4. Now flash magisk, then reboot and install magisk apk. Download from here
NOTE: I dont know why but you need a microsd card in order to flash files, because twrp cant mount /data
NOTE 2: At this point you dont have su BUT you can install magisk modules (yes, xposed too).
Now lets give BP2 Pixel's style.
5. Download this script to remove all Google stuff, yes, just do it. I recommend the EXTREME one.
6. Flash it trough recovery and wipe chache/dalvik. do not reboot yet.
7. Now lets flash Gapps again, updated and modular. Just go to this page and select your desired package. I recommend AROMA not only because you install what you need, but you can remove stock apps (calculator, fmradio, stock email, etc). http://opengapps.org/
8. Now, yes, you can boot system.
9. I also made this script to remove all SilentCircle stuff. Just flash it.
NOTE 3: I wrote this script before removing gapps and that things i explained, so let me know wichs apps still get installed and i will add to the script. Also let me know what apps you want to remove.
Screenshots:
Updating...
Click to expand...
Click to collapse
I am having a problem, every time I try and install Magisk thro' TWRP I get "failed to verify whole file signature" and "signature verification failed", I can install BP2 9, 10, 11 and 14 zips without any problems. Bloatware zip also throws up the same messages. may need a step by step instruction. As before TWRP is installed and BP2 11 doe's not brick the phone, not sure what 14 will do, thought it would brick the phone. Many thanks
dgc1 said:
I am having a problem, every time I try and install Magisk thro' TWRP I get "failed to verify whole file signature" and "signature verification failed", I can install BP2 9, 10, 11 and 14 zips without any problems. Bloatware zip also throws up the same messages. may need a step by step instruction. As before TWRP is installed and BP2 11 doe's not brick the phone, not sure what 14 will do, thought it would brick the phone. Many thanks
Click to expand...
Click to collapse
Hi, i dont use the bp2 anymore since past year but i remember that you have to flash the zips from external sdcard, never use twrp to flash files trough internal. Maybe thats the problem. Hope ive helped you.
Hi guys when I tried to flash the recovery it told me:
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.556s
[[email protected] Desktop]#
What should I do?
Many thanks
KF
kenfalco_14 said:
Hi guys when I tried to flash the recovery it told me:
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.556s
[[email protected] Desktop]#
What should I do?
Many thanks
KF
Click to expand...
Click to collapse
To unlock the bootloader I suppose, but how?
kenfalco_14 said:
To unlock the bootloader I suppose, but how?
Click to expand...
Click to collapse
settings
developer options
oem unlocking - on
restart phone
hold volume down (bootloader mode)
connect usb and do command from PC:
fastboot oem unlock-go
## Your DATA will be DELETED ### make backup
I personally have another problem. I can't see TWRP.
Just black screen.
So i'm trying to fight with it using adb shell...
If I have a root and run all scripts mentioned here, I will explain it here later...
BP2 boot to TWRP
Hi All,
I have read several thread and web pages on how to root, install twrp, rom etc and I can not get it to work.
I was able to update the BP2 to 3.0.14 from .9
All I want to do is change to a custom rom.
I did the following:
-enable USB debugging
-enable oem unlock
-installed platform tools on PC
-adb reboot bootloader
-fastboot devices - phone is there
-fastboot oem unlock-go
-reboot - phone appears to be unlocked
-fastboot flash recovery twrp.img
>Sending 'boot.img' (17392 KB) OKAY [ 0.545s]
>Booting OKAY [ 0.040s]
>Finished. Total time: 0.596s
-fastboot reboot
reboots to blank screen
Do over, and when fastboot reboot, I hold down Volume+
still get blank screen
Any ideas?
David_h99 said:
Hi All,
still get blank screen
Any ideas?
Click to expand...
Click to collapse
It's because the screen not supported by TWRP.
When you run TWRP you should see all your files in windows by USB cable, right? Hope you put SD card in it.
So you are the same boat like me.
ROOT still doesn't work for me btw, but i have a few commands:
0) run twrp (probably it disappeared for you and stock recovery back, so i'm running it like that in download mode:
fastboot.exe boot twrp-3.4.0-0-bp2.img
1) open shell: adb shell
in the shell:
for install magisk:
twrp install /external_sd/Magisk-v21.1.zip
you have to have this file on sd card okay? =)
To rill bloatware:
twrp install /external_sd/BP2_Bloatware.zip
To kill google stuff will be not so easy because it will ask you questions on the screen.
So i've repacked it to force version without questions (will attach my version here)
twrp install /external_sd/G-Killer_v3_forced.zip
Then you need to install open gapps
twrp install /external_sd/open_gapps-arm-6.0-pico-20201113.zip
If you want to decrypt DATA partition then:
cat /etc/fstab
look for numbers for your DATA partition
then do format:
make_ext4fs /dev/block/mmcblk0p33
your end will be different possibly.
Then disable dm verify:
twrp install /external_sd/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
take it here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
and final reboot:
reboot
Anyway ROOT just simply doesn't work. I was fighting with it a lot of hours
tried super su also without any luck.
Hope it helps you somehow.
speed_boy said:
It's because the screen not supported by TWRP.
When you run TWRP you should see all your files in windows by USB cable, right? Hope you put SD card in it.
So you are the same boat like me.
ROOT still doesn't work for me btw, but i have a few commands:
0) run twrp (probably it disappeared for you and stock recovery back, so i'm running it like that in download mode:
fastboot.exe boot twrp-3.4.0-0-bp2.img
1) open shell: adb shell
in the shell:
for install magisk:
twrp install /external_sd/Magisk-v21.1.zip
you have to have this file on sd card okay? =)
To rill bloatware:
twrp install /external_sd/BP2_Bloatware.zip
To kill google stuff will be not so easy because it will ask you questions on the screen.
So i've repacked it to force version without questions (will attach my version here)
twrp install /external_sd/G-Killer_v3_forced.zip
Then you need to install open gapps
twrp install /external_sd/open_gapps-arm-6.0-pico-20201113.zip
If you want to decrypt DATA partition then:
cat /etc/fstab
look for numbers for your DATA partition
then do format:
make_ext4fs /dev/block/mmcblk0p33
your end will be different possibly.
Then disable dm verify:
twrp install /external_sd/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
take it here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
and final reboot:
reboot
Anyway ROOT just simply doesn't work. I was fighting with it a lot of hours
tried super su also without any luck.
Hope it helps you somehow.
Click to expand...
Click to collapse
Thanks for response.
When I do fastboot devices, it shows thone
Once i do the fastboot.exe boot twrp-3.4.0-0-bp2.img command, it reboots and blank screen.
When I do adb shell, i get "adb.exe: no devices/emulators found"
I do adb devices, and it shows no devices attached
I do have installed "Google Nexus ADB interface" device installed
David_h99 said:
I do have installed "Google Nexus ADB interface" device installed
Click to expand...
Click to collapse
In win10 I have "adb interface" with ID: VID_18D1&PID_4EE2
In win7 it is "Android composite adb interface"
in both OSes works well.
So try to change driver for example.
speed_boy said:
In win10 I have "adb interface" with ID: VID_18D1&PID_4EE2
In win7 it is "Android composite adb interface"
in both OSes works well.
So try to change driver for example.
Click to expand...
Click to collapse
I am not able to find where to change this to "adb interface"
do you know how I can change this?
I can't speak for the rest of you, but I've been waiting for LineageOS to support this phone since I bought it almost a year ago. I saw a post on /r/LineageOS indicating that mata was finally being supported and sure enough here it is:
https://download.lineageos.org/mata
Since there doesn't appear to be a thread on the topic yet, I figured I'd go ahead and create one so all interested parties can discuss it. I probably won't get around to flashing it myself until this weekend and I'd love to hear how it's working for other people prior to that (and if not, hell I'll flash it and roll the dice).
jaylittle said:
I can't speak for the rest of you, but I've been waiting for LineageOS to support this phone since I bought it almost a year ago. I saw a post on /r/LineageOS indicating that mata was finally being supported and sure enough here it is:
https://download.lineageos.org/mata
Since there doesn't appear to be a thread on the topic yet, I figured I'd go ahead and create one so all interested parties can discuss it. I probably won't get around to flashing it myself until this weekend and I'd love to hear how it's working for other people prior to that (and if not, hell I'll flash it and roll the dice).
Click to expand...
Click to collapse
I did it and so far looks good
jowandrys said:
I did it and so far looks good
Click to expand...
Click to collapse
Can you give us a link to the procedure that you followed in order to flash it?
Thanks !
Djalil87 said:
Can you give us a link to the procedure that you followed in order to flash it?
Thanks !
Click to expand...
Click to collapse
https://wiki.lineageos.org/devices/mata
jowandrys said:
I did it and so far looks good
Click to expand...
Click to collapse
Do you play any games? I'm having issues with touch in games only so far
joha386 said:
https://wiki.lineageos.org/devices/mata
Click to expand...
Click to collapse
I think the installation guide is wrong. To unlock the bootloader, the command "fastboot oem unlock" will not work.
MattCB72 said:
I think the installation guide is wrong. To unlock the bootloader, the command "fastboot oem unlock" will not work.
Click to expand...
Click to collapse
Yes it didn't for me. I used instead:
> fastboot flashing unlock
Not able to install Gapps. Always get Error 70...
dazeone said:
Do you play any games? I'm having issues with touch in games only so far
Click to expand...
Click to collapse
I've specifically noticed touch issues in Pokémon GO. Unable to reproduce the problem reliably, but it seems that after several hours of uptime single-finger touches no longer register (again, only in PoGO -- other apps work flawlessly). Strangely, using 1 finger as an anchor anywhere on the screen, then tapping the intended button with a 2nd finger will register correctly.
Fortunately, I've been able to resolve the intermittent issue with a simple reboot.
Edit: Looks like touch issues in games may have been present back in 15.1.
Steps that I followed to get it up and running
Djalil87 said:
Can you give us a link to the procedure that you followed in order to flash it?
Thanks !
Click to expand...
Click to collapse
Clean install steps, WILL destroy ALL data, make backups!! before performing any of this and as always YMMV
0: (optional) Update firmwares/radios etc. to latest
0.1: Download latest stock package. [URL: https://www.essential.com/developer/current-builds]
0.2: Unzip to a location and modify the install script flashall.sh(*nix)/flashall.bat(win) to remove the reboot line (last line)
0.3: Reboot to bootloader: Keep pressing vol down + power buttons OR adb reboot bootloader via a privileged OS terminal.
0.3: Run the install script with admin privs: sudo ./flashall.sh(*nix) OR (run as admin) flashall.bat(win)
0.4: Reboot bootloader: Keep pressing vol down, select using power button hen you see the option OR fastboot reboot-bootloader
1: Erase userdata: sudo fastboot -w
1.1: (very optional) check slot to make sure we are in slot a (sudo fastboot getvar current-slot), if not then boot to slot a.
2: Install twrp to boot (fastboot flash boot TWRP-SEP.img or latest twrp image) (Note: I use that specific twrp image because the touchscreen works for me YMMV)
3: Boot to twrp using vol up/down buttons and power button to make the selection.
Now we are within TWRP and hopefully touch works, if the touch doesn't work, try to use a different TWRP build or try to use adb shell commands, indicated below (where applicable)
4: Here we wipe and format everything (if no touch then adb shell twrp wipe <system/data>)
4.1: Format data (Any adb shell commands to achieve a similar result?, "adb shell twrp wipe data" maybe)
4.1.1: (optional) format data to f2fs
4.2: Wipe system (adb shell twrp wipe system)
5: We start copying and initial installing ROM files to device, (adb push <file> /sdcard/)
5.1: Copy and install file: Lineageos rom [URL: https://download.lineageos.org/mata]
5.2: Copy and install file: TWRP installer [URL: https://dl.twrp.me/mata/]
6: Reboot to recovery, this should boot back up to twrp (any adb shell command to achieve this?) (Note: This step is needed otherwise gapps installation *may* fail later)
7: Now we copy and install rest of the files to device in order. (adb push <file> /sdcard/) OR (if sideloading: adb sideload <file>)
7.1: Here you get to choose if you don't want google integration (Lucky You!)
7.1.1: (optional) Copy and install file: <nanodroid> if you are interested in going the microg route. [URL: https://nanolx.org/nanolx/nanodroid]
7.1.2: (optional) Copy and install file: <OpenGapps pico> (or whatever you want man). [URL: https://opengapps.org/]
7.2: (optional, needed if disabling forced encryption) Copy and install file: DM verity_forceencrypt zip file (download zip from github and remove .git files and recompress to .zip, making sure the filename is (without quotes): "Disable_Dm-Verity_ForceEncrypt_master" [URL: https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt/archive/master.zip]
7.3: (optional, needed if root is desired or if disabling forced encryption in 7.2) Copy and install file: <Magisk stable> [URL: https://forum.xda-developers.com/apps/magisk]
7.4: (optional, untested, may break OTA) Perform step 5.2 again if you want to maintain TWRP as recovery.
8: Reboot to system.
8.1: (optional) If device is consistently bootlooping (Note: 2-4 interim reboots are normal), then GOTO step 1.
8.2: (optional) If a system app is force closing, try to erase its data and cache first, otherwise GOTO step 1.
profit?? (and/or optionally cry over wasted time in this possibly pointless exercise)
psychic_quark said:
6: Reboot to recovery, this should boot back up to twrp (any adb shell command to achieve this?) (Note: This step is needed otherwise gapps installation *may* fail later)
Click to expand...
Click to collapse
Thanks for this excellent step by step guide. I didn't get touch to work on my TWRP (latest version from TWRP site) so I did use adb shell commands in TWRP but unfortunately I didn't manage to install GApps. I think I'm missing the step 6. you are describing. I have LOS running with root but no GApps.
Any guess on how I can manage to reboot to recovery while I'm in TWRP sideload mode to get back to TWRP again?
Thanks !
Another way to use twrp without touch is by using a mouse. If you have one with a type C connector, plug it in and you can flash LOS and the twrp installer. Then boot back to recovery and flash GAPPS. I had to do it this way but I had an adapter for the type C plug so I could use a regular mouse. The adapter came with my Pixel 2XL.
I kept getting error 70, so I used MindTheGapps, which installed fine. Don't know if there's any adverse effects of doing that though, by my phone seems to be working fine.
Wish there was some way to configure fullscreen on the notch though.
theycallmetony said:
I've specifically noticed touch issues in Pokémon GO. Unable to reproduce the problem reliably, but it seems that after several hours of uptime single-finger touches no longer register (again, only in PoGO -- other apps work flawlessly). Strangely, using 1 finger as an anchor anywhere on the screen, then tapping the intended button with a 2nd finger will register correctly.
Fortunately, I've been able to resolve the intermittent issue with a simple reboot.
Edit: Looks like touch issues in games may have been present back in 15.1.
Click to expand...
Click to collapse
is there a better solution? It no longer registers my touches after several minutes, so I need to reboot my phone to play games every time…Because of the bad optimization of the kernel, before my phone runs smoothly there is some annoying minutes…
And when I try to flash Neutrino Kernel and reboot, all my PH-1 does is stuck in "phone is starting" with a dialog reminding me that there is an internal error with my system, and it never truly enters the launcher… Has anyone tried yet?
Rachel030219 said:
is there a better solution? It no longer registers my touches after several minutes, so I need to reboot my phone to play games every time…
Click to expand...
Click to collapse
Been running the 20190614 nightly for ~13 hours straight without the need to reboot. Pokémon GO is still running smooth!
Edit: Touch problems started again a couple hours after posting this. Fortunately, a reboot still resolves the issue.
Anyone try LineageOS for microg? Keep trying to flash the rom but no dice, just get sent back to twrp.
Hero2457 said:
Anyone try LineageOS for microg? Keep trying to flash the rom but no dice, just get sent back to twrp.
Click to expand...
Click to collapse
Same here, unfortunately. The first time (this was a clean flash after a full wipe), it showed the boot animation for an hour before going back to twrp. I tried flashing it again after another wipe, and this time it stayed in the boot animation overnight, for at least ten hours. I'm not sure where to send a bug report or what info to attach to the bug report.
The regular (non-microG) LOS on the other hand, works fine.
Djalil87 said:
Thanks for this excellent step by step guide. I didn't get touch to work on my TWRP (latest version from TWRP site) so I did use adb shell commands in TWRP but unfortunately I didn't manage to install GApps. I think I'm missing the step 6. you are describing. I have LOS running with root but no GApps.
Any guess on how I can manage to reboot to recovery while I'm in TWRP sideload mode to get back to TWRP again?
Thanks !
Click to expand...
Click to collapse
I was on Q beta 4 and these steps worked for me:
Here's what worked for me:
fastboot flash boot <twrp image from twrp.me>
<boot into recovery>
Touch isn't working, so instead I do: adb shell twrp sideload
adb sideload <lastest lineage rom>
(again) adb shell twrp sideload
adb sideload <twrp installer zip>
adb reboot recovery
Touch worked in twrp!
Proceeded with installing opengapps/nanodroid and all that jazz.
TBH you don't need touch to achieve most (if not all) functionality of twrp.
To reboot back to recover from within twrp (assuming you have already flashed twrp installer after flashing rom), just do: adb reboot recovery
psychic_quark said:
Clean install steps, WILL destroy ALL data, make backups!! before performing any of this and as always YMMV
0: (optional) Update firmwares/radios etc. to latest
0.1: Download latest stock package. [URL: https://www.essential.com/developer/current-builds]
0.2: Unzip to a location and modify the install script flashall.sh(*nix)/flashall.bat(win) to remove the reboot line (last line)
0.3: Reboot to bootloader: Keep pressing vol down + power buttons OR adb reboot bootloader via a privileged OS terminal.
0.3: Run the install script with admin privs: sudo ./flashall.sh(*nix) OR (run as admin) flashall.bat(win)
0.4: Reboot bootloader: Keep pressing vol down, select using power button hen you see the option OR fastboot reboot-bootloader
1: Erase userdata: sudo fastboot -w
1.1: (very optional) check slot to make sure we are in slot a (sudo fastboot getvar current-slot), if not then boot to slot a.
2: Install twrp to boot (fastboot flash boot TWRP-SEP.img or latest twrp image) (Note: I use that specific twrp image because the touchscreen works for me YMMV)
3: Boot to twrp using vol up/down buttons and power button to make the selection.
Now we are within TWRP and hopefully touch works, if the touch doesn't work, try to use a different TWRP build or try to use adb shell commands, indicated below (where applicable)
4: Here we wipe and format everything (if no touch then adb shell twrp wipe <system/data>)
4.1: Format data (Any adb shell commands to achieve a similar result?, "adb shell twrp wipe data" maybe)
4.1.1: (optional) format data to f2fs
4.2: Wipe system (adb shell twrp wipe system)
5: We start copying and initial installing ROM files to device, (adb push <file> /sdcard/)
5.1: Copy and install file: Lineageos rom [URL: https://download.lineageos.org/mata]
5.2: Copy and install file: TWRP installer [URL: https://dl.twrp.me/mata/]
6: Reboot to recovery, this should boot back up to twrp (any adb shell command to achieve this?) (Note: This step is needed otherwise gapps installation *may* fail later)
7: Now we copy and install rest of the files to device in order. (adb push <file> /sdcard/) OR (if sideloading: adb sideload <file>)
7.1: Here you get to choose if you don't want google integration (Lucky You!)
7.1.1: (optional) Copy and install file: <nanodroid> if you are interested in going the microg route. [URL: https://nanolx.org/nanolx/nanodroid]
7.1.2: (optional) Copy and install file: <OpenGapps pico> (or whatever you want man). [URL: https://opengapps.org/]
7.2: (optional, needed if disabling forced encryption) Copy and install file: DM verity_forceencrypt zip file (download zip from github and remove .git files and recompress to .zip, making sure the filename is (without quotes): "Disable_Dm-Verity_ForceEncrypt_master" [URL: https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt/archive/master.zip]
7.3: (optional, needed if root is desired or if disabling forced encryption in 7.2) Copy and install file: <Magisk stable> [URL: https://forum.xda-developers.com/apps/magisk]
7.4: (optional, untested, may break OTA) Perform step 5.2 again if you want to maintain TWRP as recovery.
8: Reboot to system.
8.1: (optional) If device is consistently bootlooping (Note: 2-4 interim reboots are normal), then GOTO step 1.
8.2: (optional) If a system app is force closing, try to erase its data and cache first, otherwise GOTO step 1.
profit?? (and/or optionally cry over wasted time in this possibly pointless exercise)
Click to expand...
Click to collapse
Brillant post @psychic_quark that was the only guide which worked for me, coming from Q beta 3. Thanks.
Step 1.1 was needed for me to flash boot_a or _b in step 2 depending on the result in 1.1.
@jaylittle thanks also for telling us. I also waited for a year to get LOS on my PH-1. I got it from the amazon deal and was ran invisiblisk ROM of Dec.
I ran the June 15 ROM with opengapps pico and magisk in recent version and yestersay I updated via OTA to June 18 ROM without loosing root. Thats very cool. With other ROMs I had to install magisk after update again.
Did anyone tried to install twrp permanently?
And my second question is about removing the red warn during booting which has to be ack-ed. I found this https://mata.readthedocs.io/en/latest/ under topic "Removing the Red Verity Warning" did anyone tried this and will this remove root?
Thanks for your help.