Database Info

[Q] TF700 bricked...?

Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!

Fastboot
pippolino123 said:
Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!
Click to expand...
Click to collapse
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??

lj50036 said:
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??
Click to expand...
Click to collapse
unfortunately not... I don't see the three icons it is stuck with the ASUS logo

nvflash
pippolino123 said:
unfortunately not... I don't see the three icons it is stuck with the ASUS logo
Click to expand...
Click to collapse
Do you have your Blob files from enabling nvflash??

lj50036 said:
Do you have your Blob files from enabling nvflash??
Click to expand...
Click to collapse
sorry don't understand what you mean. Can you please clarify. ..?

nvflash
pippolino123 said:
sorry don't understand what you mean. Can you please clarify. ..?
Click to expand...
Click to collapse
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/

lj50036 said:
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/
Click to expand...
Click to collapse
yes, I think you are right... didn't know about the nvflash stuff. Thanks either way for your help!

Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app

lj50036 said:
Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sure I will... thanks again and happy holidays

So since I feel like I have a complex problem that I can't seem to search for, I'm piggy backing this thread. It's been a year since I rooted this tablet, and I went on deployment with it. Worst ROM ever, couldn't get YouTube, WiFi was sketchy at best so I came back and it even had the OTA updater to update to a newer version, well that wouldn't load at all.
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen. So when I tried to update to this new ROM, I kept getting download faults, so I figured I was stuck with this crap ROM because basically I quit trying. Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik (I didn't save anything to this tablet, nothing to lose)
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?

First the good news:
The page with the three icons is the bootloader menu which means you should have fastboot access to your tablet from your computer.
You can use fastboot to flash a new recovery (TWRP) and once that is installed you can flash the new rom.
So this can be fixed relatively easy, but you have to do some reading before attempting it. Done correctly this is a safe procedure. Done without understanding what you are doing could leave you with a hard brick - right now you're probably just soft bricked.
s14owner95 said:
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen.
Click to expand...
Click to collapse
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik.
Click to expand...
Click to collapse
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?
Click to expand...
Click to collapse
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have to unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.

berndblb said:
First the good news:
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Click to expand...
Click to collapse
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
berndblb said:
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Click to expand...
Click to collapse
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
berndblb said:
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.
Click to expand...
Click to collapse
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery

Hope this worked

s14owner95 said:
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery
Click to expand...
Click to collapse
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???

berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?

s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
Click to expand...
Click to collapse
Mmmhh, your tablet may need a little deeper cleaning. Check out buster99's post (#12). His method has helped dozens recover from worse than you have right now.
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
His instructions are for the TF300. naturally you want to flash the blob for the TF700. That would get you back to a healthy stock system. Then you can again flash TWRP and through it a custom rom.
Good luck!
---------- Post added at 05:36 PM ---------- Previous post was at 05:28 PM ----------
s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?
Click to expand...
Click to collapse
Are you saying the twrp flash went ok?
You don't flash the rom in fastboot. You boot back into recovery, choose "Install" and select the CROMi-X zip you downloaded.
But before you do that I would seriously suggest you format your data partition. That means you have to have the downlaoded rom zip on your external card (otherwise you will erase it with the format).
So boot into TWRP, choose Wipe > Advanced > Format data
Then go back to TWRP Home, choose Install and navigate to the CromiX zip. Make sure the box "verify zip signature" is checked and flash the rom.
Do this only if you have a working recovery!!! Do not attempt with your busted one!!
You can only access the tablet in MTP (as an external drive) if your system is working. It's not - yet.

OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.

s14owner95 said:
OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.
Click to expand...
Click to collapse
To use ADB you have to be in your recovery or the Android system needs to run.
If you have a working recovery back - why do you want to mess with ADB unless you are familiar with it? You are treading on thin ice doing stuff without really understanding what you are doing! What's the rush?

The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it

s14owner95 said:
The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it
Click to expand...
Click to collapse
Your drivers are working. You need different sets of drivers for different modes: fastboot drivers, adb drivers, mtp drivers.
Your tablet shows up as a bootloader interface because it is in fastboot mode - ergo the fastboot drivers are working.
You HAVE to get a working recovery onto the tablet. It will NOT work without a recovery. To push a rom zip to the tablet is useless - the only thing working on your tablet is fastboot mode.
If the recovery flash fails, try buster99's method. That should clean all the crud off your partitions.
But you need to have the Asus firmware blob file for this! You cannot do this with any rom zip!!
Edit: You did push the correct recovery this time, did you?

Give up and go stock?

A burst of fearsome energy overtook me tonight and I just had to root my phone
Kingoroot, Kingroot, Towelroot etc didn't work. Then I read about this thing called TWRP.. sounds great, I said.
Unlocked the bootloader, got TWRP recovery going, tested it out, got ready to add SuperSU and the one that gets rid of bootloader unlocked screen.
Boot loop. Stuck on the Motorola logo. It aint going anywhere.
I've tried all of the suggestions I could find so far here, like using mfastboot to clear cache and user data. It's looking like a dead end. I was following the instructions on a youtube video so of course I didn't back up anything before I tried SuperSU Should I cut my losses and try the stock firmware, or could I do more damage that way?
This is going to ruin my weekend, isn't it?

bootloophell said:
A burst of fearsome energy overtook me tonight and I just had to root my phone
Kingoroot, Kingroot, Towelroot etc didn't work. Then I read about this thing called TWRP.. sounds great, I said.
Unlocked the bootloader, got TWRP recovery going, tested it out, got ready to add SuperSU and the one that gets rid of bootloader unlocked screen.
Boot loop. Stuck on the Motorola logo. It aint going anywhere.
I've tried all of the suggestions I could find so far here, like using mfastboot to clear cache and user data. It's looking like a dead end. I was following the instructions on a youtube video so of course I didn't back up anything before I tried SuperSU Should I cut my losses and try the stock firmware, or could I do more damage that way?
This is going to ruin my weekend, isn't it?
Click to expand...
Click to collapse
If you can still boot to your custom recovery its really not a big deal. Just install the ROM zip of your choosing and appropriate gapps. If you are boot looped when it starts to reboot just hold in the power button for about 10 seconds till it powers off then press and hold volume down while still keeping the power button pressed. After about 5 seconds or so of holding both buttons stop pressing both together. If done correctly you should be at the boofloader screen.

n0ts0smart said:
If you can still boot to your custom recovery its really not a big deal. Just install the ROM zip of your choosing and appropriate gapps. If you are boot looped when it starts to reboot just hold in the power button for about 10 seconds till it powers off then press and hold volume down while still keeping the power button pressed. After about 5 seconds or so of holding both buttons stop pressing both together. If done correctly you should be at the boofloader screen.
Click to expand...
Click to collapse
Yes, I can get to the bootloader. Factory reset there and reset using TWRP doesn't fix the bootloop. That's kinda where I am right now.

Uninstalling SuperSU did it! I used the un-su zip file.

Do you have one of the following 1)Motorola USB drivers for your PC and fastboot or mfastboot/adb setup for your device? 2)ROM zip on your internal storage. 3)A USB OTG drive? Any of these will work. Let me know which you have and we will go from there.

