Related
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.
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
i updated my verizon Galaxy S3 (I535) today, and forgot to unroot it so expectedly i go the "unsuccessful" update, but it did update, i have the changes. but i cannot get into supersu so i cannot unroot my phone (never really used the rooting anyways)
is there anyway to unroot my phone atm? and/or to make sure i have the entire update?
(wasnt really expecting to get the update at all with a rooted phone)
also i cannot get into supersu cause my phone is still recongnized as 4.3 instead of 4.1.2
...not really sure what to do
Hmm, well you can root using SafeRoot according to multiple users in our general TW 4.3 thread.
Maybe you can unroot after you root using that but there's no way to downgrade or Odin flash a ML1 tar unless we see one published in the near future. If you unroot after rooting then you could probably try installing the TW 4.3 update.zip in recovery but there's no guarantees it'll work and if it messes up, you're SOL until further notice.
Edit: so its clear, you can ONLY root. Flashing roms is not possible or recommended as of this moment if on TW 4.3
SlimSnoopOS said:
Hmm, well you can root using SafeRoot according to multiple users in our general TW 4.3 thread.
Maybe you can unroot after you root using that but there's no way to downgrade or Odin flash a ML1 tar unless we see one published in the near future. If you unroot after rooting then you could probably try installing the TW 4.3 update.zip in recovery but there's no guarantees it'll work and if it messes up, you're SOL until further notice.
Edit: so its clear, you can ONLY root. Flashing roms is not possible or recommended as of this moment if on TW 4.3
Click to expand...
Click to collapse
ok thanks,
ill keep watch, i mean everything seems fine on my phone its just the "unsucessful update" is a bit foreboding given that i obviously have the update o.o
no way to downgrade either atm i take it?
if i could down grade i could unroot easily and then update
KabuTheFox said:
ok thanks,
ill keep watch, i mean everything seems fine on my phone its just the "unsucessful update" is a bit foreboding given that i obviously have the update o.o
no way to downgrade either atm i take it?
if i could down grade i could unroot easily and then update
Click to expand...
Click to collapse
Nah, you'll have a hardbricked phone with seemingly no way to fix it if you attempt to downgrade. If/when VRUCML1 stock tar file is posted then you could flash that in Odin. What you'll need is something specifically for TW 4.3 whether that's root, root/unlock, or Odin. Nothing older is compatible.
KabuTheFox said:
i updated my verizon Galaxy S3 (I535) today, and forgot to unroot it so expectedly i go the "unsuccessful" update, but it did update, i have the changes. but i cannot get into supersu so i cannot unroot my phone (never really used the rooting anyways)
is there anyway to unroot my phone atm? and/or to make sure i have the entire update?
Click to expand...
Click to collapse
I believe that by going to the OTA 4.3, you are no longer rooted. The update "unrooted" you.
Thanks Slim !!
:good::good:
SlimSnoopOS said:
Hmm, well you can root using SafeRoot according to multiple users in our general TW 4.3 thread.
Maybe you can unroot after you root using that but there's no way to downgrade or Odin flash a ML1 tar unless we see one published in the near future. If you unroot after rooting then you could probably try installing the TW 4.3 update.zip in recovery but there's no guarantees it'll work and if it messes up, you're SOL until further notice.
Edit: so its clear, you can ONLY root. Flashing roms is not possible or recommended as of this moment if on TW 4.3
Click to expand...
Click to collapse
SafeRoot was a success and I now have a rooted device. I just purchased this used and it did an automatic update when i turned it on. Pretty bummed about now being able to switch out the ROM, but at least I've got root now! saferoot is awesome!
aarontsuru said:
I believe that by going to the OTA 4.3, you are no longer rooted. The update "unrooted" you.
Click to expand...
Click to collapse
the update database doesnt recongize my phone tho, and thats why it couldnt complete the update.
but according to my phone im still on 4.3 technically
it has been some time, there might already be something out for all i know by now
4.4 and 4.3 Sticky Roll-Up Thead
Do not use EZ-Unlock! You will instantly hard brick your phone and you will have to go through a painstaking hardbrick repair or get a JTAG repair.
Thread Purpose
The official 4.3 touchwiz update brought significant changes to the Verizon Galaxy S3. Once you took the update, the phone is completely stuck on the 4.3 or 4.4 base and any attempt to change the rom (unless using safestrap) will brick the device. Previous rooting and unlocking methods will no longer work on the update and will cause bricks if used. However, there are great threads going around regarding the update but are fragmented all over the device sections. We need a place to have all the information available on the new update. The old sticky roll-up thread should be used for anyone who still has an unlocked bootloader, meaning you did not take the 4.3 or 4.4 OTA update or your phone did not come with it pre-installed.
If you have 4.4 NE1 baseband you are unable to go back to any version of the 4.3 updates. Running any kind of 4.3 rom in safestrap will not work, and installing a stock 4.3 rom will brick your phone. You are limited to using a modified safestrap located in this thread, with no current modified custom roms.
This thread should strictly be for reference only, meaning posts should only be made if you believe a specific thread should be linked in the OP. If you want to discuss any aspects of this update that you're confused about, please use the 4.3 discussion thread (first linked sticky) or post your question in the Q&A forum. Keeping post counts low will make it easier for new members to access the information they need, so please post appropriately.
How can I tell if I have the official 4.3 or 4.4 update if I bricked my device?
It's important to know what base you're on so you can fix a brick. In any circumstance except a hard brick, once you boot into download mode you will see one of three possibilities:
If you're on a 4.3 or 4.4, you're in the right place:
4.3
Product Name: SCH-I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit:0
Bootloader RP Swrev: 0
4.4
Product Name: SCH-I535
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
Bootloader RP Swrev: 0
If you're on the 4.1 baseband, you're in the wrong place and you should head here: Stickied Threads [9.2.13]
The information displayed in download mode will look like this:
4.1
Product Name: SCH-I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
Stuck Threads
https://towelroot.com
Only tool available that will root 4.4 NE1 and 4.3 NC1 basebands. Will also root 4.3 ML1.
Touchwiz 4.3 (VRUCML1 and NC1) update discussion thread
Great resource with plenty of helpful people roaming the thread constantly. Use this thread to discuss any aspect of the 4.3 update you want.
[ROOT] Saferoot: Root for VRUEMJ7, MK2, and Android 4.3
A tool that will root the 4.3 VRUCML1 base. Will not work on NC1 or NE1 basebands.
[RECOVERY LOCKED] Safestrap Recovery v3.71 [2014-01-10 Alpha]
Only custom recovery that will work on the 4.3 VRUCML1. Do not try to use any other custom recovery, you will brick your phone. Right now you can only install custom Touchwiz 4.3 roms, so follow the directions in the thread. Will not work on the VRUCNC1 baseband, lacks kernel modules for WIFI connectivity. Will not work at all on the NE1 baseband.
[RECOVERY LOCKED/NE1] Unofficial Safestrap Recovery v3.75 [2014-06-27 KK B01]
Only recovery that will work on the NE1 baseband.
[HOWTO]Comprehensive IMEI/EFS Backup
Old thread, but a good one. This should be done immediately after you root, steps A and B (if still possible).
[INDEX] TW 4.3 Download List (5-24-14)
Everything you can install on 4.3 basebands NC1 and ML1.
[INDEX] TW 4.4 Download List (7-10-14)
Everything you can install on 4.4 baseband NE1.
[GUIDE Win/Linux/Mac] Debrick 4.3 with Odin or Verizon Utility + PIT [SOFT BRICK]
Use this if you bricked your device, and you're still able to access download mode. You can also use this guide to return completely to stock if you need to. For NE1 you need to use an appropriate NE1 stock rom, not the 4.3 rom listed.
[GUIDE] Debrick your bricked SCH-I535! [BOOTLOADER/HARDBRICK]
Use this if you bricked your device and can't enter download mode. Computer will recognize device as QHSUSB-DLOAD, but other than that you have no other sign of life. You can also fix this problem with a JTAG repair if you can't get this method to work.
Useful Information
If you have 4.3 VRUCNC1 baseband, since wifi modules aren't available it is recommend to Odin flash the Stock 4.3 VRUCML1 rom then root and install safestrap. That way you will have working wifi after rom installations.
[FAQ] KNOX and you
Very useful information on KNOX that everyone should understand. However, we have a locked bootloader and the sprint device doesn't, so don't listen to what he's telling you about flashing AOSP roms. If you do it you'll brick the phone, just understand what he's saying about what knox is.
[FIRMWARE] (MODEM/RPM/TZ/SBL) Verizon SGS3 (SCH-I535)
Good information on the locked bootloader and why it can't be downgraded to a previous modem. Do not flash any files from this thread if you're on the 4.3 base.
I think that's all I can think of, hope this helps everyone who needs it!
I am unfortunately stuck on 4.3 stock that came with a warranty replacement phone. I somehow hard bricked it BUT the hard brick link above worked perfectly.
Thank you for this thread
Sent from my SCH-I535 using Tapatalk
Very good post. Thank you for your trouble and time. Wish more people would visit and read before they start rooting and flashing. Thanks again.
Sent from my SCH-I535 using xda app-developers app
Thanks for grouping everything. helped a lot
Not sure if this is the right thread to ask, but can I use safestrap to flash a custom kernel on the stock ROM?
Sent from my SCH-I535 using Tapatalk
root
The root method send me to the S4 forum. Is this the correct fourm for rooting my s3 4.3 using safestrap?
jl2222 said:
The root method send me to the S4 forum. Is this the correct fourm for rooting my s3 4.3 using safestrap?
Click to expand...
Click to collapse
Worked for me.
tyler.frost92 said:
Not sure if this is the right thread to ask, but can I use safestrap to flash a custom kernel on the stock ROM?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Actually, the safestrap thread would have been the best place to ask a question about safestrap. And no, you cannot flash a custom kernel on safestrap.
Sent from the Shark Tank using XDA Premium 4 mobile app
Thread updated with new information about the VRUCNC1 baseband.
Let me know if I missed something.
BadUsername said:
Thread updated with new information about the VRUCNC1 baseband.
Let me know if I missed something.
Click to expand...
Click to collapse
Don't know if I'm missing something or what.
But, I have the VRUCNC1 firmware and it's rooted. Was going to install SafeStrap, but not sure how that will work out.
(i previously had ML1 before the update forced itself upon me)
EVoorhees said:
Don't know if I'm missing something or what.
But, I have the VRUCNC1 firmware and it's rooted. Was going to install SafeStrap, but not sure how that will work out.
(i previously had ML1 before the update forced itself upon me)
Click to expand...
Click to collapse
If it was rooted before you can either enable survival mode in supersu or sometimes root will survive the Ota to nc1. Safestrap should work for you on nc1.
If you don't have root and you're on nc1, you're unable to root that.
Sent from my HTC6525LVW using Tapatalk
EVoorhees said:
Don't know if I'm missing something or what.
But, I have the VRUCNC1 firmware and it's rooted. Was going to install SafeStrap, but not sure how that will work out.
(i previously had ML1 before the update forced itself upon me)
Click to expand...
Click to collapse
BadUsername said:
If it was rooted before you can either enable survival mode in supersu or sometimes root will survive the Ota to nc1. Safestrap should work for you on nc1.
If you don't have root and you're on nc1, you're unable to root that.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Only problem that I'm noticing is that using Safestrap on VRUCNC1 requires VRUCNC1 kernel modules. These do not exist as of this moment of course. There have been a few users whom used Safestrap on VRUCNC1 then had no wifi when flashing the VRUCML1 kernel modules. So, there is a road block in that regards.
SlimSnoopOS said:
Only problem that I'm noticing is that using Safestrap on VRUCNC1 requires VRUCNC1 kernel modules. These do not exist as of this moment of course. There have been a few users whom used Safestrap on VRUCNC1 then had no wifi when flashing the VRUCML1 kernel modules. So, there is a road block in that regards.
Click to expand...
Click to collapse
That makes sense, thanks for posting that.
Sent from my HTC6525LVW using Tapatalk
SlimSnoopOS said:
Only problem that I'm noticing is that using Safestrap on VRUCNC1 requires VRUCNC1 kernel modules. These do not exist as of this moment of course. There have been a few users whom used Safestrap on VRUCNC1 then had no wifi when flashing the VRUCML1 kernel modules. So, there is a road block in that regards.
Click to expand...
Click to collapse
That's what I was planning on doing since I didn't see a module for NC1.
Thanks for the heads up, though.
Anyone know how I can add the ability to change songs using the volume buttons like in Cyanogenmod? I've been doing a little research and haven't found anything yet. Its not hugely important but would be one of the major things I need, besides the reseting volume and constant WiFi nag, that I need until I get time to get safestrap recovery and install a custom stock ROM. I'm pretty damn angry that the replacement phone I got from Asurion has the ML1 update. I personally can't stand TW. I wish there was a Boot loader unlock tool like HTC phones as I don't need a warranty anymore.
Any help would be appreciated. I'll update this if I can find anything, perhaps in a Xposed module. I'm sure what I'm looking g for is right in front of me and that I'm just oblivious of it.
Edit: Wanam Xposed seems to have one or more of the features I require. I haven't had the opportunity to teat it yet but that seems to be my solution.
Edit 2: had some issues where the phone was restarting. Defaulted everything back to normal and have only had 1 or two since. I didn't use many of the features of Wanam so I'm not sure exactly what it was.
Edit 3: It continued happening even after I flashed a stock .tar file in Odin and I eventually narrowed it down to the battery that asurion had sent me. Seems Wanam was not the culprit!
Sent from my SCH-I535 using Tapatalk
I will note that my phone has the line BOOTLOADER RP SWREV: 1 in the Download mode, which is different than what is up there. I have 4.3, ML1 update. Is there a difference? What does this line indicate, if anything?
Help! I have a Samsung S3 I535 for Verizon with the very latest baseband version ...NC1. At this point I can do nothing with the phone as far as root, recovery or a custom ROM! My Sprint version of the S3 is much easier to work with! I surmise that my phone has the Knox boot loader and can not be unlocked? However, I thought that the phone (I535) could be rooted and have a custom recovery. Is this correct and I just can't seem to find the proper thread or am I stuck with STOCK for the rest of this phones (probably short if I can't set it up to my liking) life?
len207 said:
Help! I have a Samsung S3 I535 for Verizon with the very latest baseband version ...NC1. At this point I can do nothing with the phone as far as root, recovery or a custom ROM! My Sprint version of the S3 is much easier to work with! I surmise that my phone has the Knox boot loader and can not be unlocked? However, I thought that the phone (I535) could be rooted and have a custom recovery. Is this correct and I just can't seem to find the proper thread or am I stuck with STOCK for the rest of this phones (probably short if I can't set it up to my liking) life?
Click to expand...
Click to collapse
Read the OP of this thread.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
If it was rooted before you can either enable survival mode in supersu or sometimes root will survive the Ota to nc1. Safestrap should work for you on nc1.
If you don't have root and you're on nc1, you're unable to root that.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Towelroot works with NC1 and is an APK.
5ft24 said:
Towelroot works with NC1 and is an APK.
Click to expand...
Click to collapse
Ya I read that a couple days ago, I'll add it to the OP when I get a chance.
Sent from my HTC6525LVW using Tapatalk
So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
My Current "About Phone" Info...
Android Version - 4.1.2
Baseband version - I535VRBMB1
Jelly Beans - Build 20
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol
aholeinthewor1d said:
So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol
Click to expand...
Click to collapse
Can't tell you exactly why that happened, but it shouldve worked.
You're right though, stay away from the stock Ota 4.3 update. I'm happy you read first because so many people don't. My guess is your firmware was a little too old. Try to flash the mf1 firmware aio and then try gummy.
To be clear, you can still use any custom rom, even the 4.3 ones, just stay away from the stock rom or anything having to do with 4.3 ML1 firmware
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Can't tell you exactly why that happened, but it shouldve worked.
You're right though, stay away from the stock Ota 4.3 update. I'm happy you read first because so many people don't. My guess is your firmware was a little too old. Try to flash the mf1 firmware aio and then try gummy.
To be clear, you can still use any custom rom, even the 4.3 ones, just stay away from the stock rom or anything having to do with 4.3 ML1 firmware
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply. What do you mean try to flash the MF1 firmware...does that mean a 4.2 ROM?
I think I saw the new jellyBeans/alliance ROM was 4.3...or maybe it was something else..either way it would be ok to flash the 4.3 ROM? and if I wanted I could go back to a 4.1 Rom then..
aholeinthewor1d said:
Thanks for the quick reply. What do you mean try to flash the MF1 firmware...does that mean a 4.2 ROM?
I think I saw the new jellyBeans/alliance ROM was 4.3...or maybe it was something else..either way it would be ok to flash the 4.3 ROM? and if I wanted I could go back to a 4.1 Rom then..
Click to expand...
Click to collapse
Yes you can interchange between both of them if you want to.
So go here, read all of the details, and just follow his recommendation:
http://forum.xda-developers.com/showthread.php?t=1788313
Also don't double post, modify your post in the development section and put "wrong section, mod please delete".
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Yes you can interchange between both of them if you want to.
So go here, read all of the details, and just follow his recommendation:
http://forum.xda-developers.com/showthread.php?t=1788313
Also don't double post, modify your post in the development section and put "wrong section, mod please delete".
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The reason I have so confused is cause of the link you sent. I read that before and it says..
"You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well."
Like i said I have been out for a while and lost track of what firmwares came out and the order of them and which I need to be on to flash a 4.4 ROM. Someone else told me the only reason my first flash failed was because my recovery was older
***EDIT****
Ignore that entire thing I just realized you said to stay away from ML1 and that MF1 is ok..opps
aholeinthewor1d said:
The reason I have so confused is cause of the link you sent. I read that before and it says..
"You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well."
Like i said I have been out for a while and lost track of what firmwares came out and the order of them and which I need to be on to flash a 4.4 ROM. Someone else told me the only reason my first flash failed was because my recovery was older
Click to expand...
Click to collapse
I see, that actually makes perfect sense.
I think I read you were on the mb1 firmware, that's new enough to not cause problems.
Basically you can't get the ml1 firmware from that thread I linked you. The only ml1 file available is the modem, and that's perfectly safe to flash.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I see, that actually makes perfect sense.
I think I read you were on the mb1 firmware, that's new enough to not cause problems.
Basically you can't get the ml1 firmware from that thread I linked you. The only ml1 file available is the modem, and that's perfectly safe to flash.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I think I am getting it... I am on MB1...next was MF1....and then ML1. As long as I have a new recovery I can flash any MF1 based ROM right over MB1...and then I can flash the ML1 modem ONLY. If that is correct let me know..also does it matter if I do MF1 ROM or ML1 modem first?
again just wanted to say thanks for the help I appreciate it
aholeinthewor1d said:
I think I am getting it... I am on MB1...next was MF1....and then ML1. As long as I have a new recovery I can flash any MF1 based ROM right over MB1...and then I can flash the ML1 modem ONLY. If that is correct let me know..also does it matter if I do MF1 ROM or ML1 modem first?
again just wanted to say thanks for the help I appreciate it
Click to expand...
Click to collapse
You're close, firmware is completely independent from rom. You can flash any 4.3, 4.4, or 4.1 rom without changing your firmware.
Right now you can flash mf1 aio package, then ml1 modem, or just flash the ml1 modem over your current mb1 firmware.
Basically you aren't required to be on a specific rom build in order to use a specific modem.
Edit: I think you have the right idea, flash any rom you want, then the mf1 aio package, then the ml1 modem. Your firmware sequence is correct.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
You're close, firmware is completely independent from rom. You can flash any 4.3, 4.4, or 4.1 rom without changing your firmware.
Right now you can flash mf1 aio package, then ml1 modem, or just flash the ml1 modem over your current mb1 firmware.
Basically you aren't required to be on a specific rom build in order to use a specific modem.
Edit: I think you have the right idea, flash any rom you want, then the mf1 aio package, then the ml1 modem. Your firmware sequence is correct.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
ah ok...idk why I was thinking the firmware was what the ROMs were based from....so either way ML1 firmware sucks and I stay away...I guess my last questions are...what would be an advantage of going to the MF1 firmware...
and I always used clockworkmod recovery...do you know the option available now? and maybe some features of each