Hello community, first of all I clarify that I am using the google translator.
As the title says, my poco f3 has a hard brick, I was trying to flash the miui global rom via fastboot(stock rom was global miui for turkey) but an error occurred in the process (the same as attached in the image), at that moment I got scared because the phone did not start the system.
The bootloader was obviously unlocked, I tried to recover with XiaoMitool but nothing, I couldn't flash super.img either in Xiaomiflash, then I decided to download its stock rom and redo the process but it failed.
Before all this I had tried to install TWRP or OrangeFox but none could be installed, I only got to the TWRP boot but the option to flash the current TWRP did not appear and it did not recognize the internal memory and the OTG with the zip. Right now it only shows the POCO logo and goes directly to fastboot mode.
I'd appreciate your help.
Edit: It does not have the recovery stock
edixon2021 said:
Hello community, first of all I clarify that I am using the google translator.
As the title says, my poco f3 has a hard brick, I was trying to flash the miui global rom via fastboot(stock rom was global miui for turkey) but an error occurred in the process (the same as attached in the image), at that moment I got scared because the phone did not start the system.
The bootloader was obviously unlocked, I tried to recover with XiaoMitool but nothing, I couldn't flash super.img either in Xiaomiflash, then I decided to download its stock rom and redo the process but it failed.
Before all this I had tried to install TWRP or OrangeFox but none could be installed, I only got to the TWRP boot but the option to flash the current TWRP did not appear and it did not recognize the internal memory and the OTG with the zip. Right now it only shows the POCO logo and goes directly to fastboot mode.
I'd appreciate your help.
Edit: It does not have the recovery stock
Click to expand...
Click to collapse
try booting twrp via fastboot and then format data.
Obviously you'll lose your data, but it might give you access to your phone back.
Good morning.
Try to enter with quiet fastboot mode, both in twrp and orange fox, it's the same process. Put the phone in fastboot mode and then open minimal adb.
1. Put the fastboot devices command, the serial number of your mobile should appear on the command screen.
2. Put the command fastboot boot orangefox.img or twrp.img, take a good look at the file you have downloaded, to make the boot easy, it has to be an .img image and not a zip file.
3. If you can get into both fastboot and orangefox, please format the data.
4. Try to flash the miui stock rom with the same process where the error appeared, remember that this rom (it worked for me) has to be the rom for the poco f3 fastboot, since there are 2 versions (I think I have seen this) one which is fastboot and another which is not.
LUCK!
ShAnGoS said:
Good morning.
Try to enter with quiet fastboot mode, both in twrp and orange fox, it's the same process. Put the phone in fastboot mode and then open minimal adb.
1. Put the fastboot devices command, the serial number of your mobile should appear on the command screen.
2. Put the command fastboot boot orangefox.img or twrp.img, take a good look at the file you have downloaded, to make the boot easy, it has to be an .img image and not a zip file.
3. If you can get into both fastboot and orangefox, please format the data.
4. Try to flash the miui stock rom with the same process where the error appeared, remember that this rom (it worked for me) has to be the rom for the poco f3 fastboot, since there are 2 versions (I think I have seen this) one which is fastboot and another which is not.
LUCK!
Click to expand...
Click to collapse
Hello, i had already tried to boot with twrp.img but without success, the good news is that I have already recovered it and the solution was as simple as taking the flash_all.bat from the rom and it could already be in any version of miui.
What I don't understand is why it hadn't worked with XiaoMitool and Xiaomiflash, and I still can't install TWRP because it doesn't recognize internal memory and OTG.
Anyway thanks for your help.
edixon2021 said:
Hello, i had already tried to boot with twrp.img but without success, the good news is that I have already recovered it and the solution was as simple as taking the flash_all.bat from the rom and it could already be in any version of miui.
What I don't understand is why it hadn't worked with XiaoMitool and Xiaomiflash, and I still can't install TWRP because it doesn't recognize internal memory and OTG.
Anyway thanks for your help.
Click to expand...
Click to collapse
Glad you got it sorted, When installing a MIUI stock rom remember to put the Firm wear folder on your C: Drive and remove any spaces from title,
As for TWRP & Orangefox recoverry, i installed these in fast boot mode and use "Temporary Recovery" by downloading RUN_TWRP-Orange Fox FIXED.bat /unzipping/ and running the "RUN_TWRP-Orange Fox FIXED.bat File, once in temporary OF Recovery you can choose to make OF Recovery permanent by installing current version of OF from within OF, Check my post on the EVO-X Thread post 20,
you will also find my post regarding OTG issues,
--------------------------------------------------------------------------
OTG is no longer Now working with Orangefox recovery.
To overcome the OTG showing 0MB or .., remove the OTG adaptor,
reboot into OF Recovery, re-connect your OTG adaptor and
tap ☰ in the bottom right of the main screen to open the MENU,
open Mount, tap USB-STORAGE (wait 5 seconds) the (USB-STORAGE background will turn black), shortly after the check box will enabled, many thanks to Rafsf for the Workaround.
I hope this helps a bit
johnr64 said:
Glad you got it sorted, When installing a MIUI stock rom remember to put the Firm wear folder on your C: Drive and remove any spaces from title,
As for TWRP & Orangefox recoverry, i installed these in fast boot mode and use "Temporary Recovery" by downloading RUN_TWRP-Orange Fox FIXED.bat /unzipping/ and running the "RUN_TWRP-Orange Fox FIXED.bat File, once in temporary OF Recovery you can choose to make OF Recovery permanent by installing current version of OF from within OF, Check my post on the EVO-X Thread post 20,
you will also find my post regarding OTG issues,
--------------------------------------------------------------------------
OTG is no longer Now working with Orangefox recovery.
To overcome the OTG showing 0MB or .., remove the OTG adaptor,
reboot into OF Recovery, re-connect your OTG adaptor and
tap ☰ in the bottom right of the main screen to open the MENU,
open Mount, tap USB-STORAGE (wait 5 seconds) the (USB-STORAGE background will turn black), shortly after the check box will enabled, many thanks to Rafsf for the Workaround.
I hope this helps a bit
Click to expand...
Click to collapse
Thank you very much friend you deserve heaven, finally I was able to install OF permanently.
Related
Hello, I have sent my phone to warranty and after that I received a phone with NO RPMB and after many frustrations I found (with help of many users and forums) how to workaround this..
To start:
Download boot image from here
Download twrp from the official website
Change the name to boot.img and twrp.img and put it in the platform-tools folder
Open the terminal there
Download your favourite rom
Enter fastboot mode on your phone
!!!!After this you will loose all of your data!!!!
Paste this to the terminal
fastboot oem unlock
(select yes on your phone)
fastboot flash boot boot.img
fastboot flash recovery twrp.img
fastboot format userdata
fastboot format cache
Reboot to recovery (if it doesn't enter at the first time enter download mode again and restart to recovery)
After that you have twrp and can flash every rom.. yay!!!
Wipe everything.
Copy the rom zip to your phone using MTP
Install your fancy new rom
If you want to install magisk:
Install the magisk manager.
On the app select install and select patch image file. (it will create a new boot image already patched)
After that install the new image (patched_boot.img) using twrp
Do a clean instalation of your ROM (recomended) or a Factory Reset first
Reboot to twrp
Select install
Click in install image
Select patched_boot.img
Select install to boot partition
Reboot.
Install magisk manager and do the sugested setup.
You now have magisk working
Thanks to all the users that helped me!!
I had real trouble getting twrp to work the last time I tried this a few months ago. Followed the steps here and am now on pixel experience with magisk. Thanks!
Hello, im in the same situation of NO RPMB. This procedure will permanently lets have bootloader unlocked?
About Magisk, i can install it in usual way once im in the recovery? (I mean download latest stable version for Bullhead and flash via TWRP).
Thanks.
sigibian said:
Hello, im in the same situation of NO RPMB. This procedure will permanently lets have bootloader unlocked?
About Magisk, i can install it in usual way once im in the recovery? (I mean download latest stable version for Bullhead and flash via TWRP).
Thanks.
Click to expand...
Click to collapse
My bootloader is still unlocked after following this guide
For Magisk:
-Install your custom ROM and boot it up (without root)
-Then extract the boot.img from the ROM zip file and save it on your phone storage.
-Install the Magisk manager apk
-In Magisk manager, select install Magisk> choose the patch boot image option and -Select the boot.img you previously saved.
Once it's done, reboot into twrp and flash the patched boot.img. When you reboot Magisk will be working.
I've had no issues with my bootloader, even after an ota update for pixel experience.
Thank you, i will try it.
Another question. I never tried dowload mode before, as i read in other post i should Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb that's already connected to pc, right?
When in download mode i can fire up fastboot commands like im in bootloader mode?
So then after do last command fastboot format cache i can reboot to recovery from terminal using adb reboot recovery or i can / should do it from device?
About twrp it's ok to use the latest 3.2.3.0 official version or the 3.2.1 4core version from here as someone suggested from Reddit? https://forum.xda-developers.com/nexus-5x/development/recovery-twrp-3-2-1-4-core-t3796656
sigibian said:
Thank you, i will try it.
Another question. I never tried dowload mode before, as i read in other post i should Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb that's already connected to pc, right?
When in download mode i can fire up fastboot commands like im in bootloader mode?
So then after do last command fastboot format cache i can reboot to recovery from terminal using adb reboot recovery or i can / should do it from device?
About twrp it's ok to use the latest 3.2.3.0 official version or the 3.2.1 4core version from here as someone suggested from Reddit? https://forum.xda-developers.com/nexus-5x/development/recovery-twrp-3-2-1-4-core-t3796656
Click to expand...
Click to collapse
The official twrp works for fine for me, haven't tried the 4 core version but it can't hurt to try if you need it.
Power off your phone then press and hold volume - and power to enter bootloader, then connect to your pc and follow the steps in the OP
So i have to enter in bootloader mode? At point 6 of OP there is written to enter in the download mode, this makes me confusing.
Can anyone explain me latest 2 commands why they are needed?
fastboot format userdata
fastboot format cache
sigibian said:
So i have to enter in bootloader mode? At point 6 of OP there is written to enter in the download mode, this makes me confusing.
Can anyone explain me latest 2 commands why they are needed?
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
This thread is fairly comprehensive;
https://forum.xda-developers.com/nexus-5x/general/moto-nexus-5x-sticky-roll-t3207487
Holding volume - and power takes you to fastboot mode (download mode essentially), theres also an option to reboot into recovery (selectable using the volume keys.)
Formatting user data and cache is necessary prior to installing a new rom (especially if moving from stock). You lose all data (back up first!) But a clean flash is the best place to start.
baddesthad said:
This thread is fairly comprehensive;
https://forum.xda-developers.com/nexus-5x/general/moto-nexus-5x-sticky-roll-t3207487
Holding volume - and power takes you to fastboot mode (download mode essentially), theres also an option to reboot into recovery (selectable using the volume keys.)
Formatting user data and cache is necessary prior to installing a new rom (especially if moving from stock). You lose all data (back up first!) But a clean flash is the best place to start.
Click to expand...
Click to collapse
Thanks for the explanation but for installing a new ROM usually you can do factory reset directly in TWRP, plus doing all the wipes, this should be enough.
About fastboot mode and download mode, they are completely different, fastboot mode: vol down + power, download mode for LG: Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb.
My question is what i can do in download mode? As OP says after entering download mode open terminal and use fastboot commands.
sigibian said:
Thanks for the explanation but for installing a new ROM usually you can do factory reset directly in TWRP, plus doing all the wipes, this should be enough.
About fastboot mode and download mode, they are completely different, fastboot mode: vol down + power, download mode for LG: Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb.
My question is what i can do in download mode? As OP says after entering download mode open terminal and use fastboot commands.
Click to expand...
Click to collapse
You need to use vol- and power to go into fastboot mode then connect to the pc. As for userdata and cache, if you don't clean them when coming from stock you will have issues (your data will be encrypted if you're on stock?). As I said this guide worked for me. The op was talking about fastboot mode in the 6th option (also there is much more information in the thread I linked above)
sorry for the confusing i wanted to say fastboot mode..
i knew the thread that you are saying but most people doesn't want to search so I made a little thread only with the needed parts..
I use it myself so I have a place to remember all the steps when I need to change the rom to a new one or when I make experiments and brick my phone XD
If anyone know anything else that should be in here just say, I really want to improve the post
Hi. I just went through the whole process several times (I have tried the different modified boot images from the dedicated post) and my device is still locked [emoji24] any suggestions?
fhartane said:
Hi. I just went through the whole process several times (I have tried the different modified boot images from the dedicated post) and my device is still locked [emoji24] any suggestions?
Click to expand...
Click to collapse
your device will always be locked this is a workaround to get twrp, new roms and magisk while it stays locked..
with twrp usable it won't matter if you are locked or not
PedroM.CostaAndrade said:
your device will always be locked this is a workaround to get twrp, new roms and magisk while it stays locked..
with twrp usable it won't matter if you are locked or not
Click to expand...
Click to collapse
Thanks for the answer. You mean that now I have twrp, I can flash custom Roms with my bootloader locked without any issue?
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
Yes if you have TWRP you can install custom ROMs, custom Kernel's, magisk, super su, etc..
the locked bootloader only prevents you from using fastboot commands like the one needed for installing custom recovery
Now that you have TWRP you can use it for everything
Hello everyone, I also have a nexus 5x with motherboard that has been replaced under warranty and unfortunately I can't keep the bootloader unlocked.
I tried the procedure you have indicated, but at this point there is the problem, because after inserting the boot.img and twrp.img inside the phone, then when I go to do the unlocking procedure with 'fastboot oem unlock (select yes on your phone) 'in practice the memory is deleted on the phone, so I lose the previously uploaded files, and therefore I can no longer continue with the flash procedure of boot.img and twrp.img because they are no longer present in memory.
I hope I made myself understood, maybe I am wrong, or is there a way to solve this problem?
Fabiojoker said:
Hello everyone, I also have a nexus 5x with motherboard that has been replaced under warranty and unfortunately I can't keep the bootloader unlocked.
I tried the procedure you have indicated, but at this point there is the problem, because after inserting the boot.img and twrp.img inside the phone, then when I go to do the unlocking procedure with 'fastboot oem unlock (select yes on your phone) 'in practice the memory is deleted on the phone, so I lose the previously uploaded files, and therefore I can no longer continue with the flash procedure of boot.img and twrp.img because they are no longer present in memory.
I hope I made myself understood, maybe I am wrong, or is there a way to solve this problem?
Click to expand...
Click to collapse
fastboot is for the files on your PC not your phone
you need to put the files inside of platform-tools and then open cmd inside it and use the fastboot commands
fastboot will take the files of your PC
Hello, thank you for your information, since I haven't done modding on phones for a long time, I didn't remember exactly the procedure with fastboot and therefore I didn't understand where I had to put the files, but in the end I did it.
Thank you
PedroM.CostaAndrade said:
fastboot is for the files on your PC not your phone
you need to put the files inside of platform-tools and then open cmd inside it and use the fastboot commands
fastboot will take the files of your PC
Click to expand...
Click to collapse
Why is a custom boot image needed? I don't want to root.
Hi everyone,
I got Chinese version Note 8 Pro from Mi official store and unlocked bootloader after 7 days.
I downloaded Global MIUI 11 ROM via official miui download link, "ifelixit+FLASHER+TOOLKIT+Begonia" and installed ADB drivers etc.
After run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1, it installed recovery, then I'm able to boot into TWRP, and then I installed global rom from there, meanwhile wiped everything in it as I don't need China version rom. Phone reboot well and new global rom works great.
Then I try to install Magisk, I noticed recovery seems be restored to original, no worries, I re-run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1 to install TWRP again. Whatever I did, I cannot get TWRP back, when I hold power/+, it keep blank and will restart, but if I don't hold them, it can get into the system.
My first question is: 1. At this stage, is recovery crash already?
I didn't think too much and I get into system, install Magisk manager, let it to patch boot.img, I then use following command in fastboot mode
fastboot flash boot boot_patch.img
After I finished, I noticed maybe I can do TWRP here as well, then I also input
fastboot flash boot TWRP.img
After reboot, the phone is dead....No fastboot, NO recovery, no vibration. exactly described as here
[UNBRICK - stuck on DA mode / Authorised Service Account required]
https://forum.xda-developers.com/re...ide-unbrick-stuck-da-mode-authorised-t4000433
I re-think what I did, my question is
2. Will boot_patch.img Magisk patched not suitable for China phone with global rom?
3. Is fastboot dead because I installed recovery into boot via fastboot flash boot TWRP.img?
Thanks for your time and appreciated for any knowledgeable reply.
Flash your original boot.img for your original firmware or just download the xiaomitoolV2 and flash it that way. I see a lot of people flashing stock firmware using TWRP. Hence the v2 tool only works if your phone still fully boots. NOTE do not flash stock FW or UPDATE using TWRP you will brick the device. Chances are your FW didn't flash and just ADB CMD fatsboot flash boot ( then set BOOT.IMG ) in the CMD and get the devices booting again. Then use the V2 tool to flash the global firmware get that to stick then use the ifelixit tool to flash recovery once in recovery go advanced file mgr system-root at the bottom delete boot P then close AVB 2.0 then hit the install root button SU - magisk 19.4 will be installed. no need to wipe or format the phone ( DON'T FORGET TO WIPE CACHE & DALVIC.
---------- Post added at 09:00 AM ---------- Previous post was at 08:52 AM ----------
fastjohnson said:
Flash your original boot.img for your original firmware or just download the xiaomitoolV2 and flash it that way. I see a lot of people flashing stock firmware using TWRP. Hence the v2 tool only works if your phone still fully boots. NOTE do not flash stock FW or UPDATE using TWRP you will brick the device. Chances are your FW didn't flash and just ADB CMD fatsboot flash boot ( then set BOOT.IMG ) in the CMD and get the devices booting again. Then use the V2 tool to flash the global firmware get that to stick then use the ifelixit tool to flash recovery once in recovery go advanced file mgr system-root at the bottom delete boot P then close AVB 2.0 then hit the install root button SU - magisk 19.4 will be installed. no need to wipe or format the phone ( DON'T FORGET TO WIPE CACHE & DALVIC.
Click to expand...
Click to collapse
Remove the back off the phone and disconnect the battery for 5 min just to be sure hold the power button to clear all power left in the phone. Main objective is to get useage again fastboot or recovery. If you get recovery sideload your boot img and flash it on the next reboot twrp will be overridden.
fastjohnson said:
Flash your original boot.img for your original firmware or just download the xiaomitoolV2 and flash it that way. I see a lot of people flashing stock firmware using TWRP. Hence the v2 tool only works if your phone still fully boots. NOTE do not flash stock FW or UPDATE using TWRP you will brick the device. Chances are your FW didn't flash and just ADB CMD fatsboot flash boot ( then set BOOT.IMG ) in the CMD and get the devices booting again. Then use the V2 tool to flash the global firmware get that to stick then use the ifelixit tool to flash recovery once in recovery go advanced file mgr system-root at the bottom delete boot P then close AVB 2.0 then hit the install root button SU - magisk 19.4 will be installed. no need to wipe or format the phone ( DON'T FORGET TO WIPE CACHE & DALVIC.
---------- Post added at 09:00 AM ---------- Previous post was at 08:52 AM ----------
Remove the back off the phone and disconnect the battery for 5 min just to be sure hold the power button to clear all power left in the phone. Main objective is to get useage again fastboot or recovery. If you get recovery sideload your boot img and flash it on the next reboot twrp will be overridden.
Click to expand...
Click to collapse
Thanks. Currently my phone doesn't have reboot, no recovery, purely blank on screen, only power led shows when connecting via USB. In this situation, must open back case to disconnect the battery? I heard about it's free to go back to mi store and re flash it back. To open back case it won't have warranty anymore. Struggling....
idog8818 said:
Thanks. Currently my phone doesn't have reboot, no recovery, purely blank on screen, only power led shows when connecting via USB. In this situation, must open back case to disconnect the battery? I heard about it's free to go back to mi store and re flash it back. To open back case it won't have warranty anymore. Struggling....
Click to expand...
Click to collapse
I also have two bricked phones note 8 pro with no recovery, only white led shows when connecting via USB.
First bricked with TWRP and then flashed with false boot.img, second is bricked with OrangeFox-Unofficial-begonia.img.
I was open back case and disconnect the battery, stay 3 days but nothing working to reboot to fastboot or recovery.
Also I have already tried with short circuit test point to EDL mode but phone is still dead. I have downloaded many xiaomi and other tools and firmwares, installed all available usb drivers and reading all internet forums.
Please help!
Same
Hello,
I think I did the same error, flashing a wrong boot.img...
I tell you if I manage to do something.
hello, the solution to the problem is the battery is completely discharged until the device stops responding to any attempts to start using the key combination. unless you tried to flash a fastboot partition. the solution works after hard bricking after trying to upload incompatible twrp or other rom (I uploaded Chinese twrp on eu rom). ok, we start:
1. holding vol - and power plug in the usb cable (the buttons are released when the notification LED changes from very bright for a moment to slightly dimmed)
2. you will see the long unseen battery symbol with a lightning inside (i.e. a completely discharged battery, the charge status will begin to show the percentage)
3. Turn off the USB cable at 3 percent.
4. now an important thing - you need to start the phone only trying to enter the fastboot mode otherwise the phone will start to boot the system and get stuck again and you will have to unload it again
5. you will finally enter the fastboot , using only the software from xiaomi or xiaomi flash and fastboot rom
I succeeded after 2 weeks of waiting for it to discharge ...
I copied this tutorial from this partner klocek80 , and it worked perfectly
https://forum.xda-developers.com/showpost.php?p=81191977&postcount=72
danyv77 said:
hello, the solution to the problem is the battery is completely discharged until the device stops responding to any attempts to start using the key combination. unless you tried to flash a fastboot partition. the solution works after hard bricking after trying to upload incompatible twrp or other rom (I uploaded Chinese twrp on eu rom). ok, we start:
1. holding vol - and power plug in the usb cable (the buttons are released when the notification LED changes from very bright for a moment to slightly dimmed)
2. you will see the long unseen battery symbol with a lightning inside (i.e. a completely discharged battery, the charge status will begin to show the percentage)
3. Turn off the USB cable at 3 percent.
4. now an important thing - you need to start the phone only trying to enter the fastboot mode otherwise the phone will start to boot the system and get stuck again and you will have to unload it again
5. you will finally enter the fastboot , using only the software from xiaomi or xiaomi flash and fastboot rom
I succeeded after 2 weeks of waiting for it to discharge ...
I copied this tutorial from this partner klocek80 , and it worked perfectly
https://forum.xda-developers.com/showpost.php?p=81191977&postcount=72
Click to expand...
Click to collapse
This only helps when boot image is not damaged.
Duchan_xda said:
I also have two bricked phones note 8 pro with no recovery, only white led shows when connecting via USB.
First bricked with TWRP and then flashed with false boot.img, second is bricked with OrangeFox-Unofficial-begonia.img.
I was open back case and disconnect the battery, stay 3 days but nothing working to reboot to fastboot or recovery.
Also I have already tried with short circuit test point to EDL mode but phone is still dead. I have downloaded many xiaomi and other tools and firmwares, installed all available usb drivers and reading all internet forums.
Please help!
Click to expand...
Click to collapse
I'm with you. The boot image has error and when MTK realize it has something wrong it will NOT enter into fastboot. The only way to fix this is too use SP Flash Tool for deep flash. Mi store uses this way as well to fix the issue.
Try this:
https://c.mi.com/thread-2173190-1-0.html
ppthom said:
Try this:
https://c.mi.com/thread-2173190-1-0.html
Click to expand...
Click to collapse
This does NOT work. Please don't waste time on it.
:good:Thanks for clarifying this. Back to square one ...
idog8818 said:
Hi everyone,
I got Chinese version Note 8 Pro from Mi official store and unlocked bootloader after 7 days.
I downloaded Global MIUI 11 ROM via official miui download link, "ifelixit+FLASHER+TOOLKIT+Begonia" and installed ADB drivers etc.
After run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1, it installed recovery, then I'm able to boot into TWRP, and then I installed global rom from there, meanwhile wiped everything in it as I don't need China version rom. Phone reboot well and new global rom works great.
Then I try to install Magisk, I noticed recovery seems be restored to original, no worries, I re-run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1 to install TWRP again. Whatever I did, I cannot get TWRP back, when I hold power/+, it keep blank and will restart, but if I don't hold them, it can get into the system.
My first question is: 1. At this stage, is recovery crash already?
I didn't think too much and I get into system, install Magisk manager, let it to patch boot.img, I then use following command in fastboot mode
fastboot flash boot boot_patch.img
After I finished, I noticed maybe I can do TWRP here as well, then I also input
fastboot flash boot TWRP.img
After reboot, the phone is dead....No fastboot, NO recovery, no vibration. exactly described as here
[UNBRICK - stuck on DA mode / Authorised Service Account required]
https://forum.xda-developers.com/re...ide-unbrick-stuck-da-mode-authorised-t4000433
I re-think what I did, my question is
2. Will boot_patch.img Magisk patched not suitable for China phone with global rom?
3. Is fastboot dead because I installed recovery into boot via fastboot flash boot TWRP.img?
Thanks for your time and appreciated for any knowledgeable reply.
Click to expand...
Click to collapse
Are you recover your phone? I'm still waiting one year...
Duchan_xda said:
Are you recover your phone? I'm still waiting one year...
Click to expand...
Click to collapse
I didn`t find any background on your issue, just something like you actually have a device with white led light blinking.
I read this thread before (yes, some weeks ago) this happened to me yesterday https://forum.xda-developers.com/redmi-note-8-pro/how-to/guide-unlock-note-8-pro-authorised-t4168805 the short story is that I were trying to return to Miui 12 after of using some custom ROMs and something in the flashing process failed I mean it was an incomplete flashing and I assumed that most probably just the bootloader partition was damaged. The whole important fact in this situation is that you have yet available fastboot mode but like the splash partition with its image was gone I couldn `t see it and I were anyway in fastboot mode so I could flash the proper files to "unbrik" it. (my device is unlocked)
What you should try is connect it with PC while you`re pressing the volume down, enter to adb/fastboot environment and type fastboot commands to see if device is recogniced, you don`t have to hear constant reboot sounds or in this case press the power button simulating that you are powering off device.
Hi.
So I was messing around with the twrp custom recovery and (without thinking much of it) wiped everything in the advanced wipe menu :crying: (System, data, EVERYTHING)
I knew I had removed my OS and that I could just use the twrp recovery to install a new rom onto my phone BUT little did I know, when I tried to boot into the custom recovery, it would just loop the screen with the redmi logo
I am still able to boot into fastboot mode, and I have tried to flash the same twrp recovery but with no avail (It still loops the redmi logo screen)
So now I'm here to ask if there is any advice that you could give me to try and fix this problem that I have gotten myself in (I am not worried about deleting any of my personal files. I would just like to get twrp to boot so that I can install another rom)
Thanks in advance to anyone who can help me with this problem :highfive:
Hi, which rom are you trying to install? for android 9 use this recovery https://forum.xda-developers.com/re...overy-unofficial-twrp-recovery-redmi-t4002397, for android 10 this one... https://forum.xda-developers.com/showpost.php?p=82062075&postcount=7...
If what nuvulet said doesn't work, in fastboot, flash the exact same stock ROM you had before, let it boot and then flash TWRP.
nuvulet said:
Hi, which rom are you trying to install? for android 9 use this recovery https://forum.xda-developers.com/re...overy-unofficial-twrp-recovery-redmi-t4002397, for android 10 this one... https://forum.xda-developers.com/showpost.php?p=82062075&postcount=7...
Click to expand...
Click to collapse
Hi, thanks for the fast reply.
The stock android I had before I wiped everything was android 9, MIUI 11. I tried againt to flash the recovery through fast boot but (like before) when I try to boot into the recovery (by holding the volume up button as it reboots), the redmi logo keeps appearing and disappearing and doesn't go to the twrp recovery. At the current moment I don't have any OS installed (since it got deleted when I wiped everything)
Any other leads I could try?
wang1chung said:
If what nuvulet said doesn't work, in fastboot, flash the exact same stock ROM you had before, let it boot and then flash TWRP.
Click to expand...
Click to collapse
I'm not sure how I can flash the stock ROM without the twrp recovery. I had the impression that you needed twrp recovery in order to install ROMs in the first place.
If there is a method to flash a ROM using fastboot, please explain since my unexperienced self has no idea how to do this. :laugh:
Thanks for the fast reply too
Sqorpz said:
I'm not sure how I can flash the stock ROM without the twrp recovery. I had the impression that you needed twrp recovery in order to install ROMs in the first place.
If there is a method to flash a ROM using fastboot, please explain since my unexperienced self has no idea how to do this. :laugh:
Thanks for the fast reply too
Click to expand...
Click to collapse
MiFlash works through fastboot mode. It's also safer to flash with MiFlash, just make sure you have the correct ROM.
I can't find the guide right now, I'm at work
Ok, do you know adb fastboot... if not, follow this guide...
https://forum.xda-developers.com/showthread.php?t=2317790
Install usb adb drivers for RN8P if you don't have, try this for w10...
https://forum.xda-developers.com/redmi-note-8-pro/help/usb-drivers-t4035617
Download twrp for android 9 or android 10 from here...
https://forum.xda-developers.com/showpost.php?p=82115341&postcount=2
Put the recovery (*.img format) into installed adb folder...
Open cmd and navigate to inside adb folder...
Put the phone into fastboot mode (press volume- and power) connect usb and type in console...
adb devices (this start adb server)
Type...
fastboot devices (this return a device number, if not, something is wrong)
Type...
fastboot flash recovery *.img (change * for the name of the recovery file)
Disconnect the phone and press volume+ and power at the same time and now you have twrp intalled...
When start if the data is encrypted, push cancel, go to wipe, go to format data, type "yes", and confirm slide...
Now connect the phone to usb (if not recognize the phone, go to mount, and enable MTP)
Copy the rom in to internal storage for your android twrp version... search here
https://forum.xda-developers.com/redmi-note-8-pro/how-to/redmi-note-8-pro-android-10-public-t4072795
You have several versions... for eu, search in my post...
And the rest, install, select, etc. etc....
nuvulet said:
Ok, do you know adb fastboot... if not, follow this guide...
https://forum.xda-developers.com/showthread.php?t=2317790
Install usb adb drivers for RN8P if you don't have, try this for w10...
https://forum.xda-developers.com/redmi-note-8-pro/help/usb-drivers-t4035617
Download twrp for android 9 or android 10 from here...
https://forum.xda-developers.com/showpost.php?p=82115341&postcount=2
Put the recovery (*.img format) into installed adb folder...
Open cmd and navigate to inside adb folder...
Put the phone into fastboot mode (press volume- and power) connect usb and type in console...
adb devices (this start adb server)
Type...
fastboot devices (this return a device number, if not, something is wrong)
Type...
fastboot flash recovery *.img (change * for the name of the recovery file)
Disconnect the phone and press volume+ and power at the same time and now you have twrp intalled...
When start if the data is encrypted, push cancel, go to wipe, go to format data, type "yes", and confirm slide...
Now connect the phone to usb (if not recognize the phone, go to mount, and enable MTP)
Copy the rom in to internal storage for your android twrp version... search here
https://forum.xda-developers.com/redmi-note-8-pro/how-to/redmi-note-8-pro-android-10-public-t4072795
You have several versions... for eu, search in my post...
And the rest, install, select, etc. etc....
Click to expand...
Click to collapse
Yes, this is the method I used to flash the twrp recovery.
My problem was that even after installing it (using this method), i would still not be able to boot into the recovery.
However, it is fixed now. I used the Mi Flash tool in order to install the stock rom and then installed twrp after that. :good:
wang1chung said:
MiFlash works through fastboot mode. It's also safer to flash with MiFlash, just make sure you have the correct ROM.
I can't find the guide right now, I'm at work
Click to expand...
Click to collapse
I tried this method and IT WORKED!!
After installing Mi flash I was able to download the stock rom and install it through the program without any errors.
I was then able to finally boot into the OS and install twrp recovery, then install the custom rom! :laugh:
Thanks for this method. I would probably still be stuck on the Redmi logo if it weren't for this
Hi,
I attempted to flash ArrowOS for my Poco F3 2 days ago but I didn't follow the steps correctly. My plan was to unlock bootloader, boot twrp and install ArrowOS. After I tried this, the ArrowOS loadup screen kept on loading for a hour. I rebooted the device and ended up in the ArrowOS recovery. After some times, I tried to flash the MIUI fastboot rom with Mi Flash Tool and I think I chose "clean all and lock." This caused a problem because I became stuck on the fastboot page and when I tried to reboot, it would go to the Poco startup page briefly before jumping back to the fastboot. I've tried to hold the power button and the volume keys but it has no effect. Also, on the Poco page there was no unlocked padlock which was weird because when I first tried to flash ArrowOS I could see the unlocked padlock. When I checked on my computer using Mi Unlock, it showed that my device was unlocked.
I think I did manage to flash fastboot rom for MIUI using XiaomiToolV2 because it said that the installation was complete.
Another problem is that when I boot TWRP with fastboot from my computer, there isn't any internal storage shown after I click the install button. I think this is because I wiped the device with TWRP when I was following various tutorials. When I try to add a file to the internal storage from my computer it shows an empty folder and any files I copy into it isn't shown.
I would be really grateful for any help as I've been trying to fix this problem for 2 days now. Thank you!
I've attached a video of the phone being stuck on fastboot.
12839172398 said:
Hi,
I attempted to flash ArrowOS for my Poco F3 2 days ago but I didn't follow the steps correctly. My plan was to unlock bootloader, boot twrp and install ArrowOS. After I tried this, the ArrowOS loadup screen kept on loading for a hour. I rebooted the device and ended up in the ArrowOS recovery. After some times, I tried to flash the MIUI fastboot rom with Mi Flash Tool and I think I chose "clean all and lock." This caused a problem because I became stuck on the fastboot page and when I tried to reboot, it would go to the Poco startup page briefly before jumping back to the fastboot. I've tried to hold the power button and the volume keys but it has no effect. Also, on the Poco page there was no unlocked padlock which was weird because when I first tried to flash ArrowOS I could see the unlocked padlock. When I checked on my computer using Mi Unlock, it showed that my device was unlocked.
I think I did manage to flash fastboot rom for MIUI using XiaomiToolV2 because it said that the installation was complete.
Another problem is that when I boot TWRP with fastboot from my computer, there isn't any internal storage shown after I click the install button. I think this is because I wiped the device with TWRP when I was following various tutorials. When I try to add a file to the internal storage from my computer it shows an empty folder and any files I copy into it isn't shown.
I would be really grateful for any help as I've been trying to fix this problem for 2 days now. Thank you!
I've attached a video of the phone being stuck on fastboot.
Click to expand...
Click to collapse
Well I don't own that phone but it sounds like you didn't unlock the bootloader properly and your internal storage is encrypted that's why it shows 0 and that's probably why your having problems. Is there an encryption disabler zip? Your supposed to format data and flash an encryption disabler and than magisk v23 on Samsung devices than boot.
Okay, so I've just used the Format Data option in TWRP which says it will remove encryption on internal storage. But this didn't seem to fix any problems
12839172398 said:
Okay, so I've just used the Format Data option in TWRP which says it will remove encryption on internal storage. But this didn't seem to fix any problems
Click to expand...
Click to collapse
Did you flash a disabler zip? Also is your bootloader locked?
No, I haven't flashed a disabler zip. Where would I download that. I found a XDA download called Xposed-Disabler-Recovery.zip, would that be it.
My bootloader was unlocked and the Mi Unlock tool still says that it is unlocked, but I don't see an unlocked padlock on the start up page.
12839172398 said:
Okay, so I've just used the Format Data option in TWRP which says it will remove encryption on internal storage. But this didn't seem to fix any problems
Click to expand...
Click to collapse
Did you follow the directions on Xda
INSTALLATION PROCEDURE:
First installation (Clean flash):
You need adb/fastboot tools.
Download boot, vendor_boot and rom zip:
boot_alioth.img
drive.google.com
vendor_boot_alioth.img
drive.google.com
ArrowOS - Downloads
Reboot in fastboot. Flash boot and vendor_boot:
fastboot flash boot_ab boot_alioth.img
fastboot flash vendor_boot_ab vendor_boot_alioth.img
fastboot --set-active=a
Reboot in ArrowOS Recovery:
fastboot reboot recovery
Make format data (Factory reset -> Format data).
Flash ROM (Apply update -> Apply from ADB):
adb sideload name.zip
If you want install separate gapps on vanilla buildtype, after flash ROM:
Advanced -> Reboot to recovery
Flash gapps (Apply update -> Apply from ADB):
adb sideload name.zip
Follow what show on device, should be ... Step 1/2 -> 2/2, then flashing ended, can reboot device in system. (on command line can show "(~47%) adb: failed to read command: No error", it normal!)
________________________________________
Install Update (dirty flash):
Go in Settings -> System -> Updater
Downlad new build -> Install
12839172398 said:
No, I haven't flashed a disabler zip. Where would I download that. I found a XDA download called Xposed-Disabler-Recovery.zip, would that be it.
My bootloader was unlocked and the Mi Unlock tool still says that it is unlocked, but I don't see an unlocked padlock on the start up page.
Click to expand...
Click to collapse
sounds like you have indeed locked your bootloader. you can check using fastboot cmd 'fastboot oem device-info'
if it's locked, only thing to do i would guess is to try and flash stock rom (not EU custom rom) and hope for the best, then try to unlock your bl again
12839172398 said:
No, I haven't flashed a disabler zip. Where would I download that. I found a XDA download called Xposed-Disabler-Recovery.zip, would that be it.
My bootloader was unlocked and the Mi Unlock tool still says that it is unlocked, but I don't see an unlocked padlock on the start up page.
Click to expand...
Click to collapse
Also twrp instructions
Installation:
1. fastboot boot twrp.img
2. copy that same twrp image to the device
3. go to Advanced > Install Recovery Ramdisk
4. select the image you copied
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
7. reboot to recovery, you should now be able to boot TWRP normally using Power+volume up
repeat step 3 and 4 directly after flashing a new rom, then reboot recovery to flash additional stuff
also, if your bl is indeed locked i for sure recommend you HALT all attempts at flashing twrp or any custom rom. you need to focus on trying to get stock fw back on the device and booting
WOW! Thank you guys so much for your help! My bootloader was indeed unlocked and I proceeded with the steps by Techguy777 and it worked perfectly! I now have ArrowOS booting up and I cannot thank you guys enough. I hope you have a great day!
Also I haven't installed TWRP; Should I install TWRP? Or is ArrowOS Recovery sufficient
12839172398 said:
Also I haven't installed TWRP; Should I install TWRP? Or is ArrowOS Recovery sufficient
Click to expand...
Click to collapse
Just use arrowos recovery... Doesnt really matter unless u switch around several roms
12839172398 said:
WOW! Thank you guys so much for your help! My bootloader was indeed unlocked and I proceeded with the steps by Techguy777 and it worked perfectly! I now have ArrowOS booting up and I cannot thank you guys enough. I hope you have a great day!
Click to expand...
Click to collapse
enjoy the ArrowOS, it is way better than MIUI. I am loving it since i flashed it 2 days ago!
Wow, if you chose flash and lock like you mention in 1st post and somehow your device remained unlocked, you sir are very lucky!! Glad it's all up and running. Fck knows how it stayed unlocked, but thankfully it did
Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.
how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.
Thanks for the hint, but I am not happy with the idea of someone playing with my data
1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC
Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.
Any idea? Should I give up?
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.
Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.
If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b
I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.
Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5