Database Users

[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020T only)

GRH78
Bootloader v.JK1
Baseband v.JK8
Yes, there are tons of guides out there, and even one click scripts that can ROOT the SNS (Samsung Nexus S) for you, but none of them go into enough detail for any of them to work properly.
Having many android devices working properly via ADB on your computer doesn't automatically guarantees it will see the SNS.
So, before jump to the exiting stuff of ROOTing the SNS, lets cover some basics to actually get you started and make sure you can actually ROOT the SNS, else all is in vain.
MOD EDIT: This guide does not apply to the AT&T/Rogers/Telus variants of the Nexus S (i9020A). For those models, please refer to this guide.
Part 1
Download Android SDK release 13 click the file name android-sdk_r13-windows.zip (34 MB) direct from Google, instead of wasting your time jumping through hoops and dodging pop up/flash ADs from those FileSharing places.
Note: from SDK release 14 onward, Google removed the fastboot command, you'll have to maker the fastboot command yourself if you want to use the latest version of the SDK
Turn Off your SNS
Make sure the SNS is connected to the PC via the USB cable
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it reads LOCK STATE - LOCKED
open Device Manager (or run devmgmt.msc) make sure you don't see this problem (windows failed to identify the SNS and install the correct drivers)
Do a right click and select Update Driver Software
Select Brose my computer for driver software
point it to where you downloaded the Android SDK (..\android-sdk-windows\google-usb_driver)
Make sure to CLICK "Let me pick from a list of device drivers on my computer"
Then from the list 3 choices select Android Bootloader Interface
If it's installed properly it should show up like this (reboot is not required)
NOTE: if you encounter problems like question marks, unknown drivers, or exclamation marks eve after you have installed the drivers, download and try the USBDeview 32/64 to remove and uninstall all the junk USB devices from your computer/registry​
Now that the basic preparations are done, we can finally get to have fun with the SNS & hack away via ADB.exe / FASTBOOT.exe
Part 2
open a command prompt go to run & type CMD hit enter
switch to the directory where you downloaded & unzipped the ..\android-sdk-windows\tools
type fastboot oem unlock and hit enter
Then you will get this
Code:
fastboot oem unlock
...
meanwhile on the SNS you'll see this screen
selecting YES will wipe EVERYTHING from the SNS, so make sure you have backed up everything you needed to safe before you continue.
use the Volume up/down keys to select and Power key to apply
you should see something like this after it's done
Code:
... OKAY [435.433s]
finished. total time: 435.433s
now back on this screen you should read
LOCK STATE - UNLOCKED
Download the clockwork recovery recovery-clockwork-5.0.2.0-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type fastboot flash recovery recovery.img and hit enter
you should get something like this, if not your image is corrupted, download it again
Code:
sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS
...meanwhile the SNS is rebooting Download superuser from http://forum.xda-developers.com/showthread.php?t=682828
choose the Eclair/Froyo version
Mount the USB storage
droidmage said:
So all you guys who are having trouble getting root inside the rom, When your in recovery before you flash the superuser.zip file select -- mounts and storage -- then --mount /system -- then flash the .zip file and reboot
Click to expand...
Click to collapse
drag/drop the su-version#-signed.zip file into the root of the internal SD of the SNS
Power Off the SNS
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
select Recovery
then it should boot into this screen, if not then repeat the steps to download the image
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
done!
Enjoy your unlocked & rooted phone!

NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
To simplify things with the Command Line, it's best to copy and paste the contents inside ..\android-sdk-windows\platform-tools to ..\android-sdk-windows\tools
that way you'll have all the necessary files in the same location to prevent errors
MIRROR:
since CW website seems to be down, here's a mirror for the Image file.
download the 7zip attachment, unzip and flash recovery.img (recovery-clockwork-5.0.2.0-crespo.img)

Good guide but i have a question,
didn't you miss the step about renaming the install-recovery.sh script
that reflash recovery if crc is wrong?

Thank you sir, I was hoping for a good step-by-step guide for us first-timers.

Nice guide.
The only thing that's making me hesitate to do root on my NS is reversing the whole process...
stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...
I'll wait until google releases a firmware that contains everything

Cubfan185 said:
Thank you sir, I was hoping for a good step-by-step guide for us first-timers.
Click to expand...
Click to collapse
thank you, that was the idea.
many of the GUIDEs we have here are usually aimed at people that already knows what to do, which usually leaves out all the 1st time owners of the phone.

it's fairly simple, the instructions are as simple as this
http://forum.xda-developers.com/showthread.php?t=884097
and you can choose any stock ROM to flash back
sinatosk said:
Nice guide.
The only thing that's making me hesitate to do root on my NS is reversing the whole process...
stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...
I'll wait until google releases a firmware that contains everything
Click to expand...
Click to collapse

Alright, just did it successfully. I had a few problems when installing the SDK and using fastboot. The recovery image must have been corrupt a few times for me. I had to take the battery out because it was stuck at the Google screen. My heart skipped a beat at that point, I didn't want to brick anything. Also had to put a required .dll file in the tools directory and the drivers were giving me problems, but got it all figured out. Thanks again.
Edit: Any reason why root required apps are saying they don't have root access?

Will Google definatly release a full restore firmware of the current ROMS, something simular to an HTC RUU, or is it just something we're hoping they'll do?

silly question... which fastboot binary did you use? the one from the htc developer site?

onicrom said:
silly question... which fastboot binary did you use? the one from the htc developer site?
Click to expand...
Click to collapse
it is included in the Android SDK 2.3 ... read the step by step guide again

