Database Info

CWM won't stick...Even with locked bootloader

I rooted according the directions found here: http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/ after getting a new Nexus S 4G.
Even after locking the bootloader. It goes to the Android-with-box then to the Exclaimation-point-inside triangle. When I volume-up and power-button from that screen, an "Android Recovery <3e>" comes up...
Does anyone know what might be going on? And how do I get my custom recovery to stick?

Well, that's my post, so ill try to help. First, and don't take this the wrong way, but did you follow those instructions to a T? When you boot into bootloader, your pushing CWM to you phone with the fastboot command?
Sent from my Nexus S 4G using XDA App

mikeyinid said:
Well, that's my post, so ill try to help. First, and don't take this the wrong way, but did you follow those instructions to a T? When you boot into bootloader, your pushing CWM to you phone with the fastboot command?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...

TonyArmstrong said:
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
Click to expand...
Click to collapse
Apparently alot of people have this issue, me included. I seen some posts about using root explorer to change the name of the recovery image if it shows up in system /ext. Sounds crazy but I hear it doesn't show up on all phone's. IV come to terms with having to fastboot every time I flash but I'd love to see a fix. Have you tried Amons recovery?

TonyArmstrong said:
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
Click to expand...
Click to collapse
Have you flashed recovery through Rommanager when your phone boots up?

You have to flash a non-stock kernel, the recovery gets overwritten on reboot. So if you flash CWM and reboot without flashing a custom kernel you will be back to stock recovery.
Edit: oops maybe I was wrong lol, maybe it isnt the kernel. im assuming you flashed the recovery in fastboot?

mbh87 said:
You have to flash a non-stock kernel, the recovery gets overwritten on reboot. So if you flash CWM and reboot without flashing a custom kernel you will be back to stock recovery.
Edit: oops maybe I was wrong lol, maybe it isnt the kernel. im assuming you flashed the recovery in fastboot?
Click to expand...
Click to collapse
No, I dont think your wrong bro. It makes sense. Ill test your theory soon.

Tony, when you push CWM, are you able to boot into recovery by hitting volume down twice to recovery and hitting power? If so, I suggest you flash this ROM. Its stock rooted and you will not have problems with CWM sticking. You dont even have to wipe to flash it...

I've read on some methods for rooting that there is a file /system/etc/install-recovery.sh (or something like that, should be able to find it by mounting system in recovery and adb shell ls /system/etc then using adb shell rm -r /system/etc/install-recovery.sh).
Though after I fastboot flashed the recovery, booted into recovery, did a nandroid, I formatted /system before I flashed CM7, so that would've killed the file anyways.

david1171 said:
I've read on some methods for rooting that there is a file /system/etc/install-recovery.sh (or something like that, should be able to find it by mounting system in recovery and adb shell ls /system/etc then using adb shell rm -r /system/etc/install-recovery.sh).
Though after I fastboot flashed the recovery, booted into recovery, did a nandroid, I formatted /system before I flashed CM7, so that would've killed the file anyways.
Click to expand...
Click to collapse
I just had CWM, never had any issues. Im not sure what dictates whether that file is there or not. Im guessing that since tony is so quiet though he got it figured out..

whats amazing is i dont have this script and its one of the things holding the one click up :x
also its part of init.rc so technically a new kernel would.. in theory wipe that out...

mikeyinid said:
Have you flashed recovery through Rommanager when your phone boots up?
Click to expand...
Click to collapse
I did flash CWM through Rom Manager. That didn't work the first few times. It stalled...

mikeyinid said:
Tony, when you push CWM, are you able to boot into recovery by hitting volume down twice to recovery and hitting power? If so, I suggest you flash this ROM. Its stock rooted and you will not have problems with CWM sticking. You dont even have to wipe to flash it...
Click to expand...
Click to collapse
I got it to stick -- or at least i thought I had it. I followed the initial instructions provided in a previous thread. And per the instructions, I download Rom Manager and I installed CWM through it (again).
I'm going to wipe my phone fully -- reinstall the base 2.3.4 with the the stock recovery, via the IMG files for GRJ22 and start over...See what happens then.

