Develop Bugs

[Q] Any hope of recovery?

I'm pretty sure I know the answer but I need to hear it from the experts before moving forward. Last week I received a phone call and ignored it. About 30 minutes later I turned the phone on to see who it was and the screen was frozen at the receiving call screen. Strange but ok. Pushed the power button off then on and still frozen. After a battery pull it reboots but doesn't go past the Samsung splash screen. Another battery pull with the same result. I put it on the charger and let it stay that way for a while but no progress. Another battery pull and reboot, though, and now I have a blank screen with the dreaded solid blue light. Can't get into recovery with volume up or down and power...
My phone was rooted and running an older version of Paranoid Android with no issues. I hadn't flashed or really done anything out of the ordinary with it for at least a month. Plus I had just replaced the battery a few weeks ago.
I did take it to the Sprint store and they determined it was a bad charging port. I'm 99% sure that wasn't the issue since I get the same result with a fully charged battery but if that makes them happy then ok. I just received my replacement E4GT in the mail and wanted to see if there was anything I can do to recover some things off of the old phone before I return it. My computer doesn't recognize it and, like I said, I can't get into any recovery. I hate to lose a bunch of photos and videos of the kids but it looks like this is my lesson to start a backup plan. Is there any way I can retrieve anything from the old phone? Thanks for any advice!
tony

In the future use drop box, it can back up all that stuff that we all cherish on your phone.
Maybe jtag?
Pp.
sent from a jellybean filled epic touch.

Ok so if you had Google's sync on then, with auto-instant upload to Google+ then it is backed up in a totally private album. Just log into your google account on your new e4gt. If and only if your lucky, stuff might be there. Or if you had a memory card just plug it into your desktop or laptop and it might just be there.
Sent from my SPH-D710 using xda premium

Thanks for the input. Unfortunately I didn't have G+ sync on and was saving most everything onto the phone instead of the SD card. Stupid mistakes to learn from...
tony

Need Help Recovering Internal Memory Files

Okay so my T-989 has slowly been dying, RRs, freezing randomly, SD card unmounting on its own and not working for days, Power/Lock Button goes haywire and now my screen is shot. So yeah, I battery pulled it, put the battery back in, booted up my phone and the screen stayed black but with two orange lines at the bottom of the screen. I can press the power button, feel it vibrate, the touch buttons light up, I can email myself and my phone will vibrate, so I know it works, I just cant see anything on the screen. I opened it up and EVERYTHING inside was intact, nothing broken, corroded, etc. I dropped my phone in a full cup of soda in January, pulled the battery out quick, put it in a bowl of rice in my pantry and a day later it was perfectly fine. It started with the problems I mentioned above like end of March/Beginning of April. Now I can't exactly say what caused my phone to start messing up, it could have been the soda, could have been that I've dropped it about 1000 times (Mechanics school, working in construction, partying, longboarding, etc LOL) or could be all of the above. So now my problem is, I have a expensive paperweight that still works but I can't see anything on the screen and it has many of my important files in the internal memory. Me being the impatient and hot headed person that I am, i got so pissed when I realized I don't have a phone anymore, I stabbed it... Now its safe to say I only cracked the glass, the phone still boots up, vibrates etc.
I need help recovering my files that are in the internal memory (Pictures/Videos from October till now, saved documents, etc). My computer recognizes my phone when its plugged in but obviously I cant enable Mass Media/Storage on my phone since i cant see the screen. I don't know of any way to bypass that option, and without that my computer won't show me my internal storage. Idk if this'll help, but its on AOKP, with CWM non-touch recovery version 5.x(i know it started with 5 but I don't remember the rest). I've tried mounting storage via recovery but nothing happens, I'm not even sure if I'm selecting the correct option. I don't wanna keep trying to do that cause I don't wanna mess anything up.
And I guess this also means I'll be leaving this awesome community of Devs, friends, fellow nerds and noobs. Idk what my next device will be and I don't even know when I'll be getting one (I'm actually starting to pack/get ready to move from NYC to Dubai). I always said I would only retire my T-989 if I got the chance to switch to a Note 2 but I guess I'm retiring it without a choice.

BUMP. Anyone? My LCD is shot but the phone works (boots up, etc) and i really just need to find away to get my files saved in the internal memory.

You can pull the files using adb on your computer. Check this thread for more info on how to do it.

[Q] Power button not working in my nexus..

For some odd reason my power button is not working. The only way for me to look at things on a screen is to plug it into my charger. I took it to a local phone repair shop and they said it had something to do with the powerflex (something flex, not sure if its powerflex) connected to the motherboard?
I might be searching for the wrong name because I cant find any online stores or ebay selling them. Theres Alibaba but I don't trust that site, it has bad reviews...
any recommendations or similar experiences?
It might be cheaper to get a new phone but I like this one since its rooted to the new Jellybean and I am afraid of losing all my music, shows and stuff. Im not sure if it is on the phone or on the SD card

