Database Info

Fighting a lost cause?

I've got a rooted (Super SU, but the original root manager was Superuser) LG C800 that I was having problems with. To be specific, I installed some apps on to the system. Some of these apps would be Titanium Backup for root, Avast Mobile Security, ROM Tool Box Lite, Super SU, and a quite a few others. From day one they seem to be kicked right back to my S.D. card, but not all at the same time, and some would stay on the system. I read where I should move the apps back to my S.D. card and try to re-install them on the system minus the data. When I did, the phone went nuts. Now it stays in a restart mode but never fully boots up. Can I salvage it, and if so, please tell me how?! I have tried the hard reset/recovery boot where you hold down the power button, volume, and a few other keys, but it did not work. I'm a broke college student and can't really afford to buy a new phone. I used this one for everything including tethering it to get my assignments done at home and turned in on time. Please help! I'm open to suggestions....... My phone will be completely off. When I plug it into my computer, via U.S.B., it automatically turns it on whether I want it to be on or not. Then it starts off in "reboot recovery" mode, will boot all the way to the point to where the home screen would normally turn on, but then it starts in that "boot loop" all over again but never fully boots up before going back to the beginning of that "boot loop" yet again. I can't even get it to register on my laptop as being plugged in. The reason I took the apps I placed on the system off was because sometimes when I'd re-boot the system the apps would be on the system and sometimes back on my S.D. card without my involvement of any kind other than rebooting my phone. Is completing a Nandroid recovery or re-installation of my ROM even possible with my computer no longer recognizing it as even being plugged in? From what I can tell it won't be. Am I fighting a lost cause or is it salvageable?
Rooted myTouch Q 4G, a.k.a. LG C800
I believe it has a 2.3.4 GRJ22-perf, and then something like 2.6.35.7? I can't remember off the top of my head, and I can't pull it up on my phone anymore or else I'd double check.

Have you tried booting into recovery?

(More about my phone from the original post) Honestly.........I'm not what you may consider technologically inclined. I have however done about as much research online concerning this matter as any one person can do. I've looked it up on all major sites, and many smaller ones too, that post remedies for phone, or "human" if you'd rather, malfunctions. They all talk about still being able to reach a home screen or doing the whole holding the power and volume decrease buttons until I "reboot recovery" screen appears (if that's what you're referring to as doing a recovery reboot as). Don't forget the one where you hold hold the power and volume decrease buttons along with the "A" and "F" keys as well. I even tried one from here where you're supposed to push the genius button after the Android figure leaves the screen. My phone won't allow me to do either. Basically if it's online, I myself, or this girl that's been staying with me, have tried it without any results. On the initial boot the Android figure and the box with the arrow coming out of it show up and it boots until just about the point that it use to switch over to the home screen and it will start the whole "boot loop" over again. The thing is though that the Android figure and box aren't there any other time after the first boot, and with every boot loop it makes after that, the time is reduced from the beginning of the loop to the end when it starts all over again. The phone won't shut off unless I remove the battery and even though my laptop no longer recognizes the device, when I plug my phone into it or another power source and it's off, it automatically turns itself on and begins that boot loop all over again. there is one thing I have yet to try. I read on one site where I could download a custom ROM on my S.D. and then try reboot it, but it never makes it to the point in which the files on my S.D. card are ran, much less scanned. I am still 100% open to any and all suggestions in the diagnosis of this issue. I may record and place a video on one of the more popular "tube" sites to better show or further explain what's happening and then come back on here to post the link?! Feel free to reply back if it's possible you can help before I'm able to complete that later this evening. And thanks for any and all help in advance to everyone.

[Q] Binary Reset via PC???

Somehow I have managed a binary count of 4, and I need to reset it to 0. For some reason my phone gets to the screen where it says "4G lte" with all of the rings expanding and stops, it doesn't boot any further, it just sits at that screen forever in a loop (I feel like this could be due to the binary count?). But anyways, since I don't have access to my phone I cannot use Triangle Away, so I was wondering if someone could please tell me how to reset it from the computer or in download mode. Thanks!

