Only booting into odin mode... borked recovery - Verizon Samsung Galaxy S III

Ok, here's what I did.
I have had my s3 rooted and running custom ROM's. I stupidly and accidently flashed google wallet as my recovery using ezrecovery. Now the phone only boots into odin mode. Is there a way to get recovery back onto the device so I don't have to wipe it and start over (possibly losing everything on my internal SD card)?
Thanks in advance.
Silly Noob.

I don't think you'll be able to get recovery back. You'll probably need to flash stock with Odin.
Sent from my SCH-I535 using xda app-developers app

I ended up with the same result after flashing a custom recovery incompatible with Imo's Lean Kernel/Kexec.
I used ODIN to flash the Root_66 ROM, and all of my internal SD contents remained intact. After the clean install, I flashed CWM 6.0.1 through EZ-Recovery and successfully restored a backup.
The only thing that didn't restore was the kernel.

Awesome. Lesson learned. Think twice before clicking! Odin'd to route 66 and now have recovery of my back up. Thanks guys!

Actually, I in case anyone does something similar the phone booted rooted just how I left it minus the custom rom. I re flashed the rom and I am back where I was without even having to flash a recovery. Thanks again!
Sent from my SCH-I535 using Tapatalk 2

Related

[Q] Cwm on ics Skyrocket

For the life of me i cannot boot into CWM.
I used odin and flashed the ICS leak.
I then booted up and it worked fine.
I used odin to flash the CWM. It says completed.
I rebooted and phone works fine.
then tried to boot into recovery.
all i get is the manual mode. i have tried everything i can think of but still have had no luck. any suggestions?
Have you installed Clockwork and tried to reboot to recovery from that
Sent from my SAMSUNG-SGH-I727 using XDA
How are you booting into cwm? Have you tried from rom manager? Are you on rogers or att.
Sent from my SAMSUNG-SGH-I727 using XDA
cwm on ics skyrocket
I have installed clockworkmod and i am on [email protected] i have rom manager installed. but can't boot to cwm through do to no root. that was why i was trying to boot into cwm recovery. i never figured out why it wouldn't boot into recovery. but it eventually did, even though i changed nothing on my part. after that rooting was simple just had to flash the superuser zip a couple times. thanks for the responses though.

Stuck on bootloop from Clockworkmod 5.8.4.9

PLEASE HELP!! I have successfully rooted the device and was doing ok after flashing CWmod recovery 6.0.1 through E-Z recovery app and running Liquid Rom. I managed to be dumb enough to flash CWMod version 5.8.4.9 through Rom manager and when I rebooted my phone it got stuck in boot loop. I am able to get into CWMod 5.8.4.9 but I cannot restore my backup anymore. I can also data wipe and install a new rom, but it all just keeps going into bootloop and I cannot get past the samsung custom unlock screen. It first flashed that, then the android man pops up on the next screen like its loading something and then just keeps looping through the process. I did not use ODIN for any of this process and I dont know how to get myself back tothe point where I can reboot. Any help would be tremendously appreciated, because I'm dead stuck and in a panic. Thanks in advance for any assistance.
Happend to me last night...
I made the same mistake... DO NOT download any recoveries from ROM manager. I found out the hard way... So the problem now is your phone is stuck using the recovery you downloaded. I am not sure of a quick way using that recovery if you can revert back but... My solution got me where I needed to be in order to get going again.
I had to use Odin to root to stock ROM. Yes when you wipe it will destroy your data but not your pictures, downloaded files, and other files you put on there. When I re-rooted with stock all my stuff for CM10, gapps, and the kexec CWM was there.
So use this guide...
http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Section 1!!!!! And follow the steps EXACTLY the way it says to.
This is why i have never liked rom manager...
The best solution for us to flash recoveries is ez recovery free from the market. I would use this going forward once you Odin back to stock
Sent from my SCH-I535 using xda premium
Same **** happened to me.
Odin. I lost my pics and internal memory though...
Sent from my SCH-I535 using Tapatalk 2

[Q] Blank screen after Nandroid Restore

