Related
Alright. This is a 100% stock Nexus S- nothing "development" wise was done to the device, no system tools installed that could cause issues, basically nothing but basic apps loaded on the device.
It just started today. I was working on my bf's Vibrant (another, more successful story) and grabbed my Nexus and hit the power button and it did not turn the screen back on. Holding the power button down did not reboot the device, and none of the buttons would light up or function.
So, I pulled the battery. Now every time I try to boot, it hits the "Google" screen and stays put. I left it alone for 5 minuets hoping it would finish booting and nothing. The soft buttons will light up, and if I touch them they register the touch but it does not help the phone to boot.
I do know that the phone was basically dead right before this happened, and at first I thought it was just dead. However, its been on the charger for at least 30 minuets- which should have given it enough of a charge to boot up, and still nothing.
What could cause this issue?
I did install a couple of new applications today, and I know the market updated a bunch of them but they're all apps that I've had on several phones (minus the two new ones today) and have never had an issue with any of them. The two new ones I downloaded were OS Monitor, and a 2G/3G toggle for hopes of improving some battery life.
But those are the only two things I've done differently. I've only been using the phone for a week but I haven't had any problems at all, before this.
Now- if worst comes to worst I can seem to get into the bootloader, and through that, stock recovery. So I can try to do a factory reset and wipe cache but without a backup I really kinda hope thats a last resort.
Please help, and let me know if you need any more information.
Thank you!
I understand that you're fully stock which I assume means you have a locked bootloader (everything I say from here on out assumes as such)? First, I'm going to also assume that you didn't update to 2.3.3? If not, then follow the steps in this guide to boot into a custom recovery and from there go to backup and restore and do a NANDroid backup. Now go to mounts and storage and mount USB storage (or whatever its called, don't have my phone right here). Plug your phone into your comp and copy over whatever you'd rather not lose from your SDcard (just in case you have to wipe). Now download the 2.3.3 update from here and put it on the root of your SD card. Now go back and flash this. Reboot and see if you're golden. If so, great, if not try a factory reset.
If that doesn't work go through the steps again to boot into a custom recovery, you might have to unlock your bootloader and wipe all your data (again) and restore your backup and try doing a factory reset with that. Don't worry about unlocking the bootloader, it can be relocked with a simple command and it won't wipe anything to relock it.
Here is the command just in case:
Code:
fasboot oem lock
I got all the way to having clockwork recovery booted up on the phone, but nothing would mount. Everything gave me an error, and factory reset froze...
I don't think there is anything I can even do from here, is there?
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.
Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
napstr said:
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
Click to expand...
Click to collapse
Hi.
According to what you say, it seems an hardware problem of you phone. Don't know if it may help but you can try installing an older factory image (for example kitkat) and seeing if the "force closing" problems are still there. If your phone is ok it should be able to run a factory image at least.
Download the nexus root toolkit, create a nandroid backup, then when either in CWM or TWRP wipe everything off the phone then try to flash a ASOP rom like Cataclysm if nothing else works then I don't know how to help sorry-.-
So I tried to get the stock ROM up and running again, and it seems even that is not possible. Several processes keep crashing during various tasks, even when idling. After having a short chat with Google Support about the issues I got an RMA offered, so things are cool. I locked the phone again, set the tamper-bit to false and wiped everything.
bootloader unlocked
MIUI 9.5.19 global ROM installed
Magisk 16.4
Have been using the phone for 2 weeks now it's the second time that the phone shut down because of battery to low. OK so far but it then only is booting into TWRP. Also deleting DALVIK and CACHE i can see it booting and then the black screen with the navigation arrows are visible for a second. It's seems that there is something preventing the system to come up properly. After 5 short attempts with black screen and navigationbar visible it boots into TWRP.
Also re-flashing Magisk is not solving it.
OK I could now re-flash the Global ROM again but it won't fix the general issue why the phone get's stuck once it shuts off because of empty battery and again I would loose all my data.
Anyone with ideas how to fix it or what could be the root cause?
EDIT: It seems that there is really a problem with the system itself. If I instantly hold the power button once booted until the black screen I could keep it running and I see the restart, shutdown, airplane buttons but nothing more.
In Windows I would say it's not starting the explorer.exe
anyone who had something similar?
Have you tried re-flashing with MiFlash?
Bootloop after weeks of normal use is pretty misleading considering that you are using a custom recovery that isn't even official plus Magisk and possibly other mods. You should flash the official stable ROM with the MI Flash Tool and then run the phone without any mods to see if you still experience the same problem. And if you decide to use TWRP again you are better off using it through fastboot so the stock recovery remains installed on the phone.
THx for your replies... I think I've figured it out:
It seems that the alternative launcher is the root cause. I've been using Microsoft Launcher since moths across all my devices (light+fast+sexy). Without it (replaced by Nova now) it seems that the problems are fixed
I found the phone in my bag with a discharged battery and does not want to boot all the way. It shows the animated MIUI logo for about 1 minute and then restarts, sometimes showing the menu to switch to 'wipe data' and 'assistant'.
It's all stock, locked, up-to-date, I think still on Android 10 or which one it is. I did not install any new apps and don't even use the phone for anything other than gaming.
I've tried connecting with PC Suite but it doesn't see the phone. Fastboot anything does not work since the bootloader is locked. I know I can wipe data and be done with it, just wondering if there is anything else I can do.
EDIT: I've wiped the data and reinstalled the phone but would like to know if there is a way to avoid this in the future.
Unlock bootloader. This is very important. Then you have full control over the device.
For example the other day I had hard brick because fastboot flash was interrupted. And I still managed to unbrick the device thanks to unlocked bootloader and custom recovery.
It's really hard to hard brick this device. I love Xiaomi <3