{
"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"
}
It took me sometime, but I can now share with you a TWRP with basic functionality. You of course flash at your own risk. I am not responsible for lost warranty, lost data or any other damage to your device.
This Build of TWRP is based on:
Firmware: A226BXXU4AVB1(Android 11) and A226BXXU4BVF7(Android 12)
TWRP-11 minimal manifest or TWRP-12.1 minimal manifest
Device Tree
Kernel source
Working:
flash of zips
fastbootd
flashing of GSI images (via fastbootd)
MTP
Not working:
Probably a lot of stuff ...
What you need:
Unlocked bootloader.
Odin3 v3.13.1
android platform-tools and device driver.
adb and fastboot
Magisk or GSI depending on what you want to do.
Patience, the device can be very tricky to get to download mode.
How to flash:Be advised that this build is a work in progress and is not ready as a daily driver. Only flash if you know what you are doing.
Spoiler
First read all points below, without doing anything. Warning, you will lose all your data!
If you are on Android 11 firmware download v1.01.2-alpha if you are on Android 12 firmware download the recovery.tar from here.
You start off in Odin, put recovery.tar in AP slot and the vbmeta_disabled_R.tar in the USERDATA slot, uncheck auto-reboot.
After the flash is completed hold down power + volume down, instantly after device goes Black screen press and hold power + vol up to boot to TWRP
if you didn't get to TWRP, you have to flash again.
In TWRP, go to Advanced → terminal.
Type multidisabler two times.
Now go to Wipe → Format Data (not wipe) → and type yes.
You can boot to system now.
Hot to install Magisk:
Spoiler
Method 1, Micro-SDCard
Download Magisk from here, rename the file from .apk to .zip
Save the file to a Mico-SDCard
Reboot the phone to TWRP.
Go to Install → Select Storage → Micro-SDCard. In the file system, choose Magisk-vXX.X.zip and swipe to confirm flash.
You can now Reboot to System
Method 2, sideload
Download Magisk onto your PC from here, rename the file from .apk to .zip.
Reboot the Phone into TWRP. Go to Advanced → ADB Sideload → Swipe to start Sideload.
On your PC, type in a Terminal adb sideload Magisk-v24.3.zip
You can now Reboot to System. adb reboot system
How to install GSI:
Spoiler
Go to Wipe → Format Data (not wipe) → and type yes.
Now reboot to fastboot.
Connect the phone to your pc and startup a terminal of your choice.
In the terminal type fastboot flash system name-of-your-gsi-iamge.img (it has to be a .img file, extract .img.xz files do not just rename them).
You should now be good to go and can reboot to system.
Thanks and credits to:
cheese-ass
akhil99
TeamWin
How to get TWRP log files:recovery.log
adb pull /tmp/recovery.log
OR
Advanced -> Copy Log -> Swipe to copy log to default storage
dmesg
adb shell dmesg > dmesg.log
OR
Advanced -> Copy Log -> check "Include kernel log" -> Swipe to copy log to default storage
logcat
adb logcat -d > logcat.txt
OR
Advanced -> Copy Log -> check "Include Logcat" -> Swipe to copy log to default storage
Changelogv2.00.1-alpha
bump firmware and touchscreen drivers to A226BXXU4BVF7 and TWRP to TWRP-12.1
v1.02.2-alpha
added drivers for himax touch screens.
v1.02.1-alpha
added drivers for novatek touch screens.
v1.01.2-alpha
added patch with improved multidisabler
v1.01.1-alpha
update multidisabler
v1.01.0-alpha
fix permission for mkbootimg
v1.00.0-alpha
Initial Release
This has been tested, right? If it does work, I'll probably try it out when I have free time, which might be in a few days.
Yes, it runs on my A22 5G.
Could-Chaplain said:
Yes, it runs on my A22 5G.
Click to expand...
Click to collapse
It worked. But I didn't read your post carefully and now I have to format data :/
Edit: Ran multidisabler twice. On the second time, it said that /system was an invalid argument
Edit2: Trying to mount partitions don't work, like trying to make a backup or using the file manager. Speaking of backups, I didn't format data because I really don't want to, and it rebooted safely (Thank god), so now I'm making a backup of apps I should have made a week ago.
Edit: Ran multidisabler twice. On the second time, it said that /system was an invalid argument
Click to expand...
Click to collapse
It's the same for me, but no issues so far.
Edit2: Trying to mount partitions don't work, like trying to make a backup or using the file manager. Speaking of backups, I didn't format data because I really don't want to, and it rebooted safely (Thank god), so now I'm making a backup of apps I should have made a week ago.
Click to expand...
Click to collapse
That will be because you didn't format data. If I find sometime, I will try to reproduce that. Thank you, for testing.
Edit: Backups should work fine if you uncheck data?
Is the A226BZH3AUL1 suitable？
a0963655966 said:
Is the A226BZH3AUL1 suitable？
Click to expand...
Click to collapse
If your device is a SM-A226B you should be fine. But as always, flash at your own risk.
Works great! Thanks! Keep up the good work!
Any idea why adb shell doesn't work? For the same reason why /data isn't mountable?
Thank you! Going to test asap.
lebigmac said:
Works great! Thanks! Keep up the good work!
Any idea why adb shell doesn't work? For the same reason why /data isn't mountable?
Click to expand...
Click to collapse
/data is most likely not mountable because you didn't run multidisabler twice and formatted data? ADB shell works fine for me, check in device manager that it shows up as ADB Interface.
Tested working, but haven't succeeded flashing a gsi yet, phone reboots and then goes to blank black screen, and ideas?
koosman911 said:
Tested working, but haven't succeeded flashing a gsi yet, phone reboots and then goes to blank black screen, and ideas?
Click to expand...
Click to collapse
Honestly, it could be everything. Just go over How to flash again. But this time without vbemta and multidisabler. Then continue as described in How to flash GSI. Please let me know if that works for you.
I recommend Pixel Experience.
Could-Chaplain said:
Honestly, it could be everything. Just go over How to flash again. But this time without vbemta and multidisabler. Then continue as described in How to flash GSI. Please let me know if that works for you.
I recommend Pixel Experience.
Click to expand...
Click to collapse
Are you using pixel experience on your device currently?
koosman911 said:
Are you using pixel experience on your device currently?
Click to expand...
Click to collapse
Yes and no, currently I am working on TWRP and there for flash the stock Rom quite frequently. But I do plan to use Pixel Experience. The only thing that does not work is NFC. But that seems to be the case with all the GSI I could find, as they are all based on phh.
Hey Guys, I did some work on the TWRP recovery. It's now more reliable, I highly recommend the update. You will find the download link and updated instructions at the top.
Thank you sir, updated recovery works perfectly on two separate phones so far, I've flashed a few gsi's and they work as far as they are able to obviously each gsi might have its own issues, the two phones I have don't have Nfc so I can't help to test that sadly. We appreciate the hard work.
koosman911 said:
Thank you sir, updated recovery works perfectly on two separate phones so far, I've flashed a few gsi's and they work as far as they are able to obviously each gsi might have its own issues, the two phones I have don't have Nfc so I can't help to test that sadly. We appreciate the hard work.
Click to expand...
Click to collapse
Thank you. What other phones despite the A22 5G are you using the recovery with?
Edit: Ahhh, you mean, you have nothing to test NFC with?
The model of a22 5G available in my country does not have nfc.
Related
DISCONTINUED - Left for research and archive purposes.
After much hardwork @codelover and I are pleased to release both stock rom as well as TWRP 2.8.6.0
for the 2 known variants v31 and v38. Please make sure you download and flash for your specific variant. Check faq if you do not know which variant you have.
REQUIRED FOR BOTH VARIANTS:
Windows XP/Vista/7/8/8.1/10TP 32bit or 64bit
SPFT (Windows Version) “linux version coming soon”
Correct Scatter File
Preloader Drivers (if you do not know how to install manually go here)
ADB
A Brain
Usage:
For flashing either pre-rooted Rom and/or TWRP you will need spft+scatter file. It is imperative that you make sure that if you got a v31 you only uses v31 files not v38. Same for the v38 users only use v38 files. You have been warned.
Click to expand...
Click to collapse
Flashing Rom:
Make sure
Run the file flash_tool.exe
Click on scatter-loading and select your MT8127_Android_scatter_RCA_Vx.txt file
Make sure all listed files are checked and if any isn't double click on it and select the appropriate file
Leave settings as Download Only “if working tab Format All + Download "if wont boot' then hit the Download button
Make sure your tablet is completely switched off then connect it to your PC and the flashing process will commence immediately.
Once it's done, you'll see the tick sign below and that's all. Reboot your device and setup your device afresh.
{
"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"
}
Flashing TWRP:
Same as above except only check mark recovery and select “recovery_twrp2860_vXX.img” and nothing else then proceed.
How to ROOT:
*With stock recovery: Kingo
*With TWRP: SuperSu
DOWNLOADS:
(V31.0 USERS ONLY)
Pre-Rooted Stock ROM (scatter file included in zip and attached below)
TWRP 2.8.6.0 (scatter file included in zip and attached below)
EDIT: TOUCH FOR v31 TWRP IS MISALIGNED FIX IN PROGRESS. LINK REMOVED UNTIL THEN
(V38-V1.8.0 USERS ONLY)
Pre-Rooted Stock ROM (scatter file included in zip and attached below) (Currently being fixed sorry for the issues)
TWRP 2.8.6.0 (scatter file included in zip and attached below) (Currently being fixed sorry for the issues)
NOTICE:
Please keep thread clean and DO NOT ask things others have asked already as you will be ignored. If you do have a honest question and have a working knowledge of android. I would be glad to assist you the best I can. If you are noob and messed something up DO NOT ask for help. Meaning basics of knowing adb,logcat, installing drivers, and so forth. Sorry if you are a noob but please try to understand that things we may ask of your will require this and becomes too much of a slow down if we have to guide you thur everything.
Click to expand...
Click to collapse
CREDITS:
http://twrp.me/ – @Dees_Troy & his team mates, for TWRP Recovery
@codelover - For being an awesome programmer, dev and person!
@TripFX - For being an awesome Tester, v38 rom dump and Dev Machine Hoster
@synius - For v31 rom dump and tester
@nathanski - Tester
@acejay3200 – Being a nice lab rat with knowing i may not be able to make a recovery for you or even brick your working device and not being rude..
Others I may have missed
Discontinued
Faq:
Question: How do I know which variant I have?
Ansere:
Method #1
From a booted android, goto Settings > About > Build number
You should see something like this.
RCT6773W22-ANDROID4.4.2-3101-V38-V1.8.0
Method #2 (Better & more accurate)
For this your device must be rooted & already have USB Debugging Mode enabled.
Make sure adb.exe has been installed on your system (computer).
Execute the following adb command:
Code:
adb shell
su
cat /proc/cmdline
then search for ‘lcm’ text in the output:
If lcm=cpt_clap070wp03xg_lvds < you need to use v31 files
If lcm=1-lxjc070whm270_18a_rgb < you need to use v38 files
Question: What if I dont remember which variant I have and can’t access adb?
Ansere: If this is the case we will need to use SP Flash Tool to help identify your variant.
Open SF Flash Tool, load V38 scatter and switch to ‘Read Back’ tab. Clear all then click Add,
Click the new item & change the output file name from ROM_0 to ROM.txt,
edit the readback address as below:
Start Address: 0x9000000 / Length: 0x1000
Then press “Read back” button, now connect the tab while powered off.
When it’s done, open the file with wordpad and check if you have “ANDROID” at the beginning of the file, if your answer is yes then you have V38, otherwise use V31.
'pleas take with a lol"
edited off bs bulk
Is anyone else having problems with DL link.
nathanski said:
but if you cant test and flash the wrong one re-flash other,,,
because if its not one its the other ....
Click to expand...
Click to collapse
read full faq
leetree2001 said:
Is anyone else having problems with DL link.
Click to expand...
Click to collapse
just test download links in on my pc all download fine Firefox 37.0.1 Win7 x64 all work
no touch in twrp volume keys do nothing power button shuts off tablet boot into android tablet works fine i am trying to make a backup so i dont have to flash everything again
edited off more bloat
i flashed twrp with its own scatter had no touch then with the 4.3 scatter that fixed my tablet now touch works but the buttons dont lineup
acejay3200 said:
i flashed twrp with its own scatter had no touch then with the 4.3 scatter that fixed my tablet now touch works but the buttons dont lineup
Click to expand...
Click to collapse
A correction to V31 in on its way
V38 has good reply on touch working well, small snag regarding to internal storage reported,,,
Well I got it downloaded, and it worked great for me, touch Worked great for me. I did a ful
I backup and all buttons seem to respond to touch. I used twrp easy magic's unpack, repack to install it, thanks you guys, and girl's for you're hard work.
gr8 t2o hear good results, thank you,,,
nathanski said:
Great to hear good results, what file are you reporting success with, if I may ask,,,
I stay on my tablet like most of my time when I'm not working or ect,ect when I stop using it as heavily I am going to install twrp I guess, just haven't made time as the tablet is basically my main device
Click to expand...
Click to collapse
Twrp 2.8.6 v38,the only problem I found is internal sdcard not showing up in file manager. But external sdcard does,
twrp. installer.exe http://forum.xda-developers.com/devdb/project/dl/?id=10082,, its a option
TripFX said:
Faq:
Question: How do I know which variant I have?
Method #2 (Better & more accurate)
For this your device must be rooted & already have USB Debugging Mode enabled.
Make sure adb.exe has been installed on your system (computer).
Execute the following adb command:
Code:
adb shell
su
cat /proc/cmdline
then search for ‘lcm’ text in the output:
If lcm=cpt_clap070wp03xg_lvds < you need to use v31 files
If lcm=1-lxjc070whm270_18a_rgb < you need to use v38 files
Click to expand...
Click to collapse
Note: Watch your tablet as you're doing this. You may have to grant su permissions on the tablet after executing the "su" command in adb.
I tryed using sp flash tool to flash but I couldn't get it to work is there another flash tool I could use thx
edited off bulk,
Edited.
nathanski said:
Yeah there is, in the link I have up showing time stamp 3:23
---------- Post added at 09:18 PM ---------- Previous post was at 09:16 PM ----------
Did you have to copy the whole FAQ in a simple reply
Click to expand...
Click to collapse
Thx for the help it won't boot into recovery it comes on I just can't get into recovery
mike9976 said:
Thx for the help it won't boot into recovery it comes on I just can't get into recovery
Click to expand...
Click to collapse
I can't say as to why but you do need the self education one can learn about how to use spflash tool,, seeing as that's the way that I know that's the first info I could offer ,,, you should get your version information first, then download your ROM because the scatter file that had reports of best results are in the full firmware, and you then need to know that the reset button will bring up a driver install but it happens fast to catch this you need the device manager in windows open, plug the rct in then press reset with a tothpick or other small pin ect,, the device shows up with a sound chimes on windows, right click the new device in the USB group and install using the hosted driver,,, now to the spflash tool its self load the scatter in the full ROM related to the vershion you have and then only check recovery,,, and find the twrp.IMG in you downloads and use only the download option in the spflashtools,, and click download then Right after hit reset on the back of the tablet,,, it can be done ,,,, even for the new people wanting to learn,,, regarding the twrp,installer.exe I linked to, I have no knowledge it was only reported to be a full success by another user before you so I wanted to offer a fast way for others to find it ,, so I linked to the .exe,,, and lastly ON MY TABLET I HAVE TO BE ON A CHARGER TO LAUNCH RECOVERY AT BOOT USING VOLUME KEY,..and you can download a root reboot apk that will boot from inside android directly into recovery,, maybe I helped,,,, p.s. another great thing the full ROM offers is the original OEM recovery.. Pleas do try to learn. As always i do wish every one the best
---------- Post added at 02:45 AM ---------- Previous post was at 02:38 AM ----------
best regards to you @TigerG8
[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?
This is a thread for the rooting and install of TWRP for the Uefone Power 3
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
TWRP 3.2.1-0: https://drive.google.com/file/d/1cLqcDrun5f6h1BHjUFfXDdlhwEWwM-49/view?usp=sharing
SuperSU: https://drive.google.com/file/d/1sZwahrodGJmYWzaIohxEETeIAabCOPfb/view?usp=sharing
Steps to install TWRP and SuperSU
Copy the above SuperSU to your SDCard.
First of all, you will be required to unlock your bootloader.
There is an option for this under Developer Options in the settings menu. Activate this.
Also activate USB Debugging. This makes this a whole lot easier.
Now, open a terminal, if on Linux, or command prompt if on windows, and enter the following:
Code:
adb reboot bootloader
Code:
fasboot oem unlock
Follow the onscreen instructions to unloack your bootloader. THIS WILL WIPE YOUR DEVICE!!!
Once this is complete, it will go back to the fastboot screen.
Now, from within your terminal/command prompt, navigate to the folder where you have downloaded the above recovery.img to.
Enter the following command once there:
Code:
fastboot flash recovery recovery.img
This will flash TWRP to your device, overwriting the stock recovery.
Once this is complete, there will be a screen telling you how long it took etc. Now you need to hold down your volume up button, and power button. Keep holding these untill you reach the menu for recovery, fastboot or normal mode.
Select Recovery.
This will boot into TWRP for the first time. when you get there, you will be prompted with a screen asking for a password. Cancel this.
WHAT EVER YOU DO, DO NOT FORMAT DATA LIKE IT ASKS YOU!"" YOU WILL LOSE TWRP!!!
Your then presented with the main TWRP screen, go ahead and tap on Install. Next, hit Select Storage, and select Storage 1. This is your SDCard.
Now flash SuperSU.
When this is installed, reboot to your main system, and update the SuperSu binary.
Now proceed to reboot back to recovery, how ever you wish.
Once in recovery, go into Wipe, and hit Format Data, this will wipe your phone again, but youve just done this anyway so it doesnt matter
Now flash SuperSU again, just to be safe, the same way as above.
Reboot to your system, and your done!
You will have to go through the setup of the whole android system again, but its worth it your now rooted and have TWRP to install the Custom ROMs that will be coming shortly
Have Fun!
Reserved
wow, that was quick thank you
will try it now and update as soon as it's done!
alright, so i tried to flash super su, but i never get to access the storage partitions (i think they are not mounted).
so i tried to factory reset / wipe the phone to get rid of the encryption, but i still cant select storage 1 from the menu.
here some more detail:
- i have already had the bootloader unlocked
{
"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"
}
- then i come to this screen when twrp starts, and select "swipe to allow modifications"
- then i press install and want to select "storage 1", this however doesnt work. (due to encryption?)
- i tried to mount it, but cant even mark it active. just gets gray for half a second and then nothing
- tried to do a wipe via twrp as well, with no success
any ideas?
tbst1337 said:
alright, so i tried to flash super su, but i never get to access the storage partitions (i think they are not mounted).
so i tried to factory reset / wipe the phone to get rid of the encryption, but i still cant select storage 1 from the menu.
here some more detail:
- i have already had the bootloader unlocked
- then i come to this screen when twrp starts, and select "swipe to allow modifications"
- then i press install and want to select "storage 1", this however doesnt work. (due to encryption?)
- i tried to mount it, but cant even mark it active. just gets gray for half a second and then nothing
- tried to do a wipe via twrp as well, with no success
any ideas?
Click to expand...
Click to collapse
Your third screenshot - what's the last option, under Microsd?
Also, when going through install, can u see "external SD"?
ukhellfire666 said:
Your third screenshot - what's the last option, under Microsd?
Also, when going through install, can u see "external SD"?
Click to expand...
Click to collapse
the last one is USB OTG, also showing 0MB - i actually tried flashing supersu through the usb as well, with no luck
i can see external_sd but there dont seem do be ANY contents
do you think it is the encryption? because everything shows 0MB in brackets
EDIT:
i just thought what the hell i try again to flash it via usb. havent changed anything but suddenly SUCCESS
appreciate your time thanks
tbst1337 said:
the last one is USB OTG, also showing 0MB - i actually tried flashing supersu through the usb as well, with no luck
i can see external_sd but there dont seem do be ANY contents
do you think it is the encryption? because everything shows 0MB in brackets
EDIT:
i just thought what the hell i try again to flash it via usb. havent changed anything but suddenly SUCCESS
appreciate your time thanks
Click to expand...
Click to collapse
So what did you do differently? If you can explain a bit more, I'll change/add it to the guide. Maybe as a second option or something...?
ukhellfire666 said:
So what did you do differently? If you can explain a bit more, I'll change/add it to the guide. Maybe as a second option or something...?
Click to expand...
Click to collapse
i just booted again into twrp and suddenly my 4gb usb was showing up as the only thing not 0mb, so the usb otg partition was mounted. from there on i just pressed install and located the zip file on the usb drive. had some errors. below some pics i took with my old phone:
tbst1337 said:
i just booted again into twrp and suddenly my 4gb usb was showing up as the only thing not 0mb, so the usb otg partition was mounted. from there on i just pressed install and located the zip file on the usb drive. had some errors. below some pics i took with my old phone:
Click to expand...
Click to collapse
Ahhh brilliant! I don't suppose u found that he sdcard was mounted too did you?
Have the errors gone now your rooted? The rest of the guide should still count...?
ukhellfire666 said:
Ahhh brilliant! I don't suppose u found that he sdcard was mounted too did you?
Have the errors gone now your rooted? The rest of the guide should still count...?
Click to expand...
Click to collapse
yes i am indeed rooted!
everything else, including internal storage was 0mb as well. usb otg was literally the only one.
i have not gone back into recovery since, but rebooted several times and also used root apps (adaway). everything seems to work great and the rest of the guide still counts!
in total, everything seems stable until now :good: my goal is to not touch twrp anymore until android 8.1 will be released
tbst1337 said:
yes i am indeed rooted!
everything else, including internal storage was 0mb as well. usb otg was literally the only one.
i have not gone back into recovery since, but rebooted several times and also used root apps (adaway). everything seems to work great and the rest of the guide still counts!
in total, everything seems stable until now :good: my goal is to not touch twrp anymore until android 8.1 will be released
Click to expand...
Click to collapse
The official 8.1 update with overwrite TWRP.
I am now working on a cm14.1 build. As im having to use a prebuikt kernel, this is as far as I can go.
As soon as I have a beta ROM I'll upload.
Don't suppose you could boot to recovery and just double check that everything is as it should be? Put my mind at ease, make sure it works for you, as it does for me...
ukhellfire666 said:
The official 8.1 update with overwrite TWRP.
I am now working on a cm14.1 build. As im having to use a prebuikt kernel, this is as far as I can go.
As soon as I have a beta ROM I'll upload.
Don't suppose you could boot to recovery and just double check that everything is as it should be? Put my mind at ease, make sure it works for you, as it does for me...
Click to expand...
Click to collapse
sure man, maybe joining me on discord would make this process faster https://discord.gg/jPZqn4
Hi.
Thank you for twrp.
I am trying to use SuperSu with SuHide, i wipe data with this twrp to be able to install supersu in BINDSBIN mode to /data but data partition stay unencrypted to be mountable with thw twrp.
How to encrypt it back with own known password keeping supersu and suhide working?
TWRP has no option to reformat with password, no way to get origin password for stock recovery formated partition.
Any idea?
MioCZ said:
Hi.
Thank you for twrp.
I am trying to use SuperSu with SuHide, if i wipe data with this twrp to be able to install in BINDSBIN mode to /data but data partition stay unencrypted.
How to encrypt it back with keep supersu and suhide working?
TWRP has no option to reformat with password, no way to get origin password for stock recovery formated partition.
Any idea?
Click to expand...
Click to collapse
No idea I'm afraid. Sorry.
I used encryption in system Setup, i works, but with unknown password stored somewhere in nvdata partition. I am worry about loose root after OTA update and without pasword for twrp no way to get again to data partition.
I'm thinking of buying this phone. It's great to see that root already seems to work and that there might be a CM/LineageOS Rom soon. Root and custom recovery is crucial so one reason less to not buy it.
Are you guys happy with it in general? Does the dual camera work with bokeh and shoot good photos with low lag required to capture playing kids? Good value?
I can not install Snap Chat
Thank you ukhellfire666
The recovery was successfully installed
My question:
is there any idea to fully remove superSu to install snapchat
A full system backup has been taken.
DaF1974 said:
I'm thinking of buying this phone. It's great to see that root already seems to work and that there might be a CM/LineageOS Rom soon. Root and custom recovery is crucial so one reason less to not buy it.
Are you guys happy with it in general? Does the dual camera work with bokeh and shoot good photos with low lag required to capture playing kids? Good value?
Click to expand...
Click to collapse
good day to you.
in general i am happy with it, but the camera really blows. it is - without a doubt - the worst camera i had since my LG VX-5200. iphone 6s and galaxy s6 have way better cameras.
i am really frustrated, because they advertised the 4 cameras ..." " heavily, but they really suck. maybe it's just with the stock app and another app would make it better (but somehow i doubt that)
tomorrow i will go on holiday and was stoked that the phone arrived before, so i could take it with me to take pictures etc. seems like i will need to get the old digital camera out....
alshyib said:
Thank you ukhellfire666
The recovery was successfully installed
My question:
is there any idea to fully remove superSu to install snapchat
A full system backup has been taken.
Click to expand...
Click to collapse
Is possible to flash un-supersu package. Is somewhere in SuperSu topic. Or you can flash clean ROM / your backups (boot.img, recoovery.img, system.img).
Because this i have used supersu in BINDSBIN mode and suhide. So i have hiden su, locked bootloader, working OTA and all root sensitive apps.
bootloop
Hello, I followed the instructions but my phone bootloop on twrp, it does not start the system can you help me please?
---------- Post added at 02:23 AM ---------- Previous post was at 02:21 AM ----------
Hello, I followed the instructions but my phone bootloop on twrp, it does not start the system can you help me please?
(Resized to fit the XDA thread for mobile phones)
{
"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"
}
Hello everyone, my name's SmallTarzan (@dotMiracle at Telegram), and I'm here to do it once again - to write yet another guide.
But, why am I doing this? There are two other guides already that explain the installation process well.
Well, I've gone through them, and the first one was not clear to me, I had to read it several times to properly understand the guide. I think that's, especially for new users, not helpful. The other one was written quite well, (shoutout to @madsponge26).
So, here I am, with my little bit to add to this, so far quite empty, sub-forum.
- an unlocked bootloader
- a TWRP recovery image
- a GSI image of your choice
- an Encryption Disabler - the current build of TWRP cannot decrypt your data
The process of unlocking the bootloader is the same on all Xiaomi devices. (Not counting the Android One ones.)
This process factory-resets your phone.
-
0. Open your phone's settings, go to About Phone at the top, find "MIUI version (For POCO)", and tap on it 7 times. (You should see a notification at the bottom, that you are now a developer.)
0.1 Go back, scroll down to Additional settings > Developer Options > Check "OEM unlocking" slider, (it may ask you for your password). Also, open "Mi Unlock status", agree to the permissions, and click on "Add account and device".
0.2 After this, you have to wait for 72 hours to unlock your phone. (Xiaomi Security Procedure)
-
1. Head over to Xiaomi Unlock Tool website, register, if you haven't yet, and download the tool.
2. Open the tool, accept the agreement, log in, and connect your device via USB-C cable to your computer.
3. Now, we'll need to reboot our device to fastboot: Turn off your device completely, hold down power button + volume down button at the same time, until you see a green logo of "fastboot".
4. The tool should now detect the device, press the Unlock button.
At the moment, there's only one TWRP recovery image available for this phone.
0. Currently, the TWRP cannot decrypt your data, make sure to back it up beforehand.
-
0.1 Download the Encryption disabler
0.2 Download ADB tools (Also, run the .exe, let it install all the required files, the driver from Google too.)
0.3 It's recommended to remove your screen-lock before doing this.
1. Reboot your device to fastboot again: Turn off your device completely, hold down power button + volume down button at the same time, until you see a green logo of "fastboot".
1.1 Connect your device to your computer.
2. Open your ADB folder, shift+right click on an empty space in the folder, choose open a Powershell/Command prompt window. (The folder should be located at C:/adb, or in the root of your system drive /adb.)
3. Now, put the recovery image you've downloaded in the ADB folder.
4. Type: fastboot flash recovery twrp-3.2.3.0-beryllium-20180831.img (You can, optionally, rename the file to recovery.img to make the typing easier for you.)
5. Once the process completes, hold down the power button + volume up button. (Your device may even restart twice, hold these buttons until you see the TWRP recovery screen.)
6. Allow modifications, if prompted.
7. Go to Install > select the DisableForceEncryption_Treble.zip > Swipe to flash it.
8. Once that's done, go back to the main screen (by using the on-screen buttons), Wipe > Advanced Wipe > Select Data > Swipe to wipe.
9. Go back to the main screen again, Reboot > Recovery.
(Android P for Poco F1. For those who didn't get the pun.)
0.1 Let's get the image we want first. Head over to the: Treble-Enabled Device Development, and choose the OS you'd like.
For the sake of this tutorial, and obviously, the header with Android P in it, we'll use one of the P GSI images. I, personally, like the ArrowOS.
0.2 Reboot into recovery, and connect the device to your computer.
1. Download the ArrowOS-9.0-OFFICIAL-GSI-A.zip to your computer. (Or any other .zip you'd like to install.)
2. Unzip the file with WinRAR or 7zip.
3. Copy the .img file to either your SD card, or your internal storage.
4. Install > On the bottom right "Install Image" > Find the .img file > Tap on it.
5. Select partition System/System Image > Swipe to flash.
6. This might not be necessary, but I highly recommend flashing the DisableForceEncryption_Treble.zip again.
6.1 If you don't need root, reboot the device. (Reboot > System)
0. You may, as well, reboot the device first, and do the setup, in order to avoid any potential issues.
1. Download the latest stable version of Magisk.
2. Reboot to recovery.
3. Install > Find Magisk-v17.2.zip (make sure you selected "Install zip" at the bottom right) > Find the .zip file > Swipe to Flash.
4. Again, it's recommended to flash the DisableForceEncryption_Treble.zip.
5. Reboot > System.
@madsponge26
@Shivam Kumar Jha - used his TWRP image in this guide.
@ganesh varma - used his ArrowOS GSI in this guide.
No sound/Broken sound/Low volume temporary fix: here.
For GApps, you can download them here. Flash them through the TWRP recovery.
Reserved.
EDIT: The guide works for both MIUI 10, and P custom GSI ROMs.
Also, search for GSI A images.
Thanks @SmallTarzan for the tutorial. I will try it.
Starred for later reference when I finally got this phone.
Sent from my Xiaomi Redmi Note 4 using XDA Labs
This is the first guide i actually understood. Thank you for that. I've one question though, the OS you suggested, is it stable for poco f1. I'm actually new to a treble device so i don't actually know how it works. Thank you once again for this guide.
Hello, thank you for your guide it's really very well explained with enough details that any newb can understand.
Btw, i have suggestion for your thread title, if you want you should rename your thread title to "[GUIDE]Install Any Android P GSIs In Your Poco"
Its just my suggestion cause i think it's better to follow the correct proforma:silly:
Anyway, have a nice day.
Regards,
Ali.
u_knw_who said:
This is the first guide i actually understood. Thank you for that. I've one question though, the OS you suggested, is it stable for poco f1. I'm actually new to a treble device so i don't actually know how it works. Thank you once again for this guide.
Click to expand...
Click to collapse
I haven't tried it yet, I'll do a test tommorow, and I'll let you know the result.
Ali Haide 001 said:
Hello, thank you for your guide it's really very well explained with enough details that any newb can understand.
Btw, i have suggestion for your thread title, if you want you should rename your thread title to "[GUIDE]Install Any Android P GSIs In Your Poco"
Its just my suggestion cause i think it's better to follow the correct proforma:silly:
Anyway, have a nice day.
Regards,
Ali.
Click to expand...
Click to collapse
Done, thanks!
Thanks for your well made guide. I just wonder how well everything works with these GSI images. Usually some features don't work.
Tomatot- said:
Thanks for your well made guide. I just wonder how well everything works with these GSI images. Usually some features don't work.
Click to expand...
Click to collapse
I haven't faced any issues.
SmallTarzan said:
I haven't faced any issues.
Click to expand...
Click to collapse
is gcam and face unlock working with you?
adityajiwap said:
is gcam and face unlock working with you?
Click to expand...
Click to collapse
I'll let you know later today.
@SmallTarzan,
I didn't see Treblizing step ..... Does it mean this Poco F1 is Treble enabled already?
don´t have sound.
Anyone have the same problem?
yis221 said:
@SmallTarzan,
I didn't see Treblizing step ..... Does it mean this Poco F1 is Treble enabled already?
Click to expand...
Click to collapse
Yes, it is.
detritu5 said:
don´t have sound.
Anyone have the same problem?
Click to expand...
Click to collapse
Correct, it's a bug currently present on some treble ROMs.
https://forum.xda-developers.com/poco-f1/how-to/temp-audio-distorted-p-gsis-fix-t3839427
Good stuff, five stars for you my friend for putting in the effort to help the rookies
is face unlock working?
ganyguru said:
is face unlock working?
Click to expand...
Click to collapse
Not in treble roms as of now.
detritu5 said:
don´t have sound.
Anyone have the same problem?
Click to expand...
Click to collapse
use global stable rom as base before installing GSI. it should fix it
u_knw_who said:
Not in treble roms as of now.
Click to expand...
Click to collapse
is there an apk for the facescanner in the stock rom?
Running PixelExperience 8.1 GSI. Had a problem on the google initial play service setup. google came up with a message that my device is uncertified and I had to register it at google to use the play service. Anyone else got that problem ?