Hi guys,
So I was previous rooted running a custom ICS rom, with ktoonsez, etc. Tonight I wanted to try out JB, so I saved a backup in CWM and then installed a Jellybean stock rom for my carrier with "root injected", All of this worked totally fine in Odin. Afterwards I used Odin to re-install CWM, and that worked fine, I then rebooted into CWM to install the 4.2 Camera/Gallery zip, THAT worked totally fine.
I've since rebooted my device and it seems that root permissions has totally disappeared. The 4.2 camera is still there, I can't get into CWM, Superuser is still on my device BUT it has no apps listed. And Titanium Backup and SetCPU cannot detect root.
Any ideas how to restore this? Kind of surprised that it would just....disappear even after installing CWM and 4.2 camera zip.
Related
I started out with netarchy's stock rooted froyo and amon-ra recovery.
I wanted to install the battery mods by barnacles but I couldn't flash it with amon-ra because it wasn't signed at the moment.
So I got rom manager and flashed clockwork recovery within the program. Then I selected 'flash rom' on rom manager and selected the mod zip file.
Then it rebooted and mod was installed. Then I reflashed amon-ra recovery through fastboot.
Since then it seems that I have no more root access (typing su in terminal returns permission denied)
I was still able to make a nandroid of the rom. Then I flashed an earlier nandroid and booted up and I had root access in that rom. I flashed back the latest nandroid and no root.
So what measures do I take next time to avoid losing root again?
And is there a way to gain root in this rom again?
sure fire way is to just try the whole root process over, what ever method you use. Not sure what caused your problem though.
Very weird but I've been tryin to replicate the cause, and it seems like the froyo full market apk that was floating around seems to cause it... I remembered I had flashed that too. I guess it wasn't meant for sense roms? Hmm
Ok here's my problem.
I've been playing around with a ton of ROMs lately. Which means i've been doing a lot of backing up, restoring, nandroid, you know the drill. But once I restored my nandroid backup today and tried to access ROM Manager to install a ROM, it won't boot into recovery automatically. This also goes for every other root app. Wireless Tether, Root Explorer, Titanium Backup, Busybox, etc. I removed all superuser permissions that were contained inside the app to see if that would help, but sadly, it didn't. But the thing that confuses me is I boot into HBOOT, my phone is still S-OFF, and I can get into clockwork recovery just fine.
My device is the HTC Incredible Stock Froyo firmware with Hydra kernal and Clockwork Recovery 2.5.0.5
Any way to fix this???
I installed the jb update and everything is working so far. I wasn't thinking and I went to goo manager and tried to reboot to recovery. An error popped up and I shut off the phone then rebooted it and everything is fine. I originally installed jb with twrp so I never thought that I lost it but being locked now is there a way to create a backup like a nandroid? That was my intention when I first tried to goto twrp.
This is done on a phone that was updated to 4.3 OTA from AT&T.
I followed the instructions and installed TWRP 2.6.3.0 and SuperSU and Knox Remover. I verified that the phone was rooted using root checker. I proceeded to do a Factory Reset, and Wiped the System and started running the Install on the Gummy 4.4 ROM i had saved to the phone's /sdcard. However, it fails. I try to install CM11 ROM from external SD Card and it fails.
What should I do now? TWRP had essentially erased the Android OS from my phone and the NANDROID backup recovery won't recover due to it being a backup of OTA 4.3! Should I try to reinstall a stock 4.3?
I had this issue too. I think it's something in the updater script that is in error.
I'm trying all sorts of ROMS to just get some OS on there now and everything fails to install thru the custom recovery. I think I might have to get another phone T_T
Aerowrx said:
This is done on a phone that was updated to 4.3 OTA from AT&T.
I followed the instructions and installed TWRP 2.6.3.0 and SuperSU and Knox Remover. I verified that the phone was rooted using root checker. I proceeded to do a Factory Reset, and Wiped the System and started running the Install on the Gummy 4.4 ROM i had saved to the phone's /sdcard. However, it fails. I try to install CM11 ROM from external SD Card and it fails.
What should I do now? TWRP had essentially erased the Android OS from my phone and the NANDROID backup recovery won't recover due to it being a backup of OTA 4.3! Should I try to reinstall a stock 4.3?
Click to expand...
Click to collapse
Are you sure you installed a d2att rom?
What are the errors you're getting? "It fails" isn't very clear.
This has been discussed MANY TIMES in many places.
In order to flash a 4.4+ ROM you need TWRP 2.6.3.1 OR the latest CWM.
Hello everyone,
I have rooted and unlocked my bootloader, and installed CWM 6.0.2 I believe (summer 2012). I was using 4.3 Deodexed ROM and decided to upgrade to 4.4, so I mad a nandroid backup through CWM. Then I found out that 4.4 required me to update my CWM to 6.0.4.3, so I did. After upgrading CWM, I was unable to restore my old 6.0.2 backup. Is there any way to restore it, or do I have to downgrade CWM?
If I need to downgrade CWM, can I first perform a backup of my current 4.4 ROM and then downgrade, or is there a chance it will mess with old CWM?
Thanks in advance,
silentz0r
Sorry for bumping, I have noticed that after upgrading CWM, it made new directories into /sdcard and moved my old directories into /sdcard/0. I tried copying the contents of the old CWM directory into the new one (/blobs and /backup) and tried to restore, but still got the same error message notifying me that no backup is found. Is there no way to restore an old CWM backup with newer CWM?
If anyone ever has this problem, I suggest installing ROM Manager. My backups spontaneously started working through ROM Manager (even in CWM recovery). I have no idea why the backup could not be found before, but using this pretty much fixed itself. Marked as Solved.
silentz0r_ said:
If anyone ever has this problem, I suggest installing ROM Manager. My backups spontaneously started working through ROM Manager (even in CWM recovery). I have no idea why the backup could not be found before, but using this pretty much fixed itself. Marked as Solved.
Click to expand...
Click to collapse
Thanks for the heads up!
But shouldn't you just have made a back-up before CWM upgrade, then upgrade CWM, make another backup (just in case) and then install 4.4?
I am still on 4.3 and I will do it this way in the near future.