First of all thanks to @invaderjohn for the kernel of the d620, @Quarx for his work with the L90 and @powermetza for his recovery, and @nch26 for testing what i did
HTML:
/*
* 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.
*/
Don't use it if you did not unlock your bootloader! You can do this in this thread!
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
DOWNLOAD: https://www.androidfilehost.com/?fid=95916177934528202
Installation:
**Requires unlocked bootloader and root**
1. Make a backup of the original recovery (just in case)
2. Flash the attached images below via Flashify, or adb.
3. Restart and have fun!
Please report any issues you have.
XDA:DevDB Information
TWRP 2.8.4.0 for G2 Mini D610, Tool/Utility for the LG G2 Mini
CM12 coming soon for d610!
Version Information
Status: Stable
REserved
What's the difference between Zaaap72's version and Yours?
EDIT: Oh, I see. It's for D610 hardware, my bad...
Wysłane z mojego LG-D620
Bootloader Unlocked
My device "d610turkey" How can I remove the bootloader unlock?
New version of a fully working TWRP, soon, cm12 is coming!
Two questions
How do I know if my bootloader is unlocked ?
And how to flash it?
Thanks in advance
Sadithgreenleaf said:
Two questions
How do I know if my bootloader is unlocked ?
And how to flash it?
Thanks in advance
Click to expand...
Click to collapse
After doing the process of unlocking, which is the same as d620, you gotta flash my recovery via Flashify
Flash the recovery, if the unlocking was successful you will be able to enter to twrp, if the bootloader is still locked, you will get a pink screen of lg watchdog, if the second happend, you only have to pull out battery an re power normal your phone and try again to unlock boot or restore original recovery
Good news for d610 ( all variants of d610) kernels for d618 are fully compatible with our devices, also cm12 for d618 (in cm12 zip we have to edit a file to avoid error installing.
Also After installation should have to edit this string
Code:
persist.multisim.config=dsds
To this
Code:
persist.multisim.config=none
This will disable dualsim support and enable sim recognizing
sergioslk said:
Flash the recovery, if the unlocking was successful you will be able to enter to twrp, if the bootloader is still locked, you will get a pink screen of lg watchdog, if the second happend, you only have to pull out battery an re power normal your phone and try again to unlock boot or restore original recovery
Good news for d610 ( all variants of d610) kernels for d618 are fully compatible with our devices, also cm12 for d618 (in cm12 zip we have to edit a file to avoid error installing.
Also After installation should have to edit this string
Code:
persist.multisim.config=dsds
To this
Code:
persist.multisim.config=none
This will disable dualsim support and enable sim recognizing
Click to expand...
Click to collapse
Just that and works?
exactly, remember to delete first line in updater-script, first line will prevent installation on any device that don't match d618 model
Related
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?
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
(PM me if i made a typo)
Procedure :
Step 1 : Update to the latest software update
Step 2 : Unlock bootloader ( c.realme.com/in/post-details/1110451594350034944)
Step 3: install Magisk Manager (magiskmanager. com)
Step 4: Flash Modded Boot.img (Using Fastboot)
Code:
fastboot flash boot boot.img
To boot into Bootloder to use Fastboot
Code:
adb reboot-bootloader
Software vertion Required: RMX1831EX_11_C.16 (Release date: 11/12/2019)
Download : mega.nz/#!ZchUEQCR!-6k1AIHIyK-oIeec3BOgsXMK4PT18qnrDycM4zyKkFA
FAQ
Dose this Work?
Ans: Yes. (i own this devise and worked for me)
Will this get Updates?
Ans: Yes. Depending on feedback i might stop
Why did i post a method for rooting this devise when their are 4 other threads doing the same?
Ans: because all those other methods did not work for me.(if they do pm me i will DELETE this thread)
PM me if you have any problems or need help or if i posted it in the wrong thread (I couldn't find my devise thread)
Thx if someone could make one
DONT USE
Method 2Bootless Root Method (MTK-SU)) (No longer works (causes kernel panic after the latest update))
Advantage : you don't need 2 unlock ur devise
Credits :
magiskmanager and realme
Status : Stable
Disclamer (just for courtesy) I will help u if anything hapens
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* 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.
* Your warranty will be void if you tamper with any part of your device / software. (realme devises will not lose thare warranty )
I have also successfully rooted Realme Q2 UI1.0 android 10, but when Q2 updated UI2.0 android 11, rooting using that old method failed. So please ask if there is a way to achieve the goal of rooting Realme Q2 UI2.0 android 11 with good results? Thank you!
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.
*
*/
BUG :
OTG
Lemme know
Install guide:
Boot :
Code:
fastboot boot <twrp.img>
Download: here
Contributors
imjyotiraditya
Thx to jjjhitel for his EROFS patch
Source Code: https://github.com/TeamWin/android_bootable_recovery
https://github.com/imjyotiraditya/device_xiaomi_odin-twrp
thanks and reserved
thanks and reserved
treid it this morning, and it looks and feels great so far.. no errors.
Would it be possible for somebody to post a guide for this, never installed it before?
jrvenge said:
Would it be possible for somebody to post a guide for this, never installed it before?
Click to expand...
Click to collapse
I'm not entirely sure what you mean tbh. Would you mind to explain?
imjyotiraditya said:
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.
*
*/
BUG :
OTG
Lemme know
Install guide:
Boot :
Code:
fastboot boot <twrp.img>
Download: here
Contributors
imjyotiraditya
Thx to jjjhitel for his EROFS patch
Source Code: https://github.com/TeamWin/android_bootable_recovery
https://github.com/imjyotiraditya/device_xiaomi_odin-twrp
Click to expand...
Click to collapse
Hey, i wanted to report a bug...
After i installed twrp permanently by advanced settings, i lost the touchscreen, after i rebooted into recovery.
SanHelios said:
Hey, i wanted to report a bug...
After i installed twrp permanently by advanced settings, i lost the touchscreen, after i rebooted into recovery.
Click to expand...
Click to collapse
how did u recover sir ? flashed original boot.img?
jrvenge said:
Would it be possible for somebody to post a guide for this, never installed it before?
Click to expand...
Click to collapse
as of now, no use of flashing twrp as there are no proper custom rom, but inorder to put this ur phone should be unlocked, to do that follow this guide https://forum.xda-developers.com/t/...to-eu-rom-and-root-guide-with-magisk.4338671/
vamsi209 said:
how did u recover sir ? flashed original boot.img?
Click to expand...
Click to collapse
Kinda... i booted the twrp-recovery bootimage by using
fastboot boot twrp.img
that brought me back to twrp and restored touchscreen-control. In twrp i formatted the device and completely wiped all partitions, so i would have a clean install. After all that was done i returned to bootloader and used the fastboot-image to clean-flash everything. I wanted to do this anyways, so no biggy.
It's still okay to use it, but installing it on the device as permanent recovery doesn't work as long as the touchscreen doesn't work at all.. but when this is fixed, go for it.
already did all of it...
vamsi209 said:
as of now, no use of flashing twrp as there are no proper custom rom, but inorder to put this ur phone should be unlocked, to do that follow this guide https://forum.xda-developers.com/t/...to-eu-rom-and-root-guide-with-magisk.4338671/
Click to expand...
Click to collapse
already did all of it...
SanHelios said:
Hey, i wanted to report a bug...
After i installed twrp permanently by advanced settings, i lost the touchscreen, after i rebooted into recovery.
Click to expand...
Click to collapse
Fixed!
Thanks for reporting..
vamsi209 said:
as of now, no use of flashing twrp as there are no proper custom rom, but inorder to put this ur phone should be unlocked, to do that follow this guide https://forum.xda-developers.com/t/...to-eu-rom-and-root-guide-with-magisk.4338671/
Click to expand...
Click to collapse
Phone is already unlocked as im running 21.9.28 lol
jrvenge said:
Phone is already unlocked as im running 21.9.28 lol
Click to expand...
Click to collapse
to just run this twrp, u can boot your device to bootloader, open terminal or powershell, and use command
fastboot boot twrp*.img
this will boot your twrp recovery,
as mentioned by @SanHelios there seems to be a small bug when u r flashing it permanently as recovery,
and the dev already got a fix for the same, he will mostly update the links tomorrow, i tested and it was working,
this is the file he provided, link, @SanHelios test this mate
download the above file,
use fastboot boot twrp*.img, and go to advance, and click on flash current twrp,
it will patch your boot.img file and flash the patched boot.img with twrp recovery
use volume up and power button combo to boot into twrp
imjyotiraditya said:
Fixed!
Thanks for reporting..
Click to expand...
Click to collapse
Thx for your awesome work, man..
I still dont get what it actually does lol
jrvenge said:
I still dont get what it actually does lol
Click to expand...
Click to collapse
You mean, the general function of TWRP?
yes
jrvenge said:
yes
Click to expand...
Click to collapse
TWRP is a well-rounded recovery for android-devices. There's a lot it can do, but basicly, you use it to flash/install software or images on your device. If there is a custom rom you wanna use, you flash it via TWRP, since the stock roms-recoveries only flash/install their associated roms. Apart from that, you can wipe or format your device, so it will be "clean" if you want to make a fresh installation.
In the past it was simple to install it, because devices were mostly A-only devices with a dedicated "recovery"-partition. To install it, the most common way was
- Boot into Fastboot mode, connect android via USB
- open computer CLI/Shell-window
- "fastboot flash recovery twrp.img" - Enter
The Mi Mix 4 is an A/B-Device, which means that the vital partitions are doubled and there's no "recovery"-partition anymore, since all recovery-functions are parked in a different partition. TWRP offers the ability to install itsself according to the A/B-Partitions-scheme and therefore becoming the new System-Recovery. Here the installation-steps are different.
- Boot into Fastboot mode, connect android via USB
- open computer CLI/shell-Windows
- "fastboot boot twrp.img" - Enter <- Starts the system using the image
- Touch Advanced
- Touch "Flash Current TWRP"
If a custom rom ever becomes available, there's certain routine you want to do...
backup vital information and files
format device
wipe all partitions
flash Firmware required
flash rom
flash Google Apps i.e. Open Gapps Project or NikGapps if available and desired
wipe dalvik-cache/cache/data
Enjoy
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.
#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/Recovery
* 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.
*
*/
Working Features:
- Decryption Works
- Backup works
- Wipes Work
- MTP
- ADB
- OTG
- RUI 2 ozip Flashing
- RUI 1 ozip flashing
Not Working:
- No f2fs support yet
- Not tested on CN variants (Can't confirm working status)
Flashing Guide:
Patched VBMETA is must to boot a twrp , so flash the below image to successfully boot this recovery and make it available even after booting back to RealmeUI.
Download Links:
TWRP Download Link
VBMETA Link
To flash TWRP:
fastboot flash recovery twrp-3.6-RUI2-RMX1931-final.img
Flash the VBMETA using below commands
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_path.img
ADB and Fastboot Drivers:
ADB and Fastboot Installer
Source code:
https://github.com/TeamWin/android_bootable_recovery
https://github.com/arnodorian-r/recovery_realme_RMX1931
https://github.com/arnodorian-r/kernel_realme_sm8150
Credits:
Thanks to @mrtechnophile2.0 , Roy for the testing
Thanks @pjgowtham @XiaoAk for guiding me
The best thing ever happened for realme ui 2. Great work mate..!
Finally, a proper working Recovery for our device
Wow...Finally Working TWRP for RMX1931 on RUI2.
Thanks alot bro.
Can I flash this, when I'm on Lineage-18.1?
zheka99 said:
Can I flash this, when I'm on Lineage-18.1
Click to expand...
Click to collapse
Technically its possible...but you should do it after roms released based on rui2 firmware. If not , you will endup with broken OS. For now dont flash custom roms with this recovery.
can i flash magysk to optine root, wich version?
Isavar said:
can i flash magysk to optine root, wich version?
Click to expand...
Click to collapse
Magisk-92546e8a(23016) from CANARY all Ok!
Sorry for my English. And thank you very much for your work. I have the mobile with the latest version of rui2 and with root done following this guide:
https://forum.xda-developers.com/t/...fix-rui-2-0-android-11-global-indian.4371041/ When I went to install twrp, the mobile only started in twrp , and I had to reinstall everything. I used realme flashtool and refollowed the guide to get me back up and running properly. What could have happened?
Leozgz85 said:
Sorry for my English. And thank you very much for your work. I have the mobile with the latest version of rui2 and with root done following this guide:
https://forum.xda-developers.com/t/...fix-rui-2-0-android-11-global-indian.4371041/ When I went to install twrp, the mobile only started in twrp , and I had to reinstall everything. I used realme flashtool and refollowed the guide to get me back up and running properly. What could have happened?
Click to expand...
Click to collapse
Hi
was the same for me, had to reinstall everything, only started in TWRP. Would like to install the recovery but I don't feel like this error anymore.
Thanks. It's working.
Doesnt work for me, i cant boot to realme ui after flashing the vbmeta, i got stuck on recovery. (f.14)
This recovery is broken for me, it gives me no space left on sdcard even after a full data reformat, ozip extraction stops after 500mb.
It's just not working as it should 3.4 works best
arnodorian-r said:
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.
#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/Recovery
* 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.
*
*/
Working Features:
- Decryption Works
- Backup works
- Wipes Work
- MTP
- ADB
- OTG
- RUI 2 ozip Flashing
- RUI 1 ozip flashing
Not Working:
- No f2fs support yet
- Not tested on CN variants (Can't confirm working status)
Flashing Guide:
Patched VBMETA is must to boot a twrp , so flash the below image to successfully boot this recovery and make it available even after booting back to RealmeUI.
Download Links:
TWRP Download Link
VBMETA Link
To flash TWRP:
fastboot flash recovery twrp-3.6-RUI2-RMX1931-final.img
Flash the VBMETA using below commands
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_path.img
ADB and Fastboot Drivers:
ADB and Fastboot Installer
Source code:
https://github.com/TeamWin/android_bootable_recovery
https://github.com/arnodorian-r/recovery_realme_RMX1931
https://github.com/arnodorian-r/kernel_realme_sm8150
Credits:
Thanks to @mrtechnophile2.0 , Roy for the testing
Thanks @pjgowtham @XiaoAk for guiding me
Click to expand...
Click to collapse
I followed this guide and many others in the past 48 hours, with no success. Every time I flash TWRP and the VBMETA, I get stuck in TWRP bootloop.
I started unblocking the bootloader, rolling back to RUI1 - Android 9 and using the Deep-Test App.
After the roll back, I got the phone unblocked right, but then first soft-brick, with only bootloader available and no way to flash a working ROM. After some searches, I've finally managed to unbrick, using OPPO flash tool, and installing stock rom RMX1931_11_F.14_2021102817443142.
This gives me a working phone, RUI.2 - Android 11. Standard recovery.
I tried to flash TWRP and got the phone soft bricked again, in TWRP recovery bootloop.
I'd like to install TWRP and from there going to OrangeFox and finally install Lineage 19.1...
How can i first have a working TWRP recovery??? If you can support also following steps, would be amazing. Thank you!!!
I went few step further... but still I am not able to install a working custom recovery for my realme X2 pro.
I have now also rooted my device with magisk.
I just need a custom recovery to perform 2 actions:
- make a NANDroid backup;
- install a custom ROM.
Any advice? Thank you for your time!
Installed. Working like a charm with lineage 19.1. Only problem: can't access files in storage. Digging into the matter, it seems to be an issue with android 12's new encryption method, which can't be overriden by this version of the recovery. There's a brand new TWRP 3.7.0_9.0 in the official TWRP website which boasts to overcome this problem but, whenever I try to install it (with or without the vbmeta.img provided for version 3.6.0_11), the recovery won't start. Guess a new vbmeta.img is needed as everything goes ok reinstalling TWRP 3.6.0_11 and its corresponding vbmeta. Tried to extract and install vbmeta.img from the lineage zip file without success. Shall we have to patch vbmeta.img? How can we do that? Through Magisk? I've come across some "vbmeta patcher" apk... Am I pointing the right way?
can any one help me to unlock bootloader in realme x2 pro . i am on RUI 10 . i installed in depth tool it said seccesful but no bootloader just keep rebooting and showing fast boot for a moment .. help please i search every where for fix but no way to yet
I'm using the CN variant device, which I understand does not yet have confirmed support, nonetheless sharing the error I'm encountering in case it's a simple or obvious fix I'm missing.
Having followed all above steps, I'm able to flash and get into TWRP recovery, but decryption always failed (even after a dozen tries) with the following:
"Attempting to decrypt FBE for user 0...
Failed to decrypt user 0"
Much obliged for any insight on this. I'm attempting to get back on OF after successfully installing Lineage 19.1, which broke the OF recovery, and since OF needs to be installed as a ZIP, I need to get some version of TWRP working as an intermediary. Specifically this is because I didn't install GAPPS along with Lineage 19.1 (I misread the opening post, which seemed to imply that GAPPS was included in that particular ROM). So alternatively, if there's another way to get GAPPS onto the device without recovery (sideload won't work since I can't decrypt...) then that would be helpful too.
Thanks in advance for any insight on this!