Related
Ok Fellas! just got my phone last night, rooted it installed the stock froyo JK4.
I come from htc desire so my recovery was bit different installed rom manager & got cloworkmod 2.5.1.2.
Downloaded a rom on phone, rebooted into recovery, but this recovery has purplish text instead of green & there is no install from SD. I cant think of any thing at the moment can some one please help, I wanna install some other rom, other than the stock froyo. PLEASE HELP.
You need to install clockwork revory if you go to the rom manager application there will be an option to flash clock recovery right at the top when you open the application hope this claers things up
yep i did sir, but still there is no option to install from sd, it only allows me to install as update.
from teh rom manager im selecting Galaxy S I9000 for clockwork recovery and it successfully downloads and when i press reboot into recovery its still takes me to the purple screen....i think this means that im not able to get into clockwork recovery any help.??
you have to select 'install update.zip' the first time, this will install clockworkmod and then you can proceed.
The problem is your using 3e recovery and cwm will not work with 3e.
To get 2e recovery you will have to use odin and flash a kernel that has 2e recovery, I suggest hardcores kernal as it comes with cwm already , from there you can install what ever custom rom you want using.the update.zip or installing zip from sd.
Sent from my GT-I9000M using XDA App
FuryriderX said:
you have to select 'install update.zip' the first time, this will install clockworkmod and then you can proceed.
Click to expand...
Click to collapse
Hey man as per your instructions i got the clockwork dome thru rom manager and rebooted into recovery. I pressed update and i ran for a bit but then gave an error about the signature of the package and installation aborted. Pls help.
Sent from my GT-I9000M using XDA App
Samdroid_G_S said:
The problem is your using 3e recovery and cwm will not work with 3e.
To get 2e recovery you will have to use odin and flash a kernel that has 2e recovery, I suggest hardcores kernal as it comes with cwm already , from there you can install what ever custom rom you want using.the update.zip or installing zip from sd.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Hey man you sound pretty helpful would you direct me in a direction for those recovery files ur talking about and some sorta guide. Much appreciated eh.
Sent from my GT-I9000M using XDA App
the best way to get clockwork working on i9000m (personally i believe)
is to flash the kernel for Speedmod... you should see it in development forum... just flash that kernel with odin
and your recovery will work fine
danial.aw said:
the best way to get clockwork working on i9000m (personally i believe)
is to flash the kernel for Speedmod... you should see it in development forum... just flash that kernel with odin
and your recovery will work fine
Click to expand...
Click to collapse
Hey man thanks alot, do you mind pasting a link here. If you kindly can please and thanks again.
Sent from my GT-I9000M using XDA App
There are a few things i could suggest.
1. Keep your flashing to a minimum if you have the i9000m. There is a high probability that your phone's memory card is defective and you'll ruin it by accessing it more often. Froyo broke lots of bell phones, and being a rom junky means more flash activity. I am on my second phone, but some people are up to their fifth. Flash a good stable rom and dont go too crazy flashing after that
2. download ODIN, and most 3rd party kernels have 2e i think (http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-download-speedmod.html) - pretty sure speedmod does. voodoo also does, all kernels can be found in the dev section easily
Just make sure you download the ODIN version of the kernel and not the CWM file, because since you dont have CWM already, you'll not be able to use it.
There is a problem with USB mounting your sd cards on your pc without patching, since you are running a stock 2.2, so you would need the patch unless you go to a 2.2.1 rom
3. 2.2.1 runs nicer than 2.2, but i havent flashed to a JPY because i am paranoid about my second i9000m dying before i get a backup phone . You may want to flash a jpy mod (like doc rambone's, or darky's), but if you have battery life problems flash a different modem, like the JK4 modem used in bell's latest official rom
junooni.1980 said:
Hey man thanks alot, do you mind pasting a link here. If you kindly can please and thanks again.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
You can find the thread here http://forum.xda-developers.com/showthread.php?t=822756
You can find the instructions here for ODIN http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install.html
Just read through that all the answers your looking for are there ;p.
pervert said:
There are a few things i could suggest.
1. Keep your flashing to a minimum if you have the i9000m. There is a high probability that your phone's memory card is defective and you'll ruin it by accessing it more often. Froyo broke lots of bell phones, and being a rom junky means more flash activity. I am on my second phone, but some people are up to their fifth. Flash a good stable rom and dont go too crazy flashing after that
2. download ODIN, and most 3rd party kernels have 2e i think (http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-download-speedmod.html) - pretty sure speedmod does. voodoo also does, all kernels can be found in the dev section easily
Just make sure you download the ODIN version of the kernel and not the CWM file, because since you dont have CWM already, you'll not be able to use it.
There is a problem with USB mounting your sd cards on your pc without patching, since you are running a stock 2.2, so you would need the patch unless you go to a 2.2.1 rom
3. 2.2.1 runs nicer than 2.2, but i havent flashed to a JPY because i am paranoid about my second i9000m dying before i get a backup phone . You may want to flash a jpy mod (like doc rambone's, or darky's), but if you have battery life problems flash a different modem, like the JK4 modem used in bell's latest official rom
Click to expand...
Click to collapse
Oh crap! really, i think imma sell this phone rite away then, cus coming fro desire im a rom junky. I guess this aint the rite phone from me.
Yeah, there are massive known problems with internal memory on these phones. I'm already on my second, and if i have more issues, i'll be buying the international i9000 from ncix.com. same phone, no internal memory problems.
Hi guys I hope someone can help me, I rooted my S and did factory reset ready to install darkys 9.3 rom, installed cwm and CF-Root-XW_OXX_JV1-v1.3-BusyBox-1.17.1_NO-CWM.zip that cf file, everything went ok with odin and when the phone rebooted it wont get past the Galaxy S screen, cant get into download or recovery mode and when I hold the power button it goes off and then comes straight back on, is there anything I can do to sort it, I am on Virgin, 2.2.1 JPW, thanks for any help
Did you came from another custom rom before flashing Darky's?
Have you disabled any lagfix before flashing?
Hi m8. Stock and no lagfix applied. I have been in touch with Virmin and they are couriering a new phone to me tomorrow. Thx for the reply.
sarbe said:
Hi m8. Stock and no lagfix applied. I have been in touch with Virmin and they are couriering a new phone to me tomorrow. Thx for the reply.
Click to expand...
Click to collapse
No 3 buttons combo = JIG
Always Check that you have the 3 B COMBO, before flashing anything it's on a steacky thread!! (i think admin should change the color of the sticky thread).
Will they charge you for a new phone as you have a custom rom on the exchange .
jje
No 3 button combo m8.
It is on stock m8 after doing factory reset.
GOOD .
jje
Lagfix
I also encountered this. But my problem was that I had lagfix enabled when flashing a new kernel. Just reflashed the previous kernel and disabled the lagfix. Flashed the new kernel again and everything was good.
I also found this when updating from JM7 to JS5, directly.
Seems it was a patience issue. That screen can take a long time after a flash.
Once also it ended by a shutdown after a while. Reflashing to JM5 then to JS5 through the 3 combo buttons solved it + repartition
sarbe said:
Hi guys I hope someone can help me, I rooted my S and did factory reset ready to install darkys 9.3 rom, installed cwm and CF-Root-XW_OXX_JV1-v1.3-BusyBox-1.17.1_NO-CWM.zip that cf file, everything went ok with odin and when the phone rebooted it wont get past the Galaxy S screen, cant get into download or recovery mode and when I hold the power button it goes off and then comes straight back on, is there anything I can do to sort it, I am on Virgin, 2.2.1 JPW, thanks for any help
Click to expand...
Click to collapse
Man, hope you get/got your new phone but you fu**ed up. Your problem stands out like dogs balls. You've even put it in capital letters.
1. You flashed CF ROOT JV1-NO CWM.
JV1 = Gingerbread. You were on 2.2.1 Froyo. Of course it won't boot up.
NO CWM - means exactly that. What's the purpose of installing cwm/recovery then flashing a kernal that ends with NO CWM?? It doesn't support it. How were you going to flash darkys?
Man, not knocking you but you really need to read instructions before doing **** like this. Any 2.2.1 (maybe even 2.2) cf root version would have avoided this.
2. You say the phone was stock when returned because you factory reset. You forgot that you flashed a custom kernal after that based on firmware that hasn't even been officially released yet. The reason it wouldn't boot. So, it aint stock. Shouldn't matter anyway as Sammy will just force it into download mode and reflash.
3. Since you initially flashed with Odin, then 3 button method was working before. So, the lesson for us all is: jv1 kernal + froyo base = brick. Jig sellers aren't complaining.
I'm also with virgin but using docs 2.2.1 (or CM7 2.3.3 depending on the time of day). If your near Melbourne I'm more than happy to help out with your new phone.
Sent from my GT-I9000 using XDA Premium App
ttf said:
No 3 buttons combo = JIG
Always Check that you have the 3 B COMBO, before flashing anything it's on a steacky thread!! (i think admin should change the color of the sticky thread).
Click to expand...
Click to collapse
3 button combo must have been working initially as he flashed kernal with odin. It was the kernal that busted it.
Sent from my GT-I9000 using XDA Premium App
sxi200 said:
3 button combo must have been working initially as he flashed kernal with odin. It was the kernal that busted it.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Not sure, maybe he made it with "adb reboot download" command.
My brother and I both have a Vibrant. He broke his so I loaned him mine for a week. While he had mine (which I've upgraded to 2.2), he installed Android 2.1 Voodoo 4 on it. Little to say, after rebooting, the phone wasn't booting past the boot screen.
I've now followed some instructions from the forum, and have reflashed my phone with Eugene's non-bricking ROM through Odin. The phone boots up just fine now. However, I am trying to install ROM Manager on the phone, so I can reflash my recovery ROM (non Voodoo) - and the Android market tells me it can't install the app due to not having enough free space - though I have over 1GB.
I am guessing this is because the internal disk is still setup in the Voodoo file system, and just enough space was repartitioned for the OS to go back on.
Can anyone help me restore my phone?
EDIT: I've also tried flashing a different recovery ROM through ODIN (with repartition), which also wouldn't let me get past the bootup screen.
I'm taking a wild guess here, I seriously don't know, but did you click repartition in Odin? I think that's would work, but like I said, I'm not completely sure.
I didn't repartition for the Eugene rom fix (as per the instruction I read), but did when I tried to load another version ontop of that.
I was in the Voodoo chatroom, and was able to get some help. It sounds like I need to download a stock ROM and then reset my file partition to get rid of the EXT4 partition, and reset it all to the default.
I have Eugene's "non bricking" rom, but I don't think that's what I need. Can anyone point me in the right direction of what I need and how to do this?
Just search for the stock Odin images and flash back. They should be in a sticky. I would repartition as well.
I am trying to find a stock version I can ODIN flash. Do you know where I can get one?
http://forum.xda-developers.com/showthread.php?t=848737
I've gone through ODIN, done a reflash to the stock firmware, and repartitioned the phone as well.
Now, when I boot the phone up, I get the T-Mobile screen and the Galaxy S screen, and then the phone goes black (with no lights on) and doesn't go any further. My phone has been sitting on the desk like this for 20 minutes now.
I am wondering if this is like when moving to Voodoo, it takes a while to change the format to EXT4, is the phone having to go back to the default?
I 1am into the same problem with the old voodoo. What you'll need to do is flash back to stock via odin. Ur apps memory will be real low. Flash an old 2.1 voodoo. Let it do its thing once booted put a disable voodoo file into the folder and reboot. It will be ok after that. Hope that makes sense.
Sent from my SGH-T959 using XDA App
this thread might help
http://forum.xda-developers.com/showthread.php?t=848737
fatboy547 said:
I 1am into the same problem with the old voodoo. What you'll need to do is flash back to stock via odin. Ur apps memory will be real low. Flash an old 2.1 voodoo. Let it do its thing once booted put a disable voodoo file into the folder and reboot. It will be ok after that. Hope that makes sense.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thanks fatboy, but I can't even flash back to stock. The phone won't boot up.
hey fellas
i just went to go from 2.3 back to darky ROM and my phone is having a fit, its constantly rebooting at the first boot screen, i still got download mode though
no matter what i try nothing works.
have tryed darky RE, JM5, JL2, JH1, DV3 the JVK, download EZBase now to see what happens
this is my 2nd phone i have ****ed up doing this i think
aussiesausage said:
have tryed darky RE, JM5, JL2, JH1, DV3 the JVK, download EZBase now to see what happens
this is my 2nd phone i have ****ed up doing this i think
Click to expand...
Click to collapse
Are any of those stock rom's you are trying, or are they all Darky's roms?
Flash a stock rom, hopefully that will get you up and running. After that, format your sd card.
couple of them are stock, none worked.
downloading a march 2011 stock firmware from samfirmware now, aswell as EZBase rom
If darkys is a 2.2.1 based rom then you need to flash to that base first.
Try a stock 2.2.1 firmware in odin with all 3 files and tick repartition. I use jpu and always works.
Sent from my GT-I9000 using XDA App
MY fix for broken phones is .
Use Odin flash Eclair with pit 512 and repartition checked .
Phone works flash base Froyo .
Phone works you can now customize as required .
Choose a rom this time that does not kill phone .
jje
thanks fellas, will try that.
i've flashed about 5 ROMS and tryed repartion and none have worked, will try a eclair, gotta go download one
ok, JPU did not work. 3 files, re-partion and 512 pit
oh dear
When you say jpu didn't work, did the process actually start in Odin and complete?
If not, just reboot download mode again, close and restart odin and try again.
Sent from my GT-I9000 using XDA App
yeah it said PASS, just got the stupid white reboot thing.
JE3 ( 2.1 ) halfed worked, it went into recovery, dont some **** then booted. then i got something like "kernel panic pload" with all this red writing ????????
i think that might be cause i got a 2.2 kernel flashed?
broken phone broken?
here is what im getting
Uploaded with ImageShack.us
LINKL http://img405.imageshack.us/i/img20110402030025.jpg/
sorry for the spam typing, now im getting this. and it goes to the animated SGS logo, hangs for about 1 minute then phone turns off
Uploaded with ImageShack.us
sorry for spam typing, now im getting this, it goes to the animated boot logo then hangs and turns off
Uploaded with ImageShack.us
thanks for the help guys. but phone is dead
it will not even turn on now, plug into charger nothing happens. held in power button for ages and it wont turn on, no download mode, nothing.
my 2nd SGS dies, this is 1 month old. time to call mobicity and warranty it
damn im sick of this thing
aussiesausage said:
thanks for the help guys. but phone is dead
it will not even turn on now, plug into charger nothing happens. held in power button for ages and it wont turn on, no download mode, nothing.
my 2nd SGS dies, this is 1 month old. time to call mobicity and warranty it
damn im sick of this thing
Click to expand...
Click to collapse
yes, happened that to me too. If it;s not starting anymore, than you must rewrite it's bootloader with JTAG...JIG won;t help. The point is, when you tried to go back on 2.2.1 you should first flash the bootloader with heimdal. With bootloader updated you shouldn't have any problem flashing back JM8 or something
sorry for you
Crysis21 said:
yes, happened that to me too. If it;s not starting anymore, than you must rewrite it's bootloader with JTAG...JIG won;t help. The point is, when you tried to go back on 2.2.1 you should first flash the bootloader with heimdal. With bootloader updated you shouldn't have any problem flashing back JM8 or something
sorry for you
Click to expand...
Click to collapse
may i ask what JTAG is?
There might be answer to your misery, check Yovi's thread, he found hard reset method for totally bricked phone.
Sent from my GT-I9000 using XDA Premium App
Edit. Just read you can not power up. Go with Jobiza's post.
Flash just a kernel in PDA ie voodoo or speedmod k13. Nothing else and auto reboot checked. After that flash away.
This happened to me and I tried different combos for hours till this method and it worked.
Good luck mate.
Sent from my GT-I9000 using XDA App
Don't know did you tried it, but if you are able to go to Download Mode, download JVK with bootloaders from XDA, start Odin check Re-Partition and Phone Bootloader Update select filef from new FW connect phone and it should do the magic I hope.
If not http://forum.xda-developers.com/showthread.php?t=1018620
Maybe last resort?
http://forum.xda-developers.com/showthread.php?t=1018620&page=2
^^^
Yeah aussiesausage!
Let us know if this works! You can do it!
My 2 cents..
I was using ICSSGS from 1st RC. But it becomes very laggy after 3-4 weeks, so factory reset every month was necessary. I decided to change ROM.
I installed DOC's v12 ( I assume is is the same Doc that was cooking ROMs for my Omnia, and I was werry pleased with those ROMs). Did wipe, cleaned cache, cleaned Dalvik, formatted /system, flashed ROM, wipe again and it was working. But after two days it was still very laggy (talking about waiting for response for 3-5 seconds) so I wanted something faster. I had choose this Openkang milestone 6.
And then the fun begins.
Downloaded, copied to sd, booted to CWM, all wipes, flashed ROM, flashed gapps and went to bootloop. 3 button combo worked only for download mode, not for entering CWM. There was no way I could access CWM. I even could not enter Android boot (don't know exactly how it is called, but it saved my TF101 more than once.)
So after 1/2 hour of unsuccessful trying to get to CWM, phone just shows logo for icyglitch kernel and went to boot again, I have seen that only option to do anything was Odin. I downloaded Odin, downloaded some 2.3.6 ROM and downloaded CWM for that rom.
First I had to find driver for phone. I remembered phone on ICS wants nexus drivers so I installed those, booted phone to download mode and flashed 2.3.6 rom with Odin.
Phone booted, boot animation was on screen, but it did not boot to working Android. I didn't care too much, just booted to download mode again, flashed CWM and now I had at least access to my sd card. Did all wipes again, flashed DOC again and went to bootloop (Icyglitch kernel logo) again.
....
So I repeated Odin procedure, and when I had working CWM I flashed good old ICSSGS 4.02. This one worked.
I had spent 4 hours to solve this problem mostly because I was not full prepared to flash.
-I had no working USB driver on PC
-I did not had Odin
-I do not have ADB installed. Even if I had it, I don't know much how to use it.
-I did not have any working 2.3.6 ROM WITH bootloader
-Nandroid backup... hmmmm... what is that? Bah, don't need it...
Luckily I flashed my phone so many times I already roughly know what to do, but I still have experienced my share of "OMGOMGOMGOMG".
My advice to new and seasoned flashers:
Don't be cocky. After million of successful flashes once will go wrong. If nothing else Murphy will kick in. And when something goes wrong, be sure that all that you need to rescue phone is on your HDD and you know WHERE it is and how to use it. And read guides. And when you finish reading read them again, then go to sleep and flash next day.
Now I'm even more satisfied with myself because I do not flash other people's phones. If it happens that I create a 400€ brick, it will be at least mine.
If this helps anyone to restore phone, click Thanks button :good:
Thankyou for being man enough to share this, I hope all noobs read this and start getting the message!
slaphead20 said:
Thankyou for being man enough to share this, I hope all noobs read this and start getting the message!
Click to expand...
Click to collapse
Lol you were faster .
I had the same problem today trying to flash aokp m6...
Got bootloop and then Odin was hanging at various points when I tried going back to stock GB.
I thought I was goosed but the good old SGS came through in the end!
Sent from my GT-I9000 using xda premium
Flashing can be frightful. I'm sure every seasoned flasher here on XDA has had their fair share of OMG moments. I know I sure have.
Future advice: after you lost recovery, you didn't need to go back to GB. Stratosk (of Semaphore Kernel) has a .tar version of his ICS kernel that can be flashed with Odin, which will then restore your CWM. This would have been a faster, simpler fix for you. Keep that in mind for next time.
I would suggest you try SlimICS the next time you get sickend of (laggy) ROM. I for one, absolutely love SlimICS, and as all, it does have some drawbacks (no lag, though) when you're pimping it out too much.
upichie said:
Flashing can be frightful. I'm sure every seasoned flasher here on XDA has had their fair share of OMG moments. I know I sure have.
Future advice: after you lost recovery, you didn't need to go back to GB. Sratosk (of Semaphore Kernel) has a .tar version of his ICS kernel that can be flashed with Odin, which will then restore your CWM. This would have been a faster, simpler fix for you. Keep that in mind for next time.
Click to expand...
Click to collapse
Too bad I didn't know that. Somehow I was convinced that no ICS rom or kernel is flashable via Odin. But Later when everything worked and I finally had time to breathe I thought that I didn't need to go to GB. I think maybe only to flash any GB CWM with Odin would be enough. All I needed was working CWM, not entire rom.
Anyway, I'll try Slim now, let's hope I won't need to rescue phone again.
I bricked my phone twice yesterday, trying to install a CM9. It was my first attempt to modify a phone. Nice start.
bpp9 said:
I bricked my phone twice yesterday, trying to install a CM9. It was my first attempt to modify a phone. Nice start.
Click to expand...
Click to collapse
Happens to everyone! 2years in and I accidentally wiped my sd card yesterday! Was a long night! It's a fast learning curve but fun when you get the hang of it!
Always brick my phone in the past, nearly one time a day
Well some tips for flashing:
- On stock ROMs, try flashing all partition firmware (i.e. 3 files in Odin) with re-partition checked before finding for help.
- Always backup you data with apps like Titanium backup, I don't usually use nandroid because it is not so flexible.
- Get GB bootloader before going to CM based ROMs, and go back to froyo bootloader if you want to have froyo back (search EzBoot for this).
- CM based ROMs and stock ROMs use a different filesystem, so flash all partition firmware before going back from CM to stock.
- Same reason, you will mostly get bootloops when going to CM ROMs. In this case, just hold the 3-button combo to enter recovery and flash it again.
- Same reason again, don't use CWM2 recovery to flash CM.
In case that anyone don't know, CM means CyanogenMod.
Hope this helps!
Sent from my GT-I9000 using xda app-developers app
tt0204 said:
Always brick my phone in the past, nearly one time a day
Click to expand...
Click to collapse
Uauuu, and you still didn't have heart attack?
I'm not sure if the fact that I managed to rescue my phone is good. Now I still don't have reason to buy SGS II.
And yes, Slim is woking, you can see my new signature. :highfive:
Managed to flash properly before I did
Wait at least until we get a working jelly bean before getting a new phone!
Sent from my GT-I9000 using xda app-developers app
slaphead20 said:
Happens to everyone! 2years in and I accidentally wiped my sd card yesterday! Was a long night! It's a fast learning curve but fun when you get the hang of it!
Click to expand...
Click to collapse
Ahaha, I did the exact same thing the day before yesterday!
Using GT-I9000 my sent Tapatalk 2 from.
First time i flashed my phone was a heart in mouth moment when it boot looped for the first 2 or 3 times.
Swore I'd never flash my phone again. Over a year later and my phone has gone through countless changes and still going strong.
The only other issue I've had with customizing my phone is telling my flatmate about it. Problem being that he doesn't quite understand the concept of 'rooting' or 'flashing'. At least not in the geek sense of the words.
Yesterday,i was reverting to stock from ics you know...And rooted JW4 with cf.then i wanted to flash semaphore's 2.7.4.I am %100 sure that there was nothing wrong.Just semaphore over cf.Did that ten times!... so here it is;
when flashing process started odin gave fail WHILE flashing zImage.not after or before.Just at the middle of flashing zImage.
I dunno why maybe that one was a random error of odin who nows....
Anyway after it said fail,phone shutted down itself from download mode..First thing that i tried,entering to recovery.But phone was not responding.No boot logo or..just black screen.
I took a deep breath.Restarted my pc while it is restarting i put out the battery from phone wait for 30sec.
Then after pc started up ,i opened odin and put the files etc etc.
Then magical thing happened
I tried directly to the d.mode it worked and flashed JVQ then got JW4 from kies
This was my story...
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
dreamer94 said:
Yesterday,i was reverting to stock from ics you know...And rooted JW4 with cf.then i wanted to flash semaphore's 2.7.4.I am %100 sure that there was nothing wrong.Just semaphore over cf.Did that ten times!... so here it is;
when flashing process started odin gave fail WHILE flashing zImage.not after or before.Just at the middle of flashing zImage.
I dunno why maybe that one was a random error of odin who nows....
Anyway after it said fail,phone shutted down itself from download mode..First thing that i tried,entering to recovery.But phone was not responding.No boot logo or..just black screen.
I took a deep breath.Restarted my pc while it is restarting i put out the battery from phone wait for 30sec.
Then after pc started up ,i opened odin and put the files etc etc.
Then magical thing happened
I tried directly to the d.mode it worked and flashed JVQ then got JW4 from kies
This was my story...
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
Click to expand...
Click to collapse
Actually boot directly into download mode without rebooting computer/phone will work
i know but wanted to live with that action,adrenaline
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
I think we should start a membership here. Anyone who wants to join must expirience "OMG" factor for at least 20 min. I had it 4-5 times, if I count my hassling with Omnia too.
Isn't something interesting? I mean, look at us. We flash phones, sometimes we manage to make it useless, we spend hours for rescuing them, all that time we swear to god that we will never do that again, but 5 minutes after we manage to make our phones work we are ready for next flashing. Here in Slovenia we use to say that even donkey goes on ice only once, but looks like we newer learn...
My current favorite thread, it's refreshingly honest to see people laughing at themselves, and sharing their disasters, we all do it, in fact that's why we do it! Nice to see so much humility
About not bricking other people's phones....
Right now I'm in the process of bricking my boss's phone. He wants ICS on his Dell Streak 5, even if it is only pre-alpha ... Wish me luck.