Xiaomi Redmi 6A root impossible - Xiaomi Redmi 6A Questions & Answers

Hello everyone, problem.
after unbrick procedure
I am with miui 10 android 8.1.0.011019
boot in twrp format data wipe , yes
error failed to mont '/data' ( invalid argument )
install Magisk-v15.3 last line
failed to mont '/data' ( invalid argument)
... done
install MagiskManager-v5.5.5.apk
i don't get root permissions .
where am i wrong? thank you

patrizi said:
Hello everyone, problem.
after unbrick procedure
Click to expand...
Click to collapse
boot in twrp format data wipe , yes
Reboot Twrp
Format again
If still the same error.
Use this tool(does not lock the bootloader) :https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Flash a fastboot rom https://xiaomirom.com/en/rom/redmi-6a-cactus-global-fastboot-recovery-rom/
and install twrp and try again

A thousand thanks . in order to perform the procedure I had to try 4 versions of MiFlash, to find the complete one .
i went back to miui 9.6 android 8.1.0 English / Chinese language .
now everything should be fine.
Thanks again, good evening everyone
same exact problem
failed to mont '/data' ( invalid argument)
... done
possible ?

NOSS8 said:
boot in twrp format data wipe , yes
Reboot Twrp
Format again
If still the same error.
Use this tool(does not lock the bootloader) :https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Flash a fastboot rom https://xiaomirom.com/en/rom/redmi-6a-cactus-global-fastboot-recovery-rom/
and install twrp and try again
Click to expand...
Click to collapse
Drive with fastboot, I'm working on it
do I find on the forum? thank you

patrizi said:
Drive with fastboot, I'm working on it
do I find on the forum? thank you
Click to expand...
Click to collapse
What's the problem now?

NOSS8 said:
What's the problem now?
Click to expand...
Click to collapse
Good morning .
turned on this morning I find:
android system
there's an internal problem with your device. contact your manufacturer for details, ok. with audio notification
pressed ok everything seems to be OK / working
current firmware: miui 9.6 stable 9.6.3.0 (ocbcnfd). android version 8.1.0. android security patch level 2018-05-05
installed with MiFlash20210226 where I selected clean all in automatic configuration.
writes with 70 - 100 seconds the green line does not fill completely, shows reboot alert with pc notification sound, the phone is in fastboot
does not reboot, has not completed writing, the count does not stop I have waited up to 780 seconds does not reboot, does not
complete writing, stopped at that point, I unplugged the cable and restarted manually. as before failed to mont '/ data' (invalid argument)
TWRP always cactus Italian, previously I have tried others without Italian does not format DATA.
still write problem for protection? that zone (date) has not been overwritten.
you can do a deep format (eliminate protection problems) with fastboot or how?
thank you

patrizi said:
Good morning .
turned on this morning I find:
android system
Click to expand...
Click to collapse
Post the Miflash log.
If android 11 Use https://androidfilehost.com/?fid=14655340768118443054

NOSS8 said:
Post the Miflash log.
If android 11 Use https://androidfilehost.com/?fid=14655340768118443054
Click to expand...
Click to collapse
good morning , installed TWRP-3.3.0-0423-REDMI6A-CN-wzsx150
fixed format error , I install Magisk-v15.3 reboot does not install app MagiskManager-v5.5.5.apk goes into error starts in recovery
I try to delete everything again without errors ,
reboot, delete everything again
install lineageos without errors restart ,
vibrates does not turn on, I also tried detach / attach battery it's bricked now,
procedure for recovery
error: status_sec_img_type-mismatch (0xc002002a) hint verified boot is enabled please download signed image (cust-verified.img) or disable verified boot.
searched for info by mistake
everything is correct, i made no mistakes, i have to try with latest version of flasch tool
I can not understand . thank you

patrizi said:
good morning , installed TWRP-3.3.0-0423-REDMI6A-CN-wzsx150
Click to expand...
Click to collapse
If it's this rom, it's Magisk v21.4
https://forum.xda-developers.com/t/rom-unofficial-lineage-os-17-1.4252127/
Redmi 6a(cactus) Download
Magisk: Download
Recovery redmi 6a: TWRP OrangeFox
Google Apps: OpenGApps (use arm/10.0 nano gapps)
Or https://forum.xda-developers.com/t/...6-lineageos-16-0-for-xiaomi-redmi-6a.3982609/
Magisk version should be 19.3 or below only

NOSS8 said:
If it's this rom, it's Magisk v21.4
https://forum.xda-developers.com/t/rom-unofficial-lineage-os-17-1.4252127/
Redmi 6a(cactus) Download
Magisk: Download
Recovery redmi 6a: TWRP OrangeFox
Google Apps: OpenGApps (use arm/10.0 nano gapps)
Or https://forum.xda-developers.com/t/...6-lineageos-16-0-for-xiaomi-redmi-6a.3982609/
Magisk version should be 19.3 or below only
Click to expand...
Click to collapse
I followed all the info for the recovery.
with SP_Flash_Tool I always have the same error
I have tried with different versions of Global Recovery ROM (cactus)
error: status_sec_img_type-mismatch (0xc002002a) hint verified boot is enabled please download signed image (cust-verified.img) or disable verified boot.
with can I use instead of SP_Flash_Tool?
or a basic file to start in fastboot and send manually?
I can't get over the error
thank you

patrizi said:
I followed all the info for the recovery.
with SP_Flash_Tool I always have the same error
I have tried with different versions of Global Recovery ROM (cactus)
error: status_sec_img_type-mismatch (0xc002002a) hint verified boot is enabled please download signed image (cust-verified.img) or disable verified boot.
with can I use instead of SP_Flash_Tool?
or a basic file to start in fastboot and send manually?
I can't get over the error
thank you
Click to expand...
Click to collapse
with SP_Flash_Tool:
don't use that but Miflash or better download the Fastboot rom correspond to the rom you want to install (the last one seems) then extract the zip from the TGZ file and run the flash all.bat included in the zip.

NOSS8 said:
with SP_Flash_Tool:
don't use that but Miflash or better download the Fastboot rom correspond to the rom you want to install (the last one seems) then extract the zip from the TGZ file and run the flash all.bat included in the zip.
Click to expand...
Click to collapse
the phone, however, is in brik, it does not turn on, pressed the power key vibrates , nothing else
Does Miflash work with the unbrik procedure?
thank you

patrizi said:
the phone, however, is in brik, it does not turn on, pressed the power key vibrates , nothing else
Does Miflash work with the unbrik procedure?
thank you
Click to expand...
Click to collapse
I never told you about .SP_Flash_Tool.
Mi Flash only works if fastboot mode is possible otherwise only EDL Mode will be able to recover the phone.

