Database Info

"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.

i535 Rooting/ROM'ing level of difficulty/risk

So I had a Galaxy S1 Captivate for about 2 year and my wife has a Fascinate and I rooted/flashed them both like it was my job for the last couple years. I never once hard bricked either and for the most part knew what I was doing. I have a couple home made jigs so DL mode or (soft bricks) were never an issue. My question to you guys is I'm trying to gauge how difficult/risky is it to root and rom the GS3 (Verizon model specifically). The reason I'm wondering this info is because I personally don't own my GS3, it is property of my company and I don't want to chance bricking or not being able to easily flash back to stock unless it has gotten easier or less risky since the original Galaxy lineup. I mean if you had 2.3 bootloaders on your GS1 and you had access to a jig, there was pretty much a 0% chance of hard bricking unless you do something really stupid. Sorry for rambling on!

jayjr1105 said:
So I had a Galaxy S1 Captivate for about 2 year and my wife has a Fascinate and I rooted/flashed them both like it was my job for the last couple years. I never once hard bricked either and for the most part knew what I was doing. I have a couple home made jigs so DL mode or (soft bricks) were never an issue. My question to you guys is I'm trying to gauge how difficult/risky is it to root and rom the GS3 (Verizon model specifically). The reason I'm wondering this info is because I personally don't own my GS3, it is property of my company and I don't want to chance bricking or not being able to easily flash back to stock unless it has gotten easier or less risky since the original Galaxy lineup. I mean if you had 2.3 bootloaders on your GS1 and you had access to a jig, there was pretty much a 0% chance of hard bricking unless you do something really stupid. Sorry for rambling on!
Click to expand...
Click to collapse
I came from the Fascinate and this phone is just as easy to flash. Just make sure you read the OP and only flash things made for the US versions and you'll be fine. If something gets hosed, you can always odin back. Here is a great guide to get you started.
http://forum.xda-developers.com/showthread.php?t=1762709
Sent from my SCH-I535 using xda app-developers app

Deliquified said:
I came from the Fascinate and this phone is just as easy to flash. Just make sure you read the OP and only flash things made for the US versions and you'll be fine. If something gets hosed, you can always odin back. Here is a great guide to get you started.
http://forum.xda-developers.com/showthread.php?t=1762709
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I haven't checked that link out yet but how easy is it to go back to the Verizon stock ROM if need be?
Does the ROM procedure go something like this?...
Power Off, DL mode with jig, ODIN a CWM or Kernel package with CWM, mount SD, drag and drop ROM, Flash, win?

well...
well the good news is that you don't have to flash a custom rom for root. I just rooted and unlocked my phone while still running the stock rom. =) i'd post my tutorial but I'm a new member and I have 8 more posts to do before I can post in development.

eorly420 said:
well the good news is that you don't have to flash a custom rom for root. I just rooted and unlocked my phone while still running the stock rom. =) i'd post my tutorial but I'm a new member and I have 8 more posts to do before I can post in development.
Click to expand...
Click to collapse
There is already an in depth tutorial for that as well as one for those who have the recent OTA.
http://forum.xda-developers.com/showthread.php?t=2046439
The above link is those with the jelly bean OTA.
http://forum.xda-developers.com/showthread.php?t=1762709
This above is the in depth guide I was talking about. It was posted on 7/10/12. So there is no need for another tutorial unless you found a new way to do it. If you are talking about RootDebugFS then there is a tutorial for that here as well as the SuperSU version here as well.

I also came from a fascinate which was super easy to flash. As long as you read up on your homework this phone is cake to flash.

You shouldn't have many problems. If you need help, PM me. I'm glad to help.

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

So I'm wondering one last thing. I hear about a "flash counter" on the GS3... anything I need to be really careful about to not trip this "counter"? Will Verizon void the warranty if tripped?
Thanks again guys!
Also, I'm going to be using this phone a lot for work and I ported my old personal number to Google Voice so this will be my personal phone as well, so I need the phone to be pretty solid and stable, should I be looking to flash Original ROMs or from the regular development section?

