Hey Guys/Gals!!!
Looking for help.
I received my N6 yesterday. After logging into the device, and turning developer options on, I placed the device into fastboot mode and proceded with unlocking the bootloader like I did with all my previous Nexus devices. In hindsight, the only error was my failure to check the OEM unlock box in the developer option page.
After getting the device into fastboot mode, I entered "Fastboot OEM unlock". I was given the screen asking if I wanted to unlock the bootloader. I selected yes and hit the power button. The phone then showed "Device is unlocked. Status Code 3." Not doing anything else, I tried restarting by selecting start and hitting the power button. A new screen came up with a little robot with a spinning sphere. Underneath the robot was "erasing..." This screen went on and on for ages. Eventually, I got tired of letting it sit there and was able to power off via the main fastboot screen.
This morning, I kept getting the erasing message. I kept powering down, not sure what else was going on.
Now, I am no longer getting the erasing message. The phone boots up, gets past the google screen with an unlocked padlock at the bottom, and proceeds to the splash screen (swirling dots). There it just sits.
I tried entering recovery mode via the fastboot screen, but I get my old friend the robot with the spinning sphere (this time no erasing message).
I know the factory images haven't been posted, but can someone help with what I have so far? Will reflashing solve the problem?
Nucleonic said:
Hey Guys/Gals!!!
Looking for help.
I received my N6 yesterday. After logging into the device, and turning developer options on, I placed the device into fastboot mode and proceded with unlocking the bootloader like I did with all my previous Nexus devices. In hindsight, the only error was my failure to check the OEM unlock box in the developer option page.
After getting the device into fastboot mode, I entered "Fastboot OEM unlock". I was given the screen asking if I wanted to unlock the bootloader. I selected yes and hit the power button. The phone then showed "Device is unlocked. Status Code 3." Not doing anything else, I tried restarting by selecting start and hitting the power button. A new screen came up with a little robot with a spinning sphere. Underneath the robot was "erasing..." This screen went on and on for ages. Eventually, I got tired of letting it sit there and was able to power off via the main fastboot screen.
This morning, I kept getting the erasing message. I kept powering down, not sure what else was going on.
Now, I am no longer getting the erasing message. The phone boots up, gets past the google screen with an unlocked padlock at the bottom, and proceeds to the splash screen (swirling dots). There it just sits.
I tried entering recovery mode via the fastboot screen, but I get my old friend the robot with the spinning sphere (this time no erasing message).
I know the factory images haven't been posted, but can someone help with what I have so far? Will reflashing solve the problem?
Click to expand...
Click to collapse
Since it sounds like there's no way to do a factory reset, the fastest way back to a functional phone is to reflash the factory image.
I would call google and see of they have an eta on the factory image being released. I know it's a long shot but it seems like you the tried everything else.
When you reboot to recovery and get the robot push volume up.
I would go back into recovery and do another factory reset. Make sure it's plugged in and when it says erasing just let it sit until it's finished even if it takes a couple of hours. It may have really been erasing in the background and got interrupted several times when you powered off.
Have you tried relocking the bootloader to see if that makes a difference?
Wow!
Try holding the power button down for like 30 seconds to hard reset it.
Just tested this. You didn't break anything it's just an odd way to open recovery. You need to hold down power and then press volume up when the open android image is on the screen.
@Nucleonic did you solve the problem?
Still nothing but swirling balls. Just have to wait for the factory image to be released.
Nucleonic said:
Still nothing but swirling balls. Just have to wait for the factory image to be released.
Click to expand...
Click to collapse
Can you give it any fastboot commands? If there is a way to pull the image off my phone I will (does anyone know how)
Fastboot works great. That is how I am able to power off the device. OEM lock/unlock is fine. Fastboot devices is fine. Fastboot reboot and reboots boot loader all work fine. Because I can and have nothing else to do, I even put in an incompatible recovery. Fastboot flash recovery works. Just can't get the thing to boot past the spiraling balls.
Weird, I wonder what happened. Anyone know? I think I've read others have had success unlocking the bootloader without checking the box in settings like Nucleonic.
Nucleonic said:
Hey Guys/Gals!!!
Looking for help.
I received my N6 yesterday. After logging into the device, and turning developer options on, I placed the device into fastboot mode and proceded with unlocking the bootloader like I did with all my previous Nexus devices. In hindsight, the only error was my failure to check the OEM unlock box in the developer option page.
After getting the device into fastboot mode, I entered "Fastboot OEM unlock". I was given the screen asking if I wanted to unlock the bootloader. I selected yes and hit the power button. The phone then showed "Device is unlocked. Status Code 3." Not doing anything else, I tried restarting by selecting start and hitting the power button. A new screen came up with a little robot with a spinning sphere. Underneath the robot was "erasing..." This screen went on and on for ages. Eventually, I got tired of letting it sit there and was able to power off via the main fastboot screen.
This morning, I kept getting the erasing message. I kept powering down, not sure what else was going on.
Now, I am no longer getting the erasing message. The phone boots up, gets past the google screen with an unlocked padlock at the bottom, and proceeds to the splash screen (swirling dots). There it just sits.
I tried entering recovery mode via the fastboot screen, but I get my old friend the robot with the spinning sphere (this time no erasing message).
I know the factory images haven't been posted, but can someone help with what I have so far? Will reflashing solve the problem?
Click to expand...
Click to collapse
Try this:
• Press and hold Vol DN key then momentary press PWR key. Unit should power on into the bootloader screen. (you can now let go of the Vol DN key)
• Use the Vol DN to scroll two positions down until the bootloader options show “Recovery mode”
• Use the power key to select “Recovery Mode”
• Wait for your phone to enter recovery. The display will show the laying down Android with a red triangle exclamation mark.
• Press and hold the power key then quickly press the Vol up key (Caution pressing the power key for longer then 10s will reset the device).
• The phone should now be in system recovery option mode.
• Use the Vol DN key to scroll two positions down to the “wipe data/factory reset”
• Use the power key to select that option.
• Scroll down through the “no” option until you get to the “yes” option using the Vol Dn key 7 positions.
• Use the power key to select that option.
Your phone should now eared and reset back to factory mode. Once completed, use the power key to restart the device.
Else you can use the following fastboot commands to reset:
fastboot erase userdata
fastboot erase cache
fastboot reboot
Hope that helps,
fifo209 said:
Try this:
•Press and hold Vol DN key then momentary press PWR key. Unit should power on into the bootloader screen. (you can now let go of the Vol DN key)
•Use the Vol DN to scroll two positions down until the bootloader options show “Recovery mode”
•Use the power key to select “Recovery Mode”
•Wait for your phone to enter recovery. The display will show the laying down Android with a red triangle exclamation mark.
•Press and hold the power key then quickly press the Vol up key (Caution pressing the power key for longer then 10s will reset the device).
•The phone should now be in system recovery option mode.
•Use the Vol DN key to scroll two positions down to the “wipe data/factory reset”
•Use the power key to select that option.
•Scroll down through the “no” option until you get to the “yes” option using the Vol Dn key 7 positions.
•Use the power key to select that option.
Your phone should now eared and reset back to factory mode. Once completed, use the power key to restart the device.
Else you can use the following fastboot commands to reset:
fastboot erase userdata
fastboot erase cache
fastboot reboot
Hope that helps,
Click to expand...
Click to collapse
Thanks! I executed the fastboot commands. After reboot, I'm still stuck with the spiraling balls.
First time power on after rest take a very long time. (up to 5 min)
Sent from my AOSP on Shamu using Tapatalk
Still have swirling balls 18 minutes after turning back on.
I downloaded the factory image for the N6. I ran sh flash-all.sh. This is what I got:
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.342s]
finished. total time: 0.463s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (67170 KB)...
OKAY [ 2.105s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.730s]
finished. total time: 2.835s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(1322,0xa0b121d4) malloc: *** mach_vm_map(size=1681272832) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679592636 bytes
error: update package missing system.img
What do I do next? can't get past that error message.
You don't need to enable Developer Options just to unlock the bootloader. When I first powered on my N6, I went right to the bootloader screen without loading Lollipop at all, since I knew it would delete everything, so why go through the setup process twice?
I did fastboot oem unlock, and rebooted. I only enabled Developer Options after I unlocked bootloader, and set up Lollipop
Related
I was trying to update recovery and I typed the wrong commands in fastboot.
Instead of
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
I typed:
Code:
fastboot boot recovery openrecovery-twrp-2.6.3.3-m7.img
When that failed because "recovery" didn't exist I still didn't notice my mistake, and went with:
Code:
fastboot boot openrecovery-twrp-2.6.3.3-m7.img
creating boot image...
creating boot image - 10240 bytes
downloading 'boot.img'...
OKAY [ 0.232s]
booting...
OKAY [ 0.003s]
finished. total time: 0.240s
Since then my phone pretty much stopped working. The screen is on, but is hung - the power buttons and volume buttons do nothing. Here are some commands I tried
Code:
fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 0.588s
-------------------------------
fastboot devices
HT35CW91**** fastboot
-----------------
fastboot reboot-bootloader
rebooting into bootloader...
Even the reboot just hung there with no change in the device. Is it a paperweight now or is there a way back? Obviously I can't remove the battery and I've not unplugged the USB cable just in case
Teefee said:
I was trying to update recovery and I typed the wrong commands in fastboot.
Instead of
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
I typed:
Code:
fastboot boot recovery openrecovery-twrp-2.6.3.3-m7.img
When that failed because "recovery" didn't exist I still didn't notice my mistake, and went with:
Code:
fastboot boot openrecovery-twrp-2.6.3.3-m7.img
creating boot image...
creating boot image - 10240 bytes
downloading 'boot.img'...
OKAY [ 0.232s]
booting...
OKAY [ 0.003s]
finished. total time: 0.240s
Since then my phone pretty much stopped working. The screen is on, but is hung - the power buttons and volume buttons do nothing. Here are some commands I tried
Code:
fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 0.588s
-------------------------------
fastboot devices
HT35CW91**** fastboot
-----------------
fastboot reboot-bootloader
rebooting into bootloader...
Even the reboot just hung there with no change in the device. Is it a paperweight now or is there a way back? Obviously I can't remove the battery and I've not unplugged the USB cable just in case
Click to expand...
Click to collapse
fastboot boot <name of recovery>.img no longer works; it only works on hboot 1.44
just reboot using POWER + VOLDOWN the flash recovery.
nkk71 said:
fastboot boot <name of recovery>.img no longer works; it only works on hboot 1.44
just reboot using POWER + VOLDOWN the flash recovery.
Click to expand...
Click to collapse
Thanks for the response. The phone doesn't respond to any button presses, so I can't VOLDOWN to Power Down. I have tried holding VOLDOWN + POWER like you said but the screen is still on and the phone hasn't done anything
Teefee said:
Thanks for the response. The phone doesn't respond to any button presses, so I can't VOLDOWN to Power Down. I have tried holding VOLDOWN + POWER like you said but the screen is still on and the phone hasn't done anything
Click to expand...
Click to collapse
no i meant press and hold POWER + VOLDOWN buttons (preferably under a bright light), then when it reboots, let go of POWER, but keep holding VOLDOWN and you're back in bootloader.
also it's safe to unplug it. once you do, bootloader may actually respond to normal presses again.
nkk71 said:
no i meant press and hold POWER + VOLDOWN buttons (preferably under a bright light), then when it reboots, let go of POWER, but keep holding VOLDOWN and you're back in bootloader.
also it's safe to unplug it. once you do, bootloader may actually respond to normal presses again.
Click to expand...
Click to collapse
Thanks very much, you're a lifesaver! When I unplugged the device the screen still didn't respond but pressing & holding POWER+VOLDOWN for ~10 seconds rebooted the phone and I'm back in business.
Teefee said:
Thanks for the response. The phone doesn't respond to any button presses, so I can't VOLDOWN to Power Down. I have tried holding VOLDOWN + POWER like you said but the screen is still on and the phone hasn't done anything
Click to expand...
Click to collapse
actually just tried, once unplugged bootloader still "hung", had to use the POWER + VOLDOWN as mentioned above to go to bootloader again
I have a Nexus 6. I've been on build LMY47D. My storage was showing as 32GB when I have a 64GB version. I read this post for a fix. I did a fresh install of adb, checked the OEM unlock, removed security (PIN) and turned on USB debugging from developer settings. I used "adb reboot bootloader" to reboot to the bootloader and then typed the commands from the post I linked above:
fastboot format userdata
fastboot format cache
I was wanting to take the OTA update so I was planning on flashing the LRX22C image and wanted to make sure I was OEM unlocked so before rebooting I also did:
fastboot oem unlock
The result said:
<bootloader> device already unlocked!
FAILED <remote failure>
finished. total time 0.002s
I figured I was unlocked and essentially factory reset, so I entered:
fastboot reboot
It was on the spinning dots for about an hour. I read somebody with something similar rebooting after such a long time and everything being ok, so I tried it with no luck.
I can get boot to the bootloader. The lock is unlocked. When I try to go to recovery I just see the dead android with the red sign and exclamation. My PC no longer sees the phone, I think because I'm no longer in USB debugging? Is there any way to fix this? I've tried selecting "factory" from the bootloader, but get the same result--endless bootloop. Any help is appreciated!
EDIT: Thought I'd add, at the bottom of the bootloader screen it shows "Device is Unlocked. Status Code: 3"
EDIT 2: While waiting for feedback, I downloaded wugfresh's nexus toolkit and selected the softbrick/bootloop option. It's downloading a factory image atm, so we'll see how this goes.
Marcellus1 said:
I have a Nexus 6. I've been on build LMY47D. My storage was showing as 32GB when I have a 64GB version. I read this post for a fix. I did a fresh install of adb, checked the OEM unlock, removed security (PIN) and turned on USB debugging from developer settings. I used "adb reboot bootloader" to reboot to the bootloader and then typed the commands from the post I linked above:
fastboot format userdata
fastboot format cache
I was wanting to take the OTA update so I was planning on flashing the LRX22C image and wanted to make sure I was OEM unlocked so before rebooting I also did:
fastboot oem unlock
The result said:
<bootloader> device already unlocked!
FAILED <remote failure>
finished. total time 0.002s
I figured I was unlocked and essentially factory reset, so I entered:
fastboot reboot
It was on the spinning dots for about an hour. I read somebody with something similar rebooting after such a long time and everything being ok, so I tried it with no luck.
I can get boot to the bootloader. The lock is unlocked. When I try to go to recovery I just see the dead android with the red sign and exclamation. My PC no longer sees the phone, I think because I'm no longer in USB debugging? Is there any way to fix this? I've tried selecting "factory" from the bootloader, but get the same result--endless bootloop. Any help is appreciated!
EDIT: Thought I'd add, at the bottom of the bootloader screen it shows "Device is Unlocked. Status Code: 3"
EDIT 2: While waiting for feedback, I downloaded wugfresh's nexus toolkit and selected the softbrick/bootloop option. It's downloading a factory image atm, so we'll see how this goes.
Click to expand...
Click to collapse
When you see the dead android (recovery) just press volume up + power simultainiously and do a data factory reset, after that the phone should boot up fine.
PS: don`t use toolkits, they cause more harm then good if used by unexperienced users and experienced users don`t use it anyway
gee2012 said:
When you see the dead android (recovery) just press volume up + power simultainiously and do a data factory reset, after that the phone should boot up fine.
PS: don`t use toolkits, they cause more harm then good if used by unexperienced users and experienced users don`t use it anyway
Click to expand...
Click to collapse
Thanks for your response. I actually tried pressing volume up + power simultaneously several while at recovery and nothing happened. After that I tried other key combinations, wondering if I got it wrong, and nothing happened with those either.
I ended up using the toolkit (before I saw your response) and my phone is back in business *HUGE sigh of relief*
Marcellus1 said:
Thanks for your response. I actually tried pressing volume up + power simultaneously several while at recovery and nothing happened. After that I tried other key combinations, wondering if I got it wrong, and nothing happened with those either.
I ended up using the toolkit (before I saw your response) and my phone is back in business *HUGE sigh of relief*
Click to expand...
Click to collapse
FWIW: to enter the recovery menu in stock recovery, the combo is - press and hold power, and press and release volume up.
I recently purchased a Moto X XT1056 through eBay to use as a guinea pig for flashing custom ROMs without risking my primary phone. When I first booted the phone, the last owners account was still present and alot of apps were crashing. I didn't care because I was going to wipe it anyway. I do eventually, and frustratingly, make it to the Settings Menu that allows me to factory reset the phone. It restarts, does its thing and reboots, but it didnt get wiped. I thought, 'No worries, I'm going to unlock it and that will wipe it.'
I started following the instructions on the CM website.
First thing I did was use the Moto web site to get an unlock code and unlock the bootloader. I'm assuming that succeeded because I get the Bootloader unlocked boot screen and the bootloader screen says 'Device is UNLOCKED. Status Code: 3'.
Then I tried to flash twrp-2.8.7.0-ghost.img per the instructions and get this result:
Code:
[[email protected] phone]# mfastboot flash recovery Recovery.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (8498 KB)...
OKAY [ 0.834s]
writing 'recovery'...
OKAY [ 0.949s]
finished. total time: 1.783s
[[email protected] phone]#
I assume everything is fine and reboot into Recovery using the bootloader screen, but all I get is the dead android and red triangle. Pressing VOL+ and Power get me to the stock recovery where I can reboot the machine. It boots into Android and I notice that the unlock didn't wipe the device. I turn it off and using the button combo boot into the bootloader then select Recovery and use the stock recovery to factory reset the device. I reboot the phone and see that the previous owners account is still there and there are a bunch of popups stating that apps are crashing. I have tried a number of things from a few threads I have read, but nothing seems to work. Trying to flash anything to any partition just seems to succeed without an error, but nothing changes. The only time I get anything different is when i try to erase or format a partition, then I get 'Permission Denied'.
I haven't been able to find any help using search on these forums or using Google.
Please Help.
I do know that it has 4.4.4 on it and Bootloader 30.B7.
I use Linux only and do not have access to a Windows machine.
Android SDK is installed so I have 'adb' and 'fastboot' and I also installed 'mfastboot.'
And, yes, I issued all the commands with root privileges.
its dead already! problem is inside emmc chip! its fried ;(..
Heya! I've got the Huawei P9 rebranded on the Chinese EVA-AL10 Oreo firmware.
My phone has recently stopped working and is unable to boot into the system and recovery.
The bootloader is unlocked and it freezes on the Your device has been unlocked and can't be trusted screen that shows 3 boot options in the middle of the screen (Press power key to continue, Vol up 3 seconds for erecovery, Device will boot automatically after 5 if nothing is done on that screen). It also freezes on a similar screen without the three options if I do the Vol up + Power shortcut to enter the erecovery.
If I do the Volume up, Volume down and power boot shortcut, it boots into a screen with a green background along with a red rectangle in the upper half of the screen and a blue rectangle in the lower half. It stays on this screen for about a minute before freezing on the Your device has been unlocked... screen when it attempts to enter the erecovery.
The same screen shows when I do the Volume down and power boot shortcut when it isn't connected to my computer. The difference this time being that every time it reboots after a short period of time, it reboots into the same screen.
It is only able to successfully able to boot in the Fastboot & Rescue Mode.
Joshywooful1 said:
Heya! I've got the Huawei P9 rebranded on the Chinese EVA-AL10 Oreo firmware.
My phone has recently stopped working and is unable to boot into the system and recovery.
The bootloader is unlocked and it freezes on the Your device has been unlocked and can't be trusted screen that shows 3 boot options in the middle of the screen (Press power key to continue, Vol up 3 seconds for erecovery, Device will boot automatically after 5 if nothing is done on that screen). It also freezes on a similar screen without the three options if I do the Vol up + Power shortcut to enter the erecovery.
If I do the Volume up, Volume down and power boot shortcut, it boots into a screen with a green background along with a red rectangle in the upper half of the screen and a blue rectangle in the lower half. It stays on this screen for about a minute before freezing on the Your device has been unlocked... screen when it attempts to enter the erecovery.
The same screen shows when I do the Volume down and power boot shortcut when it isn't connected to my computer. The difference this time being that every time it reboots after a short period of time, it reboots into the same screen.
It is only able to successfully able to boot in the Fastboot & Rescue Mode.
Click to expand...
Click to collapse
For the beginning, let's see which firmware your phone thinks it is on. Execute in Fastboot and copy back results (omit output of the first line - serial number):
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
zgfg said:
For the beginning, let's see which firmware your phone thinks it is on. Execute in Fastboot and copy back results (omit output of the first line - serial number):
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
Click to expand...
Click to collapse
Code:
fastboot devices
fastboot
fastboot oem get-bootinfo
(bootloader) unlocked
OKAY [ 0.002s]
Finished. Total time: 0.006s
fastboot oem get-product-model
(bootloader) EVA-AL10
OKAY [ 0.003s]
Finished. Total time: 0.006s
fastboot oem get-build-number
(bootloader) :EVA-AL10 8.0.0.535(C00)
OKAY [ 0.003s]
Finished. Total time: 0.007s
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :EVA-AL10C00B398
OKAY [ 0.005s]
Finished. Total time: 0.008s
fastboot getvar vendorcountry
vendorcountry: all/cn
Finished. Total time: 0.003s
The phone itself is a European model Huawei P9 EVA-L09, rebranded to EVA-AL10 using HWOTA7.
Joshywooful1 said:
The phone itself is a European model Huawei P9 EVA-L09, rebranded to EVA-AL10 using HWOTA7.
Click to expand...
Click to collapse
Do you want to go back to EVA-AL10c00 (b540 Oreo) or you want to downgrade to EVA-L09c432 (b504 Nougat)
zgfg said:
Do you want to go back to EVA-AL10c00 (b540 Oreo) or you want to downgrade to EVA-L09c432 (b504 Nougat)
Click to expand...
Click to collapse
I'm wanting to go back to EVA-AL10c00.
Joshywooful1 said:
I'm wanting to go back to EVA-AL10c00.
Click to expand...
Click to collapse
Download the official service repair for EVA-AL10c00b528:
https://androidhost.ru/6sl
Unpack until you find two folders, software with DLOAD installation and documentation with the installation guide - read and follow the guide very carefully, it describes how to perform DLOAD installation
Upon DLOAD, boot to b528 - do not setup Google account, do not restore apps or so, just connect to WiFi and check if you receive OTA updates up to b540 Patch02 (go to Settings/System/Software Update to check if OTA updates are available)
If you don't receive OTA, boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+ and boot then) and take Install latest firmware and recovery
EDIT:
Upon you update to b540 Patch02, install TWRP for Oreo, and flash Network patch (optionally also Face Unlock patch) as described in the OP posts:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
zgfg said:
Download the official service repair for EVA-AL10c00b528:
https://androidhost.ru/6sl
Unpack until you find two folders, software with DLOAD installation and documentation with the installation guide - read and follow the guide very carefully, it describes how to perform DLOAD installation
Upon DLOAD, boot to b528 - do not setup Google account, do not restore apps or so, just connect to WiFi and check if you receive OTA updates up to b540 Patch02 (go to Settings/System/Software Update to check if OTA updates are available)
If you don't receive OTA, boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+ and boot then) and take Install latest firmware and recovery
EDIT:
Upon you update to b540 Patch02, install TWRP for Oreo, and flash Network patch (optionally also Face Unlock patch) as described in the OP posts:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Click to expand...
Click to collapse
There's no installation guide in the ReleaseDocs folder. It only has several documents in Chinese (including one that tells me to use HiSuite to update my system which I'll not be able to follow as I'm unable to boot into the system). There are no documents that have DLOAD specific instructions.
zgfg said:
Download the official service repair for EVA-AL10c00b528:
https://androidhost.ru/6sl
Unpack until you find two folders, software with DLOAD installation and documentation with the installation guide - read and follow the guide very carefully, it describes how to perform DLOAD installation
Upon DLOAD, boot to b528 - do not setup Google account, do not restore apps or so, just connect to WiFi and check if you receive OTA updates up to b540 Patch02 (go to Settings/System/Software Update to check if OTA updates are available)
If you don't receive OTA, boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+ and boot then) and take Install latest firmware and recovery
EDIT:
Upon you update to b540 Patch02, install TWRP for Oreo, and flash Network patch (optionally also Face Unlock patch) as described in the OP posts:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Click to expand...
Click to collapse
Never mind what I said before. I've found the installation guide. It's all in Chinese so I had to put it through Google Translate so I could read it.
Joshywooful1 said:
Never mind what I said before. I've found the installation guide. It's all in Chinese so I had to put it through Google Translate so I could read it.
Click to expand...
Click to collapse
Strange, a year ago I downloaded such EVA-AL10c00b528 package from the same site and successfully unbricked.
It did have Installation guide in English
You should create DLOAD folder on your SD card, copy into the file and folder as found in the Software folder (see my screenshot), then make sure battery is 50% or more full, disconnect from USB, switch off, press and keep pressing both Vol+ and Vol-, boot
For your reference, see a similar guide from another service repair package:
https://mega.nz/#!F8UGyYQR!hOeQJyRyb13sKViCPL0XNK-cY5obHetUcvfNqHMJjTg
zgfg said:
Strange, a year ago I downloaded such EVA-AL10c00b528 package from the same site and successfully unbricked.
It did have Installation guide in English
You should create DLOAD folder on your SD card, copy into the file and folder as found in the Software folder (see my screenshot), then make sure battery is 50% or more full, disconnect from USB, switch off, press and keep pressing both Vol+ and Vol-, boot
For your reference, see a similar guide from another service repair package:
https://mega.nz/#!F8UGyYQR!hOeQJyRyb13sKViCPL0XNK-cY5obHetUcvfNqHMJjTg
Click to expand...
Click to collapse
I've just tried to enter the DLOAD mode and it just boots into the screen with a green background and 2 rectangles, a red one near in the upper portion of the screen and a blue one in the lower portion of the screen, as shown in this photo. It stays on this screen for a short amount of time before rebooting into the same screen.
Joshywooful1 said:
I've just tried to enter the DLOAD mode and it just boots into the screen with a green background and 2 rectangles, a red one near in the upper portion of the screen and a blue one in the lower portion of the screen, as shown in this photo. It stays on this screen for a short amount of time before rebooting into the same screen.
Click to expand...
Click to collapse
I never had such a brick but I remember that I saw some people reporting a screen with rectangles
You could try flashing Oreo no-check recovery:
https://mega.nz/#!UlklhYLD!rzn-ifOYF_HChWuWjYoqvcJQEXsUDE25LcQyfedKM2k
Code:
fastboot flash recovery_ramdisk eva_vie_recovery_nocheck.img
Then try to repeat DLOAD with AL10c00b528
Otherwise, there are on-line services providing paid unbrick support:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://ministryofsolutions.com/paid-services
Even better, you can ask @Tecalote (author of HWOTA7 method for rebranding and upgrading to Chinese Oreo), look at his profile and find his gmail address (he doesn't look to XDA anymore and probably he will not answer on PM) - he is from Germany and he unbricks Huawei phones on the per-donation model
You can also open the phone and use yourself the low-level Testpoint method:
https://forum.xda-developers.com/p9/how-to/solution-dead-p9-bootloader-locked-fpr-t3997631
zgfg said:
I never had such a brick but I remember that I saw some people reporting a screen with rectangles
You could try flashing Oreo no-check recovery:
https://mega.nz/#!UlklhYLD!rzn-ifOYF_HChWuWjYoqvcJQEXsUDE25LcQyfedKM2k
Code:
fastboot flash recovery_ramdisk eva_vie_recovery_nocheck.img
Then try to repeat DLOAD with AL10c00b528
Otherwise, there are on-line services providing paid unbrick support:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://ministryofsolutions.com/paid-services
Even better, you can ask @Tecalote (author of HWOTA7 method for rebranding and upgrading to Chinese Oreo), look at his profile and find his gmail address (he doesn't look to XDA anymore and probably he will not answer on PM) - he is from Germany and he unbricks Huawei phones on the per-donation model
You can also open the phone and use yourself the low-level Testpoint method:
https://forum.xda-developers.com/p9/how-to/solution-dead-p9-bootloader-locked-fpr-t3997631
Click to expand...
Click to collapse
I've just tried to flash that recovery and just got this output:
Code:
Sending 'recovery_ramdisk' (25668 KB) OKAY [ 0.697s]
Writing 'recovery_ramdisk' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
zgfg said:
I never had such a brick but I remember that I saw some people reporting a screen with rectangles
You could try flashing Oreo no-check recovery:
https://mega.nz/#!UlklhYLD!rzn-ifOYF_HChWuWjYoqvcJQEXsUDE25LcQyfedKM2k
Code:
fastboot flash recovery_ramdisk eva_vie_recovery_nocheck.img
Then try to repeat DLOAD with AL10c00b528
Otherwise, there are on-line services providing paid unbrick support:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://ministryofsolutions.com/paid-services
Even better, you can ask @Tecalote (author of HWOTA7 method for rebranding and upgrading to Chinese Oreo), look at his profile and find his gmail address (he doesn't look to XDA anymore and probably he will not answer on PM) - he is from Germany and he unbricks Huawei phones on the per-donation model
You can also open the phone and use yourself the low-level Testpoint method:
https://forum.xda-developers.com/p9/how-to/solution-dead-p9-bootloader-locked-fpr-t3997631
Click to expand...
Click to collapse
I've attempted to use DC-Phoenix to unbrick my phone and it always fails, saying
Code:
Cannot enter in Recovey mode
. I don't have the right screwdriver to remove the screws from my phone, so I can't do the testpoint method either. Is there anything else I could do?
Joshywooful1 said:
I've just tried to flash that recovery and just got this output:
Code:
Sending 'recovery_ramdisk' (25668 KB) OKAY [ 0.697s]
Writing 'recovery_ramdisk' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Click to expand...
Click to collapse
Per your previous Fastboot results, Bootloader is unlocked.
On the Chinese firmware FRP is unlocked by default, there was even no OEM Unlock option in Developers menu
So what is blocking your Fastboot to flash - on the Fastboot screen, bottom part, what does it say, Phone locked (green) or Phone unlocked (red), and similarly, FRP locked or unlocked?!
zgfg said:
Per your previous fastboot results, Bootloader is unlocked.
On the Chinese firmware FRP is unlocked per default, there was even no OEM Unlock setting in Developers menu.
So what is blocking Fastboot to flash - on Fastboot screen, bottom part, what does it say, Phone locked (green) or Phone unlocked (red), and similarly FRP locked or unlocked?!
Click to expand...
Click to collapse
It says
Code:
PHONE Unlocked
and doesn't say anything about FRP lock/unlock.
Joshywooful1 said:
It says Phone unlocked and doesn't say anything about FRP lock/unlock.
Click to expand...
Click to collapse
Yeah, Phone=Bootloader and I just checked, Chinese AL10 does not even display FRP status on the Fastboot screen
Joshywooful1 said:
... I don't have the right screwdriver to remove the screws from my phone, so I can't do the testpoint method either. Is there anything else I could do?
Click to expand...
Click to collapse
Yes, a shame, it's a pentalobe screwdriver but the same is used for iPhones, hence not really so hard to find
And two other options were given in one of my previous answers:
zgfg said:
...
Otherwise, there are on-line services providing paid unbrick support:
...
https://ministryofsolutions.com/paid-services
Even better, you can ask @Tecalote (author of HWOTA7 method for rebranding and upgrading to Chinese Oreo), look at his profile and find his gmail address (he doesn't look to XDA anymore and probably he will not answer on PM) - he is from Germany and he unbricks Huawei phones on the per-donation model
...
Click to expand...
Click to collapse
Btw, it might be valuable for the others to prevent a similar brick, if you describe what you were doing to get such a serious brick where phone can not boot to Recovery or eRecovery, and that flashing (although Bootloader and supposedly FRP are unlocked) and even DLOAD fail
Joshywooful1 said:
I've just tried to flash that recovery and just got this output:
Code:
Sending 'recovery_ramdisk' (25668 KB) OKAY [ 0.697s]
Writing 'recovery_ramdisk' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Click to expand...
Click to collapse
What were you doing before the brick? Did it suddenly reboot into the "RGB" screen like the other reported case over here, or were you installing some ROM or kernel? Those "RGBricks" seem to be pretty rare but fatal. How old is your phone?
Let's hope you still have enough write cycles in your eMMC judging from that log...because if that happens it means your phone finally kicked the bucket and needs a eMMC or board change. But let's be optimistic. Try wiping /system with fastboot and check if it fails. Try the testpoint method too
Joshywooful1 said:
Heya! I've got the Huawei P9 rebranded on the Chinese EVA-AL10 Oreo firmware.
My phone has recently stopped working and is unable to boot into the system and recovery.
The bootloader is unlocked and it freezes on the Your device has been unlocked and can't be trusted screen that shows 3 boot options in the middle of the screen (Press power key to continue, Vol up 3 seconds for erecovery, Device will boot automatically after 5 if nothing is done on that screen). It also freezes on a similar screen without the three options if I do the Vol up + Power shortcut to enter the erecovery.
If I do the Volume up, Volume down and power boot shortcut, it boots into a screen with a green background along with a red rectangle in the upper half of the screen and a blue rectangle in the lower half. It stays on this screen for about a minute before freezing on the Your device has been unlocked... screen when it attempts to enter the erecovery.
The same screen shows when I do the Volume down and power boot shortcut when it isn't connected to my computer. The difference this time being that every time it reboots after a short period of time, it reboots into the same screen.
It is only able to successfully able to boot in the Fastboot & Rescue Mode.
Click to expand...
Click to collapse
If chinese oreo b540 ROM is installed in your phone and you can boot into bootloader then try extracting recovery_ramdis, kernel, system and Ramdisk from Update.app and flashing it through Fastboot.
I would suggest you to follow this article https://openkirin.net/user_guide/how-to-flash-extracted-partition-images/
and this
https://openkirin.net/user_guide/how-to-extract-partition-images-from-stock-emui-firmware/
MI8 with older twrp and older LOS suddenly bootlooping. it is unlocked.
If I hold Vol Down, it flashes a fastboot logo for a few seconds.
If I hold Vol Up, it flashes the TWRP logo 3.3.1-1 for a bit longer than the fastboot.
If I hit 'adb devices' just right I can see the device for a few seconds.
I cannot shut off the phone.
Any help?
don't know what I am doing, but
./fastboot flash recovery /home/poiu/Downloads/t.img
< waiting for any device >
Sending 'recovery' (43588 KB) OKAY [ 1.614s]
Writing 'recovery' OKAY [ 0.133s]
Finished. Total time: 1.752s
@Kenora_I
Reflash Lineage (preferably a newer one)
Clear data before though and after just in case.
um why did you tag me
Because in pm you said to make a thread and tag you.
How do i flash lineage when it reboots in ~2 secs
LargePrime said:
How do i flash lineage when it reboots in ~2 sec
Click to expand...
Click to collapse
Oh sorry I forgot.
How did you flash recovery then?
Unsucessfully.
When i did ./fastboot ... It waited till it could see the phone and started the flash i guess, but as i said it said it was done in 1.7sec, so i think the phone rebooted, like it do, not caring if the flash was done
Type fastboot oem edl and automatically your phone will go to EDL Mode. If the command does not work, try fastboot reboot-edl or fastboot reboot edl.
If it can recieve and execute this it should enter emergency download mode.
And if that works then what should i do?
Flash it normally with miflash
Or qualcomm flash tool or sp flash tool depending on your chipset
./fastboot oem edl
< waiting for any device >
OKAY [ 0.000s]
Finished. Total time: 0.000s
still looping
./fastboot reboot-edl
< waiting for any device >
fastboot: usage: unknown command reboot-edl
./fastboot reboot edl
< waiting for any device >
fastboot: usage: unknown reboot target edl
The power button is probably broken.
You cant shut off the phone meaning something wrong with the power button.
The fastboot and twrp screens won't stay on for more than a few seconds.
I've done my reading and looking at similar issues. I've just concluded that the power key is damaged in some way.
Your best bet is to find someone to fix it. Or you can try to fix it yourself(but that is risky if you don't know what you're doing.)
I'm sorry for looping around the issue, I suspected the power button at first but I didn't really wanna leave you with a hardware issue unless I was sure so......
So, firstly, thanks.
You said power button, so i just played with the power button for 30 sec, AND IT BOOTED!
BUT, it has a SAFE MODE graphic on the screen.
rebooted and its fine?
can i ask how to update twrp and lineage, and can it keep the data intact?
Uh safe mode happens when the power button is held during boot.
Um that still is broken i think.
LargePrime said:
So, firstly, thanks.
You said power button, so i just played with the power button for 30 sec, AND IT BOOTED!
BUT, it has a SAFE MODE graphic on the screen.
rebooted and its fine?
can i ask how to update twrp and lineage, and can it keep the data intact?
Click to expand...
Click to collapse
upon reboot graphic is gone, but I agree it is sus
LargePrime said:
upon reboot graphic is gone, but I agree it is sus
Click to expand...
Click to collapse
Yep. Maybe get it looked at.
how update TWRP and LOS? in a way that keeps data?
LargePrime said:
how update TWRP and LOS? in a way that keeps data?
Click to expand...
Click to collapse
Well do they boot?
If LOS boot okay
Twrp can be flashed normally
Hope your issue is solved
I think it is. seems ok.
Thanks much