[Tool] RFT - REALME Flash Tool to flash stock ROM (For Unlocked Bootloader) - Realme 6 Pro ROMs, Kernels, Recoveries, & Other De

REALME FLASHTOOLS
V 1.1.3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This tool can make you easier to install stock roms, Rollback, Downgrade
This program is made for Windows, with .NET Framework 4.5.1 This is VB.net program
What the tool can do:
- Flash phone - For now the tool supports Realme 6 Pro only.
- Requires the bootloader to be unlocked.
- Able to create custom flash process
- Can dump your current partitions to create a flashable file
Thanks to:
- Narender Singh (TechMesto.com)
- Hikari Calyx (hikaricalyx.com)
Downloads:
* RFT v.2.0.2 (required : NET Framework 4.8) - 24 Dec 2021 (NEW)
* RFT v.2.0.1 (required : NET Framework 4.8) - 11 july 2021
* RFT v.1.1.3 (Stable)- 09 may 2021
* RFT v.1.1.2 (Stable)- 08 April 2021
Firmware - Normal Flash
- A27 Download
DONATE LINK
Donate here
System requirements:
- Windows 7, 8, 8.1,10 or higher, 32bit or 64bit
- .NET Framework 4.8
- USB Data Cable
- Phone
- Prosesing Ozip file need 20 - 25Gb Free space on drive ( RFT drive ) use as temporary , automatic deleted after flash complete.
- Python 3.7.2 or newer .. Download & install HERE
- Check ENVIRONMENT VARIABLES Windows -> user Variables -> path -> make sure Python and Python\Script folder has there,
If Not, Add it
NOTES:
if first time try RFT and return failed.. Its Ok its because driver not installed yet on your PC (fastbootd driver) ..
wait windows complete install / update driver and reflash....
RTF should be work after that

change Logs
V.1.0.1
- fix flash phone with custom recovery
- Fix minor problem identify files
- fix check flash status
- Now Support Flash Custom Rom .zip
V.1.0.2
- Now Support Repartition Dinamic partition use ozip dinamic_partition files ( u can flash Freely from Custom , or flash different region firmware )
- fix extract Ota problem on windows 32 bit
- add homebrew firmware feature = build Flashable firmware for Normal Flash Use OZip Files,
homebrew is ozip complete Processed.. will save much time if u often flash phone compare to use ozip
V.1.0.3
- Add some Convertion Process On Ozip...
V.10.4
- Tweak Dynamic Partition process
- Add Russian Language
V.1.0.5
- fix metadata super
- add russian translation
V.1.0.6
- Fix Problem Flashing Rom on V.1.0.5
v1.0.7
- add custom restore (phone rooted, usb debuging mode) ( work like flashsify but from pc), do not use to restore super..
v1.0.8
- fix issue flashing Android 11
- new flashing order to pervent bricked
- fix stuck process while do dump partition
- fix homebrew for a11 files
v.1.0.9
- add support custom rom A11
v.1.1.0
- fix issue on some pc
- fix restore backup issue at 1.0.9
- add "verify before flash" : test your phone able to enter fastbootd / not
v.1.1.1
- fix issue on some PC
- add Delay option for people Who face issue ( cause windows )
issue = command continoues execute and failed ( when phone on reboot )
v.1.1.2
- fix russian translate
- fix issue failed convert
- fix error while cancel process
v.1.1.3
- fix text position for russian language
- fix failed to flash when flash stock rom with custom ozip option selected
- add generate 1 click debloat script... every user can have their own 1 click debloat
v.2.0.0
- cause i lose my previous source, build new one less feauture
- flash ozip
- backup partition ( dump)
- improve alot performance proc / ram used more less than v.1.x.x
- new flash flow process
- add if flash failed , ozip wont reextract again, it will use previous data
V.2.0.1
- fix issue when pc have 2 version of python, or different python variable
- fix russian translate
- remove unbackup partition in backup form
V.2.0.2
- fix flash custom rom a12

How to Flash use RFT
* Normal flash
- menu flash- flash phone - normal flash
- Choose Profile Flash
- Choose Folder Firmware ( u can build from Ozip)
- select Option available
- choose Option
Disabled vbmeta = use --disabled-verty --disable-verification when Flash Vbmeta (for root, custom recovery , custom rom)​ (do not check it if u plan to Flash all Stock Rom, example For Relock bootloader)​
Erase User data = Wipe user data​
- Boot Your phone Into Bootloader
- flash
* Flash Use ZIp, ozip
- menu flash- flash phone - Ozip
- Choose Ozip File
- choose Option
Disabled vbmeta = use --disabled-verty --disable-verification when Flash Vbmeta​ (do not check it if u plan to Flash all Stock Rom, example For Relock bootloader)​
Erase User data = Wipe user data​
Custom Rom = For flashing Custom Rom , this Option will Ignore Check Ozip filesize.​ Check Ozip filesize use to Pervent user to flash Incremental Update... Flash incremental update will brick your device​
- Connect and boot Phone To Bootloader
- Flash
- Build Homebrew Firmware
- homebrew firmware use to save time , if u often flash phone, Ozip need Process before able to use to flash...
Homebrew is Ozip after process
- menu - homebrew -ota files
- choose ozip files
- Choose Folder to save
- make homebrew

Great Work.!
Thanks.!

Wow Flash tool for Realme 6 PRO

