Good evening guys.
For a couple of days the phone has been in bootloop and I have problems with the persist partition. It all started at the beginning of the year. For no apparent reason, the main camera stopped working (error: unable to connect to camera). The curious thing is that in the smartphone test menu, all the cameras are functional, except for the main one. The tests I did were:
Format the phone from the settings.
Reinstall the rom via fastboot.
Install other roms.
In the case of formatting and reinstalling, the camera app only worked if I held down the icon and chose to take a selfie. Using other roms, however, the pre-installed camera (camera go, for example), did not start. If instead I installed one of the various gcams for surya, these worked. But if I tried to load the config files briefly into the gcam, it also crashed and wouldn't open anymore.
In the end, I opted to keep the stock rom (rooted) and use a gcam with no setup. These days, the phone hasn't been used except to play online (only on wifi) and hasn't given any problems. Yesterday however, while I was playing, the gyroscope started moving by itself and/or getting stuck and not working.
At that point, I decided to do yet another fastboot flash. This time though, the phone didn't boot anymore, remaining in bootloop. I also tried to change version (from global to european), to flash again other roms (pixel os, miui.eu, pixel expiriece), but nothing to do. The only thing I noticed is that the recovery warns me that I can't mount /persist. I also tried recovering the persist.img from the original rom (I don't have a backup) and flashing from twrp. It seems to work fine, but then actually the same error comes back. I also tried from the terminal, always via twrp, but even there it says it has copied the data, but the error returns.
Could you help me?
Thank you.
Related
Hello to everyone and I hope somebody will help me with my problem. First of all, I bought this nice phone 2 months ago. It was branded and, of course, one by one, I did the followings: unlock, root, install CWM( first 4.0.0.9, after 5.0.1.4 and finally 5.0.2.0). After that, because the software of LG is not so successful, I stepped forward(very fast, after 2-3 days) and installed different custom roms.
Everything was fine with my phone (except those random reboots), but few days ago I got the first force closes of some applications. Directly I applied those 3 resets from recovery and surprise, after booting, the phone was like before, all apps inside, nothing changed. After I tried again factory reset, even with code 3845#*920# and is much worst, the phone is not rebooting now from recovery mode. What is strange, the phone is operational in some way, some apps are still working, but if I stress the phone little more, I get a lot of force closes and I have to switch it off-on. Same, if I try to uninstall or to install apps force closes are coming. I connected the phone to computer, everything seems to be ok, I copied roms for flushing with CWM, but again surprise, those roms are not on sdcard of the phone, in fact I can't copy or delete nothing on sd-card. I tried to install a rom from an external card, nothing, anything I am doing, the phone going to the initial configuration which was when I got problems. I tried even to flash kdz or bin through Win XP or Win 7, nothing, I saw that the phone is stucking when starting installation of the rom itself.
So, I am ready to send the phone to LG, I suspect allready a problem of hardware. But my hope is that somebody of you which doesn't have secrets in Android and LG phones can give me a sollution.Thank you in advance! And scuze please my english.
Luckgav said:
Hello to everyone and I hope somebody will help me with my problem. First of all, I bought this nice phone 2 months ago. It was branded and, of course, one by one, I did the followings: unlock, root, install CWM( first 4.0.0.9, after 5.0.1.4 and finally 5.0.2.0). After that, because the software of LG is not so successful, I stepped forward(very fast, after 2-3 days) and installed different custom roms.
Everything was fine with my phone (except those random reboots), but few days ago I got the first force closes of some applications. Directly I applied those 3 resets from recovery and surprise, after booting, the phone was like before, all apps inside, nothing changed. After I tried again factory reset, even with code 3845#*920# and is much worst, the phone is not rebooting now from recovery mode. What is strange, the phone is operational in some way, some apps are still working, but if I stress the phone little more, I get a lot of force closes and I have to switch it off-on. Same, if I try to uninstall or to install apps force closes are coming. I connected the phone to computer, everything seems to be ok, I copied roms for flushing with CWM, but again surprise, those roms are not on sdcard of the phone, in fact I can't copy or delete nothing on sd-card. I tried to install a rom from an external card, nothing, anything I am doing, the phone going to the initial configuration which was when I got problems. I tried even to flash kdz or bin through Win XP or Win 7, nothing, I saw that the phone is stucking when starting installation of the rom itself.
So, I am ready to send the phone to LG, I suspect allready a problem of hardware. But my hope is that somebody of you which doesn't have secrets in Android and LG phones can give me a sollution.Thank you in advance! And scuze please my english.
Click to expand...
Click to collapse
Run,run, as fast as you can. Run to lg and shove it up their ass....
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 dear community,
As many other unsolved threads in this forum I'm stock in TWRP and bit lost to the next followable path.
Really weird symptoms :
Digitizer down. Disassembling the phone and replacement with this full parts screen
I take this opportunity to upgrade to the last excellent SultanRom (cm-13.0-ZNH2K-20160808-STABLE-Sultan-bacon)
I perform a clean install (wipe /data and /system with also upgraded TWRP 3.0.2-0)
Then, flashing the ROM, Google apps package, and reboot.
Boot in TWRP. 2 or 3 attempts, still in TWRP.
Open the phone to "see" something
Reboot, 4 or 5 attempts or more...
And TADAM! OPO finally boot in OS.
I reboot to see if problem persist, and same difficulties to boot in OS...
I finally reach OS (I do not know how?! Chance? :crying
I set up and use the phone normally and realise the rear camera is not working. Any rear camera button is present in photos applications, I can not see with "test device" applications. (I had perhaps do a bad reconnecting?)
Another more serious point : the volume - down alone, like a phantom, and SOMETIMES I can't turn off the screen...
I decided to re-open the device, try to fix the rear camera, watch if the volume - is not trapped under the shell.
I also do a full wipe, reinstall ROM...
Now I'm still stuck in TWRP, with fingers crossed to get on the OS by chance!
Any idea? :angel:
Hi all,
here is my problem.
I have an OPO since 2014, since then I flashed quite everything to it.
A couple of months ago my sim module stopped working, it was an hardware problem, so I had it repaired a week ago (I wasn’t in a rush, I have another phone I use as my main one) and came back fully working. I don’t know if this is implied in the problem I’ll describe, but it’s a fact that worths the mention.
Since I was on the new CM 14.1 nightly, I decided to update the ROM from the updater in the settings menu, so I downloaded the latest one and reboot in recovery and install it.
There started all my problems: it happened an error while TWRP was working, “E: unknown command [log]”, I didn’t understood what it was about so I restarted anyway.
The phone was in bootloop in that moment, thus I decided to clean install the nightly I downloaded earlier, this time also with the gapps: this time, after the same error already mentioned, TWRP crashed while installing the gapps.
From that moment I couldn’t do anything: the phone acted weird, it restarted three or four times and then it went black. I was able to enter fastboot, I hardly managed to enter the recovery since not every time the combination “vol-+power” worked.
So I decided to flash the stock ROM with fastboot. Nothing, it wasn’t a solution, the problems are still there and I don’t know what to do.
I’m now able to enter TWRP with fastboot, and I can install a ROM without problems, but eventually TWRP crashes, the phone restarts three or four times and then it dies.
What the hell is going on with my phone?
I also notice something: when I install a new ROM (with TWRP), the recovery crashes etc etc but when I manage to renter, folders in the “sdcard” are:
- a “0” one
- an “obb” one
- the "TWRP" one.
If I put a zip in the “sdcard” folder, and again install it, after the reboots the “sdcard” folder is still intact, with the three folder “0” “obb” and “TWRP”, the zip I flashed seems to disapper
BUT
If I open the “0” folder, I found the zip I copied earlier! It happens every time I install a ROM: I found multiple combination of the three folder on the path "sdcard/0/0/0" ect etc. I have a video that can show this issue more clearly, but I can't post it at the moment (I'm a "new" user).
It’s a long post, I know, but I wrote the less I could, if someone needs some other infos pleas ask, I really want to bring back this phone.
Thanks