VerizonS3 said:
Somehow I have managed a binary count of 4, and I need to reset it to 0. For some reason my phone gets to the screen where it says "4G lte" with all of the rings expanding and stops, it doesn't boot any further, it just sits at that screen forever in a loop (I feel like this could be due to the binary count?). But anyways, since I don't have access to my phone I cannot use Triangle Away, so I was wondering if someone could please tell me how to reset it from the computer or in download mode. Thanks!
Click to expand...
Click to collapse
While I can't answer your specific questions in regard to the count..
It might be worth it to hook up to a PC with the USB cable and check out the logcat. Typically in a boot loop it'll be trying to do the same steps (and failing..) over and over again. Might be some very useful information there and the problem could be totally unrelated to what you suspect it is.
Another super ez option would be to simply restore your last known working nandroid backup..

CrustyMcLovin said:
While I can't answer your specific questions in regard to the count..
It might be worth it to hook up to a PC with the USB cable and check out the logcat. Typically in a boot loop it'll be trying to do the same steps (and failing..) over and over again. Might be some very useful information there and the problem could be totally unrelated to what you suspect it is.
Another super ez option would be to simply restore your last known working nandroid backup..
Click to expand...
Click to collapse
Unfortunately I do not know how to use the logcat what-so-ever, so I wouldn't know what to look for, the loop only begins when it gets to the verizon rings, it's not restart the whole bootup, it just gets stuck at the last boot animation and never displays the homescreen, if I am making sense
As for restoring the most recent nandroid, my phone for some reason will also not boot into recovery mode, I can hold Volume Up+Power+Home to attempt it and it will show the Samsung Screen and the "Recovery Booting..." in the top corner, but the recovery mode never actually comes up, I just have to let go and then it restarts itself normally and gets up to the Verizon animation and loops there

Need assistance/info with bricked shield tablet

Received a shield tablet through a promotion my company was doing with nvidia, decided to try it out. (pointing this out ahead of time to let the 'just return it' people know that I cant and am stuck with it.) upon finally deciding to boot it up a couple months later, it booted into the bootloader menu instead of booting like normal. then when choosing to boot would boot into a very stripped version of android with few apps, tegra services repeatadly crashing, no app store/play/etc . I wanted to have the proper out of the box experience nvidia intended, so decided to hunt down a stock factory image to flash to it to just resolve the issue and start from scratch with my new tablet. was able to flash recovery/boot/system/userdata/etc via fastboot. upon restarting, screen went black and wouldnt start. plugged in to computer, device manager says "APX" and that's it. with unknown device/driver icon. if I power it off all the way and plug it back in it just goes back to saying "APX" with a "?" in device manager.
how can I get it out of this mode and booting so I can finally try this thing out? have tried diff combos including bootloader/recovery mode button presses at boot time and nothing works, goes back to the same thing. I've also seen mention about nvflash and some other things when looking into this, but nothing solid on where I get the program, how im supposed to use it to fix my device.
Thanks

Replaced screen, not booting

Hey guys,
just replaced my screen by myself and it isn't working. It boots and the screen lights up for a few seconds but thats it. So it seems like I ****ed up somewhere. :/
Now I've got some questions for you guys.
1. What could cause this error? Since it's already not working I don't mind taking it apart some more and trying to fix it.
2. Do you think if I send it to the support from OnePlus they will take a look at it?
3. The whole reason I did this was to get my data back. Is there any way to access the data on the phone without the touchscreen? I encrypted it using CynogenMod. USB-Debugging is enabled.
Thank you so much guys, I'd really appreciate some help. This **** is really tearing me down since it was a lot of work.

I did this on my own phone but Idk about OPO. If you use the power+voldown method to boot into recovery (yes ik nothing on screen) then connect a usb and see what happens
If you power it on, wait 5 mins then call it and if the phone rings you should be able to rule out the display and speakers and storage, obvs if the display is still not on at this point it is probably the display.
you can also adb from recovery and or fastboot so you should be able to see it in there if it is still working (make sure you change the phone for a decent amount of hours before you do any of these) If the display is dead its likely its been on for the last day and dead

