Database Info

[Q] Problem during rooting help

I was attempting to get root access to my galaxy tab 2 10.1 running android 10.2.1 (or whatever the latest Samsung update was it is 10.2 on my phone but am sure it was 10.2.1 on the tablet.
I was following this guide that someone here recommended
http://www.ibtimes.co.uk/articles/4...-p5113-android41-jellybean-android404-ics.htm
I set usb debug and made sure the drivers were on my pc and made sure KIES was completely not running
Followed the instructions to the letter but should have worried when I found the instructions to get to download were wrong - I found on videos that it was reboot using power and right volume key. That was successful
It connected to ODIN fine and the yellow box came up
I made sure the two boxes were ticked and then searched for the file
CF-Auto-Root-espresso10wifi-espresso10wifibby-gtp5113.zip and started ODIN
it seemed to be going fine until suddenly a red box came up with update failed
Now all I can get on the device is "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
No matter how I try to restart this I get the same screen and imagine I couldn't connect to kies even if I should
Can anyone help as I am worried that I have bricked my device - I was looking for a simple way to get root without flashing a whole rom - or is that what I was doing anyway?

Here is a link that may can help you : http://forum.xda-developers.com/showthread.php?t=1722745
Try to do the point A to install CWM Recovery and root correctly the tab then do the point E to install the stock Android 4.0.4
ps : if you want to do something to your tab, try to search here before other websites, big community, good informations/tips (personnal advise) :good:

Maybe file you downloaded is corrupted , redownload it from xda or sammobile and do steps again

n0is said:
Here is a link that may can help you : http://forum.xda-developers.com/showthread.php?t=1722745
Try to do the point A to install CWM Recovery and root correctly the tab then do the point E to install the stock Android 4.0.4
ps : if you want to do something to your tab, try to search here before other websites, big community, good informations/tips (personnal advise) :good:
Click to expand...
Click to collapse
I will take a look but so far the only thing I get is the message to connect to KIES and it wont of course connect - cant get into any other modes - you would think they would have some kind of hard boot recovery button that gets you to basic screen to download the latest firmware.
And I did start here and believe that this led from a post here - I was trying to find the least complicated method of getting root access without changing what I already had too much - the only other process that I found on here seemed to have lots of people reporting problems if it wasn't a 3g model
It is beginning to look like I may have found out what bricking is - thanks for the reply anyway

would like to do that
mjrshark said:
Maybe file you downloaded is corrupted , redownload it from xda or sammobile and do steps again
Click to expand...
Click to collapse
In fact the instructions do say if it doesn't work first time, to run it again with the boxes unticked - the problem is that I cant get back to download mode, or any mode other than the message to connect to kies, so have no way of doing this. So looks like it may have bricked - is there any way of unbricking a tablet?:crying:
It's going to be an expensive mistake especially as I haven't even had the £50 cash back from Samsung yet and I would have to pay full price now to replace it,

So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium

not optamistic but will try!
samsgun357 said:
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I will try but I don't think it is going to work. Whenever I connect the tablet by USB I get the usb connecting sound followed immediately by the USB disconnect sound - this just continues to happen every 4 seconds or so all the time that the device is connected. At the moment I have it on charge as once the error screen comes on it doesnt seem to go off for a very long time and then it wont start unless I charge it first. After a few minutes on charge - The firmware upgrade encountered an issue message comes up. I am going to leave it a while until I am sure it is fully charged and then try what you suggest - not optamistic though since I now realise that it is not even connecting properly. I just have a bad feeling about this. I had to disconnect it from the power yesterday because the error screen stays on continuously and the device starts to get warm
Assuming that I ever manage to get a stock image installed will this mean I can go back to normal kies updates - all I really wanted was the standard samsung android O/S but with super user added.
Unfortunately I had read the linked article a while back and what made me more confident was the statement that said it was "virtually impossible to brick this device"

Since it's still going into Charging mode and spitting out error messages, it's not completely bricked. It's just in a reboot loop (a.k.a. soft brick).
Keep trying to get it into Download mode. Sometimes the timing is a little tricky if it's in a boot loop.
1. Disconnect it before trying to get it into Download Mode. If it's plugged in (charger or PC), the device will go into Charging mode instead.
2. Hold the Power button for 10 seconds to make it reboot.
3. When you see the screen turn off, let go of Power and then press and hold Power and Volume Right/Up.
4. If done correctly, it will immediately go into Download Mode. If you see the Samsung logo instead, repeat from Step 2.

some progress but still stuck - any more ideas please
samsgun357 said:
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Hi well thanks -
when I connected Odin it did show up yellow and so I downloaded the P5110 stock from from the other thread - all went well and it reported all OK and re-booted - saw the animated sequence but now it has stalled on the samsung logo and still wont connect to kies
So still stuck but at least it has moved on - The instructions on the other page were a little unclear about one stage
It said if there was pit file included to set something and tick repartition - this was all in one line and so I assumed part of the pit instruction - as there was no pit file I did not tick re-partition - I wonder if I should have done?
I have just reconnected to ODIN and the ID Com is still lit up yellow so presumably I could try running it again, or should I look on here for another stock rom - I am wondering if I have somehpw scewed up the bootloader and if so how I go about restoring it
ODIN is the only thing it connects to right now

System Software not authorized by verizon wireless has been found on your phone

I need help guys,
I used Odin to root the phone and did my first custom rom which is the clean rom...it went through the process and when it was about to reboot i got the system software not approved by verizon and take phone to store
I have been told to odin back to stock but it wont let me. The stock image on odin wont work it says fail
I tried the first method and used odin in download mode to flash the stock image
Failed:
This is what I get
added
Odin V3 engine
File Analysis
all threads completed (succeed 0 / Fail 1)
In the Odin Download mode on the phone the top left reads as follow
Odin Mode (Red Letters)
Product Name (SCH-I535)
Custom Binary Download : Yes (1 counts )
Current Binary Custom
System Status Custom
Qualcomm Secureboot: Enable

One thing I gotta mention is that when I got the phone last week it had an OTA update from Verizon which I did install and then a few days later I rooted the phone and when I tried to use Clean Rom it gave me the dreaded Verizon message

Sounds like you didn't unlock the bootloader.

Ya your bootloader is locked again ... unlock it and redo the steps everything should be fine after that

Guys I know that the bootloader is locked but i cannot get back to stock to unroot phone and then unlock the bootloader
Odin recognizes phone but the stock image goes into fail mode right away
I cannot get into recovery and the only thing I can do is go to download mode and Odin but nothing else

http://forum.xda-developers.com/showthread.php?t=1840030&highlight=jtag
http://forum.xda-developers.com/showthread.php?t=1798850
http://rootzwiki.com/topic/29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii/
http://www.android.gs/fix-bricked-verizon-galaxy-s3/
one of these may be able to help you ... i lost the original link i had but saved these for bootloader issues hope they help they should

Stranger_84 said:
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=jtag
http://forum.xda-developers.com/showthread.php?t=1798850
http://rootzwiki.com/topic/29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii/
http://www.android.gs/fix-bricked-verizon-galaxy-s3/
one of these may be able to help you ... i lost the original link i had but saved these for bootloader issues hope they help they should
Click to expand...
Click to collapse
You are aware he can Odin flashed the latest OTA instead of that you have provided. Here it is :http://forum.xda-developers.com/showthread.php?t=2046439. This will also help fix his phone being that it is recent. Forgot this link to get him back on track: http://forum.xda-developers.com/showthread.php?t=1974114.

i thought thats what he already tried? but yes you can odin any ota file being that an unlocked bootloader isnt needed.

When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time

I'm not sure being ive never had that issues ... im sorry and good luck

try flashing odin stock ROM, not bootchain

NYGiants4Natic said:
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
Click to expand...
Click to collapse
Did you put the file in PDA in Odin they only work if you checked PDA.

NYGiants4Natic said:
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
Click to expand...
Click to collapse
I had a similar issue once. This helpful post by h3llsdr0id eventually got me up and running. Took a total of like 4 hours though lol.
http://forum.xda-developers.com/showpost.php?p=30569324&postcount=26
Make sure you have the correct files. This is for the original root66 so it's ICS. Once I booted up and activated I took the Verizon OTAs all the way to JB and then rooted/unlocked bootloader.
edit: I actually had to go back to ICS to reprovision my SIM so not sure you have to go through all of this. Try to odin stock JB ROM like mentioned above.

Thank YOU so much guys you have made my day.
After trying all last night and today I got it back to stock with the OTA file through ODIN. That is all I needed and it went right back to brand new stock phone using 4.1.1
WOW.
I thought I was going to have a dead phone.
Thank you all

Glad you got it up and working!!!!!

Yea I had the same problem but all it needed was a handy flash back to stock. The good thing with making these mistakes is that if it happens again you know what to do.
Sent from my SCH-I535 using xda app-developers app

I'm having the same problem and can't get into download mode
Gatanater said:
Yea I had the same problem but all it needed was a handy flash back to stock. The good thing with making these mistakes is that if it happens again you know what to do.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Hi there,
Could someone please help me. I bricked my phone 3 days go and went through odin and root66 stock to unbrick it. I installed CWR and backed up everything, then i purchased triangle away to reset the flash counter. When I did that I got the software not authorized by verizon error screen. It won't let me get into download mode or recovery. Can I still try to use odin? What should I do? I'd really appreciate some help today is the 4th day I have been trying to fix my phone, only to make it worse.
Thank you in advance

You have to get into download mode to use Odin. It will go into download mode, if you will search, there are ways to pull battery along with button combo to get it there. After rooting, use EZ Unlock 1.2 and that will unlock your bootloader without then unauthorized message from Verizon. Make sure you use only that version, the others don't work.

Re: I'm having the same problem and can't get into download mode
mj76 said:
Hi there,
Could someone please help me. I bricked my phone 3 days go and went through odin and root66 stock to unbrick it. I installed CWR and backed up everything, then i purchased triangle away to reset the flash counter. When I did that I got the software not authorized by verizon error screen. It won't let me get into download mode or recovery. Can I still try to use odin? What should I do? I'd really appreciate some help today is the 4th day I have been trying to fix my phone, only to make it worse.
Thank you in advance
Click to expand...
Click to collapse
Pull battery, hold volume down+home+power keys while you put the battery back in. If that's too many buttons to fumble with at the same time you can try pulling battery, put it back, hold all three keys while plugging it into your computer. My old phone worked that way, idk about the s3. You SHOULD get the download triangle and it asking you if you want to continue. Hit volume up to continue then plug it in and odin should recognize it. Get the stock rom image to flash in the PDA slot of odin. Accept the OTA's until you're up to date then unlock bootloader, root, then flash custom roms/kernels AFTER you've done the appropriate reading. Theres a sticky in development takes you step by step on how to unbrick, then unlock and root. Those should help once you get into download. Hope this helps! :fingers-crossed:

flammablepez said:
Pull battery, hold volume down+home+power keys while you put the battery back in. If that's too many buttons to fumble with at the same time you can try pulling battery, put it back, hold all three keys while plugging it into your computer. My old phone worked that way, idk about the s3. You SHOULD get the download triangle and it asking you if you want to continue. Hit volume up to continue then plug it in and odin should recognize it. Get the stock rom image to flash in the PDA slot of odin. Accept the OTA's until you're up to date then unlock bootloader, root, then flash custom roms/kernels AFTER you've done the appropriate reading. Theres a sticky in development takes you step by step on how to unbrick, then unlock and root. Those should help once you get into download. Hope this helps! :fingers-crossed:
Click to expand...
Click to collapse
Thank you for your response. I tried pulling the battery out and holding volume down, home and power keys at the same time while putting battery in, even as i plugged it into my phone, but nothing but the unauthorized error screen comes up. I should note that my phone is note 2 not s3. I apologize for posting it here, but this thread seemed to be just like the problem i was having.

Help?

I did this: http://forum.xda-developers.com/showthread.php?t=2046439 then attempted to put CM10(http://forum.xda-developers.com/showthread.php?t=1840414) on the phone. I downloaded the stable version for Verizon wireless and made sure it was correct etc. I went to TWRP and put install then went to the .zip and continued after doing that the phone resets saying "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.". I am not entirely sure what I did wrong but it will no longer let me enter twrp but it does let me go to the download screen. Did I brick it or what? Thanks.

ryan7654321 said:
I did this: http://forum.xda-developers.com/showthread.php?t=2046439 then attempted to put CM10(http://forum.xda-developers.com/showthread.php?t=1840414) on the phone. I downloaded the stable version for Verizon wireless and made sure it was correct etc. I went to TWRP and put install then went to the .zip and continued after doing that the phone resets saying "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.". I am not entirely sure what I did wrong but it will no longer let me enter twrp but it does let me go to the download screen. Did I brick it or what? Thanks.
Click to expand...
Click to collapse
That method did that too me as well. use this instead
http://forum.xda-developers.com/showthread.php?t=2332825
You didn't brick it I had that pop up my first flash as well
Pretty sure It was because it didn't unlock the bootloader correctly.
http://forum.xda-developers.com/showthread.php?t=2199042

spitfire143 said:
That method did that too me as well. use this instead
http://forum.xda-developers.com/showthread.php?t=2332825
You didn't brick it I had that pop up my first flash as well
Pretty sure It was because it didn't unlock the bootloader correctly.
http://forum.xda-developers.com/showthread.php?t=2199042
Click to expand...
Click to collapse
How do I use odin to put the bootloader file on my phone since it's not an .md5 file etc.? Sorry, just don't understand.

" I held volume down/home for a few seconds and then held power. The phone booted to a mode I had not seen before (recovery/download as you said?) and I said cancel and the phone booted!"
Boot normal. use tool in first link to unlock the bootloader and CM should be up and running
---------- Post added at 02:00 AM ---------- Previous post was at 01:58 AM ----------
also you should be able to get into recovery just let go of the volume, power, home as soon as you see the samsung logo pop up

spitfire143 said:
" I held volume down/home for a few seconds and then held power. The phone booted to a mode I had not seen before (recovery/download as you said?) and I said cancel and the phone booted!"
Boot normal. use tool in first link to unlock the bootloader and CM should be up and running
---------- Post added at 02:00 AM ---------- Previous post was at 01:58 AM ----------
also you should be able to get into recovery just let go of the volume, power, home as soon as you see the samsung logo pop up
Click to expand...
Click to collapse
I did the hold the volume button down/home at same time then press power but that sends me to the normal do I want to download press up to continue or down to cancel. I pressed down and it still gave me the warning. I try going to recovery but it prevents me by telling me the same message. I think it's the bootloader like you said but I don't understand how to get the file on the phone through oden. I downloaded that first link but it won't go through oden because it's not the .md5 etc and the computer isn't showing me the phone data through my files.
I am going to odin flash a stock image then re-boot.

I reflashed the phone using odin. I went through and used the "casual" rooting process which appeared to work. I went into twerp then pressed install then pressed the .zip for the CM mod. It re-loaded and now it's stuck on the CyanogenMod screen with a circle. I don't understand if it's installing or what?
I understand now why it wasn't working. Answer in here: http://forum.xda-developers.com/showthread.php?p=36341274 Anyways, now that I got CM to work. GAPPS refuses to work, it sends an error message saying that the Setup Wizard has failed. I don't understand that.
Checked to make sure the GAPPS version I downloaded was the one compatibale with the CM version, it was not so I re-downloaded the correct version now everything is working great. Thanks spitfire143 for all the help and getting me on the right track!

[Q] Bricked - please help!

Hey guys,
I managed to f*** up my phone and don't know exactly what went wrong. I'm worried it's a hard brick, but don't know for sure. It won't turn on though, which is freaking me out. I hope one of y'all can help.
So I was running CM10.1 for a long time and everything was great. I eventually installed an update through the built-in CM updater app, decided I didn't like it, and attempted to re-install through the .zip I still had on my sdcard. I'm still not sure why, but doing so put me in a boot-loop. I was pretty busy at the time so just flashed back to stock. Wasn't ideal, but worked fine.
So now I have some free time and decided I'd try to re-install CM. Prior to the install attempt, I was running 4.1.2 stock, rooted and with an unlocked bootloader. Here's what I did:
1: Flashed the VRALEC bootloader, as recommended by the CM wiki, through Odin.
-At this point, everything still worked OK. I think this next step is where I went wrong.
2: Flashed the VRALF2 kernel through Odin.
-This is what I think I did wrong. After I flashed it, instead of booting up the phone got past the Galaxy S3 graphic then the LED just slowly changed from blue to light blue and back. Either way, I still was able to do the following steps.
3: Flashed CWM 6.0.1.2 through Odin.
4: Installed CM10.2 and gapps from recovery.
5: Rebooted, stuck in a boot-loop showing the CM logo.
So hindsight being 20/20, this is where I should have stopped and asked for help. Instead, I decided that I'd try to fix it myself and tried to flash back to stock. When I tried to do so, Odin said it failed. I then reflashed the VRALEC bootloader, again through Odin. This was successful, but after it rebooted, it showed the Galaxy S3 graphic for a bit and then went blank. Since then, I can't get the phone to turn on or enter download or recovery modes.
Can anyone help? I'm really worried I hard-bricked my phone. What do I need to do / where can I go from here?

Update - Maybe not hard-bricked!
berichardson13 said:
Since then, I can't get the phone to turn on or enter download or recovery modes.
Click to expand...
Click to collapse
So I've managed to get the phone into recovery mode, which is the factory recovery (not CWM). And I can also get into download mode. But when I start up the phone, it stops at the "Samsung Galaxy S III" graphic and just stays there. From that screen, I can only get it to turn off by taking out the battery.
Hopefully this means I'm not hard-bricked. Does anyone know what I can do from here to get it functional again?

berichardson13 said:
So I've managed to get the phone into recovery mode, which is the factory recovery (not CWM). And I can also get into download mode. But when I start up the phone, it stops at the "Samsung Galaxy S III" graphic and just stays there. From that screen, I can only get it to turn off by taking out the battery.
Hopefully this means I'm not hard-bricked. Does anyone know what I can do from here to get it functional again?
Click to expand...
Click to collapse
If you can get into recovery/download, you are definitely not hardbricked. Try to do a factory reset in recovery. If that doesn't work try to ODIN a full stock image.
*your internal storage will be wiped with a factory reset (obviously).
I'm pretty sure they recommend flashing the newer CM's from the MF1 base. I might be making that up though.

Sounds like you forgot to flash something, check the thread you used again
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
If you have a blue led light after the Samsung galaxy s3 screen when it goes black then you don't have the proper drivers for your screen which would be in the file you didn't flash
Sent from my SCH-I535 using XDA Premium 4 mobile app

BattsNotIncld said:
If you can get into recovery/download, you are definitely not hardbricked. Try to do a factory reset in recovery. If that doesn't work try to ODIN a full stock image.
Click to expand...
Click to collapse
Tried the factory reset, ended up in the same spot. So, next I'll try flashing back to stock.
I've done this before, but after the scare earlier I'm being overly paranoid - am I going to need to flash a different kernel? Or is it gonna be enough to just flash something like the VRBMF1 image?

Flash back to stock 4.1.2, use Casual to root and unlock, and get a recovery.
http://forum.xda-developers.com/showthread.php?p=42791826
Sent from my Last Ever Samsung Device.

0331 said:
use Casual to root and unlock, and get a recovery.
Click to expand...
Click to collapse
So this is another dumb question. But having just downloaded the newest version of Java to my Windows 7 computer, I still can't get Casual to open. Instead, this command prompt dialogue box pops up for a little bit then disappears. Nothing else happens after that. I'm opening it with JRE 1.7 - should I be doing something differently?
Edit - I just opened it in terminal, got it going fine, but can't get Casual to recognize my phone. I'm about to update the drivers, see if that does the trick.

berichardson13 said:
So this is another dumb question. But having just downloaded the newest version of Java to my Windows 7 computer, I still can't get Casual to open. Instead, this command prompt dialogue box pops up for a little bit then disappears. Nothing else happens after that. I'm opening it with JRE 1.7 - should I be doing something differently?
Edit - I just opened it in terminal, got it going fine, but can't get Casual to recognize my phone. I'm about to update the drivers, see if that does the trick
Click to expand...
Click to collapse
If it still doesn't work, try the slightly older version of Casual: http://rootzwiki.com/topic/44201-★-casualroot-unlock-recovery-1-click-all-otas★/
Sent from my SCH-I535 using Tapatalk 4

Phone booting to secure fail:kernel

Okay so I didn't do the proper research when attempting to root my mother's phone.
She was on 4.3 already (must've updated automatically at some point)
What I did was first root it using the 4.3 root method. Then I realized I couldn't flash a kernel without a CWM. So I tried to flash CWM via terminal. When I tried to boot to recovery it was giving me Secure Fail: Kernel, I figured that I did something wrong. I flashed it again using GooManager. Now I pressed reboot recovery and same thing. So I realized I wasn't unlocked yet -oops.
I was going to download ez-unlock then but now, unlike when I flashed TWRP from terminal, I can no longer boot up the phone. Even without holding the vol up+home+power, it always starts to say booting recovery and I end up at the Secure Fail: Kernel screen that says "System software not authorized by VZW blah blah"
So did I brick her phone? And is there a way to fix it? I figured maybe I can odin back to stock or something?

There are more threads here about fixing a bricked 4.3 phone.
Try getting into download mode first with vol down-home-power method. If the phone will stay in download mode, then you should look into reflashing things back to stock to unbrick. On this forum area there are a few threads some sticky check them out

vax1170 said:
There are more threads here about fixing a bricked 4.3 phone.
Try getting into download mode first with vol down-home-power method. If the phone will stay in download mode, then you should look into reflashing things back to stock to unbrick. On this forum area there are a few threads some sticky check them out
Click to expand...
Click to collapse
Wow. I appologize for not searching properly. It is actually somewhat embarassing that it is the top sticky. I must've looked through 5 pages in general and forgot to check this forum. Sorry about that.