Related
Hello Users,
I have a Asus Zenfone 2 [Z00a]. Yesterday I want downgrade my phone to Stock Rom (Android 5). After I installed some files with Adb on my Pc, I restarted my Phone and I want to go the Recovery Mode. Now my Recovery Mode doesn't functionate. When my Phone start I come into Bootloader Mode instantly without push any buttons on my Phone. When I selected the Recovery Mode with the Power Button. My Phone restart automatic and the Bootloader start again.
I hope you can help me.
Scoocyjuice
Scoocyjuice said:
Hello Users,
I have a Asus Zenfone 2 [Z00a]. Yesterday I want downgrade my phone to Stock Rom (Android 5). After I installed some files with Adb on my Pc, I restarted my Phone and I want to go the Recovery Mode. Now my Recovery Mode doesn't functionate. When my Phone start I come into Bootloader Mode instantly without push any buttons on my Phone. When I selected the Recovery Mode with the Power Button. My Phone restart automatic and the Bootloader start again.
I hope you can help me.
Scoocyjuice
Click to expand...
Click to collapse
flash boot.img, recovery.img from fastboot
sukhwant717 said:
flash boot.img, recovery.img from fastboot
Click to expand...
Click to collapse
My Computer doesn't find my phone when I connected with a cable.
Tried different USB cables and USB ports?
Scoocyjuice said:
My Computer doesn't find my phone when I connected with a cable.
Click to expand...
Click to collapse
when you connect ur phone to pc does pc make any detection sound or not. open device manager and remove and connect phone to pc. see if any change happens there
Can you send me the flash.img and the TWRP Recovery for my Asus Zenfone 2?
sukhwant717 said:
when you connect ur phone to pc does pc make any detection sound or not. open device manager and remove and connect phone to pc. see if any change happens there
Click to expand...
Click to collapse
. After two mouth my PC can see my Asus and Minmal ADB can see my Asus too. What's the next step?
Scoocyjuice said:
. After two mouth my PC can see my Asus and Minmal ADB can see my Asus too. What's the next step?
Click to expand...
Click to collapse
flash raw firmware..
sukhwant717 said:
flash raw firmware..
Click to expand...
Click to collapse
Without any Recovery? I've tried to install TWRP on my Asus. The Pc said: The Installation ist successfully and when I go to the Recovery Mode on my Phone it is the same as before. Yesterday I put out the SD-card of my Phone and I want to copy the data on my Pc. My Pc said the SD-card hat a wrong Patition. I think that's is the Problem!
Scoocyjuice said:
Without any Recovery? I've tried to install TWRP on my Asus. The Pc said: The Installation ist successfully and when I go to the Recovery Mode on my Phone it is the same as before. Yesterday I put out the SD-card of my Phone and I want to copy the data on my Pc. My Pc said the SD-card hat a wrong Patition. I think that's is the Problem!
Click to expand...
Click to collapse
as you stated you are stuck in fastboot mode. you can flash firmware in fastboot mode
sukhwant717 said:
as you stated you are stuck in fastboot mode. you can flash firmware in fastboot mode
Click to expand...
Click to collapse
Which commad must I need for install that. Can you send me the command for me?
Scoocyjuice said:
Which commad must I need for install that. Can you send me the command for me?
Click to expand...
Click to collapse
see section install firmware without AFT
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
I have a two phones.
Mi Max 3/32 : Global 8.1.6.0. I recieved OTA to 8.2.1.0. Start downloading, on 40%+- phone freeze and reboot. Stuck on MI logo and dont boot. Dont show powered by android. Just mi logo.
Then i flash 8.2.1.0 trough MiFlash, bootloader locked, and... Same situation. Stuck on bootlogo. I Flash china rom, i flash global, flash older version. Come on Xiaomi! What wrong with you?!
Okay. Story #2
Mi max pro 3/64. Global 8.0.3.0. I downloading OTA, press instal, phone reboot and go install update. Ok. After this process, phone boot and... Cycle reboot. Again and again. On launcher, on setup wizards, on mi logo. Everywhere. Hmmm, okay, i open miflash repeat all as in story #1. Not effect. Zero. Cycle reboot. How?!
I dont know.
Both phones not bricks. But and dont work.
Debugging on usb is a necessary? I dont activated bcaz my phones dont booted. Funny, yeah.
Can it connect via adb?
Sent from my MI MAX using Tapatalk
RAMBO29 said:
Can it connect via adb?
Sent from my MI MAX using Tapatalk
Click to expand...
Click to collapse
yes
If it can connect via adb, flash via EDL mode and see.
If you are on miu you must check developer settings cause miui time to time unchecks option oem unlocking (in my case two times) for this reason ever i look at this and allow usb debugging always must be allowed and look at dev options is absolutely necessary to correct flash of roms, may be you are rooted when you tried to update and system cannot update by this way (device itself or autoupdate). to solve try first installing same version through fastboot, probably yet you don`t loose your data. but you must select option "flash_all_except_storage" from your unpacket zip rom
IndDoc said:
If it can connect via adb, flash via EDL mode and see.
Click to expand...
Click to collapse
hmm, for this it is necessary unlock boot?
SubwayChamp said:
If you are on miu you must check developer settings cause miui time to time unchecks option oem unlocking (in my case two times) for this reason ever i look at this and allow usb debugging always must be allowed and look at dev options is absolutely necessary to correct flash of roms, may be you are rooted when you tried to update and system cannot update by this way (device itself or autoupdate). to solve try first installing same version through fastboot, probably yet you don`t loose your data. but you must select option "flash_all_except_storage" from your unpacket zip rom
Click to expand...
Click to collapse
okay,
I did so. flash firmware and immediately bootloop. no root.
Dark_Eyes said:
hmm, for this it is necessary unlock boot?
Click to expand...
Click to collapse
Not required if you're going to flash the stable version.
IndDoc said:
Not required if you're going to flash the stable version.
Click to expand...
Click to collapse
sorry my mistake, i try but fastboot devices comand work (see device), adb ... not.
flash via fastboot
FAILED (remote: device is locked. Cannot erase).
need to unlock, yep?
That's not EDL, that's fastboot. See here for a guide how to use EDL mode.
IndDoc said:
That's not EDL, that's fastboot. See here for a guide how to use EDL mode.
Click to expand...
Click to collapse
i know about that. but my phones flashing via miflash (edl mode, Qualcomm HS-USB QDLoader 9008) and no boot (mi logo or mi logo plus powered by android stuck 5-10-15-55 mins)
why? i dont know.
upd. It's a MIRACLE. one phone (3/32) is ALIVE
Dark_Eyes said:
i know about that. but my phones flashing via miflash (edl mode, Qualcomm HS-USB QDLoader 9008) and no boot (mi logo or mi logo plus powered by android stuck 5-10-15-55 mins)
why? i dont know.
upd. It's a MIRACLE. one phone (3/32) is ALIVE
Click to expand...
Click to collapse
Good! Make sure you are flashing the right verison. If your phone is stuck on 'powered by android' screen, it's a good sign. It means your phone will eventually boot up.
IndDoc said:
Good! Make sure you are flashing the right verison. If your phone is stuck on 'powered by android' screen, it's a good sign. It means your phone will eventually boot up.
Click to expand...
Click to collapse
this is not quite right.
2nd phone flashing, booting, setup wizard (white screen, w\out miui 8 logo, freeze, reboot. cycle.)
1st phone working 5-7 min, freeze and reboot, stuck mi logo w\out powered by android. damn.
Dark_Eyes said:
this is not quite right.
2nd phone flashing, booting, setup wizard (white screen, w\out miui 8 logo, freeze, reboot. cycle.)
1st phone working 5-7 min, freeze and reboot, stuck mi logo w\out powered by android. damn.
Click to expand...
Click to collapse
Sounds like you have a hardware problem. Take it to a service center.
IndDoc said:
Sounds like you have a hardware problem. Take it to a service center.
Click to expand...
Click to collapse
agree, it seems. thank you.
Dark_Eyes said:
this is not quite right.
2nd phone flashing, booting, setup wizard (white screen, w\out miui 8 logo, freeze, reboot. cycle.)
1st phone working 5-7 min, freeze and reboot, stuck mi logo w\out powered by android. damn.
Click to expand...
Click to collapse
Well, let me tell the way that I flash exactly, for me works perfectly, EDL never work for me. Flash for fastboot couldn't work properly if you place files in any side of your PC. I place adb folder in main disk, in my case c:, unpack all the files of you rom beside the 4 files of adb in same folder (adb has created a path in system environment) then in mode fastboot with usb plugged device (how you loosed your data) right click on "flash_all" for rom can repair your partitions. (I don't remember now if appears with right click option to execute like an administrator better) don't use meanwhile your pc. may that help you
SubwayChamp said:
Well, let me tell the way that I flash exactly, for me works perfectly, EDL never work for me. Flash for fastboot couldn't work properly if you place files in any side of your PC. I place adb folder in main disk, in my case c:, unpack all the files of you rom beside the 4 files of adb in same folder (adb has created a path in system environment) then in mode fastboot with usb plugged device (how you loosed your data) right click on "flash_all" for rom can repair your partitions. (I don't remember now if appears with right click option to execute like an administrator better) don't use meanwhile your pc. may that help you
Click to expand...
Click to collapse
correct me:
you reboot to fastboot (vol- + power), rabbit logo, connect usb w\out pressing any buttons
create folder adb (4files adb + all files of firmware w\out folder image)
and run flash all
unlock boot required?
Dark_Eyes said:
correct me:
you reboot to fastboot (vol- + power), rabbit logo, connect usb w\out pressing any buttons
create folder adb (4files adb + all files of firmware w\out folder image)
and run flash all
unlock boot required?
Click to expand...
Click to collapse
Yes, mode fastboot in device with any trick like EDL, just connect to pc, no unlock bootloader required but must be an stock rom, fastboot image rom
SubwayChamp said:
Yes, mode fastboot in device with any trick like EDL, just connect to pc, no unlock bootloader required but must be an stock rom, fastboot image rom
Click to expand...
Click to collapse
after i click flash all, window appears 1 sec and all. no effect. what wrong?
Dark_Eyes said:
after i click flash all, window appears 1 sec and all. no effect. what wrong?
Click to expand...
Click to collapse
Recogniced device?, type first fastboot devices to be sure
Hi guys,
Rooted Oneplus 3 is soft bricked. Please help me!!! :crying:
:crying:Quick desription: Fastboot formatted it. My PC detects it.
Tried to Fastboot flash latest TWRP ("twrp-3.0.2-0-oneplus3.img") via CMD Prompt.
After that I get a message saying that the processed was "finished" (within 0.802s!).
Now I reboot+volume down and bootloop continues. Phone starts, I see the normal warnings I used to get after rooting it. Then I see the Oneplus logo for a fraction of a second and then it boots again and the process repeats itself.
I think it may be worth mentioning that the reason all this happened is an encryption problem that occurred while I was flashing a rom update with TWRP: After the flashing finished, got an error saying "unable to mount storage". Wiped cache+dalvik and then restarted. Got a black screen that did not display any signs of life after several minutes. Then turned it off and on by long press on the power button. Then I got an error saying that the encyption process was disrupted and that I have to wipe my phone (strange given that I did not select any encryption button in TWRP). Anyhow, then I fastboot formatted the phone and that's it.
Thank so much for anyone who can help!!!
fastboot flash recovery recovery.img (I recommend blu_spark's TWRP) reboot to recovery, if it doesn't work, try:
fastboot boot recovery recovery.img
See if you boot to recovery and then try flashing a custom ROM.
Hi Fobos, thanks for responding quickly.
I tried using fastboot boot command (with twrp-3.0.2-0-oneplus3.img). No luck with that.
Also, didn't find a downloadable blu_spark *.img version for twrp recovery. would you be so kind to add a link?
Thank you.
Now I think it's hard bricked ( Help!!!
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
ppppp44 said:
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
Click to expand...
Click to collapse
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Kayembe said:
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Click to expand...
Click to collapse
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
anup807 said:
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Click to expand...
Click to collapse
Hi Anup!
Thanks for the link to the Blu_Spark version of TWRP.
On CMD Prompt, tried to format recovery, console stopped responding. "Fastboot format recovery"...Just stops responding
Also tried "Fastboot delete recovery". I get a message saying "deleting recovery..." then also stops responding. Nothing happens from there.
I tried to use the OPO3 Root Toolkit. It does detect the fastboot device, but when I try to flash or boot or do anything else other than detection, it is unable to find the device. Says operation failed.
What now? :crying:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Check your cable (try another one), even reinstall your adb drivers on your machine (if Windows).
Let the device charge for 30 minutes at least then retry (charge with new cable too).
ppppp44 said:
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
Click to expand...
Click to collapse
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Kayembe said:
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Click to expand...
Click to collapse
Hey Kayembe,
I only get to fastboot mode. No Adb device detected. No recovery mode available.
ppppp44 said:
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Click to expand...
Click to collapse
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Machiel187 said:
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Click to expand...
Click to collapse
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
ppppp44 said:
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
Click to expand...
Click to collapse
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
ok I somehow managed to flash Blu_Spark Twrp and got it to work.
Within TWRP, flashed OnePlus3Oxygen_16_OTA_051_all_1704112009_2521.zip
and also SuperSU.zip, and no_verity.zip.
Getting some errors.
Device still doesn't boot.
Attaching the log TXT here.
I am desperate... please help.,..
Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
try "default_password" for the password
ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
Go to Fastboot type 'fastboot erase userdata' (you have to reflash OOS tho.. Make sure you are on the latest TWRP. I'm not a fan of Bluspark but his TWRP is currently more up 2 date.
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.
Hey Guys i have an Big Problem and i dont knwo what to please help
So i wanted to flash lineageos and that worked good but its garbage the camera ist very basic and there are a lot of features which not work
So i decide to get back to Oxygenos und root it
Yeah and know my phone is stuck at something it only shows the one plus logo, sometimes nothing, and somethimes i get into fastboot but that not helping because when i boot or flash boot a recovery nothing happends it shows only the one plus logo!!
So i have an One Plus image but i cant sideload it into fastboot
is there an fastboot image?
i hope so!!
thans for reading i am from germany so my english is not the best
Use the msm tool for unbrick your devices
ChrisFeiveel said:
Use the msm tool for unbrick your devices
Click to expand...
Click to collapse
Hey thanks for anwering i have downloaded it but i really dont know how to use it
but the bigger problem ist that the phone only shows a red flash and a white circle!
so i cant get into fastboot
SeppelLetsPlay said:
Hey thanks for anwering i have downloaded it but i really dont know how to use it
but the bigger problem ist that the phone only shows a red flash and a white circle!
so i cant get into fastboot
Click to expand...
Click to collapse
Search for the link and be sure to read on how to use the tool completely until you understand!
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
TheGhost1951 said:
Search for the link and be sure to read on how to use the tool completely until you understand!
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Click to expand...
Click to collapse
Yeah but i dont get in EDL or Fastboot
its only shows the obeplus logo every 3 seconds and reboot
but power + vol +/- are ignored
only +/- is also not working
please help i am despair
SeppelLetsPlay said:
Yeah but i dont get in EDL or Fastboot
its only shows the obeplus logo every 3 seconds and reboot
but power + vol +/- are ignored
only +/- is also not working
please help i am despair
Click to expand...
Click to collapse
Try power+vol- to get to recovery.... Other than that keep trying different button combinations... What happens when you hold both vol buttons and power button for more than ten seconds? To completely shut phone off hold vol up and power button. Otherwise I have heard some say let the phone battery run down battery until phone shuts off. Then try the buttons again. Only just both vol buttons no power and phone not plugged in. Start the MSM tool it will say waiting on device, then with phone off, hold both vol buttons down wait 10 seconds then connect phone to PC.
So when i press power + "-" nothing happend, no vibration, no screen nothing
when i press +/- and power the phone starts and there stands fastboot but a few seconds läter come the red flash and the phone shuts down(but it is onto an powercord)
when i only press +/- also nothing happend and the phone is not responded in msm
SeppelLetsPlay said:
So when i press power + "-" nothing happend, no vibration, no screen nothing
when i press +/- and power the phone starts and there stands fastboot but a few seconds läter come the red flash and the phone shuts down(but it is onto an powercord)
when i only press +/- also nothing happend and the phone is not responded in msm
Click to expand...
Click to collapse
Do not use +/- and power....do not use the power button just +/- only
TheGhost1951 said:
Do not use +/- and power....do not use the power button just +/- only
Click to expand...
Click to collapse
ok but as i sag wehen i power off the device(with fastboot) the +/- doesent work and its not regnosized
but i have sucsessfully launched twrp with fastboot boot twrp
but when i sideload the zip i get the error that the storage cant be mounted
SeppelLetsPlay said:
ok but as i sag wehen i power off the device(with fastboot) the +/- doesent work and its not regnosized
but i have sucsessfully launched twrp with fastboot boot twrp
but when i sideload the zip i get the error that the storage cant be mounted
Click to expand...
Click to collapse
You don't side load it, make sure the magisk app is located in phone storage, boot to twrp then select install while in twrp......
Ok and for what i need magisk first i must get oxygenos to run
and how can ich get magisk.apk onto the device? on my pc i cant see the phone/storage
SeppelLetsPlay said:
Ok and for what i need magisk first i must get oxygenos to run
and how can ich get magisk.apk onto the device?
Click to expand...
Click to collapse
Sorry that response was for another person!
TheGhost1951 said:
Sorry that response was for another person!
Click to expand...
Click to collapse
oh ok sorry
TheGhost1951 said:
You don't side load it, make sure the magisk app is located in phone storage, boot to twrp then select install while in twrp......
Click to expand...
Click to collapse
Ok, you were able to get to fastboot, now we are getting somewhere....hold on. We will get you up and running....!
You will need phone in fastboot mode connected to PC..,..do you have the ROM you want to flash?
TheGhost1951 said:
You will need phone in fastboot mode connected to PC..,..do you have the ROM you want to flash?
Click to expand...
Click to collapse
yeah i have the stock rom
c.47 europe full ota
OnePlus 9 and 9 Pro Firmware Flash File (Stock ROM)
If you're using a OnePlus 9 and 9 Pro or planning to buy it, then this guide is for you. If you want to install Stock Firmware, here we will share the
www.getdroidtips.com
SeppelLetsPlay said:
yeah i have the stock rom
c.47 europe full ota
OnePlus 9 and 9 Pro Firmware Flash File (Stock ROM)
If you're using a OnePlus 9 and 9 Pro or planning to buy it, then this guide is for you. If you want to install Stock Firmware, here we will share the
www.getdroidtips.com
Click to expand...
Click to collapse
Extract the zip, should see a payload.bin and change it to payload.img. then fastboot flash payload.img that will flash it to the phone... Then fastboot boot, that should reboot into setup screen on phone. If it doesn't, the last step would be to change the active slot and reboot again in fastboot mode...
Finally, from fastboot mode, fastboot twrp img and in twrp tap on reboot and boot to EDL mode with MSM tool "started" and that will start the process... If the above procedure fails! This is the way I recover from a crashed phone!
unknown partition 'payload.img'
error: cannot determine image filename for 'payload.img'
Does not work
SeppelLetsPlay said:
unknown partition 'payload.img'
error: cannot determine image filename for 'payload.img'
Does not work
Click to expand...
Click to collapse
Read my last post above...to use the MSM tool