Related
I have root access and have CWM, am using stock ROM. My phone does not show up as a USB device after downloading drivers multiple times as I have found in the threads on here as well as AndroidCentral, I could use help as I cannot alter the location of files and such on phone via PC having to move each individual file via "my files" will take forever. So how do I make computer read the phone as a USB device instead of CD Drive so it won't be read only.
Use Peanut Butter Jelly time Kernel with OTB, it solved my issue.
can that be flashed with ODIN as I have no way to access my SD Card as of now?
No it cant, just download it from your phone browser and boot into recovery. Flash, win.
I put SD card in my Fascinate and am transferring files with my fascinate, if i use Altered beast should i put PBJ on first? PBJ is just a kernel correct?
Yeah its just a kernel, flash the rom first then the kernel. Its voodoo with overclock, let me know how it works out. Hope I helped.
any idea after getting Altered Beast and the PBJ kernel it tells me phone is due for upgrade, what happens if i do the upgrade?
JayHawk9292008 said:
any idea after getting Altered Beast and the PBJ kernel it tells me phone is due for upgrade, what happens if i do the upgrade?
Click to expand...
Click to collapse
I have no idea why it would ask you for an update, are you on EE4 already?
JayHawk9292008 said:
any idea after getting Altered Beast and the PBJ kernel it tells me phone is due for upgrade, what happens if i do the upgrade?
Click to expand...
Click to collapse
I have no idea why it would ask you for an update, are you on EE4 already? Maybe its because your using an alpha rom? Im using Gummy Charged, I have no issues and the update isnt popping up. I WOULDNT DO THE UPDATE, watch out. Did your USB mount now?
I was EE4 to begin with fresh opening the phone, it said there was an update so I went ahead and did it. Before I ever did any playing with the phone, when I began rooting I had EE4. it now says:
Baseband v.: i510.06 V.EE4 SCH-I510.EE1
Kernel v.:2.6.32.9 [email protected] #1
Build number: SCH-I510.ED2
But it is finding phone as a removable disk now!
JayHawk9292008 said:
I was EE4 to begin with fresh opening the phone, it said there was an update so I went ahead and did it. Before I ever did any playing with the phone, when I began rooting I had EE4. it now says:
Baseband v.: i510.06 V.EE4 SCH-I510.EE1
Kernel v.:2.6.32.9 [email protected] #1
Build number: SCH-I510.ED2
But it is finding phone as a removable disk now!
Click to expand...
Click to collapse
Oh, thats why. The rom you are using is ED2, which downgraded you from your EE4. I would wipe your data and cache, flash Gummy Charged EE4, then flash the imnuts kernel AFTER that. You wont have an issue and youll have the newest Froyo update.
Is there a way to change the notification bar with Gummy? I hate the stock version! LOL
http://forum.xda-developers.com/showthread.php?t=1116086 Here is the rom. First, make sure Voodoo is off. Download Voodoo toggle from the market and turn your voodoo off. Clear cache/data and flash the rom, after that flash the kernel. Then let your phone boot up, mount it to USB and delete the folder called "voodoo." Boot back into recovery, go to voodoo and enable it. Itll start the conversion.
And yeah you can do that... Im not to sure how good you are with ADB put I pulled my whole framework-res.apk and ported a theme from another rom.
don't know much about adb at all
Well it takes time... But anyways, to the main point. Did you get it working?
Btw, here is the theme I ported. Let me know if you like it, maybe I can do your notification drop down. http://forum.xda-developers.com/showthread.php?p=15471987#post15471987 (Very last post.)
do i have to do wipe data/factory reset? or just wipe cache?
Factory reset to be safe.
Future reference, if all fails. Go to settings>Usb Settings>Ask on Connection.
I have a Nexus s with 4.0.3 flashed via bootloader.How can i downgrade to 2.3.x without root,cwm or debug(cause it isn't working) ?
i've tried several methods but none of them worked(Odin,Heimdall)
They all requires me to enter download mode with debug enabled.My debug mode is enabled but as far as i read on xda,the degub is not working in this version of ICS.
my question is : how can i downgrade to ANY firmware from this ICS version
P.S. Entering recovery mode is not an option...the phone simpli enters in a recovery/download mode - loop and keeps restarting.
Please respond fast.10x
The way I did it was to download Clockwork Mod app and scroll down to where it says stock... then 2.3.3. Once u flash that you'll lose root and an update to 2.3.x will be prompted to ya. If it doesn't then Google (Download) 2.3.4(x) and manually update. What model do u have btw?
- Google
You need to root is the basic moral here. Nothing else is really worth the effort of getting it done.
Hi
If the procedure for the nexus is the same as it is for the S2.
It should be straight forward.
Download your ROM, if its Orange you want here is a good link, I used it myself today:
http://androidromupdate.com/2012/02...-i9100p-firmware-updates-list-and-stock-roms/
The ROM I used was the NON WIPE type - I9100BVKJ4_I9100ORAKJ4_ORA
I include a picture of what I did.
I was initially on a custom ICS 4.0.3 XXLPH and have gone back to Orange stock rom.
Load the integrated Rom just into the PDA window - connect your phone in download mode and start, and that should be it!
Don't check re-partition or anything else.
Keep trying it will work.
I also had an initial prob whereby I installed the wrong kernel and the phone screen was messed up and seemed to be bricked and to get it back I loaded odin up.
Put phone in download mode.
Checked re-partition - unchecked 'auto reboot and f.reset'
Used a PIT (partition file)
Used a kernel file suitable for the S2 in the PDA window and pressed 'start'
This seems to have repartitioned and wiped the mistake and unbricked the phone.
This loaded and the phone booted - no messed screen.
Then I continued to accomplish the ROM switch over.
tsam19 said:
Hi
If the procedure for the nexus is the same as it is for the S2.
It should be straight forward.
Download your ROM, if its Orange you want here is a good link, I used it myself today:
http://androidromupdate.com/2012/02...-i9100p-firmware-updates-list-and-stock-roms/
The ROM I used was the NON WIPE type - I9100BVKJ4_I9100ORAKJ4_ORA
I include a picture of what I did.
I was initially on a custom ICS 4.0.3 XXLPH and have gone back to Orange stock rom.
Load the integrated Rom just into the PDA window - connect your phone in download mode and start, and that should be it!
Don't check re-partition or anything else.
Keep trying it will work.
I also had an initial prob whereby I installed the wrong kernel and the phone screen was messed up and seemed to be bricked and to get it back I loaded odin up.
Put phone in download mode.
Checked re-partition - unchecked 'auto reboot and f.reset'
Used a PIT (partition file)
Used a kernel file suitable for the S2 in the PDA window and pressed 'start'
This seems to have repartitioned and wiped the mistake and unbricked the phone.
This loaded and the phone booted - no messed screen.
Then I continued to accomplish the ROM switch over.
Click to expand...
Click to collapse
Don't do this. The method for the Nexus S is definitely NOT the same as the SGS2, or even the SGS. Although it may be possible to use Odin or Heimdall, it is not recommended. We already have enough freedom to do as we please.
I thought all android / samsung phones would follow the same procedure for flashing new roms or unbricking via Odin?
Kies is useless for updating as we all know.
So what other methods beside Odin or Heimdall can be used on the samsung nexus?
Cheers for clarifying though, I was only tying to be helpful
galaxy 2 ics to gingerbread
dear all
i am much upset that i upgrade my galaxy s2 to ics 4.0.3 , it is much laggy i want to downgrade it to gb 2.3.5 or 2.3.6 , can anybody help me to do this , with the all the steps and downloading links of the exact files , i tried alot many times and when it is done on odin with pass message , cell restarts and with error screen .
thanks in anitcipitation
Regards
Shoaib Hassan
i've just downgraded to 2.3.2 i used the rom wiper from bm and then simply flashed the oxygen rom over it
the only way and easily is odin.just go to downloading.make sure to download the correct modem ,baseband and needed files by cheking your nexus s version.ex.i9020t,i9023 .there are not the same version,and will use different modem,baseband ...
I also want to downgrade from ics to gingerbread too, by pure luck i managed to upgrade to ics (i'm completely new to this) but having had this on my phone for awhile, I want to return to gingerbread...
I'm currently grabbing kernel_I9100xwkj3 (couldnt find xwkj1 anywhere)
and
gt-i9100_o2i_i9100xwkj1_i9100o2ik11_i9100xxk14
to use with odin?
question is... is this all i need and is there anything i need to be aware of?
You need to make use of fastboot and flash the stock GB rom from factory images provided by google, then you can flash cwm and then flash any rom you want
it is because cwm can flash roms with android version up but not down means that you can flash 4.1 if u have 4.0.4 but if you are on 4.0.4 then you cannot flash 2.3.x
Hope it helps
Not getting a cell phone signal at all on my Captivate. very rarely I get it and it stays on until I reboot for some reason, or sometimes goes off on its own. No problem with wi-fi or anything else.
Have had Gingerbread 2.3.5 - KK4 (official) for a long time, and did not have this problem. Here is what I did:
Installed Cyanogenmod 9.0 (ICS 4.0.4) on my Captivate that had the stock Gingerbread KK4. Also installed the gapps-ics package from 29 April 2012
I did this after rooting, and installing clockworkmod.
Even updated it to Cyanogenmod 9.1, but have the same issues.
More detail on it:
- The cellular radio shows no signal, but Wifi is on fine.
- When I press the power button, I see the power off and reboot options, including one that says "Airplane Mode is ON", although it clearly isn't since Wifi is working
- A couple of times, I rebooted into recovery, and did a "repair permissions" and rebooted, and it got a signal, but does not happen always
- Once the signal is on, it stays on for the whole day, but goes off again after a reboot
- Turning Airplane mode on and off does not help
Is this a modem issue, that seems to be a popular problem. It's almost as if there is a software bug that fools the phone into switching off wireless radio
Please help me fix it, or share successful fixes
I had same problem when I went to helly bean then back to remics-jb I flashed back to stock then back up to what I wanted it fixed the problem so I think its the modem.
Sent from my SGH-I897 using xda app-developers app
You need to flash to stock and back.
Sent from my SGH-I777 using xda premium
How do you flash your rom?
Im a little bit afraid to bricked again my cappy.
Sent from my SAMSUNG-SGH-I897 using xda premium
KOROCK is right
So were you able to fix? I had a similar problem as well; I made the mistake of putting cm9.1 on and it bricked because I followed the instructions that popped up when I thought I had flashed it correctly. I tried everything; this is my daily driver so I had no choice but to find a fix, and find it fast as my clients were unable to get a hold of me for a few hours.... Anyways, got a little off track; but did you fix?
up_on1 said:
So were you able to fix? I had a similar problem as well; I made the mistake of putting cm9.1 on and it bricked because I followed the instructions that popped up when I thought I had flashed it correctly. I tried everything; this is my daily driver so I had no choice but to find a fix, and find it fast as my clients were unable to get a hold of me for a few hours.... Anyways, got a little off track; but did you fix?
Click to expand...
Click to collapse
Not fixed yet. Wheredo I get the stock rom.?
rdugar said:
Not fixed yet. Wheredo I get the stock rom.?
Click to expand...
Click to collapse
A little search/reading goes a long way.. http://forum.xda-developers.com/showthread.php?t=1300843
KK4 is what you'll want to go back to stock but I highly suggest you read this before you do anything http://forum.xda-developers.com/showthread.php?t=1350266
Also, before returning to stock, you could try flashing a different modem.
Check to see if your baseband is still there. If it said "Unknown", you need to restore it. CM9 is supposed to have the modem.bin file included though. Check to see if the /radio folder have modem.bin in it, if it does, and the baseband still say Uknown, then manually delete the modem.bin, do a wipe and reflash a CM rom that have modem.bin included.
If Baseband is still there and still no signal, then check to see if IMEI is corrupted or lost (if its null or doesn't match the back of the phone). You can either copy over the efs backup folder if you have one and "fix permission" in CWM. If not, then you need to ODIN the phone to stock to fix it.
Hello I rooted my i997r infuse rogers but the com# in oden was in the wrong box and it saied succesful /failed one but I didn't think much of it I was so exited that it worked I upgraded from 2.3.3 to 2.3.6 AT&T firmware thinking i have to in order to install ics I then installed cms 10 J.B 4.3 my phones runs great better than ever before execpt for the fact that my screen takes about one minute to turn on with lines I think its called rainbowing im not sure I think it has something to do with my original root that messed up my screen so I want to downgrade to stock using odin and reinstall and hopefully my screen won't be messed up so I used http://forum.xda-developers.com/showthread.php?t=1193927 it was successful I used the Odin_UXKG3_rooted_no_bootloaders_v2.zip then Odin_Stock_Rogers_UXKG3_Kernel.zip and my screen now has a shade of gray with this shade of blue this blue shade that covers the screen right when I turn it on it keeps getting worse it goes away after a couple minutes in recovery mode but now I just don't know what to do I can't even use my phone now help me please! How do I fix my video driver I guess this is whats going on help I can't seem to find a working link for CWM-UXKG3-rooted-de-odexed-update-v2.zip maybe if I install the cwm the light neon blue screen will go away?
crayzze said:
Hello I rooted my i997r infuse rogers but the com# in oden was in the wrong box and it saied succesful /failed one but I didn't think much of it I was so exited that it worked I upgraded from 2.3.3 to 2.3.6 AT&T firmware thinking i have to in order to install ics I then installed cms 10 J.B 4.3 my phones runs great better than ever before execpt for the fact that my screen takes about one minute to turn on with lines I think its called rainbowing im not sure I think it has something to do with my original root that messed up my screen so I want to downgrade to stock using odin and reinstall and hopefully my screen won't be messed up so I used http://forum.xda-developers.com/showthread.php?t=1193927 it was successful I used the Odin_UXKG3_rooted_no_bootloaders_v2.zip then Odin_Stock_Rogers_UXKG3_Kernel.zip and my screen now has a shade of gray with this shade of blue this blue shade that covers the screen right when I turn it on it keeps getting worse it goes away after a couple minutes in recovery mode but now I just don't know what to do I can't even use my phone now help me please! How do I fix my video driver I guess this is whats going on help
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showthread.php?t=1613523
Thanks I read the part about the bootloaders I flashed to gb 2.3.6 and then flashed the bootloaders hoping it would fix the blue screen i always get and have to wait 5 minutes to go away every time turn m screen on it just isin't when I power my phone on its whenever I turn my screen on I can't see anything when someone calls me I have to wait, im on a rogers infuse and I hope this isn't a permanent bug. I went back to 2.3.3 gb stock I don't have a rogers boot logo anymore but it runs fine execpt for this light neon blue that covers the screen does anyone else ever have this problem please help.
crayzze said:
Thanks I read the part about the bootloaders I flashed to gb 2.3.6 and then flashed the bootloaders hoping it would fix the blue screen i always get and have to wait 5 minutes to go away every time turn m screen on it just isin't when I power my phone on its whenever I turn my screen on I can't see anything when someone calls me I have to wait, im on a rogers infuse and I hope this isn't a permanent bug. I went back to 2.3.3 gb stock I don't have a rogers boot logo anymore but it runs fine execpt for this light neon blue that covers the screen does anyone else ever have this problem please help.
Click to expand...
Click to collapse
rainbow screen on recovery = no gb bootloaders
blue screen on phone ...maybe bad cable connection or corrosion at contact
you might have to open it and check the connections
Working and tested CWM 1.2 ghz
Phase 1:
---------
To obtain CWM head over too Jscotts odin url.
1. download the file which includes root access.
"Stock UCLB3 with root
UCLB3_Unbrick_root_1.1.zip"
2. you will also need Samsung Kies, which will install the usb driver for your Samsung galaxy. The link is on the website.
3. Place your phone into Download mode
To do this, have your usb cable for your phone plugged into the computer but disconnected from your phone. shut off your phone. When the power is off press Volume up and Volume down simultaneously, after the buttons are pressed plug in the usb cable at the same time, which should be connected to the computer.
This will place the phone in Download mode.
4. open the included Odin.exe, when you see the yellow bar under ID:COM then everything is good.
Follow the rest of the instructions on jscotts website.
Finally when this procces is done, reboot into android.
Phase 2:
---------
1) Download SGS kernel flasher
2) Click on the link on jscotts website to download a stock kernel which contains CWM. use "2013.04.30-CWM-Synthesis-1.2Ghz.zip in the following link:
forum.xda-developers.com/showthread.php?p=25724638
You now have a working GB cwm and next is follow Enthropy's CM9 guide for your first ROM!
Fullmetal Jun said:
Phase 1:
---------
To obtain CWM head over too Jscotts odin url.
1. download the file which includes root access.
"Stock UCLB3 with root
UCLB3_Unbrick_root_1.1.zip"
2. you will also need Samsung Kies, which will install the usb driver for your Samsung galaxy. The link is on the website.
3. Place your phone into Download mode
To do this, have your usb cable for your phone plugged into the computer but disconnected from your phone. shut off your phone. When the power is off press Volume up and Volume down simultaneously, after the buttons are pressed plug in the usb cable at the same time, which should be connected to the computer.
This will place the phone in Download mode.
4. open the included Odin.exe, when you see the yellow bar under ID:COM then everything is good.
Follow the rest of the instructions on jscotts website.
Finally when this procces is done, reboot into android.
Phase 2:
---------
1) Download SGS kernel flasher
2) Click on the link on jscotts website to download a stock kernel which contains CWM. use "2013.04.30-CWM-Synthesis-1.2Ghz.zip in the following link:
forum.xda-developers.com/showthread.php?p=25724638
You now have a working GB cwm and next is follow Enthropy's CM9 guide for your first ROM!
Click to expand...
Click to collapse
Thank you but it's not bricked... are you suggesting this will take away the screen issue?... k so it's been a while since I used my infuse the screen was getting so annoying that I put it away for a month last night I turned it on and the screen seemed fine, I was very pleasantly surprised I re rooted it and put on the new cm10 jellybean and noticed the longer I kept using the screen the more the lines/screen problem came back I left it untouched overnight after modding it and this morning it's fine again until continued use of the screen... I have taken it apart and unplugged all the screen plugs reattached looked around everything seemed fine so I dunno... I have a really newbie question for the way I went about getting to jellybean from stock... first I rooted it with Odin_Infused_Gingerbread_Kernel_v1 and noticed that cwm was installed so is this all I need to proceed with installing ics? because I kept thinking I needed to install 2.3.6 and that is not firmware meant for my phone and thats what I think might be the cause of my screen issue sooo do I just need to root it first then go straight to ics or do I need to put 2.3.6 then ics?
I am on a rogers infuse.
crayzze said:
Thank you but it's not bricked... are you suggesting this will take away the screen issue?... k so it's been a while since I used my infuse the screen was getting so annoying that I put it away for a month last night I turned it on and the screen seemed fine, I was very pleasantly surprised I re rooted it and put on the new cm10 jellybean and noticed the longer I kept using the screen the more the lines/screen problem came back I left it untouched overnight after modding it and this morning it's fine again until continued use of the screen... I have taken it apart and unplugged all the screen plugs reattached looked around everything seemed fine so I dunno... I have a really newbie question for the way I went about getting to jellybean from stock... first I rooted it with Odin_Infused_Gingerbread_Kernel_v1 and noticed that cwm was installed so is this all I need to proceed with installing ics? because I kept thinking I needed to install 2.3.6 and that is not firmware meant for my phone and thats what I think might be the cause of my screen issue sooo do I just need to root it first then go straight to ics or do I need to put 2.3.6 then ics?
I am on a rogers infuse.
Click to expand...
Click to collapse
Re-reading your thread, I realized that you have a i997R - Roger's. These come stock GB 2.3.4 - unlike the i997-ATT that started with 2.2.1
The difference is that the i997R has already built in bootloaders from the start. That means that Roger's phone do not get the distorted recovery with flashing we termed as "rainbow." The rainbow is fixed with a bootloader flash. Roger's phone do not need this step.
I think the color distortion you are seeing could be due to a heating issue, the screen or the graphics chip. More likely than not, this may be hardware related.
If you have opened and cleaned out the connections and such, and have not noted any difference, then the problem may be deeper situated. Further testing may require another Infuse and swapping out parts to see where the issue lies.
gl
Help!
qkster said:
Re-reading your thread, I realized that you have a i997R - Roger's. These come stock GB 2.3.4 - unlike the i997-ATT that started with 2.2.1
The difference is that the i997R has already built in bootloaders from the start. That means that Roger's phone do not get the distorted recovery with flashing we termed as "rainbow." The rainbow is fixed with a bootloader flash. Roger's phone do not need this step.
I think the color distortion you are seeing could be due to a heating issue, the screen or the graphics chip. More likely than not, this may be hardware related.
If you have opened and cleaned out the connections and such, and have not noted any difference, then the problem may be deeper situated. Further testing may require another Infuse and swapping out parts to see where the issue lies.
gl
Click to expand...
Click to collapse
Yes I bootloader flashed it in desperation with an at&t bootloader and now lost the rogers bootloader lol... My phone came stock 2.3.3 gb and I desperatly wanted gb 2.3.6 so I rooted it and did so, then after discovering ics and then after jb... I believe that installing 2.3.6 might have damaged the hardware being that its only ment for at&t i997's or possibly a combination of 2.3.6 and then installing ics then jb or whatever the case may be my screen needs 1 to 5 minutes to fully appear... my question is if I ever happen to root another rogers i997 do I need to upgrade to 2.3.6 before installing ics or can I install right after root? Because I also might re root the phone back to stock and root it then install the newer version of ics then jb cm 10.2... I am currently running on jb cm 10.2 do you think it would make a difference if I rerooted to stock then install newer ics then jb with upgrading to 2.3.6 for at&t phones??? Thank you.
crayzze said:
Yes I bootloader flashed it in desperation with an at&t bootloader and now lost the rogers bootloader lol...
Click to expand...
Click to collapse
no big deal..same phone..same hardware..different version of firmware..it's the APN for providers that makes the difference
crayzze said:
My phone came stock 2.3.3 gb and I desperatly wanted gb 2.3.6 so I rooted it and did so, then after discovering ics and then after jb... I believe that installing 2.3.6 might have damaged the hardware being that its only ment for at&t i997's or possibly a combination of 2.3.6 and then installing ics then jb or whatever the case may be my screen needs 1 to 5 minutes to fully appear.
Click to expand...
Click to collapse
yes..you are right. Rogers came with 2.3.3 not 2.3.4 as I previously stated.
the earlier versions of gb came with Carrier IQ that track users. It was taken out later.
I doubt Installing 2.3.6 or ICS or JB will cause any prob with the phone. I suspect your phone may have some hardware issues.
After the first flash, the os (esp ICS or JB) may need time to build cache and dalvik..sometimes it may take a few minutes. Blue or distorted screen, however, is not typical from my experience.
crayzze said:
my question is if I ever happen to root another rogers i997 do I need to upgrade to 2.3.6 before installing ics or can I install right after root? Because I also might re root the phone back to stock and root it then install the newer version of ics then jb cm 10.2... I am currently running on jb cm 10.2 do you think it would make a difference if I rerooted to stock then install newer ics then jb with upgrading to 2.3.6 for at&t phones??? Thank you.
Click to expand...
Click to collapse
IMO, it doesn't matter how you get to CM10.2. Rooting is just one method. The idea is to get insecure recovery...ie..cwm.
from stock rom, you can odin or heimdall a custom kernel without rooting. boot into recovery and flash what you want.
it doesn't matter if its rogers or att. same phone..same hardware. years ago, it only mattered when a user had to return or exchange the phone for warranty...after the warranty period ended..it's not a big deal.
flash away at any method you want. it doesn't make any difference in my mind. get some practice..the infuse has many restore methods via odin or heimdall
rooting gives one access to the root directory
insecure kernel or custom recovery allows one to flash firmware without manufacturer signature
Hello all,
Okay, I admit that I am gonna get a lot of "use the search tool first" replies, but please hear me out. I have done my fair share of searching. Its not that I haven't found anything, its just the things I found are useless for this SGS 4G. I really wanted to install Cyanogen Mo on the SGS (its not actually mine, a friend asked me to do it since he saw my old SGS GT-I9000 running CM).
I am gonna try and give a detailed report . The phone was originally from T-Mobile and now unlocked permanently. Its running firmware version 2.3.3 that I installed just recently. I found out that I can't install CWM on the stock kernel or bootloader or whatever and I needed a new of the thing. So I went on searching and searching....found a handful of help but none work. Every method breaks at some point and I go to the "firmware update failed" thing on the phone, which I then install 2.3.3 again using ODIN and try another method. I have tried a lot of things. Hemidall, ODIN, SuperOneClick, and a lot of gibbrish-sounding methods. None work. I am now running 2.3.3. Here are some infos:
ABOUT PHONE:
Model Number: SGH-T959V
Firmware Version: 2.3.3
Baseband Version: T959VUVKF1
Kernel Version: 2.6.35.7-T959VUVKF1-CL270364
Build Number: GINGERBREAD.VUVKF1
The files I used to flash to 2.3.3 using ODIN v1.85:
PIT: Hawk_Sidekick_VibrantPlus_831.pit
PDA: CODE_T959VUVKF1_CL270364_REV00_user_low_noship.tar.md5
PHONE: T959VUVKF1-Phone-CL1020302.tar.md5
CSC: SGH-T959V-CSC-TMB-VIBRANTP.tar.md5
I hope the above infos are enough. So, can anyone help me and point me to the right direction on how to install CWM and then install CM10 or 9 on my friends SGS 4G?
Thanks,
Tamrat
Hmmm, an interesting set of binaries, ones that don't ring a bell with me. I'm used to seeing T959VUVKJ6.
Where did you find those? Half curiosity, half trying to understand the problem, half since much of the "old" images for the phones got lost when Multiupload and what have you were shut down.
For the SGS4G, the kernel, root file system, and recovery file system are all in "boot.img" -- flash one, you flash them all. They can be flashed through Odin (assuming you really like Windows), heimdall (multi-platform), through recovery, or from a root command line (for the adventurous only).
I would say the most robust way to get where you need to be would be to use Lumin's guide to make sure you've got a viable Gingerbread set-up going, then flash something reliable to get you to MTD, like TeamAcid's CM9.
From there, you should know that some of the KK ROMs use slightly different MTD partitioning and aren't a "just flash this ROM and keep your data" kind of thing.
jeffsf said:
Hmmm, an interesting set of binaries, ones that don't ring a bell with me. I'm used to seeing T959VUVKJ6.
Where did you find those? Half curiosity, half trying to understand the problem, half since much of the "old" images for the phones got lost when Multiupload and what have you were shut down.
Click to expand...
Click to collapse
A long day Googling... and then a site turned up. One thing I forgot to mention was, before I installed this firmware, I had to use the "remove battery->plug usb->press the button combos->insert the battery" to enter download mode, but now I juts have to press vol down and power button.
Thanks for the reply,
Failure again
UPDATE:::
I tried to update to 2.3.6 as the guide suggests and I also wanted a clean stock OS in case the old one was not. But once again updating to 2.3.6 has been a pain. Kies Mini recognizes the phone but it doesn't recognize the firmware running on the phone. And also, firmware update is impossible since the button is greyed out.
I googled again and found the official 2.3.6 firmware for the phone (file name: T959VUVKJ6-REV00-home-low-CL694130.tar.md5) and tried flashing it using ODIN; absolutely no luck. It fails at the stage which says Slb.bin. Restarting the phone after that gives a "firmware upgrade failure" display. Only way to wake up the phone is to flash the previous OS back.
I am really confused here.
*********************EDIT***************
Some how, after like 10 retires and fiddling with ODIN, it finally flashed 2.3.6 to the SGS 4G. Still, fingers crossed.
*********************EDIT 2***************
Finally, its all working fine now. Thank you @jeffsf, thank you very much.
F*****************K
forgot an important step and now my IEMI number is gone........
do i throw the phone now, or is there any other way???
Don't throw your phone away! How do you know that you have "no IMEI" on your phone? We'll go from there.
Hopefully, you've backed up your data before starting to play around with ROMS. If so just load your backed up efs folder onto your storage & use Root Explorer to drop it over your existing one , it will overwrite your imei file & you will be good as new.
========================================================================================
I'm also in need of help, I have been running SlimSaber since last weekend, was wanting to try out Beanstalk. First full wipe, install & reboot wipe again, reinstall etc as per Dao's OP, but after the first install, it won't boot past the kernel splash. Tried again with same result. Decided to click it back to stock & start over, using Gremlin Remover (odin). Then saw that others were having similar issue so I tried to load in build from April1st.
But now it only boots back into recovery, won't boot to the OS ( everything indicated install was complete & no errors.)
1 clicked back again & just tried to put SlimSaber back on again, but have the same problem, will only boot into recovery.
I had to first load CM9 to get CWM 6.xx so I could install kk using TWRP
What am I not doing correctly? Thanks for any suggestions.
Flash kernel
Reboot recovery
Wipe all partitions
(Reboot recovery for good measure and wipe again if paranoid)
Install
Boot
If that doesn't do it, it is likely ROM or hardware.
---
Posted from whatever phone booted today
Since this is running GB VUVKG4, could you recommend a kernel that would work & get me to TWRP (or CWM 5.xx+)?
Either the Team Acid CM9 or Hefe Kernel should work.
---
Posted from whatever phone booted today