Related
Hi all,
Firstly i hv learned a lot from xda developers and been coming to these forums for over a year now, but this is my first time posting here so apologies if my question is in the wrong section, guide me to the right forum and i will move to it.
I recently bought a used Pantech Sky Vega A800s, very nice device for its cheap price imo
but i have been having some problems with my phone.
the first is that battery drains very fast, but i figured it could just be a degraded battery so i chose to ignore it for now.
i was aware of korean phones sms limit problem (80 character limit) so after buying my phone i started searching for its soloution and came across various guides including installing 3rd party sms apps and rooting the phone to replace original sms app.
3rd party apps didnt work for me so i chose to go with rooting method.
now the real problem began,
i followed tons of guides and used many tools to root my phone but none of them worked for me, the process would finish but phone will always restart with normal unrooted os.
finally i was able to root my phone using a desktop pc app called VROOT.
now i tried to install CWM on this phone but after trying several methods and using many tools still i am unable to do it.
so far i have tried,
> using automated CWM batch scripts (from official Sky A800s forums/XDA threads)
> manually using FASTBOOT FLASH RECOVERY RECOVERY.IMG in fastboot mode
> trying FASTBOOT OEM UNLOCK and repeating above steps
here is what happens every time, (doesnt matter which of the above methods i use)
Phone reboots to fastboot if not already in fastboot
cmd window shows successful writing of recovery image
cmd window shows reebooting to recovery mode
now the phone reboots, screen turns black-ish for a few seconds, then it reboots again the logo shows up a couple of times and then it continues on with normal boot process into the stock os.
i have been digging around the internet for a soloution and so far i have found no soloution.
according to my understanding, all the tools and scripts i found on the internet were either for stock rom 2.3 or 4.0.4
while my phone is updated to stock 4.1.2 via official update, so maybe this is the reason i was unable to root my phone the regular way in the first place and i had to resort to using VROOT.
now maybe 4.1.2 is the reason i cant install/boot into CWM.
i really need recovery on this phone bcz i want to flash the MIUI V5 rom for sky a800s
also there is another major problem i which i think might get solved by installing a custom rom,
problem is that my phone sometimes will work fine for hours with normal texting and calls, but randomly sometimes it will crash upon recieving a sms with this mesage "YOUR PHONE WILL RESTART DUE TO AN ERROR WHILE RUNNING APPLICATION. PLEASE DO NOT REMOVE THE BATTERY TO PREVENT DAMAGE TO YOUR PHONE"
then phone restarts but immediately upon entering the OS it crashes again with same message. this continues untill i remove the SIM CARD from phone, leave it out for an hour or more (meanwhile the phone runs fine without sim), after sometime i can put the sim back in and it works fine now.
i have observe this happens randomly upon receiving a text message.
another thread on xda developer said to wipe data and wipe cache (reset ro factory) will solve this but it didnt work for me
thank you for being patient enough to read through my post
i just wanted to include all about my problem and all i have tried to solve it so far so you people can help me better with my problem.
any help with getting CWM working or solving the SMS CRASH problem is needed.
anyone!
bump!
so nobody will reply and i cant post my prob to official pantech sky thread bcz i hv less than 10 posts
I guess i will just have to make 10 posts to be able to get help from the official pantech sky thread then,
6 more posts to go
Hi there
5 more to go
6th post now
post numnber 7
# 8
divergent asyssli >> stupid captcha
10 posts completed
off to official pantech thread now
Bye Bye
URGENT HELP NEEDED -- "com.android.systemui has stopped" bootloop -- Verizon LG G3
I apologize in advance if this is posted in the wrong section, but I need some urgent help with my phone. I posted in this section hoping to get some quick responses.
I have a LG G3 with rooted stock 4.4.2 rom running xposed.
So I pulled my phone out of my pocket today only to see the Verizon boot logo in effect. I was thinking "that's weird, guess my phone needed to reboot? Strange." But the only problem is it never stopped. It will only boot up to the lock screen and occasionally it will display an error message telling me the systemui has stopped. Then about 10 seconds later, it reboots itself. It continues this process until I pull the battery.
I've tried booting into safe mode, no luck. It doesn't even actually boot into safe mode (it doesn't say safe mode in the bottom left corner.) Then it just reboots again,
I tried wiping the cache, no luck.
I don't want to just do a factory reset because that hasn't seemed to help anyone else with this issue as far as I've seen. I have not found any helpful information on how to fix this problem.
And no, I haven't changed anything lately that could have messed it up. A couple days ago I cut off some wakeup paths for Google Play Services via Greenify, but I don't think that's the cause of the problem.
My question is, what do I do? I feel lost on this subject. Normally I've always been able to diagnose problems on my own, but not in this situation.
I have all my apps and data backed up to Titanium Backup on my SD card if that's of any relevance.
Any suggestions?
If you can go to CWM just flash abother ROM like android L
Sent from LG L3 via XDA App / Wyslane z LG L3 przez aplikacje XDA
Recten said:
If you can go to CWM just flash abother ROM like android L
Sent from LG L3 via XDA App / Wyslane z LG L3 przez aplikacje XDA
Click to expand...
Click to collapse
How would I go about doing that with a device that won't boot up?
I'm not familiar with flashing ROMS and things like that.
Ideally, I'd like to be able to fix it and keep the phone the way it was. I understand that may not be possible though
Helmetheadog said:
I apologize in advance if this is posted in the wrong section, but I need some urgent help with my phone. I posted in this section hoping to get some quick responses.
I have a LG G3 with rooted stock 4.4.2 rom running xposed.
So I pulled my phone out of my pocket today only to see the Verizon boot logo in effect. I was thinking "that's weird, guess my phone needed to reboot? Strange." But the only problem is it never stopped. It will only boot up to the lock screen and occasionally it will display an error message telling me the systemui has stopped. Then about 10 seconds later, it reboots itself. It continues this process until I pull the battery.
I've tried booting into safe mode, no luck. It doesn't even actually boot into safe mode (it doesn't say safe mode in the bottom left corner.) Then it just reboots again,
I tried wiping the cache, no luck.
I don't want to just do a factory reset because that hasn't seemed to help anyone else with this issue as far as I've seen. I have not found any helpful information on how to fix this problem.
And no, I haven't changed anything lately that could have messed it up. A couple days ago I cut off some wakeup paths for Google Play Services via Greenify, but I don't think that's the cause of the problem.
My question is, what do I do? I feel lost on this subject. Normally I've always been able to diagnose problems on my own, but not in this situation.
I have all my apps and data backed up to Titanium Backup on my SD card if that's of any relevance.
Any suggestions?
Click to expand...
Click to collapse
Flash the twrp recovery: http://dottech.org/172848/how-to-install-twrp-recovery-in-lg-g3-for-verizon-guide/
Then boot to the recovery and go to Advanced---> Fix Permissions-->Swipe to confirm.
Hit thanks if i helped you!
Has anybody been running into their phone rebooting with Marshmallow? Mine is still doing it. Already tried re flashing and clearing cache.
Treizez34 said:
Has anybody been running into their phone rebooting with Marshmallow? Mine is still doing it. Already tried re flashing and clearing cache.
Click to expand...
Click to collapse
I am having the same issue. Random reboots.
I already install the 6.0 three times. one sideload and two fresh installs (full wipe + factory images). I even tried to roll back to lollipop and then update again.... same problem =(
device:
Nexus 5 - 32gb international + moto360
Sorry for my English.
I have the same problem with the Nexus 5 32GB D820.
Marshmallow clean installation ran smoothly yesterday, today began to randomly reboot.
I tried to make a factory reset and left in a bootloop.
I had to re-flash the factory image.
Let's see if it happens again.
Likely defective power button
My nexus 5 32gb is also randomly rebooting on android 6.0
The same problem with D821 16 Gb. 4 times clean installation. 1 time step-by-step installation for each part of factory image - no result. Random reboots.
There is no random reboot software bug, only faulty key
GR0S said:
There is no random reboot software bug, only faulty key
Click to expand...
Click to collapse
What do you mean with faulty key? Faulty like hardware or faulty like software? Cause I have my Nexus for 1,5 years and had never problems with power button at all. The problem comes only with Marshmallow.
---------- Post added at 07:22 AM ---------- Previous post was at 06:47 AM ----------
So, there is no full restart. If you press the power button for 10 seconds, the phone will restart and you'll hear a little vibration and see "Google" logo, after that Marshmallow animation appears. Faulty key can only cause full restart effect. But in Marshmallow I have only the shell restarts, i.e. the phone restarts with Marshmallow animation (not with vibration and "Google" logo) and this lasts 3-5 seconds. This is definitely software bug.
Are we talking about M, flashed with fastboot, and almost no user apps installed and no mods (root, custom kernel, etc)?
Because if we are, there are no random reboots.
Sent from my Nexus 5 using Tapatalk
beekay201 said:
Are we talking about M, flashed with fastboot, and almost no user apps installed and no mods (root, custom kernel, etc)?
Because if we are, there are no random reboots.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Exactly. Flashed with fastboot, no mods, no root, no any customs. Only user apps. But you are right. I'm testing all my apps and I've found 2 weather apps. They probably caused the reboots. I'm not sure about it, cause I'm looking into all my apps.
its not a defective power button.
I roll back to lollipop and the random reboot stopped.
I did another try with marshmallow, this time with sideload installation and full wipe after. At the beginning i get two random reboots, but now it seems to be ok. no more random reboots.
SOLVED. The problem was caused by Weather Live application (https://play.google.com/store/apps/details?id=com.apalon.weatherlive). With first installation of Android M I noticed that the app shows error message. Now, when I know cause and effect, I read feedbacks in Play Market and see other people reports crashes in Marshmallow with this app. So, if you have random restarts in Android M and Weather Live app installed, then try to delete it and wait if system will be stable.
dr_stevens said:
SOLVED. The problem was caused by Weather Live application. With first installation of Android M I noticed that the app shows error message. Now, when I know cause and effect, I read feedbacks in Play Market and see other people reports crashes in Marshmallow with this app. So, if you have random restarts in Android M and Weather Live app installed, then try to delete it and wait if system will be stable.
Click to expand...
Click to collapse
I found the same issue. I'm a registered user of Weather Live, but I've found that the app is causing numerous crashes after I upgraded my Nexus 5 to Android 6 ( Marshmallow). I ran a bug report and searched it for 'FATAL EXCEPTION:', I can see that everytime there is a crash, one of the threads affected belongs to Weather Live. What I then get is a restart of the User Interface, so it goes into the 'android' animation you normally see on boot. The phone stays up because the System Uptime is not reset.
I've uninstalled the app for the moment to see if that cures the issue.
i am experiencing random reboots with my Spice Dream Uno and ended up in this forum while searching for my cause. first i thought its my device got hardware issue but it never happened before in lollipop or kitkat. it seems just like a possible hardware fault too and phone will be in bootloop , then cant even power on the display(backlight flluctuates,with black screen). when i pull the battery and reinsert after few minutes the phone starts normally. seems like Marshmallow has critical campatibility issues with some applicationsThe crash never happens in same application for me.And i have no roots ,customs etc..Came to 6.0 via OTA from lollipop.
My device dont have any issues upto now(its been an year).
I've been noticing it with a very minimal base of packages. Seems to only happen shortly after waking from deep sleep so I highly suspect doze. The phone will be fine... you set it aside... it enters doze deep sleep... phone wakes, you unlock... then bam, reboots, and enters boot loop at the Google splash screen. I've already done a factory reset, will be attempting a fastboot reflash with the new November system image today.
I got a Moto G First generation (X1032) with lollipop 5.1
A few weeks ago I had the option to do a update, after I installed the update my phone was restarting and it now gets stuck in a bootloop. I can still come to the bootloader.
When I connect my phone to my computer it won't install, so I can't acces my phone.
My phone needs to startup in order to install it, but that's not possible because it will get in a bootloop.
My phone was rooted, but I fully unrooted it before I did the update.
Is there anyway to survive my phone? Already tried factory reset, but that won't do.
Thank you for your time.
Davoz said:
I got a Moto G First generation (X1032) with lollipop 5.1
A few weeks ago I had the option to do a update, after I installed the update my phone was restarting and it now gets stuck in a bootloop. I can still come to the bootloader.
When I connect my phone to my computer it won't install, so I can't acces my phone.
My phone needs to startup in order to install it, but that's not possible because it will get in a bootloop.
My phone was rooted, but I fully unrooted it before I did the update.
Is there anyway to survive my phone? Already tried factory reset, but that won't do.
Thank you for your time.
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
My guess is that you need to flash again the stock ROM.
You ended up into a bootloop because you may changed some system files, and for each update the installer is checking that.
There are two situations:
- The update process will went good but you will be stuck into a bootloop
- The update process will be interrupted directly from the recovery
Here is a good guide about how to get back to stock.
Good luck!
I've got a Vodafone UK version SM-G920F that has recently started to freeze, crash and reboot constantly.
I managed to back up my data and perform a factory reset from the Setting page, but it crashed 10+ times during the install process (would freeze at various different stages, either rebooting on its own, or requiring a Vol Down+Power reset)
I'm now on a fresh install, but it's still rebooting constantly. I managed to use it like normal for an hour today, but right now it's just rebooted 3 times and won't even get past the Samsung loading screen without several Vol Down+Power resets.
What other options do I have? And is anyone aware of a known hardware issue that could cause this?
I was considering flashing a different ROM, but I'm scared it would reboot during the process and corrupt something...
robjg said:
I've got a Vodafone UK version SM-G920F that has recently started to freeze, crash and reboot constantly.
I managed to back up my data and perform a factory reset from the Setting page, but it crashed 10+ times during the install process (would freeze at various different stages, either rebooting on its own, or requiring a Vol Down+Power reset)
I'm now on a fresh install, but it's still rebooting constantly. I managed to use it like normal for an hour today, but right now it's just rebooted 3 times and won't even get past the Samsung loading screen without several Vol Down+Power resets.
What other options do I have? And is anyone aware of a known hardware issue that could cause this?
I was considering flashing a different ROM, but I'm scared it would reboot during the process and corrupt something...
Click to expand...
Click to collapse
Maybe a battery issue?
a friend just gave me his very same model phone with the very same issues.. if I find out anything I'll tell you here, or if you solve it first please write down what you did.
Thanks Vibbuz.
I've been trying to download a stock firmware to flash via Odin, but download speeds from Updato are really bad.
So I managed to flash a firmware after installing Odin on a Windows laptop (painful trying to get it to work on my Mac)
Firmware installed OK, but after boot I was getting a constant "com.sec.epdg" pop-up box that wouldn't let me use the phone at all. Not sure if that's due to the tsar3000 firmware?
Wiped the cache and did a factory reset after booting into recovery, and now it's stuck in a boot-loop again (95% of the time it hangs at the Samsung logo animation)
Just tried using SamFirm v0.3.6 to find the correct file. Downloaded a 4gb file, but several attempts to extract only gives BL, CP, CSC files but no AP (throws up an Unknown Error during process).
So still stumped!
Yet another update. Left Updato running overnight and downloaded a firmware.
Flashed it with Odin, claims to have succeeded but phone then reboots and hangs at "Erasing" stage (Android logo is spinning, then stops)
I'm starting to think it's pretty broken...
I've been having this exact same issue since June. If your phone happens to boot try activating power saving mode (to reduce cpu speed) as soon as possible.
It seems that doing that diminished the frequency in which my phone rebooted. If it also helps you it might be a faulty battery that can't provide enough voltage. (I'm not 100% sure on this part though, just thought of it because of the apple batteries drama)
Please post your results! Looks like a lot of people are affected by this and it would be great if we could find the cause of the problem.
I just read your thread actually! Sounds very similar to mine.
I've got nowhere. I don't think it's hard-bricked as I can still access Odin mode on the phone, and sometimes boots to Recovery, but it freezes and various different points and is currently unusable (either freezes at Samsung logo, "Erasing" part after installing firmware, or once it started to run though new device setup then froze).
Went ahead and bought an S8, but still want to fix the S6!
robjg said:
I've got a Vodafone UK version SM-G920F that has recently started to freeze, crash and reboot constantly.
I managed to back up my data and perform a factory reset from the Setting page, but it crashed 10+ times during the install process (would freeze at various different stages, either rebooting on its own, or requiring a Vol Down+Power reset)
I'm now on a fresh install, but it's still rebooting constantly. I managed to use it like normal for an hour today, but right now it's just rebooted 3 times and won't even get past the Samsung loading screen without several Vol Down+Power resets.
What other options do I have? And is anyone aware of a known hardware issue that could cause this?
I was considering flashing a different ROM, but I'm scared it would reboot during the process and corrupt something...
Click to expand...
Click to collapse
Does it have twrp? Try a non stock ROM and kernel
So did anyone manage to find an issue in this rebooting. I am having the same issue.
damir_nis said:
So did anyone manage to find an issue in this rebooting. I am having the same issue.
Click to expand...
Click to collapse
Hi I have same Problem I send the my s6 for repairmen that Saied me this problem related to mobile Hard drive.
I didn't believe it and try some official rom and a rom from Philippine GLB solve my problem for 3 M/o but now developed as same problem whitout any successful rom installation.
I think this problem from incompatibility google play store version to my rom. please flash a custom rom without google apps and immediately after installation turned off data and Wi-Fi internet after 2 day whit sim card whit out any change in setting can use it.
Hello,
anyone found some kind of solution? Happened to me also - freezing, restarts and then my S6 stopped working.. Sometimes I can boot to recovery menu, sometimes it boots up to android (and then freezes again), but the chances are almost non existing. Service man told me the same thing as @ghasemzm - eMMC failure. Yes, it is completely possible, but i don't wanna believe it, because they only tried to reflash the rom. I've made some "google research" and found that there were some issues in power IC on S6/S6E. Could this be related to it?
ghasemzm said:
Hi I have same Problem I send the my s6 for repairmen that Saied me this problem related to mobile Hard drive.
I didn't believe it and try some official rom and a rom from Philippine GLB solve my problem for 3 M/o but now developed as same problem whitout any successful rom installation.
I think this problem from incompatibility google play store version to my rom. please flash a custom rom without google apps and immediately after installation turned off data and Wi-Fi internet after 2 day whit sim card whit out any change in setting can use it.
Click to expand...
Click to collapse
Will test the theory and let the group know.
So i have installed philipines latest update 6.0.1 i think with PIT file provided on Sammobile.
I have tested it for a day with normal ussage like i set up every other phone and it still continued restarting.
Figured out let me test with no google account signed in and the phone is working perfectly. For a full day.
So i dont know what the problem is but i will try again with google account tomorrow for a day see what happens.
After that will install 7.0.1 uk update with PIT file for it and test with that.
I have the same problem and I am quite sure that it is the mobile hard drive.
I tried to use F2FS but didn't find a working rom for that.
Samsung refused repair because of root.... Never Samsung again!
same issues here - any solutions found? My best guess is hardware fault...