[Completed] [Fixed]Bricked Huawei P8 - XDA Assist

I was running a lollipop bootloader and since i wanted to upgrade to marshmallow i had to update the bloodloader too, so i flashed a new stock boot.img obtained from a stock rom and soon after that i also flashed twrp, i think i somehow bypassed the new (locked?) bootloader with a custom recovery and now i'm stuck in "Rescue Mode".
Device is now stuck into that mode, i cannot turn it off or enter recovery, as soon as i restart my phone it goes into rescue mode, i have already tried all key combinations and also tried to force install from sdcard, my computer is not recognizing my device either so i can't use adb, i had no idea bricking a device like this was even possible, i'm quite desperate.. please help.
[How i fixed it] I somehow managed to get out of Rescue Mode, what i did wrong was not holding vol down + power long enough, you have to hold them down until phone restarts, that takes about 10 seconds, after that you will feel a vibration and huawei logo will appear, keep holding buttons down for 4-5 more seconds before taking your fingers off, it should then go into fastboot, once you're there adb should work and you will be able to unlock the bootloader if it is not unlocked already, after that you should be able push data to device or flash recovery again. If adb still doesn't work check usb drivers, your best bet is probably downloading HiSuite.

Awesome! :good:
Glad you got it going! I'll close this thread now! But here is your device section for future use, http://forum.xda-developers.com/t/huawei-p8
Cheers!

Related

No boot to Fastboot Mode after flashing/restore

Hi,
I was on Android N and decided to go back to KangVip Slim trough my TWRP Backup. So i opened the Bootloader again and flashed TWRP. But restoring of my backup failed and i started to wipe and delete in TWRP different things. I think i erased to much...
The result is, that now i the phone is booting to Huawei Logo and stucked there. All button-combinatios don't work.
No stock recovery, no dload method and the worst thing...no bootloader mode (USB connected to PC). The phone just reboot to the Huawei Logo.
I opened the phone, remove the battery cable, put it back, but it's still the same. I also discharged the battery and charged again. Same result, it boots just to the Huawei logo.
Is there any thing i could try to bring back to life or is it hardbricked?
Thanks in advance for any idea..
AL10 or L29,L09 to you have?
With AL10 version is easy to go back.
Install Android N again in Twrp.
Install Stock Recovery.
Go Back with Hi Suite.
Your open your Phone to reboot?
Press Power Button 10 sec. to reboot after reboot press 3 sec. to boot in eRecovery and shot down the Phone.
After Power off press Volume Down and hold and put in the Usb Cable in the Phone.
After this boot in Bootloader.
Flash Twrp for android N and wipe Cache,Dalvik,Data and System.Then flash Android N in Twrp.
Hi,
i have a L29. No TWRP, no bootloader mode to flash anything.
What happens when you switch off,then Power on and Press so long Volume up until the erecovery starts?
This must work!
Nothing, just reboot to the Huawei logo. I think there is no e-recovery installed.
Tavros said:
Nothing, just reboot to the Huawei logo. I think there is no e-recovery installed.
Click to expand...
Click to collapse
letschky said:
What happens when you switch off,then Power on and Press so long Volume up until the erecovery starts?
This must work!
Click to expand...
Click to collapse
Let me add one more step. Connect your phone to the computer via usb cable then switch off your phone. Press and hold Vol up + Power. Release it when you see Huawei logo.
Hope this will enable you to enter eRecovery.
Good luck
I tried that, but no success..
I think the Mate 8 is the first phone that i have brick...
I have the same issue too. L29. No TWRP, no bootloader mode to flash anything. Hopefully someone can guide us through this
Good news..
After I put the phone aside a few days and the battery has completely discharged, I connected the phone with my PC and tried to get into the fastboot mode.
I tried this before, without success. I was shocked when I saw the bright screen! It was in fastboot mode. I did not expect that. I left it untouched until the battery was charged a little bit.
Then i started to flash the NXT-L29C432B560 Firmware. It wasn't possible to do it with the "dload" method, so installed twrp-3.0.3.img and flashed the firmware with TWRP. For help use: https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c185b560-official-t3556789.
And now it works fine, like never something happend.
So all of you with same problem: Give it a try.
Now i have two babies.. Mate 8 and Mate 9. I will keep both....:good:
HI i have my mate 8 in the same conditons that you used to! please help me im desperate it doesnt even get on fastboot mode. Please I would appreciate your help thanks
dexz said:
Let me add one more step. Connect your phone to the computer via usb cable then switch off your phone. Press and hold Vol up + Power. Release it when you see Huawei logo.
Hope this will enable you to enter eRecovery.
Good luck
Click to expand...
Click to collapse
Hello!
I can do that with my mate 8, but only things i can access are erecovery, stock recovery and dload mode. neither of them work.
dcds_dck said:
I have the same issue too. L29. No TWRP, no bootloader mode to flash anything. Hopefully someone can guide us through this
Click to expand...
Click to collapse
Had this problem with L09. I've been trying to fix it all the week long.
If you can access dload mode, follow this guide:
https://forum.xda-developers.com/mate-8/general/huawei-mate-8-downgrade-android-7-0-to-t3530999
If your phone is not NXT-L09, search for NXT-XXX (XXX= your phone model) rollback. It will surely work.

