Related
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
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
My phone has been soft bricked after trying to flash the latest dkp kernel. I was using philz touch recovery and I tried to flash dkp kernel 3-20 build, and I got an error during flashing saying that it couldn't decompress the ramdisk. So I tried to flash the older version of dkp that I was using, and it failed to flash! I have never had problems like this before. So now my phone will not boot to system or go back to recovery. I can only access download mode. I was using CM11 with the ML1 modem and dkp kernel before my phone got bricked. It really frustrates me that my phone just randomly decided to freak out and brick itself, because I've been doing the same thing forever and never had any problems flashing a kernel. Please tell me how I can fix my phone. Thank you.
jonny30bass said:
My phone has been soft bricked after trying to flash the latest dkp kernel. I was using philz touch recovery and I tried to flash dkp kernel 3-20 build, and I got an error during flashing saying that it couldn't decompress the ramdisk. So I tried to flash the older version of dkp that I was using, and it failed to flash! I have never had problems like this before. So now my phone will not boot to system or go back to recovery. I can only access download mode. I was using CM11 with the ML1 modem and dkp kernel before my phone got bricked. It really frustrates me that my phone just randomly decided to freak out and brick itself, because I've been doing the same thing forever and never had any problems flashing a kernel. Please tell me how I can fix my phone. Thank you.
Click to expand...
Click to collapse
This how i did back to stock.
http://forum.xda-developers.com/showthread.php?t=1867253
Will help u on soft brick.
Odin enter download mode flash stock image. After that's all done. Dnt let ur fone install the ota. And root using CASUAL root and ur back to business
Sent from my SCH-I535 using Tapatalk
twistedillutions said:
This how i did back to stock.
http://forum.xda-developers.com/showthread.php?t=1867253
Will help u on soft brick.
Odin enter download mode flash stock image. After that's all done. Dnt let ur fone install the ota. And root using CASUAL root and ur back to business
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I did an ODIN back to stock MF1. In ODIN it says "Pass!" above the com port, and it also says <OSM> All threads completed. (succeed 1 / failed 0). However, my phone has been stuck on the 4G LTE screen with the colorful rings for around 15 minutes and it doesn't seem to be doing anything. What should I do?
Pull battery out and reboot.. Thats mentioned on instructions.
Post wat odin tells u
Sent from my SCH-I535 using Tapatalk
twistedillutions said:
Pull battery out and reboot.. Thats mentioned on instructions.
Post wat odin tells u
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Well when I pulled the battery and tried to reboot a samsung logo with an unlocked symbol was underneath it and it still gets stuck on the 4g LTE screen. Also, it won't allow me to enter the recovery.
So I went back to download mode on my screen and i noticed that it still says "System Status: Custom"
jonny30bass said:
Well when I pulled the battery and tried to reboot a samsung logo with an unlocked symbol was underneath it and it still gets stuck on the 4g LTE screen. Also, it won't allow me to enter the recovery.
Click to expand...
Click to collapse
Boot into recovery, factory reset, then reboot.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Boot into recovery, factory reset, then reboot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Like I said, it won't go into recovery mode. It seems like it is going to and then it just has a black screen.
BadUsername said:
Boot into recovery, factory reset, then reboot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
You have to be able to boot into recovery, make sure you hold the volume up + home for an extended period of time.
If you can't, you need to Odin the stock rom and try again.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
You have to be able to boot into recovery, make sure you hold the volume up + home for an extended period of time.
If you can't, you need to Odin the stock rom and try again.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The ODIN to stock did not work correctly. Maybe I need a different MF1 tar file. Can someone point me to a link for it? I have searched an can't find a completely stock MF1 file.
jonny30bass said:
The ODIN to stock did not work correctly. Maybe I need a different MF1 tar file. Can someone point me to a link for it? I have searched an can't find a completely stock MF1 file.
Click to expand...
Click to collapse
http://www.androidfilehost.com/?fid=23134718111254196
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
http://www.androidfilehost.com/?fid=23134718111254196
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
That's the exact one that I just used. It didn't seem to restore to stock with that.
jonny30bass said:
That's the exact one that I just used. It didn't seem to restore to stock with that.
Click to expand...
Click to collapse
Don't know what else to tell you, it's a completely stock file.
Recovery, system, kernel, and bootloader.
If you can't boot into recovery it must've not flashed perfectly or something else is wrong, like your hardware.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Don't know what else to tell you, it's a completely stock file.
Recovery, system, kernel, and bootloader.
If you can't boot into recovery it must've not flashed perfectly or something else is wrong, like your hardware.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I highly doubt that it is a hardware issue. I just tried to ODIN again and I'm in the same situation. One thing that I have noticed is that it tries to reinstall the MTP driver after using ODIN and it fails to install.
EDIT: Nevermind. I was able to enter recovery this time. I just did a factory reset. Hopefully it boots now. I will report back with results.
UPDATE: Ok. Everything seems fine now. Used casual to root and unlock bootloader again. Then installed PhilZ Touch Recovery. Now I am making a backup, and I am going to flash a Kit Kat Rom.
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.
I was running Jellybeans 4.1.2 did a factory reset, flashed this 4.3 ML modem, rebooted into the recovery and flashed the Alliance zip. When I I try to start the phone it gets stuck loading the samsung screen and rebooting, I can still boot into recovery by holding the power, home, and volume up and already tried to reflash but I'm still having the same issue.
Should I try an older build or different setting when I set up the rom. The whole set up process works and it seems to install just fine until I try to actually boot the phone.
notaneggspert said:
I was running Jellybeans 4.1.2 did a factory reset, flashed this 4.3 ML modem, rebooted into the recovery and flashed the Alliance zip. When I I try to start the phone it gets stuck loading the samsung screen and rebooting, I can still boot into recovery by holding the power, home, and volume up and already tried to reflash but I'm still having the same issue.
Should I try an older build or different setting when I set up the rom. The whole set up process works and it seems to install just fine until I try to actually boot the phone.
Click to expand...
Click to collapse
Try wiping data and caches in recovery. Then reboot.
Root Wizard said:
Try wiping data and caches in recovery. Then reboot.
Click to expand...
Click to collapse
Tried that twice with no luck, trying to load a different kernal from the set up options and getting stuck at extract:/system/framework/ext.jar for the past 2 hours. If I do anything from here I brick the phone?
Hm, im not sure. But what device are you running?
Sent from my SCH-I535 using Tapatalk
Root Wizard said:
Hm, im not sure. But what device are you running?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Samsung Galaxy SIII SCH-I535 on Verizon.
Can you
enter odin mode?
Sent from my SCH-I535 using xda app-developers app
Root Wizard said:
Can you
enter odin mode?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I can try it I'm just afraid of bricking it.
Well, you can use it to reflash stock JB and stock kernel though....and i know a debrick method that has worked for me when i was bricked.
Sent from my SCH-I535 using Tapatalk
Root Wizard said:
Well, you can use it to reflash stock JB and stock kernel though....and i know a debrick method that has worked for me when i was bricked.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Yeah, I can't enter recovery I'll probably have to pull the battery which as I understand will likely brick the phone since I'm stuck 50% into the flash.
Ok try that and tell me what happens.
Sent from my SCH-I535 using Tapatalk
Root Wizard said:
Ok try that and tell me what happens.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Pulled the battery and booted into recovery no problem. Can I got back to Jellybeans 19 or 20 with the ML1 modem, I was on the original modem when I was running that rom.
Ok, good to know!
Sent from my SCH-I535 using Tapatalk
notaneggspert said:
Pulled the battery and booted into recovery no problem. Can I got back to Jellybeans 19 or 20 with the ML1 modem, I was on the original modem when I was running that rom.
Click to expand...
Click to collapse
Yes. You can run any modem with any ROM. Apparently LTE data does not work correctly on the latest 4.3 base unless you have the ML1 modem, though.
I don't see why Alliance ROM isn't booting for you. Was it in an actual bootloop or just stuck on Samsung logo? I know that the first boot after flashing a 4.3 ROM takes extra long. Also a simple battery pull when it's stuck on Samsung logo sometimes works.
If it was in a boot loop you might have had a bad download. Try re-downloading the Alliance ROM zip and re-flashing!
Wait, how are you getting to recovery on an S3 Verizon 4.3?
Sent from my SCH-I535 using Tapatalk
BattsNotIncld said:
Yes. You can run any modem with any ROM. Apparently LTE data does not work correctly on the latest 4.3 base unless you have the ML1 modem, though.
I don't see why Alliance ROM isn't booting for you. Was it in an actual bootloop or just stuck on Samsung logo? I know that the first boot after flashing a 4.3 ROM takes extra long. Also a simple battery pull when it's stuck on Samsung logo sometimes works.
If it was in a boot loop you might have had a bad download. Try re-downloading the Alliance ROM zip and re-flashing!
Click to expand...
Click to collapse
I'm honestly not sure the difference between a bootloop and the samsung logo. The phone vibrates as part of the boot, Samsung logo comes up, vibrate, black screen and repeat.
I'll download the zip again and start over. Should I try the build 21 first for any reasons?
Try an sd card with written boot to it
Sent from my SCH-I535 using Tapatalk
notaneggspert said:
I'm honestly not sure the difference between a bootloop and the samsung logo. The phone vibrates as part of the boot, Samsung logo comes up, vibrate, black screen and repeat.
I'll download the zip again and start over. Should I try the build 21 first for any reasons?
Click to expand...
Click to collapse
The build number does not matter. You should be able to flash anything. What you are describing is definitely a boot loop. I would try to re-download the build 22 zip. What recovery are you on?
BattsNotIncld said:
The build number does not matter. You should be able to flash anything. What you are describing is definitely a boot loop. I would try to re-download the build 22 zip. What recovery are you on?
Click to expand...
Click to collapse
ClockworkMod Recovery v6.0.4.5
Or try downloading a soft brick debricking software on your cpu
Sent from my SCH-I535 using Tapatalk
notaneggspert said:
ClockworkMod Recovery v6.0.4.5
Click to expand...
Click to collapse
That's the latest recovery so you should be good. The only thing I can suggest is to re-download the zip and try again. Make sure you back up your data and factory reset before flashing (wipe data, cache, dalvik).
If that doesn't work you should be able to flash back to your old 4.1.2 build. Did you make a nandroid?