Related
For some reason, I keep losing root privileges. This has happened on 2 roms now. What am I doing wrong??
Sent from my Desire HD using XDA App
Are you using rooted ROMs or stock ROMs?
If the ROM you are flashing is a stock RUU then you will lose root.
Which ROMs are you trying?
How did you obtain root?
Have you got Radio and ENG S-OFF?
What recovery version are you using?
What method are you using to flash the ROMs?
Ive been using RCMix 6.1.0.1 and now Levo 1.3. Haven't had a problem with anything before when I've ran cm7 or froyo roms, or muiu.
Sent from my Desire HD using XDA App
I'm using the latest recovery. And have eng off. I haven't had problems until these last couple of weeks. And I've been rooted since December
Sent from my Desire HD using XDA App
What method are you using to get root back?
And I know it's a daft question but bear with me: What is happening that makes you suspect you are losing root?
I applied full wipe then flashed a new Rom. I thought it was rcmix to begin with but apparently not. Could it be something to do with recovery? All I've done is flash the ril and a different theme.
Sent from my Desire HD using XDA App
monkmeister901 said:
I applied full wipe then flashed a new Rom. I thought it was rcmix to begin with but apparently not. Could it be something to do with recovery? All I've done is flash the ril and a different theme.
Click to expand...
Click to collapse
Don't know yet.
Mr_JMM said:
How did you obtain root?
What recovery version are you using?
Click to expand...
Click to collapse
Mr_JMM said:
And I know it's a daft question but bear with me: What is happening that makes you suspect you are losing root?
Click to expand...
Click to collapse
At the risk of sounding rude, I'm asking these questions for a reason.
I used visionary to root. Had to downgrade originally.
I am using 3.0.2.6 cwm.
I'm not sure what I have done. As I said I've not had problems before whilst using other roms, just 2.3 with sense.
I think I might just revert back to cm7.
Sent from my Desire HD using XDA App
Maybeyou'll answer if someone else asks What makes you think you are losing root, and how do you get it back ?
ghostofcain said:
Maybeyou'll answer if someone else asks What makes you think you are losing root, and how do you get it back ?
Click to expand...
Click to collapse
Nice one, cheers. Thought maybe I was going mad or writing in a foreign language or something.
monkmeister901 said:
I used visionary to root.
Click to expand...
Click to collapse
Are you selecting Temp Root only or do you choose Attempt Perm Root as well?
Are you checking the options box to ensure the changes stick after reboot?
And one that's just occurred to me, what makes you think you are losing root?
I'm not sure why this is occuring. I was hoping someone might gave an idea. I have done nothing different this time than in previous occasions.
To get root permissions back, I have to full wipe the phone, using the full wipe zip. I then reflashed a new rom (from rcmix to levo) which then gave me a fully functioning rooted phone again. However, the same issue has now come back.
Permroot was achieved ages a go. I have flashed many custom roms, radios, bootanimations etc. This has only happened in the last week.
When going to setcpu, it says phone does not have root permissions, this is the same in rom manager, gscript lite and titanium backup.
monkmeister901 said:
I'm not sure why this is occuring. I was hoping someone might gave an idea. I have done nothing different this time than in previous occasions.
To get root permissions back, I have to full wipe the phone, using the full wipe zip. I then reflashed a new rom (from rcmix to levo) which then gave me a fully functioning rooted phone again. However, the same issue has now come back.
Click to expand...
Click to collapse
After you flash a new ROM does root disappear randomly a few days later or only the first time you flash the ROM (meaning you have to keep flashing ROMs twice)?
I get all the benefits of rooting back when i flash a rom for the 1st time. The lose it later.
I updated to cwm 3.0.2.8 then went back to 3.0.2.6 because it is the one rom manager recognises. Could this be an issue?
monkmeister901 said:
I get all the benefits of rooting back when i flash a rom for the 1st time. The lose it later.
I updated to cwm 3.0.2.8 then went back to 3.0.2.6 because it is the one rom manager recognises. Could this be an issue?
Click to expand...
Click to collapse
To be honest I have never heard of root just suddenly not working.
Have you got the superuser app installed? Are your running any task killers apps?
Did you use ROM Manager to flash the .2.6 recovery?
There's two versions of those easy-wipe zip things (don't use or like them myself), are you using the full wipe one? If so, to rule it out do the wipes manually in recovery before flashing the ROMs
Mr_JMM said:
To be honest I have never heard of root just suddenly not working.
Click to expand...
Click to collapse
Now you have!
Recovery was installed via Rom manager. Do you think flashing a new recovery image could help?
Mr_JMM said:
There's two versions of those easy-wipe zip things (don't use or like them myself), are you using the full wipe one? If so, to rule it out do the wipes manually in recovery before flashing the ROMs
Click to expand...
Click to collapse
I don't normally use the either. Just thought this could solve the problem.
Sent from my Desire HD using XDA App
Mr_JMM said:
Have you got the superuser app installed? Are your running any task killers apps?
Click to expand...
Click to collapse
???
Are you checking and confimring the MD5HASH of the ROM files (all files) before flashing them?
monkmeister901 said:
Recovery was installed via Rom manager. Do you think flashing a new recovery image could help?
Click to expand...
Click to collapse
Will answer that one after I know above.
I've had this happen a number of times on various ROM's such as Cyanogen, CoreDroid, RCHDMix etc... on each occasion nothing was changed that would have triggered a sudden failure of SU privileges. So, the reasons behind this remain a mystery (possible SU bug during ROM startup maybe that continues with all other restarts after?).
However, to remedy the problem I had to go to recovery menu and performed a wipe/reflash.
Annoying... yes. But as long as you do regular back up's then it's only 15 minutes to perform a full recovery and reinstallation of everything.
So far I've been using CoreDroid v6 since it was released without any issues like this (yet!).
Just to confirm, if you still have the SuperUser app installed, do your authorised apps still appear with a green dot next to them?)..
Superuser is installed and has green dots by those apps in need of such privileges. I don't use task managers.
I check md5 sums before flashing.
I have now fully wiped manually and restored a backup. SU privileges are back. I will not change anything and see if I lose them again or if its just me.
Thanks for all the input
Sent from my Desire HD using XDA App
monkmeister901 said:
Superuser is installed and has green dots by those apps in need of such privileges. I don't use task managers.
I check md5 sums before flashing.
I have now fully wiped manually and restored a backup. SU privileges are back. I will not change anything and see if I lose them again or if its just me.
Thanks for all the input
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Basically start again. Use ur recovery Ingram to restore, then root ur desire from scratch using visionary++ perm root, then eng-s-off, then Tom manager, flash clock mod, then flash new rom.?
Download terminal emulator from market type such and enter. If it returns # ur set.
Has anyone tried the new 5.0 recovery available in rom manager? Any issues?
Sent from my Incredible 2 using XDA App
I was actually wondering the same thing. In fact, I'm curious as to how you even update to the newest version of CWM.
Greatly appreciate anything you guys have to say.
So far so good. I haven't done much with it, but I haven't had any problems.
You can update the recovery with ROM Manager. My only advice is that you check the box to erase the old recovery before flashing the new one. The box to check is in the ROM Manager settings.
Sent from my ADR6350 using xda premium
its fine ive been going haywire flashing with it. no worries guys
I have it too. Just download through Rom Manager. The Text color is actually Cyan instead of orange. I like it.
I just got another update prompt when I opened ROM Manager. I went from 5.0.1.9 to 5.0.2.0, but I'm not sure what they changed.
Yup. Using it fine, and love the new color. Easy to read for an old man.
Well, I tried Cyanogen, AOPK and now I tried PARANOID 2.0.
None of them works, GAPPS works, but I get the Status 7 error while installing a ROM, i'm using the SGH-T999V and none of them works.
How are you trying to install them?
Sent from my SGH-T999 using xda premium
You are rooted and trying to install with cwm or twrp recovery, right.
I ask because that error reminds me of stock recovery for some reason...
Sent from my SGH-T999 using xda app-developers app
Hey make sure you've rooted your phone first. I'm on cm10 with leankernel and everything works just great. Good luck!
Sent from my SGH-T999v using xda app-developers app
Sounds like stock recovery to me bud..
Sent from my T999 GS3 @ 2GHZ
d2tmo wrong device?
Status 7 errors can occur in ClockworkMod for everyone saying he's using a stock recovery.
Make sure your rooted and you should be good
Hey SGH-T999V,
I think we'd all love to help, but we need some more information. Can you tell us step by step exactly what you are doing? Once we have that, I think we will be able to help you past this.
I am fully rooted with clockworld recovery 5.0.4 or something, installing zip from sdcard then Status error 7 and yeah...
From what I've gathered, status 7 errors usually occur when the ROM is incompatible with the device e.g when flashing a CDMA rom on a GSM phone. My first advice would therefore be to confirm that the zip file is for the correct GS3 variant. You mentioned aokp and CM. Both these ROMS refer to the T999 as "d2tmo" and the zip files usually contain this in the name (e.g cm-9-20120909-NIGHTLY-d2tmo.zip). I would therefore check this first before anything else.
Assuming that's not the issue, some suggestions would be:
1. This is a longshot, but try toggling signature verification and see what happens. I doubt this is the issue but I have had update zips fail because this was accidentally toggled
2. Try updating CWM: http://forum.xda-developers.com/showthread.php?t=1766552
3. Try changing the recovery to TWRP and see if its the recovery. The easiest way I've found is to use the GooManager app. Install from the play store. Run the app. Hit the menu key and select Install OpenRecoveryScript. Reboot into the TWRP recovery and try flashing from there.
4. Try rerooting the device from scratch
I got this error when I rooted using the Sprint method. I had to reflash cwm using Rom manager before I could install Cyanogen
Sent from my SGH-T999 using xda premium
I had the same problem. I updated cwm and it fixes it. Your version is old....
Sent from my SGH-T999 using Tapatalk 2
Just updated CWM to 6.0.1.2 and tried to flash with TWRP... same Status 7 error with every single ****ing ROMs i'm trying to install.
Wiped everything many times before installing zip, nothing works... i'm giving up and downloading stock ROM until Samsung releases official JB 4.1.
You might have to go back to stock and root it again
Sent from my SGH-T999V using XDA Premium HD app
could try installing the roms with Odin
Could try downloading the roms using Rom manager pro and having it install them
You just got to get one to work and you'll be golden
Is it a setting problem in cwm?
Like toggling allow installation of unsigned packages
Sent from my SGH-T999 using xda premium
Just update cwm to a newer version. I promise that'll fix it.
Sent from my SGH-T999 using xda premium
Or pay someone to do it. Look for rooting services on craigslist
Sent from my SGH-T999 using xda premium
same here
Hi, there,
just looking for solution for the same problem and got this thread...
well, I was rooted and on cyanogen and everything worked fine.
had backups and stuff.
decided to return to stock just to have it updated and backed up and after that to return to cyanogen.
when in CWM, after stock, while re-root-ing, I did a fix permission which erased some of my system files in the backups, so all my backups on the phone became useless (lesson #1: always move your backups away from the phone).
decided to start from scratch, so using ODIN I flashed the proper stock ROM for T999V. Installed the CWM version 5. something, superuser etc.
made a backup this time and store it outside the phone
when I tried to flash the cyanogen 10.0 for m2tmo (which I've flashed before without trouble), I got the error message as our friend here.
I edited the updater-script file in order to erase the first lines and got it flashed...
the problem that I have right now is that I am stuck in the first screen when the cyanogen keeps going round and round and round.... and nothing happens
any suggestion from here?
http://wiki.rootzwiki.com/ClockworkMod_Recovery#Status_7
The status 7 error can be from a bad download, bad signature, and I have seen it from using an old version of clockwork. I would first make sure you are running the most current version of recovery. if that doesn't solve your problem try redownloading the Rom.
First off I want to say I have actually searched and read every thread imaginable.
Basically every time I try to flash a new rom (Tried 4 now) I get the error status 7.
This is not my first root and rom flash either, I've done 2 tablets and 5 phones all without issue.
I have tried TWRP, cwm 5.5, CWM 6.0.1.2 and i get the same error.
I have gone through the roms and deleted the first line, same error.
I have wiped data/reset.
I have tried ics and jb roms.
I have tried THREE different rooting methods.
Nothing but stock works... Please help!!!!
Edit: Forgot too add in that Rom Manager does not recognize what phone I am or that I already have CWM, as well same with goo manager and twrp.
I am Telus BTW
Thanks in advance!
Have you checked your build.prop? Error 7 is usually a build.prop error,iirc.
Try cwm touch
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Have you read this thread http://forum.xda-developers.com/showthread.php?t=1884246
[Q] Flash Failed: Status 7
I installed cwm v6 and it allows me to avoid the error and installed cm10.
If you use the other recovery versions, it seems you have to change the build.prop to d2att from d2can. Shame as I like twrp.
One of those things that isn't really clear or written about for those of us that haven't gone through it. For those that know it's an obvious thing.
I won't forget it now.....
Mike
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Every once in a while when a new app needs root permission, i open the app waiting for the superSU popup, and it never comes. my phone ends up freezing and i have to restart it via a battery pull or long press of the power key. Once i reboot and enter the app, the superSU popup comes right away and i can grant it root permission.
Any ideas why it would be doing this?
Replace your Superuser app. Or update it.
I've done that. A few times. Still giving me that issue. It seems pretty random. And it's only the first time an app asks for permission. Seems to happen only to apps that use deep root too, like busybox etc... I think lol
Sent from my SGH-T999 using xda app-developers app
I've never had a problem with superSU, do all superuser apps do this?
Sent from my SGH-T999 using Tapatalk
No. And I've never had a superSU issue till now either. Here's the last thing I did before I noticed the issues.
I was having power button issues, but it wasn't constant, so I thought it might be a rom based issue, so I went back to the root66 version of stock 4.3
I realized that it was a hardware button, so I switched back to saranhai's stockmod slim rom. I also updated my CWM to the latest version. Those are the only things I've done between it working fine and me having these issues now. Not sure what it could be.
Sent from my SGH-T999 using xda app-developers app
Please do a Factory Reset and then try one of the apps that previously gave you trouble with Root Access.
I did a factory reset before I flashed the last rom. Think I still need to do another one?
Sent from my SGH-T999 using xda app-developers app
Given your current Problem, I'd say yes. Do it in Recovery so it will format Dalvik & Cache as well. Needless to say don't restore anything unless you have tested that the problem is indeed gone.