Database Develop

Deleted files return on boot

Hi all, just purchased an HTC one and rooted following some instructions via an xda video.
The phone is confirmed rooted s-on (via root checker) and has super su installed. Now the phone came only with some O2 hideous bootanimation and downanimation and I wanted to remove them. Installed root browser and deleted the .zip files from system/customise/resources and restarted to confirm. When turning off, the animation isnt there, but upon restart the animations return, together with the files deleted previously. Any ideas what can I do to leave these files permanently deleted?
thx

aquist said:
Hi all, just purchased an HTC one and rooted following some instructions via an xda video.
The phone is confirmed rooted s-on (via root checker) and has super su installed. Now the phone came only with some O2 hideous bootanimation and downanimation and I wanted to remove them. Installed root browser and deleted the .zip files from system/customise/resources and restarted to confirm. When turning off, the animation isnt there, but upon restart the animations return, together with the files deleted previously. Any ideas what can I do to leave these files permanently deleted?
thx
Click to expand...
Click to collapse
Flash an unsecure kernel, the stock kernel doesn't allow deleting of anything.

Seanie280672 said:
Flash an unsecure kernel, the stock kernel doesn't allow deleting of anything.
Click to expand...
Click to collapse
any recommendations? and i assume you'd flash it normally?

aquist said:
any recommendations? and i assume you'd flash it normally?
Click to expand...
Click to collapse
I use ElementalX, a lot of guys on here do, and flash it in recovery, twrp 2.6.3.3 its recommended, I know there is newer versions on that site ive linked below, but use 2.6.3.3 as its the most compatible.
TWRP 2.6.3.3. can be found here: http://techerrata.com/browse/twrp2/m7
ElementalX here: http://forum.xda-developers.com/showthread.php?t=2249774
make sure you do a full back-up beore flashing anything, bootloader must be unlocked, and select the correct kernel as per your phone sense and rom version, found in settings, about phone.

Seanie280672 said:
I use ElementalX, a lot of guys on here do, and flash it in recovery, twrp 2.6.3.3 its recommended, I know there is newer versions on that site ive linked below, but use 2.6.3.3 as its the most compatible.
TWRP 2.6.3.3. can be found here: http://techerrata.com/browse/twrp2/m7
ElementalX here: http://forum.xda-developers.com/showthread.php?t=2249774
make sure you do a full back-up beore flashing anything, bootloader must be unlocked, and select the correct kernel as per your phone sense and rom version, found in settings, about phone.
Click to expand...
Click to collapse
cheers man, it worked. what a ton of features from which to choose!
A small note, I managed to go through the whole process with the latest TWRP and not on the 2.6.3.3...just a heads up for those who might have the same problem

[Q] Is Moto G safe to root?

Hi, as the title states, is the new moto g safe to root despite the various bugs and issues with the recovery?

mahendru1992 said:
Hi, as the title states, is the new moto g safe to root despite the various bugs and issues with the recovery?
Click to expand...
Click to collapse
Yea go ahead. Its totally safe to root. No issues or bugs faced till now. Follow this thread : http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245/
I have rooted and flashed TWRP v 2.8.0.1. I am hoping someone compiles a working CWM recovery for our device.

mahendru1992 said:
Hi, as the title states, is the new moto g safe to root despite the various bugs and issues with the recovery?
Click to expand...
Click to collapse
Yes you can root and unlock boot loader but I think the guy who posted it pulled the recovery part and closed his thread due to recovery bug issues.

Okay I will, thanks.
Though what's strange is the version number. I went to the official site of TWRP and the version was 2.8.0.0, but on the root thread, the version is 2.8.0.1.

Better use this recovery i found somewhere (image file, use flashify). With 2.8.0.1 i wasn't eable to create backups
https://drive.google.com/folder/d/0B0AbMwIJ-N7xM25CdjlQOUl2Qlk/edit