NOSS8 said:
I never told you about .SP_Flash_Tool.
Mi Flash only works if fastboot mode is possible otherwise only EDL Mode will be able to recover the phone.
Click to expand...
Click to collapse
i noticed that the error always occurs after writing the same file
in my case "odmdtbo" at this point I have:
error : status_sec_img_too_large (0xc0020005)
hint
Verified boot in enabled .
Please download signed image(cust-verified.img) or disable verified boot .
I can't find info to disable verification.
the file is safe and I tried like this:
disconnect phone, uncheck write files before the error
connect phone, write, answer: writing completed disconnect phone
invert selection of file writing boxes (check for no selection errors)
connect phone write
writing completed disconnect phone
turn on phone in fastboot mode
turns on and enters fastboot
SP_Flash_Tool does not connect to the phone (first attempt)
test connection with Mi Flash, here it is ok
select file to write,
ok start writing never ends.
fastboot always ok
I'll try again tomorrow.
i can't understand these writing problems

patrizi said:
i noticed that the error always occurs after writing the same file
in my case "odmdtbo" at this point I have:
Click to expand...
Click to collapse
(again)can you post the log of Miflash!!!!!
Edit the flash all bat script and delete:
fastboot %* flash cust %~dp0images/cust.img || @ECHO "Flash cust error" && exit 1
save and exit.

NOSS8 said:
(again)can you post the log of Miflash!!!!!
Edit the flash all bat script and delete:
fastboot %* flash cust %~dp0images/cust.img || @ECHO "Flash cust error" && exit 1
save and exit.
Click to expand...
Click to collapse
I have edited, not complete writing, I insert log
thank you

NOSS8 said:
(again)can you post the log of Miflash!!!!!
Edit the flash all bat script and delete:
fastboot %* flash cust %~dp0images/cust.img || @ECHO "Flash cust error" && exit 1
save and exit.
Click to expand...
Click to collapse

The bootloader is locked you must unlock it before using Miflash.
Review the method post#2
image path:E:\android\6a\111new1111\ROOT\soft\cactus-8-11-8\cactus_global_images_8.11.8_20181108.0000.00_8.1_global
Path too long E:\Miflash\cactus11
if you manage to unlock it use this method post#11

NOSS8 said:
The bootloader is locked you must unlock it before using Miflash.
Review the method post#2
image path:E:\android\6a\111new1111\ROOT\soft\cactus-8-11-8\cactus_global_images_8.11.8_20181108.0000.00_8.1_global
Path too long E:\cactus11
if you manage to unlock it use this method post#11
Click to expand...
Click to collapse
bootloader is locked ??
I have already performed post procedure 2
not complete writing
I have to use a recent file or older?
I do not understand .
thank you

patrizi said:
bootloader is locked ??
I have already performed post procedure 2
not complete writing
I have to use a recent file or older?
I do not understand .
thank you
Click to expand...
Click to collapse
You have selected:
[12:37:55 bf4b07ea7d2a]:script :E:\android\6a\111new1111\ROOT\soft\cactus-8-11-8\cactus_global_images_8.11.8_20181108.0000.00_8.1_global\flash_all_lock.bat
result
[12:37:56 bf4b07ea7d2a]:err:FAILED (remote: not allowed in locked state)
You've made this mistake before.
Right path; E:\Miflash\cactus11
{
"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"
}

Related

Lenovo K6 Power - Rooting,Unlock bootloader,Install TWRP and use Xposed on Stock Rom