Great guide, I'm new to the SDK and adb and fastboot so this helped a lot. My phone crashed last night and I had to completely restore it. Biggest upset is I was racing my girlfriend to beat Angry Birds Seasons and now my save games are gone. Along with other app data and all my settings.
So the Nexus S is stock what I root phones to get to. I love the pure Google experience. Never had one completely crap out crash though.
I followed your guide to the tee and got it what I thought would be rooted. When I get to the end though I boot up and the ClockworkMod ROM Manager v3.0.0.2 says "You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Also Superuser app says there is an update available, then tries to install and says it can't. So it puts the update zip on my root of my storage. I boot into CMR and try to install that and it errors saying it's not there. But it is when I look is mass storage mode from my computer.
I boot into clockwork mod recovery just like your guide says the bootloader says unlocked. I don't get it. What did I miss? Only reason I want to root is to use Titanium backup. I really wish google had a better backup system for app data but they don't... yet. So I don't want what happened last night to happen again.
Thanks in advance,
JB
Nexus S, stock rom just want root access for backup.

AllGamer said:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
Click to expand...
Click to collapse
Hmmm I miss this post. Does this happen with 2.3.1 aswell and root will still be on after reboot?
If so. I'm rooting RIGHT NOW!!!
Thank-you
edit: I did some searching and found the answer ... there is a file at "/etc/install-recovery.sh". that restores your recovery back to stock upon reboot while still retaining root ( 2.3 and 2.3.1 ). As stated previously... you simply re-flash the recovery to get to the recovery again

sinatosk said:
Hmmm I miss this post. Does this happen with 2.3.1 aswell and root will still be on after reboot?
If so. I'm rooting RIGHT NOW!!!
Thank-you
edit: I did some searching and found the answer ... there is a file at "/etc/install-recovery.sh". that restores your recovery back to stock upon reboot while still retaining root ( 2.3 and 2.3.1 ). As stated previously... you simply re-flash the recovery to get to the recovery again
Click to expand...
Click to collapse
yes, i actually like it this way, it keeps your original safe

Titanium Backup and few other apps are why i ROOT the phone as well.
after you fastboot over the CW recovery image and rooted, were you able to install Super User?
there is another trick, you can Install Super User first from Market
then repeat the steps to fastboot the clock work recovery image and get root access
jvblack82 said:
Great guide, I'm new to the SDK and adb and fastboot so this helped a lot. My phone crashed last night and I had to completely restore it. Biggest upset is I was racing my girlfriend to beat Angry Birds Seasons and now my save games are gone. Along with other app data and all my settings.
So the Nexus S is stock what I root phones to get to. I love the pure Google experience. Never had one completely crap out crash though.
I followed your guide to the tee and got it what I thought would be rooted. When I get to the end though I boot up and the ClockworkMod ROM Manager v3.0.0.2 says "You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Also Superuser app says there is an update available, then tries to install and says it can't. So it puts the update zip on my root of my storage. I boot into CMR and try to install that and it errors saying it's not there. But it is when I look is mass storage mode from my computer.
I boot into clockwork mod recovery just like your guide says the bootloader says unlocked. I don't get it. What did I miss? Only reason I want to root is to use Titanium backup. I really wish google had a better backup system for app data but they don't... yet. So I don't want what happened last night to happen again.
Thanks in advance,
JB
Nexus S, stock rom just want root access for backup.
Click to expand...
Click to collapse

Followed the guide to a T as well and did not get root access. But unlocking the bootloader, installing the SDK and learning about fastboot and such was very helpful. Using that, I used the automated batch file posted in this topic http://forum.xda-developers.com/showthread.php?t=882333 and it worked.

What to do if my Device Manager showed Android 1.0?

ykphuah said:
What to do if my Device Manager showed Android 1.0?
Click to expand...
Click to collapse
you select the correct driver to install the ABD support or Bootloader support, depending in which screen you have the phone on
just review the step by step guide, it is mentioned there

sinatosk said:
Nice guide.
The only thing that's making me hesitate to do root on my NS is reversing the whole process...
stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...
I'll wait until google releases a firmware that contains everything
Click to expand...
Click to collapse
If you're running 2.3.1 all you need to do to get back to stock recover is reboot the phone, because /etc/install-recovery.sh runs every boot and checks to see if the recovery is stock or not...if not it flashes it for you. So unless you've renamed the /etc/install-recovery.sh file you can easily get stock recovery.

knytphal said:
If you're running 2.3.1 all you need to do to get back to stock recover is reboot the phone, because /etc/install-recovery.sh runs every boot and checks to see if the recovery is stock or not...if not it flashes it for you. So unless you've renamed the /etc/install-recovery.sh file you can easily get stock recovery.
Click to expand...
Click to collapse
... yeah I know. Made a post earlier today about it in this thread...

[GUIDE] Flash Official JB 4.1.2 Firmware on P6810 Wi-Fi Device