Wait, I'm confused. Why would you flash stock images when your already stock? If you follow the instructions in the link you posted in the op there is no reason you shouldn't be rooted. Have you actually even booted into recovery?
TonyArmstrong said:
I got it to stick -- or at least i thought I had it. I followed the initial instructions provided in a previous thread. And per the instructions, I download Rom Manager and I installed CWM through it (again).
I'm going to wipe my phone fully -- reinstall the base 2.3.4 with the the stock recovery, via the IMG files for GRJ22 and start over...See what happens then.
Click to expand...
Click to collapse
Sent from my Nexus S 4G using XDA App

I realllyyy don't suggest flashing a recovery with rom manager. I'm not bashing ROM Manager, I'm a paid user, but the way that it flashes recoveries is unsafe. I've had it almost brick my Evo and I've seen it brick other phones.
Just use fastboot... if you can't get that working, you probably shouldn't be messing with the phone.

mikeyinid said:
Wait, I'm confused. Why would you flash stock images when your already stock? If you follow the instructions in the link you posted in the op there is no reason you shouldn't be rooted. Have you actually even booted into recovery?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I'm rooted successfully. I feel more comfortable (with recovery acting flaky) with unrooting and starting over from scratch...
Call me kooky, but a bone-stock unrooted phone with no user data, no nothing, is how I got it, so why not return it to that state and start over. That's the only way I know to insure that whatever I do is not influenced by any data, bad file permissions, etc. that could hose rooting and installing recovery.

TonyArmstrong said:
I'm rooted successfully. I feel more comfortable (with recovery acting flaky) with unrooting and starting over from scratch...
Call me kooky, but a bone-stock unrooted phone with no user data, no nothing, is how I got it, so why not return it to that state and start over. That's the only way I know to insure that whatever I do is not influenced by any data, bad file permissions, etc. that could hose rooting and installing recovery.
Click to expand...
Click to collapse
OCD, I know the feeling lol. What got it to stick?

