After having experimented with several custom ROMS over the last few days, I decided to go back to the stock ROM. I attempted to flash the stock 4.4.2 ROM using LGFlashTool. It does fine up until about 85% finished, when it reboots the phone, with the message "waiting 25 seconds for reboot". The phone reboots, then reboots a second time, and comes up in the MiniOS auto touch test, with a prompt saying "do not touch the screen". This hangs for several minutes, and the LGFlashTool eventually times out and says that the process failed. However, if you then click on OK (despite the "do not touch screen" warning), and use the combination of holding down the power button and clicking on "Normal Boot", the phone boots up and appears to be working correctly. I was then able to install the Verizon OTA update to bring the phone up to Lollipop. Am I OK at this point, or do I need to repeat the ROM-flashing process? If I need to repeat the process, how do I keep the device from hanging in the Auto Touch Test mode?
Related
Hi there! I'm a stupid-stupid person. I was trying to get Lollipop faster, so I tried to flash lollipop on my phone.
I managed to root it, but haven't done any backup, except for media and contacts.
I'll try to explain what I've done.
So I rooted the phone, entered the download mode and then I tried to flash it using LG Flash Tool 2014.
When in download mode, it was stuck at 0%, so I didn't wait to go ahead, I tried to flash it.
Now, the flash failed several times. The phone was alright then.
Further, I tried again and at some point something happened, it got to two percent, it wrote COM4 and then it failed. It might have been my antivirus that stopped the process, I'm not sure.
Well, now I have a useless phone. It keeps showing the LG logo.
The hard reset doesn't work, it's not recognized in Device manager, and it doesn't work download mode.
When I try to power it off it does so only after a long press. At first, when the screen goes black, if I release the power switch, then it will reboot again. If I press it long enough, the phone will power off.
I'm desperate, of course.
The phone was running Kitkat.
OK I screwed up. I would appreciate any help here. Rogers S6 Edge, G925W8. It was stock 5.0.2.
Wanted to try a ROM so flashed TWRP, then flashed Kingfisher ROM v1.1 (it seemed the safest / W8-friendly). ROM was fantastic (much better battery), but GPS would never lock.
Tried to start over by flashing stock Rogers 5.0.2 via Odin but it wouldn't flash. I read (a little too late) that downgrading isn't something Samsung enjoys. Argh!
Then out of desperation, I flashed the BL (BL_G925W8VLU2BOH8_5.1.1.tar) from http://forum.xda-developers.com/galaxy-s6-edge/general/canadian-odin-5-1-1-bootloader-twrp-t3196595 , which was a very bad move, I assume because I wasn't on 5.1.1 to begin with. Crap!!
So now the phone gets to the Galaxy S6 edge splash screen, with "KERNEL IS NOT SEANDROID ENFORCING", and it stays there. The phone also gets very warm, and I can't shut it off. Using VolDown+Power+Home reboots it (showing the same message) but doesn't shut it off. Using VolUp+Power+Home reboots it but only says the same thing about Recovery.
Please tell me that I didn't just brick this phone!!
UPDATE:
Am able to get the phone into Download/Odin mode by holding the 3 buttons (voldown+power+home) while plugging the phone into USB. The stock Rogers image refuses to flash (Odin says fail immediately), but I am a step closer thanks to @brar.arsh's thread ( http://forum.xda-developers.com/galaxy-s6-edge/general/canada-galaxy-s6-edge-canadian-users-t3069314 )
From there I grabbed the "S6 Edge Stock Firmware OG2" which comes in 4 parts (BL, AP, CP, and CSC). I added all 4 pieces to Odin and started flash. Boot.img and recovery flashed, but then during the system.img flash, it failed about half-way through. Right after that failure, something changed because the device now became "Unknown Device" to windows, and it complained that "a USB device has malfunctioned, and Windows no longer recognizes it".
This gave me hope that I could get into Recovery (since that flash was successful), but the phone likes to boot directly to the "The update failed so please launch Smart Switch" message - regardless of starting with VOLUP+PWR+HOME button combination. So no recovery access... but making progress.
I belive I initiated a flash that contained JUST the BL, CP, and CSC portions, and it passed quickly. This, of course, isn't enough to get the system going. I just wanted to see if it would fail in other areas.
Trying the emergency flash via Smart Switch: Smart Switch said it required the phone to be in Recovery mode, but it still attempted the fix even though I was in Odin/Download mode. Good news, but unfortunately it gave the same result - a failure at around 50% of the entire flash operation.
I have tried re-flashing the AP portion several times and it fails at different progressions (50%, 75%, 90%)... so close.
I was thinking that it was maybe a power issue (since the battery was completely dead during the "kernel is not seandroid enforcing" period, with no way to turn the phone off or pull battery), I wondered if the battery just needed a little juice before starting the operation. I let it stay plugged in for a few minutes after one of the many failed flash attempts (screen was illuminated with the progress bar frozen at the point of failure). I noticed that when I unplugged it, it didn't die immediately, so I plugged it back in (getting the "USB device has malfunctioned" message again), and forced it to restart by holding the VOLDOWN+PWR+HOME buttons). It got back into Odin mode and the PC recognized it again. Loaded up just the AP portion in Odin, hit Start, left the room, and when I came back it said PASS! I cannot prove that it had any battery power from this method... or if it even helped. This could have just been a fluke.
The phone automatically rebooted into Recovery mode (which scared me) so I hit Power Down.
Rebooted the phone - I hear the lame Samsung startup song, and it is booting. Hallelujah.
My wife was using her phone (completely stock, no mods whatsoever) and it started shutting down processes (contacts, calendar, etc). She held the power button down to manually shutdown and then rebooted shortly after. The next day, it started to do it again, so she did the same thing only this time it stuck on the "M" logo screen. When she brought it home, I held the power & vol down buttons in for 2 minutes and the phone began to reboot but still stuck on the "M" logo screen.
I began searching vigorously online for a solution and have tried everything. **NOTE** - I am completely unsure what version of software the phone was running before this happened. The first thing I tried was RSD Lite with the JB Stock file from Team US Cellular. The flashing fails during certain lines of the .XML file. I took suggestions from other users to delete the lines it fails on and let the file continue the flash. Once it reboots, it is still stuck on the "M" logo screen. I then tried all the other stock firmware files I could and the same result each time.
Next, I tried using ADB and Fastboot tools. My PC recognizes the phone when plugged in and running command "adb devices" shows the phone listed, but whenever I try to run a pull or other command, I get error:closed. I've tried all the solutions of making sure ADB files are updated, running the list of commands to get the daemon connection reset, etc. I can't push/pull anything using adb. I tried using mFastboot with no luck either.
I tried the above steps over and over for 3 days straight, hoping I missed something simple. My final option was to boot into Recovery Mode and run Wipe Data/Factory Reset. When I select that option, about 3 lines of command begin to run and the phone reboots and goes back to being stuck on the "M" logo screen. The command lines and reboot literally happen within 2 seconds. That tells me Factory Reset is corrupted, but I'm not 100% at this point.
Does anyone have any insight on if there is anything I can do at this point? It wouldn't be such a big deal to lose the phone, but we have pics/videos of our 2 year old that we never got backed up at home or in the cloud and they're very important to us. Unfortunately, the phone did not have and SD card. I'm honestly out of ideas at this point and have never felt so defeated.
I got brave and decided to just unlock the phone and attempt to install TWRP on it and that doesn't even work. It says it flashed it, but whenever I choose Recovery, it never boots to TWRP. It continues to use the stock recovery screen. I'm assuming this thing is just completely done for?
Hello. I have a problem with my phone. I forgot to delete root and decided to click the wireless update provided in the phones settings. While rebooting in this process the phone has become stuck on the 'no command' screen and then times out and repeats in a loop. I have managed to enter the recovery stage and try several of the options on this screen but with no success.
Something very much the same just happend to my HT17 Pro with non-rooted stock ROM and regular suggested update. It is stuck in on and off "HOMTOM" logo and trying to boot into recovery end in "no command"...
just pres power + vol up one time. worked for me!
Hi guys,
first of all thank you for taking your time and reading through this. I'm not completely new to android, nor using fastboot and recovery. I flashed a few phones over the past years I even resurrected bricked ones. However I have no idea what is happening to my Honor 8. One thing to mention, it's the latest Nougat update, and a STOCK ROM.
It all started this afternoon. The phone suddenly reboot while using it. After that, the android screen came on, then Honor animation and.. freeze. Completely. I had to reboot using the long press method since it was stuck between the bootloader and the rom itself. It started up ok after that.
An hour passed, and while I was typing a message, it froze again. I could go back to home but the phone was really slow. After opening up Messenger again, it froze completely. Had to restart again with the long-press reboot method. It started up ok, entered the sim pin and upon entering the screenlock code it froze again, completely. Long-press reboot, again.
Since then, the phone won't boot. It gets stuck every time on "Honor powered by Android" for about a minute, then it reboots itself. I even got some weird green screen with a blue and a red rectangle, but that just stopped after a few reboots.
I mentioned that I know how to recover and fix stuff when something acts weirdly, but that's not the case, I can't do ANYTHING. No fastboot, no recovery, no button combinations, I can't even turn off the phone. It just keeps rebooting on and on, and yes, the battery will eventually die, but I have no access to any recovery options. I even tried dload but no luck.
It's still under warranty so I can send it back but I just rather fix it at home (without taking it apart), because I don't want to wait 3 weeks to get fixed. But it seems like that is the only option right now, I have never ever seen anything like this happen.
Any help or comment is appreciated. Even if it's not possible to do it at home (hardware issues?), I am really curious what can be the cause of this issue (damaged rom, filesystem permission issues?).
Thanks.