Hello guys,
{
"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"
}
Lenovo K6 Power k33a42 is a new device released by lenovo on Dec 16, as many of you have bought this phone i would like to share how this phone can be rooted and how we can install twrp on this phone
UNLOCKING BOOT-LOADER : ​
Unlocking your Android phones bootloader is the first step to rooting and flashing custom ROMs
WARNING: UNLOCKING YOUR BOOTLOADER VOIDS YOUR WARRANTY.PROCEED AT YOUR OWN RISK.
NOTE: Unlocking the bootloader will Wipe/ factory reset your device, and will delete all personal data from your device such as apps, photos, messages, and settings.
INSTRUCTIONS:
1) Download the View attachment K33a42_bootloader_unlock.zip and View attachment drivers.zip zip archive attached here
2) On your device, turn on USB debugging and allow OEMunlocking
if there is no developer options in settings - go to the " Settings -> Device Info " and click on the item " Build number " until the display shows that " you became a developer
go back to the device's main Settings menu and go to Developer options tick "OEM unlocking " and " USB debugging'
when you connect for the first time using debugging via USB you will need to confirm the RSA fingerprint key to trust the PC
3) Extract the Unlock bootloader zip to any directory
4) Connect the device (K33a42) to a PC via USB-cable.
5. Go to the extracted directory and execute Unlock_Bootloader.bat and expect to complete the unlock process.
after the process is completed the boot loader will be unlocked.
INSTALLING TWRP :​
1) Extract the folder View attachment TWRP.zip archive to any drive.
2)On your phone, turn on USB debugging (drivers for ADB must be installed).
Connect your phone to a PC via usb-cable
3) You have 2 options either you can try the TWRP (only run one time) or else you can replace the stock recovery with twrp
Use accordingly
run Flash-TWRP.bat (replace stock recovery) or
run Run-TWRP.bat (for one time only).
4) Wait for the phone to boot into TWRP.
You can now disconnect the usb-cord.
Installation is finished.
and also at the starting of the twrp recovery the language will be in Russian because the creator in SevenMaxs from lenovo-forums.ru (I'am looking forward to modify default lang to english)
here is the video which shows how to do so
https://www.youtube.com/watch?v=KOhR92EKD7A
* In the stock firmware Secure Boot is enabled by default , so any changes made to the system partiton lead to a bootloop. Therefore, when you first start TWRP set the system mode to Read Only !
So in order to proceed we need to disable the secure booting in the kernel
Now to disable Secure Boot verification in the boot.img
1. Extract boot.img using twrp backup of boot partition
(you can use android image kitchen for extracting)
2. Make changes in the ramdisk \ default.prop file
change the following line:
ro.secure = 1
to
ro.secure = 0
3. repacked boot.img and flash into the device using twrp.
I know this part may be tough for some uses hence voila i have the secure boot disabled boot image , flash this to boot partition using twrp​
ROOTING​
Flashing SuperSU zip via TWRP Recovery
Download and transfer the View attachment SuperSU-v2.79-201612051815.zip zip file attached here to your device’s storage.
Boot your device into TWRP recovery.
Tap on Install and select the SuperSU zip file that you transferred to your device in Step 1.
After selecting the .zip file, do Swipe to Confirm Flash on the bottom of screen to begin the flashing process.
Once SuperSU is flashed, you’ll get Reboot System option, select it.
Congratulations! Your device should be rooted now. Look for the SuperSU app in app drawer.
INSTALLING XPOSED​
1)Install the xposed installer from playstore
2)Open the installer, and tap the ‘Install/Update’ button. Don’t worry if the app seems stuck here; just give it time and it will eventually show you a Superuser request, which you should make sure to grant and click reboot
Almost all the modules should work on stock rom as it is close to Aosp
modules which i can confirm to work are
: Android N-ify
; Gravitybox
: Bootmanager
:fingers-crossed:
All the credit goes to SevenMaxs
for creating the recovery
and for his guides for proper installation
orginal forum thread
please thank him :fingers-crossed::fingers-crossed:
Thank you
Thankzz.
Sent from my CAM-L21 using Tapatalk
When i try to flash SuperSU-v2.79-201612051815.zip, it says that is corrupt. What can i do ?
Plzz, fix it
Sent from my CAM-L21 using Tapatalk
I found another SuperSU, that worked for me: https://www.androidfilehost.com/?fid=385035244224405790
Thank you again ArjunrambZ and SevenMaxs!
LoverOfLife said:
When i try to flash SuperSU-v2.79-201612051815.zip, it says that is corrupt. What can i do ?
Click to expand...
Click to collapse
i will take a look at the zip, may be upload problem, well any super su zip will work,, this was thw one that i tried
Sent from my VIBE K6 Power using XDA Labs
LoverOfLife said:
Thank you
Click to expand...
Click to collapse
taweng7 said:
Thankzz.
Click to expand...
Click to collapse
taweng7 said:
Plzz, fix it
Click to expand...
Click to collapse
will uplpad today
also the secure boot disabled boot img also
:laugh:
Sent from my VIBE K6 Power using XDA Labs
I'll add adb/fastboot instruction for those who don't use Windows:
Of course you have to enable developer options, adb debug, oem unlocking
UNLOCK:
> adb reboot bootloader
> fastboot oem device-info
> fastboot oem unlock-go
(and... yes you can lock it back with fastboot oem lock)
TWRP:
> fastboot flash recovery /path/to/your/twrp.img
> fastboot oem reboot-recovery
BOOT.IMG:
> fastboot flash boot /path/to/your/ro.secure=0/boot.img
> fastboot reboot
P.S. (to manipulate your boot.img and change the default.prop file under linux you can use abootimg)
ilfastidio said:
I'll add adb/fastboot instruction for those who don't use Windows:
Of course you have to enable developer options, adb debug, oem unlocking
UNLOCK:
> adb reboot bootloader
> fastboot oem device-info
> fastboot oem unlock-go
(and... yes you can lock it back with fastboot oem lock)
TWRP:
> fastboot flash recovery /path/to/your/twrp.img
> fastboot oem reboot-recovery
BOOT.IMG:
> fastboot flash boot /path/to/your/ro.secure=0/boot.img
> fastboot reboot
P.S. (to manipulate your boot.img and change the default.prop file under linux you can use abootimg)
Click to expand...
Click to collapse
you seems to be working on linux, do u have the sources synced on ur pc?
meanwhile i will update the thread to include these to the topic
Sent from my VIBE K6 Power using XDA Labs
ArjunrambZ said:
you seems to be working on linux, do u have the sources synced on ur pc?
meanwhile i will update the thread to include these to the topic
Click to expand...
Click to collapse
I only work on linux. Windows is evil.
I have a big question: why in the default.prop of the russian TWRP.img there is ro.secure=1 ?????
It should be set to 0.
I guess that's why I bricked exactly after flashing Supersu from TWRP...
ilfastidio said:
I only work on linux. Windows is evil.
I have a big question: why in the default.prop of the russian TWRP.img there is ro.secure=1 ?????
It should be set to 0.
I guess that's why I bricked exactly after flashing Supersu from TWRP...
Click to expand...
Click to collapse
as far as i know.. having ro.secure enabled on recovery wont have any effect as we aren't changing anything withrespect to recovery.. but when we change something in system partition with a secure boot enabled kernel we get boot loops
Sent from my VIBE K6 Power using XDA Labs
ArjunrambZ said:
as far as i know.. having ro.secure enabled on recovery wont have any effect as we aren't changing anything withrespect to recovery.. but when we change something in system partition with a secure boot enabled kernel we get boot loops
Click to expand...
Click to collapse
Certainly I'm wrong, but I keep on not understanding. When you are in recovery mode you are loading the kernel inside the recovery and, of course, the default.prop inside the recovery.
That means that you flashed, or are going to flash, a boot.img with ro.secure=0 but running a recovery with ro.secure=1
From recovery you can manipulate system... but with a r0.secure=1 . I don't see a sense in this. But I'm a donkey.
I checked other official releases of twrp, and they all have ro.secure=0 in the default.prop
ilfastidio said:
Certainly I'm wrong, but I keep on not understanding. When you are in recovery mode you are loading the kernel inside the recovery and, of course, the default.prop inside the recovery.
That means that you flashed, or are going to flash, a boot.img with ro.secure=0 but running a recovery with ro.secure=1
From recovery you can manipulate system... but with a r0.secure=1 . I don't see a sense in this. But I'm a donkey.
I checked other official releases of twrp, and they all have ro.secure=0 in the default.prop
Click to expand...
Click to collapse
okay, firstly im also ain't any expert, but i get your point
i dont know why secure boot was enabled in recovery
but when i tried the procedure as explained in the thread i didnt get bootloop ( keeping secure boot in recovery) hence i came to the conclusion that it may not be valid.,, and i may be completely wrong here, if some one could clarify if would be better
Sent from my VIBE K6 Power using XDA Labs
Rooting panasonic eluga note 32GB ROM
Please provide rooting mothod for panasonic eluga note
amnv said:
Please provide rooting mothod for panasonic eluga note
Click to expand...
Click to collapse
sorry i dont have the device
Sent from my VIBE K6 Power using XDA Labs
ArjunrambZ said:
sorry i dont have the device
Sent from my VIBE K6 Power using XDA Labs
Click to expand...
Click to collapse
Its ok brother.. Thanks
My wifi is not working can someone help me? I did this process and after that it's not working
foRgaK said:
My wifi is not working can someone help me? I did this process and after that it's not working
Click to expand...
Click to collapse
i havent experienced this issue
but if u can attach a log file of turning on tbw wifi ,we can help
Sent from my VIBE K6 Power using XDA Labs

