Database Info

[Q] Strange problems with my LG

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....

[Q] Help! I tried to root my tablet and now I seem to have broken it -- it won't boot

Alright, so yesterday I tried to root my tablet (Samsung Galaxy Tab 3 10.1 Wifi) yesterday by installing TWRP and then loading the Superuser zip found in their link in the play store. It worked fine--I had root access and all was going fairly well. I then tried to make a small tweak to the build.prop file by changing ro.build.version.codename from REL to L.
When I rebooted to apply that change, I could not start up, so I did a factory reset (not a big deal, no essential files on there). It then booted fine, but when I reinstalled/updated all my apps, the Google services were crashing like mad. So I reverted the build.prop file back to REL and again it would reboot, so I did another factory reset and all was good; the Google apps were fine.
Well I was still rooted and I wanted to take advantage of all that time I spent doing it, so I downloaded the bootanimation zip found on this thread and replaced my bootanimation.zip that was already on there. I restarted to see the animation, and this is when the real nightmare started happening. I could not boot now at all.
I did another factory reset, and still it wouldn't boot. I then used TWRP to do a full reset, and still nothing. I did an advanced reset and somehow managed to delete the operating system files (I have no idea how), causing TWRP to say that no operating system was installed. I still couldn't boot, of course.
Finally, I decided I had had enough of this rooting ****. I searched all over the internet looking for a North American version of my stock ROM, and finally found one posted on this forum post. I wouldn't normally trust any random file, but I was getting desperate here. I used Odin to flash that ROM, and there were no errors. Now when I go into recovery, it gives me stock and not TWRP, so I know that was probably successful.
However, I still cannot boot. I get stuck on the screen that says Samsung Galaxy Tab 3, which sometimes goes away and then comes back. I can't send it in for warranty, because it still says "custom" in the recovery mode. How can I fix this? any ideas?
I really want my tablet back :crying:

Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5

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.

HELP - Phone cannot be factory reset... To cry or laugh?

Hello everyone!
This is my first post here, and I have a problem with my phone.
It is Highscreen Boost II (russian one, you didn't maybe even heard about it). Google for it...
The main problem is that the phone started to act strange one day. Example: I unlock the phone, start opening my apps (Fb, Insta, Viber...) and after a few minutes it just restarts by them self. I also tried to turn OFF the Internet connection, but all the same thing.
The phone is rooted, and it have CWM recovery. And here starts the funny part. XD
When I go to CWM, i go to factory reset, it all done right, it says "successful" on the, but what is the strange part, that it just takes like 5 sec. to do the "reset". When I press reboot system, it reboots the phone, but nothing even changes XD.
I also tried, flashing new ROM, it says that is all done, but when I restart the phone, it just came back on the previous state that it was before. The other funny thing is that, the phone keeps go back, on the same date (~20. February 2017). I fix it manually in the Date and Time settings. I also tried in CWM, to go to Mounts and Storage, and doin' from there format of the SYSTEM, and than flash the ROM, it flash it for 10 sec. Reboot and all the same stuff. I even tried Mount /System and than Format it, i tried to format everything, but without success. It just says the CWM that is done, and nothing else...
Than, i tried to flash the Stock Recovery (it can be flashed from the CWM), it says that it's flashed, than when i try to reboot the phone in the Recovery mod, again it comes back with the CWM, so in fact, nothing has changed in the end. I also connected the phone with the ADB connected to the PC, entered in Fastboot mod, Booted in the STOCK RECOVERY (live boot - to say...), using the commands in the terminal, it successfully boot up the stock recovery, than i tried to do the factory, cash and all usually necessary before flashing the Stock ROM, after that, i flashed the ROM (from the ZIP file, SD card...), again, it was very short time, saying that it was successfully installed, restarted the phone, and imagine it all works good
-\ Nah', just kidding, it is the same thing again, all the same, not even changed the Recovery, the ROM, nothing... I also tried flashing the Custom/Stock ROM thru the commands on the PC, it says DONE on the end, and all the same, nothing...
After all that, i decided to restore the phone with other ROM (to say) in the way to go to the DFU mod (pressing + and - and Power button together), so i enter the phone in Download mod (to say). In that way, once (2 years ago) i recovered my phone from Hard Brick, since i deleted the partitions and all that stuff....
Than, i decided to flash the ROM from the DFU tool (Innos Upgrade Tool) - from here i was following the instructions, and doing all like before. It is connected in the device manager, and detected as DFU android phone (something like that), as it should be. When i try to format the partitions, it just crashes, or when i try to flash the ROM, it went to 100%, and doin' nothin' I even tried to reboot, and all, all over the same thing...
I want to add, that, i remember that on that date ~20. February 2017 When it always return to that date/time over and over again, that on that day, i re-flashed the ROM, because my system started to crash from itself... So by flashing the ROM from CWM only, it works fine, and didn't lost any app, i mean didn't needed to install all apps that i am using...
*The phone is running fine if i don't use it non-stop, i mean if i start to go in my settings, and click too many times, it will just reboot and go back on that date/time state... I am using it only for calling and sending some SMS. Nothing else...
*My 70% of the apps, we're on the SD card moved, trough the Link2SD app (root), so i cannot uninstall the apps that are here, neither i put the SD card IN.... This doesn't matter. But another thing is that, if i for an example took a Photo, add contact in the phone book, send SMS, call someone, after restarting the phone that data/info/sms/photo is not there... It acts like it is in the cash memory, something like that... It just all looses and starts over again, from the same date, and time.
My opinion is that the phone, somehow... that the "NAND" memory chip is death (just an example)... Something like the BIOS CMOS battery on the PC's, that is dead, and cannot keep the changes, after rebooting the phone, so it goes back on that time when it was last time in "good condition".
I really don't need the phone anymore, but it would be nice for an backup option to have it fully functional.
I want to hear your opinions, did you ever met a problem like this before? If you did, what did you did/fixed it?
For me this is kinda funny, because i never had/saw a problem like this before. So i don't know should i cry or laugh around... XD
Thanks.

How to flash persist.img in this phone?

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.