n0ts0smart said:
Do you have one of the following 1)Motorola USB drivers for your PC and fastboot or mfastboot/adb setup for your device? 2)ROM zip on your internal storage. 3)A USB OTG drive? Any of these will work. Let me know which you have and we will go from there.
Click to expand...
Click to collapse
It's ok, I'm back in business - the issue was the installation of the latest version of SuperSU. I used Install from SD Card in TWRP to install the SuperSU remover and it booted fine.
Taking my time now because I need this phone, I'm living in a new country. I backed up and tried an older SuperSU but didn't work - I suppose by doing a factory reset I might have done something that stops a root.
Edit: this http://forum.xda-developers.com/showpost.php?p=63615067

Download the latest stable build of super SU from Chainfires site here. http://download.chainfire.eu/supersu-stable
Then just flash the zip you downloaded in TWRP. You don't need the systemless version of SU if that is what you were trying to do.

n0ts0smart said:
Download the latest stable build of super SU from Chainfires site here. http://download.chainfire.eu/supersu-stable
Then just flash the zip you downloaded in TWRP. You don't need the systemless version of SU if that is what you were trying to do.
Click to expand...
Click to collapse
I think that was the one that bootlooped it. I'll be doing a backup first this time
My main reason for posting my solution in this thread is in case the same thing happens to someone else. Removing SuperSU with that un-su.zip solved it for me.

A Newbie’s guide to install PB1 ROM, root, unlock the bootloader and update to PF4-6