[Moto G6 Plus] 2: Returning to Stock

THIS GUIDE IS FOR THE MOTO G6 PLUS ONLY
2: Returning to Stock
If for any reason your phone is no longer functioning properly such as a bootloop (the phone is restarting itself over and over), "Can't Load Android System," "Startup Failed", or any such error you can fix this by flashing the stock firmware using fastboot.
I have taken stock firmware version OPW27.113-89 and packaged it with a few extras. XDA Member luiz_neto has provided a modified logo.bin that removes the unlocked bootloader warning during boot. A special thanks to XDA Member lohanbarth for providing the stock firmware. I have included the fastboot file for Windows, Linux and Mac users. Windows users can run the .bat file to execute all the necessary commands. For Linux and Mac users, I have included a bash script. You will need access to a PC and connect your phone via a USB cable.
*Downloads:
Modified Stock Firmware OPW27.113-89: (Download)
MD5: 3a1d984a8a3d0c57fb21931a8004eb27
Instructions:
*On your phone:
2A. With the phone powered off(even if for just a moment between the phone rebooting) hold the Power button and the Volume Down(Vol -) at the same time. You should boot into what is called the bootloader. It should display information on the screen and state "AP Fastboot Flash Mode" in orange lettering.
*On your PC:
2B: Extract the firmware which is in tar.xz container/file extension. Windows user probably need to use Winrar, 7Zip or PeaZip to extract the file.
2C: Using Windows Explorer, navigate to the folder EVERT_OPW27.113-89_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml and click on it to open it.
2D: Hold the Shift Key on your Keyboard. While holding Shift, Right Click in the window(not on the file). Depending on your windows version you should see either "Open PowerShell Window here" or "Open Command Window here." Select which ever one applies.
2E: You will see a black and white screen or a blue and white screen. The steps are the same no matter which screen you see. Simply type(or copy and paste) the following command:
Windows:
Code:
flash_rom.bat
For Linux and Mac you need to make the script file executable. It will make the fastboot binary executable for you. From a terminal run these 2 commands one at a time:
Linux:
Code:
chmod a+x flash_rom.sh
./flash_rom.sh
Mac:
Code:
chmod a+x flash_rom_mac.sh
./flash_rom_mac.sh
Your phone should reboot on it's own. If for some reason it doesn't try tapping the enter key on your keyboard or use the volume keys to make sure “Start” is selected on the right side of the phone and pres the power key on the phone. It should successfully boot the stock firmware.
Xplorer4x4 Hello good afternoon is on is corrupted When it unzips it says that header is corrupted! @Xplorer4x4
carlosgeraldo said:
Xplorer4x4 Hello good afternoon is on is corrupted When it unzips it says that header is corrupted! @Xplorer4x4
Click to expand...
Click to collapse
Did you try to download the package again?
Does anyone know whether It's possible to remove the "Your device has loaded a different operating system." after flashing stock rom through fastboot and relocking bootloader? I was looking to sell the phone...
Mara-X said:
Does anyone know whether It's possible to remove the "Your device has loaded a different operating system." after flashing stock rom through fastboot and relocking bootloader? I was looking to sell the phone...
Click to expand...
Click to collapse
Flash the stock firmware in my op.
Sent from my Moto G6 Plus using XDA Labs
Xplorer4x4 said:
Flash the stock firmware in my op.
Sent from my Moto G6 Plus using XDA Labs
Click to expand...
Click to collapse
No, I'm not talking about the unlocked bootloader warning, but the message that appears after you lock the bootloader. "Your device has loaded a different operating system"
Mara-X said:
No, I'm not talking about the unlocked bootloader warning, but the message that appears after you lock the bootloader. "Your device has loaded a different operating system"
Click to expand...
Click to collapse
I have never relocked my bootloader so I can't say for sure but this sounds out of the ordinary. Did it boot fine with an unlocked bootloader?
Sent from my Phh-Treble vanilla using Tapatalk
weazie said:
Did you try to download the package again?
Click to expand...
Click to collapse
I found the error: it was in my PC I started a program to fix the registry and after that unzipped the file normally!
Mara-X said:
No, I'm not talking about the unlocked bootloader warning, but the message that appears after you lock the bootloader. "Your device has loaded a different operating system"
Click to expand...
Click to collapse
Hi! have you succeed with your issue flashing this stock firmware ?
Does this stock firmware helps to remove warnings "This device has loaded a different operating system", and "Verity mode disabled" during boot?
And the worst thing is the message "System integrity compromized" and hens - GooglePay disabled and no software updates., when bootloader is re-locked?
MrMatnenko said:
Hi! have you succeed with your issue flashing this stock firmware ?
Does this stock firmware helps to remove warnings "This device has loaded a different operating system", and "Verity mode disabled" during boot?
And the worst thing is the message "System integrity compromized" and hens - GooglePay disabled and no software updates., when bootloader is re-locked?
Click to expand...
Click to collapse
Same problem here. I hate this messages
<bootloader> flash permission denied
friends, any command I give appeared this, someone knows how to solve?
Failed anything I've tried... Can you help @Xplorer4x4 ?
andreym_costa said:
Failed anything I've tried... Can you help @Xplorer4x4 ?
Click to expand...
Click to collapse
Shows the message "Failed Remote ' ' and "Flash permission denied"
andreym_costa said:
Shows the message "Failed Remote ' ' and "Flash permission denied"
Click to expand...
Click to collapse
You MUST provide MORE information! Screenshots, a detailed error description and not only a piece of your error.
WoKoschekk said:
You MUST provide MORE information! Screenshots, a detailed error description and not only a piece of your error.
Click to expand...
Click to collapse
I'm trying again... And now seeing this, can you help?
{
"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"
}
andreym_costa said:
I'm trying again... And now seeing this, can you help?
Click to expand...
Click to collapse
Please follow my guide below. That would be much easier I think, because it seems you are doing several things wrong.
1. download ADB/Fastboot tools from here and extract the downloaded zip to 'C:\' to create the path 'C:\platform-tools'
2. download your current firmware build here.
You use 116-16-22 but the latest build is 11-16-29 for RETBR.
3. extract the firmware.zip to 'C:\platform-tools'
Watch out to extract only single files and images to that path and do not create a subfolder => see screenshot attached
4. extract attached flashfile.zip to 'C:\platform-tools'
5. open 'C:\platform-tools' in Explorer and type 'cmd' in the address bar and hit 'Enter'
=> opens a new cmd window
6. boot your Moto into fastboot mode, connect it to your PC and run 'fastboot devices'
=> output: <SERIAL-NO> fastboot
7. execute 'flashfile.bat' and start flashing
WoKoschekk said:
Please follow my guide below. That would be much easier I think, because it seems you are doing several things wrong.
1. download ADB/Fastboot tools from here and extract the downloaded zip to 'C:\' to create the path 'C:\platform-tools'
2. download your current firmware build here.
You use 116-16-22 but the latest build is 11-16-29 for RETBR.
3. extract the firmware.zip to 'C:\platform-tools'
Watch out to extract only single files and images to that path and do not create a subfolder => see screenshot attached
4. extract attached flashfile.zip to 'C:\platform-tools'
5. open 'C:\platform-tools' in Explorer and type 'cmd' in the address bar and hit 'Enter'
=> opens a new cmd window
View attachment 5654883
6. boot your Moto into fastboot mode, connect it to your PC and run 'fastboot devices'
=> output: <SERIAL-NO> fastboot
7. execute 'flashfile.bat' and start flashing
Click to expand...
Click to collapse
I tried again and now these errors occur. I thought it might be a locked bootloader, but apparently everything is ok, at startup it has an unlocked bootloader warning. And really thank you to helping me.
andreym_costa said:
I tried again and now these errors occur. I thought it might be a locked bootloader, but apparently everything is ok, at startup it has an unlocked bootloader warning. And really thank you to helping me.
Click to expand...
Click to collapse
No, your bootloader isn't unlocked. The OEM-Unlock toggle would be inactive (greyed out) in case of an unlocked bootloader.

