so ive had my s2 for a couple years, i wound up dropping it the other day, threw it into a constant reboot.. seemed like a power button issue. i tinkered with that a little but little results. i was able to get it to boot up and did a twrp backup of everything. but since then ive been unable to get it to run for anything more then that, IF even that long. a factory reset aswell locks up just after app optimization. its like.... it get to a certain point on the phone and locks up.. i was able to pull my misco-sd out and get the files off it. but i'd like to get to my internal storage as thats where my camera was saving eveything too.. when i switched roms earlier this summer it must have used different save to locations.. its my photos are what im after.. booting into recovery i can see all my files, plugging in and trying to mount yields no results.. im going to try on my laptop aswell but on my pc its doing nothing.. Im curious if anyone has had the similar situation , near that, or better luck with CWM.. any other info or insight would be awesome.. much thanks..
Related
Ok, this is starting to get incredibly frustration. This morning, i started the download for puzzle quest 2. the game downloaded at a normal pace, but has been stuck for hours at "installing application"
I really have no idea what to do. I've tried turning off and on the phone, taking out the battery. i've even managed to get the download to restart several times. but..its still there. and it still gets stuck at "installing application".
any ideas?
the only option left that i can think of is a hard reset...and i don't want to do that.
also, i've been looking around and have yet to find anyone with this same issue. which is particularily unnerving. i have a samsung focus with a pny class 4 8gb sd card.
my little sister had this. the way i got it to work was to put the phone on charge, do the download over wifi, and make sure the screen doesn't go to standby. it appeared to work for her device. though she has a mozart. try it and let me know.
can you tap-hold on it and cancel/delete the install and try it again?
what i ended up doing was just wait long enough and i guess it managed to install.
still though. the issue is bothering. i'm beginning to suspect that my sd card has some errors on it. perhaps some bad clusters? i really don't know about those sort of things.
what was the app and how big was it? the app my sister was trying to install was guitar hero 5... it's massive to download... massive to install.
puzzle quest 2. its a pretty big one as far as i know.
i'm trying to dl guitar hero now. we'll see how long it takes...
[Warming up]
I've been having problems lately trying to figure out the problem..
So, first i suspected the SD card, doesn't seem like my original 16GB card was the problem, because i bought 2 new 32GB Micro SDHC cards already, same problem..
[Now the problem]
80% of the times when i reboot and go into recovery and flash a couple of roms, or reboots in general, i for the most part get stuck in Bootscreen, if i try to wipe Cache and Dalvik-Cache, it sometimes solves the problem and 20% of the times i can get into the system, the other 80% of the times that i actually succeed into getting the rom to load up, i mostly get stuck there aswell, untill it reboots the phone, and im back at the imfamous bootscreen...
So, i've figured, is there anyway for me to log the stuff that is happening at the boot screen? because im curious to what the problem might be..
[The things i've done already]
Everything is formated as EXT4, and has been so since Mike introduced it with his rom..
i've tried Mikes rom, Unity, Honey roms, Coredroid, RCmix, all the same on all of them.
I always wipe my phone fully before i boot the rom, mostly with Mikes Super Wipe Script, but sometimes with the wipe zip mentioned from the Rom Dev explicitly telling me to use that..
I always let the rom boot 2 times before i start flashing themes and stuff..
Just going Stock rom doesn't help either, i've tried that aswell, no change.
I've cleaned the phone, from top to toe.. (brushed and cleaned with special liquid)
I've tried different Micro SDHC cards, 1 of em was a counterfeit card, the newest one works just flawlessly, i've benchmarked, checked for errors and even done a Bluff check on it, all working 100% nominal.
CPU running at 998Mhz, just incase..
[Ending]
So, does anyone have any suggestions?.. Does anyone have any way for me to get logs of the Bootscreen (as its a wallpaper, i have no chance in actually seeing what is happening)
Are there any ADB commands i could use to check errors in bootscreen? Any diagnostics tests?
Maybe even a way to refresh the Bootloader with ADB commands?..
ANY help would be greatly appreciated!!
You have some pretty serious problems here. Not that I could diagnose it, but it sounded like hardware related problems to me. Btw, here's the link about boot log you've requested.
http://forum.xda-developers.com/showthread.php?t=1025561&highlight=Boot+logcat
8penned from my blazing fast DHD
drpsyko said:
You have some pretty serious problems here. Not that I could diagnose it, but it sounded like hardware related problems to me. Btw, here's the link about boot log you've requested.
http://forum.xda-developers.com/showthread.php?t=1025561&highlight=Boot+logcat
8penned from my blazing fast DHD
Click to expand...
Click to collapse
Have to agree on that
Do you still have warranty?
drpsyko said:
You have some pretty serious problems here. Not that I could diagnose it, but it sounded like hardware related problems to me. Btw, here's the link about boot log you've requested.
http://forum.xda-developers.com/showthread.php?t=1025561&highlight=Boot+logcat
8penned from my blazing fast DHD
Click to expand...
Click to collapse
Thanks man, very much appreciated!
I'll run some logs tomorrow and see whats up with the phone, i actually got the phone running optimal again with yet another fresh rom flash and it all seems to work, have only restarted the phone 2 times, as im afraid of restarting the phone and get stuck again..
If i do get stuck, im stuck forever, and have to try above mentions i've done before, wipe cache and dalvik-cache, sometimes this works, most of the times it doesn't, and i end up fully wiping a couple of times and reflashing roms untill it works.. (I know this might sound like an SD card problem, but its not, i've gone thrue this with a couple of programs)
Anyway, a thousand thanks for that link, will probably help me quiet some..
madmaxx82 said:
Have to agree on that
Do you still have warranty?
Click to expand...
Click to collapse
Aye, this phone i have in my hands right now has already been in for repairs before and they changed the PCB of the phone, got a new IMEI number and all that..
But i do have warranty left for it, but i have to iron out the problem before i send it in, don't wanna risk being sent back to me and i have to pay lots of $ for their trouble (you know how HTC 3rd party repair centers works).. Plus they might actually scratch my screen some more as they did when i last sent it in...
Well, i have another "minor" problem with the phone aswell, not sure if its my phone or a general new cosmetic problem occurring on phones sent in for repairs, as i haven't noticed it on my earlier phone (Well theoretically the same phone).. Is that when i look at the screen in pitch black moving screens, i can see a distinct line going from Top Right to Bottom Left corner, and the Top Left side of the screen is black, and the lower right part of the screen is black/grey, you can see the difference, but not noticeable when your actually booted up, only in the Bootanimation part is it visible, i've tried different Bootanimations and everyone that has a Black background has this cosmetically problem.
Aah crap, Wall of text..
Haha just gonna add that i installed both apps you mentioned earlier, and the phone feels more like a Dev phone now, but anyway, it all worked great, not sure if it logged anything yet, didnt find anything in the app yet if it does..
I noticed something strange though, Gsensor Enabled, then right before bootup, Gsensor Disabled..
Have no idea why it does that, have no problem with Gsensor though..
Edit:
6 successful restarts!! That's something new!
I have no idea why its behaving this good.. Well time will tell..
hey all,
a strange series of thing happened to my phone this week.
i went to put it on charge and it wouldn'T charge.it seems to have a busted connector..the little contacts are misaligned and one seems to be missing.. this would explain why i cannot access my phone with my laptop. i fixed that not too bad as now atleast it's charging.
Friday night i had a water mishap with my galaxy.it was "dipped" in fast in and fast out but now i noticed it'Sslow to access the sdcard. i take a file manager and browse to SDCARD and it takes like a 1minute before i can seem things.. and even then, it's choppy when i browse down.. one thing thogh it will play mp3s with out issues..
anyboady got an idea? i don't know if it's the connector of the wter that did this as the time line betweenthe two is pretty close.
sometimes it will just reboot if i move the connector while plugged it.. i know theres soemthing going down with this.
i've tried wiping the phone and putting a new rom, but still the same. all else work alright. the phone is under warranty but it's pretty difficult to put it back to stock if i can't access it with a 'puter.
the biggest problem is the access to SDcr being slow.. anybody got an idea ?
Thanks.
I need help figuring out exactly what's wrong with my phone as it has very weird symptoms that seem one-of-a-kind to any problems I've been able to find already posted. Basically everytime I turn on my phone it gets stuck on the load screen with the bar near completion but it won't actually boot and it doesn't loop - to make matters more peculiar once I pop out the battery and try again then the Android guy blasts off and my phone turns on. It always takes me a second try for it to boot but it does so without fail - usually. The rare incidences that I can't get my phone to boot then I can easily get into twrp & after wiping both caches/factory reset it will boot immediately after on the 'first try'. Even worse is that my battery power has been extremely reduced to maybe 4-5hrs regardless of how much I use my phone and it will turn off unexpectedly no matter how much power is left.
the only thing I can think of is that it started soon after I put an external sd card in and tbh I don't quite understand how to take advantage of my extra 16gb yet and the fact that I'm bound to wipe my phone again has kept me from exploring my options
please if anyone can help me save my phone and maybe even link to a thread explaining how to use an external sd card properly. I got confused awhile back trying to understand partitioning and Idk which apps have to stay internal or how to retrieve ones on my sd.
Oh, one last thing, I started using a wall charger for my Samsung batteries and now I can't charge my phone thru the usb anymore without it 'disconnecting' immediately
I was using Paranoid Android before my troubles started but I'm back on stock 4.1.2. I've never posted on xda before so hopefully I did so properly and provided enough background information. thank you in advance to any genius out there who can get me my phone back!!!
[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