Hi guys.
Im hoping someone has a clever fix to my problem.
Version: FLD-L09C432B131, rooted and with TWRP.
Issue:
I took a plunge into the updating sea and installed B360. Never thought it would go through since I didnt unroot first. Well, it actually worked and the phone booted fine. The "About" part listed the new version but I was still on decembers security patch. So I ran Firmware Finder and started with the small file, 230MB or something. Unpacked it and moved to dload via the menu in FF.
Now the problems began. Phone booted and ran the update without any noticable issue....until it was time for a reboot.
It now only boots into Huawei eRecovery with the options to:
"Download latest version and recovery" - Which fails after connecting to wifi and trying to download from huawei.
"Reboot" - Just returns to eRecovery.
"Shutdown" - self-explanatory.
The devices does show up for a few seconds in ADB when it reboots and is connected to my PC. But not for long.
I was hoping to be able to flash TWRP with ADB but its kinda hard when it doesnt stay connected.
Anyone wise out there with some input?
Much obliged.
/nort
Ok update.
I managed to get adb to work finally by timing the seconds the phone was actually visible to the computer. A reset back to B131 and now im on B360. Not sure if i have the latest version with the battery fix but I guess that will be obvious soon enough.
Hi
I had my 2016 pixel with the latest 8.0 security update.
I was enroled on the beta so i got 8.1 but was unable to install it (multiple times) due to the already known problem.
Today i was using the phone, and i froze, only to restart to what looks like a corrupted bootloader.
Entering recovery fails.
Restarting does nothing.
I had the option to allow bootloader unlocking enabled (i enabled it before my first attept to flash the beta, just in case).
Unloking the bootloader does nothing and it remains locked, so flashing a factory image fails.
Am i doomed?
Pictures attached.
Only thing i have not tried (cause i did not find how to do it), was to try and boot the other slot (i am currently on B).
Bootloader: N/A
Just google some more, this is final, device is dead.
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..
1. december 2020, version N985FXXS1ATK1
I updated the phone on 7. December around noon, and after the update the phone keeps rebooting.
After it boots up, it seriously laggs. It then shows the notification "finishing system update" which after it reaches around a fifth of the progress abr, the phone reboots.
But it is not a real reboot, it only shows the Samsung logo for a couple of seconds and jumps back to the home screen, lags again and the notification starts from the beginning.
The phone's uptime is aorund 15 seconds before it reboots. This was a standard OTA update, no bootloader stuff, no nothing.
I'm taking it tomorrow to store.
I've tried:
- reseting network data
- wiping cache from the boot menu
- booting into safe mode
No difference.
Has anyone else experienced this, or has any advice?
got the same update but no such issues. let them fix it in the store
Dud motherboard if you have exhausted all software troubleshooting options. Had a sm-n985F with similar issues. Random reboots.
Limeybastard said:
Dud motherboard if you have exhausted all software troubleshooting options. Had a sm-n985F with similar issues. Random reboots.
Click to expand...
Click to collapse
Does not have to be motherboard issue.
updates through OTA can get corrupt/damaged so your update mostlikely got this so it reboots all time.
Try reinstalling your phone via smart switch app on pc or ODIN and see if problem remains.
If it stops then it was due to corrupt/damaged files in update via OTA.
Jake.S said:
Does not have to be motherboard issue.
updates through OTA can get corrupt/damaged so your update mostlikely got this so it reboots all time.
Try reinstalling your phone via smart switch app on pc or ODIN and see if problem remains.
If it stops then it was due to corrupt/damaged files in update via OTA.
Click to expand...
Click to collapse
Hence why I mentioned if you have exhausted all software avenues.
I took it to the store. They flashed it and now it works with the latest update. Like you said, it just got corrupt