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
Hi all,
I'm trying to understand what did I do wrong.
I bought my device with an unlocked bootloader miui V8 (global rom).
I tried to flash TWRP recovey and MIUI PRO rom. I follow the steps that are mentioned here
and got soft brick - the device got stuck on the mi logo (with the unlock sign), even when I wait in patience the device just turned off.
- At the beginning I flashed the TWRP recovery by xuefer, boot into it and flashed the dm-verity disabler (as mentioned in the guide) and got error 1.
I reboot the device and it didn't boot.
- I boot to the recovery again and wipe the data - didn't boot.
Boot to recovery again and wipe to factory
-I flashed the MIUI PRO rom and the device still didn't boot.
I tired to flash the TWRP recovery by iscle - now the dm-verity disabler succeed but the device still didn't boot.
made the wiping steps as above again - and the device still got stuck at the mi logo.
At any step I manged to boot into the TWRP recovery and fastboot mode.
My lest option was to go back to the global stock rom using MiFlash
Now I'm on Global MIUI 9 with locked bootloadr
What did I do wrong?
I want to unlock the bootloader and to get back my control on my device.
Please advice
Thanks
Download the latest TWRP on this forum. Flash it. After, go to twrp, wipe data, cache, flash MIUI PRO rom, and after flash also flash the latest SuperSU zip. Then try again and see if it's gonna boot up.
how sure were you that the device had an unlocked bootloader when you purchased it? if it was brand new, certainly its bootloader is locked.
Do you have an open padlock when your phone is booting ?
Remember to boot to twrp just after flashing and before booting to the rom.
Thank you all for your answers!
Thank you all for your answers!
ekin_strops said:
Download the latest TWRP on this forum. Flash it. After, go to twrp, wipe data, cache, flash MIUI PRO rom, and after flash also flash the latest SuperSU zip. Then try again and see if it's gonna boot up.
Click to expand...
Click to collapse
This is exectly what I've done. and I't didn't worked.
Can you please point me to exact TWRP that you meant?
What about the dm-verity disabler ? it isn't necessary?
ondoy1943 said:
how sure were you that the device had an unlocked bootloader when you purchased it? if it was brand new, certainly its bootloader is locked.
Click to expand...
Click to collapse
I've checked the bootloader status in the Dev menu and with fastboot (fastboot oem device-info).
In addtion to all I had the open padlock sign when the turned on the device.
lightman33 said:
Do you have an open padlock when your phone is booting ?
Remember to boot to twrp just after flashing and before booting to the rom.
Click to expand...
Click to collapse
I had the open padlock sign.
Now unfortunately I flashed with MiFlash the global rom and my bootloader is locked.
I want to know the mistake I've done - so I don't fail with it again after I'll get the approval to open my bootloader.
Thanks
no mistake, they are three batches files in the rom zip. One of them is relocking the bootloader.
Flash_all with without erase data
Flash_all with wipe data
Flash_all with relock bootloader
I don't know miflash interface but you unfortunately choose the third choice. You need now to unlock your bootloader again (maybe by creating a new xiaomi account, not sure of this).
lightman33 said:
no mistake, they are three batches files in the rom zip. One of them is relocking the bootloader.
Flash_all with without erase data
Flash_all with wipe data
Flash_all with relock bootloader
I don't know miflash interface but you unfortunately choose the third choice. You need now to unlock your bootloader again (maybe by creating a new xiaomi account, not sure of this).
Click to expand...
Click to collapse
I'm sorry if you miss understood me, but I meant to the mistake I've made with the TWERP and rom flashing.
I can't figured out what I've did wrong.
Sorry if was not clear but the problem could be here :
Now unfortunately I flashed with MiFlash the global rom and my bootloader is locked.
II think you choose in Mi Flash tool an option to flash with re-lock the bootloader (don"t know how it's designed in the app because I flashed my phone manually, using one of the 3 batch files).
Hope it will help you.
lightman33 said:
Sorry if was not clear but the problem could be here :
Now unfortunately I flashed with MiFlash the global rom and my bootloader is locked.
II think you choose in Mi Flash tool an option to flash with re-lock the bootloader (don"t know how it's designed in the app because I flashed my phone manually, using one of the 3 batch files).
Hope it will help you.
Click to expand...
Click to collapse
Thank you for your answer.
I will open my bootloader,
I'm just trying to understand which TWRP version to flash for the miui pro rom (or any other)
And what is the process (or "the correct steps") to :
* Flash the TWRP recovery
* And to flash any other different rom from the miui stock.
Thanks
I took the TWRP from this forum, this is my md5 if you want to check yours :
f52ff052971b67df097d4cfa8a2ec162 twrp-3.2.0-0-oxygen.img
And this is my howto :
$ sudo fastboot flash recovery twrp-3.2.0-0-oxygen.img
target reported max download size of 536870912 bytes
sending 'recovery' (16196 KB)...
OKAY [ 0.504s]
writing 'recovery'...
OKAY [ 0.095s]
finished. total time: 0.600s
$ sudo fastboot boot twrp-3.2.0-0-oxygen.img
downloading 'boot.img'...
OKAY [ 0.487s]
booting...
OKAY [ 0.576s]
finished. total time: 1.063s
For the ROM, I took file here : http://bigota.d.miui.com/7.12.8/oxy....8_20171208.0000.00_7.1_global_93a8045184.tgz
Filename : oxygen_global_images_7.12.8_20171208.0000.00_7.1_global_93a8045184
From forum : http://en.miui.com/thread-1273027-1-1.html
and the command to flash was (after unzip the file) :
$ sudo ./flash_all_except_storage.sh
Beginning of the log :
product: oxygen
erasing 'boot'...
OKAY [ 0.027s]
finished. total time: 0.027s
erasing 'sec'...
OKAY [ 0.021s]
finished. total time: 0.021s
target reported max download size of 536870912 bytes
sending 'crclist' (0 KB)...
OKAY [ 0.040s]
writing 'crclist'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'sparsecrclist' (0 KB)...
OKAY [ 0.040s]
writing 'sparsecrclist'...
Hope it will help you...
ymca said:
Thank you for your answer.
I will open my bootloader,
I'm just trying to understand which TWRP version to flash for the miui pro rom (or any other)
And what is the process (or "the correct steps") to :
* Flash the TWRP recovery
* And to flash any other different rom from the miui stock.
Thanks
Click to expand...
Click to collapse
Hi! As others have already told you,
What I would do is to completely format the phone with Mi Flash (download the latest global stable fastboot version from http://en.miui.com/a-234.html), then flash it to the phone using the Flash All option, then flash my recovery or the one from xuefer (the one you prefer, both work), if you are flashing miui pro I think there is no need to flash the dm-verity file, so just wipe system + data + cache and flash miuipro.zip
Thank you all for your replais !
I will try and update right after I'll get the bootloader unlock approval.
Meanwhile you all have a great day !
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.
so here how i bricked my phone.
i wanted to try new miui 12 on my k20 pro .so i download the latest beta release from official sources, then what i did next is change the device name in update script of miui 12 zip file ,i replaced 'Raphael' by 'Raphaelin' as i am using Indian variant after tring it for some time i decided to go back to my previous version as i had an backup.
After i restored my back up and reboot it went into boot loop , keeps booting till logo.(restore was 100%ok)
so next i took it to just install a custom rom ,i decided upon pixel rom and installation went successfully but on reboot option it showed me no os installed .
So i decided what the **** lets just go to stock rom using 'mi flash tool' (i have used this method as last resource many time before in case if all went to ****) but in this time it showed my an error of mismatching image and device . i don't know why this happened as i have done it many times before and every time it went pretty ok.
then i tried to boot to recovery but to no avail it was not happening i keep booting into bootloader next what i did is try to reflash my recovery
fastboot flash recovery twrp.img
it went ok
then
fastboot boot twrp.img
it showed me an error
creating boot image...
creating boot image - 38807552 bytes
Sending 'boot.img' (37898 KB) OKAY [ 0.836s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed.
so my current situation is i can't boot into recovery and i install stock miui with mi flash .
so Guys any idea why this all is happening.
Are you able to boot into recovery by using 'volume+' and power button combination?
pankajgulia111 said:
so here how i bricked my phone.
i wanted to try new miui 12 on my k20 pro .so i download the latest beta release from official sources, then what i did next is change the device name in update script of miui 12 zip file ,i replaced 'Raphael' by 'Raphaelin' as i am using Indian variant after tring it for some time i decided to go back to my previous version as i had an backup.
After i restored my back up and reboot it went into boot loop , keeps booting till logo.(restore was 100%ok)
so next i took it to just install a custom rom ,i decided upon pixel rom and installation went successfully but on reboot option it showed me no os installed .
So i decided what the **** lets just go to stock rom using 'mi flash tool' (i have used this method as last resource many time before in case if all went to ****) but in this time it showed my an error of mismatching image and device . i don't know why this happened as i have done it many times before and every time it went pretty ok.
then i tried to boot to recovery but to no avail it was not happening i keep booting into bootloader next what i did is try to reflash my recovery
fastboot flash recovery twrp.img
it went ok
then
fastboot boot twrp.img
it showed me an error
creating boot image...
creating boot image - 38807552 bytes
Sending 'boot.img' (37898 KB) OKAY [ 0.836s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed.
so my current situation is i can't boot into recovery and i install stock miui with mi flash .
so Guys any idea why this all is happening.
Click to expand...
Click to collapse
What ROM did you try and restore in the Mi Flash Tool?
If you tried an Indian ROM, then try to flash a Chinese ROM instead.
pankajgulia111 said:
so here how i bricked my phone.
i wanted to try new miui 12 on my k20 pro .so i download the latest beta release from official sources, then what i did next is change the device name in update script of miui 12 zip file ,i replaced 'Raphael' by 'Raphaelin' as i am using Indian variant after tring it for some time i decided to go back to my previous version as i had an backup.
After i restored my back up and reboot it went into boot loop , keeps booting till logo.(restore was 100%ok)
so next i took it to just install a custom rom ,i decided upon pixel rom and installation went successfully but on reboot option it showed me no os installed .
So i decided what the **** lets just go to stock rom using 'mi flash tool' (i have used this method as last resource many time before in case if all went to ****) but in this time it showed my an error of mismatching image and device . i don't know why this happened as i have done it many times before and every time it went pretty ok.
then i tried to boot to recovery but to no avail it was not happening i keep booting into bootloader next what i did is try to reflash my recovery
fastboot flash recovery twrp.img
it went ok
then
fastboot boot twrp.img
it showed me an error
creating boot image...
creating boot image - 38807552 bytes
Sending 'boot.img' (37898 KB) OKAY [ 0.836s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed.
so my current situation is i can't boot into recovery and i install stock miui with mi flash .
so Guys any idea why this all is happening.
Click to expand...
Click to collapse
You need to remove these lines from .bat files within fastboot ROM folder. or if you are on Linux then corresponding lines from .sh files.
Code:
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *raphaelin" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *raphaelin" || exit /B 1
Robbo.5000 said:
What ROM did you try and restore in the Mi Flash Tool?
If you tried an Indian ROM, then try to flash a Chinese ROM instead.
Click to expand...
Click to collapse
It worked , I have indian variant but it showed mismatched image and device.
But it worked well with global variant , I flashed mi 9t pro global version.
Thanks
pankajgulia111 said:
It worked , I have indian variant but it showed mismatched image and device.
But it worked well with global variant , I flashed mi 9t pro global version.
Thanks
Click to expand...
Click to collapse
I got into the same issue, just go into the flash_all file of the indian stock rom and change it into raphael and it will work as charm.
Senior_Pj said:
I got into the same issue, just go into the flash_all file of the indian stock rom and change it into raphael and it will work as charm.
Click to expand...
Click to collapse
How to modify flash_all file on Windows 10
toufik_d said:
How to modify flash_all file on Windows 10
Click to expand...
Click to collapse
Notepad++
Senior_Pj said:
Notepad++
Click to expand...
Click to collapse
I tried and could not change it
toufik_d said:
I tried and could not change it
Click to expand...
Click to collapse
I did it last week
Senior_Pj said:
I did it last week
Click to expand...
Click to collapse
thank you very much
It has been modified with another program and transferred to the Indian version
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?