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.
Hi, i'm new here and i can't post a new thread in the right section. so i do it here.
I have a huge problem.
i wanted to root my mate 9. But i've doen something verry stupid...
first i unlocked the bootloader.
then i wiped i wiped all. and now, if it loads, it get freezed on the bootscreen. it reloads after a while and after 2 time reloading it opens Huawei eRecovery. Then i thought, i could recover my files. But it faisl everytime and says: Getting package info failed.
I tried also to flash system, radio, bootloader, boot and recovery. One time with newsest version of salfish, and then with the newsest version of hammerhead.
What can i do, nothing works
https://forum.xda-developers.com/mate-9/how-to/funkyhuawei-2-0-t3544686
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..
I installed Lineage on my Moto G7 Power a few days ago, and after rebooting it yesterday, it's stuck in bootloop (the Lineage starting animation is displaying), i have left it for 4 hours with nothing changing. can reboot it by holding the power button and I am able to get into recovery. USB debugging still works aswell.
I installed the newest nightly Lineage build for ocean (19.1), along with MindTheGapps and TWRP.
This has happened again, 2 days ago. I tried dirty flashing the same lineage version and nothing happened. I ended up completely restoring my phone using the official tool motorola provides.
then, after reinstalling lineage and twrp this time (so i would have access to my data if it were to happen again), and setting everthing up again, it just happened again yesterday.
things I've tried:
- clearing the cache using twrp
- letting it boot for hours on end
- repairing the file system with twrp (idek what that does, but I had hopes)
I would really like to just find a solution to this, as I very much enjoyed using Lineage (when it was working), but reinstalling everything every 2 days is not an option. this **** is driving me insane, i haven't been able to find a decently answered forum post on this anywhere.
so yeah, i would be eternally grateful for any help I can get.
thank you <3
Hello,
Did you ever find a solution to this? I am unable to boot into LineageOS as well, the boot just hangs. Posted on this thread: https://forum.xda-developers.com/t/official-lineageos-19-1-for-the-moto-g7-g7-power.4436929/page-7
greenmatrix said:
Hello,
Did you ever find a solution to this? I am unable to boot into LineageOS as well, the boot just hangs. Posted on this thread: https://forum.xda-developers.com/t/official-lineageos-19-1-for-the-moto-g7-g7-power.4436929/page-7
Click to expand...
Click to collapse
no, I'm sorry, I have nothing. I gave up after the fourth time of wiping everything and am back to using the motorola rom. a real shame
good luck tho and if you find something that works, do let me know please!!
Bummer. I will let you know if I figure it out.
Got it working, see https://forum.xda-developers.com/t/...or-the-moto-g7-g7-power.4436929/post-87342621