Sorry in advance for my double post, but to explain more specificly I had to do it. I am in that exact situation and all I wanna know if it is possible to have twrp recovery with official (stable) ROM. https://forum.xda-developers.com/redmi-note-5-pro/help/twrp-replaced-stock-recovery-t3811954
And if this screen is normal.
skepasti21 said:
Sorry in advance for my double post, but to explain more specificly I had to do it. I am in that exact situation and all I wanna know if it is possible to have twrp recovery with official (stable) ROM. https://forum.xda-developers.com/redmi-note-5-pro/help/twrp-replaced-stock-recovery-t3811954
And if this screen is normal.
Click to expand...
Click to collapse
I think yes, but first you have to unlock bootloader.
zkoz said:
I think yes, but first you have to unlock bootloader.
Click to expand...
Click to collapse
My bootloader is unlocked already... Thanks a lot.
Στάλθηκε από το Redmi Note 6 Pro μου χρησιμοποιώντας Tapatalk
Once you install TWRP, you will not be able to boot to Stock rom, so just install stock rom after that.
Yes, that is normal default screen. there is nothing wrong in it.
You can install official twrp or any other recovery available for Redmi 4X for e.g orangefox, redwolf or some other(s).
Flashing recovery is very simple, since you've already bootloader unlocked then just flash it via fastboot.
theagilecoder said:
Once you install TWRP, you will not be able to boot to Stock rom, so just install stock rom after that.
Click to expand...
Click to collapse
R u sure about that? Cos now we're talking my phone runs official stable ROM and latest TWRP. [emoji4][emoji1690]
Στάλθηκε από το Redmi Note 6 Pro μου χρησιμοποιώντας Tapatalk
It would seem that for me Flashing the TWRP Recovery (or any other, tried Orangefox too) doesn't work. I would really appreciate some input on this.
Here's some info:
- Redmi 4
- MIUI 10.2 | Stable // 10.2.2.0(MBECNXM)
- Android version 6.0.1
- Android Security Patch level 2018-04-01
- Unlocked the Phone (Successfully)
- Booted into fastboot
- used "fastboot flash recovery <filename>.img" to flash the twrp image (also tried older versions of the twrp image; also tried the orange fox recovery image)
It gives me the following output:
Code:
C:\Minimal ADB and Fastboot> fastboot flash recovery twrp.img
Sending 'recovery' (36040 KB) OKAY [ 1.002s]
Writing 'recovery' OKAY [ 0.977s]
Finished. Total time: 2.046s
- I proceed to use "fastboot boot twrp.img"
It gives me the following output:
Code:
C:\Minimal ADB and Fastboot> fastboot boot twrp.img
Sending 'boot.img' (36040 KB) OKAY [ 1.001s]
Booting FAILED (remote: 'dtb not found')
fastboot: error: Command failed
Now unto the errors / things I've tried:
- If I try to just use "fastboot reboot" -> it proceeds to eternally get stuck on the "mi.com" loading screen
- If I try to use the "standard" power off > Power + Vol Up -> The phone boots into the Chinese interface which is not TWRP (yellow big buttons, bottom button is blue) -> I change the language to english, hit "Recovery" and it yet again either stays stuck or boots into Mi 3.0 Recovery
I have tried all TWRP Santoni versions currently officially available on the official TWRP site.
All give me the same error if I try to boot the recovery direclty through fastboot as seen above: "(remote: dtb not found)"
can anyone please help me with this?
Godlyblade said:
It would seem that for me Flashing the TWRP Recovery (or any other, tried Orangefox too) doesn't work. I would really appreciate some input on this.
Here's some info:
- Redmi 4
- MIUI 10.2 | Stable // 10.2.2.0(MBECNXM)
- Android version 6.0.1
- Android Security Patch level 2018-04-01
- Unlocked the Phone (Successfully)
- Booted into fastboot
- used "fastboot flash recovery <filename>.img" to flash the twrp image (also tried older versions of the twrp image; also tried the orange fox recovery image)
It gives me the following output:
Code:
C:\Minimal ADB and Fastboot> fastboot flash recovery twrp.img
Sending 'recovery' (36040 KB) OKAY [ 1.002s]
Writing 'recovery' OKAY [ 0.977s]
Finished. Total time: 2.046s
- I proceed to use "fastboot boot twrp.img"
It gives me the following output:
Code:
C:\Minimal ADB and Fastboot> fastboot boot twrp.img
Sending 'boot.img' (36040 KB) OKAY [ 1.001s]
Booting FAILED (remote: 'dtb not found')
fastboot: error: Command failed
Now unto the errors / things I've tried:
- If I try to just use "fastboot reboot" -> it proceeds to eternally get stuck on the "mi.com" loading screen
- If I try to use the "standard" power off > Power + Vol Up -> The phone boots into the Chinese interface which is not TWRP (yellow big buttons, bottom button is blue) -> I change the language to english, hit "Recovery" and it yet again either stays stuck or boots into Mi 3.0 Recovery
I have tried all TWRP Santoni versions currently officially available on the official TWRP site.
All give me the same error if I try to boot the recovery direclty through fastboot as seen above: "(remote: dtb not found)"
can anyone please help me with this?
Click to expand...
Click to collapse
MIUI 10 has anti roll back protection. It makes sure if you make any changes to the recovery, it "rolls back" to the stock recovery.
To resolve this, just flash a custom ROM from TWRP from a USB OTG.
theagilecoder said:
MIUI 10 has anti roll back protection. It makes sure if you make any changes to the recovery, it "rolls back" to the stock recovery.
To resolve this, just flash a custom ROM from TWRP from a USB OTG.
Click to expand...
Click to collapse
Sorry but I don't quite understand what you mean. Would you mind expanding on the "just flash a custom ROM from TWRP from a USB OTG"?
The issue I have is that I don't yet have managed to boot into TWRP because, even after successfully flashing it to the phone - I get the posted above error when trying to boot the .img directly from the PC. If I try to reboot the phone manually I can't boot into TWRP either - it either restarts into the MI Recovery 3.0 or it restarts to boot normally, which obviously wipes the TWRP recovery and restores MI Recovery.
Godlyblade said:
Sorry but I don't quite understand what you mean. Would you mind expanding on the "just flash a custom ROM from TWRP from a USB OTG"?
The issue I have is that I don't yet have managed to boot into TWRP because, even after successfully flashing it to the phone - I get the posted above error when trying to boot the .img directly from the PC. If I try to reboot the phone manually I can't boot into TWRP either - it either restarts into the MI Recovery 3.0 or it restarts to boot normally, which obviously wipes the TWRP recovery and restores MI Recovery.
Click to expand...
Click to collapse
Cant write a details tutorial here sorry. You can discord me at theagilecoder#2747 .
---------- Post added at 04:17 PM ---------- Previous post was at 04:15 PM ----------
skepasti21 said:
R u sure about that? Cos now we're talking my phone runs official stable ROM and latest TWRP. [emoji4][emoji1690]
Στάλθηκε από το Redmi Note 6 Pro μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
Coz you might be running an older version of ROM sans Anti rollback protection, genius.
theagilecoder said:
Cant write a details tutorial here sorry. You can discord me at theagilecoder#2747 .
---------- Post added at 04:17 PM ---------- Previous post was at 04:15 PM ----------
Coz you might be running an older version of ROM sans Anti rollback protection, genius.
Click to expand...
Click to collapse
I added you Thank you
Hey guys. I figured out that I still run Android 6.0.1 on my Xiaomi Redmi 4 - despite having MIUI 10.2 and the phone not finding any new updates to be made. I assume that is the reason why I am unable to flash a TWRP recovery since they assume Santoni is for Android 7.1
I'm not quite sure how to get around this now.
Related
I tried to force update to b170, resored the backup from howtoroot thread and flashed stock recovery from within twrp, rebooted and my devicve is stuck on
ERROR MODE
err no11 recovery image
errror no 2 load failed
doesnt boot to fastboot, cant be seen by pc
cant even turn it off... it is infinite loop if i hold power button it boots "huawei logo for 1 second and again error mode"
Please help me to recover my device :/
Oh damn.. i recovered it basially i waited until batery died and then it got into fastboot mode, i unlocked bootloader, flashed twrp, restored b164 to b170 backup, and now im waiting until i download full update to b170 to finish the process, after that device will be 100% perfect
aciupapa said:
Oh damn.. i recovered it basially i waited until batery died and then it got into fastboot mode, i unlocked bootloader, flashed twrp, restored b164 to b170 backup, and now im waiting until i download full update to b170 to finish the process, after that device will be 100% perfect
Click to expand...
Click to collapse
How to boot into TWRP when after flashing it reboot infinitely on error mode and can't shutdown it.
Pressing VolumeUp for eRecovery go to error mode
aciupapa said:
Oh damn.. i recovered it basially i waited until batery died and then it got into fastboot mode, i unlocked bootloader, flashed twrp, restored b164 to b170 backup, and now im waiting until i download full update to b170 to finish the process, after that device will be 100% perfect
Click to expand...
Click to collapse
HI man I have the some problem error mode screen but in oreo update p8 lite 2017 any solution plz
p181153 said:
How to boot into TWRP when after flashing it reboot infinitely on error mode and can't shutdown it.
Pressing VolumeUp for eRecovery go to error mode
Click to expand...
Click to collapse
If you solved your problem tell me plz plz plz
jalel25 said:
If you solved your problem tell me plz plz plz
Click to expand...
Click to collapse
nope, this community do not help at all, my phone is dead even if a solution exist but nobody will tell me. I made 2 threads about it and they all go off topic and don't respond when I tell them. It's a very bad community
p181153 said:
nope, this community do not help at all, my phone is dead even if a solution exist but nobody will tell me. I made 2 threads about it and they all go off topic and don't respond when I tell them. It's a very bad community
Click to expand...
Click to collapse
I hope one of them help me ?
jalel25 said:
I hope one of them help me
Click to expand...
Click to collapse
Wait for moment when battery is at 0% and phone will shut down. Boot into fastboot and flash TWRP recovery, create backup, wipe all on device and reboot it.
mijanto313 said:
Wait for moment when battery is at 0% and phone will shut down. Boot into fastboot and flash TWRP recovery, create backup, wipe all on device and reboot it.
Click to expand...
Click to collapse
I tried that. My phone has been in this state for probably a month already. I heard the only solution is DC Phoenix via testpoint method.
Try Firmware finder for huawei + erecovery method , which is :
- download firmware finder on *another android phone* and search for exact phone model (ex : PRA-LA1C185)
- choose the very first firmware down the list
- Get an update thorugh dns >> Manually >> Register update
- After that , reboot your bricked phone into erecovery by ( power + volume*+*)
- press download recovery and last firmware
- wait till getting package
- by now should firmware start downloading
- let phone complete it's work and reboot
Hope that's work for you ?
p181153 said:
nope, this community do not help at all, my phone is dead even if a solution exist but nobody will tell me. I made 2 threads about it and they all go off topic and don't respond when I tell them. It's a very bad community
Click to expand...
Click to collapse
About your problem - If your phone throws errors when you try to boot into TWRP, then something is wrong with TWRP (for example you flashed incompatibile version). Boot into bootloader aka fastboot mode and try to flash TWRP again from there.
Off-topic part: In my opinion, this is the most helpful & best community about Android phones. Noone is going to help you if you keep spamming. Just be patient, we are humans, not robots
Botar230 said:
About your problem - If your phone throws errors when you try to boot into TWRP, then something is wrong with TWRP (for example you flashed incompatibile version). Boot into bootloader aka fastboot mode and try to flash TWRP again from there.
Off-topic part: In my opinion, this is the most helpful & best community about Android phones. Noone is going to help you if you keep spamming. Just be patient, we are humans, not robots
Click to expand...
Click to collapse
Hi,i bricked yesterday but today I installed the wrong TWRP as you said and I do not have access to anything .. Do you have a solution? Some say the bootloader is locked..
thank's !
Freysheur said:
Hi,i bricked yesterday but today I installed the wrong TWRP as you said and I do not have access to anything .. Do you have a solution? Some say the bootloader is locked..
thank's !
Click to expand...
Click to collapse
Bootloader can't be locked if you managed to flash TWRP. Do the following:
1. Make sure the phone is turned off
2. Hold Vol- and plug the usb cable in
3. You should be in bootloader aka fastboot mode
4. Flash TWRP using (p8 lite 2015) fastboot flash recovery <path>.img
5. fastboot reboot
Botar230 said:
Bootloader can't be locked if you managed to flash TWRP. Do the following:
1. Make sure the phone is turned off
2. Hold Vol- and plug the usb cable in
3. You should be in bootloader aka fastboot mode
4. Flash TWRP using (p8 lite 2015) fastboot flash recovery <path>.img
5. fastboot reboot
Click to expand...
Click to collapse
Hi bro', i love you :silly: I did not know the technic for enter in fastboot without volume "-" .
Okay, the bootloader and FRP is unlocked but before i'am on Nougat and i have passed on Oreo. For flashed the TWRP my commands are " fastboot flash recovery_ramdisk recovery.img ".
And i have a error message when i flash the ROM Stock or TWRP with the normal commands as " fastboot flash recovery recovery.img ".
My error message it's :
fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (11204 KB)...
OKAY [ 0.290s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.305s
Thank's for your reponse, sorry for my english, i'm french !
Freysheur said:
Hi bro', i love you :silly: I did not know the technic for enter in fastboot without volume "-" .
Okay, the bootloader and FRP is unlocked but before i'am on Nougat and i have passed on Oreo. For flashed the TWRP my commands are " fastboot flash recovery_ramdisk recovery.img ".
And i have a error message when i flash the ROM Stock or TWRP with the normal commands as " fastboot flash recovery recovery.img ".
My error message it's :
fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (11204 KB)...
OKAY [ 0.290s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.305s
Thank's for your reponse, sorry for my english, i'm french !
Click to expand...
Click to collapse
Use fastboot flash recovery only on 2015 variant. You need to use recovery ramdisk on 2017 variant
Sent from my LG-K220 using XDA Labs
Botar230 said:
Use fastboot flash recovery only on 2015 variant. You need to use recovery ramdisk on 2017 variant
Sent from my LG-K220 using XDA Labs
Click to expand...
Click to collapse
Why before i used the flash recovery and it worked ?
Do you have an answer to the error " FAILED (remote: partition length get error) " ?
---------- Post added at 11:25 AM ---------- Previous post was at 10:40 AM ----------
Ok, i try install ROM via TWRP..
I have no errors but i bootloop again.. and he puts me in the menu Huawei eRecovery..
---------- Post added at 11:39 AM ---------- Previous post was at 11:25 AM ----------
I try install ROM via Fastboot CMD.
C:\Users\Alban\Desktop\fastboots>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.011s
C:\Users\Alban\Desktop\fastboots>fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (15524 KB)...
OKAY [ 0.389s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.413s
Hmmmm, i installed MorfuZ rom, he boot but he restart alone..
So I do not have a rom ...
jalel25 said:
I hope one of them help me
Click to expand...
Click to collapse
Everyone, I made a guide on my website to unbrick the device.
Here is the link:
http://mrviking.simplesite.com/440246066
I have VIE-L29 latest build
EMUI 5.0.1
Android 7.0
1. Bootloader is already unlocked. I used the code from Huawei.
2. Flashed TWRP (twrp-3.2.1-0-vienna.img) to recovery using Minimal ADB and Fastboot (result as shown below).
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (22456 KB)...
OKAY [ 0.879s]
writing 'recovery'...
OKAY [ 0.173s]
finished. total time: 1.068s
3. Tried several times but failed to boot into TWRP recovery. It just boots into the oem recovery everytime (volume down + power on button + plug in USB)
try to flash TWRP 3.1.1-1 (from here)
I advise you to flash it to recovery2 (not recovery) then just reboot and press vol up more then 3 secs
xzanium said:
try to flash TWRP 3.1.1-1 from here
I advise you to flash it to recovery2 (not recovery) then just reboot and press vol up more then 3 secs
Click to expand...
Click to collapse
sounds good, thanks. But just so as not to mess up:
-fastboot flash recovery2 twrp-3.1.1-1-vie.img
-fastboot reboot
please confirm, and then i'll be on my way to root!
cmd ok
xzanium you rock!
xzanium said:
cmd ok
Click to expand...
Click to collapse
it worked!
i got TWRP to boot on recovery2 and installed SUPERSU
Thanks man!
Root Checker info on my P9
I installed root checker today and it reported that root access was ok, but it also reported the following stats:
Huawei VIE-L29 root statistics
ranked by ease of installation
Summary:
Available Root Versions: 2
Root Available: Yes
Latest Android Version: 7.
HUAWEI Ease of Root Install Rank: 15
additionally, on ease of rooting the app reported:
Rank: 6620 (out of 8066)
Root Install Difficulty: Hard
Well, it wasn't that hard thanks to the help i got in this thread... just saying
Hi I have rooted my phone huawei p9 and i have the twrp recovery and tried installing different rom in my phone but while installing twrp is rebooting and the new rom is not getting installed in my phone. can you please advise?
What ROM Version?
Huawei P9 is very picky on which ROMS it can run. What ROM specifically did you try to install? please include the source where it was downloaded from, size, version, date etc.
So basically I was installing TWRP onto my Mi A2. I installed twrp on slot b using fastboot flash boot_b twrp.img When then trying to boot into the b slot using fastboot set_active b That command wasn't recognized. I tried installing JDK and SDK manager to get the latest syntax etc. of adb/fastboot. I tried everything again and accidently typed fastboot flash boot twrp.img . This made me flash twrp to my a slot too. The new adb/fastboot syntax still didn't recognize the set_active command. So now I'm simply stuck with twrp on both my slots. I tried installing havoc-OS v2.0 for GSI. downloading the img.xz file. Extracting it and tried flashing it on slot a. But it kind of failed. This was the code:
PS C:\Users\noahe\Desktop\Ny mapp\platform-tools> fastboot flash system_b havoca2.img
target reported max download size of 536870912 bytes
sending sparse 'system_b' (524284 KB)...
OKAY [ 17.596s]
writing 'system_b'...
OKAY [ 0.001s]
sending sparse 'system_b' (524284 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 18.764s
PS C:\Users\noahe\Desktop\Ny mapp\platform-tools> fastboot reboot
rebooting...
finished. total time: 0.001s
I would appreciate some help
It sounds like (at least initially) your version of fastboot doesn't understand dual slots? an older version? You say you updated right? The new version does understand dual slots I'm assuming?
First thing, what happens if you press power and vol UP and hold them both until it starts to reboot?
Stop using minimal adb, use this
https://developer.android.com/studio/releases/platform-tools
Flash the stock boot image and it should work
EDIT: since you tried flashing system, flash stock system again too
If all that results in is you staying in TWRP, look at twrp and hopefully it's one of the newer versions that allows you to set the 'active slot'. Hopefully choosing the other slot and then indicating reboot in twrp will cause the device to boot normally.
AsItLies said:
It sounds like (at least initially) your version of fastboot doesn't understand dual slots? an older version? You say you updated right? The new version does understand dual slots I'm assuming?
First thing, what happens if you press power and vol UP and hold them both until it starts to reboot?
Click to expand...
Click to collapse
Nothing really, the only thing on my both slots are twrp so I can't boot into other recovery modes etc.
Nebrassy said:
Stop using minimal adb, use this
Flash the stock boot image and it should work
EDIT: since you tried flashing system, flash stock system again too
Click to expand...
Click to collapse
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.
ncse said:
Nothing really, the only thing on my both slots are twrp so I can't boot into other recovery modes etc.
Click to expand...
Click to collapse
As mentioned then, just flash stock boot.img, for the version that your device is currently running. The various stock boot images are easily found, along with the patched_boot.img (that you don't want).
The only issue is that the 2 slots, one will be the most current software you last updated to, the other will be the previous version you updated from. Do you know which one as active and what version it was running? If not, sounds like you'll have to guess.
If you can get one slot to boot you can then probably fix the other okay.
---------- Post added at 09:38 ---------- Previous post was at 09:29 ----------
ncse said:
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.
Click to expand...
Click to collapse
I'd stop flashing roms. Yer bootloader is the problem now, not the rom.
AsItLies said:
As mentioned then, just flash stock boot.img, for the version that your device is currently running. The various stock boot images are easily found, along with the patched_boot.img (that you don't want).
The only issue is that the 2 slots, one will be the most current software you last updated to, the other will be the previous version you updated from. Do you know which one as active and what version it was running? If not, sounds like you'll have to guess.
If you can get one slot to boot you can then probably fix the other okay.
---------- Post added at 09:38 ---------- Previous post was at 09:29 ----------
I'd stop flashing roms. Yer bootloader is the problem now, not the rom.
Click to expand...
Click to collapse
Do I only flash the boot.img file? I don't know if you noticed but the jasmine 9.6.15 is a folder with all the stock images.
I know before all this i was on slot a with the 9.6.15 update
ncse said:
Do I only flash the boot.img file? I don't know if you noticed but the jasmine 9.6.15 is a folder with all the stock images.
I know before all this i was on slot a with the 9.6.15 update
Click to expand...
Click to collapse
If you haven't change system, you haven't flashed any rom to it, on slot a, then yeah, just flash the boot.img for that version to slot a. You should then be able to set that as active (if it isn't already) and boot.
AsItLies said:
If you haven't change system, you haven't flashed any rom to it, on slot a, then yeah, just flash the boot.img for that version to slot a. You should then be able to set that as active (if it isn't already) and boot.
Click to expand...
Click to collapse
Now i get bootloops. Should I flash system.img too? Apprently all this fault is because you have to type .\fastboot.exe instead of fastboot in powershell.
EDIT: I flashed system.img too. It works again. Thanks for all the help!
ncse said:
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.
Click to expand...
Click to collapse
Fastboot flashing unlock_critical
Hi guys
I can't install twrp on my Redmi Note 10 pro Chinese Variant phone
i opened the boot loader means it's unlocked now
But when I try to install twrp using adb tool I receive this message
FAILED (remote: partition doesn't exist)
the file i have only is TWRP-3.5.1-sweet-Nebrassy-1 and TWRP-3.5.1-sweet-Nebrassy- 2
i have tried by using a new cable, another PC, different USB ports
every time i face this error
thank you
asadattari12 said:
Hi guys
I can't install twrp on my Redmi Note 10 pro Chinese Variant phone
i opened the boot loader means it's unlocked now
But when I try to install twrp using adb tool I receive this message
FAILED (remote: partition doesn't exist)
the file i have only is TWRP-3.5.1-sweet-Nebrassy-1 and TWRP-3.5.1-sweet-Nebrassy- 2
i have tried by using a new cable, another PC, different USB ports
every time i face this error
thank you
Click to expand...
Click to collapse
Follow the guide:
https://forum.xda-developers.com/t/4288121/post-85137963
Do Clean Flash custom ROMs section up to step 13. Ignore step 8, 9 and 12
Use the TWRP file you have, the TWRP-3.5.1-sweet-Nebrassy- 2.img for step 13.
flash file ( fastboot rom) to be placed in deskyop and try . mi flash tool support only file on desktop folder
pl1992aw said:
Follow the guide:
https://forum.xda-developers.com/t/4288121/post-85137963
Do Clean Flash custom ROMs section up to step 13. Ignore step 8, 9 and 12
Use the TWRP file you have, the TWRP-3.5.1-sweet-Nebrassy- 2.img for step 13.
Click to expand...
Click to collapse
same error appears with this tool too
mathan7 said:
flash file ( fastboot rom) to be placed in deskyop and try . mi flash tool support only file on desktop folder
Click to expand...
Click to collapse
file is already on desktop
First
Code:
fastboot reboot bootloader
Then do the steps again.
Show screenshots of the program what error you get.
pl1992aw said:
First
Code:
fastboot reboot bootloader
Then do the steps again.
Show screenshots of the program what error you get.
Click to expand...
Click to collapse
what i found later that i was using twrp for sweet code, later i was known that the code for my phone is Chopin, and Twrp file for Chopin is not available, so i am trying to do root without custom recovery
asadattari12 said:
what i found later that i was using twrp for sweet code, later i was known that the code for my phone is Chopin, and Twrp file for Chopin is not available, so i am trying to do root without custom recovery
Click to expand...
Click to collapse
First you need to go back to MIUI.
fastboot reboot bootloader
then flash your phone device official MIUI fastboot ROM (China).
Do not choose anything with lock option.
pl1992aw said:
First you need to go back to MIUI.
fastboot reboot bootloader
then flash your phone device official MIUI fastboot ROM (China).
Do not choose anything with lock option.
Click to expand...
Click to collapse
flashing is done with orignal rom, Phone is OK now, how can i root it without custom recovery?
asadattari12 said:
flashing is done with orignal rom, Phone is OK now, how can i root it without custom recovery?
Click to expand...
Click to collapse
Installation
The Magic Mask for Android
topjohnwu.github.io
If the official way don't work, then you have to wait until someone figure out how to root.
You phone doesn't even belong to here. No forum for you phone yet.
So you may need to find Chinese forum to see if they can root it.
asadattari12 said:
file is already on desktop
Click to expand...
Click to collapse
firet flash fatboot
fastboot flash bootloader fastboot.img
then try flash tool
asadattari12 said:
Hi guys
I can't install twrp on my Redmi Note 10 pro Chinese Variant phone
i opened the boot loader means it's unlocked now
But when I try to install twrp using adb tool I receive this message
FAILED (remote: partition doesn't exist)
the file i have only is TWRP-3.5.1-sweet-Nebrassy-1 and TWRP-3.5.1-sweet-Nebrassy- 2
i have tried by using a new cable, another PC, different USB ports
every time i face this error
thank you
Click to expand...
Click to collapse
you are using a TWRP for RM Note 10 pro global(codename is: sweet), The China Version is based on MTK CPU, it's codename is :chopin. There still no available TWRP for chopin.
fxxkingchopin said:
you are using a TWRP for RM Note 10 pro global(codename is: sweet), The China Version is based on MTK CPU, it's codename is :chopin. There still no available TWRP for chopin.
Click to expand...
Click to collapse
Does OrangeFox REC is TWRP ? When I input .\fastboot flash boot recovery.img in CMD, everything seems alright. But when I reboot my RedMi Note 10 Pro, the screen is looping in black &RedMi logo. What should I do?
GilbertWong said:
Does OrangeFox REC is TWRP ? When I input .\fastboot flash boot recovery.img in CMD, everything seems alright. But when I reboot my RedMi Note 10 Pro, the screen is looping in black &RedMi logo. What should I do?
Click to expand...
Click to collapse
Try directly after flashing recovery via Fastboot:
Press buttons volume+ and power so long as you see the logo and feel vibration.
Now recovery ofox should start again and should be stable
Laptapper said:
Try directly after flashing recovery via Fastboot:
Press buttons volume+ and power so long as you see the logo and feel vibration.
Now recovery ofox should start again and should be stable
Click to expand...
Click to collapse
I did it according to your instruction. I press buttons volume+ and power , but nothing happens. My phone kept black. What should I do?
GilbertWong said:
I did it according to your instruction. I press buttons volume+ and power , but nothing happens. My phone kept black. What should I do?
Click to expand...
Click to collapse
You've flashed twrp via Fastboot without any glitches or not?
So you stay after flashing in Fastboot, if you press then the buttons as long as you see logo and feel vibration then the recovery should start
Laptapper said:
You've flashed twrp via Fastboot without any glitches or not?
So you stay after flashing in Fastboot, if you press then the buttons as long as you see logo and feel vibration then the recovery should start
Click to expand...
Click to collapse
I think I flashed OrangeFox image correctly.
CMD result is below .
D:\APPs\_Utility\AndroidRootTools\platform-tools>.\fastboot flash boot recovery.img
Sending 'boot_b' (34024 KB) OKAY [ 0.788s]
Writing 'boot_b' OKAY [ 0.063s]
Finished. Total time: 0.976s
FastBoot feedback in phone screen is below.
USB Transferring...
USB Transmission OK Time:0 s Vel: 45MB/S
After I quitted FastBoot and reboot , the screen was looping in black & RedMi logo.
Anything I did wrong?
GilbertWong said:
I think I flashed OrangeFox image correctly.
CMD result is below .
D:\APPs\_Utility\AndroidRootTools\platform-tools>.\fastboot flash boot recovery.img
Sending 'boot_b' (34024 KB) OKAY [ 0.788s]
Writing 'boot_b' OKAY [ 0.063s]
Finished. Total time: 0.976s
FastBoot feedback in phone screen is below.
USB Transferring...
USB Transmission OK Time:0 s Vel: 45MB/S
After I quitted FastBoot and reboot , the screen was looping in black & RedMi logo.
Anything I did wrong?
Click to expand...
Click to collapse
Not quitting Fastboot, remove cable and press the buttons together until vibration
GilbertWong said:
I think I flashed OrangeFox image correctly.
CMD result is below .
D:\APPs\_Utility\AndroidRootTools\platform-tools>.\fastboot flash boot recovery.img
Sending 'boot_b' (34024 KB) OKAY [ 0.788s]
Writing 'boot_b' OKAY [ 0.063s]
Finished. Total time: 0.976s
FastBoot feedback in phone screen is below.
USB Transferring...
USB Transmission OK Time:0 s Vel: 45MB/S
After I quitted FastBoot and reboot , the screen was looping in black & RedMi logo.
Anything I did wrong?
Click to expand...
Click to collapse
You're not using RN 10 Pro global, it must be RN 10 Pro 5g (codename chopin), a.k.a. Poco X3 GT, which is A/B device. Global one is not A/B device.
Do not continue any further before risking bricking your device.
x3r0.13urn said:
You're not using RN 10 Pro global, it must be RN 10 Pro 5g (codename chopin), a.k.a. Poco X3 GT, which is A/B device. Global one is not A/B device.
Do not continue any further before risking bricking your device.
Click to expand...
Click to collapse
Yes，it is chopin. So chopin can not be rooted?
Hello guys!
I am having issues with the battery (I think it's faulty) and I just wanted to reflash the EU MIUI Stable ROM to see if it's a software problem.
Currently with unlocked bootloader (no root) EU MIUI 13 STABLE and Android 12.
What I did:
didn't remember if I had TWRP installed and flashed EU MIUI 13 STABLE via Fastboot
MIUI 13 - MIUI 13 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
linux_fastboot_update_rom.sh was successful
but now stuck in MIUI Recovery mode after every boot
I guess I had TWRP installed and this is why it got issues?
So I decided to fix it by installing TWRP first, and then flash ROM via TWRP:
found official TWRP for Mi 11 here: https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374109/
installed this via fastboot: fastboot boot twrp-3.6.2_11-0-venus.img
did "Advanced > Flash Current TWRP"
stuck in TWRP Recovery mode boot
did TWRP Wipe data (since required by installing the ROM)
stuck in Fastboot mode
it might have removed by mistake /system or /persist, I just did the default Wipe Data of TWRP
Device is correctly recognized with fastboot devices but I get this error when trying to boot with TWRP:
Code:
$ fastboot boot twrp-3.6.2_11-0-venus.img
Sending 'boot.img' (196608 KB) OKAY [ 4.999s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Do you guys have any tip to recover the device? Any help very much appreciated
dlime3004 said:
Hello guys!
I am having issues with the battery (I think it's faulty) and I just wanted to reflash the EU MIUI Stable ROM to see if it's a software problem.
Currently with unlocked bootloader (no root) EU MIUI 13 STABLE and Android 12.
Click to expand...
Click to collapse
Seems you use a A11 TWRP for a A12 rom
Use A12 https://androidfilehost.com/?w=files&flid=321497
NOSS8 said:
Seems you use a A11 TWRP for a A12 rom
Use A12 https://androidfilehost.com/?w=files&flid=321497
Click to expand...
Click to collapse
You are right!
I just tried to boot with that but I still got that the same error:
Code:
$fastboot boot twrp-3.6.2_12-v6.0_A12-venus-skkk.img
Sending 'boot.img' (196608 KB) OKAY [ 5.203s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Any way to debug this?
dlime3004 said:
You are right!
I just tried to boot with that but I still got that the same error:
Code:
$fastboot boot twrp-3.6.2_12-v6.0_A12-venus-skkk.img
Sending 'boot.img' (196608 KB) OKAY [ 5.203s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Any way to debug this?
Click to expand...
Click to collapse
Dowload this rom https://sourceforge.net/projects/xi...13.0.8.0.SKBCNXM_v13-12-fastboot.zip/download
extract it
Phone in fastboot plug in to the pc
Open the folder
Use" first install.bat" according your OS
First boot take a long time.
Lastest TWRP BOOT
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
NOSS8 said:
Dowload this rom https://sourceforge.net/projects/xi...13.0.8.0.SKBCNXM_v13-12-fastboot.zip/download
extract it
Phone in fastboot plug in to the pc
Open the folder
Use" first install.bat" according your OS
First boot take a long time.
Click to expand...
Click to collapse
Thank you very much! I've run the "first install" script and managed to recover the phone!
Would PM me your PayPal? I'd like to get you a coffee
dlime3004 said:
Thank you very much! I've run the "first install" script and managed to recover the phone!
Would PM me your PayPal? I'd like to get you a coffee
Click to expand...
Click to collapse
Here all is FREE !!!!!!!!!!!!
Amazing, hope I can help in the future as well
@NOSS8 im so thankful for your response as i was facing this problem today after trying to move away from pixel experience and going back to stock. you are the hero of the day.