derekwilkinson said:
I realllyyy don't suggest flashing a recovery with rom manager. I'm not bashing ROM Manager, I'm a paid user, but the way that it flashes recoveries is unsafe. I've had it almost brick my Evo and I've seen it brick other phones.
Just use fastboot... if you can't get that working, you probably shouldn't be messing with the phone.
Click to expand...
Click to collapse
I used fastboot to install CWM initially (fastboot flash recovery recovery-xxxxx.zip -- can't remember the filename right now). The directions for rooting the NS4G state explicitly to use ROM Manager to flash the recovery to "make sure it sticks" after initially pushing it to the phone via fastboot.
It's obviously a hack, but apparently it works more often than it fails.
I'm a paid user of ROM Manager as well. I have to admit, it was fine to flash Amon Ra to my Evo. Since I'm new(er) to the NS4G, I'm going to defer to those with more expertise and follow the directions given.

TonyArmstrong said:
I used fastboot to install CWM initially (fastboot flash recovery recovery-xxxxx.zip -- can't remember the filename right now). The directions for rooting the NS4G state explicitly to use ROM Manager to flash the recovery to "make sure it sticks" after initially pushing it to the phone via fastboot.
It's obviously a hack, but apparently it works more often than it fails.
I'm a paid user of ROM Manager as well. I have to admit, it was fine to flash Amon Ra to my Evo. Since I'm new(er) to the NS4G, I'm going to defer to those with more expertise and follow the directions given.
Click to expand...
Click to collapse
well the "make sure it sticks" flashing with rom manager doesn't make any sense. the only way the recovery would be overwritten is if the ROM you flash over writes it or in fastboot

mikeyinid said:
OCD, I know the feeling lol. What got it to stick?
Click to expand...
Click to collapse
Yeah, I'm very anal when it comes to this kind of stuff...I was a developer for a little bit (Java middleware, then on to the front-end stuff) where regression testing was important. Sometimes, it's best to reload things piece by piece to see what breaks what. Then go from there.
I haven't gotten it to stick yet; gonna get some sleep and start over tomorrow. I used fastboot to push the stock boot, bootloader, system, recovery, and userdata IMGs a moment ago, and the phone is back to bone stock.

Ready for 2.3.6., or am I?

Haven't really done much to my phone in a while but now that I got the sdcard issue fixed and the phone is stable I got on here to see if any new developments in the ulocked bootloader front and noticed we now have an update to 2.3.6. I wish it was ICS but that's coming, so I'd like to upgrade to the latest firmware and would like to know the best way I should go about it.
I'm currently rooted and have removed most of if not all of the bloatware, I've read that can cause problems when doing the OTA update. Is that true? If so, will doing a factory reset restore all that's needed to allow me to do the OTA?
I have no desire to flash lfabers deodexed 2.3.6 since the volume rocker isn't working right (or so I heard).
If a factory reset is not good enough should I install RSDLite 5.6 and flash the 2.3.5 FXZ and then do the OTA?
Let me know what you think as I'd like to make this happen as seamless as possible, don't need any surprises ya know?

This is covered in the noob thread, but...
Factory reset will not be good enough, since the OTA update actually looks for the bloatware to update.
Before you do anything, I recommend going into Atrix 2 Bootstrapper and creating a backup. You'll have to flash back to stock, update, then use the Motofail one click root in the noob thread. Then you can restore your data using the Bootstrapper.
I highly recommend the Supercharged V5_1 ROM and ICS theme, though.

Go ahead and take the jump, you won't be disappointed. Both the stock and V5 are very good

At first the deodexed 2.3.6 wasn't completely working because of a bad deodex, but lfaber06 got that all worked out.
If you want to update to stock 2.3.6 you will have to flash the 2.3.5 fxz first to get all your bloatware back.
Doing the OTA while rooted is fine, it will just remove your root and then you can just re-root.

Thanks guys...I have followed the steps outlined above (and in the referenced noob thread) and have successfully flashed the 2.3.5 fxz. Downloading the OTA as we speak.....Gonna get root back once that's installed then reinstall the CWM bootstrap and then restore from the backup I made at the beginning of this process and i'm good to go right?

916x10 said:
Thanks guys...I have followed the steps outlined above (and in the referenced noob thread) and have successfully flashed the 2.3.5 fxz. Downloading the OTA as we speak.....Gonna get root back once that's installed then reinstall the CWM bootstrap and then restore from the backup I made at the beginning of this process and i'm good to go right?
Click to expand...
Click to collapse
Restoring the CWM backup will restore you back to 2.3.5. However, CWM is awesome enough that it will let you restore only parts of the backup. Boot into CWM, got to backup and restore, then go to Advanced Restore. If you select "Restore data" you will get back your apps and settings but keep 2.3.6.

cogeary said:
Restoring the CWM backup will restore you back to 2.3.5. However, CWM is awesome enough that it will let you restore only parts of the backup. Boot into CWM, got to backup and restore, then go to Advanced Restore. If you select "Restore data" you will get back your apps and settings but keep 2.3.6.
Click to expand...
Click to collapse
Cool...restoring as we speak. Thanks for your help

916x10 said:
Cool...restoring as we speak. Thanks for your help
Click to expand...
Click to collapse
Glad to help!

You guys are the ****!
The flashing/update/rooting/restoring process went off without a hitch and my device is back to how I had it setup before I started it. This was my first time ever using the CWM Recovery bootstrap and RSDLite so I was a bit nervous but after using then I realize that CWM Recovery and RSDLite is just like xRecovery and FlashTool for my previous SE Xperia X10.

Well it gets even easier then using RSD lite. Get jydaddy's RAZR boot into CWM exploit and install it! Well worth it. With his exploit everytime you boot you boot into CWM.All you do is perform one extra step to reboot. Say you flash something and it goes wrong , instead of having to boot into fastboot and flash the fastboot files with RSD you simply pull the battery, let it boot into CWM and perform a simple restore. Your phone never gets hooked up to a single cord and saves sooo much time for!!!

JRW 28 said:
Well it gets even easier then using RSD lite. Get jydaddy's RAZR boot into CWM exploit and install it! Well worth it. With his exploit everytime you boot you boot into CWM.All you do is perform one extra step to reboot. Say you flash something and it goes wrong , instead of having to boot into fastboot and flash the fastboot files with RSD you simply pull the battery, let it boot into CWM and perform a simple restore. Your phone never gets hooked up to a single cord and saves sooo much time for!!!
Click to expand...
Click to collapse
+1 the exploit is great!

[Q] a little help

ive been rooted for a long time now, i have a Moto Attrix 2. recently i did the updated to the 2.3.6 but before i did, i went ahead and did the perminent root method. this helped me keep root. now i want to jump into Roms. i'm not new to this. i had a Droid X proir to the Attrix. so i kinda know my way around. sorta..aha, ive read the process of the rom i want to install on to my phone which is supercharge Rom

So do you have a question, I couldn't tell from your post

awe man, i'm sorry about that.
my question...actually the question is about the process needed to be taken. i read thru the steps to flash supercharge rom V5 but, i have no clue to where start from since i have not flash a rom on this device.? so i'm startin off from scretch i'm sorry about that, i shoulda proof read that..lol, before i posted.

Step 1)Install CW recovery from this link http://forum.xda-developers.com/showthread.php?t=1346977
Step 2) Run it and reboot into recovery
Step 3) MAKE A BACKUP! I repeat MAKE A BACKUP! this is important in case something goes wrong while flashing a new rom you can flash your backup and return your phone to normal.
Once you have learned to do that you can now start flashing roms. Just download the roms and follow the directions in the roms. ALL ROMS REQUIRE CW Recovery to install so you'll get used to it. I just wanted u to follow those 3 steps before you start flashing roms. People forget to make backups and they end up losing all their info.
Read the BEGINNERS GUIDE it has all the info you could ever need.

