Hello,
So here it how it goes:
My N5 freezes suddenly and shortly after it goes into a bootloop ( stuck at Google logo ). And from there on, the only thing I can do is just go into the bootloader.
If I go to recovery mode I can see that I get "msm_sdcc.1/by-name/misc no such directory" or something like that.
The only thing that helps make this issue dissapear is performing an oem unlock in fastboot mode, but this is not a good solution since this is the 2nd time it has happened to me in the past 3 months.
What do you guys suggest I should check/do to prevent this issue from ever happening?
Thanks!
Does the bootloader relock itself at reboot? If it does, the emmc chip is going or gone.
@audit13
The bootloader doesn't relock itself. It remains unlocked even after reboot.
I just unlock it to perform this "trick" that helps me get out of the bootloop. ( also after unlocking it, I perform a fastboot oem lock, done this both times ).
Also, don't know if it is related, when i go into recovery mode i get the android with an X or an ! (forgot which one) which is most probably due to files missing.
The screen with the dead android is normal. No need to relock the bootloader in my opinion.
Have your tried flashing a completely stock rom, including th userdata.img file to see if that solves the issue?
@audit13 Wanted to keep the stock rom with which it had come. Also doesn't an update ( from L to M for example) change the rom completely?
An ota update will move the phone to the latest of the current version (e.g. 5.0 to 5.01). The the ota will move from LP to mm.
Personally, I prefer mm.
So.. The phone did it again today, same behavior, same result ( bootloop out of nowhere ). This time I performed a complete new install of the OS ( wipe cache, factory reset + reflashed a factory image).
At this moment the phone is working as usual and now I will wait and see if the issue reoccurs (hope not).
If someone else has any other ideas an how to prevent or read some logs from the phone ( even if I performed an oem unlock ) please reply.
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..
Hello,
I had FRD-L02 stock with EMUI 4. I bought phone on Amazon in USA. It was working there and I haven't had any problems in Europe too. But then one day came and the phone was stuck in boot mode (those 3d honor letters). Nothing helped except factory reset. I did it and phone was working fine for half a day or just one day. After that the same scenario was repeating and I was doing factory resets.
I was not able to see any updates. Dload was not working.
I bought a bootloader unlocking code from DC-unlocker. It worked. Then I used fastboot mode to flash TWRP. After that I used HWOTA8.
I tried to install FullOTA-MF-PV package with FRD-L09C432B521 (8.0.0.521) (update_full_FRD-L09_hw_eu.zip ; update.zip ; update_data_full_public.zip ). So I was not only updating OS but I was also changing the region. During the installing moment of the second package I accidentally touch the screen and installation stop (maybe it would be happening without touching too). After that the bootloader screen changed. I had EMUI 8 and it was working fine except it didn't had keyboard and a lot of apps. It seems that I have tried everything to install fully all of the packages. I had some problems in the way but then I succesfully load fastboot, installed TWRP once again (actually, I couple different ones; some of them was not giving full access to the files). So I was able to load HWOTA8 once again. It seems to be working fine... But after that I am stuck with unlocked bootloader with no OS, no recovery, no adb or fastboot, no sound when connecting to PC.
Please, could you help me? Is there any way to fix my phone?
DC-Phoenix
Mumtaz77 said:
DC-Phoenix
Click to expand...
Click to collapse
The problem is that I can't start fastboot mode
Actually, it is possible to go to fastboot mode. Just wait till the battery is empty, then press volume down and then connect to pc.
Hi,
I have a mi note 3, with global ROM. Yesterday, it received an OTA upgrade to 10.4.2.0, and immediately after the install, when the phone booted, it started showing errors about Find My device crashing. I managed to enable developer mode (this phone was unrooted and stock recovery with locked bootloader) and using adb I could stop the find my device crash by removing the package (so it wouldn't reboot) and backup about half of its contents. It did reboot though, and then It just would not boot at all to the system and would just keep boot looping (i never got the home screen).
Having tried a few things with ADB, I decided to do something a bit more drastic and I used ADB sideload to install the same ROM again using the recovery mi assistant option. That worked but still the phone wouldn't boot, so I decided to erase user-data (which according to the xiaomiadb does remove all apps but not pictures and all other stuff). Then the phone did boot, but It got stuck again, this time on the android setup screen where it says something like 'wait a second while we setup your device...' and getting again the same error about Find My Device crashing.
Is there any hope on recovering the data in the phone? I had two ideas but I have no idea if they are stupid or if they have any chance of working:
1-. Unlock bootloader using the Xiaomi app, in fastboot, but instead of rebooting, after unlocking using fastboot to load twrp and then trying to save the data via twrp
2-. Wait for another global rom update, apply that via recovery and see if it does fix the issue with Find My Device
Is any of those ideas realistic? If not, is there any chance to save the data from the phone? even if it implies opening it and so?
Thanks!
The first option seems extremely risky, unlocking the bootloader will format all data - maybe before reboot. The second needs patience, most probably that was the last miui 10 stable. Don't you have a miui account? Most of your stuff is there, you could login from your browser and check it out.
Thanks dpikros. Yes, I have access to the mi account, but I never trusted mi cloud with my data, so I had all sync to mi cloud disabled unfortunately.
I tried installing the previous MIUI, but it's based on Android 8.1 and the sideload won't allow me to use it. I think same will happen with developer ROM.
Does anybody know if the data format happens before or after reboot when unlocking? I was thinking, unlock bootloader and then use fastboot to boot the twrp image (without even flashing it) but not sure if the Xiaomi unlock app will automatically reboot the phone or if it will somehow delete if from unlock directly.
Thanks
I got my Nokia 3.1 in a bit of a weird situation trying to flash the stock ROM. I feel like it's a lost cause, but since I can still boot in recovery mode, there may still be a solution, I will explain in case someone can help.
It started when I tried to update from Android 8.0 to 10.0 (none of the previous OTA updates had worked and would always reboot in Oreo 8.0). This time, it didn't work and got the phone stuck in a boot loop.
The phone is still under warranty, but because I bought it overseas and there's no Nokia care centre here is New Zealand, I had no option but trying to repair it myself.
A wipe/factory reset didn't help, but after changing the active slot from B to A (using fastboot), it booted again in Oreo 8.0. Only problem is that I could no longer start a fresh Oreo 8.0 install without updating first and since all updates failed, I was stuck.
I suspect slot B is damaged or corrupt, hence the impossibility to update. To check it, I switched back the active slot to B after a factory reset, and that was not a great idea, the phone wouldn't even boot and looked hard-bricked.
But I still managed to use SP tool to download firmware, so I did that with the original Nokia 3.1 stock ROM (ES2).
However, I could not flash all files, I'm not too sure why.
I had the error message:
ERROR: STATUS_SEC_INSUFFICIENT_BUFFER
Verified boot is enabled
Please download signed image (sutinfo-verified.img) or disable verified boot
I didn't know how to do either of these, so I skipped the three problematic files: sutinfo.img, systeminfo_a.img, and cda_a.img (not sure what they do?).
It worked and un-bricked the phone, but it now boots to recovery mode only. What puzzles me is that I also no longer have access to fastboot, even when I reboot to bootloader (as if it skipped bootloader and went straight to recovery). I suspect it is because it still boots on slot B but I don't know how I can check that or change it back to slot A without fastboot access.
I tried using adb: adb shell getprop ro.boot_suffix but although it can see the device, it failed because it says device is unauthorized. I've tried all the fixes for this I found, to no avail.
So that's where I am, able to boot to recovery (but with adb unauthorized), able to flash firmware (except those files that must be signed), and unable to access fastboot.
I'm giving up hope that it's repairable, but I'd love to at least understand what happened, if someone has any idea...
Sorry for the long story...