getting this error
Flashing "abl.img" to abl....
Sending 'abl' (212 KB) OKAY [ 0.074s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
Finished. Total time: 0.104s
edit- worked on recovery after re-installing drivers

Ronny mehata said:
getting this error
Flashing "abl.img" to abl....
Sending 'abl' (212 KB) OKAY [ 0.074s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
Finished. Total time: 0.104s
edit- worked on recovery after re-installing drivers
Click to expand...
Click to collapse
yes , make sure phone driver installed..
when RTF start flashing dont use your phone..
RTF work on recovery & bootloader ? so phone will restart couple times

If bootloader unlocked still safe to system update? Im afraid to get a notifs " root detected "

Is it okay if I install Phyton 64 bit instead of 32 bit?
---------- Post added at 10:23 ---------- Previous post was at 10:22 ----------
davejimson said:
If bootloader unlocked still safe to system update? Im afraid to get a notifs " root detected "
Click to expand...
Click to collapse
Yes. You can still can update your phone.
You won't get that notification.

Felix Siahaan said:
Is it okay if I install Phyton 64 bit instead of 32 bit?
---------- Post added at 10:23 ---------- Previous post was at 10:22 ----------
Yes. You can still can update your phone.
You won't get that notification.
Click to expand...
Click to collapse
choose base on your pc windows.. 64bit or 32bit

--

Help
So, I got a Realme 6 Pro RMX 2063.
I'm in need to re-install a stock rom to the phone, I have 4 different roms I can use
1 is an EU rom which didn't work well despite me having been able to install it,
and I have a what I believe is the global ota rom, both in the .ozip format.
And another 2 roms in the .ofp format.
I've attempted to use this flash tool but I got an system partition flash error. Additionally the
Python program was previously installed and its folders added to the windows - Environment Variable.
To re-flash stock firmware to this phone has been a headache as this tool was not the only method I've
tried. Also, follows in annex to this message a screenshot I took of the log on the program showing the failure.
Lastly, in what mode does the phone have to be for using this program ?, Fastboot or Stock Recovery ?
Maybe someone could explain how to with more depth ?. Thank You

klmtg said:
So, I got a Realme 6 Pro RMX 2063.
I'm in need to re-install a stock rom to the phone, I have 4 different roms I can use
1 is an EU rom which didn't work well despite me having been able to install it,
and I have a what I believe is the global ota rom, both in the .ozip format.
And another 2 roms in the .ofp format.
I've attempted to use this flash tool but I got an system partition flash error. Additionally the
Python program was previously installed and its folders added to the windows - Environment Variable.
To re-flash stock firmware to this phone has been a headache as this tool was not the only method I've
tried. Also, follows in annex to this message a screenshot I took of the log on the program showing the failure.
Lastly, in what mode does the phone have to be for using this program ?, Fastboot or Stock Recovery ?
Maybe someone could explain how to with more depth ?. Thank You
Click to expand...
Click to collapse
thanks i will update guide how to use it..
from bootloader...
from error u got... is u from custom rom?
i already put NOTES
do you read it
if u flash custom rom from custom recovery...
RTF use ozip will not work..
because system got repartition...
from stock eu to other should be ok...
v1.0.2 fix problem because different partition size, u can flash From custom or cross region now
thanks

Realme 6 pro revive
Hi there,
i unlocked bootloader for realme 6 pro,
but after a while using the phone i decided to relock the bootloader because i was having issues while streaming netflix & amazon,
so i did locked the bootloader but now the the phone shows (The current image boot/recovery have been destroyed),
i cannot boot into fastboot neither into recovery mode,
is there any way to revive the phone ?

spookey007 said:
Hi there,
i unlocked bootloader for realme 6 pro,
but after a while using the phone i decided to relock the bootloader because i was having issues while streaming netflix & amazon,
so i did locked the bootloader but now the the phone shows (The current image boot/recovery have been destroyed),
i cannot boot into fastboot neither into recovery mode,
is there any way to revive the phone ?
Click to expand...
Click to collapse
visit service Center
do you reflash before relock?
i tested my tool, relock after flash ,all work Fine, im able to relock without problem
RFT replace recovery to stock,
problem because it detect unofficial file on your partition,
can because root, Twrp(custom recovery) installed, just simple --disable-verity when flsh vbmeta
on your case because Custom Recovery
to relock make sure everything same as stock....

sayaoks said:
visit service Center
do you reflash before relock?
i tested my tool, relock after flash ,all work Fine, im able to relock without problem
RFT replace recovery to stock,
problem because it detect unofficial file on your partition,
can because root, Twrp(custom recovery) installed, just simple --disable-verity when flsh vbmeta
on your case because Custom Recovery
to relock make sure everything same as stock....
Click to expand...
Click to collapse
didn't flashed the stock before relocking,
i was using custom recovery while relocking bootloader.
it's in warranty because i had relocked bootloader but boot.img is modified that's why it doesn't goes into fastboot and recovery as well,
i have visited the service center they have given me a few days to fix it,
hopefully it gets revived.
thank you

sayaoks said:
How to Flash use RFT
* Normal flash
- menu flash- flash phone - normal flash
- Choose Profile Flash
- Choose Folder Firmware ( u can build from Ozip)
- select Option available
- choose Option
Disabled vbmeta = use --disabled-verty --disable-verification when Flash Vbmeta (for root, custom recovery , custom rom)​ (do not check it if u plan to Flash all Stock Rom, example For Relock bootloader)​
Erase User data = Wipe user data​
- Boot Your phone Into Bootloader
- flash
* Flash Use ZIp, ozip
- menu flash- flash phone - Ozip
- Choose Ozip File
- choose Option
Disabled vbmeta = use --disabled-verty --disable-verification when Flash Vbmeta​ (do not check it if u plan to Flash all Stock Rom, example For Relock bootloader)​
Erase User data = Wipe user data​
Custom Rom = For flashing Custom Rom , this Option will Ignore Check Ozip filesize.​ Check Ozip filesize use to Pervent user to flash Incremental Update... Flash incremental update will brick your device​
- Connect and boot Phone To Bootloader
- Flash
- Build Homebrew Firmware
- homebrew firmware use to save time , if u often flash phone, Ozip need Process before able to use to flash...
Homebrew is Ozip after process
- menu - homebrew -ota files
- choose ozip files
- Choose Folder to save
- make homebrew
Click to expand...
Click to collapse
Normal flash need to fastboot mode?

Kuma_Chaser said:
Normal flash need to fastboot mode?
Click to expand...
Click to collapse
Yes.. boot to bootloader

Help beeded please! Urgent!
I bricked my Realme 6 Pro by clicking "Lock the bootloader" with custom rom. Now it says broken boot/recovery and asks to flash. But no adb or fastboot device found. It can only boot to EDL. How to fix? Please any help

Mine is RMX2063 and before first flash, i had RMX2063_A.35 so the latest update via OTA.
I have tested the tool, and it is 100% working. Flashed my Realme 6 Pro first time now without a problem.
It took 45min to flash (downgrade to RMX2061_11.A.26 (RU Region by mistake) But all worked perfect.
Curently flashing (RMX2061EU_11.A.26 (Region: Europe)
I did the best choice choosing this version insteed of what i had before?
And do i still receive automatically updates on this EU version?
I am in UK so don't want all that bloatware from the China or International versions.
Any ideas?
Update: (RMX2061EU_11.A.26 (Region: Europe) seems to be the same: Region Operator: RU

Related

Lenovo A3500HV Root,CWM,Flashtool Backup,ROM Dump,Scatterfile,Update.zip and Links

Hi this thread contains Clockworkmod Recovery,Flashtool Backup,ROM Dump,Deodexed ROM,Nandroid Backup,Official Update,Patched Boot.img and Scatterfile
UPDATE
-Will be making Philz touch recovery on december (On my vacation when i have free time) it is a modified,update and better recovery than the CWM......hope you can wait for it TWRP Recovery is way better than Philz Recovery
-Guys who want CWM recovery for the A3500H or F or FW version please post your recovery here i shall try to make it into CWM recovery (On december you can also ask for philz recovery)
-Thinking of making an custom ROM on december also
-Will be posting the Updates/nandroid backup/romdump/Deodexed.zip of the 4.4.2 versions in the middle of next month
-Also i have found a new method of sniffing the URL of the update.zip without any logcat all you need is root and xposed module and a windows OS will be making a tutorial for it soon.Capturing OTA Update URL For Noobs (No logcat required)
Rooting Guide-
1) Flash CWM Recovery using Flashtool
2) Flash UPDATE-SuperSU-v2.02.zip using CWM recovery (Links provided below)
Dodexing Guide-
1) Flash the zip file in CWM to deodex (It help youin theming) (Will upload the deodexed 4.4.2 Soon)
Important-
1) Do not flash Patched boot.img (Gives adb Root shell by default) if you are using 4.4.2 version (Will upload it soon)
2) When making a nandroid backup make sure that you backup and erase all data in your in your internal memory otherwise it shall make a backup of that too.
3) Before Flashing the system partition make a IMEI bacup using Mobileuncle Tool and restore it after flashing or the mobile internet and call will not work.
4) To go to recovery press vol+,vol- and power
Changelog-
04/11/2014
- Added TWRP Recovery
- Added TWRP Nandroid Backup Of A3500HV_A422_01_22_140402_IN
- Patched(ADB Root Shell) And Unpached Boot.img (Kernals) For Android 4.2.2
Press Thanks if it helps (That is if you can find it since the thanks has disappeared in the new forum theme.....lol)
Tools
Tools Required for these procedure-
Drivers-
-ADB Driver (Thought i would give since not all adb driver works on this tablet)
-Preloader VCOM Driver (Required to for SP Flashtool to work)
Tip- If having problem in installing driver in windows 8,8.1 head to the tutorial section blow for detains since unsighned drivers needs to be enabled in these windows version
Windows Softwares-
-SP FlashTool
-ADB Installer (Allows ADB to be used systemwide)
-USB Deview (Checks What Drivers You Have Installed And Helps To Uninstall Them)
Apps-
-MobileUncle Tools
-Flashify v1.7.4.apk
Tutorials
These are tutorials that you must read before doing anything (It will only take 5 Min)-
CWM Flashable Files
These are the list of files that can be flashed by Clockworkmod Recovery
Rooting zip-
-SuperSU.zip
Deodexed App-
-A3500HV_A422_01_22_140402_IN
Flashtool Files
These are the list of files that can be flashed by SP Flashtool-
ROM (Inclusive with CWM Recovery and Patched boot.img)-
-A3500HV_A422_01_22_140402_IN
Recovery-
-Original
-CWM
-TWRP
Boot.img (Kernals)-
-Patched (ADB Root Shell) And Unpatched For Android 4.2.2
Nandroid Backup
This is a nandroid backup of a clean system (I am not sure if it will work on other devices but what the hell....lol)
Important-
Backup and restore IMEI using Mobile Uncle or you will loose your call and internet function
Versions-
CWM-
-A3500HV_A422_01_140402
TWRP- (Do not flash the NVram partition or you will loose your call function also make an IMEI Mobile Uncle Backup)
-A3500HV_A422_01_140402
Official Updates
This is the Official Lenovo Updates Flashable.zip and its links (The Link gives the official lenovo link but the file is 1GB and download Accelerator seems to corrupt it use my link it is exactly the same and the files are broken into 400mb parts and you can use download accelerator on it...:victory
For the updates to work you need to reflash the stock recovery (Link Above) install the update Reflash the CWM then Done
Method 2-This method can only be used for the rooted device to install recovery (Since you need to flash CWM before you rot the device i did not write it above
-extract the original recovery. rar
-open flashify.apk on the tablet
-select recovery.img to flash
-done flashing successful
-reboot now
-recovery now is stock select update.zip
-flash it
-take 2 minutes
-successful
-reboot sysw now
-take 3 minutes
-my system build version and the launcher is updated
-Flash back the CWM recovery with Flashify
Note- Sometimes the update removes the root then you need to follow the rooting procedure again
Updates-
-01) Lenovo_A3500-HV_A442_01_S037_WC69
Links-
-01) Lenovo_A3500-HV_A442_01_S037_WC69
TUTORIAL- Capturing OTA Update URL For Noons (No logcat required)
ROM Dump
This is the ROM Dump of the entire ROM
-A3500HV_A422_01_22_140402_IN (CWM Recovery) (After First Run)
Others
These Folders Contain Other Stuffs-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
great work
thank you great work ...is there any way to flash update.zip by cwm recovery ? it give me error 7 and installation aborted ..if i toggle signature verification it give me error cant verify whole file
one more question
i already rooted my tablet and have cwm ..if i want to restore the original one must do imei backup .or not?
drabuaiad said:
thank you great work ...is there any way to flash update.zip by cwm recovery ? it give me error 7 and installation aborted ..if i toggle signature verification it give me error cant verify whole file
one more question
i already rooted my tablet and have cwm ..if i want to restore the original one must do imei backup .or not?
Click to expand...
Click to collapse
I guess you have to flash the original recovery then try it if still no results then use use ota rootkeeper (or similar app) to hide root before update if that still does not work remove root through Supersu settings and then try it lenovo has really made this model such that you can not get root easily therefore they must be checking for root before updates after that use the default steps for rooting above .
Above all check your lenovo and see that it is a3500 HV and not simply h or f as the kernel are different
No when you are flash a boot.IMG or recovery.IMG you need not do a backup and while flashing through CWM with the official update you need not since there are scripts in it to transfer the imei or so I guess but but since you are rooted its always best to do one because adding an imei number is more difficult than a restore and the process takes a few seconds and only needs about 120 bytes (you can backup a billion of those and still not run out of space
Better safe than sorry....lol
thank you again
Yes my tablet is a3500 hv and i have the FW 4.4.2.....35 which is the same as .....37 except the lenovo launcher
So i am satisfied with it and waiting if new update arrives i will restore the original recovery
I think there is no more update will land here except if android L is the next one..i dont think so
drabuaiad said:
thank you again
Yes my tablet is a3500 hv and i have the FW 4.4.2.....35 which is the same as .....37 except the lenovo launcher
So i am satisfied with it and waiting if new update arrives i will restore the original recovery
I think there is no more update will land here except if android L is the next one..i dont think so
Click to expand...
Click to collapse
Great but did you root your tablet after you got the 4.4.2 update or before I tried the update and the same error 7 guess need stock recovery also i will be posting a tutorial on how to capture official update links that does not require logcat and only requires to install two software and an app. Found this method while trying to capture offnline setup from online installer (in windows 7 when you use a online setup it quietly downloads a offline setup and then installs it and after installation deletes it I found a way how to capture the link so in that method I use the reverse tethering to take internet from the computer and then capture the link from the computer...lol) Will make a thread in the next two days.
excellent it is new idea
I am waiting your tutorial
I received 5 updates for my tab..three of them is 4.4.2 after i update the 35 version i found the root method above ..flashing cwm recovery then install superiser.zip.
After that i get small update 9.22mb that will replace lenovo launcher and change the build number to 37 ..but cant install it and give me error 7
I catch the update.zip from ggogleota folder and transfer to my external sdcard and try to flash it after toggle sg verification and also toggle assert ...
But also give me installation aborted
I stop trying and i have now original recovery downloaded in my tablet and ready for any new update lol
drabuaiad said:
excellent it is new idea
I am waiting your tutorial
I received 5 updates for my tab..three of them is 4.4.2 after i update the 35 version i found the root method above ..flashing cwm recovery then install superiser.zip.
After that i get small update 9.22mb that will replace lenovo launcher and change the build number to 37 ..but cant install it and give me error 7
I catch the update.zip from ggogleota folder and transfer to my external sdcard and try to flash it after toggle sg verification and also toggle assert ...
But also give me installation aborted
I stop trying and i have now original recovery downloaded in my tablet and ready for any new update lol
Click to expand...
Click to collapse
Cool so if it works please tell me I shall update the official update post of this forum and also tell me if you did the update by changing recovery only or by changing recovery and also unroofing hope it works....:fingers-crossed:
And within one months time after my final exams are over I will try to make a custom ROM nothing fancy just the most updated Updates custom apps deodexed some patches etc etc and so on....just something I am thinking of doing with my new alienware during my Christmas vication.
oh my god
its working
i do this
extract the original recovery. rar
open flashify.apk on the tablet
select recovery.img to flash
done flashing successful
reboot now
recovery now is stock (it is somewhat different i think it is of 4.2.2 FW) select update.zip
flash it
take 2 minutes
(it write delete unwanted files!!!!!!)
successful
reboot sysw now
take 3 minutes (long time)
my system build version and the launcher is updated
---------- Post added at 05:42 PM ---------- Previous post was at 05:22 PM ----------
NB root is removed
good for me
After the second reboot .recovery now the stock of FW 4.4.2 it looks different
Lenovo A3500H MT8382???
anandisrocking007 said:
Hi this thread contains Clockworkmod Recovery,Flashtool Backup,ROM Dump,Deodexed ROM,Nandroid Backup,Official Update,Patched Boot.img and Scatterfile
Rooting Guide-
1) Flash CWM Recovery using Flashtool
2) Flash UPDATE-SuperSU-v2.02.zip using CWM recovery (Links provided below)
Dodexing Guide-
1) Flash the zip file in CWM to deodex (It help youin theming) (Will upload the deodexed 4.4.2 Soon)
Important-
1) Do not flash Patched boot.img (Gives adb Root shell by default) if you are using 4.4.2 version (Will upload it soon)
2) When making a nandroid backup make sure that you backup and erase all data in your in your internal memory otherwise it shall make a backup of that too.
3) Before Flashing the system partition make a IMEI bacup using Mobileuncle Tool and restore it after flashing or the mobile internet and call will not work.
4) To go to recovery press vol+,vol- and power
Press Thanks if it helps (That is if you can find it since the thanks has disappeared in the new forum theme.....lol)
Click to expand...
Click to collapse
Dear anandisrocking007 thank you for enormous effort on rooting lenovo A3500.
I confused if I can use your procedures for my lenovo A7-50 A3500H_A422_01_23_140404_TR, chipset mt8382 , 4.2.2 (update ready but not installed to 4.4.2).
I would like to use phone specification of tablet while I install my SIM card to access internet.
Also I had problem to install MTK driver to use flashtool for CWM recovery.
Thanks in advance for your help.
Cihangir
baycanc said:
Dear anandisrocking007 thank you for enormous effort on rooting lenovo A3500.
I confused if I can use your procedures for my lenovo A7-50 A3500H_A422_01_23_140404_TR, chipset mt8382 , 4.2.2 (update ready but not installed to 4.4.2).
I would like to use phone specification of tablet while I install my SIM card to access internet.
Also I had problem to install MTK driver to use flashtool for CWM recovery.
Thanks in advance for your help.
Cihangir
Click to expand...
Click to collapse
Your version is H not HV (Different Hardware well about 95% same) use thisk link- http://forum.xda-developers.com/android/development/guide-lenovo-a3500-h-t2879208
The kernal might be different so be carefull if you are using this recovery in this thread though the probability of the there being problem for the recovery is low if any problem please contact me and if you want a CWM recovery for the following device just sent me the recovery.img
As for rooting you can use tis update zip it is going to work for over 99% of the mobile in the world
As for the problem for the driver use the tutorial for the installing drivers in windows 8 if you are using that version of windows 8 for me the drivers worked perfectly if not disable the antivirus its 100% not a virus and also you need to be in admin account when you install the driver and not in the guest account.....
At december or so i would be making Philz touch recovery which is a modified and better recovery image based upon CWM recovery
If any more problem feel free to contact me.....:victory::victory:
drabuaiad said:
oh my god
its working
i do this
extract the original recovery. rar
open flashify.apk on the tablet
select recovery.img to flash
done flashing successful
reboot now
recovery now is stock (it is somewhat different i think it is of 4.2.2 FW) select update.zip
flash it
take 2 minutes
(it write delete unwanted files!!!!!!)
successful
reboot sysw now
take 3 minutes (long time)
my system build version and the launcher is updated
---------- Post added at 05:42 PM ---------- Previous post was at 05:22 PM ----------
NB root is removed
good for me
After the second reboot .recovery now the stock of FW 4.4.2 it looks different
Click to expand...
Click to collapse
The recovery is HV not FW 100% sure i know which tablet i have maby in different countries different recovery don't know also did you need to remove root for the update to work or did the update remove the root??????
By the way in december (When i go back home for vecation and have plenty of time) i am thinking of making Philz touch recovery it is a modified updated and better version of CWM recovery.
mmmmm
waiting your new recovery
the update remove the root but still the super user present as a system application ...
The recovery i flashed is not the same as this present after first boot after updating
my tablet now work fine but may i change my mind with your first custom rom