eL_MeXiCaNo said:
Step 1)Install CW recovery from this link http://forum.xda-developers.com/showthread.php?t=1346977
Step 2) Run it and reboot into recovery
Step 3) MAKE A BACKUP! I repeat MAKE A BACKUP! this is important in case something goes wrong while flashing a new rom you can flash your backup and return your phone to normal.
Once you have learned to do that you can now start flashing roms. Just download the roms and follow the directions in the roms. ALL ROMS REQUIRE CW Recovery to install so you'll get used to it. I just wanted u to follow those 3 steps before you start flashing roms. People forget to make backups and they end up losing all their info.
Read the BEGINNERS GUIDE it has all the info you could ever need.
Click to expand...
Click to collapse
thanks bro, i got that part down, ive been rollin around with a back up for weeks now ..
oh yea and the other thing, when i went and did the forever root before the OTA update, the one thing that didn't update was the baseband.

Droid_Boi86 said:
thanks bro, i got that part down, ive been rollin around with a back up for weeks now ..
oh yea and the other thing, when i went and did the forever root before the OTA update, the one thing that didn't update was the baseband.
Click to expand...
Click to collapse
Dont worry about ever doing the forever root there's a root method for 2.3.6
Before flashing any rom I suggest you flash the 2.3.5 FXZ and update to 2.3.6 and then root it. This way you start from a fresh base and don't have any random bugs that would take a long time to hunt down and fix due to coming from a non-stock rom.

Ask away. What questions do you have? I recommend installing CWM on Recovery zip (and download the remove script while your at it you might want that). Revoke root rights to Bootstrap after installing the on boot zip. It takes one cycled reboot for the script to take effect. Make sure it works before installing any ROMs. Read the Read Me file for supercharged before installing. That's a few tips from me. Oh, if you have a windows based PC install and know how to use RSD lite and the fxz file in case of a disaster. In other words incase you can't recover from some unforeseen event using your phone and CWM Recovery alone. Make sure your battery is fully charged before installing a new ROM. Off the top of my head those tips come to mind.
Sent from my MB865 using XDA

