Hi there, everyone.
I had the Kit Kat 4.4.2 OMNI ROM the version that had problems with loop boot.
I tried installed 09-02 Gustavo_s kernel followed from this topic:
http://forum.xda-developers.com/showthread.php?p=50297932
And Im still having problem.
Installed the 20110310 pit-file and still get FAILED in Odin.
Installed an official ROM and still get FAILED in Odin.
I tried with 1.5.33 drivers version and returned to 1.5.27, still having problems.
Tried with Odin 3.09, 3.07, 3.04 and having FAILED problems, except for 1.87 that I have "stuck" problems.
It keeps doing without finishing it, maybe it is in a loop...
What can you do or am I doing it wrong?
p.s.: it has a bootlop in TWRP and LOGO and enters in Download Mode
Please, a little help.
Thanks in adv
Same as everyone else who has problems with an Odin flash; Hopper8's 'Odin troubleshooting' guide stickied in the General section, try all the stuff in that thread as many times as you need to in order to get a successful flash.
idomybest said:
Hi there, everyone.
I had the Kit Kat 4.4.2 OMNI ROM the version that had problems with loop boot.
I tried installed 09-02 Gustavo_s kernel followed from this topic:
http://forum.xda-developers.com/showthread.php?p=50297932
And Im still having problem.
Installed the 20110310 pit-file and still get FAILED in Odin.
Installed an official ROM and still get FAILED in Odin.
I tried with 1.5.33 drivers version and returned to 1.5.27, still having problems.
Tried with Odin 3.09, 3.07, 3.04 and having FAILED problems, except for 1.87 that I have "stuck" problems.
It keeps doing without finishing it, maybe it is in a loop...
What can you do or am I doing it wrong?
p.s.: it has a bootlop in TWRP and LOGO and enters in Download Mode
Please, a little help.
Thanks in adv
Click to expand...
Click to collapse
in which step in odin does it show failed?
---------- Post added at 07:23 AM ---------- Previous post was at 07:21 AM ----------
idomybest said:
Hi there, everyone.
I had the Kit Kat 4.4.2 OMNI ROM the version that had problems with loop boot.
I tried installed 09-02 Gustavo_s kernel followed from this topic:
http://forum.xda-developers.com/showthread.php?p=50297932
And Im still having problem.
Installed the 20110310 pit-file and still get FAILED in Odin.
Installed an official ROM and still get FAILED in Odin.
I tried with 1.5.33 drivers version and returned to 1.5.27, still having problems.
Tried with Odin 3.09, 3.07, 3.04 and having FAILED problems, except for 1.87 that I have "stuck" problems.
It keeps doing without finishing it, maybe it is in a loop...
What can you do or am I doing it wrong?
p.s.: it has a bootlop in TWRP and LOGO and enters in Download Mode
Please, a little help.
Thanks in adv
Click to expand...
Click to collapse
install a kernel with cwm then perform a FULL WIPE then try flashing stock use another odin...or try to restore any nand backup
My steps to fix this issue would be
1. Try with different USB ports.
2. Uninstall the Samsung driver and connect while device is in download mode. Let the drivers install themselves (on Windows 7 and above)
3. Try with a different PC.
I had the same issue. Used Odin v1.85.
When it did not work, I uninstalled the driver and let it install on its own.
When I tried again, this time the Odin flashed successfully and I could boot my phone.
PS: The newer builds of OmniRom have this bootloop issue fixed.
And your steps are covered in Hopper's stickied thread. The whole point of having such a comprehensive thread that covers every possible situation stickied is so everyone doesn't have to regurgitate the same crap over & over for n00bs who are unable to manage something as basic as searching for info that's been covered countless times here before, let alone fix their busted phones.
bhavstech said:
in which step in odin does it show failed?
---------- Post added at 07:23 AM ---------- Previous post was at 07:21 AM ----------
install a kernel with cwm then perform a FULL WIPE then try flashing stock use another odin...or try to restore any nand backup
Click to expand...
Click to collapse
Above Odin 1.87, it gives FAILED in a "NAND Wirte Start" stuck, it doesnt complete the task
I tried Siyah s2 5.0.1, Dorimanx and Gustavo_s Kernels and I dont get anything
gsainath4u said:
My steps to fix this issue would be
1. Try with different USB ports.
2. Uninstall the Samsung driver and connect while device is in download mode. Let the drivers install themselves (on Windows 7 and above)
3. Try with a different PC.
I had the same issue. Used Odin v1.85.
When it did not work, I uninstalled the driver and let it install on its own.
When I tried again, this time the Odin flashed successfully and I could boot my phone.
PS: The newer builds of OmniRom have this bootloop issue fixed.
Click to expand...
Click to collapse
I know about OmniRom new releases, but this ****ed it up.
I already had USB-Flex problems, bought the new Flex and changed it by my own.
The USB now is fully working, the problem is the Flash that I cant make.
By the way, it is a good point to uninstall the driver and let Windows decide.
Well, just uninstall or do anything more?
MistahBungle said:
And your steps are covered in Hopper's stickied thread. The whole point of having such a comprehensive thread that covers every possible situation stickied is so everyone doesn't have to regurgitate the same crap over & over for n00bs who are unable to manage something as basic as searching for info that's been covered countless times here before, let alone fix their busted phones.
Click to expand...
Click to collapse
Search and read is easy, fix is hard. Someone already said a phrase like this one.
Many people had the problem I have, but it is not about the SAME problem, exactly one.
If you are mad, mate, dont be.
I tried 4 differente USB cables (2 genuines), 6 different USB ports, 3 different kernels, 2 different ROMS, 1 3-part ROM and 1.3, 1.4, 1.83, 1.84, 1.85, 1.87, 3.04, 3.05, 3.06, 3.07 and 3.09 ODIN versions and Im still having the problem.
EDIT: forgot to mention, I tested 1.4.103, 1.5.27.0 and 1.5.33.0 version of USB Drivers too
This not only about a "n00b asking for help with basic searching in the forum".
Please.
idomybest said:
I know about OmniRom new releases, but this ****ed it up.
I already had USB-Flex problems, bought the new Flex and changed it by my own.
The USB now is fully working, the problem is the Flash that I cant make.
By the way, it is a good point to uninstall the driver and let Windows decide.
Well, just uninstall or do anything more?
Click to expand...
Click to collapse
Just uninstall the existing drivers and don't install any driver.
Put the device in download mode and then connect to the PC. It will auto install any required drivers.
After the device boots up, the PC will again install the necessary drivers, if required.
gsainath4u said:
Just uninstall the existing drivers and don't install any driver.
Put the device in download mode and then connect to the PC. It will auto install any required drivers.
After the device boots up, the PC will again install the necessary drivers, if required.
Click to expand...
Click to collapse
The news is that, now, my phone bricked and I dont know how. Actually.
I tried, in the last case, the PIT, got failed, reboot it, got into Download Mode, it was working. Then I turn it off. And it wont turn on again. Well, its get hot, but dont show anything. Bricked.
Maybe a motherboard replacement or I dont know if JIG Usb would help
idomybest said:
The news is that, now, my phone bricked and I dont know how. Actually.
I tried, in the last case, the PIT, got failed, reboot it, got into Download Mode, it was working. Then I turn it off. And it wont turn on again. Well, its get hot, but dont show anything. Bricked.
Maybe a motherboard replacement or I dont know if JIG Usb would help
Click to expand...
Click to collapse
You shouldn't have used previous versions of Odin to flash latest roms/kernels. That bricks the phone.
Is your phone still in warranty period? Maybe you can get it replaced before they could figure out that you flashed custom kernel.
Related
Hey,
I'm fairly new to this, but I spend 3 hours last night looking for an awnser, so I hope this isn't a trivial question that has been answered already.
Basically I tried to root my kl4 (if I remember correctly) via odin, it took about 5 seconds and told me it was succesfull, yet my phone got into the phone-triangle-computer mode, I coulnd turn it off as long as either the usb or the battery was connected, there was no way to enter the download or recovery mode, but after a while I realized that odin still recognized it, even though my computer didn't, so I downloaded the XXLA1 firmware, opened it via odin and everything went back to normal.
I tried this with a bunch of different kernels, none of them worked.
Resetting wasn't a problem, but I'd really like to know what is going wrong and what can I do to fix this
Any help would be greatly appreciated!
Swarle said:
Hey,
I'm fairly new to this, but I spend 3 hours last night looking for an awnser, so I hope this isn't a trivial question that has been answered already.
Basically I tried to root my kl4 (if I remember correctly) via odin, it took about 5 seconds and told me it was succesfull, yet my phone got into the phone-triangle-computer mode, I coulnd turn it off as long as either the usb or the battery was connected, there was no way to enter the download or recovery mode, but after a while I realized that odin still recognized it, even though my computer didn't, so I downloaded the XXLA1 firmware, opened it via odin and everything went back to normal.
I tried this with a bunch of different kernels, none of them worked.
Resetting wasn't a problem, but I'd really like to know what is going wrong and what can I do to fix this
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Every time I've heard of that screen being shown, it was a result of someone trying to flash an I9100 firmware to an I9100G, or vice versa.
It can be fixed by flashing the correct model's firmware to your phone.
Check the label under the battery. What does it say for model number?
Thats one of the things I checked first, I have a 9100G and I was only using 9100G-firmwares :/
I read a lot of threads regarding that screen, but I couldn't find this exact problem, but maybe I've searched at the wrong places^^
Swarle said:
Thats one of the things I checked first, I have a 9100G and I was only using 9100G-firmwares :/
I read a lot of threads regarding that screen, but I couldn't find this exact problem, but maybe I've searched at the wrong places^^
Click to expand...
Click to collapse
Well which I9100G firmwares were you trying? Were you also sticking to I9100G kernels? You said above "I tried this with a bunch of different kernels, none of them worked." Well, which kernels were you trying?
Also, FYI, the Computer - /!\ - PC screen is apparently a forced download, you should be able to flash from there.
I was trying a lucifr one, forgot which version, 3 or 4 different Superatmos versions and something from myGkernel, everyone with the same results, odin says after 5 seconds it succeded and I got that screen on my phone.
I already deleted the files I used, so I can't say for sure which versions they where.
Swarle said:
I was trying a lucifr one, forgot which version, 3 or 4 different Superatmos versions and something from myGkernel, everyone with the same results, odin says after 5 seconds it succeded and I got that screen on my phone.
I already deleted the files I used, so I can't say for sure which versions they where.
Click to expand...
Click to collapse
check ur pm mate
Swarle said:
I was trying a lucifr one, forgot which version, 3 or 4 different Superatmos versions and something from myGkernel, everyone with the same results, odin says after 5 seconds it succeded and I got that screen on my phone.
I already deleted the files I used, so I can't say for sure which versions they where.
Click to expand...
Click to collapse
I think I would just flash back to a stock firmware and start over at this point. Try this.
ctomgee said:
I think I would just flash back to a stock firmware and start over at this point. Try this.
Click to expand...
Click to collapse
yea
I already flashed back to the stock firmware after every kernel I tried, since my phone literally couldn't do anything, not even go into download or recovery mode, because as soon as some ki d of power source was attached it booted automatically in this phone-triangle-computer screen.
All I could do was plug the usb in, strangely odin recognized it and allowed me to flash the stock firmware, going back to the way it was before.
I'll add step for step what I did, maybe I made a mistake somewhere.
I started with downloading and installing the mobile drivers. After that I got the newest firmware via Kies, downloaded the newest 2.3.6 Superatmos kernel and started odin. I had to add the fileending to the kernel so the PDA-thing of odin would recognize it and clicked start.
Then it continued like I described before, I downloaded a stock firmware, not the newest but the XXLA1, because I thought more kernels would support that
, flasht it and repeated the process with different kernels, same outcome.
Swarle said:
I already flashed back to the stock firmware after every kernel I tried, since my phone literally couldn't do anything, not even go into download or recovery mode, because as soon as some ki d of power source was attached it booted automatically in this phone-triangle-computer screen.
All I could do was plug the usb in, strangely odin recognized it and allowed me to flash the stock firmware, going back to the way it was before.
I'll add step for step what I did, maybe I made a mistake somewhere.
I started with downloading and installing the mobile drivers. After that I got the newest firmware via Kies, downloaded the newest 2.3.6 Superatmos kernel and started odin. I had to add the fileending to the kernel so the PDA-thing of odin would recognize it and clicked start.
Then it continued like I described before, I downloaded a stock firmware, not the newest but the XXLA1, because I thought more kernels would support that
, flasht it and repeated the process with different kernels, same outcome.
Click to expand...
Click to collapse
r u on ics or gb
---------- Post added at 02:45 AM ---------- Previous post was at 02:42 AM ----------
Swarle said:
I already flashed back to the stock firmware after every kernel I tried, since my phone literally couldn't do anything, not even go into download or recovery mode, because as soon as some ki d of power source was attached it booted automatically in this phone-triangle-computer screen.
All I could do was plug the usb in, strangely odin recognized it and allowed me to flash the stock firmware, going back to the way it was before.
I'll add step for step what I did, maybe I made a mistake somewhere.
I started with downloading and installing the mobile drivers. After that I got the newest firmware via Kies, downloaded the newest 2.3.6 Superatmos kernel and started odin. I had to add the fileending to the kernel so the PDA-thing of odin would recognize it and clicked start.
Then it continued like I described before, I downloaded a stock firmware, not the newest but the XXLA1, because I thought more kernels would support that
, flasht it and repeated the process with different kernels, same outcome.
Click to expand...
Click to collapse
if u r on ics and if u want to change ur kernel as well
then u can directly flash siyah it has auto root via odin ..
or u can also try this
http://forum.xda-developers.com/showthread.php?t=1501719
Gingerbread.XXLA1, Kernelversion 2.6.35.7 dpi.Dell 165 #2
Swarle said:
Gingerbread.XXLA1, Kernelversion 2.6.35.7 dpi.Dell 165 #2
Click to expand...
Click to collapse
this mite be usefull
http://forum.xda-developers.com/showthread.php?t=1679778
ONLY FOR ICS
Is it possible to root the phone while on ics and then switch back to gingerbread while keeping it rooted? If so then that would probably be the easiest method
Swarle said:
Is it possible to root the phone while on ics and then switch back to gingerbread while keeping it rooted? If so then that would probably be the easiest method
Click to expand...
Click to collapse
no
its not possible
r u gonna be on stock rom after rootin
or u gonna try cutom roms
Kk, then i'll have to switch to ics.. I'll report back tomorrow if it worked, thanks
Hi Guys,
Sorry to bother you with this, but I'm out of ideas...
I decided to root my i9100 using this guide9.
As I was doing this, the recovery rom would reboot when using the volume buttons to navigate (only on the first "page") - This was easily worked around by using the touchscreen, but now I'm wondering if this was the start of my issues...
I applied the SU busy box installer, and got root. I installed rom manager, and noticed that it seemed to lock up when doing certain things. I put this down to CWM saying there was no official mod for the i9100.
The next day I decided to try and install a CM10.1 nightly, so I took a backup, wiped cache and data, and applied the rom and gapps.
When I rebooted, the phone wouldn't finished booting, it just sat at the initial logo screen.
After that, I tried following this recovery guide but the odin flash failed at around 80% (I retried and the same happened again).
Since then I've had difficulty getting in to recovery mode. I've tried flashing various stock roms with odin, and trying to restore with Kies.
In Kies I get as far as it conencting to the phone in download mode, but it pops up a "notice" in a foreign language - presumably Korean (and I can't copy the text to even attempt a google translation).
I tried flashing Siyah-s2-v5.0.1 to get a different recovery - that seemed to have a garbled progress bar, before hanging when I tried to wipe /data again.
When I use odin to flash a stock rom - is it supposed to restore absolutely everything? I'm not sure how I'm still getting problems if this is the case. Any ideas on what to try next?
(The current stock rom I'm try ing to use is this one)
Let me know if I'm missing any info, and thanks in advance for any help.
Using rom manager would have been the start of your problems-not the temp cwm recovery in the rooting guide.
If you can boot into download mode then I would download LP7 stock rom, disable kies and flash that with Odin.
{go back to your iphone since you are an android noob}
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Silly Billy said:
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Click to expand...
Click to collapse
I9100 right?
Try this:
- Download this ROM.
- Kies installed? uninstall it, re install it. Close it all up with Task manager (3 or 4 applications running).
- Flash ROM via Odin (CSC, MODEM, PHONE).
- If that doesn't fly, try another usb port & usb cable. Another PC would also be recommended.
- Repeat the process.
- Still no luck? try flashing a previous siyah version.
- No go? repeat all the above.
- Let us know how you did.
gastonw;37017081- Download this ROM.[/QUOTE said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
As a matter of interest, how far did you go with Phistachios repair guide.
{go back to your iphone since you are an android noob}
Silly Billy said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
Focus on getting a ROM to boot.
That ROM will install stock recovery.
gastonw said:
Let us know how you did.
Click to expand...
Click to collapse
For some reason, I can't get Odin to flash that rom - it just hands for a while at the start of data.img, before saying "Complete(Write) operation failed."
There a .pit file in the archive, although the link says not to repartition (so I didn't).
Some roms seem to get written, some don't, I'm not sure why...
theunderling said:
As a matter of interest, how far did you go with Phistachios repair guide.
Click to expand...
Click to collapse
Odin failed about 80% through flashing (step 4, after taking the ICS steps). I tried flashing the kernel afterwards, which flashed, but didn't help with my boot issues.
gastonw said:
Focus on getting a ROM to boot.
That ROM will install stock recovery.
Click to expand...
Click to collapse
Of course, I was just trying to get a better understanding of how things work - I'd settle for anything booting right now.
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
theunderling said:
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
Click to expand...
Click to collapse
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
gastonw said:
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
Click to expand...
Click to collapse
I guess I'll keep at it then.
I'd tried another cable with kies shut down. Just tried a different machine, and flashed the ROM you suggested with heimdall. It flashed without complaining (unlike odin), but I'm still getting a boot loop.
Looking at the initial recovery guide I was following - I suspect that I might've flashed the bootloader (the guide shows in bold which file goes in which box, so I probably loaded them all). Maybe this is the source of my troubles...
I also noticed that heimdall can pull data from the phone too - if I can pull and mount these, am I likely to find any useful log files?
For completeness (and anyone else who finds themselves with the same issue): It seems I hit the EMMC brick bug, which rendered some of my EMMC storage unusable.
This helpful chap came up with a workaround to partition around the dead space. (Please read the post carefully and make sure this really is your problem before flashing!)
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Sent from the little guy
gastonw said:
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Click to expand...
Click to collapse
Yes, that's right. IIRC, I flashed a working recovery with Odin, then did most of the work from adb shell.
I got my device back to life for the most part. I get the occasional hang but haven't investigated much (have since bought a Nexus 4, so not using the S2 so much).
Just thought I'd share for the next poor soul who has the same problem
Hello,
I read a lot of threads but nothing worked and now I just want to now if my handy is dead! I hope you can give me some information. Maybe some solutions.
Here is my actual situation:
On day my handy was turned off. I tried to turn it on but it keeps in a bootloop. Only the first GT-!9100 was seen and it restarts.
I took out the battery and started it again. Then it booted until the message "App 1 of 1 will be optimized". I waited a long time (about 2 hours) and nothing happend. I took out the battery and tried to boot again. Same problem like at the beginning - again bootloop.
Then I tried to get in recovery mode. It worked! I wiped the cache and restartet my handy. But again bootloop. Now I couldn't get into recovery mode. The droid was lying with a red triangle and my handy restartet automatically. So I tried the download mode. It worked! I downloaded from sammobile the actual firmware I9100XWLSD_I9100DBTLS7_DBT. I tried to flash it with odin v3 1.85 over the PDA button. I connected the handy with odin it tells me that he found my handy and I started to flash. It stucks at cache.img. I waited over night. Nothing happend. Still stucking on cache.img. I took my battery out an dwhen I put it back an started may handy I get now the yellow triangle "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So tried another one with three parts and PIT. In this time with re-partition in odin. But same procedure. I stucked at cache.img.
I still have the yellow triangle and I only can get into download mode.
Then I heard from soft/hard brick problem. I also tried the solution with only flashing the PIT. But no success
So I tried a custom kernel Clockwork Mode Recovery (GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9.tar) to get in recovery mode back. I tried to flash but it stuicks again at "NAND write". I waited again. Nothing happend. So I restarted my handy with tooking out the battery and putting it back again. But in download mode I see that my handy has a custom binary! So it worked. But I can't get into recovery mode of Clockwork
I also tried CF-Root. Here the same problem!
What's wrong with my handy? Is it broken? I've heard maybe I have to re-partition my hand over adb but I found nothing.
One thing is that for half a year I had a problem with my internal SD. It could not mount. After a update of the firmware (luckiely there was a new one!) over OTA it worked again. Maybe I have really a problem with my internal memory...
I hope I have give you all neede information to analyze my problem and I hope really you can help me. If not then it would be good to know if my handy is dead.
Thanks in advance
Best regards,
mr.mash
mr.mash said:
Hello,
I read a lot of threads but nothing worked and now I just want to now if my handy is dead! I hope you can give me some information. Maybe some solutions.
Here is my actual situation:
On day my handy was turned off. I tried to turn it on but it keeps in a bootloop. Only the first GT-!9100 was seen and it restarts.
I took out the battery and started it again. Then it booted until the message "App 1 of 1 will be optimized". I waited a long time (about 2 hours) and nothing happend. I took out the battery and tried to boot again. Same problem like at the beginning - again bootloop.
Then I tried to get in recovery mode. It worked! I wiped the cache and restartet my handy. But again bootloop. Now I couldn't get into recovery mode. The droid was lying with a red triangle and my handy restartet automatically. So I tried the download mode. It worked! I downloaded from sammobile the actual firmware I9100XWLSD_I9100DBTLS7_DBT. I tried to flash it with odin v3 1.85 over the PDA button. I connected the handy with odin it tells me that he found my handy and I started to flash. It stucks at cache.img. I waited over night. Nothing happend. Still stucking on cache.img. I took my battery out an dwhen I put it back an started may handy I get now the yellow triangle "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So tried another one with three parts and PIT. In this time with re-partition in odin. But same procedure. I stucked at cache.img.
I still have the yellow triangle and I only can get into download mode.
Then I heard from soft/hard brick problem. I also tried the solution with only flashing the PIT. But no success
So I tried a custom kernel Clockwork Mode Recovery (GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9.tar) to get in recovery mode back. I tried to flash but it stuicks again at "NAND write". I waited again. Nothing happend. So I restarted my handy with tooking out the battery and putting it back again. But in download mode I see that my handy has a custom binary! So it worked. But I can't get into recovery mode of Clockwork
I also tried CF-Root. Here the same problem!
What's wrong with my handy? Is it broken? I've heard maybe I have to re-partition my hand over adb but I found nothing.
One thing is that for half a year I had a problem with my internal SD. It could not mount. After a update of the firmware (luckiely there was a new one!) over OTA it worked again. Maybe I have really a problem with my internal memory...
I hope I have give you all neede information to analyze my problem and I hope really you can help me. If not then it would be good to know if my handy is dead.
Thanks in advance
Best regards,
mr.mash
Click to expand...
Click to collapse
do u have your phone in warranty ?
also as u can get into download mode try flashing kernel stock kernel first then the flash the stock rom (3 way package) .. do not use pit
pit shud b the last option
I can image that the following happened to your phone (not sure, only a guess):
- you were on Android 2.3.x or 4.0.x
- there was on OTA update to 4.0.4 which caused the 'updating Apps' message
- for what reason ever it was not able to update all apps successfully
- you went to recovery and *wiped*!
Being on 4.0.4 this bricked your phone due to the emmc brick bug. After that all flashing / booting / etc. will fail ...
If this is the case, there is not much to do. There is a program and a thread to modify the partition table to make it re-useable, but only in special cases.
Sent from my Nexus 7 using xda app-developers app
Hello,
thanks for your answers.
@neerajganga:
No warranty anymore I tried the stock firmware from sammobile (I9100XWLSD_I9100DBTLS7_DBT) in Odin with PDA. But I get stucked on cache.img. Or is there another stock kernel I can use?
@AndDiSa:
I was on the latest stock firmware 4.1.2.
Do you know where I can find this threat to modify the partition table to make it re-useable?
Thanks
Best regards,
Mike
mr.mash said:
Hello,
thanks for your answers.
@neerajganga:
No warranty anymore I tried the stock firmware from sammobile (I9100XWLSD_I9100DBTLS7_DBT) in Odin with PDA. But I get stucked on cache.img. Or is there another stock kernel I can use?
@AndDiSa:
I was on the latest stock firmware 4.1.2.
Do you know where I can find this threat to modify the partition table to make it re-useable?
Thanks
Best regards,
Mike
Click to expand...
Click to collapse
well 4.1.2 does not have the brick bug
did u try reinstallin the drivers and also use another usb port ?
---------- Post added at 11:55 PM ---------- Previous post was at 11:53 PM ----------
mr.mash said:
Hello,
thanks for your answers.
@neerajganga:
No warranty anymore I tried the stock firmware from sammobile (I9100XWLSD_I9100DBTLS7_DBT) in Odin with PDA. But I get stucked on cache.img. Or is there another stock kernel I can use?
@AndDiSa:
I was on the latest stock firmware 4.1.2.
Do you know where I can find this threat to modify the partition table to make it re-useable?
Thanks
Best regards,
Mike
Click to expand...
Click to collapse
also u mite wanna read this about emmc brick bug
u can find the extended pit for i9100 here
http://forum.xda-developers.com/showthread.php?t=2094564
neerajganga said:
well 4.1.2 does not have the brick bug
did u try reinstallin the drivers and also use another usb port ?
---------- Post added at 11:55 PM ---------- Previous post was at 11:53 PM ----------
also u mite wanna read this about emmc brick bug
u can find the extended pit for i9100 here
http://forum.xda-developers.com/showthread.php?t=2094564
Click to expand...
Click to collapse
Tee thread is http://forum.xda-developers.com/showthread.php?t=1823918, but if you were already on 4.1.2, you should be save. Probably it's something different and I was wrong.
@neerajganga:
I used a different PC with a different version of Windows (WIN7 on the 1st PC and WIN XP on the 2nd one). Same problem. Odin keeps stucking on cache.img :'(
I read the thread of the emmc brick bug but my problem is that for solution one I can't flash Siyeh Kernel 5.0.1 because of stucking with odin.
For the 2nd solution I need to get in recovery mode and this is not possible because of the yellow triangle.
@AndDiSa:
The thread says that it is possible to use the scanner manually in adb. Does it mean I can use it without going into recovery mode? If yes, would it be possible to explain to me how I can do it in few steps?
Thanks.
Best regards,
mr.mash
mr.mash said:
@neerajganga:
I used a different PC with a different version of Windows (WIN7 on the 1st PC and WIN XP on the 2nd one). Same problem. Odin keeps stucking on cache.img :'(
I read the thread of the emmc brick bug but my problem is that for solution one I can't flash Siyeh Kernel 5.0.1 because of stucking with odin.
For the 2nd solution I need to get in recovery mode and this is not possible because of the yellow triangle.
@AndDiSa:
The thread says that it is possible to use the scanner manually in adb. Does it mean I can use it without going into recovery mode? If yes, would it be possible to explain to me how I can do it in few steps?
Thanks.
Best regards,
mr.mash
Click to expand...
Click to collapse
u can still try flashing a kernel
ADB is useable only in recovery mode or on a running system, unfortunately neither of those are working for you currently
Sorry, but currently I don't know what else you could try.
Sent from my Nexus 7 using xda app-developers app
Try to go in recovery mode and format the whole device inside recovery. Try to use odin to flash a recovery if your device doesn't boot in to. If you're successfully then try from there to flash a kernel and a zip from stock rom.
Sent from my GT-I9300 using xda premium
Key word: pit file
Reason for flashing a pit file: unknown
Solution: flash another pit file
Odds: hard brick, mobo change.
Sent from the little guy
@neerajganga:
Which kernel should I try else? I used CF-Root and Siyeh Kernel 5.0.1. Can you give me some more information? Thanks.
@AndDiSa:
Nevermind. Thanks for your help.
@testadeferro
I tried to flash GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9. Odin stucked. After it I tried to get in recovery mode - no chance.
What kind of recovery should i use else?
@gastonw
I tried to flash only the PIT file with re-partition in odin of different threads. Same problem. Odin stucked. And for flashing a PIT for emmc bricks I need to know the brick start and brick end to choose the right one and for this I need to go into recovery mode.
Thanks.
Best regards,
mr.mash
mr.mash said:
@neerajganga:
Which kernel should I try else? I used CF-Root and Siyeh Kernel 5.0.1. Can you give me some more information? Thanks.
@AndDiSa:
Nevermind. Thanks for your help.
@testadeferro
I tried to flash GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9. Odin stucked. After it I tried to get in recovery mode - no chance.
What kind of recovery should i use else?
@gastonw
I tried to flash only the PIT file with re-partition in odin of different threads. Same problem. Odin stucked. And for flashing a PIT for emmc bricks I need to know the brick start and brick end to choose the right one and for this I need to go into recovery mode.
Thanks.
Best regards,
mr.mash
Click to expand...
Click to collapse
were u able to flash siyah kernel successfully ?
Yeah, you need to know what part of your memory is corrupted in order to flash the right pit file. Now tell me something, are you 100% sure your nand was corrupted?
Sent from the little guy
If he gets in download mode isn't time for mobo replacement but for a jtag maybee or riff box.
Sent from my GT-I9300 using xda premium
@mr.mash
try this pit : http://www.mediafire.com/?3nw116ctfd9nqq2
testadeferro said:
If he gets in download mode isn't time for mobo replacement but for a jtag maybee or riff box.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Not just yet.
Sent from the little guy
@mr.mash
also once u done flashing the pit i mentioned above ... flash a stock kernel first .. then flash the entire rom
@neerajganga:
I used CF-Root and Siyeh Kernel 5.0.1. and Odin stucks. The left upper corner says "Kernel" and the green barrel is full but in the message there is no complete or success info. It just freezes. When I turn my handy on I get the yellow triangle and I can't get into recovery mode. When I'm in the download mode it shows me that I have a custom binary. So I think it worked but no boot or recovery mode possible.
No success with the PIT file. I choosed re-partiton and only your PIT file but Odin stucked.
@gastonw:
I don't know it exactly. First there was the bootloop then it wanted to optimize 1 of 1 app. After wipe cache no recovery mode anymore. That's why I tried the custom roms. I just can give you the information what I see in Odin and on my phone.
How can I know that my USB drivers are not working correct. In Odin I get the yellow ID:COM with my COM port shown. I tried now a different PC and there I just installed the USB drivers. No KIES. And still the same problem with my phone.
Maybe I really have to re-partiton my phone but right now I didn't found something to try it out. Maybe you can give me some information about it.
Thanks.
Best regards,
mr.mash
But you did flash a pit file right?
Sent from the little guy
So, I was on 4.1.2 (running CM 11), and I downloaded the toltevzw_mj9_official_firmware1.tar.md5 and Odin 3.07.
I loaded the toltevzw_mj9_official_firmware1.tar.md5 into the PDA section of ODIN, and booted into download mode.
I ran Odin, and it seemed to work--restarted, Odin said it was successful, but now I have no cellular service and my Baseband Version is "unknown".
I've tried this multiple times, with different computers and different cords. I even flashed back to stock to get the modem back, then tried again. Same result.
Am I using ODIN wrong? Can anyone help me? Please? I have searched these forums, but every thread I found was unhelpful.
Thank you.
beans3660 said:
So, I was on 4.1.2 (running CM 11), and I downloaded the toltevzw_mj9_official_firmware1.tar.md5 and Odin 3.07.
I loaded the toltevzw_mj9_official_firmware1.tar.md5 into the PDA section of ODIN, and booted into download mode.
I ran Odin, and it seemed to work--restarted, Odin said it was successful, but now I have no cellular service and my Baseband Version is "unknown".
I've tried this multiple times, with different computers and different cords. I even flashed back to stock to get the modem back, then tried again. Same result.
Am I using ODIN wrong? Can anyone help me? Please? I have searched these forums, but every thread I found was unhelpful.
Thank you.
Click to expand...
Click to collapse
What I have found to help me and not run into this issue is flash back to stock, and re-root using the causal tool. Then I would install the lastest CWM or TWRP, install 4.3TW rom, boot up, reboot back into download mode, run odin package of the firmware (make sure you have a good md5, a bad download can affect it accepting the upgraded firmware), then wipe data,cache, dalvik and reboot. Then once rebooted confirm your modem was accepted and working, then get a GPS lock, then upgrade to CM11 if thats what you prefer.
bigmike35 said:
What I have found to help me and not run into this issue is flash back to stock, and re-root using the causal tool. Then I would install the lastest CWM or TWRP, install 4.3TW rom, boot up, reboot back into download mode, run odin package of the firmware (make sure you have a good md5, a bad download can affect it accepting the upgraded firmware), then wipe data,cache, dalvik and reboot. Then once rebooted confirm your modem was accepted and working, then get a GPS lock, then upgrade to CM11 if thats what you prefer.
Click to expand...
Click to collapse
So I did most of this, installed Alliance Rom. Now, ODIN won't recognize my device when it is in download mode. It will recognize it when I boot up normally, however. Yet, as soon as I boot into download mode, nothing.
Why is this such a pain in the ass for me? I haven't seen anyone have this much trouble.
beans3660 said:
So I did most of this, installed Alliance Rom. Now, ODIN won't recognize my device when it is in download mode. It will recognize it when I boot up normally, however. Yet, as soon as I boot into download mode, nothing.
Why is this such a pain in the ass for me? I haven't seen anyone have this much trouble.
Click to expand...
Click to collapse
That is a common problem, no worries man.
You need to go into device manager and delete/uninstall the casual/Samsung driver. Look under android development, then droid style, a sticky thread which shows you to delete driver. When you do that, that should do the trick for you!
Thank you bigmike35, so much. Everything you said worked.
To anyone else with this problem, try installing a 4.3 rom first before the mJ9. I wasted hours and hours by not doing this.
beans3660 said:
Thank you bigmike35, so much. Everything you said worked.
To anyone else with this problem, try installing a 4.3 rom first before the mJ9. I wasted hours and hours by not doing this.
Click to expand...
Click to collapse
Can you post a Link to this 4.3 Rom? or even the Rom name? thanks
Hi, ad the title says i've bricked my player
I was on cm12 and tried to flash stock ROM from odin
I fkashed two times, the first one i got a bootloop, the second one the device got bricked :crying: , i can't do anything, it won't turno on or go into download mode :crying:
Please hekp me!
I've found a guide which tells about a program called unbrickble rezurrector, but i can't find the jar...
PLease help me i miss my player :crying: :crying:
Do you think that a USB jig will do the trick?
edoardog said:
Hi, ad the title says i've bricked my player
I was on cm12 and tried to flash stock ROM from odin
I fkashed two times, the first one i got a bootloop, the second one the device got bricked :crying: , i can't do anything, it won't turno on or go into download mode :crying:
Please hekp me!
I've found a guide which tells about a program called unbrickble rezurrector, but i can't find the jar...
PLease help me i miss my player :crying: :crying:
Click to expand...
Click to collapse
To power your device all the way off plug it in and hold power until the battery logo comes up.
Then unplug it and hold power, home, and volume down to boot into download mode.
Use odin (https://www.google.com/url?sa=t&rct...=ewT0JrvKAjyPbAfN2FyCTQ&bvm=bv.91071109,d.eXY) to flash the stock firmware form here:
http://forum.xda-developers.com/showthread.php?t=2192488
Androprise said:
To power your device all the way off plug it in and hold power until the battery logo comes up.
Then unplug it and hold power, home, and volume down to boot into download mode.
Use odin (https://www.google.com/url?sa=t&rct...=ewT0JrvKAjyPbAfN2FyCTQ&bvm=bv.91071109,d.eXY) to flash the stock firmware form here:
http://forum.xda-developers.com/showthread.php?t=2192488
Click to expand...
Click to collapse
hi, I've managed to make it boot into recovery by using unbrickable resurrector... now i've got another problem, I can't flash stock rom :crying:
I've followed adam outler guide to recover from a brick, but odin won't flash on the player! it just says SetupConnection..
<ID:0/004> Can't open the serial(COM) port! I can only make it go to download mode, and if I unplug it from the pc it shuts... I don't know what to do!
i don't think that the drivers are the problem, i can flash on my galaxy tab 3...
edoardog said:
hi, I've managed to make it boot into recovery by using unbrickable resurrector... now i've got another problem, I can't flash stock rom :crying:
I've followed adam outler guide to recover from a brick, but odin won't flash on the player! it just says SetupConnection..
<ID:0/004> Can't open the serial(COM) port! I can only make it go to download mode, and if I unplug it from the pc it shuts... I don't know what to do!
i don't think that the drivers are the problem, i can flash on my galaxy tab 3...
Click to expand...
Click to collapse
My player has sometimes had this problem with Odin 3.07. It has always worked fine with Odin 1.85 however. I have attached the Odin zip just extract it and run. If it still doesn't work try installing Samsung Kies (or re-install) to get the USB driver. Should that fail install the samsung mobile USB Driver (also attached).
Kies Link (Use Kies 2.6): http://www.samsung.com/us/kies/
Androprise said:
My player has sometimes had this problem with Odin 3.07. It has always worked fine with Odin 1.85 however. I have attached the Odin zip just extract it and run. If it still doesn't work try installing Samsung Kies (or re-install) to get the USB driver. Should that fail install the samsung mobile USB Driver (also attached).
Kies Link (Use Kies 2.6):
Click to expand...
Click to collapse
ok, thank you very much for your help
i managed to flash stockrom but the player won't turn on i don't know what happend
after it ends flashing it just shuts, it won't rebot... i don't know
edoardog said:
ok, thank you very much for your help
i managed to flash stockrom but the player won't turn on i don't know what happend
after it ends flashing it just shuts, it won't rebot... i don't know
Click to expand...
Click to collapse
I'm in a similar situation (bricked after cm12, no recovery, have let the battery die, gathering info on what to do next).
Here's a total guess, maybe the repartitioning for the cm12 is messing up the stock rom (did you have "repartition" checked in odin?) have you tried flashing cm11 or 12 instead of stock?
Also if this doesn't work try flashing with the pit file which can be found lower down on the same post as the stock ROMs.
TheRealBubba said:
I'm in a similar situation (bricked after cm12, no recovery, have let the battery die, gathering info on what to do next).
Here's a total guess, maybe the repartitioning for the cm12 is messing up the stock rom (did you have "repartition" checked in odin?) have you tried flashing cm11 or 12 instead of stock?
Click to expand...
Click to collapse
Hi, each time i flash in odin i check repartition and load the pit file...
how do I flash CM11 or CM12? I can't put it in recovery...
I think we are in the same situation, i was thinking... can't we make a CM11 or CM12 flashable tar file? i don't know if it's possibile, i'm a newbie and know only a little of android and similar OS...
uff, if the galaxy payer could only boot in recovery we could be able to flash one rom to fix it!
sorry for my bad english
edoardog said:
I think we are in the same situation, i was thinking... can't we make a CM11 or CM12 flashable tar file? i don't know if it's possibile, i'm a newbie and know only a little of android and similar OS...
uff, if the galaxy payer could only boot in recovery we could be able to flash one rom to fix it!
sorry for my bad english
Click to expand...
Click to collapse
I couldn't get mine into recovery either. I couldn't even get proper download mode. But, I used odin3 v1.85 (I also tried kies, and re-installing that may have installed drivers that turned out to be necessary, windows spent a lot of time searching for drivers... I'm a linux guy, I don't really understand how/why windows needs to spend 10 minutes searching for the same drivers again and again - whatever), and tried flashing lots of things, assorted pit files, roms and recoveries...
Eventually I managed to install a stock rom that I got from the first post in this thread:
http://forum.xda-developers.com/showthread.php?p=39188127
It installed correctly, but booted into an animation bootloop.
I cannot flash cwm on to it. When I boot into recovery I get the (stock?) android 3e recovery, and a screen full of red telling me that cache does not exist. None of the four options, reboot, install update zip from sd, wipe data/factory reset, wipe cache, do anything.
Stuck there now.
TheRealBubba said:
I couldn't get mine into recovery either. I couldn't even get proper download mode. But, I used odin3 v1.85 (I also tried kies, and re-installing that may have installed drivers that turned out to be necessary, windows spent a lot of time searching for drivers... I'm a linux guy, I don't really understand how/why windows needs to spend 10 minutes searching for the same drivers again and again - whatever), and tried flashing lots of things, assorted pit files, roms and recoveries...
Eventually I managed to install a stock rom that I got from the first post in this thread:
http://forum.xda-developers.com/showthread.php?p=39188127
It installed correctly, but booted into an animation bootloop.
I cannot flash cwm on to it. When I boot into recovery I get the (stock?) android 3e recovery, and a screen full of red telling me that cache does not exist. None of the four options, reboot, install update zip from sd, wipe data/factory reset, wipe cache, do anything.
Stuck there now.
Click to expand...
Click to collapse
I'm going to try to flash that, thank you for your respond... Windows can be relly slow in seraching driver, linux is a lot faster XD, yesterday i tried to flash my galaxy player from JODIN3, which is basically ODIN for LInux, the problem is, after it ends, it says SUCCESS!! but the player won't boot... Maybe the battery is dead this happens everytime I flash the pit and stock rom, ODIN says success but then it shuts, giving no life signs
This is a really strange problem even I tryed to flash everything (from kernels, to recovery, to stock roms and the bootloader which posted AdamOutler) we need to ask to an experienced dev what maybe has happend, ecause i relly have no idea
edoardog said:
I'm going to try to flash that, thank you for your respond... Windows can be relly slow in seraching driver, linux is a lot faster XD, yesterday i tried to flash my galaxy player from JODIN3, which is basically ODIN for LInux, the problem is, after it ends, it says SUCCESS!! but the player won't boot... Maybe the battery is dead this happens everytime I flash the pit and stock rom, ODIN says success but then it shuts, giving no life signs
This is a really strange problem even I tryed to flash everything (from kernels, to recovery, to stock roms and the bootloader which posted AdamOutler) we need to ask to an experienced dev what maybe has happend, ecause i relly have no idea
Click to expand...
Click to collapse
I'll look into JODIN3, messing around with Windows is so painfull. I would skip flashing the pit, just odin the one thing. I've also found that if odin fails flashing something, everything else I try flashing afterwards will fail. The only success I've had has been with disconnecting everything, plugging the device back into the PC, the starting odin new.
I've gotten a working gingerbread ROM, from here:
http://meticulus-development.com/index.php/galaxy-player-5-0-2/galaxy-player-5-0-stock-roms/
(irritating finding the download link among all the malware bull**** and "windows support" popups, it required registering for 4shared, but a throwaway email works)
The recovery is still a native samsung android 3e, and it took me a while to figure out that the "select" key wasn't the power button, but the home softkey... That might have been true of the last one I had flashed, the one that bootlooped, maybe I could have wiped... anyway. I've got a working gingerbread GP5.0 I can give my daughter (if I can avoid the temptation of putting cwm and then cm11 on it).
TheRealBubba said:
I'll look into JODIN3, messing around with Windows is so painfull. I would skip flashing the pit, just odin the one thing. I've also found that if odin fails flashing something, everything else I try flashing afterwards will fail. The only success I've had has been with disconnecting everything, plugging the device back into the PC, the starting odin new.
I've gotten a working gingerbread ROM, from here:
http://meticulus-development.com/index.php/galaxy-player-5-0-2/galaxy-player-5-0-stock-roms/
(irritating finding the download link among all the malware bull**** and "windows support" popups, it required registering for 4shared, but a throwaway email works)
The recovery is still a native samsung android 3e, and it took me a while to figure out that the "select" key wasn't the power button, but the home softkey... That might have been true of the last one I had flashed, the one that bootlooped, maybe I could have wiped... anyway. I've got a working gingerbread GP5.0 I can give my daughter (if I can avoid the temptation of putting cwm and then cm11 on it).
Click to expand...
Click to collapse
Thank you very much! I'll try and flash, I'm curious to see if this one works! downloading right naw!!
TheRealBubba said:
I'll look into JODIN3, messing around with Windows is so painfull. I would skip flashing the pit, just odin the one thing. I've also found that if odin fails flashing something, everything else I try flashing afterwards will fail. The only success I've had has been with disconnecting everything, plugging the device back into the PC, the starting odin new.
I've gotten a working gingerbread ROM, from here:
http://meticulus-development.com/index.php/galaxy-player-5-0-2/galaxy-player-5-0-stock-roms/
(irritating finding the download link among all the malware bull**** and "windows support" popups, it required registering for 4shared, but a throwaway email works)
The recovery is still a native samsung android 3e, and it took me a while to figure out that the "select" key wasn't the power button, but the home softkey... That might have been true of the last one I had flashed, the one that bootlooped, maybe I could have wiped... anyway. I've got a working gingerbread GP5.0 I can give my daughter (if I can avoid the temptation of putting cwm and then cm11 on it).
Click to expand...
Click to collapse
Actually it didn't work DDD: whatever thank you very much for trying helping me, I think I need to change the entire device XD, but i was thinking... maybe if I install the usa rom on my INTL do you think that it may work, i've read that it works but the home button won't be recognized... dunno
I'm gonna try, as we say in italy, rotto per rotto, I will try and install
edoardog said:
Actually it didn't work DDD: whatever thank you very much for trying helping me, I think I need to change the entire device XD, but i was thinking... maybe if I install the usa rom on my INTL do you think that it may work, i've read that it works but the home button won't be recognized... dunno
I'm gonna try, as we say in italy, rotto per rotto, I will try and install
Click to expand...
Click to collapse
Hmmm, I think the US/Intl might not be super important, since all you really want is to get a working recovery on there. I got one of those GB roms on, then was able to flash cwm. I don't think you need to be able to use the rom, but installing it make odin able to flash cwm. Once cwm was on I installed the cm11 xip and all is good.
Good luck with yours.
TheRealBubba said:
Hmmm, I think the US/Intl might not be super important, since all you really want is to get a working recovery on there. I got one of those GB roms on, then was able to flash cwm. I don't think you need to be able to use the rom, but installing it make odin able to flash cwm. Once cwm was on I installed the cm11 xip and all is good.
Good luck with yours.
Click to expand...
Click to collapse
I still have the same results, the player won't boot after finishing flashing... oh well, thank you very much for your help
Maybe i'll buy another one, it's a very cool device
TheRealBubba said:
I couldn't get mine into recovery either. I couldn't even get proper download mode. But, I used odin3 v1.85 (I also tried kies, and re-installing that may have installed drivers that turned out to be necessary, windows spent a lot of time searching for drivers... I'm a linux guy, I don't really understand how/why windows needs to spend 10 minutes searching for the same drivers again and again - whatever), and tried flashing lots of things, assorted pit files, roms and recoveries...
Eventually I managed to install a stock rom that I got from the first post in this thread:
http://forum.xda-developers.com/showthread.php?p=39188127
It installed correctly, but booted into an animation bootloop.
I cannot flash cwm on to it. When I boot into recovery I get the (stock?) android 3e recovery, and a screen full of red telling me that cache does not exist. None of the four options, reboot, install update zip from sd, wipe data/factory reset, wipe cache, do anything.
Stuck there now.
Click to expand...
Click to collapse
If the stock recovery is not working try flashing a CWM recovery for the GB ROMS.
For the Intl Player with the hardware button this one should work
http://forum.xda-developers.com/showthread.php?t=1414565
You need the Odin file to flash then recovery should work.
Do a cache wipe, factory data reset, and wipe the Dalvik cache.