Database Info

Help T_T I think im bricked: ( turns out bootloader didn't unlock...

i flashed a stick rom and now getting unathorized software message on boot and cant get in to the phone, but I do have access to odin, am i screwed or what : (

moocowgal said:
i flashed a stick rom and now getting unathorized software message on boot and cant get in to the phone, but I do have access to odin, am i screwed or what : (
Click to expand...
Click to collapse
Go to my guide and follow section 6....also try reading a couple threads before posting. This the whole reason why verizon locked the darn bootloader in the first place. Research then flash, dont flash then research!!!

Edited for incorrect advice.

voodoomanx said:
http://forum.xda-developers.com/showthread.php?t=1762204
Download and flash root66 with odin. What stock rom gave you the triangle?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This is incorrect...you must flash the stock kernel before flashing a stock rom in odin. Op go to my guide and follow section 6.

I suggest doing a factory reset in recovery, immediately after you flash root66. My phone would not finish booting after ODIN'ing root66 coming from BeansRom 9. It was sticking at the Verizon 4g boot image for 20 minutes.

droidstyle said:
This is incorrect...you must flash the stock kernel before flashing a stock rom in odin. Op go to my guide and follow section 6.
Click to expand...
Click to collapse
Depends on what rom he flashed. That's why I asked. If he flashed a stock rom with stock kernel flashing root 66 in odin would work.
Sent from my SCH-I535 using xda app-developers app

voodoomanx said:
Depends on what rom he flashed. That's why I asked. If he flashed a stock rom with stock kernel flashing root 66 in odin would work.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Read the op...she is getting the verizon triangle of death...that means one thing, either she flashed a custom recovery via odin or flashed a custom rom that was packaged with a custom kernel on a locked bootloader. The advice you gave is incorrect for this situation. Im not here to argue, im here to help pass along correct information to keep bricks at a minimum. Sometimes i may come off a bit brash, but im just trying to get the point across. Seems silly to take a 600.00 device and turn it into a paper weight all because lack of research don it?

droidstyle said:
Read the op...she is getting the verizon triangle of death...that means one thing, either she flashed a custom recovery via odin or flashed a custom rom that was packaged with a custom kernel on a locked bootloader. The advice you gave is incorrect for this situation. Im not here to argue, im here to help pass along correct information to keep bricks at a minimum. Sometimes i may come off a bit brash, but im just trying to get the point across. Seems silly to take a 600.00 device and turn it into a paper weight all because lack of research don it?
Click to expand...
Click to collapse
All I did was ask what rom they attempted to flash. I don't care either way. Your guides have gotten me out of a couple jams. I wish people would read them first.
I'm also getting sick of all the warranty fraud going on.
Now that I reread the OP you are correct. I will edit my reply so as not mislead anyone.
Sent from my SCH-I535 using xda app-developers app

voodoomanx said:
All I did was ask what rom they attempted to flash. I don't care either way. Your guides have gotten me out of a couple jams. I wish people would read them first.
I'm also getting sick of all the warranty fraud going on.
Now that I reread the OP you are correct. I will edit my reply so as not mislead anyone.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
We all misread a post from time to time no biggie. You corrected me on a post in the ez unlock thread. The end result is to make sure the right information is getting passed around. :highfive:

Just saying. Nice catch droidstyle on saying "she" . I thought that was cool. Lol
Sent from my SCH-I535 using xda premium

"Unauthorized Software Found" Notice -- How to reset it?

Hi guys.
So I am very new to the Verizon Galaxy S3, and I didn't see this question anywhere that I looked in this section so forgive me anyways if it has been posted before.
After flashing the cm10 nightly from 2012-10-05 (October 5) I got the unauthorized software notice and I can't get it to go away.
Does anybody know how to reset it?
Help is much appreciated.
Thanks.
--Sam

You will have to Odin back to stock and start over. That message means you did not unlock your bootloader.

apacseven said:
You will have to Odin back to stock and start over. That message means you did not unlock your bootloader.
Click to expand...
Click to collapse
I did unlock my bootloader. But now that I can't tether it might be a while to download the 1.2GB file. Thanks man!

If you used ez unlock, there is a chance u had the version that wasnt unlocking properly. That message def comes from flashing custom kernel and a secure aboot in my experience. I think the version everyone said for sure works was 1.2.

apacseven said:
If you used ez unlock, there is a chance u had the version that wasnt unlocking properly. That message def comes from flashing custom kernel and a secure aboot in my experience. I think the version everyone said for sure works was 1.2.
Click to expand...
Click to collapse
I had to use 1.1 cause 1.2 wouldn't open on my phone. :/

Yep, the dreaded triangle. I had use EZ Unlock v1.4 and it screwed me. Use v1.2 or v1.0 I had to Odin back to stock and start from there. All is running well now.
This was how I got it back to stock (rooted). I had to use that special tip in the grey box to work for mine.

I remember when I had this happen to me. I was a total noob at flashing when I got my S3. Tried to install some rom with custom kernel and kept getting this at reboot. Didn't know anything about unlocking bootloader
A month later and I'm a pro... Well maybe not a pro, but no more triangle of death!
At the time, though, I nearly **** my pants lol.
Sent from my SCH-I535 using xda app-developers app

That happened to me, I thought sh#%, I gotta go to Verizon and act stupid. I Messed with it for a few minutes and figured it out. Then odined it back. You learn fast thanks to the geniuses in these forums.
Sent from my SCH-I535 using xda app-developers app

Sorry for posting on an old thread but I though a link to Ez Unlocker V1.2 would be nice for anyone else having this problem. http://forum.xda-developers.com/showthread.php?p=31819403

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Had this happen to me last weekend. I thought my boot loader was unlocked but it turned out the superuser app I flashed (which I thought was an updated one) didn't have the thing to unlock the boot loader. Basically I just rooted and assumed I had it unlocked... Then flashed MOAR and after aroma froze 5 times and finally got the whole way through i met mr triangle. Haha
Sent from my SCH-I535 using xda app-developers app

Download the official software update from somewhere online and flash it in Odin. Just make sure you download it for Verizon
Sent from my SCH-I535 using xda app-developers app

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

No longer works after Verizon 4.3 OTA
ThePatelBros said:
Download the official software update from somewhere online and flash it in Odin. Just make sure you download it for Verizon
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This process no longer appears to work after Verizon OTA'd the official 4.3 update. I tried to flash back to stock following the steps here:
http://forum.xda-developers.com/showthread.php?t=1840030
However I'm unable to flash the VRALEC bootchain successfully. I'm wondering if Verizon had a little extra magic in that update.

johncase142 said:
This process no longer appears to work after Verizon OTA'd the official 4.3 update. I tried to flash back to stock following the steps here:
http://forum.xda-developers.com/showthread.php?t=1840030
However I'm unable to flash the VRALEC bootchain successfully. I'm wondering if Verizon had a little extra magic in that update.
Click to expand...
Click to collapse
Don't flash anything in Odin. Once on TW 4.3, you're permanently on TW 4.3 because of Knox bootloader. You have the potential to brick your device if you flash anything in Odin.

SlimSnoopOS said:
Don't flash anything in Odin. Once on TW 4.3, you're permanently on TW 4.3 because of Knox bootloader. You have the potential to brick your device if you flash anything in Odin.
Click to expand...
Click to collapse
I have already tried the original 4.0.4 ROM and am getting the yellow unauthorized triangle. Any idea how to make this thing boot again?

johncase142 said:
I have already tried the original 4.0.4 ROM and am getting the yellow unauthorized triangle. Any idea how to make this thing boot again?
Click to expand...
Click to collapse
After which step did you see this yellow triangle? Could you be very specific? Did the ICS tar flash successfully? Cuz from what I understand with 4.3 on other carrier's S3, once you're on TW 4.3 you can't downgrade. I want to tell you to flash VRBMF1 jellybean stock firmware since you've already flashed ICS firmware with no hard brick.

SlimSnoopOS said:
After which step did you see this yellow triangle? Could you be very specific? Did the ICS tar flash successfully? Cuz from what I understand with 4.3 on other carrier's S3, once you're on TW 4.3 you can't downgrade. I want to tell you to flash VRBMF1 jellybean stock firmware since you've already flashed ICS firmware with no hard brick.
Click to expand...
Click to collapse
I tried flashing the VRALEC bootchain first, and it took, but then threw the yellow triangle. After that I tried loading VRALF2 stock firmware and it did not give any errors. I tried again with VRALEC bootchain with no success. Then tried VRALF2 bootchain and VRBMD3 bootchain. I can boot into stock recovery and Odin, but that's all.

johncase142 said:
I have already tried the original 4.0.4 ROM and am getting the yellow unauthorized triangle. Any idea how to make this thing boot again?
Click to expand...
Click to collapse
We don't know. That means bootloader is locked. It would have to be Odin again. If got that with stock tar could be brick. If try to unlock may get hard brick. You kinda past the point of no return. Can try to Odin another newer one like MF1 and see what happens. It is saying the kernel is not compatible. Can't clear that message anyway without another stock Odin. Can't unlock with that message anyway. It's too late.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2

prdog1 said:
We don't know. That means bootloader is locked. It would have to be Odin again. If got that with stock tar could be brick. If try to unlock may get hard brick. You kinda past the point of no return. Can try to Odin another newer one like MF1 and see what happens. It is saying the kernel is not compatible. Can't clear that message anyway without another stock Odin. Can't unlock with that message anyway. It's too late.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Ok, I'm already downloading MF1 on my really slow Internet connection. It may be done by sunrise.

[Q] What is a BootChain

I've spent an hour searching for something to explain what bootchains are. I want to understand how they allow the S3 to be rooted and why you need to put them back when you're done. But I'd settle just for a simple what are they.

TommyTFC said:
I've spent an hour searching for something to explain what bootchains are. I want to understand how they allow the S3 to be rooted and why you need to put them back when you're done. But I'd settle just for a simple what are they.
Click to expand...
Click to collapse
A bootchain is the process your phone takes in order to boot. Flashing a specific bootchain is the bootchain available at the time when it was released.
It specifically tells the phone to boot through a series of steps in order to make sure the phone is running correct files. If any part of the chain is broken, the phone won't be able to boot up.
An example which we bypass on our specific phone is the aboot step in the bootchain. To unlock the phone, we simply flash a modified aboot file that makes the phone think it's running the correct rom and kernel. Aboot is only one part of the bootchain.
Hope that makes sense.
Sent from my SCH-I535 using Tapatalk 2

So the files in the tar are programs and they each execute in turn?
The rooting instructions say it doesn't matter if you put the original back. Know why?
Sent from my SCH-I535 using xda app-developers app

TommyTFC said:
So the files in the tar are programs and they each execute in turn?
The rooting instructions say it doesn't matter if you put the original back. Know why?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Basically you got it. That's exactly what's in the tar file.
I'm not really sure how exactly the new rooting process works the way it does, but I know it has something to do with breaking the chain and allowing it to inject a superuser app and recovery. The original bootchain blocks this process and doesn't allow superuser permission. ICS allowed this, which is why it was easier to root it. JB blocks this method, which is why a modified bootchain is needed.
I'm only assuming, but restoring to the original bootchain is simply recommended because it's what should be on the phone. If there's something wrong with the modified bootchain then it may break your booting checkpoints. You're probably safe not restoring it, but you can be sure you're safe if you do restore it.
Sent from my SCH-I535 using Tapatalk 2

Yea you should restore the original bootchains. You want to be original.

Did a search, and this was the best thread I could find.
I'm looking to root, and know that I need to download the correct bootchain.
Question: How do I determine which one that is?
I'm running the (new, awful) version of 4.1.2 that just updated my Verizon Galaxy S3. Currently, I'm stock... but not for long.
Thanks for the assistance.

ccstra54 said:
Did a search, and this was the best thread I could find.
I'm looking to root, and know that I need to download the correct bootchain.
Question: How do I determine which one that is?
I'm running the (new, awful) version of 4.1.2 that just updated my Verizon Galaxy S3. Currently, I'm stock... but not for long.
Thanks for the assistance.
Click to expand...
Click to collapse
You can get everything you need from the S3 link in my signature. Instructions are there also.

If anyone is more curious about this, you should google "2nd-init" or "milestone bootchain" theres a couple good blogs/posts discussing how they got past the locked boot loader on the Motorola Droid/ milestone.

[Q] Quasi-Noob with Questions

Hi, all. I rooted my continuum a couple of years ago via Odin, so I've done it once and I'm not afraid of it. But now I have a GS3 with the new MF1 update. I want to root so I can get rid of the VZW junk and find the best tethering option. I paid $400 for my phone instead of upgrading with Verizon so I can keep my unlimited data, so I'm not about to wantonly brick it, which is why I'm asking dumb questions!
1) Can I root without unlocking the bootloader? The reason why I'm asking is that I don't want to flash any custom roms at this time, just clean out the bloatware and have SU. Or am I mistaken...I thought the only reason to unlock it was to install a custom recovery, but that the recovery is only needed to flash a custom rom, not to root it.
1a) If I can root without unlocking the bootloader, which is the best way?
I went through [GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2 OTA ***UPDATED 5/29*** here --> http://forum.xda-developers.com/showthread.php?t=2046439
But it seems that the VRBMF1 bootchain is not available yet. Someone mentioned flashing mb1 with Odin, and then using the mb1 bootchain to root, but that seems counterintuitive if I don't plan on then flashing a custom rom.
1b) What would happen if I flashed a different bootchain than the version I currently have and tried rooting?
2) If my phone is soft-bricked, as has happened to a couple of people using the Casual method, is it possible/hard to unbrick it?
3) I have baseband VRBMF1, but I noticed that with the Casual method, whoever did it in the video had VRBMA2. Now, I understand that the baseband version is independent of the firmware, but can the baseband version interfere with the rooting process, for instance using the Casual method?
Also, the main reason why I haven't done Casual is that it bricked a few phones. I'm not opposed to having a custom recovery, as would be installed with Casual, but given the few failures, I'm not eager to try it.
4) I've been using PDANet+ to tether, but I'm not convinced that using PDANet with wifi is good, as it seems to use the phone's hotspot (unlike using the USB function in the app). What is the best way to hide tethering from Verizon? And are there better options available to root users?
Thanks for any advice!