KEB64 said:
Ask away. What questions do you have? I recommend installing CWM on Recovery zip (and download the remove script while your at it you might want that). Revoke root rights to Bootstrap after installing the on boot zip. It takes one cycled reboot for the script to take effect. Make sure it works before installing any ROMs. Read the Read Me file for supercharged before installing. That's a few tips from me. Oh, if you have a windows based PC install and know how to use RSD lite and the fxz file in case of a disaster. In other words incase you can't recover from some unforeseen event using your phone and CWM Recovery alone. Make sure your battery is fully charged before installing a new ROM. Off the top of my head those tips come to mind.
Sent from my MB865 using XDA
Click to expand...
Click to collapse
whats the reason for denying bootstrap su? ive seen this before and im a 3year android user/flasher and ive yet to deny my bootstrap su after installing anything. so, just wondering why.

rob219 said:
whats the reason for denying bootstrap su? ive seen this before and im a 3year android user/flasher and ive yet to deny my bootstrap su after installing anything. so, just wondering why.
Click to expand...
Click to collapse
Because if you dont deny bootstrap SU after FLASHING CWM ON STARTUP zip then you will not get CWM everytime you boot up, it's a bug. So if you want CWM everytime you boot your phone you have to deny bootstrap SU. Other than that IDK the exact technical details on why it does this, it just does.

KEB64 said:
Ask away. What questions do you have? I recommend installing CWM on Recovery zip (and download the remove script while your at it you might want that). Revoke root rights to Bootstrap after installing the on boot zip. It takes one cycled reboot for the script to take effect. Make sure it works before installing any ROMs. Read the Read Me file for supercharged before installing. That's a few tips from me. Oh, if you have a windows based PC install and know how to use RSD lite and the fxz file in case of a disaster. In other words incase you can't recover from some unforeseen event using your phone and CWM Recovery alone. Make sure your battery is fully charged before installing a new ROM. Off the top of my head those tips come to mind.
Sent from my MB865 using XDA
Click to expand...
Click to collapse
thanks alot man, as far as the RSD lite goes i kno my way aroung that. so i should be good. but as for the first thing you suggested. about the CVM on Recovery Zip? i wanna learn how to do that, meaning install CVM properly. if you could explain or shot me a link to where i read up on it.

Droid_Boi86 said:
thanks alot man, as far as the RSD lite goes i kno my way aroung that. so i should be good. but as for the first thing you suggested. about the CVM on Recovery Zip? i wanna learn how to do that, meaning install CVM properly. if you could explain or shot me a link to where i read up on it.
Click to expand...
Click to collapse
Sorry KEB - not to step on your toes or anything, but...
Get and install the A2 Bootstrap from here.
You can now boot into "Recovery" mode through the Bootstrap app. You can test it first or you can just go and get the CWM on Boot zip files here. Download the two zip attachments in the first post to your sdcard.
Then open the A2 Bootstapper app - click the top button, then ok, then the 2nd button.. and viola! It will boot into recovery.
Then wipe your cache partition, and dalvik cache, and install zip from sdcard. "...Global..." zip makes it boot into recovery every time you reboot, and the "..Remove.." zip removes it.
Good luck. Happy reading!

alteredlikeness said:
Sorry KEB - not to step on your toes or anything, but...
Get the A2 Bootstrap from here.
Get ROM Manager from the Google Play Store.
Install both.
You can now boot into "Recovery" mode through the Bootstrap app. You can test it first or you can just go and get the CWM on Boot zip files here. Download the two zip attachments in the first post to your sdcard.
Then open the A2 Bootstapper app - click the top button, then ok, then the 2nd button.. and viola! It will boot into recovery.
Then wipe your cache partition, and dalvik cache, and install zip from sdcard. "...Global..." zip makes it boot into recovery every time you reboot, and the "..Remove.." zip removes it.
Good luck. Happy reading!
Click to expand...
Click to collapse
thanks for that good explaination on that. now i gotta figure out why my laptop isn't seeing my phone...=/