[Recovery][Mi 9][Cepheus]Unofficial TWRP recovery 3.3.0 b8 by LR.Team/wzsx150

Forgive My Poor English
It's For MI 9 (Not For MI 9 SE)
A Chinese Developer done this
The author's Email & Alipay Donate : [email protected]
The author's weibo :WEIBO
NEED UNLOCK BOOTLOADER and you can flash this recovery
Features and Notice:
1.NOT SUPPORT ENCRYPTED DATA PARTITION
2.Support Full Size offical MIUI ROM
3.NEED UNLOCK BOOTLOADER and you can flash this recovery
4.You can ROOT(magisk is the default) or UNROOT in this recovery
...
viberation not work in this recovery
More Partition in BACKUP/RECOVER
flash .bin & .mbn in Recovery(WARNING : DO NOT SELECT WRONG PARTITION)
...
and some other things
ps: DO NOT FORMAT VENDOR PARTITION (Or Do More Backup to Avoid this Situation)
DOWNLOAD
DOWNLOAD LINK
Beatryma said:
new update from wzsx150
TWRP 3.3.0 Beta 8:
https://mega.nz/#!CH5jgYTB!yNqOiVoo3cf0_15jIwZ-btO52cvpOG7iZrRCe19V2Nc
Click to expand...
Click to collapse
HOW TO FLASH
Power off your phone and press volume down key and press power key to boot to Fastboot Mode
Download Fastboot tools..
open a command line(cmd or powershell in windows) and change directory to the directory where fastboot tool locate(cd PATH/TO/FASTBOOT/TOOL), then you can use fastboot simplely
use
Code:
fastboot flash recovery [PATH TO THE IMAGE FILE YOU DOWNLOADED]
to flash(or grab that file into the cmd window, it will automaticly fill the full path of that file)
then use
Code:
fastboot reboot recovery
to boot the recovery(or just manually press volume up key and power key to reboot to recovery)
because this recovery is not support encrypted data partition, you can download flashable zip at computer and use
Code:
adb push THE/ZIP/FILE/YOU/DOWNLOAD /tmp/
(/tmp is a RAM-disk, means that the size of this partition is your free ram), you can push the flashable zip into your phone and flash it in recovery(or use otg storage devices, but the original author not mention it and Im not testing it)
IF YOUR BOOTLOADER IS LOCKED,but you wanna try it
You can use
Code:
fastboot boot [PATH TO THE IMAGE FILE YOU DOWNLOADED]
to only boot the recovery(not flash recovery)
(not sure 100% success)
Do anything on YOUR OWN RISK
Pictures(and How to set language to English )
I'm not the Author,again..
the author is wzsx150 from LR.TEAM
If you are using Xiaomi MI 9 SE OR OTHER PHONE,DO NOT FLASH THIS RECOVERY IN THIS THREAD.
First screen is 'Keep system partition read-only'
Left bottom is keep system RO,Right Buttom is change Language
{
"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 is the Main screen and you can follow these steps to change Language to ENGLISH
Great, will try it asap
finally, this works ... where i find magisk for mi 9
but I'm wrong something .... I can't start it with the volume down key + power button
baggino said:
finally, this works ... where i find magisk for mi 9
but I'm wrong something .... I can't start it with the volume down key + power button
Click to expand...
Click to collapse
if you wanna boot into recovery mode ,press volume up key + power button
q792602257 said:
if you wanna boot into recovery mode ,press volume up key + power button
Click to expand...
Click to collapse
how do i go about entering twrp? with volume up and power button does not work
I wanted to try installing magisk, but maybe it's too early....
I can't make a backup with this TWRP.
Verstuurd vanaf mijn MI 9 met Tapatalk
Did you change TARGET_OTA_ASSERT_DEVICE or whatever from xiaomimi9 to cepheus? If not, it's still broken in some way.
*justintime* said:
I can't make a backup with this TWRP.
Verstuurd vanaf mijn MI 9 met Tapatalk
Click to expand...
Click to collapse
This recovery not support encrypted data partition(data partition is encrypted by default),the only way yo backup is connect a otg storage device(i'm not testing and the original author not mention whether support otg device)
msdx321 said:
Did you change TARGET_OTA_ASSERT_DEVICE or whatever from xiaomimi9 to cepheus? If not, it's still broken in some way.
Click to expand...
Click to collapse
Maybe not , I cant upgrade by manually download full size rom and click reboot to install at the stock updater, but you can download at computer and use
Code:
adb push THE/ZIP/FILE/YOU/DOWNLOAD /tmp/
(/tmp is a RAM-disk, means that the size of this partition is your free ram), you can push full size package into it and flash it in recovery
ps: the recovery doesnt support data decrypt, and I cant use sideload to flash these zips(TAT)
q792602257 said:
This recovery not support encrypted data partition(data partition is encrypted by default),the only way yo backup is connect a otg storage device(i'm not testing and the original author not mention whether support otg device)
Click to expand...
Click to collapse
I have mounted OTG with microsd card. But backup is not possible.
Verstuurd vanaf mijn MI 9 met Tapatalk
Rommco05 said:
and flash from OTG is possible?
Click to expand...
Click to collapse
Did not try...... I am fine with Xiaomi.eu atm and have no sense in installing everything again. [emoji16]
So if you flash from OTG it would be possible to backup??
Is this twrp support format data to remove encryption?
q792602257 said:
Forgive My Poor English
It's For MI 9 (Not For MI 9 SE)
A Chinese Developer done this
The author's Email & Alipay Donate : [email protected]
The author's weibo :WEIBO
NEED UNLOCK BOOTLOADER and you can flash this recovery
Features and Notice:
1.NOT SUPPORT ENCRYPTED DATA PARTITION
2.Support Full Size offical MIUI ROM
3.NEED UNLOCK BOOTLOADER and you can flash this recovery
4.You can ROOT(magisk is the default) or UNROOT in this recovery
...
viberation not work in this recovery
More Partition in BACKUP/RECOVER
flash .bin & .mbn in Recovery(WARNING : DO NOT SELECT WRONG PARTITION)
...
and some other things
ps: DO NOT FORMAT VENDOR PARTITION (Or Do More Backup to Avoid this Situation)
DOWNLOAD
DOWNLOAD LINK
HOW TO FLASH
Power off your phone and press volume down key and press power key to boot to Fastboot Mode
Download Fastboot tools..
open a command line(cmd or powershell in windows) and change directory to the directory where fastboot tool locate(cd PATH/TO/FASTBOOT/TOOL), then you can use fastboot simplely
useto flash(or grab that file into the cmd window, it will automaticly fill the full path of that file)
then use to boot the recovery(or just manually press volume up key and power key to reboot to recovery)
because this recovery is not support encrypted data partition, you can download flashable zip at computer and use
(/tmp is a RAM-disk, means that the size of this partition is your free ram), you can push the flashable zip into your phone and flash it in recovery(or use otg storage devices, but the original author not mention it and Im not testing it)
IF YOUR BOOTLOADER IS LOCKED,but you wanna try it
You can use to only boot the recovery(not flash recovery)
(not sure 100% success)
Do anything on YOUR OWN RISK
Pictures(and How to set language to English )
I'm not the Author,again..
the author is wzsx150 from LR.TEAM
If you are using Xiaomi MI 9 SE OR OTHER PHONE,DO NOT FLASH THIS RECOVERY IN THIS THREAD.
First screen is 'Keep system partition read-only'
Left bottom is keep system RO,Right Buttom is change Language
this is the Main screen and you can follow these steps to change Language to ENGLISH
Click to expand...
Click to collapse
是b5那个版本吗?
baszu said:
Is this twrp support format data to remove encryption?
Click to expand...
Click to collapse
Yes it is.
So this is the recovery I should try on my chinese mi 9, then install the EU rom from here?
perryano said:
So this is the recovery I should try on my chinese mi 9, then install the EU rom from here?
Click to expand...
Click to collapse
There is no Difference on which version to put. Though the Transparent
I prefer using this TWRP version, because support OTG.
Sent from my Xiaomi MI 9 using XDA Labs
Does this version can be install in MI9 TE?
giangnamytb said:
Does this version can be install in MI9 TE?
Click to expand...
Click to collapse
There is no difference For this version. Similar to the normal version
Hi all,
I have mi9 with 8gb china version.
1. Can I use this tmrw version?
2. If yes, I would flash gapps micro because currently google contact won't sync. Maybe any users in here have experience, can be sync or not with this
Sent from my MI 9 using Tapatalk

Unofficial TWRP 3.4.2b Recovery for Redmi 9 (lancelot/Indian Prime) - Miui 11.

Source: https://unofficialtwrp.com/xiaomi-redmi-9-root-twrp-3-4-1/ The author wrote this: all issues fixed!
Thanks to the developer for the energy and time. Developer: wzsx150.
This is a working unofficial TWRP recovery for Redmi 9 for Miui 11. Tested on android 10, Miui Global 11.0.6 rom.
Miui 12 is work? I do not know. Everyone doesn't know. It probably won't work.
Original file: https://www.mediafire.com/file/auj2wh2lh8lzp47/3.4.2+Redmi+9+CN+EN.rar/file I modified this a bit.
What is required for installation:
Twrp img (blue) (recovery.img): Download
vbmeta_redmi9.img Download
1: Unlock bootloader
2: installed adb & fastboot drivers Download
3: Optional: Mtk usb driver Download
3a: Let the phone battery be charged to more than 50% !!!
(4: Everyone is at their own risk)
(5: Backup all data, recommended. Save idea 1, Save idea 2
6: Turn off the phone
7: Then press the volume down button + power on button to enter fastboot succes fastboot screen
8: Now connect your phone to your computer (windows emits a connection sound)
9: Open one a cmd/command line, where you downloaded the files cmd
10: Issue the two commands one after the other
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta_redmi9.img
11: You ready. Restart the phone in recovery mode
fastboot reboot recovery
12: If you did everything right, this picture will welcome you
12.a: If recovery asks you for a security pattern, enter what you use on your phone.
{
"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"
}
12: If you messed up something, don't worry. Someone here will help. (It can usually be restored with Adb or fastboot, which is broken)
13: A few pictures of the program
14: Four colors are available: blue, red, brown, purple.
Blue TWRP Recovery: Download
Red TWRP Recovery: Download
Braun TWRP Recovery: Download
Purple TWRP Recovery: Download
For now, only Chinese and English language are available! The other languages are being prepared. Soon. As there will be time for it.
It doesn't hurt to have these:
Qualcomm HS-USB QDLoader 9008 Driver 64-bit [Windows] Qualcomm driver
MediaTek MT65xx Preloader VCOM USB Driver [32-bit & 64-bit] Mediatek Vcom driver
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 Adb & fastboot drivers
MTK usb driver Download
SDK Platform tools Download
Google usb driver Download
Thanks for watching. If you liked my job, you can invite me for a beer.
Paypal: [email protected]
Crypto: 3FJuZGaw98oefj45AiypytaJzyATuRn7dE
Reserved
I saw this at telegram yesterday
Is this updated version?
SunuWijaya said:
I saw this at telegram yesterday
Is this updated version?
Click to expand...
Click to collapse
Where did you see that? (I don't understand) Two versions of this have been made. This is the second.
short question,what have you modified and how did you testet which things,we have no custom rom,what about backup and restore,did you testet,what about flashing zips in general and are all partitions rw?Thanx!!!!
-CALIBAN666- said:
short question,what have you modified and how did you testet which things,we have no custom rom,what about backup and restore,did you testet,what about flashing zips in general and are all partitions rw?Thanx!!!!
Click to expand...
Click to collapse
Hello. Well ... there weren't many tests available yet.
What I modified:
1: Skins / colors
2: Spelling mistakes
3: Syntax errors 2-3 pieces
What I was able to test in recovery:
1: Install zip / img: works
2: Backup and restore partition / data: works
3: Mount partitions: works
4: Wipe / advanced wipe: works
5: Reboot "all: works
6: Terminal: works
7: ADB Sideload: works
8: File manager: works
9: Settings "all works, except multilanguage.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
Other. For everyone. It also became a fifth skin. Orange / black. Download
------------------------------------------------------------------------------------------------------------------------------------------------------------------------​It's different again. For everyone. I noticed a mistake yet. I haven’t used recovery in a long time, so I didn’t notice the error. After a while, twrp recovery disappears. And the original recovery will be again. I don't understand why .... If you twrp recovery in flash fastboot mode again, you have twrp again. For a while.
Can dis twrp flash kernel?
Meggyi said:
Hello. Well ... there weren't many tests available yet.
What I modified:
1: Skins / colors
2: Spelling mistakes
3: Syntax errors 2-3 pieces
What I was able to test in recovery:
1: Install zip / img: works
2: Backup and restore partition / data: works
3: Mount partitions: works
4: Wipe / advanced wipe: works
5: Reboot "all: works
6: Terminal: works
7: ADB Sideload: works
8: File manager: works
9: Settings "all works, except multilanguage.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
Other. For everyone. It also became a fifth skin. Orange / black. Download
View attachment 5164259
------------------------------------------------------------------------------------------------------------------------------------------------------------------------​It's different again. For everyone. I noticed a mistake yet. I haven’t used recovery in a long time, so I didn’t notice the error. After a while, twrp recovery disappears. And the original recovery will be again. I don't understand why .... If you twrp recovery in flash fastboot mode again, you have twrp again. For a while.
Click to expand...
Click to collapse
Ok,big thanx for info.Cheers!!!
SunuWijaya said:
Can dis twrp flash kernel?
Click to expand...
Click to collapse
Does it have a custom kernel? Modified kernel? Has anyone tried kernel flash? I don't think so. (Zip and img flash, it knows) Do you know of a modified kernel?
Meggyi said:
Does it have a custom kernel? Modified kernel? Has anyone tried kernel flash? I don't think so. (Zip and img flash, it knows) Do you know of a modified kernel?
Click to expand...
Click to collapse
Just try to flash stock kernel
Afaik the issue with the missing twrp recovery is normal and only on miui based rom,on custom roms there is no issue like that.Most Xiaomi/Redmi devices do that.
Meggyi said:
Does it have a custom kernel? Modified kernel? Has anyone tried kernel flash? I don't think so. (Zip and img flash, it knows) Do you know of a modified kernel?
Click to expand...
Click to collapse
Yes it is have custom kernel named Minati-Xenodrome
How to use twrp to flash GSI ?
-CALIBAN666- said:
Afaik the issue with the missing twrp recovery is normal and only on miui based rom,on custom roms there is no issue like that.Most Xiaomi/Redmi devices do that.
Click to expand...
Click to collapse
Yeah, I get it. I didn’t have many phones that miui had. That makes sense. Stupid miui
Good job....I flash custom kernal...and it successful...but can this twrp able to go fastbootd as you mentioned and flash gsi like stock recovery?
Have you flashed a rom?
The solution for the issue that twrp is gone after some times is to flash the no-verity-opt-encrypt file for the device directly after flash of recovery,after this twrp is permanent,for the file check source link in first post.Cheers!!!!
Thank you very much, but my Redmi 9 China version cannot boot after flashing into twrp.
On Redmi 9 China version, I sorted out this version to be available.It seems that it can only be used for MIUI11
zhihuiyuze channel
论坛附件,Redmi9 twrp且可以在中国版使用
t.me
Google Drive Education Edition cannot share files (so use Telegram
There is another problem. It seems that if I use your modified version, /cust fails.
What we can do with this TWRP on lancelot?
I have the Redmi 9 (lancelot) with MIUI 11 installed. My bootloader is unlocked, I've the adb & fastboot drivers installed. I would really like to install that TWRP. While I'm flashing both files, cmd gives no errors, everything is fine. But at the end, I can not boot into recovery with "fastboot reboot recovery" from the cmd, it gives me an error. If I leave fastboot mode and try to enter TWRP manually by holding the volume and power key, it doesn't work. My device will get stuck inside a bootloop.
I'm able to fix the bootloop with disabling DAA & SLA protection in the MTK mode and flashing back the stock firmware with SP Flashtool. I tried it 3 times, every time the same issue and having to flash back the stock firmware. Do you have any tips to fix that? Or is there another or updated version I could try?
Edit: Nvm, got it working

How To Guide [ROM][STOCK][FASTBOOT][OP9R] Stock OxygenOS Fastboot ROMs

Ever wanted to unbrick your device or switch to stock ROM from a custom ROM without using MSM Unbrick tool and keeping your bootloader unlocked after that well fastboot ROMs are here to help you . I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
1). Download the zip
2). Unpack the zip in a folder
3). Reboot the OnePlus 9R in fastboot-bootloader mode (Power and volume + and volume-)
4). Connect the OnePlus 9R to PC
5). Run flash-all.bat flasher
6). Wait until the process end
7). Voila! your OnePlus 9R will now boot into OxygenOS
POINTS TO REMEMBER
* "Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
* These ROMs can't be used to update or downgrade your phone but just to restore your phone. Downgrade from OOS 12 works now.
* This can’t be used to switch from ColorOS to OxygenOS you can use MSM unbrick tool to do that.
DOWNLOAD:-
https://sourceforge.net/projects/op8t-9r-fastboot-roms/files/OnePlus_9R/
Nice
Hi OP, I changed the tag from Development to How To Guide, because we only use Development for original work like you build the ROM from kernel/device tree etc... Thanks.
HELLBOY017 said:
Ever wanted to unbrick your device or switch to stock ROM from a custom ROM without using MSM Unbrick tool and keeping your bootloader unlocked after that well fastboot ROMs are here to help you . I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
1). Download the zip
2). Unpack the zip in a folder
3). Reboot the OnePlus 9R in fastboot-bootloader mode (Power and volume + and volume-)
4). Connect the OnePlus 9R to PC
5). Run flash-all.bat flasher
6). Wait until the process end
7). Voila! your OnePlus 9R will now boot into OxygenOS
POINTS TO REMEMBER
* "Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
* These ROMs can't be used to update or downgrade your phone but just to restore your phone.
* This can’t be used to switch from ColorOS to OxygenOS you can use MSM unbrick tool to do that.
* !!! IMPORTANT !!!
Before flashing make sure you know about which type of ram your device supports i.e LPDDR4X/LPDDR5 as flashing wrong xbl config will hardbrick your device.
Here’s how you can check what type of ram your device has:-
Now, as to exactly find out which variant that you have, turn on USB debugging and enter this command:-
Code:
adb shell getprop ro.boot.ddr_type
If the value is 0, that means you have LPDDR4X. If the value is 1, that means you have LPDDR5.
This command is more reliable than the Devcheck and other apps.
DOWNLOAD:- https://drive.google.com/file/d/1LTknGhfR2JTtXhN0rGMCS4OwmUdqt3PF/view?usp=sharing
Click to expand...
Click to collapse
Errr sorry I can make sure that I have the DDR5,but it seems that when I complete the flash using the DDR5 profile config,my phone hard bricked, so how can I get it back? Now it can not even enter 9008 mode
zwk22160 said:
Errr sorry I can make sure that I have the DDR5,but it seems that when I complete the flash using the DDR5 profile config,my phone hard bricked, so how can I get it back? Now it can not even enter 9008 mode
Click to expand...
Click to collapse
You will most likely need to visit the service center and get your phone repaired.
Are you sure that your device had DDR5?
theincognito said:
You will most likely need to visit the service center and get your phone repaired.
Are you sure that your device had DDR5?
Click to expand...
Click to collapse
Actually,I checked my DDR type via devcheck instead of the adb command. Seems that the dev check is no so reliable. Anyway, I have already sent my phone to the service center to repair, I have a OnePlus 7 pro as the backup phone, so it doesn't affect me too much.
Created a Tutorial based on your firmware/instructions. Hoping you will like it.
https://androidmtk.com/install-firmware-oneplus-9r
zwk22160 said:
Actually,I checked my DDR type via devcheck instead of the adb command. Seems that the dev check is no so reliable. Anyway, I have already sent my phone to the service center to repair, I have a OnePlus 7 pro as the backup phone, so it doesn't affect me too much.
Click to expand...
Click to collapse
Yeah. The apps aren't reliable at this. Always use the adb command. 100% reliable. And since it's harbricked for you, I am pretty sure that you have a DDR4X variant.
zwk22160 said:
Errr sorry I can make sure that I have the DDR5,but it seems that when I complete the flash using the DDR5 profile config,my phone hard bricked, so how can I get it back? Now it can not even enter 9008 mode
Click to expand...
Click to collapse
It’s clearly written to not trust devcheck and other apps that prop is the only trusted source of finding which type of ram ur device has. It has also come to my attention that DDR5 devices can boot to EDL if we flash wrong xbl configs on them but the DDR4 ones can’t boot to EDL if wrong xbl config is flashed. (Means ddr4 users would have to get phone repaired by service center if wrong xbl config is flashed on their device)
PetiaWarzel said:
Created a Tutorial based on your firmware/instructions. Hoping you will like it.
https://androidmtk.com/install-firmware-oneplus-9r
Click to expand...
Click to collapse
Appreciate it a lot! Thanks
I faced the same problem
Service center says they can't flash it back
They ended up replaced a new motherboard for me
hmm for me the
Code:
adb shell getprop ro.boot.ddr_type
returns empty.
I guess that infers I'm using LPDDR4X?
Edit:
Code:
adb shell getprop
This would return a complete list of all the properties you can query with this command. For me, this list doesn't seem to have any field called "ro.boot.ddr_type"
{
"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"
}
I'm using the Chinese variant of OP9R, not so sure if it matters.
Also, DevCheck would not report RAM variants under the hardware tab as well.
Leohearts said:
I faced the same problem
Service center says they can't flash it back
They ended up replaced a new motherboard for me
Click to expand...
Click to collapse
I checked it again and
OnePlus9R:/ $ getprop | grep ddr
[ro.boot.ddr_type]: [1]
[vendor.boot.ddr_type]: [1]
OnePlus9R:/ $
I'm sure flashed the ddr5 version, but it hard-bricked and even cant boot into 9008
*UPDATED*
* Added OxygenOS 11.2.6.6 Fastboot ROM
* Removed xbl configs so that now no more hardbricks happen
* Reduced partition sizes for inactive slot so that ROMs can be flashed properly through fastboot
will this work on Chinese variant 12gb/256gb ddr4 ? LE2100 bl is already unlocked
Mkkt Bkkt said:
will this work on Chinese variant 12gb/256gb ddr4 ? LE2100 bl is already unlocked
Click to expand...
Click to collapse
If ur using oxygenos then yes
HELLBOY017 said:
If ur using oxygenos then yes
Click to expand...
Click to collapse
yes , for some reason it came with oxygenos preinstalled
HELLBOY017 said:
Ever wanted to unbrick your device or switch to stock ROM from a custom ROM without using MSM Unbrick tool and keeping your bootloader unlocked after that well fastboot ROMs are here to help you . I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
1). Download the zip
2). Unpack the zip in a folder
3). Reboot the OnePlus 9R in fastboot-bootloader mode (Power and volume + and volume-)
4). Connect the OnePlus 9R to PC
5). Run flash-all.bat flasher
6). Wait until the process end
7). Voila! your OnePlus 9R will now boot into OxygenOS
POINTS TO REMEMBER
* "Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
* These ROMs can't be used to update or downgrade your phone but just to restore your phone.
* This can’t be used to switch from ColorOS to OxygenOS you can use MSM unbrick tool to do that.
DOWNLOAD:-
https://mega.nz/folder/ePIETB4D#sU8cJ54l4UI7JCXGwc7Nog
Click to expand...
Click to collapse
Download link in Mega can't download with standard account, requires premium. could you please upload in other hosting website if possible? Thanks!
logeshwywan said:
Download link in Mega can't download with standard account, requires premium. could you please upload in other hosting website if possible? Thanks!
Click to expand...
Click to collapse
Will do
Link updated.
*Apologies for updating it late as I had fever so didn't have time for mirror it somewhere else

Categories

Resources