Yesterday, I was running RemICS-UX 2.0 without a hitch, then I started getting "unfortunately, xxxx has stopped working". dozens of them. at a time.
so, I tried re-flashing the ROM, and nothing happened; same problem.
I tried doing a factory reset, wiping dalvik cache, and manually formatting /data and /cache from CWM, but when I booted, all the apps and whatnot were still there, exactly how they had been before.
I repeated this process multiple times.
Eventually, I tried flashing kernels and gingerbread ROMs with no success, some bootloop on the Samsung logo and some just sit at their loading animation. I tried going into download mode, but Odin3 didn't seem to respond to my device. I'm not sure if it's a compatibility issue with windows 8 or if that particular problem lies in the device.
This thing is my primary mobile device, and I'm a bit frustrated that this is happening, so, naturally any help or advice you guys have to offer would be greatly appreciated. Thanks in advance!
High possibility of Windows 8 being the problem here. I dont know WHY that happened to your 5.0, but i guess you could try reflashing the stock GB rom on Windows 7. Your device can power on, the screen works, cwm works, so i doubt its related to the device. best luck.
Mashed_Potatoes said:
High possibility of Windows 8 being the problem here. I dont know WHY that happened to your 5.0, but i guess you could try reflashing the stock GB rom on Windows 7. Your device can power on, the screen works, cwm works, so i doubt its related to the device. best luck.
Click to expand...
Click to collapse
I forgot to install the Kies drivers after upgrading and Odin3 recognizes it but gets stuck
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I got my galaxy player to boot SM34's CM9 ROM, but the keyboard gives a force close message every few seconds, most stuff just crashes.
The really weird thing here is that when I use android's factory reset, manually delete data files in root browser, or format in CWM, I get a success message, but when I reboot, everything is still there.
halomademeapc said:
I forgot to install the Kies drivers after upgrading and Odin3 recognizes it but gets stuck
I got my galaxy player to boot SM34's CM9 ROM, but the keyboard gives a force close message every few seconds, most stuff just crashes.
The really weird thing here is that when I use android's factory reset, manually delete data files in root browser, or format in CWM, I get a success message, but when I reboot, everything is still there.
Click to expand...
Click to collapse
You should try Odin v.1.7, i never had problems with it.
Also, shut down KIES, it could be interfering.
Mashed_Potatoes said:
You should try Odin v.1.7, i never had problems with it.
Also, shut down KIES, it could be interfering.
Click to expand...
Click to collapse
tried that, still no luck.
is there any way to format /data or /system from a PC?
Do you have a backup? I ran into the same problem two months ago
Sent from my YP-G70 using xda app-developers app
no, but I actually got it working with the 3.0 kernel and CM10. Oddly enough, this is a lot more stable than all of the ICS releases were for me (it still hasn't crashed a single time). Now I just need microSD and music so my mp3 player will actually... you know... play music.
Anyhow, thanks everybody for helping me with this. I really do appreciate having a community like this around.
If you're running CM10, or any other ICS-based rom, you'll want to reflash your kernel before switching to a non-ics rom. That might be what caused your problem, even though you were trying to change to another ICS rom.
I wasn't trying to switch ROMs, I was reflashing the one I already had installed.
Sent from my YP-G70 using xda app-developers app
Related
Alright, I'll be brief with this...
Have stock Vibrant, OTA killed it, tried master reset, no help, tried Odin, FAILS on factoryfs.rfs, tried 4 other downloads of Odin stock rom, same problem. No SD card, no sim, nothing but phone, battery and usb.
Won't boot, won't turn on, just maybe the backlight turns on to no screen. Figured out how to get it into download mode still, but thats the only thing that I can do.
Now, is there a different ROM that I could use thats had more success? Am I doing something simple wrong? Forgetting something? Is there any help out there for this? Or is my phone just screwed?
Someone said removing the battery for about 1 or 2 minutes works
Did you try to odin the origonal stock firmware first?
Proudly pumped from my vibrating vibrant using the ubiquitous XDA App
It's been out for about 2 hours, so I'll give it a try like that....
No dice =/
Oh, didn't mention earlier, also tried the download with and without the battery, still fails at the same point.
fit333 said:
Did you try to odin the origonal stock firmware first?
Proudly pumped from my vibrating vibrant using the ubiquitous XDA App
Click to expand...
Click to collapse
Yeah, that's all I've been wanting to put back on, but that's the one that keeps failing on me. I', wondering if another Odin ROM might work
And I don't even get the screen anymore that is your avitar fit333
Mage42384 said:
Yeah, that's all I've been wanting to put back on, but that's the one that keeps failing on me. I', wondering if another Odin ROM might work
Click to expand...
Click to collapse
If you followed instructions it WILL flash after a posible fail or two
Proudly pumped from my vibrating vibrant using the ubiquitous XDA App
Mage42384 said:
And I don't even get the screen anymore that is your avitar fit333
Click to expand...
Click to collapse
Call it nostagia.. only the og rom did that, means your almost there. Lol
Proudly pumped from my vibrating vibrant using the ubiquitous XDA App
fit333 said:
If you followed instructions it WILL flash after a posible fail or two
Proudly pumped from my vibrating vibrant using the ubiquitous XDA App
Click to expand...
Click to collapse
I'll go step by step with what I'm doing, just to make sure.
1-load odin
2-plug usb into phone (no battery yet)
3-hold vol up/down, insert battery (only way i can get into dl mode now)
4-select pit and tar(phone) files in odin, make sure only reboot and time are checked
5-press start and be patient, lol.
Here is my report in Odin
<ID:0/008> File analysis..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> cache.rfs
<ID:0/008> modem.bin
<ID:0/008> factoryfs.rfs
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
fit333 said:
Call it nostagia.. only the og rom did that, means your almost there. Lol
Proudly pumped from my vibrating vibrant using the ubiquitous XDA App
Click to expand...
Click to collapse
Hahaha, I wish. That was what I had last night, no screen since.
Oh, and I've tried the update probably 20 times today in hopes, same thing everytime
Have you got odin 1.3 and have you tried eugenes froyo that dosnt brick, its worked magic for me in the past.
Proudly pumped from my vibrating vibrant using the ubiquitous XDA App
1.3 wouldn't work or recognize my phone at all, just using v1.00 that everybody else has been saying to use for it. I'll hunt down 1.3 right now and give that a shot.
Same thing... I'll try eugenes as soon as I get home and on a good connection. Would you be able to post a quick link to the thread with the one that didn't brick for you? Thanks (^_^)
Stick a incense stick beside it, and pray for miracle.
question, did you drop in water before? friend beside me is talking about taking it apart and putting it back together might work. we both fix computers hardware and software debuging.
problems like this, might also be hardware faultyness...just hope it is not that issue...
ekoandrew said:
Stick a incense stick beside it, and pray for miracle.
question, did you drop in water before? friend beside me is talking about taking it apart and putting it back together might work. we both fix computers hardware and software debuging.
problems like this, might also be hardware faultyness...just hope it is not that issue...
Click to expand...
Click to collapse
No water damage, and I've saved phones with it before. Using my storm2 now thanks to being able to pull things apart, lol.
But I was hoping it wouldn't come back as faulty hardware, but it's seeming that way to me =( Of course, I'm already waiting on tmobile for my replacement......I'm 31 on the list, lol, who knows when I'll get that phone...
What ROM are you trying to flash? Have you ever used it before? Could the file be corrupt?
mmas0n said:
What ROM are you trying to flash? Have you ever used it before? Could the file be corrupt?
Click to expand...
Click to collapse
I've downloaded from 5 different sources (at least) the stock 2.1 update 1 that's going around and seems to be working for everybody. I can't find any other rom that I can use with Odin, and I can't get into recovery to try adb (even though when I could, it wouldn't let me overwrite files on the phone)
Is there any other program I could use that utilizes download mode and standard dumps that are posted all over the place? Or is there a way to take those dumps and use them with Odin?
My wife's phone bricked on the OTA
I used this:
http://forum.xda-developers.com/showthread.php?t=803492
What seems different is the first flash (PART 1) with Original.tar I click repartition. That worked fine. Then in part two I didn't click repartition (as stated).
The download in the thread should have it all - including odin.
Also
http://ip208-100-42-21.static.xda-developers.com/showpost.php?p=8734955&postcount=4
Hey all. There's a lot knowledgeable folks around here, so I thought I'd see if I can get some help on my problem.
I've got a Galaxy Tab 10.1 Wifi (GT-P7510, non-branded, UEKME), that I rooted about two months ago, using the instructions found on the Android Forums (can't post a link, but ti's the basic easy way to root, using Odin3). Not a superuser, but wanted to be able to back up everything. Seemed easy enough and the rooting went fine.
Haven't done anything else to it, aside from installing a few run of the mill apps. It did auto-update a couple of times.
Was working fine, now it just got stuck on this screen with a message:
Code:
ODIN3 Download Mode
(Protocol v2.1)
Reason: No Kernal
Secure Mode: Secure
Check Signature: Check
Custom Binary Download: No (0 counts)
Custom Binary: Samsung Official
Waitting USB Cable...
Downloading...
Do not turn off target!!
Apparently, it went to this screen while I was away. I didn't see it until I picked it up and there it was. It comes to this screen after the Samsung title screen (not the animation) and a VERY quick screen with some red writing (goes by too fast to see what it says).
I tried to follow the original instructions again. Put the tab in download mode (power + volume down), open Odin3, select the md5, and hit start. Get a FAIL with this message:
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The screen on the tab updates with this:
Code:
WritePArtition: Error to NvStorMgrFileWrite![err:0x30000]
DownloadPartition_odin: Error to WritePartition![err:0x30000]
Tegra_Nand_Write: Error to DownloadPartition_odin![err:0x30000]
That's as far as I've gotten. I noticed the Re-Partition option is not checked in Odin3, and the errors on the tab have to do with partitions... but didn't want to do that if I could eff it up even more.
I'm also wondering if one of the auto-updates didn't muck up the works. Maybe messed with my bootloader? Again, didn't want to go doing dangerous things without some reassurance. Also, I can't get into recovery mode; it just kinda flashes when I hit the button and stays on the option screen for download/recovery.
Any direction on how to proceed?
Any advice would be so great. It's been like this for about a week and I can't find any help. Thanks everyone.
TL;DR: Stuck in Download Mode, get errors on re-root.
This helped me and I've seen it help many others too in similar situations. Since you're stuck in download mode already it might need to be adjusted and followed from somewhere other than the beginning.
Goto http://www.teamovercome.net/p7500/?page_id=5
Towards the bottom of the guide There is a section called Restocking yer system.
Follow that on down.
Make sure you use the files for you device (7500 or 7510).
Make sure you triple check that you follow everything as suggested. The most common one I see missed is the last step of doing a Wipe data/factory reset.
Let us know how it goes, as this keeps us trying to help when we know we're successful.
Sent from my GT-P7510 using XDA Premium HD app
You have an incomplete bootsector the bootloader is broken but ofcourse your recovery is safe. Just flash a stock firmware on top of it, or flash CWM. You don't have to worry about the options being checked as Odin 1.83 onwards fixes this issue.
Well, I was really hopeful when I read your response and read through the guide, but alas, I still got the FAIL when running Odin.
Aside from the rom, what else is there? I know of bootloaders, but not their function or how they work, and undersstand that loading the incorrect one (or incorrectly) can really make my tab a brick.
Are there any other suggestions?
Thanks for your help so far, maybe we can get this thing working. It's a shame - I've only had it for a couple of months...
Is there any other way to flash my firmware and/or repair my bootsector/bootloader?
Thanks for your help.
stusic said:
Well, I was really hopeful when I read your response and read through the guide, but alas, I still got the FAIL when running Odin.
Aside from the rom, what else is there? I know of bootloaders, but not their function or how they work, and undersstand that loading the incorrect one (or incorrectly) can really make my tab a brick.
Are there any other suggestions?
Thanks for your help so far, maybe we can get this thing working. It's a shame - I've only had it for a couple of months...
Click to expand...
Click to collapse
If you followed what I posted, and triple checked every step and check box in the guide was exactly what you did, then I'm lost for other suggestions. Misledz is on a different time than here, so you can either try my process again, if that's what you used, making sure you do evrything as said in the restocking yer system guide on down or wait for more help.
Yeah, I was hoping because it was a really well written guide with links to the correct files right there that I'd have some luck. The directions are pretty straightforward, so I don't think I missed anything, but I can certainly try again.
Thanks, I'll update in a bit.
I think I'm going to have to wait to see if Misledz has any other suggestions - I just tried it again and got the same fail.
stusic said:
I think I'm going to have to wait to see if Misledz has any other suggestions - I just tried it again and got the same fail.
Click to expand...
Click to collapse
Sorry that sucks.
Hope Misledz or someone comes along for you.
Best of luck.
Edit: Looking at the Odin repartition error makes me think it may be a full hardware failure issue. But there is still hope with the right files or method for it to be fixed.
I can't find it, but there was another thread here with the same "Reason: No Kernal" error and I think it turned out to be a hardware failure.
Sorry well yeah I've been on offset timezone's and I tend to check this section regularly as I hope to learn more about the tablet In hopes I can get some development done on it.
In the sense I'll assure you that you can't really brick the tablet as they are somewhat hard to brick via software, unless you install a firmware that isn't compatible (Like a 7500 on a 7510) or like wipe the bootloader. Put it this way anything done in download mode is safe.
Now to your query. It can't be a hardware issue because as you can see the tablet itself boots perfectly to Odin.
I would suggest skipping the v4 of CWM and flash the v5
[http://www.mediafire.com/?6c5tdmds927npdv]
and
http://www.teamovercome.net/p7500/wp-content/plugins/download-monitor/download.php?id=15
Normally errors like this occur only because of cases like ramdisk being different. One is the 5.1 and the other is the 5.5 version, I suggest it's best to try both. I feel you will have better luck testing both. No worries they are both safe and the 4.0.4 has some issues as far as some tablet's are concerned.
Misledz said:
Now to your query. It can't be a hardware issue because as you can see the tablet itself boots perfectly to Odin.
Click to expand...
Click to collapse
That's reassuring.
Misledz said:
I would suggest skipping the v4 of CWM and flash the v5
[http://www.mediafire.com/?6c5tdmds927npdv]
and
http://www.teamovercome.net/p7500/wp-content/plugins/download-monitor/download.php?id=15
Normally errors like this occur only because of cases like ramdisk being different. One is the 5.1 and the other is the 5.5 version, I suggest it's best to try both. I feel you will have better luck testing both. No worries they are both safe and the 4.0.4 has some issues as far as some tablet's are concerned.
Click to expand...
Click to collapse
I notice the second file is in a p7500 directory. I'm guessing this is an all-encompassing directory with p7500 and 7510 files?
EDIT: I see that the file is for all versions (75xx). Thanks.
I'm at work now, but I'll try it when I get home and give an update.
Thanks for taking the time to help me out.
*fingers crossed*
Dammit. No luck.
Did you already tried flashing with a pit file?
Flash with pit will rebuild your partitions.
When loading pit file repartition will automaticaly be select.
Do not repartion without pit file or your device will become abrick.
After flash with pit file you will see a lot of errors this is normal
And will be fixed after factory reset.
Good luck.
Sent from my GT-P7500 using xda premium
brieuwers said:
Did you already tried flashing with a pit file?
Flash with pit will rebuild your partitions.
When loading pit file repartition will automaticaly be select.
Do not repartion without pit file or your device will become abrick.
After flash with pit file you will see a lot of errors this is normal
And will be fixed after factory reset.
Good luck.
Sent from my GT-P7500 using xda premium
Click to expand...
Click to collapse
If you check out his screen shot posted above it shows he used a pit file at least in one attempt
He's still having issues so your help with this would be and is highly needed and appreciated.
Sent from my GT-P7510 using XDA Premium HD app
I've used the pit file and tar file from the guide that Benzoman directed me to. I also tried using the updated CWMs that were suggested (although a pit file wasn't included).
I had installed the windows drivers a while back, but just installed the Kies. Interestingly, after that, I tried flashing again and, although it still failed, it took a lot longer (as opposed to almost instantly). Almost thought I had it for a second...
Am I right in thinking that I can use the pit file from the guide and the tar file from CWM together?
Slightly off-topic; what's the purpose of flashing a bootloader? That's one thing I haven't tried yet.
Thank you for your continued help. I would have lost all hope by now if it weren't for you and this forum.
So is it all good? I don't tend to like leaving people who need help Especially when it's also educational for me.
Flashing a bootloader wouldn't be advisable cause it may really brick the tab.
You don't really need to pit file as it is used for repartioning, flashing just the PDA is good enough
Misledz said:
So is it all good?
Click to expand...
Click to collapse
No, it's still stuck. It seems like any pit file I try doesn't work, which was why I was asking about the bootloaders (I know it's dangerous, but for all intents and purposes, it's already bricked).
I don't know what else to do; I was hoping the updated CWM would help, but it runs into the same problem the other pda files have. I'd be more than happy to try any other suggestions you may have.
Thanks again.
I don't know if it's any help, but I was able to capture the really quick flash of red text as it boots. See attachment.
stusic said:
I don't know if it's any help, but I was able to capture the really quick flash of red text as it boots. See attachment.
Click to expand...
Click to collapse
Sorry over my head, but hopefully Someone will look at the error and know what's going on.
Sent from my GT-P7510 using XDA Premium HD app
Code:
[SIZE="1"][I]
post1
Hey guys... i have a big problem on my Samsung Galaxy S II (g)
(ive searched for an answer but I was not able to find one)
okay lets go:
[LIST]
[*]i have this phone now for 1/2 year i think.
[*]rooted
[*]android 4.0.3 with 3.0.8-TH
[email protected]
SMP PREEMPT kernel
[/LIST]
I've wiped my phone a month ago.
[LIST]
[*]now I have severe problems with the sound of my phone
it will lag every 1-3 secs with a shift from 0.5 sec~ (this is bad because I'm a music producer and need my phone!)
if my phone is charging, i can hear music without problems. i can't play games (I tried it, I normally do not play on mobile)
my soundcloud lags too, its not only a player problem.
[*]sometimes my phone freezes.. (before a wipe this happend 30-40 secs after reboot annoying)
[*]my cell phone simply reboots when it wants. quite annoying.
[/LIST]
i think its something with voltage distribution.
ive tried so much. wipe my phone several times, unroot, root again, fix permissions.. nothing worked
[LIST]
[*]calls are unaffected
[*]sometimes if i want to hear music, and the screen is off, the lags are gone.. sometimes
[/LIST]
pls help. i need my phone, do you guys have any ideas?!
edit:
sorry if the english is not pefect, im german :/
--------------------------------------
post2
now i have some more problems
[LIST]
[*]sometimes the "loading" sound play randomly
[*]the lock screen sound comes 2 secs later
[*]i cant connect my phone via usbconnection (in settings) to my computer, it says "usb connected please disconnect" after a fresh restart same problem. (without connect before)
[*]my phone freezes more often
[/LIST]
i cant do anything.. wipe my phone will end in the same problems
wipe dalvik cache too..
it worked for some month before with the same settings...
something with my permissions wrong?
[/I][/SIZE]
Small Text is already fixed.. thanx guys
I search a Rooted kernel for my i9100g
already tried and doesnt work with:
CWM-R (via odin) + root.zip/SU-BB.zip // causes bootloop
Philz CWM root pacakge for Galaxy S2 // does not work causes bootloop
Siyah-s2-v6.0b4 // does not work too and causes bootloop too
found a working root with stock recovery
http://forum.xda-developers.com/showthread.php?t=2065581
back to my problems..
still have soundlags in my entire system..
cant hear music. cant watch videos... the bootanimation-sound lags too..
i still think this is something with my permissions.. are permissions wiped too? or are they on the phone alone ( i mean how much voltage for cpu or stuff like this)
dunno how to delete copied this post in my 1.
Oh guys pls. I wrote so much informations down and got no answersm other ppl here just wrote "my phone stops working" and got 10 answers. Pls.
I need help!!
Do a completely clean install of the rom you're using (no restoring apps initially), then reinstall/restore apps a couple at a time to rule in/out something like that as a cause. Setups sometime go wonky after a couple of months, I normally do a clean install every 3 mths or so if I stick with one rom to avoid the type of thing you're talking about. It's time well spent.
If the problem persists, do a completely clean install of a stock rom, again reinstall/restore a couple of apps at a time. See how that goes.
"now a bootloop"
MistahBungle said:
Do a completely clean install of the rom you're using (no restoring apps initially), then reinstall/restore apps a couple at a time to rule in/out something like that as a cause. Setups sometime go wonky after a couple of months, I normally do a clean install every 3 mths or so if I stick with one rom to avoid the type of thing you're talking about. It's time well spent.
If the problem persists, do a completely clean install of a stock rom, again reinstall/restore a couple of apps at a time. See how that goes.
Click to expand...
Click to collapse
hey dude.. thanx for your post.
i have no a complete bootloop.. cant fix it myself..
tried with clean install of
"I9100GXXLSR_I9100GXXLSP_I9100GDBTLS1_HOME.tar"
from sammobile
(gt 9100 g 4.1.2 android)
nothing happend.. after the first failed try to fix my loop (i accidently used the gt9100 ics it softbroked my phone with the message "use kies to retry blablabla")
now it worked...
after that it configured android normal.. than bootloop..
what can i do now?
edit:
ssn: I9100GGSMH
cant find a bootloader.. can i use a other one?
here http://forum.xda-developers.com/showthread.php?t=1754158
hmh.. anyway.. downloads are down..
last odin flash:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GXXLSR_I9100GXXLSP_I9100GDBTLS1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.img
<ID:0/005> NAND Write Start!!
<ID:0/005> factoryfs.img
<ID:0/005> hidden.img
<ID:0/005> MLO
<ID:0/005> modem.bin
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> zImage
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!
edit edit edit edit edit xD:
reset the flashcounter and try to tell the shop that this happend after the last OTA update? xD
worked one time for a broken nokia n95 long time ago (uff i think it was a n95)
Yes, you could reset the flash counter & send it in for warranty service. However, all they'll likely do is wipe the phone & put the latest stock firmware they have on it. Which might fix the problem. Or it might not. But there's nothing to suggest it's a hardware problem.
I'm not sure why you'd flash a bootloader ? You only flash bootloaders if you have a specific reason for doing so I.E rom you're running won't boot without running a particular bootloader (I'm still running old GB bootloader, never had a problem running any ICS rom with it). I don't know if you can use that bootloader or not; I'm not familiar with what bootloaders work with which roms on the I9100G.
When you were using CM9, did you ever use Rom Manager ? That would explain the bootloop you were having at that time; Rom Manager is notorious for causing bootloops/breaking recovery with Samsung devices.
Honestly, if it were me (tho I have an I9100), I'd root the phone (flash a rooted kernel with CWM), format cache, data, system in CWRecovery then Odin flash a stock rom, tho this may not necessarily be the way to go with an I9100G. Wait & see if someone with an I9100G reads your thread & might have seen this problem before.
MistahBungle said:
Yes, you could reset the flash counter & send it in for warranty service. However, all they'll likely do is wipe the phone & put the latest stock firmware they have on it. Which might fix the problem. Or it might not. But there's nothing to suggest it's a hardware problem.
I'm not sure why you'd flash a bootloader ? You only flash bootloaders if you have a specific reason for doing so I.E rom you're running won't boot without running a particular bootloader (I'm still running old GB bootloader, never had a problem running any ICS rom with it). I don't know if you can use that bootloader or not; I'm not familiar with what bootloaders work with which roms on the I9100G.
When you were using CM9, did you ever use Rom Manager ? That would explain the bootloop you were having at that time; Rom Manager is notorious for causing bootloops/breaking recovery with Samsung devices.
Honestly, if it were me (tho I have an I9100), I'd root the phone (flash a rooted kernel with CWM), format cache, data, system in CWRecovery then Odin flash a stock rom, tho this may not necessarily be the way to go with an I9100G. Wait & see if someone with an I9100G reads your thread & might have seen this problem before.
Click to expand...
Click to collapse
hmh.. okay.. let my try to explaine.. im german and my schoolenglish isnt the best.. but yeah:
ive download the latest ics rom from sammobile for germany and my phone.. didtn work.. exactly same problem as before.. it will start booting.. and loop in the "samsung gs2" screen.
ive used cm9 on my old droidX but not on this phone.. the only thing ive used was 4.0.1 i think before it was in germany..(french rom) with root and cwm recovery.
someday it start lagging.. if i hear music with screen on it will lagg horrible..
it starts to play the "loading" sound randomly..
it starts also to reboot if it want to.
after all of that (the problems if tried to explain in the first post) i tried to wipe my data.. it worked.. but the problems was still there..
today my phone just turned of like everyday 40 times.. and stucked on the boot screen..
now ive flashed my phone with the newest ICS (4.1.2) with succeed (2 times) but it wont start..
ive tried to flash the kernel alone.. still same problem.
oh man.. this is my nightmare.. im a musician.. i need my phone to hear my music or bring it to friends who play my music in the clubs, call with important ppl.. (play thats not sooo important.. i have still a usb drive)
i need my phone
hmh.. maybe you can give it a look with teamviewer (maybe skype to talk) and my cam pointed on my phone.
if you want.
anyway. thanks for your help.
i hate my edits:
i try now your last sentence..
sorry.. overread it
okay ive tried it...
now there is a other bootscreen.. after that samsung gs2 comes a configuating android (normal) and a only "samsung" screen
now after 5 minutes of waiting (jeah i can wait a long time xD)
theres "installing applications"
it works..
finaly.. THANKS!
i love you..
it didnt worked with only ICS.. but with CWM.. nice..
i hope the problems are gone..
if it is so.. i will mark this thread as solved..
thanks again.
edit:
it look like it worked... so.. i will mark this as solved.. but pls.. dont close it.. i will test it for 2-3 days.. after that i want be able to change the prefix
Glad you got it working, good job persevering/not giving up on it & fixing it yourself Mods won't close the thread unless you ask them to, so yeah, test it out for a bit, and if you have further problems post to this thread again.
MistahBungle said:
Glad you got it working, good job persevering/not giving up on it & fixing it yourself Mods won't close the thread unless you ask them to, so yeah, test it out for a bit, and if you have further problems post to this thread again.
Click to expand...
Click to collapse
oh thats nice.. okay..
so.. i cant root now.. haha
its an old problem that i had before.. but i dont know how to fix it now.. i dont find anything about it..
did you know how?
i have the root.zip and a superuser/busybox zip... dosnt working both.. telling me that its not verified..
this is now so dumb.. xD
edit:
ah.. i cant install CWM.. after that i cant boot.. and im back in my lovely bootloop..
Aren't there rooted kernels you can flash for the I9100G rather than having to mess around with flashing multiple files ? (I don't know because I don't have an I9100G).
MistahBungle said:
Aren't there rooted kernels you can flash for the I9100G rather than having to mess around with flashing multiple files ? (I don't know because I don't have an I9100G).
Click to expand...
Click to collapse
i only find this:
http://forum.xda-developers.com/showthread.php?t=1631934
cant find a cooked kernel grr..
maybe a 4.1.2. android rom with build in cwm?
is there anything like that?
would be amazing if you could help me..
its hard to find as a german hahaha
all i find is just the cwm standalone
edit:
Philz CWM root pacakge for Galaxy S2 // does not work
Siyah-s2-v6.0b4 // does not work too
Try this thread, found it in my bookmarks from > 12 mths ago. Not sure if there's any current kernels you can use, ask in the thread.
Edit - And be careful, don't flash a I9100 kernel to your phone (check thoroughly, if in doubt, don't flash) or you'll end up back at square one.
RedRaw said:
would be amazing if you could help me..
its hard to find as a german hahaha
all i find is just the cwm standalone
edit:
Philz CWM root pacakge for Galaxy S2 // does not work
Siyah-s2-v6.0b4 // does not work too
Click to expand...
Click to collapse
hmh.. cant write in this forum.. damn. have not the permission.
but thanks dude... thanks for your help and for your ideas and to poke me right to the soluton haha
You're welcome Good luck. Maybe change the title of your thread & include I9100G in it & you might find people who can help will read it.
MistahBungle said:
You're welcome Good luck. Maybe change the title of your thread & include I9100G in it & you might find peopxle who can help will read it.
Click to expand...
Click to collapse
Done but my soundproblems are back.
I think its the permissions.
Is there a way to reset my permissions or that someone with "stock-permissions" can send me his?
I had permission denied pro installed before it start like this (found out after a long time of thinking)
It tried to fix permissions without asking me. And after a hour i think or 30 minuts my phone reboots. I think it "crashed"
I Would try to fix this through fixing again my permissions via permissions denied pro. But i cat root my phone. (Causes bootloop with 3 methods i tried all in my first post)
This is killing me
Edit:
Found a working root
I will post the link later.im on my phone.
But permission denied pro does nothing. Just scan my device an finished. Im confused.
Someone here with 9100g and rom toolbox pro?
Need the build.prop and kerneltweaks (if not changed) to compare
Would be awesome
Someone?
Hi everyone.
It's now been a few days that my I9100G is down. I've tried severals things found online : using a .pit file alone then flashing the firmware alone, .pit and firmware at the same time, using severals differents firware package, changing my cable, changing the USB port used, yes kies is closed, yes I've reinstalled the drivers.
I didn't tried with a x86 computer yet but I will this afternoon.
The symptoms
- Boot stuck on the logo.
- Recovery mode unavailable (I press the three buttons, I release them when the logo appear nad nothing more happend).
- Download more available.
What happends:
One day my phone suddently restart on his own. It happends to me. but when it start it was asking me to enter a password to decrypt it... but I don't remember having set this thing (and it's the first time it ever ask me that, even after a lot of reboots).
So, since I'm rooted and with CWM I boot into recovery and try a wipe. But since I don't want to lose everything I first try just a cache wipe. Then the problems started :
- after a first reboot, and since the wipe didn't changed anything, I tried to enter again in the recovery, but I get an error message (I don't remember which, I think it was something like an impossibility to mount some storage) and I get kicked off the recovery mode.
- I try to flash again a version of CWM for the I9100G.
- I can't enter at all in recovery mode anymore
- I try a full reinstalation using a all-in-one package of the firmware. It failed a different places:
- I9100GXXLSR_I9100GXXLSP_I9100GXEFLSR_HOME.tar.md5 usually fail during factoryfs.img
- I9100GXXKL5_I9100GXEFKL3_I9100GXXKL4_HOME.tar.md5 usually fail during modem.img
I start to run out of solutions and I'm in a great need of help now, I've tried all I could on my own.
Here is a bit of log from my last try with Odin :
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GXXKL5_I9100GXEFKL3_I9100GXXKL4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> cache.img
<ID:0/010> NAND Write Start!!
<ID:0/010> factoryfs.img
<ID:0/010> hidden.img
<ID:0/010> MLO
<ID:0/010> modem.bin
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
Click to expand...
Click to collapse
thanks for reading
PS : I don't know if it's normal but I've flashed a couple time before and it never was awefuly long, here each tried take at least 1h-1h30. I would like to know if that's normal ^^
What exactly do you mean by that ?
Edit - Two things come to mind given the stages the flashes have been failing at; bad downloads & something PC side - temporary break in connection b/w phone & PC but not long enough for the PC OS to register, or dodgy USB ports. But that may/may not be ruled out depending on your answer to the above question.
NejaaHal said:
I didn't tried with a x86 computer yet but I will this afternoon.
Click to expand...
Click to collapse
MistahBungle said:
What exactly do you mean by that ?
Click to expand...
Click to collapse
I mean that my computer is running a 64bit OS (windows 7). I will get a computer running a 32bit OS this afternoon (maybe Odin don't like being run on a 64 bit environement <.<
MistahBungle said:
Edit - Two things come to mind given the stages the flashes have been failing at; bad downloads & something PC side - temporary break in connection b/w phone & PC but not long enough for the PC OS to register, or dodgy USB ports. But that may/may not be ruled out depending on your answer to the above question.
Click to expand...
Click to collapse
Bad downloads : maybe, but that would mean that the 3 or 4 differents downloads I did (because I thought of that possibility and I've tried to re-download the roms) all were corrupted at some point ^^'
Connection problem : maybe too, but (yeah again a but) I don't touch my computer at all during the process expeciallt to avoid the connexion to be broke.
PS : all my .tar.md5 archives gives me the "error" "There is no correct records at the end of archive" when I check them with 7-zip
Ahhh OK. Win7 x64 wouldn't normally be an issue. Trying a 32 bit OS more than likely won't give you any different result on the same machine. Given everything you've already tried, you need to try a different machine. And if it were me, I'd try more than one, because the alternative is giving up & paying someone to fix it.
The error you get with 7Zip is normal for stock roms & doesn't affect anything, but very good idea to try checking the integrity of the download though. Try checking the zip before you unzip the tar.md5. If it says files are missing/broken, there's your problem. If not, go with trying on another machine. Also, search for Hopper8's "Odin troubleshooting' thread. As thorough as you've been to this point (and you have been very thorough), there might be something relatively minor mentioned in his thread that you may not have tried.
MistahBungle said:
Ahhh OK. Win7 x64 wouldn't normally be an issue. Trying a 32 bit OS more than likely won't give you any different result on the same machine. Given everything you've already tried, you need to try a different machine. And if it were me, I'd try more than one, because the alternative is giving up & paying someone to fix it.
The error you get with 7Zip is normal for stock roms & doesn't affect anything, but very good idea to try checking the integrity of the download though. Try checking the zip before you unzip the tar.md5. If it says files are missing/broken, there's your problem. If not, go with trying on another machine. Also, search for Hopper8's "Odin troubleshooting' thread. As thorough as you've been to this point (and you have been very thorough), there might be something relatively minor mentioned in his thread that you may not have tried.
Click to expand...
Click to collapse
Yeah, I ment to use another computer ^^ I'm trying right now. Can you confirm me that a flashing can take one hour or more? (I'm not used to that amount of time)
And yeah, I don't want to give up and pay someone to do something I could do. I'm not a newbie in IT stuff, (even if I don't really know the architecture of an android phone and I don't know the use of the differents files in a rom).
7zip tell me that everything is ok about the downloaded .zip.
Thanks for the tip, I'm going to read that thread
No, a stock rom flash on the S2 should only take a couple of minutes tops. Normally in these situations, as long as you have download mode you can recover it, unless the NAND is messed up, then it's a JTAG (not always possible though) or in many cases a motherboard replacement. But forget that for now & only worry about that when you reach the end of the line so far as stuff you can try goes.
OK. So we can rule out bad download plus pretty much all the other stuff you've tried so far. Try on another machine & read his thread to make doubly sure there's not something really small/obvious we're both missing here.
ok, The ROM I've took come from sammobile so I guess it shouldn't take that amound of time.
That's factoryfs.img that take the most of the time ^^
I just realized that I forgot to launch Odin as administrator with windows 7 (my current try is on a x86 windows XP). But my previous (successfull ) flashes were like that too ^^'
I will continue to try on that other computer, but that will take some time to try all ports (since there is roughly 1h-1h30 to try to flash + the time for a full recharge of the battery <.<)
After having read a couple of threads here I realized that I took a .pit file from somewhere but haven't followed the step there :
[Fix] [Guide] [For Noobs] Recover from Corrupted Memory[USE EXTREME CAUTION]
But since I still not know how is organized an android phone I don't know if I've just used a generic thing that have just done nothing or if I could have messed up something. The file have this name : omap4_all_20110627_emmc.pit
I'm sorry for the double post : this is an update
The first try failed during factoryfs.img. I'm currently charging the phone for a next try.
So far I've tried
- I9100GXXLB1_I9100GATOKL1_ATO
- I9100GXXLSR_I9100GXEFLSR_XEF
- I9100GXXKL5_I9100GXEFKL3_XEF
Would anyone have any idea of which other rom I could try?
Shouldn't make any difference which rom you use, as long as it's an I9100G rom. Try every stock rom you're physically able to download; Sometimes with these situations you could try 10 flashes and they all fail, yet for whatever reason the 11th works. If I had a dollar for every occasion I've seen that happen on here over the past ~2 yrs, I'd have a fair bit of money - it's not super common, but it's not unheard of either.
So keep at it, perseverance might just recover it when trying every single thing you/everyone else on here can think of won't.
Okay, I'll keep going then ^^ may a custom rom work better?
I still don't understand why it take so much time ^^'
My guess is....at this point, you probably don't have root access, so a custom rom probably won't flash (can you even get into recovery mode?)
Read hopper8s guide and look for the link to the 3 part or test firmware. Most (if not all) single file firmwares simply overwrite what is already installed.....the test firmware will wipe the previous install and allow you to clean flash the firmware.....it *might* work where other firmwares haven't.......
Sent from my GT-I9100 using xda app-developers app
---------- Post added at 06:36 PM ---------- Previous post was at 06:18 PM ----------
Edit
Forget about the test firmware until you can be sure it's compatiable with the i9100G.....
Sent from my GT-I9100 using xda app-developers app
keithross39 said:
My guess is....at this point, you probably don't have root access, so a custom rom probably won't flash (can you even get into recovery mode?)
Read hopper8s guide and look for the link to the 3 part or test firmware. Most (if not all) single file firmwares simply overwrite what is already installed.....the test firmware will wipe the previous install and allow you to clean flash the firmware.....it *might* work where other firmwares haven't.......
Sent from my GT-I9100 using xda app-developers app
---------- Post added at 06:36 PM ---------- Previous post was at 06:18 PM ----------
Edit
Forget about the test firmware until you can be sure it's compatiable with the i9100G.....
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
No, as I said in my first post I can't access the recovery mode. or I don't do it correctly or it don't work anymore.
Hummm ok I will wait about the test firmware ^^' what could happend if it is not compatible?
I'm a little lost into the amount of rom available. Should I only try official roms? could I try other ones, if yes, which ones?
The worst part is that I don't remember which version was running on my phone. I was rooted, up to date I think, but that's all I remember, and I always see "only use this rom with a x.x.x rom" so <.<
also, after having tried so much time to reinstall it, does the indication "only use this rom with a x.x.x rom" still apply?
It doesn't matter which stock firmware you flash/whether it's specifically for your carrier or not. The aim is to get the phone working normally, so any stock I9100G firmware will do.
The suggestion to try a 3 part firmware is a good one, but I honestly don't know if there is such a thing for the I9100G as there is for the I9100.
You really need to start trying with a different PC and more than one if you can, because the alternative involves paying a Samsung service centre a not insignificant sum of money to fix your phone.
Done some google searching and it seems that there is no test firmware for your phone.....I WOULDN'T recommend using the one linked to in hopper8s thread.....the hardware in the phones (specifically the chipsets) are different......you'd probably kill your phone if you used it.
Below is a link to the latest firmware for your phone...
http://hotfile.com/dl/193267715/c98...GT-I9100G-XEF-I9100GXXLSR-1359122020.zip.html
Sent from my GT-I9100 using xda app-developers app
Thanks for all your answers.
I will then continue to try severals computers and severals roms.
I still wonder one thing :
would it be possible to install all the different parts separately? it always fail at the same step, is it possible to install the different parte one after the other? that would avoid me to have to wait 2h between two tries ^^
Also I wonder : what is the use of the .dll file I always find in the .zip ?
Edit : I just noticed something; in the latest version of Odin there is a option called "NAND erase all". would it be a good alternative to the 3-part test firmware?
I hate to do that but : little up about my last questions ^^'
NejaaHal said:
Hi everyone.
It's now been a few days that my I9100G is down. I've tried severals things found online : using a .pit file alone then flashing the firmware alone, .pit and firmware at the same time, using severals differents firware package, changing my cable, changing the USB port used, yes kies is closed, yes I've reinstalled the drivers.
I didn't tried with a x86 computer yet but I will this afternoon.
The symptoms
- Boot stuck on the logo.
- Recovery mode unavailable (I press the three buttons, I release them when the logo appear nad nothing more happend).
- Download more available.
What happends:
One day my phone suddently restart on his own. It happends to me. but when it start it was asking me to enter a password to decrypt it... but I don't remember having set this thing (and it's the first time it ever ask me that, even after a lot of reboots).
So, since I'm rooted and with CWM I boot into recovery and try a wipe. But since I don't want to lose everything I first try just a cache wipe. Then the problems started :
- after a first reboot, and since the wipe didn't changed anything, I tried to enter again in the recovery, but I get an error message (I don't remember which, I think it was something like an impossibility to mount some storage) and I get kicked off the recovery mode.
- I try to flash again a version of CWM for the I9100G.
- I can't enter at all in recovery mode anymore
- I try a full reinstalation using a all-in-one package of the firmware. It failed a different places:
- I9100GXXLSR_I9100GXXLSP_I9100GXEFLSR_HOME.tar.md5 usually fail during factoryfs.img
- I9100GXXKL5_I9100GXEFKL3_I9100GXXKL4_HOME.tar.md5 usually fail during modem.img
I start to run out of solutions and I'm in a great need of help now, I've tried all I could on my own.
Here is a bit of log from my last try with Odin :
thanks for reading
PS : I don't know if it's normal but I've flashed a couple time before and it never was awefuly long, here each tried take at least 1h-1h30. I would like to know if that's normal ^^
Click to expand...
Click to collapse
No, thats definitely not normal, I have an i9100 and it has never taken longer than a few mins to flash via odin. I did make the mistake once of trying to flash my wifes i9100 which i assumed was an i9100g because it was white, might be not applicable to you, but it may be worth checking you have an i9100g not an i9100 - just look under your battery!
Good luck.
Jimsilver73 said:
No, thats definitely not normal, I have an i9100 and it has never taken longer than a few mins to flash via odin. I did make the mistake once of trying to flash my wifes i9100 which i assumed was an i9100g because it was white, might be not applicable to you, but it may be worth checking you have an i9100g not an i9100 - just look under your battery!
Good luck.
Click to expand...
Click to collapse
Thanks ^^ but I am completly absolutely sure I have a i9100G ^^ because I already had problems before to find a way to root my phone ^^ and it say I9100G on the phone ;p I even tried to change it for a normal i9100 at the store I bought it but they told me they only had that version^^
Edit / news: I've tried to flash some part separately (from here :
[COLLECTIONS][MIRROR] Official Firmwares, Kernels, Modems, Bootloaders ). the bootloader don't fail, the kernel don't fail but the modem always fail while writing (now writing [...] -> blank line -> Received response from LOKE -> fail)
I don't know what to do now <.<
New question : have anyone any solution to allow me to have at least access to the recovery? is there any way to flash only the recovery? I made a lot of searches but couldn't find anything :/
If you can flash a custom kernel, you'll get (usually) CWM recovery.......then at that point you can do the full range of wipes and in theory flash custom roms.....
Sent from my GT-I9100 using xda app-developers app
Hello gentlemen, here I am asking for help.
After trying different ROMs, I decided to go back to stock because of the frequent reboots. Today, after a few days since stock, all of a sudden the phone reboots itself and gets stuck on the Galaxy S3 logo (not bootloop). Opening recovery leads to a list of errors similar to this post, if not identical. Alas, being the d***head I am, i didn't backup EFS or system, or at least I don't know where did i put them lol
@xDave7: make shure that the downloaded firmware is correct, and flash it with Odin. Then boot into recovery and do a FactoryReset. If system still won't boot, flash a 3part-rescue-firmware with PIT-file to repartition.
rp158 said:
@xDave7: make shure that the downloaded firmware is correct, and flash it with Odin. Then boot into recovery and do a FactoryReset. If system still won't boot, flash a 3part-rescue-firmware with PIT-file to repartition.
Click to expand...
Click to collapse
Failed, here's the log
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Btw, the firmware I tried to flash was the one Kies gave me, then I downloaded it from sammobile. But since it didn't work out, could you explain me the second method, or link me a guide? Thank you
OP, your eMMC (your phone's, actually) might be on its way to the garbage - and might not. The problem is that if it is - it takes the whole phone with it.
I'd suggest going into the recovery and trying to mount the phone to PC and downloading everything you can - if you can - before doing anything else.
After that, repartition FW + PIT, and if it fails - try working from a different PC. If it fails from any PC when trying to write eMMC - well, then you probably need to buy a new phone.
Repartitioning FW:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
or
http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
Hey @Jack_R1, thanks for your answer. Before I proceed with one of those guides, what do you mean with:
Jack_R1 said:
I'd suggest going into the recovery and trying to mount the phone to PC and downloading everything you can - if you can - before doing anything else.
Click to expand...
Click to collapse
because I think I don't get what you mean
He means adb pull, search for how to use it. But you'll probably find all your data is gone anyhow.
boomboomer said:
He means adb pull, search for how to use it. But you'll probably find all your data is gone anyhow.
Click to expand...
Click to collapse
@boomboomer so is this to save files like pictures, music, videos, etc...? Because if that's the case, it doesn't matter really that much, the important matter is to make this phone work again. So, is there anything else I need to know before going with those guides?
Other that you'll probably need to buy a new phone, no.
boomboomer said:
Other that you'll probably need to buy a new phone, no.
Click to expand...
Click to collapse
Well, that's encouraging lol just out of curiosity, is there a reason becuase it stopped working all of a sudden and ****ed itself up so badly?
Nand memory wear.
Flash an official cwm or stock recovery.
Sent from a stolen phone!