[RECOVERY][Realme 6 Pro] TWRP Recovery [Stable]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void (or isn't ? who am I to judge ?)
*
* 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.
*
*/
Team Win Recovery Project 3.4.1 for Realme 6 Pro
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.
Ported From Realme X50 5G
• by ctapchuk from 4pda
Most Bugless Recovery Right Now
Installation
1. Disable verified boot first
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img which is extracted from current stock rom ozip file
2. Flash downloaded twrp
Code:
fastboot flash recovery twrp.img
3. Reboot to recovery
Code:
fastboot reboot recovery
List of features :
• Decryption of storage works on latest Stock firmware (September security patch)
• Successful installation of any ROM's
• External sdcard & USB-OTG support
• Additional features such as close AVB2.0 (disabled-verify on vbmeta), disable replace TWRP
• Working mounting of dynamic partitions (r/o only)
• Additional backup/restore partitions list (except system, vendor and etc)
Download :
https://drive.google.com/file/d/1NWS74xHgyIKwpTd5sZ6af9ukroXF7VAp/view?usp=sharing
Version Information
Status : Stable
Current Stable Version : 3.4.1b_0507
Stable Release Date : September 30, 2020
Reserved
Good work, i was trying to find a proper TWRP for my Realme 6 Pro from lasat week.
Until now i was able to flash updates or downgrades just via Realme Flash Tool.
Do we still need to flash vbmeta_v2 in order for TWRP to work properly?
Testing now.
Update:
It does need the OF_avb-patcher.zip tp be flashed in order to keep TWRP after restart and to decrypt MPT storage and phone corectly.
I did not flashed it and all the time got stuck in a boot loop and TWRP and all phone remained encrypted, was not able to do anything until i flashed Stock Rom via Realme Flash Tool.
Disclaimer: Flashing Stock Rom will make TWRP gone, to preserve it, follow the steps:
1. Flash Stock ROM .ozip
2. Flash patched-vbmeta-v2.img
3. Flash TWRP from above link
4. Flash OF_avb_patcher.zip
6. Flash Magisk via TWRP (If required)
7. Done
Richardo87 said:
The same issue i was getting with the previous TWRP versions, cannot access MTP storage. Also while phone on, cannot copy anything on storage.
Click to expand...
Click to collapse
Please provide screenshots of your problem. I assume that you are trying to copy files to an encrypted internal storage. Decrypt /data or copy files to SD card
Is this compatible with build number RMX2061_11_A.35? Thank you!
Sent from my RMX2061 using XDA Labs
ByinAlbirt said:
Is this compatible with build number RMX2061_11_A.35?
Click to expand...
Click to collapse
Yes
Richardo87 said:
Good work, i was trying to find a proper TWRP for my Realme 6 Pro from lasat week.
Until now i was able to flash updates or downgrades just via Realme Flash Tool.
Do we still need to flash vbmeta_v2 in order for TWRP to work properly?
Testing now.
Update:
It does need the OF_avb-patcher.zip tp be flashed in order to keep TWRP after restart and to decrypt MPT storage and phone corectly.
I did not flashed it and all the time got stuck in a boot loop and TWRP and all phone remained encrypted, was not able to do anything until i flashed Stock Rom via Realme Flash Tool.
Disclaimer: Flashing Stock Rom will make TWRP gone, to preserve it, follow the steps:
1. Flash Stock ROM .ozip
2. Flash patched-vbmeta-v2.img
3. Flash TWRP from above link
4. Flash OF_avb_patcher.zip
6. Flash Magisk via TWRP (If required)
7. Done
Click to expand...
Click to collapse
No need i guess. Try 'Disable Replace TWRP' and reboot ...
debdeep98 said:
Yes
Click to expand...
Click to collapse
Thank you so much! I have successfully installed TWRP Recovery in my realme 6 Pro build number RMX2061_11_A.35.
Sent from my RMX2061 using XDA Labs
Richardo87 said:
Good work, i was trying to find a proper TWRP for my Realme 6 Pro from lasat week.
Until now i was able to flash updates or downgrades just via Realme Flash Tool.
Do we still need to flash vbmeta_v2 in order for TWRP to work properly?
Testing now.
Update:
It does need the OF_avb-patcher.zip tp be flashed in order to keep TWRP after restart and to decrypt MPT storage and phone corectly.
I did not flashed it and all the time got stuck in a boot loop and TWRP and all phone remained encrypted, was not able to do anything until i flashed Stock Rom via Realme Flash Tool.
Disclaimer: Flashing Stock Rom will make TWRP gone, to preserve it, follow the steps:
1. Flash Stock ROM .ozip
2. Flash patched-vbmeta-v2.img
3. Flash TWRP from above link
4. Flash OF_avb_patcher.zip
6. Flash Magisk via TWRP (If required)
7. Done
Click to expand...
Click to collapse
All you need is vbmeta.img from your stock ROM.
I used above instructions and everything work just fine, including decryption of internal storage.
@Kevin Saiza thank you for your good work.
Everything's working as expected.
Right now I'm using:
Firmware A.35
LR.TWRP 3.4.1B_30.09
Magisk 21.0 (pass safety net check)
Newer version with all features including fastboot(d) working, ported from Xiaomi Black Shark 3 is on download in pda. Can someone attach download link here for :
LR.TWRP 3.4.2B_05.10 — RMX2061 (from Black Shark 3) .img
or
LR.TWRP 3.4.2B_05.10 — RMX2061 for Windows.zip
Thanks!
Junior MemberThanks: 0
Junior MemberThanks: 0
Is this compatible with build number RMX2065_11_A.35? Thank you!
neoxcool said:
Newer version with all features including fastboot(d) working, ported from Xiaomi Black Shark 3 is on download in pda. Can someone attach download link here for :
LR.TWRP 3.4.2B_05.10 — RMX2061 (from Black Shark 3) .img
or
LR.TWRP 3.4.2B_05.10 — RMX2061 for Windows.zip
Thanks!
Click to expand...
Click to collapse
Coming Soon
Andres88z said:
Junior MemberThanks: 0
Junior MemberThanks: 0
Is this compatible with build number RMX2065_11_A.35? Thank you!
Click to expand...
Click to collapse
Yes why not .
Kevin Saiza said:
Yes why not .
Click to expand...
Click to collapse
Some problem with RMX2063. You try whit RMX2061
Sorry Is 2063
thank's
LR.TWRP 3.4.2B_05.10 for RMX2061 Ported from Xiaomi Black Shark 3 by Ctapchuk & logotoy73
Change extention to .img
https://anonfiles.com/hfcehcd1p9/LR.TWRP_3.4.2B_05.10_for_RMX2061_img
Changelog:
• Port from Xiaomi Black Shark 3
• Upgrade to version 3.4.2
• Fixes in Russian language
• Changed the font for English language
• Fixed fastbootd
• A/B table selection Disabled
• Correct display of the status bar
If i only boot, i need flash vbmeta?
I need urgent help please the twrp does not recognize my otg it only recognizes the sd but the otg does not what should I do to make it recognize it please help
:good:
Can't delete file from phone with root explorer so i tried with TWRP as usualy and for the first time IT DOESNT WORK!! Never seen that before. Though system's not mounted as read only. What to do..?
Do nothing. vendor, product and system partitions are R/O, because they are part of new type partition named "super". It is dynamic partition that is not editable.
Take a look here for details
Implementing Dynamic Partitions | Android Open Source Project
source.android.com

General [SHARED] [ROM] MiuiMiX Rom 13.0.4.0 Redmi Note 10 Pro [sweet] A12

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Stable MiuiMiX Rom for the Xiaomi Redmi Note 10 Pro [sweet]
MiuiMiX is a custom build Rom based on xiaomi.eu and china beta firmware.
Created to give you the best experience while maintaining a smooth os and long battery life.
MiuiMiX comes prerooted and Magisk is installed right out of the box, it´s even more debloated without missing important apps. All Roms from us are beeing globalized.
You can check out all features on our site or supportchannels.
All known Miui Bugs
If you find any other bug, please report them to us!
Pre-requisites:
Unlocked bootloader
Custom recovery (See the recommended recoveries)
Read the FAQ
Clean Flash (If you are coming from another ROM or you are changing between stable and weekly builds):
Boot into your custom recovery
Wipe system and vendor (highly recommended when coming from non-MIUI rom)
Format Data (the one with "YES", isn't the same as a wipe data)
Reboot into recovery
Copy the ROM zip into your internal storage or to your SD card
Flash the ROM. (Gapps and Magisk are built-in. Firmware and vendor are inside all zip files)
Wipe dalvik/art cache and cache
Reboot system and enjoy! (First boot may take up to 5-10 min.)
Updating coming from a previous version of the rom (Dirty flash, only stable over stable or weekly over weekly. Never weekly over stable or vice versa.):
It is recommended to deactivate ALL magisk modules before updating
Reboot into recovery
Flash lastest MiuiMiX build
Wipe dalvik/art cache and cache
Reboot system
DOWNLOAD Link
Pertamax
Flash via fastboot or recovery? The file name is fastboot but in instructions flashing via recovery
"see recommended recoveries" - where ?
"see FAQ" - where ?
magisk does not work
[email protected] said:
Flash via fastboot or recovery? The file name is fastboot but in instructions flashing via recovery
Click to expand...
Click to collapse
is fastboot
do gestures work with 3rd party launchers?
Ashle said:
magisk does not work
Click to expand...
Click to collapse
24 or higher is needed(support a12)
Which recovery have to use?
@Murad Ali Perhaps it would be a good idea to correct the first post? The installation steps do not apply to this ROM at all, since it's a fastboot ROM...
@prashant.palange None. As mentioned above, it is a fastboot ROM. It's installed via fastboot (so needs PC) and includes two batch files for installation. If coming from a stable MiuiMix ROM version, you can use the "update" one, if from weekly (or if you want to do a clean install anyway), then use the "install with data format" one, but bear in mind this one (quite obviously) formats your data partition INCLUDING internal storage, so backup everything you want to keep beforehand.
Case_ said:
@Murad Ali Perhaps it would be a good idea to correct the first post? The installation steps do not apply to this ROM at all, since it's a fastboot ROM...
@prashant.palange None. As mentioned above, it is a fastboot ROM. It's installed via fastboot (so needs PC) and includes two batch files for installation. If coming from a stable MiuiMix ROM version, you can use the "update" one, if from weekly (or if you want to do a clean install anyway), then use the "install with data format" one, but bear in mind this one (quite obviously) formats your data partition INCLUDING internal storage, so backup everything you want to keep beforehand.
Click to expand...
Click to collapse
good but this is not fastboot file. regular zip.
@Murad Ali The link in your post leads to the fastboot install .zip archive you get from official MiuiMix sources (it's literally the same link). It even says "fastboot" right there in the archive filename. It is not a ROM that installs via recovery, because there is no fully working recovery for Android 12. You unpack the zip on a PC and install the ROM via fastboot (which is even included in the archive, along with the installation batch files, so the installation is as straightforward as possible).
I'm frankly kinda surprised you seem to have no idea what you have linked here (and made a thread for).
Case_ said:
@Murad Ali The link in your post leads to the fastboot install .zip archive you get from official MiuiMix sources (it's literally the same link). It even says "fastboot" right there in the archive filename. It is not a ROM that installs via recovery, because there is no fully working recovery for Android 12. You unpack the zip on a PC and install the ROM via fastboot (which is even included in the archive, along with the installation batch files, so the installation is as straightforward as possible).
I'm frankly kinda surprised you seem to have no idea what you have linked here (and made a thread for).
Click to expand...
Click to collapse
sorry i am not a developer. I liked and shared the rom, if there is a mistake it will be corrected. Also, the link says it's a fastboot rom.
@Murad Ali Well, like I already said, there's indeed a mistake, in that basically the entire first post with all the info on how to flash the ROM is wrong. Pretty much none of what is mentioned there applies, it's all meant for a recovery ROM update, whereas this one is a fasboot ROM update.
Here's what the second part of the first post should look like (for example - feel free to use it if you want):
Pre-requisities:
Unlocked bootloader
PC with unpacked contents of the .zip archive you've downloaded, including folder structure (important)
Custom recovery is not needed for this ROM! You will not be using it at all! At the time of this writing, there is no fully working Android 12 custom recovery, none of them can decrypt an encrypted data partition. If you have custom recovery currently installed on your phone, it will however not be affected by the ROM install/update procedure (but it will still not be able to decrypt an encrypted data partition).
Clean Flash (If you are installing from scratch, coming from another ROM or you are changing between stable and weekly builds):
Backup all the data from your phone you don't want to lose, including the internal storage (photos, messages e.g.) The install process will do a complete wipe of your data including your internal storage! (External SD should be fine.)
Boot your phone into fastboot (bootloader) mode
Connect the phone to PC (make sure you have the correct drivers installed for fastboot mode)
Run the "fastboot_first_install_with_data_format" script/batch for your platform (windows/linux/macos).
The ROM will now be flashed to the phone automatically and then a factory reset of your phone will be done.
You are done. Your phone should now reboot into your new ROM. (First boot may take up to 5-10 min.)
Updating coming from a previous version of the rom (This includes coming from a MIUI 12/A11 stable version of the MiuiMix ROM. Dirty flash, only stable over stable or weekly over weekly. Never weekly over stable or vice versa.):
(Optional) Backup all the data from your phone you don't want to lose, including the internal storage (photos, messages e.g.) - This is not required for update, you should not lose anything, but it's a good safe practice anyway.
Boot your phone into fastboot (bootloader) mode
Connect the phone to PC (make sure you have the correct drivers installed for fastboot mode)
Run the "fastboot_update_rom" script/batch for your platform (windows/linux/macos).
The ROM will now be updated on your phone automatically.
You are done. Your phone should now reboot into your updated ROM. (First boot may take up to 5-10 min.)
It is recommended to deactivate ALL magisk modules before updating.
DOWNLOAD Link
Hello friends, I really apreciate this ROM but I have a problem... not only with this ROM, but with all Xiaomi ROMs...
I'm a tester, I like to test a lot of aplications, ROMs, anything. Of course, I need a system backup in case something goes wrong... But I cannot backup in custom recovery (TWRP or OrangeFox) because Data partition cannot be mounted, it shows "0 MB"...
I tried everything found on google but nothing works... the same 0 MB data partition... I even tried this in fastboot:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
but powershell or cmd shows "--disable-verity unrecognized option"
Please, can anybody help me? Thank you.
Hellera said:
Hello friends, I really apreciate this ROM but I have a problem... not only with this ROM, but with all Xiaomi ROMs...
I'm a tester, I like to test a lot of aplications, ROMs, anything. Of course, I need a system backup in case something goes wrong... But I cannot backup in custom recovery (TWRP or OrangeFox) because Data partition cannot be mounted, it shows "0 MB"...
I tried everything found on google but nothing works... the same 0 MB data partition... I even tried this in fastboot:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
but powershell or cmd shows "--disable-verity unrecognized option"
Please, can anybody help me? Thank you.
Click to expand...
Click to collapse
In twrp and ofox it's not possible.
You have to be encrypted to do that in Recovery with android A12 , I think also in A11.
But I'll think you can do it if booted and rooted with alphabackup
Laptapper said:
In twrp and ofox it's not possible.
You have to be encrypted to do that in Recovery with android A12 , I think also in A11.
But I'll think you can do it if booted and rooted with alphabackup
Click to expand...
Click to collapse
Thank you @Laptapper, I tried a custom ROM, crDroid with A12 and it works... I can backup/restore everything... with MIUI ROMs doesn't work.
@Hellera Those ROMs likely don't use encrypted data partition (which is a security risk). If you disable any screen locks you might have in your MIUI ROM, you should be able to see and use the data partition just fine (I did that with TWRP 3.6 and MiuiMix 13.0.2). However, whether or not you will be able to correctly backup and (more importantly) restore a ROM like that to a working state in case you need to has to be tested more.
Also once you set up a screen lock again, the data partition gets encrypted again.
Case_ said:
@Hellera Those ROMs likely don't use encrypted data partition (which is a security risk). If you disable any screen locks you might have in your MIUI ROM, you should be able to see and use the data partition just fine (I did that with TWRP 3.6 and MiuiMix 13.0.2). However, whether or not you will be able to correctly backup and (more importantly) restore a ROM like that to a working state in case you need to has to be tested more.
Also once you set up a screen lock again, the data partition gets encrypted again.
Click to expand...
Click to collapse
@Case_ I never use any screen locks and I'm on MiuiMix 13.0.2, twrp and ofox doesn't see data partition, 0 MB... I think is about the android version 12... with version 12.5.7 android 11 I had not such problems... Is frustrating...
@Hellera Well, like I said, for me disabling fingerprint and PIN worked on MiuiMix 13.0.2. I guess there are more reasons why the data partition might stay encrypted even if you disable any screen locks.

[ROM][Huawei][13] LeaOS - Lineage 20.0 for Huawei device (EMUI 9.1 version)

Non-Official Lineage 20.0 for EMUI 9 Huawei (ANE, FIG, POT, VTR, STF)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LeaOS is a project which based on LineageOS 20.1 with Andy Yan's and TrebleDroid GSI patches. I have added my personnals patches for Huawei devices : Encryption, Signal Strengh, Speed Boot, Assisted GPS, NFC, CAST/Miracast, Media App fixes, Camera HDR, SafetyNet etc..)
Changelog :
LeaOS Maarch 2023 version
Move to Android r35 (SPL Maarch)
Add offline charging
Add spoof model to pass safetynet
LeaOS February 2023 version
First release
Pre-requisite :
You must have TWRP installed if you want install patch. and a phone with unlock bootloader
Installation (crypt or uncrypt)
Download the version that corresponds to your Huawei phone model here and extract img file. You can choose with ou without GoogleApps
Flash system image : fastboot flash system <drag system.img here>
Flash twrp image: fastboot flash recovery_ramdisk <drag twrp img here>
Boot into twrp: power + vol+ while NOT connected to pc
Resize system: Wipe > Advanced Wipe > System > Repair or Change File System > Resize File System > Swipe
Wipe cache, dalvik/art cache, internal storage
Wipe data
(option) Install DRM patch for EMUI 9.1 to support DRM : 8-Huawei-FixPreav-AB-v1.3-signed.zip
(option) Install single modem patch for multi-sim device : 11-Huawei-MonoSim-AB-v1.1-signed.zip
reboot to System and set up the phone with Lineage first start assistant.
Enjoy !!!
Source Code:
https://github.com/Iceows
ROM OS Version: Android 13
ROM Kernel: Linux Huawei 4.9.148 or Phenix 4.9.319
ROM Firmware Required: EMUI 9.1
Based On: Lineage 20.0 and TrebleDroid
Credits:
@Frax3r (Testing)
@PHH
@eremitein
@RakinTheGreat (GCam)
@TureX (Kernel)
And all the others who tested my patches and helped me improve this ROM
Support Group
Channel update
Testting on FIG-XXX, will post results
Mafworld said:
Testting on FIG-XXX, will post results
Click to expand...
Click to collapse
How did you manage to install it? I began with EMUI 9.1 .115, unlocked the bootloader flashed the system, flashed twrp, resized system partition, wiped cache, dalvik/art cache, internal storage, installed stock recovery but I can't wipe data. It says reset failed. As far as I remember not wiping data from stock recovery wont work, phone is just stuck in a TWRP loop
EDIT: Well it just booted right in without formatting data. Guess it's fine
Shume said:
How did you manage to install it? I began with EMUI 9.1 .115, unlocked the bootloader flashed the system, flashed twrp, resized system partition, wiped cache, dalvik/art cache, internal storage, installed stock recovery but I can't wipe data. It says reset failed. As far as I remember not wiping data from stock recovery wont work, phone is just stuck in a TWRP loop
EDIT: Well it just booted right in without formatting data. Guess it's fine
Click to expand...
Click to collapse
Not need reset data from stock recovery
AltairFR said:
Not need reset data from stock recovery
Click to expand...
Click to collapse
Well the storage isn't accessible through the file manager, 0 space for images, can't download from browser, and if data is wiped from twrp the device loops into twrp
EDIT: Wiping data from twrp and reflashing the stock recovery took me out of the loop, everything seems to be working now. I'll report bugs if I find any
Shume said:
Well the storage isn't accessible through the file manager, 0 space for images, can't download from browser, and if data is wiped from twrp the device loops into twrp
EDIT: Wiping data from twrp and reflashing the stock recovery took me out of the loop, everything seems to be working now. I'll report bugs if I find any
Click to expand...
Click to collapse
Can you upload stock recovery. It just boots in twrp but it is frozen
acidhell said:
Can you upload stock recovery. It just boots in twrp but it is frozen
Click to expand...
Click to collapse
Its on Haky86's sourceforge
Does anyone know how can I get root access with this custom ROM? I need recovery.img file but I don't know how to get it. Appreciate all the help.
Why you say recovery ? Just enable adb in root mode
When I was on EMUI 9.1 I extracted recovery image from UPDATE.APP so i could root with magisk. I figured I'd do the same now that I am on this custom ROM but yeah, got stuck.
I have many Bluetooth disconnections. In order to make a connection I have to stop Aufio FX, then scan bluetooth device and untick HD audio. After a restart I have to do these steps all over again.
Can I use this on EMUI 12?
I managed to install it on FIG-LX1, but my screen constantly goes blurry for a few seconds and then goes back to being sharp. Any fix for that?
Hello, any bugs/not working?
Everything works fine, I don't have any issue with my P Smart 2018 (FIG-LX1).
However, I lost a huge amount of time to root my phone. And I don't succeed. Does anyone have tutorial/information to help ?
JeyJer said:
Everything works fine, I don't have any issue with my P Smart 2018 (FIG-LX1).
However, I lost a huge amount of time to root my phone. And I don't succeed. Does anyone have tutorial/information to help ?
Click to expand...
Click to collapse
Root with magisk
Skole said:
Does anyone know how can I get root access with this custom ROM? I need recovery.img file but I don't know how to get it. Appreciate all the help.
Click to expand...
Click to collapse
As Skole previously, and according to the official Magisk procedure, I should have the "recovery.img" file to patch with Magisk. Unfortunately, this file is nowhere ?
-----------------------
EDIT: after discussing with @Skole yesterday (thank you again!), I finally got the point. If you want to root your FIG-LX1, you should download the official Huawei's stock ROM and then extract the RECOVERY_RAMDIS.img from it (you can use tools like Huawei Update Extractor to do so).
Then, use Magisk to patch the RECOVERY_RAMDIS.img file. At last, you should flash it in fastboot mode with the command
Bash:
fastboot flash recovery_ramdisk /path/to/magisk_patched.img
Note that the command below doesn't work
Bash:
fastboot flash recovery /path/to/magisk_patched.img
Next, when your phone is off, press Power + Vol+ buttons ; realease them when you see the splash screen Huawei.
You can follow this popular tutorial to root your phone, but keep in mind the advices above
If something went wrong (like me yesterday ), look at the "dload" method to unbrick your phone thanks to EMUI !
Merci beaucoup AltairFR for LeaOS ! You and Skole give my huawei a new life !
Hello, I have been trying to install this with no luck. I have an FIG-LX1 (bootloader & FRP unlocked) with TWRP already installed.
I'm stuck on the second step, where I need to flash the .img file I downloaded. This is the output I get from fastboot flash system LeaOS-20.0-20230331-iceows-google-fig.img: (the same also happens with the image that doesn't have gapps)
Code:
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 13.743s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
Can someone point me in a direction to go? I've been googling for hours with no avail.
(the phone currently cannot boot into any OS. only TWRP I got from this post)
kuylar said:
Hello, I have been trying to install this with no luck. I have an FIG-LX1 (bootloader & FRP unlocked) with TWRP already installed.
I'm stuck on the second step, where I need to flash the .img file I downloaded. This is the output I get from fastboot flash system LeaOS-20.0-20230331-iceows-google-fig.img: (the same also happens with the image that doesn't have gapps)
Code:
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 13.743s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
Can someone point me in a direction to go? I've been googling for hours with no avail.
(the phone currently cannot boot into any OS. only TWRP I got from this post)
Click to expand...
Click to collapse
Your system partition is two small, try to install leao-phh without gapps to see if boot
I think your system partition is too small.
You can use this tool. https://forum.xda-developers.com/t/huawei-partition-kit-enlarge-system-partition.4545993/ made by AltairFR pretty sure.
You will need OS first , you can install this one without google aps. https://forum.xda-developers.com/t/...fig-lx1-leaos-phh-android-13-version.4558685/

How To Guide ROOT REALME GT2 (RMX3312) in 10 minutes

REQUIREMENTS - BL UNLOCKED
You need to be on VERSION : RMX3312_11.C.12_IN_202304230924
If not on RMX3312_11_C.12 version - download the entire OTA PACKAGE from the above link & LOCAL INSTALL
Reboot to Bootloader adb reboot bootloader or Power + Volume Down
Take the ROOT BOOT image from the zip file given below and PASTE it in platform tools folder
FLASH the ROOT BOOT IMAGE fastboot flash boot RMX3312_11.C.12_ROOTBOOT.img
Type - fastboot reboot
Finished - Now your Realme GT2 - RMX3312 is now ROOTED!
P.S. : FLASH ON BOTH SLOTS
To keep ROOT when you receive an OTA update
DOWNLOAD THE OTA UPDATE
Let it UNZIP
When it shows - INSTALL / REBOOT TO INSTALL option, put to recents - Open MAGISK
There in MAGISK - SELECT THE INSTALL OPTION on the TOP RIGHT
& then select INSTALL TO INACTIVE SLOT (AFTER OTA) OPTION
Click on OK on the POP-UP MENU in MAGISK
NOW THE DEVICE WILL REBOOT - UPDATE TO THE LATEST OTA & STILL KEEP ROOT!
DOWNLOADS : Both STOCK & ROOT boot images are attached below in one ZIP FILE!
Each Boot Image is 192MB & the compressed ZIP FILE below is 72.6MB.
NOTE : I'm NOT RESPONSIBLE FOR BRICKS, STONES, BLASTS, WIPES etc. of RMX3312
Thank you of the guide.
Just questions, what is meant by "P.S. : FLASH ON BOTH SLOTS"?
and What is the SafetyNet status?
gx7x said:
Thank you of the guide.
Just questions, what is meant by "P.S. : FLASH ON BOTH SLOTS"?
and What is the SafetyNet status?
Click to expand...
Click to collapse
He means you need to run the flash boot command for each slot
for instance your system runs on a slot, as soon as you type the
fastboot flash boot [boot image]
if it shows writing boot_a
then you need to type
fastboot flash boot_b [boot image]
to flash in the b slot also
if it shows writing boot_b
then you need to type
fastboot flash boot_a [boot image]
to flash in the a slot also
and you can pass the safteynet easily even when in root, u can use zygisk and magiskhide to pass the safteynet and you can run any banking app you want
Please do not use the boot images provided if you have not updated to the current latest version
Note: EU version boot image might be different so don't try
p.s you can extract boot images yourself from any version you want!
Stano36 said:
How to extract images from OTA zip files:
Extract the OTA zip file
Download and extract payload-dumper-go
Drag and drop payload.bin on payload-dumper-go executable
Spoiler: Video instructions
Click to expand...
Click to collapse
HIGHLY recommend to extract boot for your version, tnx to Stano36 we have well prepared collation of update. Thanks to Prajwal_Beast for this guide!
I have some questions about "a" and "b" partitions, where can I found some information why we have two partitions and all have two or some of them and etc..
b0nb0n3v said:
HIGHLY recommend to extract boot for your version, tnx to Stano36 we have well prepared collation of update. Thanks to Prajwal_Beast for this guide!
I have some questions about "a" and "b" partitions, where can I found some information why we have two partitions and all have two or some of them and etc..
Click to expand...
Click to collapse
We have two partitions so that if one fails the other can safely boot however most of us are careless and flash on both partitions so it's not really helpful for us
How to root gt 2 running on pixel os?
_PsyDuck_ said:
How to root gt 2 running on pixel os?
Click to expand...
Click to collapse
extract the pixel os file & patch the boot image using magisk & flash the magisk patched boot image
Thanks

Categories

Resources