Related
Guys, i hope you can help again.
im rooted, running ics by entropy, but i have this annoying issue.
Every time i go to cwm to flash something like beats audio or another modem, i cant get back to my main rom, just keeps rebooting into cwm and even if i select reboot now, just boots again into cwm.
Its annoying because every time i want to install something i have to reinstall the rom from zero.
maybe im missing an application or something.
hope you can help me out.
I too have had this happen, but only when I use adb to reboot into CWM recovery by sending an "adb reboot recovery" to get into recovery. I can make that happen every time, so when running this ICS kernel / recovery, I'm careful to only use the extended power menu or the phone buttons to get to recovery.
Once it happens, the only way to fix in this situation is to re-flash the rom.
Just curious, how are you going into recovery?
jscott30 said:
Just curious, how are you going into recovery?
Click to expand...
Click to collapse
i select ''go to recovery'' in the CWM app, maybe thats the issue.
Jaocagomez said:
i select ''go to recovery'' in the CWM app, maybe thats the issue.
Click to expand...
Click to collapse
Probably related to the same bug in that particular recovery. I may flash CM9 in a little bit to see if I can reproduce that by going from the Rom Manager app. There is an option to get to recovery in the power menu. I'm almost certain that if you use that and/or the phone buttons, you won't have the same issue.
EDIT: I just flashed CM9 to test this, and I can't get the issue to happen when going to recovery from the Rom Manager app. Seems to work like it's supposed to from there. As soon as I issue an "adb reboot recovery", though, the same thing happens: the phone will only reboot to recovery from then on and has to be re-flashed to get to a rom. To be safe with this recovery, though, I'd still suggest only using the option in the power menu or the phone buttons.
YES! I HAVE THE SAME DAMN ISSUE!
Always happens. I have to Odin back to stock then reflash CM9. I don't know how it works from power button but using Rom Manager I get stuck. I "reboot system" now and it gets to Galaxy S/CyanogenMod screen and right back into recovery.
Simple question....when this happens..have you tried taking battery out and wait abt 30=40 to 60 seconds then replace batt and just restart? This happened to me and i did this 2x and bam the rom booted up....fine
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
I booted into recovery from rom manager flashed the new gapps pack and from then on it always booted straight to recovery I reflashed the rom 5-6 times with no success so I got a new infuse
Sent from my SAMSUNG-SGH-I997 using XDA
bigjoe2675 said:
Simple question....when this happens..have you tried taking battery out and wait abt 30=40 to 60 seconds then replace batt and just restart? This happened to me and i did this 2x and bam the rom booted up....fine
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Happened at work. Took out, waited a few hours. Nothing
Sent from my SGH-I997 using XDA
joe3681 said:
Happened at work. Took out, waited a few hours. Nothing
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
Did you mount the system from cwm before flashing the gapps package?
Sent from my SGH-I997 using XDA
It mounts itself
Sent from my SGH-I997 using XDA
Could have sworn directions said to go to mounts and storage mount system then flash gapps
Sent from my SGH-I997 using XDA
joe3681 said:
It mounts itself
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
My bad format system data and cache
Sent from my SGH-I997 using XDA
gatoraid84 said:
My bad format system data and cache
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
Yes. Tried several times. Installing a mod ends in a full wipe/format then eventually odin back to stock
Sent from my SGH-I997 using XDA
I had to use jscott30s Odin package twice yesterday screwing with this thing
Sent from my SGH-I997 using XDA
after I flash CWM 6.0.1.2, if I reboot into recovery, the phone goes into Android system recovery. Why is that?
In order to go back to CWM Recovery, I have to go to ROM Manager, flash CWM 6.0.1.2 again, and then reboot into recovery. Once I am in CWM and need to exit (reboot), I get asked the following:
"ROM may flash stock recovery on boot. Fix?"
Yes - Disable recovery flash.
Should I click yes so the phone does not go into Android system recovery? there is a message that says this cannot be undone so I do not want to do something that may screw up my phone.
I am on stock but rooted, of course. Thanks.
Same thing happens to me. Even if I use twrp or cwm touch
Sent from my SCH-I535 using xda app-developers app
justin94 said:
Same thing happens to me. Even if I use twrp or cwm touch
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Have you clicked yes to disable the stock recovery?
Anyone?
Sent from my SCH-I535 using Tapatalk 2
TabletConnect said:
Anyone?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Click yes... No problem
Sent from my SCH-I535 using xda app-developers app
I have searched everywhere for about an hour now and can find no solutions or even discussions about my problems anywhere. I had problems with it not even trying to install CM 10 and I searched and found out I needed Clock work mod 6.0, now I can't wipe my cache. I tried installing CM 10 without wiping and it gets stuck on the spinning CM boot animation. Is it because I can't wipe my cache do I need to install super user first?
I would reaaaaaally appreciate help because I really want to get a custom rom on my phone but for some reason it just doesn't want to cooperate and do it easily like others seem to be able to do.
[SOLVED Alright so after I posted this I decided to try wiping and installing with TWRP instead, everything worked like a charm this time. I flashed and rebooted and got past boot animation and my phone is now set up.
What do you mean you can't wipe the cache?
Basic flashing instruction:
You wipe caches, data, and system then try to flash your ROM.
Sent from my SAMSUNG-SGH-I727 using xda premium
spitfire2425 said:
What do you mean you can't wipe the cache?
Basic flashing instruction:
You wipe caches, data, and system then try to flash your ROM.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
It gets stuck when it tries to wipe the cache and sits there, I have waited for 30+ minutes and it does nothing, I have to pull the battery.
And I know I need to do all that, I just wanted to see what would happen, it got stuck on boot animation again as I thought.
Rcox100 said:
It gets stuck when it tries to wipe the cache and sits there, I have waited for 30+ minutes and it does nothing, I have to pull the battery.
And I know I need to do all that, I just wanted to see what would happen, it got stuck on boot animation again as I thought.
Click to expand...
Click to collapse
Use twrp.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
Use twrp.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
+1 or try a factory reset to get past the boot loop.
Sent from my SGH-I727 using xda app-developers app
xcrazydx said:
Use twrp.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Yeah thats exactly what I did right before you commented, thanks. Should I just delete my post or is there a way to mark it as solved?
Rcox100 said:
Yeah thats exactly what I did right before you commented, thanks. Should I just delete my post or is there a way to mark it as solved?
Click to expand...
Click to collapse
Edit the title as solved and ask a mod to close the thread if you wish.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
You Genius, You Made My Day...
jd1639 said:
+1 or try a factory reset to get past the boot loop.
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Hey dude, wow
you are a genius dude, you made my day a great one...
I just did factory reset from recovery mode as you suggested, and for me it worked like a charming charm...
KUDOS to you guys...
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 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?