You have the guide you need. Just follow the directions. You can root without unlocking boot loader. If you unlock the boot loader then you can flash a custom Rom that has built in tether feature if you don't want to use pda. I would just bite the bullet and do casual. It really is fool proof.
Sent from my SCH-I535 using Tapatalk 2

bbqsfire said:
You have the guide you need. Just follow the directions. You can root without unlocking boot loader. If you unlock the boot loader then you can flash a custom Rom that has built in tether feature if you don't want to use pda. I would just bite the bullet and do casual. It really is fool proof.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply. I agree with you about having the guide I need for the Odin method, but I still don't have the correct bootchain. Will another work? And the casual root does seem foolproof, except for the few bricks. No one has identified what caused those, whether some java issue, or something else.
So if I used the Odin method, does it matter which bootchain for 4.1.2 I use, either MB1 or MD3, considering i'm on MF1?

hturbulence said:
Thanks for the reply. I agree with you about having the guide I need for the Odin method, but I still don't have the correct bootchain. Will another work? And the casual root does seem foolproof, except for the few bricks. No one has identified what caused those, whether some java issue, or something else.
So if I used the Odin method, does it matter which bootchain for 4.1.2 I use, either MB1 or MD3, considering i'm on MF1?
Click to expand...
Click to collapse
It will not matter because you can flash the radio later. You will be flashing an older bootchAin but once you flash a Rom and the radio you are fine.
Sent from my GT-P5113 using xda premium

If the bootchain doesn't matter, why are there different versions? I'm not so concerned about the radio because that doesn't change with rooting, does it? I guess my question would be, if I'm on the VRBMF1 build, and say I used the VRBMD3 bootchain, would everything go as planned? I mean, doesn't the bootchain just tell the phone in which order to use files for boot?
I really appreciate your help!:good:

I came from the continuum too, have to say I miss the ticker, but not the lack of RAM!
I used this method to root my S3:
http://forum.xda-developers.com/showthread.php?t=1984436
Used the first link (mb1 no wipe). It is Stock, locked bootloader, stock recovery, rooted. Then I used OTA Rootkeeper (from play store) to back up root. Then I took the OTA to MF1. This will get you to the latest stock firmware with root. You can unlock the bootloader and install a custom recovery later if you want, which is what I did. . No issues for me so far.
Sent from my SCH-I535 using xda app-developers app

Thanks for the info. I actually rooted with casual about an hour ago. I was nervous about the casual method because of the few bricks with MF1, but I gave it a shot, and it worked.
Now, just have to figure out best way to tether without VZW knowing!
Sent from my SCH-I535 using xda app-developers app

Having trouble getting Heimdall to work on OSX

So I've been using an HTC MyTouch 4G for the past few years and had the rooting/flashing process down with that phone, but I recently switched to the Verizon variant of the Samasung Galasy S III and have run into an issue trying to root and flash an aftermarket rom to this device.
As per the CM Wiki for my device, I need to install and use Heimdall to downgrade the bootloader. I'm not new to using the terminal, so I figured this wouldn't be a difficult step, however I can't get Heimdall to work even after many attempts to download just the binary from the CM wiki, download the entire package including the frontend directly from the website Heimdall is hosted on, and even after compiling directly from source.
After trying to install it many different times/ways, I'm running into the same error every single time. After opening the terminal and trying to execute any command pertaining to Heimdall (Heimdall help, Heimdall detect, etc.) I get a response of "Illegal Instruction." I cannot get it to do ANYTHING other than to respond with "Illegal Instruction."
It's driving me mad because all I need Heimdall for at this point is to downgrade the bootloader.
I know I must be making some very minute error, but I can't figure it out.
Just a bit more information: I'm running OSX 10.6 so the current Heimdall Frontend is not compatable, so I have to use the Terminal (which I'd rather do anyways because I have more control that way.)
Any help or isight would be appreciated.
Thanks!

