I am selling my old galaxy s due to having a new phone and I have made it freeze when it boots.
It was flashed onto myICS when I was using it and before handing It over I wanted to wipe everything so it was clean for the new owner. I did this in the phone options and then also in recovery mode to make sure, but after rebooting it is just stuck at the galaxy s boot loader.
I tried flash another Rom onto it and the same thing happened even though odin said it was successful.
I'm not sure what to do now as I am scared of truly bricking the phone so I am asking what should I do to get it up and running again?
Thanks
hmm
it should work after reflashing and whiping data/cash in recovery mode
No luck with it.
I tried wipe data and reboot and had no luck. Then tried reflashing, wiping data and still no luck.
Do you think it might be something with the kernal thatI had installed with the myICS rom, not being compatable with the rom I was flashing to?
steph1389 said:
No luck with it.
I tried wipe data and reboot and had no luck. Then tried reflashing, wiping data and still no luck.
Do you think it might be something with the kernal thatI had installed with the myICS rom, not being compatable with the rom I was flashing to?
Click to expand...
Click to collapse
Didn't you format partitions before flashing? Have you tried doing a fully clean install?
did u try to flash a stock rom via odin
Related
I recently got a galaxy player 5 international with froyo. I rooted it with no problems, but when I tried to flash a kernel with cwm recovery it would get stuck in a boot loop unless i went into the cwm recovery mode. I noticed that the kernel I used, rumirand's r14, was based off of GB and thought that might be my problem. I tried updating my firmware to GB using WT Ho's custom rom, and now it just hangs on the samsung logo, but I can still get into cwm. I made sure to wipe both caches and wipe data before installing the rom. Is this fixable or have I turned it into an expensive paperweight?
Did you try a factory reset?
I am not expert but i tried the same with R14 kernel and bricked but done the same with R13 and it worked .
Chris4evernoob said:
Did you try a factory reset?
Click to expand...
Click to collapse
Now or before installing the rom? I did a factory reset before installing, but I haven't done one since.
DZonikg said:
I am not expert but i tried the same with R14 kernel and bricked but done the same with R13 and it worked .
Click to expand...
Click to collapse
I just flashed the R13 kernel, but I'm still in the same situation.
Instead of flashing a new kernel there should be factory reset option on the first set you have or in "mounts and storage"
I had this problem once and I managed to solve it flashing a full rom (like 2.3.5 rooted and with rj kernel). It seems some users are having problems when flashing only the kernel. After you solve the problem, flash back group rom.
I just tried the rom+kernel. It said it was successful but it must not have been because it was hanging on boot again, and now it won't respond to the power button. If I plug it in to the computer it gets an image of a battery turns off and repeats.
jnmaster said:
I just tried the rom+kernel. It said it was successful but it must not have been because it was hanging on boot again, and now it won't respond to the power button. If I plug it in to the computer it gets an image of a battery turns off and repeats.
Click to expand...
Click to collapse
Can you go back to CWM after flashing rom+kernel? If yes, usually it is a matter of wiping the data and Dalvik cache. Which ROM+Kernel did you flashed?
WT Ho said:
Can you go back to CWM after flashing rom+kernel? If yes, usually it is a matter of wiping the data and Dalvik cache. Which ROM+Kernel did you flashed?
Click to expand...
Click to collapse
No, I'm not able to get a response from the power button.
I used the ROM + kernel you posted http://forum.xda-developers.com/showthread.php?t=1446774
Hello all, could use some help here.
I'm trying to restore my Note to the factory ROM and I'm running into an issue.
Fyi, I had the latest Paranoid JB Rom from Oct 13.
I followed the proceedures outlined in the forums (used ODIN to restore the default "attstockrom") and after that restore the phone would loop rebooting into ATT rethink possible animation screen.
I found and downloaded the latest 4.04 rom for the phone (I717UCLF6) and rebooted. Now it just hangs at the "ATT Rethink possible" graphic (no animation, no loop).
Odin does see the device fine so I can reflash again with no problems if I need to. I'm thinking of trying the I717UCLA1 version from Jan to see if that works but I'm hoping I can get some better advice before I do something that might cause more permanent problems.
Any advice on how to get back to stock ICS (or even JB) and get the phone working again?
Thanks!
Try doing a factory data/cache wipe from Recovery.
I flashed the stock rom via ODIN. There is no factory data/cache wipe since there's no custom recovery.
Are you suggesting flashing CWM/TWRP on the phone now then doing that?
Houston we have liftoff. Thanks for the tip Fappa, that got me into the phone (reinstalled cwm, factory reset). However I'd still like to remove CWM and go back to completely stock....
I'm not overly worried about it as I'm selling the phone but I'd like the new owner to have a completely clean phone in case they need to send it in at some point for repair. But in any case it's up and running with CWM and factory ICS rom.
santiagodraco said:
I flashed the stock rom via ODIN. There is no factory data/cache wipe since there's no custom recovery.
Are you suggesting flashing CWM/TWRP on the phone now then doing that?
Click to expand...
Click to collapse
I'm sure fappa meant to use the stock android recovery and wipe. when I go back to stock it always hangs at AT&T boot logo and have to wipe/reset from stock recovery to get it to boot.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Yes do what they say or you will continue to boot loop.
Sent using cheezoline.
Hey all,
I bought my phone back in USA (i9300) and I decided to flash my carrier's latest ROM (ELL6) so I downloaded it and flashed away with odin.
Everything went great, except that my phone is now bootlopping between carrier's bootanim and samsung's. I already tried to flash it again.
I was coming from CM10.1 official and had recovery 6.0.2.8.
What can I do to fix this?
thanks!
ok nevermind, fixed it by going to stock recovery (volup+home+pwr) and wiping data / factory defaults.
mikeflash said:
Hey all,
I bought my phone back in USA (i9300) and I decided to flash my carrier's latest ROM (ELL6) so I downloaded it and flashed away with odin.
Everything went great, except that my phone is now bootlopping between carrier's bootanim and samsung's. I already tried to flash it again.
I was coming from CM10.1 official and had recovery 6.0.2.8.
What can I do to fix this?
thanks!
Click to expand...
Click to collapse
wipe data a factory reset, if that doesn't work then reflash rom again.
If still doesn't work format system, data and cache and reflash then factory reset.
thanks. It worked.
Not sure if it was odin stock or wipe data that deleted all my personal files on the internal card... grrr. This is my 3rd galaxy phone, and it's the first time I ever go back from custom to stock ROM. Didn't know I was about to lose my pictures and mp3.
was stuck on the same problem on a gs2, backup all and wipe away
Hey guys,
I was just wondering what the general consensus is on which recovery is the most preferred.
I was using TWRP 2.6, but that gave me problems (being stuck on samsung logo everytime my phone rebooted). Reverted back to 2.5.0.2 and it seems to work fine so far. I did try CWM in the past but for some reason my boot loader would get locked and I would have to ODIN back to stock.
So what's your preferred recovery and why?
Thanks.
Exodus885 said:
Hey guys,
I was just wondering what the general consensus is on which recovery is the most preferred.
I was using TWRP 2.6, but that gave me problems (being stuck on samsung logo everytime my phone rebooted). Reverted back to 2.5.0.2 and it seems to work fine so far. I did try CWM in the past but for some reason my boot loader would get locked and I would have to ODIN back to stock.
So what's your preferred recovery and why?
Thanks.
Click to expand...
Click to collapse
I like TWRP. It works well with the new phone and Roms that are coming out plus it is so easy to use. Never liked CWM very much. You did right by reverting to an older version of TWRP I had to do that once.
TWRP... i don't even consider anything else.
Do you guys know why my phone gets stuck on the samsung logo everytime i restart my phone?
Doesn't matter what ROM i use it always happens....
Did you do a factory reset, system wipe, preload wipe, cache wipe, and dalvik wipe? Or try fix permissions from recovery?
If not, go do all of those.
If that doesn't work, something is missing from the system partition that is keeping it from booting. Which means you deleted it. :good:
Dubbsy said:
Did you do a factory reset, system wipe, preload wipe, cache wipe, and dalvik wipe? Or try fix permissions from recovery?
If not, go do all of those.
If that doesn't work, something is missing from the system partition that is keeping it from booting. Which means you deleted it. :good:
Click to expand...
Click to collapse
I did ALL of those, still have the problem.
So.... I just ODIN-ed back to stock and going to root and basically re-do everything -_-
Hello everyone, I hope you can help me on this one since I'm already panicking.:
I have a Galaxy S3 international version, with Android 4.2.2, rooted, Philz recovery.
Wanted to flash a custom ROM, backed up EFS folder and data. Only thing missing was doing a NANDROID backup. Did the NANDROID backup to sdcard and rebooted....and now device won't start; it's stuck on the "SAMSUNG" logo. , WHAT THE HELL DID I WRONG?
I haven't formated anything or handled any system folders or anything. Just went , like in previous android phones, to recovery, made backup and rebooted. Any ideas? many thanks!
rhrs1987 said:
Hello everyone, I hope you can help me on this one since I'm already panicking.:
I have a Galaxy S3 international version, with Android 4.2.2, rooted, Philz recovery.
Wanted to flash a custom ROM, backed up EFS folder and data. Only thing missing was doing a NANDROID backup. Did the NANDROID backup to sdcard and rebooted....and now device won't start; it's stuck on the "SAMSUNG" logo. , WHAT THE HELL DID I WRONG?
I haven't formated anything or handled any system folders or anything. Just went , like in previous android phones, to recovery, made backup and rebooted. Any ideas? many thanks!
Click to expand...
Click to collapse
If its stuck in a bootloop factory reset and wipe cache in recovery.If that does not work install your backup and lastly if that doesn't work flash stock with odin.
Always remember the first thing to try whenever you are stuck in a bootloop is to factory reset wipe cache in recovery.
tallman43 said:
If its stuck in a bootloop factory reset and wipe cache in recovery.If that does not work install your backup and lastly if that doesn't work flash stock with odin.
Always remember the first thing to try whenever you are stuck in a bootloop is to factory reset wipe cache in recovery.
Click to expand...
Click to collapse
I did a full wipe and cache wipe and everything back to normal. What puzzles me is what was it that put the phone in a bootloop?
rhrs1987 said:
I did a full wipe and cache wipe and everything back to normal. What puzzles me is what was it that put the phone in a bootloop?
Click to expand...
Click to collapse
Good question but unfortunately I've not got a definite answer for you.Some times it is files leftover from a flash but no matter how experienced you are at flashing, bootloops are just one of those things you have to get used to.[emoji1]
tallman43 said:
Good question but unfortunately I've not got a definite answer for you.Some times it is files leftover from a flash but no matter how experienced you are at flashing, bootloops are just one of those things you have to get used to.[emoji1]
Click to expand...
Click to collapse
Indeed have to get used to it... many thanks for response tallman43