[GUIDE] Flash Official JB 4.1.2 Firmware on P6810 Wi-Fi Device
Sick and tired of Samsung ignoring the official JB 4.1.2 update for our much maligned and forgotten device?
Well, you’re in luck, this guide will effectively turn your P6800 Wi-Fi device into a P6800-GSM/3G model. We do this by changing the device partition layout and then flashing P6800 firmware with Odin.
Of course, due to hardware differences, you won’t have a working radio/modem. Also, some unneeded system apk's will need to be removed and the UI will also need some cosmetic changes etc, but it's a start.
WARNING & DISCLAIMER: I am not responsible, YOU are! You can probably forget about your warranty. This will wipe everything and increase your flash counter too !
PRE-FLASH REQUIREMENTS
1. Internal sdcard contents backed up off device
2. Any apps & data (is you wish) backed up off device
DOWNLOAD REQUIREMENTS
1. P6810 Wi-Fi model with a FULL battery
2. Windows PC
3. P6800_3G_16G.pit
4. Download P6800 JB 4.1.2 DXMD3 firmware from:
a) Samsung-updates.com
b) sammobile.com​5. Odin 3.07
6. Samsung drivers
METHOD
1. Extract P6800_3G_16G.pit & P6800 firmware so you just have .pit & .tar files
2. Drivers
a) Uninstall or disable KIES
b) Install Samsung drivers & reboot PC​3. Run Odin 3.07 & install
[PIT] = P6800_3G_16G.pit
[PDA] = P6800 official JB 4.1.2 firmware .tar file​4. Download Mode
a) Power off device
b) Hold volume down + Power
c) Release buttons at Warning Menu
d) Volume up to continue​5. Connect device to PC via USB cable
6. ID:COM should change colour in Odin 3.07
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7. Click [START] and watch the magic
8. If you get a screen message with button [Reset perangkat] (Reset device), just tap it
NEW PARTITION LAYOUT
FURTHER RECOMMENDATIONS
*. Flash TWRP 2.6.1 in Odin [PDA]
*. Flash P6800 JB 4.1.2 SkyHigh kernel​
MY P6810 RUNNING EROBOT ROM + SKYHIGH KERNEL
GUIDE: DOWNGRADE P6810 (WIFI) FROM OFFICIAL JB 4.1.2 TO ICS 4.0.4 IN POST #2
.

[guide] downgrade p6810 (wifi) from official jb 4.1.2 to ics 4.0.4
[GUIDE] DOWNGRADE P6810 (WIFI) FROM OFFICIAL JB 4.1.2 TO ICS 4.0.4
WARNING & DISCLAIMER: I am not responsible, YOU are! You can probably forget about your warranty. This will wipe everything and increase your flash counter too !
PRE-FLASH REQUIREMENTS
1. Internal sdcard contents backed up off device
2. Any apps & data (is you wish) backed up off device
DOWNLOAD REQUIREMENTS
1. P6810 Wi-Fi model with a FULL battery
2. Windows PC
3. P6810_WIFI_16G.pit
4. Download P6810 ICS 4.0.4 firmware from:
a) Samsung-updates.com
b) sammobile.com​5. Odin 3.07
6. Samsung drivers
7. P6810 TWRP Recovery
METHOD
1. Extract P6100_WIFI_16G.pit & P6100 firmware so you just have .pit & .tar (or .tar.md5) files
2. Drivers
a) Uninstall or disable KIES
b) Install Samsung drivers & reboot PC​3. Run Odin 3.07 & load
[PIT] = P6810_WIFI_16G.pit
[PDA] = P6810 official ICS 4.0.4 firmware .tar file
Uncheck [AUTO REBOOT]​
[/IMG]
4. Download Mode
a) Power off device
b) Hold volume down + Power
c) Release buttons at Warning Menu
d) Volume up to continue​5. Connect device to PC via USB cable
6. Odin ID:COM should change colour
7. Click [START]
8. Success = “RESET”
* Factory Reset is required for boot
- ICS device is known the be affected by SuperBrick (aka Brick-Bug)
- Those trolls that want to debate this can debate themselves out of this thread !
- Instead, we do this the "SAFE" way by using a custom recovery​9. Disconnect USB cable
10. Reboot into Download Mode
a) Power off device
b) Hold volume down + Power
c) Release buttons at Warning Menu
d) Volume up to continue​11. Click [RESET] button in Odin and load
[PDA] = P6810 TWRP Recovery.tar
Uncheck [Auto restart]​12. Connect device to PC via USB cable
13. Odin ID:COM should change colour
14. Click [START]
15. Success = “RESET”
16. Enter Recovery Mode
a) Disconnect USB cable
b) Hold volume UP + Power until enter TWRP menu (release only when in recovery)
c) If unsuccessful first time, release buttons & try again
d) TWRP Recovery may give message “unable to mount ‘/data’” & auto reboot​17. Enter Recovery Mode again
a) Wipe – format data (type “yes”)
b) ignore message " 'unable to mount ‘/data' "
c) Reboot System
d) Tap [Do Not Install] SuperSU​18. Device will boot – wait about 5 mins
* Setup ROM and enjoy
* Your device & partitions are now restored to original P6810 ICS 4.0.4
.

You are a genius!
I'll give it a try as soon as I can!
Thanks!

furius said:
You are a genius!
I'll give it a try as soon as I can!
Thanks!
Click to expand...
Click to collapse
Let me know how you go. You should be fine as long as you meet all the requirements and follow the steps.
Sent from my GT-I9500 using XDA Premium 4 mobile app

UpInTheAir said:
Let me know how you go. You should be fine as long as you meet all the requirements and follow the steps.
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Why do we need to flash p6800 recovery? Due to different layout partition? So if we need to go back to p6810 (through restore from backup) we need to flash p6810 recovery first?
Inviato dal mio HTC One X utilizzando Tapatalk

furius said:
Why do we need to flash p6800 recovery? Due to different layout partition? So if we need to go back to p6810 (through restore from backup) we need to flash p6810 recovery first?
Inviato dal mio HTC One X utilizzando Tapatalk
Click to expand...
Click to collapse
After flash the P6800 firmware, you don't need to flash any custom recovery. It's just a recommendation and also reminder to flash stuff for P6800. You need it if you wish to flash eRobot ROM.
TO RETURN TO P6810 PARTITIONS & FIRMWARE
Follow the above steps but substitute Step #3
A - P6810_WIFI_16G.pit + bodivas P6810 JB ROM .tar file + then flash P6810 CWM/TWRP Recovery & FULL nandroid restore
To be clearer: If you need to go back,
1. Flash P6810 PIT + bodivas ROM in Odin
2. Let ROM boot
3. Flash P6810 CWM/TWRP Recovery in Odin and then FULL restore the ICS Nandroid
Don't forget to keep the Nandroid backup on your external sdcard, internal will get wiped !
Sent from my GT-I9500 using XDA Premium 4 mobile app

