Hi guys, I have an Honour 4C wich reading through forums i managed to update it to most recent AOKP 7.1.2 version (https://forum.xda-developers.com/p8lite/development/rom-t3717536) for P8Lite Alice and everything was ok.
I can recall some years ago I had to change my model from CHC-U01 to CMH-U01 to update to 6.0 if my memory is right and recently flashed P8 Lite firmware (B896) in order to flash AOKP and device was running without problems.
I was running my phone in performance governor for gaming , forgot turn it off, My phone complety run out of battery while asleep i woke up put it to charge.
It charged a little and after it powered on by itself bootlooping into OS.
I'm now facing a bootloop, phone auto turns on when charging and bootloops.
If I enter fastboot and exit into a shutdown its stays charging ok. (Just to turn on by itself at some point)
PC detects fastboot just fine and I can fastboot, however, no matter what I Flash i can't get sytem to boot up properly NOR can i boot TWRP recovery.
I flash twrp into recovery, IT says it was flashed OK but when i boot into recovery it just open that EMUI menu with reboot into system , wipe cache/ and system restore (wich takes 1sec , says system restored but it doesnt).
I've tried to flash B896_Update.zip used HuaweiUpdateExtractor and flashed BOOT RECOVERY AND SYSTEM OK , but again, no changes... it boots into AOKP Logo when it should boot into Huawei logo if any changes took efect.
If boot into fastboot and press KeyvolumeUP, other eRecovery EMUI appears now with restart , wifi update and shutdown.
When I try this Wifi method it bootloops right after it says connecting..
Also I can't do a fastboot erase (cache...userdata..any) because it gives FAILED (remote: Command not allowed) ... my bootloader is UNLOCKED and command prompt is running in administrator mode.
Same happens if i try to run fastboot boot twrp_Recovery.img , download OK but FAILED remote: Command not allowed.
I have no way to do an ADB sideload and try to go from that because system doesnt boot.
Is it just HardBricked even so I can boot into bootloader and fastboot?
It is driving me crazy it feels like fastboot just "fake flashes" or something . Nothing takes effect ....
Related
The other day my WiFi Xoom stopped getting past the "Motorola Dual Core" screen.
I have removed the SD card.
Android recovery mode gives me the error android with the "!"
It does this plugged in or on battery.
Not rooted.
What else should I try?
neoka said:
The other day my WiFi Xoom stopped getting past the "Motorola Dual Core" screen.
I have removed the SD card.
Android recovery mode gives me the error android with the "!"
It does this plugged in or on battery.
Not rooted.
What else should I try?
Click to expand...
Click to collapse
What were you trying to do before this hapened? Need more info to be able to help.
24348542 26
DavilaDarkness said:
What were you trying to do before this hapened? Need more info to be able to help.
Click to expand...
Click to collapse
Hadn't really done anything. Just normal use. No out of the ordinary installs. Turned it off. Next day I tried turning it on and it won't boot.
Did you ever resolve this ?? I was give one to repair for a child and it too is stuck on the red boot screen. The good thing is the person who sold it to them was a hacker and put TWRP on it of all things. I was floored when I tried to enter recovery and found teamwin.
but the problem is its still stuck on the boot screen, i did flash it 3-4 times with M604 M602 flashes and some other customs but nothing works, it completes flashing and wiping caches but always goes back to stuck on boot screen..
perhaps I have to unclock the bootloader or something for the flash to be succesfull ?
Just wanted to say I fixed it with these commands and firmware if anyone is interested. I tried everything else including flashing with twrp and wiping all caches and it didn't work, getting the stock firmware and doing it like this worked to clear boot screen endless stuck
download fastboot and adb and xoom drivers 6.4 (about 5mb) and the appropriate stock firmware. for me it was ZM604
at the command type
adb reboot bootloader
you may need to unplug and replug cable after it goes in fastboot mode.
fastboot devices
.. should return something "02a439cj0skjdke fastboot" to proceed.
fastboot oem unlock
.. look at your tablet and follow the instructions, for me it was down twice and up once to accept unlock conditions, then it reboots
on reboot press vol down 2 seconds after you see moto logo, it will enter fastboot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
no need to relock after, you will see android logo and first boot pop up after 2-3 mins
Hi there,
Yesterday I decided to upgrade from 5.1.1 (Sultan unofficial) to 6.0.1 (Sultan unofficial). :good:
Sh*t went down because I was running TWRP 2.8.6.1 and OP stated you must run 2.8.6.0.
So I got stuck into bootloot, hence I booted into recovery, put image of 2.8.6.0 into my phone and then flashed the img file through the appropriate menu.
Sh*t went down once again (And I'm not sure of why, but maybe because you cannot downgrade that way). Now I have a messed up recovery.
Well then, I get into fastboot, use Wugfresh's one-click-tool to flash back to 5.1.1. Everything goes well : my phone boots up :good:.
I disable update recovery with system updates in developers options (even though I am aware that this switch doesn't work on Lollipop)
Then I decide to root again and install TWRP 2.8.6.0 and the process fails : not that I get errors, but the command :
fastboot boot recovery.img
isn't doing its thing, hence I never boot into recovery
I'm quite surprised, but well I try to flash recovery :
fastboot flash recovery twrp-2.8.6.0.img
command executes without errors
I reboot into cm, try to boot into recovery and :
"Surprise Motherf*cker !" CM recovery shows.
I read that I must clear cache before (or after) flashing recovery
fastboot erase cache
Then shut the phone down holding Vol-down and power buttons and then boot into recovery holding Vol-down once again.
No luck, this time, every time I try to boot into recovery with this method, 1+ logo shows, phone vibrates, and 1+ logo shows etc. indefinitely
I abandoned... flashed 4.4.4 used wugfresh tool to root and flash twrp, then flashed marshmallow
Now I am rooted and running Marshmallow, but TWRP has been erased... Tried to flash through Flashify and Rashr, no luck.
(I disabled update cm recovery under developer settings)
Does someone understand why I don't manage to get TWRP under Android 5 and 6, and could explain me why ? :fingers-crossed:
Thank you !
debilausaure said:
Hi there,
Yesterday I decided to upgrade from 5.1.1 (Sultan unofficial) to 6.0.1 (Sultan unofficial). :good:
Sh*t went down because I was running TWRP 2.8.6.1 and OP stated you must run 2.8.6.0.
So I got stuck into bootloot, hence I booted into recovery, put image of 2.8.6.0 into my phone and then flashed the img file through the appropriate menu.
Sh*t went down once again (And I'm not sure of why, but maybe because you cannot downgrade that way). Now I have a messed up recovery.
Well then, I get into fastboot, use Wugfresh's one-click-tool to flash back to 5.1.1. Everything goes well : my phone boots up :good:.
I disable update recovery with system updates in developers options (even though I am aware that this switch doesn't work on Lollipop)
Then I decide to root again and install TWRP 2.8.6.0 and the process fails : not that I get errors, but the command :
fastboot boot recovery.img
isn't doing its thing, hence I never boot into recovery
I'm quite surprised, but well I try to flash recovery :
fastboot flash recovery twrp-2.8.6.0.img
command executes without errors
I reboot into cm, try to boot into recovery and :
"Surprise Motherf*cker !" CM recovery shows.
I read that I must clear cache before (or after) flashing recovery
fastboot erase cache
Then shut the phone down holding Vol-down and power buttons and then boot into recovery holding Vol-down once again.
No luck, this time, every time I try to boot into recovery with this method, 1+ logo shows, phone vibrates, and 1+ logo shows etc. indefinitely
I abandoned... flashed 4.4.4 used wugfresh tool to root and flash twrp, then flashed marshmallow
Now I am rooted and running Marshmallow, but TWRP has been erased... Tried to flash through Flashify and Rashr, no luck.
(I disabled update cm recovery under developer settings)
Does someone understand why I don't manage to get TWRP under Android 5 and 6, and could explain me why ? :fingers-crossed:
Thank you !
Click to expand...
Click to collapse
Normally when you flash TWRP via fastboot, if you boot to the OS it will replace your recovery so the workaround is to flash recovery via fastboot. Turn off phone via long pressing power button then volume down + power button and you should have TWRP. That's how I've always done it
Sent from my A0001 using Tapatalk
Renosh said:
Normally when you flash TWRP via fastboot, if you boot to the OS it will replace your recovery so the workaround is to flash recovery via fastboot. Turn off phone via long pressing power button then volume down + power button and you should have TWRP. That's how I've always done it
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thank you for your answer
As I mentionned, I have already tried the method you described, I just ran through the process again to confirm you this isn't working
The commands I used :
Code:
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery twrp-2.8.6.0-bacon.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10180 KB)...
OKAY [ 0.313s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.469s
Then I unplug my phone, then long press power button, and when the phone is off I press power button + volume down
With this process 1+ logo shows up for 7~8 secs, then the phone vibrates and the screen goes dark, and then the 1+ logo shows up again indefinitely like there's no recovery to be found...
If I release vol-down, phone ends up booting system
Hello,
as the title says... I bricked my phone. In the past, I successfully installed LineageOS on my old Galaxy S3. I got a used Huawei P9 Lite recently and wanted to install a custom ROM. Here's what happened:
1. Unlocked the phone
2. Accessed Fastboot mode
3. Installed TWRP* via fastboot flash recovery file.img
4. This didn't work and I read on the web, I could try to flash revocery2 with fastboot flash recovery2 file.img
5. This didn't help either, so I decided to cancel my plan and use the manufactorer's system since the system still booted (of course, I didn't install any custom OS).
6. The phone told me on each startup it's unlocked. I didn't need the unlock anymore, so I accessed the Fastboot mode again.
7. I re-locked the system by using fastboot oem relock password.
8. The phone asked me to do confirm this action and do a factory reset
9. After this, I'm stuck at the Huawei logo and can't access Fastboot mode anymore!
When I shut down the phone, it immediately restarts itself. No chance to get into Fastboot mode again, which I did through pressing Vol- and plugging in an USB cable.
*I tried several versions, 3.0.1 and 3.2.1 since no version worked
This may be a beginner's fault, my last phone was already unlocked and I had not a single problem back then. But this time... I hope you can help me.
What would happen if I let drain the battery down to 0% - the phone wouldn't restart of course. If I press Vol- and plug it in, would I come back to Fastboot mode or would it stay in this loop?
Any help is appreciated!
Hey guys, I'm new to this board bc I can solve my problems mostly on my own but this time... I have no clue what I'm supposed to do.
I tried using ADB and Fastboot to flash TWRP and everything worked fine. When I rebooted my phone I couldn't get into recovery and I was trying different commands to access recovery but I got "command not allowed".
Then, by accident, I typed:
-fastboot flash boot twrp.img
and since then I'm unable to boot my phone (bootloop), can't reach recovery and I have no idea what to do.
I'm always stuck in the "Your device is booting now..." screen for a few minutes, then my phone just reboots.
Hi guys, I have an Honour 4C wich reading through forums i managed to update it to most recent AOKP 7.1.2 version (https://forum.xda-developers.com/p8l...t/rom-t3717536) for P8Lite Alice and everything was ok.
I can recall some years ago I had to change my model from CHC-U01 to CMH-U01 to update to 6.0 if my memory is right and recently flashed P8 Lite firmware (B896) in order to flash AOKP and device was running without problems.
I was running my phone in performance governor for gaming , forgot turn it off, My phone complety run out of battery while asleep i woke up put it to charge.
It charged a little and after it powered on by itself bootlooping into OS.
I'm now facing a bootloop, phone auto turns on when charging and bootloops.
If I enter fastboot and exit into a shutdown its stays charging ok. (Just to turn on by itself at some point)
PC detects fastboot just fine and I can fastboot, however, no matter what I Flash i can't get sytem to boot up properly NOR can i boot TWRP recovery.
I flash twrp into recovery, IT says it was flashed OK but when i boot into recovery it just open that EMUI menu with reboot into system , wipe cache/ and system restore (wich takes 1sec , says system restored but it doesnt).
I've tried to flash B896_Update.zip used HuaweiUpdateExtractor and flashed BOOT RECOVERY AND SYSTEM OK , but again, no changes... it boots into AOKP Logo when it should boot into Huawei logo if any changes took efect.
If boot into fastboot and press KeyvolumeUP, other eRecovery EMUI appears now with restart , wifi update and shutdown.
When I try this Wifi method it bootloops right after it says connecting..
Also I can't do a fastboot erase (cache...userdata..any) because it gives FAILED (remote: Command not allowed) ... my bootloader is UNLOCKED and command prompt is running in administrator mode.
Same happens if i try to run fastboot boot twrp_Recovery.img , download OK but FAILED remote: Command not allowed.
I have no way to do an ADB sideload and try to go from that because system doesnt boot.
Is it just HardBricked even so I can boot into bootloader and fastboot?
It is driving me crazy it feels like fastboot just "fake flashes" or something . Nothing takes effect ....
Hi Korreya,
Once I to had ended up in a boot loop when I had messed up during twrp (that was 1st time I had tried flashing it into a phone).
I eventually tried many methods, few of which you have also mentioned, and finally succeeded but I exactly don't remember what I had did so I'm not sure if this works.
Download the stock Honor4C ROM (I'm not able to post the link so you could just Google it) and copy the file named UPDATE.APP into a folder named "dload" (without the " , if there's no such folder just create one) on your SD card and then try going into the eRecovery EMUI and updating the system.
PS: Note that this would install the official stock ROM on the device.
Try it and do let me know if that helps.
Peace