So the latest and greatest from OnePlus is available now. It's still a beta, but it's daily-driver-stable.
Download:
http://downloads.oneplus.net/2016-03-30/op2/OnePlus_2_OxygenOS_3.0_Beta/
Changelog etc:
https://forums.oneplus.net/threads/oxygenos-3-0-community-build-now-available-for-oneplus-2.439059/
TWRP flashing instructions by @Naman Bhalla:
Naman Bhalla said:
DOWNLOADS :-
recovery.img :- https://www.androidfilehost.com/?fid=24459283995297945
Step 1 :- Clean flash the ROM with new boootloader.
Step 2 :- From TWRP,go to Install Menu,click on Images button.
Step 3 :- Select the recovery.img you just downloaded.Select Recovery.Swipe to flash.
Step 4 :- From TWRP Home,reboot to recovery.
Step 5 :- Clean flash ROM with new bootloader again.
Step 6 :- Reboot into system !!!
Click to expand...
Click to collapse
More detailed instructions (credits again to @Naman Bhalla):
https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
Remember that normal SuperSU doesn't work! Use this instead (credits to @Yash98 and @Naman Bhalla):
https://www.androidfilehost.com/?fid=24459283995297946
IMO, the UI hasn't changed too much. Stock launcher only allows 5x5 grid now, but I normally use Nova anyway. Took some screenshots of some of the changes I noticed. I'm using 400 DPI and, as you can see, the dark mode so it will look a bit different if you're not.
Yeah just checked on Oneplus community site. Anybody flashed it yet?
waiting for TWRP version
tlxxxsracer said:
waiting for TWRP version
Click to expand...
Click to collapse
Check the Naman Bhalla comment in the first page of this thread: https://forums.oneplus.net/threads/oxygenos-3-0-community-build-now-available-for-oneplus-2.439059/
MrJukeHardbane said:
Yeah just checked on Oneplus community site. Anybody flashed it yet?
Click to expand...
Click to collapse
Yeah me, via TWRP. Did a full wipe as instructed and after the reboot my phone does not get past the 1+1 boot logo. Can not boot into TWRP either. This is bull****.
Dun Dunn Dunnnnn....
SammyVDA said:
Yeah me, via TWRP. Did a full wipe as instructed and after the reboot my phone does not get past the 1+1 boot logo. Can not boot into TWRP either. This is bull****.
Click to expand...
Click to collapse
If you read the whole official post you would know it's for oneplus recovery only.
Wysłane z mojego ONE A2003 przy użyciu Tapatalka
SammyVDA said:
Yeah me, via TWRP. Did a full wipe as instructed and after the reboot my phone does not get past the 1+1 boot logo. Can not boot into TWRP either. This is bull****.
Click to expand...
Click to collapse
It worked for me, although for some reason couldn't boot into the new recovery - just hung on 1+ logo. I was about to try unbricking it when the OOS logo suddenly appeared. Am just setting up now
It means that mm update is pushed in Q2 and not releasing tomorrow.
Edited the OP a bit. Sorry I can't do much, I'm not at home atm.
Flashed stock recovery and everything installed fine. Hung at the logo a little bit, but then booted up.
Attempted to reflash TWRP, it took but would not boot into recovery again. However, I flashed the H2-MM TWRP and that seems to be working just fine.
EDIT: SuperSU and Xposed flashed through H2-MM perfectly.
Restored original recovery and flashed. Everything seems OK!
I do not lose my data( music pictures etc) if I flash oxygen recovery? I'm on CM13 and wrtp recovery
Envoyé de mon ONE A2005 en utilisant Tapatalk
mimbel said:
I do not lose my data( music pictures etc) if I flash oxygen recovery? I'm on CM13 and wrtp recovery
Envoyé de mon ONE A2005 en utilisant Tapatalk
Click to expand...
Click to collapse
You shouldn't. I'd back everything up to the computer just to be safe.
mimbel said:
I do not lose my data( music pictures etc) if I flash oxygen recovery? I'm on CM13 and wrtp recovery
Envoyé de mon ONE A2005 en utilisant Tapatalk
Click to expand...
Click to collapse
I'd strongly advise not to keep data partition unformated when converting from cyanogenmod to oxygenos, it will produce problems with all sorts of apps and system components due to configuration mismatch between systems.
Also, oxygenos mm uses same bootloader as hydrogen mm so you will have to use specific recoverys compatible with that bootloader for this update.
Best regards
Peter
it is normal that after the flash remains stationary on the start logo 1+?
pitrus- said:
I'd strongly advise not to keep data partition unformated when converting from cyanogenmod to oxygenos, it will produce problems with all sorts of apps and system components due to configuration mismatch between systems.
Also, oxygenos mm uses same bootloader as hydrogen mm so you will have to use specific recoverys compatible with that bootloader for this update.
Best regards
Peter
Click to expand...
Click to collapse
The data partition and internal storage partition are separate. Wiping /data/ doesn't usually wipe /sdcard/ or whatever they name it now.
That being said, I definitely agree that one should fully wipe when switching from CM to OOS and vice versa.
---------- Post added at 12:36 PM ---------- Previous post was at 12:36 PM ----------
nicola_rebecch95 said:
it is normal that after the flash remains stationary on the start logo 1+?
Click to expand...
Click to collapse
It'll hang for a few 15-30second longer than normal. I had the same fears.
It'll hang for a few 15-30second longer than normal. I had the same fears.
Click to expand...
Click to collapse
It is so for several minutes
nicola_rebecch95 said:
It is so for several minutes
Click to expand...
Click to collapse
Somethings wrong then. Did you flash through TWRP or stock recovery? Dirty flash or clean install?
Some screens
Wysłane z mojego ONE A2003 przy użyciu Tapatalka
Related
Now supports among other things back up to pc. I've installed and tested and works.
https://dl.twrp.me/ailsa_ii/twrp-3.1.0-0-ailsa_ii.img
Edit: the original article https://www.xda-developers.com/twrp...-support-for-adb-backup-ab-ota-zips-and-more/
Edit: seems flashing via TWRP image flash is providing better success than via TWRP app. Recommend updating via TWRP flash.
thanks
Do not work.
Get a black screen if i try to Boot in to twrp.
Must go back to 3.0.4.1..
Eller1987 said:
Do not work.
Get a black screen if i try to Boot in to twrp.
Must go back to 3.0.4.1..
Click to expand...
Click to collapse
u sure ur bl is unlocked?
MaxRink said:
u sure ur bl is unlocked?
Click to expand...
Click to collapse
Yes.
I am in LOS 14.1 and twrp 3.0.4.1. works fine.
Flashed 3.1.0.0. whit Flashify.
Worked great for me! I always flash in TWRP, I guess that a I am old school. Thanks for pointing out the new version. I will have to try out the new ADB backup feature later. Although I am not sure if we are still having problems restoring backups like we used to on this phone. I haven't been able to keep up with the forum's lately.
Wrong thread, this needs to be in General
Mod please move.
I flashed the image file in recovery and I still ended up with a black screen.
borijess said:
I flashed the image file in recovery and I still ended up with a black screen.
Click to expand...
Click to collapse
Weird man i got it working flashing it feom twrp it self
borijess said:
I flashed the image file in recovery and I still ended up with a black screen.
Click to expand...
Click to collapse
Maybe you should also write from which TWRP version you come and which Axon 7 model(US/Chinese/European?) you own?
redandr said:
Maybe you should also write from which TWRP version you come and which Axon 7 model(US/Chinese/European?) you own?
Click to expand...
Click to collapse
i have a A2017G and come from twrp 3.0.4.1..
Which partion must i flash for the update to 3.1.0.0.?
I flashed this 3.1 on my chinese b13 with twrp 3.0.4-1 and everything is fine. Flashed it thru twrp btw.
---------- Post added at 11:26 AM ---------- Previous post was at 11:25 AM ----------
Eller1987 said:
i have a A2017G and come from twrp 3.0.4.1..
Which partion must i flash for the update to 3.1.0.0.?
Click to expand...
Click to collapse
Flash it in twrp install and choose img. Flash it for recovery partition.
redandr said:
maybe you should also write from which twrp version you come and which axon 7 model(us/chinese/european?) you own?
Click to expand...
Click to collapse
twrp 3.0.41 axon 7 us version.
Ok I flashed TWRP through fastboot and it worked. I think my first DL was bad. It was half the size of the second one I downloaded.
Success here too. Thank you.
Its all ok with Axon Zte A2017 Chinese.
The last TWRP I conscioulsy installed was 3.0.4.1 but it now shows 3.0.N1-1, what is that? Could it have been updated automatically from the TWRP app?
Also, before I noticed that my boot partition disappeared from TWRP, I can no longer make backups of it or restore the ones I had. Why could that happen? I get something like "unable to locate boot". Thanks
0Kajuna0 said:
The last TWRP I conscioulsy installed was 3.0.4.1 but it now shows 3.0.N1-1, what is that? Could it have been updated automatically from the TWRP app?
Also, before I noticed that my boot partition disappeared from TWRP, I can no longer make backups of it or restore the ones I had. Why could that happen? I get something like "unable to locate boot". Thanks
Click to expand...
Click to collapse
I am guessing you used EDL mode to install TWRP as that is the modified version, as I saw that too. I used TWRP to flash the 3.0.4-1 image and all is normal.
EDIT: TWRP 3.0.4-1 on A2017U Running modified Stock B15 (lots of APKs frozen). Flashing TWRP 3.1 both from TWRP and from "Official App" results with black screen for Recovery. TWRP 3.0.4-1 re-flashed OK from app.
N1-1 is from unjustified devs bootstack.
lafester said:
N1-1 is from unjustified devs bootstack.
Click to expand...
Click to collapse
N1-1 & 3.0.4-1 both work fine, but 3.1 boots to black screen. Why?
Twrp 3.1.0 worked fine on my Axon 7 US version A2017U
Flashed via fastboot over stock recovery.
Will edit this thread and report back if issue is discovered.
Hi! I have an LG G5 h850 and I've flashed this ROM (a full flashable zip of Android Nougat 7.0 stock). The problem is I can't seem to root my phone.
If I flash any SuperSU zip with TWRP 3.1.0.0, the phone won't be able to boot afterwards (it will get stuck at the LG logo).
I've iunlocked my bootloader using the official procedure (fastboot getvar unlocked returns "yes") and I've also flashed no verity opt encrypt 5.1 after wiping data: my TWRP can access internal storage.
What am I missing? Is there a specific SuperSU zip which works on a Nougat h850? Has the problem got something to do with dm-verity?
I have an LG G5 H850 with TWRP 3.1.0..0 and SuperSU 2.65 installed. I did not install the no-verity and my phone is operating normally. Just need a way to get rid of the "your phone is unlocked" screen on boot up.
Sent from my LG-H850 using Tapatalk
N or M?
Stransky said:
I have an LG G5 H850 with TWRP 3.1.0..0 and SuperSU 2.65 installed. I did not install the no-verity and my phone is operating normally. Just need a way to get rid of the "your phone is unlocked" screen on boot up.
Sent from my LG-H850 using Tapatalk
Click to expand...
Click to collapse
Are you sporting Nougat or Marshmallow? With Android M I rooted it with no problems.
Nougat and i had no problems rooting.
Sent from my LG-H850 using Tapatalk
Stransky said:
Nougat and i had no problems rooting.
Sent from my LG-H850 using Tapatalk
Click to expand...
Click to collapse
That's astounding. Do you remember the procedure you followed? Is the ROM the same I used (LG-H85020A-Flashable.COMPLETE.zip)? Is the precise SuperSU version UPDATE-SuperSU-v2.65-20151226141550?
Patching sepolicy failure
I've proceeded to reinstall N and SuperSU 2.65 and I see the following message:
Code:
- Patching sepolicy
--- Failure, aborting
Given Android N requires systemless mode, hence boot image patching, could this be the cause? What should I do?
HisDudeness3008 said:
That's astounding. Do you remember the procedure you followed? Is the ROM the same I used (LG-H85020A-Flashable.COMPLETE.zip)? Is the precise SuperSU version UPDATE-SuperSU-v2.65-20151226141550?
Click to expand...
Click to collapse
The ROM is the same (H85020a) but my phone was updated OTA.
Sent from my LG-H850 using Tapatalk
---------- Post added at 06:22 PM ---------- Previous post was at 06:15 PM ----------
Further to my last I used @autoprime's unlocking the G5 bootloader thread and followed the instructions on it, including the installation of TWRP etc.
Sent from my LG-H850 using Tapatalk
Enter password to unlock
Stransky said:
The ROM is the same (H85020a) but my phone was updated OTA.
Sent from my LG-H850 using Tapatalk
Click to expand...
Click to collapse
I see... I couldn't update OTA because when it had to install the downloaded update it just rebooted to TWRP.
Anyway, after getting that error message, I flashed a newer version of SuperSU. It patched sepolicy successfully and even booted (I don't know what I did different than other times). Anyway, it prompted me with an "Enter password to unlock message", with some attempts already out (23/30).
Could it be because I have decrypted data partition? I read the decryption and root access are mutually exclusive. I decripted just because, after the 30th failed boot attempt, I tried it just to change something and see if it worked.
If I have to choose between the two, I'll choose root access. How do I restore encryption?
Sorry, have no idea, I don't use encryption.
Sent from my LG-H850 using Tapatalk
Stransky said:
Sorry, have no idea, I don't use encryption.
Sent from my LG-H850 using Tapatalk
Click to expand...
Click to collapse
I mean the default setup of the G5, whereas TWRP can't access internal storage and will ask you for a password upon starting, to which you have to hit "cancel".
When I hit cancel in TWRP in answer to the password I then swipe below to allow modifications. At least that is what I am offered on the swipe window.
Sent from my LG-H850 using Tapatalk
Yeah, that is indeed the default behaviour. However, at some point I've flashed no-verity-opt-encrypt zip. This removes the encryption. TWRP doesn't have to ask you for a password you do not know, and can thus modify /data partition. This, however, prevents you from rooting your device. And, apparently, prevents me from booting my phone right now. Is there any way to revert the effects of no-verity-opt-encrypt?
I am sorry, I am not even remotely akin to a developer, I only follow their instructions so am not aware if it is possible to revert the no- verity effects. The only suggestion I can come up with is to do a factory reset backbto stock Nougat and then redo the installation of TWRP etc omitting "no-verity" option. But I would check with someone like Autoprime first to see if this will work and not create more problems. Sorry I can't be of more help.
Sent from my LG-H850 using Tapatalk
No problem, you've been of enough help! I thank you for your time.
I know, I'm not akin to a developer as well, but I have the bad habit of getting myself into developer trouble
Solved one: I unbricked my phone. Followed this excellent guide from by dksoni411. I thank him with all my heart, as well as AutoPrime, Hyelton, bullghost and anyone else who contributed.
Solved two: I finally managed to root my h850. Don't know what I did different from the other dozen times I tried. From stock Nougat 7.0 I rebooted to fastboot mode via adb, flashed TWRP in fastboot, booted into recovery without allowing normal boot to happen before it, flashed SuperSU (v2.79-20161211114519), didn't wipe cache or dalvik, and rebooted. Upon boot, phone reset once and then booted straight into Nougat, with SuperSU apk installed. Yay!
HisDudeness3008 said:
Solved one: I unbricked my phone. Followed this excellent guide from by dksoni411. I thank him with all my heart, as well as AutoPrime, Hyelton, bullghost and anyone else who contributed.
Solved two: I finally managed to root my h850. Don't know what I did different from the other dozen times I tried. From stock Nougat 7.0 I rebooted to fastboot mode via adb, flashed TWRP in fastboot, booted into recovery without allowing normal boot to happen before it, flashed SuperSU (v2.79-20161211114519), didn't wipe cache or dalvik, and rebooted. Upon boot, phone reset once and then booted straight into Nougat, with SuperSU apk installed. Yay!
Click to expand...
Click to collapse
Tnx man! :good: U should post step by step what u did to root as separate thread, cuz U have been a tremendous helper, u know?? U solved Huuuuuge problem , so U can be great helper to those who could came into similar troubles :victory:
Hey guys!
I have created a TWRP flashable zip of latest Stock MM Rom for G4c.
ONLY FOR H525N
FIX FOR c90n -> c90
Requirements:
(1) Unlocked Bootloader
(2) TWRP
Steps:
(1) Download the ZIP here.
(2) Copy it to your phone.
(3) Reboot into TWRP.
(4) Wipe > Advanced Wipe. Select Dalvik / ART Cache, System, Data, Cache. Swipe to Wipe.
(5) Select "Install". Select the zip file you downloaded in the first step.
(6) Swipe to flash. Wait for it to flash. It might take some time. Wipe Dalvik/Cache after you flash to avoid bootloops.
(7) Select Reboot.
You have successfully flashed MM!
If you want root, download SuperSu Flashable Zip. Reboot into TWRP. Select the SuperSu flashable zip. You have successfully rooted!
I will keep updating the ZIP as and when LG releases a new ROM or patch.
Hold on guys. Don't flash it for now, we need to modify the file. Update will come soon.
Anghirrim said:
Hold on guys. Don't flash it for now, we need to modify the file. Update will come soon.
Click to expand...
Click to collapse
Done.
pvineeth97 said:
Hey guys!
I have created a TWRP flashable zip of latest Stock MM Rom for G4c.
ONLY FOR H525N
FIX FOR c90n -> c90
Requirements:
(1) Unlocked Bootloader
(2) TWRP
Steps:
(1) Download the ZIP here.
(2) Copy it to your phone.
(3) Reboot into TWRP.
(4) Wipe > Advanced Wipe. Select Dalvik / ART Cache, System, Data, Cache. Swipe to Wipe.
(5) Select "Install". Select the zip file you downloaded in the first step.
(6) Swipe to flash. Wait for it to flash. It might take some time. Wipe Dalvik/Cache after you flash to avoid bootloops.
(7) Select Reboot.
You have successfully flashed MM!
If you want root, download SuperSu Flashable Zip. Reboot into TWRP. Select the SuperSu flashable zip. You have successfully rooted!
I will keep updating the ZIP as and when LG releases a new ROM or patch.
Click to expand...
Click to collapse
Glad to see you guys look like you got everything worked out finally....Good job:good:
TheMadScientist said:
Glad to see you guys look like you got everything worked out finally....Good job:good:
Click to expand...
Click to collapse
You should thank @pvineeth97. Ahmed and I are just testing.
Anghirrim said:
You should thank @pvineeth97. Ahmed and I are just testing.
Click to expand...
Click to collapse
New Version uploaded.
Version: 1.4
Everything is working even with root?
Wysłane z mojego LG-H525n przy użyciu Tapatalka
DonOleq said:
Everything is working even with root?
Wysłane z mojego LG-H525n przy użyciu Tapatalka
Click to expand...
Click to collapse
Yep guy. You can root with supersu and it survives reboot.
First, unlock your phone by flashing the aboot (it works fine now, but only if you are under lollipop n10f).
This kdz works fine, to flash with LGUp
https://lg-firmwares.com/download-file/?fileId=3354
Then install TWRP from the official thread.
You know what? I'm going to make it. I need to be on v10f to unlock bootloader and install twrp?
Wysłane z mojego LG-H525n przy użyciu Tapatalka
DonOleq said:
You know what? I'm going to make it. I need to be on v10f to unlock bootloader and install twrp?
Wysłane z mojego LG-H525n przy użyciu Tapatalka
Click to expand...
Click to collapse
Lol, I was editing my answer. See above.
Once you have TWRP installed, you can flash the MM zip and supersu.
The rom works pretty smoothly once debloated.
Just one thing, this MM zip has a MM specific patched aboot and TWRP.
Indeed, on our phone, the LP and MM structures are completely different. So the LP patched aboot does not work on MM.
For TWRP, under LP, the phone is named c90n and in MM, it's c90. So it changes this.
---------- Post added at 08:07 PM ---------- Previous post was at 07:59 PM ----------
@DonOleq
Join us on Telegram. We have a small discussion group to work on LOS without spamming too much the XDA threads with WIP's.
https://t.me/joinchat/E1Fw0gyeVrsBeek3ue3xXw
Can someone provide me with a link to flashable marshmellow zip for the h525n? The dropbox link in the thread is expired. I need the a flashable marshmellow to install lineageos.
LwannaCM said:
Can someone provide me with a link to flashable marshmellow zip for the h525n? The dropbox link in the thread is expired. I need the a flashable marshmellow to install lineageos.
Click to expand...
Click to collapse
Let me ask Vineeth.
http://www.mediafire.com/file/0hyol4xz2yprlz8/H525n_MM_TWRP.zip
LwannaCM said:
Can someone provide me with a link to flashable marshmellow zip for the h525n? The dropbox link in the thread is expired. I need the a flashable marshmellow to install lineageos.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B_K7Ht571iIVV1pxNGZ1Y0hydkU/view
We are moving to Slack. Here's an invitation link for everyone: https://join.slack.com/t/g4cdevcamp...U2MmQxYzE0YmYxMjMxYjRkMmNjYzcxNjFlNzMwYWYwNDU
Hi guys.
I just want to tell you that, thanks to you, I have been able to resuscitate my device. My LG G4c has the bootloader unlocked, it is rooted and it runs with MM. Thanks to all and, especially, to @ahmed.al, for guiding me, to @Anghirrim, for his good indications, and to @pvineeth97, for his magnificent work.
Thank you very much.
Mondark said:
Hi guys.
I just want to tell you that, thanks to you, I have been able to resuscitate my device. My LG G4c has the bootloader unlocked, it is rooted and it runs with MM. Thanks to all and, especially, to @ahmed.al, for guiding me, to @Anghirrim, for his good indications, and to @pvineeth97, for his magnificent work.
Thank you very much.
Click to expand...
Click to collapse
Cool and happy it worked for you. Thanks for this Nice message.
Join us on Telegram to follow-up on LOS development.
Hey guys, i flashed this rom from latest TWRP 3.2.1.0 but when the phone boots the led notification stays always on color red
Dr4In said:
Hey guys, i flashed this rom from latest TWRP 3.2.1.0 but when the phone boots the led notification stays always on color red
Click to expand...
Click to collapse
I'm about to flash a G4c in the next few days, at the moment I'm reading through the topics to do things right.
There are only some things that make me unsure of the process. One of it ist mentionend above by user @Dr4In. Maybe @Anghirrim or @pvineeth97 can say something about this problem?
The problem is also described here in the last post:
https://forum.xda-developers.com/g4c/development/rom-android-6-0-marshmallow-lg-g4c-t3314927
tito_puente said:
I'm about to flash a G4c in the next few days, at the moment I'm reading through the topics to do things right.
There are only some things that make me unsure of the process. One of it ist mentionend above by user @Dr4In. Maybe @Anghirrim or @pvineeth97 can say something about this problem?
The problem is also described here in the last post:
https://forum.xda-developers.com/g4c/development/rom-android-6-0-marshmallow-lg-g4c-t3314927
Click to expand...
Click to collapse
Personally i didnt find any fix for the notification red led which was 24/24 open so i went back to stock rom, the only advice i can give you is, if you install LOS make sure not to do Factory Reset from the settings, because after that the phone only booting to TWRP and if you install the rom from TWRP it wont boot its just booting into the TWRP, the only way to brake this loop is by flashing stock rom with LGUP.
In the link you mention it was my mistake about LGUP and i figure it out later.
Dr4In said:
Personally i didnt find any fix for the notification red led which was 24/24 open so i went back to stock rom, the only advice i can give you is, if you install LOS make sure not to do Factory Reset from the settings, because after that the phone only booting to TWRP and if you install the rom from TWRP it wont boot its just booting into the TWRP, the only way to brake this loop is by flashing stock rom with LGUP.
In the link you mention it was my mistake about LGUP and i figure it out later.
Click to expand...
Click to collapse
The led problem have been solved at least in AEX. Don't remember for LOS 14.1.
There is a turnaround as well in order to completely disable the led. I can find it back.
Hi,
I've built TWRP for the XZ1. Has someone and unlocked bootloader and is willing to test it?
Idk but we need good custom stock!
Wysłane z mojego G8342 przy użyciu Tapatalka
Araa01 said:
Idk but we need good custom stock!
Click to expand...
Click to collapse
Then test it.
4rz0 said:
Then test it.
Click to expand...
Click to collapse
Test? Where is twrp?
Where is unlock bl?
Where is custom?
Wysłane z mojego G8342 przy użyciu Tapatalka
Araa01 said:
Test? Where is twrp?
Where is unlock bl?
Where is custom?
Wysłane z mojego G8342 przy użyciu Tapatalka
Click to expand...
Click to collapse
That's what this thread is about. You can unlock your bootloader on the Sony webpage.
After that, you tell the OP that you want to test their TWRP release.
I´d like to test it, but installation/test requires root, does it not?
I have unlocked BL, but i still have no rooting method
modpunk said:
Hi,
I've built TWRP for the XZ1. Has someone and unlocked bootloader and is willing to test it?
Click to expand...
Click to collapse
Look up.
Wysłane z mojego G8342 przy użyciu Tapatalka
I want to test the twrp. I unlocked and I want to flash the new recovery
N1ghtr08d said:
I want to test the twrp. I unlocked and I want to flash the new recovery
Click to expand...
Click to collapse
You can find it here https://xor.cryptomilk.org/android/twrp-3.2.0-0-poplar-patchlevel-2017-11-05.img
Which firmware version is this for? I'm currently running 47.1.A.5.51 November 1st 2017
N1ghtr08d said:
Which firmware version is this for? I'm currently running 47.1.A.5.51 November 1st 2017
Click to expand...
Click to collapse
This has not firmware version, it is a TWRP recovery ...
Ok perfect. Thanks.
I'm new to modding Sony phones. There is a thread with the xperifix talking about downloading according to the correct firmware version so I just wanted to cover my ass, just in case.
You're right, there's something with the backup encryption depending on the firmware version.
So what does that mean for me in this case?
how do i access TWRP after i flashed it? i have the bootloader unlocked and i flashed TWRP but when i'm connected through adb and i run "adb reboot recovery" nothing happens except the phone reboots as normal and i'm not sure of the hardware button combo to boot into recovery. I'm thinking it's power+vol up but when i do that the phone just vibrates once then three times and does nothing, not even boot normally.
Can you help please?
---------- Post added at 10:56 PM ---------- Previous post was at 10:52 PM ----------
Never mind, i figured out the button combo. It's power+vol down when the phone vibrates once release power and hold onto the vol down button
---------- Post added at 11:20 PM ---------- Previous post was at 10:56 PM ----------
OP, so here's the scoop. Every time i boot into recovery it asks for the password to decrypt, i don't know what that might be so i click cancel. Also i went into WIPE and i formatted DATA and typed YES and it did it's thing and i had to set up the phone again as expected however when i get back into the OS and check the security section of settings, it says it's still encrypted.
I'd like to flash supersu 2.82 but because it's encrypted i can't find the folder i placed it into and i don't have an SD card handy to place it on that to install. And besides i wanna get rid of the encryption anyway so we need to figure that out asap please.
Is there any kind of default password that i can use when entering TWRP to decrypt the data? And how can we remove encryption from the phone correctly with TWRP?
Thanks
N1ghtr08d said:
how do i access TWRP after i flashed it? i have the bootloader unlocked and i flashed TWRP but when i'm connected through adb and i run "adb reboot recovery" nothing happens except the phone reboots
Click to expand...
Click to collapse
Rebooting to recovery with adb is broken in the Sony Kernel. I've fixed that already for LineageOS.
N1ghtr08d said:
OP, so here's the scoop. Every time i boot into recovery it asks for the password to decrypt, i don't know what that might be so i click cancel.
Click to expand...
Click to collapse
The password is the PIN of your device.
N1ghtr08d said:
Also i went into WIPE and i formatted DATA and typed YES and it did it's thing and i had to set up the phone again as expected however when i get back into the OS and check the security section of settings, it says it's still encrypted.
Click to expand...
Click to collapse
The phone uses File Based Encryption and is normally always encrypted. If you don't set a PIN the password is set to "default_password". If you set a PIN the key to unlock FBE is encrypted using your PIN.
N1ghtr08d said:
I'd like to flash supersu 2.82 but because it's encrypted i can't find the folder i placed it into and i don't have an SD card handy to place it on that to install. And besides i wanna get rid of the encryption anyway so we need to figure that out asap please.
Click to expand...
Click to collapse
I think for SuperSU you need a special Xperia version they offer here on XDA ...
Thanks for the quick reply. Do you have a working version of lineage for the Xperia XZ1?
Hi
I'm on 47.1.A.5.51, unlocked BL
Downloaded https://xor.cryptomilk.org/android/twrp-3.2.0-0-poplar-patchlevel-2017-11-05.img
Installed TWRP image
adb reboot bootloader
fastboot flash recovery twrp-3.2.0-0-poplar-patchlevel-2017-11-05.img
fastboot reboot
Click to expand...
Click to collapse
Rebooted into recover (Vol-)
Tried to install SU from https://forum.xda-developers.com/attachment.php?attachmentid=4164510&d=1496008012 as stated in How to Install TWRP
Got error in installer within TWRP:
Super SU Installer
- Mounting /system, /data and rootfs
- BAD RECOVERY DETECTED, NO UNZIP, ABORTING
Installed latest Magisk zip file from Magisk tread and flashing was successful.
Wiped caches, rebooted and it hang on Sony logo
Flashing Magisk Uninstaller Makes the phone boot again but it warns about corrupt system at boot. Have to reflash stock rom without userdata.sin in order to get rid of the corrupt warning
2.82 doesn't work for Xperia users. I believe 2.79 is still recommend by chainfire for us. I'm about to flash it right now. I'll report back with the result in a few minutes. If you don't hear from me.... Something drastic went wrong! Fingers crossed.
---------- Post added at 02:48 PM ---------- Previous post was at 02:44 PM ----------
Ok so I got exactly the same result as pergoteborg. I'm gonna do a little research because I think I read something about the "no unzip" in another thread.
So i followed a few steps from another thread to create a symlink to unzip and was able to successfully flash supersu 2.79 however when i reboot into the OS there is no Supersu installed and when i run root checker it fails saying there is no root, also the official Supersu app from the app store says "Root undetected".
The steps i followed to create the symlink are as follows:
1. Boot to twrp.
and now comes the trick
2. Connect your device to a pc and adb push the attached busybox to sbin (took it from twrp from another arm64 device cannot remember which).
adb push pathtobusybox\busybox /sbin/ (replace pathtobusybox with the loacation of the unziped busybox for example C:\ )
3. Open adb shell
adb shell
4. Give busybox the required rights
chmod 750 /sbin/busybox
5. Create unzip symlink
ln -s /sbin/busybox /sbin/unzip
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Otg works
- Flash Rom works
- F2FS support
- Fastboot boot command support
Not working:
- Fastbootd
- Adb sideload
- Backup restore and image flash (system-vendor-product)
- Android 11 fully support
Download:
TWRP 3.4.0-14 Unofficial by mauronofrio
TWRP 3.4.0-12 Unofficial by mauronofrio
To Flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually or using a fastboot command.
Code:
fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img
or
Code:
fastboot oem reboot-recovery
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/Teamwin/android_bootable_recovery
https://github.com/mauronofrio/android_device_xiaomi_lmi
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
- Thanks to @bigbiff and @Captain_Throwback for the hard work on this android 10 TWRP
Thanks to all testers on the Telegram Group
Created 2020-09-23
Wicked work m
Nice to see the first thread appear here
Actually, i've found a homemade TWRP which is most of the function work fine and can be used to flash by adb. But unfortunately it seems not be maintain any longer, i want to share it to you and hope it can help you to fix you bugs and be strong enough and stable enough, keep going dude. Here is the link:https://mega.nz/file/njxCXSqA#R37PC2vpICMMsm4kqyu_V1PHGH4BRmTeMCgUZtgALZc
Omg its kicking off
I've translated it to polish and made a topic at miuipolska.pl ( xiaomi.eu for our country). Nice to see you here too
Wysłane z mojego POCO F2 Pro przy użyciu Tapatalka
I've flashed the TWRP, did a format, reboot recovery, and it asked for password for decrypt data.
I've never set any password before, any idea why ?
Update, also did the following from scratch :
- Flash back to original China ROM via Miflash (fastboot). Booted back to MIUI.
- Reboot to fastboot
- Flash the TWRP 3.4.0-12 as above, and went into recovery
- Format Data
- Reboot Recovery
- Again, it's asking for decrypt data password.
Mine is a K30 Pro, if it matters.
i just installed it and it seems working good at least everything that i use thanks for the work
Thank you for sharing twrp with us, can I flash above the old one or I need to flash new rom for that
Sent from my POCO F2 Pro using Tapatalk
Thaiban said:
Thank you for sharing twrp with us, can I flash above the old one or I need to flash new rom for that
Sent from my POCO F2 Pro using Tapatalk
Click to expand...
Click to collapse
i Just did without flashing, no issue here
Envoyé de mon POCO F2 Pro en utilisant Tapatalk
soza971 said:
i Just did without flashing, no issue here
Envoyé de mon POCO F2 Pro en utilisant Tapatalk
Click to expand...
Click to collapse
Have u tried flashing a ROM with this recovery ?
Then going back to the recovery, can it decrypt the data properly ? Assuming u didn't set any pass lock in ur MIUI.
takagen said:
Have u tried flashing a ROM with this recovery ?
Then going back to the recovery, can it decrypt the data properly ? Assuming u didn't set any pass lock in ur MIUI.
Click to expand...
Click to collapse
i did not flash any rom i never had to, it worked normally Just after flashing the recovery
Envoyé de mon POCO F2 Pro en utilisant Tapatalk
takagen said:
I've flashed the TWRP, did a format, reboot recovery, and it asked for password for decrypt data.
I've never set any password before, any idea why ?
Update, also did the following from scratch :
- Flash back to original China ROM via Miflash (fastboot). Booted back to MIUI.
- Reboot to fastboot
- Flash the TWRP 3.4.0-12 as above, and went into recovery
- Format Data
- Reboot Recovery
- Again, it's asking for decrypt data password.
Mine is a K30 Pro, if it matters.
Click to expand...
Click to collapse
Same here. its asking me password for decryption data partition but I don't have any password !
hrh_fourtyseven said:
Same here. its asking me password for decryption data partition but I don't have any password !
Click to expand...
Click to collapse
Thanks for confirming the same issue.
I would have thought I've missed some steps.
But just by formatting data, without doing anything else and rebooting back to recovery it's already asking for decrypt password, which none were set in the first place.
takagen said:
Thanks for confirming the same issue.
I would have thought I've missed some steps.
But just by formatting data, without doing anything else and rebooting back to recovery it's already asking for decrypt password, which none were set in the first place.
Click to expand...
Click to collapse
Did you try the old password to unlock miui ?
Envoyé de mon POCO F2 Pro en utilisant Tapatalk
hrh_fourtyseven said:
Same here. its asking me password for decryption data partition but I don't have any password !
Click to expand...
Click to collapse
soza971 said:
Did you try the old password to unlock miui ?
Envoyé de mon POCO F2 Pro en utilisant Tapatalk
Click to expand...
Click to collapse
No password has been set whatsoever.
Even if it has been, formatting would have cleared it anyway.
If u read what I've shared, I had also miflash back to original state n start all over, still the same.
If you may, probably u can try flashing back the same ROM on top of what u have, go back to TWRP n see if u have any issue.
takagen said:
No password has been set whatsoever.
Even if it has been, formatting would have cleared it anyway.
If u read what I've shared, I had also miflash back to original state n start all over, still the same.
If you may, probably u can try flashing back the same ROM on top of what u have, go back to TWRP n see if u have any issue.
Click to expand...
Click to collapse
i am stock right now flashed with miflash , if i flash back rom with miflash i will have to flash twrp again, btw what rom are you trying to flash? xiaomi.eu ?
Envoyé de mon POCO F2 Pro en utilisant Tapatalk
soza971 said:
i am stock right now flashed with miflash , if i flash back rom with miflash i will have to flash twrp again, btw what rom are you trying to flash? xiaomi.eu ?
Envoyé de mon POCO F2 Pro en utilisant Tapatalk
Click to expand...
Click to collapse
Didn't even got the chance to flash any ROM.
Format data, did a recovery reboot, will end up with this issue. Since can't decrypt data, so no ROM can be copied in to flash
takagen said:
Didn't even got the chance to flash any ROM.
Format data, did a recovery reboot, will end up with this issue. Since can't decrypt data, so no ROM can be copied in to flash
Click to expand...
Click to collapse
i am out of solution sorry
The thing is that it s working by my side but right now i need my Phone tonight i gonna try to flash Xiaomi.eu and let you know
Envoyé de mon POCO F2 Pro en utilisant Tapatalk
soza971 said:
i am stock right now flashed with miflash , if i flash back rom with miflash i will have to flash twrp again, btw what rom are you trying to flash? xiaomi.eu ?
Envoyé de mon POCO F2 Pro en utilisant Tapatalk
Click to expand...
Click to collapse
soza971 said:
One question after miflash did you boot miui to set it up ? Or did you flash the twrp right after the flash with miflash ?
Envoyé de mon POCO F2 Pro en utilisant Tapatalk
Click to expand...
Click to collapse
After miflash, booted into MIUI successfully.
Rebooted into fastboot to install Twrp per instruction.
takagen said:
After miflash, booted into MIUI successfully.
Rebooted into fastboot to install Twrp per instruction.
Click to expand...
Click to collapse
I edited my post above read it tonight i Will try to flash Xiaomi.eu i cant before i need my Phone in the day
Envoyé de mon POCO F2 Pro en utilisant Tapatalk