there is no removable sdcard on gnex.
you can always plug into computer tho and copy all the media over that you would like to save and then easily transfer that to a new device when you get one.
but.... since you are rooted, you can try using one of the Touch2Wake, sweep2wake apps. or see if your current kernel you are using has built in tap to wake and just enable it.
I think there are xposed modules also that give you greater control of the tap/gesture controlled waking of device. keep in mind that you might see some battery loss from these apps and such, but it shouldn't be THAT bad. and will allow you in the meantime to be able to turn device screen on just by tapping the screen or doing a gesture on screen.
I recommend that before you try new kernels or anything, that you backup, both nandroid backup AND backup any media you want to a computer(or get a flash drive and plug right into device using a USB OTG cable which can be found VERY cheap, like $5 online) and just copy over your media to that.
some have had similar issues before and only needed to take device apart(look in YouTube for Galaxy Nexus teardown for step by step) and just cleanih with rubbing alcohol/qtip where the power button makes it contact as there can become.buildup dirt there after a while of constant use.
GOOD.LUCK!
and REMEMBER! BACKUP before doing ANYTHING that might result in messing up something. I cannot stress that enough, and it will save you a lot of stress. if you've got pictures and video you've taken with device you want to save and need a place to backup just get Google+ app and turn on auto backup in settings. and set to backup all current now. you get 15gb free storage for full size pic/video backups with em. just nice peace of mind to know they will always be there in case something goes wrong

Thanks for good guide... :good:

[Q] LS980-Cloudy G3 ROM- TWRP installed&accessible- [email protected] Android is Updating screen