Sorry for the late answer, really appreciate your help!
So if I connect the phone to the PC (tried it in recovery and in normal mode) windows detects the phone under "Devices" but sadly if I type in "adb devices" in cmd it doesn't detect the device.
But still, windows is detecting the phone so it seems to still function. I booted into recovery and I could use the touscreen and the lower buttons. I couldn't see anything but it was vibrating whenever I was using the touscreen. So it seems like only the display part is broken.
Can't call the phone since it's fully encrypted so I need to type in a password before booting anything (recovery, normal mode, ...)
I'll try to contact the vendor of the display and see what he has to say.
If anyone got any more tips I'd appreciate them. I'm a pretty big noob so I even appreciate "common sense" tips.

I know this may be a "common sense" thing to say, but double check your connections. Sometimes the connectors aren't made properly and a pin could be covered so you can try connecting and disconnecting several times to see if it clears up.
Since the touch screen was registering and vibrating, then it could be the backlight that's broken. Try holding a flashlight at an angle and see if you can make out anything on screen. If it's the backlight, then you can probably back up your data in case your phone does end up breaking.

reconnected everything multiple times and also tried the flashlight trick. sadly with both no luck
but something good:
adb recognizes my phone in "recovery"
bad news: no commands work, most likely because the phone is encrypted. if I enter a command nothing happens, it looks like its loading forever.
any ideas?

Hey!
I also had the same problem after I replaced OPO's screen about one year ago. The replacement screen was from ebay.
I could see the Cyanogen logo but after a few seconds the screen became black. Booting into recovery mode worked well.
On the video also ROM boots well but the screen stays black.
https://www.youtube.com/watch?v=VcWDCJIkPKQ
Eventually, the screen was defective and I returned it and bought new one.

Question Stuck in recovery mode PLEASE HELP

I thought this would be a good place to ask this.
A few minutes ago, I accidently pressed the volume up and down buttons for a long time on my zflip 3 and it booted into the recovery menu. Now this normally wouldn't be a problem.. if my power button wasn't dented in.
I refused to fix it due to the sheer cost of the fix and could turn my display off by double tapping. However, this means that I have no way to exit recovery mode. I tried using ADB on both my bac and pc (using usb 2.0, 3.0, and c on my pc and c/thunderbolt ports on mac).
My phone however would not connect of show up under devices, and I am suspecting it is because I have done something to the debugging settings. I let the battery run out and it would just boot back into the recovery interface once charged up. It even once went to a light blue screen that said something along the lines of how a custom os can cause major problems.
I am a noob at phone stuff and I really don't know what to do. I have a bunch of photos of my grandma who passed away last year and they aren't backed up to google cloud. I really need any help I can get. Thank you.

Hi, provided that you have already
- enabled adb debugging;
- installed adb.
Now you have to
1. enter fastboot mode;
2. in adb type
Code:
fastboot erase recovery
then, reinstall recovery if you want to.

s.0105._j said:
I thought this would be a good place to ask this.
A few minutes ago, I accidently pressed the volume up and down buttons for a long time on my zflip 3 and it booted into the recovery menu. Now this normally wouldn't be a problem.. if my power button wasn't dented in.
I refused to fix it due to the sheer cost of the fix and could turn my display off by double tapping. However, this means that I have no way to exit recovery mode. I tried using ADB on both my bac and pc (using usb 2.0, 3.0, and c on my pc and c/thunderbolt ports on mac).
My phone however would not connect of show up under devices, and I am suspecting it is because I have done something to the debugging settings. I let the battery run out and it would just boot back into the recovery interface once charged up. It even once went to a light blue screen that said something along the lines of how a custom os can cause major problems.
I am a noob at phone stuff and I really don't know what to do. I have a bunch of photos of my grandma who passed away last year and they aren't backed up to google cloud. I really need any help I can get. Thank you.
Click to expand...
Click to collapse
How about rebooting to system using volume buttons?