Hey all, I am looking for a little help with my phone. As the title says, I don't have enough posts to ask my question in the development section, so I have to post here and hope someone can help me figure this out.
I'm running the latest release 5 of Jellywiz with incubus' ICS theme and the VRLG7 modem on my unlocked rooted with cwm 6.0.1.2 Verizon Galaxy S3. I'm not a developer, but I'm not a noob either, so I have all the bases covered for generic troubleshooting.
Last night my phone died at a party, when I got home I plugged it in and went to sleep. This morning it was fully charged so I unplugged it and booted it up. pretty much as soon as it was booted up (before i even unlocked the device) i saw a toast notification that "system has been granted superuser permission" then 5-10 seconds later I felt 4 or so vibrations and then the device reboots itself.. Once it reboots, it does again what I just described and will continue doing it until I take out the battery.
One time I managed to get into superuser and delete the system entry, then once it asked permission I denied its request. Didn't change the end result at all. Now it says "system has been DENIED superuser permission" and still reboots, following the same pattern.
Also, this isn't the first time this has happened. A few days ago when release 5 first came out I updated from release 3 and lost GPS, restored to an earlier backup that had GPS (i think release 1) and dirty flashed 5 again which kept my GPS working. Then I debloated some stuff and when I rebooted I experienced this problem. I eventually odin'd back to stock and did the whole reunlocking rerooting and all that fun stuff and then loaded up release 5 to have a fresh and clean install and it worked flawlessly for about 2 days until now.
So I guess my questions are; is there something i can do now to fix this "system root access" leading to reboots other than using odin to go back to stock, AND since I've been through odin once and it just came back on its own, what might i be doing to cause this problem in the first place. (nobody that i could find in the Jellywiz thread or on a simple google search had this problem)(I had hardly restored any apps or data just before the most recent occurrence so i dont think it has anything to do with other apps)
Thanks in advance for any help or advice, I believe you all with be able to help me get to the bottom of this!
Ok, first off, its a good thing that this wasnt posted in development, as it would have been promptly moved. You have not developed anything ( other than a problem )
Have you done any overclocking? More specifically, overclocking where your custom freq. profiles are applied at boot?
preusstang said:
Ok, first off, its a good thing that this wasnt posted in development, as it would have been promptly moved. You have not developed anything ( other than a problem )
Have you done any overclocking? More specifically, overclocking where your custom freq. profiles are applied at boot?
Click to expand...
Click to collapse
I agree a new thread about this wouldnt belong in development, but i can't even post in the thread relating to the ROM until i have 10 posts.
I have not overclocked or undervolted or really edited anything about the rom in any way... I odin'd to stock, unlocked, rooted, loaded custom recovery, factory reset, wiped data, cache, dalvik, all that stuff, loaded release 5, rebooted, then back to recovery to fix permissions, then rebooted, then recovery to flash rom developers theme, then rebooted... worked well for 2 days, then this morning i keep getting "system granted superuser permissions" leading to multiple vibrations, freezing, and a reboot.
Related
My phone was working perfectly with an older version of the evil hero rom so 2 days ago I decided to update to the newest version which is v2xx or w/e and ever since then I have not been able to either go past the green mytouch boot up screen or If it does boot I cant login into my google account if I skip that step I can browse the web fine over 3g and wifi but cant login into the account...I have tried many different memory cards I have unrooted and re-rooted my phone like a million times now...if someone can just tell me whats going on...I flashed the engineering spl too .2005...I would post in general but it seems as if that section does not get as many hits as does the android development.
First of all.
If you were having several issues PRIOR to trying that laundry list of steps to go about solving the problem...YOU CONTINUED TO GET IN OVER YOUR HEAD! That's admirable that you made an (unsuccessful) attempt to go about fixing said issue on your own; but not worth it.
You were stuck on the SPLASH SCREEN - not locked in bootloop. Typically, if you didn't WIPE before an upgrade, that splash screen should remain for roughly 5-10 minutes depending on the range of changes made in the upgraded version of the ROM. Also, if you follow the developers thread on ROM features, you might want to re-read or properly describe exactly what you did, saw and tried to do ---> IN THAT THREAD!
My suggestion: Assuming that you backed up your ORIGINAL NANDROID from the stock "Cupcake" version of the OS...restore that backup, then start all over from the basics.
Reignzone said:
If you were having several issues PRIOR to trying that laundry list of steps to go about solving the problem...YOU CONTINUED TO GET IN OVER YOUR HEAD! That's admirable that you made an (unsuccessful) attempt to go about fixing said issue on your own; but not worth it.
You were stuck on the SPLASH SCREEN - not locked in bootloop. Typically, if you didn't WIPE before an upgrade, that splash screen should remain for roughly 5-10 minutes depending on the range of changes made in the upgraded version of the ROM. Also, if you follow the developers thread on ROM features, you might want to re-read or properly describe exactly what you did, saw and tried to do ---> IN THAT THREAD!
My suggestion: Assuming that you backed up your ORIGINAL NANDROID from the stock "Cupcake" version of the OS...restore that backup, then start all over from the basics.
Click to expand...
Click to collapse
Yo I did all of that im using the nandroid backup right now and I said I unrooted my phone and started from scratch and am still having the same issue and I always wipe before a new flash...its just frustrating that i cant login into the google account and the rom works fine other than that
also i never said that I bricked the phone or something the recovery is working and all...I have done all the basics I have the partitions and what not...the only reason Im posting here is to see if anyone know if certain mytouch's made after a day are having problems with root I saw it in some thread some where but wasnt able to find it I think it was mytouch's made after July 26th?
Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.
i have a samsung captivate i897.
i bought it sim free and unlocked from the states but i'm in the UK.
i recieved it already rooted running cyanogen mod and miui and have had it for 8 months. its worked perfectly the whole time.
until the past month i'd say its been radomly forcing closs on nearly everything.
i havent installed any new software or roms or anything or even dl any new apps so i cant figure out what would be causing the problem.
i tried checking for updateds on the muiu and it runs android 2.3.7
i'm not a tech person at all so i spoke to one of the tech guys at my local phone shop and he said i should try a factory reset.
so i guess i'm asking a few questions here:
1) does anyone have any idea what might be up with my phone?
2) can someone elplain to me the easiest/safest way to fix it?
please bear it mind i am a total noob at this tech stuff. i'll try to understand and cooperate as much as i can with those so kind to help me, but i'd really appreciate if people would help/point me in the right direction instead of giving me a short blunt answer which assumes i know all this tech stuff then locking my thread.
If it's already rooted & running a custom ROM, then you probably already have a custom recovery installed (probably clockworkmod). 1st thing would be to boot into recovery & do a backup. Then, you can try flashing any ROMs you want / factory reset / whatever, and restore your backup if you don't like the results.
-- Sent from my TouchPad using Communities
how do i know if i have clockwork mod installed (i've never seen it before, but then again if its on the boot menu where i've not been before)
for booting into recovery i just long press the power button (at least it works like this on my phone) > reboot > recovery > ok
then what should happen after i press "ok" ?
also just to state (if it helps) the options i get for rebooting are: normal, hot boot, bootloader & recovery.
i dont really feel confident to be flashing roms (mainly because i dont really know how/which are stable etc) on the other hand i do need to fix it. guess i'd like to try the factory reset first though..... under the assumption its slightly easier.
i thought factory reset would restore the phone back to stock settings? but the guy in the phone shop said it wouldnt? (not sure how reliable he is ;] )
found this thread here which seems kinda similar
http://forum.xda-developers.com/showthread.php?t=1264177&page=3
have tried uninstalling some apps to see if it helps.
the thing is with the problem is seems to occur randomly. the phone will work like perfect again for a few days then boom starts forcing close yet again.
only time will tell.
Hi! I realise this if my first post I'd like to tread lightly; but I'm about 4 days into solving my issues and I just want to finish it...
I've had my Nexus i9020a (bought from Koodo) since ~May 2012. I upgraded to ICS sometime in the summer and sometime in the last few weeks it has started rebooting. I hadn't been installing new apps, etc. I'm not sure what the cause is. I 'Factory Reset' today in an attempt to resolve the issue, thinking it may be a program gone AWOL; but it has rebooted a few times since. I *just* looked through rebooting FAQ on this site and have edited the first few features listed there. I'm not sure if it has worked yet, but I'll get back to you on that. For the record, the only programs I have installed now are Swiftkey 3, Handcent and Beats (DDR simulator, updated in November).
In the meantime, before I found the solutions here, I decided to take another shot at unlocking the bootloader and try installing... probably CyanogenMod.
Specs: Windows 7 64 bit with Nexus S I9020a (Koodo) running 4.0.4 (4.1.1/2 OTA haven't come through, despite dozens of attempts at clearing the GSF cache, etc)
So I've been using the Nexus S: Full Update Guide found at:
hxxp://wiki.cyanogenmod.org/wiki/Nexus_S:_Full_Update_Guide
(It won't let me post the link)
I've followed the guide for installing the Android SDK, gone to CMD and typed 'adb devices' and had it show up. Theoretically, the SDK should be running fine.
Next, I turned on the USB debug mode. Then I booted up the bootloader, plugged the NS into the PC... and despite not having issue when the it's turned on (driver installed properly) windows says drivers have not been found for the device. Thus, when I type fastboot devices, it comes up with nothing.
I've been, and will continue perusing forums for this, but so far I haven't seen anyone with this specific problem.
Edit: I have also gone to the directory with fastboot/adb and used cmd to reboot into the bootloader, only to have windows 'ding ding ding' an unrecognised device.
2nd Edit.
I've gotten a stage further! I'll keep the thread open because I may come across something and it's nice to write my issues down. Seems my head can wrap around the problem a bit better. Anyway, I installed PDAnet and BAM, it works. Onto getting CWM installed! Thanks for the, uh, help!
3rd Edit.
CyanogenMod 10.0 stable is booting for the first time!! It's taking a while... but I appear to be on the home stretch! Also, my phone didn't reboot for a few hours before I installed CM. So if I don't end up somehow bricking it... and I mean, this first boot is taking a heck of a long time... The animation sets me at least a bit at ease... maybe 4.0.4 will work out...
Edit 4
I forgot to clear the app and cache data before flashing the ROM to the phone and thus the issue... after a VERY tension filled moment of pulling the battery during first boot... I rebooted, cleared said data and reflashed the ROM. After a boot, I realised I forgot the GAPPS zip and fixed that. Now I'm running CM10 Stable!! I'm stoked that after months of putting it off cuz last time I did it I didn't get anywhere after many days, but now it's done!! Thanks again for such an awesome site!
Thanks for sharing your experience instead of just saying "Mods please delete this i solved my own problem" :good:
So it look like the JB OTA update is here for the USA. Mine is rooted, and has already download the update, but I haven't applied it yet, as I'm rooted and I don't know if I have to do something special first.....
Any one have any info on this?
Same Boat !!
Me too in same boat with P3113.See the post below yours :crying: Hope experts replies soon.
I went ahead and installed it on my daughters tab. CWM protected itself, and root. I'm still poking around, but thus far no issues beyond it says "update failed" but clearly didn't.
I'm wondering if I should remove CWM and unroot it first...
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Updated with Root ?
sheepdog elite said:
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Click to expand...
Click to collapse
So if i understand correctly , you allowed the OTA with root and it wiped data ? I am suprised it installed with Custom recovery !!!
I have over 200 user apps. Will i retain those Apps (dont mind data being wiped)
No, it didn't wipe data. I wasn't worried about it "if" it did, because it's my daughters, and I have TIBU for all her games from like last week.
Just to be perfectly clear. NOTHING went wrong. It installed the new O.S., booted fine, said the update failed, but the update didn't fail. Probably because CWM preserved root, and bootloader, so verification failed.
I ran it..... It updated thru CWM... Once done said update failed, but I had a new agreement to agree too. Sys info says its running 4.1.1.
If I have and issue, ill update here.
Failed for P3113
Based on your experience thought I would try too... Unfortunately failed miserably... I have Cwm 6.0.2.3 and attached is the crash log... Maybe some experts can give their views..
I guess I'll post my successful config just for the sake of comparison.
I'm currently running CWM 6.0.1.1. The tab was rooted with a file called gtab2_jellybean_rooter (think I got it from XDA, but i'm not positive) and had no other modifications/roms/etc.
If you're running any sort of ROM you're definitely boned, gotta wait for a ROM update. Beyond that, I'm not really sure what to say
To do the proper update, you should un-root and then re-root once done. That way you get the full support with your update if needed.
I am rooted, running CWM 6.0.2.3. I accepted the update and hit the install thinking that it would fail just as it does on a rooted SIII. The notification said the install had failed, but as others here have indicated, it appears as though the install was successful. I retained root and all seems to be normal; with one exception: It appears that the Tab no longer "sleeps" but shuts down completely. Regardless of whether I turn it off with the power button (short press) or if the screen simply goes to sleep, I have to long press the power button and it goes through a full boot.
Is anyone else experiencing this? Is there a setting I am missing? I am not a noob at rooting, etc. as I have been doing it since my OG Droid on Verizon, but it surprised me when the update seemed to install (even Google Now is working), and I am stumped about this "shut down" that seems to happen.
I experienced the same thing. I was rooted and had installed CM10, went back to original backup, using latest CWM. I hit system update and it downloaded the update, asked me to continue. CWM asked me if I wanted to install unsigned zip, I accepted, and it went through. At first boot it said update failed, but like everyone else, it went through. I have had no issues at all. My tab goes to sleep correctly.
Have peace in mind.
I finished updating (unfortunately, the battery was 9%, so I had to wait for an hour to charge before doing anything) and I got "failed" error like everybody got, but the system shows 4.1.1 and the performance is improved, and I applied root again.