Hello,
I rooted my stock phone (Verizon, 4.4.2, VS98027A, Kernal: 3.4.0-perf) using Stumproot, than installed SuperSU and used Autorec to install TWRP. I succesfully created a Nandroid backup and transferred this to my PC for safekeeping. I also took the opportunity to transfer all pics and backup all my apps, texts, etc. But I'm having an issue where the phone will freeze when I try to knock on (or wake it in general) and boot to the verizon logo and restart.
I planned on flashing a new rom to the phone (I need something super stable like CM) - Would that possible fix the issue? I read somewhere else that this problem is caused by Autorec, but I can I fix it properly?
Thanks for the help, complete noob here.
furry007 said:
Hello,
I rooted my stock phone (Verizon, 4.4.2, VS98027A, Kernal: 3.4.0-perf) using Stumproot, than installed SuperSU and used Autorec to install TWRP. I succesfully created a Nandroid backup and transferred this to my PC for safekeeping. I also took the opportunity to transfer all pics and backup all my apps, texts, etc. But I'm having an issue where the phone will freeze when I try to knock on (or wake it in general) and boot to the verizon logo and restart.
I planned on flashing a new rom to the phone (I need something super stable like CM) - Would that possible fix the issue? I read somewhere else that this problem is caused by Autorec, but I can I fix it properly?
Thanks for the help, complete noob here.
Click to expand...
Click to collapse
Your problem was using AutoRec. I've said it throughout a few threads, and others have stated that AutoRec causes issues on 27A.
You should be using a bumped recovery, not the old 2.7.0.0 recovery found in AutoRec. Try flashing blastagator's latest bumped recovery (Reboot to recovery to make sure thew new recovery loads up first), then the 27A bootstack, and then flash the boot image I posted in one of MicorMods' threads.
I'll make it easy for you:
Recovery (If you can't get the recovery to flash, you will have to adb it manually, or use MicorMod's tool): http://blastagator.ddns.net/twrp/2-8-5-1.php
27A bootstack: http://www.mediafire.com/download/jbswp6k7vwiijvx/bouchigo_VS980-27A_bootstack.zip
MD5: a25e8745be420e7286ed84127496d5d1
Boot image: http://www.mediafire.com/download/xa24h6fln972mz7/Fix_Rooted_Status_LG_G2-VS980-27A_v2.zip
MD5: 29c3c830e3147687db9ba3534fa8b481
Thank you!
So if I understood correctly, transfer the blastagator vs980 recovery and MD5 to my phone. Reboot into recovery, then flash this bumped recovery file.
Then transfer the 27A bootstack and boot image you posted onto my phone. Boot into TWRP that I currently have installed, select these 2 files, and flash the phone correct?
furry007 said:
Thank you!
So if I understood correctly, transfer the blastagator vs980 recovery and MD5 to my phone. Reboot into recovery, then flash this bumped recovery file.
Then transfer the 27A bootstack and boot image you posted onto my phone. Boot into TWRP that I currently have installed, select these 2 files, and flash the phone correct?
Click to expand...
Click to collapse
Just transfer all the files at once to a folder on your phone. Boot into recovery, flash blastagator's recovery, reboot recovery (there's an option in twrp that reboots into recovery without having to leave recovery) to make sure the new recovery loads up. Now proceed to flash the bootstack and boot image files.
Thanks! Will give this a shot and report back
Related
Hey guys,
I just flashed from 4.2 Malladus to 4.4 Malladus smoothly. Everything loaded and is buttery smooth now. I attempted to enter Recovery to make a back up but it only left me with a black screen after the LG logo. I can't seem to figure out what happened, I tried to enter TWRP through ROM Manager's boot in recovery option and also the Power off and Restart into Recovery that comes with the ROM installed.
Anyone have any ideas on how I can access my recovery again?
ifizik said:
Hey guys,
I just flashed from 4.2 Malladus to 4.4 Malladus smoothly. Everything loaded and is buttery smooth now. I attempted to enter Recovery to make a back up but it only left me with a black screen after the LG logo. I can't seem to figure out what happened, I tried to enter TWRP through ROM Manager's boot in recovery option and also the Power off and Restart into Recovery that comes with the ROM installed.
Anyone have any ideas on how I can access my recovery again?
Click to expand...
Click to collapse
Did you update your firmware also? Can't directly flash a recovery on 24A. There's some extra steps involved, AutoRec listed in the LG G2 section is the easiest way around that.
I believe I did, TBH I do not know that answer for sure. I merely followed the steps listed in the installation guide for Malladus within this page:
https://docs.google.com/document/d/1xsU9W656TA-Lw1LAlL7hqROf2QjiOI2puyDU-DDP41Q/edit - that step being 3b, telling me to flash vs980_1xx_to_24a.zip to prep for 4.4. I'm assuming that's the file for the firmware but I could be wrong.
I followed the steps completely and everything booted up beautifully, minus the issue with me having no recovery when attempting trying to make a back-up.
I'll check out the AutoRec suggestion you've given me, thanks.
ifizik said:
I believe I did, TBH I do not know that answer for sure. I merely followed the steps listed in the installation guide for Malladus within this page:
https://docs.google.com/document/d/1xsU9W656TA-Lw1LAlL7hqROf2QjiOI2puyDU-DDP41Q/edit - that step being 3b, telling me to flash vs980_1xx_to_24a.zip to prep for 4.4. I'm assuming that's the file for the firmware but I could be wrong.
I followed the steps completely and everything booted up beautifully, minus the issue with me having no recovery when attempting trying to make a back-up.
I'll check out the AutoRec suggestion you've given me, thanks.
Click to expand...
Click to collapse
If you were on 11A you needed the vs980_1xx_to_24a_twrp.zip. Meaning you had to have taken the OTA to 12B, not just have flashed the radio. If you were on 11A and didn't flash the right prep zip it would erase recovery. Either way, just download Flashify from the market and let it flash whichever recovery you want. That should work just fine. With either of those prep zips it flashed the JB aboot, and laf. So Flashify will get your recovery back.
So the AutoRec method worked beautifully. I have a recovery once again and was able to make a back-up so i can flash kernels
Thanks for the help.
JRJ442 said:
If you were on 11A you needed the vs980_1xx_to_24a_twrp.zip. Meaning you had to have taken the OTA to 12B, not just have flashed the radio. If you were on 11A and didn't flash the right prep zip it would erase recovery. Either way, just download Flashify from the market and let it flash whichever recovery you want. That should work just fine. With either of those prep zips it flashed the JB aboot, and laf. So Flashify will get your recovery back.
Click to expand...
Click to collapse
If you scroll down on page 2 of the document in the FAQ section it tells you how to install a recovery.
Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!
mobone32 said:
Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!
Click to expand...
Click to collapse
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again
mobone32 said:
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again
Click to expand...
Click to collapse
you should be able to install TWRP by using the command, "mfastboot recovery twrp.img"
regarding CM11, I don't think is needed anymore to go from CM10 to CM12. it was at one time, but I believe CM or TWRP made some updates so that step is no longer necessary.
but before we can help you further, let us know what ROM you are on now and what ROM you want to be on next.
also, this thread is very helpful: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
Ok I got TWRP on there. Now I would like to get to lolipop 5.1 one way or another. I've always liked CyanogenMod (of course) but want to try CyanHacker. http://forum.xda-developers.com/moto-x/development/rom-cyanhacker-lollipop-ghost-t3033367
Right now I'm on a stock sprint rom I got with kitkat 4.4.4
Here's what I was going to do: (copied from forum)
1. mfastboot flash the latest TWRP if you aren't already at that point. I won't help you on fastboot things as you should already know- look around in the forums for info.
2. BACKUP YOUR STUFF- don't want to lose things without being able to get them back, right?
3. Flash the downloaded CM11 snapshot.
(Heres where I'm stuck. This is where I soft bricked it last night. I tried just now to apply the update using twrp and it just fails. It also fails at rooting my phone.)
4. Let CM11 fully boot and go through the setup screen- just skip everything and get to the homescreen.
5. Reboot into Recovery and wipe EVERYTHING- system, data, dalvik cache, cache, etc.
6. Flash your Lollipop ROM.
7. Flash PA-gapps.
8. Flash SuperSU.
9. Wipe cache/dalvik cache.
10. Reboot.
11. ???
12. Profit.
Thanks for any help!
Hi Nexus 6 Community
Im new to own a Nexus 6 but Im an "enthusiastic flasher" per say. I've being looking around with no luck so I was hopping someone will point me to the right direction:
Usually whenever I flash anything on my previous phones I like to flash TWRP again in case of boot loops or something flashing bad that could delete or corrupt my custom recovery. I'm rooted and installed the latest TWRP through fastboot, but as I previously said, I would like to have a flashable zip to ensure my recovery will be installed and have a higher chance of not being locked out of my phone.
Or I'd notice you can flash images through TWRP, will this re-install my recovery using the TWRP .img file?
I really appreciate all for your help, thanks
Once you boot into twrp for the first time it patches /system to prevent the stock rom from replacing it unless you choose the "keep system mounted as read-only." This option is only offered to you if you boot into twrp with an untouched /system. And as for worrying about being locked out of your phone, as long as you have an unlocked bootloader you can always use a google factory image to get back to stock w/o a custom recovery.
I'd assume no one's made a flashable zip for twrp because reflashing it wouldn't accomplish much of anything if you already have twrp to flash it in.
So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
theprof7 said:
So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
Click to expand...
Click to collapse
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
raptorddd said:
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
Click to expand...
Click to collapse
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
theprof7 said:
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
Click to expand...
Click to collapse
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
https://drive.google.com/file/d/0B90RfjoH13UEbDFBSG5XWVA0ME0/view?usp=sharing
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
theprof7 said:
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
try a custom kernel it has superSU installed.. i say imperium kernel.
try first the custom kernel.. if not you can only downgrade to 20o. no lower or youll hard brick phone.
Click to expand...
Click to collapse
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
can you please share what guide you used to unlock and root this phone? I'm having issues on finding it, im on the newest update
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
Please, can you share what guide you used to unlock and root this phone (20p)? Can not find any complex info anywhere.
Thank you.
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
king200 said:
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
Click to expand...
Click to collapse
You can get the latest Imperium kernel (5.0 currently) from: http://forum.xda-developers.com/g4/orig-development/kernel-imperium-kernel-g4-v1-0-t3282915
Yes, fastboot boot from the twrp image was kind of a hack, but it worked. As for SuperSU, I tried v1.94 and SuperSU-v2.76-20160630161323.zip. Both soft-bricked the phone. Maybe the newest SuperSU will work, but I wouldn't count on it given that several previous versions didn't.
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
I need to flash twrp and root from 20p also. One question to clarify exactly what you did,
Did you originally try flashing TWRP from TWRP? You said you flashed root from TWRP but I want to verify if you tried flashing TWRP from TWRP like:
> adb reboot bootloader
> fastboot boot twrp-3.0.2-0-h811.img
then in TWRP:
> install click on image tab.. then select twrp-3.0.2-0-h811.img recovery and flash it.
> reboot recovery (should reboot to TWRP you just flashed)
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
emailej said:
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
Click to expand...
Click to collapse
Yes, just loads TWRP temporarily. Later I installed some apps that flashed the recovery successfully, either rashr or flashify (I don't remember which)
I hope you have all the files and pc is reading your phone in adb.
Keep the downloaded twrp file in your adb folder with dwonloaded name (Ex:1234twrp.img)
Copy the file and keep in phone internal storage with names recovery.img
adb reboot bootloader (wait for phone to boot in bootloader ofcourse)
fastboot boot 1234twrp.img (whatever your twrp img file name would be)
Now you are in twrp recovery page in the phone.
Tap Install > Images (bottom right) > select recovery.img >
Now you are in next screen where options to slect recovery or boot
Tap recovery and swipe you will see [image flash complete]
Now twrp is permeant. You can restart in recovery without PC. (Tested)
I have flashed more than 6 methods to install supersu. Keep trying and reply.
Hey guys so I'm panicking right now, so I just unlocked the bootloader, flashed TWRP and rooted my phone but now the phone won't boot it's just stuck at the boot icon with the two circles chasing each other, am I screwed and is my phone useless now ?
Don't worry, this is a common problem that occurs when you use an older version of SuperSU.
Flash SuperSU v2.79 to root. You won't even have to reflash the OS. Your phone should reboot once during the booting process.
Alternatively, you can reflash the stock OS and root with Magisk v11.1, which will also root your phone.
Anova's Origin said:
Don't worry, this is a common problem that occurs when you use an older version of SuperSU.
Flash SuperSU v2.79 to root. You won't even have to reflash the OS. You phone should reboot once during the booting process.
Alternatively, you can reflash the stock OS and root with Magisk v11.1, which will also root your phone.
Click to expand...
Click to collapse
Okay so can you tell me how to remove 2.78 before I flash 2.79 ? thanks
You don't need to remove it. Flashing the newer one should replace the older one. I had the same problem when I first rooted following a slightly outdated guide. Flashing the newest version fixed it without a problem.
Anova's Origin said:
You don't need to remove it. Flashing the newer one should replace the older one. I had the same problem when I first rooted following a slightly outdated guide. Flashing the newest version fixed it without a problem.
Click to expand...
Click to collapse
My phone isn't showing up on my pc as a removable storage and when I type adb devices my phone isn't showing up either
If you have a usb-C OTG adapter, the easiest way is to copy it onto a flash drive and flash from the drive in TWRP.
TWRP should also have a way of mounting your phone to your PC, though I've personally never managed to get it to work.
Also, I believe adb works while you're in recovery mode. You can use adb to push the superSU zip to your phone's internal storage. If you aren't sure how to use adb, the toolkit consolidates all of the useful commands together.
Anova's Origin said:
If you have a usb-C OTG adapter, the easiest way is to copy it onto a flash drive and flash from the drive in TWRP.
TWRP should also have a way of mounting your phone to your PC, though I've personally never managed to get it to work.
Also, I believe adb works while you're in recovery mode. You can use adb to push the superSU zip to your phone's internal storage. If you aren't sure how to use adb, the toolkit consolidates all of the useful commands together.
Click to expand...
Click to collapse
I managed to flash 2.79 but I don't think it worked, still stuck booting, will leave it for a few minutes though to see if anything changes, any suggestions if that wasn't the issue ?
Dirty flash whatever version of OOS you're on, wipe delvic/cache, then immediately flash SuperSU without rebooting recovery.
Anova's Origin said:
Dirty flash whatever version of OOS you're on, wipe delvic/cache, then immediately flash SuperSU without rebooting recovery.
Click to expand...
Click to collapse
I have no idea how to do any of that, I'm a beginner could you explain to me please ?
stefinho said:
I have no idea how to do any of that, I'm a beginner could you explain to me please ?
Click to expand...
Click to collapse
1) Download the full ROM of OOS from OnePlus (ignore their instructions, they are assuming that you have the stock recovery installed).
2) Transfer the full zip onto your phone.
3) Boot into TWRP
4) Find where you've put the full ROM on your internal storage and flash it
5) Once TWRP finishes flashing it, tap the "wipe dalvik/cache" button, DO NOT REBOOT (if you reboot at this point, your TWRP will be replaced with stock recovery)
6) Press back on TWRP, find your SuperSU.zip and flash that
7) Reboot
This process replaces any non-user files that may have been damaged. You won't lose any data or the apps that you have downloaded. This will replace the recovery with stock if you do not root immediately before rebooting.
Anova's Origin said:
1) Download the full ROM of OOS from OnePlus.
2) Transfer the full zip onto your phone.
3) Boot into TWRP
4) Find where you've put the full ROM on your internal storage and flash it
5) Once TWRP finishes flashing it, tap the "wipe dalvik/cache" button, DO NOT REBOOT (if you reboot at this point, your TWRP will be replaced with stock recovery)
6) Press back on TWRP, find your SuperSU.zip and flash that
7) Reboot
Click to expand...
Click to collapse
Thanks, will try that now.
Anova's Origin said:
1) Download the full ROM of OOS from OnePlus (ignore their instructions, they are assuming that you have the stock recovery installed).
2) Transfer the full zip onto your phone.
3) Boot into TWRP
4) Find where you've put the full ROM on your internal storage and flash it
5) Once TWRP finishes flashing it, tap the "wipe dalvik/cache" button, DO NOT REBOOT (if you reboot at this point, your TWRP will be replaced with stock recovery)
6) Press back on TWRP, find your SuperSU.zip and flash that
7) Reboot
This process replaces any non-user files that may have been damaged. You won't lose any data or the apps that you have downloaded. This will replace the recovery with stock if you do not root immediately before rebooting.
Click to expand...
Click to collapse
DUDE, it worked thank you so much man really appreciate the help