Related
Hey guys,
I have encountered a serious problem on my device. Today I rebooted my phone once and it has just stuck on the samsung logo. Then the phone began to reboot without ending....It could not just start. With the help of TWRP I have made a full wipe and tried to reinstall my actual firmware Superman 1.10.5, but I always stuck at 25%, the phone did not respond to any actions. I even tried to flash the stock 4-file firmware with Odin, but it did not help, the phone constantly reboots. Sometimes it manages to boot to the stage where the sign "installation of applications" appears, but a while later it stucks again and reboots. Please, help me to solve the issue, because I am begininng to think that it would be unpossible to recover the phone. I am only able to enter the download mode or recovery, anything else does not work.
Thanks....
AuroraLX said:
Hey guys,
I have encountered a serious problem on my device. Today I rebooted my phone once and it has just stuck on the samsung logo. Then the phone began to reboot without ending....It could not just start. With the help of TWRP I have made a full wipe and tried to reinstall my actual firmware Superman 1.10.5, but I always stuck at 25%, the phone did not respond to any actions. I even tried to flash the stock 4-file firmware with Odin, but it did not help, the phone constantly reboots. Sometimes it manages to boot to the stage where the sign "installation of applications" appears, but a while later it stucks again and reboots. Please, help me to solve the issue, because I am begininng to think that it would be unpossible to recover the phone. I am only able to enter the download mode or recovery, anything else does not work.
Thanks....
Click to expand...
Click to collapse
Really sad to hear that story mate. First things first, I assume your BL version is matching with the firmware your flashing right. And when you go to TWRP, can you see /system and /data partition from the mount menu? If not, you have to perform a factory reset. I had issue like that with my Galaxy S7 and usually factory reset(not wiping) helped me with that situation. Since your system can boot up, but crashes after awhile, I do suspect that some of your partition might be corrupted(at least its what happened to me). So trying factory reset can be a good bet for you.
And... I think you have to provide more information with which variant you are using, and your BL version, TWRP version too, solve the problem quicker. Hope this information helps.
CenteaOSD said:
Really sad to hear that story mate. First things first, I assume your BL version is matching with the firmware your flashing right. And when you go to TWRP, can you see /system and /data partition from the mount menu? If not, you have to perform a factory reset. I had issue like that with my Galaxy S7 and usually factory reset(not wiping) helped me with that situation. Since your system can boot up, but crashes after awhile, I do suspect that some of your partition might be corrupted(at least its what happened to me). So trying factory reset can be a good bet for you.
And... I think you have to provide more information with which variant you are using, and your BL version, TWRP version too, solve the problem quicker. Hope this information helps.
Click to expand...
Click to collapse
Yep, you are right, BL versions always matched firmwares. I tried to wipe the phone with TWRP 3.0.2.3 and also to make a factory reset with the stock recovery. The stock firmware, which I tried to flash, was G930FXXU1BPH6_G930FOXE1BPH1_SER consisting of 4 files including BL,AP,CP and CSC. After 3rd or 4th flash of the same stock firmware the phone suddenly became alive and began to boot. Wu-huuu:silly: I was happy as a child. After having successfully launched the stock rom I have again flashed TWRP 3.0.2.3, went to "wipe" option and formatted data. Then I have installed a Superman Rom 1.12 and everything went the right way. I don't understand only one thing: why after having wiped the phone several times and having reseted it through the stock as well as TWRP recovery it didn't want to boot.
As you said, I suppose that the one of partitions was corrupted. Oh damn, I thought that I won't be able to resuscitate this phone.
I have flashed about 20 phones during my life, but I have never ever encountered such serious problems.
my honor 8 is stuck on honor 8 blue screen, cant turn it off.
cant access fastboot, recovery or even dload. only vibrates twice.
can anyone help me to solve this issue???
abbassbhai said:
my honor 8 is stuck on honor 8 blue screen, cant turn it off.
cant access fastboot, recovery or even dload. only vibrates twice.
can anyone help me to solve this issue???
Click to expand...
Click to collapse
Have you tried to flash custom ROMs or TWRP?
overcustom said:
Have you tried to flash custom ROMs or TWRP?
Click to expand...
Click to collapse
i was trying to dload mm firmware. The firmware dloaded fine but after factory reset and reboot, the fone is jus staying on honor screen after 3d text. i tried to go in erecovery but cannot, fone jus vibrates twice and then after 3d honor text, it stays on blue honor screen forever.
i tried to boot in fastboot as well as dload.....same thing happend not booting in fastboot or dload.
only 3d text and blue screen.
now fone doesnt even turns on if power button pressed ,but juss vibrates twice and blue screen after 3d text.
Leave your device as it is so that the battery is fully drained and is powered off. Then plug your device to charger for 5 minutes. Unplug it and now try to boot to recovery.
Hold the power button and volume up button until you hear the first vibration and screen goes on. Leave both buttons. Now you can go to recovery. Perform a full factory reset. Then power off your device and move the dload package to your external SD card. Repeat the same process but this time hold both volume buttons and power button.
hackslash said:
Leave your device as it is so that the battery is fully drained and is powered off. Then plug your device to charger for 5 minutes. Unplug it and now try to boot to recovery.
Hold the power button and volume up button until you hear the first vibration and screen goes on. Leave both buttons. Now you can go to recovery. Perform a full factory reset. Then power off your device and move the dload package to your external SD card. Repeat the same process but this time hold both volume buttons and power button.
Click to expand...
Click to collapse
thankyou bro for ur suggestion...i already tried all tht but no luck.
the fone turns on everytime whatever i try to do....only 3d text and it is stuck on blue honor screen.
no recovery dload fastboot etc.
Hi. Sorry the revive.
Could you solve this? I'm in the same situation
No unlock, can't enter to recovery, can't enter to erecovery so I can't flash with dload, fastboot is a joke if the phone has locked bootloader so I can't reflash the recoveries.
abbassbhai said:
my honor 8 is stuck on honor 8 blue screen, cant turn it off.
cant access fastboot, recovery or even dload. only vibrates twice.
can anyone help me to solve this issue???
Click to expand...
Click to collapse
Noivern said:
Hi everyone!
First, sorry reviving the threadm but this one is similar to my trouble.
Second, every flash process was done with dload method and vol + - and power combination.
Third, I never unlock my phone before or flashed any custom rom or recovery, everything was stock.
Last night, I tried to rollback my honor 8 frd-al19 to emui 6.0 with proper rollback package and firmware for Android 6.0 (both official and for my model), but phone went into boot lock. It isn't boot loop, It's stuck on the Honor blue logo. I can't even turn off the phone.
I did this procedure once before with success. I was on fdr-al19c432b360 firmware 100% functional (I was an idiot to rollback again when not needed at all... I know). I applied the rollback package correctly, and then I did a mistake and flashed full c636b131 Android 6.0 firmware instead of c432b131 Android 6.0.
Phone started ok with everything working. But I noticed my bad (emui didn't find any update package from OTA, and noticed the error in version model shown) and reflashed rollback package... At this point is where I think I messed up the recoveries or something. When ended the flashing process, I copied the correct firmware (the c432b131 android 6) on dload folder and tried again to flash.... but this time phone never entered on erecovery nor recovery. Only thing I get is stuck honor blue screen. It refuses to enter on recovery or erecovery. It just reboots, vibrate twice and keeps stuck after that on honor screen.
Strange thing, is that I did this procedure once before some months ago with success, but that time I didn't make the mistake with the versions.
After panic, I tried to boot in fastboot connected to my pc, and HiSuite knows there is something connected, because it launches it self, but don't recognize the phone and says it can't be recovered. Also, Adb don't see the phone either, only fastboot.
With fastboot commands I tried to reboot into recovery and nothing happened. Then wipe cache/user data, reflash stock recovery. Everything failed with message "remote: not allowed". And of course, because I never unlocked my bootloader. Fastboot says phone locked, frp locked (was frp, don't remember now exactly).
Then, I read about to let the battery die. I did. That didn't work either, phone keeps stuck on honor blue logo.
I downloaded multitool for huawei software, and everything requires an unlocked bootloader to recover.
Then, I tried to get unlock code, but huawei site ask me product id which I can't get because phone is bricked (I have all other data, imei, serial, etc.) . Tried with id generator too, and nothing what I tried have work so far. It's frustrating.
I'm pretty hopeless now, no unlock, no recovery, no erecovery, so I can't flash anything on the damn phone to try to recover it.
Can I save my phone or is it just an expensive brick? Any help will be REALLY welcome.
:crying:
Click to expand...
Click to collapse
Well, is a bit silly to answer yourself but this can help someone else:
I did purchase a license of 3 days of dc phoenix software and force updated version android 6.0 c432B131 on my honor 8 fdr L19.
It flashed ok, but software said that couldn't install update. On phone went to 99% for long time (more than 1 hour).
So I looking for some info, and also the software said that I had to manually update. I just copied the same rom with dload method: just the same UPDATE.APP on the folder, and tried the 3 buttons: It worked!
After a success bootup, it found inmediatelly (OTA) the update to android 7, c432b360 firmware and downloaded and installed.
Here went something strange: after updated again via OTA, everything was working ok, but on about phone, the version shown wasn't the c432b360. Instead it said something about test keys build. Just for being safe, I tried to full reset the phone and... it failed. It said failed on erecovery menu, and after that, the next boot up I couldn't pass over wifi setting menu: keyboard was missing and it just tried to talk to text input. Another panic moment, so I tried to enter on recovery to clear cache and reset user with no luck. After that, phone refused to start showing an error message on fastboot screen: "phone couldn't pass verification, it may not function properly".
What to do? just do all the things again, but just with dload method. As I was on android 7, first I installed downgrade package. Ok, it did well. After, installed again c432b131 (android 6). And finally success!.
Once again, phone ask for install OTA android 7 and I let it. Now, I just didn't tried to do a factory reset and so far is ok.... but it hasn't AOSP Android keyboard anymore. So far is working ok, everything is working: wifi, phone, 4g mobile internet, nfc, sensors, apps, gps, compass... so I'm pretty happy now, but not sure what happened when I tried to factory reset and what happened to AOSP Android keyboard.
Noivern said:
Well, is a bit silly to answer yourself but this can help someone else:
I did purchase a license of 3 days of dc phoenix software and force updated version android 6.0 c432B131 on my honor 8 fdr L19.
It flashed ok, but software said that couldn't install update. On phone went to 99% for long time (more than 1 hour).
So I looking for some info, and also the software said that I had to manually update. I just copied the same rom with dload method: just the same UPDATE.APP on the folder, and tried the 3 buttons: It worked!
After a success bootup, it found inmediatelly (OTA) the update to android 7, c432b360 firmware and downloaded and installed.
Here went something strange: after updated again via OTA, everything was working ok, but on about phone, the version shown wasn't the c432b360. Instead it said something about test keys build. Just for being safe, I tried to full reset the phone and... it failed. It said failed on erecovery menu, and after that, the next boot up I couldn't pass over wifi setting menu: keyboard was missing and it just tried to talk to text input. Another panic moment, so I tried to enter on recovery to clear cache and reset user with no luck. After that, phone refused to start showing an error message on fastboot screen: "phone couldn't pass verification, it may not function properly".
What to do? just do all the things again, but just with dload method. As I was on android 7, first I installed downgrade package. Ok, it did well. After, installed again c432b131 (android 6). And finally success!.
Once again, phone ask for install OTA android 7 and I let it. Now, I just didn't tried to do a factory reset and so far is ok.... but it hasn't AOSP Android keyboard anymore. So far is working ok, everything is working: wifi, phone, 4g mobile internet, nfc, sensors, apps, gps, compass... so I'm pretty happy now, but not sure what happened when I tried to factory reset and what happened to AOSP Android keyboard.
Click to expand...
Click to collapse
A late answer but maybe useful for some
Because the OTA showed up, was not a full OTA file. I guess it was only 1.3 gb something. It was a test build and didnt have any apks inside including the keyboard. And also not a stable one (test build) So it is always better to download FULL package from the menu and flash that one.
Hey,
I need some help with this problem. I have a frd lo4 on nougat. I tried to return to stock from being rooted. The dLoad folder method wasn’t working (returned invalid package) so I unrooted via the SU app, flashed stock recovery, and went into fastboot and relocked the bootloader with the code.
Now it won’t boot or shut off. Just a bootloop showing the blue screen. I could use to access fastboot before but now my pc doesn’t detect my phone. I’ve tried different ports and pc’s. I can’t access recovery either.
Any help is appreciated
EDIT: I let the battery die, then tried going into fastboot mode and it worked. I flashed the stock recovery 1 and 2. I then used the correct rollback package and put it on my sd card then flashed. I then downloaded the full 6.0 firmware and did the same. Now I’m unrooted, locked bootloader, and stock.
Hope this helps someone.
Excatly the same thing happened to me 1 week ago.. My phone was going on bott loop in recovery mode.. I tried Dload method and recovery but nothing happened.. atlast i let the battery die. After the battery is completly dead i connexted the charger and hola the adb is working now. Then i flashed correct recovery and rom. Ecerything is working fine now.
Hi everyone!
First, sorry reviving the threadm but this one is similar to my trouble.
Second, every flash process was done with dload method and vol + - and power combination.
Third, I never unlock my phone before or flashed any custom rom or recovery, everything was stock.
Last night, I tried to rollback my honor 8 frd-al19 to emui 6.0 with proper rollback package and firmware for Android 6.0 (both official and for my model), but phone went into boot lock. It isn't boot loop, It's stuck on the Honor blue logo. I can't even turn off the phone.
I did this procedure once before with success. I was on fdr-al19c432b360 firmware 100% functional (I was an idiot to rollback again when not needed at all... I know). I applied the rollback package correctly, and then I did a mistake and flashed full c636b131 Android 6.0 firmware instead of c432b131 Android 6.0.
Phone started ok with everything working. But I noticed my bad (emui didn't find any update package from OTA, and noticed the error in version model shown) and reflashed rollback package... At this point is where I think I messed up the recoveries or something. When ended the flashing process, I copied the correct firmware (the c432b131 android 6) on dload folder and tried again to flash.... but this time phone never entered on erecovery nor recovery. Only thing I get is stuck honor blue screen. It refuses to enter on recovery or erecovery. It just reboots, vibrate twice and keeps stuck after that on honor screen.
Strange thing, is that I did this procedure once before some months ago with success, but that time I didn't make the mistake with the versions.
After panic, I tried to boot in fastboot connected to my pc, and HiSuite knows there is something connected, because it launches it self, but don't recognize the phone and says it can't be recovered. Also, Adb don't see the phone either, only fastboot.
With fastboot commands I tried to reboot into recovery and nothing happened. Then wipe cache/user data, reflash stock recovery. Everything failed with message "remote: not allowed". And of course, because I never unlocked my bootloader. Fastboot says phone locked, frp locked (was frp, don't remember now exactly).
Then, I read about to let the battery die. I did. That didn't work either, phone keeps stuck on honor blue logo.
I downloaded multitool for huawei software, and everything requires an unlocked bootloader to recover.
Then, I tried to get unlock code, but huawei site ask me product id which I can't get because phone is bricked (I have all other data, imei, serial, etc.) . Tried with id generator too, and nothing what I tried have work so far. It's frustrating.
I'm pretty hopeless now, no unlock, no recovery, no erecovery, so I can't flash anything on the damn phone to try to recover it.
Can I save my phone or is it just an expensive brick? Any help will be REALLY welcome.
:crying:
Noivern said:
Hi everyone!
First, sorry reviving the threadm but this one is similar to my trouble.
Second, every flash process was done with dload method and vol + - and power combination.
Third, I never unlock my phone before or flashed any custom rom or recovery, everything was stock.
Last night, I tried to rollback my honor 8 frd-al19 to emui 6.0 with proper rollback package and firmware for Android 6.0 (both official and for my model), but phone went into boot lock. It isn't boot loop, It's stuck on the Honor blue logo. I can't even turn off the phone.
I did this procedure once before with success. I was on fdr-al19c432b360 firmware 100% functional (I was an idiot to rollback again when not needed at all... I know). I applied the rollback package correctly, and then I did a mistake and flashed full c636b131 Android 6.0 firmware instead of c432b131 Android 6.0.
Phone started ok with everything working. But I noticed my bad (emui didn't find any update package from OTA, and noticed the error in version model shown) and reflashed rollback package... At this point is where I think I messed up the recoveries or something. When ended the flashing process, I copied the correct firmware (the c432b131 android 6) on dload folder and tried again to flash.... but this time phone never entered on erecovery nor recovery. Only thing I get is stuck honor blue screen. It refuses to enter on recovery or erecovery. It just reboots, vibrate twice and keeps stuck after that on honor screen.
Strange thing, is that I did this procedure once before some months ago with success, but that time I didn't make the mistake with the versions.
After panic, I tried to boot in fastboot connected to my pc, and HiSuite knows there is something connected, because it launches it self, but don't recognize the phone and says it can't be recovered. Also, Adb don't see the phone either, only fastboot.
With fastboot commands I tried to reboot into recovery and nothing happened. Then wipe cache/user data, reflash stock recovery. Everything failed with message "remote: not allowed". And of course, because I never unlocked my bootloader. Fastboot says phone locked, frp locked (was frp, don't remember now exactly).
Then, I read about to let the battery die. I did. That didn't work either, phone keeps stuck on honor blue logo.
I downloaded multitool for huawei software, and everything requires an unlocked bootloader to recover.
Then, I tried to get unlock code, but huawei site ask me product id which I can't get because phone is bricked (I have all other data, imei, serial, etc.) . Tried with id generator too, and nothing what I tried have work so far. It's frustrating.
I'm pretty hopeless now, no unlock, no recovery, no erecovery, so I can't flash anything on the damn phone to try to recover it.
Can I save my phone or is it just an expensive brick? Any help will be REALLY welcome.
:crying:
Click to expand...
Click to collapse
Well, is a bit silly to answer yourself but this can help someone else:
I did purchase a license of 3 days of dc phoenix software and force updated version android 6.0 c432B131 on my honor 8 fdr L19.
It flashed ok, but software said that couldn't install update. On phone went to 99% for long time (more than 1 hour).
So I looking for some info, and also the software said that I had to manually update. I just copied the same rom with dload method: just the same UPDATE.APP on the folder, and tried the 3 buttons: It worked!
After a success bootup, it found inmediatelly (OTA) the update to android 7, c432b360 firmware and downloaded and installed.
Here went something strange: after updated again via OTA, everything was working ok, but on about phone, the version shown wasn't the c432b360. Instead it said something about test keys build. Just for being safe, I tried to full reset the phone and... it failed. It said failed on erecovery menu, and after that, the next boot up I couldn't pass over wifi setting menu: keyboard was missing and it just tried to talk to text input. Another panic moment, so I tried to enter on recovery to clear cache and reset user with no luck. After that, phone refused to start showing an error message on fastboot screen: "phone couldn't pass verification, it may not function properly".
What to do? just do all the things again, but just with dload method. As I was on android 7, first I installed downgrade package. Ok, it did well. After, installed again c432b131 (android 6). And finally success!.
Once again, phone ask for install OTA android 7 and I let it. Now, I just didn't tried to do a factory reset and so far is ok.... but it hasn't AOSP Android keyboard anymore. So far is working ok, everything is working: wifi, phone, 4g mobile internet, nfc, sensors, apps, gps, compass... so I'm pretty happy now, but not sure what happened when I tried to factory reset and what happened to AOSP Android keyboard.
Noivern said:
Hi everyone!
First, sorry reviving the threadm but this one is similar to my trouble.
Second, every flash process was done with dload method and vol + - and power combination.
Third, I never unlock my phone before or flashed any custom rom or recovery, everything was stock.
Last night, I tried to rollback my honor 8 frd-al19 to emui 6.0 with proper rollback package and firmware for Android 6.0 (both official and for my model), but phone went into boot lock. It isn't boot loop, It's stuck on the Honor blue logo. I can't even turn off the phone.
I did this procedure once before with success. I was on fdr-al19c432b360 firmware 100% functional (I was an idiot to rollback again when not needed at all... I know). I applied the rollback package correctly, and then I did a mistake and flashed full c636b131 Android 6.0 firmware instead of c432b131 Android 6.0.
Phone started ok with everything working. But I noticed my bad (emui didn't find any update package from OTA, and noticed the error in version model shown) and reflashed rollback package... At this point is where I think I messed up the recoveries or something. When ended the flashing process, I copied the correct firmware (the c432b131 android 6) on dload folder and tried again to flash.... but this time phone never entered on erecovery nor recovery. Only thing I get is stuck honor blue screen. It refuses to enter on recovery or erecovery. It just reboots, vibrate twice and keeps stuck after that on honor screen.
Strange thing, is that I did this procedure once before some months ago with success, but that time I didn't make the mistake with the versions.
After panic, I tried to boot in fastboot connected to my pc, and HiSuite knows there is something connected, because it launches it self, but don't recognize the phone and says it can't be recovered. Also, Adb don't see the phone either, only fastboot.
With fastboot commands I tried to reboot into recovery and nothing happened. Then wipe cache/user data, reflash stock recovery. Everything failed with message "remote: not allowed". And of course, because I never unlocked my bootloader. Fastboot says phone locked, frp locked (was frp, don't remember now exactly).
Then, I read about to let the battery die. I did. That didn't work either, phone keeps stuck on honor blue logo.
I downloaded multitool for huawei software, and everything requires an unlocked bootloader to recover.
Then, I tried to get unlock code, but huawei site ask me product id which I can't get because phone is bricked (I have all other data, imei, serial, etc.) . Tried with id generator too, and nothing what I tried have work so far. It's frustrating.
I'm pretty hopeless now, no unlock, no recovery, no erecovery, so I can't flash anything on the damn phone to try to recover it.
Can I save my phone or is it just an expensive brick? Any help will be REALLY welcome.
:crying:
Click to expand...
Click to collapse
did u solve this bro. Same here happened, no recover no erecovery but just fastboot mode working. I let the battery died but cant charge it now, charging light is just blinking.. I have unlocked bootloader..
Well, I have this device with problems a few weeks ago, it was working normally, then it unloaded and hung up, when I put it to load it took a while to connect, but after a few minutes it turned on but in infinite loop ... So I thought I burned the room stock, I did that, and it installed everything right, but it did not change anything, it installed the TWRP 2.7, I tried to make the wipe and burn others room, but it did not continue the same way. I tried fastboot, rsd lite, sdcard, and everything and nothing. I tried to install a new version of TWRP, it says it installed everything right too, but when it opens it continues in the same version. When trying to make the wipe dalvik cache the error.
In short ... I install the rooms normally and nothing happens, the same with other recovery.
I think I lost the device forever, please help me.
Sorry, I'm using the translator. Thanks for reading this far.
marcosjord said:
Well, I have this device with problems a few weeks ago, it was working normally, then it unloaded and hung up, when I put it to load it took a while to connect, but after a few minutes it turned on but in infinite loop ... So I thought I burned the room stock, I did that, and it installed everything right, but it did not change anything, it installed the TWRP 2.7, I tried to make the wipe and burn others room, but it did not continue the same way. I tried fastboot, rsd lite, sdcard, and everything and nothing. I tried to install a new version of TWRP, it says it installed everything right too, but when it opens it continues in the same version. When trying to make the wipe dalvik cache the error.
In short ... I install the rooms normally and nothing happens, the same with other recovery.
I think I lost the device forever, please help me.
Sorry, I'm using the translator. Thanks for reading this far.
Click to expand...
Click to collapse
Can you put a better explanation and say what rom you were using and some more info would be nice. Also was your bootloader unlocked when you flashed TWRP.
(my phone is huawei gr5 2017 but didnt find the forum and figured out honor 6x is the same name)
Hello, i unlocked my bootloader and made a mistake flashing the trwp recovery into my boot image didnt know what to do for a day, obviously i kept factory resetting from twrp hoping to fix it, later on i found a boot img for my nuild number here on xda and it worked but now whenever i try to uninstall an app my phone restarts, when i try to make a pin or a fingerptint the settings keeps on crashing and developer options also crash when i try to open it any fixes please would be really helpfull
my Build number is: BLL-L21C185B386.
Uptade: i solved it and heres how if anyone have the same problem, I relocked the bootloader then booted my phone, it booted into my stock recovery and said that data partions are severly damaged and i have to format it so i did then it made me download of what i think is the stock firmware after download and installation it booted into the system with no problems fingerprints and pins are working like before.