Hi I recently updated my phone to the newest version of ViperROM.
Ever since I did the update (full wipe), when I go into recovery it mentions this:
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
I didn't have this before I updated my phone, and I'm pretty sure I haven't updated the CWM recently either... I also have SuperSU installed for root access.
I've reinstalled the ViperRom 2-3 times with the same issue, my work colleague is getting the same thing on his phone to (same phones). Both phones have the same recovery, supersu and rom.
Very wierd, anyone else seen anything like this or know how I might fix it?
I've used the option to add SuperSU to system, but the message still shows.
I can't seem to do anything while I have this message. There is an OTA update from ViperROM which I can't install, because is keeps asking to fix root.
Any help would be greatly appreciated.
Andy
killerb4dger said:
Hi I recently updated my phone to the newest version of ViperROM.
Ever since I did the update (full wipe), when I go into recovery it mentions this:
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
I didn't have this before I updated my phone, and I'm pretty sure I haven't updated the CWM recently either... I also have SuperSU installed for root access.
I've reinstalled the ViperRom 2-3 times with the same issue, my work colleague is getting the same thing on his phone to (same phones). Both phones have the same recovery, supersu and rom.
Very wierd, anyone else seen anything like this or know how I might fix it?
I've used the option to add SuperSU to system, but the message still shows.
I can't seem to do anything while I have this message. There is an OTA update from ViperROM which I can't install, because is keeps asking to fix root.
Any help would be greatly appreciated.
Andy
Click to expand...
Click to collapse
Can you gain root access on the phone? E.g. terminal emulator and use the 'su' command. Do you get a SU prompt?
If not have you tried manually flashing SU zip?
CYNiCAL2KX said:
Can you gain root access on the phone? E.g. terminal emulator and use the 'su' command. Do you get a SU prompt?
If not have you tried manually flashing SU zip?
Click to expand...
Click to collapse
Its got to the point where I'm attempting to install a different SU.zip, and now CWM attempts to install then the screen goes blank.
I can't install anything via CWM at the moment...
I've had root access before installed the Viper 5.0 update, now is gone all weird.
I now can't install any .zip file via the phone, CWM attempts it showing "installing zip" then the screen goes blank and reboots.
killerb4dger said:
Its got to the point where I'm attempting to install a different SU.zip, and now CWM attempts to install then the screen goes blank.
I can't install anything via CWM at the moment...
I've had root access before installed the Viper 5.0 update, now is gone all weird.
Click to expand...
Click to collapse
Have you done Backup Data, wipe and fresh install, then restore Data?
CYNiCAL2KX said:
Have you done Backup Data, wipe and fresh install, then restore Data?
Click to expand...
Click to collapse
I have a backup from before i updated ViperRom 5.0, can I not install TWRP or something? Its just I would then need to reinstall ViperRom again and set everything up.
To be honest, it wasn't perfect from when I did the update, but it still looks better than the old version I was on.
killerb4dger said:
I have a backup from before i updated ViperRom 5.0, can I not install TWRP or something? Its just I would then need to reinstall ViperRom again and set everything up.
To be honest, it wasn't perfect from when I did the update, but it still looks better than the old version I was on.
Click to expand...
Click to collapse
If you back up data you won't need to set it up again. That's my point. Do this
Install TWRP, do a full backup, then wipe and install 5.5 fresh. Then restore Data. Restoring data will return your phone back to the way you had it.
CYNiCAL2KX said:
If you back up data you won't need to set it up again. That's my point. Do this
Install TWRP, do a full backup, then wipe and install 5.5 fresh. Then restore Data. Restoring data will return your phone back to the way you had it.
Click to expand...
Click to collapse
Oh I see, thanks
Related
So I had alot of issues rooting but im finally in, all rooted. Downloaded ROM Manager from the market and installed CWM. Says its successful, but when I manually reboot into CWM i get a error, so I cant install the 1.1 fix
Any ideas?
Really no one knows? This sucks!
This normally happens when recovery is not flashed properly. Did you try flashing again via Rom Manager? Also when you flash, does the screen show something like "Rom Manager has been granted super user permissions"?
ya, it flashes successfully through rom manager....
I think the problem is when I was trying to go back to 1.0.1 I flashed a restore through CWM. Then I whiped the /system and /data folders. The directions said to do this but I didnt realize I was supposed to do this BEFORE flashing not after. Basically I had no restore partition left so when I went and let it fail to boot 8x i got a error, and i had no OS. I ended up doing the N/Pwr, it restored, then i got a bootable CWM, booted into it and flashed the 1.0.1. But not everything seems, odd.
I can go into Rom Manager and install CWM fine, it says installation successful. But if I reboot into recovery, I get the error. I really need this fixed but im thinking it may be easier to just use a bootable CWM. Any ideas? I need to get 1.1 on here before I lose root
DroidHam said:
I think the problem is when I was trying to go back to 1.0.1 I flashed a restore through CWM. Then I whiped the /system and /data folders. The directions said to do this but I didnt realize I was supposed to do this BEFORE flashing not after. Basically I had no restore partition left so when I went and let it fail to boot 8x i got a error, and i had no OS. I ended up doing the N/Pwr, it restored, then i got a bootable CWM, booted into it and flashed the 1.0.1. But not everything seems, odd.
I can go into Rom Manager and install CWM fine, it says installation successful. But if I reboot into recovery, I get the error. I really need this fixed but im thinking it may be easier to just use a bootable CWM. Any ideas? I need to get 1.1 on here before I lose root
Click to expand...
Click to collapse
I fixed this by downloading the latest busybox from the market, installed it, then ran the "fix permissions" from Rom Manager. I then reinstalled the latest CWM, and it would allow me to reboot into recovery.
Trying to install safestrap so I can upgrade from my current .215 to .217. My phone was not rooted so I first ran the root utility from Fishbear and the app said it was successful in applying root. I downloaded superuser from the market, but it forecloses every time I open it. I tried clearing the data cache and also using the superuser update utility; didn't work. I re-ran Fishbear's root script and it exited with the confirmation that my device was already rooted, with super user version 3.0.3.2.
Any suggestions?
Tightmopedman9 said:
Trying to install safestrap so I can upgrade from my current .215 to .217. My phone was not rooted so I first ran the root utility from Fishbear and the app said it was successful in applying root. I downloaded superuser from the market, but it forecloses every time I open it. I tried clearing the data cache and also using the superuser update utility; didn't work. I re-ran Fishbear's root script and it exited with the confirmation that my device was already rooted, with super user version 3.0.3.2.
Any suggestions?
Click to expand...
Click to collapse
I tried migrating from .215 to .217 and the data partition was incompatible so I had a whole bunch of weird errors. I don't recommend doing a safestrap backup / restore for that version. Just wipe your data and fastboot .217. It will be a pain to upgrade but yuo will not regret it later.
danifunker said:
I tried migrating from .215 to .217 and the data partition was incompatible so I had a whole bunch of weird errors. I don't recommend doing a safestrap backup / restore for that version. Just wipe your data and fastboot .217. It will be a pain to upgrade but yuo will not regret it later.
Click to expand...
Click to collapse
Cool, thanks for the advice, but I'd rather have a deodexed/bloat removed ROM. I actually just restored my phone to defaults through the stock recovery menu and was able to get super user to work. From there I installed busybox and safestrap and got me some .217!
I've had my HTC one for a little over half a year and I have been running cynogenmod 10.1 on it with no problems until I decided to update it to 10.2.1. when i had finished doing that I started having problems with it running and the just randomly rebooting frequently so I went back into my recovery (twrp 2.5.0.0) and went to recover into my nandriod backup. After I wiped the phone and used the backup i restarted it and now my phone just sits on the HTC One loading screen.
I can still enter into the recovery and bootloader (1.44 s-on), adb does find it in its device list when its connected to the computer. also when I go to restart the recovery I get a message saying "your device appears to not be rooted install supersu now? This will root your device". It doesn't do anything when i do say install or not to install it and just restarts the device. I did have it rooted before so I'm not sure if the recovering of the old phones image removed the root?
Not quite sure what I may have done wrong as I'm still fairly new to rooting and all but I'm unsure as to where to go from here. I've been digging through threads on the HTC one forum and I feel like I may be over thinking what i need to do. I couldn't really find a direct answer and i don't want to accidentally make it worse.
so here i am any help would be appreciated.
vash3100 said:
I've had my HTC one for a little over half a year and I have been running cynogenmod 10.1 on it with no problems until I decided to update it to 10.2.1. when i had finished doing that I started having problems with it running and the just randomly rebooting frequently so I went back into my recovery (twrp 2.5.0.0) and went to recover into my nandriod backup. After I wiped the phone and used the backup i restarted it and now my phone just sits on the HTC One loading screen.
I can still enter into the recovery and bootloader (1.44 s-on), adb does find it in its device list when its connected to the computer. also when I go to restart the recovery I get a message saying "your device appears to not be rooted install supersu now? This will root your device". It doesn't do anything when i do say install or not to install it and just restarts the device. I did have it rooted before so I'm not sure if the recovering of the old phones image removed the root?
Not quite sure what I may have done wrong as I'm still fairly new to rooting and all but I'm unsure as to where to go from here. I've been digging through threads on the HTC one forum and I feel like I may be over thinking what i need to do. I couldn't really find a direct answer and i don't want to accidentally make it worse.
so here i am any help would be appreciated.
Click to expand...
Click to collapse
update your twrp version, 2.5.0.0 is very outdated. then flash latest cm11
alray said:
update your twrp version, 2.5.0.0 is very outdated. then flash latest cm11
Click to expand...
Click to collapse
Alright ill give it a try and let you know if it works but im still confused why my backup didnt work. Could the old version of twrp?
vash3100 said:
Alright ill give it a try and let you know if it works but im still confused why my backup didnt work. Could the old version of twrp?
Click to expand...
Click to collapse
Maybe. Did you backed-up every partition (boot, system and data)?
You could try to restore you back-up with the latest twrp, it might also help to clear cache.
vash3100 said:
Alright ill give it a try and let you know if it works but im still confused why my backup didnt work. Could the old version of twrp?
Click to expand...
Click to collapse
Its most likely that the old recovery is the issue. 2.7.0.0 has been released and why not CM11, which is in its snapshot stage?? And, your HBOOT and firmware are also extremely outdated. 1.44 was the HBOOT at launch. 1.56 is the latest
It took awhile but everything is working again. I guess my backup was corrupt or something because it still didnt work after i flashed the recovery to a newer version.
I made a backup of a couple games and random other apps, about 20 as I decided to flash the cyanogenmod nightly onto it. Everything works fine, I enabled root in developer settings. When I first opened the app I got a warning about my SU binary being outdated, that its functional but maybe unstable on 4.3+ devices. So when I go Batch > Restore Missing Apps with Data it starts to restore but just sits at 0%
Has anyone else had this problem? I'm guessing its something to do with the SU binary warning I mentioned. How do I update this?
Audaces said:
I made a backup of a couple games and random other apps, about 20 as I decided to flash the cyanogenmod nightly onto it. Everything works fine, I enabled root in developer settings. When I first opened the app I got a warning about my SU binary being outdated, that its functional but maybe unstable on 4.3+ devices. So when I go Batch > Restore Missing Apps with Data it starts to restore but just sits at 0%
Has anyone else had this problem? I'm guessing its something to do with the SU binary warning I mentioned. How do I update this?
Click to expand...
Click to collapse
You need to flash the latest version of SuperSU through recovery (Chainfire's). The baked in Superuser doesn't seem to work with TBU
Toneman07 said:
You need to flash the latest version of SuperSU through recovery (Chainfire's). The baked in Superuser doesn't seem to work with TBU
Click to expand...
Click to collapse
Do I have to flash it through recovery? Or can I just grab it from the app store?
Audaces said:
Do I have to flash it through recovery? Or can I just grab it from the app store?
Click to expand...
Click to collapse
Ehh, Maybe ... I usually flash through recovery and just keep the zip saved on my phone.
I don't think its a TBU issue I've used it a few times without any problems.
Hello !
At first I apologize for my English, I am French.
So i used the custom ROM Validus and this problem appears for every ROM. Like you know, when you root, you can't use snapchat and u need to login before you root your phone. So i installed Validus, i install all apps i need and login (included snapchat) but after that when i flash super su, my phone reset and i have a error message which flashes. In the message i have ".com.android" something and i'm obliged to shutdown the phone, reset the phone and re-install the ROM.
And this appears with all ROM (Tesla, Tuga etc...) and i don't know how can i use snapchat acutally.
I tried to disable super user in the app, doesnt work
I saw we can use xposed app but for 7.1.1, it's not possible actually
Any ideas ?
Thanks,
Snapchat discorvers root as it denies working on it. After flashing install snapchat and login. Then return to recovery and install SU afterwards. Possibly you have to use tools like RootCloak.
Inciter said:
Snapchat discorvers root as it denies working on it. After flashing install snapchat and login. Then return to recovery and install SU afterwards. Possibly you have to use tools like RootCloak.
Click to expand...
Click to collapse
It's what i tried to do (without RootCloak) and when i do that, i lost all my data (like i wipe all data when i try to install SU...) but RootCloak works for 7.1.1 ? Because i already tried to flash Xposed, doesnt work (error 1)
Try SUHide. Though the data wipe seems odd.
Inciter said:
Try SUHide. Though the data wipe seems odd.
Click to expand...
Click to collapse
I tried to flash suhide after flash ROM, doesnt work, the ROM don't charge (the loading of the ROM don't stop)
PS : I tried with Validus ROM and others, same things
Here's a workaround for Nexus 6. Maybe it's working on 3T as well. Something else I found here.
Nevertheless, the auto data wipe is strange. Did you clean or dirty flash?
Inciter said:
Here's a workaround for Nexus 6. Maybe it's working on 3T as well. Something else I found here.
Nevertheless, the auto data wipe is strange. Did you clean or dirty flash?
Click to expand...
Click to collapse
I don't know what is dirty flash ? What i know is i alway wipe all data before install any custom ROM
But I found a solution. I installed Root Swich, it's a simple app which allows to deactivate the root and activate it as you want.
So i disabled root and install snapchat and login successfully.
But i want to understand why when i want to flash super su for any custom ROM i have a auto data wipe :/
Since your device is beyond my reach I can't help investigating the problem. Maybe the data is not really deleted but r/w permissions have just been modified and cannot be accessed any more. But anyway, I'm glad your found a workaround.
Inciter said:
Since your device is beyond my reach I can't help investigating the problem. Maybe the data is not really deleted but r/w permissions have just been modified and cannot be accessed any more. But anyway, I'm glad your found a workaround.
Click to expand...
Click to collapse
Thanks for your help anyway !
Now I just need someone who knows how can i fix the problem of data. Cause if one day i will need to flash something, it's gonna wipe the data of my phone
Maybe if i do a clean factory reset or something ? Cause i used my 3T a lot cause of this to find a solution so maybe something happenned when i tried so many things. (Test of ROM etc ...)
I have more information, when I install any custom ROM and after that I want to flash super su, wipe cache etc ... I boot on the ROM normally but i see my phone haved a factory reset and i have this ".com.android.phone has stopped" Impossible to remove the message and I am forced to wipe again data and reinstalll the ROM.
Conclusion : I can install ROM but after that, i can not do anything, if i do anything, BOUM, reset factory. And i don't understand why ....
I tried the last (Unofficial) TWRP but when i tried to boot on the ROM after flashing it, my phone didn't boot on the ROM but always on TWRP.
Maybe I brick my phone but i can use it, i don't have storage problem or others so ...
I'm lost ... Any ideas ?
up ?
Balashe said:
up ?
Click to expand...
Click to collapse
Do you have this issue with only flashing super su or try to boot into recovery don't do anything and reboot check if it still reset everything.
Which recovery you are using?
The version
nitinvaid said:
Do you have this issue with only flashing super su or try to boot into recovery don't do anything and reboot check if it still reset everything.
Which recovery you are using?
The version
Click to expand...
Click to collapse
I have this issue only flashing super su, when i try to boot into recovery and then reboot into the ROM, nothing happened.
I use 3.0.3.1, when i tried 3.0.4.0 and flash a ROM, the phone only boot on recovery and not into the ROM
I'm actually having a similar issue. One day my phone was acting weird and I had to force reboot. I noticed after that I lost root. I've tried flashing SuperSU again, and it flashes fine but I still don't get root. This morning I upgraded to 4.0.3, and tried flashing root, and same thing no root.
The weirdest part is I can flash a custom kernel with TWRP 3.0.3.1 and the kernel flashes fine and I have the custom kernel, if I try flashing SuperSU, it flashes fine but I get no root AND it removes the custom kernel!!! Everything I'm using is the most updated too. What gives? I want root back....