Hello everybody,
today i whanted to install the newest Nougat beta build with OTA.
After the download of the OTA the One Plus 3 reboots to the TWRP v.3.0.2-1 and asks me for a password to "descypt data"
I´ve never set a password for TWRP, and my normal SIM password our the backup password for my fingerprint doesn´t works.
So i´ve tryed to reboot my Phone back to the System but he always come back to the TWRP so that means that my One Plus ist currently
completly useless for me D:
I´ve already tryed a help tutorial:
https://www.youtube.com/watch?v=2DWiMuEcpww
but it doesn´t work because i cant mount my patition (because he asks me for the password) to delete the locksettings data.
- sorry for my bad english
You need a modified twrp
how can i get them?
Flash TWRP once again via fastboot....had the same problem...I dowgraded twrp and it started working normally
Hunter9037 said:
how can i get them?
Click to expand...
Click to collapse
http://forum.xda-developers.com/devdb/project/dl/?id=21835
doesn´t work for me.
I used the TWRP Version from theduke7, im now still at v.3.0.2-1
Hunter9037 said:
doesn´t work for me.
I used the TWRP Version from theduke7, im now still at v.3.0.2-1
Click to expand...
Click to collapse
format recovery partition and flash again
how can i format this partition? and will i lost all my data?
Nice.....now i´ve deleted inadvertently everything....all of ny pictures, movies, memories and more....
But now i can install the new OTA Update...... but it doesn´t work, TWRP says: "E: unknow command [log]"
such a wonderful phone ....
And he shows: "the dm-verity is not started in enforcing mode and may not work properly" at boot
Hunter9037 said:
Nice.....now i´ve deleted inadvertently everything....all of ny pictures, movies, memories and more....
But now i can install the new OTA Update...... but it doesn´t work, TWRP says: "E: unknow command [log]"
such a wonderful phone ....
And he shows: "the dm-verity is not started in enforcing mode and may not work properly" at boot
Click to expand...
Click to collapse
That error log (x2) at the end of the flash is normal on Nougat so you can ignore it.
dm-verity is up because you are using TWRP. Again, you can ignore.
The TWRP version number on the splash screen does not change with the modded TWRP so as long as you flashed from within TWRP/fastboot and it was successful, you are on the version you flashed.
But i cant boot my system
Hunter9037 said:
But i cant boot my system
Click to expand...
Click to collapse
1. Can you tell us what version of TWRP you're running.
2. If you go into TWRP > Wipe > check data and click Change/Repair Partition, what filesystem is listed for your /data partition?
Hw4ng3r said:
1. Can you tell us what version of TWRP you're running.
2. If you go into TWRP > Wipe > check data and click Change/Repair Partition, what filesystem is listed for your /data partition?
Click to expand...
Click to collapse
Sure, thats the TWRP mod Version 3.0.2-1
Rom: OnePlus 3 OxygenOS Open Beta 9 (VOpen Beta 9 (2016-12-14))
Mount Point: /data
File system: f2fs
Present: Yes
Removable: No
Size: 54918 MB
Used: 0MB
Free: 52622 MB
Backup Size: 0MB
Finaly! i made it! I get back to Stock Recovery and the Phone starts with a message: "failed to install update" after that he restarted with success
I had formatted all things including internal storage using twrp. After that I flashed oxygen os 4.0 with USB using twrp.Installation is successfull.But when I rebooting the system it still boots into TWRP screen.I am not able to see one plus boot logo as it always boots to twrp screen even after successfully installation.I am wondering why even after succesfull flashing still the phone always boot into twrp screen.Pls help in resolving the issue
Flashing a lower version and then the 28 version back helped me... Had the same problem
jaganmohans said:
I had formatted all things including internal storage using twrp. After that I flashed oxygen os 4.0 with USB using twrp.Installation is successfull.But when I rebooting the system it still boots into TWRP screen.I am not able to see one plus boot logo as it always boots to twrp screen even after successfully installation.I am wondering why even after succesfull flashing still the phone always boot into twrp screen.Pls help in resolving the issue
Click to expand...
Click to collapse
1 ) flash stock recovery and sideload full zip of 3.2.8 oxygen os
2) boot to system
3) reboot to stock recovery
4) sideload full zip of 4.0.1
5) boot to system
6) boot to bootloader and flash twrp -28 recovery (adb fastboot flash)
7) after flashing boot to twrp recovery from bootloader
8) flash SU SR2 v2.79 and boot to system
Hi!
Does Magisk (including root, etc.) work flawlessly on a Pixel C with Android 8.1? Or is better to stay with 8.0 and wait a little bit?
Thanks in advance and kind regards,
star3141.
It works, initially it would force close but now seems stable. I used v14.5 beta.
On the other hand super su by chainfire does not work. Would flash but app missing. Downloading from play store and updating binaries through app causes boot loop.
v14.5 works perfectly here, no problems at all.
Hi!
Thanks for the replies. Maybe I will give it a try at Christmas or alternatively wait for the first update of 8.1 in January.
Hello!
Today, I gave it a try but unfortunately faced some kind of total reflection.
1. I downloaded and flashed the latest android factory image (ryu-opm1.171019.016 = 8.1 from Feb. 2018) from Google.
2. I downloaded and booted (without installing) twrp-3.2.1-0-dragon by means of "fastboot boot twrp-3.2.1-0-dragon.img"
3. In TWRP I mounted the system partition rw
However, after mounting the system partition rw, android won't boot into the system anymore. I am alway getting the green android guy laying on its back with "No command". When I boot into TWRP and mount /system in ro-mode, then will boot afterwards without any problems. So the problem must be related to mounting /system in rw-mode by TWRP.
I have also tried twrp-3.0.0-0-dragon-ryu-02112016-1.img, which worked on my previous 8.0 installation, but it won't work in this 8.1 release anymore.
Any ideas how to get rid of this problem?
Thanks in advance and kind regards,
star3141.
Hello!
I found a solution!
If someone else suffers from similar problems then try the following which hopefully will fix everything: :fingers-crossed:
1. Download and flash the latest (in my case Android 8.1 from Feb. 2018) android factory image from Google.
2. Complete the standard android setup procedure and, when the system is up and running, enable "USB debugging" in the "Developer Options".
3. Restart your device in bootloader mode by "adb reboot bootloader".
4. Format your /data partition by "fastboot format userdata" to remove the filesystem encryption.
5. Download the latest TWRP (in my case "twrp-3.2.1-0-dragon.img") and start it by "fastboot boot twrp-3.2.1-0-dragon.img".
6. In TWRP mount /system in rw-mode and just to be sure check if the /data partition can be accessed. If not, just wipe/format it as ext4 again.
7. Download the latest Magisk (in my case "Magisk-v15.3.zip") and sideload it by "adb sideload Magisk-v15.3.zip" in TWRP.
8. Reboot into the android system and install the Magisk app (in my case "MagiskManager-v5.5.5.apk")
9 Viola! Enjoy a working and rooted android 8.1. :victory:
Kind regards,
star3141.
didn't have any problems with magisk 15.3 on 8.1 but with 16.0 the pixel won't boot anymore (stays at the google logo, not even reaching the bootaniamtion). anyone else having this issue? after flashing boot-image and reinstalling magisk 15.3 it works fine again...
For me as well, get 16.0 not to run, Bootloop
Yep, same here, then I bricked it restoring a nandroid backup where it destroyed system, then I couldn't get past encryption password in TWRP. So it's been one of those days...
m+a+r+k said:
Yep, same here, then I bricked it restoring a nandroid backup where it destroyed system, then I couldn't get past encryption password in TWRP. So it's been one of those days...
Click to expand...
Click to collapse
did you already try "default_password" (without quotes of course)? had this issue too some time ago after restoring a nandroid – reflashing twrp via fastboot and decrypting with default_password helped
doumer said:
did you already try "default_password" (without quotes of course)? had this issue too some time ago after restoring a nandroid – reflashing twrp via fastboot and decrypting with default_password helped
Click to expand...
Click to collapse
Yes, tried that as well. I think I just corrupted the system, wiped data and system in trying to get around the Magisk problem.
m+a+r+k said:
Yes, tried that as well. I think I just corrupted the system, wiped data and system in trying to get around the Magisk problem.
Click to expand...
Click to collapse
Hm, as long as you still have fastboot access, I would try to manually flash partiotions (system, vendor etc), flash twrp, install masgisk 15.3, start from scratch and restore the apps with titanium backup (hopfully you have a backup!). as long as its not a hard brick, it's all fixable
doumer said:
Hm, as long as you still have fastboot access, I would try to manually flash partiotions (system, vendor etc), flash twrp, install masgisk 15.3, start from scratch and restore the apps with titanium backup (hopfully you have a backup!). as long as its not a hard brick, it's all fixable
Click to expand...
Click to collapse
Oh, I'm back to normal now. I couldn't get it to connect to PC as all I had was fastboot and recovery. I discovered the only way to get adb/fastboot connection from PC was to go into TWRP and ADB Sideload. Once that was established it made the connection and I installed 8.1 from the command line with the flash-all.bat.
Then I could restore the nandroid. All is well now, thanks.
good to hear!
Same problem here with 16.0. Seems to be either a bug or some kind of incompatibility with the pixel c.
Magisk 16 and Pixel C
Any word on resolution of the boot loop issue?
Reflash + downgrade to 15.3 seems the only working solution at the moment.
I have re-rooted using Magisk 15.3 from SuperSu. Am I OK updating to 16.0 through Magisk, or should I try 16.3?
mightywhites29111971 said:
I have re-rooted using Magisk 15.3 from SuperSu. Am I OK updating to 16.0 through Magisk, or should I try 16.3?
Click to expand...
Click to collapse
16.0 causes a boot loop. Somebody else had an issue with 16.3. I'd stay with 15.3. Just turn off update notifications and Magisk won't bother you.
Cheers
Hello, I have a wileyfox swift device, with Lineage 14.1 OS running on it, it has twrp in place, last night i checked updates and there were 3-4 updates all 410- 420 MB i choose latest one and clicked update . after downloading device asked to permit restart for installation.. i clicked yes and since then device boots in twrp automatically, i tried these so far:-
1. In TWRP went to ROOT data/data/linageos updates/ then i found a zip file 416 MB i flashed that, wiled cache and dalvik... still after reboot my device goes in twrp only.
2. In TWRP i went to wipe and marked every option then hit wipe, after this it said NO OS FOUND. so i placed linageos 14+gapps in my sd card and flashed both.... stilll i get same issue
i had even tried to reflash the twrp and tried above ..still no luck!
please help this is my mom's phone, she is leterally mad at me now
Now the phone is unable to boot to system, I have no idea what I could do to fix it as there is no way to use adb or fastboot command…
I remember that the stock rom version is S11a, it have some problems when I tried to root it, and failed to flash recovery even I've got the root permission (response "write error: no space left")
------↑solved by using LG flashtool↑------
Now I am facing the problem that unable to install TWRP recovery using dd, it responds “ write error: No space left on device” I’ve reinstall the LG drivers, reboot the phone, reboot the computer, unroot and root again, but the problem still occurs.
----- update ------
solved by using flashify, and TWRP version 3.3.1 instead of latest 3.6.1, so that it won’t have “secure boot error” warning, and boot to recovery successfully.
But there is a new problem now, when I tried to sideload MindTheGapps after installed LOS 18.1 successfully, it warns me “could not mount /mnt/system! Aborting”. This is the third phone that having this warning for me, and I still couldn’t figure out which step goes wrong.
Nothing goes wrong after flashed to lineage recovery, installed MindTheGapps now.
--update--
I also tried to flash lineage recovery from TWRP on my D855, it also works, I installed MindTheGapps and everything works fine. So this is the problem of TWRP? Or reinstall the recovery is the solution? Maybe I would have a test later.