getting to be far too familiar a scenario lately....
lately EVERY time i reboot my phone (running ics build 2, 3 and 4, stock kernel) it gets stuck on samsung logo.. somehow my phone will only boot into the frigging cm7 recovery which as im sure youre all aware is rather useless to fix any problems im having in ics and leaves me unable to flash, backup, or restore anything. it's quite frustrating and i have no idea how to fix it but by going back to bml, re-partitioning, then odin ei20 modem, cm7 fixed recovery, then flash back to ics but doin this every reboot it getting very tedious..
ive read about recovery loops, but the fix doesnt work for me as i cant mount the ICS /system partition in cm7 recovery...and ive been all over trying a zillion things to get it to work and havent pulled dmesg or logcat but if someone thinks it would be useful ..i wish i knew why EVERYTHING is great, then BANG, reboot and it's FML city.
i should add this phone is a replacement via insurance and that the entire time ive had it, i've been having this problem to varying degrees of intensity,.sometimes if i rebooted enough the ics boot animation would finally come up and freeze part way through, and in the first week with this phone is seemed fine. the first few times i rebooted and battery pulled until it started but this is the fourth time in two weeks ive found myself going back to repartition from odin and then back to ics.. the phone is only mine for a month,.
if nobody has any ideas ill be getting it replaced tomorrow in store. i have the no fee insurance replacement plan, but i would prefer not to have to use another as it's not under warranty and this would be my second replacement and this mes has to last me until the gnex hits uscc in hopefully april if it ever does because i'd rather switch to vzw than take any of usccs other offerings currently.. if they dont get the gnex it'll be time for me to move on...
anyway please advise.. thanks
http://exzacklyright.blogspot.com/2012/01/how-to-flash-ics-on-verizon-samsung.html
exzacklyright said:
http://exzacklyright.blogspot.com/2012/01/how-to-flash-ics-on-verizon-samsung.html
Click to expand...
Click to collapse
Thanks for the response. Sounds like a good guide for newbs but in my case information is redundant. I have no problems with the install, unless recovery switches to cm7 recovery during reboot and cannot manage to boot/flash/nandroid until I Odin stock ei20 with repartition and wipe out every bit of data I had. The posts about howto fix CWM bootloop for cm9 do not seem to work for me, as the post says.. Please reread the OP, ya got me excited thinking there was a solution ;-/ thanks anyway, maybe it will help another user.
wizayne said:
Thanks for the response. Sounds like a good guide for newbs but in my case information is redundant. I have no problems with the install, unless recovery switches to cm7 recovery during reboot and cannot manage to boot/flash/nandroid until I Odin stock ei20 with repartitions and wipe out every bit of data in had. The posts about howto fix cwm bootloop for cm9 do not seem to work for me, as the post says.. Please reread the OPEN, ya got me excited thinking there was a solution ;-/ thanks anyway, maybe it will help another user.
Click to expand...
Click to collapse
have you tried flashing glitch kernel to the phone. imo it sounds like a kernel issue and not so much a phone issue.
mkuehl06 said:
have you tried flashing glitch kernel to the phone. imo it sounds like a kernel issue and not so much a phone issue.
Click to expand...
Click to collapse
The problem started after using ics from alphalulz v1 on around build 3 team hacksung IMMEDIATELY AFTER flashing glitch kernel v14 build 4...I have since kept away from glitch on ics, and the problem remains.
Lately it hasn't been as bad though and it seems by hitting random buttons during boot that it will eventually start but reading tells me glitch v14 build 5 is still recovery bootloop ridden and I haven't seen a word about it in the OP for ANY ics components be it team hacksung roms or glitch kernel, and an issue like this which from reading is seemingly widespread *should* be mentioned.
Any suggestions?
In your op you said e120, what phone are you using. E120 isn't a fascinate build.
Sent from my SCH-I500 using XDA App
Ei20 is the latest and greatest version of gb/radio from uscc for the mesmerize, not that it'll change the outcome afaik to go to anything else... unfortunately ;-/
But it is a full flash package if ya open the tar up complete with movinand, sbl, radio, rfs, etc.. I think it is a 10 or 11 file package and I've used it a hundred times with making the switch from mtd to bml
wizayne said:
Ei20 is the latest and greatest version of gb/radio from uscc for the mesmerize, not that it'll change the outcome afaik to go to anything else... unfortunately ;-/
But it is a full flash package if ya open the tar up complete with movinand, sbl, radio, rfs, etc.. I think it is a 10 or 11 file package and I've used it a hundred times with making the switch from mtd to bml
Click to expand...
Click to collapse
That makes more sense to me now I know what phone your on. Try rootzwiki they have a mesmorize section, they can help ya out more than I can. I have fassy so idk much about mes
Sent from my SCH-I500 using XDA App
Related
I bought a T-Mobile Galaxy S T959. When it turns on, it says "Samsung Galaxy S GT-i9000", then the screen changes to "Samsung VIBRANT" I reflashed back to stock using odin, but it still shows the same gt-i9000 boot screen.
Does anyone know how to change it back to normal? So far, I have rooted the device, installed clockwork and flashed to the bionix rom, and installed sgs kernel flasher from the market.
I watched some videos online that showed the kernel boot screen changing after flashing a new kernel through sgs kernel flasher, but I dont know much about kernels or which one needs to be flashed.
Does anyone know what needs to be done, or have any ideas I should try?
Thanks
Well theres nothing wrong with that but it seems like it bothers you so which kernel did u used to odin???
Sent from my SGH-T959 using XDA Premium App
This is happening because the phone in the past was flashed with an I9000 based kernel. Eugene I beleive used to make some back before we had Froyo. I also had that bootup screen for a while. I don't have it anymore.
I believe I lost it through one of the many kernel flashes I have done. Just flash some of the latest kernels. It MAY clear this issue for you though it really is not an issue.
It is just the wrong picture stuck in some folder on the phone. There is no harm done to your phone nor is there anything wrong or defective with it. The only thing is that it may bother you. If it does bother you, go on a flashing spree and flash some kernels and roms. I think sooner or later you will get rid of it without even trying when you upgrade your ROM/Kernel.
Thank you, I appreciate your replies.
I bought this phone from someone online, so it was like this when I got it. Therefore I am unsure of which roms/kernels were flashed onto it in the past. I have flashed many roms, but those only seem to change the boot animation. The kernel boot screen is staying the same. Like I said, I dont really know much about kernels.
Would there be one which you recommend I try that might fix it?
I know its not really a problem, but for some reason it just annoys me seeing it say gt-i9000 at startup.
My ultimate goal is to be running the latest build of team whiskey's bionix rom. I have no clue which kernel I should flash or that would work with it.
Any help or advice is greatly appreciated.
Thank you
Try the bullet kernel.
http://edtdev.com/forum/topic/86-kernelbullet-1420ghz-4202011/
It is the fastest kernel for the Vibrant to date (1.42Ghz STABLE on most phones, outstanding battery life, all features and tweaks). It also has a custom boot screen which MAY replace your I9000 one. I'm saying MAY because I am not fully sure. In either case it is either the best or one of the best kernels for this phone to date.
As for ROMs, Team Whiskey quit Vibrant development around late February. They have moved on the the Nexus S and G2X so I'm not sure their latest ROM is the best. It's certainly an amazing ROM but there may be more recent ROMS which have more features or speed. Choice is yours.
You may try flashing some Froyo kernels from Eugene. Since his kernels likely introduced the I9000 boot you have now, flashing newer versions MAY get rid of it...who knows. Alternatively, there is another option if you are SET on getting it out.
If you flash with ODIN and also check repartition, I beleive ODIN will WIPE everything off the phone completely. Yes, all backups...everything will be gone but it should in theory also take that I9000 with it. It's a bit more risky than normal ODIN but the choice is there if you are set on it. Try the other options first and if you decide to do a repartition, READ on how to do it properly first.
@}{Alienz}{
Thank you, I tried to flash a few kernels and it seems to me like what you said about the wrong picture being stuck in the phone is what the problem is.
I Re-flashed with Odin and did a re-partition as well, but the image is still there. After rooting and flashing the bullet kernel, it still shows the gt-i9000 screen and then it switches to the bullet screen instead of the vibrant one it used to be.
After trying a few kernels, they all seem to replace the screen after the i9000 kernel screen.
Im going to keep trying to get rid of it, but i wanted to thank you for your response as I am one step further now.
Ah. Dumb-stuck image problem then huh. I thought the kernels would flash it right out. Well...you can ask someone above me about how to get it out.
Go to the EDT dev website. www.edtdev.com and join their IRC. See if a developer there can help you out with getting rid of it.
Also try the Team Whiskey IRC chat. They have more devs and people in their IRC that may be able to help. Their chat is located here:
http://webchat.freenode.net/?channels=teamwhiskey&uio=d4
I'm sure someone at those IRC chats will help you out.
try flashing the stock "param.lfs" file through odin
Okay I have had this problem and know exactly how to fix it. What happened was whoever had that phone before you flashed an I9000 gingerbread kernel with I9000 gingerbread bootloaders, that's why it shows that every time. Here is what I did to fix it. I don't know if it has to be done this way, this is just how I did it.
Step 1: download both of these files
PDA:http://dl.dropbox.com/u/23420259/Eugene_JK2_Froyo.tar.md5
PIT:http://dl.dropbox.com/u/23420259/s1_odin_20100512.pit
Step 2: Flash those files through Odin, but make sure you uncheck repartition, as I have read that if you leave it checked while flashing those files you might end up with a hard bricked phone. It will boot straight into recovery after it's finished flashing and will have some errors, that's okay just click reboot system now.
Step 3: Odin back to stock 2.1 like normal.
After you do that and Odin back to stock 2.1 wait like 10 minutes and then flash whatever rom you like. After step 2 though you should be rid of that awful GT-I9000 boot screen. I just Odined back to stock 2.1 to get rid of the broken recovery. I don't think you have to do this.
Let us know if this helped you, so that if it doesn't work someone might have an alternate way to fix it.
Oh also before I forget, I have to give credit where credit is due. Those are files are Eugenes files and I am in no way saying that I developed or had a hand in developing them.
I am currently running comrom 2.1 with OTB 1.6 kernel. Looking to go with the flow on updates lol. Wanting to get everyones opinion. Should I switch? If so, how about should I do that? Don't want to mess anything up on my phone
powerstroke said:
I am currently running comrom 2.1 with OTB 1.6 kernel. Looking to go with the flow on updates lol. Wanting to get everyones opinion. Should I switch? If so, how about should I do that? Don't want to mess anything up on my phone
Click to expand...
Click to collapse
Well the first thing you should do is read, read, and read again on the CM7 test build thread along with the waiting room in the general thread. For every handful of success stories there are even more horrible failures.
Another question you should ask yourself is why are you considering switching? Because you know, understand, and like CM7 features? Or because you have seen endless posts on here about how it is now working?
Believe me I love CM7. I ran it for my daily driver for a few months back when 60% of it didn't function. Now that it is in TEST build 10 (still not full release like Ultimate Kang bang 2.1 that you are running) people are flashing it like it is a full RC. They are also having terribly problems and soft bricked phones more than an Touchwiz based ROM at the moment.
If you really like CM7 features, understand the process for flashing an MTD/BML ROM, and feel prepared for the worst then go for it. If it is successful for you it will change your whole perception of the Fascinate. Add on the new Glitch V11.1 kernel and you will never run anything else!!
...If you are just flashing it because it is the flavor of the week... I'd wait till it is in nightlies before flashing. Just reduces the chances of an oh-s#%t-moment happening.
powerstroke said:
I am currently running comrom 2.1 with OTB 1.6 kernel. Looking to go with the flow on updates lol. Wanting to get everyones opinion. Should I switch? If so, how about should I do that? Don't want to mess anything up on my phone
Click to expand...
Click to collapse
I was exactly where you are 24 hours ago myself. I took the plunge and I'm glad I did. CM7 is the best thing that has ever been on my phone. I had zero installation problems. I haven't even tried the new 1.7ghz kernel yet. Got nems 1.6 though doing nicely. While I echo the precautions of the prior post I whole heartedly endorse the switch
Sent from my SCH-I500 using XDA Premium App
gkirby11 said:
Well the first thing you should do is read, read, and read again on the CM7 test build thread along with the waiting room in the general thread. For every handful of success stories there are even more horrible failures.
Another question you should ask yourself is why are you considering switching? Because you know, understand, and like CM7 features? Or because you have seen endless posts on here about how it is now working?
Believe me I love CM7. I ran it for my daily driver for a few months back when 60% of it didn't function. Now that it is in TEST build 10 (still not full release like Ultimate Kang bang 2.1 that you are running) people are flashing it like it is a full RC. They are also having terribly problems and soft bricked phones more than an Touchwiz based ROM at the moment.
If you really like CM7 features, understand the process for flashing an MTD/BML ROM, and feel prepared for the worst then go for it. If it is successful for you it will change your whole perception of the Fascinate. Add on the new Glitch V11.1 kernel and you will never run anything else!!
...If you are just flashing it because it is the flavor of the week... I'd wait till it is in nightlies before flashing. Just reduces the chances of an oh-s#%t-moment happening.
Click to expand...
Click to collapse
Great answer!
powerstroke, like he said; read, read, and read some more. that's what i did. and i ended up going for it, and so far i am not looking back. Just prepare yourself with backup plans in case something goes wrong.
From my point of view, I'm enjoying CM7 as least as much more than CommRom as I enjoyed CommRom more than Stock. I'd say that it's CM7 from here on out for me, except that's what I said about CommRom not too long ago. Who knows what the Devs will come up with next?
I liked CM7 but the low in call volume and the sucky AOSP camera made me go back to CommRom 2.1 with EC09 radio.
i agree, just read up like crazy so you don't mess anything up but take the plunge if your prepared. i went from just stock, debloated ed01 to the latest cm7 and i've had no problems. look up omfgb though because i'm waiting for that one to be more functional and i'm probably gonna switch to it
Give miui a shot to. It's pretty.
Fascinatemtd MIUI 1.7.15 - Glitch v11.1
Ok awesome guys appreciate all the info. I think I'm going to give it a whirl. Main question I have now is, what is the easiest and safest way to switch over to that rom from where I am now? Just do the factory reset, wipe cache, and wipe dalvik cache? Then flash the CM7 rom through recovery? or something else? Just want to make sure I do it right lol
^^^
That's why everyone said read.....
Ha...No **** lol. I understood that part but for people that might have already switched between those roms might have other suggestions. No need to be a smartass
Well since your being a smartass, lol, want to find me a forum that specifically shows how to switch from a froyo rom to cm7????
powerstroke said:
Well since your being a smartass, lol, want to find me a forum that specifically shows how to switch from a froyo rom to cm7????
Click to expand...
Click to collapse
Easy, try the thread for the CM7 ROM in the development section. jt covers it in the op, and there are several more specific walkthroughs in the the thread.
provided by Land Shark:
(coming from stock DL09)
1. Power down phone, pull battery
2. ODIN EC09 modem, pull usb cord, close ODIN
3. Reopen ODIN, connect USB, flash fixed CWM 4 from OP of CWM7 thread (here: http://forum.xda-developers.com/showpost.php?p=14554015&postcount=1)
3. Close ODIN, pull usb cord, put battery back in phone, hold volume up, volume down, and power buttons but release all three as soon as you see samsung logo flash for the second time
4. Flash CM7 07/13 build and GAPPs (Google Apps) from OP
5. Reboot phone, wait for ROM to fully boot and load, finish setting up phone with contacts, apps, etc., profit.
ok..followed your instructions. now im in a loop when its trying to flash. "waiting for sd card to mount" over and over. counting down in seconds? what should i do?
If you are serious about diving into cm7 read all u can I red for 3 days. Nearly 2500 posts and its knowledge I'll need should anything not go smooth you may have one glitch that u try and fix mess that up and its steam rolls into a long process but if u follow word for word and know exact orders of Odin and flashes and how to get to the proper cwm its beautiful just make sure ur beyond prepared before the first click that's about the best advice I can give 2cents are now in the pot
JOrtenzi said:
provided by Land Shark:
(coming from stock DL09)
1. Power down phone, pull battery
2. ODIN EC09 modem, pull usb cord, close ODIN
3. Reopen ODIN, connect USB, flash fixed CWM 4 from OP of CWM7 thread (here: http://forum.xda-developers.com/showpost.php?p=14554015&postcount=1)
3. Close ODIN, pull usb cord, put battery back in phone, hold volume up, volume down, and power buttons but release all three as soon as you see samsung logo flash for the second time
4. Flash CM7 07/13 build and GAPPs (Google Apps) from OP
5. Reboot phone, wait for ROM to fully boot and load, finish setting up phone with contacts, apps, etc., profit.
Click to expand...
Click to collapse
well this is what i did and still have problem!!!!!!!!! T.T
1) odin ebo1 with atlas pit 2.2
2) cwr blue on CM7(jt site)
3) installed cm7 latest one 7/17
4) now stuck on cm7 logo and just stuck there... nothing happens ........... any HELP????????!!!!!!
izzjkjoe said:
well this is what i did and still have problem!!!!!!!!! T.T
1) odin ebo1 with atlas pit 2.2
2) cwr blue on CM7(jt site)
3) installed cm7 latest one 7/17
4) now stuck on cm7 logo and just stuck there... nothing happens ........... any HELP????????!!!!!!
Click to expand...
Click to collapse
This works for me, but in step 2. I odin cwr 3-30 fix all. immediately Boot into it and wipe everything, then flash the 7/4 build, from there use cm7 recovery from power button to flash newest build w/o wiping...worked multiple times for me.
Sent from my SCH-I500 using XDA App
I was on com rom with ed04 radio, i just did the 3 wipes and install miui zip, takes less than 5mins.
Sent from my I500 using XDA Premium App
I have lurked for a while looking for a thread that closely matches the path I have taken. I arrived here partly by the sequence of threads and instructions I read and what has worked for me so far. I am somewhat versed in installing different ROMs as I did so on my Incredible.
I would like to get to ICS. It just looks cool. I bricked once last night trying. I used Odin to get back to stock GB. Then got to where I am.
Details:
1. Use Odin to get to stock GB. (EH03 and Atlas _v2.2 pit) Reboot to stock GB.
2. Use Odin to push CWM4 fixed for CM7
3. Three finger to CWM4 and load salsaCM7_fascinate_02132012.zip
4. Install Gapps zip from CWM4
5. Use phone
Currently when I boot recovery from the three finger method I get CWM4 but it will not mount /data, /system, /cache, etc. If the device is booted and I reboot to recovery with the power button I get CWM5 and all files mount correctly.
Can I just load an ICS ROM from CWM5?
Do I need to start with build 2 or can I use 6.1 from here?
Or do I need to go back to stock EH03, load a plain CM7 and move forward that way?
I think I may have found an answer in Droidstyle's guide in section 4. I would have to go back to stock though to get CWM4 to work, then install THS build 1.
Do I have to do this or can I reboot into CWM5 recovery from the SalsaMOD CM7 and install an ICS ROM? Would I have to use an earlier build like 1 or 2 or can I go straight to 6?
You can go straight to ICS from CM7, and you can certainly try jumping straight to the latest build, but I always have had to install build 1 or 2 first and then the later build. When I went from CM7 to ICS, I was on a different CM7 rom, but you should be able to go to ICS without having to go all the way back to stock.
Another thing to keep in mind is NEVER to 3-finger into recovery once you've flashed an ICS rom, you'll end up bootlooped. I'd get into the habit of always rebooting recovery from the power menu.
Chuckles at the fact someone flashed salsa...
Ooh and Goodluck flashing
Sent from my SCH-I500 using xda premium
k_nivesout said:
You can go straight to ICS from CM7, and you can certainly try jumping straight to the latest build, but I always have had to install build 1 or 2 first and then the later build. When I went from CM7 to ICS, I was on a different CM7 rom, but you should be able to go to ICS without having to go all the way back to stock.
Another thing to keep in mind is NEVER to 3-finger into recovery once you've flashed an ICS rom, you'll end up bootlooped. I'd get into the habit of always rebooting recovery from the power menu.
Click to expand...
Click to collapse
Many thanks. I have both builds on my SD card at the moment. I did make the mistake of booting recovery from the three finger method. That's why I had to Odin all the way back to stock. I won't be doing that again.
neh4pres said:
Chuckles at the fact someone flashed salsa...
Ooh and Goodluck flashing
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Yeah yeah yeah... I saw that coming after reading several threads today.
It is actually working okay for me. I just like the look of the ICS ROMs. I think I am going to go with THS build 6.1 w/ Icy Glitch kernel like DroidStyle mentioned in another thread.
Also, I am going to try the 4G world and pick up a Charge this afternoon. Any thoughts on that device?
Oldtymehockey said:
Many thanks. I have both builds on my SD card at the moment. I did make the mistake of booting recovery from the three finger method. That's why I had to Odin all the way back to stock. I won't be doing that again.
Yeah yeah yeah... I saw that coming after reading several threads today.
It is actually working okay for me. I just like the look of the ICS ROMs. I think I am going to go with THS build 6.1 w/ Icy Glitch kernel like DroidStyle mentioned in another thread.
Also, I am going to try the 4G world and pick up a Charge this afternoon. Any thoughts on that device?
Click to expand...
Click to collapse
THS 6.1 and glitch v14 has been a great combo for me, I've never really had a more stable setup, even with overclocking. My uptime was around 120 hours before I finally got a freeze and a reboot but that probably wouldn't have even happened if I left the kernel settings default.
I can certainly see where 4g speeds would come in handy and look forward to upgrading to a 4g device when we get it in my area. I've gotta say though, the charge doesn't seem to be too popular among the modding community, I know there are a few roms around for it, but to my knowledge, they don't have working ICS. I was pretty happy with CM7/MIUI for a while and held off on switching full-time to ICS, but I can't really see myself going back now. Amazing performance and 4.0 is just a great upgrade for android in general, in addition to looking "cool". I've gotta think that going to a phone that's not as well supported rom/kernel wise, and without functional ICS would feel like sort of a downgrade, even with the charge's beautiful screen and LTE radio, but that's just me. Unless it's a screamin deal, I'd just hold out for a nexus.
Good move using Droidstyles guide ! FWIW....I have better luck with the THS 6.0 build.
Sent from my SCH-I500 using XDA App
The Fascinate is running ICS nicely thanks to DroidStyle. I did get the Charge. I did get it a hundo less than the going rate in my area. I need to go to 4G because I have been 'throttled' on 3G. It is a suxdonut but I am a data user so VZW punishes me.
I do need to get this Charge off stock but in the meantime at least I can bring up a web page in less than five minutes. My speeds were below 300k on 3G when I was 'throttled'.
I think my next step will be to learn some basic dev skills for these devices. I mean, if I can teach myself old school VBA I think I can fumble through some development. If I come up with something good, I will certainly share.
Just curious, how did you know that you were being throttled?
I recently installed the nightly build of ICS on my samsung vibrant. Today the phone had a error that said encryption cannot be completed phone must be erased. I let it do a factory reset . Then I got stuck in a endless boot cycle showing the vibrant logo and then the cynogen guy for a few seconds then reboot. I could still access the recovery menu but it refused to flash any roms I threw at it. I downloaded and ran odin 1 click recovery and it changed my tmobile phone to a att phone. And it lost the recovery mode. It just shows att screen first then samsung vibrant second and just reboots. I can still get into download mode and flash roms using odin 3 but no matter what rom I select or if I choose repartion or not the flash will go through successfully but then the phone reboots into same problem as before. I suspect the recovery files are gone since no button combination anymore gets me into recovery. Is there anything else I can do?
Man I am having the exact same problem. I really hope someone can figure something out soon. Did yours randomly get that error? Or did you actually try to encrypt your phone?
Sounds like you used the wrong Odin 1 Click. If it installed Captivate bootloaders, that would cause a problem.
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
It just happened
It happened on its own. Was working fine all day walked in my house as as soon as it hit wifi it started going crazy. I had the data plan turned off months ago. Maybe theres something to it connecting up to the net. I have found out if you install your sim you get a reduced menu of recovery options but without sim it just constantly reboots. it only gives option of reboot, reinstall packages,delete all user data, delete cache data. If you try reinstalling the packages theres nothing there. Deleting caches made no differance. ADB does work and responds while in this lesser form of recovery is there a easy way to use adb to force a full system flash?
Thanks
That link was perfect had a link to eugenes no brick froyo rom which fixed my problem. Dloaded that used its pit and tar files and repartioned and im back to stock. Going back to team whiskeys mod. If all ICS roms has bugs like that is unusable.
bfranklin1986 said:
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Do you have access to BOTH your internal and external SD cards? The Encryption Bug is totally and completely random and does not discriminate. There is currently no known reason or solution. Several of us across a few different devices have been working on this for months.
Consider yourself luck if you have access to both SDs as you are the 2nd person to get in and out today. Many, many others have not been as fortunate.
If you could please pull up this thread and put as much information in there as possible, it would be greatly appreciated. Are you unlocked, what happened right before, what bootloaders are you on, what ROM were you trying to flash, what ROM did you end up getting booted,....those types of things. As much detail as you can muster together, after you catch your breath and relax a minute.
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Update
I think I might have pulled the trigger to quick. While the link above did give me Eugenes rom which at least got me out of the boot cycle both internal and external sd shows 0 and I am unable to load anything on either card. I have tried differant microsd cards all of them show the same thing. So eugenes rom got me working kind of but cant store anything at all. That sucks loved my vibrant and its almost out of contract and planned on using on prepay.
Agreed 100 %
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Moped_Ryder said:
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Click to expand...
Click to collapse
chickenmon said:
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Click to expand...
Click to collapse
I got tagged on a Nook Color with it. BUT, since the Nook Color has a feature that no others I think do (you can boot a ROM straight from an SD card and not mess with the oringinal OS at all), I was able to just pull my Microsd out and reformat it and then put CM7 on it for my wife.
So far from what I have seen and been working on:
Vibrant, Captivate, My wife's Nook Color, A few Transformers, SGSII,...
Anything I can do?
Anything I can do to get my partions right again? I can flash the twm 5.2.2 but none of the roms i throw at it including ics passion stays in a boot cycle. Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
chickenmon said:
... Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
Click to expand...
Click to collapse
You may want to bring up this issue directly in Merio90's thread. I believe Alex9090 went thru possibly similar issues and may be able to help you in that thread (unless she happens to pop in here).
I'm assuming you were trying to mount sdcard and emmc within recovery first (storage and mounts)? If you do have access to recovery again and can mount the external sdcard, maybe try repartitioning the card within recovery (using the parameters in Merio90's instructions)? Then transfer your rom zip and re-flash.
People have actually flashed Eugene's Froyo post-EU ... but without an ext sdcard. Quite an oddity. It's the only one (AFAIK) that'll fully boot up (even after losing int sdcard access due to EU) yet without an external sdcard in place.
Your assumptions are correct. I cannot mount emmc. I cannot flash any rom via 2.5 or 5.2 recovery only through odin and only eugenes rom still allows phone to boot but no mounting of internal or external sds. Ive spent about 3 days on this. There must be some hardcore adb commands to force a true factory reset partioning and all. Very annoying. Thanks for the help if I find any ways to fix it I will repost it here.
Might be bricked?
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Not related at all to my original problem.
tenantrep said:
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Click to expand...
Click to collapse
First of all, not to sound like a ****; but it's rude to hijack someone elses thread. You should've created your own thread for this.
Second; you might have fried your bootloader which in turn, yeah, that's bad and you might have bricked your phone.
Did you try to boot into recovery via the battery pull method. If not, try that and see how it works. I would link you to the instructions but I'm too lazy and tired right now to search for it and again, this is someone else's thread. Just do a search for it and you should find it.
If you need more help or guidance, create your own thread and start there.
Noticed your running Ice Cream Zenwich rc1.3. How do you like it. Ive installed slim 3 times today and twice I have gotten the encryption error within a hour. Needless to say not impressed major pain in the ass to have to do a million and half tricks with awm, adb, popping sd cards in and out etc.
Update
Also the current build of ics slim does not allow the imei information to be retrieved from sim for tmobile requiring a reflash of the modem. You have to download and install a new modem. I used csm5. The guide on the link in this post dow work but its a real pain and requires lots of trial and error. Wondering if google intentionally bricking these things knowing we all got gadget lust for the sIII now.
chickenmon said:
Noticed your running Ice Cream Zenwich rc1.3. How do you like it ...
Click to expand...
Click to collapse
ICZen_rc1.8.3 (AOKP #39, ICS 4.0.4) + subZero #144 (New Test Kernel just released in mr_pyscho's RootzWiki kernel thread) is Linaro infused ... and I've got to say the combo is THE fastest rom experience I've ever had on my Vibe. Whatever MP did in his new test kernel just blows the doors off the previous performance limits.
Btw .. you keep encountering EU again. Really odd unless possibly your external card wasn't partitioned correctly. Not a knock directly on you, but it is a common occurrence lately. FYI, I repartitioned mine directly from recovery.
Also ... Br1cK'd (ICZen) and mr_psycho (subZero) are aware of the EU situation and try to include safeguards in their builds. However, until we know the exact root cause of EU, we're all just shooting in the dark. Imo, it's at least comforting to use a rom & kernel where the dev's are at least mindful of EU.
this is what i get for oding late at night but i managed to do something very very stupid I odined my phone with a one click package for my captivate
I've been able to get the phone back in mostly working order now though.. but i feel in my gut something still may not be right.
here is where i got the package
http://forum.xda-developers.com/showthread.php?t=1300843
This below is what version i accidently installed.
I897UCKI2 Android 2.3.5 Gingerbread
With Bootloaders - Link to thread - Second Post [With CWM Injected Kernel from Boog]
so after i made this mistake.. (noticed my phone had a at&t bootscreen an wouldn't load) I went forth an flashed stock firmware avail for aiotools for the vibrant an then installed the stock froyo bootloader
I'm hoping everything is right in its place well except once i get cm9 flashed it boots up an shows a EU error so i freak yank the battery an odin this phone back into the stoneage an well... surprisingly.... my internal memory is 100% there O.O
anyways current issue is not being able to get cm7 to install though i'm probably missing something due to being tired anyways..
help sugestions banter calling me a noob I just want to make sure i did possibly everything to fix this mistake.
pintek said:
I'm hoping everything is right in its place well except once i get cm9 flashed it boots up an shows a EU error so i freak yank the battery an odin this phone back into the stoneage an well... surprisingly.... my internal memory is 100% there O.O
Click to expand...
Click to collapse
You,my friend, dodged a bullet here.
pintek said:
anyways current issue is not being able to get cm7 to install though i'm probably missing something due to being tired anyways..
Click to expand...
Click to collapse
Well, when you say you are not able to get CM7 to install, what exactly is it doing?
Are you getting thrown into a bootloop (caused by CWR mismatch and pretty common)? If so, pull battery and boot into recovery and re-flash CM7 over itself again. No wipe. Then reboot.
You may have to flash a different kernel, like glitch or something like that. But try the above first. Should work for you. Does it still say ATT when you boot up?
Lucky for you, everything is good, but if you want to flash a GB or higher ROM, i would suggest you flash the bootloaders in this thread: http://forum.xda-developers.com/showthread.php?t=1117990
After that just flash CM9, and you *should* be good, if not, try flashing it again with wiping data, cache, and dalvik cache. I guarantee that will work.
I ended up having to format both SD cards an retrying install custom rom via aio tool an with luck was able to get cm7 installed then cm10 an i dno't have the ime error everyone else seams to have . I did before this flash the gb bootloader over this cause it was the only thing that managed to remove the at&t splash screen before the kernal.
Lesson I learned....
remember that the vibrant you use aio tool not a premade pack >.<
an ya i do own both phones so this does complicate things now an then <,<
I also have both devices. Set up two different folders on your pc, one marked i897 and the other t959. I also add i897 or t959 to any files that could possibly get mixed up in Odin.
Its peanut butter jelly(bean) time...