Mate 9 keeps restarting until reach eRecovery mode - Huawei Mate 9 Questions & Answers

Mate 9 keeps restarting
Showing HUAWEI logo, restarts several times then entering eRecovery ( I believe after update or automatic update )
I tried to Download firmware through WiFi but always getting failed.
I need to run it without losing data. I didn’t backup the phone.
Any help

Xprofessor1 said:
Mate 9 keeps restarting
Showing HUAWEI logo, restarts several times then entering eRecovery ( I believe after update or automatic update )
I tried to Download firmware through WiFi but always getting failed.
I need to run it without losing data. I didn’t backup the phone.
Any help
Click to expand...
Click to collapse
Did you maybe take OTA when the phone was rooted and/or TWRP was installed?
If not, then try the following:
- Switch off and charge the phone
- Boot, and if it still goes to eRecovery, accept Install latest firmware and recovery
Without taking Factory reset, you will not loose data

Related

Bricked Huawei Y560-l01

Hey everyone.So,today i wanted to root my Huawei Y5 because of a sound problem and it all went well (Rooted with KingRoot)...Here is the problem...After a restart my phone went straight into recovery,i connected it to pc asap to use adb but it won”t detect the phone I can”t find any newer firmwares on the internet and the other dload.app simply don”t work because i have a newer build (Tue Nov 24 22:57:09 CST 2015).Also i have to mention that bootloader is still locked.Could someone kindly help me? (Sorry for my bad English)
how did you manage to root without unlocking bootloader? and by the way, try clearing cache and dalvik cache
deletescape said:
how did you manage to root without unlocking bootloader? and by the way, try clearing cache and dalvik cache
Click to expand...
Click to collapse
I just installed KingRoot and it rooted...Everything was fine then i restarted to see if root is permanent or not..I restarted and all my phone does is go straight into recovery and nothing else...I can only use ADB Sideload by pressing on ''apply update from adb''... I also clicked on ''reboot to bootloader'',it restarts and puts me into Huawei Logo and it just stay's there (Phone won't appear in adb,but it shows on device manager).I also tried to install the stock firmware but it say's that my actual version is newer than old one (a update came 1 week ago on my phone,in options).
All i wanted to do is install xposed to remove the volume too high warn when inserting headphones because it would bug on 50% and the warn would dissapear and wouldn't show again. (Tried to delete dalvik and cache and still the same)
rebooting to bootloader boots your device into Fastboot mode. it is normal that only the huawei logo shows up there! Just force reboot it!

Samsung Galaxy S6 Edge is not booting even after a factory reset

My Samsung Galaxy S6 Edge is not booting even after a factory reset
A mobile app. for Android was installed successfully and since then I’m only having issues with my Samsung mobile:
- Since the installation of both the Hockey & Mobile Banking apps, my mobile freezes during any regular action and after a few seconds the device auto-restarts itself intermittently; this happened during the weekend while in use;
- Sunday night I uninstalled both the Hockey & Mobile Banking apps and the phone continued to freeze and restart intermittently. I was able to boot in SAFE MODE.
- This morning after the phone was turned off and turned on, the phone is not loading; the boot is looping and unable to reach the menu. I’m able to boot in SAFE MODE.
- This morning I did a Factory Reset, when done I get the “welcome” screen and right thereafter, the mobile freezes, auto-restarts and the boot keep looping.
Any help would be highly appreciated.
Hey guys, any suggestions...? I tried last night restoring the OS using Samsung Smart Switch application and the process went just fine the first time and during the setup process the phone just restarted against and for stuck in bootloop again.
I did a second attempt but after the PC is don and the phone boots it gets stuck.
Sometimes after restoring stock firmware and you get a bootloop, you have to boot to stock recovery and factory reset then wipe cache partition.
I know you said you did that once before you posted, you did that before you used SmartSwitch. Have you tried factory reset since restoring with SmartSwitch?
Yes, I did with SS last night; I did it again this morning and after completing the 100% software download, it started updating the device and at 97% it stopped and got the message "FAILED".
now as we speak, I restarted it again and now it's at 66^ downloading the files.
How can I perform a clean install using SS...? or do I need ODIN...? I want to keep the mobile as original as possible.
If you can find your stock firmware, download it and flash it with Odin, it's more reliable.
Maybe a stupid question: Where can I find my stock firmware...?
My info:
PDAIX / CSCI2 / PHONE: PHH (XFA)
I found the Firmware on SAMMOBILE: https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G925F/XFA/download/G925FXXU4DPIX/108273/
Is this a stock Firmware and reliable source...?
Sammobile is a very reliable source, if that firmware is the newest one for your model number and country/region/carrier then you're good to go.
I did install Firmware corresponding to my phone (PDAIX / CSCI2 / PHONE: PHH (XFA)) using Odin, I can use the phone for like 2 or 3 minutes and then it freezes, restarts and gets into boot loop.
Any more drastic measurements to take...? Is there an online tool to test the hardware function(s)...?
After flashing stock firmware, have you tried booting to stock recovery then do the factory reset and wipe cache then reboot.
Yes, I did...!
In ODIN, do I load only the "AP"...?
In most situations, AP is all you need if the firmware is an all in one firmware file, if you have a 4 part firmware then you need to put each part in its corresponding tab/slot in Odin.
Sometimes you have to flash more than once to be successful.
My phone is running like a horse now...! No more intermittent restarts nor boot looping.
I just did a clean install of Android 7.
The clean install of Android 7 went fine and now it's working back again, was because I changed the "Reactivation Lock" to OFF; I think this helped.

honor 8 hard bricked, only vibrates twice. No recovery,no fastboot and no dload.

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.

Bricked. No recovery or fastboot

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..

Help - Stuck at checking for updates after factory reset got failed

Hey guys, i am stuck at checking for updates screen on BKL-L09. I was on stock EMUI, i did a factory reset and it went up to more or less 45% and failed. however it booted back to setup wizard and connected to WiFi and then the screen is stuck at checking for updates forever.
Solutions that havent worked
1. can not skip set up wizard because it needs me to verify google account
2. can get into bootloader with Volume down and cable method but unfortunately OEM unlock is not enable so unable to flash stock img
3. can not reboot to recovery. When tried, it takes me to erecovery and there it connects to wifi but doesnt download anything.
Any help will be appreciated guys, thanks a lot.
If anybody is in Bengaluru, can you tell me how does Huwei service center treat unlocked View 10?

Categories

Resources