Bricked my Nvidia Shield Tablet LTE RoW after Nougat update

Hi!
I've read many threads and I haven't found the answer I'm looking for.
I've flashed the 5.1 update via TWRP on my tablet, and in the first boot it rapidly installed something, rebooted and never worked again. I can't use adb fastboot because my pc doesn't recognize my tablet. It shows as APX. I've tried to install the APX drivers and I can't, even after I reboot into advance settings.
Have I not read the correct post? Please help get my tablet back. I know it was stupid of me not to disable wifi before deleting the TegraOTA, I was in a hurry and forgot. Is there any hope?
Thanks for your patience.
Sounds like it took the forced update to kill it. If you can't get into the bootloader to use fastboot I don't think you'll be able to do much.
I might have done the same thing as you. If you do vol down+power does that still start up? if so this worked for me
https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
I'm stuck now I'm on the stock rom and dont want to connect to wifi and get a killswitch, but I can't get a custom recover to load to change roms
Edit: When on the laying down android with "no command" if you hit the power+volup+voldown it will go into recovery settings. I guess the custom recovery isn't really flashing over.
Unplug USB cable press power for 30 seconds and then press the power and vol down should go to bootloader if your tablet didn't get kill switched. If it still doesn't boot and shows apx once connected then its been kill switched. Pressing power and vol up will place it into apx mode by default.
Sent from my SHIELD Tablet K1 using Tapatalk

Unable to boot, enter flash mode or enable USB debugging after 'succesful' flash

