I have been reporting the "random reboot during standby" problem in the following thread. http://forum.xda-developers.com/showthread.php?t=1386785
However, the thread was mainly about Screen of Death, and I have not experienced any SOD at all, I think it is better to start a new thread.
Here's the details - on Monday afternoon I purchased my P6210 (brand new, sealed). Started setting it up Monday evening. On Tuesday morning I rooted it, and in the afternoon applied the permission hack to allow writing on external SD.
Wednesday morning, I noticed the first random reboot during standby (on AC) as it woke me up. During the day, the reboot happened at least 3 more times (either on AC or battery).
In the afternoon (still Wednesday), I did a security wipe, and stayed with mainly stock apps. I only installed K-9, a file explorer and few other apps that did not require root as I Superuser was not installed. However, it remained rooted, and the SD write permission mod was not removed by security wipe.
Regardless of the wipe, reboots continued for at least 3 more times by Thursday morning. This is when I returned it to the store for an exchange.
=======
Now unit #2 - no rooting, no permission mod.
I did reinstalled all the apps I had as before, with the exception of the ones requiring root.
The result? Not a single random reboot in the last 1.5 day.
****************
The question is, what actually caused the problem. I see three possibilities:
- faulty hardware in the first unit;
- the rooting; or
- the permission mod. (Note: I didn't recall seeing the reboot until Day 3, after I did the mods)
Unfortunately, I don't know what was actually involved in the rooting, nor the permission mod. Are there any remote possibilities that they could cause the random reboot?
I spoke too soon, just had my 1st random reboot on the new unit. It still hasn't been rooted or modded, only running legit apps downloaded from Play Store. So I guess whatever causing the reboot happens out of the box...
[Update] After having two random reboots in one afternoon, I deleted the last couple apps I installed. It has been reboot-free in the last 2 days!!
One of these apps that I deleted was Dell Voice (may be it doesn't play well with my wifi only tab).
ikeny said:
I have been reporting the "random reboot during standby" problem in the following thread. http://forum.xda-developers.com/showthread.php?t=1386785
However, the thread was mainly about Screen of Death, and I have not experienced any SOD at all, I think it is better to start a new thread.
Here's the details - on Monday afternoon I purchased my P6210 (brand new, sealed). Started setting it up Monday evening. On Tuesday morning I rooted it, and in the afternoon applied the permission hack to allow writing on external SD.
Wednesday morning, I noticed the first random reboot during standby (on AC) as it woke me up. During the day, the reboot happened at least 3 more times (either on AC or battery).
In the afternoon (still Wednesday), I did a security wipe, and stayed with mainly stock apps. I only installed K-9, a file explorer and few other apps that did not require root as I Superuser was not installed. However, it remained rooted, and the SD write permission mod was not removed by security wipe.
Regardless of the wipe, reboots continued for at least 3 more times by Thursday morning. This is when I returned it to the store for an exchange.
=======
Now unit #2 - no rooting, no permission mod.
I did reinstalled all the apps I had as before, with the exception of the ones requiring root.
The result? Not a single random reboot in the last 1.5 day.
****************
The question is, what actually caused the problem. I see three possibilities:
- faulty hardware in the first unit;
- the rooting; or
- the permission mod. (Note: I didn't recall seeing the reboot until Day 3, after I did the mods)
Unfortunately, I don't know what was actually involved in the rooting, nor the permission mod. Are there any remote possibilities that they could cause the random reboot?
Click to expand...
Click to collapse
I had the same problem with mine when I rooted it. I keeped getting reboots so I unrooted it and now I'm just running sock and it been fine ever since, I've had the tab since it was released... I,ve made up my mine not to do and hacks on mine till ICS is out and everything is stable
Sent from my GT-P6210 using xda premium
ikeny said:
[Update] After having two random reboots in one afternoon, I deleted the last couple apps I installed. It has been reboot-free in the last 2 days!!
One of these apps that I deleted was Dell Voice (may be it doesn't play well with my wifi only tab).
Click to expand...
Click to collapse
I'm curious. What were the other apps you uninstalled?
wolverine38812 said:
I had the same problem with mine when I rooted it. I keeped getting reboots so I unrooted it and now I'm just running sock and it been fine ever since, I've had the tab since it was released... I,ve made up my mine not to do and hacks on mine till ICS is out and everything is stable
Sent from my GT-P6210 using xda premium
Click to expand...
Click to collapse
Just to clarify, I haven't rooted my tab to date. In my case, I definitely have the reboot issue without root. In your case, would it be the apps you installed after you rooted, rather than just the rooting itself?
k_t_b said:
I'm curious. What were the other apps you uninstalled?
Click to expand...
Click to collapse
Google goggles. I'm guessing it wasn't the cause of problem.
I don't really know what caused it to reboot but it has'nt done it since i went back to stock. I don't think it was the apps cuz the only other app that I dont have on my tab now ,when it was rooted is the app that changes the screen density [ I don't remember what it was called]... I also used titanium backup when I had it rooted but I know its not that app cuz I still have it installed
Sent from my GT-P6210 using xda premium
It's probably irrelevant, but I found that if I increased the screen density to 180dpi (probably anything over 160?) using the DPI Changer Utility app, then the tablet would boot to the homescreen and then reboot, over and over.
wolverine38812 said:
I don't really know what caused it to reboot but it has'nt done it since i went back to stock.
Click to expand...
Click to collapse
I also concern that rooting may contribute to the random reboot. I wouldn't mind to experiment it, but I don't know how to completely remove root if I need to.
FYI, I have the Canadian LB2 firmware, and it is not available online for me to flash it to the tablet using Odin.
Could you share with me how you did the unrooting (reverting to stock ROM)?
Well to throw a wrench into the mix I have my Tab Plus rooted and I don't get random reboots on LA3 firmware.
Zadeis said:
Well to throw a wrench into the mix I have my Tab Plus rooted and I don't get random reboots on LA3 firmware.
Click to expand...
Click to collapse
P6200 or P6210?
It seems to crash when apps cannot access the network during standby, and that's why some are fixing the issue by installing the Auto Airport Mode app.
Hence, having 3G or not may make a difference.
I have a 6210 so no 3G for me.
Zadeis said:
I have a 6210 so no 3G for me.
Click to expand...
Click to collapse
Thanks, I'll definitely try rooting, as soon as I learn how to unroot first.
PS. Do you have Titanium Backup, or did you change the display density? (These are the other suspects that could cause the reboots in wolverine's case)
I use rom toolbox for freezing apps and other things so no I don't have titanium backup.
I have changed the density before (also using rom toolbox) and didn't like the results and went back. So for me it is still at the normal 160.
I hope I am being of some help here!
ikeny said:
Could you share with me how you did the unrooting (reverting to stock ROM)?
Click to expand...
Click to collapse
When I did the update to LA3 it unrooted mine but this should work just as well:
1. Download a file explorer, allow root acess, mount as r/w
2. Go to system/bin
3. Find SU file and delete it
4. Reboot
I didn't do it this way but it should work, do it at your own risk. I am not responsible if something happens to your tablet
Sent from my GT-P6210 using xda premium
wolverine38812 said:
When I did the update to LA3 it unrooted mine but this should work just as well:
1. Download a file explorer, allow root acess, mount as r/w
2. Go to system/bin
3. Find SU file and delete it
4. Reboot
I didn't do it this way but it should work, do it at your own risk. I am not responsible if something happens to your tablet
Sent from my GT-P6210 using xda premium
Click to expand...
Click to collapse
I too, prefer to unroot by flashing a factory image with Odin. The problem is, I have a Canadian P6210 (w/o IR port) with LB2. Until LB2 factory image is released (or something newer), I don't think I'll root my tab. It has been running rock-solid without any reboot for the last few days, I don't want to risk losing it by rooting.
Update - still not rooted and running only apps installed from Play store, it suffers from random reboots. Sometimes once or twice in one days, other times no problem in days. No obvious patterns noted.
By the way, also have one SOD in about 2 weeks that I own this tab
A quick Google search shows that this problem is reported on many models of galaxy tabs (7.7, 10.1, ...)
I've had my 6210 for a month without issue then it stared sod and reboot with great frequency. I read about a few solutions but I couldn't understand why it would start happening without me making setup changes (unless hardware failed or a write failure corrupted something). I decided to reboot in recovery to clear the cache. Its been two days without a problem. I have no idea how long it will last but it's working for now...
Sent from my GT-P6210 using Tapatalk
I'm on LA3 as well, I've never experienced this problem. Maybe there is some common denominator here, like manufacture date etc.
Related
When someone sends me a message they get this message automatically "Command not supported* Battery remaining 95%"
The battery % changes whatever my battery status is. It also shows in my list that I actually sent the message. Anyone have a clue what is going on here?
You've been around for a while, so hau about some more information such as:
When did it start?
Recent changes to the phone (before and after this started happening)? Specifically ROMs and applications.
Anything you've already tried to fix this?
Wulamoc said:
You've been around for a while, so hau about some more information such as:
When did it start?
Recent changes to the phone (before and after this started happening)? Specifically ROMs and applications.
Anything you've already tried to fix this?
Click to expand...
Click to collapse
Well, if any of the information was needed I would have said it. There have been no recent changes, this started today (hence the post). ROM is listed. This happens rather I use stock messaging or another. No fix has been done since I don't know how to fix and have never seen this issue (hence the post). If you can help great, if not that is fine too.
virusmonk3y said:
Well, if any of the information was needed I would have said it. There have been no recent changes, this started today (hence the post). ROM is listed. This happens rather I use stock messaging or another. No fix has been done since I don't know how to fix and have never seen this issue (hence the post). If you can help great, if not that is fine too.
Click to expand...
Click to collapse
Have you started simple - pulling the battery?
Also - any battery status apps installed? https://market.android.com/details?id=net.mobilemonkeys.Battery looks like some have the ability to automatically respond to a text with a battery level - one might be going rogue?? (SMS Commander is another that can do this)
homeslice976 said:
Have you started simple - pulling the battery?
Also - any battery status apps installed? https://market.android.com/details?id=net.mobilemonkeys.Battery looks like some have the ability to automatically respond to a text with a battery level - one might be going rogue?? (SMS Commander is another that can do this)
Click to expand...
Click to collapse
No battery apps. Tried pulling battery, nothing.
If this just started today, there had to be something that triggered it. Have you considered flashing your backup (assuming you have one) to see if it goes away?
pazzo02 said:
Never mind
Click to expand...
Click to collapse
That's about where I'm at.
Seems like an app issue, rather than a carrier/rom/w/e issue.
And given it's obscurity, one is going to have to clean wipe down to base ROM without any installed apps/widgets and see if the issue persists.
If it doesn't, then reloading Apps-Data and see if it persists...
If it does persist before reloading apps-data, then they would have eliminated some unfathomable number of variables...
pazzo02 said:
If this just started today, there had to be something that triggered it. Have you considered flashing your backup (assuming you have one) to see if it goes away?
Click to expand...
Click to collapse
If something triggered it, I have no clue what did. Last night, I charged my phone, woke up for work, the wife sent me a text and that is when it happened. I have a back up yea, which I might have to do.
Did you ever fix this or figure out what it was? My GS3 has started doing this. No ROM, rooted and unlocked. Only SMS app I have installed would be Mighty Text.
Moved to Q & A section.
Sent from my Galaxy Nexus using Tapatalk 2
That is weird!
Here's what I would do...
1. Check for any apps that updated through the Google Play Store overnight
a. If any updated, uninstall and see if that fixed your issue.
b. if none updated, continue to step 2
2. Reboot into CWM Recovery and wipe dalvik cache and fix permissions from CWM
3. Test your device
a. if problem is fixed stop here
b. if problem persists continue to step 4
4. Verify that you do have a nandroid backup of your phone
a. to do this, open file explorer and navigate to the you CWM folder on your SD card and verify a nandroid backup has been made
b. if one is not made, reboot into recovery and do this now!!!
5. Go to settings and reset your device.
6. When phone boots back up, test SMS
a. if issue persists, download CM 7.2 and re flash your rom and go to step 7
b. if issue is fixed, continue to step 7
7. If the issue is fixed, you know its a setting or app on your phone causing the problem.
8. If you have a previous nandroid backup, which you stated you did, flash the nandroid through CWM
9. Test SMS
a. if issue is fixed GREAT
b. if issue is not fixed, wipe your phone and install your apps back one by one from the google play store
Previously when I would flash a CM ROM I would dirty flash it so I didn't have to reinstall my apps back to my phone. If you are flashing nightlies of CM 7.2, I would do a regular flash to wipe the device completely.
On a side note, an Unofficial version of CM10 is available for the Inspire 4G... It will be picked up by the CM Dev team in about a month. That means we will have some Jelly Bean love official from CM.
Cheers!!!
I picked up an AT&T 4G LTE Note Pro (SM-P907a) yesterday and so far I am absolutely loving it. And though this is my first post, I am no stranger to XDA, I currently have Galaxy S4, Note 3, Note 10.1, and now the Note Pro, all are rooted running custom roms, minus the Note Pro. I have never hade to make a post before because I understand how to use the search function and have always been able to find the answersI have needed, until now. I am hoping someone can tell me if it is possible yet to root AT&T's version of the Note Pro 12.2, SM-P907A? Will CF auto root for the Verizon SM-P905 work? Or am I simply to ahead of the game and need to wait for root to become available? Thanks!
Same here. Just got mine. Want to use about 3 apps that require root. It's only been out one day. At&t probably didn't add anything to what Samsung did as far as locking the bootloader. All I really want at this point is root, I don't need a new room yet. Yet
Based on how long the Verizon variant users have been waiting. .. come back in September. In all seriousness though, I hope you folks don't have to wait that long...
Sent from my SM-P900 using Tapatalk
Have either of you tried to root with towel root?
Sent from my SM-N9005 using XDA Premium 4 mobile app
thanks
AboveAverage said:
Have either of you tried to root with towel root?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
brilliant!!!! thanks. I am installing busybox as I type this :laugh:
EDIT: haha spoke too soon, SuperSU won't install. Do you know how to get a custom recovery on it when rooted this way?
I can confirm towelroot is working for AT&T P907a.
Steps I took.
1. Download and installed towelroot (towelroot.com)
2. Ran towelroot apk, device rebooted.
3. Downloaded SuperSU 1.99r4 (download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip)
4. Ran SuperSU apk, installed binaries, disabled Knox
5. Done!!
jmedlin said:
I can confirm towelroot is working for AT&T P907a.
Steps I took.
1. Download and installed towelroot (towelroot.com)
2. Ran towelroot apk, device rebooted.
3. Downloaded SuperSU 1.99r4 (download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip)
4. Ran SuperSU apk, installed binaries, disabled Knox
5. Done!!
Click to expand...
Click to collapse
has yours been freezing and rebooting?
EDIT: also all I could find in the zip file was Superuser.apk, is that what you meant?
phirestalker said:
has yours been freezing and rebooting?
EDIT: also all I could find in the zip file was Superuser.apk, is that what you meant?
Click to expand...
Click to collapse
Mine has been running smooth, no reboots no freezing nothing. And yes unzip the file and SuperuserSU.apk is inside.
phirestalker said:
has yours been freezing and rebooting?
EDIT: also all I could find in the zip file was Superuser.apk, is that what you meant?
Click to expand...
Click to collapse
Mine is. But it was actually worse before root.
during one of the reboots I've been having it actually showed custom aND a lock that is unlocked. now when I reboot it doesn't say that anymore. root checker shows that it is properly rooted so I'm not sure that there's a problem.has anyone else noticed this?
I've had a couple of reboots.. what is weird is that it flashes to the at&t logo the my lockscreen. When I unlock it its like it rebooted but it happens so fast.. I am not sure if its a system reboot or just the user session crashing...
phirestalker said:
during one of the reboots I've been having it actually showed custom aND a lock that is unlocked. now when I reboot it doesn't say that anymore. root checker shows that it is properly rooted so I'm not sure that there's a problem.has anyone else noticed this?
Click to expand...
Click to collapse
When I reboot now I see this custom android and unlocked logo at the bottom of the screen. What I am unsure of is if it had this before I rooted.
If someone who based rooted their 907a reads this please check if you get this on a bootscreen during a restart.
I would like to hear from a couple people how their tabs are doing after root. I'm thinking about doing it.
My AT&T Note Pro 12.2 keeps rebooting. My WiFi only 12.2 restarts when attempting towel root and never patches the necessary files. My AT&T Note 3 was flawless though. 1 out of 3 ain't bad I guess. Really just want the ad block ability. Is there an unroot so I can get my tablet to stay on more than an hour?
Me and my friend both got the att 12.2.
After rooting I've had reboot issues while he hasn't. So I've been slowly uninstalling programs that I use and he doesn't. Thinking it might be one program or another or a combo of programs. First I uninstalled Greenify to no effect. Next I switched back to the Samsung launcher from Nova Launcher Pro. So far its been two days without a reboot since switching back to the touchwiz launcher.
I ran Nova launcher fine before root.. And my friend with the exact tablet rooted the same way has had no issues..
Are you running a launcher different than Samsungs?
Ill report back.. but so far so good.
That's a very good point. I'm using the stock launcher still but I do have a ton of apps. I'll have to try deleting some see if that has any affect.
Ok, some added details on my "rebooting" although it doesn't show the samsung logo, so I don't think it is a full reboot.
I have noticed that the only time it happens is when I lock the screen or when it locks itself. Sometimes it has been locked for a while and it will randomly do it. I don't believe it has ever happened while I was using it. Oh, and a few times it happened while unlocking the screen. So it all seems to be related to the lock screen. I don't have any apps that add functionality to the lock screen. I have a pattern unlock and Smart Stay enabled (although this never worked for me, maybe my face is too weird to be detected? Lol). I am going through the process of turning off things to see what might be causing the problem. The first thing I disabled was the LastPass accessibility extension. I will give it a day or 2 but I have been playing around with locking and unlocking with various apps open as i write this and I haven't had a "reboot" yet.
I noticed that another poster had trouble with a different app and like him this trouble started after I rooted it. The LastPass accessibility extension worked fine before rooting. I will tell you what this extension does and maybe it will help us narrow down what area of the system has been changed to be incompatible with certain software.
The extension "watches" for password entries on apps and webforms and offers to autofill with saved passwords.
Sorry for the long post, hope it is helpful to someone.
I've been running Lastpass for months on my Wifi model so I doubt it is the cause. Good idea to systematically disable things though. I have problems since enabling a custom keyboard though. Perhaps try disabling all other input methods other than stock?
Sent from my SM-P900 using Tapatalk
muzzy996 said:
I've been running Lastpass for months on my Wifi model so I doubt it is the cause. Good idea to systematically disable things though. I have problems since enabling a custom keyboard though. Perhaps try disabling all other input methods other than stock?
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
You're right, after a while it started doing it again. I guess it didn't happen as often as I thought. I really hope someone comes along who knows how to diagnose crashes to find out what is causing them.
I've been getting reboots also every once in awhile on my sm-p907a it reboots.I also tried safe strap recovery for the at&t samsung galaxy note 3 version 3.75.It seems to be working I did a nanoid backup and it successfully worked but took awhile. I didn't do a restore because I don't want to mess anything up until there's a stock Odin firmware download to restore if something goes wrong.The dpi is of but u can c almost the whole recovery screen if anyone wants to play around with it
Hi,
I'm having trouble with my OpO since I rootet it. Here is the history:
-Day One: Just stock 25R, installed all Apps via google play, no problems whatsoever.
-Update 30O still no problems.
-Then I rootet the phone and flashed TWRP recovery to install the Titanium Backups of my old Nexus 4. Thats when I had the first random reboots. Some while Browsing in Chrome, Some on Youtube, Some while listening Music on Hedphones.
Since I have no Sim-Pincode activated a reboot just means, that I'm Offline for about 20 seconds but having that about 5 times a day just isn't acceptable.
-Then I got the 33R OTA update, which made my root and TWRP recovery disappear because I forgot to make a check in the developper settings, but that did not make the reboots disappear
-Today I flashed the 25R stock Image of the Firmware via Fastboot to set my One to real Factory status. I only installed apps via google play and recovered the app data of 2-3 apps via helium backup without root. I got the two OTA updates, and another reboot.
-Then I rootet the thing again, to use a logcat app, and now I have two logcats ending with a reboot.
I really hope that you can help me since I allready sold my old phone and expect that it will take really long until I get a new OpO here in Germany.
The next thing I will do is flash the 25R Image again and install the apps without using helium at all and leave out the goolors icon pack that I used before. But after that I'm absolutely out of ideas.
UPDATE: Yeah so it's definitely a HW defekt or something I cannot solve. I just wiped everything via TWRP, then flashed the factory image 25R without root and just installed some apps via google play. But after one hour I read an email and it rebooted....
Unfortunately I cant post the links to the logcats due to my low post count.
Logcats don't help you when it comes to finding out what is causing your phone to reboot. It is last_kmsg that is responsible for debugging reboots.
A hardware defect would not be causing your phone to reboot, its something to do with the way your phone is configured / set up.
I would highly recommend you to start from scratch completely and do the following,
- Flash XNPH33R http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip from scratch. Make sure you do wipe.
(OR.. flash a custom ROM after wiping)
- List all of the apps that you currently have installed.
- Are you using Xposed?
- Whats your set up? ROM/Kernel/Gapps/etc.
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Ord3r66 said:
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Click to expand...
Click to collapse
I meant, you can try a custom ROM and see if you can reproduce the problem. Custom ROMs are running on code that is much newer than CM11S.
Ensure you're on XNPH33R when it comes to OTAs.
I just wanted to add my frightful experience. I've had the OPO for two weeks now without problems and no random reboots. Had my first reboot today and just now my phone powered off and wouldn't turn back on. I plugged it back into the wall charger and it turned itself back on but was stuck on the boot logo. I tried holding down the power button to turn it off but nothing. Pressing the power button only turned the display on and off but still stuck on boot logo. Eventually I held down the power button and volume down and the phone buzzed and went to recovery. I'm on stock 33R and Franco's kernel. Haven't tweaked anything. Now I'm afraid my phone is going to brick itself.
Sent from my A0001
Yeah so this is definitely getting worse. At first I had 1-2 reboots a day but today after unplugging I already had 3 reboots in one hour.
I think I am definitely going to send it back when I'm back home next Week.
I already flashed stock Firmware 3 times and did what feels like 10 full wipes in one Week.
This cant be normal. Apps that I installed that arent in the top 50 in the play store are: Dailyme, yatse for xbmc, line, Wolfram aplha and ogyoutube.
That really sucks. I already sold my nexus 4 and have no other phone left
Btw: I'm on 33R for the third time this Werk. Everytime via OTA
Try a different Rom like crDroid + AK Kernel. Running this 2 things since 2 weeks and i only got one reboot just because my camera stopped working because in undervolted my phone ^^
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Ord3r66 said:
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Click to expand...
Click to collapse
ok I understand your frustration but to fully test your phone you will need to run stock and stock only with no outside apps loaded. Try and do this for a day or half a day or so and see what your results may be. Its your phone and of course do what you like but testing your phone and doing the same thing every time as in reloading your apps is not a good way of fully testing.
also did you do a last_kmsg report as recommended.
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
Yes you need root. After a reboot just pull the last_kmsg file from /proc/ using adb, file Explorer of your choice, etc.
Sent from my One A0001 using Tapatalk
Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
of course there is a tutorial there is a tutorial for everything.... Got to utilize google my friend.
OKay it's me again. Meanwhile the Oneplus support answered my mails and told me to flash custom Kernels to resolve the issue.
Since Yesterday I tried three Kernels (Franco, Heeroluca and AK) and nothing changed, so now I start to gather some Last_kmsg files name it after the APP where the reboot occured and upload it here. Ofcourse I'm also sending those files to the Oneplus Support
Here is the first one:
https://dl.dropboxusercontent.com/u/43103242/1_Line_Messenger_last_kmsg
https://dl.dropboxusercontent.com/u/43103242/2_standby_screenoff_last_kmsg
Have the same problem. Using wi-fi -> reboot. Don't know how to fix this defect. I hope a solution will be found
Had a random reboot while browsing chrome. I was scrolling down the page and received a text at the same time when my screen froze. After freezing for a few seconds, it rebooted itself. I tried getting the last_kmsg but it tells me that it isn't found. The code I used was: "su" followed with "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" in terminal emulator. Let me know if there is anything else I can do. Thanks!
I have also problems with chome beta browser. I get freezes. Is this issus only with chrome or with all browers?
Gesendet von meinem A0001 mit Tapatalk
I've just received an OTA for my P900 (bought in UK, completely stock, not rooted, P900.XXUANI1). Since then the tablet has been rebooting randomly several times a day. It's a funny sort of reboot where the tablet is back up and running almost instantly, not like on a usual startup. The screen goest black, the "Samsung" logo flashes for a half a second and it's back at the lockscreen. No blue-lines-logo animation that goes with a usual startup, but all the apps I was using are closed and the recent apps list is empty.
Is anyone having the same problems? Any ideas on how to fix this?
You can try a factory reset.
ShadowLea said:
You can try a factory reset.
Click to expand...
Click to collapse
I know I probably should after an update anyway, but I'd hate to have to set up the tablet all over again, so I'll give it a few more days. I was wondering if anyone came accross this problem and found a different solution. Some people mentioned their ATT version crashing and how un-disabling an app has fixed it. I don't have an app called My Magazines though, so that's no good. I have a bunch of apps disabled though. Could any of them cause such funny behaviour?
I think it is a problem on several firmwares, and the devices are rooted.
I fixed it using the Xposed Framework and the Wanam addon.
Or you can try the http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 add-on.
Thanks, this seems to be it. It looks like I'll be rooting my tablet when I get home today I should have done it ages ago anyway, if only to set the desktop user agent in the browser and get rid of adds.
Well, CF Autoroot didn't work for some reason. Now the system won't load at all (I can still get into download mode). Anyway, I described the problem here, if you can help, please let me know!
Tintinnuntius said:
Well, CF Autoroot didn't work for some reason. Now the system won't load at all (I can still get into download mode). Anyway, I described the problem here, if you can help, please let me know!
Click to expand...
Click to collapse
I've been there. Follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2794996
Then install SuperSU from the app store. Then try to flash CF Autoroot again. Good luck. And let me know if the file CyberDie1 referred to us worked for you.
Makoto1 said:
I've been there. Follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2794996
Then install SuperSU from the app store. Then try to flash CF Autoroot again. Good luck. And let me know if the file CyberDie1 referred to us worked for you.
Click to expand...
Click to collapse
Thank you so much, you just saved me a trip to the service centre. I've followed through with the first three steps and it booted back into the system I wish I could give you more than one "Thanks".
I don't have time to go through the rest of the steps today since I still have some stuff to do for work, but if the tablet keeps "rebooting" I'll be back in a few days to root and report how it went with the Xposed module.
BTW, I haven't been able to find the file "openrecovery-twrp-2.7.1.0-v1awifi.img.tar" the guide mentions as no. 4, and no other twrp version for P900 (only P905) on their site. Do you maybe have a link for that?
And big thanks again!
Tintinnuntius said:
Thank you so much, you just saved me a trip to the service centre. I've followed through with the first three steps and it booted back into the system I wish I could give you more than one "Thanks".
I don't have time to go through the rest of the steps today since I still have some stuff to do for work, but if the tablet keeps "rebooting" I'll be back in a few days to root and report how it went with the Xposed module.
BTW, I haven't been able to find the file "openrecovery-twrp-2.7.1.0-v1awifi.img.tar" the guide mentions as no. 4, and no other twrp version for P900 (only P905) on their site. Do you maybe have a link for that?
And big thanks again!
Click to expand...
Click to collapse
I'm also at work so I'm not at my computer. I think I found that file by doing a Google search for it. Yes, let me know if it keeps rebooting. I have my own tablet rebooting issues (as you can see in one of the other threads, heh). I lost my root by reinstalling SuperSU one too many times... I blame it on trying to change settings before reinstalling because I was trying to achieve something.
Makoto1 said:
I'm also at work so I'm not at my computer. I think I found that file by doing a Google search for it. Yes, let me know if it keeps rebooting. I have my own tablet rebooting issues (as you can see in one of the other threads, heh). I lost my root by reinstalling SuperSU one too many times... I blame it on trying to change settings before reinstalling because I was trying to achieve something.
Click to expand...
Click to collapse
I tried googling, but like I said, the official TWRP site did not have a file for p900, only p905. Here's the list of all the supported devices on their site, I only see p905 and 3g variants.
Then there's this site. I didn't realize that "v1awifi" is the part that refers to p900. I'm going to use the latest version from here today and try to get root again. If I succeed, I'll then try the Xposed package. I only had three reboots in the last 24 hours though (which is much less than before my first root attempt), so it might be a while before I can be certain the reboots are gone.
EDIT: I rooted in a few minutes without a single problem. Xposed and module installed, starting the clock for reboot-watch now I'll report back immediately if I get a reboot, or in 24h if I don't.
EDIT2: It looks like Xposed with the Samsung SystemServer Crash Fix works. The app posts notifications when a crash is prevented, and I've just had three in the last hour, with no crashes.
Best of luck. I tried that Xposed and Wanam module combo and it seemed to work for most crashes. However, I still get reboots when I wake it up from sleep after a full charge (from my experience).
Makoto1 said:
Best of luck. I tried that Xposed and Wanam module combo and it seemed to work for most crashes. However, I still get reboots when I wake it up from sleep after a full charge (from my experience).
Click to expand...
Click to collapse
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Tintinnuntius said:
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Click to expand...
Click to collapse
I also installed the System Server Crash Fix, but it didn't prevent the reboot. Hopefully it works for you!
I purchased Titanium Backup and froze all the Knox related processes and apps, but I still got a reboot. So, I just did a factory wipe on the tablet and rerooted. This time it prompted me and asked about disabling Knox. This time I chose cancel instead of disable. Crossing my fingers now. If I still see a reboot tomorrow morning I will probably forget about rooting my tablet.
Tintinnuntius said:
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Click to expand...
Click to collapse
Just adding in. The SystemServer Crash Fix is an Xposed module why you also need to install the Xposed Installer. First validate Xposed, then the crash fix app, finally reboot and you're done. Finally, just pray that your issues are gone...
Makoto1 said:
I purchased Titanium Backup and froze all the Knox related processes and apps, but I still got a reboot. So, I just did a factory wipe on the tablet and rerooted. This time it prompted me and asked about disabling Knox. This time I chose cancel instead of disable. Crossing my fingers now. If I still see a reboot tomorrow morning I will probably forget about rooting my tablet.
Click to expand...
Click to collapse
I went halfway between your approaches. I chose to disable Knox when asked, but I did not freeze any of the apps with Knox in the name in TB. First, I reset the default apps settings and then used TB to freeze a bunch of bloatware, but nothing with Knox in the name. The only such app currently frozen is Knox Notification Manager 1.0. Also, I never installed Wanam module, just SSCF.
Tintinnuntius said:
I've just received an OTA for my P900 (bought in UK, completely stock, not rooted, P900.XXUANI1). Since then the tablet has been rebooting randomly several times a day. It's a funny sort of reboot where the tablet is back up and running almost instantly, not like on a usual startup. The screen goest black, the "Samsung" logo flashes for a half a second and it's back at the lockscreen. No blue-lines-logo animation that goes with a usual startup, but all the apps I was using are closed and the recent apps list is empty.
Is anyone having the same problems? Any ideas on how to fix this?
Click to expand...
Click to collapse
I have the same problem, since I upgrade my T900, I have the same behavior you described.
Read a lot and tried everything, even Xposed Installer. Nothing corrected it.
I didn't test this firmware version it without root (can't live without it!).
If what you said that you have the random reboot without root, I really think that this firmware release is buggy.
I will now return to the previous firmware.
fdu123 said:
If what you said that you have the random reboot without root, I really think that this firmware release is buggy. I will now return to the previous firmware.
Click to expand...
Click to collapse
There's no doubt that Samsung is at fault. My tablet was stock, unrooted, in no way modified, and it still crashed several times every hour, usually when screen timed off and was turned on again, but also on other occasions. I would flash an older version too, but then I might have to do a clean install and set it up again, so I tried root + Xposed + SSCF first, and fortunately it worked. With the added benefit of Desktop User Agent in Chrome, no ads and a much snappier tablet. I should have rooted months ago
arcadia2uk said:
Just adding in. The SystemServer Crash Fix is an Xposed module why you also need to install the Xposed Installer. First validate Xposed, then the crash fix app, finally reboot and you're done. Finally, just pray that your issues are gone...
Click to expand...
Click to collapse
I installed the SystemserverCrash Fix app first, then the Xposed Installer... is that why it didn't work for me? Thanks in advance.
---------- Post added at 10:40 AM ---------- Previous post was at 10:32 AM ----------
Tintinnuntius said:
There's no doubt that Samsung is at fault. My tablet was stock, unrooted, in no way modified, and it still crashed several times every hour, usually when screen timed off and was turned on again, but also on other occasions. I would flash an older version too, but then I might have to do a clean install and set it up again, so I tried root + Xposed + SSCF first, and fortunately it worked. With the added benefit of Desktop User Agent in Chrome, no ads and a much snappier tablet. I should have rooted months ago
Click to expand...
Click to collapse
Which app did you use for no ads? Adblock Plus and Adaway didn't seem to work for me...
Makoto1 said:
Which app did you use for no ads? Adblock Plus and Adaway didn't seem to work for me...
Click to expand...
Click to collapse
Adblock Plus version 1.2.1.325 works fine for me. It allows some unobtrusive ads through by default. If you want to block all you can, but you have to manually enable it in app settings.
If a particular app is still showing ads it sometimes helps to clear the cache.
Makoto1 said:
I installed the SystemserverCrash Fix app first, then the Xposed Installer... is that why it didn't work for me? Thanks in advance.
Click to expand...
Click to collapse
You could always try installing them the right way round to see if it will make a difference. I think I installed both apps at the same time, but then I opened Xposed, activated it, rebooted the tablet, then activated the module (which showed up in Xposed automatically, IIRC).
First, you should double-check that the SSCF is activated in Xposed, if it is not, it won't stop the crashes.
Can anyone verify that the method posted by Unjustified Dev in this thread will work the the indicated phone model?
Rooted LG Lucky
I rooted using kingroot version 4.8.0 I could use the stock Rom have no download if anyone could help thanks. Its a straight talk lg lucky running 4.4.2 kitkat I'm no computer whiz and I couldn't figure out how or what I needed phone works fine . now I just want to be able to do a factory reset safely if need be only deleted stock apps that I don't use nothing important I hope.
boct1584 said:
Can anyone verify that the method posted by Unjustified Dev in this thread will work the the indicated phone model?
Click to expand...
Click to collapse
I have obtained root on the device today. Ive read that some were able to do it with kingroot on the older versions but all have had no luck on the version with software version L16CV11a and build number KOT49I.L16CV11a. Well i managed to root it today with a certain methid...will post up a guide later after ive written it out...may see if i can further the progress now that ive rooted it.
STOCK firmware??
i got an lg lucky and its stuck in bootloop does anyone know how i could get stock firmware to flash? it goes to factory reset menu but freezes as soon as it starts to do its thing... maybe not fixable??
bonnis.phone said:
i got an lg lucky and its stuck in bootloop does anyone know how i could get stock firmware to flash? it goes to factory reset menu but freezes as soon as it starts to do its thing... maybe not fixable??
Click to expand...
Click to collapse
Depends on if yourlucky was rooted and if you deleted files you should have
Sent from my Nexus 6 using Tapatalk
REV3NT3CH said:
I have obtained root on the device today. Ive read that some were able to do it with kingroot on the older versions but all have had no luck on the version with software version L16CV11a and build number KOT49I.L16CV11a. Well i managed to root it today with a certain methid...will post up a guide later after ive written it out...may see if i can further the progress now that ive rooted it.
Click to expand...
Click to collapse
I have the newer Model LGL16C/4.4.2/Baseband version M8610B-AAAANAZM-1.0.6060/Kernel version 3.4.0+/Build KOT49I.L16CV11a/Software version L16CV11a/"Lucky". Service provider is Tracfone, aka Crapfone. Attempts to root with Kingroot as well as Kingoroot failed, including several apps which claim to root your phone. I paid less than $10 US dollars for this phone and rooting it isn't high on my priority list, however rooting the damn thing has presented a bit of a challenge.
A working guide to rooting this phone would be great.
2k73 said:
I have the newer Model LGL16C/4.4.2/Baseband version M8610B-AAAANAZM-1.0.6060/Kernel version 3.4.0+/Build KOT49I.L16CV11a/Software version L16CV11a/"Lucky". Service provider is Tracfone, aka Crapfone. Attempts to root with Kingroot as well as Kingoroot failed, including several apps which claim to root your phone. I paid less than $10 US dollars for this phone and rooting it isn't high on my priority list, however rooting the damn thing has presented a bit of a challenge.
A working guide to rooting this phone would be great.
Click to expand...
Click to collapse
Give me a few days to write it out...basically if you have the knowledge...what I did was run kingroot while plugged into PC...was a tad tricky but I'll get further into it later...took a few tries
Sent from my Nexus 6 using Tapatalk
REV3NT3CH said:
Give me a few days to write it out...basically if you have the knowledge...what I did was run kingroot while plugged into PC...was a tad tricky but I'll get further into it later...took a few tries
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hey mate,
I hate to be like a noodge, but would you be able to explain how you rooted? Would be so much appreciated.
REV3NT3CH said:
Give me a few days to write it out...basically if you have the knowledge...what I did was run kingroot while plugged into PC...was a tad tricky but I'll get further into it later...took a few tries
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
PizzaMaster said:
Hey mate,
I hate to be like a noodge, but would you be able to explain how you rooted? Would be so much appreciated.
Click to expand...
Click to collapse
Hey so i spent forever trying ro find a root that would work on this. Or a custom ROM anything really. Try going into McAfee Security, setting up an account, go to settings and disable the lock down device option. That was the problem for me at least McAfee was blocking any root from installing. From there i rooted my lucky with kingroot one click root. Hope this helps!
The Easiest Way To Root Your LG Lucky Without a PC
Easy way to install SuperSU on your LG Lucky
Just follow directions
Use KingRoot 4.5.0 app - google KingRoot apk all versions. Download and install apk.
Google replace kingroot with supersu. There will be a few sites popup, Mediafire is where the original .zip file is hosted. You can even search "how to replace/remove kingroot with supersu" here on XDA for more info.
Once you have downloaded the .zip file be sure to extract it to your INTERNAL sd, the script in the zip will not work from your external sd.
Open the extracted file and copy the mrw file to the internal storage, the path should look like /storage/emulated/0/mrw.
Now go to the play store, download and install Terminal Emulator. I use the one by Jack Palevich as it is only 551kb and easy to use.
Open the terminal emulator and type "su" in order to grant super user permission to the emulator,
On the next line type "/system/bin/sh - /storage/emulated/0/mrw/root.sh" and press enter.
Now the script will run and open up SuperSU automatically. Install binary when prompted with the "normal" option. Choose yes when it asks if you want to delete other superuser apps. (this removes kingroot).
Before rebooting phone, go into the settings of SuperSU and enable pro mode, change icon if you wish, enable survival mode, enable su during boot. I think you have to restart app at this point, can't remember as I did this months ago. Then restart the SuperSU app, go back into settings to Install SuperSU into system. Reboot phone,
When phone reboots, this is when Kingroot is finally uninstalled. Your phone will still be rooted with SuperSU. At this point you may wish to update SuperSU as this is version 2.46 and the newest version is 2.71 Beta. You can get the newest version of SuperSU from the thread here on XDA.
(thanks MrWolf for the script to make the change and thank you Chainfire for SuperSU, FlashFire, CF.lumen, etc...)
LGL-16C successfully (so far) rooted using Kingoroot.exe (latest version). Had to change from mtp to camera on USB then was recognized. Have SuperSU 2.72, SuperSU Pro, BusyBox Pro, and Xposed installed with Xblast and Lucky Patcher running. No custom recovery or roms available and I have searched hi and lo. Was a Net10 $15 phone with nothing to lose, so...will try more stuff out another day and post again.
mikemc63 said:
LGL-16C successfully (so far) rooted using Kingoroot.exe (latest version). Had to change from mtp to camera on USB then was recognized. Have SuperSU 2.72, SuperSU Pro, BusyBox Pro, and Xposed installed with Xblast and Lucky Patcher running. No custom recovery or roms available and I have searched hi and lo. Was a Net10 $15 phone with nothing to lose, so...will try more stuff out another day and post again.
Click to expand...
Click to collapse
Until any source is made there will be no recovery or ROM and tbh I don't have the time to dig into it currently.. The positive with rooting though is removing the bloat
Sent from my Nexus 6 using Tapatalk
REV3NT3CH said:
Until any source is made there will be no recovery or ROM and tbh I don't have the time to dig into it currently.. The positive with rooting though is removing the bloat
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hi. Could you tell me how you installed supersu after rooting with kingroot? Thanks
Well I have root and supersu installed but it won't update binary. Any help out there? Thanks
Hey everybody. I did it!! Just root with kingroot 4.5 and replace kinguser with super sume. Worked great. All kingroot stuff is gone!! Ive rebooted 3 times to make sure and all is good.
Well if anyone is interested in looking at the source code, lg support has downloads available for nearly every phone they've ever made.
http://opensource.lge.com/osList/list?m=Mc001&s=Sc002
The file for the LGL16C is on page 2. Every thing seems to be listed alphabetically so it's easy to locate.
I still have my lucky and actually use it often although I no longer have it activated.
@ cecnwv,
Thanks for the link. Using Ares 11 and got "IP banned for 6 hours,try again later" after dbl tppng yellow icon. I did something wrong. Not at my PC. (unfortunately)
Thanks for any enlightenment,
michaeltheclyde
Two 10a LGL16C Tracfones, one free (recon from Tf) and one new $14.95 @ eBay from Best Buy, rooted with everything that has Google in the name frozen (TB) but no image to restore. (twrp)
Has anyone made a complete backup of their system apps using Titanium Backup? Being that one can't use fastboot/download mode (this phone has it locked out and a special USB cable is required) so my backup options were limited. I thought I did a full backup with Titanium Backup, but apparently lost it as I only found a small partial one on my PC.
Issue is I had uninstalled some bloatware and integrated updates for a few apps. But after factory resetting the phone it is behaving a bit odd. The notification bar doesn't really work anymore (apps still able to use sound/vibration to make a notification, but nothing appears in the notification bar) and I am unable to call the phone because it never rings and it immediately goes to voice mail. So the phone app is borked too.
Plus soft button to the right of the home button (I forget what it's called) doesn't bring up the app history anymore so I can't close background apps. (the volume buttons also don't really do anything anymore. Normally using them causes the volume bar for ringtone to appear and if using a media app, the volume bar for media audio comes up instead. But now nothing happens).
The phone is in a pretty broken state and even doing app updates from Play Store doesn't work anymore. Was gonna try and look around if someone has some app/data backup of the system apps installed. This is a TracFone branded phone and is currently running Android 4.4.2 (Kernel version 3.4.0+). Which is the last Android update they made for this phone.
Perhaps there's a single service/app that is responsible for notifications/volume bar that is borked. But I have no idea which system app is broken so a full app restore is my next best option.
The first thing wrong I noticed after resetting it was that the intial setup screen would return everytime I rebooted the phone. (only way i could get that to stop was freezing it in Titanium Backup). So maybe related to that app somehow. I don't recall ever uninstalling/merging update data for that perticular app though so it's probably a side effect of a different app going haywire.
EDIT:
Ok looks like I resolved the issue. I just removed the LGStartupWizard.apk then did a factory reset via Volume Down+Power button combo. It boots straight to home menu now and everything works. I guess the LG setup wizard thing got borked somehow. No more setup wizard but verious things like google account and whatnot can be configured manually via settings so no real loss.
All the missing things like the app history button, lock screen, notification bar, etc are now working as a result of resetting after removing LGSetupWizard.apk.
Apache Thunder said:
Has anyone made a complete backup of their system apps using Titanium Backup? Being that one can't use fastboot/download mode (this phone has it locked out and a special USB cable is required) so my backup options were limited. I thought I did a full backup with Titanium Backup, but apparently lost it as I only found a small partial one on my PC.
Issue is I had uninstalled some bloatware and integrated updates for a few apps. But after factory resetting the phone it is behaving a bit odd. The notification bar doesn't really work anymore (apps still able to use sound/vibration to make a notification, but nothing appears in the notification bar) and I am unable to call the phone because it never rings and it immediately goes to voice mail. So the phone app is borked too.
Plus soft button to the right of the home button (I forget what it's called) doesn't bring up the app history anymore so I can't close background apps. (the volume buttons also don't really do anything anymore. Normally using them causes the volume bar for ringtone to appear and if using a media app, the volume bar for media audio comes up instead. But now nothing happens).
The phone is in a pretty broken state and even doing app updates from Play Store doesn't work anymore. Was gonna try and look around if someone has some app/data backup of the system apps installed. This is a TracFone branded phone and is currently running Android 4.4.2 (Kernel version 3.4.0+). Which is the last Android update they made for this phone.
Perhaps there's a single service/app that is responsible for notifications/volume bar that is borked. But I have no idea which system app is broken so a full app restore is my next best option.
The first thing wrong I noticed after resetting it was that the intial setup screen would return everytime I rebooted the phone. (only way i could get that to stop was freezing it in Titanium Backup). So maybe related to that app somehow. I don't recall ever uninstalling/merging update data for that perticular app though so it's probably a side effect of a different app going haywire.
EDIT:
Ok looks like I resolved the issue. I just removed the LGStartupWizard.apk then did a factory reset via Volume Down+Power button combo. It boots straight to home menu now and everything works. I guess the LG setup wizard thing got borked somehow. No more setup wizard but verious things like google account and whatnot can be configured manually via settings so no real loss.
All the missing things like the app history button, lock screen, notification bar, etc are now working as a result of resetting after removing LGSetupWizard.apk.
Click to expand...
Click to collapse
Awesome, this worked for me too, though the issue wasn't exactly the same. When I got the phone it had already been rooted with Kingo at some point and I noticed after resetting it that I had similar problems (it may have had the issues before the factory reset too, I just didn't notice one way or the other). Anyway, I was getting slightly different misbehavior. No recents key, yes, but also no response from the Home key. Pull-down notifications bar was mostly working, but with no visible notifications and I couldn't press the Setup "gear" in top right. My volume buttons and Play Store were fine, though, but I'd noticed that when I tried further factory resets (from the menu, not via hard reset) that it wasn't "really" resetting, as any downloaded files/etc. remained on the phone. I'd tried freezing LGSetupWizard already, but as you noted, that doesn't fix it for whatever reason. Deleting altogether does. Yay. I do wonder what the hell is happening during the root or reset that triggers this problem, though. It behaves as if Setup Wizard was just never completed, so you remain "locked out" of most of the same functions that are unavailable during setup normally. Oh well.
Anyway, as old ten-dollars-or-less type phones go, this isn't the worst I've ever used by a long shot. Heck, it's arguably better than a few other slightly bigger/newer/pricier crap-phones out there! (Looking at you, ZTE Legacy/Quest...) FWIW, I had "ripped" all of the APKs from /system/app and /priv-app for some reason back when I first got this thing, so if they'd be of use to anyone I'll be happy to upload all or individual files. Hell, if anyone can tell me how to do a full ROM dump I'd be happy to do that too, because there's definitely still no official stock image available online that I could find a trace of. (Granted, I don't know if there'd be any way to utilize a non-official backup image anyway or turn it into a flashable KDZ, but that's not my point...)
Thank you, I got my lucky rooted! I'm wondering if anyone ever found any custom ROMs or recoveries for this device. It seems like this was never popular for any of that, but thought I'd ask. Thanks.