Is it completely impossible to flash back to stock using Mobile odin from bodivas ROM?
Sent from my GT-P6810 using XDA Premium HD app

karlsbug said:
Is it completely impossible to flash back to stock using Mobile odin from bodivas ROM?
Sent from my GT-P6810 using XDA Premium HD app
Click to expand...
Click to collapse
I don't know, but haven't found a way with PC Odin yet. Still a few things to try later on using old ICS 4.0.4 bootloader etc.
The only successful method so far is the Nandroid way.
Sent from my GT-I9500 using XDA Premium 4 mobile app

Cheers UITA, btw usb otg is now working with your your latest kernel. Excellent!
Karlsbug.
Sent from my E330 using xda app-developers app

Update. It seems I have wifi issues with v1.6.0. I unpacked the kernel from bodivas rom, reflashed, seems OK, now. Wifi would only work if I turned it off and on again. No usb otg now:crying:
karlsbug said:
Cheers UITA, btw usb otg is now working with your your latest kernel. Excellent!
Karlsbug.
Sent from my E330 using xda app-developers app
Click to expand...
Click to collapse

karlsbug1971 said:
Update. It seems I have wifi issues with v1.6.0. I unpacked the kernel from bodivas rom, reflashed, seems OK, now. Wifi would only work if I turned it off and on again. No usb otg now:crying:
Click to expand...
Click to collapse
I think you're in the wrong thread.......
Anyway, I tested all OK on bodivas stock ROM. Had no issues the past day. Backup your data and save off device. Reflash his stock ROM (no multi-windows) and try again.
BTW, I have managed to revert to ICS 4.0.4 without using nandroid. :highfive:
I'll post the method here later today. I have some business today.
From now on, I'll be using eRobot, but must make a flashable script to uninstall some non-related feartures and apk's etc. I'll even attempt later on to modify some apks to get rid of some unneeded options in settings menu.

Guide: DOWNGRADE P6810 (WIFI) FROM OFFICIAL JB 4.1.2 TO ICS 4.0.4
Full Guide: DOWNGRADE P6810 (WIFI) FROM OFFICIAL JB 4.1.2 TO ICS 4.0.4 in Post #2.
I don't use Mobile Odin, but don't think it's possible.....
Now enjoy your JB "P6800" or ICS P6810
Cheers,
UITA
Edit: Nearly forgot, thanks bodivas for suggesting Factory Reset.

I know its the wrong thread but i cant post inthe ROM sorry.
Atb
Sent from my GT-P6810 using XDA Premium HD app

After flashing JB, I don't think flashing CWM or TWRP is working properly. I get successful flash of P6800 TWRP, but fails to boot into recovery volume up + power. Flashing the P6810 TWRP recovery partly works, but does not show the internal sdcard. Maybe something to do with bootloader still showing P6810 ?
Will take a look later.
Sent from my GT-I9500 using XDA Premium 4 mobile app

BUG - Can't quite get any custom recovery flashed properly on JB
Edit: Just flash TWRP 2.6.1.0 in Odin [PDA]. Done
In TWRP recovery:
Internal sdcard = emmc
External sdcard = sdcard
My P6810 IS NOW running eRobot ROM + SkyHigh kernel :
EDIT : STILL A FLAW IN THE "RECOVBERY PROCESS". SOME RECOVERIES STILL FAIL TO FLASH AND OTHERS DON'T MOUNT /RECOGNISE ALL PARTITONS. THE TWRP 6.1.0 DOES NOT BACK UP THE PRELOAD PARTTION, WHICH IS A REQUIREMENT TO RESTORE CORRECTLY.

Running erobot rom and skyhigh kernel on my P6810 too!
I followed your instruction and all was fine! All is working well, I'll report more feedback in the next days ...
Thanks UpInTheAir

One more thing: from your screen shot you are using tablet UI while erobot has phablet UI ... I tried to switch to tablet UI changing lcd density but touchwiz continues to crash ... how did you get it working?
And again ... is there the possibility to have the multi window feature as in bodivas rom?

