Related
Hiya guys.
I've searched the forum as much as I can to try and solve my problems and it's got me so far but I can't find any more information to get my phone back working properly so though I'd bite the bullet and make a thread. If the information I require is actually lurking out there then I apologise just please point me in the right direction.
Here is my story.
Right I rooted my device through some video I followed on youtube (I cant post the link)
I think it successfully (as far as I know) rooted my SGS.
So with my newly rooted SGS I downloaded Darky's ROM and followed the instructions in the guide to flash it onto the device.
In the end it failed and the phone powered off and wouldn't power back on.
Panic Ensued.
I have since got my phone back into the download mode and flashed froyo 2.2 (I downloaded from some link on this site) it said it was successful but now it won't boot past the Samsung Galaxy S logo.
Please help?
Thanks alot in advance.
try to do a factory reset in recovery (sometimes it works)
and another thing, it may be that the froyo rom you downloaded was bad or something..
try to use this one with odin if the factory reset wont work. i know this one works.
Flash as PDA using Odin with repartition enabled and 512 pit
http://sourceforge.net/projects/teamhacksung/files/galaxys/GT-I9000_FROYO_FULL_PDA.tar/download
that one fixed my friend phone when something slimier happened to him.
Right thanks alot mate don't know what the hell happened but left it off and just turned it on and now it's working fine!
Scared me a little that I nearly bricked it but I really wanna try installing a new rom but don't wanna break it again :S
Just read the flash instructions and you won't have any problems.
Sent from hell to take your soul
When you flash it can take up to 10 minutes for the 1st boot, so go have a cup of tea and be patient!
Sent from my GT-I9000 using XDA Premium App
Ah right that was my first time so it might have just been me being impatient and thinking it wasn't working because it had been broken.
Also just wondering, the link I downloaded this Froyo ROM from (from another thread on here, can't find it now) is it custom or stock?
Heres some details...
Firmware version
2.2.1
Kernel version
2.6.32.9
[email protected]#36
The phone feels much snappier than before!
I'm new to all this ROM/flashing bees wax so just wondering.
Thanks muchly!
If its from some thread on here its custom some how some way (unless you just changed the kernel - which is speedmod - a very popular one - from your details.
G
Yeah it's off here from a thread I was reading on how to sort my phone being stuck in download mode.
Is it alot faster than the original rom I was running then?
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
in terminal emulator type su and then reboot recovery maybe it work
or may be you just flashed unsupported recovery
nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
I have been having the same problem recently, but not just with this rom. I have flashed many roms to my device, but it appears that almost everytime i try to flash something now, the same exact thing happens as the OP. any information on what is wrong or how to fix this would be greatly appreciated.
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
Sometimes this happens, but i am usually still able to use the rom after i wait for awhile. Recently it just gets stuck at the ATT logo screen and does nothing else.
HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK
studacris said:
HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK
Click to expand...
Click to collapse
i just tried it with a solid connection and it almost instantly said failed in the red box. now i cant turn it on or get to download mode so im pretty sure it is hard bricked. is there any way you can help me with this?
EDIT: False alarm, i can still get to download mode so i can ODIN back to stock, but i do not know if i should risk it again
Whew that was close.
You can flash to stock using a bootloader less package, that way if it fails it can't hard brick.
Then if that works, find an entire stock gingerbread package with bootloaders included, and flash that instead of just the bootloader one click. this again, will involve risk, but full Odin package seem to work better on some phones than one clicks do.
I tried to flash the bootloader again and it succeeded. i then proceeded to try and flash Fasty KK4 v1.1 and once again i was stuck at the ATT logo. For some reason with every rom i flash, when the logo pops up, it starts dim and then get bright. After it gets bright, it stays that way and it is a real pain not being able to use custom roms anymore.
If you have the GB bls just make sure you follow LL's instructions in the OP for Fasty. I had the same issue, but it was me mistake for not following the istructions properly
studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
i DO get a very colorful white noise screen whenever it boots up ...the screen goes away once it fully reboots....I wondered about it but just assumed it was a quirk of the FASTY III package...
Is Rom Manager a froyo based app?
No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS
studacris said:
No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS
Click to expand...
Click to collapse
Really? Rom Manager helped me a lot until this Fasty III installation....even in my previous rom Fasty II it worked fine and did great for backing up and restoring backups....saved my asss a few times with those restores lol....But if this program doesn't work for fasty III what comparable program can I use?
Also I still can't intorecovery mode...nothing works...I even tried using ADB and Droid Explorer....nothing seems to get it into recovery mode...
Am I going to have to flash back to stock ROM and try reinstalling fasty iii again? This seems all so tedious lol...
OR is there a way for me to flash back to Fasty II without having to go back to stock rom? or without having to access the recovery screen?
Thank you^
All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.
studacris said:
All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.
Click to expand...
Click to collapse
Thank you for the info!
Looks like fasty III is a GB based mod after all...I guess I should read up more on the rom before installing lol....I did not expect the dev to go from froyo to gb -_-
I was thinking of using your previous post for the one click gb bootloaders only....but it seems a little iffy and I can't afford to hardware brick the phone lol...
Makes me wonder tho...is it really THAT risky to flash bootloaders? It would make things simpler if i could just flash the gb bootloaders and go from there....
the whole flash should take less than a minute, where the actual writing takes only a few seconds...but if you were to lose communication in that awful window then it would be bad day.
But that is a small window, and if you have never had connection issues you should be ok if Odin tends to be iffy, you van try heimdall I've heard that works better for some.
Still haven't tried flashing the bootloaders because i'm scared of the possibility of hard bricking my phone... If worst case scenario was to happen and it gets hard bricked....are there any options to restore that phone? or is it just paper weight after?
Also until I flash those bootloaders there is no way to back up my phone or anything?
Thanks for all ur help btw!
another issue i am having is that the phone seems pretty laggy after installing this rom...even with tegra overclock premium and tweaking it up to 1252mhz 1275mv 1100mv setting...it still seems laggy when opening sms etc....is this just the results of a bad rom install? also battery life seems crappy....even after doing the battery recalibration...of course i couldn't wipe the battery stats since i cant get into recovery...
Hard bricks are recoverable by a hardware modification known as unbrickable mod, search for user Adam outler, or go to mobiletechvideos.com they both offer this service if you're not a soldering expert.
Battery recalibration does NOTHING the stats are reset everytime you charge to 100, and besides that they don't calculate your current battery level, just what's been using it, its what's used in settings> about phone> battery use. It has nothing to do with extending battery life.
oh lol...i have been reading all these threads where people are talking about how much their battery life improved after they did the recalibration and stat wipe ....well anyways I am going to attempt the bootloader flashing...I hope everything goes well! after that I want to try reflashing the fasty III ROM...
Do you have any recommendations as far as a good ROM for teh captivate? One that doesn't lag and has good gps & battery life? I would appreciate any help you can give.
Thanks!
I used AdamOutler 's guide to root and put a custom ROM on Captivate 2.2 found here:
http://forum.xda-developers.com/showthread.php?t=1012769
And everything went swiftly. AT THIS POINT, I MADE A NANDROID BACKUP
I then wanted to step up to an Ice Cream Sandwich ROM, which was the main purpose of my rooting in the first place. So, I downloaded the ROM found in this forum, as it is the most popular amongst the forums, so to seem. I found it here:
http://forum.xda-developers.com/showthread.php?t=1363760
Well I downloaded the ROM straight from my phone on the browser, then put it on the Root of my internal memory.
I booted into recovery, Factory Reset/Wipe Cache Partition/Wipe Dalvik Cache.
Went to install .zip from SD card, then clicked on install the ICS ROM.
Began to seem as if it was updating, then the phone shut off, started bootlooping.
No big deal I thought, just boot into recovery, right? I booted into recovery. It went from the Red CWM that i had seen before, to a Blue one.
I selected my nandroid backup, and it gave me all sorts of errors.
Got to the point where CWM was acting as if it could even find where it was supposed to work from?
Now I have the Phone>!<Computer on the black screen when I try to turn on.
Anyone else ever had this problem, or could someone tell me what went wrong? Not in a huge rush as this is just my development phone, but do I need to go ahead and use the Odin3 One Click to do a full complete restore or is there any way of saving what I had?
Thanks guys, God Bless.
LOL OOPS thought i was in the dev section.... ignore..help below.
xCaptivateRx said:
I used AdamOutler 's guide to root and put a custom ROM on Captivate 2.2 found here:
http://forum.xda-developers.com/showthread.php?t=1012769
And everything went swiftly. AT THIS POINT, I MADE A NANDROID BACKUP
I then wanted to step up to an Ice Cream Sandwich ROM, which was the main purpose of my rooting in the first place. So, I downloaded the ROM found in this forum, as it is the most popular amongst the forums, so to seem. I found it here:
http://forum.xda-developers.com/showthread.php?t=1363760
Well I downloaded the ROM straight from my phone on the browser, then put it on the Root of my internal memory.
I booted into recovery, Factory Reset/Wipe Cache Partition/Wipe Dalvik Cache.
Went to install .zip from SD card, then clicked on install the ICS ROM.
Began to seem as if it was updating, then the phone shut off, started bootlooping.
No big deal I thought, just boot into recovery, right? I booted into recovery. It went from the Red CWM that i had seen before, to a Blue one.
I selected my nandroid backup, and it gave me all sorts of errors.
Got to the point where CWM was acting as if it could even find where it was supposed to work from?
Now I have the Phone>!<Computer on the black screen when I try to turn on.
Anyone else ever had this problem, or could someone tell me what went wrong? Not in a huge rush as this is just my development phone, but do I need to go ahead and use the Odin3 One Click to do a full complete restore or is there any way of saving what I had?
Thanks guys, God Bless.
Click to expand...
Click to collapse
Different kernels have different colour recoveries. kernels change with rom.
Different CWM version recoveries are incompatible.
Almost anyone that has flashed a samsung galaxy phone has seen that screen, and it is correctly written " Phone /!\ PC " (you can choose to underline the /!\ if you want to be fancy). it is called the "soft brick screen" hint hint.. go search.
yes
yes. restore with same kernel you used to back it up.
TRusselo said:
Different kernels have different colour recoveries. kernels change with rom.
Different CWM version recoveries are incompatible.
Almost anyone that has flashed a samsung galaxy phone has seen that screen, and it is correctly written " Phone /!\ PC " (you can choose to underline the /!\ if you want to be fancy). it is called the "soft brick screen" hint hint.. go search.
yes
yes. restore with same kernel you used to back it up.
Click to expand...
Click to collapse
Very good responce...however after odin3 one clicking back to stock 2.1 eclair, I lost my clockwork mod folder that was on the internal SD, of course. Rookie mistake, I should've definately copied it on to the external SD card. Thanks for informing me of proper terminology. Also, after downloading rom manager and flashing, booting recovery, I can only access cwm through the rom manager, the three button fix doesn't work.
Why was this moved? I posted in general..
because you have a question/problem
rom manager is only used with 2.1 (for captivate). doesnt work on 2.2 or 2.3.X or 4.0.X
in all newer versions of android we "bake" cwm into the custom kernels we package into the custom roms. so there is no stock recovery and you dont need the update.zip.
dunno why you would flash all the way back to 2.1... EWWW.
in the dev section there is a sticky called odin master collection. use a newer stock rom. the master collection also has stocks versions, pre-packcaged with a custom cwm kernel so you can skip a step of getting it after going back to stock.
Do we know why this happened in the first place? Incompatible kernel? Is there a guide somewhere for moving from GB to ICS?
Sent from my SGH-I897 using XDA App
I thought you had to have GB bootloaders before you flashed any ICS roms ? I know I've read that ,then again I've read 10,000 threats and sometimes it becomes mind numbing.
Do you not have to flash back to 2.1 after having these problems? Right now my phone is at the soft brick screen, no button combo working. Not recognized by the computer either. I'm heading out to radio shack and make a USB jig in a bit. I'd love to just flash straight up to a gingerbread ROM if I can possibly get this thing in download mode. Anybody help a brotha out!
Edit: the sim is not activated, I just run it off Wi-Fi because big red is my carrier. This is my development phone. So I can't just KIES update to whatever the newest is.
Sent from my DROID X2 using XDA App
Any firmware should work, no need to go all the way to eclair...just flash gingerbread.
Don't think its been mentioned yet but when going from 2.2 to ICS, you have to flash the rom twice to get out of the bootloops. Sounds like you were at that point but when you flashed your nandroid instead of the ICS rom again, your phone must not have liked it.
aww.W.T.F? said:
I thought you had to have GB bootloaders before you flashed any ICS roms ? I know I've read that ,then again I've read 10,000 threats and sometimes it becomes mind numbing.
Click to expand...
Click to collapse
Not all ICS ROM's require GB bootloaders. I ran THS, and am now on vibranturk's AOKP and I came straight from 2.1
I think the issue was you're supposed to flash them twice. Well that fixed it for me. I dkbhave the gingerbread boot loaders now though
Sent from my SGH-I897 using xda premium
I went from bone stock Froyo 2.2 straight to THS ICS with no problems whatsoever. So some ICS Roms doesn't need GB bootloaders.
Sent from my SGH-I897 using xda premium
I'm on the same situation as the original poster: I'm on andromeda3 and now I want to upgrade to ICS. Right now my captivate has cwm 2.5.1.2 can I flash any ICS mod from there or do I need to do something else?
See this.... TRusselo's "Guide..." that is a Stickied Thread in the Q & A Forum.
I believe u will need the Gingerbread Bootloaders...
Sent from my SAMSUNG-SGH-I777 using xda premium
Guys, I'm new to the site but i have read nearly every xda forum post going for getting the Galaxy Tab P1000 with an ICS rom on it and im out now and cant find a thread relating to what i want to ask.
I have tried everything and even though it will install the tab simply refuses to boot, either get the black screen or stuck on the samsung logo, or boots then immediately reboots, ive tried everything from ODIN gingerbread roms to flashing cyna's and others custom ICS roms using their described methods, I can easily unbrick it now too! . ive tried different SD cards in different formats and buildign in the different zImage kernels to match my p1000.. what i cant seem to find is anyone that has successfully got a tab from Vodafone UK on ICS so any help on this would be beyond appreciative .
please!
Rich.
Quick question, for starters, you sure you have a P1000 and not some of the other ones (P1000N, P1000L...)?
If you do, try to explain the methods step by step you've been using for flashing ROMS.
When I started, I also bricked my Tab a few times before I got it right lol
(I actually bricked my tab flashing CM9 update just 10mins ago XD it's now booting again lol)
Hi Stilm, it says it is a P1000 on the back and on the box, no mention at all of an N or L as i noticed you need different kernels/zImage's for those too so can only presume its definitely just a p1000, i think in fact i did try one just to rule it out. it just seems weird that ive not seen a working UK Voda unit on anything but 2.2 but surely its only the rom thats different not the actual hardware.
first i tried cynagenmods instructions to get his CM9 on it including rooting it with oneclickroot to gain SU access, copy zip to SD Card and could boot to cynas menu to select the zip off the SD but, would say successful then brick it or would fail after a bit way through and say cant mount sd.
i tried a few other methods from other sites too but they all seem largely the same, i also tried renaming the cm9 file name to update.zip and using the update function on the original menu but this still bricked it lol.
About CM9, if it doesn't boot after flashing the ROM, flash a kernel (zImage).
the zImage is built in to the rom though, is it possible to flash just the zimage say through odin?.. because after it fails to boot the only way to get anything on it seems to be through odin or at best through the standard built in recovery?
You can use Heimdall, or tar it and use Odin. Or you can download a nightly.
would it recognise it if i tar it though i thought it had to be in a certain layout/format not just a tar container? i will give nightly a go too!
can anyone tell me why it always says CANT MOUNT /SDCARD/filename.zip installation aborted.?
johnsonra said:
can anyone tell me why it always says CANT MOUNT /SDCARD/filename.zip installation aborted.?
Click to expand...
Click to collapse
Hey, froyo and ics are totally different system. It is hard enough to flash a froyo to gingerbread without going through some problems. From my experience flashing gingerbread on froyo, I had to get a new pit file flashed together with the rom using Odin, with repartition checked. Even after that I would get error msgs like E:failed to mount /data or /system etc. I had to push new dbdata.rfs to get it working right.
any luck with getting ICS on though? so many have and its doing my head in now... given im an IT Pro too youd think itd be done by now lol. youre right though about GB thats why im thinking if its down to the actual vendor supplied units, ive not heard yet if other UK Vodafone users have had any success or indeed failure?
I attempted to root my SGS (which had stock Gingerbread Value 2.3.6) using a guide on the Snappyguides blogspot page (the system won't let me, as a newbie, post the URL).
Odin did its thing and then the Samsung Galaxy screen came up (just the white lettering, not the multicoloured animated S) and then... nothing. It just stayed like that for about five seconds, then the white Samsung Galaxy S came up again, then the blank screen ad infinitum.
I can access the download screen and I can access the recovery screen (which does seem to indicate that ClockworkMod v2.5.1.0 has been installed). The trouble is that none of the options seem to do anything.
I have tried searching the forum for similar problems and have read the sticky. The only answers I seem to have been able to find so far suggest flashing a new Rom.
Before I go this far, is flashing a new Rom really necessary in this instance? I have never done this procedure before, so I'm wary of messing things up even further. But obviously if the phone is past the point of no return as far as the stock Rom is concerned, then that'll be what I have to do.
I'd appreciate some advice before doing anything else to my phone though.
I now seem to be able to get the recovery menu options to respond, so maybe all is not lost. Have set it to root and it's currently converting to EXT4 and is about halfway through that.
I'm hoping once that's done, it'll be bootable.
If not, what do I need to do to make the SGS boot again? Is there any way of getting back to stock or can I only flash a stock rom back on?
Nope, still not booting. It just keeps going to the Samsung I9000 white lettering, stays there for five seconds, goes blank for five seconds, then the white lettering goes back and on, off like that forever.
So... anyone willing to help?
...
have a look in this thread http://forum.xda-developers.com/showthread.php?t=1225879
Lexrsk said:
have a look in this thread http://forum.xda-developers.com/showthread.php?t=1225879
Click to expand...
Click to collapse
Thanks for responding.
Sorry for being a n00b but I can't find anything in there that helps me. All I see is a lot of jargon about various roms, kernels and something called Voodoo.
I had a working phone with Gingerbread 2.3.6 Value. I added Clockworkmod via Odin. Now I can't get the phone to boot beyond the splash screen. It doesn't even get as far as the animated S, all I get is the splash screen going on and off every few seconds.
All I want is to get my phone working again, I really couldn't care less about custom roms etc.
If anyone can help this poor n00b, I'd be very grateful!
Incidentally, I've downloaded what I understand to be the factory rom for JW4 from sammobile.com - this is a 171MB zip file with just two files inside - a tar file called JW4_JW5_JW4 and a dll file called SS_DL.dll. I'm not really sure what to do with these to restore my phone via Odin. This is the kind of thing I need help with - the threads I've read so far don't make much sense to a poor confused n00b I'm afraid.
evilcartman2 said:
Thanks for responding.
Sorry for being a n00b but I can't find anything in there that helps me. All I see is a lot of jargon about various roms, kernels and something called Voodoo.
I had a working phone with Gingerbread 2.3.6 Value. I added Clockworkmod via Odin. Now I can't get the phone to boot beyond the splash screen. It doesn't even get as far as the animated S, all I get is the splash screen going on and off every few seconds.
All I want is to get my phone working again, I really couldn't care less about custom roms etc.
If anyone can help this poor n00b, I'd be very grateful!
Incidentally, I've downloaded what I understand to be the factory rom for JW4 from sammobile.com - this is a 171MB zip file with just two files inside - a tar file called JW4_JW5_JW4 and a dll file called SS_DL.dll. I'm not really sure what to do with these to restore my phone via Odin. This is the kind of thing I need help with - the threads I've read so far don't make much sense to a poor confused n00b I'm afraid.
Click to expand...
Click to collapse
I'll help u, I went through this when I was a noob and because I didn't know about xda I had to just figure a way out, I am sorry to say but u have soft bricked your phone, luckily its not hard to unbrick, here's a link to a post i made the other day with proper guides that I use often and they are noob friendly, the files u need to download are there but it 2.3.3 and it JW4 but it will be a start to get ur phone back to life,
If you like my posts hit thanks
Here the link http://forum.xda-developers.com/showthread.php?p=25572245
If you like my posts hit thanks
OK, thanks for that. I'm supposed to be asleep right now, so I'll come back to this later but thanks for helping.
But just to clarify for now - this will restore the phone to a working version of 2.3.3 and from there I can get back to the latest stock rom (2.3.6) via Kies, yes? I need to get into Kies anyway to restore my contacts from backups (as I haven't yet seen a way of restoring the backups except via Kies).
Thanks once again.
evilcartman2 said:
OK, thanks for that. I'm supposed to be asleep right now, so I'll come back to this later but thanks for helping.
But just to clarify for now - this will restore the phone to a working version of 2.3.3 and from there I can get back to the latest stock rom (2.3.6) via Kies, yes? I need to get into Kies anyway to restore my contacts from backups (as I haven't yet seen a way of restoring the backups except via Kies).
Thanks once again.
Click to expand...
Click to collapse
Yip I guess that is right. I have never tried it but yes it should work
If you like my posts hit thanks
Well, I did get it working again in the end by using a factory rom. Thanks for your help anyway, W1nst0n.
I do intend to attempt to root it again but this time I intend to do it properly.
Any suggestions on what may have caused the boot problem I had? Perhaps using a version of ClockworkMod that was incompatible with 2.3.6 Value?
evilcartman2 said:
Well, I did get it working again in the end by using a factory rom. Thanks for your help anyway, W1nst0n.
I do intend to attempt to root it again but this time I intend to do it properly.
Any suggestions on what may have caused the boot problem I had? Perhaps using a version of ClockworkMod that was incompatible with 2.3.6 Value?
Click to expand...
Click to collapse
Yeah that or the wrong root file for ur baseband
If you like my posts hit thanks
evilcartman2 said:
Well, I did get it working again in the end by using a factory rom. Thanks for your help anyway, W1nst0n.
I do intend to attempt to root it again but this time I intend to do it properly.
Any suggestions on what may have caused the boot problem I had? Perhaps using a version of ClockworkMod that was incompatible with 2.3.6 Value?
Click to expand...
Click to collapse
Check in about phone for the kernel version. for example mine is 2.6.35.7-I9000TDVJV6-CL530973
The important part is the bold text.
search the link that i posted earlier for a odin version and flash as PDA
Good luck
Evilcartman, when u wanna get me help find me on the I9000 q&a-ask me anything I got the answer thread, it where I spend most of my time.
If you like my posts hit thanks