Just use the casual script instead of trying to downgrade
Sent from my SCH-I535 using Tapatalk 4 Beta
If I've helped, please hit the thanks button

tylerlawhon said:
Just use the casual script instead of trying to downgrade
Sent from my SCH-I535 using Tapatalk 4 Beta
If I've helped, please hit the thanks button
Click to expand...
Click to collapse
Casual script? Mind elaborating or guiding me in the right direction?

checkthisSH said:
Casual script? Mind elaborating or guiding me in the right direction?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2332825
You shouldn't need to do anything with the bootloader, use this to load a custom recovery, then flash the cm10 image for the Verizon sgs3.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
http://forum.xda-developers.com/showthread.php?t=2332825
You shouldn't need to do anything with the bootloader, use this to load a custom recovery, then flash the cm10 image for the Verizon sgs3.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for getting back to me so quickly.
According to the CM Wiki and a couple of other sources I can't think of at the moment, if I'm coming from stock/no root, I would need to load an older bootloader before flashing recovery and ultimately flashing CM10.
The Samsung root process is a bit different from some of the other phones I have worked with. Would you mind explaining to me why I wouldn't need to load an older bootloader?
Edit: After taking a look into the thread you provided for me I may have answered my own question. Loading the older bootloader is probably essential to getting the exploit to work with Heimdall, right? But not with the Casual exploit?