marcviado said:
Yes you can root and unlock boot loader but I think the guy who posted it pulled the recovery part and closed his thread due to recovery bug issues.
Click to expand...
Click to collapse
Yup current TWRP v2.8 has some issues while flashing KK ROMS and taking too much time to clear cache. The device reboots automatically while taking a TWRP system backup.
We need a CWM recovery ASAP :fingers-crossed:
---------- Post added at 03:12 AM ---------- Previous post was at 03:06 AM ----------
KingGehl said:
Better use this recovery i found somewhere (image file, use flashify). With 2.8.0.1 i wasn't eable to create backups
https://drive.google.com/folder/d/0B0AbMwIJ-N7xM25CdjlQOUl2Qlk/edit
Click to expand...
Click to collapse
Same here.
Thanks a ton I wanted to rollback to the previous version. I didnt have the latest system backup after the OTA update.

KingGehl said:
Better use this recovery i found somewhere (image file, use flashify). With 2.8.0.1 i wasn't eable to create backups
https://drive.google.com/folder/d/0B0AbMwIJ-N7xM25CdjlQOUl2Qlk/edit
Click to expand...
Click to collapse
No problems with this one right?

mahendru1992 said:
No problems with this one right?
Click to expand...
Click to collapse
v2.7 is relatively bugless as compared to v2.8

mahendru1992 said:
No problems with this one right?
Click to expand...
Click to collapse
Nope, works as expected

Okay, I need a little help here. I flashed the old twrp via fastboot but then got the mismatched partition size error. Well I thought what the hell, and I selected recovery from the menu, but the problem is that the phone doesn't go into recovery, just reboots. What should I do?
EDIT: I also tried rebooting via recovery when the phone wasn't connected to the laptop. If i press the power button on any of the options - normal powerup, recovery, factory or barcodes - the phone switches off.
EDIT 2: I tried getting into recovery via adb, but all I get is a 'no command' message when the phone reboots. A quick google search showed me that the no command message means that the phone still has the stock recovery. It seems like twrp isn't flashing. Any ideas!?

How can i install a kernel?

I've been trying to find how to install a kernel for a few days but i couldn't find any good and updated source. I'm thinking of installing latest helium to my device. Can anyone help me?

ExclusiveBFS said:
I've been trying to find how to install a kernel for a few days but i couldn't find any good and updated source. I'm thinking of installing latest helium to my device. Can anyone help me?
Click to expand...
Click to collapse
Through any recovery is the most easy way, but you have to unlock bootloader first.

Do you even know what it does?

Bigrrd225 said:
Do you even know what it does?
Click to expand...
Click to collapse
Yeah, I do. I just didn't want to flash it and take risk. I must have learned details
HUEguy said:
Through any recovery is the most easy way, but you have to unlock bootloader first.
Click to expand...
Click to collapse
My bootloader is unlocked. And I have the twrp. Thanks!

ExclusiveBFS said:
Yeah, I do. I just didn't want to flash it and take risk. I must have learned details
My bootloader is unlocked. And I have the twrp. Thanks!
Click to expand...
Click to collapse
Then just flash the .zip file via TWRP. Simple. Of course you'll need a ROM compatible with helium otherwise you'll be stuck in a bootloop.
Also goes without saying that you should take a nandroid backup via TWRP first in case something goes wrong.
Edit : When you say you have TWRP, is it part of your current kernel or you flashed it in your FOTA kernel partition via Rashr or something? If its the former then flashing Helium would overwrite TWRP and you could wind up without a working recovery cause I don't think Helium comes with any. Might want to flash TWRP in your FOTA partition with Rashr before you proceed.

XenolithicYardZone said:
Then just flash the .zip file via TWRP. Simple. Of course you'll need a ROM compatible with helium otherwise you'll be stuck in a bootloop.
Also goes without saying that you should take a nandroid backup via TWRP first in case something goes wrong.
Edit : When you say you have TWRP, is it part of your current kernel or you flashed it in your FOTA kernel partition via Rashr or something? If its the former then flashing Helium would overwrite TWRP and you could wind up without a working recovery cause I don't think Helium comes with any. Might want to flash TWRP in your FOTA partition with Rashr before you proceed.
Click to expand...
Click to collapse
I was on latest candy5, i flashed adrian dc's twrp from recovery but now I'm installing the stock ftf, I will try carbon lp rom. When the installation completed, I will flash adrian dc's twrp again. Then I will flash the helium kernel with twrp. Is there a problem with that? Should I install twrp with rashr?

