Database Develop

I think I've bricked the Huawei P9

I have a European Huawei P9 EVA-L09 model which I adore. It was running Marshmallow and EMUI 4.1. I found a Nougat beta ROM and I tried to install it but have left it in an unusable state.
I don't think the phone is rooted but I do think the bootloader is unlocked.
I can boot into 3 modes.
Mode 1 - Just reboot
Huawei eRecovery where I get the options to download latest version and recovery, Reboot and Shutdown. If I select the Download latest version and recovery it setups my Wifi and then fails with the message Getting package info failed.
Mode 2 - Power + Vol Up
It boots into a screen that gives me the option to Reboot your System Now, Wipe data / factory Reset , Wipe Cache partition. Selecting Wipe Data/Factory reset returns back to this screen with an error - Red Exclamation mark. Selecting Wipe Cache partition seems to perform a wipe and returns to the original screen with the 3 options again.
Mode 3 - Connect to PC with Hisense and power + vol down
This goes into an android recovery screen which is white with a green android displayed
I have the USB drivers installed on my PC but I cannot see the phone in Windows explorer when I plug it in via USB. I do hear the recognition tone that Windows has recognised that a USB device has been attached. The Huawei PC software doesn't recognise it unless I go into the white android screen and select recover. This always fails saying it cannot find a package.
I have installed stock P9 Marshmallow firmware on my SD card in a dload folder (which is how I bricked it in the first place. When I hold Vol up and Vol Down and power it starts installing but then fails about 40% - 50% through. I have tried multiple versions of the L09 firmware but none of them install successfully.
I am not very technical and not an android expert so cannot say I have done everything perfectly correctly. #
Is my phone bricked or is it possible get my phone back working?

You can get your phone back, search the forums for dc phoenix, which has helped people including myself.
The other option is to go the huawei website, and look under downloads for p9. Find the two firmwares for beta rollback and follow the instructions, although i am not 100% confident that will work for you

use dc phoneix ... i was the in tha same condition

So I have installed and tried install a few different ROMs to the phone. DC Phoenix recognizes the phone as it comes up with the IMEI and version in the left hand window. It seems to install the ROM sucessfully.
I get a message at the end saying it finished successfully but when I boot back up it just goes straight into the same eRecovery screen I have tried B166 and B322 and no luck. Is there anything different I should be doing?

...and now I have a new issue
Thanks for everyone's help. After downloading and trying about 10 different ROMs I was able to get a Nougat ROM to install. Now I have a different problem
1. When I reboot I get a verification failed message. I get an option to go to eRecovery (which works the same as above and doesn't find a package)
So what I really want now is just to get back to stock Marshmallow and not have a verification message and not have some Nougat version that doesn't look like the official Huawei ROM.
So what next folks?

I encountered the exact same problem a few days ago. I didn't try DC Phoenix, instead sent it to Huawei for repair, claiming the phone was in a boot-loop I couldn't recover from.
They have fixed it now and the P9 is on its way back to me. What's strange is that they have swapped the whole motherboard for a new one! Didn't expect that.

"Bricked" Note 8, can't boot into TWRP

So I tried to mod my phone (with this, if you're interested https://forum.xda-developers.com/gal...creen-t3759567) but I did something stupid. I thought TWRP was working properly but I'd installed Oreo and didn't wipe data. Well I installed the zip anyway. At the end, an error showed up (could not mount /data or something similar) and my phone will now not boot.
If I try to boot the phone, it just vibrates and stays black. Volume Down + Power + Bixby gets the phone out of this state and the charging screen shows again. I can't boot into TWRP at all. I can boot into download mode but Odin keeps failing when I try to reflash the XEF Oreo firmware (screenshot is in the attachment, it says passed but doesn't attempt to flash the files). I managed to flash TWRP which worked but since I can't boot into it it didn't help. Anthing else I can flash with Odin, or can anybody tell me what's going on / if it's unrecoverable? (I've tried a couple of different versions, they all exhibit the same behaviour)

chemeleon said:
So I tried to mod my phone (with this, if you're interested https://forum.xda-developers.com/gal...creen-t3759567) but I did something stupid. I thought TWRP was working properly but I'd installed Oreo and didn't wipe data. Well I installed the zip anyway. At the end, an error showed up (could not mount /data or something similar) and my phone will now not boot.
If I try to boot the phone, it just vibrates and stays black. Volume Down + Power + Bixby gets the phone out of this state and the charging screen shows again. I can't boot into TWRP at all. I can boot into download mode but Odin keeps failing when I try to reflash the XEF Oreo firmware (screenshot is in the attachment, it says passed but doesn't attempt to flash the files). I managed to flash TWRP which worked but since I can't boot into it it didn't help. Anthing else I can flash with Odin, or can anybody tell me what's going on / if it's unrecoverable? (I've tried a couple of different versions, they all exhibit the same behaviour)
Click to expand...
Click to collapse
There is a newer version of odin, are you using that? You will need that to flash Oreo. Can get it in the link below. Odin v3.13.1
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072

Doh! Had it already, was the only one I didn't try. It's flashing now. Many thanks

SM-A305G Boot Loop, trying to flash stock firmware

I made the mistake of flashing the wrong version of TWRP using Heimdall, causing the device to get caught in a boot loop. Initially, I couldn't enter recovery or download mode to re-flash the firmware, but after disconnecting the battery to shutdown I was able to get back into download mode and flash a stock ROM (downloaded from SamFirm).
After flashing the ROM (now using Odin) and auto rebooting, I get the installing software update screen with a loading symbol (for a few seconds), followed by a boot loop (Samsung screen -> Knox warning -> reboot -> repeat).
- Power cycling the device boots back into recovery mode.
- "Reboot device" option from recovery mode enters the boot loop.
- "Reboot to bootloader" option reboots into download mode (I'm not sure why)
- Wiping the cache / factory reset between reboots seems to have no result
The phone is an unlocked SM-A305G/DS from Amazon, so I'm not confident I have the carrier version correct. The only record of the CSC version I had before was the .pit file I extracted through Heimdall before flashing the wrong firmware. It contained the string "TPA", so that's my current best guess. I have tried firmwares for TPA, CHE, and CHO but with the same results.
Any ideas what might be wrong? I imagine the device isn't hard bricked, so I don't know what else could have went wrong. Kind of a newbie when it comes to android firmware, but I have some technical background, so let me know if there's some more things I can try or if more information might be needed to debug this issue.
Some more specific questions:
1. Does the carrier code matching the device matter? If so, is there a way to find the original CSC from IMEI on an unlocked/no warranty phone? The few websites I tried don't appear to be able to get that info.
2. Is there any way to access the logs from the last normal boot attempt? (Recovery mode only appears to keep logs for itself, not normal boot)
3. Could tripping Knox somehow be the problem? I didn't think it had any repercussions except voiding the warranty (which the device didn't come with)....
4. Can Samsung support somehow help me find my CSC/correct firmware even if I don't have a warranty?

Solved
Posting solution here just in case someone makes the same mistake,
I realized that I neglected to post the information displayed in download mode, most importantly:
`KG State: Prenormal`
Googling that, I found that this might be caused because of a mismatch between my SIM card region and the installed firmware region. So I removed my SIM card, re-flashed the latest stock firmware again, and it booted :laugh:
Also, download mode displayed the correct CSC code regardless of installed firmware (I installed CHE firmware and it still displayed TPA), though I'm not sure if that's consistent across devices.

Samsung Galaxy Note 9 Crownlte Bootloop

Hi, I've recently bought a Samsung Note 9, secondhand, yet still new condition. Courier dropped the delivery and I was impressed with what I received, unboxing through to switching it on. Awesome display, features, speed, etc.. unfortunately, it didn't last long. Went through the initial setup, google acc, personal preferences, up to the point where security features needed to be activated. As I wanted to enroll fingerprints, it asked for passkey before biometrics could be recorded. I entered a 5 digit code, again to confirm, and then it was set. Then the trouble started. Phone locked by pressing the power button then refused to unlock with the passcode that I've just saved. After a while of trying to enter the key I've used, as well as some alternative combinations for in case I've made a mistake (twice?), I've resorted to boot into recovery mode by switching off the device and pressing bixby+vol up+pwr. Booted into recovery, chose factory reset and let it run.
It finished in less than a second, before I chose to reboot device. Only to see the screen stay dark with red words top left corner of screen: Only official firmware to be installed something something. And that's what I kept on getting, did abovementioned step again, same issue, tried formatting cache, same issue, tried lacking storage boot, same issue, tried flashing custom rom via Odin, same issue, tried to find official firmware and installed that same issue. I've noticed that none of the packages I try to install works due to an error stating that Signature Verification Failed. Every time, whether I try sideloading via adb, updating via sdcard or flashing with Odin, I get the same result. Last try was flashing the bootloader with an recovery zip I found somewhere and now it just bootloops the Samsung Galaxy Note 9 startup screen, vibrates, restarts and same screen again. Even if I let it loop, it keeps on forever. I can still access bootloader, recovery and Download mode with pressing the button combinations, but nothing I try of the options available resolves the problem.
I'm really at a point where I don't know what to do or try, please advise. Here's some additional info that might help:
Samsung Galaxy Note 9 SM-N960F Crownlte.
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSI3
After a few of my flashing attempts, abovementioned line now reads:
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSF9
Its the Exynos version of the Note 9. Any direction or help will be much appreciated.
Thanx

Sdejager2 said:
Hi, I've recently bought a Samsung Note 9, secondhand, yet still new condition. Courier dropped the delivery and I was impressed with what I received, unboxing through to switching it on. Awesome display, features, speed, etc.. unfortunately, it didn't last long. Went through the initial setup, google acc, personal preferences, up to the point where security features needed to be activated. As I wanted to enroll fingerprints, it asked for passkey before biometrics could be recorded. I entered a 5 digit code, again to confirm, and then it was set. Then the trouble started. Phone locked by pressing the power button then refused to unlock with the passcode that I've just saved. After a while of trying to enter the key I've used, as well as some alternative combinations for in case I've made a mistake (twice?), I've resorted to boot into recovery mode by switching off the device and pressing bixby+vol up+pwr. Booted into recovery, chose factory reset and let it run.
It finished in less than a second, before I chose to reboot device. Only to see the screen stay dark with red words top left corner of screen: Only official firmware to be installed something something. And that's what I kept on getting, did abovementioned step again, same issue, tried formatting cache, same issue, tried lacking storage boot, same issue, tried flashing custom rom via Odin, same issue, tried to find official firmware and installed that same issue. I've noticed that none of the packages I try to install works due to an error stating that Signature Verification Failed. Every time, whether I try sideloading via adb, updating via sdcard or flashing with Odin, I get the same result. Last try was flashing the bootloader with an recovery zip I found somewhere and now it just bootloops the Samsung Galaxy Note 9 startup screen, vibrates, restarts and same screen again. Even if I let it loop, it keeps on forever. I can still access bootloader, recovery and Download mode with pressing the button combinations, but nothing I try of the options available resolves the problem.
I'm really at a point where I don't know what to do or try, please advise. Here's some additional info that might help:
Samsung Galaxy Note 9 SM-N960F Crownlte.
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSI3
After a few of my flashing attempts, abovementioned line now reads:
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSF9
Its the Exynos version of the Note 9. Any direction or help will be much appreciated.
Thanx
Click to expand...
Click to collapse
1. Install official stock rom from sammobile from this link (doesn't matter which you download):
https://www.sammobile.com/samsung/galaxy-note9/firmware/#SM-N960F
2. Load up Odin, put corresponding files to their slots, AP to AP, BL to BL, etc..
3. Boot into download mode (phone powered off, press and hol volume down + bixby button and insert cable to computer)
4. Flash it, wait for it to boot up.

Ok, I'll try that today and hopefully my next reply will be me posting from the Note. Let's hold thumbs.
Thanx

How did you solve the problem.. Same here.. Stuck at bootloop
Am unable enter in to download mode.. Tried hundreds of times

Minzlife said:
Am unable enter in to download mode.. Tried hundreds of times
Click to expand...
Click to collapse
try this
Plug your phone to pc
Hold power button + volume down for a few seconds
Then right before the phone logo shows, bixby + volume down
Now download mode shows. Flash stock rom

TWRP soft brick?

After months of deliberation I finally decided to root my Note 9. It was the first time I've ever tried rooting and it seems to have gone horribly wrong. To root the phone, I followed the guide in the video titled 'How to Root Galaxy Note 9! [EASIEST METHOD]' on youtube which has an instruction link in the description. As a new user here, the forum doesn't allow me to post links yet, so please just type the title on youtube and it'll come up as the first result.
What I did was:
- unlocking bootloader
- Flash AP file with TWRP version 3.4.0
- Wipe data
- Since I was worried about using a software from an unknown source, I then flashed the official magisk v20.4 instead of the 'N9-S9_root_for_oem_issue_devices_v3' file recommended in the video.
After doing so, the note 9 restarted and showed the error message "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data.". I allowed the phone to reset.
Following this, the phone restarted and showed exactly the same message of 'verification failed' and no amount of going through the rebooting process resolved the issue. I googled the issue and was advised to flash the phone with Odin by going into download mode. I then tried to go into download mode, but the phone will simply not go into it and tries to restart the normal way. I also tried to connect to my laptop to see if I can flash with odin but the phone was not recognised at all by the computer.
I then tried to reboot using the twrp key combo and this worked. I then decided to try flashing with the 'N9-S9_root_for_oem_issue_devices_v3' file in the tutorial. Yet, this led to the same issue as with the official magisk file.
Looking at some rooting tutorials, I see that some of them recommend flashing CSC, AP, BL and CP instead of just the AP in the tutorial I followed. I then thought that perhaps the issue is I need to install a ROM on the device. I therefore tried to load the lineage 17.1 ROM in the micro SD card and installed it (top left option on twrp 'install') as well as the magisk and disable_dm_verify_forceencrypt zip files.
In hindsight, this was a stupid move from me - I did so I was in full panic mode at that point and desperate for a solution.
After doing so, the phone rebooted and showed a booting animation of a single blue curved line stuck with a circle rolling from right to left on it.
I left it for a while, hoping that it meant the new ROM was booting. 30 min later it was still stuck on the animation!
I then tried to reboot the phone. Pressing power button did nothing. I then tried different combinations and eventually power + volume up + bixby allowed it to restart in TWRP mode.
As of now, the phone is still in TWRP mode. The phone is still not recognised by my laptop and will not enter download mode if I press volume down + bixby when restarting.
I am fully aware that I've screwed up the rooting process and feel awful about it. It was the first time I've ever tried rooting and I really hope it is only a 'soft brick' and that my phone can be saved. I would really appreciate if anyone here could advise what I can do to complete the root process correctly from here?
Many thanks,
Sam

Is there a "download" or "bootloader" option when you press the reboot button in TWRP? My Note9 is on stock, so I'm not 100% certain myself. However if there is, that should take you to Samsung's download screen. This way you can send yourself back to stock if you give up on rooting your device.
BTW, I do recommend following a note9 rooting guide on XDA (it's not too hard to find) over a youtube video, since YouTube videos can often be out of date or a little sketchy.