checkthisSH said:
Thanks for getting back to me so quickly.
According to the CM Wiki and a couple of other sources I can't think of at the moment, if I'm coming from stock/no root, I would need to load an older bootloader before flashing recovery and ultimately flashing CM10.
This process is a bit different from some of the other phones I have worked with. Would you mind explaining to me why I wouldn't need to load an older bootloader?
Click to expand...
Click to collapse
I've never seen those instructions before, but i would try posting this In the cm10 question and answer thread.
That could also be old instructions, find the cm10 development thread and see what the latest instructions are for installation.
I've never used heimdall and couldn't give you instructions how to use it, using odin to flash those would be significantly easier if you can get access to a window computer.
Either way, that process won't achieve root anyway. You're better off running casual first to get a custom recovery and root access, then run that process later if needed.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
I've never seen those instructions before, but i would try posting this In the cm10 question and answer thread.
That could also be old instructions, find the cm10 development thread and see what the latest instructions are for installation.
I've never used heimdall and couldn't give you instructions how to use it, using odin to flash those would be significantly easier if you can get access to a window computer.
Either way, that process won't achieve root anyway. You're better off running casual first to get a custom recovery and root access, then run that process later if needed.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
In theory, and please correct me if I'm wrong, but it looks like I should be able to use Casual up until I need to flash CM10. Which is as simple as throwing the .zip file onto my SD card and installing from recovery. That way I probably won't even have to touch Heimdall.
The only thing that concerns me is that following the CM wiki instructions has you flash an older kernel as well. Again, this appears to me like it could only be required to load the customer recovery using Heimdall, but I'm not entirely sure.
I'll have to look around for the CM10 dev thread around here because the one on the CM forum is a ghost town.
Thanks again for all of your help!