I have Verizons S3. I recently rooted and unlocked the bootloader and have TWRP recovery. I was on 4.1 JB. I made a Nandroid Backup of System and Data. I then flashed the CM10.1 Monthly ROM, and all seemed to be working fine. However, I was having some issues with my app backups and the weird "emulated" directory structure. So I decided to go back to my Nandroid Backup and start over.
I went into TWRP, did a factory reset, cleared System Data, cache/dvalick cache, then I restored the Nandroid Backup (system and data). TWRP said it was successful and asked to reboot. When I did, the Samsung logo flashes, and then the screen stays black. I tried going back into recovery, but it won't let me. I can get to download though.
I think I'm going to have to use Odin to reflash a ROM as I can't get into recovery, right? But I'm also trying to understand what I did wrong. Did I forget a step? Did it have something to do with differences between 4.1 and 4.2? I'm new to this, and have searched the forums but can't find anything that answers my questions specifically. I appreciate the help.
anacree said:
I have Verizons S3. I recently rooted and unlocked the bootloader and have TWRP recovery. I was on 4.1 JB. I made a Nandroid Backup of System and Data. I then flashed the CM10.1 Monthly ROM, and all seemed to be working fine. However, I was having some issues with my app backups and the weird "emulated" directory structure. So I decided to go back to my Nandroid Backup and start over.
I went into TWRP, did a factory reset, cleared System Data, cache/dvalick cache, then I restored the Nandroid Backup (system and data). TWRP said it was successful and asked to reboot. When I did, the Samsung logo flashes, and then the screen stays black. I tried going back into recovery, but it won't let me. I can get to download though.
I think I'm going to have to use Odin to reflash a ROM as I can't get into recovery, right? But I'm also trying to understand what I did wrong. Did I forget a step? Did it have something to do with differences between 4.1 and 4.2? I'm new to this, and have searched the forums but can't find anything that answers my questions specifically. I appreciate the help.
Click to expand...
Click to collapse
You're supposed to backup "boot.img" as well. I'm pretty sure boot.img is the kernel which you failed to backup. The phone won't boot into your nandroid because the kernel wasn't restored as well. In TWRP: system, data, and boot are all supposed to be backed up simultaneously if you want to restore the entire nandroid. Odin flash and make sure to do a proper nandroid with all three that I listed.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
You're supposed to backup "boot.img" as well. I'm pretty sure boot.img is the kernel which you failed to backup. The phone won't boot into your nandroid because the kernel wasn't restored as well. In TWRP: system, data, and boot are all supposed to be backed up simultaneously if you want to restore the entire nandroid. Odin flash and make sure to do a proper nandroid with all three that I listed.
Click to expand...
Click to collapse
Ah, perhaps that "boot" checkbox wasn't check. =P So basically the CM10.1 boot.img is still there, but now the wrong ROM is there so it won't boot? Can I just flash the boot.img with Odin now, or will I need to do a full ROM flash?
anacree said:
Ah, perhaps that "boot" checkbox wasn't check. =P So basically the CM10.1 boot.img is still there, but now the wrong ROM is there so it won't boot? Can I just flash the boot.img with Odin now, or will I need to do a full ROM flash?
Click to expand...
Click to collapse
Flash nandroid and then try to flash a kernel. Might work Idk. Worth a shot.
sent telepathically
---------- Post added at 07:14 PM ---------- Previous post was at 07:13 PM ----------
jdub251 said:
Flash nandroid and then try to flash a kernel. Might work Idk. Worth a shot.
sent telepathically
Click to expand...
Click to collapse
Edit. Are you still not able to get into recovery? Sorry missed that in your post.
sent telepathically
jdub251 said:
Are you still not able to get into recovery? Sorry missed that in your post.
Click to expand...
Click to collapse
No, when I do the button combo for recovery, the word "Samsung" flashes, then "Galaxy S3" logo, but after that nothing...just blank screen. I was on stock Verizon s3 before this, so I guess I need to put that kernel back on the phone? Is the kernel the same as the bootloader? Can I use the unlocked bootloader referenced in this post: http://forum.xda-developers.com/showthread.php?t=1974114?
So, I tried using Odin to flash back the stock JB 4.1.1 kernel, which should have matched my Nandroid backup, but then I got an unlocked padlock on my splash screen and then the yellow triangle. blah. so i flashed a stock no wipe rom and that got me back into touchwiz, but I cant get into recovery no matter what i do. And I still have the padlock. I think I may need to do a stock full wipe rom?
anacree said:
So, I tried using Odin to flash back the stock JB 4.1.1 kernel, which should have matched my Nandroid backup, but then I got an unlocked padlock on my splash screen and then the yellow triangle. blah. so i flashed a stock no wipe rom and that got me back into touchwiz, but I cant get into recovery no matter what i do. And I still have the padlock. I think I may need to do a stock full wipe rom?
Click to expand...
Click to collapse
If you flashed a fully stock rom then you need to root, unlock, and install your custom recovery again.
Sent from my SCH-I535 using xda app-developers app
Ok, so I finally got time to try this again after flashing back to (what I thought) was stock Jelly Bean 4.1. I was following the directions here in this thread: http://forum.xda-developers.com/showthread.php?t=2046439
I get the VRALEC bootchain fine, phone reboots and all seems well. I got to flash TWRP 2.4, do a batter pull, and when I try to boot into recovery mode suddenly there is the Samsung splash screen with an unlocked padlock on it. Then the screen goes black and doesn't go into recovery. When I release the buttons, the phone then boots into the OS. I can still get to the download mode, but for some reason I can't get into a custom recovery. Any help on this? Please?
I used this file to wipe my phone back to stock JB: COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship.tar.md5
Thanks for the assistance. =)
Redo step three like the directions state.
Edit : In that thread, some folks even suggest waiting 5-10 mins after its successfully flashed before booting into recovery.
Sent from my SCH-I535 using xda app-developers app
Forgot to followup here, but I got it working. I left my phone plugged in after flashing the recovery for like 15 minutes. I also released the power button on trying to boot into recovery once the Samsung logo appeared. I finally got into recovery and was so happy. Thanks for the help!
Running mastamoon's unofficial CM 10.1. =)
anacree said:
Running mastamoon's unofficial CM 10.1. =)
Click to expand...
Click to collapse
Perfect! Glad you've got it all working properly!
Sent from my SCH-I535 using xda app-developers app

Soft-bricked - Looking for Odin Flashable Stock Recovery 3e

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

help - cant even boot into recovery anymore

My backup phone is an S5 and I was messing around with roms. I had been flashing roms for a while using twrp no problem. I forget what I selected, maybe factory data reset or some other option to do I wipe. But now everything is gone. I cannot even get into a recovery program anymore.
Pulled battery and booted up, it will say recovery loading and then you see the spinning android robot but then it gets stuck. I tried loading the ROMs onto the SD card. That is of no use since I cant even get into the recovery. What the heck did I do?
Odin back to Stock.
Sent from my SM-G900P using Tapatalk
csmasn said:
Odin back to Stock.
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
agreed, you probably borked the recovery somehow. Odin either the stock OS back and itll put stock recovery back, or just Odin twrp in it again. Be careful going past OK4 if youre gonna Odin the stock setup back on it as rooting after OK4 and ROM compatibility based on baseband can be a PITA

Categories

Resources