Droid_Boi86 said:
thanks for that good explaination on that. now i gotta figure out why my laptop isn't seeing my phone...=/
Click to expand...
Click to collapse
Make sure you have the drivers downloaded for the Atrix 2.

thethird84 said:
Make sure you have the drivers downloaded for the Atrix 2.
Click to expand...
Click to collapse
By "seeing your phone," do you mean ADB-wise? Settings -> Applications -> Development -> USB Debugging (enable)

PM me if you need any help. I have Supercharged V5 update 2 running and I love it. there are some things you need to do to make sure it works right though.

thanks alot! i will do..

HOLD ON THIS!!! How To Update TMOUS to 1.84 when Rooted!

HOLD ON UPDATING!!! There are a bunch of people having data and wifi issues with this release. I have not had them but that doesn't mean you won't. Update at your OWN risk. You've been warned.
If you would like to update the software but not the baseband (probable cause for data/wifi issues) then just use my Nandroid linked below and leave your current baseband.
To everyone that keeps trying to relock their phones and flash the RUU to get the update it will NOT work. If you look at your software version you will see that it has added and R2 in it. I don't know why it does this, maybe it's a why for HTC to screw over the hackers yet again. Here is how to get the update.
There are 2 ways to get the update.
First: Use my Stock Rooted 1.84 Nandroid that I posted here. Simple but you will have to flash the radio separate.
Second: More steps but worked for me. NOTE: Only works if your on stock rooted phone. Will not work on custom ROM. Get Stock 1.53 Nandroid here. Credit to Reviewers for posting.
This will NOT wipe your phone nor do you need to wipe your phone if you are on Stock Rooted.
1a - This step only needed if you are on a custom ROM. If your on Stock Rooted then proceed to step 1b.
Download the above linked Nandroid (for 1.53) and restore it in Recovery. Reboot.
1b - Download this tool and use it to flash stock recovery. It will auto reboot your phone into bootloader so just start with your phone normally booted.
Credit goes to hasoon2000 for creating the tool!
2 - Your phone will reboot, once booted back up go to Settings>About Phone>Software Update. It will find the update and download then prompt to install. Select yes and let your phone update and reboot.
3 - Fire up the tool from step 1b again and this time flash CWM Recovery (whichever you prefer).
4 - After reboot is complete reboot again back into recovery and flash this to restore SU permissions (seems the update breaks them, at least for me).
Credit goes to Chainfire for creating this!
5 - Reboot, Done.

Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?

DigitalMonk said:
Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?
Click to expand...
Click to collapse
Did you totally wipe your phone? If not then the update is in your " download" folder
Sent from my HTC One S

Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?

DigitalMonk said:
Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Try deleting that file and checking again. Back it up to your computer first of course.

setzer715 said:
Try deleting that file and checking again. Back it up to your computer first of course.
Click to expand...
Click to collapse
Didn't work for me. I got about 2 downloads out of the servers, and then they aren't sending it anymore. Weak.

No go so far. Copied it to my PC, deleted it from my Download folder, re-booted and then checked for an update 3 different times and nothing so far.

With all of the people having wifi and data issues TMO may have stopped sending it until they figure out what is going on. I do know for a fact that TMO tests any software update the send so something may have gone haywire with it. Maybe got radio mixed up.

DigitalMonk said:
I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Wait.. I didn't know this. You mean even if we "unroot" and flash stock recovery (and using stock ROM of course), we cannot flash this ourselves?
I currently have the CWM touch recovery and root, u/l bootloader, etc., and TMO has sent me 2 updates, both were in the Downloads folder. I didn't notice that it updated (as I never confirmed) but they obviously didn't install.
But I would have done the above if I had known we couldn't just flash it ourselves. WTF T-mobile?? Those of us who know how to flash a file should at least not be prevented from doing so (especially since we need to have the original recovery installed).
Sent from my HTC One-S (rooted), stock ROM

