Alright I need some help please. First off i need to re-partition my modem and i have no idea how to. Due to constant flashing it screwed something up and i can no longer receive data coverage. Now i looked and looked and i couldn't find anything. So i decided to start a new thread. I need a step by step walk through this will be my first time doing it. And i really don't want to say this cuz i am myself a noob (please no noob's on this one i cant afford another phone). i have had some help by some other people witch was good advice but i have exhausted my options here. I have tried everything from flashing new modems to flashing new ROMS to odin'ing back to stock A.T.T. I'm Stumped i have done absolutely everything i can think of to this phone and still no data. I have the correct apn settings i know that. I'm just completely stumped i dont know what to do.
Phone: Att Samsung Galaxy Note SGH-I717
Android Version: 2.3.6
Okay brother ....I've been digging for gold, And to clarify your issue, you do not need to partition a modem.
You need to repair the device partitions.
Now, this doesn't mean that you should just start changing partitions using CWM or TWRP, or ODIN.
What it does mean, is you need to let Odin do it for you.
I won't take the time to go into PIT files and mapping, as we both would explode from boredom in 10 seconds.
But I will tell you that there are different levels of depth regarding roms and how they flash.
Odin stock roms go pretty deep, but sometimes not deep enough, and Odin will sometimes ignore the PIT remapping function during the flash if the file structure is already present on the device.
That being said, an Odin return to stock is not always successful when seeking a complete restructuring of the device partitions.
However, I have located a rom (factory ICS leak) that contains the entire device partition package, the PIT.IMG Package, baseband, and factory ICS image.
By using this one click Odin file, you will force the device back to factory status using ICS.
This will allow you to push the UCLE2 modem again once you root using CWM.
The ICS root method is slightly different than GB, so check the ICS root info in the super thread before rooting again. This will prevent errors or worse if done incorrectly.
The link below is the most complete package I can find, and includes files not found in the GB Odin.tar.
The file is good. And has been used many times to repair issues we see here.
Take your Time, and read read read....especially when rooting again.
Note: prior to pushing this Odin file, you "MUST" wipe all data and factory reset the device to ensure a "CLEAN" build of the file structure.
And once flashing is complete, follow the root method for ICS... And once rooted, flash the modem by using CWM.
You will need to manually add and save your new APN settings.
Once these steps are complete, you should have a working device with data..
If not, you may have device damage of some kind, which requires a repair of the device by an authorized service center.
I'm uncertain of the software having the ability to damage hardware, but I'm certain it is possible, and you may have this issue.
But if you are willing to try this rom, it will likely help.
Beyond my advice above, I've got nothing more to offer, other than moral support.
Of Course, standard disclaimers apply, and you do this at your own risk ...
Best of luck to you ....g
http://rootzwiki.com/topic/25980-sgh-i717ucle2-official-leak/
alright how do i flash in odin just like a normal .tar file????
nope didnt work
alright man i fill completely stupid 180% i put my girl friends att micro sim in my note it turns out my sim card is bad cuz i got her 4g as soon i i put her sim in but thank u at the same time as i apologize to you cuz i have learned alot from u and u have helped me alot through this issue of mine i fill so dumb right now i truly am sorry for the hassle i have put u through in the last couple of days
Deleted... not a useful comment
Sk84all20 said:
alright man i fill completely stupid 180% i put my girl friends att micro sim in my note it turns out my sim card is bad cuz i got her 4g as soon i i put her sim in but thank u at the same time as i apologize to you cuz i have learned alot from u and u have helped me alot through this issue of mine i fill so dumb right now i truly am sorry for the hassle i have put u through in the last couple of days
Click to expand...
Click to collapse
Dont feel stupid.
We all come here to learn about devices, and the problems that are associated with them.
If nothing else, you've learned many things about Odin, and the importance of taking your time with these things, and about proper setup of the device.
I'm pleased to hear that your device is not damaged, and you are up and running.....g
gregsarg said:
Dont feel stupid.
We all come here to learn about devices, and the problems that are associated with them.
If nothing else, you've learned many things about Odin, and the importance of taking your time with these things, and about proper setup of the device.
I'm pleased to hear that your device is not damaged, and you are up and running.....g
Click to expand...
Click to collapse
agreed, OP my last post wasn't intended to make you feel stupid, I do things exactly like this more than I'd care to admit and I facepalm a lot. I completely forgot to recommend trying different sim chip which is one of the things I always check. My brother gets tired of me stealing his sim card to test my phone haha.
Happy to hear your phone is working!
Thank u all for ur help greatly appreciate it
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I717 Back from the Dead....AWESOME THANKS!!!
WoW I just about wrote off my I717 after a botched JellyBean upgrade. Came across this file and thought it was too good to be true...but is wasn't...GREAT THANKS!!!
Related
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.
Hey I recently rooted my Samsung Galaxy S II I9100, at first everything was fine, but i had some trouble installing apps so i used es file manager to install them, it began to work for some apps. anyway, this morning I woke and turned it on and it didn't get past the bootscreen(i left it for about 45 minutes on one occasion, and I tried rebooting many times.
The first thing i did after attempting to boot my device was to flash the kernel again via odin, this did not work(tried twice).
so i did a lot of research over the past 10 hours into my problem and have tried many different things; installing a stock rom, removing battery, pretty much anything on the forums that people said have worked. nothing.
I can get into recovery mode and download mode.
I don't care about my data on my phone, it has already been wiped.
It's still covered by warranty so i can wipe the flash count(?) and send it in for warranty IF I HAVE TO. preferably not however.
although i highly doubt it, I may have been using the wrong rom, and I may have forgotten to reset my phone before one of the re-flash's
So if you havn't figured out my question by now, how do i return my phone to working condition?
Don't get mad at me for making a thread that has probably been made a hundred times, none of the solutions in the other threads fixed my problems, and I was browsing not only xda but other forums for hours, I found that reason enough to post a new thread. Apologies if this is in the wrong section, I am new here, and never found it necessary to create an account until now, when I couldn't find a solution.
Help is appreciated, this problem is really rustling my Jimmies on Christmas day.
because this is such a problem, I will REWARD anyone who presents a working solution that does not involve sending it off for warranty or buying a jig. Sorry if i missed out some information, please request for missing info in a response.
1.forget about warranty and jig....that has nothing to do with your current situation.
2.post the details about your phone and what firmware your on and what crap you were flashing.
Maybe a simple reset/wipe in stock recovery is needed.
.
theunderling said:
1.forget about warranty and jig....that has nothing to do with your current situation.
2.post the details about your phone and what firmware your on and what crap you were flashing.
Maybe a simple reset/wipe in stock recovery is needed.
Click to expand...
Click to collapse
originally i was on ics 4.0.3, and i used this tutorial galaxys2root.com/galaxy-s2-root/how-to-root-galaxy-s2-i9100-icsandroid-4-0/ (can't post url link because im a new user) and this kernel by the file name "CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5.tar". I then searched for stock roms for it and got "CF-Root-SGS2_XX_OXA_KP8-v5.2-CWM5.tar" and "CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.tar"
If you want a stock rom go to Sammobile,join(so you can download).....then input smartphone>android>your phone model>your country/carrier.
Choose whatever 4.0.3 it recommends after you input the above and hit send.
Then flash that with Odin and see what happens.
Then report back here.
I am from Australia and when I searched for roms for the I9100, no Australian roms showed :s
would one from another country work, or would that be locked or...?
Theres 3 listed for starters for the plain gt-i9100.....is that your exact model....or is it p/g/m etc.
This is why I asked for your model.
gt-i9100 is my model that's all it said in my phone information in the settings (before it stuffed up), manual, on start up and in download mode.
sorry, I'm not excellent with my technical android terminology.
false alarm, it just didn't load properly before, I will start a the download (will take like 15 minutes) and report back when i flash it. gt-i9100 is definitely my model.
You just input which one of these 3 applies,hit send,then download.
Then flash it (the extracted file)in download mode with Odin.
so i put the extracted file in the 'PDA' field, put it into download mode, plug it in and start the process?
Yep.
It failed the first 2 tries, I think I have a bad usb cord, but worked the third, might of been what stuffed it up in the first place maybe (?), thank you so much for your help man
Good.Wait til boxing day til you flash siyah-s2.v.4.1.5 kernel for root.......lol.
hehe... yeah... I'm not going to try root again... lol
syntaxibles said:
It failed the first 2 tries, I think I have a bad usb cord, but worked the third, might of been what stuffed it up in the first place maybe (?), thank you so much for your help man
Click to expand...
Click to collapse
Going back to your first post,maybe you could make a donation to one of the developers on this site of your choosing.
sounds good, which developer in particular would be a good choice?
I quite like Doomlord,but its up to you
And just post back on this thread if you need help rooting etc.
Usually I'm the one answering these types of questions, but my knowledge of these operations has been quite outdated since ICS came around.
I have to help a neighbor return his phone to stock--the modem, the recovery, the ROM....the whole kit and kaboodle (wow that's a stupid saying...haha) before replacing it.
I'd start by backing up all SD data, all apps, and then transferring the contacts over to the sim, so he can use a backup phone between the time the old one is on its way out, and the new one/replacement is on its way in.
Next would be on to the flash counter...it just needs to say 0 really. I understand that there'll always be a way to tell it's been modified, but if it says zero, it will cool some minds. The flash counter reset that's been around...it still works, right? There's no reason why a change from GB to ICS, and on to JB would cause it to suddenly brick a phone, right?
After that comes the tricky part. My knowledge of ODIN and ADB are acceptable, to doing the actual flashing shouldn't be the issue. The issue is that we don't have a nandroid, and even if we did, we'd still need to replace the CWM recovery with the stock one. In addition to the above, my knowledge of RTS's is from the old days--heralding all the way back to the Gingerbread times..../sigh...those were the days. So here comes the part(s) I need help with. I spent hours and hours flipping through search after search, thread after thread, comment after comment. And threads that hit the key words are all dead, have dead links, or haven't had any activity in them since before ICS was officially released. This means that there is no anecdotal evidence of someone doing what I'm trying to with a setup that's similar.
So...I need an overview--just a generalized one-- so I choose the right process, instructions, downloads, etc.
Can you gentlemen/gentle ladies give me a hand, and tell me what I need/need to do, and what threads I should follow? Hopefully my Karma here in the Q&A is strong!
Sent from my Transformer using XDA Premium HD app
I use the flash counter reset zip found here first; http://forum.xda-developers.com/showpost.php?p=24145452&postcount=1
Then I use Kies to return everything else to 100% stock. (Title of the thred says return to GB, because that was the latest supported rom at the time, Kies will return you to the latest supported rom which is now UCLF6) Just did this same procedure last week, it's by far the easiest method! http://forum.xda-developers.com/showpost.php?p=27869730&postcount=1
First of all, I am not new to flashing, rooting and etc. I have helped many of my friends with custom roms and etc so flashing and Odin is not something I know nothing about.
However, I was asked by my friend that his S2 was running slow and wanted me to put a custom rom on there. So I did the usual thing of using the ZergRush method to give him root access and I tested Superuser with Root Checker and everything was fine. So I went to install a custom recovery (Phil's CWM) via Odin and using the latest tar file from Phil's website but this is where things didn't go according to plan.
When I hit the Start button in Odin, it did the normal thing of writing to the NAND but instead of taking the usual 8-10 seconds, it took a lot longer. I actually waited 20 minutes and nothing was happening. There was no indication on the S2 that anything was happening and Odin was still stuck on the NAND Writing with all the buttone grayed out. So I waited a bit longer and after 30 min I decided to close Odin and try again, but when I try to get into Download Mode, I got the message 'Software Update Fail'. I tried to flash the custom recovery again but when it gets to the NAND Write, it instantly goes to 'Fail'.
Out of the 8 Samsung phones I have rooted and put a custom rom on, this is the first time this has happened. I searched the forum but most of it point to a bricked phone. I know at this point is is pretty critical that I do not try any random thing and asking you guys for any advice. I have tried flashing with a different version of Odin and also on different computers but gave me the same result. So any help would be much appriciated.
Hopper8's 'Odin troubleshooting' guide; search for it. You need to try everything in that thread over & over & over, only way you're fixing it is if you get a successful Odin flash away. In particular flashing the 3 part firmware might fix it.
Given the alternative - motherboard replacement or new phone - keep trying stuff, these cases are sometimes fixed by persevering (for whatever reason the first 8 stock rom flashes you try don't work but the 9th does, etc)
Thanks for the information MistahBungle, I have tried most of what has been said but I have not tried the leaked rom for the i9100. I will definately give this a shot.
No worries The rationale with flashing the 3 part is it will wipe the phone & hopefully remove any 'remnants' of what was previously on the phone which might be causing issues. If that doesn't work, download a bunch of stock roms from Samfirmware (carrier/country doesn't matter, just make sure you DL I9100 firmwares) & start flashing, this sometimes solves problems like this as I mentioned in my PP. Good luck.
MistahBungle said:
No worries The rationale with flashing the 3 part is it will wipe the phone & hopefully remove any 'remnants' of what was previously on the phone which might be causing issues. If that doesn't work, download a bunch of stock roms from Samfirmware (carrier/country doesn't matter, just make sure you DL I9100 firmwares) & start flashing, this sometimes solves problems like this as I mentioned in my PP. Good luck.
Click to expand...
Click to collapse
Just giving you an update. The 3 part leaked rom did the trick! I been flashing for a few years now but never ever had Odin go wrong so this is a new experience for me. I really appricate your help with this, was so worried I stuffed up a friends phone.
Good news then No worries, glad you got it sorted (& you've still got a friend ). Yeah, that's a handy trick the 3 part, it's bailed a few people out. Don't forget to thank Hopper's OP in his thread.
Z-Blade said:
Just giving you an update. The 3 part leaked rom did the trick! I been flashing for a few years now but never ever had Odin go wrong so this is a new experience for me. I really appricate your help with this, was so worried I stuffed up a friends phone.
Click to expand...
Click to collapse
Good to see you got it working, always like hearing of people getting their (or not their own in your case) phone back to life
MistahBungle said:
Good news then No worries, glad you got it sorted (& you've still got a friend ). Yeah, that's a handy trick the 3 part, it's bailed a few people out. Don't forget to thank Hopper's OP in his thread.
Click to expand...
Click to collapse
Thanks for keeping on referring my thread, the more people it can help the better I'm working 6 days a week for now so haven't much time to go on Q&A and help out. Also thanks for before, I think you know what I'm referring to. Much appreciated. :good: