Related
I lost my previous phone and bought a clean used one, Droid MAXX. Came nice and working, 4.2.2, OTA 12.15.15.
I first used RockMyMoto (ADB, telnet) to root successfully. Then immediately proceeded to TitaniumBackup to batch-restore about 40-50 apps with data. Seemed to finish successfully on surface (didn't run all). Rebooted to settle all changes and -- bam, a problem! The phone gets stuck at the animated boot logo (red eye).
I forced to shut it down by holding the Power key, then tried to boot into Recovery -- reboots with no prompts and gets stuck at the same point again. After many attempts gave up and agreed to do a hard reset, chose Factory in boot menu -- again reboots with no prompts and gets stuck again.
I am desperate to get back to a workable phone and ok with starting over. Is it possible to get back to what I received -- un-rooted, factory reset device? Having spent all day with this, I am at a verge of buying another phone again... Cannot believe that this phone became useless. Thank you very, very much for your help!
Have you tried flashing it back to 12.15.15 using the fxz and RSD lite? Phone will try to update after boot up, just place the phone in airplane mode and WiFi off to prevent it wanting to update if you want to root. At very least what I do is make sure I postpone the install of the update for 23hr 59min till I get root and freeze the update apps.
1080xt rooted 12.15.15
Problem solved with House of Moto. Did a full restore to 12.15.15. Will root again but will be doing an incremental restoration of apps, as I'm afraid something didn't work well in the batch process.
Hi everyone.
I have an LG G Flex 2 (H955) that suddenly went on a fritz. It used to be rooted fine, it was on default firmware, 10 something (wouldn't OTA due to rooting), no issues, but as I am a heavy user, enabled multiuser, had a bunch of apps installed and running it started to slow down on occasion, but nothing unexpected. Anyway, few days back, it shut down on its own while I was typing a message and the phone entered bootloop - on it's own. I decided to cut my losses and did the factory reset the hardware way, it booted up, did the "optimizing apps thing", got to welcome screen and - froze - then just restarted. It's been doing that ever since. Sometimes it boots all the way and then freezes and starts, sometimes it gets stuck on LG logo, sometimes even boots and works for a minute or two but still freezes and reboots.
I can access Download mode, and HW factory reset. I flashed several stock ROMs I found with LG flash tool 2014. It goes without a hitch, boots up, again gets to the welcome screen and reboots. I tried to to the dd cmd way to flash the only system.img I found online, but I get a security error at boot. It gets fixed when I flash the stock ROM again with flash tool. I am at my wits end. I have no warranty, I have no backed up original dump. With my limited knowledge I have somewhat of a hunch that one of the partitions might be corrupted as it boots most of the time but as it tries to write or read something from somewhere (hence showing the Welcome screen) it dies.
Would anyone have a suggestion as to what I might try next, or had a similar experience?
Thank you all very much in advance for any help.
Have you tried this tool with the appropriate image?
http://forum.xda-developers.com/g-flex2/general/p-restore-recovery-to-stock-tool-h950-t3171550
Hi and thanks for the tip. However, no, I have not tried this method as my device is H955, International version, and I am not keen on messing up the phone worse then it already is.
I will look it up in more detail, but as far as I can see it only pertains to the H950 (ATT version)
Edit: I looked it up in detail, and the developer removed the H955 support as there is a KDZ for it and he claims the .kdz is a much better option - however - .kdz does not work for me. It flashes the rom all right, both in Normal and CSE Flash modes, but the problem persists. Turns on (if I'm lucky), freezes, reboots and so on.
D'oh, didn't see the H955 part. :-|
Sorry to hear you are still stuck, can't offer much more unfortunately.
I know one of the flashing modes does a reset, but maybe a reset after the flash might help.. i think it's, from powred off, down plus power until the lg logo then release and then hold power on its own until you get to a recovery screen where you can reset.
you probably already tried that I'm guessing though. taken memory card out if you're using one?
thepktrckt said:
D'oh, didn't see the H955 part. :-|
Sorry to hear you are still stuck, can't offer much more unfortunately.
Click to expand...
Click to collapse
Don't worry about it, you tried to help, and I appreciate it
meangreenie said:
I know one of the flashing modes does a reset, but maybe a reset after the flash might help.. i think it's, from powred off, down plus power until the lg logo then release and then hold power on its own until you get to a recovery screen where you can reset.
you probably already tried that I'm guessing though. taken memory card out if you're using one?
Click to expand...
Click to collapse
Hi and thanks for yet another tip. However, you guessed right - I tried everything - reset from the recovery, before the flash, after the flash, in the middle of flash, with memory card, without memory card, tons of times - you name it, I've tried it. And still, it boots up (sometimes, though), freezes and go bye-bye. I'm completely out of ideas. If I could somehow rebuild partitions from Download mode, or use ADB, or push some image I found and flash it directly, but there is no way to push files to phone in Download mode (and 5.1.1. disabled external memory, so that is out of the option too).
It seems I'm stuck for now. I'm wondering if the repair guys have some tricks up their sleeves, perhaps with those hardware boxes, jtag something or other...
im on same boat with h955p, any solution?
the battery is the problem 100%. i had the same problem and i managed to fix it with buying a new battery and replacing it. 10$ on aliexpress plus you get the tools and it is really easy to replace.
hi. i was stuck in this situation. you can reflash the original stock rom back from LG UP software. at me this was the problem. my friend have a korean model and at him the 4g data connection was the problem...i was on the update of the marshmellow and freeze and reboot...factory reset didn't do something cool and keeps rebooting...but i was smart and lucky and my brain was thinking at the reflash of the phone...so i was to the reflash so my phone was completely and fully functional...no freeze , no reboot...and look for the v20a italy firmware (stock rom)...i say this because this v20a italy rom is so f***in stable and no battery drain...better than other stock rom marshmellow. Thanks me later.
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.
I'm really hoping you guys can help me out here. This is an S7 I bought from a Best Buy when I visited the US in 2017, and I got the Unlocked version so I would be able to use it back in my home country. Unfortunately, this is the second time I've had trouble with it in a span of 4 months and the first time it was a hardware problem and ended up quite expensive to get fixed.
Today I was using my phone normally when I decided to use the Google instant translation to translate something on my computer screen. That caused my phone to freeze, restart, and then tell me I was using an unauthorized flash and it was going to be locked, or something like that. Even after restarting a few more times, the phone would never get past that screen. I proceeded to factory reset/cache reset and from then on the phone just got stuck in a boot loop.
I learned that the fix would be to flash the phone. After a lot of work I found the G930UUESACSI1-20190930144640 firmware (the XAA version, for Unlocked) and successfully used Odin 3.13 at the Download Mode screen to flash my phone. It then restarted, went back to the blue screen, started installing some updates, when it was 100% it restarted again. Unfortunately, the loop remained. Galaxy S7 logo first, then the Samsung logo, then it just repeats.
I have also tried turning the phone off with the Recovery screen shut down option (since I can't seem to be able to turn it off with the power button right now), wait a few minutes, then turn it back on. Nothing changed.
Please, does anyone have any insight into this? What else could I possibly try, or what could I be doing wrong? I really don't want to send it to repair yet again in such a short time.
Many thanks in advance.
gabeblack said:
I'm really hoping you guys can help me out here. This is an S7 I bought from a Best Buy when I visited the US in 2017, and I got the Unlocked version so I would be able to use it back in my home country. Unfortunately, this is the second time I've had trouble with it in a span of 4 months and the first time it was a hardware problem and ended up quite expensive to get fixed.
Today I was using my phone normally when I decided to use the Google instant translation to translate something on my computer screen. That caused my phone to freeze, restart, and then tell me I was using an unauthorized flash and it was going to be locked, or something like that. Even after restarting a few more times, the phone would never get past that screen. I proceeded to factory reset/cache reset and from then on the phone just got stuck in a boot loop.
I learned that the fix would be to flash the phone. After a lot of work I found the G930UUESACSI1-20190930144640 firmware (the XAA version, for Unlocked) and successfully used Odin 3.13 at the Download Mode screen to flash my phone. It then restarted, went back to the blue screen, started installing some updates, when it was 100% it restarted again. Unfortunately, the loop remained. Galaxy S7 logo first, then the Samsung logo, then it just repeats.
I have also tried turning the phone off with the Recovery screen shut down option (since I can't seem to be able to turn it off with the power button right now), wait a few minutes, then turn it back on. Nothing changed.
Please, does anyone have any insight into this? What else could I possibly try, or what could I be doing wrong? I really don't want to send it to repair yet again in such a short time.
Many thanks in advance.
Click to expand...
Click to collapse
You need to clear the cache after flashing to get out of the boot loop.
Use the download key combo to restart. As soon as the screen goes black move to Volume up+home+power.
In the recovery menu choose clear/ Wipe cache, then choose reboot.
I apologize for not updating this thread before when it was still recent. The fact is that I didn't manage to fix my phone; clearing the cache after flashing did nothing to stop the loop.
I ended up taking the phone to the people who have fixed it in the past and after more than one month, they gave up. So I got my phone back and I want to try to give it another go before I just sell it for parts.
Unfortunately, my phone has come back even worse. Now it has no Recovery Menu to speak of, at least none that I can access; after a few seconds of the blue text on the top saying that it's entering recovery mode, it then proceeds to a blue screen saying: "Security Error: This phone has been flashed with unauthorized software and is locked.". I can still access Download Mode.
I have attempted flashing a few firmwares that I believe should have worked with my SM-G930U. Odin listed the attempts as "pass" and, after restarting and going back to the Download screen, it says the binary is Official. However, after trying to restart the phone normally, it starts displaying the blue screen again, and then, after going to Download mode, the binary is reverted to "Custom".
I believe right now the order of the day is to get the recovery menu to work again so I can do all the cache cleaning that seems to be required after flashing firmware. Any ideas at all on how I should proceed? Is there something specific I should download to fix the recovery menu?
How many files are you flashing in Odin, is it just 1 file in the AP slot, or 4 files: AP, BL, etc.? Also, is your phone rooted?
Drunkpilot said:
How many files are you flashing in Odin, is it just 1 file in the AP slot, or 4 files: AP, BL, etc.? Also, is your phone rooted?
Click to expand...
Click to collapse
Never rooted, was using the phone legit before it froze and entered boot loop. I flashed all 4 files, multiple times.
Someone tried fixing my phone a few days after I replied to this thread and some progress seems to have been made, but now the phone cannot get past a black screen with a "SBL Error! rdx_init!" in red text, and "upload mode" in yellow text. Still cannot access Recovery Mode, but Download Mode still works.
I did a little Googling on rdx_init errors and it seems I need a firmware dump from another G930U or something like that...any ideas on how I can proceed?
Flash it with Eng Boot in all slots using patched Odin. Reboot to recovery and wipe it. Reboot system. Then root it with advanced adb root. Links for all of this are here in xda. Enjoy
STA1NL3SS said:
Flash it with Eng Boot in all slots using patched Odin. Reboot to recovery and wipe it. Reboot system. Then root it with advanced adb root. Links for all of this are here in xda. Enjoy
Click to expand...
Click to collapse
Sorry, I'm not an expert at this by any means, I'm not sure what files to get. So far I've found and downloaded the following:
S7_Oreo_Nougat_Adb_Advanced_Root_V10
S7_Oreo_Nougat_Adb_Advanced_Root_V12
S7_Oreo_Su_Binary_Only_ADB_Root
But I had no luck flashing any of these cause my binary is 10. Is there any more help you can provide me? I really don't know how to proceed
gabeblack said:
Sorry, I'm not an expert at this by any means, I'm not sure what files to get. So far I've found and downloaded the following:
S7_Oreo_Nougat_Adb_Advanced_Root_V10
S7_Oreo_Nougat_Adb_Advanced_Root_V12
S7_Oreo_Su_Binary_Only_ADB_Root
But I had no luck flashing any of these cause my binary is 10. Is there any more help you can provide me? I really don't know how to proceed
Click to expand...
Click to collapse
I thought I had one in my phone, but I don't. If you look at the thread where you downloaded the Root_V12, you will see it. It's near the end of the thread somewhere.
Hello , yesterday I I turned off (power off through power button menu) my Pixel 2 for some time, when I turned it on again it got stuck as the title says for more than 30 minutes. Whenever I long-press the power button the phone restart but gets stuck again in the same loop. I'm able to access the bootloader and the recovery mode, I even managed to use adb to sideload the latest OTA update but that doesn't fix my problem. I understand that a factory reset/wipe could fix the issue but some of the data on the phone are important to my work and have not been backed up so I'm trying to save them if possible.
My Pixel 2 is running stock A11, last updated in October to 11.0.0 (RP1A.201005.004, Oct 2020) It has been working normally since I updated it almost a month back. It's not rooted and the bootloader is locked.
This is my first time to delve into topics such as flashing, sideloading...etc. and my experience is pretty limited so my questions are as follows:
1) Is there a way to extract/copy/backup the data in this case so that I could proceed with factory reset?
2) If the answer is no, is there any possible way to get out of the infinite loading loop?
3) If all else fails, do you think that waiting for the December OTA (final update intended for Pixel 2) and then sideloading it could fix the issue?