I wanted to update PB1 Lollipop to PF4-6.0 and unlock the boatloader. All that information is available on this forum in different posts, but requires some degree of back ground knowledge and is not always easy to follow for newbie’s like me. BY trial and error, and reading lot of thread postings, I was able to accomplish the goal. I am posting this guide as it may be helpful for other newbies.
BIG thank you to jrkruse, GeTex, muniz_ri, and other developers who put up lot of work. All credits go to them and I don’t claim any credit for anything.
My phone had Samsung eMMC and that is why I was able to unlock the bootloader. If your phone has Toshiba eMMC, you can’t unlock the bootloader and have to stop after rooting installing the PB1 ROM.
You can check eMMC by opening this file “/sys/block/mmcblk0/device/cid” in a root explorer app (e.g. root explorer). If the first two number start with 15, then you have Samsung eMMC. If first two numbers are 11, then you have Toshiba EMMC and your boot loader is unlockable at this time.
Another way to check eMMC is by installing eMMC Brickbug Check from the
HTML:
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en
or from
HTML:
https://apkpure.com/emmc-brickbug-check/net.vinagre.android.emmc_check/download?from=details
and then running the app.
Install PB1 ROM and then root following instructions from here
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Before Doing Anything Please Install The Latest Samsung Drivers SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe
Installing PB1
You will lose all of your app data and apps installed, your internal storage will be fine, backup is recommended anyways
1. Download G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip and unzip it
2. Reboot to recovery (Power+Volume Up+Home Button) and wipe data from recovery, reboot to bootloader
3. Plug In your phone and open Odin
3a. Make sure your phone is recognized (In the Odin Screen Under ID:COM the box under will be blue with your com port id #)
4. Click the AP button in the Odin Screen and locate and click on the G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar .md5 this is the file that was unziped from the G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip (Everything you do will be flashed via AP!!!!)
4a. This will take a few minutes for odin to load and verify MD5. When done in the odin message box it will say
5. Under options DO NOT CHANGE ANYTHING
6. Now click on Start
7. When finished you will get a green box that says PASS!
8. Phone will reboot automatically to recovery and finish updating then it will restart. It may be stuck on red Verizon screen for 10-15 minutes, so just be patient.
9. When Phone has finished loading and has booted up go through setup and do not add any google accounts or Samsung accounts or anything
OPEN DEVELOPER OPTION
Go to the settings menu on your GS5.
Scroll down to the "System section and tap "About Device."
Now scroll down to "Build number."
Tap the "Build number" section seven times. ...
Now back out to the main settings menu, and you'll see "Developer options" listed
Enable USB debugging
Uncheck “Verify apps via USB”
Go to Security
Check the box next to Unknown sources
Uncheck reactivation lock if it is checked (if you have a Samsung account click on reactivation lock enter your Samsung account and the tick should be off )
Go to Settings/Display and set your screen timeout to 5 min
Rooting Instructions
1. Download this zip GS5_LOLLIROOT_BLACKCAT.7z
2. Unzip folder.(You need a unzip application like 7z or Winrar).
ALSO COPY THIS FOLDER INTO SD CARD AND PUT IT IN THE PHONE
3. Open The Folder and click Bat file #1, “Install APKs” plug in your phone
On Allow USB debug message, check always allow this computer and click OK
Then follow directions
It will install APKs and then boot into bootloader “Downloading” and odin will open
Flash NK2_kernel.tar I AP slot
The phone will reboot get stuck on Samsung screen
Wait for the phone to reconnect
Press Enter flashing is complete to the root process can start
All the Steps for the main rooting process are done ON THE BAT FILES, READ THEM!!!!
If the root process hangs Close the bat, unplug phone pull battery and reboot phone to recovery (VolUp+Pwr+Home). In recovery wipe cache only and reboot. If phone reboots back to recovery instead, pull battery and manually reboot. Now Launch Bat #3 and then plug phone back in and
IF you get into android and cannot get root, Open bat file #2 and start from there again
If your phone wont reboot, use Bat #4 and try and enter download mode manually(VolDown+Pwr+Home)
When root is finished, pull your battery on your phone. Replace battery and reboot to download mode Power+Volume Down+Home
Use odin and Flash the VZW_BPB1_KERNEL_ONLY.tar.md5 Kernel through AP
IF STILL HAVING ISSUES RUNNING THE BAT FILES, REINSTALL PB1 THRU ODIN AND RESTART FROM SCRACTH
When phone reboots, go to the GS5_LOLLIROOT_BLACKCAT folder you placed on your phone
Open KRoot.apk and install it. Once installed open Kroot. Click The Up Arrows a couple of time until you get to Try It and click Try It and that's it. Don’t click nothing else just close Kingroot. You should now have root. If It says Root not available and the bat said your were rooted Reboot Phone and open KingRoot You should now be rooted (otherwise reboot phone and check again)
Now go to google play and install SuperSU-Me pro app (I purchased this app). Run it to remove kinguser and replace it with SuperSu. After this process open SuperSu and will ask to update binary click update normal
Copy this G900V_Fix Safestrap.zip (It may come in handy later on) to your SD Card and Internal Storage Copy Safestrap_Flashable_Kernels and Safestrap_Flashable_Firmware and anything else you want to install like the below rom
Now go to the folder on your SD card and open Busybox.apk Installer Allow SuperSu permission click on install.
After you get message about successful install, Click on Safstrap Allow SuperSu permission then click Install Safestrap after it installs, click open Safestrap and click on install/update recovery. After it is installed, click on “Reboot To Recovery”.
Make a backup of existing Rom In safestrap
Unlocking Boot Loader
Unlock the Galaxys S5 Bootloader using DEV Bootloader by Method 2
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
Remove the phone’s SD card. Either back up all the files on the card to your computer or use another empty sd card as unlocker will wipe everything on the SD card during the process.
Copy Samsung_Bootloader_Unlocker.zip on to the card
Power off the phone and insert the sd card. Reboot the phone. Then Reboot into Safstrap by opening LP Safestrap Installer and clicking on “Reboot to Recovery”
Once into the Safestarp, install the Unlocker.
Reboot system when you get the Successful message
You will see a brief “Android is upgrading” screen
click on SamsungUnlocker app
Wait and make sure to grant SuperSu access. This may take a few seconds to come up
type yes in the terminal screen when it ask you (Yes/No) Hit enter on the keyboard
wait for phone to power off
reboot to bootloader (Power off phone, then press VolDwn+Pwr+Home and keep pressing till you see the bootloader, press then volume up) and verify it says MODE: Developer
While phone is still on the Bootloader" or "download mode, connect phone to computer thru USB and start Odin and flash Twrp recovery using Odin AP. Use TWRP 3.0.0. as newer versions have difficulty accessing the sd card. You can down load TWRP 3.0.0 for ODIN from https://dl.twrp.me/klte/twrp-3.0.0-0...e.img.tar.html
Reboot
Note: To re-use the sd card used for unlocking, format your SDcard in android OS, otherwise, use a Linux box and a card reader and use FDISK to wipe all the partitions, then it can be formatted correctly
Now copy following files on to the sdcard
-G900V_PF4_Stock_Deodexed_Debloated_Rooted_ROM.zip (For "Unlocked" Bootloaders Only!)
-TWRP_Prepare.zip
-PB1_Firmware_Only_NK2_Kernel.tar.md5
-S5_KLTE_USA_VZW.pit
-SafeStrap_PF4_Bootloader_Unlock_AIO.zip
MARSHMALLOW PF4-6.0.1 INSTALLATION
http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
From the above thread, flash G900V_PF4_Stock_Deodexed_Debloated_Rooted_ROM.zip (For "Unlocked" Bootloaders Only!)
Reboot into TWRP by pressing the volUp+home+power button and release all the buttons as soon as you seen the initial few lines on top left of screen
Click Wipe then Click Advanced Wipe Then select System, Data, Cache. Then swipe to start wipe
Press Back button
Now flash the above ROM thru TWRP's Install button and then reboot
Phone will hang at the Verizon red screen
NOW FOLLOW INSTRUCTIONS FROM “If You Already Have Bootloader Unlocked And On A Samsung TW Rom” section of this thread
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
Reboot into TWRP by pressing the volUp+home+power button and release all the buttons as soon as you seen the initial few lines on top of screen (If you reboot into android recovery, choose Reboot to bootloader and then reinstall TRWP thru Odin AP)
In TWRP Flash TWRP_Prepare.zip
Reboot system
It will reboot in to safstrap recovery (watch carefully as Safestrap Splash Screen is visible only for few seconds and then disappears – Choose recovery on the left side of the splash screen)
From safestrap, choose Reboot > Download
In Odin Under AP slot load PB1_Firmware_Only_NK2_Kernel.tar.md5
In Odin Under PIT load S5_KLTE_USA_VZW.pit
When finished on reboot watch for Safestrap Splash Screen and enter Safestrap (watch carefully as Safestrap Splash Screen is visible only for few seconds and then disappears)
Now go to Reboot Menu and click on Download Mode
Make sure in download mode the current binary is Samsung Official. If it says custom, repeat the above step till it shows Current Binary: Samsung official.
If Binary Status is Official Pull battery, restart and enter SafeStrap by choosing Recovery on the left side of the splash screen (DON’T press any buttons till you see safstrap screen and then enter)
Install: SafeStrap_PF4_Bootloader_Unlock_AIO.zip
Phone will Power Off.
Pull remove battery and then place it back
This process installs TWRP 3.2 which doesn't see the SD card. Hence, now we need to install TWRP 3.0.0
Reboot into TWRP by pressing the volUp+home+power button and release all the buttons as soon as you seen the initial few lines on top of screen. Click on Reboot and then Download button. When phone boots into Download mode, reflash TWRP 3.0.0 via ODIN AP
When phone reboots, It may be stuck on Verizon red screen for 10-15 minutes, just be patient.
That's it, you will now have on a rooted/unlocked PF4
2017-01-10: Edited the guide to make it simpler.
Sorry for not being able to answer questions in this thread as I have a very limited knowledge of this whole process.

Great job!
This works*.
I just finished the process of researching everything and installing most things based on the many different threads people vaguely pointed to.
It's nice to see someone compile it all together in one spot.
I previously had to reinstall the full PB1 restore image several times because I had gotten stuck along the way a few times.
The main thing I took from you that was different from other guides was that I installed PF4 from TWRP instead of FlashFire, maybe that helped things work.
*Some tips/modifications based on what I did based on other guides and now partially yours for the last few steps that worked just now:
1. The part where you install G900V_Fix Safestrap.zip and then Install PB1 ROM (VZW_BPB1_ODEX_DEODEX_V9.zip) is unnecessary.
So in other words, after Knox_Removal_SU_BB_INIT.D.zip, skip straight to unlocking Bootloader.
2. After unlocking the bootloader and reformatting the SD card, I'd suggest copying over all the remaining zip files you need for the rest of the tutorial to your device... that way you don't need to take out the microSD card and find a microSD reader.
3. I can't remember for sure, but I think after installing the PF4 ROM (I used G900V_PF4_Stock_Rooted_ROM.zip (For "Unlocked" Bootloaders Only!)), I had to reinstall TWRP 3.0.0 from ODIN.
4. Here's the link to TWRP 3.0.0 for ODIN https://dl.twrp.me/klte/twrp-3.0.0-0-klte-klte.img.tar.html
Those are all the suggestions I can remember. Great guide!

Royal2000H said:
Great job!
This works*.
I just finished the process of researching everything and installing most things based on the many different threads people vaguely pointed to.
It's nice to see someone compile it all together in one spot.
I previously had to reinstall the full PB1 restore image several times because I had gotten stuck along the way a few times.
The main thing I took from you that was different from other guides was that I installed PF4 from TWRP instead of FlashFire, maybe that helped things work.
*Some tips/modifications based on what I did based on other guides and now partially yours for the last few steps that worked just now:
1. The part where you install G900V_Fix Safestrap.zip and then Install PB1 ROM (VZW_BPB1_ODEX_DEODEX_V9.zip) is unnecessary.
So in other words, after Knox_Removal_SU_BB_INIT.D.zip, skip straight to unlocking Bootloader.
2. After unlocking the bootloader and reformatting the SD card, I'd suggest copying over all the remaining zip files you need for the rest of the tutorial to your device... that way you don't need to take out the microSD card and find a microSD reader.
3. I can't remember for sure, but I think after installing the PF4 ROM (I used G900V_PF4_Stock_Rooted_ROM.zip (For "Unlocked" Bootloaders Only!)), I had to reinstall TWRP 3.0.0 from ODIN.
4. Here's the link to TWRP 3.0.0 for ODIN https://dl.twrp.me/klte/twrp-3.0.0-0-klte-klte.img.tar.html
Those are all the suggestions I can remember. Great guide!
Click to expand...
Click to collapse
In retrospect, you are right that I did not need to install PB1 ROM (VZW_BPB1_ODEX_DEODEX_V9.zip). So removed that part. also made other changes as suggested.
Thank you!

mms2020 said:
In retrospect, you are right that I did not need to install PB1 ROM (VZW_BPB1_ODEX_DEODEX_V9.zip). So removed that part. also made other changes as suggested.
Thank you!
Click to expand...
Click to collapse
Great! Just a few more suggestions:
1. I think the part with "Once phone reboots, GO BACK TO PHONE AND CHANGE FOLLOWING SETTINGS " (basically the whole part about reenabling developer options and enabling USB debugging) is unnecessary and can be deleted because you deleted the part about installing that second ROM so all that should still be enabled.
2. I'd move the link to TWRP for ODIN from the bottom to right after the first time you mention TWRP (the line that starts with: While phone is still on the Bootloader" or "download mode, connect....)
3. What I meant in my previous reply was that I think flashing PF4 wiped TWRP, so in order to reboot to TWRP right after you install PF4, you need the user to reinstall TWRP from ODIN (right before/after this line: NOW FOLLOW INSTRUCTIONS FROM “If You Already Have...)

Royal2000H said:
Great! Just a few more suggestions:
1. I think the part with "Once phone reboots, GO BACK TO PHONE AND CHANGE FOLLOWING SETTINGS " (basically the whole part about reenabling developer options and enabling USB debugging) is unnecessary and can be deleted because you deleted the part about installing that second ROM so all that should still be enabled.
2. I'd move the link to TWRP for ODIN from the bottom to right after the first time you mention TWRP (the line that starts with: While phone is still on the Bootloader" or "download mode, connect....)
3. What I meant in my previous reply was that I think flashing PF4 wiped TWRP, so in order to reboot to TWRP right after you install PF4, you need the user to reinstall TWRP from ODIN (right before/after this line: NOW FOLLOW INSTRUCTIONS FROM “If You Already Have...)
Click to expand...
Click to collapse
Made those changes as well. If I remember correctly, I did not need to reflash TWRP after PF4 installation as it was flashed through the TWRP. Thanks

Great thread!
If I unlock the bootloader, do I still need to flash a new kernel from pb1 lollipop to a marshmallow kernel if I want to flash a marshmallow based rom on there? Particularly CM 13.

Nice!
If I want to flash cyanogen mod 13 do I do it after I flash the bootloader unlock & twrp, or do I have to flash SafeStrap_PB1_Bootloader_Unlock_AIO.zip first?

Thanks for this thread, OP.
I know a ton of work went into the methods explained in the threads used to create this newbie guide, but it can be difficult to follow those information dense threads for those of us who only get into rooting and flashing every couple of years with a new phone.
Sucks that Google and Verizon are making this more difficult. I fondly recall one click rooting!
They lock down the phones and load up the bloatware and if you aren't tech savvy enough to get around their locks (or just tech savvy enough to be able to follow an XDA how to thread), then you're almost forced into buying a 32gb phone so that you don't run out of memory when you start installing apps you actually want rather than the bloatware they prepackage.
I am blown away by how much bloatware has been removed from this debloated PF4.

Trying real hard
t-wrench said:
Thanks for this thread, OP.
I know a ton of work went into the methods explained in the threads used to create this newbie guide, but it can be difficult to follow those information dense threads for those of us who only get into rooting and flashing every couple of years with a new phone.
Sucks that Google and Verizon are making this more difficult. I fondly recall one click rooting!
They lock down the phones and load up the bloatware and if you aren't tech savvy enough to get around their locks (or just tech savvy enough to be able to follow an XDA how to thread), then you're almost forced into buying a 32gb phone so that you don't run out of memory when you start installing apps you actually want rather than the bloatware they prepackage.
I am blown away by how much bloatware has been removed from this debloated PF4.
Click to expand...
Click to collapse
Hi Guys, Well after much trying I have my phone rooted and the bootloader unlocked. Do I have to load the PF4 or can I continue to use it as it is. Or may I use a debloated PB1 rom? Thanks

Thumbmasher said:
Hi Guys, Well after much trying I have my phone rooted and the bootloader unlocked. Do I have to load the PF4 or can I continue to use it as it is. Or may I use a debloated PB1 rom? Thanks
Click to expand...
Click to collapse
You can use it as is.
But since you did all this work, might as well upgrade to Marshmallow.

t-wrench said:
You can use it as is.
But since you did all this work, might as well upgrade to Marshmallow.
Click to expand...
Click to collapse
I am afraid of loosing my work. It took all day. Can I flash 5.0 roms now? Like this one?
http://forum.xda-developers.com/verizon-galaxy-s5/development/vzwstock-based-tw-rom-3-4-16-t3329029

Thumbmasher said:
I am afraid of loosing my work. It took all day. Can I flash 5.0 roms now? Like this one?
http://forum.xda-developers.com/verizon-galaxy-s5/development/vzwstock-based-tw-rom-3-4-16-t3329029
Click to expand...
Click to collapse
I'm not sure on exactly what you can flash. I followed this newbie guide and it worked fine. Hopefully someone else can chime in.
As for loosing your work, if you followed the guide to unlocking the bootloader, you now have TWRP recovery. So make a backup, and store it on the microSD, or even safer yet, copy it from the microSD to another drive. If you screw things up, just use TWRP to restore the backup. Even if accidentally wipe the microSD, you'll still have that backup preserved off the phone.

Well, I had the (joy) of working on my mom's S5 VZW today. It was only running KK, so I got it rooted and bootloader unlocked OK,installed TWRP fine, but I tried flashing CM 14.1 (I had the 12/24 nightly downloaded before the servers all shutdown) and after 20 minutes it still wasn't getting past the CM logo. I'm used to these things taking a while, but 20 minutes is way too long. I'm currently downloading the PJ2 Stock Rooted Debloated rom to try from TWRP instead, since I can't download CM13 thanks to the whole CM/Lineage split.
For what it's worth, in the directions above, after flashing G900V_PF4_Stock_Deodexed_Debloated_Rooted_ROM.zip, I did have to reflash TWRP with Odin (someone else mentioned this, too). The directions at that step were unclear; did I need to let that boot all the way up, and if so, how long should I wait, since this is a Deodexed ROM I know it could take like 15 minutes, but it still wasn't booting after 20. So I just did a battery pull, reflashed TWRP, and proceeded to install the remaining zips as instructed.
While in TWRP, I can't make a backup to the external SD card; maybe it's mounted read-only? I can backup to the internal sdcard, which is OK if I ever get it booted up to any OS where I can use a file manager or transfer to PC.
Still, these directions were very helpful, hoping I can get this thing running in the next hour or so... I have to leave tomorrow!

Not sure if @mms2020 is still reading this, but in the SamsungUnlocker app, it seems that "Yes" is case sensitive. When I typed 'yes', the phone immediately powered off and subsequent reboot into bootloader does NOT show mode Developer and Odin flashing of TWRP 3.0.0 fails. I repeated and typed "Yes", then app generates a few more lines on screen, then phone powers down. Now bootloader shows mode Developer and Odin flashing of TWRP 3.0.0 succeeds.

Thanks for the guide it was actually quite straight forward to follow. I have a ok3 verizon s5 rooted w/ twrp installed and bootloader unlocked. Having never dealt with verizon or samsung phones before. What do I have to do to upgrade to a nougat CM14 rom? (i'm mainly concerned with connectivity issues). Since twrp is installed can I just install a cm14 image? (full wipe and all).

Thanks for the guide! :good:

I'm on lollipop, rooted, unlocked bootloader, I want to upgrade to marshmallow and keep twrp, so I don't need to install safestrap do I?
Sent from my SM-G928F using XDA-Developers Legacy app

I followed the steps a few days ago, it went perfectly. The root, the bootloader unlock, and the Marshmallow upgrade was all so easy! Nothing like my Note 4. I had to do all the work for that phone. This phone has it easy. It's all done for the users already. All I needed was a computer, with adb, common sense, and the ability to read lol. Anyways I'm on the Nemesis N7 international port and my phone is flying on this rom!! Couldn't be happier with my Now.... what....3 year old S5!
Sent from my SM-G903F using XDA-Developers Legacy app

Thanks for this. I wonder if this is normal, SuperSU-Me pro is stuck in processing for a long time. Is there a trick to it?
Thanks for any replies, Tom

thoughto said:
Thanks for this. I wonder if this is normal, SuperSU-Me pro is stuck in processing for a long time. Is there a trick to it?
Thanks for any replies, Tom
Click to expand...
Click to collapse
Try a different version
And no, it shouldn't take long at all. There is 2 steps though. And it will guide u through the steps. Or should anyway.
Sent from my SM-G903F using XDA-Developers Legacy app

Wileyfox Spark X

Hi all,
This is not the right forum, but I didn't see one specifically for Spark X models, so I'm sorry.
A friend of mine has a Wileyfox Spark X device, which was bootloader unlocked, had TWRP 3.0.2 installed and was running on the original firmware (6.0.1) but rooted and xposed installed.
Now an update came out for Android 7. To update the device, I put back the original firmware and recovery, started doing the upgrades and all went smooth.
Device is up and running on Android 7, however when I now try to install TWRP again, it won't work.
(fastboot flash the TWRP recovery (same version as before - 3.0.2) seems to work ok. I then go to pull the battery after flashing, put battery back, and start recovery by pressing vol down and power.
I see the device going to a black screen, then reboot and keeps doing this as long as I keep the vol down pressed. Once I release the device continues normal boot and goes into Android.
I assume this has to do with a change in Android 7?
Seems I can get TWRP working again, if I flash the original boot image, however then ofcourse the Android boot doesn't work anymore. (additionally once in TWRP, it seems /system cannot be mounted anymore and TWRP thinks no system is installed)
So in short, I believe I should get a newer TWRP version that is compatible with Android 7. I tried the different versions available on twrp.me (up to 3.1.1.0) however to no avail. None works with the latest android.
As such, the device is able to run in android 7, but without root. (no adb root option in developer options, adb root doesn't work either, kingroot etc also no go)
Does anyone have any options that I can still try? or could help me with a proper TWRP version that should work? (I did find some TWRP recoveries on 4pda (russian website) for Spark + that claim to be for Android 7, but those didn't work either))
Thanks !

@Asansi
I'm sorry I can't help you, but may I ask how you rooted the phone? I can't get mine to be properly rooted.

I can help you with any problem. I'm a senior person in that model since I have been using it ever since. If you could like
Sent from my Wileyfox Spark using XDA

HackerAce said:
I can help you with any problem. I'm a senior person in that model since I have been using it ever since. If you could like
Sent from my Wileyfox Spark using XDA
Click to expand...
Click to collapse
Apologies for ressurecring a zombie thread but, OP has a spark X and you have a Spark, so it would appear that you SENIOR person in that model failed at the very first hurdle.
Am still wonderng if there is an sign of a 7.0 compatible twrp for spark X? Don't suppose anyone has a link to the latest Spark X firmware either?

TWRP versions
Asansi said:
Hi all,
This is not the right forum, but I didn't see one specifically for Spark X models, so I'm sorry.
A friend of mine has a Wileyfox Spark X device, which was bootloader unlocked, had TWRP 3.0.2 installed and was running on the original firmware (6.0.1) but rooted and xposed installed.
Now an update came out for Android 7. To update the device, I put back the original firmware and recovery, started doing the upgrades and all went smooth.
Device is up and running on Android 7, however when I now try to install TWRP again, it won't work.
(fastboot flash the TWRP recovery (same version as before - 3.0.2) seems to work ok. I then go to pull the battery after flashing, put battery back, and start recovery by pressing vol down and power.
I see the device going to a black screen, then reboot and keeps doing this as long as I keep the vol down pressed. Once I release the device continues normal boot and goes into Android.
I assume this has to do with a change in Android 7?
Seems I can get TWRP working again, if I flash the original boot image, however then ofcourse the Android boot doesn't work anymore. (additionally once in TWRP, it seems /system cannot be mounted anymore and TWRP thinks no system is installed)
So in short, I believe I should get a newer TWRP version that is compatible with Android 7. I tried the different versions available on twrp.me (up to 3.1.1.0) however to no avail. None works with the latest android.
As such, the device is able to run in android 7, but without root. (no adb root option in developer options, adb root doesn't work either, kingroot etc also no go)
Does anyone have any options that I can still try? or could help me with a proper TWRP version that should work? (I did find some TWRP recoveries on 4pda (russian website) for Spark + that claim to be for Android 7, but those didn't work either))
Thanks !
Click to expand...
Click to collapse
I've tried TWRP 3.0.2-0 (i.e. latest from https://dl.twrp.me/porridgek3/): it flashes Ok but it won't boot up afterwards. I've tried 3.0.2-0 but as you say "it seems /system cannot be mounted anymore and TWRP thinks no system is installed)". After letting it finish, Root Checker (not unsurprisingly) says that device is not rooted. Have you progressed with this issue? BTW I've emailed TWRP Support (from their web page) asking if they have a working version.

Same problem here, It's pretty annoying. My sister's getting this same phone (on Android 6) soon so I might just make a full backup with TWRP on it and somehow restore it on my phone.

Systemless Root
I can't decide whether to try the rooting method given in https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung
The method is:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Has anyone had experience of this method?

Resurrection! This post shall LIIIIVE!
No, seriously tho, does anyone have any updates on the issue? Or could at least point me in the right direction to root a Wileyfox Spark X? At this point, any help is much appreciated, since I have not been able to get ANY method working for me.
Thanks a lot
Sent from my Wileyfox Spark X using XDA Labs

Systemless Root
ScreamingSteve said:
Resurrection! This post shall LIIIIVE!
No, seriously tho, does anyone have any updates on the issue? Or could at least point me in the right direction to root a Wileyfox Spark X? At this point, any help is much appreciated, since I have not been able to get ANY method working for me.
Thanks a lot
Sent from my Wileyfox Spark X using XDA Labs
Click to expand...
Click to collapse
Steve,
Have you tried the method detailed in post #7?

johnaaronrose said:
Steve,
Have you tried the method detailed in post #7?
Click to expand...
Click to collapse
I am afraid not, since I can't install TWRP. One info would help me out a lot tho: would an Android-Downgrade (from 7.0 to CM13) help with installing TWRP and rooting?
Steps taken earlier:
quite literally everything (that would make sense even remotely)
Steps taken today:
- Downloading TWRP 3.2.1-0 (https://twrp.me/wileyfox/wileyfoxsparkx.html)
- fastboot-unlocking the bootloader (no issues)
- trying to install TWRP (no issues there either)
- when trying to reboot straight to recovery, I don't get past the bootlogo, suggesting to me that either the install or TWRP was corrupted.
Any help one might get?
Thanks a lot?

TWRP
ScreamingSteve said:
I am afraid not, since I can't install TWRP. One info would help me out a lot tho: would an Android-Downgrade (from 7.0 to CM13) help with installing TWRP and rooting?
Steps taken earlier:
quite literally everything (that would make sense even remotely)
Steps taken today:
- Downloading TWRP 3.2.1-0 (https://twrp.me/wileyfox/wileyfoxsparkx.html)
- fastboot-unlocking the bootloader (no issues)
- trying to install TWRP (no issues there either)
- when trying to reboot straight to recovery, I don't get past the bootlogo, suggesting to me that either the install or TWRP was corrupted.
Any help one might get?
Thanks a lot?
Click to expand...
Click to collapse
The only version that I had success with was 3.0.2 from https://dl.twrp.me/porridgek3/"]https://dl.twrp.me/porridgek3/[/URL]
Even then, It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. still in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu.
AlwaysLivid suggested that you can boot to TWRP by executing "fastboot boot recovery.img" (where recovery.img is the TWRP img file renamed) on MSDOS Prompt / Terminal according to whether you're using Windows or a Linux distro (e.g. Ubuntu which I use). Presumably this would be after you have taken the battery out for a few seconds before inserting it again and have then booted into the appropriate mode with the Volume Down & Power buttons held down.

johnaaronrose said:
The only version that I had success with was 3.0.2 from https://dl.twrp.me/porridgek3/"]https://dl.twrp.me/porridgek3/[/URL]
Even then, It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. still in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu.
AlwaysLivid suggested that you can boot to TWRP by executing "fastboot boot recovery.img" (where recovery.img is the TWRP img file renamed) on MSDOS Prompt / Terminal according to whether you're using Windows or a Linux distro (e.g. Ubuntu which I use). Presumably this would be after you have taken the battery out for a few seconds before inserting it again and have then booted into the appropriate mode with the Volume Down & Power buttons held down.
Click to expand...
Click to collapse
Thanks a lot, I'll try your method, the explicit call to boot the TWRP image could really help.
Thanks for your extended explanation tho, showed me some new ways to eventually get this stuff to work.
Sent from my Wileyfox Spark X using XDA Labs

johnaaronrose said:
I can't decide whether to try the rooting method given in https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung
The method is:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Has anyone had experience of this method?
Click to expand...
Click to collapse
Finally, your advice with "Fastboot boot twrp.img" worked magic!
Got twrp installed, but now I'm facing the same problem as you with the systemless root. I'll dig around a little and see what I can find.

I need help. I relocked my bootloader, and now my phone (OP7P) won't even turn on

So over the past day I had rooted my oneplus 7 pro and all was going well until I decided to delete the netflix stock application. Then I restarted my phone from holding the power button and pressing restart and then I booted into fastboot. Everytime I pressed start it would send me back to fastboot but I was able go to twrp recovery. Stupidly, I wiped the whole phone thinking I had no other options. Then after that, I found a setting in advanced that allowed me to leave recovery mode I think? Whatever it was, I was booted back into the oneplus start screen and reset up my phone. Then I tried to re-root my phone and couldn't get it to work because it said the magisk zip file was corrupt. Then I just decided to give up and go back to stock.
Little did I no, you are NOT supposed to relock the bootloader, because that is exactly what I did. After doing that, I got a message saying my phone was corrupt and I looked up quick solution and it said to press my volume buttons and power buttons. Now my phone won't even turn on. I am freaking out right now, knowing that my phone is probably bricked and I am going to have to pay probably a third of what I even paid for this phone to get it fixed. When I plug my phone into my pc the device is shown as "QUSB_BULK_CID:0404_SN:3BB285D7". If any of you guys can help, I'm all ears.
edit: I meant I locked oem/bootloader. Also, I got the phone to power on. It is in a bootloop where the oneplus logo shows up and then it gives me the message "Your device is corrupt. it can't be trusted and will not boot"
edit 2: After two hours, I finally fixed it. I downloaded the MSM tool and found the qualcomm drivers and after a few trial and errors, I finally got it to work

gotdiamonds99 said:
So over the past day I had rooted my oneplus 7 pro and all was going well until I decided to delete the netflix stock application. Then I restarted my phone from holding the power button and pressing restart and then I booted into fastboot. Everytime I pressed start it would send me back to fastboot but I was able go to twrp recovery. Stupidly, I wiped the whole phone thinking I had no other options. Then after that, I found a setting in advanced that allowed me to leave recovery mode I think? Whatever it was, I was booted back into the oneplus start screen and reset up my phone. Then I tried to re-root my phone and couldn't get it to work because it said the magisk zip file was corrupt. Then I just decided to give up and go back to stock.
Little did I no, you are NOT supposed to relock the bootloader, because that is exactly what I did. After doing that, I got a message saying my phone was corrupt and I looked up quick solution and it said to press my volume buttons and power buttons. Now my phone won't even turn on. I am freaking out right now, knowing that my phone is probably bricked and I am going to have to pay probably a third of what I even paid for this phone to get it fixed. When I plug my phone into my pc the device is shown as "QUSB_BULK_CID:0404_SN:3BB285D7". If any of you guys can help, I'm all ears.
edit: I meant I locked oem/bootloader. Also, I got the phone to power on. It is in a bootloop where the oneplus logo shows up and then it gives me the message "Your device is corrupt. it can't be trusted and will not boot"
edit 2: After two hours, I finally fixed it. I downloaded the MSM tool and found the qualcomm drivers and after a few trial and errors, I finally got it to work
Click to expand...
Click to collapse
U probably should have flashed stock firmware before relocking the bootloader

As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.

cuNezzar said:
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
Click to expand...
Click to collapse
OK here's the order. Boot into twrp, don't flash.
Wipe -> ADVANCED -- select system + vendor -> SWIPE TO WIPE
reboot bootloader
fastboot boot back into twrp
-- then --
Format data, Wipe cache & dalvik-cache
Flash ROM.
Then reboot system. Boom.
Remember you will most likely have to flash the ROM via sideload. As transferring will not work in a bricked phone.

cuNezzar said:
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
Click to expand...
Click to collapse
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root

Austinredstoner said:
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Click to expand...
Click to collapse
Austinredstoner said:
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Click to expand...
Click to collapse
Damn forgot about that. Yeah In that case its most likely bricked to hell OP with no method of recovery as far as I know.