Hi, I'm trying to root my phone, I already unlocked the bootloader and now I want to root it, I'm trying with the method to patch the boot.img with magisk manager and then flash It via fastboot, but I can't find the firmware! Does anyway have the stock boot.img of the firmware COL-L29 9.0.0.162(C432E4R1P9)
albysprx said:
Hi, I'm trying to root my phone, I already unlocked the bootloader and now I want to root it, I'm trying with the method to patch the boot.img with magisk manager and then flash It via fastboot, but I can't find the firmware! Does anyway have the stock boot.img of the firmware COL-L29 9.0.0.162(C432E4R1P9)
Click to expand...
Click to collapse
Here is COL-L29 9.0.0.162(C432E4R1P9) FullOTA-MF one file firmware:
http://update.hicloud.com:8180/TDS/...86/g1699/v216022/f1/full/update_full_base.zip
It's registered now on servers as COL-LGRP2-OVS 9.0.0.162
I can confirm that is the one file FullOTA-MF pushed to devices on COL-L29C432E4R1P9B159.
Simple OTA firmware is v216021.
Where did you get that from?
It's still unavailable in Huawei update finder for me.
leAndroid91 said:
Where did you get that from?
It's still unavailable in Huawei update finder for me.
Click to expand...
Click to collapse
oslo83 said:
I can confirm that is the one file FullOTA-MF pushed to devices on COL-L29C432E4R1P9B159.
Click to expand...
Click to collapse
It is pushed to mine and the http link was grabbed via adb logcat.
oslo83 said:
Here is COL-L29 9.0.0.162(C432E4R1P9) FullOTA-MF one file firmware:
http://update.hicloud.com:8180/TDS/...86/g1699/v216022/f1/full/update_full_base.zip
It's registered now on servers as COL-LGRP2-OVS 9.0.0.162
I can confirm that is the one file FullOTA-MF pushed to devices on COL-L29C432E4R1P9B159.
Simple OTA firmware is v216021.
Click to expand...
Click to collapse
there isn't ramdisk.img in this firmware
{
"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"
}
albysprx said:
there isn't ramdisk.img in this firmware
Click to expand...
Click to collapse
There is no ramdisk anymore on pie emui9.
On emui9, it's recovery_ramdisk image you have to patch with magisk.
Then flash it to recovery_ramdisk partition.
Then boot with root access by booting to recovery mode (without USB cable: hold VolumeUp before device boots).
oslo83 said:
There is no ramdisk anymore on pie emui9.
On emui9, it's recovery_ramdisk image you have to patch with magisk.
Then flash it to recovery_ramdisk partition.
Then boot with root access by booting to recovery mode (without USB cable: hold VolumeUp before device boots).
Click to expand...
Click to collapse
so the adb command changes?
I have the patched_boot.img
what I need to type on adb?
After that, I boot the phone from the recovery mode and install magisk directly from magisk manager, right?
thanks
albysprx said:
so the adb command changes?
I have the patched_boot.img
what I need to type on adb?
After that, I boot the phone from the recovery mode and install magisk directly from magisk manager, right?
thanks
Click to expand...
Click to collapse
You could install MagiskManager before.
The fastboot command changes to
.\fastboot.exe flash recovery_ramdisk patched_boot.img
Read some magisk documentation on pie.
Rooted!
COL-L29 9.0.0.162(C432E4R1P9)
here are my steps:
1- Downloaded the firmware by oslo83 (thanks)
2- Extracted the recovery_ramdis.img with Huawei Update Extractor
3- Copied the recovery_ramdis.img to my phone and patched with magisk manager
4- Copied the patched_boot.img into the platform-tools folder into my PC
5- Rebooted the phone in bootloader mode with the command: adb shell reboot bootloader
6- Flashed the patched_boot.img with fastboot:
fastboot devices
fastboot flash recovery_ramdisk patched_boot.img
fastboot reboot
7- Immediatly disconnected usb cable
8- After reboot, with magisk manager, installed magisk with a direct install
9- Profit!
Thanks everyone for the help!
EDIT: SafetyNet OK!
The next pushed approved FullOTA-MF for Honor10 COL-L29 C432 should be :
COL-LGRP2-OVS 9.0.0.177
http://update.hicloud.com:8180/TDS/...86/g1699/v209463/f1/full/update_full_base.zip
@oslo83
So it's safe to update from COL-L29 9.0.0.162(C432E4R1P9) to COL-LGRP2-OVS 9.0.0.177
??
It's safe but:
-B177 fingerprint is not approved by google yet so safetynet's cvs check fail for now.
-it *could* never be pushed by OTA and also following OTA updates *could* not be pushed to those with B177
-there is a *bug* with huawei wallet added in this build : when you're not logged at boot, it launch the huawei connect screen. This could be fixed via root or via adb.
Related
Here is the full update package for CM 11's Build XNPH22Q as well as the OTA update zip (The OTA cannot be flashed alone, you need o come from a previous build to flash the zip)
For the fastboot image zip you flash each of the images in fastboot DO NOT FLASH IN RECOVERY: Unzip the file and then run each of the commands
Code:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Download links:
Full Fastboot Img zip: http://d-h.st/qe5
OTA Zip: http://d-h.st/o9I
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it, or it kills your neighbor's dog.. It was the other guy... I swear.... Flash at your own risk
Thx for last update... Oppo users will be happy...
:good:
It may too be a server problem from androidfilehost but somehow the download is broken in a strange way. On the download page it says that the file is about 4xx.xx MB but when you download it, it's only 0B and of course you can not open it. So, I want to request if you could upload the fastboot image .zip to an alternative web host like MEGA or Google Drive. I believe not only I would appreciate it very much!
Thank you in advance!
Cheers
iH8ra!n
Apparently this isn't the production build, but the final pre-production build. Phones sold to public will be sold with the next update installed, at least that's implied by the message:
This is the final pre-production release for the OnePlus One and will prepare your device for the production build to follow.
Click to expand...
Click to collapse
iH8ra!n said:
It may too be a server problem from androidfilehost but somehow the download is broken in a strange way. On the download page it says that the file is about 4xx.xx MB but when you download it, it's only 0B and of course you can not open it. So, I want to request if you could upload the fastboot image .zip to an alternative web host like MEGA or Google Drive. I believe not only I would appreciate it very much!
Thank you in advance!
Cheers
iH8ra!n
Click to expand...
Click to collapse
I uploaded them to dev host now. Mega doesn't let me see how many people have DL'ed it
Dev Host links are working, thanks a lot
thanks for your post, awaite invite, then buying and testing.
anyone mind adb pulling mixer_paths.xml, media_profiles.xml and audio_conf from this final build for me?
very much appreciated
ayysir said:
anyone mind adb pulling mixer_paths.xml, media_profiles.xml and audio_conf from this final build for me?
very much appreciated
Click to expand...
Click to collapse
Sure.. where is the audio_conf? In that same dir I have audio_effects.conf, audio_policy.conf is it in a different dir?
graffixnyc said:
Sure.. where is the audio_conf? In that same dir I have audio_effects.conf, audio_policy.conf is it in a different dir?
Click to expand...
Click to collapse
should all be in system/etc folder
ayysir said:
should all be in system/etc folder
Click to expand...
Click to collapse
yeah then it's not there only audio_policy.conf and audio_effects.conf
Media_profiles: https://www.dropbox.com/s/3imu2xo4k2k6ebb/media_profiles.xml
mixer path: https://www.dropbox.com/s/eqrd0a1z0q07pbb/mixer_paths.xml
Audio effects: https://www.dropbox.com/s/eyopy7gcuic30oq/audio_effects.conf
Audio policy: https://www.dropbox.com/s/94ewo086v40fn9o/audio_policy.conf
thank you sir
if I ever want to go back to stock everything for RMA purposes, all I need to do is load the fastboot img and it'll restore the phone to factory condition?
Hi graffixnyc,
I wanted my OnePlus One flashed with this rom: http://forum.xda-developers.com/showthread.php?t=2772511
I'm locked in bootloop.
And now I can not go back to cyanogenmod cm11s via your method.
Look at my screen :
{
"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"
}
webgrafx said:
Hi graffixnyc,
I wanted my OnePlus One flashed with this rom: http://forum.xda-developers.com/showthread.php?t=2772511
I'm locked in bootloop.
And now I can not go back to cyanogenmod cm11s via your method.
Look at my screen :
Click to expand...
Click to collapse
Your bootloader is locked.. You need to unlock your bootloader first..Hence the "Failed.. device not unlocked" message you see there.
graffixnyc said:
Your bootloader is locked.. You need to unlock your bootloader first..Hence the "Failed.. device not unlocked" message you see there.
Click to expand...
Click to collapse
Yet it is unlocked with this command: fastboot oem unlock
But I can more TWRP restored and told me that I have not installed OS
Not possible to give me an ADB command sideload with zip cm11s?
webgrafx said:
Yet it is unlocked with this command: fastboot oem unlock
But I can more TWRP restored and told me that I have not installed OS
Not possible to give me an ADB command sideload with zip cm11s?
Click to expand...
Click to collapse
It's not unlocked.. That's why you are getting that failed error.. I don't know why it's not unlocked if you ran fastboot oem unlock but that failed message in your screen shot means the bootloader is not unlocked. Sorry, I don't have time to make a zip
Sent from my HTC One_M8 using Tapatalk
For the italian users: http://www.smartylife.net/guida-installazione-cm11s-oneplus-one/
Hi Graffix
question, once I have flashed the fastboot zip using the individual commands, I can flash teh OTA zip using TWRP or stock recovery ? or is there is any method to flash it?
thanks for your help,
I have ver CM11.XNPH16Q (April 16) and wanted to upgrade.
Can I have to say as?
thanks
@graffixnyc
Explain in detail please
Ok so i found out that you cant root this phone without flashing vbmeta.img
So its pretty simple to root your phone, here are the steps:
1. Patch your boot.img with magisk
2. download vbmeta.img and put it into your adb folder (do the same with patched boot.img)
3. in adb type: adb reboot bootloader
4. check if device is connected, then type fastboot flash boot patched_boot.img [doesn't matter whats the name]
5. after flashing the boot.img, flash the vbmeta.img by typing fastboot flash vbmeta vbmeta.img [as said i think the name doesn't matter]
6. Reboot by fastboot reboot and you are done!
ofc i will give you the vbmeta.img download link:
vbmeta
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Maybe i will post a screenshot that my redmi 9c is rooted but im lazy so pog
EDIT: i haven't checked on this forum post since years because i hard bricked my redmi 9c by flashing auto ported twrp through one app (i think it was called flahify idk). If i am gonna get this phone unbricked, I may do some more updates regarding my phone status, but rn I am using moms old phone. Anyways, I hope you have a great day.
Ok so I'm not that lazy but here you go
{
"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"
}
ALSO YOU NEED UNLOCKED BOOTLOADER!!!
Why your vbmeta file type is not .img file ? It's .bin file. So..... how to flash bin file ?
working without opening bootloader?
I have questions that needs verification:
1. Where do i get/extract `boot.img`?
Answer: i dont know
2. How to patch `boot.img` with magisk?
Answer: Download apk from magisk website and use the app to patch
3. Where do i get `vbmeta.img` file?
Answer: From OP post
4. How to unlock bootloader?
Answer:
Code:
fastboot oem unlock
5. How to flash `boot.img`?
Answer:
Code:
fastboot flash boot patched_boot.img
5. How to flash `vbmeta.img`?
Answer:
Code:
fastboot flash vbmeta vbmeta.img
working perfect
AdamNotFunTV said:
Ok so i found out that you cant root this phone without flashing vbmeta.img
Click to expand...
Click to collapse
How did you manage to get it working with this vbmeta.img file ? Did you had to alter the original vbmata.img in a specific way ? If yes, what would have I to do if I wanted to patch the original file myself ?
Worked for me perfectly.
Downloaded the stock ROM for my Redmi 9C (V12.0.7.0.QCRMIXM) from here: https://www.xda-developers.com/down...ut-several-xiaomi-redmi-mi-poco-devices/amp/#
Extracted the boot.img from the download, patched it with Magisk then flashed the patched boot file followed by vbmeta.img via adb.
Very easy.
How I can get boot.img file for my redmi 9C?
it is safe to unlock bootloader with adb tools or I should use mi unlock tool instead?
will it not soft brick my redmi 9C after unlocking bootloader with adb tools?
Is it really safe method to root redmi 9C?
Tnuctipun said:
Worked for me perfectly.
Downloaded the stock ROM for my Redmi 9C (V12.0.7.0.QCRMIXM) from here: https://www.xda-developers.com/down...ut-several-xiaomi-redmi-mi-poco-devices/amp/#
Extracted the boot.img from the download, patched it with Magisk then flashed the patched boot file followed by vbmeta.img via adb.
Very easy.
View attachment 5193225View attachment 5193211
View attachment 5193747
What flashed you first?
Patched_boog.img or vbmeta.img
Please reply
Click to expand...
Click to collapse
First I flashed patched_boot.mg.
Then I flashed vbmeta.img.
Tnuctipun said:
First I flashed patched_boot.mg.
Then I flashed vbmeta.img.
Click to expand...
Click to collapse
Do you successfully rooted your redmi 9C?
Is there no problem after rooting redmi 9C?
What model do you own?
Redmi 9C Global or Redmi 9C NFC?
Please reply
@technical said:
Do you successfully rooted your redmi 9C?
Is there no problem after rooting redmi 9C?
What model do you own?
Redmi 9C Global or Redmi 9C NFC?
Please reply
Click to expand...
Click to collapse
Yes, I've successfully rooted my phone and no, I've had no problems whatsoever. Everything is copacetic.
My phone is the Redmi 9c running the global MIUI 12.
Are you really sure you want and/or need to root your phone?
Tnuctipun said:
Yes, I've successfully rooted my phone and no, I've had no problems whatsoever. Everything is copacetic.
My phone is the Redmi 9c running the global MIUI 12.
Are you really sure you want and/or need to root your phone?
Click to expand...
Click to collapse
Yes I really want to root my redmi 9C Global
Tnuctipun said:
Worked for me perfectly.
Downloaded the stock ROM for my Redmi 9C (V12.0.7.0.QCRMIXM) from here: https://www.xda-developers.com/down...ut-several-xiaomi-redmi-mi-poco-devices/amp/#
Extracted the boot.img from the download, patched it with Magisk then flashed the patched boot file followed by vbmeta.img via adb.
Very easy.
Click to expand...
Click to collapse
Please give us the boot file. I wouldn't like to download the whole firmware because have a limited data plan
Can someone provide the boot.img for Redmi 9C.
Never mind. I give you a boot.img that was extracted from angelica_global_images_V12.0.8.0.QCRMIXM Firmware, this file boot.img has not been patched yet.
Xiaomi Redmi 9C - Google Drive
drive.google.com
ivan jo hann said:
Please give us the boot file. I wouldn't like to download the whole firmware because have a limited data plan
Click to expand...
Click to collapse
As far as I know, you need the boot file for your specific version of MIUI.
No need to download the complete ROM, you can extract the boot.img file using online zip extractors (google).
Tnuctipun said:
As far as I know, you need the boot file for your specific version of MIUI.
No need to download the complete ROM, you can extract the boot.img file using online zip extractors (google).
Click to expand...
Click to collapse
Yes, and your firmware version of MIUI is the same as mine.
{
"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"
}
#SHRP A10/11
Download : https://mega.nz/file/gpgWmBwa#MqToq4Htapb4cd-nwzcBNbpAbuBD_TREbPvK9bFHsmI
Features :
-f2fs support(flash f2fs patcher from tweaks section and convert data and catch(optional) to f2fs to use f2fs).Must use f2fs supposed Kernel.
-Can flash and backup system,vendor and product.
-You can flash gsi and ub port image directly.
-Can resize system and vendor partition to flash Large image size ..
(Flash system vendor resize zip from tweaks and reboot to recovery
-system, vendor, product rw support (flash system rw zip from tweaks section)
Notes :
-After resize you can flash system up to 3.4 gb and vendor up to 900 mb.
-Disable shrp theme to prevent bootloop.
-If you are in miui you need to flash patch vbmeta from below link.
http://transfer.sh/e3LV0n/unipatchedvbmeta_twrp.zip
Flash it after flash the recovery..
Install :
Download and flash from any recovery or extract and flash recovery.img from pc
Sorce (twrp tree) : https://github.com/Arafattex/device_xiaomi_lancelot
Screen shot :
What is the solution to the problem of returning the official recovery after a reboot? Knowing that I tried flashing the Magisk, but the phone does not turn on (bootloop)
Az.az1 said:
What is the solution to the problem of returning the official recovery after a reboot? Knowing that I tried flashing the Magisk, but the phone does not turn on (bootloop)
Click to expand...
Click to collapse
It never happened which version of magisk you flash ? is you are miui if yes flash patch vbmeta...
http://transfer.sh/e3LV0n/unipatchedvbmeta_twrp.zip
how to disable theme?
EDIT: nvm I got it, although installing Magisk v23 from official site does bootloop the phone.
Removing it solved it and got my phone boot.
Shas45558 said:
Il n'est jamais arrivé quelle version de magisk vous flashez ? est-ce que vous êtes miui si oui flash patch vbmeta...
http://transfer.sh/e3LV0n/unipatche...sh/e3LV0n/unipatchedvbmeta_twrp.zip
[/QUOTE]
Click to expand...
Click to collapse
http://1- thanks for your reply
2- I have the latest version of Magisk 23.0
3-I'm on the official ROM
4- The link you sent does not work
64Timothy121 said:
how to disable theme?
EDIT: nvm I got it, although installing Magisk v23 from official site does bootloop the phone.
Removing it solved it and got my phone boot.
Click to expand...
Click to collapse
Theme is disabled no need
64Timothy121 said:
how to disable theme?
EDIT: nvm I got it, although installing Magisk v23 from official site does bootloop the phone.
Removing it solved it and got my phone boot.
Click to expand...
Click to collapse
How did you remove it? I got a bootloop too after installing Magisk from SHRP and I can only go to fastboot, but when I flash SHRP again the bootloop is still there and it won't go into recovery anymore.
ecvarts said:
How did you remove it? I got a bootloop too after installing Magisk from SHRP and I can only go to fastboot, but when I flash SHRP again the bootloop is still there and it won't go into recovery anymore.
Click to expand...
Click to collapse
I reflashed and booted into the img, yet the phone actually booted into the system. I hit the combo for recovery and somehow I got back in this time and it says Magisk is installed. Weird... But if it works...
Could someone re-upload the vbmeta patch?
This link no longer works... https://transfer.sh/e3LV0n/unipatchedvbmeta_twrp.zip
Thank you very much!
+1 vbmeta_twrp link is not working
+1 I‘d like to use this rom,but can you give me another recovery link?tks
Here is the detailes guide to install This recovery.
Go to Fastboot mode
Run the following commands.
fastboot flash recovery recoveryname.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
In the recovery install SHRP img file
then install vbmeta_patched img file
then reboot to recovery
All files are attached.
Don't forget to click Thanks button
rakesh.aggarwal said:
Here is the detailes guide to install This recovery.
Go to Fastboot mode
Run the following commands.
fastboot flash recovery recoveryname.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
In the recovery install SHRP img file
then install vbmeta_patched img file
then reboot to recovery
All files are attached.
Don't forget to click Thanks button
Click to expand...
Click to collapse
Hello, I followed this procedure and my phone (Redmi 9) got stuck in a bootloop, I can't even get into fastboot anymore. I might be able to recover it using EDL however, but most likely I will have to send it to authorized repair. RIP.
Update: Not even the guy I sent the phone to repair could fix it, RIP.
zerowhy said:
Hello, I followed this procedure and my phone (Redmi 9) got stuck in a bootloop, I can't even get into fastboot anymore. I might be able to recover it using EDL however, but most likely I will have to send it to authorized repair. RIP.
Update: Not even the guy I sent the phone to repair could fix it, RIP.
Click to expand...
Click to collapse
I have attached the unbricking tool here. It worked for me. If you just chose the correct CPU architecture, it will work for any mediatek phone.
The above guide was for Shiva(Poco M2) not for Redmi 9.
Hmm.. I can't seem to flash the official firmware with this recovery. It just shows an error when flashing it. I am on PixelPlus UI 12.1.
MaxisMan said:
Hmm.. I can't seem to flash the official firmware with this recovery. It just shows an error when flashing it. I am on PixelPlus UI 12.1.
Click to expand...
Click to collapse
What kind of errors?
Sorry for a stupid question. But is Flash button has the same function as Install button when installing *.zip patch file? This is the 1st time I'm using this recovery
My REALME 7 PRO I always return to TWRP mode every time boot. At first after I was flashing twrp 3.5.0 running normally, after I tried to flash with magisk v21.4 and no_verity_opt_encrypt.zip, then every time booting always returned to TWRP mode. Please help what should I do?
SaggafF MaoeX said:
My REALME 7 PRO I always return to TWRP mode every time boot. At first after I was flashing twrp 3.5.0 running normally, after I tried to flash with magisk v21.4 and no_verity_opt_encrypt.zip, then every time booting always returned to TWRP mode. Please help what should I do?
Click to expand...
Click to collapse
What did you do? What ROM?
Need more information.
BTW Try the new version of Magisk v23 and TWRP v3.5.1 (if using Android 10).
deserted said:
What did you do? What ROM?
Need more information.
BTW Try the new version of Magisk v23 and TWRP v3.5.1 (if using Android 10).
Click to expand...
Click to collapse
I use the Realme 7 Pro Stock ROM with Android 11. I tried to root my realme with the mentioned tool above.The bootloader is open, TWRP has been installed and normal before I flash with Magisk V21.4 and no_verity_opt_encrypt.zip.
Try to flash patched boot image.
You need vbmeta.img and patched_boot.img
Rose in Realme 7 Pro | Discussion™
t.me
606.36 MB folder on MEGA
17 files
mega.nz
Reboot your phone to bootloader:
adb devices
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot patched_boot.img
fastboot reboot recovery
deserted said:
Try to flash patched boot image.
You need vbmeta.img and patched_boot.img
Rose in Realme 7 Pro | Discussion™
t.me
606.36 MB folder on MEGA
17 files
mega.nz
Reboot your phone to bootloader:
adb devices
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot patched_boot.img
fastboot reboot recovery
Click to expand...
Click to collapse
What file should I choose? Lastly I know my realme 7 pro, use the Android 11 version with the last patch on October 5, 2021
{
"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"
}
SaggafF MaoeX said:
What file should I choose? Lastly I know my realme 7 pro, use the Android 11 version with the last patch on October 5, 2021
View attachment 5483495
Click to expand...
Click to collapse
A = android 10
C = android 11 <-- for you
Number = version of Android you have.
It will be faster if you join the Realme 7 Pro channel on Telegram.
It's solved. You are awesome. Thank you for your help.
deserted said:
Try to flash patched boot image.
You need vbmeta.img and patched_boot.img
Rose in Realme 7 Pro | Discussion™
t.me
606.36 MB folder on MEGA
17 files
mega.nz
Reboot your phone to bootloader:
adb devices
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot patched_boot.img
fastboot reboot recovery
Click to expand...
Click to collapse
It is now on android 11, 32 storage, sim support
Current guides aren't enough for me
m
Civil123y said:
Current guides aren't enough for me
Click to expand...
Click to collapse
why? have unlocked bootloader already ? please show your download mode screen.!
For this step Yes i unlocked successfully
What i did next is flashing whole ap patched with bl cp csc
I have root and r/w system.
Whole AP or just boot.img?
Abish4i said:
Whole AP or just boot.img?
Click to expand...
Click to collapse
Whole( i tried boot.img once it works without system rw)
With whole, i can use mixplorer and lucky patcher to remove system apps completely.
And i didn't succeed running twrp
Civil123y said:
Whole( i tried boot.img once it works without system rw)
With whole, i can use mixplorer and lucky patcher to remove system apps completely.
And i didn't succeed running twrp
Click to expand...
Click to collapse
what your magisk version.? didn't success run or access twrp? how did you installed twrp file?
tom.android said:
what your magisk version.? didn't success run or access twrp? how did you installed twrp file?
Click to expand...
Click to collapse
My tab is 225n,
i used 225 twrp
I flashed it in user data slot once with ap ,,,csc,,,etc
And i tried it in ap slot.
Posts about twrp are a bit vague to me.
Magisk 25.2
I tried 24 also
Could i have done it wrong. I followed guides out there
Civil123y said:
Could i have done it wrong. I followed guides out there
Click to expand...
Click to collapse
Can you show log from ODIN? Did it successfully went through also did you uncheck auto reboot as well as multidisabler after.
Check specifically magisk 24.2
Civil123y said:
Could i have done it wrong. I followed guides out there
Click to expand...
Click to collapse
OK listen carefully this is my trick to install this twrp.
1. don't used latest uses only v.24.x
2. patch magisk the whole ap file. and flash it at AP slot of Odin.
3. flash BL ,CSC in normal way.
4. OK if flash twrp.tar file at USERDATA slot
5. if you not set to disable auto-reboot at Odin option , you must very quickly press and hold power+vol up yourself.
6. if you can't access to twrp ( recovery mode ) in step 5 please uses command > adb reboot recovery
**** please use magisk v24.x only for the 1'st time to access twrp.
Abish4i said:
Can you show log from ODIN? Did it successfully went through also did you uncheck auto reboot as well as multidisabler after.
Check specifically magisk 24.2
Click to expand...
Click to collapse
Odin passed successfully, no errors, (if multidisabler is inside twrp , i can't run twrp at all)
tom.android said:
OK listen carefully this is my trick to install this twrp.
1. don't used latest uses only v.24.x
2. patch magisk the whole ap file. and flash it at AP slot of Odin.
3. flash BL ,CSC in normal way.
4. OK if flash twrp.tar file at USERDATA slot
5. if you not set to disable auto-reboot at Odin option , you must press and hold power+vol up yourself.
6. if you can't access to twrp ( recovery mode ) in step 5 please uses command > adb reboot recovery
**** please use magisk v24.x only for the 1'st time to access twrp.
Click to expand...
Click to collapse
Number 4? Should i flash it with number 3 or i should reboot again to download mode to flash it separately.?
I should use twrp from github 225 for my 225n?
@tom.android couldn't we just skip 5 step.
i.e start without flashing TWRP.
Civil123y said:
Number 4? Should i flash it with number 3 or i should reboot again to download mode to flash it separately.?
I should use twrp from github 225 for my 225n?
Click to expand...
Click to collapse
What is your KG status?
odin slot
1.BL slot. >>bl file from your firmware.
2.AP slot.>>ap file (patch from magisk v24)
3.CP slot.>>cp file from your firmware
4.CSC slot>>csc file from your firmware
( safty first not uses CSC_HOME
5.USERDATA>> twrp.tar
-flash all at the same time.
-Disable auto-restart from odin option
when odin finished flashing you must press and hold (power + vol up.) to access recovery mode.
can't used "multidisabler"???
- another error may be this twrp 225 not for 225N. don't known sorry.
Abish4i said:
@tom.android couldn't we just skip 5 step.
i.e start without flashing TWRP.
What is your KG status?
Click to expand...
Click to collapse
This before flashing, right now
{
"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"
}
Not working after reflashing stock and doing steps.
Civil123y said:
Not working after reflashing stock and doing steps.
Click to expand...
Click to collapse
Use telegram?
And did you use CSC and patched ODIN?
Currently your CSC is ?
Can access recovery mode or not , what showing up.