furius said:
One more thing: from your screen shot you are using tablet UI while erobot has phablet UI ... I tried to switch to tablet UI changing lcd density but touchwiz continues to crash ... how did you get it working?
And again ... is there the possibility to have the multi window feature as in bodivas rom?
Click to expand...
Click to collapse
I was running eRobot v1 , Phablet is v2.3P. I really do suggest a full wipe immediately prior to flash (if ROM doesn't automatically). I haven't flashed v2.3P yet, but have a read through the eRobot thread on the development section. Please let me know what you find out. Edit: jhust flashed it, working ok
http://erobotrom.blogspot.com/p/erobot-rom-for-g-tab-77.html?m=1
I have permission from eRobot to modify and release his ROM at XDA. I was going to do tablet UI, but now doing Phablet instead. I am working on a Aroma installer version to flash in custom recovery. As per my previous post, custom recoveries aren't working 100% with preload not being able to backup or restored. We need this for 4.1.2.
Although the guide works flawlessly, the end useability is not quite there with custom recovery not quite working as expected.
If I can't get this working easily for user simplicity, the eRobot ROM will be built/modded for P6810 partitions instead. So the only requirement will be flashing bodivas base ROM and custom P6810 recovery from daniel_hk TWRP 6.0.0.0. I have some family time today, but hopefully have something out for "P6800" partitioned or original P6810 partition device soon.
Edit: Just Flashed "version 1" of eRobot 2.3P SkyHigh Edition with new Aroma 2.70RC2 installer. Just got to config for a lot more Aroma options before first release. Flashing and testing takes time, just one little error can give a big headache ! Just look out in the development thread for a "new" ROM for the P6810 in a few days time. If a FULL wipe is done (preload, system, data, dalvik), there are no flash issues. Maybe I'll look at adding a few more system mods (time permitting) later on, wait and see.......
Sent from my GT-I9500 using XDA Premium 4 mobile app

This appeared to work well for me. Then I got to the screen where there is the, "Reset perangkat" dialog button (and a back button on the bottom left). I've tried over and over to tap either button, but my touchscreen is apparently non-responsive (and the screen times out and goes to sleep as you're touching it - so apparently it's not detecting any input). I tried reflashing again, and there was no change. The screen orientation automatically rotates, the volume buttons work, the power button works - it's just that the touch screen is non responsive. I am going to try downloading a different 4.1.2 ROM from SamMobile (but their servers are slow so it'll be awhile).
Any other ideas?

gat0rjay said:
This appeared to work well for me. Then I got to the screen where there is the, "Reset perangkat" dialog button (and a back button on the bottom left). I've tried over and over to tap either button, but my touchscreen is apparently non-responsive (and the screen times out and goes to sleep as you're touching it - so apparently it's not detecting any input). I tried reflashing again, and there was no change. The screen orientation automatically rotates, the volume buttons work, the power button works - it's just that the touch screen is non responsive. I am going to try downloading a different 4.1.2 ROM from SamMobile (but their servers are slow so it'll be awhile).
Any other ideas?
Click to expand...
Click to collapse
Quite strange, I've lost count the times I've used this method and not come across this.
If you get stuck at the reset screen again, maybe you could try:
1. Disconnect USB cable
2. Enter stock recovery: factory reset (hold volume UP + power until enter recovery)
3. Reboot and wait 5-10 mins for first boot
If still not working, try flash again same full firmware package (same CSC), because it won't/shouldn't ask for the reset if already flashed (didn't ask again for me anyway)
Sent from my GT-I9500 using XDA Premium 4 mobile app

[RECOVERY]TWRP 3.0.3-1 unofficial [SM-T700/T705/800/805/807] - UPDATE 10/02/2017

UPDATE 10/02/2016- New version of TWRP has been released v3.0.3-0. See below:
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
I have updated versions SM-T800/805 with new builds. TWRP is now v3.0.3-1
TWRP OFFICIAL APP RELEASED: https://twrp.me/app/
Fixes:
Download mode now available in REBOOT options.
Root Shell now available in ADB.
Radio and Recovery backup.
System image backup/restore
Factory image flashing.
Supersu root option removed. This is to pre-empt the upgrade to MM which would cause a bootloop.
MTP fix - MTP now finally working in recovery.
Note: On my PC MTP works perfect in windows 7, but on Windows 8.1 was a little quirky. If you get a USB DEVICE NOT RECOGNISED error after enabling MTP, disable then quickly re-enable MTP and this should fix it.
This version also has system image backup and restore included. It is also possible to flash factory firmware images via the Image install button. (see the TWRP changelog above for more info)
UPDATE 5/3/16:
Have modified the twrp source code and extended factory image partition flashing to include all images except SBOOT.bin (still working on how to flash the bootloader via recovery)
This means BOOT, SYSTEM, RECOVERY, CACHE, HIDDEN, MODEM(RADIO) can all be flashed from the factory firmware. No need for ODIN anymore. As far as I know the Tab S is the only device supporting this at the moment.
(Note: to flash the modem it is necessary to rename MODEM.bin to MODEM.bin.img first)
TWRP_3.0.2-1-T700
TWRP-3.0.2-1-T705
TWRP-3.0.2-1-T800
NOTE: Certain models of the T800 version have a bug at the moment where the screen will be blank when booting to TWRP recovery until the screen timeout kicks in. After that pressing any button will show the screen. As a work around setting the timeout to 15 secs will shorten the wait.
TWRP-3.0.2-1-T805/T807(ATT or Verizon not supported)
twrp_3.0.3-1_sm-t800_10217
twrp_3.0.3-1_sm-t805_10217
FLASH WITH ODIN OR FLASHFIRE OR EXTRACT THE RECOVERY.IMG AND FLASH WITH TWRP
NOTE: It is important to boot to recovery after flashing with Odin or twrp may not stick and will be replaced with stock recovery.
When flashing uncheck auto reboot in Odin, immediately after flashing manually reboot and boot into twrp.
Manual reboot is POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FEEDBACK IS APPRECIATED PLEASE
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.

Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.

gcappa said:
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
Click to expand...
Click to collapse
As long the bootloader is unlocked, and if someone has an stock recovery pulled from it, then he could be twrp for it

Bootloader is unlocked. But I already flashed a modified cwm which doesn't work too well. So not sure if I could pull the stock recovery unless I reflash the stock rom.

gcappa said:
Bootloader is unlocked. But I already flashed a modified cwm which doesn't work too well. So not sure if I could pull the stock recovery unless I reflash the stock rom.
Click to expand...
Click to collapse
If you have the firmware downloaded just right click on the md5 and open it with 7zip or Winrar, then simply just drag the recover IMG to your desktop and send it here(or link to download). I'm not going to go to much in depth as I don't want this thread to be filled with non related to twrp stuff. I'm also unsure if he has time but ash is one good recovery builder

Ok, I'll do all that when I get home and upload a link.

gcappa said:
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
Click to expand...
Click to collapse
Should be possible as long as the right files are available. This is a snapdragon 805 device?
Seeing as I don't have this device you would have to test the builds and I would need some info from the device. Might take a few builds to get a proper working one.
I take it you are currently rooted? Also could you send me a link to the version of cwm you are using?

gcappa said:
Ok, I'll do all that when I get home and upload a link.
Click to expand...
Click to collapse
Is the sm-n9100 the Chinese version Note 4 Duos?
The TWRP recovery below is for this version, please test:
twrp-2860-n1900
Stock Recovery:
Stock-recovery-n1900
Note: You take responsibility for testing this.

Failed to flash on my T-800.

dwarfer66 said:
Failed to flash on my T-800.
Click to expand...
Click to collapse
What failed to flash? It's made for the t800. It flashes fine on a t805. No one else has had any issues. What is the full version of your device?

ashyx said:
Unofficial version of the latest TWRP, don't think it's been released yet.
Found it by accident for another device, so have rebuilt it for the Tab S Exynos version only.
TWRP-2.8.6.1
Click to expand...
Click to collapse
Thank again ashy this is awesome, keep up the good work.
Confirmed its working T800 5.0.2

ashyx said:
What failed to flash? It's made for the t800. It flashes fine on a t805. No one else has had any issues. What is the full version of your device?
Click to expand...
Click to collapse
This unofficial TWRP fails to flash, just says failed when trying to install.

dwarfer66 said:
This unofficial TWRP fails to flash, just says failed when trying to install.
Click to expand...
Click to collapse
Again, you need to confirm what your exact model is and build number. As you can see from the post above it flashes fine on a T800.
Post a screenshot of the issue with Odin.

It's flashing for me ok on my T800 with IronRom 2.0. Only thing is the root ain't working. Or do I need to unselect auto-reboot and do a forced shutdown? And clear cache and reboot?
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
edit: reflashed IronRom 2.0 to fix cache issue. After the cache wipe it boots up
edit2: it appears to be rooted but it ain't working. But when an app should ask for root permissions the app goes black screen. For Titanium backup it just hangs on checking

RDDraco said:
It's flashing for me ok on my T800 with IronRom 2.0. Only thing is the root ain't working. Or do I need to unselect auto-reboot and do a forced shutdown? And clear cache and reboot?
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
edit: reflashed IronRom 2.0 to fix cache issue. After the cache wipe it boots up
edit2: it appears to be rooted but it ain't working. But when an app should ask for root permissions the app goes black screen. For Titanium backup it just hangs on checking
Click to expand...
Click to collapse
Did you update the supersu app as requested? You need to post a screenshot of root validator so I can see the status of root.
You may just need to select full unroot from settings in the supersu app then boot into twrp and run the root process again or flash the supersu2.46 zip.
Also regarding wiping cache, it can sometimes take longer depending on what's in cache at the time. It may seem like it's hung but eventually completes. On occasion I've seen it take up to a few minutes to wipe.

Just saying that root is broken on custom roms such as iron rom. It's an known issue with touchwiz lollipop roms.
-DUHA

So it's a Rom issue?
What's the actual problem?
Isn't the Rom already rooted, unusual for a custom Rom to not be prerooted?

Guess that explains why it wasn't working. (Tkkg1994 managed to get IronRom working with root in v2.0.5) so its fine for me now.

RDDraco said:
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
Click to expand...
Click to collapse
Looked into this issue and have fixed it. Wipe Cache should work now.

ashyx said:
Unofficial version of the latest TWRP, don't think it's been released yet.
Found it by accident for another device, so have rebuilt it for the Tab S Exynos version only.
TWRP-2.8.6.1
NOTE: If after using TWRP to root you don't see the notification to update Supersu, just install the latest Supersu app from Play. Check root status with Root Validator
Supersu
Root validator
Click to expand...
Click to collapse
Just today, I rooted my new Tab S (SM-T800) AFTER allowing it to OTA update to Android 5.0.2. After that, I used Odin to flash the latest version of CWM I could find for this device, and that trashed recovery altogether. Couldn't get into recovery at all. So I used Odin again to flash TWRP 2.8.6.0 and had recovery back, BUT I kept getting notifications that SuperSU needed to be updated. What I did then was flash "BETA-SuperSU-v2.48.zip", and that resolved the "update needed" problem, and all seems to be working smoothly now. :good:
I'm running stock Touchwiz Lollipop 5.0.2 . Haven't tried changing ROM's, but don't really have a desire to do that just yet.

help root n900w8 5.0

how to root sm-n900w8 lollipop 5.0??

help

Either flash a CF Auto Root file from Chainfire, or install TWRP Custom Recovery and flash a SuperSU ZIP file. Both of these methods will trip Knox.

CF Auto Root not work in lollipop 5.0 for n900w8

I'm also waiting for confirmed root before upgrading to 5.0

TWRP works
The latest TWRP works to root SM-N900W8 Lollipop, but it does trip knox.
So use at your own risk.

james231 said:
The latest TWRP works to root SM-N900W8 Lollipop, but it does trip knox.
So use at your own risk.
Click to expand...
Click to collapse
Can you please give me the procedures on how to use twerp.

thykhin said:
Can you please give me the process on how to use twerp.
Click to expand...
Click to collapse
First download an install ODIN also download the latest TWRP (this is the one I have https://twrp.me/devices/samsunggalaxynote3canada.html). this TWRP page has a section
called "Odin Install Method" follow that info.
this web page will show you how to use odin http://forum.xda-developers.com/showthread.php?t=1372414
"download mode"
Put your phone into download mode by turning it off.
Now press and hold “Volume Down + Power + Home” buttons together for a little bit of time
After the Samsung logo appears release the buttons.. there will be a warning page and you can use the volume/power buttons to move and select download mode.
when you are in download mode it will say “Downloading, Do not turn off target!!”
this page will show you how to use TWRP http://android.wonderhowto.com/how-...only-custom-recovery-youll-ever-need-0156006/
I am not responsible for anything bad that may happen. Always remember that you do this at your own risk !!!! Always backup!!!
If i remember correctly it erases everything on the phone, so backup your personal stuff
I hope this helps

james231 said:
First download an install ODIN also download the latest TWRP (this is the one I have https://twrp.me/devices/samsunggalaxynote3canada.html). this TWRP page has a section
called "Odin Install Method" follow that info.
this web page will show you how to use odin http://forum.xda-developers.com/showthread.php?t=1372414
"download mode"
Put your phone into download mode by turning it off.
Now press and hold “Volume Down + Power + Home” buttons together for a little bit of time
After the Samsung logo appears release the buttons.. there will be a warning page and you can use the volume/power buttons to move and select download mode.
when you are in download mode it will say “Downloading, Do not turn off target!!”
this page will show you how to use TWRP http://android.wonderhowto.com/how-...only-custom-recovery-youll-ever-need-0156006/
I am not responsible for anything bad that may happen. Always remember that you do this at your own risk !!!! Always backup!!!
If i remember correctly it erases everything on the phone, so backup your personal stuff
I hope this helps
Click to expand...
Click to collapse
Thank You! I was able to successfully root my N900W8UBU2DOG2.

twrp-2.8.7.2-angler.img overwritten by stock recovery

So I have flashed TWRP 2.8.7.2 on my 6P, and was able to go into it. However, if I shut the phone down then boot into the bootloader, arrow down to Recovery Mode and press the power button, I get the android lying on his back with a red triangle with an exclamation mark above his open front, with "No command." written below it. I can hold down the power button and press the volume up button to get to stock android recovery, then reboot to bootloader just fine.
If I connect the phone to my pc and flash TWRP again, I can get into TWRP, however, next time I reboot, it is gone. I read on TWRP's Nexus 6P page the following:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
Click to expand...
Click to collapse
So, I flashed TWRP, then entered fastboot reboot in the cmd window, it rebooted to the bootloader. Then I pressed the volume down button to Recovery mode, pressed power and it went into TWRP. In TWRP I went to Reboot and selected Power Off. I booted it back into the bootloader, selected Recovery mode and it went back to the android with the red triangle and "No command."
I'm at a complete loss. I've read through hundreds of posts here on xda, with one person having the same issue, but fixed it by re-downloading the TWRP .img file and flashing it, Which I've tried... I even flashed the 2.8.7.1 version and had the same problem, then again with the 2.8.7.2 version and still same problem. I've searched for a more detailed explanation of "the proper key combo to enter recovery" and couldn't find anything.
I would really appreciate any help you guys can give me. The biggest thing I have come to understand after reading hundreds (literally) of posts, this community of people are really helpful.
My Android version is 6.0 and my Build number: is MDB08L.
Thanks for any help you guys can give.

this happened to me as well. i fixed it but i don't remember how. I think you need to flash twrp again and there is a tick box or setting that you need to check that will prevent the stock recovery from overwriting twrp. sorry i couldn't be more help.

jrc27 said:
this happened to me as well. i fixed it but i don't remember how. I think you need to flash twrp again and there is a tick box or setting that you need to check that will prevent the stock recovery from overwriting twrp. sorry i couldn't be more help.
Click to expand...
Click to collapse
Thanks for the quick reply. I just flashed TWRP again, entered it through recovery mode, but do not see a tick box or setting... I've looked through the options so many times that I may just be overlooking it by now. Any idea what the tick box or setting might have been labeled as?

I'm having the same issue and cannot seem to find a solution as well. I feel like I'm missing something very obvious...

You will need root explorer and go to the system folder. Then from there you need to rename this file to recovery-from-boot.bak or just delete.
Sent from my Nexus 6P using Tapatalk

I recently experienced the same issue with my Nexus 5 (as I was upgrading it from Kitkat to Marshmallow). I finally solved it by flashing TWRP via Flashify (https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=fr)
So, here are the steps I used : flashed TWRP via bootloader (via PC with USB cable) and boot straight into recovery... flash my rom (with root included) then reboot normally. Then downloaded flashify from the playstore, then flashed TWRP again using flashify... Done, never had this issue since then... I can now reboot into TWRP without problem from the rom, the bootloader or TWRP itself
I don't have a Nexus 6P yet (should do next week ), but it could be worth testing Flashify

Thanks for the suggestions guys.
I'm sorry, I should have mentioned that I haven't gone any further than trying to flash TWRP. This is the first phone I've even unlocked the bootloader on, so I'm extremely new at this.
I'm guessing that Root Explorer and Flashify both require root, which I don't have. Is there a way to get root access with TWRP not staying installed? Is it possible to root the phone while TWRP is installed? The reason I ask is if rooting the phone requires the phone to be rebooted, then TWRP will no longer be installed.
Please excuse the rudimentary questions, I just don't want to mess anything up. I've read so many things over the past several years that warn people to be careful because the phone could be bricked.

j.r.pitcher said:
Thanks for the suggestions guys.
I'm sorry, I should have mentioned that I haven't gone any further than trying to flash TWRP. This is the first phone I've even unlocked the bootloader on, so I'm extremely new at this.
I'm guessing that Root Explorer and Flashify both require root, which I don't have. Is there a way to get root access with TWRP not staying installed? Is it possible to root the phone while TWRP is installed? The reason I ask is if rooting the phone requires the phone to be rebooted, then TWRP will no longer be installed.
Please excuse the rudimentary questions, I just don't want to mess anything up. I've read so many things over the past several years that warn people to be careful because the phone could be bricked.
Click to expand...
Click to collapse
Don't worry, we have all been junior at this at some point... (and I don't pretend to be an expert, but I've gone through this whole process a few days back with my nexus 5... so it's fresh for me)
I'm guessing that if you have unlocked the bootloader and are trying to install TWRP, you ultimately want to root your phone.
To root your phone you have 2 options,
- either root your stock rom, by following the instruction here [GUIDE] Unlock/Root/Flash for Nexus 6P (read the (section 6) instructions carefully and make sure the version (build) of your rom is the correct one to flash a modified boot.img)
- or you can directly replace the stock rom with a pre-rooted rom that you can find in the XDA Developer section (the Chroma rom for instance could be a good one)
In both cases, you'll need to flash some files via TWRP...
Since you have an issue with rebooting into TWRP, you will have to first boot into your stock rom, copy or download on your phone SD card the zip files that you'll need to flash with TWRP and then reboot into bootloader, and follow the instruction for rooting or install a modified pre-rooted rom. Whenever you'll need to boot into recovery during the process, you will need flash TWRP again via adb and boot directly into TWRP (the flash and direct boot adb instruction from cmd on your PC is: fastboot boot <twrp name>.img).
Once you have a rooted rom, you can test Flashify to make TWRP recovery permanent
Enjoy your new rooted phone
PS: don't worry too much about bricking your phone. I believe this occurs when people don't read instructions carefully enough and don't flash the correct zip files or img files... You may find some video tutorials on how to root, but XDA guides are usually great

Well said surfinette!

Surfinette said:
Don't worry, we have all been junior at this at some point... (and I don't pretend to be an expert, but I've gone through this whole process a few days back with my nexus 5... so it's fresh for me)
I'm guessing that if you have unlocked the bootloader and are trying to install TWRP, you ultimately want to root your phone.
To root your phone you have 2 options,
- either root your stock rom, by following the instruction here [GUIDE] Unlock/Root/Flash for Nexus 6P (read the (section 6) instructions carefully and make sure the version (build) of your rom is the correct one to flash a modified boot.img)
- or you can directly replace the stock rom with a pre-rooted rom that you can find in the XDA Developer section (the Chroma rom for instance could be a good one)
In both cases, you'll need to flash some files via TWRP...
Since you have an issue with rebooting into TWRP, you will have to first boot into your stock rom, copy or download on your phone SD card the zip files that you'll need to flash with TWRP and then reboot into bootloader, and follow the instruction for rooting or install a modified pre-rooted rom. Whenever you'll need to boot into recovery during the process, you will need flash TWRP again via adb and boot directly into TWRP (the flash and direct boot adb instruction from cmd on your PC is: fastboot boot <twrp name>.img).
Once you have a rooted rom, you can test Flashify to make TWRP recovery permanent
Enjoy your new rooted phone
PS: don't worry too much about bricking your phone. I believe this occurs when people don't read instructions carefully enough and don't flash the correct zip files or img files... You may find some video tutorials on how to root, but XDA guides are usually great
Click to expand...
Click to collapse
Thanks for the detailed instructions, I really appreciate it.
To be perfectly honest, I was really nervous trying all of that out. I know you said that I shouldn't worry too much about bricking the phone, but it was still a fear.
I have TWRP installed now and it is sticking. Below is a description of how I got it to stay installed.
I didn't have access to my pc this weekend, so was planning on doing it yesterday (Monday). However, Sunday I was re-reading through the posts in this thread and jrc27 mentioned a tick box or setting that you need to check, and I remembered that when I installed TWRP the first time there was a screen that gave you a choice of "Keep Read Only" or "Swipe to Allow Modifications", then remembered someone posting elsewhere about doing the "Swipe to Allow Modifications" is what let's TWRP overwrite the part of Android that resets the recovery mode to the stock recovery mode upon reboot. Well, everytime I would reboot the phone it would be back to the stock recovery mode, so I must have hit "Keep Read Only" that first time, and checked the "Never show this screen during boot again" checkbox. In another post someone was having a different problem with TWRP and someone else told them to delete the .twrps file in the TWRP folder.
So, I flashed TWRP again, and in Advanced, I went into the File Manager, found the .twrps file and deleted it. Rebooted the phone, flashed TWRP again and had the screen that gave me a choice of "Keep Read Only" or "Swipe to Allow Modifications". I did the "Swipe to Allow Modifications", and it booted into TWRP just fine. I rebooted the phone, went to recovery mode and it again booted into TWRP. So, finally it is sticking.
Again, thanks for all of the suggestions, I do appreciate it greatly, as well as welcoming comments and tone of voice (or text as it may be).
Here is what that screen looks like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

warpanda said:
I'm having the same issue and cannot seem to find a solution as well. I feel like I'm missing something very obvious...
Click to expand...
Click to collapse
I'm new to xda, so not sure how the forums work. I just posted a reply to Surfinette with how I fixed the issue on my phone. I don't know if you get a message saying a new post was added or not, so I am replying to your post to let you know about it.

u must have the zip in SD card for rooting..
simply....
after flashing twrp do not reboot, or stock recovery will be flashed again... (thats how it works stock)
instead:
after flashing twrp, scroll down and click recovery to boot it... once in twrp, flash the root zip.... the zip used for rooting the device already includes the script that fixes the code that reflashes the factory recovery
(this is assuming you already download the root zip. when i say root zip i mean the proper SuperSU at the time... either system or systemless versions)

chaco81 said:
u must have the zip in SD card for rooting..
simply....
after flashing twrp do not reboot, or stock recovery will be flashed again... (thats how it works stock)
instead:
after flashing twrp, scroll down and click recovery to boot it... once in twrp, flash the root zip.... the zip used for rooting the device already includes the script that fixes the code that reflashes the factory recovery
(this is assuming you already download the root zip. when i say root zip i mean the proper SuperSU at the time... either system or systemless versions)
Click to expand...
Click to collapse
Thanks for the info, chaco81!