Hi,
I am looking how to fix my friend's Realme 8 5G (RMX3241) phone.
Here is the story:
1) My friend downgraded his firmware but by an accident installed ROM for India region, the result was he had no GSM signal on the phone (he lives in EU).
2) He also unlocked bootloader, but probably not correctly, because it shows orange state and I can't go into recovery with combination vol up + power
3) The phone booted, but no GSM.
What I did:
1) Managed to boot into recovery using "adb reboot recovery".
2) Then I pressed 'reboot' in recovery (I wanted to load a proper region ROM) and since then I am watching "realme" logo for like 10 minutes straight, so I assume it went into bootloop.
What I can do now:
1) After pressing vol down + power it shows:
oplus Verify fail
need to verify signature of another brand
oplus Verify pass
fastboot verify success
fastboot_unlock_verify ok
However in this state I can't reach this phone using adb
2) Pressing vol up + power doesn't boot into recovery, just normally boots the system but it goes into bootloop.
3) The orange state is still there.
So assume I am now left with bootlooped system with no access to ADB.
Can anyone help me with this? Are there any solutions to this?
Tried SP Flash tool but after loading scatter file it shows:
Platform MT68 not support on this version.
Please update to latest flashtool and try again.
Well, I have a solution for that.
It seems that the system is bricked, so you need to download a proper firmware version for your phone, and flash the stock ROM via fastboot (platform-tools) by erasing super and vbmeta partitions, and flashing every single IMG file of the firmware stock ROM.
2) He also unlocked bootloader, but probably not correctly, because it shows orange state and I can't go into recovery with combination vol up + power
Click to expand...
Click to collapse
Orange state is normal also as far as i know there is not a button combination to boot into recovery on this phone
1) After pressing vol down + power it shows:
oplus Verify fail
need to verify signature of another brand
oplus Verify pass
fastboot verify success
fastboot_unlock_verify ok
However in this state I can't reach this phone using adb
Click to expand...
Click to collapse
This is fastboot mode and you have to use fastboot which is bundled with adb, in this state you can: unlock bootloader, flash partitions or you can reboot to recovery
Taracair said:
Tried SP Flash tool but after loading scatter file it shows:
Platform MT68 not support on this version.
Please update to latest flashtool and try again.
Click to expand...
Click to collapse
SP_Flash_Tool_v5.2124 works for me
You have to:
Have proper VCOM MTK drivers installed
Boot the phone by pressing vol up + vol down while connected to pc via usb
Use MTKAuthBypass v7 before flashing in order to bypass auth protection system.
UPDATE:
mtkclient it's perfect and on the github everything is explained on how to use it
Related
So I already had a rooted (and I'm pretty sure unlocked bootlader) version of the stock Asus and wanted to put CM13 nightly on there. Everything was going smooth until I got to the stage where I have to load into TWRP and I got the error screen with the little dead alien and the red symbol.
Now I can't enter normal boot, but entering recovery mode seems to work. I tried the option to side load a package from ADB on that screen but nothing worked (.zip files extracted, but I got an error on the phone).
As you can tell, I'm really new to this so any help would be greatly appreciated. I tried looking around, but it seems the more common issue is people not being able to enter recovery mode or something similar.
Thanks
Looks like your doing it wrong. Being rooted does not necessarily mean that your bootloader is unlocked.
By the looks of it your in recovery mode with the dead robot with the "error" message. That is normal. To reboot back into system you either have to press (I don't remember) power button and volume up or down button. Then you should see some options with reboot to system. Or if that does not work you can hold the power button till it turns off.
Then you get back into Android, download the official bootloader unlock tool from ASUS and install it on your device. NOTE: If you updated to MM then this will not work and this will void your warranty.
Run the tool and press unlock and it should reboot into fastboot where it should begin the unlocking process. I believe it should automatically reboot and you should see that the Asus logo is now black instead of white. If not, repeat the process.
You can now proceed to flash twrp recovery. Boot into fastboot/bootloader mode either with "adb reboot bootloader" or hold a specific set of buttons while off to go directly into fastboot.
On the computer, connect your device and type in "fastboot flash recovery (path to twrp IMG without brackets)"
When done you should be able to reboot into twrp recovery where you can flash the cm13 zip.
Hope this helped.
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)
Recently i've unlocked my bootloader in order to install a custom ROM. Everything went fine until i flashed twrp image. Whenever i try to get into recovery ( power+vol up ) it pops a window saying "Firmware Update". In the cmd log it says that recovery flashed successfully. I've enabled OEM unlocking and adb in the dev settings. BL is unlocked. Device was connected to the PC at the moment of flashing ( obviously ) aswell as at the moment of entering the recovery.
Please help me find a solution, thanks.
fastboot flash recovery twrp.img and then enter recovery by holding power + vol down (to get into bootloader) and then choose recovery mode and enter.
Exactly what Przemcio said. Flash the TWRP from your PC using fastboot, and then boot into it from the bootloader. I never use Pwr+Vol_Up, I always use Pwr+Vol_Dn to get into whatever I want.
Vol up is for LG Flash tools only.
I flash recovery via fastboot. Press vol down
Sent from my Pixel using Tapatalk
yeah, it's orange encrypted and now i have to decrypt.
i just can't bypass this message "your device cannot be checked for corruption". Whenever i try to choose the recovery this pops up and then phone reboots. I flashed stock google image for nexus 5x and it didn't solve the issue, nor fomratting data thru adb.
Hello everyone! Complete dumbass here!
I was following the guide to root my razer phone. I've had it for a couple months, and decided to root it. I followed the guide here https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137
After a couple bumps in the road, such as fastboot commands not working, not being recognized, etc. I finally was able to unlock bootloader and install twrp. But it was #9 that got me stuck again.
"9.) Once in recovery, go to the install button, and select Install Zip, and select Magisk-v16.0.zip."
In recovery, adb devices and fastboot devices yielded no devices attached. Doing a search, I came across another forum post where it states the sdcard is encrypted and can't be accessed in twrp, and the fix is to do something like "Wipe>Wipe Data> Type Yes" and that should factory set the card. I did this and rebooted the device. I waited for a half hour for the animated PixelFloatingInACircle logo to be done with it's floating in a circle, but ended up going to bed and letting it die. Woke up this morning, plugged it in, got the razer logo splash screen with the orange text telling me of my impending doom, then went back to the animation. I let my dog out and came back and it was still on. I unplugged it and am letting it die again to see if there's another solution.
I'm wondering if anyone else came across this issue, and if so, how did they fix it? Any help would be appreciated.
Use the factory images in the developer portal. You have to manually install the fastboot driver or you won't see the phone in fastboot devices. After that you can flash_all.bat.
PS: if you just want root you can use magisk installer to patch the boot image (from the factory images) and then flash the patched_image.img. That's it, now you have root via magisk
waiflih said:
Use the factory images in the developer portal. You have to manually install the fastboot driver or you won't see the phone in fastboot devices. After that you can flash_all.bat.
PS: if you just want root you can use magisk installer to patch the boot image (from the factory images) and then flash the patched_image.img. That's it, now you have root via magisk
Click to expand...
Click to collapse
The problem is when I try to enter download/recovery mode after charging the battery a little, it doesn't go to that menu. Instead, it skips right to the particle logo, and that's where it hangs.
The only guide I saw was the one I listed. Is there a guide for this magisk installer?(Ya know, in case I figure the first problem out, so I might try my hand at potentially creating another)
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons.
Edit: the button combination is power+vol+ for about 10-15 seconds, and the phone will reboot. You have to connect the phone via usb cable (before rebooting) to the computer (the only thing i'm not sure is if you have to have the fastboot drivers in the pc installed previously or if you can do it after entering fastboot) and just after the screen goes black while hard rebooting you have to release all the buttons and then press and hold the vol- button. The combination of vol- and the usb cable on boot seems to trigger fastboot mode.
I think the guide is in the guides forum, but the way it worked for me was without twrp:
- install magisk manager from this link -> https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
- push your boot.img (the easiest way is getting it from the factory image corresponding to the firmware you are using) to the sdcard
- open magisk manager -> install -> patch image only -> boot.img
- this will generate a patched_boot.img in /sdcard/MagiskManager
- copy that file to your pc
- go to fastboot and flash that patched image: fastboot flash boot patched_boot.img
- enjoy root, and you can use magisk hide for apps that don't like root
Regards
waiflih said:
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons
Click to expand...
Click to collapse
Tried this originally after I let it die the first time. It still boot to the animation logo.
Bloodeagle said:
Tried this originally after I let it die the first time. It still boot to the animation logo.
Click to expand...
Click to collapse
Read the edit, I found that the trigger is having the usb cable connected to the pc. Try that, or you can also try to adb while the device is booting (particles logo). Sometimes adb is responsive even when booting. There you can try to adb reboot bootloader
waiflih said:
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons.
Edit: the button combination is power+vol+ for about 10-15 seconds, and the phone will reboot. You have to connect the phone via usb cable (before rebooting) to the computer (the only thing i'm not sure is if you have to have the fastboot drivers in the pc installed previously or if you can do it after entering fastboot) and just after the screen goes black while hard rebooting you have to release all the buttons and then press and hold the vol- button. The combination of vol- and the usb cable on boot seems to trigger fastboot mode.
I think the guide is in the guides forum, but the way it worked for me was without twrp:
- install magisk manager from this link -> https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
- push your boot.img (the easiest way is getting it from the factory image corresponding to the firmware you are using) to the sdcard
- open magisk manager -> install -> patch image only -> boot.img
- this will generate a patched_boot.img in /sdcard/MagiskManager
- copy that file to your pc
- go to fastboot and flash that patched image: fastboot flash boot patched_boot.img
- enjoy root, and you can use magisk hide for apps that don't like root
Regards
Click to expand...
Click to collapse
Progress! Got it into download mode. I have the boot.img I got from razer, should I push that and see if it boots normally?
Bloodeagle said:
Progress! Got it into download mode. I have the boot.img I got from razer, should I push that and see if it boots normally?
Click to expand...
Click to collapse
As you already wiped the data partition, you should use the flash_all script. But yes, you can try flashing each partition
waiflih said:
As you already wiped the data partition, you should use the flash_all script. But yes, you can try flashing each partition
Click to expand...
Click to collapse
I moved the flash_all script into the tools folder and after a little while, the phone booted up into setup! After a couple taps, I've realized the wifi isn't working, which I know is a known issue. I'm gonna let it sit for the night and finish it in the morning!
EDIT : Soooo, I know I said I was going to bed, but I decided to fix the wifi issue, which in turn, also rooted my phone. I've downloaded the root checker, and it confirms it! Thanks so much Waiflih! You rock!
Hi guys, it seems I'm having the same problem and basically after unlocking my bootloader and flashing twrp to both of my slots I'm stuck on "Your device has been unlocked and can't be trusted" booting up infinitely.
The USB plug in and holding the volume - button doesn't bring up "download mode" and no matter what buttons I try and press on my phone my computer doesn't recognize ANYTHING connected to it anymore.
Bloodeagle, how did you manage to get "download mode" back onto your phone? it seems like mine refuses to do anything like download mode.
saberhashemi said:
Hi guys, it seems I'm having the same problem and basically after unlocking my bootloader and flashing twrp to both of my slots I'm stuck on "Your device has been unlocked and can't be trusted" booting up infinitely.
The USB plug in and holding the volume - button doesn't bring up "download mode" and no matter what buttons I try and press on my phone my computer doesn't recognize ANYTHING connected to it anymore.
Bloodeagle, how did you manage to get "download mode" back onto your phone? it seems like mine refuses to do anything like download mode.
Click to expand...
Click to collapse
Have you tried holding few combinations of different butt9ns for a minute or two to see if that results in you getting in downl9ad mode?
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.