checkthisSH said:
In theory, and please correct me if I'm wrong, but it looks like I should be able to use Casual up until I need to flash CM10. Which is as simple as throwing the .zip file onto my SD card and installing from recovery. That way I probably won't even have to touch Heimdall.
The only thing that concerns me is that following the CM wiki instructions has you flash an older kernel as well. Again, this appears to me like it could only be required to load the customer recovery using Heimdall, but I'm not entirely sure.
I'll have to look around for the CM10 dev thread around here because the one on the CM forum is a ghost town.
Thanks again for all of your help!
Click to expand...
Click to collapse
That's exactly what I'm saying. However, the whole thing is confusing to me also. It seems weird that you'd need an older bootloader in order to run the rom.
Just make a backup before you flash in recovery, then if it won't run at least you have a way to get a working phone.
The kernel should have nothing to do with anything, as soon as you flash cm10 it'll get overwritten with the cm10 stock kernel.
Also make sure that the bootloader is unlocked before you flash, or you'd have to odin back to stock.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
That's exactly what I'm saying. However, the whole thing is confusing to me also. It seems weird that you'd need an older bootloader in order to run the rom.
Just make a backup before you flash in recovery, then if it won't run at least you have a way to get a working phone.
The kernel should have nothing to do with anything, as soon as you flash cm10 it'll get overwritten with the cm10 stock kernel.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'm assuming it has something to do with using Heimdall, and if that's the case, I don't know why anyone would ever want to use that method when it is clearly more difficult. Maybe someone else can weigh in on the topic.
Thanks again for the solid advice. I'll take the Casual route and see where it takes me.

BadUsername said:
That's exactly what I'm saying. However, the whole thing is confusing to me also. It seems weird that you'd need an older bootloader in order to run the rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
FYI, every rooted and unlocked Verizon GSIII is using a pre-release unlocked bootloader so you're using an older bootloader already.
Sent from my SCH-I535 using Tapatalk 4 Beta

SlimSnoopOS said:
FYI, every rooted and unlocked Verizon GSIII is using a pre-release unlocked bootloader so you're using an older bootloader already.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
You mean once you unlock the phone with an old aboot file right? The newer phones would have a newer bootloader until you change it.
The instructions are really confusing because they're instructing to downgrade the bootloader to inject an aboot file and custom recovery. I still think that entire step is unnecessary.
Sent from my SCH-I535 using Tapatalk 2