[Q] LS980-Cloudy G3 ROM- TWRP installed&accessible- [email protected] Android is Updating screen
Hello everyone,
I would like to say first of all to the community, thank you for SHARING KNOWLEDGE. That is the key to everyone's success.
Now down to the gritty. My, now, I guess, mess of a LS980. For starters, the phone was running I would say very well considering my abuse. Big overclocks, gaming hardcore, and pushing the storage space hard. I performed a very easy and simple rooting and recovery program installation. If I remember properly, it all started with an app/.apk that sparked my interest with making the phone mine, was Autorec? (red roundish logo?) In some time I decided to install my first aftermarket ROM. I chose and installed without any issues , Cloudys G3 ROM. I cannot however remember the version number. It is by no means recent. I think I installed it last September so maybe 1.0 or 1.2 (sorry so much bad luck with stuff recently) TWRP version 2.7.0.0 is my recovery, and its functional. Unfortunately I do NOT have my apps backed up. I have no space. (just managed to get about 7GB on this PC to try to back them up but there is not external back up option, UNLESS you are OTG cable equipped I am not )
Now, I think, (this has been the state of the phone for about 3 weeks now) this all started to go south when I saw there was a Dorimanx OTA app in the play store. I used his Kernel for as long as I have had the G3 ROM installed. With no problems. So I figure this would be easier for me than button mashing trying to get into recovery mode without popping my screen out the front. LOL Upon using the app, I was informed of an update, I read the included information, and generally knew the deal. I allowed the app to download what it needed and restart and install like a good little computer. And this is where it gets a little grey for me in terms of order and symptoms. I remember checking the status of the install and it read failed! I looked into the reason why, and I was just plain full of junk. I then uninstalled painfully a bunch of rarely if that, used apps and gained back about 2.2GB of space. I ran Dorimanxs app again and let it do its thing and reboot. And again it reported fail! I looked into it more and noticed there were newer Kernels than available on his inter-web. Alpha versions. I located them on my device and rebooted into TWRP mode and selected , then flashed his 10.4.1 Kernel. Everything went fine. Phone reboots, the LG logo is no longer animated, and takes a bit longer to actually boot into a GUI. But it was, luckily.
So now, the phone would be a usable thing for about 3 minutes tops, before a power off, to a reboot. Which at first I didnt notice to be a boot loop. My battery surprisingly went from full to about 6% in no more than 15-20 minutes. I noticed the battery was getting warm like I was running the CPUs maxed under a serious load for a good half hour. Around the range to make someone pull it out their pocket wondering wth? So after the next reboot, power cycle, I jumped back into TWRP mode, and dug around for what I thought was the culprit, Xposed. I was having the worst time with my phone after a major Xposed framework error. I picked up my phone one day and out of the blue the xda framework was telling me that there were so many errors with it and my apps that ran fine, not being installed or activated. Upon looking into it, it was removed from the phone. I belive the order was , stable, 2.5/ 2.6, then I tried the beta 2.7. and thats the version that eventually , either broke, or uninstalled, I think, during those frequent Crashes! I tried to install the previous versions, even going back to the versions that came out last year like 2.4 . But none would install. And the phone grew more unstable in terms of its cooperation with its software. My normal apps and games worked fine. The phone worked the same, the music player, but there were apps that only can work with xposed that I utilize constantly, that were kaput. So I left the phone off. For a while. I had/have no time and really no resources to research and rescue a sunken ship. I come back about two weeks to it and I take a look around in the phones storage and hunt for any kind of recovery and disabler. I found xposed's disabler and flashed it. Same luck as before. About 3 minutes on, then dump.
I dig some more and found a ccc71 back up folder with some hearty backups that I didn't know were still there (no wonder I was always loosing space) and found another xposed installer.zip . I figured well , it didn't make any sense trying to disable something that wasnt enabled in the first place. (thats why I walk away and come back . fresh mind to tackle what stumps me) So I flashed the installed zip and reboot. Same thing, but now it started to loop around one minute. I power down. Found the recovery.zip that was saved on the beater PC and adb pushed it over the the phone. Im not good enough to adb install it. So TWRP'd it and rebooted, and d'oh! Now we just have the motionless LG ball, but flashing blue and green LED. And after about 2 minutes it would black screen, but be on. Not hung or anything. I connected to the PC, it never finds the right stuff but I used adb to verify state. And it said device. It still could communicate and push. I had it dump its debug, surprise! as it flashes that crap as fast as it can up the screen. But Im a PC guy so it was a fun, pause/break over and over till I found something useful. I saw some things that I could recognize like, failed starts, and longer than normal (for a speedy experience) function or call times, but nothing that slapped me with a red flag.
And that ended that nights attempts to fix thanks to the slowest no ram having box I was using to try to learn how to have the debug save to a .txt file on my PC so I could take a good look at the results.
Upon reading forum after forum, I came to something that looked promising, telling me that, that particular boot issue was due to the wrong radio being installed. So I hunted, and hunted, and laaaaaged my arse off and finally found it. Great I thought. Powered up ten or twenty times, finally get into TWRP, tried to flash it. BBBBBAAAAAANNNNT! nope. Downloaded another copy of the file and tried it again. No luck. ( I must say not until roaming around in these forums tonight did anyone bother to mention that you dont flash that radio. You instead have to inject it via LGFlashTool, which I have used before, and its a pain in the butt.
But before I go any farther, make anymore mistakes. I need some help.. I would really LOVE to be able to flash this , slap that, curse its name then hug it and get her working, without having to ditch my 492 apps. If I would have to say goodbye to happy times, I would like to say good riddance to ugly and annoying G3 ROM. I like not flat UI. My phone was depressing me every time I had to do any navigating around inside it. So I would love to go back to KK Stock LG ROM if push came to shove. But if possible I would just like to "repair, and regain access into the phones GUI system". So I could backup my apps. And eventually labor back to OEM Kitkat.
I apologize for the length of the post. But I just dont see the point of ping ponging with partial exchanges of information. I hope I have made my situation clear, and someone knows of someway, I can get my GUI/phone working again. Thanks to all in advance.
"a non functional smartphone, is an oxymoron"

Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart

strangely enough
siggey said:
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
strange thing,
just about 5 minutes ago, the phone, which I left on sitting at the LG screen by accident yesterday after posting the above, changed screens and presented me with the Launcher selection screen.
I immediately noticed that it looked wrong. Like if the resolution was way off. Like an old low res screen, very dull, sort of blurred looking.
I figured what the heck and tapped the screen and it of course did not immediately respond. It took its sweet time , about 30 seconds to show a change. The menu disappeared and a error message along the lines of , android system UI has crashed.
That is not the message verbatim, it was gone to fast for me to take it all in. And now its sitting at the blank powered on and repeating blue/green LED.
I havent done as you suggested yet. I kept getting results from Norway and other places and didnt understand a thing. But I found a TWRP update from Dorimanx, there was a link to it. And now I have to find my version of the OS. And to be clear, were you suggesting doing a re install, basically a file overwrite? And if so, when doing something like that, do you wipe the Dalvik cache ? Or do you just "dirty flash" it?
Thank you ,

I think that your screen is overheated. Never let the phone in bootloop for long time, it can destroy the screen.
About the cache, is better to clean it, but if I remember well the rom installer alredy do this.
_____________________________________Read more write less and be smart

Bricked phone data recovery?

Hey guys, recently my phone updated to Android Nougat 7.0. This was a Google update, no root, no custom roms, nothing. Straight out of the box Nexus 5X. Everything worked fine, until the phone froze.
First, a little backstory. I was watching a Snapchat story and one of the Facebook Messenger chat heads was in the way, so I swiped the chat head away so I could watch the story. The phone froze, so I just figured that Snapchat and Facebook Messenger weren't going to play nice together. I held down the power button until the device turned off, then I tried to restart it. I got as far as the "Google Splash" screen for about 15 seconds or so and then the phone went to black. I've tried fastbooting into recovery mode, and the phone went black every time. I put it on my charger and it showed the image of a battery with a lightning bolt and then cut to black. Pushing the power button had no effect. The phone would no longer even attempt to boot. Occasionally, I can get the phone to fastboot, or try turning on, but then it just dies again. I'm assuming the is a soft brick?
Now for the good part. I called Google and am getting a warranty replacement, but due to poor judgement/paranoia, I haven't backed up any of my pictures to the cloud. I've tried connecting the phone to my computer, but my computer still can't read the device. I keep getting a "device descriptor request failed" error in my computer's device manager. Is there any way to get my pictures and other files off of this phone? I'd like to avoid flashing anything to the phone, because Google is holding a charge on my account for the replacement. If it fails warranty inspection or whatever it is they do, I'd rather not be out $500.
Thanks for any help!

Can you get into fast boot long enough to flash all partitions other then user data?
If you have not tried I would download latest factory image from google.
Edit flashall script by removing -w in there. This will skip the data partition and load all others.
It's worth a shot.
Side note: I personally love cloud backups. I can just log into any other phone now and all my data is back within in your. Photos, apps etc. It is pretty awesome not to have to worry.
If you are not comfortable with this method then you need to do manual backups often.
Update: If your bootloader is locked you are likely screwed from getting anything back. Very first thing I did to my phone was unlock bootloader even if you are not going to root. This does not void your warranty on a Nexus.
Sent from my Nexus 5X using Tapatalk

Adb pull those files. I know it'll take a while because of subdirectories, but it seems to be the easiest option if your computer recognizes the phone.
Sent from my KYOCERA-C6745 using Tapatalk

milan187 said:
Can you get into fast boot long enough to flash all partitions other then user data?
If you have not tried I would download latest factory image from google.
Edit flashall script by removing -w in there. This will skip the data partition and load all others.
It's worth a shot.
Side note: I personally love cloud backups. I can just log into any other phone now and all my data is back within in your. Photos, apps etc. It is pretty awesome not to have to worry.
If you are not comfortable with this method then you need to do manual backups often.
Update: If your bootloader is locked you are likely screwed from getting anything back. Very first thing I did to my phone was unlock bootloader even if you are not going to root. This does not void your warranty on a Nexus.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I haven't touched anything on the phone as far as software is concerned, I guess I should consider this a lesson learned then? The phone doesn't stay on for very long in fastboot. However, today I've been getting the red "low battery" LED notification. I'll charge it up and see what I can do, maybe that'll buy me enough time.
Admittedly, I don't know very much about flashing phones, rooting, unlocking, etc. I've loaded/installed a custom ROM onto my old Nexus 5 and reverted it back to standard Android, but that's about all I've done.
RealWelder said:
Adb pull those files. I know it'll take a while because of subdirectories, but it seems to be the easiest option if your computer recognizes the phone.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
My computer does not recognize the phone. I keep getting a "device descriptor request failed" error. I don't mind how long it will take, I have a lot of vacation pictures and pictures of my new home on there that I'd rather not lose.

If you can't keep it on long enough then it's likely just a lesson learned. Maybe it's some kind of hardware failure. Try the charge. There is an LG recovery option still but that would wipe your data anyway so it's probably pointless.
I would really recommend just unlocking your bootloader with next phone. So you have some options if something like this happens. This wipes your data so best to do as first thing.
Cloud backup is also recommended. You can use other services if you don't want to trust google. Even apps like Mega can do auto backup of Camera folder. Im sure dropbox and others can do the same. I prefer Google Photos.
Sent from my Nexus 5X using Tapatalk

milan187 said:
If you can't keep it on long enough then it's likely just a lesson learned. Maybe it's some kind of hardware failure. Try the charge. There is an LG recovery option still but that would wipe your data anyway so it's probably pointless.
I would really recommend just unlocking your bootloader with next phone. So you have some options if something like this happens. This wipes your data so best to do as first thing.
Cloud backup is also recommended. You can use other services if you don't want to trust google. Even apps like Mega can do auto backup of Camera folder. Im sure dropbox and others can do the same. I prefer Google Photos.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Ill have to toy with it and see what I can come up with. Maybe write Google a little note when I return it and see if they can do anything for me. I think it's something software related. It seems like others are having the same issues I'm having. The phone fails before fully booting up.
The phone's seen its fair share of dust, but I've kept pretty good care of it. Always in a decent case, screen protector, etc.
I'll be unlocking my bootloader as soon as I get my warranty replacement. As well as syncing what I can find on my computer. I'd rather not do this again.
Sent from my Nexus 7 using Tapatalk