Related
Hey guys,
First of all I checked every brick thread I could find and I am pretty sure none of the solutions applies to my problem.
I've flashed hundreds of times on numerous phones so I take most precautions to make sure I don't brick my phone, still, that's what happened now for the first time.
Situation:
- Download mode and recovery mode checked... both working
- Had Darky's DarkSteel 3.0 running with LagFix (no problems)
- Disabled LagFix by adding the folder
- Reboot ... disabled lagfix ... still running strong
- Flashed Darky's LegendarySteel 4.0 ... running
- Reboot ... hey no Voodoo ... oops lagfix folder was still there of course
- removed folder
- reboot ... still no lagfix ... OK so I accidentally chose the wrong Darky's ... The one with SpeedFix kernel not the one with Voodoo
- remember: lagfix folder still there, but I thought it would not be enabled as Darky's SpeedFix version had no Voodoo, also, Quadrant showed 900 like you would expect without lagfix
- Checked recovery/download just for precaution ... both working still
- Flashed the rom I wanted: Darky's LegendarySteel 4.0 with VOODOO
- So basically, I flashed WITHOUT "disable lagfix" folder, somehow thinking this would not be a problem considering LagFix wasn't running on the previous rom, and was disabled before flashing the previous rom.
- Clockwork Recovery clear cache / wipe partition ... choose zip ... run update ... OK REBOOT
- Stuck at Galaxy S logo
- No recovery
- Download mode works
- Tried Odin to flash stock rom using PIT 512 with and without repartition ... both just wait for a long time on some message "checking file system" and I don't know how long that should take but after 20mins I gave up.
- Tried rebooting and waiting forever as advised on the Voodoo site ("if you had a lagfix enabled previously, it will take forever, just be patient") well I waited forever (hours?) and still "Galaxy S" bootup screen
- Kies recognizes nothing
- Same for ADB
- Only download mode works ... Odin does recognize the device so all could not be lost right?
My questions:
- What should I flash (including firmware, PIT, odin version, repartition, wait time etc) to get up and running again?
Any help would be greatly appreciated!!!
nin2thevoid said:
Hey guys,
First of all I checked every brick thread I could find and I am pretty sure none of the solutions applies to my problem.
I've flashed hundreds of times on numerous phones so I take most precautions to make sure I don't brick my phone, still, that's what happened now for the first time.
Situation:
- Download mode and recovery mode checked... both working
- Had Darky's DarkSteel 3.0 running with LagFix (no problems)
- Disabled LagFix by adding the folder
- Reboot ... disabled lagfix ... still running strong
- Flashed Darky's LegendarySteel 4.0 ... running
- Reboot ... hey no Voodoo ... oops lagfix folder was still there of course
- removed folder
- reboot ... still no lagfix ... OK so I accidentally chose the wrong Darky's ... The one with SpeedFix kernel not the one with Voodoo
- remember: lagfix folder still there, but I thought it would not be enabled as Darky's SpeedFix version had no Voodoo, also, Quadrant showed 900 like you would expect without lagfix
- Checked recovery/download just for precaution ... both working still
- Flashed the rom I wanted: Darky's LegendarySteel 4.0 with VOODOO
- So basically, I flashed WITHOUT "disable lagfix" folder, somehow thinking this would not be a problem considering LagFix wasn't running on the previous rom, and was disabled before flashing the previous rom.
- Clockwork Recovery clear cache / wipe partition ... choose zip ... run update ... OK REBOOT
- Stuck at Galaxy S logo
- No recovery
- Download mode works
- Tried Odin to flash stock rom using PIT 512 with and without repartition ... both just wait for a long time on some message "checking file system" and I don't know how long that should take but after 20mins I gave up.
- Tried rebooting and waiting forever as advised on the Voodoo site ("if you had a lagfix enabled previously, it will take forever, just be patient") well I waited forever (hours?) and still "Galaxy S" bootup screen
- Kies recognizes nothing
- Same for ADB
- Only download mode works ... Odin does recognize the device so all could not be lost right?
My questions:
- What should I flash (including firmware, PIT, odin version, repartition, wait time etc) to get up and running again?
Any help would be greatly appreciated!!!
Click to expand...
Click to collapse
Flash some ecleir ROM with 512 re-partition. Hope this helps.
ragin said:
Flash some ecleir ROM with 512 re-partition. Hope this helps.
Click to expand...
Click to collapse
Try the Odin 1.7 from my thread posted here.
Try flashing back to the kernal that you had on the rom first?
Don't really know if it would help.. just taking a shot in the dark..
God I love this forum. Thanks for the tips all. I was using older ODIN and now using 1.7 (couldn't find it in the specified thread since the link was missing ^^ but used the forum search instead).
It's flashing ... At least that!! I will report back how it goes!
Edit:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> dbdata.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> param.lfs
<ID:0/003> modem.bin
<ID:0/003> cache.rfs
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Live and kicking again! Woot... Thanks all!
Well, atleast we know that odin 1.7 is more stable and more "unbrick" friendly =)
nin2thevoid said:
God I love this forum. Thanks for the tips all. I was using older ODIN and now using 1.7 (couldn't find it in the specified thread since the link was missing ^^ but used the forum search instead).
It's flashing ... At least that!! I will report back how it goes!
Edit:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> dbdata.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> param.lfs
<ID:0/003> modem.bin
<ID:0/003> cache.rfs
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Live and kicking again! Woot... Thanks all!
Click to expand...
Click to collapse
If it has helped you, please post a reply in my thread. can help others like you.
from my experience odin works the best if you connect your phone and hit the flash button immediately. connecting the phone in download mode and waiting with it always caused the flash process to "stuck" just like you describe.
anyway happy 1.7 helped you.
I had the exact same problem last night.
to solve the issue... I basically reflashed to ECLAIR JM8.
Then installed the ROM i wanted from clockwork recovery, and everything went back to normal!
Hope things work out well for you! cheers!!
I guess Re-Partition solved the problem. This should also work with Odin 1.0 / 1.3
No it was 1.7 that solved it since I did the exact same steps as with 1.3. Upgrading Odin was the fix for sure. I'm surprised not many people use 1.7... all the tutorials and guides point to 1.0 and 1.3.
Thanks for all the help guys!
hi gays,
actuly i have the same problem " screen of death "
but it happened whit my when i tried to flash -speedmod kernel - and - ce-root- in PDA
and it's stopped in middel of the action -- it happened in odin3 1.7 > it's naver happened in odin3 1.3 and odin3 1.3.2
i think there something wrong with 1.7
--sorry for bad English - i hope you understand what i'm tring to say
thanks for your time !!
I have a similar problem, which is not solved yet. I would be glad if someone would help.
Explanation of my probs:
I think I've bricked my SGS. It's a European version, not branded with T-mobile or any operator.
Friday I flashed the JPU (Android 2.2.1) and it worked fine. I've updated it several times via Odin, and never really had problems.
Then I installed the Voodoo recovery image and a custom ROM (Darkys 5.2 ROM). Still worked fine, a quadrant score of 1650. But then... I went to the recovery and chose to partition the internal SD card (EXT3/4). The phone said it succeeded doing this, but then it rebooted and I only got the Samsung logo (in white, no colors). Waited for 10 minutes, nothing happened.
Now I can't get it into recovery mode, however, the 3-button combo is still working, so I can get it into download mode as usual. But it does'nt work. It starts, I get the green slider on the phone, but after a very short time the update stops, it happends while Odin writes sbl.bin
I've tried several ROM's, but it does not work. I don't know what to do now - why can't I flash the phone even though it's in download mode?
Hope that someone can help me.
--- update ---
Hmm, maybe I'm on the right track now - I hope so.
Now I can turn on the phone, but it does go into the stock recovery, even though I just turn it on. It's the stock recovery (Android system recovery <2e> Samsung recovery Utils - for BML -
I downloaded Odin 1.7 from this link:
Download Odin-1.7with.pit.512.803.zip from General-Search.com
I did this on my work computer instead of my laptop. Never used Odin on this computer before. Then I just wanted to test Odin, so I chose some random PDA file I had on the computer. I chose the JPK Root + Busybox 1.17.1 + 2e\i9000_Kernel.tar that I used for rooting the JPK firmware when I was running that.
Then I have flashed the other file from that package (I9000XXJPK_Kernel.tar) - but when I turn on the phone, it stops but shows the white Galaxy S logo.
...more to come.
UPDATE!
UPDATE! Flashed JM7 firmware (that's the newest I already had downloaded on my work computer) and the beast is ALIVE AGAIN! Hallelujah!
I solved it with old ODIN flash 1.3 firmware JPA_JP4_U_JPP.tar (no pit file) USB pluged and unpluged a cuple of times. no repartition and no bootblock . After first flash i had to wipe and factery restore in 2e recovery. and flash again. After that the phone was fine. The KIES version i have installed is 1.5.3.10103.102. I think it is the driver version that KIES installs that is the problem, You could try installing older KIES vith older drivers. After first flash the new firmware could not install aps after first boot, thats why i wiped and flashed again.
Sory for bad English
Help pls.. I can run but it failed in the end after waiting it to run. I had tried reopening the oldin and replug in batt all no use...
Thank you so much for the tips here guys, been trying to recover my nephews softbricked i9000 for 5 days now - finally sorted, woohoo!!!!
I used Odin 1.7, Re-Partitioned with the 512 pit file and flashed a stock rom.
This was my last attempt too so Christmas has come early!
Hi
I was trying to flash another ROM on my SGS, while having some bugs on CM7.
I formatted system, cahce and data, and did wipe data/factory reset + wipe cache.
I kept getting an error on flashing the new ROM, and accidently hit the "reboot system" while navigating around in CWM3.0.0.5. Now I can't get back to CWM with 3-button combo and got no ROM on my phone?
what to do? Wierd enough I can get into download mode
thanks in advance
PS: I normally use 3 button combo to get into CWM, and did this prior this episode
just flash via odin, with 3 files and re-partition.
that should work.
derrzredeem said:
just flash via odin, with 3 files and re-partition.
that should work.
Click to expand...
Click to collapse
I'm not so farmiliar with Odin yet... tried it a couple of times, sticking strictly to a guide, that I cant find right now :S
Could you give me a quick tutorial in what to combinate .e.g.?
PIT? PDA? PHONE or CSC? And what is what?
I know I used to flash a radio with the PDA function...
thanks
you should flash a low level package means a 3 files PDA, MODEM and CSC.
i.e XXJPU which contains XXJPU_modem, OXAJPU_CSC, and XXJPU_Rev3_PDA. Now you should put the files according to the names (like PDA in PDA, Modem in Modem and so on). I usually use 512pit for re-partition.
You should not put modem in pda when flashing using odin, like i said before "put the files according to the names"
ps. Do not tick any other option except repartition, (F. Reset Time, and Auto-reboot) when going back to samsung ROM from CM7
Good Luck
derrzredeem said:
you should flash a low level package means a 3 files PDA, MODEM and CSC.
i.e XXJPU which contains XXJPU_modem, OXAJPU_CSC, and XXJPU_Rev3_PDA. Now you should put the files according to the names (like PDA in PDA, Modem in Modem and so on). I usually use 512pit for re-partition.
You should not put modem in pda when flashing using odin, like i said before "put the files according to the names"
ps. Do not tick any other option except repartition, (F. Reset Time, and Auto-reboot) when going back to samsung ROM from CM7
Good Luck
Click to expand...
Click to collapse
Thanks a lot. You just managed to answer my next question at the same time as I was about to put it out (regarding check marks F. Reset Time, and Auto-reboot)... looks like it is going through now... The blue line is increasing anyway under the litthe android builder
thank you so very much
EDIT: God dang it Phone bootet up once again in original rooted firmware anf 3e recovery is back
Hmm... seems I was a bit to fast on the keyboard anyway
Followed "How to: flash firmware and kernels" from post #2 in this thread
http://forum.xda-developers.com/showthread.php?t=723596
I found a 512 pit from the link, where I also downloaded Odin. I chose the I9000XWJS3.7z from original firmware package (from the link), which included a .tar file, that I chose as PDA.
The phone boots up now, but when as it is about to show android UI, it starts to vibrate and the screen turns black, and menu button + back button light up continously.
I can get into 3e recovery know though, but is there a way to flash clockworkmod or another custom recovery via odin og 3e recovery? or could I try another combination of pit and PDA file ind Odin?
thanks again
Odin log:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> modem.bin
<ID:0/004> param.lfs
<ID:0/004> zImage
<ID:0/004> cache.rfs
<ID:0/004> factoryfs.rfs
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
You're in a bootloop. Try wipe cache partition and do a factory reset from recovery and then reboot.
If that doesn't work try a different firmware. A LOW LEVEL PACKAGE one, JPU for example.
Afaik, JS3 only had one file (and the new JS3 is using 803pit file, tho it comes with 3 files; for me 512 always gave the best result).
Edit : You need to use a correct pit file when flashing a firmware.
~drz
derrzredeem said:
You're in a bootloop. Try wipe cache partition and do a factory reset from recovery and then reboot.
If that doesn't work try a different firmware. A LOW LEVEL PACKAGE one, JPU for example.
Afaik, JS3 only had one file (and the new JS3 is using 803pit file, tho it comes with 3 files; for me 512 always gave the best result).
~drz
Click to expand...
Click to collapse
Just to make sure I got the last part right. 803pit is for JS3? but I can use 512pit instead?
where do I get 803pit? do you have a link?
Im downloading JPY and will test it, if 803pit og wipe doesn't work.
thanks for the response
larsn84 said:
Just to make sure I got the last part right. 803pit is for JS3? but I can use 512pit instead?
where do I get 803pit? do you have a link?
Im downloading JPY and will test it, if 803pit og wipe doesn't work.
thanks for the response
Click to expand...
Click to collapse
God, you need to learn to listen/read. Use JPU, JPY is a single file.
Ps. Good luck though
~drz
Okay, I thought the name JPU/JPY determined which area it is fore?
Im downloading from here
https://www.wuala.com/Samsung Galaxy S/Firewares , Updates and Odin/?key=AfzUZSU4SpKU
but I cant seem to find JPU...
thanks for your help. Im a bit noobish regarding samsung... Its buy far not the same as HTC hehe
EDIT: Can't I just flash an original firmware with Odin, and it such case? Where do I find it. tried JPY, JS3 from above link, and get bootloops no matter what. Those files are downloaded from the sticky guide in general section, and I followed the guide. If I need to use JPU, where do I download it? all 3 files?
Right now, the phone just vibrates in intervals, but contiounsly, with back button and menu button light on
Yes, every firmware is for different region. But you need to get your phone to work first, right?
After that you can flash any firmware you want
You can download JPU from http://samfirmware.com or find a thread by BogdanSNB in general section.
Btw, Gingerbread is out
~drz
SOLVED
Finally got it to work with XJWM9 as PDA, XEEJM1 as CSC, XXJM4 as PHONE and 512pit file.
Hey guys i have followed the guides , i was putting on a stock rom for my phone to be sent back as a replacement. it failed half way through the flash when i upgraded the phone to 2.2
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.rfs
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can get back into recovery mode. I tried flashing it with the PIT PDA and CSC file. It fails constantly, i clicked re partition in one flash too it didnt work either. SO i am stuck. Any other suggestions?
Using odin 1.3 - It worked the multiple other times i flash it to different roms.
Maybe you're using Windows x64? try using another version of Odin, possibly 1.7 & make sure when you open it to go to the correct pit file & not the last one opened, also if the phone is going back do a wipe/factory rest too in recovery mode & then try reflashing with Odin, hope that helps.
Hi i used a windows XP machine with the same results. I did try 1.3 and 1.7.
is there another PIT file i can try? I downloaded a couple and neither worked.
I have no recovery anymore only download mode, the phone does not boot at all no phone -> computer icon.
Is the 512 PIT file the right one for the galaxy thought it was.
Have you tried redownloading the firmware? Or another source for the same firmware? Maybe its corrupt somehow. I know it is supposed to check the md5 but worth a shot. Or try an earlier version of your firmware, if it is for return they shouldn't care.
G
I have tried 3 - 4 different roms with all the same result, the phone was going back under a different issue (network related). It always fails at the same point from each rom.
Steps i have done.
1. pit file only (repartition)
2. pit pda and csc (512 pit , vodaAU stock rom, voda au csc)
3. standard stock rom (which worked) but doesnt now.
4. Darkys resurrection rom (failed same spot)
5. odin 1.3 and odin 1.7
6. windows 7 and windows XP
I am annoyed about this, the other times worked fine! Just went i went to send it back for replacement . boom failed.
I tried a more recent ginger rom, failed again act factory.rfs. It's almost like the internal SDcard is broken. This time it flashed modem.bin
Did you remember to turn off the lagfix before the first flash? If the file system is ext4 and you flash RFS then I think that you can have issues.
There is a way to fix it as I was on another thread today where that was the issue but I don't know if the error showed up in Odin for them.
Just another thought...
G
BTW I think in most cases odin will still flash OK even if SD card is cooked. We i9000m owners know way too much about that...
After google search you also might try 1) another odin or heimdall - personally I'd try heimdall at this point if I were you or EZ odin maybe? 2) You likely know not to have kies agent in the tray but hey worth mentioning 3)redownload drivers (which I'll guess that you've done too)
Hi mate ,
Yes i did disable lag fix before flash i kept the orig rfs file system did not convert to EXT4. I might try Heimdall.
After google search you also might try 1) another odin or heimdall - personally I'd try heimdall at this point if I were you or EZ odin maybe?
2) You likely know not to have kies agent in the tray but hey worth mentioning
All taskmanager escaped all the kies stuff, reinstalled kies as well.
3)redownload drivers (which I'll guess that you've done too)
Did this on two machines.
EZ odin fixed it. It booted i just put my providers CSC on it, im pretty sure they wont check the base band and rev number when they get it back.
Glad it worked!
G
Sent from my GT-I9000M using XDA Premium App
[Q][i9000][MOD][GB] - How do I root stock DXJV9
How can I root my i9000 on 2.3.3?
Model number
GT-I9000
Firmware version
2.3.3
Baseband version
I9000DXJV9
PDA: I9000DXJV9
PHONE: I9000DXJV9
CSC: I9000OLBJV9
Kernel version
2.6.35.7-I9000DXJV9-CL216763
[email protected] #2
Build numer
GINGERBREAD.DXJV9
Bought in Thailand last year and updated via Kies only with the official updates.
I have been searching and reading for over a day (admin check my IP in the webserver logs if you like) to find out how I can root my Samsung Galaxy S i9000 International,
ideally keeeping my settings, launcher, homescreens, SMS, apps ... without having to restore backups ..
I am happy with keeping close to stock.
I backed up apps, sms, callhistory, kies backups just to be safe
Both 3-button combos are working
I came across SuperOneClick but it didn't work, it's not supposed to work on 2.3.3 Gingerbread
Then in severeal threads where ppl specifically asked about DXJV9, the FuguRoot Mod was suggested.
A question remains:
- there is no stock kernel listed for DXJV9 but the instructions say you have to flash with it afterwards, where would I find it
There are some kernel files listed in this guide but none of them for DXJV9.
Also I would be unsure if I need to extract the zImage-root.tar before specifying it in odin, inside is a file called zImage without file extention. Another guide said the .tar needs to be extracted first.
Are there any other ways to achieve this, all I want is root. Any tips appreciated!
I would use the latest Speedmod kernal to get root. I base this on my experience flashing the Chebon ROM which is a good rom for Asia. Basically, second step in Chebon is to flash speedmod latest version. This will give you root.
update: found the original kernel, bricked phone
I finally found a post with the original kernels by Ramad.
In another video guide I established that I don't have to extract the zImage-root.tar file before adding it to the PDA section of odin.
I followed the exact steps to flash the FuguMod Kernel and it worked fine:
odin3 v1.82
PDA: zImage-root.tar (the FuguRoot MOD)
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> zImage
<ID:0/012> RQT_CLOSE !!
<ID:0/012> RES OK !!
<ID:0/012> Removed!!
<ID:0/012> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Then everything fine, red fish, battery symbol appeas, I enter download mode again, ok
Then extracted the original kernel for my version
Kernel_DXJV9.tar (5600 KB)
closed odin, disconnected phone, opened odin again, connected phone, comms established, so I select the Kernel_DXJV9.tar , but then:
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> zImage
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone now can't be turned on. Brick at this stage.
Disappointed because of all the long hours researching for a safe method just to get root ...
Again I would appreciate any help on how to proceed.
I already tried to re-download and re-extract the original kernel, same result, odin fails.
update: worked!!
Update 2:
I kept trying two more times to flash the original kernel file from Ramad, Kernel_DXJV9.tar, with odin,
because I read somewhere that "odin is not the most reliable piece of software".
Eventually it worked, even though I did everything exactly the same way.
So my advice if anyone gets the fail message with odin, keep trying, even another 3, 4, 5 times ...
Redownload the file, reextract, re-open odin, re-connect the phone in download mode, re-flash, if it fails, try again ... odd as it is ...
So now I can see the SuperUser app
I can't see BusyBox, but I am checking on the market now.
update 3: Kies can't detect my phone anymore
update 3: Kies can't detect my phone anymore
Error
Reconnect the device in Samsung Kies (PC Studio)
mode. Current connection mode not supported by Kies
Click to expand...
Click to collapse
Just like some other people on the thread report, Kies no longer detects my phone, but the files
/system/bin/drexe
and
/system/bin/npsmobex
are there, they aren't missing if I look with Astro File Manager.
So I thought I need a file manager that can modify permissions, and I downloaded a couple of them, they mount /system as rw .. and then I can not not see those two files anymore, it's so strange.
If I open ASTRO I can see those two files but ASTRO can't change permissions.
I have yet to figure out how I can get into a command shell / terminal to modify the permissions with chmod on the command line.
I downloaded the BusyBox App from the market.
update 4: Kies connection problem not solved
update 4: Kies connection problem not solved
I used a root file manager to copy those 2 files from the FuguRoot thread to their location:
/system/bin/drexe
and
/system/bin/npsmobex
The permissions were fine.
I made sure to be on TwLauncher when connecting,
I also disabled USB debug mode
but Kies still keeps trying to connect to my phone, no luck ....
Since you have backups and the system is unstable I would just go back to stock.
The stock dxjv9 rom is found here:
[Firmwares]Stock I9000 and I9000M Firmwares collection [Latest: XWJVN, DDJV9, XWJVK] - http://forum.xda-developers.com/showthread.php?t=1102881
The instructions are pretty good and have used it to downgrade to JVQ 2.3.4 to DXJV9 2.3.3 to try out the Chebon Rom as mentioned (JVQ was a bit unstable for me but now JVR).
I've not tried the FuguRoot but I know Speedmod works.
Sorry URL got truncated but search the title. It is in the General section.
I'm happy that I finally have root, but I probably need to go back to stock when I want to sync with Kies again.
If I want to go back to stock, do I only need to flash the PDA part, or everything including Modem, .pit ?
I had a look at the link and seems like there are some special instructions. I haven't tried connecting this to Kies though so can't comment on that.
---
DXJV9/DXJV9/OLBJV9/Sbl (MultiCSC): Download (158.1 MB) (Build date: Wed May 18 19:32:07 KST 2011)
(MultiCSC: CCM, DGI, GLB, KOR, MIS, MM1, SIN, SMA, STH, THL, UMB, XEV, XME, XSE, XSO, XSP, XTC, XTE, XXV)
Special for DXJV9:
1. Flash with re-partition using 513.pit.
2. You will see a lot of red text after the flash is done, don't panic, just do a 'wipe data/factory reset' and reboot the device when done.
3. Let the device boot all the way then turn it off.
4. Re-enter Download Mode and re-flash only the CSC file without pit and without re-partition.
5. Enjoy
update 5: back to stock
Zhousibo said:
I had a look at the link and seems like there are some special instructions. I haven't tried connecting this to Kies though so can't comment on that.
---
DXJV9/DXJV9/OLBJV9/Sbl (MultiCSC): Download (158.1 MB) (Build date: Wed May 18 19:32:07 KST 2011)
(MultiCSC: CCM, DGI, GLB, KOR, MIS, MM1, SIN, SMA, STH, THL, UMB, XEV, XME, XSE, XSO, XSP, XTC, XTE, XXV)
Special for DXJV9:
1. Flash with re-partition using 513.pit.
2. You will see a lot of red text after the flash is done, don't panic, just do a 'wipe data/factory reset' and reboot the device when done.
3. Let the device boot all the way then turn it off.
4. Re-enter Download Mode and re-flash only the CSC file without pit and without re-partition.
5. Enjoy
Click to expand...
Click to collapse
I have followed these instructions now to go back to stock. All worked well.
I want to try getting root another way, I prefer to have root and still be able to use Kies, I could not get Kies to work with the fuguroot Mod. It was nice to have root though without having to do a complete wipe and data restore.
Next I'll try the suggested method with Speedmod.
Speedmod Kernel and Chebon Rom, the solution for DXJV9
Speedmod Kernel and Chebon Rom are a good solution for having root on DXJV9. It's running well and I can use Kies again.
Thanks to the apps Titanium Backup, "SMS Backup&Restore" and "Backup Call History" flashing everything did not cause much of a headache.
Good to hear. I always thought upgrading the kernel would prevent you from upgrading through Kies. I don't think it makes a big difference as once you start flashing though, not much incentive to go back. Beware, can be addictive trying new roms
can you teach me how you rooted ur galaxy s with dxjv9?
For me, the simplest option was to install SpeedMod kernel (check the Development forums and do a search for SpeedMod). Also check CF-Root. Follow the instructions and your should be good.
MrWil said:
Speedmod Kernel and Chebon Rom are a good solution for having root on DXJV9. It's running well and I can use Kies again.
Thanks to the apps Titanium Backup, "SMS Backup&Restore" and "Backup Call History" flashing everything did not cause much of a headache.
Click to expand...
Click to collapse
Sorry to bother! How can i find Speedmod Kernel, Chebon Rom and its instruction?
Search the Dev forums for Chebon and Speedmod. Should come up pretty quick.
Sent from my GT-I9000 using XDA Premium App
So did any of that process delete anything, because i just want to back up everything and then go to Darkyys ROM. And restore primarily contact data with all links intact.
Thanks
There are options for No-wipe but the cleanest method is usually a wipe.
Most ROM flashes will typically wipe your data which usually means wiping settings and applications (the SD card is usually not wiped). Contacts and stuff synced to Google are typically stored with your Google account (just make sure you have synced).
Titanium Backup is a good option to keep backups but is not free. I think there are others if you search.
Most likely you will have to wipe if going to Darky (but once on Darky's then No-wipe options are very good and you don't lose settings, etc.)
So after playing around with some different software in Froyo, got the force close errors, have tried numerous Odin3 1-click to stock which appears to work fine but phone goes past AT&T splash screen and then just goes dead....
The internal sd card seems to be the problem - which lots of other posts are talk about....but even when Odin3 1click back to stock, it doesn't seem to format the sd.
I am getting this error when attempting to "format internal sd-card" in recovery mode.
I get the following error:
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
Here is the result of my successful Odin3 one-click back to stock JF6:
<ID:0/029> boot.bin
<ID:0/029> cache.rfs
<ID:0/029> dbdata.rfs
<ID:0/029> factoryfs.rfs
<ID:0/029> param.lfs
<ID:0/029> zImage
<ID:0/029> modem.bin
<ID:0/029> cache.rfs
<ID:0/029> Removed!!
<ID:0/029> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Can anyone tell me where or how I might find the answer to this, or can you point me to a csc, pit, pda, tar etc combination that might work?
Have loaded many roms before this but can't solve this problem... sorry is this post been done to death.
Cheers
i897 Captivate, 1007 version, was running UCKB1, and I can access 2e recovery and download with no issues
careysenior said:
So after playing around with some different software in Froyo, got the force close errors, have tried numerous Odin3 1-click to stock which appears to work fine but phone goes past AT&T splash screen and then just goes dead....
The internal sd card seems to be the problem - which lots of other posts are talk about....but even when Odin3 1click back to stock, it doesn't seem to format the sd.
I am getting this error when attempting to "format internal sd-card" in recovery mode.
I get the following error:
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
Here is the result of my successful Odin3 one-click back to stock JF6:
<ID:0/029> boot.bin
<ID:0/029> cache.rfs
<ID:0/029> dbdata.rfs
<ID:0/029> factoryfs.rfs
<ID:0/029> param.lfs
<ID:0/029> zImage
<ID:0/029> modem.bin
<ID:0/029> cache.rfs
<ID:0/029> Removed!!
<ID:0/029> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Can anyone tell me where or how I might find the answer to this, or can you point me to a csc, pit, pda, tar etc combination that might work?
Have loaded many roms before this but can't solve this problem... sorry is this post been done to death.
Cheers
i897 Captivate, 1007 version, was running UCKB1, and I can access 2e recovery and download with no issues
Click to expand...
Click to collapse
1- Get in download mode
2- Use Odin-One-Click to go back to stock JF6
Here's the link to odin one click: http://forum.xda-developers.com/showthread.php?t=731989
It's the longest way, but safest.
but i guess u used the same and it didnt work..sometime its bcoz if corrupted file..so download it again and try fresh...
and if this doesnt work..then search for kf1 thread...and flash stock gb....try it...
There was no sbl in the odin you ran. Not sure if that would give issues other then bricking your phone if you do that with gb bootloaders but the one in the link in the last post should have it.
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.
Try this
http://forum.xda-developers.com/showthread.php?t=1191094*
Sent from my GT-I9000 using XDA App
Its because you have the modded 3e recovery to make it 2e, this is a defect of tht recovery on the UCKB1 ROM, i couldnt ever get it to work without the original recovery! Hope i helped, if i didnt tell me what was wrong
Sent from my Cappy at 1.6 GHz, V6 supercharger, KAK tweaks, and 3G booster using the XDA Premium App!
Hi B-ock - that's something I haven't heard before... how can I correct this error? How do I go back to the 3e recovery?
I've tried the Heimdall method mentioned above, and while I was very hopeful it would work (and it all seemed to go fine) - it still came up with the same errors that Odin showed.
Have tried odin 1click numerous times.
Thanks for the help guys, any other suggestions? I'm at my wits end!
Whats ur build number amd what originally came on the phone, froyo or eclair
Sent from my Cappy at 1.6 GHz, V6 supercharger, KAK tweaks, and 3G booster using the XDA Premium App!
Hi, build is 1007 and it was on Froyo 2.2(.1?) before the crash...
Any ideas where I can get my own csc, pit, pda files etc?
Thanks,
Carey
When you used the heimdall package did you click the button the flashes the pit and bootloaders or just a flash the rom only with boots no repartition? It seems like you need to repartition, and Heimdall default is to flash with no boots or repartition because it's safer. You might want to double check this. It might fix everything.
sent from the drivers seat, yup texting while driving
I had a similar problem. It was a resault of a corrupt partition table. I tried everything including using parted from the shell to repartition everything. The partitions showed up but I always got some kind of error like unable to write - I/O error. Same with fdisk. I took mine in for warranty and they replaced the main board to get it working again. If you have tried Odin back to stock with a pit then that has probably happened to you also. Most likely happened on a failed lagfix conversion like with me.
Sent from my SGH-I897 using XDA Premium App