I have a Samsung Captivate, running android 2.3 (cyanogenmod). After upgrading, my phone will no longer enter recovery. I've tried the 3 button trick, using quickboot, and oclf... no luck. Every time I attempt it, the phone will reboot, but it will immediately boot back into 2.3. Also, I can no longer access my phones internal storage. Before, whenever I plugged my phone in, it would show up as two separate drives... internal, and external. Now I only have external. If I try to flash a new rom, I get a blank screen, then it reboots.
Now my phone is rebooting randomly.
Since CM7 is still in its testing stages, it is pointless trying to get help here. Try the CM forums.
So this issue has persisted throughout wiping data/factory resetting. I'm really not sure what this is.
Basically what happens is that my phone will gradually get slower and slower until it freezes and then reboots. However, after it reboots, it will go into a boot loop. What I will then need to do is basically wait it out by shutting it off. Then, I wait for an hour (maybe more) before I try turning it back on again, at which point it returns to normal.
Any idea? I thought it might be a memory leak? But how would that affect rebooting? I'd like to also mention that at one point my recovery somehow disappeared as well. I managed to re-flash TWRP using Flashify, but I haven't dared going back into the recovery, because last time when I had lost my recovery, I ended up thinking that I had to wipe my phone completely (because even Download Mode wasn't working correctly).
By the way, I'm running an AT&T LG G2 d800, on the "d80010q" firmware 4.2.2. I'm rooted, with Xposed modules running, as well as the camera mod flashed. No other modifications have been made except for buildprop and systctl (kernel) changes through android tuner.
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.
Hi!
My Nexus 5 device seems to have many issues, some that I have resolved, some that appeared next. Here is some history.
- The first issue that I had was that some sensors were not detected, and the others were not working. Sensor testing applications found some of them (but they didn't work), and others like the accelerometer didn't even show up in the list.
- For a couple of months now, once in a while (at each ~2 weeks), I find my Nexus 5 powered off, and bricked (the boot process stops at the Google logo)
- Each time, flashing the original images worked (simply using flash-all.sh)
- After one of these flashes, I had no wifi. Flashing the original image did not work. Rooting/installing TWRP recovery, erasing cache, etc. did not work. I finally got it to work by installing a custom ROM, and never understood why it worked.
- Device bricked again, flashed the original image back. Wifi still works, but no SIM card detected. Absolutely no sensors are detected. The device reboots after a couple of minutes. This is where I am now.
What I tested so far :
- Rooting the device, running e2fsck on the partitions, some of them showed errors. None of them show bad sectors.
- Moving the content of /persist (to try to fix the SIM card problem)
- Flashing custom ROM, stock ROM, old ROM, different radio, etc.
- Removing/inserting the SIM card
I really am out of ideas, does anybody have ideas that I could test? I'm starting to think that I have an hardware issue but I still hope to repair the device... The issues started to appear right after the guarantee was expired.
EDIT: I found many threads about power button issues, however right now if I boot to Android the device reboots after few minutes, but when the phone is in TWRP recovery it stays open and never reboot. I therefore think that the reboot problem is not related with the power button.
Hi,
last week I successfully installed LineageOS as of March 15 on my OP6 and it worked perfectly.
This morning, I applied the system update to the latest version as of March 22. It took a long time to process (about 5 minutes), then rebooted as usual, but then surprisingly stuck in Crashdump mode.
After some switching off and on again with the same result, I found I still could boot into recovery by VolDown + Power (it’s the simple lineage recovery, not TWRP).
Since then, I tried several times to reinstall both Lineage versions as of 15th and 22nd the usual way, but the phone never would boot any system. The recovery works perfectly, system can be flashed by ADB sideload and reports success, but after rebooting from recovery into system, it either runs into Crashdump or back into fastboot.
Bootloader is unlocked.
I have applied the copy-partition tool to make sure there is no bad software in the other slot but that didnt help either.
I have done factory reset / format all and re-flashed Lineage (latest and older version) but same result - fastboot or Crashdump.
Any hints what I can try to get a working Lineage again?
--ks
Update: It was possible to flash OxygenOS by MsmDownload, which booted perfectly and is running through its setup procedure now. Though I prefer LineageOS by far, I won’t switch back unless I am sure this won’t happen again
Browsing a bit further through this forum, I got the impression this is quite common on OnePlus phones from OP6 on, and so might happen at random intervals even with the manufacturer’s OS. In other words, a built-in fault. I want my wonderful OP 5T back
--ks