{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello!
We are back with brand new Pie beta builds, for you all to play with.
[Changelog]
Bug fixes
Clock timer and stopwatch interface display is incomplete
Microphone doesn't work when earphones are plugged in
Crash issues with native message app
Those who download the Community Beta build will get OTA update when the stable build is released.
Instructions for updating to the Community Build
Backup your entire device as it is a big update and change of Android version
For those on the latest stable version 181206
Preconditions: Boot Loader should be locked
Steps:
1. Download the file from the link provided on the forum post
2. Move the downloaded file to internal storage root folder using the File Manager.
The device can then be updated via two methods.
First method: Local Update
1. Open Settings -> System update -> Click top right setting icon
2. Choose Local update
3. Click on the downloaded file and wait until the device reboots
Second Method: Recovery Update
1. Turn off the device -> Press power and volume up key simultaneously until the device enters the Fastboot Mode
2. Navigate to Recovery option using volume and power button -> Choose English -> Install from Internal storage -> Select the downloaded zip file -> Select 'Yes'
3. Wait until the installation is complete -> Reboot
For those who are on the latest Open Beta version 180712
Note: The entire data will be wiped since there will be a version transition from Open beta to the stable version. If you made a OnePlus Switch backup, be sure to make a copy of it before moving forward.
Steps:
1. Download the file from the link provided on the forum post
2. Move the downloaded file to internal storage
3. Device can be updated only via Recovery Update:
Turn off the device -> Press power and volume up key simultaneously until the device enters the Fastboot Mode
Navigate to Recovery option using volume and power button -> Choose English -> Install from Internal storage -> Select the downloaded zip file -> Select 'Yes'
Wait until the installation is complete -> Reboot
FAQ
1. Dirty flash over TWRP - gives Decryption error and will lose data.
2. Dirty / clean flash over unlocked bootloader- leads to loss of data
3. Magisk / rooting - works without issues
4. Titanium backup - works without issues
In case of unlocked bootloader or custom recovery - Backup and flash Pie community Beta build, restore backup or wait till official release.
Flashing over leaked build - users report to be working,no official support would be available on this.
Thank you once again for all your patience. We are one step closer to releasing the Pie for OnePlus 3 / 3T, you can now download and try our community build right now.
Never Settle.
Downloads
Community Beta 2 - OnePlus 3T
Community Beta 2 - OnePlus 3
Community Beta - OnePlus 3T
Community Beta - OnePlus 3
Official TWRP 3.3.0-1
ROOT: Magisk
Want to get rid of DM-Verity/Force Encryption? Check this THREAD
Please let me know if i'm missing anything. Thanks
Sent from my OnePlus 3T using XDA Labs
Nice?
Siddk007 said:
Hope to see active discussion in the new thread as well
Click to expand...
Click to collapse
I tried to flash open beta 20 but i had white led and black screen.
So hear how i did it.I have Blu_Spark TWRP v8.61 and I am on ext4 only data,so I wipe everything except internal store.
I flash the full beta 20 zip which i have to my download section,and the flash finished succseful.But then when i tried to flash the magisk 15.0 the phone stuck in the recovery and then closed and then white led and black screen!
So i went back to recovery manually and flash my back up and i am in Freedom Os now.
Can you explain me what was wrong?
P.s I did that twice and with magisk 14.6.
Thank you for opening this Thread!And I wish to all happy new year!
xarrismoto said:
I tried to flash open beta 20 but i had white led and black screen.
So hear how i did it.I have Blu_Spark TWRP v8.61 and I am on ext4 only data,so I wipe everything except internal store.
I flash the full beta 20 zip which i have to my download section,and the flash finished succseful.But then when i tried to flash the magisk 15.0 the phone stuck in the recovery and then closed and then white led and black screen!
So i went back to recovery manually and flash my back up and i am in Freedom Os now.
Can you explain me what was wrong?
P.s I did that twice and with magisk 14.6.
Thank you for opening this Thread!And I wish to all happy new year!
Click to expand...
Click to collapse
Unmount system prior to flashing the rom
Nice to open d thread..... mch needed...... Thanks to siddk007:good:
Thank you for your thread, Siddk007.
2018
Hi community,
nice to see the thread continued.
Wish all members here a happy New Year!
Greets, reinipic
@DarkSJ1998 because last discussion is locked i'm replying here, I used magisk v15.1
I have fixed the issue by flashing OOS5.0.1 then i experienced messages FC and checked someone else in oneplus forum had same problem then i flashed OB20 again and both issues are fixed.
The only weird thing is right after i flashed OOS5.0.1 in twrp the twrp showed another loading patching partition then rebooted so i couldn't flash Magisk and wipe cache do i had to flash twrp again with fastboot mode then flashed magisk and again twrp rebooted itself without any option. When i flashed OB20 same thing?! Previously soon after i flashed rom zip it used to give me to back to twrp main menu or wipe dalvik cache or reboot. Using twrp-3.2.1-0
lover said:
@DarkSJ1998 because last discussion is locked i'm replying here, I used magisk v15.1
I have fixed the issue by flashing OOS5.0.1 then i experienced messages FC and checked someone else in oneplus forum had same problem then i flashed OB20 again and both issues are fixed.
The only weird thing is right after i flashed OOS5.0.1 in twrp the twrp showed another loading patching partition then rebooted so i couldn't flash Magisk and wipe cache do i had to flash twrp again with fastboot mode then flashed magisk and again twrp rebooted itself without any option. When i flashed OB20 same thing?! Previously soon after i flashed rom zip it used to give me to back to twrp main menu or wipe dalvik cache or reboot. Using twrp-3.2.1-0
Click to expand...
Click to collapse
can u please confirm if Magisk 15.1 works with oos 5.0.1 as its not working for some users
Sent from my OnePlus 3T using XDA Labs
Siddk007 said:
can u please confirm if Magisk 15.1 works with oos 5.0.1 as its not working for some users
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
It worked but Messages FC.
lover said:
It worked but Messages FC.
Click to expand...
Click to collapse
thanks, btw this has nothing to do with message fc. try clearing data of messages app
Sent from my OnePlus 3T using XDA Labs
Siddk007 said:
thanks, btw this has nothing to do with message fc. try clearing data of messages app
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
When i was on OOS5.0.1 i did clear data of Messaging app. But did not solve the problem. Surprisingly when i did flash OB20 over it all my messages was there and was not lost
stuck on 1+ logo after flashing
followed the instructions too!!!!!!
what to do now?
[email protected]@rjnj said:
stuck on 1+ logo after flashing
followed the instructions too!!!!!!
what to do now?
Click to expand...
Click to collapse
Did you flash magisk?...or SuperSU?...
cultofluna said:
Did you flash magisk?...or SuperSU?...
Click to expand...
Click to collapse
Magisk
Now i flashed ob18 again with magisk and restored the data
But i want ob20 because some apps are giving problems in beta 18
[email protected]@rjnj said:
Magisk
Now i flashed ob18 again with magisk and restored the data
But i want ob20 because some apps are giving problems in beta 18
Click to expand...
Click to collapse
Wich version of magisk?....
Reflash OB 20 and magisk 14.6 afterwards..
OP updated with Magisk 14.6 to avoid further issues to users
Later update from app to 15.1
Related
UPDATE 10/02/2016- New version of TWRP has been released v3.0.3-0. See below:
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
I have updated versions SM-T800/805 with new builds. TWRP is now v3.0.3-1
TWRP OFFICIAL APP RELEASED: https://twrp.me/app/
Fixes:
Download mode now available in REBOOT options.
Root Shell now available in ADB.
Radio and Recovery backup.
System image backup/restore
Factory image flashing.
Supersu root option removed. This is to pre-empt the upgrade to MM which would cause a bootloop.
MTP fix - MTP now finally working in recovery.
Note: On my PC MTP works perfect in windows 7, but on Windows 8.1 was a little quirky. If you get a USB DEVICE NOT RECOGNISED error after enabling MTP, disable then quickly re-enable MTP and this should fix it.
This version also has system image backup and restore included. It is also possible to flash factory firmware images via the Image install button. (see the TWRP changelog above for more info)
UPDATE 5/3/16:
Have modified the twrp source code and extended factory image partition flashing to include all images except SBOOT.bin (still working on how to flash the bootloader via recovery)
This means BOOT, SYSTEM, RECOVERY, CACHE, HIDDEN, MODEM(RADIO) can all be flashed from the factory firmware. No need for ODIN anymore. As far as I know the Tab S is the only device supporting this at the moment.
(Note: to flash the modem it is necessary to rename MODEM.bin to MODEM.bin.img first)
TWRP_3.0.2-1-T700
TWRP-3.0.2-1-T705
TWRP-3.0.2-1-T800
NOTE: Certain models of the T800 version have a bug at the moment where the screen will be blank when booting to TWRP recovery until the screen timeout kicks in. After that pressing any button will show the screen. As a work around setting the timeout to 15 secs will shorten the wait.
TWRP-3.0.2-1-T805/T807(ATT or Verizon not supported)
twrp_3.0.3-1_sm-t800_10217
twrp_3.0.3-1_sm-t805_10217
FLASH WITH ODIN OR FLASHFIRE OR EXTRACT THE RECOVERY.IMG AND FLASH WITH TWRP
NOTE: It is important to boot to recovery after flashing with Odin or twrp may not stick and will be replaced with stock recovery.
When flashing uncheck auto reboot in Odin, immediately after flashing manually reboot and boot into twrp.
Manual reboot is POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FEEDBACK IS APPRECIATED PLEASE
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
gcappa said:
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
Click to expand...
Click to collapse
As long the bootloader is unlocked, and if someone has an stock recovery pulled from it, then he could be twrp for it
Bootloader is unlocked. But I already flashed a modified cwm which doesn't work too well. So not sure if I could pull the stock recovery unless I reflash the stock rom.
gcappa said:
Bootloader is unlocked. But I already flashed a modified cwm which doesn't work too well. So not sure if I could pull the stock recovery unless I reflash the stock rom.
Click to expand...
Click to collapse
If you have the firmware downloaded just right click on the md5 and open it with 7zip or Winrar, then simply just drag the recover IMG to your desktop and send it here(or link to download). I'm not going to go to much in depth as I don't want this thread to be filled with non related to twrp stuff. I'm also unsure if he has time but ash is one good recovery builder
Ok, I'll do all that when I get home and upload a link.
gcappa said:
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
Click to expand...
Click to collapse
Should be possible as long as the right files are available. This is a snapdragon 805 device?
Seeing as I don't have this device you would have to test the builds and I would need some info from the device. Might take a few builds to get a proper working one.
I take it you are currently rooted? Also could you send me a link to the version of cwm you are using?
gcappa said:
Ok, I'll do all that when I get home and upload a link.
Click to expand...
Click to collapse
Is the sm-n9100 the Chinese version Note 4 Duos?
The TWRP recovery below is for this version, please test:
twrp-2860-n1900
Stock Recovery:
Stock-recovery-n1900
Note: You take responsibility for testing this.
Failed to flash on my T-800.
dwarfer66 said:
Failed to flash on my T-800.
Click to expand...
Click to collapse
What failed to flash? It's made for the t800. It flashes fine on a t805. No one else has had any issues. What is the full version of your device?
ashyx said:
Unofficial version of the latest TWRP, don't think it's been released yet.
Found it by accident for another device, so have rebuilt it for the Tab S Exynos version only.
TWRP-2.8.6.1
Click to expand...
Click to collapse
Thank again ashy this is awesome, keep up the good work.
Confirmed its working T800 5.0.2
ashyx said:
What failed to flash? It's made for the t800. It flashes fine on a t805. No one else has had any issues. What is the full version of your device?
Click to expand...
Click to collapse
This unofficial TWRP fails to flash, just says failed when trying to install.
dwarfer66 said:
This unofficial TWRP fails to flash, just says failed when trying to install.
Click to expand...
Click to collapse
Again, you need to confirm what your exact model is and build number. As you can see from the post above it flashes fine on a T800.
Post a screenshot of the issue with Odin.
It's flashing for me ok on my T800 with IronRom 2.0. Only thing is the root ain't working. Or do I need to unselect auto-reboot and do a forced shutdown? And clear cache and reboot?
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
edit: reflashed IronRom 2.0 to fix cache issue. After the cache wipe it boots up
edit2: it appears to be rooted but it ain't working. But when an app should ask for root permissions the app goes black screen. For Titanium backup it just hangs on checking
RDDraco said:
It's flashing for me ok on my T800 with IronRom 2.0. Only thing is the root ain't working. Or do I need to unselect auto-reboot and do a forced shutdown? And clear cache and reboot?
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
edit: reflashed IronRom 2.0 to fix cache issue. After the cache wipe it boots up
edit2: it appears to be rooted but it ain't working. But when an app should ask for root permissions the app goes black screen. For Titanium backup it just hangs on checking
Click to expand...
Click to collapse
Did you update the supersu app as requested? You need to post a screenshot of root validator so I can see the status of root.
You may just need to select full unroot from settings in the supersu app then boot into twrp and run the root process again or flash the supersu2.46 zip.
Also regarding wiping cache, it can sometimes take longer depending on what's in cache at the time. It may seem like it's hung but eventually completes. On occasion I've seen it take up to a few minutes to wipe.
Just saying that root is broken on custom roms such as iron rom. It's an known issue with touchwiz lollipop roms.
-DUHA
So it's a Rom issue?
What's the actual problem?
Isn't the Rom already rooted, unusual for a custom Rom to not be prerooted?
Guess that explains why it wasn't working. (Tkkg1994 managed to get IronRom working with root in v2.0.5) so its fine for me now.
RDDraco said:
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
Click to expand...
Click to collapse
Looked into this issue and have fixed it. Wipe Cache should work now.
ashyx said:
Unofficial version of the latest TWRP, don't think it's been released yet.
Found it by accident for another device, so have rebuilt it for the Tab S Exynos version only.
TWRP-2.8.6.1
NOTE: If after using TWRP to root you don't see the notification to update Supersu, just install the latest Supersu app from Play. Check root status with Root Validator
Supersu
Root validator
Click to expand...
Click to collapse
Just today, I rooted my new Tab S (SM-T800) AFTER allowing it to OTA update to Android 5.0.2. After that, I used Odin to flash the latest version of CWM I could find for this device, and that trashed recovery altogether. Couldn't get into recovery at all. So I used Odin again to flash TWRP 2.8.6.0 and had recovery back, BUT I kept getting notifications that SuperSU needed to be updated. What I did then was flash "BETA-SuperSU-v2.48.zip", and that resolved the "update needed" problem, and all seems to be working smoothly now. :good:
I'm running stock Touchwiz Lollipop 5.0.2 . Haven't tried changing ROM's, but don't really have a desire to do that just yet.
Unofficial release -TWRP recovery for the Galaxy J3 Emerge - SM-J327P, Qualcomm MSM8937
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Update 15/3/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.0-1_j327p_14317
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers @Doctur, @infixremix, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
.
Reserved
Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro
Doctur said:
Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro
Click to expand...
Click to collapse
Thanks for the heads up with the other member and your support. I'll report it.
@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it
JUSMEJOSE said:
@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it
Click to expand...
Click to collapse
No sorry i don't own this device.
@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
View attachment 4081849
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Sent from my Nexus 5X using XDA-Developers Legacy app
rekids said:
@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Click to expand...
Click to collapse
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.
Thank you so much ?, will let you know how it goes.
Sent from my Nexus 5X using XDA-Developers Legacy app
I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?
joeyjojojjjjjj said:
I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?
Click to expand...
Click to collapse
Pin request? Never heard of that before. Have you set a pin/password on your device?
Nevermind, my daughter pit an unlock pin on it. Got it now going to try this.
Everything went smooth! Thank you so much!
rekids said:
Everything went smooth! Thank you so much!
Click to expand...
Click to collapse
Thanks for the click, out of 141 downloaders only 3 were clickers.
I find it amsusing that the author of the thread below using stolen files from this one has just as many clicks.
https://forum.xda-developers.com/an...-j3-emerge-t3573551/post71443474#post71443474
.
No problems at all... Everything went perfect!
I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?
Cyclic said:
I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?
Click to expand...
Click to collapse
Yes I'd advise disabling Knox.
need help!!!!
ashyx said:
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.
Click to expand...
Click to collapse
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS
pumkinhead13 said:
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS
Click to expand...
Click to collapse
There's no way the patch did that. You must have wiped the system partition in twrp.
https://www.androidfilehost.com/?fid=817550096634755921
ashyx said:
There's no way the patch did that. You must have wiped the system partition in twrp.
Click to expand...
Click to collapse
uuuh no, so I did all the above said to do and everything was fine, it booted up (before i flashed the patch) then I went back into recovery, flashed the patch and selected "boot to system" it booted to samsung logo then at the top in small yellow writing just said "kernal" it sat there for 15 mins, before i pulled the battery, then flashed again....this time upon finish it stated "NO OS"
Red Wolf Recovery Project
Red Wolf Recovery is custom recovery based on the TWRP source code with it's own unique features. And one of these features is also support of the MIUI Incremental OTA's! However this thing is slightly more complicated then just downloading of the zip and flashing.. You have to first enable some things for this and flash some another ZIP file etc. So that's reason why i think that it would be nice to create a guide for this. Now let's look at it...
Pre-requisite
Redmi Note 3 - Snapdragon version!
Common sense
Steps
Download latest build of the recovery from here. And correctly follow the installation process.
After the correct installation reboot your device in to the recovery.
Now click on the "Advanced" and then on "Special Actions".
Here enable these checkboxes:
"Support MIUI Incremental OTA" and "Include System in OTA Survival".
Now clean/dirty flash some full MIUI ROM and flash whatever you want after that.
Now reboot your device in to the system.
When you get some update just download it using updater app and let it automatically reboot in to the RedWolf
Now everything is done! RedWolf will automatically install it and reboot back to the system!
After that you don't have to flash full ROM anymore.. Just always wait for the update from updater app and let it automatically reboot in to the RedWolf.
Now you can flash SuperSU or Magisk and incremental OTA's without any hustles. Use the built-in SuperSU/Magisk option for rooting your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Frequently Asked Questions
Q. I am getting Error 7 while flashing incremental OTA?
Ans: If you are really sure that you followed the installation process correctly then send us a log or screenshot and we will look at it.
Q. Can I install xposed, Viper, blah blah..?
Ans: Yes! You can install anything but make sure that you use this recovery for flashing the zip files.
Q.This recovery can be used in any ROM?
Ans: Yes! You can use this recovery in any ROM.
ATG Droid said:
Red Wolf Recovery Project
Red Wolf Recovery is custom recovery based on the TWRP source code with it's own unique features. And one of these features is also support of the MIUI Incremental OTA's! However this thing is slightly more complicated then just downloading of the zip and flashing.. You have to first enable some things for this and flash some another ZIP file etc. So that's reason why i think that it would be nice to create a guide for this. Now let's look at it...
Pre-requisite
Redmi Note 3 - Snapdragon version!
Common sense
Steps
Download latest build of the recovery from here. And correctly follow the installation process.
After the correct installation reboot your device in to the recovery.
Now click on the "Advanced" and then on "Special Actions".
Here enable these checkboxes:
"Support MIUI Incremental OTA" and "Include System in OTA Survival".
Now clean/dirty flash some full MIUI ROM and flash whatever you want after that.
Now reboot your device in to the system.
When you get some update just download it using updater app and let it automatically reboot in to the RedWolf
Now everything is done! RedWolf will automatically install it and reboot back to the system!
[SIZE="3! You can use this recovery in any ROM.
Click to expand...
Click to collapse
Its much better than ZCX since once zcx is replaced by official twrp then it requires full wipe so keep up the good job.
What is different from zcx twrp
Sent from my Redmi Note 3 using Tapatalk
Androbots said:
Its much better than ZCX since once zcx is replaced by official twrp then it requires full wipe so keep up the good job.
Click to expand...
Click to collapse
Can I flash this on 2gb ram variant?
lordsh said:
What is different from zcx twrp
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Look at the thread in the development section.. Here is the feature list. Anyway the main difference here is that RedWolf is based on the latest TWRP base and it also support AOSP 8.0.0 based ROMs
rohan_45 said:
Can I flash this on 2gb ram variant?
Click to expand...
Click to collapse
Yup
In ZCX the system img file (size more than 1 gb) is stored in sdcard. Do RedWolf also stores the system img file in sdcard ? (for incremental ota updates)
What if i edit build.prop...will i still be able to update incremental updates??
is that really ota update working on it??anyone tested??
umang0712 said:
What if i edit build.prop...will i still be able to update incremental updates??
Click to expand...
Click to collapse
Depends on what will you edit.
I can't save my custom settings, like reverse nav bar, system time etc. It is auto defaulted after every reboot. How can I save them?
Awesome recovery looks great, but I will downgrade to ZCX until the "bad app" checking is fixed.
Thanks.
M RN3 got bootloop . its not booting only mi logo showing what to do pls help fast as it is not my phone !! Its my fathers pls help guys. The device was running miui 8 marshmallow one. I did flashed correctly twrp also boot up but then I selected reboot to system from within twrp and it doesn't boot to system . What to do pls help. No offence to the twrp recovery developer but I need help pls ? Guys
kg hggggg tightly said:
M RN3 got bootloop . its not booting only mi logo showing what to do pls help fast as it is not my phone !! Its my fathers pls help guys. The device was running miui 8 marshmallow one. I did flashed correctly twrp also boot up but then I selected reboot to system from within twrp and it doesn't boot to system . What to do pls help. No offence to the twrp recovery developer but I need help pls ? Guys
Click to expand...
Click to collapse
Dude I got the same problem, download lazyflasher zip file ,flash it through twrp ,and reboot,it worked for me
dudemathai said:
Dude I got the same problem, download lazyflasher zip file ,flash it through twrp ,and reboot,it worked for me
Click to expand...
Click to collapse
Ya i understood so that means that if i want to flash custom rom will i need to flash lazyflasher whenever i flash a custom rom?
kg hggggg tightly said:
Ya i understood so that means that if i want to flash custom rom will i need to flash lazyflasher whenever i flash a custom rom?
Click to expand...
Click to collapse
I don't think you need to flash it when you change roms,what I know is that lazyflasher bypasses miui so that you won't be stuck in bootloop while you flash anything into miui
otyg said:
Awesome recovery looks great, but I will downgrade to ZCX until the "bad app" checking is fixed.
Thanks.
Click to expand...
Click to collapse
What problem are you facing? This recovery seems better and updated than ZCX.
Sent from my Redmi Note 3
can i use magisk with this?
rs168 said:
can i use magisk with this?
Click to expand...
Click to collapse
Yes
is this support with newest miui 9..?
xerocracker said:
is this support with newest miui 9..?
Click to expand...
Click to collapse
Yes
Sent from my Redmi Note 3 using XDA Labs
Unofficial release -TWRP recovery for the Galaxy J3 2017 - SM-J330F/FN/FZ/G/DS EXYNOS 7570
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.3.1-0 Released
May 22, 2019
TWRP 3.3.1-0 is out now for most currently supported devices.
What's new in 3.3.1-0:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance
UPDATE 10/8/2019
TWRP 3.3.1-1 OO/PP build released
Current status: Beta
Update 15/9/2018
TWRP 3.2.3-1 OO build released.
Current status: Stable
Update 27/1/2018
TWRP 3.2.1-1NN build released
Current status: Stable
Update 23/11/2017
TWRP 3.1.1-1 NN build released.
Current status: Stable
Features:
TOUCHSCREEN working
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.[/B]
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
2. Uncheck Auto reboot. (NOT REQUIRED FOR INSTALLING TWRP 3.3.1-1)
3. Load the respective file below into the AP slot and hit start.
4. After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME. (NOT REQUIRED FOR INSTALLING TWRP 3.3.1-1, THE DEVICE WILL AUTO BOOT TO RECOVERY)
5. Flash the V3 RMM bypass zip
https://forum.xda-developers.com/showpost.php?p=79745844&postcount=627
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT AND BECOMING RMM LOCKED FOR 7 DAYS.
I ALSO SUGGEST BACKING UP ANYTHING YOU NEED ON INTERNAL STORAGE. AT SOME POINT YOU MAY EXPERIENCE A 'VERIFICATION FAILED MESSAGE' .
THIS IS NORMAL, BUT WILL REQUIRE THE DATA PARTITION TO BE FORMATTED IN TWRP.
DOWNLOAD:
twrp_3.3.1-1_sm-j330x_13819
twrp_3.2.3-1_j330_13918
twrp_3.2.1-1_sm-j330f_270117
twrp_3.1.1-1_sm-j330f_231117
Nougat Root instructions:
Install latest Magisk release with TWRP:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption, disable dmverity and mount internal storage:
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install the boot image patch.
Boot image patch
no-verity-no-encrypt_ashyx
5. Install Magisk(if root is required)
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6. Reboot
OREO ONLY ROOT INSTRUCTIONS:
1. Install the Root patch kernel with TWRP.
J330F-FN_root_no_sim_patch
NOTE:This is a custom Oreo J330F/FN XXU3BRG3 permissive/enforcing kernel and patch built from source. It makes changes to the system partition also.
What does it do?:
*It installs a custom kernel to fix the no SIM issue when rooting.
*Patches the system to fix WIFI and Bluetooth not turning on when using custom kernels.
*Patches DM-Verity.
*Removes forced encryption and patches /data not able to be mounted (after formatting).
*Removes the SecurityLogAgent nag when using a custom kernel.
2. If you wish to mount /DATA for access to internal storage then FORMAT the /DATA partition.
3. To root install the latest Magisk below.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
PIE ONLY ROOT INSTRUCTIONS:
To root install latest Magisk below.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable encryption (mount DATA in TWRP) install the zip below with TWRP:
Disable_Dm-Verity_ForceEncrypt_Quota_08.02.2019
Finally FORMAT /DATA in TWRP.
Reboot.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my tester @lemlis, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
UPDATE: Touchscreen fixed
.
Arggghh i feel something goes wrong with my device intead of succesfull installation. Yes i can flash zip and make nandroid backup. But my device not running properly. I can't adjust screen brightness even camera not functioning. Now i'm waiting for full batery charge to flash stock rom & try to flash twrp once again
---------- Post added at 22:19 ---------- Previous post was at 22:16 ----------
Anual said:
Arggghh i feel something goes wrong with my device intead of succesfull installation. Yes i can flash zip and make nandroid backup. But my device not running properly. I can't adjust screen brightness even camera not functioning. Now i'm waiting for full batery charge to flash stock rom & try to flash twrp once again
Click to expand...
Click to collapse
Now my j330g working normally after i flash cf auto root without flashing stock rom. What's the problem??
Anual said:
Arggghh i feel something goes wrong with my device intead of succesfull installation. Yes i can flash zip and make nandroid backup. But my device not running properly. I can't adjust screen brightness even camera not functioning. Now i'm waiting for full batery charge to flash stock rom & try to flash twrp once again
---------- Post added at 22:19 ---------- Previous post was at 22:16 ----------
Now my j330g working normally after i flash cf auto root without flashing stock rom. What's the problem??
Click to expand...
Click to collapse
Probably the version of SuperSu you flashed.
ashyx said:
twrp_3.1.1-1_sm-j330f_231117
Click to expand...
Click to collapse
Thanks.now color in TWRP is blue.Only in screenshot yellow.backup CPEFS is 0 ? with changed recovery.fsab i have CPEFS 8MB
Works all good.
lemlis said:
Thanks.now color in TWRP is blue.Only in screenshot yellow.backup CPEFS is 0 ? with changed recovery.fsab i have CPEFS 8MB
Works all good.
View attachment 4340464View attachment 4340476
Click to expand...
Click to collapse
Seems I didn't include my updated FSTAB in the new build. Corrected, thanks for pointing it out.
ashyx said:
Probably the version of SuperSu you flashed.
Click to expand...
Click to collapse
Yeaa you right..i use super su which remain in my memory card almost 2 years ago ???
Sorry for this offtopic but can anyone post a link of latest firmware for J330G/DS, which doesn't want to grab my money for Fast download speed please? I want to try this recovery but still afraid if something bad happens. Thanks in advance!
@ashyx, thank you so much for this recovery sir! I've been waiting for a recovery for this phone for so long and now it's here! you managed to create this recovery for this phone even without one! I'm impressed sir!
BlackDragonz said:
Sorry for this offtopic but can anyone post a link of latest firmware for J330G/DS, which doesn't want to grab my money for Fast download speed please? I want to try this recovery but still afraid if something bad happens. Thanks in advance!
@ashyx, thank you so much for this recovery sir! I've been waiting for a recovery for this phone for so long and now it's here! you managed to create this recovery for this phone even without one! I'm impressed sir!
Click to expand...
Click to collapse
updato.com
i cant flash super su twrp didn't show the file to flash
File to flash have to be on sd card ?
Help Me
azhar960225 said:
Help Me
Click to expand...
Click to collapse
Police. Fire or ambulance?
I Want root j3 pro 2017..but how
azhar960225 said:
I Want root j3 pro 2017..but how
Click to expand...
Click to collapse
Flash SuperSU or Magisk.
How? To Flash How? Cannot root j3 How to Flash?
7.11 Android...
arabarabow said:
twrp didn't show the file to flash
Click to expand...
Click to collapse
put zip file inside any folder.File to flash have to be in folder
Just done flashing latest build and flashed magisk, all are running fine. Tysm @ashyx !
can anyone help me telephone stuck on logo and i cant do nothing even reboot to twrp @ashyx
arabarabow said:
can anyone help me telephone stuck on logo and i cant do nothing even reboot to twrp @ashyx
Click to expand...
Click to collapse
Boot to TWRP and flash Supersu or Magisk. Use the three button combo.
Can i just use cf auto root to root my phone without installing a recovery? Or it's better to root using this method?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ANNOUNCEMENTHey everyone,
We are starting to push the incremental roll-out of OxygenOS version 10.0.1 for the OnePlus 5/T devices.
Changelog:
Code:
[B]System:[/B]
• Fixed the abnormal call recording issue
• Fixed the de-activated alarm issue when the phone was powered off
• Updated Android Security Patch to 2020.09
• Updated GMS package to 2020.08
[B]Full Screen Gestures:[/B]
• Back gesture from the bottom of the screen is available (OP5T only)
[B]Camera:[/B]
• Electronic Image Stabilization has been added, bringing you the more stable shooting experience
Explore what's new on Android 10 here.
Notes:
• If you don't have the Community app installed on your device, feel free to download it from here. You can check here for more information on the integrated Feedback tool. Make sure to let us know how you feel about the build here in the thread too, we look forward to reading your feedback.
• Click here to find out how to take logs on OxygenOS.
Warning: Please remove your existing screen lock/pin/pattern/password and set it to swipe before starting the update process.
DOWNLOADS
Full ROM Zips:
• OxygenOS 10.0.1: Official Link | AndroidFileHost Mirror | Google Drive Mirror
• MD5: 242e3a4021f0b37c513ac4be935fbea0
Custom Recoveries:
• TWRP by mauronofrio: Official Link
• TWRP by poad42: Official Link
• blu_spark TWRP by eng.stk: Official Link
• Official TWRP by Dees_Troy: Official Link
Root:
• Magisk: Official Link
Warning: Do not flash partial update OTAs (under 1 GB) on a modified/rooted device! If you want to use partial OTAs, you must first flash the full OxygenOS zip that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing a full zip in recovery.
FLASHING INSTRUCTIONS
Download the necessary files from the section above and follow the steps below:
Note: Dirty flashing is fine if you are running an old OxygenOS version or a ROM based on OxygenOS. If you are, however, coming from a Custom ROM, you must clean flash.
For Non-Rooted Users with a Locked Bootloader and Stock Recovery:
Download the full zip/incremental OTA from the downloads section above and place it in the root of your internal memory
Reboot to stock recovery > Shutdown device > Press Volume Down + Power buttons together
Select language > Install menu > Install from internal > Select the full zip > Flash
After a successful flash > Wipe cache
Reboot
Note: First boot may take some time, so please be patient and wait for it to boot.
[Dirty Flash] For Users with an Unlocked Bootloader and TWRP Recovery coming from H2OS/OOS:
Download the full ROM zip from the downloads section above
Transfer the zip to the root of your device's internal storage
Only needed if you are using a TWRP that does not ignore the compatibility.zip check: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
Reboot to TWRP and take a nandroid backup of your existing ROM
Flash Magisk Uninstaller (recommended)
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
From the TWRP menu, Install > Select full ROM zip > Swipe to flash
Flash the latest stable Magisk in case you want to root
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
If you were decrypted earlier, flash xXx No Verity 4.0.zip from here
Reboot
Note: First boot may take some time, so please be patient and wait for it to boot.
Warning: Dirty flashing (update) can be risky! Remember that if you face issues after dirty flashing, you will have to clean flash.
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
Download the full ROM zip from the downloads section above
Transfer the zip to the root of your device's internal storage
Only needed if you are using a TWRP that does not ignore the compatibility.zip check: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
Reboot to TWRP and take a nandroid backup of your existing ROM
Flash Magisk Uninstaller (recommended)
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
Flash the latest stable Magisk in case you want to root
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash xXx No Verity 4.0.zip from here
Reboot
Note: First boot may take some time, so please be patient and wait for it to boot.
Never Settle.
XDA:DevDB Information
[OFFICIAL] OxygenOS Stable for OnePlus 5T (dumpling), ROM for the OnePlus 5T
Contributors
Funk Wizard, shadowstep, Some_Random_Username
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2018-10-08
Last Updated 2020-11-20
Download Section moved to OP and Thread now maintained by:
Thread Contributors:
@shadowstep
@Funk Wizard
Flashing Instructions moved to OP and thread now maintained by:
Thread Contributors:
@shadowstep
@Funk Wizard
Thanks, works. Am unlocked and with TWRP installed. Had to use this method.
mad-murdock said:
Thanks, works. Am unlocked and with TWRP installed. Had to use this method.
Click to expand...
Click to collapse
Woh ... Sup buddy, Glad to greet you here with 5T. I still remember and appreciate your contribution over the the 3/3T unified TWRP thread. Thank you once again for your active contribution and support towards oneplus devices and i hope to see you around :highfive:
Funk Wizard said:
Woh ... Sup buddy, Glad to greet you here with 5T. I still remember and appreciate your contribution over the the 3/3T unified TWRP thread. Thank you once again for your active contribution and support towards oneplus devices and i hope to see you around :highfive:
Click to expand...
Click to collapse
Hey mate, nice you remember me. With a new OnePlus device at my hands I sure stay around for a month or two before I lose interest in Forums once again.
TWRP updated to unofficial 3.2.0-0 on the OP and tested working fine :good:
Sent from my OnePlus5T using XDA Labs
Is F2FS supported? My phone stucks into boot screen for a while now. Thanks
Edit: changed to ext4 and it's working now...
Funk Wizard said:
TWRP updated to unofficial 3.2.0-0 on the OP and tested working fine :good:
Click to expand...
Click to collapse
Same issue here as with other TWRP versions, no idea why...
Pfeffernuss said:
Same issue here as with other TWRP versions, no idea why...
Click to expand...
Click to collapse
No issues with any twrp version here
Sent from my OnePlus5T using XDA Labs
Pfeffernuss said:
Same issue here as with other TWRP versions, no idea why...
Click to expand...
Click to collapse
I have the same issues with all TWRP but opposite, it happens when I do a restore from backup, issue never resolved
Pfeffernuss said:
Same issue here as with other TWRP versions, no idea why...
Click to expand...
Click to collapse
Try deleting all backups > Reboot Recovery > Try again
I just tested again and it backed up all fine
Sent from my OnePlus5T using XDA Labs
Bradl79 said:
I have the same issues with all TWRP but opposite, it happens when I do a restore from backup, issue never resolved
Click to expand...
Click to collapse
Same here, restoring also fails :good: Will have to wait for an official TWRP I guess :good:
Funk Wizard said:
Try deleting all backups > Reboot Recovery > Try again
I just tested again and it backed up all fine
Click to expand...
Click to collapse
Gonna try this as well then, thanks :good:
Today announcet 4.7.4 oos any of you already got it [emoji56]
Verstuurd vanaf mijn ONEPLUS A5010 met Tapatalk
OxygenOS 4.7.4 OTA for the OnePlus 5T is out!
Source : https://forums.oneplus.net/threads/oxygenos-4-7-4-ota-for-the-oneplus-5t.709071/
Changelog :
Camera :
Optimized UI of Camera
Improvements for photo quality
System :
Optimizations for audio from speaker and earphones
Optimizations for face unlock
Optimizations for vibration
Wi-Fi battery usage optimization
Improved stability of fingerprint and GPS
General bug fixes and system stability improvements
otafsg.h2os.com/patch/amazone2/GLO/OnePlus5TOxygen/OnePlus5TOxygen_43.O.06_GLO_006_1712062242/OnePlus5TOxygen_43_OTA_006_all_1712062242_0ee65.zip
http://otafsg.h2os.com/patch/amazon...s5TOxygen_43_OTA_006_all_1712062242_0ee65.zip
here is the full ota link i captured via matlog
Thread Updated to OOS 4.7.4 With Download Links on the OP
I have the 4.7.2 stock ROM but rooted. Can i dirty flash it without wiping my data and system?
appileh said:
I have the 4.7.2 stock ROM but rooted. Can i dirty flash it without wiping my data and system?
Click to expand...
Click to collapse
Yes you can.