Database Develop

TWRP 3.2.3-1 for Pixel Devices

TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set

How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.

Amazing work sir! I think this is what we've all been waiting for! I mean I know I've been checking here frequently, hoping for this

Wow and so it begins, great work thanks!

Thanks
Sent from my Pixel using XDA-Developers mobile app

has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well

Dees_Troy said:
Note: I am going to be very busy the next couple of weeks. I probably won't be able to answer your questions or fix things immediately.
Click to expand...
Click to collapse
the pixel installer.zip is corrupt. :crying:

Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.

GeekMcLeod said:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
Click to expand...
Click to collapse
Do you happen to have a copy of the .zip? All the ones I download are corrupt...

zaksimmermon said:
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
Click to expand...
Click to collapse
No I haven't downloaded anything yet. Not going to until I can have supersu alongside twrp.

Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.

Snowby123 said:
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Click to expand...
Click to collapse
"In other words, Chainfire's systemless root method modifies the same binary that TWRP needs to modify in order to get data decryption working. Therefore, when you flash TWRP you are overwriting the changes made to the init binary by Chainfire's systemless root method. While this is a minor setback, thanks to the dual partition nature of the Pixel (and future devices shipping with Nougat), TWRP has some nifty new capabilities."
I'm pretty sure he's just saying dont chance something going wrong like it bootlooping or wiping data if you need your phone for something important like a phone call. Tough to answer said phonecall in a boot loop.

zaksimmermon said:
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Click to expand...
Click to collapse
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.

rtthane said:
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
Click to expand...
Click to collapse
I finally got passed that issue. I had to flash factory images and erase everything to the point of being at setup screen. I didn't set anything up, no network or wifi, skipped Google sign in, no password and also no Google functions activated. This led to an unencrypted setup, so after turning on dev settings and Android debugging I booted up the image. Now my issue is the zip to install twrp for sailfish is corrupt and if you try to unzip it there are no files in it....I downloaded the marline zip and there are files when unzipped....

Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?

ne0ns4l4m4nder said:
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
Click to expand...
Click to collapse
Are you trying to fastboot flash or fastboot boot?
Sent from my Pixel using Tapatalk

Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.

fracman said:
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
Click to expand...
Click to collapse
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off

ej_424 said:
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
Click to expand...
Click to collapse
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????

BakedTator said:
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
Click to expand...
Click to collapse
OK thanks, wondering if root will work with November update or of I need to roll back first. Prior to SU update today Nov update didn't work with the auto cf root

Zuk Z2Pro Android 7 Version

Hi All,
Was finally able to get a hold of the Android 7 version for Zuk Z2pro, at this point it's in the development phase, looks pretty stable as of now, it's just been an hour since I installed it, Got it from the Chinese site ( Landlord ) a little tough to figure out the content on the site, but the ROM is in English.
I tried flashing it with the Stock Recovery but didn't work , went back to 2.3.044 and then flashed the TWRP ( Chinese Version ) Did a dirty flash, and all the sensors {Heart Rate, UV Sensor, Pedometer, Proximity, etc } seem to be working fine. The file is available in a Baidu link, and it takes a lot of time to download.
The ROM now supports themes but as of now i see only 4 inbuilt themes and no black themes. But inbuilt themes uses nice icons to make it look simple and neat. I shall post pics of the screens. Settings now show the lab features directly to play around with fake location( never got it working though ). As of now calls and Volte working fine. Haven't been successful in making video calls over LTE with Zui Roms.
Need some help in getting a cloud storage to upload the file.
If someone could help me, would be happy to upload it for the benefit of the community. Again ***** Please do install it at your own risk, make sure you backup in TWRP before you flash this ROM , the size is 1.6 GB. ***** All thanks to the Chinese forums BBS.lenovomobiles.

Screenshots
These are the screenshots
And you can download the file from :
https://drive.google.com/file/d/0B6GiX9_gwfCqVXVhRHcyVEdfbkU/view?usp=sharing
Make sure you backup in TWRP, Please use the Chinese version of the TWRP to flash this file,

More screenshots please ??

Some bugs ? Any way to go back to Android 6? After flashing this ROM TWRP still working?
Отправлено с моего Z2 Pro через Tapatalk

Bugs
raber111 said:
Some bugs ? Any way to go back to Android 6? After flashing this ROM TWRP still working?
Отправлено с моего Z2 Pro через Tapatalk
Click to expand...
Click to collapse
Following are the bugs I have noticed
1. Vibration stops working, a reboot will be needed
2. Manual mode in the Camera gives a red tint in faster shutter speeds
3. No Root, haven't been able to root it, maybe I am doing it wrong. Flashing the Superuser in TWRP makes the sim card go an undetected state.
4. No options to set a live wallpaper ( Google Pixel wallpaper with animation ). Figured out a way to fix it by using the app shortcut maker to set a shortcut for the live wallpaper picker.
5. Battery seems to be draining faster.
Will keep adding can't complain as it is a dev version.

