Unlock bootloader
Download and unzip this archive or this archive (if you model is BTV-W09)
In command prompt:
Code:
adb reboot-bootloader
fastboot flash recovery twrp.img
fastboot reboot
Update 21/12 fot US version change twrp.img
This twrp works correctly
Rename it's to twrp.img and replace in unzipped folder
Or use this code
Code:
adb reboot-bootloader
fastboot flash recovery twrp-m3-us-greatslon.img
fastboot reboot
All new version (And for EMUI5 too) this a lot of partitions for backup/restore and images can be download here
Where did you get the TWRP recovey from?
It's not on the TWRP.me website?
Flavio said:
Where did you get the TWRP recovey from?
It's not on the TWRP.me website?
Click to expand...
Click to collapse
Read subj )
It's my work.
Thx a lot.
I managed to root my M3 now.
Thanks fro your work but...
...will be the "own created" twrp-image really work on the new M3 due to that this is not official available on the twrp-homepage?!
Have I install the SuperUser-App from Chainfire too or will be this included?
Scrabbledo said:
...will be the "own created" twrp-image really work on the new M3 due to that this is not official available on the twrp-homepage?!
Have I install the SuperUser-App from Chainfire too or will be this included?
Click to expand...
Click to collapse
It is working on my M3 LTE without issues.
I tried flashing Chainfire's SuperUser with TWRP but that didn't work (bootloop).
I used the SRK Tool to get root.
remot command not allowed
Dear Greatslon!
unlocked the bootloader wir DC Unlocking client ... done.
I'm not able to write twrp to my device ..
download O.K.
remote command not allowed ...
failed
---->
DC unlocking did not realy unlock the device
done with unlock code from huawei page it work fine
---->
any idea?
kind regards in advance,
ein777er
Have you enabled USB debugging?
Flavio said:
It is working on my M3 LTE without issues.
I tried flashing Chainfire's SuperUser with TWRP but that didn't work (bootloop).
I used the SRK Tool to get root.
Click to expand...
Click to collapse
Hi @Flavio,
With the unlock-code I could unlock the bootloader.
On every start of the tablet I get now a warning that my device is untrusted, after some seconds it booted up into the normal "Desktop" view.
After I've activated again the USB-Debugging option I send it via "adb reboot bootloader" into the fastboot-mode and now the FRP-status shows "unlocked".
So, I've flashed the downloaded "twrp.img" to the recovery partition and reboot the tablet.
There is no difference to see, I get the untrust-note and then it is booting into the desktop view.
BUT how can I get into the twrp-mode? Normally when I boot up with "Volume-up"+"Power" but here it started into the Huawei EMUI Recovery console, not the TWRP surface. So I've flashed the twrp.img again but no change. And when I boot directly into the recovery "adb reboot recovery" I get the untrust-hint and the note that the system is booting now, but nothing is happen. Whit a cold-reset it shows the same screen. First when I go into the Huawei Recovery mode and press only "Reboot" it is booting up again as normal as before into the desktop mode.
My 2nd question is: you say you have used the SRK Tool to root your device. But under the link I can find a toot for the Huawei Mate 8 ? You mean I can download and use this tool for the Huawei Mediapad M3 too? ...after I could install TWRP?
Thanks for you help.
Greets,
Scrab
Flavio said:
Have you enabled USB debugging?
Click to expand...
Click to collapse
Dear Flavio!
thx.
with the unlock code from the huawei page it works fine
kind regards,
ein777er
---------- Post added at 06:49 AM ---------- Previous post was at 06:45 AM ----------
Dear scrab!
->My 2nd question is: you say you have used the SRK Tool to root your device. But under the link I can find a toot for the Huawei Mate 8 ? You mean I can download and use this tool for the Huawei Mediapad M3 too? ...after I could install TWRP?
The tool for huawei devices version 2.0 works fine (pont 4 (root), use another huawei device for routing)
kind regards,
ein777er
Thanks ein777er for this hint.
But before I can root my device I have to install TWRP. Here is currently my stop-point due to that fastboot tells that the twrp.img was installed without issues but when I boot into the recovery the tablet stops the boot on the "untrust"-screen and first when I go into the eRecovery-mode and reboot the tablet I will be back on the working surface.
For the root process the SRK tool want as well to boot into twrp first and I end up in the same stop-screen.
Maybe this is caused from the installed version of EMUI?
I made no updates/upgrades and have only unpack it from the box. So I have EMUI 4.1 as system.
Beside this is there any known fix yet to "hide" the untrust screen during the boot?
Greets,
Scrab
Dear Scrab!
>But before I can root my device I have to install TWRP. Here is currently my stop-point due to that fastboot tells that the twrp.img was installed without issues but when I boot into the recovery the tablet stops the boot on the "untrust"-screen and first when I go into the >eRecovery-mode and reboot the tablet I will be back on the working surface.
try this :
https://play.google.com/store/apps/details?id=gt.recovery.reboot
or
recoverymode : press vol+ and power
>Maybe this is caused from the installed version of EMUI?
>I made no updates/upgrades and have only unpack it from the box. So I have EMUI 4.1 as system.
i use it also out of the box
kind regards
Scrabbledo said:
Hi @Flavio,
BUT how can I get into the twrp-mode? Normally when I boot up with "Volume-up"+"Power" but here it started into the Huawei EMUI Recovery console, not the TWRP surface. So I've flashed the twrp.img again but no change. And when I boot directly into the recovery "adb reboot recovery" I get the untrust-hint and the note that the system is booting now, but nothing is happen. Whit a cold-reset it shows the same screen. First when I go into the Huawei Recovery mode and press only "Reboot" it is booting up again as normal as before into the desktop mode.
Click to expand...
Click to collapse
I need to turn off the tablet and then turn it on with Volume Up and Power on and hold it till TWRP starts.
//EDIT
OK last time I installed the Button combination changed. Try Vol+ and Vol- and Power. Had whole day headache till I recognized this
greatslon said:
Unlock bootloader
Download and unzip this archive
In command prompt:
Code:
adb reboot-bootloader
fastboot flash recovery twrp.img
fastboot reboot
Click to expand...
Click to collapse
I get an error when I try to make a backup: createTarFork() process ended with ERROR: 255.
Everything else I tested works great.
sebbo2015 said:
I get an error when I try to make a backup: createTarFork() process ended with ERROR: 255..
Click to expand...
Click to collapse
try to make backup to internal storage
---------- Post added at 03:52 PM ---------- Previous post was at 03:45 PM ----------
If your M3 USB plug (charger or computer) you can't go TWRP, only EMUI recovery.
please use Vol+ and Power when not connected USB for custom recovery
So I have my bootloader unlocked via the official huawei website method, and now I'm trying to flash twrp. I followed the instructions and attempted to flash twrp. See the attached screenshot of my command window. It seems like it finished successfully (only took 0.7 seconds) but I saw nothing happen on the tablet itself. Just the same white screen with the android logo that says FASTBOOT&RESCUE MODE. No script or anything changed. So far I've been unable to boot into TWRP.
I have tried holding down the VOL UP + POWER combination and it takes me to the black "Your device has been unlocked and can't be trusted." screen with the text "Your device is booting now..." at the bottom and the tablet will just stay frozen there. Then if I hold the power button for a few seconds it will take me to a similar black screen but with three options. If I do option (1) which is to hold the VOL UP button for 3 seconds it will take me to the EMUI recovery not TWRP.
Hopefully someone can help out here.
I'm stuck on the same step as you. Greatslons version of twrp doesn't seem to work on the US versions. Just freezes upon boot. Anyone have any idea why that would be?
Fyi, my working twrp flash to my non-US M3 was also very fast. So fast that I thought it didn't really do anything. But it worked.
Did you guys do the OEM unlock step? I wonder if there is some kind of region locking between the hardware and the bootloader.
I did the OEM unlock step. I also tried flashing it to recovery and recovery2, both of which didn't work. Sucks cause we can't root without twrp, yet we have our bootloaders unlocked.
elsamuraiguapo said:
So I have my bootloader unlocked via the official huawei website method, and now I'm trying to flash twrp. I followed the instructions and attempted to flash twrp. See the attached screenshot of my command window. It seems like it finished successfully (only took 0.7 seconds) but I saw nothing happen on the tablet itself. Just the same white screen with the android logo that says FASTBOOT&RESCUE MODE. No script or anything changed. So far I've been unable to boot into TWRP.
I have tried holding down the VOL UP + POWER combination and it takes me to the black "Your device has been unlocked and can't be trusted." screen with the text "Your device is booting now..." at the bottom and the tablet will just stay frozen there. Then if I hold the power button for a few seconds it will take me to a similar black screen but with three options. If I do option (1) which is to hold the VOL UP button for 3 seconds it will take me to the EMUI recovery not TWRP.
Hopefully someone can help out here.
Click to expand...
Click to collapse
Exact same issue here I got the unlock code and unlocked the bootloader, no issues there. Next I flashed twrp and got the exact same result as you. There doesn't seem to be any way to get in to twrp at all... I even tried "adb reboot recovery" but it just goes in to the "Your device has been unlocked.. " screen and then says "Your device is booting now...", then gets hung on that screen. How do we get past this? Thanks in advance for any help.
I bought this device thinking I could root it
I'm in the USA and I bought the device from Amazon: https://www.amazon.com/gp/product/B01LB08BH6/
Related
I want to install cwm recovery in my canvas a1 for backup my current rom android 4.4.4.
I m going to install lollipop 5.1 I heard about some bug in lollipop so for my safety i want a backup.
I used minimal adb and fastboot for installing cwm.
But when i type the command "fastboot flash recovery recovery.img"
End hit enter
Then it show a error.
"Failed (remote download for partition 'recovery' is not allowed'
What should i do now?
http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165
Go to this thread and follow the simple instructions...dnt go through such command prompts..when an easy way is available hit thanks if i helped
MaxySpark said:
I want to install cwm recovery in my canvas a1 for backup my current rom android 4.4.4.
I m going to install lollipop 5.1 I heard about some bug in lollipop so for my safety i want a backup.
I used minimal adb and fastboot for installing cwm.
But when i type the command "fastboot flash recovery recovery.img"
End hit enter
Then it show a error.
"Failed (remote download for partition 'recovery' is not allowed'
What should i do now?
Click to expand...
Click to collapse
Before flashing CWM recovery, you have to unlock the boot loader, using the command:
Code:
fastboot oem unlock
Then press Volume Up in phone to confirm.
Now you can flash.
Note: Unlocking bootloader formats the User data (/data partition), such as apps and other settings. Take a backup using Titanium Backup Tools, then proceed
Your recovery partition is locked.
1. Make yourself a developer (go to Settings -> About Phone -> Tap on Build until developer
2. In Developer options turn on Enable OEM unlock
3. Flash the new recovery, don forget to "fastboot oem unlock"
4. Important: don't allow phone to complete a normal reboot after flash. When rebooting, press Vol Up + Vol Down + Power to enter CWM recovery directly. Otherwise the stock recovery will replace CWM again.
When I type the command "fastboot oem unlock" and press enter, my phone displays a long-ish disclaimer text about the dangers of unlocking the bootloader, ending with the instruction to use Volume Up key to confirm ("YES, unlock...") or the Volume Down key to cancel ("NO, don't unlock..."). Pressing Volume Down works as expected: the line "returning to fastboot in 3secs" is displayed, followed by a return to fastboot. But pressing Volume UP seems to have NO EFFECT at all!! NOthing highlighted, no change in the screen, pressing power afterward does nothing. It is not a hardware problem of the Volume Up button either -- Volume Up/Down keys work in normal apps and in recovery mode just fine.
I was hoping that perhaps it just silently succeeded, but when i next try to flash the CWM recovery img, I still get 'sending recovery' OKAY but 'writing recovery' FAILED??
what do I do to get the volume UP to work while the phone in this mode??
BTW the phone is a Rook 4G phone from EE here in the UK. This is apparently the same as a ZTE Blade 3 A410 phone with carrier branding.
THANKS in advance for any help!
sbpetrack said:
When I type the command "fastboot oem unlock" and press enter, my phone displays a long-ish disclaimer text about the dangers of unlocking the bootloader, ending with the instruction to use Volume Up key to confirm ("YES, unlock...") or the Volume Down key to cancel ("NO, don't unlock..."). Pressing Volume Down works as expected: the line "returning to fastboot in 3secs" is displayed, followed by a return to fastboot. But pressing Volume UP seems to have NO EFFECT at all!! NOthing highlighted, no change in the screen, pressing power afterward does nothing. It is not a hardware problem of the Volume Up button either -- Volume Up/Down keys work in normal apps and in recovery mode just fine.
I was hoping that perhaps it just silently succeeded, but when i next try to flash the CWM recovery img, I still get 'sending recovery' OKAY but 'writing recovery' FAILED??
what do I do to get the volume UP to work while the phone in this mode??
BTW the phone is a Rook 4G phone from EE here in the UK. This is apparently the same as a ZTE Blade 3 A410 phone with carrier branding.
THANKS in advance for any help!
Click to expand...
Click to collapse
Hi, I have exactly the same situation!
No effect on Volume UP. I can't understand...
marc2800 said:
Hi, I have exactly the same situation!
No effect on Volume UP. I can't understand...
Click to expand...
Click to collapse
Absolutely identical experience here with the Alcatel One Touch Pop 3 - 5015x. I was following this tutorial http://forum.xda-developers.com/and...lcatel-one-touch-pop-s3-t3060092/post65430049, had a problem with the OEM, solved it by finding the top post on THIS thread and now I have the exact same issue as you two gentlemen. Any help would be appreciated, cus the phone seems bricked as it is. It's stuck in boot loop and receiving no input.
Thi is NOT the exact same issue as we have: you are stuck in a boot-loop; we have a version of fastboot which seems to have disabled the volumeUp button, thereby making it impossible to confirm our request to unlock the bootloader. e can only press VolumeDown (which cancels our request to unlock the bootloader).
i posted at http://forum.xda-developers.com/showpost.php?p=65462453&postcount=48 a suggestion for how to proceed in your case: just use SP Flash tools to reinstall a stock recovery image, and then use that recovery to install a complete stock ROM.
,BTW, Sir, when you say:
> ...with the Alcatel One Touch Pop 3 - 5015x. I ... had a problem with the OEM, solved it by finding the top post on THIS thread
note that the solution given in the top post of this thread is designed for Android One devices, and your Alcatel One Touch does NOT appear in the list of supported devices for that "fix." can't say it's entirely surprising that you would get into a bootloader problem if you apply top your phone a bootloader unlock solution for some random other platform!! LUck would not likely be with you when doing that.
zeta274 said:
Absolutely identical experience here with the Alcatel One Touch Pop 3 - 5015x. I was following this tutorial http://forum.xda-developers.com/and...lcatel-one-touch-pop-s3-t3060092/post65430049, had a problem with the OEM, solved it by finding the top post on THIS thread and now I have the exact same issue as you two gentlemen. Any help would be appreciated, cus the phone seems bricked as it is. It's stuck in boot loop and receiving no input.
Click to expand...
Click to collapse
I can't understand why volume down is working fine and not volume UP...
zeta274 said:
Absolutely identical experience here with the Alcatel One Touch Pop 3 - 5015x. I was following this tutorial http://forum.xda-developers.com/and...lcatel-one-touch-pop-s3-t3060092/post65430049, had a problem with the OEM, solved it by finding the top post on THIS thread and now I have the exact same issue as you two gentlemen. Any help would be appreciated, cus the phone seems bricked as it is. It's stuck in boot loop and receiving no input.
Click to expand...
Click to collapse
Go in bootloader mode, connect your phone to your computer and tell me what do you get if you tape in your console "fastboot devices"
I want to know the number before fastboot.. mine is strange and maybe not the original
MaxySpark said:
I want to install cwm recovery in my canvas a1 for backup my current rom android 4.4.4.
I m going to install lollipop 5.1 I heard about some bug in lollipop so for my safety i want a backup.
I used minimal adb and fastboot for installing cwm.
But when i type the command "fastboot flash recovery recovery.img"
End hit enter
Then it show a error.
"Failed (remote download for partition 'recovery' is not allowed'
What should i do now?
Click to expand...
Click to collapse
That is also my problem with my phone!
---------- Post added at 05:56 AM ---------- Previous post was at 05:54 AM ----------
GokulNC said:
Before flashing CWM recovery, you have to unlock the boot loader, using the command:
Code:
fastboot oem unlock
Then press Volume Up in phone to confirm.
Now you can flash.
Note: Unlocking bootloader formats the User data (/data partition), such as apps and other settings. Take a backup using Titanium Backup Tools, then proceed
Click to expand...
Click to collapse
Hi, I had done that fastboot oem unlock command and pressed Volume Up but nothing happened and my bootloader still locked could you help? Thanks, my phone is Starmobile UP HD MTK6582 :laugh:
GokulNC said:
Before flashing CWM recovery, you have to unlock the boot loader, using the command:
Code:
fastboot oem unlock
Then press Volume Up in phone to confirm.
Now you can flash.
Note: Unlocking bootloader formats the User data (/data partition), such as apps and other settings. Take a backup using Titanium Backup Tools, then proceed
Click to expand...
Click to collapse
really thanks:angel:
I can't
I have an error installing a ROM, partition x not allowed.
I can't go in recovery mode + I can't open my phone to enable usb debugging.
I don't have root & and I don't have my OEM unlocked.
How can I install my ROM for Asus Zenfone GO ZC500TG? :'( :'(
Anyone, please?!!
ADB devices allowed?
I have the same problem, but i just resolve it now. First, i've connected my phone in normal mode, then i opened cmd and wrote: adb devices, and a popup displayed in my phone to allow adb debug. I allowed and reboot to bootloader and follow all steps to unlock bootloader.
I also have problems, my phone is a polaroid turbo c4 plus and i cand get through the setup, so i can't install cwm and i am searching for methods to recover it, it's pretty hard since theres nothing online about it
For those that, like me, could not get driver recognition on the latest Win 10 x64 no matter what you tried. And ,yes, using every tutorial I could find on this and two "other Forums". Odin failed to see my device (still can't) Cydia impactor allows rebooting into fastboot and D/L but doesn't connect in either alt. mode. Yes, drivers all removed and replaced in varying states (usbdeview, etc.).
But ADB/Fastboot works!
Make sure you have your adb/fastboot drivers installed universally (Check this Fabulous Forum)
Download device-specific TWRP - I used this one for the 4gb version - https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
L.Shift-R. click in the folder you downloaded to (Open Command Window Here) - "adb devices" (to make sure device registers) then - "adb reboot bootloader" gets you into fastboot. - "fastoot boot {your-recovery-name}.img"
I got a fully functional TOUCH CAPABLE TWRP. Which I proceeded to load this - https://www.dropbox.com/s/j1owqv7mjkdpo75/UPDATE-SuperSU-v2.46.zip?dl=0 - and, VOILA! ROOT!!
I had similar issues with my laptop and drivers. Used a friend laptop in the end to "see" the phone and install twrp.
Sent from my S7 using Tapatalk
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
vaskovass said:
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
Click to expand...
Click to collapse
Hi there, I have the same issue. No success
I found a way, instead of volume up, use the home button this worked for me.. however after I unlocked the OEM and flashed TWRP the phone didn't want to boot anymore. It was stuck on Elephone logo with warning: "Orange State: The phone has been unlocked and can't be trusted. Your device will boot in 5s", however it didn't boot and stayed like that for almost an hour. Had to flash back the stock firmware to boot. Tried 1 more time the procedure to root but again the same. Maybe I do something wrong?
stock fw flash back
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
dnsgtr said:
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
Click to expand...
Click to collapse
I read somewhere the is a zip inside the update.zip & is that one that is flash able with twrp.
Have a look
During the main time I managed to flash the 0218 stock rom.
I still got the orange message but the phone finally boot. Then I just called the twrp recovery img via atb. I did nothing only touch the reboot in the twrp screen and since then "Orange status...." again.
May be the twrp recovery img is not the right one...
Bad command "fastoot boot {your-recovery-name}.img"
after OEM alow (informacion phone/compilacion number touch fast 9 times/access/alow oem)
fastboot oem unlock
"fastboot boot {your-recovery-name}.img" for me is fastboot boot recovery.img and all OK
bat still not working (phone not thrust unlocked bootloader cleaning data in 5..4..3..2..1.. and rebot)
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Shadowsalyer said:
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Click to expand...
Click to collapse
small chance you enable root from developer options. (i think it will be adb only)
if so , maybe can use adb shell and "dd" to write recovery to correct partition.
problem is many of the available twrp do not boot on custom rom .
example code. (if you do wrong , it may be bad)
Code:
dd if=/ext_sdcard/twrp_Recovery_ramdisk.img of=/dev/block/mmcblk0p32
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Shadowsalyer said:
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Click to expand...
Click to collapse
Like what you have , twrp stuck on splash screen
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Shadowsalyer said:
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Click to expand...
Click to collapse
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Just to clarify, it gets stuck on TWRP splash screen. When I turn off the phone, it immediately boots up again into TWRP. I tried getting into fastboot mode with all kinds of combinations of button presses, but no luck. Not even Volume Up + USB cable works
smokinjoe2122 said:
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
I have seen this happen before , solution was to wait for dead battery, or disassemble to unplug battery
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
This is because after the frp unlock, it needed to see a factory reset, and it usually needs to be done with stock recvery.
So will have to wait till battery is dead and and plug in usb while holding volume button. Should then load to fastboot. Where it is best to flash stock recovery to clear the recovery bootloop. The bootloop is do to the fact yo unlocked frp and now phone needs to wipe/data
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
dcraffam said:
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
Click to expand...
Click to collapse
i just took mine apart and discconected the battery and still no luck that program deleted my fastboot
Please can you tell me the process to install twrp I have the L24
I waited all the way till the battery drained, stuck in the USB, and it booted to ROM! Sadly it immediately shut off again because the battery is dead (even with keeping the USB in). I'm going to keep trying though.
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Shadowsalyer said:
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Click to expand...
Click to collapse
Seems to be a f-up situation either way.
You have adb DD available, found out before.
Don't know if maybe flashing stock recovery is good idea at this point.
I think fastboot.img can be flashed with DD too, but don't try till someone can confirm.
If flash stock recovery clears the loops, maybe best to do full-ota manual flashing.
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Shadowsalyer said:
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Click to expand...
Click to collapse
Fastboot.img is the large part the bootloader. If flashing it goes bad, might be dead phone after, just rember that.
Will add a list of partition names and command s for you soon.
here is a list of oreo partitions and there /dev/blk/** number
and here is an example of code to save images with dd assuming you put the images on your extrnal-sdcard in folder called oreo-images
Code:
dd if=/dev/block/mmcblk0p5 of=/mnt/ext_sdcard/oreo-images/fastboot.img
Do that save first and compare the md5 of the file from update.app to this file.
or just check the md5 before making the copy
Code:
adb shell md5sum /dev/block/mmcblk0p5
If you are conviced you need to flash the images, here is example of writing the image assuming files are in sdcard folder oreo-update-images
Code:
dd if=/mnt/ext_sdcard/oreoupdate-images/fastboot.img of=/dev/block/mmcblk0p5
As I have said, this might be bad advise , I have not done fastboot.img flashing before. But on other devices it is same as lk.img or uboot.img, There is danger in flashing it incorrectly. That is why my suggestion was to flash no-check-recovery and do manael update with "echo -update_package" commands.
Along with the statement that fastboot.img is similar to lk.img or uboot.img on other phones, Your fastboot cannot be gone. because phone boots.
but do let us know how it goes.
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Shadowsalyer said:
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Click to expand...
Click to collapse
To recovery_ramdisk. 32
What about check md5 of fastboot partition, that will be helpful to know if it did get wiped out.?
Hmm seems like I'm not allowed to use dd after all:
HWBND-H:/ $ dd if=/storage/7C96-7E17/BND-RECOVERY-NoCheck.img of=/dev/block/mmcblk0p32
dd: /dev/block/mmcblk0p32: Permission denied
And here I was thinking I was close to solving it...
Also can't run md5sum on the fastboot partition, since that needs root as well.
Hello,
I was on stable global indian 10.4.4 (INMX), unlocked, rooted, twrp.
Then got notification of update, downloaded update, reboot (as prompted by updater app), update failed, error 7.
Rebooted phone to system. Updater said to download full rom now which i did,, and reboot again, same error.
I thought twrp might b incompatible with update so i flashed stock recovery n repeated all above.
Now phone stuck at bootloop and does not boot into recovery or fastboot by pressing vol+/- and power,, also pressing all three together is not working.
PC doesn't detect phone as it keeps rebooting in loop.
Any way to force boot in fastboot??
beachfl said:
When it very first shuts down (the redmi logo first disappears and it goes black), before it starts to boot up again, press and hold Volume Down and Power until it takes you to fastboot.
Click to expand...
Click to collapse
Cannt go to fastboot bro by this way
majidmjmn said:
I have exactly the same problem with my redmi note 8 pro after trying to flash another twrp on my rooted unlocked phone it juat shows redmi and then goes off,no recovery and no fastboot available!
I don't know about adb shell commands would you Please explain the instructions and procedure in more details
Tnx
Click to expand...
Click to collapse
same problem bro. let me know how you solve this problem please
yeswe61155 said:
Cannt go to fastboot bro by this way
Click to expand...
Click to collapse
If it is bootlooped... you can get to fastboot... keep trying... you just have to catch it at the right time.
Letting the battery run out, then charge and try to start in quick start
danyv77 said:
Letting the battery run out, then charge and try to start in quick start
Click to expand...
Click to collapse
Thank you. Will do that and update.
danyv77 said:
Letting the battery run out, then charge and try to start in quick start
Click to expand...
Click to collapse
Update : didn't work. Still went into same. Tried 4-5 times.
I think you have to open the back cover, disconnect the battery connector, connect it to computer, hopefully it will get detected as mediatek then you can follow this guide
danyv77 said:
Letting the battery run out, then charge and try to start in quick start
Click to expand...
Click to collapse
gugelgigel said:
I think you have to open the back cover, disconnect the battery connector, connect it to computer, hopefully it will get detected as mediatek then you can follow this guide
Click to expand...
Click to collapse
Unfortunately that didn't work either. Sent to Mi Service center, they tried EDL by opening back cover,, didn't work. Now sent phone to xiaomi by service center, i'll get either this one repaired or new one in a week. (as per Mi)
Surprisingly i wasn't the only one or first one to report this. There have been similar incidences earlier as well and even the ones that were on stock everything and locked bootloader. Apparently the new update 11.0.1 is troublesome. - as reported by Mi executive.
Here's my solution
I've got my brand new Redmi Note 8 Pro and just unlocked it yesterday. Today I install the Global ROM and it just work fine BUT I when further : root and install magisk... Then I got a recovery boot loop, I try to solve the issue by flashing another TWRP and then BAM no more fastboot and no more recovery, really bricked hard.
I was using this custom TWRP mention here: https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919
Please share this solution everywhere because that really solve my issue:
(1) Flash recovery using adb YESSSSS
Source: https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/
Enable your USB debugging bridge in switch via adb to the terminal:
./adb shell
Then you should be able to find your recovery partion with:
DEV=$(ls /dev/block/platform/*/by-name/recovery); echo $DEV
that should output something like this:
/dev/block/platform/7824900.sdhci/by-name/recovery
If this is the case you only have to put the recovery.img on your sd-card or the internal storage and you are one command from flashing:
dd of=$DEV if=/external_sd/recovery.img
Thats it! No binaries you have to install. No ****ty fastboot udev rules :S
You can enter into your new recovery system with:
./adb reboot recovery
2) Good now I was able to be back in the LR Team TWRP. From there I removed root and thus magisk, completely disabled DM Verify (because this custom TWRP install everything it can also remove it) and wonder happen, I was able to boot my phone and fastboot is back !
pmesolution.ca said:
I've got my brand new Redmi Note 8 Pro and just unlocked it yesterday. Today I install the Global ROM and it just work fine BUT I when further : root and install magisk... Then I got a recovery boot loop, I try to solve the issue by flashing another TWRP and then BAM no more fastboot and no more recovery, really bricked hard.
I was using this custom TWRP mention here: https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919
Please share this solution everywhere because that really solve my issue:
(1) Flash recovery using adb YESSSSS
Source: https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/
Enable your USB debugging bridge in switch via adb to the terminal:
./adb shell
Then you should be able to find your recovery partion with:
DEV=$(ls /dev/block/platform/*/by-name/recovery); echo $DEV
that should output something like this:
/dev/block/platform/7824900.sdhci/by-name/recovery
If this is the case you only have to put the recovery.img on your sd-card or the internal storage and you are one command from flashing:
dd of=$DEV if=/external_sd/recovery.img
Thats it! No binaries you have to install. No ****ty fastboot udev rules :S
You can enter into your new recovery system with:
./adb reboot recovery
2) Good now I was able to be back in the LR Team TWRP. From there I removed root and thus magisk, completely disabled DM Verify (because this custom TWRP install everything it can also remove it) and wonder happen, I was able to boot my phone and fastboot is back !
Click to expand...
Click to collapse
you should share this information in the other posts, to see if it works for others
djzero86 said:
you should share this information in the other posts, to see if it works for others
Click to expand...
Click to collapse
Yes I did share it to the other post which I followed the tutorial But I think my method will allow anyone having access to adb and not Fastboot to flash and boot a new TWRP image which could allow them to flash once again a ROM from the Recovery or modify the source code an fix their issue.
Redmi note 8 pro no recovery and fastboot
I have exactly the same problem with my redmi note 8 pro after trying to flash another twrp on my rooted unlocked phone it juat shows redmi and then goes off,no recovery and no fastboot available!
I don't know about adb shell commands would you Please explain the instructions and procedure in more details
Tnx
My phone keeps restart
I have the same issiue and my phone keeps restart i can't give any command to solve this proplem please help me
Similar issue,
I get the Redmi splash screen, and then it reboot after about 3 seconds. During the reboot cycle, which takes another few seconds - thats the only time my PC can detect the phone.
So Smart Phone Flash Tool can detect it for those few seconds, starts download but then timeouts after 2 minutes (status protocol err). I guess it loses connection.
Phone can't boot into recovery or fastboot. Is it hardbricked/beyond repair ?
More details:
https://forum.xda-developers.com/showpost.php?p=82467553&postcount=16
poster74 said:
Similar issue,
I get the Redmi splash screen, and then it reboot after about 3 seconds. During the reboot cycle, which takes another few seconds - thats the only time my PC can detect the phone.
So Smart Phone Flash Tool can detect it for those few seconds, starts download but then timeouts after 2 minutes (status protocol err). I guess it loses connection.
Phone can't boot into recovery or fastboot. Is it hardbricked/beyond repair ?
More details:
https://forum.xda-developers.com/showpost.php?p=82467553&postcount=16
Click to expand...
Click to collapse
How you brick your phone?
Flash without autorized account
Does any of you guys use the method that mentined in this site bellow
Just type how to flash redmi note 8 pro without authorized accound in google and clike on link proveded by romprovider..(link was deleted by xda so i coulden't share it)
Use it and let me know if it works for you...
Nasser Nody said:
I have the same issiue and my phone keeps restart i can't give any command to solve this proplem please help me
Click to expand...
Click to collapse
use the method that mentined in this site bellow
and let me know if it works for you...
just type how to flash redmi note 8 pro without authorized accound in google and clike on link proveded by romprovider..(link was deleted by xda so i coulden't share it)
majidmjmn said:
I have exactly the same problem with my redmi note 8 pro after trying to flash another twrp on my rooted unlocked phone it juat shows redmi and then goes off,no recovery and no fastboot available!
I don't know about adb shell commands would you Please explain the instructions and procedure in more details
Tnx
Click to expand...
Click to collapse
Now you all already solved this problem? plz mention me plz plz
yeswe61155 said:
Now you all already solved this problem? plz mention me plz plz
Click to expand...
Click to collapse
When it very first shuts down (the redmi logo first disappears and it goes black), before it starts to boot up again, press and hold Volume Down and Power until it takes you to fastboot.
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.