Alright so I started the process of rooting, unlocking, and flashing the Bean ROM on my VZW GS3. I backed up using Nandroid and Titanium backup, rooted and unlocked the bootloader using EX Unlock yesterday. Then, without flashing a ROM, I rebooted my phone. And then I got drunk. Today, I flashed recovery, booted into recovery mode, deleted the user data (again) and installed then installed the Bean ROM. I figured my bootloader was still unlocked but I guess it wasn't. Now I'm getting the "This System Software not authorized by Verizon Wireless..." message.
Anybody have any clue what to do now?
Restock the Rom via odin flash of stock files from Adams thread
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
You say you made a nandroid yesterday but today you just flashed recovery. I'm confused.
Sent from my SCH-I535 using xda app-developers app
If you use ez unlock I'd say unlock and lock twice. Recovery told me I wasn't unlocked at first.
Sent from my SCH-I535 using xda premium
Hey guys, so I have been trying to work at this and here is where I'm at...
I'm following section 6 of this post [http://forum.xda-developers.com/showthread.php?t=1762709]. Everything works as listed except for when I select the ROM from the three in that post and try and run it through Odin. It always fails. I tried all three ROMs with the same result and since I don't know what exactly is keeping this from working, I can't troubleshoot it in any way. If anyone could help, I would really appreciate it.
Thank you!
Related
Yikes, am I in a predicament.
So, here I am, with my Nexus S I9020A on Koodo in Canada, rooted with TWRP v2.2.0 recovery and stock 4.0.4; well, with all the JellyBean buzz going about I figured, hey, why not, and I made a nandroid backup using TWRP, and copied said backup onto my PC for an extra copy.
Well, after playing around with an AOSP rom of 4.1.1 I want the stock OTA, but restoring the backup I made yields no results, touting "no recovery or img" as an error. So now I have no idea how to get to either stock JellyBean (which is where I want to be) or at least stock 4.0.4 for the I9020A so I can get the OTA.
What do I do?!
Try flashing twrp again. I had this problem on my ns4g awhile ago while running one of the older twrp recoveries. If memory serves, I was able to reflash twrp, reboot recovery, then restore a twrp backup. If it still won't restore, try wiping & flashing a ROM of your choice. You may have to adb fastboot flash...
Sent from my Nexus S 4G using xda premium
p1gp3n said:
Try flashing twrp again. I had this problem on my ns4g awhile ago while running one of the older twrp recoveries. If memory serves, I was able to reflash twrp, reboot recovery, then restore a twrp backup. If it still won't restore, try wiping & flashing a ROM of your choice. You may have to adb fastboot flash...
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I'm trying to reflash TWRP and restore again - fingers crossed.
What happened to that list of all official OTA variants for the Nexus S?
I'm referring to that list that had for instance :
Nexus S - I9020A:
2.3.4 - Download link
2.3.6 - Download link
etc, etc.
I just want to get back to stock 4.0.4 so I can get the 4.1.1 OTA :S
Or have any way to get to STOCK 4.1.1 for the I9020A Nexus :S
Found this link posted by user oldblue910, it should have what you need if you're still stuck... http://www.randomphantasmagoria.com/firmware/nexus-s/
Sent from my Nexus S 4G using xda premium
p1gp3n said:
Found this link posted by user oldblue910, it should have what you need if you're still stuck... http://www.randomphantasmagoria.com/firmware/nexus-s/
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
That's exactly what I was looking for, thanks, ended up just taking the long road there and back from Gingerbread to JellyBean, so far so good!
Thanks for everyone's help!
Whenever I boot into recovery I get this: #MANUAL MODE# --Appling multi-csc... applied the csc-code : VZW SUCCESSFULLY. APPLIED multi-csc.
I'm rooted and bootloader unlocked (I think) .I just DL ota zip VRALG7. PLEASE ADVISE before I attack someone ....thx
Sent from my GT-P5113 using XDA Premium HD app
You're not sure if you're unlocked, well are you in a custom recovery when this happens? Which one? How did you root/unlock? That error doesn't look familiar at all. I want to say Odin back to stock then root and then unlock.
Your post is worded oddly. Are you saying you accepted the Verizon OTA then this code presents itself on the stock recovery?
Sent from my SCH-I535 using xda app-developers app
My bad just a lot upset with vzw. Before I updated that vrlg7 zip update I was rooted with unlocked boot loader running cm 10 nightlies. When I updated it took root and who knows what else. I then rerooted and tried using the e-z unlock app, rooted but don't think I'm unlock because of the vzw applied file or whatever that said. All I know is I can't load my cm 10 nightlies. But I'm rooted please. Help.
Sent from my GT-P5113 using XDA Premium HD app
Just Odin back to stock using section 6 of http://forum.xda-developers.com/showthread.php?t=1762709this thread then root/unlock. Use EZ unlock v1.2 http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/from here. You'll be fine to use CM10 once you install recovery using EZ Recovery which is in the Play Store. You already know this process deletes your data so use whatever method you are familiar with to recover your apps and contacts.
Also, backup your IMEI.
Sent from my SCH-I535 using xda app-developers app
thx dude you are the man....
Hello guys I just got may galaxy S3 from a friend. I think the bootloader is still unlocked after I received an OTA today. I don't have root or recovery. I just want to be sure I use the correct root and recovery method. Could someone point me to the one they used on this build with success? I would be greatly appreciated. I did look but none are specific enough for me to be sure I'm using the correct one.
Is my bootloader still unlocked if it says (custom)?
Again I appreciate any help
Sent from my SCH-I535 using xda premium
mike216 said:
Hello guys I just got may galaxy S3 from a friend. I think the bootloader is still unlocked after I received an OTA today. I don't have root or recovery. I just want to be sure I use the correct root and recovery method. Could someone point me to the one they used on this build with success? I would be greatly appreciated. I did look but none are specific enough for me to be sure I'm using the correct one.
Is my bootloader still unlocked if it says (custom)?
Again I appreciate any help
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Welcome! In order to unlock your BL in the first place you must have had root. This is a good thread on rooting, unlocking, and flashing recovery/ROMs/kernels:
http://forum.xda-developers.com/showthread.php?t=1762709
nghtrain88 said:
Welcome! In order to unlock your BL in the first place you must have had root. This is a good thread on rooting, unlocking, and flashing recovery/ROMs/kernels:
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
Thanks so much bud! Will I be all good on the updated build I received today?
My bootloader is unlocked if it says custom on boot?
Again I really appreciate it!
Sent from my SCH-I535 using xda premium
mike216 said:
Thanks so much bud! Will I be all good on the updated build I received today?
My bootloader is unlocked if it says custom on boot?
Again I really appreciate it!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
As long as you have one of the stock builds listed in section 2 of that thread you should be good. The EZ-unlock app should be able to tell you if you're BL is unlocked.. also if you reboot the phone, if the samsung splash flashes for a split second (the one before you see Samsung Galaxy SIII), then you're prob unlocked.. if you see it for a few seconds then you're prob locked
Man I rooted flashed recovery in rom manager. (recovery wouldn't stick) so I flashed it again after making a nandroid and ended up having to recover a soft brick at 4am. Thank God for puremotive's guide on how to recover from it I was able to be back up. I don't know what went wrong. Because I didn't have busy box. Maybe I shouldn't have used the latest recovery rom manager flashes? I'm on stock with root and afraid to move anywhere! Anyone know how to make recovery stick on stock rom? I've never had this happen. Usually I would be OK and on to try AOSP on other devices uve had. Right now I'm rooted on stock rom with bootloader unlocked and have OTA root keeper in case I get another OTA. Any help would be greatly appreciated! Take care
Sent from my SCH-I535 using xda premium
How did you unlock your bootloader?
annoyingduck said:
How did you unlock your bootloader?
Click to expand...
Click to collapse
With the app
Sent from my SCH-I535 using xda premium
Ok, issue is probably that you used the current version 1.4 I think. In the app description in the playstore is a link to older versions, you want 1.2. The new ones are unlocking, but it's not sticking. There is also a link in the current root guide somewhere, but direct from the play store is fine.
annoyingduck said:
Ok, issue is probably that you used the current version 1.4 I think. In the app description in the playstore is a link to older versions, you want 1.2. The new ones are unlocking, but it's not sticking. There is also a link in the current root guide somewhere, but direct from the play store is fine.
Click to expand...
Click to collapse
link for ez-unlock 1.2
annoyingduck said:
How did you unlock your bootloader?
Click to expand...
Click to collapse
Let me be more specific because I may have had a locked bootloader.
I received the phone yesterday from my friend. He did unlock the bootloader with the app. I installed the official OTA from Verizon as soon as I got it. I rooted it. I didn't bother trying to unlock the bootloader because after the OTA when it booted it said custom with a lock symbol on boot up. I rooted and flashed the latest recovery from rom manager. I'm sure I picked the right phone. I made a nandroid but my recovery wouldn't stick. I remember it saying something about Co firming something about a recovery and I could have chosen yes. It sounded like CWM wouldn't stick if I choose yes?
I don't know if the OTA locked my bootloader back up?
I would like to try again. Any of you guys no how to make recovery stick on stock rom? I would like to try paranoid android. What recovery should I be on to flash this jelly bean based rom? I would really appreciate anyone who knows how I screwed up or has went straight to JB from a specific CWM recovery. I'm also not sure if I should said yes or know when in CWM when asking me that recovery question. I wish I remember what the question was
Sent from my SCH-I535 using xda premium
nghtrain88 said:
As long as you have one of the stock builds listed in section 2 of that thread you should be good. The EZ-unlock app should be able to tell you if you're BL is unlocked.. also if you reboot the phone, if the samsung splash flashes for a split second (the one before you see Samsung Galaxy SIII), then you're prob unlocked.. if you see it for a few seconds then you're prob locked
Click to expand...
Click to collapse
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
mike216 said:
Man I rooted flashed recovery in rom manager. (recovery wouldn't stick) so I flashed it again after making a nandroid and ended up having to recover a soft brick at 4am. Thank God for puremotive's guide on how to recover from it I was able to be back up. I don't know what went wrong. Because I didn't have busy box. Maybe I shouldn't have used the latest recovery rom manager flashes? I'm on stock with root and afraid to move anywhere! Anyone know how to make recovery stick on stock rom? I've never had this happen. Usually I would be OK and on to try AOSP on other devices uve had. Right now I'm rooted on stock rom with bootloader unlocked and have OTA root keeper in case I get another OTA. Any help would be greatly appreciated! Take care
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
mike216 said:
Let me be more specific because I may have had a locked bootloader.
I received the phone yesterday from my friend. He did unlock the bootloader with the app. I installed the official OTA from Verizon as soon as I got it. I rooted it. I didn't bother trying to unlock the bootloader because after the OTA when it booted it said custom with a lock symbol on boot up. I rooted and flashed the latest recovery from rom manager. I'm sure I picked the right phone. I made a nandroid but my recovery wouldn't stick. I remember it saying something about Co firming something about a recovery and I could have chosen yes. It sounded like CWM wouldn't stick if I choose yes?
I don't know if the OTA locked my bootloader back up?
I would like to try again. Any of you guys no how to make recovery stick on stock rom? I would like to try paranoid android. What recovery should I be on to flash this jelly bean based rom? I would really appreciate anyone who knows how I screwed up or has went straight to JB from a specific CWM recovery. I'm also not sure if I should said yes or know when in CWM when asking me that recovery question. I wish I remember what the question was
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Brian Gove said:
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Click to expand...
Click to collapse
Thanks for everything Boss! That probably was the reason my recovery wouldn't stick. I used the link to grab easy unlock 1.2. I'm now unlocked, rooted. I want to flash an AOSP based rom (paranoid android) what recovery should I flash? The newest in rom manager or the slightly older one EZ-Recovery has to offer?
Thanks once again!
Sent from my SCH-I535 using xda premium
Cwm 6.0.1.2 for aosp jb, do not use the old 5 . something touch in ez recovery
mike216 said:
Thanks for everything Boss! That probably was the reason my recovery wouldn't stick. I used the link to grab easy unlock 1.2. I'm now unlocked, rooted. I want to flash an AOSP based rom (paranoid android) what recovery should I flash? The newest in rom manager or the slightly older one EZ-Recovery has to offer?
Thanks once again!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Which is the recovery that you want to use? I have the latest CWM touch on my Dropbox if that's the one you want. The regular CWM in the app is fine to use and twrp recovery has a thread in the development forum.
Brian Gove said:
Which is the recovery that you want to use? I have the latest CWM touch on my Dropbox if that's the one you want. The regular CWM in the app is fine to use and twrp recovery has a thread in the development forum.
Click to expand...
Click to collapse
I'm on stock ICS in want to go to paranoid android. Sorry guys but after last night I'm paranoid myself!
Sent from my SCH-I535 using xda premium
Brian Gove said:
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Click to expand...
Click to collapse
Thanks once again! I'm now on PA after a pack of smokes! Appreciate all your help. You were absolutely right ! Recovery stuck and it flashed with no problem. I used the current recovery straight from ROM manager
Sent from my SCH-I535 using xda premium
Good, glad to hear you got it rolling.
i have a tmobile galaxy s3. i had installed clockworkmod and it was rooted soon after i bought it. then i unrooted it not to long ago waiting for jellybean update. anyways, i got tired of waiting. tried to re-root the phone. cwm still on phone. then accidentally erased and resetted all data and info. lost all info on internal memory card. phone reset to original settings. now, when i try to reload cwm, it doesn't work.when i run odin, and install cwm, everything goes ok, it passes. but when i try to boot to cwm, it only comes up to the android recovery. tried multiple odins and cwm tar files. none seem to work. going crazy, need rooted phone again. pppplllllleeeaaassseeeee help!
flash it
if you are rooted but just need cwr fixed-up you could just go to playstore and download one click recovery flasher or rommanager and let the app flash it for you.
I cant get my ns4g to flash a diff recovery
Sent from my Nexus S 4G using Tapatalk 2
Google the S3 QCOM Toolkit for all US varients. Download to ur laptop or computer and run the process. It just that easy. My SGS3 (atat) needed to be completely reset to facotry condition. When I got it back I used odin for a new recovery and root access but it always went back to stock recovery. Make use debugging is selected and it should take less than 5 mins.
Sent from my SGH-I777 using xda premium
Sorry I meant to say the S3 Snapdragon toolkit V2.3 which is the ALL-IN-ONE tool for all US SGS3 variants.
Sent from my SAMSUNG-SGH-I747 using xda premium
Everything was fine with the root however I used a font app installer that got the phone stuck in a boot loop (on the rainbow screen). How do I get back to rooted JB?
Did you do a back up of your original rom? You need to get back into recovery...
Sent from my SCH-I535 using xda app-developers app
No I didn't. I didn't see that in the instructions or I missed it. Any thoughts on how to get back to rooted JB?
Well if the font app got you into the boot loop then I don't think you lost root, I would get back into recovery wipe cache and hit reboot... See if that works... Good luck
Sent from my SCH-I535 using xda app-developers app
Unfortunately, I tried that. I think I did an accidental factory reset too but nothing has brought it back from the boot rainbow screen.
Did you unlock using EZ Unlock v1.2? You only mentioned that you rooted.
Sent from my SCH-I535 using xda app-developers app
No, I didn't use that. I followed the instructions to root found here (worked no problem until I met that $&#^%#& app) http://forum.xda-developers.com/showthread.php?t=2046439 I think I can reset using Odin I just don't know what to use
Aight, well did you unlock the bootloader? Your response dictates the suggested route to resolve this.
Sent from my SCH-I535 using xda app-developers app
I did follow the instructions to unlock the bootloader
If that's the case then you just need to boot into recovery and flash a rom. If you were running just stock rooted & unlocked VRBLK3, it's easier to just flash a rooted stock rom like the official VRBLK3 leak here: http://forum.xda-developers.com/showthread.php?t=2034118
Try just flashing that, without wiping, then boot into the rom.
or
If you were on a custom rom, just reflash that rom via recovery and you'll be fine. Unfortunately you lose all your settings of you wipe data in recovery so try reflashing either option without wiping if you absolutely need to try recovering whatever data already exists in your current rom. If this doesn't work, format data, wipe cache then flash the rom.
Sent from my SCH-I535 using xda app-developers app
I will give it a shot and let you know. Thanks so much! I was on stock ROM btw.
Cool, this should work
Sent from my SCH-I535 using xda app-developers app
Ok, this is a zip file. Does it have to be on the phone? If so, how do I put it there?
nctiger said:
Ok, this is a zip file. Does it have to be on the phone? If so, how do I put it there?
Click to expand...
Click to collapse
Yes it does need to be there. If you have an sdcard just drag and drop onto it directly then flash in your custom recovery. Conversely, you should be able to boot into recovery and try connecting your phone to the laptop then dragging the zip over.
The longer method will be to Odin flash VRBLK3 and start all over from there.
Sent from my SCH-I535 using xda app-developers app
I am in Clockwork Mod recovery and my comp is not recognizing my phone as it did earlier.
nctiger said:
I am in Clockwork Mod recovery and my comp is not recognizing my phone as it did earlier.
Click to expand...
Click to collapse
I don't use CWM but did you go to Mounts and Storage and select "Mount /sdcard"? Does it connect now?
Sent from my SCH-I535 using xda app-developers app
I went there but it didn't seem to do anything when I selected mount sdcard and conversely didn't connect either
nctiger said:
I went there but it didn't seem to do anything when I selected mount sdcard and conversely didn't connect either
Click to expand...
Click to collapse
Aight well since that failed, you have to do this the long way: Odin flash the VRBLK3 rooted image from your laptop onto your phone. Choose one of the two images for VRBLK3 and follow the directions.
http://forum.xda-developers.com/showthread.php?t=1984436
Edit: I realize I didn't ask but do you have an sd card?
Sent from my SCH-I535 using xda app-developers app
That worked! Thanks so much. Now, what is the best practice for backing things up so that I don't have this problem again? Should I root first then backup? Do I still have to unlock bootloader? Just wanting to handle this properly from this point forward.
It should be rooted already if you installed the Odin files from MrRobinson thread. It should come with either SuperSU or SuperUser correct? You also should still be unlocked but you can re-unlock using EZ Unlock v.1.2 from the following thread and you're undeniably unlocked. You'll hear a brief audio message if it worked.
http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
Also, please perform a nandroid back in CWM so you have something stable to return to if something goes awry in the future. That backup would have cut all this down to one simple step. You don't need to be unlocked to perform a nandroid however you do need to be rooted with a custom recovery.
Lastly, perform an IMEI backup using the "Comprehensive IMEI Backup" thread in the dev section. Do this and save the resulting Synergy zip from backup methods A and B in more than one place not on your phone. This is more so a precaution because flashing things in recovery can and may result in a complete loss of connection with Verizon.
Sent from my SCH-I535 using xda app-developers app