Related
I recently recovered my phone through ODIN and then upgraded to JI6 through Kies.....I wanted to re-root the phone and get it back to where it was before, but I'm having problems. I loaded the root file and put the update.zip in the root (not the avatar folder) and tried to update packages through recovery. I get an error message that says e:can't open /sdcard/update.zip no such file or directory. I checked the file type in both drives (avatar is on e: and everything else on g, the avatar folder shows a FAT file type, but the g: drive shows an unknown file type. I had received information to try a different update.zip file, but it won't change the error message I get when select update packages in recovery. What can I do? I've searched a lot of posts (and I risk a flaming on this one, I know), but I can't seem to find one that seems to follow my trail of getting to where I am at today. One last thing, when I was recovering through ODIN, i did not select repartition because i could not get the 512 pit file to populate in ODIN. Thanks to anybody who can help me (again).....
gtiryan said:
I recently recovered my phone through ODIN and then upgraded to JI6 through Kies.....I wanted to re-root the phone and get it back to where it was before, but I'm having problems. I loaded the root file and put the update.zip in the root (not the avatar folder) and tried to update packages through recovery. I get an error message that says e:can't open /sdcard/update.zip no such file or directory. I checked the file type in both drives (avatar is on e: and everything else on g, the avatar folder shows a FAT file type, but the g: drive shows an unknown file type. I had received information to try a different update.zip file, but it won't change the error message I get when select update packages in recovery. What can I do? I've searched a lot of posts (and I risk a flaming on this one, I know), but I can't seem to find one that seems to follow my trail of getting to where I am at today. One last thing, when I was recovering through ODIN, i did not select repartition because i could not get the 512 pit file to populate in ODIN. Thanks to anybody who can help me (again).....
Click to expand...
Click to collapse
ok....
are you SURE you are putting update.zip on the right sd card....it goes on the INTERNAL CARD ( the 16gb one )...
I'm pretty sure I am, this is the one where all of the apps and apk were stored previously?
ok then start over...
odin back to stock and re-root
ok, ODIN back to stock. No change for the update.zip. This time when I flashed I added the pit file, and also checked repartition. No change in anything regarding the message or anything from before. I have tried tyhe update before and after I went from JFD to JI6. I really have no basis to speak from, but it seems that the path from my e drive (avatar) to g drive (everything else), is where the problem is, or else I got a bad flash. They all look the same though. I assume I would need root to get anywhere other than JI6 anyway. Thanks again for your help with this. I do appreciate it.....
gtiryan said:
ok, ODIN back to stock. No change for the update.zip. This time when I flashed I added the pit file, and also checked repartition. No change in anything regarding the message or anything from before. I have tried tyhe update before and after I went from JFD to JI6. I really have no basis to speak from, but it seems that the path from my e drive (avatar) to g drive (everything else), is where the problem is, or else I got a bad flash. They all look the same though. I assume I would need root to get anywhere other than JI6 anyway. Thanks again for your help with this. I do appreciate it.....
Click to expand...
Click to collapse
ok....
1. when you Odin you are supposed to load both pit and tar files and not check repartition...
2.read that...http://forum.xda-developers.com/showthread.php?t=849028
3. are you trying to go to a stock JI6 ROM?? If so...why??
My suggestion:
Click on the Noob Guide (signature)
Download files
Load ODIN
Get phone in download mode
follow my instructions in the guide
You will then have a stock froyo leak + root
at that point I would backup, then flash something, maybe NeroV3 and then enable voodoo (if you like).
I don't see how the alt method could lead you wrong.
I apologize, I sincerely didn't notice anything that mentioned not to partition. Going forward, if I reflash through odin with the right pit and tar files WITHOUT checking partition, do you think I should be ok? As a note (if it even matters), all of my files and things were still in the internal sd card, although the new market is there from my old 2.1 rom. Not sure if it matters, just more information.
gtiryan said:
I apologize, I sincerely didn't notice anything that mentioned not to partition. Going forward, if I reflash through odin with the right pit and tar files WITHOUT checking partition, do you think I should be ok? As a note (if it even matters), all of my files and things were still in the internal sd card, although the new market is there from my old 2.1 rom. Not sure if it matters, just more information.
Click to expand...
Click to collapse
just follow s15274n's guide...he wrote a nice guide for noobs (no offense)...it'll walk u through going back to stock and you'll be ok...
Excellent information, but one question since I'm still learning. Not in the way I had hoped, but trial-by-fire.....If I download the leaked froyo with root, don't I need root access first. Also if I can flash this through ODIN, where does the update file go in the ODIN screen, do I need the 512 pit file, what about the pda, phone csc windows, what do i poopulate in those options, if any. I do bow to your experience and knowledge. I promise once I get back to where I was before I may never do this again! All this from trying to flash a new kernal that was supposed to be compatible with all bionix platforms (I was running 1.9 w/jac's ocuv). Thanks again....
gtiryan said:
Excellent information, but one question since I'm still learning. Not in the way I had hoped, but trial-by-fire.....If I download the leaked froyo with root, don't I need root access first. Also if I can flash this through ODIN, where does the update file go in the ODIN screen, do I need the 512 pit file, what about the pda, phone csc windows, what do i poopulate in those options, if any. I do bow to your experience and knowledge. I promise once I get back to where I was before I may never do this again! All this from trying to flash a new kernal that was supposed to be compatible with all bionix platforms (I was running 1.9 w/jac's ocuv). Thanks again....
Click to expand...
Click to collapse
(sigh)....
ok in Odin....as long as the phone is in Download mode...Odin has root access to the phone(technically) so just make sure you're in download mode...
Odin needs 2 files to flash a VIBRANT to stock...the pit and tar files...load the pit file in the PIT field and the tar goes in the PDA field..( i know its tricky) dont mess with any other settings...click start and WAIT
Odin is a flasher's best friend....learn to use it and you'll love it
In process now. I do like ODIN although yesterday afternoon, I would have rather taken a sharp instrument to the neck rather than use it. I preferred to use ROM manager or other methods. I know it means nothing to you guys that have experience, but this is a learning experience and one I am grateful for with all of the experience on these forums. I know you devs don't like these dumb questions, but sometimes kids just want to be professional football players but end up working in a supermarket instead....get back to you soon.
it said updating firmware then it's sitting on cache.rfs for about 5 minutes. no green loading symbol like when I flashed before. Not sure if I should unplug and retry....
waited about 20 minutes with it stuck at the cache.rfs line. Unplugged and retried. Same thing. I need to get a working phone at least for tonight. I tried one more time, but check repartition and it started loading completely. Maybe there's something wrong with one of the files? Not sure. Will update when I get home to my laptop.....
Use this version of ODIN (older versions are known to hang)
http://forum.xda-developers.com/showpost.php?p=8863820&postcount=138
The files you need to get the leaked froyo + root: CLICK HERE TO DOWNLOAD
(IGNORE THE OLD OLDN VERSION IN THIS .ZIP - USE THE ONE I POSTED ABOVE)
1 - download the files to your pc
2 - open ODIN on your pc
3 - connect USB to pc (not to the phone)
4 - power off phone
5 - go into download mode (hold both volume keys... then insert usb to the phone)
6 - ODIN should be connected, and you should be in download mode
7 - load pit file
8 - load tar file
9 - click start
10 - it will run it's course, once done the phone will reboot
11 - once rebooted, go to stock recovery and wipe data/cache (I made this bold below for emphasis since not in the video)
I gotta hand it you guys, you really bailed me out and for that I am eternally grateful. I will have to scrape the funds together for whomever needs a donation, but it is well worth it. I have one last remaining question. Now that I have Eugene's Rom, am I safe to flash another ROM by update.zip, or is ODIN the only reliable way for me to get one on the phone. I like the phone better now, but it seems like it is an out of the box ROM, which is fine. I didn't mind bionix 1.9 on 2.1 either. I just made a big mistake. Anyways, thanks again, and whomever can answer my last question I will extend my thanks in advance!!
Download rom manager
Flash cwr
Make backup in cwr
D nownload nero v3
Flash it in cwr
Enable voodoo if you desires
Enjoy your much improved phone that has a stable backup for an emergency.
I you need detailedsteps for this, read my sticky threads.
I dowloaded ROM manager last night and flashed recovery. I went to recovery and applied packages. I'm still getting this error that says the update.zip file is invalid through my e: drive (avatar folder). I just looked on both e and f. I can't seem to find any update.zip file on either card and I can't seem to flash any other ROM or even enter CW recovery. I looked at another post from someone and noticed that I never pulled my external sd card when I used ODIN to go back to stock or flash Eugene's ROM that I was suggested to use. Any formats I could try or tricks to suggest. I've looked around, but I'm not sure if this is a partition issue, an sd card (internal or external), or otherwise. Thanks again....
i noticed that there were a lot of additional file in places i didn't notice originally. I found in the CW file a recover-update and I thought that might be confusing things, I put it in a seperate folder and retried cw recovery, but that didn't work.
Problem: Whenever I boot my phone after the galaxy S logo dissapears the screen stays black, while the backlight on the touch sensitive buttons still come on.
So here is my background on what I have done with the phone
- It is on 2.1 Eclair
- Everything was fine. I had it rooted and running Bionix.
- When the problem started was when I was trying to install a matrix boot image, and a theme for Bionix.
- First symptons would it wouldnt get past the Vibrant (text) startup screen.
- In response I Restored to the Clockwork mod Restore which would have brang my phone back to normal.
- It did bring my phone back to normal except for one thing, there was a bug that said my cards were full and couldnt install any apps.
- So I went back into clockwork mod recovery and figured out quickly it didnt recognize my sd ext. But when my phone was on it did.
I understand that this problem is very out of now where and probably isnt very solveable with just a one click program. But I would be very thankful if anyone could give me any kind of information on this. Even if it is just saying "Its a problem with your Kernel". AlthoughI hope to see downloads and full instructions.
Thank for reading this.
CWM recovery is not supposed to be able to see your external sd, you are only supposed to be able to flash files from the internal sd.
Thanks given.
Do you know of any method I can do to fix this
You could Odin back to stock 2.1, but first turn off lag fix if there is one via voodoo app.
You want to ODIN using stock firmware and the 512 pit file. This will repartition your internal SD. You will (should) not lose personal data such as pictures, music, files.... You ended up trying to flash a theme or bootanimation that was not compatiable and when you restored traces of it have been left behind.
ODIN is the best method in these situations. Note that in rare cases it may be neccessary to do a full SD reformat.
The first thing you want to do is back everything up to your computer. All those pictures, music anything you want saved and then and only then try the odin with 512 pit.
If you need the files for odin you can check my sig for the odin exe pit file and tar file, if instead you need instructions on how to use odin i'd check here: http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
shreddintyres said:
If you need the files for odin you can check my sig for the odin exe pit file and tar file, if instead you need instructions on how to use odin i'd check here: http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Click to expand...
Click to collapse
Thanks for referring, I've also included the files in the guide just in case.
I certainly hope you aren't in a partitioning brick situation. I've seen this now twice and both were running Bionix 1.3.1 w/ Voodoo enabled and both somehow got certain bml partitions in an recognizable format by CWM and the Android OS. So far it hasn't been fixable with conventional flashing and PIT repartitioning. I will be trying a full JTAG re-write on one of the customer's phones tonight. I'll report back to this thread whether a JTAG session in which I fully re-write all addresses in the NAND block was able to fix this.
This marks the 3rd instance of what I'm referring to as partitioning bricking that was involved on a Vibrant that was running Bionix 1.3.1 at the time of the brick. I'm not blaming the ROM or the developer as I have used it with no issues and it's a great piece of work but perhaps the CWM packaged with it is allowing users to do things they don't intend to do causing this issue.
Thank you everyone very much for all the information and I was able to restore my phone back to stock 2.1 Eclair and then I flashed the rom bionix onto it.
I have given thanks to everyone that has posted from here on up ^^
Also if anyone is stuck in this situation also and Is reading this thing saying "what the heck I have no idea what to do". Just message me and I could full througho instructions.
Once again thank everyone and I have solved my problem. I am pretty sure it was the boot logo that made it happen.
Flashed ICS using odin. During this process we tick repartion checkbox and select a .pit file (along with PDA,PHONE,CSC). No other rom i have flashed requires this.
I wish to return to gingerbread rom at some point. the stock rom i have only requires me to select PDA as other packages-phone+csc are contained within it. However the .PIT file is not.
So my question is if i simply flash stock rom back, won't that leave the .pit in the same state it was running ics ??
PIT included in XXKP8 is the same PIT as before. So IMHO You do not need to repartition while flashing. There were people that flashed ICS sucessfully without repartition. It also means that no repartition is needed when returning to GB.
As far as I know there is only one official PIT for SGS2 - u1_02_20110310_emmc_EXT4.pit (md5: 1c7c7cf5a1955f7908a59181a52091ab), so flashing it does completly nothing (apart from increasing risk of bad flash) as Your device already contains it.
Regards
Slig
I did try flashing without .pit or repartition but didnt work.
the problems i foresaw =
Originally running 2.3.4, after flashing ICS, I now can not run any version before 2.3.6 only this and ICS.
If .pit is same maybe i should just tick repartition when flashing 2.3.4 ??
Try reading this thread, ultramag69 managed to fix the same issue you are having, and they list the steps they went though.
Solved. If i want to swap between gingerbread and ics i have to repartition and add .pit. Phone will not mount anything unless i do this. Others have had no trouble without but for me i simply have to repartition and add .pit.
I would be very thankful to anybody who can help me recover my phone.
I have an S2.
I wanted to customize it so I embarked on my documentation on this forum.
I built quite an understanding about what the steps are.
For a lack of a centralized guide I resorted to using
http://forum.xda-developers.com/showthread.php?t=1311081
wary of the flash counter issue.
I was well aware that this thread is for the AT&T version.
I managed to root succesfully (ZergRush).
Unfortunately I had to take a long break in the process (2-3 months). When I came back I only selectively remembered all the caveats.
So the fact that the guide is not for the i9100 version escaped me.
Focused too much on the details of getting the process right that the big picture went past me - I was on the wrong forum!! (((
I installed MobileOdin, and obliviously got the latest Entropy kernel.
It installed OK.
However my home and back buttons stopped working.
Upon realization of my mistake (i777 kernel over i9100 hardware) I tried to recover by installing a CF-Root version (Unfortunately my original kernel version was lost, so I had to guess the version by reading posts with similar situations - Orange UK i9100)
I found a post suggesting to install
CF-Root-SGS2_XX_OXA_KG3-v4.1-CWM4.zip
Again I used MobileOdin but this time at reboot the phone hangs on the welcome logo screen.
If I boot into recovery I get the CWM menu alright.
However I get a list of errors at mounting recovery - see attached photo.
If I select anything from sdcard I just get the fedora hat logo and nothing shows up - have to go back by pushing power.
Any help is very apprecitated - how can I get a proper kernel in?
SDCards do not seem to be read either, just the hat logo and nothing happens.
How can I get a zip with the kernel onto the phone storage so to pick it up in CWM recovery and install it?
Thanks a lot for any input.
Can't you just flash a kernel (Siyah for example) through Odin (not Mobile Odin), or even flash a custom rom through it which replaces your kernel?
Sent from the Matrix
Donnie Sins said:
Can't you just flash a kernel (Siyah for example) through Odin (not Mobile Odin), or even flash a custom rom through it which replaces your kernel?
Sent from the Matrix
Click to expand...
Click to collapse
Thanks for the quick reply.
If I use Odin won't that increase the pesky flash counter?
I would much rather flash a stock kernel, would that keep the counter the way it is?
If so, could you please link me to a stock gingerbread stock kernel?
Many thanks
DorinAlex said:
Thanks for the quick reply.
If I use Odin won't that increase the pesky flash counter?
I would much rather flash a stock kernel, would that keep the counter the way it is?
If so, could you please link me to a stock gingerbread stock kernel?
Many thanks
Click to expand...
Click to collapse
That's true, but why is that a problem for you? However, there are ways to 'reset' this counter (search for it here on xda if you really want this). If you have Siyah working, you can enter Recovery Mode again and you can start flashing.
Sent from the Matrix
DorinAlex said:
Thanks for the quick reply.
If I use Odin won't that increase the pesky flash counter?
I would much rather flash a stock kernel, would that keep the counter the way it is?
If so, could you please link me to a stock gingerbread stock kernel?
Many thanks
Click to expand...
Click to collapse
I think you should focus on your kernal problem first once you get the phone squared away then get the triangle away app to reset your counter
GT-I9100 powered by
NeatRom Lite 4.0
Philz kernal 3.81
Many40's battery tweaks
Flash a custom ROM via Odin, I suggest LiteingRom... Then go from there...
Sent from Valhalla :mwhahaha:
Can anybody confirm that if I flash a stock, non-custom, kernel :
1. The flash counter doesn't increase
2. The CWM recovery console doesn't get replaced
Thanks so much
1) Yes.
2) If you flash a stock kernel (or any kernel for that matter) you will have the recovery that comes with that kernel I.E standard Android recovery in the case of non-rooted stock (if you flash a CFRoot kernel, which is essentially a stock kernel with root, then you'll have CWM recovery). Recovery is baked into the kernel. You can flash temporary versions of CWM that will persist until the next reboot, but if you want CWM permanently, you need to run a kernel that has it.
MistahBungle said:
1) Yes.
2) If you flash a stock kernel (or any kernel for that matter) you will have the recovery that comes with that kernel I.E standard Android recovery in the case of non-rooted stock (if you flash a CFRoot kernel, which is essentially a stock kernel with root, then you'll have CWM recovery). Recovery is baked into the kernel. You can flash temporary versions of CWM that will persist until the next reboot, but if you want CWM permanently, you need to run a kernel that has it.
Click to expand...
Click to collapse
Thanks for the prompt authoritative answers.
Given the above, can I also please ask for your suggestion to solve my problem?
i.e.: phone kernel is messed up, cannot boot, recovery is unresponsive when accessing storage. would like to keep flash counter down.
hopefully download mode works to flash new kernels (haven't tried it yet have to decide on the kernel)
Should I go with:
a) flash stock kernel using PC Odin, re-root, apply proper CF-Root custom kernel (flash counter not increasing?)
or
b) flash proper CF-Root using PC Odin (hoping counter doesn't increase)
In any case, can you be so kind as to direct me to the proper version of stock and CF-Root? The one I guessed by myself got me in this mess in the first place
CF-Root-SGS2_XX_OXA_KG3-v4.1-CWM4.zip
Or is this one right, if I don't mess it up again with Entropy?
All the kernels should be Gingerbread - since I am OK with rooting it without making a mess of myself.
Ideally, on top of the kernel names, could you please give me a URL to the location of the kernel files as well, if there is a recommended one.
Cheers
Much appreciated
Scenario A.
Your phone isn't working (I presume it's still not ?), your first priority should be getting the phone working properly. Back to stock, then you can root/flash another rom/whatever.
P.S - Forget the flash counter. You seem obsessed with it. It's irrelevant unless you have to return the phone for a warranty claim. In that case, reset the counter with Triangle Away if you're running recent firmware or a jig if you're running GB (and 'old' bootloader) at the time. At the very least worry about getting the phone up and running normally before you start fretting about flash counters.
MistahBungle said:
Scenario A.
Your phone isn't working (I presume it's still not ?), your first priority should be getting the phone working properly. Back to stock, then you can root/flash another rom/whatever.
P.S - Forget the flash counter. You seem obsessed with it. It's irrelevant unless you have to return the phone for a warranty claim. In that case, reset the counter with Triangle Away if you're running recent firmware or a jig if you're running GB (and 'old' bootloader) at the time. At the very least worry about getting the phone up and running normally before you start fretting about flash counters.
Click to expand...
Click to collapse
You are right I should worry about the phone. Probably in denial about it being bricked :s
So yes, get stock back in.
Considering I still have some data to back up from the phone before upgrading from GB to latest (phone was on GB before the messiness), I suppose it is better to get a GB kernel in, am I correct?
In this case, can I please kindly ask for the location of a stock kernel to download? Is it safe to get any version of GB in?
Thanks for helping me with this
If you're currently running GB firmware, the phone won't boot without a GB kernel.
Try Samfirmware or AndroidFirmwares.net. If you can't find the kernel you're after, download the entire rom & extract the zImage from the rom package. You can flash this in the PDA section of Odin. If you don't know what firmware you're running, you're going to have to flash an entire rom. In that case, it probably doesn't make much difference which rom you flash. If you flash an entire rom, you can probably kiss any data stored on the internal SD card goodbye tho.
DorinAlex said:
You are right I should worry about the phone. Probably in denial about it being bricked :s
So yes, get stock back in.
Considering I still have some data to back up from the phone before upgrading from GB to latest (phone was on GB before the messiness), I suppose it is better to get a GB kernel in, am I correct?
In this case, can I please kindly ask for the location of a stock kernel to download? Is it safe to get any version of GB in?
Thanks for helping me with this
Click to expand...
Click to collapse
Thanks to the nice people at http://androidromupdate.com/category/orange/ I was able to locate the exact version I was having since they are storing official versions for each operator.
So I am going to go ahead and try to reflash the correct kernel for my rom using Odin.
My first hurdle is that in Odin 3.07 when I select PDA the file selection box doesn't alow zImage to be shown in the window. I am able to select it by typing zImage.
Is this Ok to start flashing just having selected zImage as PDA?
Seems kinda hacky, especially since here is where you put the whole rom tar.md5.
Should I go ahead? What is the proper why to flash just the kernel with Odin?
Many thanks
The 'proper' way to flash a kernel in Odin is (if you have a package containing just the kernel) is to put it in the PDA section & flash.
Obviously you don't have that; you have an entire rom package & extracted the zImage, correct ? So obviously you'll be flashing that.
Pro tip: Don't use Odin 3.07, use 1.85 (If I see a post from you asking 'But whyyyy ???' I won't be responding. Just trust me).
So as I believe I've already said in a post the other day, you can flash the kernel on its own or the entire rom (which will obviously flash the kernel as well given the kernel is in the rom package). If you'd simply gone back & re-read what was said then, your phone would be fixed already. The instructions were pretty simple/clear.
So it's up to you what you flash. However, you've already been given every single bit of info (and some) you need to fix your phone. More posts when you could be fixing your phone is just delaying same.
I was just about to sincerely thank you for your help, but then again your attitude has surpassed any such attempt.
As a note of courtesy: if it's an ordeal to answer specific questions to well defined problems, don't. Nobody is forcing you to answer - I suppose there are members around here who are more helpful and polite in relating to people's problems. You know, people asking questions here are trying to discover knowledge you possess and have been given by others on your turn. You shouldn't be so anal giving back to the community.
As I was pointing out in my last thread - if you had bothered to comprehend it - what you were suggesting to do was not reflected in practice.
1. Odin doesn't accept zImage files for PDA - you have to hackingly add it in the file selector box.
2. There is no sign in its GUI that Odin accepts zImage file for PDA, as mainly the PDA box is used for full roms (.tar, .tar.md5)
I simply asked for confirmation that your suggested instructions - unnatural as they have turned out to be - are the right ones.
Usually when somebody suggests some actions that are not straightforward they try their best to express themselves eloquently. This wasn't the case, so I only wanted a confirmation.
But you've made it clear this time, think twice before asking for more info around here - incomplete/inaccurate information is something to deal with on your own.
Here is an update with the status of my problem.
I was able to guess out the missing information/step from the previous posts:
The file that goes into the PDA box in Odin has to be a tar file containing the various image files one needs to flash into the phone and not directly the zImage file.
Quick recap: I had a rooted phone with an original branded rom that I had successfully rooted. I flashed a custom kernel (Entropy) that was for the AT&T version of SGS2 and some buttons were not working. I then tried CF-root for Gingerbread (guessed version). After this the phone does not go past the original logo screen when booting. I used MobileOdin both times. Recovery is CWM 4 but I get cache errors, and no access to sdcard works. Download mode seems to be OK.
I have created a tar file with just the zImage file from the full branded rom that was on my phone. (I9100BVKJ4_I9100ORAKJ4_I9100BVKJ4_HOME.tar.md5)
Using Odin 1.85 I have used the newly created tar file to flash.
Everything in the window looks like Odin snapshots on guides all around the web. After clicking start in the first big box KERNEL is shown.
I get:
<ID:0/034> Added!!
<ID:0/034> Odin v.3 engine (ID:34)..
<ID:0/034> File analysis..
<ID:0/034> SetupConnection..
<ID:0/034> Initialzation..
<ID:0/034> Get PIT for mapping..
<ID:0/034> Firmware update start..
<ID:0/034> zImage
And then nothing happens.
I have tried on two laptops, rebooted, installed kies fresh on one of them with the same result.
I wouldn't flash the whole rom just yet, since I still hope to recover some data.
What could be wrong?
I have searched quite extensively for Odin info online but people didn't seem to come across something like this.
Thanks for any help
DorinAlex said:
Here is an update with the status of my problem.
I was able to guess out the missing information/step from the previous posts:
The file that goes into the PDA box in Odin has to be a tar file containing the various image files one needs to flash into the phone and not directly the zImage file.
Quick recap: I had a rooted phone with an original branded rom that I had successfully rooted. I flashed a custom kernel (Entropy) that was for the AT&T version of SGS2 and some buttons were not working. I then tried CF-root for Gingerbread (guessed version). After this the phone does not go past the original logo screen when booting. I used MobileOdin both times. Recovery is CWM 4 but I get cache errors, and no access to sdcard works. Download mode seems to be OK.
I have created a tar file with just the zImage file from the full branded rom that was on my phone. (I9100BVKJ4_I9100ORAKJ4_I9100BVKJ4_HOME.tar.md5)
Using Odin 1.85 I have used the newly created tar file to flash.
Everything in the window looks like Odin snapshots on guides all around the web. After clicking start in the first big box KERNEL is shown.
I get:
<ID:0/034> Added!!
<ID:0/034> Odin v.3 engine (ID:34)..
<ID:0/034> File analysis..
<ID:0/034> SetupConnection..
<ID:0/034> Initialzation..
<ID:0/034> Get PIT for mapping..
<ID:0/034> Firmware update start..
<ID:0/034> zImage
And then nothing happens.
I have tried on two laptops, rebooted, installed kies fresh on one of them with the same result.
I wouldn't flash the whole rom just yet, since I still hope to recover some data.
What could be wrong?
I have searched quite extensively for Odin info online but people didn't seem to come across something like this.
Thanks for any help
Click to expand...
Click to collapse
Expect the SMS and call logs , all your data is safe IMHO. Contacts are backed up in your google account. and Internal SD is not formatted in a factory reset.
---------- Post added at 12:30 PM ---------- Previous post was at 12:18 PM ----------
also don't worry about yellow triangle and try a custom kernel. You will be able to remove it eithr by USB jig (on GB rom) or us triangle away http://forum.xda-developers.com/showthread.php?t=1494114
DorinAlex said:
I was just about to sincerely thank you for your help, but then again your attitude has surpassed any such attempt.
As a note of courtesy: if it's an ordeal to answer specific questions to well defined problems, don't. Nobody is forcing you to answer - I suppose there are members around here who are more helpful and polite in relating to people's problems. You know, people asking questions here are trying to discover knowledge you possess and have been given by others on your turn. You shouldn't be so anal giving back to the community.
Click to expand...
Click to collapse
Jesus, get over yourself. Just thank the person that he or she had taken the time to post a reply and at least try to help you because I personally wouldn't and won't give you the time of day.
If you are too bone idle to look up the solution to your problem and check out other users past experience and knowledge then why should anyone else waste their time helping.
Sent from my GT-I9100 using xda premium
The last post is a monument of self-sufficience and lack of helpfulness.
mckeowngoo said:
Jesus, get over yourself. Just thank the person that he or she had taken the time to post a reply and at least try to help you because I personally wouldn't and won't give you the time of day.
Click to expand...
Click to collapse
Guess what, you just did. Just in your manner, of conceited aggressivity
If you are too bone idle to look up the solution to your problem and check out other users past experience and knowledge then why should anyone else waste their time helping.
Click to expand...
Click to collapse
This last one is awash with fallacy and misconceptions, that I just have to keep the flame going.
It shows a complete lack of understangind of how a forum works. It's not that the question asker expects the replier to do the work of searching.
A forum relies on the presence of experienced users (i.e. people who have previously gone through the pains of learning how a thing works) who are checking up what issues less experienced people are encountering.
If they are not so high on themselves the latter more experienced users, who are also keen to return to the community what they may have on their turn been taught previously by peers, when they see a problem they quickly know the answer to, will quickly reply and save valuable effort to the question asker.
It's not that every problem has a solution posted and you just have to "look it up" and you're saved.
Half true answers may delay more. Case in point.
The solution to just put zImage in PDA in Odin DOES NOT WORK.
You have to properly package a tar file, by following guides available on the forum. The wrong assumption that you can just put the zImage in the box has delayed me a lot.
It was false also that flashing the full rom will make me lose my data. I flashed the same version of my original rom and I got everything back.
So thanks to all who offered goodwill help.
Solution was:
Flashing same version of rom (official branded, easily traceable by operator and some basic memoryon officila firmware sites), full rom, that is.
Hi Guys,
I have been scouring the boards and the internet on a solution to this problem.
GF had the phone and put it to charge.
Picked it up sometime later and it was off.
Turned it back on and it was stuck in a bootloop.
Phone was using Stock Firmware and was unrooted. It was running Jelly Bean 4.1.2. The EXACT firmware eludes me.
Phone is able to go into Download mode and recovery mode.
I have included a picture of what recovery mode looks like. [pic]
I tried flashing via ODIN. I tried different firmwares. All of them stopped at Boot.bin
I tried Kernel flash via PDA and it stopped at "NAND Write Start!" and just stayed there.
I tried flashing a bootloader and the progress bar appeared (only time it ever appeared) but it stopped after a little budge and did not move again. Not even after 30 mins. [pic]
Is there anything else I can do? I followed all the tips from http://forum.xda-developers.com/showthread.php?t=1449771 and I'm still here. Any insight would be appreciated. Thank you.
Hopper8's "Odin troubleshooting' thread. Find it, try the stuff in it. All of it. Not just try a few things & then post here saying 'I tried everything' when you didn't. The only thing that will happen if you do that is you'll still have a busted phone. And you need to try the stuff in that thread repeatedly. Over and over. As many times as you need to.
That's the only way you're fixing it (the alternative involves paying a Samsung service centre a considerable amount of money to fix it). There are no easy/simple fixes in these situations.
Im pretty sure I was in exactly the same situation a while back.Youll need to look back at my posts as Ive forgotten exactly how I fixed it.
It did involve GB and pit files via odin as nothing would flash by recovery.
Im on 2.3.5 as that was about the only thing that would flash properly and make the phone boot.I initially thought I had a bootloader problem as ICS/JB wouldnt load.
I spent 5 hours on that,and cant recall if it was the pit or the special 2.3.5 rom/or both that fixed it.
theunderling said:
Im pretty sure I was in exactly the same situation a while back.Youll need to look back at my posts as Ive forgotten exactly how I fixed it.
It did involve GB and pit files via odin as nothing would flash by recovery.
Im on 2.3.5 as that was about the only thing that would flash properly and make the phone boot.I initially thought I had a bootloader problem as ICS/JB wouldnt load.
I spent 5 hours on that,and cant recall if it was the pit or the special 2.3.5 rom/or both that fixed it.
Click to expand...
Click to collapse
Thanks. I'll search your posts.
I think I posted a pic with similar errors to yours,so look and compare them.Theres not much info floating around about our/your problem.Pit files are only meant to be a last resort option,and I was in that category.
I also think that most/all things I flashed with odin passed,but phone would not boot,which led me to flash 2.3.5 combined with pit file.
I can't find your posts.....
Im only commenting because Im pretty sure its nothing to do with odin,I feel my phone and maybe yours has a hardware problem.I done a search before and only saw 1 situation like mines on another website.
For me,there was something major wrong for my phone not to accept ics/jb stock firmwares.
I have posted a pic before with the errors,and commented what I done to get the phone working.
I also dont think anyone on here can help,as it was the worst thing to fix Ive ever came across,and its not been mentioned on here.
Its up to you what you want to flash,but my moneys on a frankenstein GB rom c/w pit.Only try it at your own risk,or wait until someone else has alternative advice.
theunderling said:
Im only commenting because Im pretty sure its nothing to do with odin,I feel my phone and maybe yours has a hardware problem.I done a search before and only saw 1 situation like mines on another website.
For me,there was something major wrong for my phone not to accept ics/jb stock firmwares.
I have posted a pic before with the errors,and commented what I done to get the phone working.
I also dont think anyone on here can help,as it was the worst thing to fix Ive ever came across,and its not been mentioned on here.
Its up to you what you want to flash,but my moneys on a frankenstein GB rom c/w pit.Only try it at your own risk,or wait until someone else has alternative advice.
Click to expand...
Click to collapse
So I flashed the pit file.... and nothing happened. It just stopped there at "DO NOT TURN OFF TARGET!!!" I eventually closed ODIN but the phone still behaves the same way. If the EPROM is damaged, it won't have a partition to partition right? Any other suggestions?
I tried to flash CF root. Just to try anything. If hung up after kernel flash. Not it says I have a custom binary. Count 1. I don't know if that is relevant but... it shows something.
levi_jm said:
I tried to flash CF root. Just to try anything. If hung up after kernel flash. Not it says I have a custom binary. Count 1. I don't know if that is relevant but... it shows something.
Click to expand...
Click to collapse
Youll need to ignore half of my previous advice(about odin),and follow Mistahbungles advice.......as my memory is playing tricks on me.Also,it was the other way around in my case.....ICS/JB flashed ok,it was GB that wouldnt(but doesnt matter here).
You have a damaged partition table,so that hopefully will be fixed by flashing .pit using Odin.If you cant get Odin to work,you could try a friends pc,or see if a local shop has Odin working.
Apologies to you both for my memory.........lol
theunderling said:
Youll need to ignore half of my previous advice(about odin),and follow Mistahbungles advice.......as my memory is playing tricks on me.Also,it was the other way around in my case.....ICS/JB flashed ok,it was GB that wouldnt(but doesnt matter here).
You have a damaged partition table,so that hopefully will be fixed by flashing .pit using Odin.If you cant get Odin to work,you could try a friends pc,or see if a local shop has Odin working.
Apologies to you both for my memory.........lol
Click to expand...
Click to collapse
I did try his advice and with 6 different versions of odins on two different laptops with 6 usb ports between them. I don't think ODIN is the problem. I think the problem is a corrupted NAND. It is so corrupt that it did not accept a .PIT flash. It didn't hard brick the phone. It did nothing to it. I am unsure what else to do.
Well maybe I was right all along about odin,but that doesnt help anything.
I cant remember if I could do anything via recovery,but I do remember that several things I tried just kept giving that page of errors.
Youll just need to google each error and see what it throws up.Stuff thats said ranges from removing sd card to replace recovery(but by odin which you cant do).