Code:
#include
/*
* 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.
*/
NVFlash backups, please do them before flashing anything below otherwise you will **** out of luck if you brick
Download:
cm-12-20150219-UNOFFICIAL-tf201.zip
cm-12-20150321-UNOFFICIAL-tf201.zip
cm-12.1-20150405-UNOFFICIAL-tf201.zip
cm-12.1-20150713-UNOFFICIAL-tf201.zip
Recovery:
recovery.img
Note that the touch buttons are really close together and there's no confirmation before you want to flash a zip sooooo... use the power keys if you are extra scared/careful.
In addition, the script output is impossible to see, which is kinda problematic.
XDA:DevDB Information
Cyanogenmod 12.1 Unofficial, ROM for the Asus Eee Pad Transformer Prime
Contributors
Namidairo, Androidroot, CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-02-15
Last Updated 2015-04-05
Hi. I see no download section. So do I use the current recovery or should I wait? Using twrp with f2fs.
Hi,
What's the differences with official cm12 for tf300t?
I tested tf300 official and had lots of problems and I would prefer not to have them again ?
hi, please upload f2fs recovery if this rom support f2fs.thank you!
Edit: all is good. I'm back on track.
Ahhhh. I used the one from cm11 topic. Big mistake. Now I'm getting android service icon flashing screen. Reboot is the same, can't access fastboot or bootloader or recovery, tablet is recognized by pc. Attached the picture of what is on my screen if anyone has an idea.
Just curious. Installed cm recovery, the rom and gapps (the smallest ones) and now waiting at Asus bootlogo. How long does the first boot take?
I have the same problem. My TF201 is stuck at the bootscreen with the Asus-logo.
What did I do:
- wiped cache
- factory reset
- flashed recovery.img from post #1
- flashed firmware from post #1
- reboot and stuck at Asus-logo
I can still reboot into the recovery.
Where did I go wrong?
Just flash the last cm11 with f2fs support to get the tablet working. No need to change recovery.
suhiSLO said:
Just flash the last cm11 with f2fs support to get the tablet working. No need to change recovery.
Click to expand...
Click to collapse
thx reply,
i listed the step as below. am i right?
1)download recovery_f2fs on cm11 section
2)use the code format mmcblk
mkfs.f2fs -t 0 /dev/block/mmcblk0p2
mkfs.f2fs -t 0 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
3)install cm12
4)reboot
if i were wrong,may i know the step and compatible recovery download link?
suhiSLO said:
Just flash the last cm11 with f2fs support to get the tablet working. No need to change recovery.
Click to expand...
Click to collapse
Why should I flash CM11 (KitKat) when I want CM12 (Lollipop, that this thread is about)?
I used the software (recovery, firmware) that Namidairo posted in his first post in this thread.
GoldenAvatar said:
Why should I flash CM11 (KitKat) when I want CM12 (Lollipop, that this thread is about)?
I used the software (recovery, firmware) that Namidairo posted in his first post in this thread.
Click to expand...
Click to collapse
Just to make the tablet working until namidairo offers a solution. At least that's what I did.
---------- Post added at 04:41 PM ---------- Previous post was at 04:34 PM ----------
atoyu said:
thx reply,
i listed the step as below. am i right?
1)download recovery_f2fs on cm11 section
2)use the code format mmcblk
3)install cm12
4)reboot
if i were wrong,may i know the step and compatible recovery download link?
Click to expand...
Click to collapse
If you want to try to make cm12 work use the recovery from this topic. I replied to goldenavatars post.
when using recovery on this topic, it hold on asus boot screen......
any md5 for this file?
Did the install using TWRP 2.7.0.0 and also flashed the gapps-lp, On reboot screen stuck at the Asus logo and will not proceed. Is there a md5 available for the ROM zip file so I can do a check?
I am currently running namidairo's CM11 build on my TF201. Do I just flash the recovery and then this image to get lollipop?
Also was GAPPS work with this build?
Thanks.
Oops, SELinux chucks a fit about some of the vendor libs when I set it to enforcing.
This is why you actually test with the same kernel that you are deploying. (Reboot shenanigans meant the bootloader ignored my staging partition and didn't flash the new kernel, yay.)
Anyway, I'll pull the zip and upload one with it set to permissive for now (Which is a temporary fix, I'll fix up the sepolicies when I have time)
Edit: Up
Working. Thank you.
Namidairo said:
Oops, SELinux chucks a fit about some of the vendor libs when I set it to enforcing.
This is why you actually test with the same kernel that you are deploying. (Reboot shenanigans meant the bootloader ignored my staging partition and didn't flash the new kernel, yay.)
Anyway, I'll pull the zip and upload one with it set to permissive for now (Which is a temporary fix, I'll fix up the sepolicies when I have time)
Edit: Up
Click to expand...
Click to collapse
Can't wait to try this later tonight
Yup, same.
Missing superSU. So additional apk install needed. I tried to install zip version but it looks like it didn't stick.
suhiSLO said:
Missing superSU. So additional apk install needed. I tried to install zip version but it looks like it didn't stick.
Click to expand...
Click to collapse
Did you enable root in developer options?
Related
TWRP 3. for Xperia Z Ultra aka togari
Up-to-date TWRP with new looks and functional display/brightness settings, and mountpoints like in sony-aosp marshmallow.
Code:
#include <std_disclaimer.h>
/*
* 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
* 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.
*/
Download: AndroidFileHost
Sources: Github
Make sure you have installed the new bootloader and have flashed the latest stock Sony ROM at least once since.
Then, erase the recovery partition and flash TWRP using fastboot.
Code:
fastboot erase recovery
fastboot flash recovery twrp-3.0.0-togari.img
Enter recovery:
Switch off the phone
Hold Vol-Down & Power button simultaneously until the phone vibrates
Release the power button and keep holding Vol-Down until the Sony logo appears
Thanks to @Dees_Troy for twrp
Thanks to Sony AOSP for basic device trees
XDA:DevDB Information
TWRP 3.0.0, Tool/Utility for the Sony Xperia Z Ultra
Contributors
alia5
Source Code: https://github.com/omnirom/android_bootable_recovery/tree/android-6.0
Version Information
Status: Snapshot
Created 2016-02-13
Last Updated 2016-02-13
C6806
Device goes into reboot loop when trying to enter. Need instructions on how to capture logcat as ADB LOGCAT cannot find device until OS or recovery is loaded.
I'm guessing you also don't have a recovery.log anywhere on your phone?
Anyway I had some problems by just applying the TA-update with EMMA with some custom-roms, by flashing the newest stock version that whole song and dance got solved (C6833)
But as you stated in some other thread, just applying the TA update doesn't work for you on the C6806, and you already have had flashed the newest stock fw, so...
I guess I'm going to ask some people and see...
BTW: what happens if you "fastboot boot PATH_NAME_OF_RECOVERY.img" ?
AFAIK the C6806 is the Google Play Edition - that has a completely different boot method. Don't try this on the GPe.
Why has this thread been opened? We already have a TWRP 3 thread here.
In previous versions it was possible to reboot into recovery from rom. cm12.1 in my case. with yours and the others in the forum it results into bootloop. only way to enter recovery is to hold power+volume down.
TimeTurn said:
AFAIK the C6806 is the Google Play Edition - that has a completely different boot method. Don't try this on the GPe.
Click to expand...
Click to collapse
There also is a non-GPE C6806 (afaik) and I'm guessing @pTeronaut would've said if he has a GPE, if he has, well... then why does he even try since this is not the gpe section
TimeTurn said:
Why has this thread been opened? We already have a TWRP 3 thread here.
Click to expand...
Click to collapse
The other TWRP 3 has a missing symlink in the init.rc script, which causes problems when trying to flash marshmallow roms
jimmkind said:
In previous versions it was possible to reboot into recovery from rom. cm12.1 in my case. with yours and the others in the forum it results into bootloop. only way to enter recovery is to hold power+volume down.
Click to expand...
Click to collapse
That's because the most roms (all of them available here?) don't support booting to recovery on the separate recovery partition. The roms need to have a patch in order to be able to boot to recovery on separate recovery partition.
When the marshmallow roms finally arrive (aka. ready to be shared in public) this will no longer be a problem
TimeTurn said:
AFAIK the C6806 is the Google Play Edition - that has a completely different boot method. Don't try this on the GPe.
Why has this thread been opened? We already have a TWRP 3 thread here.
Click to expand...
Click to collapse
You know incorrectly, The GPE is based on the original North American LTE version of the Xperia Z Ultra C6806, the only difference being the storage's partitioning, 'Xperia' being removed from the device's branding and '_gpe' being tagged onto the model code.
alia5 said:
There also is a non-GPE C6806 (afaik) and I'm guessing @pTeronaut would've said if he has a GPE, if he has, well... then why does he even try since this is not the gpe section
The other TWRP 3 has a missing symlink in the init.rc script, which causes problems when trying to flash marshmallow roms
That's because the most roms (all of them available here?) don't support booting to recovery on the separate recovery partition. The roms need to have a patch in order to be able to boot to recovery on separate recovery partition.
When the marshmallow roms finally arrive (aka. ready to be shared in public) this will no longer be a problem
Click to expand...
Click to collapse
the recovery by Saatvik Shukla had this function working. the version of that recovery was 2.8.7.0.
alia5 said:
I'm guessing you also don't have a recovery.log anywhere on your phone?
Anyway I had some problems by just applying the TA-update with EMMA with some custom-roms, by flashing the newest stock version that whole song and dance got solved (C6833)
But as you stated in some other thread, just applying the TA update doesn't work for you on the C6806, and you already have had flashed the newest stock fw, so...
I guess I'm going to ask some people and see...
BTW: what happens if you "fastboot boot PATH_NAME_OF_RECOVERY.img" ?
Click to expand...
Click to collapse
The recovery boots.
I'm beginning to think that the C6806 never got the recovery partition, and that Saatvik Shukla (who's TWRP works) & championswimmer (whose CWM works) have done something strange to get theirs working.
No recovery.log.
Please search before creating a new thread
http://forum.xda-developers.com/xperia-z-ultra/development/twrp-recovery-2-8-7-0-2016-02-03-t3307043
If you feel this thread is fundamentally different to the existing thread please PM me with the differences and I will re-open
Greg
No longer supported
Unofficial TWRP 3.1.1 w/F2FS
> For the Nexus 6 Shamu
This work is inspired by @The Flash's F2FS TWRP builds. I based this build off of the TWRP Minimal Repo.Features:
TWRP 3.1.1
F2FS Mounting and Formatting supported (En/Decryption not supported, however)
Built atop my kernel
Works
Changelog:
3.1.1-3
Updated sources to 7.1.2_r33, which includes updated f2fs-tools (1.8.0)
Minor GUI tweaks (splash screen, odd gap under "Advanced")
Bump to subversion 3
Installation:
You should know the drill of installing custom recoveries if you found this thread, but anyways:
Have an UNLOCKED Bootloader
Boot to fastboot/bootloader mode (Power + Vol Down from power off)
In adb (replace X with appropriate subversion):
Code:
fastboot flash recovery twrp-3.1.1_X-f2fs-unofficial-shamu.img
You can now reboot to your shiny, new TWRP!
How Do I convert to F2FS?
Backup important data to an EXTERNAL source; if formatting /data, entire internal sd will be wiped.
Ensure your kernel/kernel you will flash supports F2FS. You can use my kernel if you desire.
Reboot to this (or any other) F2FS supported TWRP
Go to -> Wipe -> Advanced Wipe
Tick the desired partition you want to format (ONLY do /data and/or /cache)
Select "Repair or Change Filesystem"
Select "Change File System"
Select "F2FS"
Swipe to Change
Done. Flash all your stuff!
Disclaimer:
I am not responsible for broken devices etc... Flash at your own risk. I am also not affiliated with the official TWRP crew nor Omni ROMs, so please don't complain to them about bugs unique to my own builds.
Sources:
Manifest
TWRP Recovery
Device Tree
Kernel
XDA:DevDB Information
Unofficial TWRP for Shamu w/F2FS, Tool/Utility for the Nexus 6
Contributors
Black_Hat01, Omni Rom, and the great devs of TWRP itself
Source Code: https://github.com/BlackHat01/
Version Information
Status: No Longer Updated
Current Stable Version: 3.1.1-3
Stable Release Date: 2017-09-26
Created 2017-06-27
Last Updated 2018-02-10
Downloads
Download Latest 09/26 Build - 3.1.1-3
How do i make it keep my settings. Every time i boot into twrp i have to swipe to allow modifications and need to set settings again. Also it does not see my backups i made with previous twrp 3.1.1-0
Thanks a lot for this. Does it properly decrypt F2FS data?
Neejay said:
Thanks a lot for this. Does it properly decrypt F2FS data?
Click to expand...
Click to collapse
I don't use encryption so I cannot say. If you can test it for me that would be appreciated
UPDATE:
TWRP Official 3.1.0 changelog states TWRP will try to mount both ext4 and f2fs on decrypt, so It should work.
TMG1961 said:
How do i make it keep my settings. Every time i boot into twrp i have to swipe to allow modifications and need to set settings again. Also it does not see my backups i made with previous twrp 3.1.1-0
Click to expand...
Click to collapse
It should not reset your settings every time you boot into recovery, unless there is something wrong with your /sdcard/TWRP folder. Can you send a recovery log (Advanced > Copy Log)?
Will do that after finishing the install of the rom i am doing now.
TMG1961 said:
Will do that after finishing the install of the rom i am doing now.
Click to expand...
Click to collapse
Thank you. I ask because I am not having that issue at all. Maybe also try re-flashing recovery via fastboot before everything too.
what i did was this. Booted into bootloader. erased recovery, flashd your recovery and booted into it. wiped to allow changes and made changges to settings. Then booted back into rom. The rom i tried it with was stock 7.1.1.
I just finished installing velocity rom and flashed your twrp, same result. I did copy the log. said in twrp that it was copied to /data/media/recovery.log but the log is no were to be found on the phone. Did search the whole phone with root explorer
---------- Post added at 20:00 ---------- Previous post was at 19:59 ----------
when i try to do a backup i get error unable to mount storage
---------- Post added at 20:10 ---------- Previous post was at 20:00 ----------
I think the problem is something else. Not sure but twrp does not see my storage
Black_Hat01 said:
I don't use encryption so I cannot say. If you can test it for me that would be appreciated
UPDATE:
TWRP Official 3.1.0 changelog states TWRP will try to mount both ext4 and f2fs on decrypt, so It should work.
Click to expand...
Click to collapse
Unfortunately, it doesn't work. It doesn't recognize my unlock pattern and won't decrypt. I had to go back to xanaxdroid's 3.0.2.0 twrp for it to work
I did flash the previous twrp and copied the log file. Not sure if that contains what you need ut adding it so you can have a look
Neejay said:
Unfortunately, it doesn't work. It doesn't recognize my unlock pattern and won't decrypt. I had to go back to xanaxdroid's 3.0.2.0 twrp for it to work
Click to expand...
Click to collapse
Thanks for the update. Will look into it.
Black_Hat01 said:
Thanks for the update. Will look into it.
Click to expand...
Click to collapse
No problem. I tried to look for his source, but couldn't find one for shamu directly. Here's where I downloaded his img (if it helps at all): https://forum.xda-developers.com/showpost.php?p=70452221&postcount=29
TMG1961 said:
I did flash the previous twrp and copied the log file. Not sure if that contains what you need ut adding it so you can have a look
Click to expand...
Click to collapse
Can you flash my twrp and send log please? It is the correct log. I just need to see what's going on with mine. Thanks.
i can but after flashing your twrp then flash the old one again and copy the log to the sdcard ? Cause yours says it copies the log but there is no log on the sdcard.
TMG1961 said:
i can but after flashing your twrp then flash the old one again and copy the log to the sdcard ? Cause yours says it copies the log but there is no log on the sdcard.
Click to expand...
Click to collapse
That's odd. I was on Flash's 3.1.0-4 F2FS build and flashed mine right over that build and everything works fine for me (log copying works, settings stick fine, etc..), so maybe try flashing his build, then mine. Without a log, I can't really do much, since I, and nobody else yet has experienced the same issues. I'm going to do some work on it today, and I'll try to get a new build out tonight.
Thanks for your time and help. I downloaded 3.1.0-4 F2FS and 3.1.1-6 F2FS but on both the same. All version dont show anything on the sdcard when i go to advanced/file manager in twrp. So no idea what is causing it but almost sure the problem is on my side.
TMG1961 said:
Thanks for your time and help. I downloaded 3.1.0-4 F2FS and 3.1.1-6 F2FS but on both the same. All version dont show anything on the sdcard when i go to advanced/file manager in twrp. So no idea what is causing it but almost sure the problem is on my side.
Click to expand...
Click to collapse
Perhaps it is just your device. Anyways, I uploaded a new build, maybe try this one out. If it does not, try reflashing stock twrp 3.1.1 and then coming back to an F2FS modified one. Hope the best.
Is there any difference between this and the TWRP F2FS builds found at http://nchancellor.net/Downloads/TWRP/shamu/ ?
TMG1961 said:
...I just finished installing velocity rom
Click to expand...
Click to collapse
I thought that ROM ceased development a long time ago? Happen to have any links with more info on it? https://www.android-port.de/themen/rom-n-7-1-1-velocity-shamu.9596/
espionage724 said:
Is there any difference between this and the TWRP F2FS builds found at http://nchancellor.net/Downloads/TWRP/shamu/ ?
Click to expand...
Click to collapse
Thing is, by the time I posted, I hadn't realized he updated his. But the things that are different are basically the kernel the recovery image is built with (we use our own kernels), and the support. I will be actively building and supporting while The Flash has pretty much moved on from shamu to angler. Any bugs that arise I will try to fix and I will always be trying to keep everything updated. Over time our builds will start to become more and more different.
SonyAOSP builds by @davidteri91 (This ROM has included GAPPS)
Code:
Code:
#include "std_disclaimer.h"
/*
* 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.
*/
What's working :
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Camera
Audio
GPS
What's not working :
Wi-Fi HotSpot 5Ghz
Miracast
Random reboots
Maybe more...
Report all found bugs to the sony bugtracker: https://github.com/sonyxperiadev/bug_tracker/issues
Steps for Flash:
fastboot flash oem xxxxx.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase userdata (if needed or you on stock)
Downloads :
ROM: https://androidfilehost.com/?w=files&flid=286595&sort_by=date&sort_dir=DESC
OEM: https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-loire/
TWRP: https://eu.dl.twrp.me/suzu/
Warning! From april build for dual sim use new patch from 2019.04.23. in attachment.
Sources:
SonyXperiaDev: https://github.com/sonyxperiadev?tab=repositories
SonyAOSP: https://github.com/SonyAosp
Contributors:
@davidteri91
ROM OS Version: 9
ROM Kernel: Linux 4.9.x
ROM Firmware Required: 34.4.A.2.118
Created: 2019-03-24
Last Updated: 2019-04-23
Successfully installed the ROM (the only Pie ROM for F5122 here I can flash that has GApps, plus the installation process is quite easy).
- Wi-Fi 5Ghz works for me.
- "There's an internal problem with your device. Contact your manufacturer for details" pops up after boot (probably due to the kernel, which is kinda annoying).
- There seems to be something wrong with TWRP 3.2.3-0 on this ROM. I could install and use it once, but after reboot it just disappeared.
- ...
Still testing. Thanks for the work!
can a step by step guide/process for noobs be povided here?
I am on stock unrooted 8.0 Oreo
prasad12ka4 said:
can a step by step guide/process for noobs be povided here?
I am on stock unrooted 8.0 Oreo
Click to expand...
Click to collapse
- Download everything in the links above (ROM, TWRP and OEM)
- Extract ROM, OEM to "platform-tools" (your adb folder)
- Shift click "platform-tools", open as cmd
- Enable USB-debug on your phone
In cmd:
adb devices
adb reboot bootloader
fastboot flash oem "oem.img"
fastboot flash boot "boot.img"
fastboot flash system "system.img"
fastboot erase userdata
--> Reboot, done. After boot, flash recovery TWRP if you want. That's what I did for this ROM.
P/s: I flashed stock Oreo with Emma before flashing this ROM.
LOLisLIFE said:
Successfully installed the ROM (the only Pie ROM for F5122 here I can flash that has GApps, plus the installation process is quite easy).
- Wi-Fi 5Ghz works for me.
- "There's an internal problem with your device. Contact your manufacturer for details" pops up after boot (probably due to the kernel, which is kinda annoying).
- There seems to be something wrong with TWRP 3.2.3-0 on this ROM. I could install and use it once, but after reboot it just disappeared.
- ...
Still testing. Thanks for the work!
Click to expand...
Click to collapse
Can I flash magisk?
I used this ROM some time ago, that build overheated a lot, and had some reboots, I couldn't get root in any possible way
Maybe this version is rootable
realthrash said:
I used this ROM some time ago, that build overheated a lot, and had some reboots, I couldn't get root in any possible way
Maybe this version is rootable
Click to expand...
Click to collapse
All versions of SonyAOSP build can have root with Magisk 18+
lookmanns14 said:
Can I flash magisk?
Click to expand...
Click to collapse
of course
Jurn_Software said:
All versions of SonyAOSP build can have root with Magisk 18+
Click to expand...
Click to collapse
I need to boot up to system, then reboot to TWRP and root, but since this ROM deletes the Recovery it's a little bit complicated
realthrash said:
I need to boot up to system, then reboot to TWRP and root, but since this ROM deletes the Recovery it's a little bit complicated
Click to expand...
Click to collapse
donwload and reflash twrp 3.2.3-2 recovery via adb
Is possible to add dual sim via build,prop?
khriiza said:
Is possible to add dual sim via build,prop?
Click to expand...
Click to collapse
yes, with this patch
Security patch March, April to be?
[email protected] said:
Security patch March, April to be?
Click to expand...
Click to collapse
April security patch are coming in few days, stay tuned
Jurn_Software said:
April security patch are coming in few days, stay tuned
Click to expand...
Click to collapse
Can you make an optimized kernel for this ROM?
LOLisLIFE said:
Can you make an optimized kernel for this ROM?
Click to expand...
Click to collapse
I'm not a developer. Kernel provided by sonyxperiadev developers.
P.S. due to problems related to WiFi in tone platform ... New releases are delayed to next week ...
April security patch released!!!
https://androidfilehost.com/?fid=1395089523397948583
Jurn_Software said:
April security patch released!!!
https://androidfilehost.com/?fid=1395089523397948583
Click to expand...
Click to collapse
For install this ROM we need a unlocked bootloader right, random reboot is fixed in new build and can I install this ROM if I from AOSPA Pie beta ?
Mashrmallow said:
For install this ROM we need a unlocked bootloader right, random reboot is fixed in new build and can I install this ROM if I from AOSPA Pie beta ?
Click to expand...
Click to collapse
no, random reboots not fixed. I have two the last day
Mashrmallow said:
For install this ROM we need a unlocked bootloader right, random reboot is fixed in new build and can I install this ROM if I from AOSPA Pie beta ?
Click to expand...
Click to collapse
Are the random reboots as bad as AOSPA pie?
I heard people saying it's Quickstep (the recent apps UI) that caused the crashes. Maybe try using a non-quickstep launcher (eg. Nova) and report back?
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Flash Indian Stock .ozip roms works
- Flash Roms works
- Mtp works
- Backup works
- .ozip flash
- Android 10 Support
- Android 11 Decryption
Download:
TWRP 3.4.0-10 Unofficial by mauronofrio
TWRP 3.4.0-0 Unofficial by mauronofrio
TWRP 3.3.1-13 Unofficial by mauronofrio
TWRP 3.3.1-12 Unofficial by mauronofrio
TWRP 3.3.1-11 Unofficial by mauronofrio
TWRP 3.3.1-7 Unofficial by mauronofrio
TWRP Official Builds
TWRP 3.3.1-1 Unofficial by mauronofrio
TWRP 3.3.1-0 Unofficial by mauronofrio
To Flash the TWRP:
if it's the first time you flash the TWRP or you are getting problems of TWRP lost or device doesn't boot after flashed magisk or something else you need to flash a script to patch your vbmeta:
VBMETA PATCHER
To flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually.
Flash the VBMETA PATCHER and reboot.
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_realme_RMX1931
Precompiled stock one
Donations:
Credits:
Thanks to @Jerry08 for the testing
Created 2019-11-5
This is not tested, i have not the stock recovery, so before flash directly it, please try to only boot this twrp using:
fastboot boot twrp.img command
Here we go! If this works, this will be my new phone
This is exactly what I was hoping to see, just picked up this phone and can't wait to be rid of ColorOS. Is there a solution available to flash Android 10 on this device? I'd be happy to commit a donation for getting Android 10 working smoothly on this device with full camera support.
hanakon said:
This is exactly what I was hoping to see, just picked up this phone and can't wait to be rid of ColorOS. Is there a solution available to flash Android 10 on this device? I'd be happy to commit a donation for getting Android 10 working smoothly on this device with full camera support.
Click to expand...
Click to collapse
Would also love stock Android or oxygenOS. Full camera support while keeping the super macro mode. I'm not sure if that's a feature on other phones but really like it. At 50% battery as I type this with almost 9 hours of use and lil over 4 hours on on screen time. Best battery life I've had in a phone and to top it off or charges incredibly fast.
Did anyone test this? If twrp works, then it will not be far from getting a few custom roms for this device. I really hope this works since if it does, I'm buying this phone immediately!
How to unlock bootloader? , i haven't found anything about boot loader unlock for realme X2 pro yet. We can't flash twrp with locked bootloader right?
Try this?: https://realmeroot.com/how-to-unlock-the-boatloader-in-realme-x2-pro/.
kaminsky.victor said:
Try this?: https://realmeroot.com/how-to-unlock-the-boatloader-in-realme-x2-pro/.
Click to expand...
Click to collapse
Not working , cannot install that app
Is this TWRP working on Realme X2 (RMX1991)?
ospeto said:
Not working , cannot install that app
Click to expand...
Click to collapse
Yet i did get the phone....
But...
There is an option on developers menue which i guess it should be toggled: link is below...
https://www.hardreset.info/devices/realme/realme-x2-pro/developer-options/
---------- Post added at 11:42 PM ---------- Previous post was at 11:39 PM ----------
shamllakh said:
Yet i did get the phone....
But...
There is an option on developers menue which i guess it should be toggled: link is below...
https://www.hardreset.info/devices/realme/realme-x2-pro/developer-options/
Click to expand...
Click to collapse
Also, i found this on RealmeX2Pro china forum:
https://www.realmebbs.com/post-deta...06252043546624&subForumId=1181409566403866624
shamllakh said:
Yet i did get the phone....
But...
There is an option on developers menue which i guess it should be toggled: link is below...
https://www.hardreset.info/devices/realme/realme-x2-pro/developer-options/
---------- Post added at 11:42 PM ---------- Previous post was at 11:39 PM ----------
Also, i found this on RealmeX2Pro china forum:
https://www.realmebbs.com/post-deta...06252043546624&subForumId=1181409566403866624
Click to expand...
Click to collapse
One guy on RealmeX2Pro china forum reported A Success Bootloader Unlock, here is his method link:
https://www.realmebbs.com/post-deta...06252043546624&subForumId=1181409566403866624
shamllakh said:
One guy on RealmeX2Pro china forum reported A Success Bootloader Unlock, here is his method link:
https://www.realmebbs.com/post-deta...06252043546624&subForumId=1181409566403866624
Click to expand...
Click to collapse
That's great , but I'll just wait for xda 's method to be sure. I hop we can get custom ROMs soon. Ported oxygen os or AEX would be great. That Color OS is not good. I am experiencing some notification and permission bugs now.
Just tried, and the phone won't go in bootloader mode. The 'adb reboot bootloader' do nothing :/
Thanks @nathan30 for testing!
I downloaded the package from that chinese website which was linked by @ospeto
I translated the folders inside the zip with google to english, since many people have issues with chinese characters in their file structure but in case anyone needs the original files, I kept the chinese zip as well.
Download English zip:
http://www.mediafire.com/file/qdkqs577zskml9k/realme_X2_pro_Eng.zip/file
Download Chinese zip:
http://www.mediafire.com/file/yrlhze0l5ahzd7n/realme_X2_pro_Ch.zip/file
If anyone can test this, please report back.
Thank you guys!
EDIT: There is a google translated bootloader unlocking guide in the zip.
SethPDA said:
Thanks @nathan30 for testing!
I downloaded the package from that chinese website which was linked by @ospeto
I translated the folders inside the zip with google to english, since many people have issues with chinese characters in their file structure but in case anyone needs the original files, I kept the chinese zip as well.
Download English zip:
http://www.mediafire.com/file/qdkqs577zskml9k/realme_X2_pro_Eng.zip/file
Download Chinese zip:
http://www.mediafire.com/file/yrlhze0l5ahzd7n/realme_X2_pro_Ch.zip/file
If anyone can test this, please report back.
Thank you guys!
EDIT: There is a google translated bootloader unlocking guide in the zip.
Click to expand...
Click to collapse
I could try but have you and idea about the phone which don't boot in bootloader mode ?
Is this TWRP working on Realme X2 (RMX1991)?
MTsv DN said:
Is this TWRP working on Realme X2 (RMX1991)?
Click to expand...
Click to collapse
Definitely not, don't you see this is for the Pro?
MTsv DN said:
Is this TWRP working on Realme X2 (RMX1991)?
Click to expand...
Click to collapse
I don't think it will work, maybe i can make a dedicated version
mauronofrio said:
This is not tested, i have not the stock recovery, so before flash directly it, please try to only boot this twrp using:
fastboot boot twrp.img command
Click to expand...
Click to collapse
Do you think you will get the stock recovery to test your Twrp ?
TWRP FOR THE A52 5G! (With issues)
Help needed!
Are you someone that has ported TWRP before without any issues?
Or are you someone that knows how to fix any problem that has been listed in the 'Additional Notes' section?
PM me. We can work together to fix the issue(s)
Note
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 doing this to your device
* 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.
Additional Notes
Code:
THIS RECOVERY IS NOT FULLY TESTED!
There are atleast these issues:
1. MTP Does NOT work. (Not with computer or with OTG)
2. NO access to your SD cards
3. Incorrect resolution (TWRP is 1080x1920, phone is 1080x2400)
4. Temperature sensor doesn't work.
THERE MIGHT BE MORE ISSUES I DO NOT KNOW OF! FLASH AT YOUR OWN RISK.
How to install?
First of all you need an unlocked BL. This is extremely easy to do and there are a lot of guide online.
Download recovery.tar (TWRP) from this post.
Select the AP slot in Odin
Disable auto reboot in Odin
Flash
Credits
TeamWin Recovery Project
Source code:
Minimal TWRP AOSP: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp
Device Tree for the a52 5g: Can't upload because of 25mb+ kernel file. Will make a custom kernel soon
Thank you so much for your work on TWRP. Waited for it a year
GiulianoB said:
Thank you so much for your work on TWRP. Waited for it a year
Click to expand...
Click to collapse
No problem.
Hi,
Firstly, thanks for doing this!
Secondly, I've been trying to flash a zip (BluetoothLibraryPatcher) but I cannot find a way to get TWRP to read a zip file. Things I've tried:
From the device itself: The data partition is encrypted. twrp decrypt (in the TWRP terminal) says "No crypto support was compiled into this build".
From ADB Sideload: It gets stuck on "Starting ADB sideload feature..." for 5 minutes, then fails.
From MTP/USB OTG: As you say in your post, neither MTP from PC nor from a USB flash drive works.
Would you have any idea of how I can get TWRP to read a zip file to install?
Thanks!
ByteSizedBit said:
Hi,
Firstly, thanks for doing this!
Secondly, I've been trying to flash a zip (BluetoothLibraryPatcher) but I cannot find a way to get TWRP to read a zip file. Things I've tried:
From the device itself: The data partition is encrypted. twrp decrypt (in the TWRP terminal) says "No crypto support was compiled into this build".
From ADB Sideload: It gets stuck on "Starting ADB sideload feature..." for 5 minutes, then fails.
From MTP/USB OTG: As you say in your post, neither MTP from PC nor from a USB flash drive works.
Would you have any idea of how I can get TWRP to read a zip file to install?
Thanks!
Click to expand...
Click to collapse
Hey, you can use commands by just being on the home screen of TWRP. ADB push <file location and name> /sdcard
ByteSizedBit said:
Hi,
Firstly, thanks for doing this!
Secondly, I've been trying to flash a zip (BluetoothLibraryPatcher) but I cannot find a way to get TWRP to read a zip file. Things I've tried:
From the device itself: The data partition is encrypted. twrp decrypt (in the TWRP terminal) says "No crypto support was compiled into this build".
From ADB Sideload: It gets stuck on "Starting ADB sideload feature..." for 5 minutes, then fails.
From MTP/USB OTG: As you say in your post, neither MTP from PC nor from a USB flash drive works.
Would you have any idea of how I can get TWRP to read a zip file to install?
Thanks!
Click to expand...
Click to collapse
Btw, afaik the encryption problem isn't something I can remove.
This is fantastic to see! Nice work.
Have you tried any custom ROMs with this? Do any of the current custom ROMs (like Lineage OS) support A52 5G, or are we still a far way away from that?
biscuitpants said:
This is fantastic to see! Nice work.
Have you tried any custom ROMs with this? Do any of the current custom ROMs (like Lineage OS) support A52 5G, or are we still a far way away from that?
Click to expand...
Click to collapse
Hey. I've not started a custom ROM yet. I've been busy with school mostly. I will probably start developing Lineage OS as the first custom rom.
Things405 said:
Hey. I've not started a custom ROM yet. I've been busy with school mostly. I will probably start developing Lineage OS as the first custom rom.
Click to expand...
Click to collapse
Good luck and thanks again for your effort
Hey! I found this on GitHub and I was wondering if it's you. Your post is still saying "Will upload in a minute". Thanks!
MeowNyaaa said:
Hey! I found this on GitHub and I was wondering if it's you. Your post is still saying "Will upload in a minute". Thanks!
Click to expand...
Click to collapse
Yep thats me. I can't upload a kernel file on github as its 25mb+ So the device tree won't be complete without it. I'll change the post.
Things405 said:
Yep thats me. I can't upload a kernel file on github as its 25mb+ So the device tree won't be complete without it. I'll change the post.
Click to expand...
Click to collapse
I recommend using Git LFS for that, more info about it here: https://git-lfs.github.com/
I created a device tree myself long time ago as well, was just missing the kernel
I may sell my U1 for the Dual Sim model so I can root. I need parts of this lol
Any progress?
I just can't wait for LineageOS
@Things405 I have GitHub pro if you want someone to host the device tree on there... I'm on https://github.com/SImPilotAdamT/
Also by A52 5G do you mean the A526B?
Also for some reason I can't unlock the bootloader in my device... I have the A526B international model. https://forum.xda-developers.com/t/unable-to-unlock-the-bootloader-a52-5g-sm-a526b.4476861/
TWRP 3.7.0 is out with the support for decryption on Android 12 to be able to backup firmware. Pls update, thx
I'm sorry to have left you guys hanging! I've been too busy with personal stuff but I will get back on this as soon as possible.
flashed in A526BXXU1AUAH, when press buttons for recovery, it freeze on boot logo
does this also work for the a52s 5g version?
LuzzyKins said:
does this also work for the a52s 5g version?
Click to expand...
Click to collapse
No, the version you should be looking at is: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-2-for-galaxy-a52s-5g.4488419/