Hello,
my problem is after trying to revert back to the stock rom I messed things up and I can't get back to fastboot mode.
But I will describe what I did. First thing I did many weeks ago was the installation of cyanogenmod 11 KitKat on the P6.
All worked fine except for the high power consumption. Because of that I decided to switch back to the stock rom.
To do that I have made the following steps.
1. I downloaded the Jelly Bean firmware from the official huawei website. (I can't post the link since I'm a new user)
2. I used the download extractor to extract boot.img and recovery.img
3. I flashed them via fastboot
4. I prepared a SD card with the update.app in the dload folder
5. booted the phone with volume buttons pressed. Update process started but failed. There was no error message only a huge FAIL message.
6. After that I switched back to TWRP recovery what worked fine
7. I build a flashable zip file with the update extractor of boot.img, recovery.img, system.img, cust.img, userdata.img and flashed it via TWRP
8. Than I realised that I mistakenly included the recovery.img which overwrote the TWRP recovery
Now the phone always starts to the huawei logo also when starting with volume buttons pressed. I can't access the fastboot mode anymore.
When shutting it down it reboots instantly.
My questions are the following.
* Can a corrupted recovery block the access of the fastboot mode or any mode to access the phone via USB to flash a new recovery?
* Are there other ways to reset the phone?
* Was it a problem to take a Jelly Bean stock rom after a KitKat installation?
* If the phone is bricked, do you have any suggestion what to do with it? Is it worthless now? Sell on ebay? Hope this is not necessary.
Thank you so much!
numbi said:
Hello,
my problem is after trying to revert back to the stock rom I messed things up and I can't get back to fastboot mode.
But I will describe what I did. First thing I did many weeks ago was the installation of cyanogenmod 11 KitKat on the P6.
All worked fine except for the high power consumption. Because of that I decided to switch back to the stock rom.
To do that I have made the following steps.
1. I downloaded the Jelly Bean firmware from the official huawei website. (I can't post the link since I'm a new user)
2. I used the download extractor to extract boot.img and recovery.img
3. I flashed them via fastboot
4. I prepared a SD card with the update.app in the dload folder
5. booted the phone with volume buttons pressed. Update process started but failed. There was no error message only a huge FAIL message.
6. After that I switched back to TWRP recovery what worked fine
7. I build a flashable zip file with the update extractor of boot.img, recovery.img, system.img, cust.img, userdata.img and flashed it via TWRP
8. Than I realised that I mistakenly included the recovery.img which overwrote the TWRP recovery
Now the phone always starts to the huawei logo also when starting with volume buttons pressed. I can't access the fastboot mode anymore.
When shutting it down it reboots instantly.
My questions are the following.
* Can a corrupted recovery block the access of the fastboot mode or any mode to access the phone via USB to flash a new recovery?
* Are there other ways to reset the phone?
* Was it a problem to take a Jelly Bean stock rom after a KitKat installation?
* If the phone is bricked, do you have any suggestion what to do with it? Is it worthless now? Sell on ebay? Hope this is not necessary.
Thank you so much!
Click to expand...
Click to collapse
When you say its bricked does that mean that it gets stuck on huawei ascend logo? If thats the case than you should be ablr to enter fastbboot since thats the sign you are in bootloader mode.
Sent from my P6-U06
tileeq said:
When you say its bricked does that mean that it gets stuck on huawei ascend logo? If thats the case than you should be ablr to enter fastbboot since thats the sign you are in bootloader mode.
Sent from my P6-U06
Click to expand...
Click to collapse
Well that is what I thought too, but I can't get a connection via adb or fastboot.
"adb devices" lists nothing. When connecting the phone via usb to the computer there is no log entry generated on the computer like it's the case with other usb devices.
I tried different usb cables. I'm unsure how to be really sure whether I'm in fastboot mode or not.
Before flashing the zip everything worked fine so it's very unlikely to be a driver issue or something related to the computer I think.
i have the same problem and i cant communicate with the device in any way but what happen to me that i download a wrong recovery img.
if someone can help please
i fix my phone and get it back to the stock recovery ::victory:
Can you please share how you make it? I have the same problem...
I fixed it by replacing the motherboard using a very detailed tutorial on ifixit.
The P6 is not build to be repaired by the customer but with the right tools it was ok.
skyhew said:
Can you please share how you make it? I have the same problem...
Click to expand...
Click to collapse
I turn the phone in the debug mode and flash the stock recovery back you enter the debug mode by press and hold on the volume down then after it the power for 10 sec. after you plug the phone to the computer via usb then download this file: 4shared.com/rar/9HO06Lpjba/p6_stock_recovery.html
and then unzip the file then open by order
1- adb-windows if you have windows
2- fastboot-windows
3- install-recovery-windows
and restart the phone and you have the stock recovery back
Related
Hey,
today i wanted to flash the hydro-rom on my p6 running pac-man-rom.
i thought i could flash it over, because they both need b118 cn, but no.
my p6 got stuck at the boot. i tried to get into the mode, where i can update original firmwares, because the b118 cn - update.app is still in the Dload folder..
now there is 1 big problem:
i have twrp-recovery, it has overwritten the hotkeys which i need to get in the "Dload"-mode (Vol Up + Down + Power)
so if i want to get in the "Dload"mode twrp recovery starts.
i googled a lot and found something about "adb", the same thing, i cant get my phone in the fastboot mode and i cant activate usb-debugging because i cant start my phone, just in twrp-recovery...
it would be nice, if someone could help me soon
PS: if someone has the stock recovery or a stock rom which i can flash with twrp, please post it here, it would be enough to unbrick my phone
Maiik7x said:
Hey,
today i wanted to flash the hydro-rom on my p6 running pac-man-rom.
i thought i could flash it over, because they both need b118 cn, but no.
my p6 got stuck at the boot. i tried to get into the mode, where i can update original firmwares, because the b118 cn - update.app is still in the Dload folder..
now there is 1 big problem:
i have twrp-recovery, it has overwritten the hotkeys which i need to get in the "Dload"-mode (Vol Up + Down + Power)
so if i want to get in the "Dload"mode twrp recovery starts.
i googled a lot and found something about "adb", the same thing, i cant get my phone in the fastboot mode and i cant activate usb-debugging because i cant start my phone, just in twrp-recovery...
it would be nice, if someone could help me soon
PS: if someone has the stock recovery or a stock rom which i can flash with twrp, please post it here, it would be enough to unbrick my phone
Click to expand...
Click to collapse
Its Not A Big Problem. Goto Twrp And In Reboot Menu Select Bootloader
Connect Your Mobile To PC
Download Adb And Fastboot
Download Stock Recovery http://www.androidfilehost.com/?fid=23252070760973625
Extract Recovery.img And Paste It In adb folder
Open Command Prompt In adb Folder
type :
fastboot flash recovery recovery.img
fastboot reboot
then
reboot your device while pressing vol + and vol -
After all that while pressing volume up and down at once, keep pressing the power button also, so press all 3 buttons at the same time.
thank you both, worked
Maiik7x said:
thank you both, worked
Click to expand...
Click to collapse
Great.
I think i have bricked my p6 after flashing boot(b125).img from fastboot and its stuck and restarting at bootscreen. Pls someone help with heawei multiloader as am told it can fix bricked phone from usb. File now no more assessible from huawei website. pls help.
Hey do you have twrp recovery installed? Have you already tried to get into your stock recovery ?( Holding volume up/down button simultanesly during boot)
nourudeen said:
I think i have bricked my p6 after flashing boot(b125).img from fastboot and its stuck and restarting at bootscreen. Pls someone help with heawei multiloader as am told it can fix bricked phone from usb. File now no more assessible from huawei website. pls help.
Click to expand...
Click to collapse
WisdomSeeker said:
Hey do you have twrp recovery installed? Have you already tried to get into your stock recovery ?( Holding volume up/down button simultanesly during boot)
Click to expand...
Click to collapse
my phone never came with any stock recovery. had 'factory mode' not recovery when holding those bottons. In factory mode, no option for flashing anything. Now phone only restarts on bootscreen and then on-off. initially tried flashing TWRP just befor bricking phone but adb gave error like this 'partition not support flash and i had already flash a boot.img for b125
b608 version of my phone was a brick was b118 installed, there is a solution?
sorry my poor english, I'm from Turkey, please help, please..
Both of you should try to flash the stock recovery! You can download it here www).androidfilehost.(com)/?fid=23252070760973625 (just remove the brackets) .
Then follow these steps:
1. Put your device in fastboot mode ( > adb reboot bootloader )
2. Flash recovery via fastboot ( fastboot flash recovery recovery.img )
3. Reboot via fastboot ( fastboot reboot )
Afterwards try to reboot to your stock recovery . Then you can simply install over the update.app a fresh Huawei Firmware
Greetings Wisdomseeker
WisdomSeeker said:
Both of you should try to flash the stock recovery! You can download it here www).androidfilehost.(com)/?fid=23252070760973625 (just remove the brackets) .
Then follow these steps:
1. Put your device in fastboot mode ( > adb reboot bootloader )
2. Flash recovery via fastboot ( fastboot flash recovery recovery.img )
3. Reboot via fastboot ( fastboot reboot )
Afterwards try to reboot to your stock recovery . Then you can simply install over the update.app a fresh Huawei Firmware
Greetings Wisdomseeker
Click to expand...
Click to collapse
well wisdom, like i said, its restarting at boot screen so i cant get to fastboot. i sometimes able to enter an android (3e) recovery and try installing what u said but each time, installation is stopped. Got a certain miui rom and halfway it says NOT VALID OTA PACKAGE. SCATTER FILE MISSING. All other package rom or other recovery refuse to install and say ERROR. i have tried this your files but not possible.
nourudeen said:
well wisdom, like i said, its restarting at boot screen so i cant get to fastboot. i sometimes able to enter an android (3e) recovery and try installing what u said but each time, installation is stopped. Got a certain miui rom and halfway it says NOT VALID OTA PACKAGE. SCATTER FILE MISSING. All other package rom or other recovery refuse to install and say ERROR. i have tried this your files but not possible.
Click to expand...
Click to collapse
Maybe you should try To use another SD card Or mabye Format the current one and then add the update.APP To it
PHP:
WisdomSeeker said:
Maybe you should try To use another SD card Or mabye Format the current one and then add the update.APP To it
PHP:
Click to expand...
Click to collapse
No luck! I think the huawei multiloader will do the work. Any Idea where i can download?
nourudeen said:
No luck! I think the huawei multiloader will do the work. Any Idea where i can download?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2618253
I dont understand... When i start multiloader.exe it seems to go.. But i can only download update.app file with che left One button.the center button let me either download the ROM and the right button keep the tool off. What i have to do for use this magic program?
Hello All,
I would like to start by saying that I am a novice when it comes to rooting phones so ANY help received here will be greatly appreciated. I have come across a few people within the various forums who have a very similar issue to the one I am having, but nothing exact. Now to the point.
Phone: Zenfone 2 (Model: ZE551ML-23-4G64GN-BK) came unlocked from amazon.com
Carrier: Metro PCS.
PC used to root: Win 7 64 bit / AV: Avast Free.
Issue: About 1 month ago I rooted my phone. Last night I received a prompt to do an OTA update, and selected install. I realized after that I shouldn't have done that, but it was too late. My phone would not load past the black and white ASUS loading screen.
I then proceeded to do some research online, and try to "unbrick" my phone myself. I figured out how to hold the power button + volume up key, select Recovery Mode with the power key, and press power + volume up again to get into the Recovery Mode. I was following some instructions online that didn't really make sense, which led me to choosing Wipe Cache Partition. This didn't work, so I had to manually reboot the phone (Hold the power key, and turn it back on). From that point forward I have been unable to get back into the Recovery Mode. Once I get to the sleeping android with the red triange I have tried holding power + volume up (which got me into recovery mode the first time), power + volume down, power + both volume up and down, I've rebooted my phone several times to make sure I was doing this as soon as the little android appeared and nothing happens. The android just pulses in and out and nothing happens. This is the first of my many problems as I have never flashed a ROM before, and I am a novice. Also my PC does not recognize my phone at all at this point. I'm using the same cable and port that I always use when transferring files. The port has been tested with a tablet and iPhone, which works. My questions are as follows:
1. Am I screwed? lol.
2. Is there a way/trick to getting into recovery mode again?
3. Can I still unbrick my phone without getting into recovery mode? Is there something I can do with my phone connected to the PC perhaps?
I would also like to mention the following:
1. I've downloaded firmware Version V2.20.40.160 from asus website. Is this the right "image" or 4 files I should be using to flash onto my phone?
2. I've also downloaded ADB, but it doesn't look like the 15 second one, and it does not detect my phone. What tools do I download in order to fix the issues I am having?
Thank you in advance!
Best regards,
Clavin0089
For anyone who may have found this thread I think I found a fix here. I will let you know after I test this if it works:
http:
//valuestuffz.blogspot.com
/2015/10/fix-zenfone-2
-stuck-in-recovery-wipe-cache-partition.html?m=1
Sorry. I had to break up the link in order to post it.
Clavin0089 said:
I would also like to mention the following:
1. I've downloaded firmware Version V2.20.40.160 from asus website. Is this the right "image" or 4 files I should be using to flash onto my phone?
2. I've also downloaded ADB, but it doesn't look like the 15 second one, and it does not detect my phone. What tools do I download in order to fix the issues I am having?
Thank you in advance!
Best regards,
Clavin0089
Click to expand...
Click to collapse
i was in same sit with a brick of sorts and used this guid to help me:
> http://www.asus-zenfone.com/2015/12/how-to-downgrade-asus-zenfone-2-firmware.html *** I used this to go from the 168/174 ( 174 didnt fix issue that 168 caused ) back to 160
> http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html *** How to enter recovery if you dont know how
make sure the phone is plugged into a usb2 port and not a 3.0
what got me is when i installed adb, it put adb files in a default directory on my hdd, so i just copied the files to the folder where where i had all files at See below
i used the .160 file to restore my phone and it worked..
now if phone isnt detected yet, you may still need files. have you tried iSocUSB-Driver ?
I followed the steps outlined in the link:
http
://valuestuffz.blogspot.com/2015/10/fix-zenfone-2-stuck-in-recovery-wipe-cache-partition.html?m=1
And everything appeared to have gone smoothly, however, now my phone just loads, and will not enter the home screen. I just have that ASUS IN SEARCH OF INCREDIBLE screen now. I was able to get into the recovery mode, but it doesn't appear to have worked. I also received the "Permission denied" errors mentioned in the link. Any suggestions?
My phone is now detected by the PC for the record.
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Pu$$nBooT$ said:
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Click to expand...
Click to collapse
I did push over 3 files, but when I downloaded the .160, it only had droidboot.img,and boot.img. I tried both .168 (Which may have been totally wrong, but had all 3 files) and .160 from the asus website where you can select firmware. I did the .160 most recently. I put the recovery.img, droidboot.img, and boot.img into the adb folder, and ran the following CMDs:
Fastboot erase cache
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
I then used adb sideload CMD to load the .160, and it reached 100% and said successful. I attached a screenshot of what the "permission denied" CMD looks like.
Pu$$nBooT$ said:
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Click to expand...
Click to collapse
Tonight after work I will try the links you suggested to me once more, and let you know the results. I sincerely appreciate all of your help here! Thank you very much!
anytime...
i never seen/encountered that error message before... try adb kill-server command if you run into any issues. when you start again it will load automaticaly... have you tried different usb ports? stay on usb2.0 when connected and try original oem cable that came with the phone. if you dont have it, try different micro-usb cables ( i had issues when i had my lg g3 being on a usb3 port, so i made sure mine was plugged in a 2.0 port )
Currently i am on beanstalk, and want to go back to stock.
I flashed the stock recovery via fastboot, but when i enter into Stock Recovery mode, it gives me Error icon.
The whole process is to flash the stock zip via sideload, but i am not able to enter the stock recovery.
The stock version i am trying to flash is 2.20.40.160.
I flashed all three files, Droidboot.img, recovery.img, boot.img.
And then turned the phone off, and now it is stuck on Asus screen. Urgent Help!!
btw when u see that error icon, nothing is actually wrong.... you have to hit 2 buttons simultaniously to enter recovery.
see > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html on step 6, this is normnal.. once u do button dance, you will enter step 7 and select flash via adb.. then you flash the rom file
Pu$$nBooT$ said:
btw when u see that error icon, nothing is actually wrong.... you have to hit 2 buttons simultaniously to enter recovery.
see > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html on step 6, this is normnal.. once u do button dance, you will enter step 7 and select flash via adb.. then you flash the rom file
Click to expand...
Click to collapse
Yeah, i looked it up, power + volume up. That did it. Thanks!
np...
Hello,
I searched for this problem but i dont see any posts that is related to this. So i got my deluxe, its ZS750kl 2.15 6gb ram unit with nougat OS and it was working well. Last february 2018, it got its automatic system update for Taiwan CHT VoLTE support and battery optimization. A day after the update, it suddenly went into bootloop. My unit is not rooted, running with stock nougat OS with locked bootloader. It was never modified in any form. I do some observations and i noticed that sometimes it boots normally so i successfully done a factory reset but the same problem existed. I cant do a hard reset via vol. down+power since i have a locked bootloader. I am new with fastboot method and i dont know if it will help me solve the problem so i left it untouched from March until this week. Same problem still exist even the battery is totally drained over time.
Is there someone here with the same problem? Is there a possibility of system rollback before the february update?can i flash nougat stock rom hoping it will revert back to the previous OS without VoLTE support? I think the bootloop issue is with that update, since i saw some posts with the same problem but it was after the oreo update, not the same as mine so i concluded that the problem lies somewhere in between the feb. update and the oreo update.
I hope some will look into this and help me or guide me to step by step flashing of nougat stockrom using fastboot. Sorry, im new with the method, i usually flash through twrp but i cant because of locked bootloader.
Thank you in advance,hope you can help me with my problem.
Model: ZS750KL
Ram: 6gb
Frequency: 2.15
Firmware: WW_5.17.44.87_20180222
Location: Philippines
Hi there,
I hope I can post this here.
I don't have an answer but I have a similar problem. The Phone will not start anymore. I ran into bootloop and only fastboot is working.
Any thing i can do?
Hello,
Im looking for a solution too, my phone got bootloop only fastboot is working, partition protected, phone is locked i cannot put even in recovery mode. Any help would be really appricated.
Cheers.
Hey all,
These instructions are assuming you have a 2.15ghz 570KL. I'm not responsible if your phone gets bricked any further.
Grab the standalone adb/fastboot tools
https://developer.android.com/studio/releases/platform-tools
Grab recovery.img from 15.0210.1808.70, grab twrp-3.2.3-0-Z016-20181014.img
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Grab the latest official update, make sure it's the right frequency (2.15ghz in this case)
https://www.asus.com/us/Phone/ZenFone-3-Deluxe-ZS570KL/HelpDesk_Download/
Move everything into an accessible folder
Copy the internals of the adb/fastboot such that twrp-3.2.3-0-Z016-20181014.img and fastboot.exe are in the same folder
Copy recovery.img to an sd card
Copy the official update to the same sd card
Put it in the phone
Open command prompt
Navigate to the folder using cd [filepath]
Example:
cd c:/users/MyUser/Desktop/Folder
run the following command
fastboot boot twrp-3.2.3-0-Z016-20181014.img
Boot phone to fastboot mode
Plug it in and pray.
It should boot into TWRP. Go to install, click the checkmark to switch from zip to images, then find Recovery.img. It should be located in the external_sd. Flash that to the recovery partition.
Reboot back into recovery (Power+Vol Down)
If it boots into a screen that says No Command! it means it was flashed successfully
Spam volume up, volume down, and power until the screen recovery loads
If it doesn't load after a few presses, do a hard reset (Power + Vol Down)
Try again until it works
Install the official update
Reboot and your phone should work again.
Good luck.
asianflipboy said:
Hey all,
These instructions are assuming you have a 2.15ghz 570KL. I'm not responsible if your phone gets bricked any further.
Move everything into an accessible folder
Copy the internals of the adb/fastboot such that twrp-3.2.3-0-Z016-20181014.img and fastboot.exe are in the same folder
Copy recovery.img to an sd card
Copy the official update to the same sd card
Put it in the phone
Open command prompt
Navigate to the folder using cd [filepath]
Example:
cd c:/users/MyUser/Desktop/Folder
run the following command
fastboot boot twrp-3.2.3-0-Z016-20181014.img
Boot phone to fastboot mode
Plug it in and pray.
It should boot into TWRP. Go to install, click the checkmark to switch from zip to images, then find Recovery.img. It should be located in the external_sd. Flash that to the recovery partition.
Reboot back into recovery (Power+Vol Down)
If it boots into a screen that says No Command! it means it was flashed successfully
Spam volume up, volume down, and power until the screen recovery loads
If it doesn't load after a few presses, do a hard reset (Power + Vol Down)
Try again until it works
Install the official update
Reboot and your phone should work again.
Good luck.
Click to expand...
Click to collapse
Hello There,
Thank you for tut*, do you have or know any method about i have exact same phone model but its stuck on boot and keep restarting, no recovery mode available only i can put in fastboot mode when i try to flash or anything it said partition protected... any help would be really appricated.
Cheers.
same problem, I have also opened a new thread but I have not received a reply.
In all cases following this mini-guide I am stopped at the boot twrp command. I'm getting unsigned file error.
I tried the original recovery (taken from the user link above) and the phone gets stuck on the android logo with a red triangle of danger.
ideas?
How did you unlock your bootloader? i cant follow the instructions given because my bootloader is not yet unlocked.
has anyone gotten the steps above to work without unlocking the bootloader?
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.