anupsnair said:
Following are the bugs I have noticed
1. Vibration stops working, a reboot will be needed
2. Manual mode in the Camera gives a red tint in faster shutter speeds
3. No Root, haven't been able to root it, maybe I am doing it wrong. Flashing the Superuser in TWRP makes the sim card go an undetected state.
4. No options to set a live wallpaper ( Google Pixel wallpaper with animation ). Figured out a way to fix it by using the app shortcut maker to set a shortcut for the live wallpaper picker.
5. Battery seems to be draining faster.
Will keep adding can't complain as it is a dev version.
Click to expand...
Click to collapse
So TWRP still working after flashing?
Gapps working?
Отправлено с моего Z2 Pro через Tapatalk

I'm not able to flash it via chinese TWRP. I've also tried TWRP from Emmaus. If someone can share a working recovery with this ROM I'll tell you my opinion about it. (Error 7 is the problem).

raber111 said:
So TWRP still working after flashing?
Gapps working?
Отправлено с моего Z2 Pro через Tapatalk
Click to expand...
Click to collapse
TWRP works fine, just that I wasn't able to root it, Gapps not required, as I installed the Google sync app and the Google contacts previously on the 2.3.044 build since I did a dirty update, got the play store and the Google contacts in tact

cyBeRdUdE-9 said:
More screenshots please ??
Click to expand...
Click to collapse
Hi Cyberdude,
Is there any specific screen that u are looking for?

anupsnair said:
Hi Cyberdude,
Is there any specific screen that u are looking for?
Click to expand...
Click to collapse
Screens of any major UI changes ??

Hey I was on CM13 By Emmaus, did a TWRP backup.
Flashed the Chinese TWRP.
Wipe -> Flashed the Android 7 ZUI -> Used it for a day and wanted to go back to CM13.
I flashed the TWRP By Emmaus-> Restore-> Now the phone doesnt go past the ZUK logo with the blue LED light.
What do you think needs to be done to restore the TWRP backup and go back to CM13?
Edit: Solution: I had QFIL to 1.9 then flash Emmaus Recovery and restore.

Root Zuk Z2pro Android 7
Hi All,
For those who need to root this ROM, you can flash the following file from twrp it's a modified version of SU,

anupsnair said:
Hi All,
For those who need to root this ROM, you can flash the following file from twrp it's a modified version of SU,
Click to expand...
Click to collapse
I've flashed just the last version of SuperSu beta, no modify version needed in my option because is working like a charm!
Sent from my Z2 Pro using Tapatalk

lucaam said:
I've flashed just the last version of SuperSu beta, no modify version needed in my option because is working like a charm!
Sent from my Z2 Pro using Tapatalk
Click to expand...
Click to collapse
Thank you Lucaam, for the benefit of the forum can you please post a link, when I flashed SU, the sim in my phone stopped working.

Here's to you the link https://download.chainfire.eu/750/SuperSU/BETA-SuperSU-v2.64-20151220185127.zip?retrieve_file=1 of to the file that I've downloaded. I flashed it after the first full boot.
Sent from my Z2 Pro using Tapatalk

syedtahir16 said:
Hey I was on CM13 By Emmaus, did a TWRP backup.
Flashed the Chinese TWRP.
Wipe -> Flashed the Android 7 ZUI -> Used it for a day and wanted to go back to CM13.
I flashed the TWRP By Emmaus-> Restore-> Now the phone doesnt go past the ZUK logo with the blue LED light.
What do you think needs to be done to restore the TWRP backup and go back to CM13?
Edit: Solution: I had QFIL to 1.9 then flash Emmaus Recovery and restore.
Click to expand...
Click to collapse
hey dude, i had same problem, i couldn flash any rom through twrp, nor could i recover any backup.. then i saw your post, i could hardly flash 1.9 firmware, but even then, and even with locked or unlocked bootloader, i could neither update through official firmware update process (OTA) nor could i flash anything through any recovery, it stucks on updating/flashing system image unconditionaly.. so something strange happens when flashing 7.0, so you cannot go back anyway. May you could help. Its just so anoying that i cant restore my backups, cant install any custom rom, official rom, only qfil works but dont solves any problem.
thanks in advance
Ikram

ikram.senguen said:
hey dude, i had same problem, i couldn flash any rom through twrp, nor could i recover any backup.. then i saw your post, i could hardly flash 1.9 firmware, but even then, and even with locked or unlocked bootloader, i could neither update through official firmware update process (OTA) nor could i flash anything through any recovery, it stucks on updating/flashing system image unconditionaly.. so something strange happens when flashing 7.0, so you cannot go back anyway. May you could help. Its just so anoying that i cant restore my backups, cant install any custom rom, official rom, only qfil works but dont solves any problem.
thanks in advance
Ikram
Click to expand...
Click to collapse
I"m not certain about other backups. But I had a CM13 TWRP backup.
What I did was:
QFIL to 1.9. This should work irrespective of what recovery you have. This is like an absolute reset. Once this is done, let your phone reboot and load once.
Then adb reboot bootloader
In the bootloader mode -> Flash the recovery ( You will need to flash Emmaus recovery if you are going back to CM13).
Once flashed. You can wipe the data,system and cache. Install CM13 and you should be all set.
You could also wipe and restore any old CM13 Backup too. Hope this helps.

