Okay let me start off by saying I'm no stranger to rooting or ROMs. I have had my Infuse for a few months now and I have rooted it successfully and tried several different ROMs. Currently the phone is on stock 2.2.1 rooted via superoneclick. I have already tried GTG's Ultimate Unbrick a few times to resolve the issue and it hasn't helped....and, yes, I did a factory reset as well. Right now what is happening is that the phone is booting through to the AT&T screen and then restarting again in a constant loop. What is weird is that if I play with the buttons on the phone at the bottom while on the AT&T screen it will sometimes boot all the way through and be okay and operate normally. If I push power and set it on the table and leave it alone it will just keep looping no matter how long I leave it. Weirdest thing I've run in to. I'm guessing it's a hardware issue. Any ideas anyone?
I should add that I was not doing anything....flashing or otherwise. I had just downloaded TSF Shell from the market. I have used it before on the same ROM without issue. In fact, I hadn't flashed anything new since the last time I used it.
Sent from my SAMSUNG-SGH-I997 using xda premium
well... if it isnt a bad flash, since you say you hae falshed many times before... maybe your phones flash memory is messed up. It could also be a partion layout error... if you have tried the pit reflash, and still have no luck... do as I did with a Motorola Defy... my friend trued to flash too many times and ended up damaging the memory so i just flashe da stock rom and even though it bootlooped, i turned it into warranty i my friend got a new phone in a matter of days... i dont know how it is where your from but at least here in Puerto Rico it did the job for me.
Related
Hi. I have a huge problem and I am so stressed because some of the people in these forums are awfully mean and I am already having a bad enough time, Plus I have been searching for 3 days and found no working solution. I love my phone and I fear I may just have to give up all hope, but I am just not quite ready to let go....
Seriously tho, I rooted my Optimus S and I had a hell of a time getting a recovery to work finally thunderc did the trick. then I added thundeRom, and I had it about to weeks when I came across this cool ROM called cyanogen nightly so I just had to have it. Well then my phone wouldn't flash into recovery. I tried installing many recoveries none would work.
After so many failed attempts I kept getting permission denied. I remembered that before I rooted I had the same problem and after I did a factory reset and wiped my phone clean it worked, So I did that again and I pretty sure it bricked, only I have not found any other post where the symptoms were just like mine. My phone will only blink LG nothing else.
I did back up with titanium before this and I had a nandroid backup also. Is there any hope? Does anyone know what may have happened with my recovery before this happened? It was working fine. I have not been this long without a phone in at least 10 years. Please help I would greatly appreciate it. thanks.
yes there is, if you could go into clockwork recovery (reflash it without fully turning on the phone, there probably is a way, google it )
then you could reinstall your previous backup and it would work as new.
Sent from my Nexus S using XDA App
Hey everyone, I've done some searching but I can't seem to find what I'm looking for. I was having a problem with my CM10 installations so I decided to revert back to a stock rom and start fresh.
I used odin to flash "I727UCLF6_I727ATTLF6_I727UCLF6_HOME.tar.md5" (which is supposed to be the stock ICS rom for at&t) and everything goes great, but the phone now hangs on the "Rethink Possible" AT&T logo. I've let it sit for about an hour so I'm pretty certain that nothing is going to happen.
I tried doing the same thing over hoping that maybe it was a bad flash or some kind of fluke, but came back to the exact same problem.
Any suggestions here would be phenomenal! :silly:
Factory reset
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mmerlina said:
Hey everyone, I've done some searching but I can't seem to find what I'm looking for. I was having a problem with my CM10 installations so I decided to revert back to a stock rom and start fresh.
I used odin to flash "I727UCLF6_I727ATTLF6_I727UCLF6_HOME.tar.md5" (which is supposed to be the stock ICS rom for at&t) and everything goes great, but the phone now hangs on the "Rethink Possible" AT&T logo. I've let it sit for about an hour so I'm pretty certain that nothing is going to happen.
I tried doing the same thing over hoping that maybe it was a bad flash or some kind of fluke, but came back to the exact same problem.
Any suggestions here would be phenomenal! :silly:
Click to expand...
Click to collapse
Reboot into recovery which will be stock recovery factory reset 3x and wipe cache 3x reboot and it will come up.
Yep you guys were right that did the trick! I didn't even think of it. I meant to post this last night when I actually did it but I fell asleep.
Do you know what exactly the phone is doing (or trying to do) when this actually happens to cause it? Just out of curiosity.
Thanks again!
Only way to find out is connect a debugger. Android SDK, ddms.bat
I'm not sure exactly but I have had similar issues with getting stuck in a boot loop. Usually formating and factory reset and a fresh flash did the trick.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I was sitting on BART listening to pandora and reading news on pulse when suddenly I lost service. It has not come back at all no matter how many times I turn on airplane mode or take out battery.
I searched and found some Nexus one users with a similar problem but theirs all came back when they rebooted.
I thought it might haves something to do with the ota update so I posted the problem in one of those threads and someone suggested I check the IMEI. It has not reset to 0.
My phones history: I rooted about a month ago and tried to install a new ROM but bricked. I used Odin to flash back to stock and the phone has worked since. That said, even though I though I flashed back to unrooted stock, when I turn on the phone it still shows the open lock and says "custom" under samsung. So from my limited knowledge, this could mean that the bootloader is still unlocked?
If I try to do a factory reset and there is something still tweaked from when I tried to root, is that risky to the phone? At this point I don't care much about the data. I just really need the phone to ring when people call me.
When you odined back to stock did u do a factory reset after? In my experience a factory reset after a major change always cured the issues.
Sent from my SCH-I535 using xda app-developers app
Go back to stock via ODIN if you're not on it already, dial *2767*3855# after backing up anything you may want on internal storage (like photos, etc) because it will be wiped.
I ended up switching from cmda auto Perl to lte and it worked
Sent from my SCH-I535 using Tapatalk 2
I was running slim 4.2.1 for quite some time with no problems, i loved it. I flashed 4.2.2 and my phone got stuck in NV and my phone number would come up as 000-000-3370. On first boot everything seems to be fine except that i get an error when i try to open up the play store. On my next boot is when I would see these problems. I tried everything from dirty flashing from a working 4.2.1 rom to completely formatting everything, even my external sd, and the same thing happens. This happens with every 4.2.2 rom out there. When i reboot i get stuck on the activating screen and my phone will get stuck in NV and ruim/sim wont stick no matter what i do. i don't know what else to do. someone please help!
It isn't a rom issue it is an S 3 issue that randomly occurs when flashing ROMs. You will have to flash the stock rom and reprovision your phone. I know because it has happened to me twice and both times it was with a Touchwiz ROM. You should have backed up your IMEI just in case this happens.
my imei is backed up. but why is it only 4.2.2 roms that do this?
I was able to flash back to a 4.2.1 Rom, namely pure Google for now, with no problems. but when I flash any 4.2.2 Rom the same thing happens.
All 4.2 ROMs used to do this to me.
However.
Only also happened when I flashed miui.
Now I run liquid smooth and haven't had the problem since.
sent from that young galaxy.
God bless the American people!
do u guys think I should Odin back to stock, then root, unlock, and try to flash 4.2.2?
Actually, there is an easier way
I have had this happen numerous times and it lef me to mess with my phone a little bit. I originally thought that setting it to CDMA/SIM and then rebooting would fix the problem, but I found a simpler solution to that. The last time I encountered the problem I simply set the phone to RUIM/SIM under mobile networks and then Turned on airplane mode for a few seconds then turned it off and I found my number under phone settings and everything. Try that and let me know how it goes.
Edit: Sorry, the term is RUIM/SIM, not CDMA/SIM. My bad.
hmmm, I'll definitely give that a shot later on tonight.
well I tried it, it works. but only temporarily. once I reboot it reverts back to how it was. any other thoughts?
anyone?
Chitala383 said:
anyone?
Click to expand...
Click to collapse
try this. i had the same problem. http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2
nope, none of that works either. no matter what I do ruim/sim will not stick on a reboot on any 4.2.2 Rom. I'm really getting frustrated with this.
no one has any other solutions for me?
Chitala383 said:
anyone?
Click to expand...
Click to collapse
Does your phone display an IMEI number?
Settings->About->Status
Don't need the number, just to know if you have it there....
Also do you still have Root/Unlocked bootloader?
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Chitala383 said:
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Click to expand...
Click to collapse
Have you done a complete factory restore through Odin? You would lose root and unlocked bootloader, but it may be faster to restore to stock, and reroot/mod than to try to find an "easy" fix. I was having some issues the other day in between a few ROM's, but I just factory restored, and restarted from "scratch". Now I am running perfect.
You may have already tried, but on page 1 you asked if you should, and I did not see a confirmation you did so.
Had the same problem... And yes, the phone must be reprovisioned. Although sometimes you can just adjust the network settings and change it from NV. That worked for me also.
Sent from my SCH-I535 using Tapatalk 2
I flashed root 66 via Odin, bootloop. flashed the ma2 stock image, bootloop. then flashed the lk3 stock image with success. but still with the same results as before.
tomorrow I'll try flashing g1 and start from scratch there. what do u guys think?
well, I odin'd back to bone stock G1, rooted with rootdebugfs, flashed cwm with ez recovery, unlocked my bootloader with ez unlock, flashed liquidsmooth 4.2.2 rc2 and guess what. same ****!!!!!!!!!!!!! i'm really getting fed up with this. someone has to have a solution to this cuz this is really pissing me off.
Yesterday my Droid Charge running Tweaked 3.2 would not boot, it would get past the samsung logo and start the boot animation and then turn off. Booting into recovery, several things were not mounting, was not able to wipe Dalvik cahce, only regular cache.
When I try to ODIN back to stock with PIT, it always fails on movinand.bin
I used Samsung PSTLite as well with the same result, failing on movinand.bin
I have tried flashing to ED1 and EP4.
I can flash ROMS such as Tweaked that do not have movinand.bin, but the phone does not start up at all afterwards.
Download mode still works.
What can I do??
LethalMonk6 said:
Yesterday my Droid Charge running Tweaked 3.2 would not boot, it would get past the samsung logo and start the boot animation and then turn off. Booting into recovery, several things were not mounting, was not able to wipe Dalvik cahce, only regular cache.
When I try to ODIN back to stock with PIT, it always fails on movinand.bin
I used Samsung PSTLite as well with the same result, failing on movinand.bin
I have tried flashing to ED1 and EP4.
I can flash ROMS such as Tweaked that do not have movinand.bin, but the phone does not start up at all afterwards.
Download mode still works.
What can I do??
Click to expand...
Click to collapse
Have you tried a data wipe/factory reset via cwm?
Sent from my XT907 using xda app-developers app
Yes, I can flash and boot into CWM, but wiping factory data does not do anything, it also shows multiple "error mounting such and such" messages
jco23 said:
Have you tried a data wipe/factory reset via cwm?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Try to re-PIT only.
Sent from my SCH-I510 using xda premium
What am I supposed to do after re PIT'ing? (which I have done, sucessfully)
Then flash any ROM, probably a stock one. Make sure the MD5 is good. Tell us your exact process for Odin-ing something.
Sent from my SCH-I510 using xda premium
This is what I have been doing the whole time, same result.
I know my process for ODIN'ing to be correct, battery in, SD card out, PDA checked only.
Its something other than that, I've flashed return to stock many times in ODIN before...
Is there something else I can do besides simply ODIN'ing, as I've said, I've tried ODIN and PST Lite, both failing at movinand.bin
When flashing straight to for example Tweaked, it works fine, as there is no movinand.bin
At this point, it does not even show the samsung logo anymore, the screen just quickly flashes for a moment and then turns off. Download Mode is still working though. Recovery does not boot either.
Correction, CWM does boot, but none of the partitions are mountable.
Umm, The same exact thing happen to me couple of weeks ago, I got tons of error about mounting. I know I am not helping, but I gonna say my case anyway. I tried PIT (repartition) several times, didn't work! It was random! it worked one time, and I was able to flash the pit, but when I tried to flash the EP4D didn't work! I only was able to get to the home 2 times and got tons of force-closing warnings. I have insurance, so I got a replacement. I hope you are covered as well! Just wanted to share
A fail at movinand indicates a corruption at a hardware level. I've actually pulled mine out of death (had the same issue once upon a time) just by spamming PST over and over again but I seem to be the only one who had ever succeeded in that. You're probably going to have to end up getting a new device but hey, they won't be able to tell you rooted.
Sent from my SCH-I510 using xda premium
kvswim said:
A fail at movinand indicates a corruption at a hardware level. I've actually pulled mine out of death (had the same issue once upon a time) just by spamming PST over and over again but I seem to be the only one who had ever succeeded in that. You're probably going to have to end up getting a new device but hey, they won't be able to tell you rooted.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
At this point it won't even matter. My phone broke like this and I got it switched in on the last day of warranty (luckily), and that was in August.
one last check:
have you tried using a different USB cord/USB port/different computer? I, along with many others, have experienced issues when flashing via odin with a bad cord/port (even though it had worked before). when I switched cords, it worked. but this mostly happens when the computer/ODIN fails to recognize the phone.
also, I did not remove the SD card in any of my flashings. I think once, I did remove the battery just to get the phone into download mode.
oh, and another option could be the kernel/partition/boot animation you were last on. I would recommend to try to make sure you are on RFS with stock FP5 before flashing anything.
but i suspect kvswim is probably right.
hope this helps.
ok, thanks for the help guys. I'm quite sure I dont even have a warranty on my phone, so that sucks. Might try to go into Verizon and see what happens anyway.
Do you think its worth sending it to MobileTechVideos for them to debrick, or is this outside of what they do, since it still can go into Download mode...
LethalMonk6 said:
ok, thanks for the help guys. I'm quite sure I dont even have a warranty on my phone, so that sucks. Might try to go into Verizon and see what happens anyway.
Click to expand...
Click to collapse
The phone comes with a 1 year warranty.
Sent from my SCH-I510 using Tapatalk 2