jayjr1105 said:
So I'm wondering one last thing. I hear about a "flash counter" on the GS3... anything I need to be really careful about to not trip this "counter"? Will Verizon void the warranty if tripped?
Thanks again guys!
Also, I'm going to be using this phone a lot for work and I ported my old personal number to Google Voice so this will be my personal phone as well, so I need the phone to be pretty solid and stable, should I be looking to flash Original ROMs or from the regular development section?
Click to expand...
Click to collapse
Once your rooted, you can download Triangle Away from the App Store and that will restore the counter to 0.

lvgdgts said:
Once your rooted, you can download Triangle Away from the App Store and that will restore the counter to 0.
Click to expand...
Click to collapse
Thanks! Do you need to run the app every time you flash or just right before you would need to take it in to Verizon for warranty/service?

jayjr1105 said:
Thanks! Do you need to run the app every time you flash or just right before you would need to take it in to Verizon for warranty/service?
Click to expand...
Click to collapse
If you unlock bootloader before you flash recovery you will not trip flash counter. If counter is tripped must use Triangle Away while still on stock rom. That being said flash counter does not affect anything except warranty and requires you to Odin stock root, run triangle Away then Odin full stock so best to fix as soon as you root and unlock to avoid extra work at time of return to Verizon.

prdog1 said:
If you unlock bootloader before you flash recovery you will not trip flash counter. If counter is tripped must use Triangle Away while still on stock rom. That being said flash counter does not affect anything except warranty and requires you to Odin stock root, run triangle Away then Odin full stock so best to fix as soon as you root and unlock to avoid extra work at time of return to Verizon.
Click to expand...
Click to collapse
Is there a way to just see if you tripped the flash counter without Triangle Away?

[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] Stock NE1 keeping unlocked bootloader possible?

