Related
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Lembro said:
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Click to expand...
Click to collapse
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
RyanW114 said:
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
Click to expand...
Click to collapse
Agreed! Op, do more reading and less flashing before you end up with a 600.00 paperweight!
Like he says above you have not unlocked your bootloader . Restore nandroid or recover to stock. Then unlock your bootloader and try again
Sent from my SCH-I535 using xda premium
Get rid of the Verizon screen of death
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
MDMoore313 said:
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
Click to expand...
Click to collapse
Refer to my last post
droidstyle said:
Refer to my last post
Click to expand...
Click to collapse
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
refer to post #3 and read this link
http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13
Zalithian said:
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
Click to expand...
Click to collapse
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Zalithian said:
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Click to expand...
Click to collapse
That makes more sense, as the nightlys progress and more modifications are being made, overnight the "switch is flipped" so to speak, and if you're not running a custom rom,
MDMoore313 said:
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
Click to expand...
Click to collapse
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
The secure aboot.img only checks 3 of the 5 system images on boot. Since we can flash a custom recovery to the recovery partition, the secure aboot img lets it ride, but knows it there....hence why you see the custom lock screen, but device still boots. Kexec allowed the bootloader aka secure aboot.img to see the stock kernel(boot.img) and pass signature checks, then side loads the custom kernel. Thats why there was 3 reboots...now that the bootloader is unlocked, we ditch kexec because unsecure aboot is unlocked and not checking signatures.
However, if you flash a kernel thats non kexec and the bootloader is locked, you will get the verizon screen of death since the secure aboot.img is checking signatures. So never lock the bootloader unless your on stock rom/kernel or using kexec.
Deleted
Jesus. All of these people who don't read up on things before they flash something astounds me.
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
EvoSideHustlAZ said:
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ezrecovery to unlock? What?
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
No, that just means that it normally has detected some changed files. If you WERE unlocked you would never see that icon.
TAPPED in on my (now unlocked bootloader) Verizon S3
strung said:
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
Click to expand...
Click to collapse
Well, step 1 is going Odin back to stock, but if a cache wipe and factory reset aren't done (like in Droidstyle's guide), then it will never completely boot, at least that's what I experienced after my phone sat at that screen for 10+ minutes. It doesn't run the user setup again.
Ok, i rooted and unlocked the bootloader on my S3 per the directions here... i tried a few custom roms right a way and didnt like missing out on the touchwiz widgets on asop roms, so i went back to stock rooted and it stayed like that for months...
recently i decided to try some custom roms again which need the boot loader unlocked(clean rom) which will not boot. and MIUI which destroys my sd card's format.... this didn't happen before so i know something is messed up... these roms worked fine before and have a good reputation for stability... Im also seeing something new on boot.... as the samsung logo pops on the screen below it is seen a lock in the unlocked position... when i also go to oden mode i see that it lists my phones condition as custom!!!! The only instructions ive seen listed to get the phone back to stock is to oden the stock recovery.... which i have done... but the custom status remains... what am i missing? how can i get this thing to format competely back to factory so i can do a fresh unlock/root?
You need to use Triangle Away app to reset your flash counter
Thanks doesn't hurt....
ramdesai said:
You need to use Triangle Away app to reset your flash counter
Thanks doesn't hurt....
Click to expand...
Click to collapse
ok, how does the flash counter keep me from flashing custom roms properly? and is this unlocked lock saying my bootloader is still unlocked? i attached a pic of it at boot up...
i wasnt going to bother with the flash counter as i have no plans of sending this back to samsung, i just want to make sure the bootloader and OS are factory so i can re-root and unlock fresh....
If you have unlocked bootloader, then the samsung splash screen will quickly disappear else it takes some time. If u went to stock then re run procedure for the root. If you have root, you may use EZ-Unlock app to unlock bootloader.
Thanks doesn't hurt....
teddyv said:
Ok, i rooted and unlocked the bootloader on my S3 per the directions here... i tried a few custom roms right a way and didnt like missing out on the touchwiz widgets on asop roms, so i went back to stock rooted and it stayed like that for months...
recently i decided to try some custom roms again which need the boot loader unlocked(clean rom) which will not boot. and MIUI which destroys my sd card's format.... this didn't happen before so i know something is messed up... these roms worked fine before and have a good reputation for stability... Im also seeing something new on boot.... as the samsung logo pops on the screen below it is seen a lock in the unlocked position... when i also go to oden mode i see that it lists my phones condition as custom!!!! The only instructions ive seen listed to get the phone back to stock is to oden the stock recovery.... which i have done... but the custom status remains... what am i missing? how can i get this thing to format competely back to factory so i can do a fresh unlock/root?
Click to expand...
Click to collapse
Follow the instructions in this thread. It will get you back to factory stock.
http://forum.xda-developers.com/showthread.php?t=1867253
tscalia2 said:
Follow the instructions in this thread. It will get you back to factory stock.
http://forum.xda-developers.com/showthread.php?t=1867253
Click to expand...
Click to collapse
teddyv, I recently followed the instructions posted in tbe above thread that tscalia posted for you and they worked great!! After I got back to stock, I rerooted and put on twrp recovery... then I made sure to do a nandroid backup before I flashed any new roms.... that makes it easier to revert back next time
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Sleix said:
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window, rebooting the phone normally. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Click to expand...
Click to collapse
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Sleix said:
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Click to expand...
Click to collapse
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Sleix said:
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Click to expand...
Click to collapse
No, but it wouldn't hurt.
Use 1.2 of ez unlock, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
These are the most recent recoveries, download and flash in the ez recovery app if you need to.
http://forum.xda-developers.com/showthread.php?t=2096735
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
No, but it wouldn't hurt.
Use 1.2, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Sleix said:
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Click to expand...
Click to collapse
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Before flashing anything, use a newer recovery image. The one provided by ez recovery is from last year, the newer versions are better written to prevent possible errors that come up with jellybean.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Sleix said:
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Click to expand...
Click to collapse
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Will do. Thanks for pointing that edit out.
Well, im in a pickle. Im a GN2 user and I come to you with questions. This is in regards to my wifes phone, the one s. I went through all steps properly to achieve root (or so atleast I thought), I did not s-off. I had a working recovery and rooted phone running a custom rom and things were great. Now, Im not sure what happened exactly, but one day I tried to boot into recovery and I seen a quick flicker of cwm then it went back to hboot. I thought that all I would have to do is reflash recovery through cmd (im using win7) so I did this. This did not work. It gave me the ol green circular arrows on blk screen then the red triangle. Power down reboot and it still boots normally. Now heres the part thats hard to admid. I found this device was not worth the damn trouble it was giving me so as a metaphorical 'f u' to the phone, through hboot I chose reset device. Things dont seem to be any different but I know I f'd something up. I still have (or atleast I believe) an unlocked bootloader but thats where the truck stops. Thanks guys.
Sent from my SGH-I317M using xda premium
mstickland said:
Well, im in a pickle. Im a GN2 user and I come to you with questions. This is in regards to my wifes phone, the one s. I went through all steps properly to achieve root (or so atleast I thought), I did not s-off. I had a working recovery and rooted phone running a custom rom and things were great. Now, Im not sure what happened exactly, but one day I tried to boot into recovery and I seen a quick flicker of cwm then it went back to hboot. I thought that all I would have to do is reflash recovery through cmd (im using win7) so I did this. This did not work. It gave me the ol green circular arrows on blk screen then the red triangle. Power down reboot and it still boots normally. Now heres the part thats hard to admid. I found this device was not worth the damn trouble it was giving me so as a metaphorical 'f u' to the phone, through hboot I chose reset device. Things dont seem to be any different but I know I f'd something up. I still have (or atleast I believe) an unlocked bootloader but thats where the truck stops. Thanks guys.
Sent from my SGH-I317M using xda premium
Click to expand...
Click to collapse
so about what do U need help here,if U reboot to bootloader U will see if its unlocked or locker ,it will be stated so on top of all,but if U cant flash recovery than bootloader is LOCKED,to flash recovery U will need to unlock bootloader first and if U want pure stock just flash proper RUU
I was rooted and made the mistake of accepting the latest OTA update, which I assume was the new and devious 4.3. The update process seemed to work fine, but on reboot, phone is now freezing at the white Verizon logo screen.
My boot sequence looks like this: "SAMSUNG ([lock pic] Custom)" -> "SAMSUNG GALAXY S III" on black -> Swirly SAMSUNG logo on black -> Verizon animation on white -> HANG at indefinitely repeating few-frame loop animation of shining Verizon logo on white background.
I can get to Download mode - it looks like this:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: Yes (2 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
*NO* mention of Warranty Bit.
Does this mean I am still on 4.1.2 and not dreaded 4.3 Knox? I don't want to screw up and accidentally brick this thing.
Unfortunately I have crappy notes from my original rooting, so I don't know if I had a simple root or custom ROM or custom bootloader or what. I know I have CF-Auto-Root-d2vzw-d2vzw-schi535.tar.md5, VRBMB1_Bootchain.tar.md5, and VRALEC.bootchain.tar.md5 in my work folder, and I was only rooting so I could use SGS3 Easy UMS so I likely did whatever method was needed for that.
How can I get back to functional? Stock or custom, I don't care, but with all the bricking dangers I'm reading about after this new OTA update I just want to proceed extra carefully. Also I'd really like to not have to wipe the phone with a factory reset or anything like that.
Thanks for your help!
scrowdid said:
I was rooted and made the mistake of accepting the latest OTA update, which I assume was the new and devious 4.3. The update process seemed to work fine, but on reboot, phone is now freezing at the white Verizon logo screen.
My boot sequence looks like this: "SAMSUNG ([lock pic] Custom)" -> "SAMSUNG GALAXY S III" on black -> Swirly SAMSUNG logo on black -> Verizon animation on white -> HANG at indefinitely repeating few-frame loop animation of shining Verizon logo on white background.
I can get to Download mode - it looks like this:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: Yes (2 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
*NO* mention of Warranty Bit.
Does this mean I am still on 4.1.2 and not dreaded 4.3 Knox? I don't want to screw up and accidentally brick this thing.
Unfortunately I have crappy notes from my original rooting, so I don't know if I had a simple root or custom ROM or custom bootloader or what. I know I have CF-Auto-Root-d2vzw-d2vzw-schi535.tar.md5, VRBMB1_Bootchain.tar.md5, and VRALEC.bootchain.tar.md5 in my work folder, and I was only rooting so I could use SGS3 Easy UMS so I likely did whatever method was needed for that.
How can I get back to functional? Stock or custom, I don't care, but with all the bricking dangers I'm reading about after this new OTA update I just want to proceed extra carefully. Also I'd really like to not have to wipe the phone with a factory reset or anything like that.
Thanks for your help!
Click to expand...
Click to collapse
You got lucky. For some reason your boot chain didn't flash so it's still unlockable.
You need to flash this file in Odin:
http://www.androidfilehost.com/?fid=23134718111254196
Using section 5 of this guide:
http://forum.xda-developers.com/showthread.php?t=1762709
Then root and unlock with casual:
http://forum.xda-developers.com/showthread.php?t=2332825
Then download ez unlock 1.2 and verify it's unlocked.
Then you're good to go again. Install a custom rom and never accept an Ota again.
As far as wiping your phone goes, you can't really do much about that, this is pretty much a last resort.
Sent from my SCH-I535 using Tapatalk 2
It's a nice write up Badusername..:good:
I just want to add that if you want to keep stock rooted, just make sure you disabled OTA. Like Badusername mentioned if you decided to flash custom rom then you don't have to worry about OTA.
If that's everything in download mode, then you are still on 4.1.2. If you want to try retaining your /sdcard data, then you could try Odin flashing the no-wipe VRBMB1 image.
If you would like to start clean and wipe away /sdcard, then Odin flash this VRBMF1 4.1.2 stock image. You would need to root and unlock in both cases. DO NOT accept the 4.3 OTA in either case.
Edit: ninja'd lmao...badly
Thanks! I am operational again with the No-Wipe flash. Whew!
Unfortunately, it looks like I lost all my text messages though. That was one of the main things I had been hoping to preserve, to keep a record of some conversations. Unless there's something I'm missing and they might still be lurking somewhere?
My photos survived and it looks like apart from a few settings it's mostly unwiped. Cool! Glad I didn't ruin it. Now I can try a custom 4.3 or something else if I want, but for now I'm just glad to have it working again.
This happened to me after flashing VZW-I535VRUCML1-20131220083128 instentionally to return back to stock.
after flashing with odin in PDA mode, the samsung 'custom' screen came on then the loop on the white logo.
blueblur said:
This happened to me after flashing VZW-I535VRUCML1-20131220083128 instentionally to return back to stock.
after flashing with odin in PDA mode, the samsung 'custom' screen came on then the loop on the white logo.
Click to expand...
Click to collapse
Did you boot into recovery and do a factory reset?
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Did you boot into recovery and do a factory reset?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
When? Before flashing stock? No. After? No, but if I can get into recovery, I will.
edit:::
went into recovery after flashing odin image, that did the trick. thank you.
still showing 'custom' when starting up
blueblur said:
When? Before flashing stock? No. After? No, but if I can get into recovery, I will.
edit:::
went into recovery after flashing odin image, that did the trick. thank you.
still showing 'custom' when starting up
Click to expand...
Click to collapse
No problem. Idk why custom would be there unless you tried flashing something pre-4.3 in Odin beforehand? Odin flashing the VRUCML1 tar would wipe everything else off the phone in terms of rom and root. It doesn't affect anything unless you plan on doing a warranty replacement.
SlimSnoopOS said:
No problem. Idk why custom would be there unless you tried flashing something pre-4.3 in Odin beforehand? Odin flashing the VRUCML1 tar would wipe everything else off the phone in terms of rom and root. It doesn't affect anything unless you plan on doing a warranty replacement.
Click to expand...
Click to collapse
I was trading it in to verizon for the note 3. i'm good to go now. thanks for your help!
scrowdid said:
Thanks! I am operational again with the No-Wipe flash. Whew!
Unfortunately, it looks like I lost all my text messages though. That was one of the main things I had been hoping to preserve, to keep a record of some conversations. Unless there's something I'm missing and they might still be lurking somewhere?
My photos survived and it looks like apart from a few settings it's mostly unwiped. Cool! Glad I didn't ruin it. Now I can try a custom 4.3 or something else if I want, but for now I'm just glad to have it working again.
Click to expand...
Click to collapse
Just a suggestion. I use an app in the play store called sms backup plus. It backs up your texts to your email.
https://play.google.com/store/apps/details?id=com.zegoggles.smssync
Sent from my SCH-I535 using Xparent ICS Tapatalk 2