Related
Hey,
TWRP 3.1.1 Touch Recovery beta version is released for Xiaomi Mi A1.
Download - Go to downloads tab
Update:
1. Magisk v13.4 is working fine.
Workaround for Xposed:
Xposed is not installing through TWRP and when tried with App, still it's giving errors. So below is the temporary solution till we get a permanent one.
1. Don't flash TWRP. Just boot into it from bootloader by using command - fastboot boot recovery_name.img
2. Flash latest SuperSU zip.
3. Reboot to System.
4. Your phone will be rooted now and install Xposed through app.
Important:
1. Don't flash it, just boot into it.
2. If flashed, re-flash the latest stock boot image.
Instructions:
1. Download the twrp image and twrp installer zip
2. fastboot boot twrp-3.1.1-tissot-beta.img
3. Flash twrp-installer-tissot-3.1.1.zip
4. Reboot to recovery
Flash Magisk v13.4 built for Pixel devices by @Goodwin_c. Available in the downloads tab.
Issues:
1. Flashing SuperSU will break TWRP. SuperSU will work, but TWRP will be gone.
2. Xposed won't flash without modification.
Future update:
1. Make TWRP and SuperSU to co-exist
2. Compatibility with Xposed and Latest Magisk
Disclaimer:
We are not responsible for anything that may happen to your phone as a result of installing custom recoveries, roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
XDA:DevDB Information
TWRP 3.1.1 for Mi A1, Tool/Utility for the Xiaomi Mi A1
Contributors
mahefooz4u, ravinder0003, Thanks to @Dees_Troy and TWRP Team
Source Code: https://github.com/mahefooz/android_device_xiaomi_tissot
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-10-15
Created 2017-10-13
Last Updated 2017-10-16
good work bro waiting for development to start
Great work!
Celebrations
The first step towards the good community has been taken
Great were all waiting for devs to take a look at this devices ! Will it be official when you've fixed the boot issue ? thanks
great work!! thanks guys :good: Will I be able to flash Aroma Uninstaller to debloat?
deepakmohank said:
great work!! thanks guys :good: Will I be able to flash Aroma Uninstaller to debloat?
Click to expand...
Click to collapse
Yes, Aroma installer is working
thank-you. Have you tried the way Pixel devices boot twrp, send twrp zip to internal, then flash?
---------- Post added at 11:28 AM ---------- Previous post was at 11:01 AM ----------
Sorry for asking too many questions, one more to add, which s the partition that mounts when we mount System from twrp? Is it a or b?
Coolio
lakyman said:
Great were all waiting for devs to take a look at this devices ! Will it be official when you've fixed the boot issue ? thanks
Click to expand...
Click to collapse
Don't expect too much from now.
Wait for sometime as this is ported
Great work waiting for stable version... ?
great, thank you very much!!!
deepakmohank said:
Sorry for asking too many questions, one more to add, which s the partition that mounts when we mount System from twrp? Is it a or b?
Click to expand...
Click to collapse
yea good question, I'd like to know about it too..
marhensa said:
great, thank you very much!!!
yea good question, I'd like to know about it too..
Click to expand...
Click to collapse
I could see in Pixel forums about flashing twrp. It has options to back up a, b partitions or even both. Atm no access to computer, will need to check whether urs allow us the same.
Pixel twrp a/b link:
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Surprise!!!
Booted TWRP? But isn't temporary? Sad ?.
But don't worry, I have created a zip, ahh actually ported a zip ?, to flash TWRP permanently ?.
But please do note that I haven't tested this personally yet, as I'm in a bus, traveling right now.
But if guys have guts, then go ahead, & try this, & please report back .
Instructions:
Boot TWRP & just flash this zip from TWRP. That's all...
Link:
https://www.androidfilehost.com/?fid=962021903579484616
Update Test 2: https://www.androidfilehost.com/?fid=962021903579484804
If it works, please don't forget to hit thanks...
deepakmohank said:
I could see in Pixel forums about flashing twrp. It has options to back up a, b partitions or even both. Atm no access to computer, will need to check whether urs allow us the same.
Pixel twrp a/b link:
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Click to expand...
Click to collapse
No support for a/b system. Only active system can be reached
Thanks for great effort by devs
thanks for sharing~
hope it works~
Hi!
I just want to post my experiences so far.
TWRP booted up fine, also backup and MTP works.
I tried flashing magisk v14.2, which's installer told me the B slot is currenly active etc. Flashed without any problem. But rebooting the device I got bootloop.
Restoring the boot image from the backup made the device back to booting state.
ghpranav said:
Booted TWRP? But isn't temporary? Sad ?.
But don't worry, I have created a zip, ahh actually ported a zip ?, to flash TWRP permanently ?.
But please do note that I haven't tested this personally yet, as I'm in a bus, traveling right now.
But if guys have guts, then go ahead, & try this, & please report back .
Instructions:
Boot TWRP & just flash this zip from TWRP. That's all...
If it works, please don't forget to hit thanks...
Click to expand...
Click to collapse
unfortunately it does not work
h**p://kephost-image.tk/files/64k6re0jfsp4zmienhkr.png
TaRsY said:
Hi!
I just want to post my experiences so far.
TWRP booted up fine, also backup and MTP works.
I tried flashing magisk v14.2, which's installer told me the B slot is currenly active etc. Flashed without any problem. But rebooting the device I got bootloop.
Restoring the boot image from the backup made the device back to booting state.
Click to expand...
Click to collapse
Somehow Magisk is not yet working in Mi A1. Either flashed through recovery or other method, getting bootloop and other issues.
TaRsY said:
Hi!
I just want to post my experiences so far.
TWRP booted up fine, also backup and MTP works.
I tried flashing magisk v14.2, which's installer told me the B slot is currenly active etc. Flashed without any problem. But rebooting the device I got bootloop.
Restoring the boot image from the backup made the device back to booting state.
Click to expand...
Click to collapse
If you know then Magisk is not supported officially for A/B partitons devices including Pixel
Hello guys.
I've seen this device development for custom rom and custom recovery are slow (they did it in privat currently, invited user or someone who want to join). The unofficial twrp having issue with encrypted device (asking for password). So internal storage in twrp isnt accesible and need to format data to make it works. Of course ROOTING with TWRP is still POSSIBLE by placing magisk to extSdcard anyway.
And this guide is a SECOND chance for you who wants to ROOT your phone WITHOUT TWRP. But, need a PC. The root method here are from magisk thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 .
Things needed :
- Unlocked Bootloader
- PC with ADB and Fastboot installed
- boot.img of your miui rom. You can grab it (open with winRar) from fastboot firmware (.tgz) xiaomi redmi S2. Download the firmware file in xiaomi site or in this section thread. The version are reccomended to be the same as your current miui version.
- Magisk Manager.apk https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.1/MagiskManager-v6.0.1.apk
- Know how to use minimal adb and fastboot.
Again this method does not need root, and also does not require a custom recovery. boot.img & UBL is a must.
1. Open Magisk Manager
2. Press Install > Install > Patch Boot Image File, and select your boot.img file
3. Magisk Manager will now patch your boot image, and store it in Internal Storage/Download/patched_boot.img
4. Copy the patched boot image to your PC. Place it in Minimal ADB & Fastboot directory.
5. Flash the patched boot image to your device. Here is the command :
fastboot flash boot boot.img
6. If adb say "Okay" twice, mean it succesfully.
Type : fastboot reboot
7. Wait your phone to reboot.
8. Voila!
I've done this method with my Redmi 5 Plus and not having any issue. Technically, bootloop risk are very low. Because magisk disable dm-verity.
I dont know someone already make a guide about this here. But its not detailed. So, ill keep this thread on. For root with custom recovery TWRP here.
GueztStar said:
I dont know someone already make a guide about this here. But its not detailed. So, ill keep this thread on. For root with custom recovery TWRP here.
Click to expand...
Click to collapse
Actually we have a developer working for our device. And also, we have our own forum and a treble supported TWRP and a special GSI for our device. The only thing which is not working in the GSI is there VoLte. Please visit our forum mi-ysl.tk
---------- Post added at 04:55 AM ---------- Previous post was at 04:51 AM ----------
reynold30 said:
Actually we have a developer working for our device. And also, we have our own forum and a treble supported TWRP and a special GSI for our device. The only thing which is not working in the GSI is there VoLte. Please visit our forum mi-ysl.tk
Click to expand...
Click to collapse
The credit mainly goes to @Peaktogoo
reynold30 said:
Actually we have a developer working for our device. And also, we have our own forum and a treble supported TWRP and a special GSI for our device. The only thing which is not working in the GSI is there VoLte. Please visit our forum mi-ysl.tk
---------- Post added at 04:55 AM ---------- Previous post was at 04:51 AM ----------
The credit mainly goes to @Peaktogoo
Click to expand...
Click to collapse
In general people didnt know that like i am. But, im glad to hear that. My friend have this phone and think about doing these kind of.
GueztStar said:
In general people didnt know that like i am. But, im glad to hear that. My friend have this phone and think about doing these kind of.
Click to expand...
Click to collapse
Am glad to help you
Why this phone don't have custom rom? What am I missing?
This method actually works for my S2. Thanks for sharing.
Download twrp redmi s2 by peak
Fastboot boot twrp.img
Press Cancel
Flash magisk zip
Reboot
Done
Please give latest mi magisk patched boot image .
Please ..
Thanks a lot, Gueztar!
Your method has worked on my Redmi S2.
This is the new refined home for DarkRoom Development. If you submit bug reports without a log, you may be prosecuted...or executed.
Disclaimer:
If your device fails to comply with your standards of what you consider functioning, I am not liable. This is provided free of charge and does not come with a warranty. Although, if you provide a log, I can provide some sort of assurance that I will look into your issue.
Links:
Social:
Telegram - https://t.me/darkroomdev
Discord - https://discord.gg/BGTFutW
Downloads:
https://drive.google.com/open?id=1SLC6A4RvTE_yYF_u6GMKU_q7lvX3YCFB
Source:
Github – https://github.com/DespairFactor/
Credits:
Google
Will certainly give it a try, appreciate your work!!
Will this make the touch screen work on TWRP (for 3XL?)
+1 will try once i get behind my PC
is the function to disable FSYNC available?
Ariel_PR said:
Will this make the touch screen work on TWRP (for 3XL?)
Click to expand...
Click to collapse
As of now, it does not.
Would it be possible for a list of items that are different / features of the kernel.
Thanks!
your the man
can we please get a list of features, etc
what is the purpose of performanced? @DespairFactor
---------- Post added at 08:20 PM ---------- Previous post was at 07:55 PM ----------
disable fsync
reap the benefits of speed
+1
@DespairFactor
curious to know if the kernel would let us boot /data as EXT4 - i have tried formatting /data as EXT4 with stock kernel (and adding appropriate lines for fstab.sdm845) but it always returns device is corrupt, please format device. when i boot. (i dont know if this is a kernel issue because i have formatted ext4 to f2fs before on other devices with stock kernel that support f2fs)
as odd as it sounds, i believe we can extract more performance out of the device if we format as EXT4 instead of the stock F2FS
the partitioning of F2FS on the pixel 3/xl is disgusting i believe this is why if you run /data decrypted you can no longer set a fingerprint or change PIN from settings.
accordng to the TWRP thread - -and old Pixel XL 2 forums - there is something that needs to be included in the kernel in order for touch responsiveness to work properly after flashing TWRP - this is supposed to come with a custom kernel - I don't know what files are needed - but hopeing this can be done with this kernel so we can finally flash TWRP on the 3 XL - (we can boot into twrp with adb and flash a kernel that way - but it is only a temporary custom recovery then)
Geekser said:
accordng to the TWRP thread - -and old Pixel XL 2 forums - there is something that needs to be included in the kernel in order for touch responsiveness to work properly after flashing TWRP - this is supposed to come with a custom kernel - I don't know what files are needed - but hopeing this can be done with this kernel so we can finally flash TWRP on the 3 XL - (we can boot into twrp with adb and flash a kernel that way - but it is only a temporary custom recovery then)
Click to expand...
Click to collapse
https://github.com/DespairFactor/bl...c0260/arch/arm64/configs/b1c1_defconfig#L1996
The touchscreen drivers need to be built inline instead of a module
Freak07 said:
https://github.com/DespairFactor/bl...c0260/arch/arm64/configs/b1c1_defconfig#L1996
The touchscreen drivers need to be built inline instead of a module
Click to expand...
Click to collapse
thanks for the clarity - honestly, this is way over my head - but hoping that someone will do what is needed to make this happen. When you say they touchscreen drivers need to be built inline - do you meant they need to be built inline in the kernel itself? if that is the case, hopefully the Dev for the Despair Kernel can look into that for a future update -
Geekser said:
thanks for the clarity - honestly, this is way over my head - but hoping that someone will do what is needed to make this happen. When you say they touchscreen drivers need to be built inline - do you meant they need to be built inline in the kernel itself? if that is the case, hopefully the Dev for the Despair Kernel can look into that for a future update -
Click to expand...
Click to collapse
I’m pretty sure you won’t be disappointed
Freak07 said:
https://github.com/DespairFactor/bl...c0260/arch/arm64/configs/b1c1_defconfig#L1996
The touchscreen drivers need to be built inline instead of a module
Click to expand...
Click to collapse
You can't, the kernel won't boot with the Samsung touchscreen driver compiled inline
DespairFactor said:
You can't, the kernel won't boot with the Samsung touchscreen driver compiled inline
Click to expand...
Click to collapse
Oh well.... That’s bad news
DespairFactor said:
You can't, the kernel won't boot with the Samsung touchscreen driver compiled inline
Click to expand...
Click to collapse
Does that mean it won't be possible to ever flash TWRP as a permanent Recovery solution? That instead we will have to boot into TWRP each time we watn to flash something? Just curious....I guess it wouldn't be that big of a pain the butt....
Geekser said:
Does that mean it won't be possible to ever flash TWRP as a permanent Recovery solution? That instead we will have to boot into TWRP each time we watn to flash something? Just curious....I guess it wouldn't be that big of a pain the butt....
Click to expand...
Click to collapse
I use EXKM or Franco Kernel Updater to flash kernel and then flash magisk with magisk manager followed by a reboot
DespairFactor said:
I use EXKM or Franco Kernel Updater to flash kernel and then flash magisk with magisk manager followed by a reboot
Click to expand...
Click to collapse
I think he's referring to getting an up and running permanent TWRP install for flashing ZIPs.
DespairFactor said:
I use EXKM or Franco Kernel Updater to flash kernel and then flash magisk with magisk manager followed by a reboot
Click to expand...
Click to collapse
I was wondering about that. So, flash with kernel app but don't reboot. Immediately flash magisk via magisk manager and reboot. Any chance dispair kernel maintains root after a kernel flash in the future?
Sent from my crosshatch using XDA Labs
airmaxx23 said:
I think he's referring to getting an up and running permanent TWRP install for flashing ZIPs.
Click to expand...
Click to collapse
Well, I don't know if we can do that right now, we'd need to load the modules in TWRP
ridobe said:
I was wondering about that. So, flash with kernel app but don't reboot. Immediately flash magisk via magisk manager and reboot. Any chance dispair kernel maintains root after a kernel flash in the future?
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
Yeah that's what I did, but I don't think so
Disclaimer : I am in no way an experienced developer and make sure that you have the stock firmware if needed. Please do not follow this guide if you do not know what you are doing.
Description
This is something I thought of doing as I needed this tablet for university work. I do not promise support but will post if I get more things like this done.
Kernel with Defex disabled for Samsung Galaxy Tab A 8.0 (2017) T385.
The boot image was repacked with a stock boot image and a custom compiled kernel only with modifications to remove defex and to be able to flash magisk on the latest firmware (XME-T385DXU3CTH2-20200828114930) which it was extracted from.
The ZImage is attached if you want to repack it by yourself.
I do not guarantee if this will work on your device. Flash at your own risk.
Notes on Flashing and Root
What I have used :
1. Flash boot.img to BOOT in heimdall with `--no-reboot`
heimdall flash --no-reboot --BOOT boot.img
2. Use key combo to get into TWRP Recovery
3. Factory Reset -> Type yes
4. Reboot into TWRP Recovery
5. Flash Universal+DM-Verity+and+ForceEncrypt+Disabler+(2020-11-02)
6. Flash RMM_Bypass_v3
7. Reboot into System and verify that the kernel version is correct (3.18.120 Feb 9 2021)
8. Reboot to Recovery and flash Magisk normally
Download
Github Release
Credits
@corsicanu - RMM_Bypass_V3
@SebaUbuntu - Device Tree Skeleton
References
RMM Bypass Guide
Compiling Kernel Guide
Defex Discussion Github Magisk
Android Image Kitchen
Probably keep another post just in case.
Its worked and my SM-T385 has been rooted !!!
Thank you so much for your kernel @brokenaxe
GitHub Link not working !!!
Thankyou sooo much mann.. You don't know how frustrated I was with three SM-T385 tabs in my office which were dead slow and desperately needed root. Those things straight up bootlooped after installing magisk and I was always back to square one. You're a lifesaver. Thanks again...
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Oneplus 6 that supports Android 11
can be flashed to boot with working decryption on android 11 roms
bugs:
backup/restore is unreliable
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto (Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_oneplus_enchilada
https://github.com/TeamWin/android_device_oneplus_sdm845-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/oneplus/oneplus6.html
Can anyone confirm if it work with the enchilada hotfix update for OOS 11 OB1?
Edit: Nope! Qualcomm Crashdump all the way
does not work. crash_dump. If repackaged with a stock kernel, it hangs on the TWRP logo.
Soft_M said:
does not work. crash_dump. If repackaged with a stock kernel, it hangs on the TWRP logo.
Click to expand...
Click to collapse
The kernel I'm using is Q based as that's the stable one, can you get logs after repacking with stock?
adb pull /tmp/recovery.log
adb logcat > logcat.txt
Nebrassy said:
The kernel I'm using is Q based as that's the stable one, can you get logs after repacking with stock?
adb pull /tmp/recovery.log
adb logcat > logcat.txt
Click to expand...
Click to collapse
For me this is a mystery, but now I repackaged it again with the stock kernel, and it started correctly.
Soft_M said:
For me this is a mystery, but now I repackaged it again with the stock kernel, and it started correctly.
Click to expand...
Click to collapse
cool,not much can be done right now though, as the android 11 kernel sources haven't been published yet for custom kernels to integrate what they did, and I nee to modify the kernel for fastboot boot to work, so consider this TWRP for stock 10 and customs, it's working on custom 11 roms
Maby remove the link or hole posted , because now people get crash dump error and that can't be good
NLhardcore said:
Maby remove the link or hole posted , because now people get crash dump error and that can't be good
Click to expand...
Click to collapse
this is for custom roms currently, not for stock 11
anyone can test on latest beta?, join the tg group
uploaded new build supporting stock android 11
Nebrassy said:
uploaded new build supporting stock android 11
Click to expand...
Click to collapse
bro i, we, love you, you just saved my life now, im testing it and i will try to flash something, last build is working but boot only didnt flash it yet, but seems working good, anyway super thx for your work <3
edit 1 : i just flashed a file, flashed without any problem
edit 2 : i flashed current twrp, working good <3
edit 3 :
i tell you guys, this TWRP working PERFTECT for ONEPLUS 6 ANDROID 11 STABLE
data decryption works?
CYB3R0ID694 said:
data decryption works?
Click to expand...
Click to collapse
i dont know what u mean bro, but i have password on my device and twrp asked me for it and i use it to unlock twrp, i think this is ur question? sorry for bad english
Evon88 said:
bro i, we, love you, you just saved my life now, im testing it and i will try to flash something, last build is working but boot only didnt flash it yet, but seems working good, anyway super thx for your work <3
edit 1 : i just flashed a file, flashed without any problem
edit 2 : i flashed current twrp, working good <3
edit 3 :
i tell you guys, this TWRP working PERFTECT for ONEPLUS 6 ANDROID 11 STABLE
Click to expand...
Click to collapse
How do I root after this? can I directly install magisk zip or is it not supported yet?
Nitesh Gohil said:
How do I root after this? can I directly install magisk zip or is it not supported yet?
Click to expand...
Click to collapse
i was hava a problem with my root, i installed GPU Booster and its bootloop ( before TWRP ) so i installed official boot.img again, and i was trying to root again with patched boot.img its bootloop again so i flashed official boot.img again and my phone start working normal,
AFTER TWRP, i FLASHED magisk uninstaller and boot to sys, work 100%
reboot to TWRP and install MAGISK installer and flashed 100%
now im rooted by TWRP
sorry for saying all this but just to make u sure that i FLASHED uninstaller once, and installer and working super fine
ADVICE: For battery drain in A11 : root and download this app
NoAd Battery Calibrator [ROOT] - Apps on Google Play
Calibrating your battery after flashing a new ROM may increase your battery life
play.google.com
get your phone to 100% battery and give root access to the app and click on Calibrate it will ask u for root give access and after give access press again on Calibrate, its working so good
Evon88 said:
i was hava a problem with my root, i installed GPU Booster and its bootloop ( before TWRP ) so i installed official boot.img again, and i was trying to root again with patched boot.img its bootloop again so i flashed official boot.img again and my phone start working normal,
AFTER TWRP, i FLASHED magisk uninstaller and boot to sys, work 100%
reboot to TWRP and install MAGISK installer and flashed 100%
now im rooted by TWRP
sorry for saying all this but just to make u sure that i FLASHED uninstaller once, and installer and working super fine
ADVICE: For battery drain in A11 : root and download this app
NoAd Battery Calibrator [ROOT] - Apps on Google Play
Calibrating your battery after flashing a new ROM may increase your battery life
play.google.com
get your phone to 100% battery and give root access to the app and click on Calibrate it will ask u for root give access and after give access press again on Calibrate, its working so good
Click to expand...
Click to collapse
Thanks! I just flashed magisk zip directly and I can confirm it's working without any hiccups
Evon88 said:
ADVICE: For battery drain in A11 : root and download this app
NoAd Battery Calibrator [ROOT] - Apps on Google Play
Calibrating your battery after flashing a new ROM may increase your battery life
play.google.com
get your phone to 100% battery and give root access to the app and click on Calibrate it will ask u for root give access and after give access press again on Calibrate, its working so good
Click to expand...
Click to collapse
Battery calibration apps don't do anything that any android rom couldn't do. What those apps do is reset your battery stats. But every time your phone is charged to 100% and you unplug it, your battery stats get automatically reset.
Any chance for 6t build?
Moe2003 said:
Any chance for 6t build?
Click to expand...
Click to collapse
same build should boot on 6t
Siddk said:
same build should boot on 6t
Click to expand...
Click to collapse
if thats true then why is there a 6t and 6 twrp separate?