I have spent the last week researching how to proceed with updating my Verizon Galaxy S3, but haven't found a clear concise answer pertaining to my current scenario. I thought a thread with a definitive answer would help others in my same boat save alot of time.
The last time I updated my phone was with a stock rooted MB1 rom with CWM 6023 recovery and 3.0.31-861013 kernel (2/14/13) and unlocked bootloader. Knowing that nothing good has ever come from taking OTA updates, I then removed the OTA Certs. I've kept my fingers crossed with the releases of ML1, MF1, and ND3 hoping that they would be better than MB1 but public opinion of the downsides has kept me from updating to any of these previous versions.
Now I'm DYING to update to Kit Kat and a better modem/radio than what I currently have. I've had really really poor experiences with a variety of handsets over the last 4 years using custom roms like AOSP, Cyanogen, etc. Therefore, I typically like to run a stock rooted version of whatever the current rom at the time is and remove some of the bloat myself or often there will be bloatware free stock roms for various handsets floating around so those are what I gravitate toward. More often than not custom roms have too many bugs (ie, camera not working or mms failures, etc) for production use.
So that being said, what would be the best course of action for someone such as myself to get on NE1 (or a really, really, really solid KitKat with NO bugs) and keep an unlocked bootloader for future flexibility. And, more importantly be able to update the modem/radio without locking the bootloader (as I've read some have found their bootloader locked after modem update)?
Any advice would be greatly appreciated.

Muleguy said:
I have spent the last week researching how to proceed with updating my Verizon Galaxy S3, but haven't found a clear concise answer pertaining to my current scenario. I thought a thread with a definitive answer would help others in my same boat save alot of time.
The last time I updated my phone was with a stock rooted MB1 rom with CWM 6023 recovery and 3.0.31-861013 kernel (2/14/13) and unlocked bootloader. Knowing that nothing good has ever come from taking OTA updates, I then removed the OTA Certs. I've kept my fingers crossed with the releases of ML1, MF1, and ND3 hoping that they would be better than MB1 but public opinion of the downsides has kept me from updating to any of these previous versions.
Now I'm DYING to update to Kit Kat and a better modem/radio than what I currently have. I've had really really poor experiences with a variety of handsets over the last 4 years using custom roms like AOSP, Cyanogen, etc. Therefore, I typically like to run a stock rooted version of whatever the current rom at the time is and remove some of the bloat myself or often there will be bloatware free stock roms for various handsets floating around so those are what I gravitate toward. More often than not custom roms have too many bugs (ie, camera not working or mms failures, etc) for production use.
So that being said, what would be the best course of action for someone such as myself to get on NE1 (or a really, really, really solid KitKat with NO bugs) and keep an unlocked bootloader for future flexibility. And, more importantly be able to update the modem/radio without locking the bootloader (as I've read some have found their bootloader locked after modem update)?
Any advice would be greatly appreciated.
Click to expand...
Click to collapse
Unfortunately, the ML1 update locked the bootloader and that hasn't changed with NC1 or NE1 (as far as we know). MF1 is the latest update I know of that still has the option for an unlocked bootloader. I've never used custom ROMs (but would very much like to) but I am currently on NE1 so I can't. Granted, I will say that Kitkat is a good update and things are running well. HOWEVER, from someone who would LOVE to have that option for an unlocked bootloader, I would personally discourage updates that would lock your bootloader. But the choice is yours.
Quick question (to someone with a little more expertise), If you were still on an update BEFORE MF1, and you had the option to download it OTA, could you extract the update.zip from /cache/fota like we did for the Kitkat update and distribute it so people could then flash it with Odin (and get unlocked bootloaders)? Or am I missing some flaw with that plan?

Muleguy said:
I have spent the last week researching how to proceed with updating my Verizon Galaxy S3, but haven't found a clear concise answer pertaining to my current scenario. I thought a thread with a definitive answer would help others in my same boat save alot of time.
The last time I updated my phone was with a stock rooted MB1 rom with CWM 6023 recovery and 3.0.31-861013 kernel (2/14/13) and unlocked bootloader. Knowing that nothing good has ever come from taking OTA updates, I then removed the OTA Certs. I've kept my fingers crossed with the releases of ML1, MF1, and ND3 hoping that they would be better than MB1 but public opinion of the downsides has kept me from updating to any of these previous versions.
Now I'm DYING to update to Kit Kat and a better modem/radio than what I currently have. I've had really really poor experiences with a variety of handsets over the last 4 years using custom roms like AOSP, Cyanogen, etc. Therefore, I typically like to run a stock rooted version of whatever the current rom at the time is and remove some of the bloat myself or often there will be bloatware free stock roms for various handsets floating around so those are what I gravitate toward. More often than not custom roms have too many bugs (ie, camera not working or mms failures, etc) for production use.
So that being said, what would be the best course of action for someone such as myself to get on NE1 (or a really, really, really solid KitKat with NO bugs) and keep an unlocked bootloader for future flexibility. And, more importantly be able to update the modem/radio without locking the bootloader (as I've read some have found their bootloader locked after modem update)?
Any advice would be greatly appreciated.
Click to expand...
Click to collapse
You are basically going to have to wait until a dev puts out a stock, rooted, knoxless ROM based on NE1. I've never heard of a modem flash locking a bootloader. Modern has nothing to do with the bootloader. Anyone who said this happened to them most likely flashed the firmware or full factory tar instead of the modem file by accident.
Sent from the Shark Tank using XDA Premium 4 mobile app
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
JacobManning17 said:
Unfortunately, the ML1 update locked the bootloader and that hasn't changed with NC1 or NE1 (as far as we know). MF1 is the latest update I know of that still has the option for an unlocked bootloader. I've never used custom ROMs (but would very much like to) but I am currently on NE1 so I can't. Granted, I will say that Kitkat is a good update and things are running well. HOWEVER, from someone who would LOVE to have that option for an unlocked bootloader, I would personally discourage updates that would lock your bootloader. But the choice is yours.
Quick question (to someone with a little more expertise), If you were still on an update BEFORE MF1, and you had the option to download it OTA, could you extract the update.zip from /cache/fota like we did for the Kitkat update and distribute it so people could then flash it with Odin (and get unlocked bootloaders)? Or am I missing some flaw with that plan?
Click to expand...
Click to collapse
Flashing that update.zip file through ODIN before a dev had a chance to remove Knox and the locked down bootloader would be the same exact thing as accepting the OTA. You would then be locked down.
Sent from the Shark Tank using XDA Premium 4 mobile app

landshark68 said:
You are basically going to have to wait until a dev puts out a stock, rooted, knoxless ROM based on NE1. I've never heard of a modem flash locking a bootloader. Modern has nothing to do with the bootloader. Anyone who said this happened to them most likely flashed the firmware or full factory tar instead of the modem file by accident.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I ran across a thread on here just this morning where someone was trying to update just the modem and ended up with a locked bootloader. The replies suggested that Samsung may have slipped something in with the modem file this go around. That's why I included it in this question. I will have to try to find the link to the other thread when I have more time later.

Muleguy said:
I ran across a thread on here just this morning where someone was trying to update just the modem and ended up with a locked bootloader. The replies suggested that Samsung may have slipped something in with the modem file this go around. That's why I included it in this question. I will have to try to find the link to the other thread when I have more time later.
Click to expand...
Click to collapse
You might be referring to this post in the general section. I am still unsure how they managed to do this if they downloaded the 20 MB VRUCML1 modem from our S3 forum. There is only one person whom I know to have extracted it and that is Invisiblek. Not a single other person before this user has mentioned having their bootloader locked from installing the VRUCML1 modem in CWM or TWRP. I really did not understand what they were trying to say so I just kept the convo moving in a different direction.

landshark68 said:
Flashing that update.zip file through ODIN before a dev had a chance to remove Knox and the locked down bootloader would be the same exact thing as accepting the OTA. You would then be locked down.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm on ML1 unlocked bootloader/rooted from here
http://forum.xda-developers.com/showthread.php?t=2591895
If I flash NE1 via ODIN will it wipe my phone resulting in a clean NE1 with locked bootloader or will it be a non-destructive upgrade to fully stock/locked NE1?

lexluthor said:
I'm on ML1 unlocked bootloader/rooted from here
http://forum.xda-developers.com/showthread.php?t=2591895
If I flash NE1 via ODIN will it wipe my phone resulting in a clean NE1 with locked bootloader or will it be a non-destructive upgrade to fully stock/locked NE1?
Click to expand...
Click to collapse
Not sure whether the tar file you can download from sammobile will wipe your phone, but the tar file provided by open1your1eyes0 in the below linked thread will not wipe your phone. Either way, you will be on locked down NE1. Read the disclaimer at the top of the OP in open1your1eyes0's thread:
http://forum.xda-developers.com/showthread.php?t=2795659

landshark68 said:
Not sure whether the tar file you can download from sammobile will wipe your phone, but the tar file provided by openyoureyes1 in the below linked thread will not wipe your phone. Either way, you will be on locked down NE1. Read the disclaimer at the top of the OP in openyoureyes1's thread:
http://forum.xda-developers.com/showthread.php?t=2795659
Click to expand...
Click to collapse
I don't care if I'm locked going forward. So if I flash that, after I'll still have all my apps and appdata and be on NE1, locked? And then I can root with towelroot?

lexluthor said:
I don't care if I'm locked going forward. So if I flash that, after I'll still have all my apps and appdata and be on NE1, locked? And then I can root with towelroot?
Click to expand...
Click to collapse
I believe that is correct. I thought I saw a few people in the 4.4.2 update thread post that towelroot worked on NE1. May want to read the last few pages of that thread just to make sure about towelroot.

lexluthor said:
I don't care if I'm locked going forward. So if I flash that, after I'll still have all my apps and appdata and be on NE1, locked? And then I can root with towelroot?
Click to expand...
Click to collapse
That is correct. Towelroot works just fine with NE1
Sent from my SCH-I535 using XDA Premium 4 mobile app

landshark68 said:
I believe that is correct. I thought I saw a few people in the 4.4.2 update thread post that towelroot worked on NE1. May want to read the last few pages of that thread just to make sure about towelroot.
Click to expand...
Click to collapse
So far, looking ok. I flashed via ODIN and now it's at Android is upgrading and it's optimizing 502 apps, so looks like the apps are still there.
Hopefully towelroot works fine and then I can tweak my system settings back, install xposed and I'm good to go.
---------- Post added at 09:17 PM ---------- Previous post was at 08:25 PM ----------
lexluthor said:
So far, looking ok. I flashed via ODIN and now it's at Android is upgrading and it's optimizing 502 apps, so looks like the apps are still there.
Hopefully towelroot works fine and then I can tweak my system settings back, install xposed and I'm good to go.
Click to expand...
Click to collapse
All went great. It took a good half hour after the upgrade for the CPU to stop being pegged at 100% and have the phone be responsive again.
Very easy, it kept all of my applications and settings and I didn't really need to do much other than towelroot and re-install xposed.
I'm due for an upgrade soon anyhow, so I didn't really want to go through a lot of work getting to Kitkat.

Towel root not working any longer. Keep getting unsupported device with NE1 .. Ugh ..

[Q] Quick Question about how the locked bootloader effects roms

I've been working on some stuff on my own but I am stimm pretty vanilla about android development in general (although that doesnt mean I havent developed anything else). Anyhow, I just wanted to ask exactly what effect the bootloader has on installing roms and such. I realize that this prevents anything besides touchwiz roms but I would like to know the in depth. It is my understanding that a stock kernel is required but what else?

carlofabyss said:
I've been working on some stuff on my own but I am stimm pretty vanilla about android development in general (although that doesnt mean I havent developed anything else). Anyhow, I just wanted to ask exactly what effect the bootloader has on installing roms and such. I realize that this prevents anything besides touchwiz roms but I would like to know the in depth. It is my understanding that a stock kernel is required but what else?
Click to expand...
Click to collapse
Well, I guess it would have to do with safestrap too. With safestrap, I might be wrong, but it doesn't give you the same access as a fully unlocked bootloader. I'm on an unlocked bootloader, but I'm stuck with ML1 firmware. Someone else will have to give more info on safestrap because I don't know much about it.

I guess I would check this out.
http://forum.xda-developers.com/sho....2] - I535VRUDNE1-Dump / Dev Discussion ONLY!
I would also pm the devs there if you really want to take this project over.
Good luck!

sjpritch25 said:
Well, I guess it would have to do with safestrap too. With safestrap, I might be wrong, but it doesn't give you the same access as a fully unlocked bootloader. I'm on an unlocked bootloader, but I'm stuck with ML1 firmware. Someone else will have to give more info on safestrap because I don't know much about it.
Click to expand...
Click to collapse
Apologies, I didnt acknowledge that in my post, but I am well aware that yeah safestrap does not at all give you the same freedom. So wait how are you on the unlocked bootloader and stuck? That's interesting. Safestrap is essentially not an actually replacement to your stock recovery it just allows you to flash modified stock based roms to a rom slot if you are on a locked bootloader. But if you are unlocked then in theory you should be able to flash cwm and start fresh. Also being on ML1 however, shouldnt you be locked to begin with?

razz1 said:
I guess I would check this out.
http://forum.xda-developers.com/sho....2] - I535VRUDNE1-Dump / Dev Discussion ONLY!
I would also pm the devs there if you really want to take this project over.
Good luck!
Click to expand...
Click to collapse
This is interesting, I thought everything had pretty much been abandoned for either too much of a challenge or new devices. Thanks

sjpritch25 said:
Well, I guess it would have to do with safestrap too. With safestrap, I might be wrong, but it doesn't give you the same access as a fully unlocked bootloader. I'm on an unlocked bootloader, but I'm stuck with ML1 firmware. Someone else will have to give more info on safestrap because I don't know much about it.
Click to expand...
Click to collapse
Same here. It's nice to be on an unlocked bootloader however. I'm on ML1 myself and never had any major issues. Safestrap basically allows you to use a different slot which doesn't touch the locked bootloader. On the 4.3 update which locked the bootloader there were several TW roms to chose from but when it comes to the newest baseband of NE1 your limited to stock and one other rom.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2