Related
I have just updated my nexus s to the latest 4.0.4 update..now i want to bring back root access .. as we all know were going to loose root access if we updated. anyway i previously used this method http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ now im wondering if this also applies to 4.0.4 update and what is the best recovery to flash on this update?
The only thing i did was upgrade to 4.04, dont reboot but flash superuser, all clear, root is back.
[Q](solved) how do i bring back root on my i9023 ics 4.0.4
willemt158 said:
The only thing i did was upgrade to 4.04, dont reboot but flash superuser, all clear, root is back.
Click to expand...
Click to collapse
hmn... what i did was
i went to adb
open cmd
flashed recovery3101.img
after that i installed superuser using CWM recovery . if your using the stock recovery it will only show an error msg. didnt wipe anything ... all is ok and well hehehe cheers!
I have issue with CWM and Root. I've follow the guide here.
I manage to successfully do up to step 4 without error. After that, when I reboot the device, it have a message "android installing update". I installed titanium backup and it says no root access. Superuser is available. When I tried to update on Play "Update for Superuser could not be downloaded due to an error (941)"
I tried to go back to recovery, it is the stock recovery instead of CWM. I've updated my 9023 from 4.0.3 (stock non root) to 4.0.4 using CWM. I've installed superuser using CWM as well. But when I reboot the device, it went back to stock recovery. I've tried fastboot CWM, turn off, then turn back on to go recovery, it is using CWM. But when I reboot, and try to go back to recovery, it goes to the stock recovery.
Appreciate some help. Hope my explanation is clear.
Will
First try flashing the latest Superuser than reboot, then open rootexplorer
Rename "/system/etc/install-recovery.sh" to "/system/etc/install-recovery.sh.bak".
All Stock ROMs replace the recovery on each Boot if it isn't the stock one. Renaming this script stops that. After you do this, flash CWM one more time and it'll stick.
Thanks to harbb who helped me with the same isseu
not sure if this is legit... I found a few sites with the same tutorial but different backup apps same file download though... can anyone varify?
filename: Superuser-3.0.7-efghi-signed, from a mediafire download (/?57iroxlzh8bb5qi)
from tutorial: Root Nexus S with Android 4.0.4 ICS IMM76 Firmware, from androidlot.com
(sorry can't post link)
it just said to do a recovery from bootloader, no other tampering needed... was thinking of using it if it worked as I just did the Nexus S 19023 OTA update 2.3.6 - 4.0.4 found on this forum but wanted to root to use voodoo sound... first timer and dont want to mess around with roms or cwm... figure no harm rooting as Nexus S probably won't get anymore official updates
Signature verification failed
well i have tried to install the superuser from recovery (apply update from SDcard) but every time i try to install the zip file it gives me signature verification error .
Mansuur said:
well i have tried to install the superuser from recovery (apply update from SDcard) but every time i try to install the zip file it gives me signature verification error .
Click to expand...
Click to collapse
That means your not in CWM Recovery. You have to follow the guide and use fastboot to flash a custom recover. Thats why we use a custom recovery, to bypass the signiture check
so wats da final result?
in ics 4.04 how to flash cwm and root and install vodoo?
ended up using m.sabra's one click root and flash cwm tool (/showthread.php?t=1544940) worked a charm, downloaded voodoo sound plus so i didnt have to flash new kernel, putting music back on phone now (had to unlock bootloader) to see how it sounds
also used appbackup&restore, copied backup folder from sd to computer, used the root tool, redownloded appbackup&restore, copied folder back from computer to phone, allowed install from non market, reinstalled all apps
now have superuser and cwm and all my apps back
Hope this may help. it's the way a did it on my Nexus S
Download fastboot for Windows or Mac.
Make sure you have the Android SDK installed.
Download ClockworkMod Recovery.
Download the Rooted Su Binary for 4.0.4
Make sure you have the necessary drivers installed for your device
Put your device into Bootloader Mode (turn your device off, then hold Volume Up + Power).
Once in Bootloader Mode, type the following into your Command Window
fastboot oem unlock
You should now see a couple of lines go through on your Window.
Then Type the following:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Provided this went correctly (it should), you now want to cycle down to “Recovery” on your device using the Volume buttons and press Power to confirm. This should boot you into ClockworkMod.
Select Recovery again, navigate to “Mounts & Storage” and then to “Mount USB Storage”. Once this has been done, your SD Card should appear on your PC.
Copy the Rooted Su Binary you have downloaded to your SD Card, and then Unmount USB Storage on your device.
Navigate back to the main menu of ClockworkMod and select “Install zip from sdcard”, then “Choose zip from sdcard” and select the package you just copied across, and then confirm the installation. This should install the package and root your device.
Hey guys sorry i was on vacation, thats why it took me so long time to come back, anyways... here is the link of the step by step procedure on rooting your nexus s, this is what i followed, http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
but what i did was ;
1. after updating i lost root
2. open adb tool
3. flash new recovery3101.img ( this is to replace default recovery from the stock ics 4.0.4)
4.then installed superuser from the new recovery that i installed ( CWM)
i wont go through all the details since , the link already explained that there....so cheers and hope this works for you , all the needed files is in the link also.
Mrbalders said:
Hope this may help. it's the way a did it on my Nexus S
Download fastboot for Windows or Mac.
Make sure you have the Android SDK installed.
Download ClockworkMod Recovery.
Download the Rooted Su Binary for 4.0.4
Make sure you have the necessary drivers installed for your device
Put your device into Bootloader Mode (turn your device off, then hold Volume Up + Power).
Once in Bootloader Mode, type the following into your Command Window
fastboot oem unlock
You should now see a couple of lines go through on your Window.
Then Type the following:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Provided this went correctly (it should), you now want to cycle down to “Recovery” on your device using the Volume buttons and press Power to confirm. This should boot you into ClockworkMod.
Select Recovery again, navigate to “Mounts & Storage” and then to “Mount USB Storage”. Once this has been done, your SD Card should appear on your PC.
Copy the Rooted Su Binary you have downloaded to your SD Card, and then Unmount USB Storage on your device.
Navigate back to the main menu of ClockworkMod and select “Install zip from sdcard”, then “Choose zip from sdcard” and select the package you just copied across, and then confirm the installation. This should install the package and root your device.
Click to expand...
Click to collapse
wow very detailed cheers man!
Glad to help, and hope you've got your Nexus back to root
So I installed TWRP recovery backed up my stock os and flashed cyanagen mod 11
After a week or so I went in the cyanagen mod updates and started updating, everything worked
but now when I tried to flash in to my stock rom I go to recovery and I see that I have Clockwork revovery insted of TWRP
so I was stupid and i flahsed TWRP and didnt unistall clockwork mod
When i went in the recovery i had clockworkmod and then I rebooted and went in to TWRP
Now im stuck in 2 recoverys and cant go to cyanagen
I really need help
im using the LG G2 D802
gamehero said:
So I installed TWRP recovery backed up my stock os and flashed cyanagen mod 11
After a week or so I went in the cyanagen mod updates and started updating, everything worked
but now when I tried to flash in to my stock rom I go to recovery and I see that I have Clockwork revovery insted of TWRP
so I was stupid and i flahsed TWRP and didnt unistall clockwork mod
When i went in the recovery i had clockworkmod and then I rebooted and went in to TWRP
Now im stuck in 2 recoverys and cant go to cyanagen
I really need help
im using the LG G2 D802
Click to expand...
Click to collapse
I don't know if I understood you but just to be sure; you get in recovery mode CWM and on reboot TWRP?
I don't think you will like this solution but probably you will get your phone to work again xD (you will lose your data)
First of all you need:
- Android SDK bundle (google it, you will find it) on your Computer
- And a Rom you want to sideload (In your case the Cyanogen Rom)
- Cwm
Follow this steps:
1. go to the SDK bundle folder you downloaded -> go to sdk
-> go to platformform-tools
-> copy your ROM (ZIP-file) inside that folder
-> and name it to ROM.zip (so you won't need to write down a longname in cmd afterwards)
2. go to the SDK bundle folder you downloaded -> go to sdk
-> now press [shift] + [right mouse button] on platformform-tools (folder) to open cmd
3. Reboot your device into recovery mode (use cwm)
4. Go to “Mounts & Storage” and make sure that you can see “Unmount /sdcard/” and “Unmount /system/” (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount).
5. Now connect your device to the PC.
6. Once the phone is connected to the PC type “adb devices” in the cmd. If it returns a long alphanumeric string the phone is successfully connected in ADB mode. (if not look out for a usb driver for your phone; most time the problem lies in there)
7. Now type “adb push ROM.zip /sdcard/ROM.zip” (replace the word ROM if didn't named it)
8. This may take a while so be patient.
9. Once the process is complete you’ll see a message like <12345678kb to 1234567kb> on the cmd window.
10. Now unplug the device.
11. Go to the main screen of recovery and perform factory reset, wipe cache partition and then in advance menu wipe Dalvik cache. (Now you will lose your data for sure xD)
12. Now go to install zip from sdcard and choose the zip file you just transferred.
13. Once the process is complete, reboot the device
Hope this will help you.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you use TWRP there are some similar step by step guides ( maybe you should look for sideload)
GuiltyGod said:
I don't know if I understood you but just to be sure; you get in recovery mode CWM and on reboot TWRP?
I don't think you will like this solution but probably you will get your phone to work again xD (you will lose your data)
First of all you need:
- Android SDK bundle (google it, you will find it) on your Computer
- And a Rom you want to sideload (In your case the Cyanogen Rom)
- Cwm
Follow this steps:
1. go to the SDK bundle folder you downloaded -> go to sdk
-> go to platformform-tools
-> copy your ROM (ZIP-file) inside that folder
-> and name it to ROM.zip (so you won't need to write down a longname in cmd afterwards)
2. go to the SDK bundle folder you downloaded -> go to sdk
-> now press [shift] + [right mouse button] on platformform-tools (folder) to open cmd
3. Reboot your device into recovery mode (use cwm)
4. Go to “Mounts & Storage” and make sure that you can see “Unmount /sdcard/” and “Unmount /system/” (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount).
5. Now connect your device to the PC.
6. Once the phone is connected to the PC type “adb devices” in the cmd. If it returns a long alphanumeric string the phone is successfully connected in ADB mode. (if not look out for a usb driver for your phone; most time the problem lies in there)
7. Now type “adb push ROM.zip /sdcard/ROM.zip” (replace the word ROM if didn't named it)
8. This may take a while so be patient.
9. Once the process is complete you’ll see a message like <12345678kb to 1234567kb> on the cmd window.
10. Now unplug the device.
11. Go to the main screen of recovery and perform factory reset, wipe cache partition and then in advance menu wipe Dalvik cache. (Now you will lose your data for sure xD)
12. Now go to install zip from sdcard and choose the zip file you just transferred.
13. Once the process is complete, reboot the device
Hope this will help you.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you use TWRP there are some similar step by step guides ( maybe you should look for sideload)
Click to expand...
Click to collapse
So I got to step 4 and I see the mount system but I don't see umount sdcard
Then mount system or skip this part
5,6 and 7 are the most important part.
Can you push the Rom on your phone?
GuiltyGod said:
Then mount system :S
5,6 and 7 are the most important part.
Can you push the Rom on your phone?
Click to expand...
Click to collapse
adb push ROM.zip /sdcard/ROM.zip if I dont have the sdcard umonted will this still work?
I know I am repeating myself more or less (because I always edit my posts xD)
Well as long as you can push your file there shouldn't be sny problem
GuiltyGod said:
I know I am repeating myself more or less (because I always edit my posts xD)
Well as long as you can push your file there shouldn't be sny problem
Click to expand...
Click to collapse
so I wrote the command and it sad "5143kb/s «241840314 bytes in 45.912s»"
then i went install the zip and I can't find it
ok i went and mounted the data , pushed the file and installed it, thank you so much
But now i need to install the stock backup that I did with TWRP
That's pretty weird xD Because you get the message for a successful transfer but can't find the Zipfile.
You could try to push the Zipfile again and don't wipe anything at all (because you already wiped everything) and try to find the Zip file again to flash it.
Btw what does CWM gives you as options if you click install Zip files?
GuiltyGod said:
That's pretty weird xD Because you get the message for a successful transfer but can't find the Zipfile.
You could try to push the Zipfile again and don't wipe anything at all (because you already wiped everything) and try to find the Zip file again to flash it.
Btw what does CWM gives you as options if you click install Zip files?
Click to expand...
Click to collapse
it's all good now but now i have CWM and i need TWRP to install my stock backup
Watch this video (shows you how to change recovery in general):
http://m.youtube.com/watch?v=jnESTcH2ioA
And read this instructions if you still have some doubts and want to go for sure (recovery for LG2 D802):
http://forum.xda-developers.com/showthread.php?t=2472223
Sry I am a bit lazy right now xD Came back from work
The following is an outcome of an initial post I put up in Q&A regarding achieving root on the SM-T235 for the 5.1.1 Stock Rom (and subsequent questions and dialog with other forum members on issues) I have tried to clean up the posts here but am retaining most of them as it shows the issues other users went through (and feedback perhaps useful to some) The TWRP version is key here and it is what was seen as enabling correct flashing of the SU zip to achieve root. So hope this helps!
I used the following firmware today as a demonstration (have tried now all available 5.1.1 firmwares (successfully) except the DBT which does not flash fully for some reason)
https://www.androidfilehost.com/?fid=24269982087020611
which is AUT-T235XXU1BOH7-20151217085736.zip
ROMs are available here
http://forum.xda-developers.com/tab-4/general/links-galaxy-tab-4-official-lollipop-5-t3102844
I took out external sd (so NO EXTERNAL SD..no linkstosd nothing of the sort)
(TO NOTE-I simply took out the external SD and worked with just the internal storage for THIS demonstration to weed out the issue as other members posting on my original thread were not able to achieve the root I was able to get-it is not absolutely necessary and you could have your SU zip and any other files on the external SD however it is a good idea to keep it simple initially)
SO...I went to TWRP
TWRP is the one attached here in this post (from the thread below but may be different as the OP got updated-however the one I have attached works!)
http://forum.xda-developers.com/tab-...a1-sm-t3027059
You will see in this post that has a picture of the previous OP, the file name is what I have
http://forum.xda-developers.com/show...1&postcount=52
anyway, not sure if there are any differences but am using what works for me (the attached file)
So i did the following which may contain extra or unnecessary steps-no harm though in doing them-as I was trying to demonstrate the rooting process relative to issues other forum posters were having
(EDIT-VERIFIED-you could simply start at step 4 below where you go into download mode to flash the rom (but have the SU zip on external SD card unless it is already in the internal sdcard) and also uncheck autoreboot in Odin (do NOT check repartition!) so that once the rom has been flashed you do not have to boot up the rom, but then reset odin, again go to download mode, again uncheck autoreboot, flash TWRP, then go to recovery (do not boot rom), and flash SU zip and then only boot up-thanks frenkie9999999)
Otherwise this is what I did
1) complete wipe data, cache, system, dalvik all 2 times just for good measure
2) format internal sd (note NO external sd card) (no SIM either but that is because I need my phone working during this process and my SIM is on the T705)
3) reboot to download (do NOT install SU by twrp)
4) Used odin 1.85
5) flash the rom above (or the country firmware of your choice)
6) once device boots up do not connect to anything NO google, no wireless nothing
7) just go to settings, enable development and usb debugging (just what I do normally and mock locations) and in security allow for unknown sources, in google settings I uncheck ALL options
8) do not set up anything else
9) connect device to the laptop
10) copied over the beta 2.65 latest chainfire and root explorer apk that I have (to internal storage...see pictures...I do not have anything else in the internal card, and do not have any external card)
Chainfire's SU zip is from (credits to him for his awesome work for many many years now)
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
credit goes to K94U for this post that helped me achieve root on the T235 (not my original work as such but just listing the steps here as there were no explicit instructions for the T235)
http://forum.xda-developers.com/showpost.php?p=64182938&postcount=15
11) disconnected device from the laptop
12) went to download mode
13) odin 1.85 again and this time the TWRP recovery I have attached
14) did not let it boot up.,,,forced it to recovery by first pressing power, vol down and home to get to the choice of download or continue to reboot...
15) chose continue to reboot
16) immediately switched to power, vol up and home to get to TWRP
17) flashed the SU zip
18) do not install SU as prompted by TWRP
19) let it reboot
20) found SU in the installed apps in launcher
21) opened up SU and checked the options I want
that was it...opened root explorer and sure enough have root
Google may prompt accept. decline check apps...I always decline and then go to google settings and uncheck those pesky secuirty options as well (if not done already)
the TWRP version is important as the one I have attached works for the purpose of flashing the SU zip to get root correctly
here are the screenshots and the TWRP tar
Got xposed working too wanam arm (32) v78.1 sdk22
Sent from my SM-T235 using XDA Free mobile app
@mac231us
Doesnt work for me. Did everything as your thread guides but i still can't get the SU permissions.
Enabling SuperSU gives me the note "There is no SU binary installed[...]"
Any idea what i did wrong?
1. Flashed to 5.1.1 from CM12.1 and didn't boot
2. Flashed TWRP and booted directly to recovery
3. Flashed BETA-SuperSU-v2.62-20151210170034 and reboot
4. Got SuperSU app installed but it don't let me launch it (not installed binaries)
tyktak said:
@mac231us
Doesnt work for me. Did everything as your thread guides but i still can't get the SU permissions.
Enabling SuperSU gives me the note "There is no SU binary installed[...]"
Any idea what i did wrong?
1. Flashed to 5.1.1 from CM12.1 and didn't boot
2. Flashed TWRP and booted directly to recovery
3. Flashed BETA-SuperSU-v2.62-20151210170034 and reboot
4. Got SuperSU app installed but it don't let me launch it (not installed binaries)
Click to expand...
Click to collapse
that is odd..i just did a fresh install..wiped fully formatted...went to download (do NOT install SU as twrp prompts) odin flashed the 5.1.1 (nordic)...in fact this time even rebooted and set up google account..then went back to download...installed twrp again...again rebooted but this time straight to twrp...then installed the latest su 2.62-3...rebooted (again do not check the SU install prompted by TWRP)...and the su app was there..and so was the binary
noticed chainfire now has BETA-SuperSU-v2.64-20151220185127.zip
curious did you do a 5.1.1 odin flash from cm12.1 or a twrp nandroid recovery...just wondering if it makes a difference
twrp is from here
http://forum.xda-developers.com/tab-4/general/sm-t235-lte-rooted-twrp-2-8-alpha1-sm-t3027059
again...am only speaking of the T235 (or T235Y) not any other variant
the 5.1.1 I used is from here
https://www.androidfilehost.com/?fid=24052804347821380
in order to prevent stock recovery from coming up always first go to download step (not actual download) but using the volume down, power and home to get to the choice of download and reboot..then reboot but quickly go to volume up home and power to get to the twrp recovery
@mac231us
Aww, i cant get it working..
Did exactly what you said:
1. Format everything from TWRP (5.1.1 rom)
2. Flash 5.1.1 (nordic)
3. Configure google account
4. Back to download and flash TWRP
5. Back straight from download to recovery
6. Flash 2.62-3 and reboot (didnt checked the SU install prompted by TWRP)
7. When i open SuperSU app i am getting exactly:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgrade to Android 5.0, you need to manually re-root - consult the revelant forums for your device!
Click to expand...
Click to collapse
Btw. i am getting red and blue text when booting - Kernel is not seandroid enforcing.
Galaxy Tab 4 7.0 LTE (SM-T235)
EDIT...also
tyktak said:
@mac231us
Aww, i cant get it working..
Did exactly what you said:
1. Format everything from TWRP (5.1.1 rom)
2. Flash 5.1.1 (nordic)
3. Configure google account
4. Back to download and flash TWRP
5. Back straight from download to recovery
6. Flash 2.62-3 and reboot (didnt checked the SU install prompted by TWRP)
7. When i open SuperSU app i am getting exactly:
Btw. i am getting red and blue text when booting - Kernel is not seandroid enforcing.
Galaxy Tab 4 7.0 LTE (SM-T235)
Click to expand...
Click to collapse
cannot think of anything else at the moment except that am using older version of odin v 1.85 (i too get the red and blue text..the recovery is not default as simply rebooting to recovery takes one to the stock unless doing the 3button to download to recovery process to get to twrp)
try it again w odin 1.85 and maybe go back to the way I 'instructed' the first time (where I did not set up the rom at all and went back to straight to twrp and flashed supersu...formatting internal storage is important but think you are doing that already)
you may want to ask some of the other folks who also got root
though imo there were no explicit instructions but enough for me to go on with..here....
http://forum.xda-developers.com/tab-4/general/sm-t235-lte-rooted-twrp-2-8-alpha1-sm-t3027059/page15
except for K94U's post here which was very informative
http://forum.xda-developers.com/showpost.php?p=64182938&postcount=15
and
http://forum.xda-developers.com/tab...laxy-tab-4-t3264281/post64216314#post64216314
EDIT another thought i may have done this at some point do not recall (but not today for example on this new installation) is to format the internal card using the stock recovery itself after installation of the odin-rom
then do the other steps of twrp etc from download mode again
@mac231us
Giving up and waiting for CM13.
I've did everything exactly how it should be done and SuperSU is showing information about mising SU binary.
Tried every SuperSU zips from Chainfire but effect was the same every time even with fresh flash of nordic rom and recovery. Ive tried cleaning data through stock recovery but it didnt helped.
Thanks for trying.
tyktak said:
@mac231us
Giving up and waiting for CM13.
I've did everything exactly how it should be done and SuperSU is showing information about mising SU binary.
Tried every SuperSU zips from Chainfire but effect was the same every time even with fresh flash of nordic rom and recovery. Ive tried cleaning data through stock recovery but it didnt helped.
Thanks for trying.
Click to expand...
Click to collapse
Apparently some users need these additional steps to fix supersu:
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.6x file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk
Also, SuperSU 2.64 fixed my kernel enforcing msg on boot...
@K94U
Still the same. I'll try flash KK then LL and try again whole process instead of CM12.1 -> LL.
I will let you know if it helped.
Btw. Chainfire published version 2.65 today
tyktak said:
@K94U
Still the same. I'll try flash KK then LL and try again whole process instead of CM12.1 -> LL.
I will let you know if it helped.
Btw. Chainfire published version 2.65 today
Click to expand...
Click to collapse
another wild guess is put all your supersu zip and apk files onto the internal storage itself
you will boot into the rom (now seeing that it does not matter if you boot into rom and then go back to download, odin the twrp, flash the supersu zip or that from odin rom directly go to download again, twrp odin and then flash supersu zip as both worked for me-not sure if there really is any technical difference)
you will need to boot to rom anyway especially after formatting and in order to put the supersu apk as K94U mentioned onto the device and then go back to download and do the recovery etc steps
after yesterday's fresh install the way of booting into rom, then going back to download etc (so this process has worked 2 ways, 4 times so no fluke understand some little differences may exist) i was doing backups only to find that when i actually went to the sd card no backup was there although i could transfer files back and forth between storage and the sdcard and computer and sdcard...so finally it was the sdcard that was bad...now all is working fine with backups after switching to different sdcard and using the ridgecrop 32formatter
http://www.ridgecrop.demon.co.uk
32bit version
@mac231us
Is that possible there is something wrong with the downloaded rom and it causes the problems?
When i get "upgrading" notice after flashing, bar goes 1/4 and then show "erasing".
I'll download germany 5.1.1 and try again. Totally no idea what's wrong. Maybe Link2SD has broke mine partitions or something.. after flashing SuperSU it didn't created any folders in /system
I've unmounted my sdcard but recovery still shows it as possible to wipe.
EDIT: After flashing Germany 5.1.1 there is still Erasing in 1/4 way of upgrading software..
EDIT2: Tried again with differrent usb cable and its the same.
EDIT3: After flashing SuperSU and reboot, device is starting and there is a samsung logo for a few secs and then there is a second reboot but with sound at samsung logo.
tyktak said:
@mac231us
Is that possible there is something wrong with the downloaded rom and it causes the problems?
When i get "upgrading" notice after flashing, bar goes 1/4 and then show "erasing".
I'll download germany 5.1.1 and try again. Totally no idea what's wrong. Maybe Link2SD has broke mine partitions or something.. after flashing SuperSU it didn't created any folders in /system
I've unmounted my sdcard but recovery still shows it as possible to wipe.
EDIT: After flashing Germany 5.1.1 there is still Erasing in 1/4 way of upgrading software..
EDIT2: Tried again with differrent usb cable and its the same.
EDIT3: After flashing SuperSU and reboot, device is starting and there is a samsung logo for a few secs and then there is a second reboot but with sound at samsung logo.
Click to expand...
Click to collapse
the DBT 5.1.1 has never worked for me (flash failed always) (am in the USA btw not that it makes a difference)
the ones that have worked are (have tried all of them at one time or the other when I was experimenting getting root type control (removing unwanted system apps, deodexing etc by flashing zips to perform certain mods/functions))
do not have any special apps like link2sd...i recommend removing external sdcard altogether and just working w the internal storage for now
LTE SM-T235 XXU1BOH7 AUT Region (Switzerland)
--LTE SM-T235 XXU1BOH7 NEE Region (Nordic Countries)
--LTE SM-T235 XXU1BOH7 SER Region (Russia)
--LTE SM-T235 XXU1BOH7 SKZ Region (Kazakhstan)
tyktak said:
@mac231us
Is that possible there is something wrong with the downloaded rom and it causes the problems?
When i get "upgrading" notice after flashing, bar goes 1/4 and then show "erasing".
I'll download germany 5.1.1 and try again. Totally no idea what's wrong. Maybe Link2SD has broke mine partitions or something.. after flashing SuperSU it didn't created any folders in /system
I've unmounted my sdcard but recovery still shows it as possible to wipe.
EDIT: After flashing Germany 5.1.1 there is still Erasing in 1/4 way of upgrading software..
EDIT2: Tried again with differrent usb cable and its the same.
EDIT3: After flashing SuperSU and reboot, device is starting and there is a samsung logo for a few secs and then there is a second reboot but with sound at samsung logo.
Click to expand...
Click to collapse
Here the same for me. Like Tyktak I ve tried every every step like him but not work for me too.
I
Will do flash, root etc from scratch once more tomorrow taking pictures along the way and post here...maybe by evening U.S time
Sent from my SM-T705 using XDA Free mobile app
deleted
mostly replicated/cleaned up in the OP now
@mac231us
Thanks mate, it worked!
The reason was probably the newer TWRP which was 2.8.7.0 Add this tutorial as new topic in general section of Galaxy Tab 4.
@frenkie9999999
tyktak said:
@mac231us
Thanks mate, it worked!
The reason was probably the newer TWRP which was 2.8.7.0 Add this tutorial as new topic in general section of Galaxy Tab 4.
@frenkie9999999
Click to expand...
Click to collapse
AWESOME!...yes was thinking about the TWRP yesterday so posted it this morning along with the other steps.
have requested moderator to move the thread to the General section.
@mac231us
Don't forget to edit first post so ppl won't have any problems
YesssSSS! Twrp 2.8.1.0 !!!!
Works great!!!
Thanks Mac231us!
Thanks tyktak!
-Flash TWRP 2.8.1.0 recovery with odin3 1.85 (without re-stocking) -dont forget UNCHECK "autoreboot" on odin.
-WIPE CACHE & DALVIK
- Flash SuperSU 2.65
enjoy!
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
thanks mr. Chainfire!!!!!!
without you Android will never be the same
Thanks a lot !
I followed every step and I was successful . Everything worked .
My tablet is rooted again !
I recently bought a second hand TF700T that has been rooted with Katkiss 6.0 but it has numerous problems that I need to know which is the best way to resolve. This is what I have:
Model: TF700T
Android Version: 6.0.1
Kernel Version: 3.1.10 katkernel-tf700
Build: Katkiss-024.6.0.1
ClockworkMod Recovery v6.0.4.7
The problems I have are:-
1. It has no Play Store and I am able to download the apk file but 'can't read/open' so it won't install from download (yes I have allowed apps from unknown sources). I managed to pull the apk file using ADB but the Play Store simply opens and closes a white page.
2. If I go to settings there is a SuperSU – clicking on it I get 'Unfortunately, settings has stopped'. I don't think this should happen. I don't know how to check if Super SU Beta 2.52 is installed.
3. If I go to Accounts I have Personal (IMAP) and + Add Account where I only have Exchange and Personal (IMAP). So I can't seem to be able to select a Google Account.
Presently I have nothing on the tablet I need (i.e. no data I need to keep) so if I have to start again I am happy to do that but I'm just learning so saying 'flash the rom' or such is too vague for me at this stage. I'm also not sure what or how to get 'data as f2fs' if that is important.
If someone could assist with a clear step by step of how I might resolve these issues I'd be very grateful. Happy to provide any other info sought. Not sure if this was caused when the seller wiped his personal data before selling or what, he says Play Store was working, so don't know if he bungled the rooting or what.
I got your PM and first of all, congrats you did a good amount of reading and you are on the right track.
Your problems with Google account and Play Store are probably due to either the wrong gapps (Google apps) version or the previous owner did a wipe of /data and did not reflash properly. Yep, arm 6.0 is right, but it has to be the pico edition. Since you did buy the tablet used, it probably would be a good idea to start from scratch. At least you would then know that if something won't work, it's because of something you did.
And yes, I agree with the advice to flash the Kang TWRP recovery. I have no idea if CWM supports f2fs but I don't think so. Most people use TWRP as recovery - it's the right way to go.
So let's get you prepped:
Download the rom, gapps and SuperSU from the links in Tim's thread (first post) and put them on a microSD. http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
Then head here and download the flashable zip of the Kang TWRP recovery: http://forum.xda-developers.com/showpost.php?p=59299365&postcount=2
Also copy that to the microSD
Boot into CWM recovery, go to Install and navigate to the Kang TWRP zip.
To tell the truth I can't even remember if CWM supports the microSD but I think it does. If it doesn't you have to use adb to push the zip to internal memory and then flash it from there.
Anyway, flash the Kang TWRP and then reboot. Let it boot up, then turn the tablet off and boot via buttons (Power and Vol Down to get into bootloader, VolUp on flashing RCK) into recovery which should be TWRP at this time.
Go to Wipe > Format data > type "Yes" and go have a beer (did I mention the battery needs to be full before you start?). This will take 60 minutes plus and may look as if nothing happens but it does, don't mess with it!
Once that is done follow this guide to convert internal data to f2fs: http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Start at step 4 and ignore any instructions related to data2sd/rom2sd.
Alright, now you got a squeaky clean tablet itching for a rom.
In TWRP go to Install > navigate to the microSD and select the rom zip. If you like, you can line up the other two files to be flashed right after the rom zip:
Touch: Add another zip, and repeat this for both the gapps and the supersu zips.
Or you flash them one by one - doesn't matter. But all 3 have to be flashed without rebooting in between and the rom has to be first!
Make sure "verify zip signature" is not checked, then swipe the button.
Have another beer
Once it's done, reboot to system and set up your new rom.
You definitely want to install the SuperSU app from the Play Store. You gain root by flashing the SuperSU zip, but you need the app to manage root.
If anything is unclear: Ask!
Have fun!
I'm up to the part where I get to have a beer...haaa. Wasn't all plain sailing. Having TWRP as an img file wasn't recognised on the sd card so I was unable to flash twrp that way. I managed to push twrp using ADB. (The small issue I had here originally was when I renamed the img file from say twrp-2.8.x.x-xxx.img to twrp.img (for ease of typing in adb) it was really twrp.img.img as it appears with a zip icon on my XP. After realising this it was straightforward after putting twrp.img into the adb folder and connecting the device and accessing the command prompt:
C:\adb>adb devices (to check I'm connected)
response:
List of devices attached
(numbers&letters here) device
C:/adb>adb reboot bootloader
This reboots the device into the bootloader and you hear the device buzz
C:/adb>fastboot flash recovery twrp.img
response
sending 'recovery' (7038kb)
Okay
writing 'recovery'
Okay
finished total time etc
then
c:/adb>fastboot reboot
rebooting....
I then used the power vol down buttons and yahoo I'm in TWRP and currently at the wipe data phase.
Can't tell you how much I appreciate this help and I'll repost a report after I get further along. Hope this helps others also.
Unexpected Clean Android waiting for a ROM
Beers were great. I finished the bit of 'convert internal data to f2fs' and thought when I rebooted, well don't know what I expected but 'squeaky clean tablet itching for a rom' wasn't a still present KatKiss rom logo start but that's what happened. Then I went to 'Install > navigate to the microSD and select the rom zip' and nothing on the SD card seemed to be recognised other than a self created 'LOST.DIR' directory so I copied the files into this directory ( Heh, at least it can see this directory). So I'm now in the process of installing KatKiss, Gapp 6 pico and SU User Beta.
If I'm on the wrong track here please let me know. Cheers
Paul;
No, you're doing good. You formatted /data, so did not touch /system where the rom lives. That's why your old room still boots. /system gets formatted during installation of the new rom = squeaky clean.
Sent from my Nexus 5X using Tapatalk
berndblb said:
No, you're doing good. You formatted /data, so did not touch /system where the rom lives. That's why your old room still boots. /system gets formatted during installation of the new rom = squeaky clean.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I've completed all the instructions - changed data to f2fs and then starting with the Katkiss, then Gapp pico and SuperSU (adding one zip after the other) and rebooted. Rebooted and device installed 73 apps and took me to a welcome screen with a language dropdown and a swipe button. I can access and change the language but the swipe button won't work so I'm locked on this screen. I went back to TWRP and pressed 'reboot' but what happened was the reboot button(located bottom right), settings button above it and the two bottom buttons on the left disappeared... so from there it wouldn't reboot. I had to hold the power button down to reboot and back in the flash screen but still can't get past that.
plato2 said:
I've completed all the instructions - changed data to f2fs and then starting with the Katkiss, then Gapp pico and SuperSU (adding one zip after the other) and rebooted. Rebooted and device installed 73 apps and took me to a welcome screen with a language dropdown and a swipe button. I can access and change the language but the swipe button won't work so I'm locked on this screen. I went back to TWRP and pressed 'reboot' but what happened was the reboot button(located bottom right), settings button above it and the two bottom buttons on the left disappeared... so from there it wouldn't reboot. I had to hold the power button down to reboot and back in the flash screen but still can't get past that.
Click to expand...
Click to collapse
Heck! I did not think we needed to check your bootloader if it had Katkiss on it, but now I think we do:
Boot into fastboot and read the tiny text top left. The part with 10.6.1...... is what we need
Bootloader problem now! More beer required....
berndblb said:
Heck! I did not think we needed to check your bootloader if it had Katkiss on it, but now I think we do:
Boot into fastboot and read the tiny text top left. The part with 10.6.1...... is what we need
Click to expand...
Click to collapse
OK, I went back to the wipe data bit and did it all again.... I noted that when installing the Katkiss, Gapps and SuperU zips I saw 2 lines:
checking for md5 file
skipping md5 check: No md5 file found
Have no idea if it matters or not....
OK the tiny writing at top on fastboot (why does this have to be so small....really).
Anyway it says:
Key Driver not found.. booting as
Android CardHU-User Bootloader <2.0 e> released by "ww_epad-10.6.1.14.10-2013601" A?3
It is hard to be exact with it that small so hope that helps, but the 10.6.1.14.10 is correct can't be as sure with the last numbers though.
Thinking about a solution
plato2 said:
OK, I went back to the wipe data bit and did it all again.... I noted that when installing the Katkiss, Gapps and SuperU zips I saw 2 lines:
checking for md5 file
skipping md5 check: No md5 file found
Have no idea if it matters or not....
OK the tiny writing at top on fastboot (why does this have to be so small....really).
Anyway it says:
Key Driver not found.. booting as
Android CardHU-User Bootloader <2.0 e> released by "ww_epad-10.6.1.14.10-2013601" A?3
It is hard to be exact with it that small so hope that helps, but the 10.6.1.14.10 is correct can't be as sure with the last numbers though.
Click to expand...
Click to collapse
I've done a bit of reading and I'm currently downloading ww_10_6_1_18_SDupdate.zip
I think my next step will be to unzip this file and find the T4_SDupdate file and put it on the sdmicro in root and boot into recovery. I'm guessing it will be located and the update begin. After that I'm not sure of what to expect. Will I have to go and flash twrp, wipe date, change to f2fs and install Katkiss,Gapps and SuperSU again? Will it matter if other files (TWRP, Katkiss, Gapps,SuperSU) are also on the microsd while this happens. If you could let me know if I'm on the right track that would be great.
plato2 said:
I've done a bit of reading and I'm currently downloading ww_10_6_1_18_SDupdate.zip
I think my next step will be to unzip this file and find the T4_SDupdate file and put it on the sdmicro in root and boot into recovery. I'm guessing it will be located and the update begin. After that I'm not sure of what to expect. Will I have to go and flash twrp, wipe date, change to f2fs and install Katkiss,Gapps and SuperSU again? Will it matter if other files (TWRP, Katkiss, Gapps,SuperSU) are also on the microsd while this happens. If you could let me know if I'm on the right track that would be great.
Click to expand...
Click to collapse
Sorry, that should be 22_10_26_1_18_SDupdate.zip
plato2 said:
Sorry, that should be 22_10_26_1_18_SDupdate.zip
Click to expand...
Click to collapse
Third time luck...(should be) ww_10_26_1_18_SDupdate.zip
plato2 said:
Third time luck...(should be) ww_10_26_1_18_SDupdate.zip
Click to expand...
Click to collapse
Don't do that!!
Whatever it is that is not firmware for the TF700!
You are on the latest bootloader, no reason to mess with it!!
---------- Post added at 09:29 AM ---------- Previous post was at 09:28 AM ----------
Give me some time, I'll get back to you
Sent from my Nexus 5X using Tapatalk
That was TF701 firmware you were thinking to flash. It is totally incompatible with your tablet and the T4 SD Update method works only with stock recovery. But all that aside....
Ok, what you experience is quite weird and I have no idea what caused it. Maybe a bad download maybe something went wrong during the flash - I have no idea...
So what is your situation now? Can you reboot from TWRP? Does the recovery work normally?
Because if not, that is the first thing you need to fix.
You may want to reflash TWRP anyway - just to be sure it did not get corrupted. You know how to flash in fastboot - excellent! Then let's do it that way.
Download from the first link for Kang TWRP 2.8.7.4. https://www.androidfilehost.com/?fid=24352994023705509
Look at the info under "Download information" on that page: You'll see the md5 checksum for that file. That is control value to make sure the file you downloaded is complete and not corrupted.
You'll need a small program like Hashtab on your PC to check the md5. Install it, then right click on a zip, go to Properties and there you'll see a new tab: FileHashes. Copy the string from the download page into the "Compare" box and it instantly tells you if the file you have on your PC matches the one on the server. TWRP has a feature that it will compare the md5 if you have it along with the zip in form of a small text file on your microSD. If it doesn't find a md5 it just skips the integrity check.
Your microSD - something else to check. That TWRP doesn't see the downloaded files unless they are in the LOST directory is totally crazy. How is that microSD formatted? You got another one you can use? One that actually works and does not add another question mark to this situation? If not, at least format the microSD to fat32 on your PC, load your files and then check if TWRP sees them. Also check the md5 AFTER copying the files to the card.....
Do that with all the files you downloaded.
So, first thing is to flash TWRP again. Then make sure it works, you can reboot from it etc.
Then just perform a quick wipe in TWRP. From Home select Wipe > swipe the button > done
Then reflash the rom zip, gapps and supersu on which you checked the md5.
Let me know how that goes.....
Thanks for that info. No I wasn't going to do anything stupid without you OKing it first.
I redownloaded Kang TWRP 2.8.7.4 and pushed it again successfully with adb no problem. I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU. Still frozen on front screen of rom. I put the twrp.img file onto the micro SD Card and tried to flash. It gives me an option to select staging which I didn't tick so it tells me no partitions selected for flashing. Didn't want to tick something and stuff it up. I think TWRP is OK as it did work fine before I installed the other 3 programs.
The micro SD is fine it's FAT32 formatted. The issue with the recovery program not seeing the zip files in the root dir was when I was using CWM - no longer a problem.
plato2 said:
Thanks for that info. No I wasn't going to do anything stupid without you OKing it first.
I redownloaded Kang TWRP 2.8.7.4 and pushed it again successfully with adb no problem. I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU. Still frozen on front screen of rom. I put the twrp.img file onto the micro SD Card and tried to flash. It gives me an option to select staging which I didn't tick so it tells me no partitions selected for flashing. Didn't want to tick something and stuff it up. I think TWRP is OK as it did work fine before I installed the other 3 programs.
The micro SD is fine it's FAT32 formatted. The issue with the recovery program not seeing the zip files in the root dir was when I was using CWM - no longer a problem.
Click to expand...
Click to collapse
There's some fundamental flaw in your thinking: You cannot flash the .img file in TWRP.
twrp_tf700t_kang_2.8.7.4.img - this file you have to flash in fastboot (fastboot flash recovery twrp_tf700t_kang_2.8.7.4.img)
twrp_tf700t_kang_2.8.7.4-signed.zip - this is the same recovery packaged into a flashable zip. This you can flash in recovery
I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU
Click to expand...
Click to collapse
You mean rebooting from recovery??? That sentence does not make sense. And something else is going on. Flashing a rom, gapps, supersu cannot have anything to do with your recovery not working properly. The recovery lives on it's own partition and boots from there.
Maybe time to take a break and retrace your steps. I cannot put my finger on it but somewhere you are doing something wrong.
Edit: Ha! Interesting! Just remembered that something changed in TWRP and yes, this latest version lets you flash an .img file to staging (from where it will get installed to it's proper partition during the next boot). I have no idea how solid this new feature is, so I'd still recommend falshing TWRP in fastboot.
But 2.8.7.4 works fine flashing Katkiss and associated files. Tried it myself this afternoon. All the components work. So the problem is most likely in the "how", not the "what".....
Sorry for the confusion. Really can't see what I may be doing wrong here. I followed exactly the same procedure as I did when I installed TWRP over CWM initially. I re-downloaded twrp_tf700t_kang_2.8.7.4.img , placed it in the adb folder and renamed it twrp.img. I then followed the same procedure I did originally:
C:\adb>adb devices (to check I'm connected)
response:
List of devices attached
(numbers&letters here) device
C:/adb>adb reboot bootloader
This reboots the device into the bootloader and you hear the device buzz
C:/adb>fastboot flash recovery twrp.img
response
sending 'recovery' (7038kb)
Okay
writing 'recovery'
Okay
finished total time etc
then
c:/adb>fastboot reboot
rebooting....
However, this time the response to the last command:
c:/adb>fastboot reboot
(waiting for device) and it hangs and the device doesn't reboot from recovery. However, all the other stuff before it is the same. Not sure what to try next.
plato2 said:
However, this time the response to the last command:
c:/adb>fastboot reboot
(waiting for device) and it hangs and the device doesn't reboot from recovery. However, all the other stuff before it is the same. Not sure what to try next.
Click to expand...
Click to collapse
Elaborate on this please.
You are in fastboot.
The command fastboot reboot does nothing?
Then what? Did you reboot manually?
You are not in recovery here, so i do not understand "the device does not reboot from recovery".....
Sorry, my lack of understanding. I suppose I mean I am in the bootloader which is where adb>reboot>bootloader puts me so that I can flash twrp.img. Then to get out of there and go back to the rom fastboot>reboot would put me back into the rom and I would get the response >rebooting. Now that doesn't happen it simply says (waiting for device)....So I have to reboot manually.
Just got home and playing around with it. I went into the bootloader and installed just the katkiss rom. It installed fine and then I clicked reboot and it rebooted no problem. But of course that doesn't give me any Play Store or SuperSU.... so there's still hope. So now I'm back in the bootloader and going to try the 3 together again and see what happens.Let you know shortly
Setup wizerd stopped - google play services stopped
plato2 said:
Just got home and playing around with it. I went into the bootloader and installed just the katkiss rom. It installed fine and then I clicked reboot and it rebooted no problem. But of course that doesn't give me any Play Store or SuperSU.... so there's still hope. So now I'm back in the bootloader and going to try the 3 together again and see what happens.Let you know shortly
Click to expand...
Click to collapse
So now when I install the katkiss, Gapps and SuperSU from TWRP and reboot I get 2 repeating messages Setup wizerd has stopped' and Google Play Services has stopped. It just goes from one to the other when I press OK....
my eMMC is 11
Phone is a SG900V
How do I get from 4.4 to 5.0 once I've installed everything? I followed the below tutorial and was able to get root and everything working on 4.4 but once I try and flash the MMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip from Safestrap the phone wont boot. Been trying different things from a few hours now I'm lost. Need 5.0 for android auto rooting this old phone to try and get carstream up.
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Directions For Users With CID 11' Toshiba eMMC
1. Download EMMC_11_ Root S5_QB2_PB1.zip
2. Unzip Copy RootS5 Folder To Your External SDCard and EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip and the EMMC_11_QB2_6_0_1_MM_Firmware_Bootloaders.zip and ChooseEMMC_11_PB1_LL_STOCK_SAFESTRAP_ONLY.zip .
3. Reboot Phone to Download Mode (Pwr +Vol Dwn+Home)
4. Use Odin 3.12 and load the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_257265 6_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
5. Flash let phone reboot. It will reboot to recovery and finish install then it will reboot and take a few minutes to get booted up.
6. Once computer recognizes the phone If you didnt have an ExtSDCard copy the Root S5 Folder to internal storage of phone and the EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip and the EMMC_11_QB2_6_0_1_MM_Firmware_Bootloaders.zip to Internal Storage and ChooseEMMC_11_PB1_LL_STOCK_SAFESTRAP_ONLY.zip .
7. Use the File Manager in the Apps drawer of the phone and install Apex_Lancher.apk press home button set Apex as default launcher continue to install Superuser.apk and the Busybox.apk and the SafeStrapKK.apk do not open any of those yet
8. Now Install tr_v2.apk open and CLICK MAKE IT RAIN . It should tell you you have succeeded.
9. Now Open Superuser app and click install binary normally. Once done it will tell you you need to reboot. You can skip doing this. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
10. Now Open BusyBox app grant SuperSU access and install BusyBox
11. Now Open Safestrap grant SuperSu access and click install recovery. If the SafeStrap recovery fails to install make sure BusyBox is installed by rerunning the BusyBox app it will tell you if BusyBox is installed if not click install again reboot phone and open Safestrap and try to install recovery again
12. Do Not Change Or Mess With Boot Options In SafeStrap. Rom Slots Cannot Be Used You Must Flash To Stock Rom Slot. Some Functions Do not work in Safestrap Click Choosing a image file to flash directly. All image files must be flashed via zip file
13. Once Safestrap recovery is installed click reboot to safestrap recovery
14. Once in safestrap recovery Choose Wipe. Click on advanced wipe. Select Dalvick Cache; Data; System: Cache. Click Swipe to wipe bar. When finished wiping click the back button
15. Install ChooseEMMC_11_PB1_LL_STOCK_SAFESTRAP_ONLY.zip
16. If your running ChooseEMMC_11_PB1_LL_STOCK_SAFESTRAP_ONLY.zip SafeStrap is preinstalled and there is no need to flash kernels to exit and leave safestrap it is done automatically.
Click to expand...
Click to collapse
My fault I didnt follow the last step 15. Install ChooseEMMC_11_PB1_LL_STOCK_SAFESTRAP_ONLY.zip I was thinking I needed 5.0