Hey everyone,
This is for people who are in the situation now.
I recently flashed my Rom to stock JellyBean, just no idea why, I just had the urge to go Stock (non-rooted)
All good, happily did it, no problems at all. The problem I had was when I wanted to flash it back to Rooted Custom Roms.
Now, I used Odin for this, and felt a little too confident, and thought I could do it without problems. Here is what happened...
Open Odin,
Flashed CF-Root SGS3 v6, in PDA, (as it said)
It failed, no idea why, it kept failing on NAND Backup, all the time,
then could not for the hell of it get into Recovery, at all, only the SGSIII logo at the beginning.
So after a hell of alot of research and stress and concentration, I finally figured it out.
I downloaded CF-Insecure-SGS3_XX_NEE_ALE8-v1.2,
flashed that through PDA, then downloaded the Kernel, (Perseus.alpha25.3-i9300)
and also flashed that through PDA, it phone booted passed the SGSIII start logo, and went into Recovery and updated then rebooted, and got stuck on the Logo once again, so I got into Download Mode, flashed through Odin once again, CF-Root-SGS3-v6.0 and it passed the flash.
My Recovery was back, I went into it, and had Paranoid Android Rom on my SD-Card, luckily, and thought what the heck, it aint gonna kill it, and flashed it, and it worked!
Couldn't believe my eyes, after 15 hours and 13 cups of tea and the shakes it booted the the boot screen, and went into the Android and I now!
Finally have my phone back, was so close to giving up, but luckily my Tea kept me going.
Reason I post this is I found it hard to get the information I needed through the web, someone had the same problem but it was always 1 thing different which was a big difference. They had recovery but couldn't do anything.
So here you go everyone. If this helps, then happy days, if not then, good luck and let me know what problem your having.
Very Very eagure to learn the ways of the Android.
Related
Hey all,
Please forgive me if i've missed this somehow, but i searched and searched and no luck. Here's the dealio. What happened is that on my first ever flash attempt to flash our amazing phone, i somehow grabbed the captivate stock rom and flashed via odin.
Yeah. Imagine how that soft brick felt to a noob after mustering the courage...
Well in any case, after a little research and experimentation i moved on, and flashed again and again, but that AT&T WORLD PHONE splash screen (basically the first thing you see after reboot or power on) right before the correct T-MOBILE VIBRANT splash screen just won't go away!
I've flashed several times, after reverting to stock, or over the current rom, and the damn screen just won't go away
I can't say what files are left behind by residual after that first idiotic Captivate flash to cause this, or how they affect my phone. After multiple roms i think we all know there there are no 2 Vibrants alike! So i experience some reported issues and of course all sorts of others with any available here...
If anyone can give me a hand with this issue or point me in the right direction i would really appreciate it. This community is the best!
Thanks in advance,
K~
Rareutu said:
Hey all,
Please forgive me if i've missed this somehow, but i searched and searched and no luck. Here's the dealio. What happened is that on my first ever flash attempt to flash our amazing phone, i somehow grabbed the captivate stock rom and flashed via odin.
Yeah. Imagine how that soft brick felt to a noob after mustering the courage...
Well in any case, after a little research and experimentation i moved on, and flashed again and again, but that AT&T WORLD PHONE splash screen (basically the first thing you see after reboot or power on) right before the correct T-MOBILE VIBRANT splash screen just won't go away!
I've flashed several times, after reverting to stock, or over the current rom, and the damn screen just won't go away
I can't say what files are left behind by residual after that first idiotic Captivate flash to cause this, or how they affect my phone. After multiple roms i think we all know there there are no 2 Vibrants alike! So i experience some reported issues and of course all sorts of others with any available here...
If anyone can give me a hand with this issue or point me in the right direction i would really appreciate it. This community is the best!
Thanks in advance,
K~
Click to expand...
Click to collapse
Have you tried using Odin to go back to JFD? with re partitioning checked?
Tried JK2?
The splash screen is usually controlled by the kernel, you could also just try re flashing a stock vibrant kernel to see if that works.
I'm having the same issue. Just got a used Vibrant yesterday and I'm not sure what version it was on. I downloaded a bunch of apps and all was well - it worked great. I went to bed and when I woke up this morning it was stuck on the Samsung Vibrant screen. I tried using Odin with the 512.pit and the JFD.tar but that did nothing. I then found a one-click fix, not realizing it was only for the Captivate and used it. So now my T-Mobile Vibrant is stuck on the AT&T World Phone screen.
I can get into Download mode just fine and I have re-loaded the JFD in Odin several times, including doing so with the re-partition box checked but to no avail. I'm downloading the JKT rom now, though I have little hope that that will do the trick after all I've already done.
Any suggestions?
PS - I also tried downloading the All_In_One.zip and flashing to the Original.tar, then the T959UVJI6.tar. No dice. Nothing seems to work.
So, SGH-177 had been rooted and installed CM7, then Unnamed, then AOKP. All were pretty buggy. We wanted to bring it back to factory (with root if possible). Not for a warranty claim, just so it would be somewhat stable.
Anyway, I found a one click ODIN solution for UCKH7 stock. I used that, it passed. then the phone just looped through the AT&T "Rethink Possible" splash screen. I tried to get into recovery mode, but it wouldn't load, so I flashed the Siyah kernel to get CWM on there. Still I can only get into download mode and the phone loops the splash screen.
I hoped that it was just taking some time to load up the first time, so I left it overnight. Still stuck on the splash screen this morning.
I spent hours on here last night and found lots of people saying that if you have access to download mode, or recovery mode, you should be able to fix it. I wasn't able to find any answers as to how.
Help?!
I've had this same problem before. what always fixes it for me is to get into the factory 3e recovery to do a reset. I know you said you couldnt get there but make sure (while the phone is off; remove battery if you have to before this) you are holding down both Volume buttons and the power button at the same time until you see the "Samsung Galaxy SII" screen, then release the buttons.
factory reset, then it should be fine.
If you can't get to recovery, read some more on here. I'm sure something is out there, but I don't know what it is.
Here are two posts that might help you out. I've been doing the same research since my "Oh crap its stuck in a bootloop I'll sell it cheap on eBay" SGII is due to arrive today or tomorrow.
http://forum.xda-developers.com/showthread.php?t=1451590
http://forum.xda-developers.com/showthread.php?t=1580885
Best of luck to you!
UnNamed buggy?
Out of curiosity how did you root and flash, cause that is probably one of the most stable builds we have with minor changes to stock.
Anyways good luck getting back to stock.
So, for some reason, the next time I tried booting into recovery, it worked. I got a couple errors, but then it booted up just fine. Don't know why it wouldn't get into recovery before.
Everything seems to be working as it should so far.
I'm guessing this may be why some of the threads I had seen didn't really offer a solution. Sometimes it finally works if you just hold your head right.
Thanks all!
Regarding UnNamed... I don't recall the method I used to root, it's been a long time and I've done various work on this (my wife's phone) and my Nexus One. Easy to get it confused. I flashed it through CWM recovery, factory wipe, flash from SD.
It worked fine for a while (a couple months), then it got really glitchy. Unable to answer phone calls, random reboots, etc.
Major Wood said:
I flashed it through CWM recovery, factory wipe, flash from SD.
It worked fine for a while (a couple months), then it got really glitchy. Unable to answer phone calls, random reboots, etc.
Click to expand...
Click to collapse
Did you also wipe cache and dalvik? May have been the problem...
I don't recall, but would be surprised if I hadn't done that
A year ago. When I first started flashing roms. I spent an entire week just reading the atrix forums and learning. I planned. I schemed. I asked questions. Through pm. And googled a LOT. Then when I had learned enough I did it. Point is....if yer not willing to have patience and learn as much as u can before u jump into this. Then its maybe not for you.
Sent from my SGH-I777 using Tapatalk 2
I bought a fascinate from good ol craiglist for a friend. When I bought it I noticed the original user had already rooted it and installed CM7.
Because I didnt know what he had done to it I decided to start from scratch and used Odin and flashed powerwashed_20_b3_Full_ec09modem and the atlas_v2.2.2.pit
After that I flashed cwm4_fixed_for_cm7-ODIN.tar and began getting ICS on this baby (teamhacksung-ota-eng.BUILD2.zip followed by build 11 at the time).
Everything was gravy and I gave the phone to my friend who was a happy panda. Several weeks later he calls and tells me the phone is stuck in recovery, I assume he borked something so I headed over thinking I will just Nandroid the ICS ROM that I set up before I gave it to him.
Funny thing was after rebooting from the Nandroid, the phone goes back to recovery! I was a little confused but assumed that maybe the Nandroid went bad when I backed it up. So I decided to just reflash build 11 again, after the flash was successful i reboot and.... back to recovery?
At this point I was pretty confused, CWM appeared to be working but it wasnt. Nothing was working, not even flashing CM7. The only way I got it to work again was to Odin the powerwashed_20_b3_Full_ec09modem and the atlas_v2.2.2.pit again. So that was what I did and got him back to ICS (build 13 this time).
Thinking it was a freak occurence I didnt pay it any mind, until he called me again several weeks later saying its stuck in CWM again!? So I check it out and sure enough it keeps booting to recovery and not able to nandroid or flash anything (even tho it says it does successfully).
At this point I assume its a hardware issue but dont understand what exactly, I bought another on craiglist and will swap with him and further investigate the issue.
I looked around the forums to see if anyone had a similar issue but have not seen anything like this. Anyone have any ideas??
This is most likely caused by doing the three finger reboot on the newer ICS roms. Tell them to pull the battery instead the next time their phone locks up. Also, there is boot loop breaker in the development section.
Sent from my SCH-I500 using xda premium
I assumed that as well, however my friend has no experience with these devices and would never hold down all three buttons for any reason. Both times he had reported that the phone randomly went into recovery on its own.
He could be BSing me of course, but I'll be testing it when I get it back tomorrow and see if I can recreate the scenario.
But I will be including the boot loop breaker file in the SD card and see if that at least makes this phone usable again instead of having to use ODIN every time. So thanks for that info!
Check kernel settings. Sleep Of Death, maybe?
After rooting my phone for the first time about a month ago, I though to myself "This is awesome!". After thinking that, I dug deeper and deeper into the Android Universe and found custom ROMs. The first one I flashed was just a standard 4.0.3 ROM that worked fine. The second one I flashed was a CM10 JB ROM (for my device), and this also worked. But yesterday, (22nd August) I realised that flash player wouldn't work, even though I had the .apk installed on my phone. I found out what dual-booting was when I flashed the CM10 ROM but I didn't need to do it at that time. I downloaded the latest Siyah kernel, flashed it, turned on my phone and it worked fine (CM10) and then I realised I had to go back into recovery mode to change my primary and secondary ROM. I did this, and then next time I tried to turn it on, it just stays on the boot logo. (Siyah logo when I had the SIyah kernel on there and the default SGS2 boot logo with the yellow triangle when I changed back to a plain, old, boring, nothing special kernel). I am currently downloading an OSP file to see if that will help.
That is pretty much all the info I can supply with my knowledge of Android devices but I can try and give some more if needed.
Also, do you think if I took my phone back to **** Sith (Australian retailer where I bought it from) and played dumb (eg. I went to turn it on and the screen just stayed like this, I even left it like that over night and nothing happened) they would give me a new one? I know it voids warranty when you root but maybe if I get someone who doesn't know much about these phones I could get lucky.
Please give me as much help as you can. I haven't told my parents yet because I'm not prepared to face their wrath yet. God knows what they'll do to me!
So your hoping theres someone like you on the other side of the counter when you take the phone back?
Can you get into recovery/download mode lol
Maustin96 said:
After rooting my phone for the first time about a month ago, I though to myself "This is awesome!". After thinking that, I dug deeper and deeper into the Android Universe and found custom ROMs. The first one I flashed was just a standard 4.0.3 ROM that worked fine. The second one I flashed was a CM10 JB ROM (for my device), and this also worked. But yesterday, (22nd August) I realised that flash player wouldn't work, even though I had the .apk installed on my phone. I found out what dual-booting was when I flashed the CM10 ROM but I didn't need to do it at that time. I downloaded the latest Siyah kernel, flashed it, turned on my phone and it worked fine (CM10) and then I realised I had to go back into recovery mode to change my primary and secondary ROM. I did this, and then next time I tried to turn it on, it just stays on the boot logo. (Siyah logo when I had the SIyah kernel on there and the default SGS2 boot logo with the yellow triangle when I changed back to a plain, old, boring, nothing special kernel). I am currently downloading an OSP file to see if that will help.
That is pretty much all the info I can supply with my knowledge of Android devices but I can try and give some more if needed.
Also, do you think if I took my phone back to **** Sith (Australian retailer where I bought it from) and played dumb (eg. I went to turn it on and the screen just stayed like this, I even left it like that over night and nothing happened) they would give me a new one? I know it voids warranty when you root but maybe if I get someone who doesn't know much about these phones I could get lucky.
Please give me as much help as you can. I haven't told my parents yet because I'm not prepared to face their wrath yet. God knows what they'll do to me!
Click to expand...
Click to collapse
Can you still boot to your second Rom ie CM10?
Can you still get to CWM recovery?
If your answer are yes.
-boot to CWM recovery
-flash your Samsung custom ROM again
-wipe dalvik cache
-wipe permissions
-flash Siyah kernel
-reboot phone
Swyped from my Samsung Galaxy SII
Dude, take a chill pill. This is XDA, there are a lot of awesome people here who might know a solution to your problem
Luckily, you are not the only person alive to screw up their flash player while they were on cm.
If you can go to download mode, you can start all over again from scratch by flashing a stock firmware.. and from there, let your custom stuffs begin!cheers
Sent from my brain using telekinesis
Thanks for all the responses guys!
I have managed to fix through scouring every corner of the internet. It probably took a lot longer than it should have since it i sme, oh well! I'm just so thankful everything is working again.
I think I'll stay away from dual booting!
How do I close this thread?
Send a PM to prbassplayer. He's the moderator.
Sent from my Galaxy S2 GT i9100
Thread closed
Per request.
Hi everyone,
I have been frequenting XDA for quite a while. Hugely into android and custom roms and things of the sort, but have never had a real reason to post. I have either been lucky enough to be able to find what I need by searching, or figured it out myself. This time however, I am pretty stumped.
I did a fair amount of research before starting this, and am now seeing that I did not do quite enough. If I am in the wrong place please direct me to a better one.
Here is my issue:
I have an LG g2 that I recently picked up used. Phone has never been rooted or worked on...until now. Decided I would spend my weekend working on it. Successfully rooted, and installed TWRP. Decided to flash a rom, downloaded my rom as I have always done, put it on the sdcard, made a couple of nandroids, and flashed it. Everything seemed ok, booted back up, got the correct boot animation, but it bootlooped. No big deal Im thinking, go back into recovery and wipe a couple times. Still wont boot. Go back in and restore my nandroids, and they wont boot either.
So now I am worried. Try it a coulple more times, and somehow get it to reboot to the setup screen. Wont go past there. Do the trick to avoid it and cant get it to activate. Double check everything, power off, wipe, power back on and now it wont even load to there. I tried sideloading a different rom as well as what seems to be the stock software and nothing. Im lost, I need help. Any advice?
skizzyp said:
Hi everyone,
I have been frequenting XDA for quite a while. Hugely into android and custom roms and things of the sort, but have never had a real reason to post. I have either been lucky enough to be able to find what I need by searching, or figured it out myself. This time however, I am pretty stumped.
I did a fair amount of research before starting this, and am now seeing that I did not do quite enough. If I am in the wrong place please direct me to a better one.
Here is my issue:
I have an LG g2 that I recently picked up used. Phone has never been rooted or worked on...until now. Decided I would spend my weekend working on it. Successfully rooted, and installed TWRP. Decided to flash a rom, downloaded my rom as I have always done, put it on the sdcard, made a couple of nandroids, and flashed it. Everything seemed ok, booted back up, got the correct boot animation, but it bootlooped. No big deal Im thinking, go back into recovery and wipe a couple times. Still wont boot. Go back in and restore my nandroids, and they wont boot either.
So now I am worried. Try it a coulple more times, and somehow get it to reboot to the setup screen. Wont go past there. Do the trick to avoid it and cant get it to activate. Double check everything, power off, wipe, power back on and now it wont even load to there. I tried sideloading a different rom as well as what seems to be the stock software and nothing. Im lost, I need help. Any advice?
Click to expand...
Click to collapse
would really like someone to chime in...running linux.
Bump. Can anyone give me any advice?
skizzyp said:
Bump. Can anyone give me any advice?
Click to expand...
Click to collapse
Sounds like you need to restock and start over. I'd give you links but how to do so varies by which version or carrier the phone is from.