TWRP thinks I have root (it's not prompting me to install the SU binaries when I exit recovery).
SuperSU thinks I don't have root (it says I don't have the SU binaries installed).
I've tried re-installing TWRP, I've tried re-installing SuperSU. Neither worked.
Other than wiping everything, I can't think what to do.
Any suggestions?
I'd rather leave wiping 'til a last resort; and, just my luck, the last nandroid backup wasn't all that recent.
EDIT: I've just thought, I could do a "fastboot flash system", but I can't seem to find the system.img for 44S. Anyone able to obtain it?
EDIT v2.0: Found it. Flashed it. Sorted. I guess this can be closed now!
Related
I was running 3.0.1 unlocked/rooted, Tiamat's 1.4.1 kernel. I followed the steps to update to 3.1 from here, and had no issues what so ever. This was earlier this week, and today I was going to run fix permissions in recovery. I used Quick Boot (also tried Reboot to Recovery in ROM Manager) to boot to recovery, and I got to the Android with the exclamation point...
I tried sending the modified 3.0.2.8 recovery listed in the Dev Forums using fastboot commands, and everything went smooth with no errors, but still got the Android/exclamation point.
I tried reflashing recovery via ROM Manager, and it wouldn't pop up anything, so I uninstalled/reinstalled, and the flash of recovery worked. Boom! Recovery is back! So I can do what I need (run fix permissions), and rebooted the device.
I try to reboot into Recovery again, back to Android with exclamation point. Any thoughts here as to why I must do this, and thoughts to what I can try to make Recovery "stay"?
Thanks!
RMarkwald said:
I was running 3.0.1 unlocked/rooted, Tiamat's 1.4.1 kernel. I followed the steps to update to 3.1 from here, and had no issues what so ever. This was earlier this week, and today I was going to run fix permissions in recovery. I used Quick Boot (also tried Reboot to Recovery in ROM Manager) to boot to recovery, and I got to the Android with the exclamation point...
I tried sending the modified 3.0.2.8 recovery listed in the Dev Forums using fastboot commands, and everything went smooth with no errors, but still got the Android/exclamation point.
I tried reflashing recovery via ROM Manager, and it wouldn't pop up anything, so I uninstalled/reinstalled, and the flash of recovery worked. Boom! Recovery is back! So I can do what I need (run fix permissions), and rebooted the device.
I try to reboot into Recovery again, back to Android with exclamation point. Any thoughts here as to why I must do this, and thoughts to what I can try to make Recovery "stay"?
Reflash cmw afterward and it should stay.
Thanks!
Click to expand...
Click to collapse
Use your computer to do this:
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
or alternately, you can use a root file manager such as root explorer to remove the files (I personally just renamed mine so they wouldn't be recognized. I don't like burning bridges).
Re-flash cmw afterward and it should stay.
Thanks! That worked, you the man! I renamed them as well, as I don't want to burn bridges either.
While attempting to switch to CM11 I tried upgrading TWRP from 2.4.4 to the newest 2.6+ and it messed up my recovery. Then, while trying to re-flash an older TWRP, I accidentally installed SuperSU over an existing install, and lost root. Tried re-rooting the device using motochopper and it gets to the last part, "rooting device" and it says "failed". Device the reboots, I try to open SuperSU and it says "no SU binary installed". All I'm trying to do is put back TWRP 4.2.2 so I can restore my device. Please help
EDIT: Tried using fastboot to install image, everything looks good, then my tablet freezes up. I do a power cycle, it reboots, and the recovery didn't flash.
UPDATE: Recovery flashed and wiped EVERYTHING. I am back on recovery 4.2.2.0 but nothing is mounted and I can't mount anything, I can't make backups or restore images, and ADB Sideload does not work. Any help would be really, really awesome. I have SDK Manager, and I can currently use ADB on my computer, I just don't know what commands, blobs, or images to use.
Tunameltsalad said:
While attempting to switch to CM11 I tried upgrading TWRP from 2.4.4 to the newest 2.6+ and it messed up my recovery. Then, while trying to re-flash an older TWRP, I accidentally installed SuperSU over an existing install, and lost root. Tried re-rooting the device using motochopper and it gets to the last part, "rooting device" and it says "failed". Device the reboots, I try to open SuperSU and it says "no SU binary installed". All I'm trying to do is put back TWRP 4.2.2 so I can restore my device. Please help
EDIT: Tried using fastboot to install image, everything looks good, then my tablet freezes up. I do a power cycle, it reboots, and the recovery didn't flash.
UPDATE: Recovery flashed and wiped EVERYTHING. I am back on recovery 4.2.2.0 but nothing is mounted and I can't mount anything, I can't make backups or restore images, and ADB Sideload does not work. Any help would be really, really awesome. I have SDK Manager, and I can currently use ADB on my computer, I just don't know what commands, blobs, or images to use.
Click to expand...
Click to collapse
Can you use fastboot to reflash the stock ROM?
Hey everyone,
My situation sounds pretty similar to what's described in this thread: http://forum.xda-developers.com/showthread.php?t=1840030
"there is a risk of the /system and /data partitions not wiping correctly thus leading them to be formatted with R/O permissions rather than R/W. This makes it impossible for the phone to boot up because no data can be written. Not even a typical ODIN flash back to stock or rooted stock will fix this."
I was prepared to follow the instructions, but have read around about permanent bricking or bootloader locking by downgrading after having upgraded to 4.3, so I'm seeking advice. Unfortunately, I'm not certain which bootloader/chain/modem/whatever I'm using right now.
The Source of the Problem
I was on the latest stable CM11
I upgraded to M7 using TWRP
The Google Apps were constantly crashing. I didn't realize I had upgraded to 4.4 from 4.3, so my first instinct was not to flash a newer gapps package. I did a factory reset followed by a ROM flash (same M7 package).
Booted successfully this time. Flashed gapps, downloaded Titanium.
Restored previous ID with Titanium and installed Super SU (don't remember what order).
Normal method failed for Super SU, so I used TWRP.
Installed a bunch of apps, tweaked a bunch of settings.
Restored things from Titanium. Rebooted. Bootloop.
Factory Reset (or maybe cleared cache+dalvik, don't remember) which resulted in "E:/error opening '/data/lost+found'" about thirty times in a row
Found this thread, followed mitchallica's instructions: http://forum.xda-developers.com/nexus-4/help/solved-e-error-data-lost-factory-reset-t2147501 which must have been a bad idea since he described having one l+f file, wheras I had duplicate directories
When trying to create the lost+found directory, it ended up creating the same thirty or so I had just deleted. It was impossible to create just one. I deleted it and rebooted to recovery.
This is where things get fuzzy. I performed a barrage of flashes, wipes, permission fixes, and tried a few times unsuccessfully to create the lost+found using the recovery terminal
What Doesn't Work
Normal boot lands on CM boot animation, remains there indefinitely (bootloop)
Factory Reset, Restore, Terminal Commands, and File Manager navigation that involve /data result in half second hang followed by reboot.
What Does Work!
I'm able to boot into recovery and download mode. I'm able to connect to ADB.
Current Stats That I Know Of
TWRP Version: 2.6.3.1
Last used Android version: 4.4.2
Hello there,
I have had the OPO for a while now and initially successfully gained root access, unlocked bootloader etc. However, I now have lost root access and SuperSU says the SU binary is not installed. I have tried re-flashing the SuperSU zip through TWRP several times (and I tried CWM too), I reset my phone completely, tried restoring through nandroid but It still comes up with the error. I'm not sure if this is relevent to this problem but /data will not mount for some reason as well. Is there anything you might know that could help me out? Please Help.
Thank you,
So I think I soft-bricked my phone. I can't mount '/system'. I can't adb sideload (returns "error: closed"). I can't adb push.
Is the best course of action to download 0P6BIMG.zip from http://forum.xda-developers.com/showthread.php?p=52115727, and flash via rebootRUU? The file is going to take an hour and half longer to download, so if there is a better way I'm all ears.
To give some back story. I was running ViperOne and in the process of moving to CM12. I tried to use TWRP manager to update TWRP to the latest. It kept crashing. I then used flashify to flash the latest TWRP. I checked version from flashify and it was still reporting older version. It said you may have to reboot into recovery for version to sync up, so I did, and now here I am. Soft-bricked and in TWRP 2.8.1.0.
Thanks...
So I don't know what was truly wrong... But I was able to get adb sideload to work by restarting it a couple of times. Now CM12 is installing and it looks like my data was left intact because it's upgrading and listing 170 apps.. Can anyone tell me what happened?
I don't know what went wrong. But I would not trust TWRP Manager or Flashify to flash recoveries. I have seen cases where Flashify flashed to the wrong partition.
Use fastboot - it's the safest way....