Related
I have a Rogers i896 build 10.10 running froyo. I just tried to restore back to stock rogers froyo JL1 using Odin 1.81 and using a 512 pit file. I entered into download mode and the odin process complete then the phone reboots.
Now it entered into android system recovery <3e> . with this menu:
Reboot system now
reinstall packages
delete all user data
delete cache data
format internal sd-card
it also says the following...
update media, please wait
E: Can't mount /dev/block/stl10
(Invalid argument)
E:copy_db_data_media:Can't mount DBDATA:
your storage not prepared yet. please use UI menu for format and reboot actions
copy default media content failed.
Click to expand...
Click to collapse
I'm a complete noob at this.. I read a lot and thought i'll give it a shot to flash a new rom.
Update. Tried to reflash, didn't work.
Tried to reflash with Stock Rogers Eclair, didn't work just went to the Recovery <2e> same error message with can't mount ....
I think this is bricked...
Any way around this?
did you just use the pit file and thats it? did you use the tar file in the pda slot as well?
Pirateghost said:
did you just use the pit file and thats it? did you use the tar file in the pda slot as well?
Click to expand...
Click to collapse
I used the stock rogers froyo tar file from this link
http://forum.xda-developers.com/showthread.php?t=905042
My phone can't even be turned off. I tried all the options in the menu and it gives me the same error message.
I think the only way to turn it off is if I remove the battery
likiud said:
My phone can't even be turned off. I tried all the options in the menu and it gives me the same error message.
I think the only way to turn it off is if I remove the battery
Click to expand...
Click to collapse
Sounds like a bad flash, can you get into download mode and try a reflash?
I just pulled out the battery to turn it off, and managed to get to download mode again. This time I tried odin 1.7. Odin says passed... but still the same error message
One thing I noticed that the re-partition check box on odin is checked when i put the pit file in there. I didn't realized it was checked so I clicked start with that on. It wasn't checked when I first opened the program. I just tried to reflash with it off, and same result
Is there no one here that can fix it?
I did some more searching around and found this post from the i9000 forums...
http://forum.xda-developers.com/showpost.php?p=8683455&postcount=7
I guess I was suppose to uncheck re-partition and the stock rogers roms does not include cache.rfs and dbdata.rfs file inside.
Anyone know if there's a way to get a ROM that includes those files in them so I can reflash it?
here i used this stock 2.1 with odin 1.7 and it worked.
http://dl.dropbox.com/u/19201431/SGH-I896_UXJI2StockRogers2.1.zip
your phone isnt bricked. bricked is a specific thing and has a special screen.
flash 2.1 when doing stock. 2.2 stock includes 3e recovery and it requires all update.zip files to be digitally signed. there is a way around it but its extra steps. instructions here
http://forum.xda-developers.com/showthread.php?t=909213
I tried to flash to stock 2.1 with odin but same thing happened.
It boots into recovery and i can't do anything... except its 2e instead of 3e that i saw before.
whats the exact filesize of the tar you used?
also if you dont re-partition, you dont need a pit file. (the p stands for partition)
The exact file size for the TAR is 238 MB (250,420,736 bytes)
I didn't know PIT is re-partition until after the fact.
Ok, I'm going to see if I can get my phone in the same condition as yours and then fix it. BRB...
Broke it and fixed it. Details in a sec.
Ok my steps to break it:
Flashed UXJL1 with Odin 1.81 using 512.pit and repartition checked.
Boot lands in recovery with can't mount error.
Steps to fix.
Used Odin 1.81 to flash the JH2 firmware from this post: http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36.
Did not check partition, did not load a pit file.
I've seen that error before but I couldn't remember how I fixed it. I think the key is simply to Odin flash 2.1 firmware using no pit and no repartition. I chose the package above because it doesn't change your boot loader and is compatible with newer phones.
flash into the AT&T 2.1 with the one click, what you probably did was Odin into the rogers 2.2 without turnning off lagfix. for some reason the rogers version doesnt actually repartition your phone.
opcow said:
Ok, I'm going to see if I can get my phone in the same condition as yours and then fix it. BRB...
Broke it and fixed it. Details in a sec.
Ok my steps to break it:
Flashed UXJL1 with Odin 1.81 using 512.pit and repartition checked.
Boot lands in recovery with can't mount error.
Steps to fix.
Used Odin 1.81 to flash the JH2 firmware from this post: http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36.
Did not check partition, did not load a pit file.
I've seen that error before but I couldn't remember how I fixed it. I think the key is simply to Odin flash 2.1 firmware using no pit and no repartition. I chose the package above because it doesn't change your boot loader and is compatible with newer phones.
Click to expand...
Click to collapse
Thank you so much! This worked! Except it now shows ATT for a brief moment but that's not a big issue. I went ahead and installed Serendipity smoothly!
opcow said:
Ok, I'm going to see if I can get my phone in the same condition as yours and then fix it. BRB...
Broke it and fixed it. Details in a sec.
Ok my steps to break it:
Flashed UXJL1 with Odin 1.81 using 512.pit and repartition checked.
Boot lands in recovery with can't mount error.
Steps to fix.
Used Odin 1.81 to flash the JH2 firmware from this post: http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36.
Did not check partition, did not load a pit file.
I've seen that error before but I couldn't remember how I fixed it. I think the key is simply to Odin flash 2.1 firmware using no pit and no repartition. I chose the package above because it doesn't change your boot loader and is compatible with newer phones.
Click to expand...
Click to collapse
there is a new fix for reference! no ATT boot logo/ fix ATT boot logo and NO dbdata error!!!
http://forum.xda-developers.com/showthread.php?t=979133
link in my sig too!
A friend of mine is on a T-Mobile UK Samsung Galaxy S. He's stuck on a non-simlocked and non-netlocked 2.2 (JP3), T-Mobile UK aren't releasing 2.2.1 any time soon, and hence he wants to upgrade to an unbranded 2.2.1. He doesn't want to root it... he just wants to be on the same or similar firmware as I'm on (i.e. a stock, stable, UK, unrooted, no "lagfix", etc, 2.2.1).
He has Odin. He has the Windows drivers installed. But I have some questions.
I'm on JPY which has been perfect for me. Zero problems. Is there much advantage with JS5? What has changed/added between JPY and JS5?
Best place to get the European firmware is here? http://forum.xda-developers.com/showthread.php?t=846913
Does he need just a pit file, or other files (e.g. tar) too?
extorian said:
A friend of mine is on a T-Mobile UK Samsung Galaxy S. He's stuck on a non-simlocked and non-netlocked 2.2 (JP3), T-Mobile UK aren't releasing 2.2.1 any time soon, and hence he wants to upgrade to an unbranded 2.2.1. He doesn't want to root it... he just wants to be on the same or similar firmware as I'm on (i.e. a stock, stable, UK, unrooted, no "lagfix", etc, 2.2.1).
He has Odin. He has the Windows drivers installed. But I have some questions.
I'm on JPY which has been perfect for me. Zero problems. Is there much advantage with JS5? What has changed/added between JPY and JS5?
Best place to get the European firmware is here? http://forum.xda-developers.com/showthread.php?t=846913
Does he need just a pit file, or other files (e.g. tar) too?
Click to expand...
Click to collapse
JPY is the lastest UK rom pointless using anything else until its out for the UK
People here just love new numbers and letters.
if he is going from branded would be best to use a pit file. ( pit 512)
then flash the 3 JPY files.
I tend to debrand phones when I get them in as I don't think its fair being stuck on older versions.
So... download Odin + PIT from the top of that page I linked. Flash the 512 PIT using Odin with repartition. Download the JPY firmware from the same page. Flash the 3 files in there. Reboot. Done?
What about clearing cache? Factory reset?
Anything else?
Flashing with Odin will do the factory reset.
Sent from my GTI-9000 Using that XDA app thingy
We've hit a problem
He's been trying the files on this thread: http://forum.xda-developers.com/showthread.php?t=846913
He selected repartition, and flashed the PIT file + JPY_JPY_JPY.tar at the same time (although I believe we've tried one at a time too).
Now when he reboots his phone it doesn't boot - it just vibrates.
He's tried going into recovery and clearing the cache, user data, factory reset, etc.
He can still get into download mode and recovery.
Any suggestions?
extorian said:
We've hit a problem
He's been trying the files on this thread: http://forum.xda-developers.com/showthread.php?t=846913
He selected repartition, and flashed the PIT file + JPY_JPY_JPY.tar at the same time (although I believe we've tried one at a time too).
Now when he reboots his phone it doesn't boot - it just vibrates.
He's tried going into recovery and clearing the cache, user data, factory reset, etc.
He can still get into download mode and recovery.
Any suggestions?
Click to expand...
Click to collapse
Flash pit with repartition selected.
Wait till you see a green box with pass
Unplug phone take battery out.
Then put it back on download
Click reset it Odin
Untick repartition
Select all three jpy files.
Plug in phone. Click start.
Leave till you see green pass.
Sent from my GTI-9000 Using that XDA app thingy
All three files? Should they have come with the firmware download? That only contained a 300MB file JPY_JPY_JPY.tar.
extorian said:
All three files? Should they have come with the firmware download? That only contained a 300MB file JPY_JPY_JPY.tar.
Click to expand...
Click to collapse
Different to how I get them direct for Samsung. So wouldn't know sorry.
Sent from my GTI-9000 Using that XDA app thingy
Can we get the JPY firmware direct from Samsung?
No, but samfirmware.com has all those firmwares.
Yeah they have JPY. However it's just a 512 PIT file. Is that all he needs?
Thats what i flash JPY with .
Error solving with a rom install i usually wipe everything flash back to eclair with 512 pit and repartition . That works i then flash to Froyo no repartition .
jje
Still no joy
OK, so as per the instructions above (I think), we made sure the SIM and SD card are removed. Connected the phone. With Odin, ticked Repartition, and then flashed the 512 .pit file. Waited until we saw the green box in Odin with Pass on it. Unplugged the phone and took the battery out. Put battery back in and booted the phone into download mode. Clicked Reset in Odin. Made sure re-partition was unticked. Made sure the pit file is no longer selected. Added the JPY_JPY_JPY.tar to the PDA section. Plugged in phone. Clicked start. Left it until we saw green pass. On restarting the phone, it to boots past the Galaxy S splash screen and tune then there's a single vibrate followed by a double, which then repeats.
Did we do something wrong? We noticed in Recovery there is an error displayed:
E:can't mount /dev/block/st110 (invalid arguement)
E:copy_dbdata_media:cant mount DBDATA:
copy default media content failed
What else can we try to get to JPY?
The firmware from samfirmware.com and the firmware linked from the firmwares post on XDA (mentioned earlier) both give an identical JPY_JPY_JPY.tar. We've been unable to find any firmwares with the three JPY files in it. Anyone have a link? Or any other things we can try?
extorian said:
Still no joy
OK, so as per the instructions above (I think), we made sure the SIM and SD card are removed. Connected the phone. With Odin, ticked Repartition, and then flashed the 512 .pit file. Waited until we saw the green box in Odin with Pass on it. Unplugged the phone and took the battery out. Put battery back in and booted the phone into download mode. Clicked Reset in Odin. Made sure re-partition was unticked. Made sure the pit file is no longer selected. Added the JPY_JPY_JPY.tar to the PDA section. Plugged in phone. Clicked start. Left it until we saw green pass. On restarting the phone, it to boots past the Galaxy S splash screen and tune then there's a single vibrate followed by a double, which then repeats.
Did we do something wrong? We noticed in Recovery there is an error displayed:
E:can't mount /dev/block/st110 (invalid arguement)
E:copy_dbdata_media:cant mount DBDATA:
copy default media content failed
What else can we try to get to JPY?
The firmware from samfirmware.com and the firmware linked from the firmwares post on XDA (mentioned earlier) both give an identical JPY_JPY_JPY.tar. We've been unable to find any firmwares with the three JPY files in it. Anyone have a link? Or any other things we can try?
Click to expand...
Click to collapse
You only use the PIT file and choose re-partition when you have the 3 separate flashing files.
When you have the singe JPY tar file you do not select re-partition and do not use the PIT file - do the following:
put phone into download mode
open Odin
choose your single JPY file as the PDA
make sure "re-partition" is UNTICKED
DO NOT select your PIT file
connect your phone to PC via USB
Odin will detect your phone - click start
let Odin do its stuff until your phone restarts
you are now on 2.2.1 stock
I always do an immediate factory reset.....it seems to sort out any lags or issues that you occasionally get after flashing
good luck!
When he tries to just the .tar without repartition or .pit, Odin fails.
When he tries to format the internal SD card from Recovery it says:
E:can't mount /dev/block/st110 (invalid arguement)
E:copy_dbdata_media:cant mount DBDATA:
copy default media content failed
It could be that repartitioning previously has messed stuff up? Maybe the wrong PIT (we used 512)? I've read in a few places that Clockwork recovery can fix this. Thoughts?
Or is there a 3 file JPY option we can use?
So, according to this thread http://forum.xda-developers.com/showthread.php?t=784958#8180949 it seems we messed up the partitions by using the pit file originally with repartition. If JPY isn't a full firmware we'll need to flash back to a full firmware to fix it. For example he says "The reason for this screwup is because the JH7 tar package does not contain params or dbdata files, it's not meant to be a full installer- it's meant to be an upgrade. When you partitioned you deleted your existing dbdata and params partitions on your phone, so when JH7 tried to set them up they didn't exist."
We're going to try JPU (somewhere said that's a full update) with 512 pit + repartition, then if that boots update to JPY (no pit, no repartition).
FIXED!!!
After putting the three-file JPU on it from samfirmware.com with 512 pit and repartition, it booted up into 2.2.1 fine. We then flashed the JPY tar (no pit, no repartition), and it's working.
Thanks for the help guys.
Thats great news. X
Sent from my GT-I9000 using XDA App
Hi I am the friend that has caused the headache throughout this thread, I'd just like to say a big thank you to extorian and everyone else that provided input and solutions to getting the rom installed on my phone.
I'm over the moon with the update, phone runs better than ever. Thanks again.
Sent from my GT-I9000 using XDA App
I need some help... Please!
I have a I9000T galaxy S phone and I soft bricked it. This is the story:
I flashed my phone using Odin with ROM JPY_JPY_JPY (downloaded form samfirmware, only file: PDA), and then flashed supermod-kernel-k13d-500hz...then I uploaded Modem UGJL2 for Froyo as an update.zip file (to get band 850 mhz for my country) and applied successfully!
My phone worked as a charm. No bricking.
Then I realized that there was a newer ROM: I9000XWJS5 with the XEN thing.
Since the ROM has the 3 files (MODEM, CSC, and PDA) and I read that it needed a different PIT, I flashed with the re-partition checkbox checked and with the 803 pit file.
It didn't get through. It got stuck at flashing sbl.bin
I had to unplug it after several minutes and I realized that it was soft bricked. It didn't work but download.
I tried to go back to JPY. After many tries and errors (changing PIT to 512 and repartitioning), finally I could flash back to JPY ROM. At the end of the process it reboots and the system get into Android system recovery <3e>. I can read at the bottom the following signs:
E: Can't mount /dev/block/stl10 (invalid argument)
E: copy_dbdata_media: Can't mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed.
If I reboot the system, it boots and I see the splash "S" moving theme, and it seems that it is booting but then it stops and it starts vibrating from time to time... then the screen goes black and nothing happens (but vibrating from time to time). It never appeared the "login screen"
Reading here and there, some advised to flash first the speedmod-kernel with the PIT 512 file and re-partitioning. I did so, and then, after boot I was able to get into Clockworkmod recovery screen. The menu is green and the version is 2.5.1.0
Someone suggested to flash to JPU ROM (that way it fixed a similar problem) but when I did so, it takes me to the beginning (the process hung at sbl.bin)...
I've been flashing and reflashing with different options these 3 ROMs (JPU, JPY, JS5) the only one that completes the flashing successfully is JPY, and eventhough it tries to boot, it fails to present the logon screen (dots for password)... JPU and JS5 hang at sbl.bin and after that, no boot... freeze. I have to flash back to JPY.
I have read tons of forums, I have learned a lot, but I believe I need deeper advices.
Thanks in advance!
Some further information. JPU, JPY, JS5 are ROMs that were downloaded from samfirmware.com... I guess that is what you mean when you advice to flash any stock ROM. Am I right?
Guessing you have a I9000m. If yes, Flash JPC with 512 PIT and repartition ticked. You will still be in a boot loop. Take out battery and then load JL2 into PDA of ODIN and flash. You could try it even if you do not have an i9000m but at your own risk! Advice is free, phone isn't!
droilfade said:
Guessing you have a I9000m. If yes, Flash JPC with 512 PIT and repartition ticked. You will still be in a boot loop. Take out battery and then load JL2 into PDA of ODIN and flash. You could try it even if you do not have an i9000m but at your own risk! Advice is free, phone isn't!
Click to expand...
Click to collapse
No... I don't have a I9000m, I do have a I9000T
When I flashed the JPY it turned a I9000, but I applied the Modem UGJL2 which adds the 850mhz band (which is the only difference between the I9000T and I9000.
Someone suggested going to JM8 (Eclair 2.1), but I have read that in some cases it produces hardbrick... what do you think?
Oh, been there! I can give you some advice... First, i will recommend heimdall for flashing, it allows a little bit more of control with the files you want to flash. Then, i had this problem with the dbdata... i think it's becacause of the repartition thing, honestly i'm not sure but do not worry, if you can enter download mode it's recoverable.
So, let's try something. Download heimdall, install it, install your drivers and then download the rom in this post (it's and old build of Darky's Rom), the thing here is that you <<have>> to flash this with the command line client, so you can specify the order of the files to flash leaving at the very end the Sbl.bin and modem.bin (Both files can't be flashed neither with heimdall nor Odin in my Galaxy i9000T). Obviulsy the heimdall flash will fail with the Sbl.bin file, so you just pull out your battery and power up your phone. That should do it... it have failed a couple of time for me, so if it fails for you (It gives you a boot loop) tell me so i can share my other method. If this works you should be able to enter CWM and flash a custom ROM or be able to flash another stock rom but be careful, do not flash bootloaders, modems or do a repartition (That's why i prefer Heimdall over Odin).
I hope you could have your phone back.
froysm said:
Oh, been there! I can give you some advice... First, i will recommend heimdall for flashing, it allows a little bit more of control with the files you want to flash. Then, i had this problem with the dbdata... i think it's becacause of the repartition thing, honestly i'm not sure but do not worry, if you can enter download mode it's recoverable.
So, let's try something. Download heimdall, install it, install your drivers and then download the rom in this post (it's and old build of Darky's Rom), the thing here is that you <<have>> to flash this with the command line client, so you can specify the order of the files to flash leaving at the very end the Sbl.bin and modem.bin (Both files can't be flashed neither with heimdall nor Odin in my Galaxy i9000T). Obviulsy the heimdall flash will fail with the Sbl.bin file, so you just pull out your battery and power up your phone. That should do it... it have failed a couple of time for me, so if it fails for you (It gives you a boot loop) tell me so i can share my other method. If this works you should be able to enter CWM and flash a custom ROM or be able to flash another stock rom but be careful, do not flash bootloaders, modems or do a repartition (That's why i prefer Heimdall over Odin).
I hope you could have your phone back.
Click to expand...
Click to collapse
Thank you froysm... What I see in your post is that we are going to try to flash a Darky's ROM in order to have CWM so we can flash a custom rom?
If that is so... I already have CWM... It is version 2.5.1.0 with its menu in green.
What is custom rom? are they the roms from samfirmware? I tried JPU and JS5 and they hang at slb.bin... the only one that flashes successfully is JPY, and eventhough it "runs", somehow it is not working.
In regard heimdall... Do I have to have ubuntu in order to install it? Is there a heimdall for windows?
Well, if you have CWM try one of the roms of the world famous romkitchen Cook a rom, download it, enter recovery mode, go to mounts & storage (and connect your phone to the computer) and select mount USB storage, put the donwloaded zip file in your phone. Then unmount, go bak to the main CWM menu, select install zip from sdcard, the choose zip from sdcard, find your rom and flash it! However... as far as i can remember i could never mount my phone with CWM 2.x so may need to flash Darky's Rom just to be able to mount your phone, put the zip file there and then reflash with the new ROM viw CWM...
jdelagarza said:
In regard heimdall... Do I have to have ubuntu in order to install it? Is there a heimdall for windows?
Click to expand...
Click to collapse
Yes, heimdall is available for Windows here It's pretty straight forward, just put your phone in Download mode, select the files you want to flash and hit start.
froysm said:
Yes, heimdall is available for Windows here It's pretty straight forward, just put your phone in Download mode, select the files you want to flash and hit start.
Click to expand...
Click to collapse
Thank you... believe it or not you poured some light into my darkness.
I have 3 issues and I hope you can clarify...
How would you order flash methods, in order of importance? Odin, CMW, heimdall? Which one is better, which one is worse?
I'm able to flash speedmod-kernel-k13d-500hz... that is what brings me the CMW v2.5.1.0.... should I try to install a newer version of CMW? or should I stick with heimdall option?
Flashing ROMs such as Darky's rom can be potentially harmfull? I mean, can my phone end with a hardbrick?
jdelagarza said:
Thank you... believe it or not you poured some light into my darkness.
I have 3 issues and I hope you can clarify...
How would you order flash methods, in order of importance? Odin, CMW, heimdall? Which one is better, which one is worse?
I'm able to flash speedmod-kernel-k13d-500hz... that is what brings me the CMW v2.5.1.0.... should I try to install a newer version of CMW? or should I stick with heimdall option?
Flashing ROMs such as Darky's rom can be potentially harmfull? I mean, can my phone end with a hardbrick?
Click to expand...
Click to collapse
Don't worry, that is exactly why we are here to learn from other people experience and share what we have learned.
About your issues,
I only have access to my Linux machine and heimdall says this when i ask for help (with the command
Code:
heimdall help
Usage: heimdall <action> <arguments> [--verbose] [--delay <ms>]
action: flash
arguments:
--repartition --pit <filename> --factoryfs <filename>
--cache <filename> --dbdata <filename> --primary-boot <filename>
--secondary-boot <filename> --param <filename> --kernel <filename>
--modem <filename>
So, what you have to do is navigate to the location of your files and write something like this
Code:
heimdall flash --repartition --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --dbdata dbdata.rfs --cache cache.rfs --param param.lfs --kernel zImage --primary-boot boot.bin --secondary-boot Sbl.bin --modem modem.bin
See how i reordered the files to flash leaving at the very end Sbl.bin and modem.bin?
As i told you before this will fail because of the last files, but it will allow to flash everything else. Remove your battery, put it again and try to boot your phone.
I forgot to tell you something really important!! Since the flash in going to fail it will give you the <<scary>> "Connect phone to PC" screen, but don't worry, heimdall can take care of that. Again, asking heimdall for help in the command line says something like this:
action: close-pc-screen
description: Attempts to get rid off the "connect phone to PC" screen.
And that is exactly the next step to take, write down in your command line (with the pone connected to the pc and in download mode)
Code:
heimdall close-pc-screen
And that's it, wait for the phone to boot.
This method is the one i advise when you just can enter Download Mode or when you really need to repartition.
Better? Worse? Nah, they are just really different approaches, Odin is the Samsung standard, Heimdall came to the game because it's OS X and Linux compatibility and CWM allows you to control your phone, custom kernel settings, flash updates packages with modems, boot animations , even whole roms without the need of a cable to connect your phone to a PC and other really cool stuff. Generally, since i've been in custom roms (like darky's, romkitchen, ultimate, etc) since i got this phone, i only use CWM, and when i have a big problem or i need a stock rom i use Heimdall (because i'm on Linux).
The CWM version is just fine, not all the roms are compatible with CWM 3 at the moment, so just make sure you can mount your phone in your pc with CWM. Try first the CWM option, if you can't mount it or it just don't works try the heimdall option.
The last question, I'm not saying it's 100% safe because it is not, but not only custom roms, this also can happen flashing a rom with Odin or Heimdall. Honestly i haven't heard of someone who bricked a phone in the whole thread of the romkitchen or darky's rom. I mean, it could happen, even with a perfectly stable stock rom. but it's not so common, at most, the worst thing you will encounter in your custom rom experience is a lot of Force Closes in applications (if you mix data and apps from incompatible versions) maybe a couple of boot loops, but nothing to be really scared about, just make sure you can enter Download Mode and everything will be fine.
Phew! The longest post if ever written in any forum. I hope i made everything clear, if you happen to have any other question i'll be happy to answer it (But it will have to wait for tomorrow... you know, it's midnight).
Thanks...
I'm downloading darky_heimdall.zip. As soon as it is downloaded, I will try it.
Just for your information, with CMW I tried to mount the USB and it worked!
So, now I am at a dilemma... Should I flash darky with CMW or heimdall?
Oh, if you wanted to know how I managed to install a WORKING STOCK ROM with froyo... here is the tutorial that I followed:
http://neosystm.com/2010/12/actuali...000t-a-froyo-2-2-1-xxjpy-de-forma-no-oficial/
It worked as a charm... I had Froyo 2.2.1 with JPY ROM.
The problem began when I tried to update it to JS5 ROM.
Cheers!
I just finished downloading darky's rom...
I noticed that it has 3 .bin files: boot.bin, modem.ini and slb.bin
I was curious about the content of my previous working ROM (JPY) and the not working ROMs (JPU and JS5).
I found that JPY has only the modem.bin file.
and JPU & JS5 have boot.bin and slb.bin (but no modem.bin).
Question: Since you advised to install darky's rom and but the sbl.bin file at the end, so my phone can get flashed with everything but slb.bin, can I do the same with the JS5 ROM?
I look forward to your response...
OK... I tried to flash darky's rom with CMW... it said:
"Installing: SDCARD: darky_heimdall.zip
Finding update package...
Opening update package...
Installing update..."
And it hung... I guess this was expected due the slb.bin...
I'm gonna try the heimdall method.
So, what do you think? Should I try it with JS5 or with darky's rom?
Cheers
Ok... I flashed with heimdall.
This is the result:
Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Uploading PIT file
PIT file upload successful
Uploading factory filesytem
100%
Factory filesytem upload successful
Uploading cache
100%
Cache upload successful
Uploading data database
100%
Data database upload successful
Uploading primary bootloader
100%
Primary bootloader upload successful
Uploading secondary bootloader
100%
Failed to confirm end of file transfer sequence!
Secondary bootloader upload failed!
The last two sentences appeared when I unplugged the phone after a 10-minute wait.
I removed the battery, and put it back again. Turned my phone on, and I've got the picture of the cell phone - computer hazard. I'm able to enter download.
What's next?
Froysm, do you know what's the original ROM that telcel uses to ship our Galaxy' S?
jdelagarza said:
Froysm, do you know what's the original ROM that telcel uses to ship our Galaxy' S?
Click to expand...
Click to collapse
I've found a thread that says that they fixed it going back to JM8 ROM, and then moving back to Froyo 2.2.
Does anyone know any potential damage of such flashing?
I read this post http://forum.xda-developers.com/showthread.php?t=780867
And it seems that downgrading can lead to corruption and hard bricking.
Does anyone know?
Hey, sorry i didn't answer sooner, let's see...
jdelagarza said:
I just finished downloading darky's rom...
I noticed that it has 3 .bin files: boot.bin, modem.ini and slb.bin
I was curious about the content of my previous working ROM (JPY) and the not working ROMs (JPU and JS5).
I found that JPY has only the modem.bin file.
and JPU & JS5 have boot.bin and slb.bin (but no modem.bin).
Question: Since you advised to install darky's rom and but the sbl.bin file at the end, so my phone can get flashed with everything but slb.bin, can I do the same with the JS5 ROM?
I look forward to your response...
Click to expand...
Click to collapse
Yes, you can.
jdelagarza said:
OK... I tried to flash darky's rom with CMW... it said:
"Installing: SDCARD: darky_heimdall.zip
Finding update package...
Opening update package...
Installing update..."
And it hung... I guess this was expected due the slb.bin...
I'm gonna try the heimdall method.
So, what do you think? Should I try it with JS5 or with darky's rom?
Cheers
Click to expand...
Click to collapse
That specific version of Darky's rom is intended only for heimdall, so it will obviously fail. You'll see, some files can just be flashed via CWM and some can just be flashed with Odin and Heimdall, be careful and read with which tool can be flashed.
jdelagarza said:
Ok... I flashed with heimdall.
This is the result:
Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Uploading PIT file
PIT file upload successful
Uploading factory filesytem
100%
Factory filesytem upload successful
Uploading cache
100%
Cache upload successful
Uploading data database
100%
Data database upload successful
Uploading primary bootloader
100%
Primary bootloader upload successful
Uploading secondary bootloader
100%
Failed to confirm end of file transfer sequence!
Secondary bootloader upload failed!
The last two sentences appeared when I unplugged the phone after a 10-minute wait.
I removed the battery, and put it back again. Turned my phone on, and I've got the picture of the cell phone - computer hazard. I'm able to enter download.
What's next?
Click to expand...
Click to collapse
As I told you on my last post, heimdall can take care of that. Just put your phone in Download Mode and write heimdall close-pc-screen. That should solve your problem.
jdelagarza said:
Froysm, do you know what's the original ROM that telcel uses to ship our Galaxy' S?
Click to expand...
Click to collapse
Nope, i've never found it (actually i've never needed it).
jdelagarza said:
I've found a thread that says that they fixed it going back to JM8 ROM, and then moving back to Froyo 2.2.
Does anyone know any potential damage of such flashing?
I read this post http://forum.xda-developers.com/showthread.php?t=780867
And it seems that downgrading can lead to corruption and hard bricking.
Does anyone know?
Click to expand...
Click to collapse
Try my methods first, I've tested them a lot and never had a real problem. If you want to try this, go ahead. As i told you before it's very rare to hear a phone really bricked, most of the times it's recoverable.
Oh, I forgot the heimdall close-pc-screen.
Ok... I tried it twice.
The first time my command prompt was busy trying to upload sbl.bin, so I opened another command prompt and I threw the command. The result: "Failed to access device. Error: -3"
The second time I waited until the flashing ended with error, and then I threw the command (within the same command prompt). The result: "Failed to retrieve config descriptor"
Hmmm... what was the other method that you mentioned in your first post?
In the other hand, can you read the following post, and could you go through all the comments after the post. Pay special attention to Jedi and GSCATIL...
http://foro.neosystm.com/f19/androi...00xxjvk-%96-beta-para-el-samsung-galaxy-s-69/
Jedi describes my exact problem (about the phone vibrating), and GSCASTIL is from Puebla, so he is with Telcel as well...
My problem didn't happen updating to gingerbread... It happened updating to JS5 (Froyo).
Hope this helps... what do you think?
jdelagarza said:
Oh, I forgot the heimdall close-pc-screen.
Ok... I tried it twice.
The first time my command prompt was busy trying to upload sbl.bin, so I opened another command prompt and I threw the command. The result: "Failed to access device. Error: -3"
The second time I waited until the flashing ended with error, and then I threw the command (within the same command prompt). The result: "Failed to retrieve config descriptor"
Hmmm... what was the other method that you mentioned in your first post?
In the other hand, can you read the following post, and could you go through all the comments after the post. Pay special attention to Jedi and GSCATIL...
http://foro.neosystm.com/f19/androi...00xxjvk-%96-beta-para-el-samsung-galaxy-s-69/
Jedi describes my exact problem (about the phone vibrating), and GSCASTIL is from Puebla, so he is with Telcel as well...
My problem didn't happen updating to gingerbread... It happened updating to JS5 (Froyo).
Hope this helps... what do you think?
Click to expand...
Click to collapse
Always, after any task completed successfully or unsuccessfully either with Heimdall or Odin, unplug your phone, reboot it, put it again in download mode and connect it. So do that again, flash, wait for the fail, unplug, reboot, download mode again, connect again and try to remove the error screen with heimdall.
I will read that post and see what i can find (I can't read it right now, sorry).
I wanna know if you can help me, ...
I was on sprint gtab stock rom DJ30 which updated to EA24 and EB28. Data service worked very well. Then I flashed voodoo CWM in order to install Honeycomb rom. Then install the rom via CWM. The installation was indeed finished, but it stucked in samsung logo boot. I turned off device and boot in cwm mode. Sure, it was HC rom's CWM. But it couldnt mount system, Seems the convertion to ext4 didnt work. Worse thing it couldnt mount sdcard either. So I couldnt reinstall the rom. I also couldnt reboot, so i had to long press the power button.
Stop trying installing HC rom on my device, i decided to revert back to stock rom (DJ30>EA24). But it was weird, i cant revert to stock rom with modem.bin inside the package. It always stuck in modem.bin when flashed with odin. But, when i use the package with no modem, it can flashed succesfully. I had flashed that stock rom (with modem.bin) million times without fail, but now always fail.
Yeah, my gtab is running but without modem.bin so no signal and i cant use data services. Like wifi only tab.
Many ways i've tried:
- I've tried flashed DJ30 with no modem first. Okay, it is successful. But when flash with EA24 (with modem) it stuck on modem.bin.
- I've tried flashed DJ30 with modem.bin. And it also stucked on modem.bin. Trying flashed EA24 without modem.bin, it is succesful.
- Try using heimdall. Progress 100% but it wont reboot. But when i retry n uncheck modem. Flashing work flawlesly.
- Try using odin modem only flash. Progress bar is full but it wont reboot.
- Try flashing via CWM, but still no luck.
Weird, huh. Seems my gtab cannot use modem.bin anymore.
Any clue? Thanks before ...
I'd appreciate if you can help me flashing modem.bin to my device. Or it end up with wifi only tab.
EDIT: even OTA update, stuck on "verifying modem ... updating modem ..."
I would like to bump this as I am having the same issues also. I am flashing my Sprint Galaxy Tab to EA24, and it is held up at modem.bin.
I posted a question on this, and am hoping that someone helps us.
Thanks in advance,
Claud
try re-partition and flash pit by using odin,i suffered the same issue with my vzw tab
depending on which file you're using to restore. You need to use the .tar.md5 file from the EA24 flasher and rename it to just .tar, then flash with Odin. I've flashed this several times and it gets past modem.bin just fine. If you are using the 2 files 1 with modem (Epic 4g modem) and 1 without modem you're not using the right files. I ran into the same issue with the with/without modem files. Here's a link to the EA24 flasher and the .tar.md5 file you need to go back to stock.
http://www.multiupload.com/LXQKGX5RHL
Bumping this to avoid making a new thread.
I've done many reverts back to stock from different ROMs, but this past time coming from BTL or HC (Sprint Tab btw) I'm also getting hung up on modem.bin. Never had a problem here before, so not sure what's going on.
I didn't use a pit and only had reboot checked and it worked fine.
I've never included pit. I've just always put SPH-P100.EA24.SECURE.REV07-FULL_CL871413.tar in the PDA slot and let it go through. And tried checking re-partition, but it does not go through that way.
Maniken50 said:
I've never included pit. I've just always put SPH-P100.EA24.SECURE.REV07-FULL_CL871413.tar in the PDA slot and let it go through. And tried checking re-partition, but it does not go through that way.
Click to expand...
Click to collapse
Pretty sure if you try to re-partition, you have to have the correct pit file for it to know the right places to recreate the partition table. If you're just flashing back to stock, there's no need for the pit file.
pvtjoker42 said:
Pretty sure if you try to re-partition, you have to have the correct pit file for it to know the right places to recreate the partition table. If you're just flashing back to stock, there's no need for the pit file.
Click to expand...
Click to collapse
That's what I thought and never had a need for it. Guess I do now. Think it would even work?
Maniken50 said:
That's what I thought and never had a need for it. Guess I do now. Think it would even work?
Click to expand...
Click to collapse
I've never had to repartition a device, but i've read about it working for people to bring them back from boot looping etc. If somehow the partition table gets corrupted etc. If you're already soft bricked, there's no harm in trying.
Having the same issue, trying to go from Rooted GB to BTL then back to GB or EA24
Hi,
I am having the same issues, does anyone have the .PIT file available by any chance, all of the packcages that I have downloaded for the sprint tab seem to not have any pit included...
ezitec said:
Hi,
I am having the same issues, does anyone have the .PIT file available by any chance, all of the packcages that I have downloaded for the sprint tab seem to not have any pit included...
Click to expand...
Click to collapse
http://www.mediafire.com/?jb40cs460rf8aq7
Try that one.
I have the same problem with a Verizon Galaxy Tab. The archive modem.bin lock in 100% via Heimdall. Someone conseguiui solve this problem?
mbanton said:
I have the same problem with a Verizon Galaxy Tab. The archive modem.bin lock in 100% via Heimdall. Someone conseguiui solve this problem?
Click to expand...
Click to collapse
You need to look at one of the stock VZW threads and find the files you need there, as the sprint modem will make things worse for you. Not sure if the pit files are the same or not between the sprint and VZW tabs..
pvtjoker42 said:
You need to look at one of the stock VZW threads and find the files you need there, as the sprint modem will make things worse for you. Not sure if the pit files are the same or not between the sprint and VZW tabs..
Click to expand...
Click to collapse
I have the correct files for the tab for Verizon. I have the original files Following: Sbl.bin boot.bin cache.rfs dbdata.rfs efs.rfs factoryfs.rfs ldb.db modem.bin param.lfs param.rfs pit.pit zImage
But my problem is how to record using that pit. What other files should I use a recording that will restore the partition table?
I fear that a problem occurs with even higher tab.
I am having this issue as well, and I'm also coming from HC and on Sprint. I have no trouble flashing any kernel/rom of my choosing EXCEPT for the modem.
At this point, I'm just trying to reflash it back to stock. I've got the Sprint EA24 files, including the pit (tried with and without) but it refuses to flash the modem. If I omit the modem, it flashes perfectly fine and I'm left with a bone stock tab with no modem.
Is there anyone here who went to HC and then managed to go back? As stated by others, I've gone back to stock before without issue. The HC build seems to be what caused this problem
I ran spacemoose's HC port for a day or 2 and then went back to stock until the official GB came out. I've had no issues flashing the whole EA24, or any other updates.. with and without the modem..
Hmmmm. Maybe different hardware revisions? You have any suggestions? I'm completely out of ideas and it's of little use to me without 3G.
I just did a flash back to complete stock (including modem) 2 days ago, and it didn't hesitate once while flashing everything with Heimdall. Only thing I can say is keep trying.
At this point, I've attempted to flash it no less than a dozen times and still can't get the modem to flash. I'm completely baffled as to why it won't accept it.
Hi
I was stupid and bricked my phone after trying to flash N7000XXKJ1 firmware. I guess PIT file was wrong..
Kias don't see it now and ODIN is failing to flash any KJ4 firmware, and also there is no pit in them.. any ideas or just throw it away?
Thanks!
dont throw it away you just need the correct pit file.
If you would like you can send it to me instead of throwing it away.
Hmmm I've never used PIT files when flasing on Galaxy S2 and Note. Why do you use them?
Maybe you need a jig to solve the problem.
Some update: I used borrowed jig and it is worked, sort of..
I am getting into boot loader I guess which says - can't download. battery too low.
However phone doesn't charge in current state. Is it common problem? Any ideas how to charge it before I am start looking for another Note with charged battery =)
kromosto said:
dont throw it away you just need the correct pit file.
Click to expand...
Click to collapse
all stock firmwares comes without pit file, except one I used.. is it maybe possible to extract pit info from working phone?
just to update, managed to fix by flashing N7000XXKJ4_N7000XEOKJ1_N7000XXKJ4_HOME.tar.md5 w/o pit. Had to buy universal external battery charger for $20 since stupid phone wont charge batter in recovery mode.
So i guess my advice is not to flash KJ1 with PIT =)
vvs said:
just to update, managed to fix by flashing N7000XXKJ4_N7000XEOKJ1_N7000XXKJ4_HOME.tar.md5 w/o pit. Had to buy universal external battery charger for $20 since stupid phone wont charge batter in recovery mode.
So i guess my advice is not to flash KJ1 with PIT =)
Click to expand...
Click to collapse
Glad you got it working, would have been very sad if it would have been totally bricked.
Happy days with your new Galaxy Note!
Sent from my GT-I9000 using xda premium
Ok, I don't have a note, but this thread came up with search. I have the problem that I flashed a pit for a galaxy 1900 on my galaxy player. It gives me red errors about "E:failed mount /dbdata (invalid argument)" E:failed mount /cache (invalid argument). I have tried flashing .md5 stock rom via odin, but it doesn't help. I basically need to know how to extract a pit file so that I can tell someone else how to that has my device.
when i flash firmware on galaxy A8(sm-a810f)
odin display set partition