Hi.
I flashed the boot.img from my the 2nd of May CM nightly for yuga via fastboot over my bootloader unlocked C6603. It already had the CM kernel and CM installed but I wanted to flash the kernel again via fastboot.
Code:
uberdarwin:platform-tools snowman77$ ./fastboot flash boot boot.img
sending 'boot' (9328 KB)...
OKAY [ 0.585s]
writing 'boot'...
OKAY [ 0.449s]
finished. total time: 1.034s
uberdarwin:platform-tools snowman77$ ./fastboot reboot
rebooting...
finished. total time: 0.001s
I used fastboot to restart the device and since then the device will not turn on. I've tried the power and volume up until the device vibrates short and then long but then the power needed light (the flashing of red light). I plugged it into the wall and computer charger for a few hours but it wasn't charging. It seems to be charging now. I have it plugged into the wall charger now and the red light is on but when I unplug the cable the red light stays on. I have a stock firmware and flashtool already downloaded incase I ever need it.
I've talked to a few other community members and they are unsure about it either.
Does anyone know a way to get it to boot.
Thanks
Fixed it by using Power Volume Up+Down then getting it to turn on for a few mins then got into flashmode then compiled cm kernel from today's source and flashed that and that fixed it.
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 followed mike1986 "complete flashing guide"
s I unlocked bootloader - OK unlocked
then I do boot recovery to make nandroid backup first:
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.193s]
booting...
OKAY [ 0.001s]
finished. total time: 1.194s
so I try flash recovery:
fastboot flash recovery recovery.img
sending 'recovery' (9840 KB)...
after that my phone stuck in fastboot mode, it's screen is turned ON all the time, I can't even turn it OFF
Do i bricked my phone, please help
zukers said:
I followed mike1986 "complete flashing guide"
s I unlocked bootloader - OK unlocked
then I do boot recovery to make nandroid backup first:
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.193s]
booting...
OKAY [ 0.001s]
finished. total time: 1.194s
so I try flash recovery:
fastboot flash recovery recovery.img
sending 'recovery' (9840 KB)...
after that my phone stuck in fastboot mode, it's screen is turned ON all the time, I can't even turn it OFF
Do i bricked my phone, please help
Click to expand...
Click to collapse
Hold down the power button and vol down button untill the phone reboots to the bootloader again. Make sure its in fastboot mode and type
Code:
fastboot erase cache
Then type
Code:
fastboot flash recovery recovery.img
Then
Code:
fastboot reboot-recovery
Hopefully it will boot into recovery.
zukers said:
fastboot boot recovery.img
Click to expand...
Click to collapse
only works on hboot 1.44.
as mentioned above hold POWER + VOLDOWN (under a bright light), when it reboots let go of POWER but keep holding VOLDOWN, once in bootloader follow steps above to flash recovery
i think "fastboot reboot-recovery" doesn't work (at least for me), so do a "fastboot reboot-bootloader" then enter recovery.
zukers said:
I followed mike1986 "complete flashing guide"
s I unlocked bootloader - OK unlocked
then I do boot recovery to make nandroid backup first:
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.193s]
booting...
OKAY [ 0.001s]
finished. total time: 1.194s
so I try flash recovery:
fastboot flash recovery recovery.img
sending 'recovery' (9840 KB)...
after that my phone stuck in fastboot mode, it's screen is turned ON all the time, I can't even turn it OFF
Do i bricked my phone, please help
Click to expand...
Click to collapse
I had the EXACTLY same error as you. Didn't know what caused it. After about 20 attemps I finally managed to flash it. I changed the USB Port several times... But I didn't do any other things. Just try and try and try again. And whenever your screen freezes, do what @nkk71 said.
Volume down + Power button for several seconds...
OK, I have resolved my problem, thanks all of You.
So My nexus 6 decided not to turn on anymore after plugging into the charger last night. Pressing on the power button for hours it would only power on once and then stay stuck on this message across the screen "ap fastboot flash mode (secure)" in red. After about a minute it proceeded to the bootloader which looks like its been messed up, on the top right where you would see the options "recover", "restart", etc the word appears without any of the coloring behind it.. I've tried to boot to recovery (using TWARP) but it just restarts and goes right back to the same screen with the same message. If I attempt to shut off the phone it won't turn back on for another several hours of pressing the power button. I know it charges because I've seen the battery icon when off and it was full, I've also tried different outlets and chargers and tried those outlets and chargers on my Nexus 7 in which it works fine. I've also tried a wireless charger as well to completely rule out it being a charging issue.
I managed to get it back on again and decided to plug it into my PC. I was able to detect it with fastboot devices and then proceeded to completely restore to factory setting using the stock google images assuming the bootloader could be damaged. When I ran the command to flash the updated bootloader it failed. Then again the bootloader was on the screen in which it looked distorted
:~/Android/Nexus 6/shamu-lrx22c$ fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
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) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 6.104s
~/Android/Nexus 6/shamu-lrx22c$ fastboot devices
ZX1G222NKR fastboot
~/Android/Nexus 6/shamu-lrx22c$ fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
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) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 6.105s
:~/Android/Nexus 6/shamu-lrx22c$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
Click to expand...
Click to collapse
This is where I am at now. What I've noticed is that at one point I was able to boot directly into the bootloader using power and volume down and in that the bootloader seems normal. But as of now I am unable to do that.
My next step is to get the phone on again and try to manually boot into bootloader and attempt to flash again.
Any ideas or suggestions or questions?
I hope I'm not speaking out of my butt here... I do remember reading on here that you were actually able to boot the device using the boot image on the pc without actually flashing it. If I read that right, and if I remember correctly, it was fastboot boot.img instead of fastboot flash boot.img.
Hope this helps.
Larzzzz82 said:
I hope I'm not speaking out of my butt here... I do remember reading on here that you were actually able to boot the device using the boot image on the pc without actually flashing it. If I read that right, and if I remember correctly, it was fastboot boot.img instead of fastboot flash boot.img.
Hope this helps.
Click to expand...
Click to collapse
Sounds like something to try but my phone won't power on at all. So I can't even attempt this. I was thinking could the bootloader be damaged? would that cause the phone not to power on?
No clue.
stock or rooted..decrypted..
Fiftysilver said:
Sounds like something to try but my phone won't power on at all. So I can't even attempt this. I was thinking could the bootloader be damaged? would that cause the phone not to power on?
Click to expand...
Click to collapse
Whats the status of your phone before you got into this mess..Are you on stock or custom rom? Most phone doesnt go off like yours unless its an hardware issue.
as was mentioned you can try and boot recovery from RAM basically via the pc, but the device needs to be in fastboot mode first
the command would be fastboot boot recovery_image_name.img
That reboots device with the recovery loaded into RAM. I only tried it with TWRP but assume Stock would do the same....
Another thing to check maybe the fastboot executable as well, I had to update to latest SDK
paztine said:
Whats the status of your phone before you got into this mess..Are you on stock or custom rom? Most phone doesnt go off like yours unless its an hardware issue.
Click to expand...
Click to collapse
The only thing I did with my phone was root it on stock and unlock the bootloader. I was on 5.0.1.
paztine said:
Whats the status of your phone before you got into this mess..Are you on stock or custom rom? Most phone doesnt go off like yours unless its an hardware issue.
Click to expand...
Click to collapse
I'm going to go with it being a hardware issue because now it won't turn on at all anymore. But what I want to figure out is how did it come to that point. I'm thinking a power surge or a defect in the turbo charger. TBH I never trusted that Motorola turbo charger, something about pumping a lot of juice into my phone to charge it quicker screams potential short circuit.
But hopefully I can get the phone replaced via my warranty.. But my bootloader was unlocked so I don't know how well that would go.. But then again the phone can't turn on.
I was trying to follow the steps in this guide - https://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308 - and I got hung up at step #7. After flashing the twrp recovery in fastboot, I could not get it to boot into twrp recovery.
Code:
fastboot boot twrp.img
That returned with
Code:
[email protected]:~/$ sudo fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.069s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.089s
And when I tried to reboot it took me into what I thought was the stock recovery warning me that my device was unlocked and not to be trusted and gave me the options to power off, restart, recovery or fastboot. Fastboot takes me to the fastboot mode. Recovery takes me back to this same screen warning me that it isn't to be trusted. Powering off and restarting either take me back to the warning screen or simply give me a blank screen and the white led on.
I don't know where to go from here. I've downloaded the stock rom but I don't think I can flash that from fastboot and I can't get connect to the phone with adb because I can't boot the phone.
Does anyone have any suggestions? Aside from to stop messing with stuff when I don't fully understand what I'm doing that is...
Thanks for any help!
Jono
Go back to fastboot and try booting the stock recovery. Then choose to update worry ADB sideload. That worked for me, but I'm still having issues with TWRP.
Thanks for the reply! When I try that it just takes me back to the screen that says it can't be trusted because it's unlocked and 5 seconds later if I haven't pushed the volume keys it shows the oneplus logo for a second and then the screen goes blank and the white LED comes on.
solved
Ok, I managed to flash the stock recovery; which I downloaded from oneplus directly. I'm a new user here so it won't let me post a link but they do provide a download for the stock recovery there.
At that point I was able to reboot into recovery, and now I can get it to start up again. Here's what I did in case anyone needs help.
Code:
[email protected]:~/$ sudo fastboot devices
[sudo] password for jono:
bb1c12d3 fastboot
[email protected]:~/$ sudo fastboot flash recovery recovery_OBT7.img
target reported max download size of 442499072 bytes
sending 'recovery' (22237 KB)...
OKAY [ 0.555s]
writing 'recovery'...
OKAY [ 0.171s]
finished. total time: 0.725s
[email protected]:~/$ sudo fastboot boot recovery_OBT7.imgdownloading 'boot.img'...
OKAY [ 0.544s]
booting...
OKAY [ 0.322s]
finished. total time: 0.865s
Hope that helps anyone else. After I did that it rebooted and took me through the whole setup procedure. I'm going to hold off on trying to root this thing for now.
Hello,
My Huawei P10 will not start up. Can boot into fastboot no problems, this is what comes out.
Android reboot reason:
coldboot
NA
volumnkey_down_press_process_func
Tried to flash a recovery into phone to boot upin recovery, however it comes with this error.
fastboot flash recovery twrp_p10_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (24954 KB)...
OKAY [ 0.532s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.539s
When charging the Electric symbol appears with a circle around it and it is in red. Randomly when charging it will turn on by itself and get frozen on the Huawei logo. But it will not turn on at all when not plugged into mains. Trying to turn on when it is plugged in mains only displays charging logo.
Not entirely sure if that is the correct recovery that I should be using, quick google search has given me that result. Would it be possible to flash a stock ROM?
suenoromis said:
Hello,
My Huawei P10 will not start up. Can boot into fastboot no problems, this is what comes out.
Android reboot reason:
coldboot
NA
volumnkey_down_press_process_func
Tried to flash a recovery into phone to boot upin recovery, however it comes with this error.
fastboot flash recovery twrp_p10_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (24954 KB)...
OKAY [ 0.532s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.539s
When charging the Electric symbol appears with a circle around it and it is in red. Randomly when charging it will turn on by itself and get frozen on the Huawei logo. But it will not turn on at all when not plugged into mains. Trying to turn on when it is plugged in mains only displays charging logo.
Not entirely sure if that is the correct recovery that I should be using, quick google search has given me that result. Would it be possible to flash a stock ROM?
Click to expand...
Click to collapse
Bootloader and FRP unlocked (both red on Fastboot screen)?
Test in Fastboot (first command below):
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot getvar vendorcountry
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
Try booting to eRecovery (connect to charger, keep pressing Vol+, then Pow) and Install latest firmware and recovery
zgfg said:
Bootloader and FRP unlocked (both red on Fastboot screen)?
Test in Fastboot (first command below):
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot getvar vendorcountry
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
Try booting to eRecovery (connect to charger, keep pressing Vol+, then Pow) and Install latest firmware and recovery
Click to expand...
Click to collapse
PHONE Locked
FRP Lock
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\adb>fastboot oem get-product-model
...
(bootloader) VTR-L09
OKAY [ 0.005s]
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
vendorcountry: ee/gb
finished. total time: 0.006s
C:\adb>fastboot oem get-build-number
...
(bootloader) :NRD90M test-keys
OKAY [ 0.005s]
finished. total time: 0.005s
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :VTR-L09C652B101
OKAY [ 0.007s]
finished. total time: 0.007s
That is what I get when running your code
Edit: Doing VolUp + Power key with charger does nothing. restarts the charging logo.
charging logo loops when charger is plugged in and doing nothing. Shows charging logo, led notification flashes red 3 times and turns off, turns on again with charging logo, red led flashes 3 times, turns off...
suenoromis said:
PHONE Locked
FRP Lock
Code:
C:\adb>fastboot oem get-bootinfo
(bootloader) locked
OKAY [ 0.001s]
finished. total time: 0.001s
...
Click to expand...
Click to collapse
So Bootloader (and FRP=OEM) locked, you are not allowed to flash anything ;(
zgfg said:
So Bootloader (and FRP=OEM) locked, you are not allowed to flash anything ;(
Click to expand...
Click to collapse
Phone = Dead
?
suenoromis said:
Phone = Dead
?
Click to expand...
Click to collapse
You can try flashing by Testpoints - need to open cover and short-wire the pins.
Never played with, here is some guide for P10
https://forum.xda-developers.com/mate-9/help/solution-19-00-fix-hardbricked-huawei-t3750315
You can also ask for paid help from (discuss before you buy credits):
https://ministryofsolutions.com/paid-services/amp
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://chimeratool.com/
https://funkyhuawei.club/