I updated to MF1, and it changed my recovery from ClockWork Touch to a much more basic recovery mode (rom manager says CWR and TWRP are both installed). I tried to flash basic clockwork using rom manager and as it reboot I got a message saying "software not authorized" and it would not boot.
I just used ODIN to flash the VRALEC boot chain which allowed the phone to boot. I still seem to have still have MF1. Step 6 here http://forum.xda-developers.com/showthread.php?t=2046439 says to then install the correct boot chain, but i dont see one for MF1 yet.
I then tried ODIN to flash CWR from the the above post with the same results (had to re odin vralec).
1. Should I ODIN the VRBMD3 boot chain in the mean time?
2. How do I get ClockWork Recover for MF1, touch or regular?
blindguyinanorgy said:
I updated to MF1, and it changed my recovery from ClockWork Touch to a much more basic recovery mode (rom manager says CWR and TWRP are both installed). I tried to flash basic clockwork using rom manager and as it reboot I got a message saying "software not authorized" and it would not boot.
I just used ODIN to flash the VRALEC boot chain which allowed the phone to boot. I still seem to have still have MF1. Step 6 here http://forum.xda-developers.com/showthread.php?t=2046439 says to then install the correct boot chain, but i dont see one for MF1 yet.
I then tried ODIN to flash CWR from the the above post with the same results (had to re odin vralec).
1. Should I ODIN the VRBMD3 boot chain in the mean time?
2. How do I get ClockWork Recover for MF1, touch or regular?
Click to expand...
Click to collapse
1. No, you don't have to change the bootchain. Vralec is just an old ics bootchain and should run fine.
2. http://forum.xda-developers.com/showthread.php?t=2096735
Use ez recovery to flash the most recent CWM recovery, touch or non-touch should both work great. Don't use rom manager anymore until it's updated, that's the second report I've seen of it doing that.
Sent from my SCH-I535 using Tapatalk 2
Did you ota to mf1 by any chance? Im pretty sure your boot loader was relocked.
Sent from my SCH-I535 using xda premium
Watoy said:
Did you ota to mf1 by any chance? Im pretty sure your boot loader was relocked.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I did OTA. I can still get into recovery, it is just not CWR.
BadUsername said:
1. No, you don't have to change the bootchain. Vralec is just an old ics bootchain and should run fine.
2. http://forum.xda-developers.com/showthread.php?t=2096735
Use ez recovery to flash the most recent CWM recovery, touch or non-touch should both work great. Don't use rom manager anymore until it's updated, that's the second report I've seen of it doing that.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
EZ-Recovery worked, but i also think i did something different inside CWR. It asked me if I wanted to disable something and this time I said yes.
blindguyinanorgy said:
EZ-Recovery worked, but i also think i did something different inside CWR. It asked me if I wanted to disable something and this time I said yes.
Click to expand...
Click to collapse
Good, if you say no it'll reinstall the stock recovery and you don't want that. The recovery you were seeing is the stock recovery, very basic with the hardly any options.
Sent from my SCH-I535 using Tapatalk 2
Related
So i downloaded rom manager from the market. I went to flash clockworkmod recovery to the phone and selected verizon galaxy s3. It progressed a certain amount then stopped responding. I'm a bit hesitant to reboot my phone but should this have worked?
I'm rooted and unlocked bootloader.
SerialTurd said:
So i downloaded rom manager from the market. I went to flash clockworkmod recovery to the phone and selected verizon galaxy s3. It progressed a certain amount then stopped responding. I'm a bit hesitant to reboot my phone but should this have worked?
I'm rooted and unlocked bootloader.
Click to expand...
Click to collapse
Try reflashing or ditch Rom Manager and use EZ-Recovery to flash CWM 6.0.1.0.
PJnc284 said:
Try reflashing or ditch Rom Manager and use EZ-Recovery to flash CWM 6.0.1.0.
Click to expand...
Click to collapse
I did it a second time and it asked for SU. Seemed to go through. I'm going to reboot and see if it works.
Do not use ROM manager, just use EZ Recovery from the market.
Is there something wrong with ROM manager?
Sent from my SCH-I535 using xda app-developers app
mysterysauce said:
Is there something wrong with ROM manager?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well apparently it bricked the OP's phone.
Sent from my SCH-I535 using xda app-developers app
Taehee. said:
Well apparently it bricked the OP's phone.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
It didn't brick his phone, for some reason the first time you flash cwm from rom manager, it hangs when it's about to ask for SU permissions, it force closes. Second time it will go through, doesn't brick your phone or anything of that nature.
Sent from my SCH-I535 using xda premium
PJnc284 said:
Try reflashing or ditch Rom Manager and use EZ-Recovery to flash CWM 6.0.1.0.
Click to expand...
Click to collapse
I don't believe you can hard brick a phone from a recovery. You can always flash the stock recovery.img and be fine. I used ez recovery and chose custom and selected CMW 6 flashed, said ok, rebooted and the phone automatically went into download mode and would not boot up. All i did was flash the recovery.img i pulled from cmw non touch and flashed recovery and all was good.
kpkimmel said:
I don't believe you can hard brick a phone from a recovery. You can always flash the stock recovery.img and be fine. I used ez recovery and chose custom and selected CMW 6 flashed, said ok, rebooted and the phone automatically went into download mode and would not boot up. All i did was flash the recovery.img i pulled from cmw non touch and flashed recovery and all was good.
Click to expand...
Click to collapse
well cwm bricked my phone. phone turns on says samsung and goes black. also when i plug the charger in it vibrates intermitently.
Install CWM Touch here http://forum.xda-developers.com/showthread.php?t=1719744
Long time Galaxy Nexus user and I just received my S3 yesterday in the mail!
Of course I couldn't wait to root and unlock it using the very helpful thread RootDebug, EZ-Unlock11 and EZ-Recovery2.2. Via Odin I then flashed the latest CWM 6.0.1.2. At that point I attempted to flash via CWM the Unofficial CM10 JB Rom (http://forum.xda-developers.com/showthread.php?t=1788443). Everything seemed to go just fine but it hung at boot up for 20 minutes. In my haste to play I did not clear the cache which could have been the reason. At that point I pulled the battery and rebooted only to get the infamous message to take my phone to a VZW dealer. After countless trouble free flashes I suppose it was bound to happen at some point.
So via the recovery thread I loaded VRALEC, VRALF, and stock.vwx.root66.tar from the SoftBrick thread to get back up and running. Now however I cannot reflash CWM via Odin. It always fails and on my phone it says "secure check fail : recovery".
I rebooted the phone, computer, and otherwise havent changed anything.
Suggestions to get CWM back on my phone?
Thanks!
J
I did not see that you unlocked the bootloader.
Assuming you performed the Soft Brick guide successfully, what happens when you boot into the rom and download EZ Recovery and flash CWM? You mention flashing CWM only through Odin in your post.
bigmook said:
I did not see that you unlocked the bootloader.
Click to expand...
Click to collapse
Sorry, Bootloader was/is unlocked on this phone
SlimSnoopOS said:
What happens when you boot into the rom and download EZ Recovery and flash CWM?
Click to expand...
Click to collapse
I can boot into CWM 6.0.1.0 via the EZ recovery app
I did get a message i've never seen before upon exit of CWM. "ROM may flash stock recovery on boot. Fix?" I selected Yes - Disable recovery flash
Thanks again for your input!
follow my guide...link in sig!
That message only has bearing if your running the stock rom. Custom rom's will not flash original recovery. Choosing yes or no only matters on stock, will not make any changes on a custom rom
Sent from my SCH-I535 using xda premium
you can always try to flash the new cwm thru ez recovery. Just take the recovery zip and save it to your SD card then go to ex recovery and select custom then select your path to the zip you put on your SD card and flash then reboot and it should have flashed the new cwm without even using Odin. Also make sure you have ez unlock installed and unlocked just to make sure the boot loader is unlocked. Better to be safe than sorry.
Sent from my SCH-I535 using xda app-developers app
So after 2 days of trying via Odin, I give up. Anybody here got a copy of Stock Recovery 3e? One that can be flashable via Odin?? I tried installing hyperdrive, and it installed via aroma but when I rebooted I got a Verizon Unauthorized rom warning. I really, really thought I had an unlocked bootloader after ez unlock. I don't have stock recovery nor cwm touch anymore (the one I replaced 3e with).
Since Odin just wouldn't work (tried all versions) and just fails after a few minutes, I figured maybe I could get away with flashing a recovery 3e, then wiping and reflashing a flashable stock rom from there. Any help will be appreciated.
Your best option is to figure out how to get Odin to flash stock. That will fix your recovery. Do you have the proper drivers installed? Does Windows detect it in device manager? Does Odin see it?
Sent from my SCH-I535 using Tapatalk
This solved my soft brick, I hope it solves yours too!
ojpd said:
So after 2 days of trying via Odin, I give up. Anybody here got a copy of Stock Recovery 3e? One that can be flashable via Odin?? I tried installing hyperdrive, and it installed via aroma but when I rebooted I got a Verizon Unauthorized rom warning. I really, really thought I had an unlocked bootloader after ez unlock. I don't have stock recovery nor cwm touch anymore (the one I replaced 3e with).
Since Odin just wouldn't work (tried all versions) and just fails after a few minutes, I figured maybe I could get away with flashing a recovery 3e, then wiping and reflashing a flashable stock rom from there. Any help will be appreciated.
Click to expand...
Click to collapse
Thank you! Finally out of soft brick.
Sent from my SCH-I535 using xda app-developers app
Hi guys,
3 days ago I had root but softbricked by installing hyperdrive when "I thought" I unlocked via ez-unlock but I guess that didn't take. Tried to restore back to stock but couldn't, I lost access to CWM and Odin nor Heimdall (Mac, Linux and Windows) didn't like my phone in 3 computers using 3 different cables.
But from continuous failed/incomplete/partial flashes, CWM is miraculously back! So that's like my only glimmer of hope right now. So my question is could I get back to stock or any rom from flashing something from CWM? Could I get ANY kind of ROM running again, could I root again, unlock bootloader and install new rom via CWM.. Basically can I fix my phone from CWM? Or is the only way back to any rom is via stock via Odin/Heimdall?
PLEASE HELP.
ojpd said:
Hi guys,
3 days ago I had root but softbricked by installing hyperdrive when "I thought" I unlocked via ez-unlock but I guess that didn't take. Tried to restore back to stock but couldn't, I lost access to CWM and Odin nor Heimdall (Mac, Linux and Windows) didn't like my phone in 3 computers using 3 different cables.
But from continuous failed/incomplete/partial flashes, CWM is miraculously back! So that's like my only glimmer of hope right now. So my question is could I get back to stock or any rom from flashing something from CWM? Could I get ANY kind of ROM running again, could I root again, unlock bootloader and install new rom via CWM.. Basically can I fix my phone from CWM? Or is the only way back to any rom is via stock via Odin/Heimdall?
PLEASE HELP.
Click to expand...
Click to collapse
So confusing....
Ok, so you're on a stock rom right now and you have cwm installed? You must have some type of root enabled, do you have supersu or superuser installed? If you don't you need to install one from the playstore.
If you have cwm, then all you need to do is use ez unlock to unlock your bootloader then you can flash away. Use version 1.2, you likely used 1.4 which doesn't always work.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
So confusing....
Ok, so you're on a stock rom right now and you have cwm installed? You must have some type of root enabled, do you have supersu or superuser installed? If you don't you need to install one from the playstore.
If you have cwm, then all you need to do is use ez unlock to unlock your bootloader then you can flash away. Use version 1.2, you likely used 1.4 which doesn't always work.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'm really sorry about the confusion.
I came from a stock rooted, "unlocked" rom, it had CWM touch installed. Then I tried to install Hyperdrive.. Install went well via aroma.. But after reboot I got the verizon unauthorized error and I lost access to CWM Touch but I could go into download mode... Now here's where the confusion starts...
I tried to flash back to stock via Odin. Each and every single time it failed after a few files. Believe me I looked for a solution as in several solutions all of which failed until my last flash which also failed but installed a few more files before it failed and I dunno I got CWM Touch back.
Hence the reason why I'm asking if I could fix my phone via CWM because Odin is crazy and Heimdall is also picky.
ojpd said:
I'm really sorry about the confusion.
I came from a stock rooted, "unlocked" rom, it had CWM touch installed. Then I tried to install Hyperdrive.. Install went well via aroma.. But after reboot I got the verizon unauthorized error and I lost access to CWM Touch but I could go into download mode... Now here's where the confusion starts...
I tried to flash back to stock via Odin. Each and every single time it failed after a few files. Believe me I looked for a solution as in several solutions all of which failed until my last flash which also failed but installed a few more files before it failed and I dunno I got CWM Touch back.
Hence the reason why I'm asking if I could fix my phone via CWM because Odin is crazy and Heimdall is also picky.
Click to expand...
Click to collapse
So you can get into download mode just fine? You need to use a better USB cable and try a different port on your computer. It should be able to flash, but if you're using a lower quality cable than what came with the phone it might be your issue.
This guide should work if you can't get a normal flash back to stock work:
http://forum.xda-developers.com/showthread.php?t=1840030
Basically, the only other way I know of to go back to stock without a pc is to use mobile Odin, but that needs root access. There's no file you can flash in recovery to go completely back to stock as it will still leave you with a custom recovery installed.
Sent from my SCH-I535 using Tapatalk 2
I finally got into my rom, after flashing the first boot chain (vralec) Odin messed up again, couldn't flash the 2nd one nor root66 so I pulled my batt and I guess the first vralec gave me stock recovery n just let me boot into my rom, installed twrp and ez unlock 1.2 from there, rebooted into twrp and then installed TkROM.
Thanks for all the help.
Sent from my SCH-I535 using xda app-developers app
Glad it worked out, and nice rom choice.
Sent from my SCH-I535 using Tapatalk 2
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Xx
BadUsername said:
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Smogon said:
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Click to expand...
Click to collapse
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Then check and see if you're getting a similar error message.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Click to expand...
Click to collapse
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Smogon said:
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Click to expand...
Click to collapse
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll try the second option, Thanks!
BadUsername said:
OK.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I tried CWM and the stock recovery through EZ, both gave the same error as TWRP, unable to mount /
I'm really confused as to whats wrong. At this point I don't care if I get stuck with the OTA 4.3, but I don't want to try to update it with the recovery still not reading either my SD cards.
Any Ideas?
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Smogon said:
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Click to expand...
Click to collapse
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
xevildoerxx said:
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
Click to expand...
Click to collapse
No I just used the causal tool.
dpeeps74 said:
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm pretty sure, has all the verizon bloat and logos, also I'm pretty sure the causal applet bricks the international ones. I don't remember the version of twrp that the causal script flashed, but I tried that one, the most recent one, and 2.5 i think from EZ recovery. The stock recovery from EZ has the same issue now though which is what really confuses me. at the moment I have root dissabled and the bootloader is locked and its back with the stock recovery, it still says custom when i reboot the phone though.