So my charger recently came into contact with a liquid, and without knowing this, i plugged it into my phone and completely screwed up my phone. It no longer connects to the computer and the battery indicator stays at 100% all the time. So my first question is if there is any warranty with samsung, and if there is, how can i unroot my phone without hooking it up to the computer?
I think there's a very good chance mobile odin pro could be your answer.
First, make sure you're on a rom that is compatible with the stock kernel, then flash stock kernel. This will remove cwm. So if you're running an incompatible rom, like cm7, then flash the stock kernel, you'll be screwed.
Once you have the stock kernel flashed, then flash the pda.tar that is stock unrooted.
Should be 100% stock. For good measure boot into recovery (yes, stock recovery) and wipe the phone. If at any point your phone doesn't boot properly, boot into recovery and wipe the phone.
That should all be possible without using a computer. Hopefully your battery is still charging. DO NOT ATTEMPT WITH LOW BATTERY, it's just not worth it.
Sent from my páhhōniē
Looking for a little feed back on this process - can anyone confirm that this works?
Also, anyone that has gotten a warranty replacement - Did your replacement come with 2.34 or 2.36 - I thought I read that 2.36 was still UN-rootable at this point in time.
Basically - My phone seems to be charging OK, but it will not connect to a PC at all - three different PC's - three different usb cables - three different ROMs/kernels. I am well within my one year warranty (obviously) so I feel it would be a good idea to get the process going rather than it stop working to the point where it wont even take a charge.
Thanks you in advance for anyone's help.
dschreiber69 said:
Looking for a little feed back on this process - can anyone confirm that this works?
Also, anyone that has gotten a warranty replacement - Did your replacement come with 2.34 or 2.36 - I thought I read that 2.36 was still UN-rootable at this point in time.
Basically - My phone seems to be charging OK, but it will not connect to a PC at all - three different PC's - three different usb cables - three different ROMs/kernels. I am well within my one year warranty (obviously) so I feel it would be a good idea to get the process going rather than it stop working to the point where it wont even take a charge.
Thanks you in advance for anyone's help.
Click to expand...
Click to collapse
You should be able to return your phone to stock with Mobile Odin. I havn't personally tested it, but it's designed to flash full firmwares. If you use the lite version, you need to install the supplementary library (flash kernel) manually. You need to be rooted to use Mobile Odin. I would use the One-Click downloader from the prepare your phone to return to the store or for warranty repair thread. Mobile Odin will read from the one-click exe file. Once you run it, you will no longer be rooted. You should then do a wipe data/factory reset and maybe a reformat.
So far, I havn't seen anyone report that they received a phone with 2.3.6 loaded on it. I think we will hear about it fairly soon when it starts happening.
You can root 2.3.6 but not with every method. There is a uckk6 plus root available from Entropy512. But it's probably best to use 2.3.4 if you want to stay on stock, since with UCKK6 bthid doesn't work, and it has the wifi battery drain bug, as well as some other minor problems.
creepyncrawly said:
You should be able to return your phone to stock with Mobile Odin. I havn't personally tested it, but it's designed to flash full firmwares. If you use the lite version, you need to install the supplementary library (flash kernel) manually. You need to be rooted to use Mobile Odin. I would use the One-Click downloader from the prepare your phone to return to the store or for warranty repair thread. Mobile Odin will read from the one-click exe file. Once you run it, you will no longer be rooted. You should then do a wipe data/factory reset and maybe a reformat.
So far, I havn't seen anyone report that they received a phone with 2.3.6 loaded on it. I think we will hear about it fairly soon when it starts happening.
You can root 2.3.6 but not with every method. There is a uckk6 plus root available from Entropy512. But it's probably best to use 2.3.4 if you want to stay on stock, since with UCKK6 bthid doesn't work, and it has the wifi battery drain bug, as well as some other minor problems.
Click to expand...
Click to collapse
Thanks for the reply....
Does odin read the .exe file wirelessly? Seeing as my usb port will not function do I use this file (StockKernel-PDA.tar) to reset the flash counter?
Thank you so much for your help!
dschreiber69 said:
Thanks for the reply....
Does odin read the .exe file wirelessly? Seeing as my usb port will not function do I use this file (StockKernel-PDA.tar) to reset the flash counter?
Thank you so much for your help!
Click to expand...
Click to collapse
Sounds like you also need to do some more reading. The only thing that will reset the flash counter is a jig. See my guide on preparing the phone to return to the store for more detailed information.
Mobile Odin is programmed to read from tar files, from one-click downloader executable files, and also recognizes the individual components such as zImage, factoryfs.img, boot.bin, etc.
Download the file directly to your phone sdcard (internal or external will work) and then select it in Mobile Odin.
creepyncrawly said:
Sounds like you also need to do some more reading. The only thing that will reset the flash counter is a jig. See my guide on preparing the phone to return to the store for more detailed information.
Mobile Odin is programmed to read from tar files, from one-click downloader executable files, and also recognizes the individual components such as zImage, factoryfs.img, boot.bin, etc.
Download the file directly to your phone sdcard (internal or external will work) and then select it in Mobile Odin.
Click to expand...
Click to collapse
Maybe I misinterpreted this quote:
"In addition, he posted an Odin-flashable tar package for just the stock kernel, for those who want to do a ! removal. I have mirrored the file (I don't trust Dropbox for long-term hosting) at http://www.multiupload.com/MD7SMMNG24 - his original post is at http://forum.xda-developers.com/show...&postcount=174"
I guess I assumed when he said remove "!" he meant resetting the flash counter. I will re-read the post for a third time - maybe I missed something.
dschreiber69 said:
Maybe I misinterpreted this quote:
"In addition, he posted an Odin-flashable tar package for just the stock kernel, for those who want to do a ! removal. I have mirrored the file (I don't trust Dropbox for long-term hosting) at http://www.multiupload.com/MD7SMMNG24 - his original post is at http://forum.xda-developers.com/show...&postcount=174"
I guess I assumed when he said remove "!" he meant resetting the flash counter. I will re-read the post for a third time - maybe I missed something.
Click to expand...
Click to collapse
Flashing a stock kernel will remove the yellow warning triangle and I9100 logo from the initial boot screen. It will not however reset the flash counter. Only the jig will do that.
creepyncrawly said:
Flashing a stock kernel will remove the yellow warning triangle and I9100 logo from the initial boot screen. It will not however reset the flash counter. Only the jig will do that.
Click to expand...
Click to collapse
So since my usb port does not work, I would not be able to use a JIG, I would be wasting my time cause they will see the tripped flash counter, right?
Sorry for beating this to death... rather than possibly mess my phone up even more I should just leave it and deal with it?
You will be unable to reset the flash counter. You will be able to remove the warning that occurs on bootup. You should flash back to stock UCKH7. There is little or not risk in doing so, because you will not be flashing bootloaders or anything else that could bork the phone. Mobile Odin refuses to flash those types of files, and anyway the package does not contain them.
I have never seen anyone report that they were refused warranty due to the flash counter. That doesn't mean it has never happened, of course, but it is somewhat of an indication that it might go by without being seen. On the other hand, several people have reported that they returned their phones to a store for exchange or warranty (first 30 days I think) and the phone was never even turned on. Some have said that they returned it with a custom rom installed, with the flash counter incremented, or even with the yellow warning triangle not removed. Even if someone does turn the phone on, as long as it boots up normally, it seems very unlikely that they would check the flash counter. This would be true for an AT&T service center as well as any store.
That being said, I don't know what will happen if you do the warranty over the phone and then return the phone via ups or fed ex. I think it is highly likely that you would be safe even there. But this is just my opinion. I don't think most of these employees really want to screw customers, and if the hardware is actually faulty, they should replace it regardless. The problem you have could not be from flashing custom software anyway.
If it was my phone, I think I would take it to an AT&T service center, even though the closest one to me is about a 2 hour round trip.
Right on. If you're going to listen to someone, listen to creepyncrawly's directions.
Sent from my páhhōniē
Well I may not be out of luck after all. Figuring I had nothing to loose... I removed my battery - took a Qtip and shaved it down - dipped it in some alcohol and rubbed it around inside the USB connector. I let it dry for about 20 minutes - fired it back up and BAM! Connected to my PC instantly!
I went ahead and ordered a JIG so that in the event that I do actually have to do an exchange I will have no worries.
Related
I got my S2 only a few days ago from Vodafone UK and quickly flashed to the latest Checkrom to get rid of the stock bloatware. After suffering severe battery drain to do with wifi i have flashed back to the stock carrier firmware (BUKJ3).
I did this first by using CWM to clear davlik cache and a full wipe and then after enabling USB debugging mode i rebooted into downloaded mode. Upon entering download mode the phone began to make an audible clicking noise which i dont remember it ever doing when i first rooted the phone.
I went ahead and flash the firmware and all seems well but i wanted to see if the clicking noise might indicate a fault with the phone?
One other thing, if i wanted to return the phone back to Vodafone would i need to reset the binary counter thingy even though i'm back on stock firmware? The yellow triangle never bothered me so i never removed it or reset the count after installing Checkrom.
Thanks
[Edit] I've just loaded Kies and it says 'your device does not support software updating via kies'. This is somewhat concerning since i thought i had returned my phone out-of-the-box stock by flashing this firmware -> GT-I9100_VOD_I9100BUKJ3_I9100VODKI2_I9100BUKI1.tar.md5. When i very first got the phone Kies would state that its up to date. After runing *#1234# my settings are PDA: I9100BUKJ3 , PHONE: I9100BUKI1 and CSC: I9100VODKI2.
Re: the clicking thing, no idea. Haven't encountered/heard of that before.
Re: resetting the counter. Put it this way, if you don't, and you return the phone for warranty service you're pretty much paying for the repair out of your own pocket.
I.E the counter is proof you've been messing with the phone, which voids the warranty. What firmware you've currently got on the phone is irrelevant.
Might want to invest a few dollars in a jig just in case you do decide to send it in for a warranty repair.
Goooober said:
I got my S2 only a few days ago from Vodafone UK and quickly flashed to the latest Checkrom to get rid of the stock bloatware. After suffering severe battery drain to do with wifi i have flashed back to the stock carrier firmware (BUKJ3).
I did this first by using CWM to clear davlik cache and a full wipe and then after enabling USB debugging mode i rebooted into downloaded mode. Upon entering download mode the phone began to make an audible clicking noise which i dont remember it ever doing when i first rooted the phone.
I went ahead and flash the firmware and all seems well but i wanted to see if the clicking noise might indicate a fault with the phone?
One other thing, if i wanted to return the phone back to Vodafone would i need to reset the binary counter thingy even though i'm back on stock firmware? The yellow triangle never bothered me so i never removed it or reset the count after installing Checkrom.
Thanks
Click to expand...
Click to collapse
MistahBungle said:
Re: the clicking thing, no idea. Haven't encountered/heard of that before.
Re: resetting the counter. Put it this way, if you don't, and you return the phone for warranty service you're pretty much paying for the repair out of your own pocket.
I.E the counter is proof you've been messing with the phone, which voids the warranty. What firmware you've currently got on the phone is irrelevant.
Might want to invest a few dollars in a jig just in case you do decide to send it in for a warranty repair.
Click to expand...
Click to collapse
Yeah i do have a Jig on the way. I've just encountered another problem as well. My internet speeds over wifi are appalling after flashing back to the stock firmware. 2200kbps down and 355kbps. The phone out of the box and on checkrom both performed as normal (about 10x what it is now). This stock vodafone firmware i downloaded here is clearly not what i had out-of the-box.
In that case, you might want to find out what firmware you had on the phone initially & flash that. As I'm not in the UK, I wouldn't have the foggiest.
At the end of the day, if you're returning it for a warranty repair, I wouldn't be surprised if they reflash whatever stock firmware they're currently using as part of the repair process (I've read many accounts of this happening).
Obviously once you start messing around with the phone, you potentially open a whole can (or many cans) of worms so far as how the phone performs goes. You could easily have just rooted the phone in the first instance to remove the bloatware, flashing a custom rom was not necessary in order to achieve this.
Goooober said:
Yeah i do have a Jig on the way. I've just encountered another problem as well. My internet speeds over wifi are appalling after flashing back to the stock firmware. 2200kbps down and 355kbps. The phone out of the box and on checkrom both performed as normal (about 10x what it is now). This stock vodafone firmware i downloaded here is clearly not what i had out-of the-box.
Click to expand...
Click to collapse
MistahBungle said:
In that case, you might want to find out what firmware you had on the phone initially & flash that. As I'm not in the UK, I wouldn't have the foggiest.
At the end of the day, if you're returning it for a warranty repair, I wouldn't be surprised if they reflash whatever stock firmware they're currently using as part of the repair process (I've read many accounts of this happening).
Obviously once you start messing around with the phone, you potentially open a whole can (or many cans) of worms so far as how the phone performs goes. You could easily have just rooted the phone in the first instance to remove the bloatware, flashing a custom rom was not necessary in order to achieve this.
Click to expand...
Click to collapse
I thought i had flash whatever firmware was on it originally. I downloaded the BUKJ3 UK Vodafone carrier firmware from the stock rom thread since my phone came with BUKJ3. The wifi performance is shocking tho.
I have a loose USB port on my phone, making it very hard to get a reliable connection between the phone and a PC. It still charges, although it's usually very slow to charge as well. Problem is, I've got CM7 and clockworkmod recovery running. I have a backup of my stock ROM which I could go back to, but I don't think that's sufficient for warranty repair. Is there a way to do the necessary ODIN/heimdall steps via WiFi (for flashing the stock image), or on the phone itself via a terminal emulator? If it's something that increments the flash counter, I have a jig that works if I apply pressure to it correctly (for now...again, loose USB port), so I can reset that back after. If I understand correctly, I basically just need a way to flash the stock recovery, and possibly flash the kernel back to unrooted, without USB.
Any help is greatly appreciated.
nd_geek said:
I have a loose USB port on my phone, making it very hard to get a reliable connection between the phone and a PC. It still charges, although it's usually very slow to charge as well. Problem is, I've got CM7 and clockworkmod recovery running. I have a backup of my stock ROM which I could go back to, but I don't think that's sufficient for warranty repair. Is there a way to do the necessary ODIN/heimdall steps via WiFi (for flashing the stock image), or on the phone itself via a terminal emulator? If it's something that increments the flash counter, I have a jig that works if I apply pressure to it correctly (for now...again, loose USB port), so I can reset that back after. If I understand correctly, I basically just need a way to flash the stock recovery, and possibly flash the kernel back to unrooted, without USB.
Any help is greatly appreciated.
Click to expand...
Click to collapse
You should flash back to your stock ROM backup first. Then, go on the market and download mobile Odin pro. With this app, you can flash kernels and stuff. Then you should download the stock kernel, and flash it to bring your phone back to Stock.
Sent from my SAMSUNG-SGH-I777
for a little more detail see this thread.
Thanks to the both of you. I've managed to get everything back to stock, and migrated to a replacement device. All that's left is to stick the phone with a bum USB port in the mail.
nd_geek said:
All that's left is to stick the phone with a bum USB port in the mail.
Click to expand...
Click to collapse
And do some more reading and searching before opening new threads.
Last night I went to reboot into recovery and my phone now sits at the Galaxy S2 splash screen and won't boot up. Tried plugging it in powered off and it won't even go into charging mode. The battery picture just comes up and the little spinning wheel keeps going.
So Ive been trying for the last hour to reflash the phone back to stock using both Entropys return to stock guide as well as the 'How to return your phone to the store' guide too and no luck.
Heimdall of course as always just flat out doesn't work so I hooked it up to my laptop and ran Odin. Odin connects to the phone fine and the box turns yellow, but the minute I hit start, it just gives me this:
<ID:0/008> SetupConnection..
<ID:0/008>
<OSM> All threads completed. (succeed 0 / failed 1)
I even tried the one click ICS leak from Rootzwiki and the same thing.
I can get the phone into Download mode no problem but man I cannot get it to flash ANY of these rome!!
Any advice or should I just take it to an ATT store on the way home from work??
I got it around the second week of February so hopefully worst case scenario I can still exchange it..
Im at my wits end here, can't do anything with it!!
I had same problem with my sprint Gs2, I took it into the store they told me since I rooted they couldnt help me. But the guy said go into download mode and root it again, it will remove anything and everything off it. Idk if that's what you want though. It got my phone back up and running
Sent from my SPH-D710 using xda premium
Ahh forgot to add I can't get into Recovery anymore.
No clue what happened. I can get it into Download mode but not Recovery.
If I could've gotten into Recovery I could've just flashed my Nandroid last night and fixed it hehe..
ODIN requires Download mode, not recovery mode. If your phone can indeed go into download mode as you claimed, you should be able to flash any ODIN flashable ROMs.
Try flashing just a kernel with recovery
Sent from my GT-I9100 using Tapatalk 2 Beta-2
You didn't say what you were running before the problem occured. Or if you did anything just before. Need more information to be able to troubleshoot the problem.
You might try flashing Entropy's DD kernel only with odin. He has at least one tar in his DD thread OP.
It may be that one of the components, such as param.lfs is screwed, but it would be better to have more information first before just randomly trying to flash things.
You can find most everything you might need in the Download Repository.
creepyncrawly said:
You didn't say what you were running before the problem occured. Or if you did anything just before. Need more information to be able to troubleshoot the problem.
You might try flashing Entropy's DD kernel only with odin. He has at least one tar in his DD thread OP.
It may be that one of the components, such as param.lfs is screwed, but it would be better to have more information first before just randomly trying to flash things.
You can find most everything you might need in the Download Repository.
Click to expand...
Click to collapse
Yeah sorry about the lack of info hehe! I made the thread about 20 minutes before I had to go to work and spent the hour before that trying to fix it hehe.
Anyways, I WAS running the ATT ICS leak that Task and Fenny packaged up with CWM. I WAS going to get everything backed up and attempt to move over to CM9 when it went to crap.
So far what Ive attempted to flash with Odin was the following with no luck:
Entropys 'Return to Stock' PDA.tar (the UCKH7_stock_odin with root)
ATTGalaxyS2Unroot_SGH-i777.tar
The leaked ATT Odin one click flasher from Rootzwiki (same results as using regular Odin with any of the above)
I did in fact also download the I777UCKH7-CL503881-Parts-NoBL.7z from creepys 'How to prepare your phone for return to the store' thread BUT..
The instructions tell you to unpack the 7z and then run the one click .exe inside but there is no .exe in the archive. Just the modem.bin, cache.img, image, factoryfs.img, and hidden.img. This would've been fine to try but of course Heimdall is every Mac OS users enemy and anytime I try to use the front end I get a 'missing firmware.xml' error and running it via command line just never connects to the phone.
Since Entropys return to stock package only has the factoryfs.img and zimage, sounds like I need to find a complete tar file that has all the other parts that creepy's has in it..
Last thing I did before going to work was updating the USB drivers on my Win 7 laptop to see if that would help, but since I can only use my laptop via Remote Desktop Connection from my Mac (display is dead) I had to do a Windows Update so I could get the laptop to restart (which I don't think you can do through RDC unless I missed it), and I had to run to work before it finished..
And I was STILL 10 minutes late hahaha!
So the laptop JUST got rebooted now that Im home, Im going to go see if theres also a newer version of Odin, and Im gonna go dig through the Download Repository and also check that Samsung Firmwares site to see if I can find myself a complete tar ball of the stock 2.3.4 firmware..
Ive got Saturday off finally so if I can't get it flashed and fixed by then I think Im going to bite the bullet and just take it to an ATT store and see if they'll swap it. Hopefully theres no 30 day policy, because Im pretty sure my Blackberry crapped out on me about 2 months in and they had no problem sending me another in the mail.. I REALLY wish I had my MyBackup done on my external SD card and not the internal one.. Gotta put another 40 hours into grinding in all my Zenonias to get back to where I was hehe..
Slavestate said:
Yeah sorry about the lack of info hehe! I made the thread about 20 minutes before I had to go to work and spent the hour before that trying to fix it hehe.
Anyways, I WAS running the ATT ICS leak that Task and Fenny packaged up with CWM. I WAS going to get everything backed up and attempt to move over to CM9 when it went to crap.
So far what Ive attempted to flash with Odin was the following with no luck:
Entropys 'Return to Stock' PDA.tar (the UCKH7_stock_odin with root)
ATTGalaxyS2Unroot_SGH-i777.tar
The leaked ATT Odin one click flasher from Rootzwiki (same results as using regular Odin with any of the above)
I did in fact also download the I777UCKH7-CL503881-Parts-NoBL.7z from creepys 'How to prepare your phone for return to the store' thread BUT..
The instructions tell you to unpack the 7z and then run the one click .exe inside but there is no .exe in the archive. Just the modem.bin, cache.img, image, factoryfs.img, and hidden.img. This would've been fine to try but of course Heimdall is every Mac OS users enemy and anytime I try to use the front end I get a 'missing firmware.xml' error and running it via command line just never connects to the phone.
Since Entropys return to stock package only has the factoryfs.img and zimage, sounds like I need to find a complete tar file that has all the other parts that creepy's has in it..
Last thing I did before going to work was updating the USB drivers on my Win 7 laptop to see if that would help, but since I can only use my laptop via Remote Desktop Connection from my Mac (display is dead) I had to do a Windows Update so I could get the laptop to restart (which I don't think you can do through RDC unless I missed it), and I had to run to work before it finished..
And I was STILL 10 minutes late hahaha!
So the laptop JUST got rebooted now that Im home, Im going to go see if theres also a newer version of Odin, and Im gonna go dig through the Download Repository and also check that Samsung Firmwares site to see if I can find myself a complete tar ball of the stock 2.3.4 firmware..
Ive got Saturday off finally so if I can't get it flashed and fixed by then I think Im going to bite the bullet and just take it to an ATT store and see if they'll swap it. Hopefully theres no 30 day policy, because Im pretty sure my Blackberry crapped out on me about 2 months in and they had no problem sending me another in the mail.. I REALLY wish I had my MyBackup done on my external SD card and not the internal one.. Gotta put another 40 hours into grinding in all my Zenonias to get back to where I was hehe..
Click to expand...
Click to collapse
Add me on gtalk and we can see what we can do [email protected]
At this point I don't know if anything will help heh.
All it will do is either sit on the GS2 boot screen, or it will go into Download mode.
Download mode though, no luck so far. Odin just won't flash it for some reason. It sees it, the COM port box lights up yellow, but the minute you hit Start, it just goes right to that error message I posted above. After this, I have to close both Odin and disconnect the phone and reboot it into Download mode.
I went through the Download Repo. Tried I777UCKH7-CL503881-Full.7z, and even the param.ifs by itself but everything just gives the same result. I didn't try Entropys DD though since I was running the stock ICS and didn't want to really mess anything up. Only thing I can think of left to try is flashing Task/Fennys CWM modded stock ICS kernel but after all this I doubt its going to work. I tried the stock rooted GB kernel earlier and it didn't bother flashing either.
Am I maybe connecting it wrong? I have the battery pulled and am going into Download mode by holding the vol buttons and connecting the usb cable to the laptop. I don't want to kill the battery power I have left as it won't charge now either. Basically I just fire up Odin, connect the phone and put it in Download mode, select my tar file and put it in the PDA slot, hit Start and go.. Should I be doing anything differently??
Whenever I've had a problem with Odin like that, it has always been that some partition got flashed wrong/partially/corrupted, and the only fix was to reflash the damaged partition. As long as Odin is seeing the phone, then it must be either a software/firmware problem or a hardware problem. I'm still thinking it is firmware, but it seems to be outside my experience.
I havn't been playing with ICS yet, but I have noticed that there have been a number of reports similar to yours, where people have flashed some flavor of ICS. This supports the idea that it is firmware. I have always understood that if the problem is firmware, and if the phone can boot into download mode, it can be recovered.
Yeah Im wondering if I should try flashing the PIT file I have for the phone, but I don't know crap about partitioning these things and didn't want to really mess it up.
Guess at this point its worth a shot. I was about to go sit and chat with the warranty folks at ATT (mines a refurb so Ive only got til the end of the month before warranty s up). Maybe Ill try the pit file and let Odin repartition the thing. I can't flash a firmware back onto it anyways.
EDIT: Holy crap progress.. I flashed the stock secondary boot loader with Odin (in the Bootloader slot) and that actually flashed. Now I just reconnected it and decided to try the ATT ICS leak one click from Rootzwiki and it appears my phone is now flashing!!!!! As long as my crap is still on the internal usb storage today is gonna be a good day hehe! Yep all is well so far! Phone just rebooted and its now at the ICS setup screen! WOOHOO!!! Crisis averted!! Thanks guys for the comments and help! Creepy thank you for reminding me we have that repository!!
Hey guys need some help. I've gone through as much of the forums as possible and still trying to resolve this without having to send it away.
My brother's SGS II has the following symptoms:
-turns on and stays at the SGS II GT-i9100 screen (will not change)
-phone can enter download and recovery modes
-when phone is plugged in to charge the battery symbol will not show that it's charging then continue to the SGS II GT-i9100 screen...then back to the battery icon (and loop)
-attempts to reflash anything will either be successful or fail in ODIN but still results in the 1st issue above.
What should I try next?
Hi,
your searching skills are enormous
http://forum.xda-developers.com/showthread.php?t=1108499
http://forum.xda-developers.com/showthread.php?t=1457458
..
wow they are sticked
*edit*
fullwipe - flash via CWM Recovery, thats what i would try
greetz
Are you using pit file when you flash with odin ? could be partition problem so using pit would fix that
Please don't tell people to flash pit files unless you know for absolute certain their problem (which at this stage is vague/undiagnosed; I.E we don't know what the problem is exactly) will be fixed by flashing a pit.
(You should know) flashing a pit can permanently bork a phone if that isn't what's wrong with the phone :-|
Thanks for the sarcasm my friend but when I say i've gone through most of the forum as possible I meant I've tried both those fixes to no avail...thanks anyway though :good:
leechseed said:
Hi,
your searching skills are enormous
http://forum.xda-developers.com/showthread.php?t=1108499
http://forum.xda-developers.com/showthread.php?t=1457458
..
wow they are sticked
*edit*
fullwipe - flash via CWM Recovery, thats what i would try
greetz
Click to expand...
Click to collapse
yeah right now I haven't gone any pit routes yet. I've gone through both boot/bricked guides and right now it's a wash...hell i'm getting a loop between the battery screen and GT-i9100 screen now.
MistahBungle said:
Please don't tell people to flash pit files unless you know for absolute certain their problem (which at this stage is vague/undiagnosed; I.E we don't know what the problem is exactly) will be fixed by flashing a pit.
(You should know) flashing a pit can permanently bork a phone if that isn't what's wrong with the phone :-|
Click to expand...
Click to collapse
OK. What we really need to know is exactly what's been done to the phone. Every little detail (important). From before it started acting up till now. Time to interrogate your brother & find out exactly what he's been doing with/to the phone.
The more info we get the better the chance you don't have to blindly flash that recovery package in the 2nd thread Leechseed linked to with the pit file & hope it works without knowing exactly what/why is wrong with the phone.
He was doing an upgrade to the Omega rom I believe (sorry I'm a galaxy 1 guy so I'm not familiar with the s2 roms). It was flashed succesfully but once it rebooted that was all she wrote...phone just sat there at the GT-i9100 screen.
So at this point we've tried the ICS recovery, the ginerbread recovery and the i9100M recovery (that's the version he has). All the 1 file tars will run through successfully but the ones with the multiple files (phone, csc, pda) will hang up in odin on the DATAFS:
http://i297.photobucket.com/albums/mm235/sirknattar/Untitled.jpg
MistahBungle said:
OK. What we really need to know is exactly what's been done to the phone. Every little detail (important). From before it started acting up till now. Time to interrogate your brother & find out exactly what he's been doing with/to the phone.
The more info we get the better the chance you don't have to blindly flash that recovery package in the 2nd thread Leechseed linked to with the pit file & hope it works without knowing exactly what/why is wrong with the phone.
Click to expand...
Click to collapse
There's some details missing somewhere. It just doesn't make sense for a phone to do that upgrading a rom under normal circumstances. So you have two choices essentially given you've already tried the obvious. You could send it in for warranty service, hope they don't care it's been messed with & repair it. Tho there's obviously a better than even chance you will end up paying for it (not unreasonably).
Or I guess you could flash whatever recovery package from that thread with the PIT file & hope that fixes whatever is wrong with it. Obviously if it doesn't that makes it certain you're either sending it to Samsung/an authorised repairer (quite possibly for repair at your expense, unless they don't notice/care), or to a 3rd party repairer (again at your expense; might be cheaper than Samsung if they decide to charge you for the repair).
Given the info you've provided, there's absolutely no clues whatsoever as to what caused it to happen. Unless someone else reads the thread & has other ideas. Might want to hold off on the PIT for a while & see if someone else does have other ideas given that's pretty much a final step.
Doing the .pit and re-partition as we speak and hangs up on the exact spot...DATAFS (data.img). *sigh*
I'm going to try the bootloader option next. I know my bro says he's done it already but I want to be sure. Thanks for your help man.
MistahBungle said:
There's some details missing somewhere. It just doesn't make sense for a phone to do that upgrading a rom under normal circumstances. So you have two choices essentially given you've already tried the obvious. You could send it in for warranty service, hope they don't care it's been messed with & repair it. Tho there's obviously a better than even chance you will end up paying for it (not unreasonably).
Or I guess you could flash whatever recovery package from that thread with the PIT file & hope that fixes whatever is wrong with it. Obviously if it doesn't that makes it certain you're either sending it to Samsung/an authorised repairer (quite possibly for repair at your expense, unless they don't notice/care), or to a 3rd party repairer (again at your expense; might be cheaper than Samsung if they decide to charge you for the repair).
Given the info you've provided, there's absolutely no clues whatsoever as to what caused it to happen. Unless someone else reads the thread & has other ideas. Might want to hold off on the PIT for a while & see if someone else does have other ideas given that's pretty much a final step.
Click to expand...
Click to collapse
here's another note...when flashing bootloader it comes up into the recovery screen and says "E: failed to mount /data (unknown error: 0)
trying a format data/system
MistahBungle said:
There's some details missing somewhere. It just doesn't make sense for a phone to do that upgrading a rom under normal circumstances. So you have two choices essentially given you've already tried the obvious. You could send it in for warranty service, hope they don't care it's been messed with & repair it. Tho there's obviously a better than even chance you will end up paying for it (not unreasonably).
Or I guess you could flash whatever recovery package from that thread with the PIT file & hope that fixes whatever is wrong with it. Obviously if it doesn't that makes it certain you're either sending it to Samsung/an authorised repairer (quite possibly for repair at your expense, unless they don't notice/care), or to a 3rd party repairer (again at your expense; might be cheaper than Samsung if they decide to charge you for the repair).
Given the info you've provided, there's absolutely no clues whatsoever as to what caused it to happen. Unless someone else reads the thread & has other ideas. Might want to hold off on the PIT for a while & see if someone else does have other ideas given that's pretty much a final step.
Click to expand...
Click to collapse
MistahBungle said:
Please don't tell people to flash pit files unless you know for absolute certain their problem (which at this stage is vague/undiagnosed; I.E we don't know what the problem is exactly) will be fixed by flashing a pit.
(You should know) flashing a pit can permanently bork a phone if that isn't what's wrong with the phone :-|
Click to expand...
Click to collapse
Seems I must have been lucky over the last 24 months having flashed 100's of times with Odin and pit file on SGS 1, 2 and 3 and not bricked 1 yet in fact I've never known anyone brick an SGS flashing a rom with pit other phones maybe but not SGS's
yeah i'm comfortable with flashing pit files due to my weekly rom addiciton from my SGS/cappy hahaha
Anyway I may be experiencing that corrupt SD card issue i've been reading about...not sure.
sminky01 said:
Seems I must have been lucky over the last 24 months having flashed 100's of times with Odin and pit file on SGS 1, 2 and 3 and not bricked 1 yet in fact I've never known anyone brick an SGS flashing a rom with pit other phones maybe but not SGS's
Click to expand...
Click to collapse
Why dont you just try to flash a Stock Rom??
I would try that first - wipe - flash Stock (via CWM)
I always used the ONE file package of Roms and never had any probs..
Why on earth are you re partitioning with Odin? You know Odin isn't build for the S II, and the re-partitioning it does is for the Nexus or something. IE using Odin to re partition an S II royally ****s it. Flashing a PIT might work but why don't you just start at a logical place, before going out and doing a full manual JTAG on your phone with a pair of pliers, some masking tape and a bunsen burner, why don't you do the obvious. Which is update your Odin, uninstall Kies and reinstall it for the Samsung drivers, check the USB etc. something is clearly going wrong during the flash process despite it being "successful". Failing that, take it back to the shop, if your phone isn't a £500 paper weight by the time you read this, just apply for a new one. Make sure you erase any evidence of you messing around with it and return it.
sirknattar said:
He was doing an upgrade to the Omega rom I believe (sorry I'm a galaxy 1 guy so I'm not familiar with the s2 roms). It was flashed succesfully but once it rebooted that was all she wrote...phone just sat there at the GT-i9100 screen.
So at this point we've tried the ICS recovery, the ginerbread recovery and the i9100M recovery (that's the version he has). All the 1 file tars will run through successfully but the ones with the multiple files (phone, csc, pda) will hang up in odin on the DATAFS:
http://i297.photobucket.com/albums/mm235/sirknattar/Untitled.jpg
Click to expand...
Click to collapse
The problem might be the Omega rom ??? is it compatible with I9100M series or just the I9100 the M could be the clue to the flash failing same as when Samsung released the I9100G and people who flashed that got screwed up with the incorrect bootloaders since the hardware is different in the I9100 and I9100G same problem might exist with I9100M
Thanks for everyone's help and suggestions. I've got a vague idea of the problem now and it's being sent back to Samsung for warranty (after I clear it with the JIG).
try to do the following.
1-flash any gingerbread CF kernel via odin
2-boot into recovery mode
3- wipe everything under mounts and storage including system partition
4-reboot into download mode
5-try to flash the CM9 Resurrection Edition
hope this helps mate. mine just emmc bricked on me, with the crappy LQ5 samsung firmware and had to RMA the bastard.
check ur pm mate
Hi am obviously new to these forums but not new to Android/Samsung development so I had custom roms installed on my I777 so I needed to revert back to stock in which I flashed a leak which apparently changed the pit so I was able to download all the stock files for Odin3 for my device in the Download Repository. My question is there any reason why my device just doesn't act as accurately as I though I remembered it being when it was stock. Is there any ultimately right process for flashing because most instructions including my own are all different, some say wipe cache and data first and battery pull then download mode Creepys says its not neccessary until after the flash as does ZedoMax. I've followed all of them and haven't understood why there is no ultimately right process if there is one at all using odin3 and one-click. And if this is the case what could possibly be going on with the force closes and hangups I'm getting? If someone is willing to take the time to help me with all these questions I'd greatly appreciate it.
Dunno if it'll help, but it won't hurt..
Boot into recovery and"fix permissions". *Should* help with the FC's - oh, and delete everything from your memory that you read on galaxys2root (zedomax). Whatever you've read from creepy, COMMIT to memory. The guy is ace!
Clay
Team Pirate
Sent from my PINK SGH-I777
clay101eve said:
Dunno if it'll help, but it won't hurt..
Boot into recovery and"fix permissions". *Should* help with the FC's - oh, and delete everything from your memory that you read on galaxys2root (zedomax). Whatever you've read from creepy, COMMIT to memory. The guy is ace!
Clay
Team Pirate
Sent from my PINK SGH-I777
Click to expand...
Click to collapse
I don't see the option for fix permissions first of all is that a cwm option? Also I know creepy is one of the best but what's wrong with gs2root? And I appreciate the help but which process is the ultimate right way? Do you flash pit,PDA,modem all together or is that incorrect?
GalaxyHackster85 said:
I don't see the option for fix permissions first of all is that a cwm option? Also I know creepy is one of the best but what's wrong with gs2root? And I appreciate the help but which process is the ultimate right way? Do you flash pit,PDA,modem all together or is that incorrect?
Click to expand...
Click to collapse
I don't remember for sure, but I don't think fix permissions in available in stock 3e recovery. It should be available in just about any custom recovery.
GalaxyS2Root, and it's owner who goes by the screen name zedomax, is a strictly commercial endeavour, designed to make money but not necessarily designed to help people. I think zedomax is a developer, but I'm not sure how good he is. Many of the offerings on that web site, and presumably on his dozens of other web sites for other phones, cause problems for folks, bricking phones, and other things. Further, he takes the work of developers here and posts their work on his sites without giving any attribution or remuneration. He's spread way too thin keeping up with all his various sites, and/or he just doesn't seem to care if his offerings cause problems. We've had so many people come to this forum with various problems due to GalaxyS2Root that when the name is mentioned, everyone is on it right away.
I would only use the pit to repartition on the I777 when everything else fails. It can be a help, but you should be sure that you are going to have a successful flash before you use it, since it repartitions the memory space of the phone.
Most firmware for the I777 has everything in one .tar file, which you put into the PDA slot. If you are flashing just a param.lfs or just a sbl.bin, then that goes into the PDA slot. You can also flash a modem at the same time as the rest of the firmware, using the Modem slot, but most firmware packages have the modem in them too.
So essentially the oneclicks are absolutely the only thing I need in order to ensure a 100% successful restocking? And if so am I always suppose to factory wipe/cache then battery pull (3e recovery doesn't have a power off option)? The reason why I ask so many questions is A. A lot of peoples data isn't accurate as you've stated and its better for me to have as much data as possible when potentially getting into these things. And B. I've been flashing my S2 like a madman with OCD because as soon as I'd get a force close or any sort of hiccup happened I assumed it was because I flashed it wrong when in fact I was just following some of the directions that I've aqquired from here or GS2Root and so far everything has flashed with the same results but as its been forever since my phone was purchased so I can recall if these are just the normal hiccups that come with the inconsistancy of android. So to me I'm just trying to.make sure that I'm doing things absolutely correct.
There is lots of material here to read. You can learn a lot about your phone by spending some time reading.
creepyncrawly said:
There is lots of material here to read. You can learn a lot about your phone by spending some time reading.
Click to expand...
Click to collapse
And you are absolutely correct and I have your guide bookmarked but with so many people having different takes on how to return to stock can you point me in a direction that's the completely right way of flashing your pit and attempt software. Or is your guide with one click the most surefire way to do it? Like I said before I'm a bit OCD when it comes to my phone so whenever I get a little hiccup I can't tell if those are just normal for I777 software or is it something I've done wrong which I probably haven't but it still worries me.
If you havn't done something absolutely ignorant, i.e. flash firmware for a different phone, then you should just use my guide with the linked one-click downloader. That package does not contain bootloaders or param.lfs. Those (the bootloaders and param) will always be good, and not needing replaced, if you only flash firmware from these forums and never flash leaked firmware (which usually contains bootloaders.) There should never, ever be a reason to use a pit file. As I said before, the phone has to be pretty seriously screwed before you need to repartition, and then it should be the absolutely last thing you try.
And inform yourself before you do any actual flashing. You should know exactly what you are doing to your phone, and also know what the remedy is before you do it. That way, you can avoid doing something stupid. If you really want to learn about your phone, read at least a little bit from the forums here every day for a few months, get involved in the discussions, and before you know it, you'll be one of the helpers.
Thank you so much for all of your prompt replies, I have been using the data from this site for quite some years now but never ran into any issues which required me to create an account (although I have wanted to), but for s**ts and giggles let me just say that due to the few hiccups I encountered and not knowing what would have caused them I have already flashed the pit and repartitioned as well as flashed the oneclick w/ bootloaders and param. Now asside from the few force closes that I ran into and the one time I bricked it and brought it back to fully functional is there any harm to the flashing of those tools that I've already done so far. Is there any negative side effects of what I've done that I may not be seeing or is it a case of well "there in the repository so theyre safe as long as I've flashed them correctly". And if so are these few force closes just everyday hiccups that every version of Android experiences and that I'm just overthinking it and it's just been a case of my ocd kicking me in the ass?
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
creepyncrawly said:
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
Click to expand...
Click to collapse
i did zedo then s2 unlock then aokp then siyah kernal change forgot to do triangle away then tryed a ota update messed up rom cwm messed up then i just did zedo again to get cwm again then i did aokp again then ran triangle away then i return to stock backup after root then odin flash for stock non root then i took stock and did ota update to 2.3.6 i dont think we will ever get 2.3.7 because google wallet is on 2.3.7 and we cant have it correctly .....on reboot it hangs so i did 3e wipe and cache delete reboot all has been good since batt has been outragously long on uckk7 but after ota update it shows as uckk6 i used a non rooted file maybe u used a rooted return to stock file ?anyway file i used was I777UCKH7-CL503881-No-BL as stated just used pda slot .....idk after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and do it all over again i honestly just miss the torch feature and the easy brightness slider on the pulldown
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
colorsharpkid said:
i did zedo then s2 unlock then aokp then siyah kernal change forgot to do triangle away then tryed a ota update messed up rom cwm messed up then i just did zedo again to get cwm again then i did aokp again then ran triangle away then i return to stock backup after root then odin flash for stock non root then i took stock and did ota update to 2.3.6 i dont think we will ever get 2.3.7 because google wallet is on 2.3.7 and we cant have it correctly .....on reboot it hangs so i did 3e wipe and cache delete reboot all has been good since batt has been outragously long on uckk7 but after ota update it shows as uckk6 i used a non rooted file maybe u used a rooted return to stock file ?anyway file i used was I777UCKH7-CL503881-No-BL as stated just used pda slot .....idk after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and do it all over again i honestly just miss the torch feature and the easy brightness slider on the pulldown
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
Click to expand...
Click to collapse
Honestly, I have no idea what you just said, or what you're asking.
qwertyaas said:
Honestly, I have no idea what you just said, or what you're asking.
Click to expand...
Click to collapse
Me either, sometimes punctuation goes a long way
Sent from team Pirate! Using Tapatalk 2
colorsharpkid said:
i flashed zedo then used s2 unlock. then i flashed aokp and siyah kernel. I forgot to do triangle away (because I used zedo) and then tried an ota update. This messed up my rom because I couldn't access cwm. then i flashed zedo again to get cwm back. After that i flashed aokp again and ran triangle away.
I then did a return to stock backup after root and an odin flash for stock non root. While on stock i did an ota update to 2.3.6. (some nonsense about 2.3.7 and Google wallet)
.....on reboot it hangs so i did 3e recovery wipe and wiped cache. Reboot has been good since. My batt has been outragously long on uckk7!! But, after an ota update it shows as uckk6 i used a non rooted file, maybe I should have used a rooted return to stock file?
Anyway, the file i used was I777UCKH7-CL503881-No-BL as stated and i just used pda slot .....idk, after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and flash custom ROMs all over again. i honestly just miss the torch feature and the easy brightness slider on the pulldown.
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone. im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
Click to expand...
Click to collapse
Fixed... I think. And "zedo" refers to the sh;t zedomax has on gs2root.
Clay
Team Pirate
Sent from my Buttery Pink SGH-i777
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again. I also had on flash that was the 2.3.5 leak but flashed over that and it was fine. Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
creepyncrawly said:
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
Click to expand...
Click to collapse
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again. I also had on flash that was the 2.3.5 leak but flashed over that and it was fine. Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
Sorry for double post but I wanted to make sure my questions are targeting creepy seeing as this thread is getting a bit off topic.
GalaxyHackster85 said:
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again.
Click to expand...
Click to collapse
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I also had on flash that was the 2.3.5 leak but flashed over that and it was fine.
Click to expand...
Click to collapse
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
Click to expand...
Click to collapse
I don't know how to look behind the scenes... but I would think your phone is fine.
creepyncrawly said:
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
I don't know how to look behind the scenes... but I would think your phone is fine.
Click to expand...
Click to collapse
OK great info and definitely a relief but just out.of curiousity what are the repercussions of a bad bootloader flash or an improper pit flash? And how would we know that whatever pit or bootloaders flashed weren't for our phone or are corrupted data?
creepyncrawly said:
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
I don't know how to look behind the scenes... but I would think your phone is fine.
Click to expand...
Click to collapse
And trust me I absolutely appreciate all the responses the answer to my last question is all I needed to know to truly understand how the i777 works and functions and I commend you for that. I felt that trying to find all these answers would have been trying to find a needle in a haystack.
Also regarding the repartioning I just wanted to make sure that everything is correct in terms of space. My device is showing only 1.89gb of "Device Memory" at the bout of the "Storage" screen is this normal I though it was higher before but I cant quite remember.