I use this forums a lot for info but in this case i can't find any leads of whee to go with this, so wondering if someone can chip in some ideas?
I flashed a ROM via flashtool but wasn't happy with it, so i thought i'd just go back to stock and so used flash tool AKA emma to flash one of the options given there.
First attempt to flash it said "flash failed" or something like that and had the "flashing failed, connect to computer" note in the phone when booting it. (I'm sort of making up the terms, not that much into the tech ). Anyway, i tried flashing the same FW again and this time it went through really quick being 'completed' in a few seconds.
Now when i try to boot it gets stuck in the 'Sony' logo. Can go into Fastboot but no Flash Mode (nothing happens using the vol down key), and USB debugging seems to be off now as well.
Emma only works in Flashmode so can't do anything with that. Flashtool doesn't offer anything useful in Fastboot and Xperia Companion recognises the phone when in Fastboot but asks that i unlock the screen and enter MTP...
Any help of where i can go with this?
Thanks
P.s. While keeping buttons pressed randomly it went once into flash mode, but trying to flash a ROM with flashtool it got stuck at "reding device data" and i haven't been able to enter the mode again. Is there an alternative key press combination that i stumbled on by chance? I think i just kept vol up and power held for a while and let go at a random number of phone vibrations
Just tried: Flashed twrp via fastboot and then rebooted into recovery. Same thing. It still opens to Sony splash screen and stays there
Ok, i'm kind of talking to myself here, but mild success and something that might help someone.
Managed to get back in flash mode. Don't know if it's a fluke, unique to this phone, or how it's actually meant to work, but the sequence is:
From the freezed up splash screen, and the USB connected, press and keep pressed power+vol up (hard restart/shutdown)
You get a single vibration, if you let go here it restarts. Keep pressing
You get a triple vibration, if you let go here it shuts down. Keep pressing
You get a single vibration, if you let go here it starts in fastboot. Keep pressing
You get a second single vibration, if you let go here it starts in flash mode.
Possibly a fluke but don't want to have to try again!
Anyway, i managed to flash the last working firmware and it's all good, yet this is the unwanted one. So issue is i still need to downgrade the phone to 7.1.1

Moto G7 Power XT1955-5: Stuck in BootLoop at "Unlocked and Can't Be Trusted"

Moto G7 Power XT1955-5: Stuck in BootLoop at "Unlocked and Can't Be Trusted"
I made several attempts to install twrp-3.4.0-0-ocean to this new Moto G7 Power. I was able to Unlock the Bootloader, and even had TWRP running twice., but after it was rebooted it would never go back to TRWP, it would reboot to the Stock ROM. Then, runnng adb reboot bootloader would bring me back to the stock bootloader page.
Each time it boots, it has displayed the "Your Device Has Been Unlocked and Can't Be Trusted." page, and then would eventually boot. Annoying, but ok. It is what it is.
However, this last attempt to reboot from the stock bootloader has created an endless bootloop to that "Cant Be Trusted" page.
No combos of holding down the down volume for 3 seconds with the power key.. or holding down the power key for 15 or 20 seconds.. nothing works. All it does it turn the screen off for a couple of seconds and then goes back to the "Can't Be Trusted" warning page.
Well.. turns out it does work, it's just finnicky. This video showed me how to do it.. https://www.youtube.com/watch?v=fA0DHvbIlWY
Holding down the Down Volume and Power for several seconds until the screen goes black, release the buttons, then waiting a moment will allow the bootloader to appear.
1- Should I replace the stock rom? If so, how? I can't boot far enough along to run adb push.. and TWRP will not run.
What I cant do now is factory restore the device. Where can I get a stock rom, or any suggestions? I am pretty sure that's what I get for trying to use the xt1955_5.img file from Minimal+adb_fastboot_platform-tools_r29.0.6_2020 on unofficialtwrp.com's how to page, right?
Thanks in advance..
bryangrant4 said:
I made several attempts to install twrp-3.4.0-0-ocean to this new Moto G7 Power. I was able to Unlock the Bootloader, and even had TWRP running twice., but after it was rebooted it would never go back to TRWP, it would reboot to the Stock ROM. Then, runnng adb reboot bootloader would bring me back to the stock bootloader page.
Each time it boots, it has displayed the "Your Device Has Been Unlocked and Can't Be Trusted." page, and then would eventually boot. Annoying, but ok. It is what it is.
However, this last attempt to reboot from the stock bootloader has created an endless bootloop to that "Cant Be Trusted" page.
No combos of holding down the down volume for 3 seconds with the power key.. or holding down the power key for 15 or 20 seconds.. nothing works. All it does it turn the screen off for a couple of seconds and then goes back to the "Can't Be Trusted" warning page.
Well.. turns out it does work, it's just finnicky. This video showed me how to do it.. https://www.youtube.com/watch?v=fA0DHvbIlWY
Holding down the Down Volume and Power for several seconds until the screen goes black, release the buttons, then waiting a moment will allow the bootloader to appear.
1- Should I replace the stock rom? If so, how? I can't boot far enough along to run adb push.. and TWRP will not run.
What I cant do now is factory restore the device. Where can I get a stock rom, or any suggestions? I am pretty sure that's what I get for trying to use the xt1955_5.img file from Minimal+adb_fastboot_platform-tools_r29.0.6_2020 on unofficialtwrp.com's how to page, right?
Thanks in advance..
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Glad you're out of boot loop.
Recovered from bootloop and "dead" bootloader screen! Tips to recovery
I was able to Rescue the device from periodic BootLoops and a dead end Bootloader screen.
I referenced the information on this thread in the XDA forums, specifically the “Motorala Unbricking Tools” section.
I then tried the "LMSA: Lenovo's Motorola Smart Assistant" thread to find the link to the Lenovo / Motorola download page.
The Rescue software is a bit clunky. Powerful, but clunky.
There are also some cool tools such as Clipboard Copy Text between Device and PC, a Gif Maker, a Ringtone Maker, and a SCREEN RECORDER!!
Back on Track with the Rescue:
-Linux or Mac versions are NOT available; Windoze only.
-You will need at least 2gb of ram in your virtual Windoze7 machine to run it or it will not run in a useful manner.
- Parallels16/Windoze7-64bit worked fine.
-WINE based installs will NOT work.
To run, you will need to enable USB Debugging, although there are two other ways to connect the phone I did not also try. There even appears to be a way to rescue even a truly bricked dead device.
To Rescue your device:
Download, Install, and Run Rescue and Smart Assistant.
The Rescue process will NOT relock your bootloader.
Select the Rescue tab, then select Rescue Now. If you need to backup the device, try the Backup button right next to the Rescue Now button.
The application has some bugs, shortcomings.. here's some heads up to reduce Stress caused by those bugs..
The software will ask you to select the phone you own. The slider dialogue UI is badly done, so you will go back and forth a dozen times before learning how to navigate the menu. It might auto-recognize, but it did not on mine. Good luck!
Next, download the ROM.. the progress bar does not reflect what is actually going on. Once the 2bg down is 100% complete, it will sit there for a LONG TIME doing nothing. Dont kill the app and restart. It's actually busy unpacking the .zip Rom file into a directory tree on your harddrive. Just go eat some lunch, and come back.
Then, a similar issue occurs when you install the ROM. The progress bar is pretty much done, it just sits there doing nothing.. Let it go for a long time.. it's actually doing it's job, and the progress bar is just badly done.
If you are going to use the backup.. TURN OFF YOUR POWERSAVING stuff on both ends. If it is interupted by Power Saving/Sleep mode, the software will start at the beginning. The backup process takes hours, not minutes, so this is not a good result.
Once backed up, if you are moving to a new phone, there is a couple of ways to do that. I am going to perform these functions today or tomorrow, and will update with the results of those efforts.

I Flashed My Note 20 Ultra With Recovery.img And Now Its Stuck On Orange State "Bootloader Unlocked" Warning Message!

Ok Guys So I Shouldn't Have Done This But I Used Fastboot To Flash Recovery And I think I Did It Wrong. It Said "ok" And Finished And I Rebooted Phone It Resetted And Then Stuck On The Orange State Bootloader Message. I Do The Recovery Mode And Goes Black And Nothing Is Responsive For a While, Sometimes Longer Than Others. This Happens If I Start Phone Normal Or Try Fastboot Or Download.
Because Of My Mistake I Cannot Connect To Pc Software And Im Not Sure Of What I Can Do. I Feel Like Im Not Going To Like The Answer For This But I Got To Take The Blame For This.
Btw i Have A Samsung galaxy Note 20 Ultra Sm-N986u
I think your phone is hard bricked
so you can't get fastboot using volume up+power or via adb?
rescue from manufacturer site pos or just device not being recognised?
It isn't hard bricked it's just way of Samsung trying to make life of simple people more difficult, people who paid for Samsung phones lots of money.
To sort that screen issues what you can surely do is,
Simply press volup + voldown buttons at the same time, no matter if you're on that orange screen or whatever just press those those two buttons at the same time and keep pressing them while you connect your phone to pc. you will boot into download mode. Then flash stock firmware for your phone. After stock of flashed Reboot and start your phone, go to developer options see if oem unlock option is there if it is then oem unlock it if it is not then go back to settings manually change date to year ago, then go to updates disable auto update, connect to WiFi, and press on update several times untill window shows up saying no updates, then go to developer options you should see oem unlock, unlock it.
Then boot into download mode and make sure you have working copy of recovery.
And make sure you follow instructions of whoever recovery you installed on how to boot into recovery. I have S20 plus and too had troubles with it, and the only working recovery for my phone is twrp customised. To boot into it after flashing recovery from odin auto reboot disabled I pressed voldown and power, USB cable connected, then after screen goes off I changed from voldown to volup while kept pressing power button and cable connected. Orange screen with warning showed up for 5 sec I kept pressing and it bottled to twrp and then I was able to install custom rom beyond rom and while installing in aroma I was able ti choose option to remove orange screen.
That's it.
I ran into the same error. I mistakenly loaded twrp's recovery into userdata instead of ap section. The phone was stuck at the orange screen and nothing was happening whatever i pressed. I waited till the battery to dry out and with 0% battery, i directly connected to pc and was able to get into download mode. Then i flashed stock and everything is now back to normal.
Carl Johnson (Cj) said:
I think your phone is hard bricked
Click to expand...
Click to collapse
Absolutely not

Categories

Resources