Flashed a new rom yesterday. Actually, I just updated it on top of the previous version. Anyway, after flashing this, I 'lost' root. I thought it had somehow actually unrooted my phone after going into settings and turning superuser back on and it didn't work, so I decided just to root again. Went to do that, said it was already rooted, but I went ahead and rerooted. Did not work. ROM Manager and Titanium Backup will not work. However, I can shut the phone off and manually boot into cwm with no problem. I assumed when I flashed another rom, the issue would be taken care of, but today after not getting any signal, I reflashed a rom I had previously used with no problem, but when the phone is on, it acts as if it is not rooted. Any idea how to get my root back? Also, before you say it, I have never been able to restore any backup I've ever made. They all would say md5 mismatch, and I read the solution to this was to delete that file and just make another with the same name. I did that, but now when I try to restore it says error while restoring /system! Obviously, I do not know much about these things so please go easy on me. Thank you in advance for any help and suggestions!
EDIT: Flashed back to cm 10.1 and root seems to be back, but I would still like some insight into why none of my backups will ever restore. I obviously have to be or have done something wrong.
Celeste8157 said:
Flashed a new rom yesterday. Actually, I just updated it on top of the previous version. Anyway, after flashing this, I 'lost' root. I thought it had somehow actually unrooted my phone after going into settings and turning superuser back on and it didn't work, so I decided just to root again. Went to do that, said it was already rooted, but I went ahead and rerooted. Did not work. ROM Manager and Titanium Backup will not work. However, I can shut the phone off and manually boot into cwm with no problem. I assumed when I flashed another rom, the issue would be taken care of, but today after not getting any signal, I reflashed a rom I had previously used with no problem, but when the phone is on, it acts as if it is not rooted. Any idea how to get my root back? Also, before you say it, I have never been able to restore any backup I've ever made. They all would say md5 mismatch, and I read the solution to this was to delete that file and just make another with the same name. I did that, but now when I try to restore it says error while restoring /system! Obviously, I do not know much about these things so please go easy on me. Thank you in advance for any help and suggestions!
EDIT: Flashed back to cm 10.1 and root seems to be back, but I would still like some insight into why none of my backups will ever restore. I obviously have to be or have done something wrong.
Click to expand...
Click to collapse
Couple of things come to mind...
1) Did you open an app called SuperUser and make sure that TiBu was set to "Okay" or "Allow" whichever the option is
2) When you open terminal and type su does the $ change to a # --- if Yes then you are Rooted
EDIT --
Also what ROM did you flash that seemingly caused you to loose ROOT access?
Related
Hello, I need some help with restoring via CWM on the Galaxy S3.
On the S2 I pretty much always used CM9 and jumped back and forth between versions and backing up/ restoring was never an issue.
Now however I am using the stock ROM and its rooted of course.
I made a back up of my stock rom 'cause I wanted to try and install some stuff.
I tried installing the jelly bean transition effects but the install failed, the device felt kinda sluggish (maybe my imagination) afterwards so I decided to restore my phone. The restoring went good but the last ting that happens is that CWM says that restoring /Data failed.
I reboot my phone and I come to the first start up screen where I get to choose language and so on. Everything but photos has been deleted. I try to install CM9, and I do that without any issues. Then I trie to backup my stock backup but I get the same error message and I get back to stock setup page.
My backup is a staggering 6GB, and I read somewhere that CWM can only restore 2GB?
I've deleted that backup and done another one but that is also 6GB.
Does anyone know how to restore from that first restore or how to make future restores work?
undegaard said:
Hello, I need some help with restoring via CWM on the Galaxy S3.
On the S2 I pretty much always used CM9 and jumped back and forth between versions and backing up/ restoring was never an issue.
Now however I am using the stock ROM and its rooted of course.
I made a back up of my stock rom 'cause I wanted to try and install some stuff.
I tried installing the jelly bean transition effects but the install failed, the device felt kinda sluggish (maybe my imagination) afterwards so I decided to restore my phone. The restoring went good but the last ting that happens is that CWM says that restoring /Data failed.
I reboot my phone and I come to the first start up screen where I get to choose language and so on. Everything but photos has been deleted. I try to install CM9, and I do that without any issues. Then I trie to backup my stock backup but I get the same error message and I get back to stock setup page.
My backup is a staggering 6GB, and I read somewhere that CWM can only restore 2GB?
I've deleted that backup and done another one but that is also 6GB.
Does anyone know how to restore from that first restore or how to make future restores work?
Click to expand...
Click to collapse
I had this problem with my sisters Xperia X8,couldn't restore anything that i backed up.It goes for a while and stops.But she had bootloader locked.I was shore that i unlocked her bootloader but i didn't,so i unlocked bootloader,and tried to backup and restore and it worked fine.
I'm not 100% and i don't know is that the way CWM works,but i think in order to restore your data,that you backed up,you have to unlock your bootloader.But it's the best to wait someone who knows this for 100% sure.
If you haven't unlocked bootloader try that,or you don't won't to lose your warranty!?
Good luck!
I don't think that CWM has size limitation but i can be wrong.
Have you made sure that your CWM is up-to-date? if in doubt flash the latest CF-root.
was there ever a resolution to this problem? I did the same thing, rooted the galaxy s 3 and unlock the bootloader. Get a backup of my stock set up using clockwork recovery mod. Now when I try to restore, it does not restore the data. All of my apps look like they are there, but none of them are really installed. I think I can just reinstall all of the apps by hand, I would like to know how to get over this.
Background
Used many hours to set up phone to my liking. Got a problem with earphone-jack, so i handed it in. I couldnt do a proper backup beforehand, cause this required root access. The earphone-jack got replaced, but they also decided to upgrade my phone to the newest firmware? , deleting everything in the process. I will set everything up again in the weekend, but i do NOT want to do this a third time .
I have searched around for guides, but since i cant find a LQ6 kernel, every guide is telling me to use a different kernel. The best thing would be to root only. Does this work with my phone ?
What i need
Root only
Ability to unroot would also be nice
About phone
Model: GT-I9100
Android v. 4.0.4
Baseband: I9100XXLQ6
Kernel: 3.0.15-1068762 [email protected] #3 SMP PREEMPT Wed Aug 29 13:40:41 KST 2012
Build: IMM76D.XWLPX
Other Question
If i get another problem with the phone, backup everything, unroot and hand it in. If they decide to upgrade my firmware again, will i still be able to restore my backup ? What backup program is best to use in your opinion ? I want app settings, launcher settings and homescreen setup to be backed up.
HELP : GOT TWO NEW QUESTIONS
I tried to follow the guide in "theunderling"s signature.
At first i thought the files were supposed to be on the internal SD card, so i put them there and rebooted the phone into recovery. While there i tried to find my files, of course to no luck. I thought that maybe i had to unplug the USB, so i did this while in rec. menu. Still didnt find the files, so i rebooted my phone. Suddenly there were a REALLY LOUD ALARM NOISE coming from my phone. I have never heard that sound from my phone before. It stopped after a while, but has also happened at random times since. WHAT IS THIS ? (To be clear: this came before i ran any of the downloaded programs/scripts/etc).
After this i found an external SD - card and put the files on this. Got root access in a couple of seconds, and everything seemed fine. But now my computer refuses to connect to the phone "couldnt find hardware-ID" or something (Translated from my windows language, so might not be 100 % accurate. HOW TO FIX ?
BTW Thank you all so much for your time. I really appreciate it
1.use the guide in my sig or flash a siyah rooted kernel.
2.a nand backup.
3.you can just flash the firmware you listed back on your phone and that would unroot it.
Download it from sammobile now and keep it on your pc if you need it later(and keep nand backup there also).
4.if you get it back,reroot again and put the nand backup back on your sd card and flash that in cwm.
Dont forget to back up efs folder once you root(keep that on pc).
1. Do as theunderling said, or you can use the PhilZ-CWM6 kernel, which is pure stock based. http://forum.xda-developers.com/showthread.php?t=1877270
2. Do a NANDROID backup. Make sure to have atleast 1.1GB available on your MicroSD card. This is done in CWM recovery.
3. To unroot, I believe flashing a stock kernel will do the job, if you only have flashed a kernel. Also, the SuperSU app included in the PhilZ kernel has an unroot option.
Also, backup you EFS folder. And have atleast two backups of it.
Ignore my no.3 as I was thinking you would be installing a rom later.
That rooting method I said also lets you unroot.
Hi. Thanks so much for your answers. When rooting my phone, two problems arose (See original post). Would be really grateful for any input on those.
Never heard of an alarm sound happening-maybe you set alarm/event.
Anyway,what stage are you at.Are you definitely rooted.Is the phone booting as normal and can you access recovery/download mode.
theunderling said:
Never heard of an alarm sound happening-maybe you set alarm/event.
Anyway,what stage are you at.Are you definitely rooted.Is the phone booting as normal and can you access recovery/download mode.
Click to expand...
Click to collapse
Hi! Did check around for any events/alarms, and im sure its not the issue. Since i couldnt connect to my phone via USB, i tried Kies Air, and the alarm sound started again. Tried a few times, and EVERY time i start Kies air, i will get this sound for 5-10 seconds. It also happened twice when i werent even touching the phone :/
I have tried two programs which require SU - access. Got a prompt when starting them , and they worked fine . Kies Air works fine too btw. (Its the USB - connection that i cant get to work).
Also: For some reason i had SUPERUSER installed from before, and now i cant uninstall it again. Also, when i gave the two programs i tested superuser access, it showed the SUPERUSER icon. (program in big letters)
Just to make it clear again: The alarm sound came after i had fooled around in recovery mode, before ANYTHING where installed.
Youve not answered the previous questions.
You should be flashing a "safe" siyah kernel and backing up your efs folder.You can make a nand backup before that or after.
Just get the .zip file from gohkmoran site and flash via cwm.Then get hktool from play store for your efs.
Then the alarm/usb/pc problems can be looked into.
theunderling said:
Youve not answered the previous questions.
You should be flashing a "safe" siyah kernel and backing up your efs folder.You can make a nand backup before that or after.
Just get the .zip file from gohkmoran site and flash via cwm.Then get hktool from play store for your efs.
Then the alarm/usb/pc problems can be looked into.
Click to expand...
Click to collapse
Sorry, here are some more info:
Download modeI get a warning screen against installing custom os? volume up for install and volume down for reboot. Have never tried DL boot before, so cant say anything about this one
Recovery mode Boots normal and looks exactly like earlier.
Normal Boot Looks like before i rooted. No new programs either.
Could you link directly to which kernel i should use ? I have no idea :/ sry
Sorry,I should have explained a bit more.
Get the siyah kernel file and put it on your sdcard/internalsd
Do the rachmat stuff again.Once you install cwm.zip and su-busybox.zip..........dont reboot.
Install the siyah-s2-v4.01cwm.zip file (whilst your still in temp cwm)you download from his site(google should take you to the file).
Then you end up with a safe kernel and permanent cwm.
Then you can do nand and efs backups
theunderling said:
Sorry,I should have explained a bit more.
Get the siyah kernel file and put it on your sdcard/internalsd
Do the rachmat stuff again.Once you install cwm.zip and su-busybox.zip..........dont reboot.
Install the siyah-s2-v4.01cwm.zip file (whilst your still in temp cwm)you download from his site(google should take you to the file).
Then you end up with a safe kernel and permanent cwm.
Then you can do nand and efs backups
Click to expand...
Click to collapse
What i did
Resetted to factory settings
Installed cwm.zip
Installed su-busybox.zip
Installed Siyah-s2-v4.1.5-CWM.zip
What i got
No more funky alarms. Neither with kies, or any other program. :good:
Pc connection works if i put it in mass storage mode :good:
Got a CWM app, which i used to take a nandroid backup :good:
Still cant find hardware ID. (So i still cant just connect and open folder)
Thanks so much
Most important is the connection thingy (in case its something "serious" But if you feel in an extremely helpful mood, i got two more questions.
For unrooting To unroot i probably need to:
Flash Stock Kernel (from where ???)
install SU-Uninstaller-Signed.zip
What about CWM and SuperUser. How do i get rid of those 2 ?
Backup
For more advanced backup (backup individual apps etc), I `ve heard about a couple different apps: Titanium Pro and Superuser Elite. Do you recommend one of these?
Try this for your hardware problem.I never use kies as its ****
You can use this,or go to sammobile and flash xwlpx to get back to stock.
You can use titanium backup to backup your apps and also "remove" crappy system apps etc(theres a thread that guides you what to/what is safe to remove).
And get your efs backed up.
theunderling said:
You can use this,or go to sammobile and flash xwlpx to get back to stock.
You can use titanium backup to backup your apps and also "remove" crappy system apps etc(theres a thread that guides you what to/what is safe to remove).
And get your efs backed up.
Click to expand...
Click to collapse
Thanks again!!
I dont like Kies either, but wanted to fix my problem of 2 reasons
- I was afraid it was a symptom of something serious
- MDP mode without kies is nice to use when you only need to upload a few files to your phone on the go
WELL, KIES WAS THE SOURCE OF MY PROBLEMS. When i uninstalled Kies - drivers, it worked perfectly.
Have taken backup of my efs now (with HC-Ktool, which i assume u meant ), so now i will start setting up my phone to my liking. Thanks so much :highfive:
So basically got everything i came for
But, hmm still unsure if i will get completely unrooted phone from flashing stock kernel and removing SU. Wont the CWM that came with Siyah still be installed ? Can i uninstall this normally afterwards ? Or can i uninstall it before i remove superuser, and then use the CWM -booter thingy to get rid of SU ?? Hmm sorry for being such a noob.
slimchancex said:
Thanks again!!
I dont like Kies either, but wanted to fix my problem of 2 reasons
- I was afraid it was a symptom of something serious
- MDP mode without kies is nice to use when you only need to upload a few files to your phone on the go
WELL, KIES WAS THE SOURCE OF MY PROBLEMS. When i uninstalled Kies - drivers, it worked perfectly.
Have taken backup of my efs now (with HC-Ktool, which i assume u meant ), so now i will start setting up my phone to my liking. Thanks so much :highfive:
So basically got everything i came for
But, hmm still unsure if i will get completely unrooted phone from flashing stock kernel and removing SU. Wont the CWM that came with Siyah still be installed ? Can i uninstall this normally afterwards ? Or can i uninstall it before i remove superuser, and then use the CWM -booter thingy to get rid of SU ?? Hmm sorry for being such a noob.
Click to expand...
Click to collapse
I am sure that flashing a stock kernel will unroot your phone, kill me if I am worng . (I am noob also.)
CWM will be removed once your on the stock kernel.
Once you set up your phone,make a nand backup of that.
You want to able to use usb so you can use Odin,especially if something goes wrong flashing something and you cant boot phone, or into cwm.
Flashing a stock rom unroots the phone.For warranty,you go into download mode and check binary is at zero,and official firmware is at yes.
I was going to post this in reply to this thread, but since I'm new it won't let me: http://forum.xda-developers.com/showthread.php?t=1905674&page=165
So here's my problem. We have 2 Nabi's in our house both rooted with Gapps installed. One is working fine, one was having issues with charging and the screen locking up. I decided to try to un-root the one with the problems and see if I could get a replacement. I then realized that there was a software update, so I decided to try to update first before being without a tablet for any amount of time for a warranty issue.
My plan was to restore to a backup I had, install the OTA update, then re-root it and install Gapps again. All went well with the restore and OTA update, but now I'm stuck at not being able to install root or gapps! I get no errors on the scripts and everything seems to complete fine, but when I boot up again there is no root and no gapps. Post 1647 in the link above indicates it could be a space issue which makes sense, but now my question is how do I delete anything in the system/vendor/app folder without root access?
Both root.zip and gapps.zip were pushed to the tablet and when I select install through TWRP it goes through the process really quick with no errors and says it is complete, but it doesn't appear to be actually doing anything.
Any help/advice is greatly appreciated!
Ok, I think I may have figured this out. I ended up restoring back to my un-rooted stock backup which took me back to version 2.05 with no modifications. I was then able to install root and gapps. I then used the update file provided here to update:
http://forum.xda-developers.com/showpost.php?p=45369304&postcount=1605
When I tried this file the first time before doing any sort of restores it kept failing because I was missing a bunch of files after going delete happy to get rid of all of the bloat. Since I restored to the stock backup it installed fine and I'm now on 2.1 after almost a whole day of messing with this. Now I just have to remove all of the bloat again and restore apps.
So is it safe to say there is an issue with 2.1 and the standard root/gapps files? At least now I know before I try to update the other daughter's tablet. Now to see if the update resolved some of the issues we've been having with this one....
I hope i'm not overlooking a thread where this was a problem but i'm at a loss after looking for 3 days. I was running Tonked world edition v2 (android 4.0.3) without problems for almost a year when I saw that 4.3 PAC was released for the Rezound and I thought I would try it out. It was a lot of fun but I use my tablet for most everything and world edition seemed to give better battery life. Everything worked fine with PAC when it was running and I got world edition restored just fine but for some reason superuser is acting really weird. It would allow any app that had super user permissions before the upgrade to work fine but any new app that needed root permissions after the restore is not working. I've been using Root Checker after each trial to see if root access has been restored and nothing works. Not even a request for root permissions shows up. I booted up the phone using adb to make sure I had boot access and flashed both superuser app 3.1.3 and 3.2-RC3 and also tried just the binaries 3.1.1 (each individually of course). After trying to flash superuser through recovery even though the apps listed in superuser were stil there nothing was being granted super user access anymore. I noticed that su in system/bin didn't have correct permissions and root browser wasn't able to change anything after losing root permissions so I used adb shell to try and change permissions, which I was able to change, but it didn't do anything to help the problem. The weird thing is even after wiping the system, cache, and davilk multiple times and a fresh install of the rom the same problem persists. The only thing I can think of is somehow the built in superuser app (part of aokp) is still interfearing with superuser somehow but I have no idea and like I said i'm stil at a loss of what else to try.
I apologize in advance if this has been answered somewhere eles but if anyone can point me in the right direction I would be very greatful.
I appreciate any help in advance and even the slightest advice will be helpful, thanks again.
czach5932 said:
I hope i'm not overlooking a thread where this was a problem but i'm at a loss after looking for 3 days. I was running Tonked world edition v2 (android 4.0.3) without problems for almost a year when I saw that 4.3 PAC was released for the Rezound and I thought I would try it out. It was a lot of fun but I use my tablet for most everything and world edition seemed to give better battery life. Everything worked fine with PAC when it was running and I got world edition restored just fine but for some reason superuser is acting really weird. It would allow any app that had super user permissions before the upgrade to work fine but any new app that needed root permissions after the restore is not working. I've been using Root Checker after each trial to see if root access has been restored and nothing works. Not even a request for root permissions shows up. I booted up the phone using adb to make sure I had boot access and flashed both superuser app 3.1.3 and 3.2-RC3 and also tried just the binaries 3.1.1 (each individually of course). After trying to flash superuser through recovery even though the apps listed in superuser were stil there nothing was being granted super user access anymore. I noticed that su in system/bin didn't have correct permissions and root browser wasn't able to change anything after losing root permissions so I used adb shell to try and change permissions, which I was able to change, but it didn't do anything to help the problem. The weird thing is even after wiping the system, cache, and davilk multiple times and a fresh install of the rom the same problem persists. The only thing I can think of is somehow the built in superuser app (part of aokp) is still interfearing with superuser somehow but I have no idea and like I said i'm stil at a loss of what else to try.
I apologize in advance if this has been answered somewhere eles but if anyone can point me in the right direction I would be very greatful.
I appreciate any help in advance and even the slightest advice will be helpful, thanks again.
Click to expand...
Click to collapse
go to settings> about phone> and tap build number until deveoloper options are available....when enabled go back into settings and go to developer options and ensure root access has access to apps and adb
REV3NT3CH said:
go to settings> about phone> and tap build number until deveoloper options are available....when enabled go back into settings and go to developer options and ensure root access has access to apps and adb
Click to expand...
Click to collapse
Developers options were already visible from the beginning with the Rom but that option to restrict root to apps and/or adb isn't there (at least on 4.0). I know the setting your talking about and I'm going to see if there is another way to enable it.
czach5932 said:
Developers options were already visible from the beginning with the Rom but that option to restrict root to apps and/or adb isn't there (at least on 4.0). I know the setting your talking about and I'm going to see if there is another way to enable it.
Click to expand...
Click to collapse
what recovery did you try to install superuser from
I would assume your current rom has SU built in, may want to consider a clean install. At least back up your current one and install it clean (with no app data restored) to see if it fixes the problem.
REV3NT3CH said:
what recovery did you try to install superuser from
Click to expand...
Click to collapse
CWM based recovery by Flyhalf205 v6.0.1.9
Never had any problem until now. I tried Amon-ra a long time ago but it wouldn't wipe correctly sip I've stuck work this one
mjones73 said:
I would assume your current rom has SU built in, may want to consider a clean install. At least back up your current one and install it clean (with no app data restored) to see if it fixes the problem.
Click to expand...
Click to collapse
This Rom doesn't have su built in and I've tried about every combination of wipes, flashes, and restores
-Trial-
I noticed that in system/bin that there were two files, su and su.bak su was at 0 bytes and su.bak was at 23k and I tried switching them around and also giving su.bak (renamed to su) full 777 permissions but nothing worked. After the file modification root checker failed much quicker though. Changed everything back
I just noticed after changing everything back that su had its permissions changed again. It is listed as -rwsr-sr-x which is full read only user write and full execute with suid and sgid special. I'm trying to find out but I can't find how to give all permisions with suid and sgid. Any idea if any of this helps or is the culprit?
czach5932 said:
CWM based recovery by Flyhalf205 v6.0.1.9
Never had any problem until now. I tried Amon-ra a long time ago but it wouldn't wipe correctly sip I've stuck work this one
This Rom doesn't have su built in and I've tried about every combination of wipes, flashes, and restores
-Trial-
I noticed that in system/bin that there were two files, su and su.bak su was at 0 bytes and su.bak was at 23k and I tried switching them around and also giving su.bak (renamed to su) full 777 permissions but nothing worked. After the file modification root checker failed much quicker though. Changed everything back
I just noticed after changing everything back that su had its permissions changed again. It is listed as -rwsr-sr-x which is full read only user write and full execute with suid and sgid special. I'm trying to find out but I can't find how to give all permisions with suid and sgid. Any idea if any of this helps or is the culprit?
Click to expand...
Click to collapse
install AMON RA 3.16 as it has the super user fixed into it under advanced....once installed just reflash your custom recovery of your choice....also that version of cwm is way out of date you want version 6.0.3.6...they get updated for many reasons such as stuff like this
czach5932 said:
CWM based recovery by Flyhalf205 v6.0.1.9
Never had any problem until now. I tried Amon-ra a long time ago but it wouldn't wipe correctly sip I've stuck work this one
This Rom doesn't have su built in and I've tried about every combination of wipes, flashes, and restores.
Click to expand...
Click to collapse
Kind of surprising someone would release a modded Sense ROM with no su..
Sent from my ADR6425LVW using Tapatalk
I'll try that as soon as I can. I figured why change something if it's not broken. I appreciate the help and I'll report back as soon as I can
- UPDATE-
Tried to use Amon-RA 3.16 and use the SU fix option under advanced options. It removed my other super user app and replaced it but nothing changed, no popup to ask for super user permissions. After that I booted up cwm 6.0.3.6 touch a couple of times and like it so I decided to flash it and now data and wi-fi are not working. But before flashing, I booted it up a couple time and tried wiping everything (3x) and tried both a clean install and a restore and same problem. Neither the Amon-RA, 3.1, or the 3.2 nor the manually flashed binarys do anything. I also found how to change the premissions for su but now when I try to chmod anything it says read only system. Seems like i'm going backwards and making no progress.
I still appreciate any and all help.
Sent from my SCH-i815 using XDA Premium HD app
czach5932 said:
I'll try that as soon as I can. I figured why change something if it's not broken. I appreciate the help and I'll report back as soon as I can
Sent from my SCH-i815 using XDA Premium HD app
Click to expand...
Click to collapse
also if im not mistaken...tonked had a mass multitude of issues for me....if you need the phone for global use and trying to stay stock and stable as possible there is much better options...to further help...for all ICS roms and lower use Amon Ra 3.16 period...for anything higher like jellybean or kitkat use cwm or twrp...amon ra was meant for the earlier roms as cwm and twrp were not
REV3NT3CH said:
also if im not mistaken...tonked had a mass multitude of issues for me....if you need the phone for global use and trying to stay stock and stable as possible there is much better options...to further help...for all ICS roms and lower use Amon Ra 3.16 period...for anything higher like jellybean or kitkat use cwm or twrp...amon ra was meant for the earlier roms as cwm and twrp were not
Click to expand...
Click to collapse
When I rooted my phone initially Amon-ra it wouldn't wipe correctly and kept force closing everything which is why I went with cwm. Before I went to pac and android 4.3 everything worked perfectly. I just don't understand why (with full wipes) and a restore with upgraded recoveries something from 4.3 is still messing with the system.
The main thing I want is longest battery life and if you can suggest something I'll try it but Tonked gave me over three days on one charge with minimal use. I could get 6+ hrs talk time with hours of Mog with a single charge. I'll try anything. My screen is cracked so I'm thinking of using warranty and get a refurbished phone and restoring that way but I don't want to be out a hundred bucks.
czach5932 said:
When I rooted my phone initially Amon-ra it wouldn't wipe correctly and kept force closing everything which is why I went with cwm. Before I went to pac and android 4.3 everything worked perfectly. I just don't understand why (with full wipes) and a restore with upgraded recoveries something from 4.3 is still messing with the system.
The main thing I want is longest battery life and if you can suggest something I'll try it but Tonked gave me over three days on one charge with minimal use. I could get 6+ hrs talk time with hours of Mog with a single charge. I'll try anything. My screen is cracked so I'm thinking of using warranty and get a refurbished phone and restoring that way but I don't want to be out a hundred bucks.
Click to expand...
Click to collapse
because with any recovery...a full clean wipe meaning you wipe cache, dalvik cache, system, boot, data, factory wipe, and android secure. you still have the main internal files that never get touched by any recovery....if your s-off you can run my downgrade upgrade guide to get back to full stock as the ruu's fully wipe everything....ive actually managed with both talon 1.0 and tachyon to get 24+ hourse of normal use
REV3NT3CH said:
because with any recovery...a full clean wipe meaning you wipe cache, dalvik cache, system, boot, data, factory wipe, and android secure. you still have the main internal files that never get touched by any recovery....if your s-off you can run my downgrade upgrade guide to get back to full stock as the ruu's fully wipe everything....ive actually managed with both talon 1.0 and tachyon to get 24+ hourse of normal use
Click to expand...
Click to collapse
But how would flashing pac modify anything that a full restore wouldn't change back? I know I used a ruu before, maybe I need to go and do that back to bone stock and upgrade from there. I go out of town for a couple of days and I'll try that and let you know. If you can think of anything else I will be greatly appreciative. Thanks Austin.
czach5932 said:
But how would flashing pac modify anything that a full restore wouldn't change back? I know I used a ruu before, maybe I need to go and do that back to bone stock and upgrade from there. I go out of town for a couple of days and I'll try that and let you know. If you can think of anything else I will be greatly appreciative. Thanks Austin.
Click to expand...
Click to collapse
again...most recoveries only wipes so much to an extent....even most samsung devices no matter how much you wipe in recovery you will eventually have to odin back to stock to start fresh as certain things are left behind from flashes...im only assuming some of your issues on 4.3 was sd mounting issues as well as rebooting....in the posts for them are the fixes for those issues...some of which requires TWRP only to fix...twrp is more stable than any of the recoveries because it has the fullest amount of wiping methods that you can ask for and always gets the job done right...get 2.6.3.0 as 2.6.3.3 is for kit kat only
REV3NT3CH said:
also if im not mistaken...tonked had a mass multitude of issues for me....if you need the phone for global use and trying to stay stock and stable as possible there is much better options...to further help...for all ICS roms and lower use Amon Ra 3.16 period...for anything higher like jellybean or kitkat use cwm or twrp...amon ra was meant for the earlier roms as cwm and twrp were not
Click to expand...
Click to collapse
Not sure if I have time this weekend but I just read your s-off tutorial and it seems straight forward but what I'm wondering about is going back to stock. Do I have to go all the way back to stock or could I just use the most recent ruu on your downgrade tutorial to get close enough to stock to wipe the rest of 4.3 and then go back to my Tonked Rom?
Never mind read the tutorial wrong. Will hopefully try this later and I'm hoping to get everything back to normal.
I didn't have time for s-off or time to go back to bone stock (your tutorial) but I did flash the latest ruu and got it to boot to bone stock ics and then flashed the same Tonked Rom and it booted and runs just fine but the only thing that it's granted su access is su itself. No time to mess with anything else yet but looks like I'm running out of options. I'll try your tutorial if I can.
czach5932 said:
I didn't have time for s-off or time to go back to bone stock (your tutorial) but I did flash the latest ruu and got it to boot to bone stock ics and then flashed the same Tonked Rom and it booted and runs just fine but the only thing that it's granted su access is su itself. No time to mess with anything else yet but looks like I'm running out of options. I'll try your tutorial if I can.
Click to expand...
Click to collapse
ha ok i see what you did....when flashing that ph98img file you wiped everything....even superuser....re download amon ra 3.1.6 recovery and install su&superuser via developer options in that and youll have su again
REV3NT3CH said:
ha ok i see what you did....when flashing that ph98img file you wiped everything....even superuser....re download amon ra 3.1.6 recovery and install su&superuser via developer options in that and youll have su again
Click to expand...
Click to collapse
Well even though I tried this before flashing the ruu but after flashing supersu in recovery everything is working correctly. i'm not sure why though but I lost both my two recent cwm backups (even though I used spare sd card during ruu flash). When I went to restore from my main 64 gig sd card, even tough the folder with the date showed up, when I went to restore it said no backup avail (or something like that) and then the folder disapeared. Also haven't had time to figure why backup disappeared or if any backups are currently working but i'll cross that bridge when I get time.
But back to the main issue. Looks like superuser has been having problems with a recent update where people were having the same problem I was having. I attributed it to downgrading but looks like a faulty app update (even though when I tried to look into it no one had said the update had any problems) I guess the upside was I wanted to reset my rom to stock and kinda reset, not really the way I wanted to do it, but lemons to lemonade. I really appreciate all the help and sorry for the stupid problem.
Hey guys, hope I'm posting in the correct section! (I have a verizon gs4)
I've wanted to root my gs4 for awhile now and have done quite a bit of research on this but am still confused on some things.
Is there anyway to backup my current ROM along with all my current settings before I root my phone? My pictures, contacts and apps are taken care of but as far as everything else goes, I'd like to be able to somehow revert back to how my phone is now if anything went wrong. I've downloaded ROM Manager and am trying to backup using CWM but keep getting error messages, such as "an error occured while attempting to run privileged commands" or "an error occurred while flashing your recovery", which makes me think it wants my phone to be rooted first in order to work.
If I were to root my phone, would I be able to use CWM and basically copy my UI as it is now? If I were to want to revert back to my current settings, could I then load my recovery from CWM, then unroot my phone somehow?
I apologize for sounding like a complete noob but greatly appreciate any help! I'm very eager to get this going but just want to make sure I know how to get back to where I started.
Can a Mod please delete this thread? I was drunk last night and posted this.
My phone is now rooted and backed up.
Many Thanks.