[Q] Odin can't flash stock, boot hangs at logo

Good morning...
Right now, my phone (Galaxy S III on Verizon) will not boot past the "Galaxy S III" logo. Odin will not flash a stock Jelly Bean ROM from StockRoms.net. It gets stuck on the first .img, boot.img. I am downloading a new stock ROM right now and will try a full wipe.
Being silly and ambitious, I do not have a nandroid before it wouldn't boot. On Monday (two days ago) I rooted it. I flashed the VRALEC boot chain, rebooted, flashed ClockworkMod recovery, and installed the SuperSU bootloader and root patch through recovery. I rebooted, allowing CWM to disable the automatic re-flashing of the recovery. With my newly rooted phone, I jumped at trying to install Google Wallet. I went with the route of using Wallet Installer as found on the app store. And, being silly, I checked all three OS options (JB, ICS, and one other). After authorizing the superuser request, my phone almost immediately shut off. I think I made a nandroid through CWM after that, but not one that would run.
I thought it was going to be just build.prop having issues, so I went on a wild quest trying to find a working one online and get it on the device. I worked it into the updater script of my SuperSU patch. Nonetheless, nothing there fixed it. I've tried a bunch of things, including (get this) extracting the stock system.img.ext4 image, mounting it, tarring the device, creating an MD5 for it, and wrapping it up like a nandroid to "restore" with CWM.
I'm thinking I'm going to try and wipe the entire device, maybe leave /recovery, and flash a new I-535 ROM with Odin, see if that works. I don't know if it will. Any advice?
My flash counter is at about 5 after many attempts to get back to something that will boot, so warranty is not an option. Not that they've ever been a whole lot of help anyways.

Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Sent from my SCH-I535 using Tapatalk 2

What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Sent from my SCH-I535 using xda app-developers app

joaquinla1 said:
What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Click to expand...
Click to collapse
My phone has CWM recovery on it, but I don't see any reason CWM's factory reset and cache wipe would be any different. I'll give it a shot.
mentose457 said:
Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Click to expand...
Click to collapse
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Thanks for all your help. The ROM I'm going to try and flash now is the official stock from stockroms.net. I can't post the link as I'm new but it's I535BLK_nowipe.zip. I'll keep this updated.

sworld said:
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Click to expand...
Click to collapse
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Sent from my SCH-I535 using Tapatalk 2

mentose457 said:
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Click to expand...
Click to collapse
That makes more sense.
UPDATE: I "factory reset" the data partition and formatted /system and /cache through ClockworkMod. Turned it off, flashed VRALEC through Odin, rebooted, flashed the stock ROM, and then CWM. I'm restoring my nandroid of /data right now, and I'm awaiting an OTA firmware update to bring it up to the latest VZW JB. Then I'll root.. finally.

The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree

z06mike said:
The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree
Click to expand...
Click to collapse
Really? I've only odined once on the s3 and didn't have to wipe. On the fascinate and an older version of Odin after the flash before it booted it would automatically wipe.
Sent from my SCH-I535 using Tapatalk 2

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

So, the phone is functioning now. Of course, I am running a slightly older version and once I connect to a solid Wi-Fi network I'll request the newest update again.
However, I did already try to download the software update from Verizon, and it seemed to work fine. It rebooted into recovery and CWM seemed to handle it okay, although it claimed the signature was bad. It installed though, rebooted, and updated some app databases. And then, it said the update failed with "Code 401."
Right now I'm not too worried. Hopefully I can apply the update properly soon. It is worth noting that simply using CWM "advanced restore" on only the /data partition, without exactly matching the ROM build, has seemed to leave it hanging at the "4G LTE" logo.
Thanks for all of your help!

The phone will not install a Verizon update with a custom recovery installed.