SOLVED
SOLVED: HOW? STRANGE!
i did everything exact same as at home, but somehow ..just somehow ..it didnt ****ed itself and didnt stuck on everywhere and indeed succeeded flashing every f****** rom!
so here a step-by-step (if some ever expirience same) thanks to you all which i can confirm:
1. flash 1.9.104 rom through qfil (let it boot..)
2. enable usb debuging through enabled developer settings
3. boot in fastboot (adb reboot bootloader) unlock bootloader with your unlock_bootloader.img (fastboot -i 0x2b4c flash unlock unlock_bootloader.img) right after that unlock it (fastboot -i 0x2b4c oem unlock-go) forreal
4. reboot, then enable usb debuging again and boot in fastboot again (adb reboot bootloader)
5. flash emmaus TWRP (fastboot flash recovery recovery.img) DO !NOT! USE ---> [fastboot -i 0x2b4c boot recovery.img] <--- CODE!
6. boot to TWRP, wipe data/cache/dalvik-cache (system not needed, better dont wipe system to be sure)
7. flash AICP, RR or CM13 .zip, NOT ANY OTHER (https://emmaus.pro/?dir=Zuk Z2 Pro & http://forum.xda-developers.com/zuk-z2-pro/development/rom-aicp-11-0-mm-6-0-1-unofficials-t3499283) those work for sure on emmaus TWRP
8. reboot, DONE
to every single zuk z2 pro user out there, please make sure your PC, USB PORT, USB-CABLE is working right, because even if everything seems right, under the hook its sometimes not. In my case, i knew it, but could not believe it since qfil showed me SUCCSESS in every section, the connection betweet cable and usb port was faulty, thats the only possibility. THANK YOU ALL VERY MUCH, this was one of the most HARD-BRIKS ive ever experienced, and ive been through S2, S3, S4, S5, S6, HTC ONE M7 hard-bricks.. so.. yeah!!! THANK YOU VERY MUCH :')

i try this zip on my twrp , but my phone are dead don't run anybody else
what i can do ?

Many thanks to you ! the flash worked very well. i had same issues here . best description ever many many thanks !!

[ROOT] J7 prime - CF AUTO ROOT [ SM-G610F - SM-G610M]

Here we have root for stock rom Thanks to the Chainfire Team.
Everything done by them so all thanks and credits are for them
Download
https://download.chainfire.eu/1036/CF-Root/CF-Auto-Root/CF-Auto-Root-on7xelte-on7xeltedd-smg610f.zip
Installation
-Enable USB debugging and OEM unlocking in the settings
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue
-Flash the CF-Auto-Root package as AP in ODIN(Comes within the zip file), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
I tested it on my device and it worked normally
I will not be responsible for any damage to your device, but following the steps will normally work normally
I just tested with ROM stock 6.0.1 with security patch from 1 July 2017
.

Hayleyw2 said:
Here we have root for stock rom Thanks to the Chainfire Team.
Everything done by them so all thanks and credits are for them
Download
https://download.chainfire.eu/1036/CF-Root/CF-Auto-Root/CF-Auto-Root-on7xelte-on7xeltedd-smg610f.zip
Installation
-Enable USB debugging and OEM unlocking in the settings
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue
-Flash the CF-Auto-Root package as AP in ODIN(Comes within the zip file), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
I tested it on my device and it worked normally
I will not be responsible for any damage to your device, but following the steps will normally work normally
I just tested with ROM stock 6.0.1 with security patch from 1 July 2017
.
Click to expand...
Click to collapse
Hi will it work for version 7.0 also

it's working fine for me
i have "G610FDDU1BRF2" with android version 7.0 and it gets installed successfully
thanks

How to change Supersu with Magisk?

Razortm said:
it's working fine for me
i have "G610FDDU1BRF2" with android version 7.0 and it gets installed successfully
thanks
Click to expand...
Click to collapse
How to restore stock recovery

Ryan.XM said:
How to restore stock recovery
Click to expand...
Click to collapse
Flash the cf auto root and it will automatically change your recovery into stock.

bjpp21 said:
Flash the cf auto root and it will automatically change your recovery into stock.
Click to expand...
Click to collapse
Ok thanks

I have J7 prime [SM-G610F] with stock andriod 8.1, samsung experience 9.5 and 1 November 2018 security patch will it still work?

I don't think so. I think the J7 with 8.1 is impossible to root? I can't seem to find an answer on this.

lordbaal19 said:
i don't think so. I think the j7 with 8.1 is impossible to root? I can't seem to find an answer on this.
Click to expand...
Click to collapse
its not impossible to root j7 on oreo..just search here in xda and you will find the impossible is really possible.

Well the TWRP thread has no real answers and this method doesn't work either.

I have done it
LordBaal19 said:
Well the TWRP thread has no real answers and this method doesn't work either.
Click to expand...
Click to collapse
yes, I have made root in my SM-G610m with Android 8.1 and it was with TWRP, and I have learned it from YouTube and in Spanish language.
For now I do not have available Super User. I think this post will work for me

ernestoi said:
yes, I have made root in my SM-G610m with Android 8.1 and it was with TWRP, and I have learned it from YouTube and in Spanish language.
For now I do not have available Super User. I think this post will work for me
Click to expand...
Click to collapse
Found a way:
LordBaal19 said:
Which one do you recommend? At which point do I have to install it and then I don't need to install no-verity-opt-encrypt-6.0?
EDIT: I think I finally got it. I did it like this:
1. Ok, so the phone as a fresh 8.1.0 system (just flashed the 7.0 and then it updated OTA in a matter of minutes). I enter the phone, enable the developer mode, enable OEM Unlocking and USB Debug.
2. Then I put the phone on download mode, flash the TWRP recovery disabling the auto-reboot on Odin so it doesn't boot to system automatically. This seem important since otherwise the recovery goes back to stock.
3. Then, to get out of download mode I press vol. down and power keys at the same time and the phone turn off. Then I turn on the phone into recovery mode, once in there I swipe into write mode and go to Wipe and select Format Data, type down yes and it says it's done. I go back to TWRP main menu.
4. I connect the cellphone to the PC and in storage I select Mount USB. Then drag the Magisk-v18.0.zip file into the storage that pops up on Windows. Then I saftely remove the device in Windows and go back to the main TWRP menu on the phone. I select Install and install the .zip file without selecting Signature verification or Reboot after is complete. It says is done installing and no errors seems to occur. I employ the button to wipe Cache and Dalvik.
5. I go back again o Wipe and select Format Data, type down yes and it says it's done, again.
5. Then I try to reboot to System, and choose to Do Not Install the TWRP app, and... SUCCESS!! The phone starts again, I config everything and then Magisk is there in the apps. I tried with an app that requires SU and it works!
Thanks for the help.
Click to expand...
Click to collapse
For the files and details check the OP on that thread.

LordBaal19 said:
Found a way:
For the files and details check the OP on that thread.
Click to expand...
Click to collapse
That's the way I have done it. But if you go on Z3X, select the device (SM-G610M), and you perform some activity like repair IMEI, Z3X detects the root, but it does not detect the Super User.

Help request - Custom ROM (phone unlocked/rooted) but stuck in boot animation

I've been sitting around on post-surgery "bedrest" and for whatever reason decided to install a different 7.x ROM using trusty TWRP to try something new. However, I'm stumped as to why no matter what ROM I use I get a successful installation message, but infinite boot animation.
I was running AOKP 7.x and it was stable and happy, and that installation went uneventful.
I've run down a list of possible remedies, like clearing cache, installing GAPPs in order first (no good), after LOS ROM .zip (no good), tried reinstalling AOKP (no good)....
I did make a backup of my phone via TWRP in case of an issue, but even reinstalling the backup did no good. It would load successfully, but upon restart... constant boot animation.
I wiped the SSD clean and tried a fresh install, and according to TWRP it was a success, but I've been watching the LOS boot animation for two hours now.
cRDroid sat in the boot loop all night... a full charge... no joke.
So what are my next steps for getting a working phone? I don't care what ROM I use really... I liked AOKP and just wanted to try something new.

Charlie207 said:
I've been sitting around on post-surgery "bedrest" and for whatever reason decided to install a different 7.x ROM using trusty TWRP to try something new. However, I'm stumped as to why no matter what ROM I use I get a successful installation message, but infinite boot animation.
I was running AOKP 7.x and it was stable and happy, and that installation went uneventful.
I've run down a list of possible remedies, like clearing cache, installing GAPPs in order first (no good), after LOS ROM .zip (no good), tried reinstalling AOKP (no good)....
I did make a backup of my phone via TWRP in case of an issue, but even reinstalling the backup did no good. It would load successfully, but upon restart... constant boot animation.
I wiped the SSD clean and tried a fresh install, and according to TWRP it was a success, but I've been watching the LOS boot animation for two hours now.
cRDroid sat in the boot loop all night... a full charge... no joke.
So what are my next steps for getting a working phone? I don't care what ROM I use really... I liked AOKP and just wanted to try something new.
Click to expand...
Click to collapse
What version TWRP are you using?
The latest custom ROMs require the latest modded TWRP from @bhb27.
Next step would b be to install ROM bare, no GAPPs or anything else. Let it boot successfully. You can always install all the other stuff later.
Sent via open market LG US998 V30/V30+

ChazzMatt said:
What version TWRP are you using?
The latest custom ROMs require the latest modded TWRP from @bhb27.
Next step would b be to install ROM bare, no GAPPs or anything else. Let it boot successfully. You can always install all the other stuff later.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Phone is on TWRP 3.0.2-0_MOD-04
I notice now that v3.2xxxx is out now. Can I use my current TWRP to install the newest .img file to the phone?
I didn't mention that I also attempted to flash the ROM.zip bare a few times for each of the different ROMs I tried to get working. (Both versions of LOS, AOKP , and cRDroid)

Charlie207 said:
Phone is on TWRP 3.0.2-0_MOD-04
I notice now that v3.2xxxx is out now. Can I use my current TWRP to install the newest .img file to the phone?
I didn't mention that I also attempted to flash the ROM.zip bare a few times for each of the different ROMs I tried to get working. (Both versions of LOS, AOKP , and cRDroid)
Click to expand...
Click to collapse
Go to the TWRP thread and get the latest MODDED TWRP. Do NOT use the TWRP from the official site.
I can post a link later if you can't find it, but it's the Quark TWRP thread in the same forum you got some of the other ROMs.
Sent via open market LG US998 V30/V30+

ChazzMatt said:
Go to the TWRP thread and get the latest MODDED TWRP. Do NOT use the TWRP from the official site.
I can post a link later if you can't find it, but it's the Quark TWRP thread in the same forum you got some of the other ROMs.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
OK, I'll take a look.
Can I upgrade TWRP within TWRP?

Charlie207 said:
OK, I'll take a look.
Can I upgrade TWRP within TWRP?
Click to expand...
Click to collapse
Yes.
Sent via open market LG US998 V30/V30+

ChazzMatt said:
Yes.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
OK.
Successfully upgraded TWRP, and the install of LOS seemed to go smoothly. Now it's back to the waiting game with the install/boot animation. I'll check back in a bit if nothing good has happened.

So after trying to install fresh versions of AOKP and LOS with the most recent version of TWRP I'm still stuck.
Now AOKP (which installs without a hiccup) simply lights up the boot image, and basically shuts off after 20-30 seconds.
Can I get a hint on the best way to completely wipe the phone with TWRP, and trying a different method?

Charlie207 said:
So after trying to install fresh versions of AOKP and LOS with the most recent version of TWRP I'm still stuck.
Now AOKP (which installs without a hiccup) simply lights up the boot image, and basically shuts off after 20-30 seconds.
Can I get a hint on the best way to completely wipe the phone with TWRP, and trying a different method?
Click to expand...
Click to collapse
You can try a truly clean install...
Boot your phone to TWRP, plug into PC, test file transfer. Drag something from PC to Download folder and make sure it's there...
Then, if successful, gather everything you want to install -- ROM, GAPPS, SuperSu, etc. -- onto your PC.
Next save off anything you could not stand to lose or do not have backed up already. Pictures in the DCIM folder, and such.
Now while still in TWRP, format everything on the phone. Including internal storage. You will be completely wiping the phone. You will lose everything on the phone.
Do NOT reboot!
After wiping the phone, while still in TWRP, drag over all the install files you gathered earlier. Install the ROM first and reboot. If successful, go back to TWRP and install GAPPS and whatever else you want.
Sent via open market LG US998 V30/V30+

ChazzMatt said:
You can try a truly clean install...
Boot your phone to TWRP, plug into PC, test file transfer. Drag something from PC to Download folder and make sure it's there...
Then, if successful, gather everything you want to install -- ROM, GAPPS, SuperSu, etc. -- onto your PC.
Next save off anything you could not stand to lose or do not have backed up already. Pictures in the DCIM folder, and such.
Now while still in TWRP, format everything on the phone. Including internal storage. You will be completely wiping the phone. You will lose everything on the phone.
Do NOT reboot!
After wiping the phone, while still in TWRP, drag over all the install files you gathered earlier. Install the ROM first and reboot. If successful, go back to TWRP and install GAPPS and whatever else you want.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I've done this several times as you describe it. Each time (no matter which ROM) it installs a-ok and then hangs up on the first boot animation.
If TWRP isn't going to work, is there another way to install a .zip? I seem to remember doing it via ADB a few years ago.

Charlie207 said:
I've done this several times as you describe it. Each time (no matter which ROM) it installs a-ok and then hangs up on the first boot animation.
If TWRP isn't going to work, is there another way to install a .zip? I seem to remember doing it via ADB a few years ago.
Click to expand...
Click to collapse
There's ways to push over files via ADB, as this was necessary before TWRP could handle drag and drop. I don't know of any way to flash (install) zipped files via ADB.
Maybe someone else has some ideas?
I know you want latest custom ROM. But as an experiment have you tried flashing back to stock Marshmallow? Pure stock Marshmallow? If that works, then you can try to upgrade back to custom ROMs.

ChazzMatt said:
There's ways to push over files via ADB, as this was necessary before TWRP could handle drag and drop. I don't know of any way to flash (install) zipped files via ADB.
Maybe someone else has some ideas?
I know you want latest custom ROM. But as an experiment have you tried flashing back to stock Marshmallow? Pure stock Marshmallow? If that works, then you can try to upgrade back to custom ROMs.
Click to expand...
Click to collapse
I haven't tried flashing a pure stock MM ROM yet, but will surely give that a try. Do you have a link to a recommended MM ROM?
And, I assume I'd be attempting the install just like I did previously.... e.g. wipe everything, DO NOT reboot, drag .zip from laptop to phone via USB cable, install, (then profit?).
Not that it should matter from a hardware point of view, but I'm using a 2011 MacBook Pro 15" running the latest beta version of OS 10.13.whatever. It sends files to the phone via the Android File Transfer app. I think that's the only way to physically send files from a Mac to Android.
Looking back at some past post of mine, I had a similar issue with cRDroid, which installed it's own recovery software, and wouldn't work with TWRP. I did end up (through serious trial and error headbanging) succeeding in using ADB commands via Terminal to get the phone wiped clean and installed TWRP. After that I was able to load custom ROMs via TWRP and had no problems swapping between different ROMs until just the other day.

I found this ROM, and will attempt to flash it via TWRP: https://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234

Charlie207 said:
I found this ROM, and will attempt to flash it via TWRP: https://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
Click to expand...
Click to collapse
Well **** me running....
That worked. I followed the identical wipe+install procedure for the "stock" MM 6.0.1 ROM as I had for three other 7.x ROMs, and it installed with no issues this time. I'm staring at the Welcome screen, and pretty frustrated that this was the only way to get the phone working again. I'll do a basic setup, and then see if I can flash a 7.x ROM
Thanks for your help in solving this riddle up to now. I'll see what happens....
EDIT: Now that I think of it, the only thing I did different was that, after downloading the ROM to my laptop, I edited the file name from that long name to MM6.0.1.zip so I could simply recognize it faster when clicking between windows and stuff. Other than that I followed the same installation process as noted before.
I'm going to edit/shorten the filename of the LOS ROM and see if removing unneeded characters does anything.

Nothing is working. The Brazilian stock MM ROM works, in a basic sense, but doesn't allow calls or WiFi, so that's kind of a moot point.
Back to the drawing board.

The Brazilian MM ROM was junk for my purposes, but the other MM ROM worked.. Phone is setting up now. WiFi and LTE work on it, so I guess I'll be stuck with 6.x for a while until I feel like messing around with a 7.x ROM.

Charlie207 said:
Nothing is working. The Brazilian stock MM ROM works, in a basic sense, but doesn't allow calls or WiFi, so that's kind of a moot point.
Back to the drawing board.
Click to expand...
Click to collapse
The Brazilian ROM needs your own modem. You would need to flash that in TWRP separately.
Sent via open market LG US998 V30/V30+

ChazzMatt said:
The Brazilian ROM needs your own modem. You would need to flash that in TWRP separately.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Yeah... I realized my mistake, and flashed the other MM ROM. That one works normally.
I'm stumped why all of a sudden 7.x ROMs refuse to install on my phone. I had prevously installed crDroid, AOKP, and RR 7.x ROMs just fine via TWRP.

ChazzMatt said:
There's ways to push over files via ADB, as this was necessary before TWRP could handle drag and drop. I don't know of any way to flash (install) zipped files via ADB.
Maybe someone else has some ideas?...
Click to expand...
Click to collapse
I'm not sure if all TWRP versions for different devices are the same, but with my Pixel C (TWRP 3.2.1) there is an "adb sideload" option in recovery to install zip files via adb from a computer.
I think the command is: adb sideload filenamegoeshere.zip

Sorry for reviving this thread, but I have exact same issue. Stock Lollipop and MM roms work, but any custom rom just hangs on boot animation forever did you manage to sort it out? @Charlie207

[Q][HELP] OP3T Soft bricked after installing TWRP Recovery

Today, after i installed the latest OOS 5.0.1 with Android O 8.0, i decided to root my device.
After successfully unlocking the bootloader, i flashed the TWRP Recovery and flashed the SuperSU zip, i was stuck on the 1+ Boot logo. I tried fixing the contents through advanced options of TWRP recovery and still no luck. I also tried wiping my cache, data, dalvik etc...
So far i tried:
Installed stock recovery via fastboot, then adb sideload. My device was recognized when typing ADB Devices but when i tried to adb sideload ota.zip i got the cannot read *...zip* error. Then i tried everything i could find, my devices are installed correctly, i also tried the Large Address Awarness program and still no luck.
Then i flashed TWRP again through fastboot and try to do the same through TWRP's sideload. Still no luck
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still no luck
I ran out of ideas.... What can i do?
Thanks in advance

First of all, why didn't you make a TWRP backup of the stock ROM before trying to root? This is best practice before trying any mods (root, flashing ROMs) for reasons which are probably now obvious. I'm always surprised at how many folks skip this step.
Maybe you planned ahead of time to use the stock recovery image, if you had to. But since it wasn't on the phone when you need it, you're running into the problem of getting it on there now.
Yiannis75 said:
i flashed the TWRP Recovery and flashed the SuperSU zip
Click to expand...
Click to collapse
What version TWRP, and what version SuperSU?
Honestly, I would recommend Magisk for root, over SuperSU. I've seen a number of folks have problems with recent version SuperSU on this device. And Magisk has a lot of really cool, useful features. I'm normally not one to recommend one method over another. Especially since SuperSU was so tried and true for so long. But at this point, I see no benefit of using SuperSU, but many benefits to Magisk. And seemingly less problems rooting with Magisk. My recommendation would be current version Magisk, which is v16.0.
Yiannis75 said:
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still
Click to expand...
Click to collapse
First of all, make sure you are using the "full" update zip (which will be >1 GB) and not the partial OTA "patch". You can get the full zip from here (Post #2): https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Since you have TWRP installed, boot into TWRP. You should be able to see your internal storage on your computer, just like it's a thumb drive. Just drag/copy and drop the full OTA zip onto the phone's internal storage. Then just flash the zip in TWRP.
The internal storage should be selected to "Mount" in TWRP by default. But if you can't see internal storage on your computer, make sure it's selected in the TWRP "Mount" section.

Yiannis75 said:
Today, after i installed the latest OOS 5.0.1 with Android O 8.0, i decided to root my device.
After successfully unlocking the bootloader, i flashed the TWRP Recovery and flashed the SuperSU zip, i was stuck on the 1+ Boot logo. I tried fixing the contents through advanced options of TWRP recovery and still no luck. I also tried wiping my cache, data, dalvik etc...
So far i tried:
Installed stock recovery via fastboot, then adb sideload. My device was recognized when typing ADB Devices but when i tried to adb sideload ota.zip i got the cannot read *...zip* error. Then i tried everything i could find, my devices are installed correctly, i also tried the Large Address Awarness program and still no luck.
Then i flashed TWRP again through fastboot and try to do the same through TWRP's sideload. Still no luck
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still no luck
I ran out of ideas.... What can i do?
Thanks in advance
Click to expand...
Click to collapse
Which exact version of TWRP did you install?
Are you Greek btw?
Unleashed by my rooted OP3T on 8.0

RASTAVIPER said:
Which exact version of TWRP did you install?
Are you Greek btw?
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
I believe i used TWRP 3.2.1-0... the very latest
And yeah am cypriot

Yiannis75 said:
I believe i used TWRP 3.2.1-0... the very latest
Click to expand...
Click to collapse
You can verify by booting to TWRP. It says version number on the splash screen.
Did you look at, or try my recommendations in my last response?

redpoint73 said:
First of all, why didn't you make a TWRP backup of the stock ROM before trying to root? This is best practice before trying any mods (root, flashing ROMs) for reasons which are probably now obvious. I'm always surprised at how many folks skip this step.
Maybe you planned ahead of time to use the stock recovery image, if you had to. But since it wasn't on the phone when you need it, you're running into the problem of getting it on there now.
What version TWRP, and what version SuperSU?
Honestly, I would recommend Magisk for root, over SuperSU. I've seen a number of folks have problems with recent version SuperSU on this device. And Magisk has a lot of really cool, useful features. I'm normally not one to recommend one method over another. Especially since SuperSU was so tried and true for so long. But at this point, I see no benefit of using SuperSU, but many benefits to Magisk. And seemingly less problems rooting with Magisk. My recommendation would be current version Magisk, which is v16.0.
First of all, make sure you are using the "full" update zip (which will be >1 GB) and not the partial OTA "patch". You can get the full zip from here (Post #2): https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Since you have TWRP installed, boot into TWRP. You should be able to see your internal storage on your computer, just like it's a thumb drive. Just drag/copy and drop the full OTA zip onto the phone's internal storage. Then just flash the zip in TWRP.
The internal storage should be selected to "Mount" in TWRP by default. But if you can't see internal storage on your computer, make sure it's selected in the TWRP "Mount" section.
Click to expand...
Click to collapse
I did make a nandroid backup from TWRP i just didnt restore it because i thought it was TWRP’s issue due to dm-variety... my bad but whatever
Yeah i have read about Magisk i just didnt investigate enough to know exactly what it is was so i thought it would be better to go for SuperSU because thats what i used on every android device i has... my bad aswell here
About the full update zip.. i’ll try that because i think i was trying to sidelod the ota patch which was 1.6gb...(but still, is the “cannot read xxx.zip” related with what zip file do i sideload? Whatever ill try it when i get home
And also i have already tried the mount feature of twrp recovery but my device just wouldnt show up on my computer.... I will try again later when i have the time and i will contact you if i need any help(if thats ok ofcourse) ...thanks in advance

Yiannis75 said:
I did make a nandroid backup from TWRP i just didnt restore it because i thought it was TWRP’s issue due to dm-variety... my bad but whatever
Click to expand...
Click to collapse
TWRP and root shouldn't normally trip DM-verity (make the phone not boot).
I don't think it will hurt anything at this point to restore the backup you made. You're already trying to flash stock recovery, anyway (which is not that different).
If the restore is successful (phone boots to OS), then just flash Magisk and be done with it!
Yiannis75 said:
Yeah i have read about Magisk i just didnt investigate enough to know exactly what it is was so i thought it would be better to go for SuperSU because thats what i used on every android device i has... my bad aswell here
Click to expand...
Click to collapse
I wouldn't say it's "your bad". Magisk is just a suggestion or recommendation. Some folks have had success with SuperSU. But also seems like a lot more folks than usual, having problems (like no boot) with SuperSU than I'm used to seeing. And as I mentioned, I don't see any benefit of SuperSU (over Magisk) at this point. I was slow to change as well. But after trying Magisk, there has been no going back for me since. So therefore, the suggestion.
You didn't mention what version SuperSU, but 2.82 SR5 is recommended. It's in beta now, so if you used the "stable" 2.82 version, that might be the problem right there.
Yiannis75 said:
About the full update zip.. i’ll try that because i think i was trying to sidelod the ota patch which was 1.6gb...(but still, is the “cannot read xxx.zip” related with what zip file do i sideload? Whatever ill try it when i get home
Click to expand...
Click to collapse
If it was 1.6GB, than it was the full update (at least one of them). I typed ">1 GB" so any OTA zip for this device greater than 1 GB should be okay. It's the OTA zips that are less than 1 GB that you need to watch out for, as it is not a full update, just a partial "patch" (don't flash on a modded device with TWRP or you will soft brick!).
I don't personally use sideload. While I see the convenience, I find it a bit messy. I've seen folks have problems with sideload, when simply putting the ROM on the phone and flashing with TWRP works fine (so in those cases sideload itself was the point of failure).
Now of course, getting the ROM on the phone is the problem, in your case.
Yiannis75 said:
And also i have already tried the mount feature of twrp recovery but my device just wouldnt show up on my computer.... I will try again later when i have the time and i will contact you if i need any help(if thats ok ofcourse)
Click to expand...
Click to collapse
Just post to this thread, and I'll see it. That is the best way to contact me. Good luck!

Yiannis75 said:
I believe i used TWRP 3.2.1-0... the very latest
And yeah am cypriot
Click to expand...
Click to collapse
Inta mou laleis??
Coming to Cyprus soon bro!
About your issue, use TWRP bluespark 8.61, just to be sure.
Never had issues with this version.
Unleashed by my rooted OP3T on 8.0

redpoint73 said:
TWRP and root shouldn't normally trip DM-verity (make the phone not boot).
I don't think it will hurt anything at this point to restore the backup you made. You're already trying to flash stock recovery, anyway (which is not that different).
If the restore is successful (phone boots to OS), then just flash Magisk and be done with it!
I wouldn't say it's "your bad". Magisk is just a suggestion or recommendation. Some folks have had success with SuperSU. But also seems like a lot more folks than usual, having problems (like no boot) with SuperSU than I'm used to seeing. And as I mentioned, I don't see any benefit of SuperSU (over Magisk) at this point. I was slow to change as well. But after trying Magisk, there has been no going back for me since. So therefore, the suggestion.
You didn't mention what version SuperSU, but 2.82 SR5 is recommended. It's in beta now, so if you used the "stable" 2.82 version, that might be the problem right there.
If it was 1.6GB, than it was the full update (at least one of them). I typed ">1 GB" so any OTA zip for this device greater than 1 GB should be okay. It's the OTA zips that are less than 1 GB that you need to watch out for, as it is not a full update, just a partial "patch" (don't flash on a modded device with TWRP or you will soft brick!).
I don't personally use sideload. While I see the convenience, I find it a bit messy. I've seen folks have problems with sideload, when simply putting the ROM on the phone and flashing with TWRP works fine (so in those cases sideload itself was the point of failure).
Now of course, getting the ROM on the phone is the problem, in your case.
Just post to this thread, and I'll see it. That is the best way to contact me. Good luck!
Click to expand...
Click to collapse
So, got home fixed the drivers so that my pc could recognize my device while on TWRP recovery, flashed the zip file through TWRP and it worked like a charm
Thanks for all the help bro

Help pls
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide

mannulko said:
Help pls
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
just like me, if u flash oos 5.0.2 from twrp u will be just fine. Just flash magisk instead of supersu like i did and all will be working just fine

mannulko said:
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
If posting on a thread, related to your issue; it would make sense to actually read the responses in the thread. Since your question is already answered.
In short, you need to use SuperSU 2.82 SR5. The "stable" version 2.82 won't work, and will result in no boot. Or use Magisk 16.0.
If the phone still won't boot after (only) flashing the proper version SuperSU or Magisk; then flash the full stock update file using TWRP. Then flash the right version SuperSU or Magisk.