ExclusiveBFS said:
I was on latest candy5, i flashed adrian dc's twrp from recovery but now I'm installing the stock ftf, I will try carbon lp rom. When the installation completed, I will flash adrian dc's twrp again. Then I will flash the helium kernel with twrp. Is there a problem with that? Should I install twrp with rashr?
Click to expand...
Click to collapse
If you're gonna flash stock firmware via Flashtool then your FOTA recovery will be wiped out. How are you gonna flash TWRP & Carbon LP rom when you don't have a recovery in the first place?
http://forum.xda-developers.com/xperia-sp/development/recovery-twrp-3-0-0-touch-recovery-t3309938
The recovery from the above thread is flashable but you still need an working recovery on your device to be able to do it right? What you can do it use the fastboot bootable image and install whatever you want if you're gonna go stock.
Actually you only need Rashr if you wanna stay stock but still want a working recovery.

XenolithicYardZone said:
If you're gonna flash stock firmware via Flashtool then your FOTA recovery will be wiped out. How are you gonna flash TWRP & Carbon LP rom when you don't have a recovery in the first place?
http://forum.xda-developers.com/xperia-sp/development/recovery-twrp-3-0-0-touch-recovery-t3309938
The recovery from the above thread is flashable but you still need an working recovery on your device to be able to do it right? What you can do it use the fastboot bootable image and install whatever you want if you're gonna go stock.
Actually you only need Rashr if you wanna stay stock but still want a working recovery.
Click to expand...
Click to collapse
I guess I couldn't explained my situation well. I installed carbon rom just now, and flashed gapps. I didn't check if carbon comes with a recovery but if it comes, I'm going to flash adrian dc's twrp through stock recovery. That's what I'm asking, is there a difference between using rashr to install twrp or flashing through recovery.

ExclusiveBFS said:
I guess I couldn't explained my situation well. I installed carbon rom just now, and flashed gapps. I didn't check if carbon comes with a recovery but if it comes, I'm going to flash adrian dc's twrp through stock recovery. That's what I'm asking, is there a difference between using rashr to install twrp or flashing through recovery.
Click to expand...
Click to collapse
Carbon provides CM recovery. Flash TWRP only through recovery, don't use Rashr.

