I've flashed the newest CyanogenMod nightly on my Nexus 4 yesterday, but now I seem to have lost root access (maybe because I encrypted the device?). The device is not being recognized anymore in adb, and if i enter the custom recovery (CWM) to install SuperSU again, i cannot access "choose zip from /sdcard". Also, root apps are not working anymore. How do I get root back, without losing my data?
Ok, so I saw a developer option called something like "give root access to apps" and it did seem to work, i could open up AdAway and download the host files etc (this was the only app with root access that I had on the phone). Then I restarted the device and now I'm in a boot loop - no idea what to do now. Restoring my backup from sdcard obviously doesn't work, because CWM doesn't have access to it, because the device is encrypted. What now? Can I just install a bootloader that supports encryption? Will TWRP work? Need help please.
Related
Heya,
I decided to nuke my beloved OP2 and start anew, this time including encryption. As I read in the encryption Q&A, the device should not be rooted when doing the encryption, as this can cause havoc.
If you want, you can skip the Italic part. Lets just say, all went well until I rebooted into recovery after setting my encryption password.
- I wiped everything, installed Oxygen OS 3.0.1, flashed the TWRP recovery image (which was recommended in the "how to install oxy 3 on OP2" guide. So it should be a compatible version).
- I boot up my phone and go to the android security settings. I put my phone on the charger and let it encrypt my system with the on-board encryption function. Everything goes well, device reboots fine, now encrypted.
- I went to the security settings again to set my password. I check "ask this password before booting". Now that the encryption is dealt with, I want to have my device rooted. I boot up into TWRP and, as expected, TWRP asks for the password that I just configured.
BUT TWRP won't accept my password, telling me it was wrong. I tried several times, checked that I didn't mess it up because of a foreign language (english) keyboard. When I rebooted the device, it accepted my password on the first try, booting normally afterwards.
I went into the security settings and chose a pattern instead of a password, to make sure the keyboard wasn't the cause of the failure. When booting into TWRP, it asks about my pattern now. But it doesn't accept it.
So I went back into the security settings and unchecked the "ask pattern before boot" part, hoping that TWRP might not need the pattern anymore. When I boot into TWRP now, it asks for a password again, although I have enabled a pattern only.
I rooted my devices several times already, without any problems. This is the first time that I use encryption, so I have no Idea what could be the cause of this problem. It just seems that TWRP has problems decrypting the OxyOs. Please keep in mind that I used the TWRP image that was recommended for OxyOS 3.0.1 in the official Oneplus Forum install guide, so it should be compatible with all the Software and Hardware.
Now that I can't access anything with my TWRP, I haven't installed my SuperSU yet. I can't see how I can gain root access without using TWRP. If I rooted the device first and then encrypted it, the TWRP problem would not matter, but that's exactly the thing that causes HAVOC.
Looking forward to ideas
Fennec
Edit: My progress:
- tried adb sideload the supersu.zip over the stock recovery (update from usb). Protocol error. Installation failed.
- tried all kinds of TWRP versions, starting at the newest 3.0.2. TWRP 3.0.2 claims to have solved the encryption issue, but when flashed I get a bootloop whenever I try to enter the recovery.
- I realized that my adb sideload failed because I used an old version of adb which I found on my laptop. The newest version managed to sideload the supersu and the xposed framework, giving me root rights. TWRP still does not work but at least I got root now :/
same: TWRP can not decrypt system partition on One Plus One, CM-13 and TWRP 3.0.2-0
I remember TWRP said: installation was not successful although it can boot into recovery...
Try fastboot official twrp-3.0.2-2 for me is working fine.
Remember to boot in recovery after flash
Sent from my ONE A2005 using Tapatalk
The hotspot function is not acting correctly, devices will constantly be disconnected and then reconnect. I've been able to troubleshoot the issue to my cell. When I rooted my cell I created a backup as in the directions of jrkruse on rooting 5.0. My question is if I'm using Safestrap recovery, do I boot into it -> Restore -> Select Package & is this like doing a system restore on Windows? I just want to make ask and be sure of details as I do not want to have to go through the root process again. Thank you for any responses in advance.
Also, while I have this post up, in LP Recovery Control, when I select FlashFire Recovery, nothing happens. Would this recovery help with that issue?
EDIT: I found that Safestrap recovery does work as a system restore on Windows, but you will lose anything not saved on an SD Card. As for my issue with FlashFire, thank you to user: hauckk. I am unable to install FlashFire from the Play store though as it's recognizing it's already installed.
Restoring Flash fire backup only works from inside the flash fire app
As for your other question I'm not sure
Hello,
I am having some problems since today i flashed the su binaries over my completely new lineageos install. (a14.4, fully wiped before).
it was stuck during boot at the android logo(let it boot for half an hour, multiple times, no progress). so naturally i wanted to boot to recovery, though it would not boot into recovery with any imaginable key combo.
so i went into bootloader mode (which, in my case, is jsut download mode, no fastboot whatsoever, and yes, i checked fastboot devices, (also adb), nothing to be found there)
next, knowing i had no other choide at that moment, i flashed a stock rom, via download mode. worked so far.
stock rom was running (ics), bootloader was still download mode only, and recovery was now stock android rec.
my next step was flashing a custom rom, since this was the most important thing to get to working then.
via adb sideload i fashed lineageos, once again. was working fine, so recovery next. but nothing worked.
included with lineageos is root access, so i enabled all the stuff, incl. adb, on my phone. but adb sideload always spit out errors (code 7 or 255) on rec install (twrp 2.8.something touch.zip) [some error about /tmp/update.zip] trying cwm resulted in the same thing, like did flashing gapps.
pushing the files to the internal memory (/sdcard) did not help, since 'flash from sdcard' resulted in an empty sdcard folder with no files to install (in recovery. in the file explorer while running the os, the files where there)
then i tried rashr (not sure exactly which app it was) to install rec. it said everything worked fine, trying to install cwm. so i rebooted
and nothing worked. the rom would not boot anymore (again, stuck at android logo) since the stock recovery only allows for adb access in form of sideload, no push whatsoever, and sideload did not let me install the os via zip, it was back to flashing a stock rom once again.
so i did that again (this time lolipop)
this is where i am now:
the rom boots perfectly, like does the kinda stock recovery, but again: no files in the sdcard path within the rec menu, though i pushed them there, and they appear there in the file manager.
i installed root, for those neat apps, that maybe one would work, but they need root and the stock rom does not know how to give those rights to apps, no option found for this whatsoever.
also, download mode is gone. (still no fastboot)
when i try to boot the bootloader, i just goes on to usual os boot (key combo and adb reboot bootloader result in the same thing)
recovery is still working, but pretty useless still. when i try to sideload a file, it quits with failed verification of the file. which is no surprise to me, since it shows the message halfway through the send process (observed from the adb terminal on my pc, never gets even close to 100% before the message appears on the phone which also cuts the connection therefore the file send process.)
i have absolutely no idea what the hell will get this working again. i dont really care about the download mode, but what i really need is a custom recovery to finally work, so i can install all of my stuff again.
does anyone have any idea on what i could try next?
hopefully yours,
azyrael
SOLVED
so i noticed for root apps i need to install supersu (or something like this) to give root access to apps if there is no native way within the rom to do this stuff.
install supersu and found out i somehow had no root access at all. tried ioroot etc, did not work
so i installed a stock jb android rom, rooted the device via ioroot, install recovery via autorec, and it finally worked!
this took me only two days.
thx xda for providing all of the tools i needed for this <3
kinda unsolved
so, it got recovery to work. installation of lineageos also worked perfectly., though this bricks my device.
no matter what i wipe, installing a custom rom will stop it from booting. this could only be fixed by installing a stock rom again, which also reverses root and install a stock recovery. since i only need root and the rec for installing a custom rom, which does not work anymore, i wont bother with this anymore. i have abosutely no idea whatsoever, and tried everything even barely coming to my mind.
still open for suggestions, but the stock rom will have to suffice for now.
Hello all, I unlocked my nexus 4 installed TWRP ( tried several versions) currently 3.0.3 and now TWRP bootloops..
Any thoughts or fixes for this ?
I added a screen capture, " could not mount /data and unable to find crypto footer" unable to mount storage, etc.
Did you try 2.87? Is the phone encrypted?
I haven't tried 3.0.3, but 3.0.2 works flawlessly on my N4, with device encryption.
TWRP seems to be failing at decrypting your data partition.
Does Android boot in normal mode?
I will try 3.0.2 and report back... thanks for the help!
precisely yesterday i was in the same situation when i was trying to downgrade to 4.4.4 oem.... i fix it installing other recovery, recovery-clockwork-touch-6.0.4.7-mako http://www.4shared.com/zip/6v3Z7Ghrba/recovery-clockwork-touch-6047-.html
but i install in MAC, in windows i donĀ“t know if is the same process, i was follow this video about how to unlock bootloader in mac
when i install the recovery and enter in fastboot, i put in restart, it will request for fix (yes or no, you choose) the root, i choose NO, and the nexus 4 wake up again in the Cooked Rom, so i try again downgrade :fingers-crossed:
hope it work for u like me
Hey, after 3 hours of trying on my own I definitly need help now:
I followed Funk Wizards guide to unlock Bootloader and install recovery and root. My guess is that something went wrong during the twrp installation.
As I wanted to do a backup of nandroid there've been some errors (digest). So I followed some other guides. In the end nothing worked, after installtion of su my device was not rooted (terminal did not work, root checker notified me). Also my TWRP installation seems to be corrupted, as there's always the question at the beginning "Keep System Read only?", althought I ticked never show again.
- I tried to uninstall su (with "unSU-signed") and install it again
- Magisk throws an error (error 1) at installation and does not install at all
- after restarting phone twrp also shows the internal storage as 0mb (I changed the datasystem from ext4 to 3 and back again to gain access again)
- Working on win10, installed su-v2.82, twrp 3.1.1-1, coming from stock
Hope someone can help. May I can redo everything I did, reinstall twrp and root again.
Cheers
bruzad said:
Hey, after 3 hours of trying on my own I definitly need help now:
I followed Funk Wizards guide to unlock Bootloader and install recovery and root. My guess is that something went wrong during the twrp installation.
As I wanted to do a backup of nandroid there've been some errors (digest). So I followed some other guides. In the end nothing worked, after installtion of su my device was not rooted (terminal did not work, root checker notified me). Also my TWRP installation seems to be corrupted, as there's always the question at the beginning "Keep System Read only?", althought I ticked never show again.
- I tried to uninstall su (with "unSU-signed") and install it again
- Magisk throws an error (error 1) at installation and does not install at all
- after restarting phone twrp also shows the internal storage as 0mb (I changed the datasystem from ext4 to 3 and back again to gain access again)
- Working on win10, installed su-v2.82, twrp 3.1.1-1, coming from stock
Hope someone can help. May I can redo everything I did, reinstall twrp and root again.
Cheers
Click to expand...
Click to collapse
Ongoing discussion here https://forum.xda-developers.com/oneplus-5/help/qa-help-thread-newbies-post-t3624656/post77707348
Fixed it with locking and unlocking device, flash custom recovery and redo the whole process with different twrp image..
Can be closed.