ExclusiveBFS said:
I guess I couldn't explained my situation well. I installed carbon rom just now, and flashed gapps. I didn't check if carbon comes with a recovery but if it comes, I'm going to flash adrian dc's twrp through stock recovery. That's what I'm asking, is there a difference between using rashr to install twrp or flashing through recovery.
Click to expand...
Click to collapse
The recovery that comes with Carbon is most probably Cyanogen recovery which will not let you flash unsigned zip files like custom kernels & roms, SuperSU, Xposed, etc.
Its the reason why people install a recovery in their FOTA partitions because installing new kernels or roms (which include their own kernel) wipes out the previous recovery since Xperia phones esp older one's like ours don't have a separate recovery partition - the recovery is part of the kernel so it gets replaced by whatever came (or didn't) with the new kernel or rom. Atleast that's how it works to the best of my knowledge.
With fastboot, you could boot the device into TWRP recovery using the twrp-3.0.0-rX-boot-huashan.img file and the command "fastboot boot *filename*.img". This way its just temporary and doesn't permanently flash anything. Once in the recovery, flash the rom, kernel, recovery and you are done. That's how I did it on my Mi4i though you might want to confirm but since the description next to it says fastboot bootable, I guessing it works on the same principal.
Edit : If the kernel creator says no Rashr then its no Rashr.

XenolithicYardZone said:
The recovery that comes with Carbon is most probably Cyanogen recovery which will not let you flash unsigned zip files like custom kernels & roms, SuperSU, Xposed, etc.
Its the reason why people install a recovery in their FOTA partitions because installing new kernels or roms (which include their own kernel) wipes out the previous recovery since Xperia phones esp older one's like ours don't have a separate recovery partition - the recovery is part of the kernel so it gets replaced by whatever came (or didn't) with the new kernel or rom. Atleast that's how it works to the best of my knowledge.
With fastboot, you could boot the device into TWRP recovery using the twrp-3.0.0-rX-boot-huashan.img file and the command "fastboot boot *filename*.img". This way its just temporary and doesn't permanently flash anything. Once in the recovery, flash the rom, kernel, recovery and you are done. That's how I did it on my Mi4i though you might want to confirm but since the description next to it says fastboot bootable, I guessing it works on the same principal.
Edit : If the kernel creator says no Rashr then its no Rashr.
Click to expand...
Click to collapse
I find that flashing TWRP from CM recovery and then Helium from TWRP is much simpler than flashing TWRP as a kernel in the boot partition, then flashing the rom again and the kernel.

Tomoms said:
Carbon provides CM recovery. Flash TWRP only through recovery, don't use Rashr.
Click to expand...
Click to collapse
I flashed helium v5 for lollipop through twrp 3.0.0 and rebooted. It's not booted yet, i'm waiting for 2 minutes and the screen is black. Is it normal?

Tomoms said:
I find that flashing TWRP from CM recovery and then Helium from TWRP is much simpler than flashing TWRP as a kernel in the boot partition, then flashing the rom again and the kernel.
Click to expand...
Click to collapse
Wait hang on, CM recovery lets you flash custom zip files now without moaning about file verification? Since when?
Yes that's why I asked him to temporarily boot up with the TWRP img and then flash whatever he liked from it but hey if you can flash stuff via CM recovery now then that's one less step to worry about.
Also why no Rashr? I haven't used it in a while that's why I am asking.
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
ExclusiveBFS said:
I flashed helium v5 for lollipop through twrp 3.0.0 and rebooted. It's not booted yet, i'm waiting for 2 minutes and the screen is black. Is it normal?
Click to expand...
Click to collapse
You mean black screen after the Sony splash screen? Is that rom compatible with Helium?

XenolithicYardZone said:
Wait hang on, CM recovery lets you flash custom zip files now without moaning about file verification? Since when?
Yes that's why I asked him to temporarily boot up with the TWRP img and then flash whatever he liked from it but hey if you can flash stuff via CM recovery now then that's one less step to worry about.
Also why no Rashr? I haven't used it in a while that's why I am asking.
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
You mean black screen after the Sony splash screen? Is that rom compatible with Helium?
Click to expand...
Click to collapse
First, yes it lets you flash custom zip files, that's what I was trying to tell I always used cm recovery to install twrp
And I haven't used rashr before, I didn't know how to use it. So I flashed it with cm recovery and perfectly installed.
About helium, my phone finally booted after 9 minutes, how I scared

ExclusiveBFS said:
First, yes it lets you flash custom zip files, that's what I was trying to tell I always used cm recovery to install twrp
And I haven't used rashr before, I didn't know how to use it. So I flashed it with cm recovery and perfectly installed.
About helium, my phone finally booted after 9 minutes, how I scared
Click to expand...
Click to collapse
Sorry man didn't know that CM recovery lets you do that now. Been out of the loop for a while.
Lol yeah I can relate but as long as you can see a splash screen, you're good and when you don't, Flashtool is your light in the darkness :victory:

ExclusiveBFS said:
I flashed helium v5 for lollipop through twrp 3.0.0 and rebooted. It's not booted yet, i'm waiting for 2 minutes and the screen is black. Is it normal?
Click to expand...
Click to collapse
The reboot button is broken on TWRP. Causes black screen for a long time. You must always use the Power off option instead.
XenolithicYardZone said:
Sorry man didn't know that CM recovery lets you do that now. Been out of the loop for a while.
Lol yeah I can relate but as long as you can see a splash screen, you're good and when you don't, Flashtool is your light in the darkness :victory:
Click to expand...
Click to collapse
CM recovery lets you flash signed zip, and TWRP is provided in a signed zip, while even though Helium is provided in a signed zip, it can't be flashed.

Tomoms said:
The reboot button is broken on TWRP. Causes black screen for a long time. You must always use the Power off option instead.
CM recovery lets you flash signed zip, and TWRP is provided in a signed zip, while even though Helium is provided in a signed zip, it can't be flashed.
Click to expand...
Click to collapse
@Tomoms, @XenolithicYardZone Thanks for all your help, I used more than 10 roms so far but never used a custom kernel before. You two helped me a lot

Tomoms said:
The reboot button is broken on TWRP. Causes black screen for a long time. You must always use the Power off option instead.
CM recovery lets you flash signed zip, and TWRP is provided in a signed zip, while even though Helium is provided in a signed zip, it can't be flashed.
Click to expand...
Click to collapse
Yeah kinda guessed it was signed cause in all my time flashing roms, I have never known CM recovery to allow the flashing of unsigned zips. So why doesn't it work with Helium if its signed?
ExclusiveBFS said:
@Tomoms, @XenolithicYardZone Thanks for all your help, I used more than 10 roms so far but never used a custom kernel before. You two helped me a lot
Click to expand...
Click to collapse
Your welcome man. As a famous author once said, "Help will always be given at XDA to those who ask for it. "

XenolithicYardZone said:
Yeah kinda guessed it was signed cause in all my time flashing roms, I have never known CM recovery to allow the flashing of unsigned zips. So why doesn't it work with Helium if its signed?
Click to expand...
Click to collapse
Because CM recovery sucks

Tomoms said:
Because CM recovery sucks
Click to expand...
Click to collapse
True that!

Can't install TWRP image via ADB

I've got a rooted LG G2 VS980 running 26A stock / KitKat 4.4.2. I also installed TWRP using the AutoRec for KitKat. Unfortunately, this gives me TWRP 2.7.0.0 and I'm trying to flash TWRP 2.8.6.0 using ADB.
When I enter the command
adb reboot bootloader
the LG logo comes up, then Verizon, then it boots normally into Android.
When I enter the command
adb reboot recovery
the LG logo comes up, then it goes into TWRP 2.7.0.0 recovery.
Is there any way I can get into fastboot recovery? I can't seem to access bootloader at all. Could my boot partition be corrupted after using AutoRec? I used to have another LG G2 that used to go into fastboot recovery. Not sure how to get this one to do that.
Also, when I press power and volume down at same time, see LG logo, then let go and press both buttons again, I get the "Factory date reset" page. I'd like to get fastboot instead.
To sum up, I'd like to install a newer TWRP image with ADB but can't do it with bootloader command. And I'd like to get fastboot on my LG as well.
Thanks in advance for your help.

I have an LG G2 VS9803AA (Lollipop 5.0.2) and, unfortunately, AutoRec has not worked for me at all. In fact, I have been unable to find ANY reliable/working method for installing TWRP. I will continue trying, and if I stumble upon any information I feel would help you, I will certainly let you know.
Cheers!
Terri (Psy)

NCP2 said:
I've got a rooted LG G2 VS980 running 26A stock / KitKat 4.4.2. I also installed TWRP using the AutoRec for KitKat. Unfortunately, this gives me TWRP 2.7.0.0 and I'm trying to flash TWRP 2.8.6.0 using ADB.
When I enter the command
adb reboot bootloader
the LG logo comes up, then Verizon, then it boots normally into Android.
When I enter the command
adb reboot recovery
the LG logo comes up, then it goes into TWRP 2.7.0.0 recovery.
Is there any way I can get into fastboot recovery? I can't seem to access bootloader at all. Could my boot partition be corrupted after using AutoRec? I used to have another LG G2 that used to go into fastboot recovery. Not sure how to get this one to do that.
Also, when I press power and volume down at same time, see LG logo, then let go and press both buttons again, I get the "Factory date reset" page. I'd like to get fastboot instead.
To sum up, I'd like to install a newer TWRP image with ADB but can't do it with bootloader command. And I'd like to get fastboot on my LG as well.
Thanks in advance for your help.
Click to expand...
Click to collapse
Hey man get your TWRP version you want, flash it in the TWRP version you currently HAVE , & flash the recovery.img direct as the recovery.img in TWRP, jst make sure you have the Loki bumped version & you should be safe
---------- Post added at 09:23 AM ---------- Previous post was at 09:21 AM ----------
PsyintZ said:
I have an LG G2 VS9803AA (Lollipop 5.0.2) and, unfortunately, AutoRec has not worked for me at all. In fact, I have been unable to find ANY reliable/working method for installing TWRP. I will continue trying, and if I stumble upon any information I feel would help you, I will certainly let you know.
Cheers!
Terri (Psy)
Click to expand...
Click to collapse
(Unsure if you acquired root privlidges or not)
If you have successfully rooted with KingRoot then AutoRec should've handled your request fine .
Try flashing back to stock 4.4.2 & running kingroot then AutoRec & enjoy TWRP ,
Otherwise, make sure you have kingroot updated and all that other jazz

LilAnt530 said:
Hey man get your TWRP version you want, flash it in the TWRP version you currently HAVE , & flash the recovery.img direct as the recovery.img in TWRP, jst make sure you have the Loki bumped version & you should be safe
---------- Post added at 09:23 AM ---------- Previous post was at 09:21 AM ----------
(Unsure if you acquired root privlidges or not)
If you have successfully rooted with KingRoot then AutoRec should've handled your request fine .
Try flashing back to stock 4.4.2 & running kingroot then AutoRec & enjoy TWRP ,
Otherwise, make sure you have kingroot updated and all that other jazz
Click to expand...
Click to collapse
Yeah, I have successfully rooted with KingRoot, and then used SuperSu-Me app to replace KingUser with SuperSU. I have just come across so many unfortunate stories of people bricking their G2's on the 3AA firmware while trying to install TWRP (because of our stubborn bootloader, I presume?). I did find THIS LINK to a version of AutoRec that says it's for VS980, but it doesn't specify whether or not it will work specifically for VS9803AA (5.0.2) so I have been afraid to try it. Do you think it is safe to attempt this method?
Thanks again in advance. I really appreciate your help!

PsyintZ said:
Yeah, I have successfully rooted with KingRoot, and then used SuperSu-Me app to replace KingUser with SuperSU. I have just come across so many unfortunate stories of people bricking their G2's on the 3AA firmware while trying to install TWRP (because of our stubborn bootloader, I presume?). I did find THIS LINK to a version of AutoRec that says it's for VS980, but it doesn't specify whether or not it will work specifically for VS9803AA (5.0.2) so I have been afraid to try it. Do you think it is safe to attempt this method?
Thanks again in advance. I really appreciate your help!
Click to expand...
Click to collapse
Haha no worries bro I am just learning the finer details on this device as well & it really is amazing phone!!!
I am unsure if AutoRec would work for that firmware exactly, if you are in doubt, use Flashify to backup your current recovery.img just in case maybe? Or simply use it to flash your Twrp version directly as I have NEVER noticed any issues with that app & my LG devices (had the Gpad 7.1 & 8.3 + now this G2)
---------- Post added at 07:14 AM ---------- Previous post was at 07:13 AM ----------
PsyintZ said:
Yeah, I have successfully rooted with KingRoot, and then used SuperSu-Me app to replace KingUser with SuperSU. I have just come across so many unfortunate stories of people bricking their G2's on the 3AA firmware while trying to install TWRP (because of our stubborn bootloader, I presume?). I did find THIS LINK to a version of AutoRec that says it's for VS980, but it doesn't specify whether or not it will work specifically for VS9803AA (5.0.2) so I have been afraid to try it. Do you think it is safe to attempt this method?
Thanks again in advance. I really appreciate your help!
Click to expand...
Click to collapse
I should also add I used KingRoot/AutoRec combo on this LG vs980 but I am stuck forever on 4.4.2 haha

LilAnt530 said:
I am unsure if AutoRec would work for that firmware exactly, if you are in doubt, use Flashify to backup your current recovery.img just in case maybe? Or simply use it to flash your Twrp version directly as I have NEVER noticed any issues with that app & my LG devices...
Click to expand...
Click to collapse
I do not have a current recovery, as I have been unable to get any version of TWRP installed yet. I think I am going to go ahead and try out that VS980 AutoRec from the link I provided. Hopefully all goes well. I will let you know how everything goes. Appreciate you helping me out, LilAnt!

PsyintZ said:
I do not have a current recovery, as I have been unable to get any version of TWRP installed yet. I think I am going to go ahead and try out that VS980 AutoRec from the link I provided. Hopefully all goes well. I will let you know how everything goes. Appreciate you helping me out, LilAnt!
Click to expand...
Click to collapse
Yea give it a go & if worst comes to worse just use LG Mobile Support Tool, flash back over to 4.4.2, & I can give an absolute promise on this method working on that firmware & model combo. I really do love this phone but all of the firmware stuff tends to confuse me with LG products so I always go to the lowest version of stock first haha.
& No worries bud! Just hit thanks once or twice haha & let me know how it goes for ya, hopefully you don't hit a brick xD.

[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.