I hope there is a way for me to fix this. I am a noob but, I have been successful flashing things a few times in the past (and not so lucky a few times). This time I had flashed my Infuse back to stock 2.2 Froyo UCKD5 after having Zues w/ Aries HellFire running for a couple weeks. I decided to try another ROM because I was bored. Then I screwed something up thinking I knew more than I do. As I was trying to clean things up in my files to get ready to do a back-up,something happened and about half of my apps,factory and 3rd party had no files or ?? They didn't show any MB in cache / data,in TIBU or App Mgr, only "computing...", and obviously things didn't work right. So I hit the phone's Factory Reset,went into Odin3 thinking I would try doing something I never tried before,stupid me, and installed through the PDA button, zimage root tar file, success, saw the Fugu fish and then reset Odin, turned off/ on. Pulled battery from phone, usb jig to download mode, because three button method wasn't working. I thought it had something to do with the residual kernel or bootloader from Zeus. The kernel that was running is 2.6.32.9 and I don't know what that is. Any way I thought I would install KF1 .tar Odin3 installed it but it got stuck on the Samsung power-up screen,black background white Samsung letters. I usb jigged into download mode , thinking maybe I had the wrong drivers possibly and did the Heimdall Zadig driver install, nothing changed. So, I thought that I better just reflash to stock using GTG's Ultimate Unbrick, used the UCKD5 tar and it passed. Then I unplugged the phone when it shut off to reboot, it booted into blue recovery and I hit reboot and it came right back into blue recovery. I am able to get into download mode or into the ever looping blue recovery<3e>,but nothing else. No programs,Odin, Kies, Heimdall,GTG's, recognize the phone,the laptop does and says the device may not work correctly..., but I did notice what the fails were in the recovery boot-up. So I snapped pics with my Captivate and uploaded them and I will paste them here (I think XDA lets idiots like me paste in this area?). they are readable, but if I need to type everything out I can, but not until someone asks so as to keep this already lengthy story a bit shorter. Thanks in advance,KK13/khkaiser13. sent in using my Rooted Captivate on APEX12 through XDAPremium View attachment 899419
View attachment 899420
Did you try clicking flash in Heimdall, sometimes it looks like it doesn't see the phone, but you click flash and it works. Also, have you tried clearing user data and cache? (I know you said you had factory reset at one point but now that you are stuck might be worth a try.) Looks like a boot loader issue, not sure why Heimdall doesn't see the phone, I've had good luck in the past with it.
I'm tempted to tell you to format the internal sd and try heimdall again, but maybe someone with more experience would have a better idea.
khkaiser13 said:
I hope there is a way for me to fix this. I am a noob but, I have been successful flashing things a few times in the past (and not so lucky a few times). This time I had flashed my Infuse back to stock 2.2 Froyo UCKD5 after having Zues w/ Aries HellFire running for a couple weeks. I decided to try another ROM because I was bored. Then I screwed something up thinking I knew more than I do. As I was trying to clean things up in my files to get ready to do a back-up,something happened and about half of my apps,factory and 3rd party had no files or ?? They didn't show any MB in cache / data,in TIBU or App Mgr, only "computing...", and obviously things didn't work right. So I hit the phone's Factory Reset,went into Odin3 thinking I would try doing something I never tried before,stupid me, and installed through the PDA button, zimage root tar file, success, saw the Fugu fish and then reset Odin, turned off/ on. Pulled battery from phone, usb jig to download mode, because three button method wasn't working. I thought it had something to do with the residual kernel or bootloader from Zeus. The kernel that was running is 2.6.32.9 and I don't know what that is. Any way I thought I would install KF1 .tar Odin3 installed it but it got stuck on the Samsung power-up screen,black background white Samsung letters. I usb jigged into download mode , thinking maybe I had the wrong drivers possibly and did the Heimdall Zadig driver install, nothing changed. So, I thought that I better just reflash to stock using GTG's Ultimate Unbrick, used the UCKD5 tar and it passed. Then I unplugged the phone when it shut off to reboot, it booted into blue recovery and I hit reboot and it came right back into blue recovery. I am able to get into download mode or into the ever looping blue recovery<3e>,but nothing else. No programs,Odin, Kies, Heimdall,GTG's, recognize the phone,the laptop does and says the device may not work correctly..., but I did notice what the fails were in the recovery boot-up. So I snapped pics with my Captivate and uploaded them and I will paste them here (I think XDA lets idiots like me paste in this area?). they are readable, but if I need to type everything out I can, but not until someone asks so as to keep this already lengthy story a bit shorter. Thanks in advance,KK13/khkaiser13. sent in using my Rooted Captivate on APEX12 through XDAPremium View attachment 899419
View attachment 899420
Click to expand...
Click to collapse
Before you go any further,
Read my how to..click on the first link on my sigs.
Read through several times.
There is a BIG difference b/t download mode and recovery.
Thanks, I did clear Data/Cache. I also did format the sd as a last resort but, it didn't help. I don't know if you looked at the screenshots I posted but, it says Checksum Fail and Movinand Checksum Fail. I dont know what either of those are but, willing to bet if someone knows it might be repairable. Thanks Again, to both, enochpc and qkster for the helpful info which I did not know before. khkaiser13/ kk13
khkaiser13 said:
Thanks, I did clear Data/Cache. I also did format the sd as a last resort but, it didn't help. I don't know if you looked at the screenshots I posted but, it says Checksum Fail and Movinand Checksum Fail. I dont know what either of those are but, willing to bet if someone knows it might be repairable. Thanks Again, to both, enochpc and qkster for the helpful info which I did not know before. khkaiser13/ kk13
Click to expand...
Click to collapse
Put your phone in download mode. Odin or heimdall back to stock and start over.
Don't worry about anything else as long as you can get into dl mode
Hey, thanks for responding. I know the difference b/t recov. and dload. I am stuck in recovery<3e> blue, it just returns the recovery screen no matter if I press reboot, clear cache, or clear data, or try install zip. But if I usb jig it, it goes into download mode. Thats it. What I have and don't know what or how to fix is during the reboot attempt (you can read it if you click on my screenshots) it says Checksum Fail, Movinand Fail, and lfs undone. I'm gonna try to find out more about those files ( I guess thats what those would be ???) Thanks Bro.
khkaiser13 said:
Hey, thanks for responding. I know the difference b/t recov. and dload. I am stuck in recovery<3e> blue, it just returns the recovery screen no matter if I press reboot, clear cache, or clear data, or try install zip. But if I usb jig it, it goes into download mode. Thats it. What I have and don't know what or how to fix is during the reboot attempt (you can read it if you click on my screenshots) it says Checksum Fail, Movinand Fail, and lfs undone. I'm gonna try to find out more about those files ( I guess thats what those would be ???) Thanks Bro.
Click to expand...
Click to collapse
You borked something in the ROM. That's why it won't boot. Files mismatch and don't add up. That's why you're in blue recovery.
You've to get into dl mode and flash a stock ROM img. Then start over.
qkster said:
You borked something in the ROM. That's why it won't boot. Files mismatch and don't add up. That's why you're in blue recovery.
You've to get into dl mode and flash a stock ROM img. Then start over.
Click to expand...
Click to collapse
Just to add this to what qkster said! I know you said you know the difference but be sure to have proper drivers installed I personally used GTG’s Ultimate Unbrick with 100% success. If there is any doubt about bad drivers I would also suggest reinstalling them there is a very easy to use Utility called usbdeview that lets you uninstall drivers and start fresh.
Related
So I rooted my phone a few months ago but there weren't many mods out yet, so I waited until just today. I saw this one http://forum.xda-developers.com/showthread.php?t=1157593
I followed everything until I got to the part where I had to go into recovery mode, but before I was supposed to reinstall packages to get into CWM I accidently clicked on delete all user data and delete cache date because I misunderstood. So I got into CWM after and followed it and rebooted but nothing happened and the SGS4G screen just goes on and off. I didnt know what to do so I gave this a try. http://forum.xda-developers.com/showthread.php?t=1001759
I thought it would bring my phone back to stock and rooted because I couldnt recover or restore anything. It just put me in a more confused situation. When I reboot in recovery or just turn the power button on, the SGS4G screen goes on and off still.
So all I can do is this. Go to recovery. reboot,reinstall,delete user data or cache data. It says "signature verification failed" then "installation aborted" when I reinstall packages. And like I said, when I reboot the system all it does is the SGS4G screen problem.
Is there a way to start me fresh to a stock and rooted point? I dont think I have any files or anything on my phone anymore(if that is possible). I wanted to try this over again, but correctly obviously
Thanks for any help. I really need my phone soon
Were you in download mode when you used Odin? It should have worked. Make sure that it shows a yellow symbol with the android alien holding a shovel.
Sent from my SGH-T959V using XDA App
Thanks for the reply! And yeah i was in download mode. Odin said it went through and it lead my phone into recovery phone. After that I rebooted but I'm still experiencing the SGS4G screen going on and off still. Nothing else loads.
How did you set up Odin? You got the correct file loaded into the PDA box?
Sent from my SGH-T959V using XDA App
mrchovee said:
So I rooted my phone a few months ago but there weren't many mods out yet, so I waited until just today. I saw this one http://forum.xda-developers.com/showthread.php?t=1157593
I followed everything until I got to the part where I had to go into recovery mode, but before I was supposed to reinstall packages to get into CWM I accidently clicked on delete all user data and delete cache date because I misunderstood. So I got into CWM after and followed it and rebooted but nothing happened and the SGS4G screen just goes on and off. I didnt know what to do so I gave this a try. http://forum.xda-developers.com/showthread.php?t=1001759
I thought it would bring my phone back to stock and rooted because I couldnt recover or restore anything. It just put me in a more confused situation. When I reboot in recovery or just turn the power button on, the SGS4G screen goes on and off still.
So all I can do is this. Go to recovery. reboot,reinstall,delete user data or cache data. It says "signature verification failed" then "installation aborted" when I reinstall packages. And like I said, when I reboot the system all it does is the SGS4G screen problem.
Is there a way to start me fresh to a stock and rooted point? I dont think I have any files or anything on my phone anymore(if that is possible). I wanted to try this over again, but correctly obviously
Thanks for any help. I really need my phone soon
Click to expand...
Click to collapse
signature verificaton failed means u dont have a modified recovery record
u can get that out of the cwm final thread and push it to system/bin folder overwrite the one dont replace it that will solve that issue for u
I did exactly what the thread for Odin said. I already had the 64bit drivers installed. I downloaded the link that was provided for the ROM and then Odin. The rom took a while to download but it finally did. After that I held both volume buttons and then plugged in the usb and then it went into download mode. After that I opened odin and then clicked on PDA. The only thing that I could click on was the non-extracted rom that I downloaded aforementioned above.Gave it time to download and it said successful. Then I rebooted once it sent me to recovery mode. It also states to try and do it without sim and sd card in the phone which i just tried. It went through as well, but still has the SGS4G going on and off
RaverX3X said:
signature verificaton failed means u dont have a modified recovery record
u can get that out of the cwm final thread and push it to system/bin folder overwrite the one dont replace it that will solve that issue for u
Click to expand...
Click to collapse
I would try that but idk how i would be able to push it into the system/bin folder when all my phone is letting me do is go into recovery mode
Did u flash ext4 yet?
A suggestion for you.
If you can get into Down load mode which it sounds like you can, I would use ODIN to flash KC1 with its pit, PDA, Phone and CSC files and let it fully load up. Then ODIN Whitehawk's deoxed KD1 + root and try to flash your other ROM again.
It is very hard to hard brick these phones. Always take care to make sure the mount points in recovery are set to unmount, mount, mount and finally unmount when instructed to do so.
If your getting stuck with the ext4 section which causes this boot loop alot, what I have done is to disable voodoo lagfix, reboot into the newly flashed ROM then go back into recovery and enable voodoo. Has always worked for me.
This is my first post so I apologize if I don't make any sense lol. I develop android apps for a medical software company and I'm wanting to start creating ROMs to help out this great community.
I forgot to mention: http://forum.xda-developers.com/showthread.php?t=1117554 - [REF]{BIBLE} Galaxy S 4G (7/24/11) <5:00pm cst> is your best friend
icbinb is a great rom. you will definitely have to odin, as bytesfree says. you should use kc1 by raver. after you odin kc1, boot up normally and let the rom settle in for 10 minutes. then get a root manager, such as super manager or root explorer. download the 2 files from krylons final cwm thread. move both to the proper location using the root manager. make sure the recovery file is named properly. if it has the extra .bin extension in the filename, remove it. then shut down the phone, reboot into recovery, go to reinstall packages and the orange cwm will load. once that loads up, factory reset, wipe cache, go to mounts and check the mounts (u,m,m,u), go to install from sd card, flash the ext4 converter immediately followed by icbinb. all of these zip files should be on the root of your sd. let me know how it goes.
if you get it to flash, remember to leave the phone sitting for 10-15 minutes in order for it to settle in.
also, bytefree, welcome to xda. glad to have you contributing.
As Jager said, ICBINB and others such as Black Ice are great ROMS with lots of tweaks and features. The guys that create these ROMs are awesome in their intellect and programming abilities. Mrchovee, once you get the hang of the steps required to flash a ROM it becomes second nature, just keep at it and don't let a gimped flash bring ya down man. As I said before, these little phones are hard to brick.
Hope someone has some info.
I have recently tried to recover my phone via Odin flash. I'm flashing the GummyCharged 1.9 FE odin file. I've done this SEVERAL times w/ out any problems.
My problem now is that when the Odin flash is complete it shows "Pass" and when I reboot my phone it boots with an old version of CWM (4.0.0.1). Not only that but when I try to "reboot phone" it boot loops back to CWM and will not load ANY for of an OS. I've tried multiple Odin files with no luck. Same thing over and over.
Anyone have any suggestions? I'm used to having to recover my phone from a bricked state... but never had an issue where I push a file to the phone and it will not boot after. Tried wiping data/cache after Odin as well... Still nothing.
I would try going back to stock using Imnuts' stock ROM and PIT file which can be found here: http://forum.xda-developers.com/showthread.php?t=1111486
That has always fixed any and all issues I've been having with the phone after messing something up.
EDIT: Here is the stock EE4 ROM http://forum.xda-developers.com/showthread.php?t=1172182
hazard209 said:
I would try going back to stock using Imnuts' stock ROM and PIT file which can be found here: http://forum.xda-developers.com/showthread.php?t=1111486
That has always fixed any and all issues I've been having with the phone after messing something up.
EDIT: Here is the stock EE4 ROM http://forum.xda-developers.com/showthread.php?t=1172182
Click to expand...
Click to collapse
Hey man, I cant thank you ENOUGH!!!! After A LOT of trial and error (had to download the ee4 file from another link) I was able to get this beast to boot back up. I REALLY appreciate your quick response and help!
KaneD20 said:
Hey man, I cant thank you ENOUGH!!!! After A LOT of trial and error (had to download the ee4 file from another link) I was able to get this beast to boot back up. I REALLY appreciate your quick response and help!
Click to expand...
Click to collapse
No problem. Glad you got her back up and running. No one likes a $500 paperweight.
Props to hazard he's always helping people... just want to let you know
Your a good dude...
SENT FROM THE DOG POUND
hazard209 said:
No problem. Glad you got her back up and running. No one likes a $500 paperweight.
Click to expand...
Click to collapse
Yeah, no doubt. And I was able to do a restore on the Imnuts PBJ OBT kernel from 7/30... my problem started when I installed the new kernel version (from 8/8) and tried to backup/restore. Working perfectly now though!
Having same issue still getting recovery mode
I did a fix sd cardupdate for the rom clocking.
I had gumicharge rom on it
After 4 hours my battery was at 50% so I decided hey i can just load the rom on it again and no problem clean free.
It did not work. I am using odin.
It did not work so I got the pit file from this and it gave my system life and the ed1 file wont download it stalls out and failes i tried using
CI510_VZW_EE4_ALL_ONE-LTE-CP_REV03_user_CL1014954.tar.md5
or
CI510_VZW_EP1F_ALL_ONE-LTE-CP_REV3_user_CL300919_Rooted_Debloated.tar.md5
both do nothing.
My phone just sits there reboots into Manual mode and looks like my blue recovery console.
Clear cache
Upload from SD Card
and clear memory so forth.
Thats all my options.
I am now stuck with phone i cant use or update. I am at work so now i cant use the megaupload since those are blocked by our firewall.
I was able to remote to pc to get a pit file.
At this point i dont know what to do or just do insurance claim on my phone and get another one. I dont know how to fix it now.
I cant read the sd card on any computer to put stuff on it and odin is writing things to it The pit file on this fix did give me a recovery enviroment but nothing on roms are on the sd card.
roms ive tried dont load for automaticaly its just in that manual mode thing with the icon of the little android dude.
it says
Android system recover (3e)
Enter: OK key, select:Vol Up/Vol Down
Reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
bewlo it syas #manual mode* and little android guy with eclamation point next to him.
I have tried severla tiems 3 different roms
2Much2Ask4 said:
I did a fix sd cardupdate for the rom clocking.
I had gumicharge rom on it
After 4 hours my battery was at 50% so I decided hey i can just load the rom on it again and no problem clean free.
It did not work. I am using odin.
It did not work so I got the pit file from this and it gave my system life and the ed1 file wont download it stalls out and failes i tried using
CI510_VZW_EE4_ALL_ONE-LTE-CP_REV03_user_CL1014954.tar.md5
or
CI510_VZW_EP1F_ALL_ONE-LTE-CP_REV3_user_CL300919_Rooted_Debloated.tar.md5
both do nothing.
My phone just sits there reboots into Manual mode and looks like my blue recovery console.
Clear cache
Upload from SD Card
and clear memory so forth.
Thats all my options.
I am now stuck with phone i cant use or update. I am at work so now i cant use the megaupload since those are blocked by our firewall.
I was able to remote to pc to get a pit file.
At this point i dont know what to do or just do insurance claim on my phone and get another one. I dont know how to fix it now.
I cant read the sd card on any computer to put stuff on it and odin is writing things to it The pit file on this fix did give me a recovery enviroment but nothing on roms are on the sd card.
roms ive tried dont load for automaticaly its just in that manual mode thing with the icon of the little android dude.
it says
Android system recover (3e)
Enter: OK key, select:Vol Up/Vol Down
Reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
bewlo it syas #manual mode* and little android guy with eclamation point next to him.
I have tried severla tiems 3 different roms
Click to expand...
Click to collapse
Not sure if you're going into download mode properly but try this:
open ODIN
add the PIT file in the PIT section
add the EE4 OEM file in the PDA section (do not use the phone section)
leave everything else in ODIN as default except click on "re-partition"
take your battery out of the phone
hold the volume down button & plug in your USB cable (do not let go of the volume down button until you are in download mode)
ODIN should now now show a yellow com port for your phone on top left of ODIN and your phone should display "download mode"
select start
When it's complete ODIN will show in green that it passed. Unplug your phone, put the battery back in & boot
Hope this helps & good luck
vudiff said:
Not sure if you're going into download mode properly but try this:
open ODIN
add the PIT file in the PIT section
add the EE4 OEM file in the PDA section (do not use the phone section)
leave everything else in ODIN as default except click on "re-partition"
take your battery out of the phone
hold the volume down button & plug in your USB cable (do not let go of the volume down button until you are in download mode)
ODIN should now now show a yellow com port for your phone on top left of ODIN and your phone should display "download mode"
select start
When it's complete ODIN will show in green that it passed. Unplug your phone, put the battery back in & boot
Hope this helps & good luck
Click to expand...
Click to collapse
I would do this but before starting the flash in odin put the battery back in and uncheck the auto reboot box, when its done unplug from pc and remove battery, put it back in then boot up phone
blazing through on my VZ Droid Charge 4G
anoninja118 said:
I would do this but before starting the flash in odin put the battery back in and uncheck the auto reboot box, when its done unplug from pc and remove battery, put it back in then boot up phone
blazing through on my VZ Droid Charge 4G
Click to expand...
Click to collapse
don't put the battery in during flash & leave auto reboot checked. Auto reboot will not do anything as there isn't a battery installed... it'll just turn off. Unplug the phone after you flash it & put battery back in & boot
vudiff said:
Not sure if you're going into download mode properly but try this:
open ODIN
add the PIT file in the PIT section
add the EE4 OEM file in the PDA section (do not use the phone section)
leave everything else in ODIN as default except click on "re-partition"
take your battery out of the phone
hold the volume down button & plug in your USB cable (do not let go of the volume down button until you are in download mode)
ODIN should now now show a yellow com port for your phone on top left of ODIN and your phone should display "download mode"
select start
When it's complete ODIN will show in green that it passed. Unplug your phone, put the battery back in & boot
Hope this helps & good luck
Click to expand...
Click to collapse
This is pretty much what fixed it for me. DON'T GIVE UP! Trust me, I literally had to try this several times before it booted up. I know its frustrating, trust me, but if you stick with it you can fix the phone.
Each time you're able to get to recovery mode, if you're phone doesn't boot, do like five data wipes and wipe cache. Then Odin the .pit and the EE4 from the link above in the pda field (both at the same time).
Good luck! Stick with it I know you CAN fix this!
Sent from my SCH-I510 using XDA Premium App
KaneD20 said:
This is pretty much what fixed it for me. DON'T GIVE UP! Trust me, I literally had to try this several times before it booted up. I know its frustrating, trust me, but if you stick with it you can fix the phone.
Each time you're able to get to recovery mode, if you're phone doesn't boot, do like five data wipes and wipe cache. Then Odin the .pit and the EE4 from the link above in the pda field (both at the same time).
Good luck! Stick with it I know you CAN fix this!
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
No need to wipe anything... when you have "re-partition" checked it wipes everything but the sd card
vudiff said:
No need to wipe anything... when you have "re-partition" checked it wipes everything but the sd card
Click to expand...
Click to collapse
I'm sure you're right, these are just the things that I did when I finally got it working.
I got stuck myself last night and odin started to fail every attempt, even with the pit file and following numerous instructions found around the site. I actually thought my phone was bricked for good.
I installed PST lite and selected the PIT and EE4 and selected to repartition. It took longer to do but everything came back up. Then using odin I was able to flash back to the rom I had before.
This was after an hour of trying to fix it as I mentioned and Odin kept failing.
^attempting to reflash via samsung pst lite.
loaded PIT, stock EE4. checked "repartition". when I click download, it starts, but freezes at 9%. RX_TIMEOUT shows on the phone screen.
I'm trying this method b/c Odin is not working. Same thing, just hangs, sez RX_TIMEOUT. (repartition w/ PIT, stock EE4)
sushi_stalker said:
^attempting to reflash via samsung pst lite.
loaded PIT, stock EE4. checked "repartition". when I click download, it starts, but freezes at 9%. RX_TIMEOUT shows on the phone screen.
I'm trying this method b/c Odin is not working. Same thing, just hangs, sez RX_TIMEOUT. (repartition w/ PIT, stock EE4)
Click to expand...
Click to collapse
Have you tried putting the battery back in during the flash?
Sent from my Droid Charge running GummyFroyo 1.9.1
kvswim said:
Have you tried putting the battery back in during the flash?
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
Yes. tried both with and without. Just hangs. Can never fully make it through the flash.
Stuck with soft bricked phone.
Waiting for my wife to get home with her PC laptop. Hoping it really is just a platform issue (running ODIN on Mac Boot Camp)
sushi_stalker said:
Yes. tried both with and without. Just hangs. Can never fully make it through the flash.
Stuck with soft bricked phone.
Waiting for my wife to get home with her PC laptop. Hoping it really is just a platform issue (running ODIN on Mac Boot Camp)
Click to expand...
Click to collapse
What version of Odin are you using? I'm pretty sure I'm using Odin v. 1.82 or something close to that. Not too sure that it would make the difference. Just a thought.
Also, I had to Odin QUITE a few times to get it back up. I had even run the Odin w/ JUST the .pit file. Thought I read somewhere to run the .pit an UNCHECK the repartition box (I know it says it'll give you an error but I did not get one).
All in all, not too sure what exactly it was that finally got it working. But I eventually ran the .pit and ee4 (both posted in post #2 of this thread). Then when my phone booted up, it looked like the problem remained. I had to get back to work from lunch so I just put the phone in my pocket. Then out of nowhere I heard the boot animation come on.
Just make sure you read through, pretty much, all of the threads that deal w/ this stuff. There is almost always someone that has come across the same problem that you may have and almost always someone who had figured out how to fix it.
Good luck, this CAN be fixed!
Hey everyone, I tried looking around but didn't see anything else like this, most people at least have access to the download mode, unlike me. I was installing UNiPoRN and CWM kept freezing for some reason during flashing, so I used Odin to try to flash UCKD5 from http://forum.xda-developers.com/showthread.php?t=1092021 But it kept failing for some reason, and this last time when I went to put my phone into download, I get a single green pixel towards the bottom right of the screen, no download mode nothing, how ever my computer recognizes that my phone was attached. When I try to turn on the phone normally, I have a diagonal row of green dots, but nothing like the rainbow effect. Does anyone have any clue whats wrong and what I can do to fix it? Let me know if you need more information!!
Thanks thanks thanks in advance!!
USMCJ00lz said:
Hey everyone, I tried looking around but didn't see anything else like this, most people at least have access to the download mode, unlike me. I was installing UNiPoRN and CWM kept freezing for some reason during flashing, so I used Odin to try to flash UCKD5 from http://forum.xda-developers.com/showthread.php?t=1092021 But it kept failing for some reason, and this last time when I went to put my phone into download, I get a single green pixel towards the bottom right of the screen, no download mode nothing, how ever my computer recognizes that my phone was attached. When I try to turn on the phone normally, I have a diagonal row of green dots, but nothing like the rainbow effect. Does anyone have any clue whats wrong and what I can do to fix it? Let me know if you need more information!!
Thanks thanks thanks in advance!!
Click to expand...
Click to collapse
Try the one click method, if your computer recongnizes then that is good...try these links and there is a new odin, well has the updated Gingerbread.
see my signature links to ISET page: http://forum.xda-developers.com/showthread.php?t=1610374
but here are the links to look for one click:
http://forum.xda-developers.com/showthread.php?t=1524081
newer odin:
http://forum.xda-developers.com/showthread.php?p=27286083#post27286083
Yes, as mentioned from bigjoe2675 use the newer up-to-date Odin http://forum.xda-developers.com/showthread.php?t=1705260 And flash the GB Bootloaders afterwards to fix the Rainbow distortion on the boot screen.
2.) I have rainbow distortion in recovery or in the boot animation. How can I get Gingerbread bootloaders to fix this?:
If you have rainbow distortion, you still have Froyo bootloaders. You can download THIS .rar file, extract using 7zip, and flash the tar.md5 package in Odin (use the pda slot). Flashing Gingerbread bootloaders will correct rainbow distortion in recovery and in the boot animation. Only flash these if you are having issues with rainbow distortion, and only if you have had success flashing other, less dangerous items in Odin.
Click to expand...
Click to collapse
I tried the one click, and it says kernel upload failed. And as for the pixels, I know what the rainbow looks like, I had it when I first installed ICS, however this is not the same thing (at least I don't think so, it looks nothing like it)
USMCJ00lz said:
I tried the one click, and it says kernel upload failed. And as for the pixels, I know what the rainbow looks like, I had it when I first installed ICS, however this is not the same thing (at least I don't think so, it looks nothing like it)
Click to expand...
Click to collapse
Checklist...
1) try a new download, sometimes files get corrupt..
2) try new USB port..
3) have a beer
4) install or uninstall kies drivers...then try new gb odin
5) have another beer...
As far as the pixel...not sure did you do it at at time?
Make sure you flash the bootloader after you had success with the restore to correct the "pixels" which I had before a couple of times. The random pixels are the corrupted bootloaders (I think) which should be corrected by flashing the proper one (GB Bootloaders)
Sent from my SAMSUNG-SGH-I997 using XDA
I kinda had a similar problem earlier when I was trying to install legend 4 rom. My phone would flash a boot, then nada. No button combo's worked, nothing. I got the idea to pull the battery, and I achieved the same results upon power up (glimpse, freeze, no button reaction). So, I pulled my battery again, held the volume rockers and got into download mode. Once I did that, I used Odin to go back to stock GB.
USMCJ00lz said:
!!!
Click to expand...
Click to collapse
status update...you good to go...?
check or hold!?!
I got in a SK4g for my wife intent on upgrading her current phone. I own a 4g myself, and have Rooted/ROM'd it with no issues, we we thought it best to get her the same phone for ease of use/manipulation.
I got the phone in and used superoneclick to root it, then went through the process of putting CWM in place and installing GenericGinger_2.0_SK4G. The process ran smooth as glass (as expected) until it got to reboot. On reboot it hung up on the sidekick screen. After about an hour of waiting I pulled the battery and restarted the machine.
It came back up in recovery mode with the stock recovery (blue) text. Since then I haven't been able to get it to do anything but restart into that recovery screen. Odin doesn't see the phone in download mode and t839-Sidekick4G-UVKG2-One-Click does nothing. It shows it uploading, reboots the phone, and I'm back at the blue text. flashing the bootloaders with One-Click shows success on everything *except* uploading the bootloaders. If I tell it to re-install packages I get a 'cannot validate signature' response. I've tried using android commander to push CWM's recovery file to the phone and get 'permission' denied.
I've done a lot of searching on this site, trying most suggested fixes I've come across with no luck.
what can be done with this phone to get it back in operating condition?
Thanks in advance!
try installing kies odin wouldnt see my phone until i installed it
Kies installed and Odin saw the phone. excellent, thanks!
now, the next issue... lol
I used Odin to push KD1OdinSTOCK onto the phone. it's doing more than it was (going to the initial sidekick screen then dumping to recovery). Now it'll load through the sidekick and samsung splash screens, then reset and do it again. The same thing happens when I tried StockKG2ODIN. I'm using the sk4g.pit that I pulled from this site, could that have anything to do with it/is there another one around that I could try? Anybody have thoughts or ideas on what to do next? I've tried using t839-Sidekick4G-UVKG2-One-Click again, but it nuked the drivers kies put into place and dropped the phone back to what it was doing before.
okay, I did some light reading of this thread here
and followed the directions closely. I also went through sduvick's list of things to do with the following results:
Black screen, no logo.
1. Get into download mode by using VolDown+Touchpad+Power
2. flash full sk4g.tar.md5 as posted.
device will boot through the logo and splash screens, then repeat. note: if I leave the USB cable plugged in on reboot it will go to the battery screen, otherwise it just boot loops.
_________________________________
logo only
1. Download mode
2. Flash full package
device boot loops
_________________________________
Can't flash recovery/boot/sbl
1. Download mode
2. use PIT only, run with repartition checked
3. reboot/reDownload mode
4. run the full image in Odin.
PIT only returns a black screen on the device. running the full image in afterward returns to the boot loop.
_________________________________
Anything else
1. Download mode
2. Full tar.md5 flash in Odin
3. Ask if it doesn't work
okay, so I'm asking...
I'm still able to boot into recovery mode (blue text).
I've noted a bit of strange behavior when trying to boot into download mode. holding vol down + trackball + power does nothing. however, if I plug the phone in while powered down while holding down the trackball it'll boot into download mode, no power or vol down required.
If you can't flash with Odin, you may have a hardware problem.
Judging from your issue with installing Kies, you had a driver problem previously.
Seems that you are bumbling in the dark here. Once again, people need to be better prepared to Odin their devices before they start modding them.
In fact, getting Odin working should be the first thing a person should do with their phone after rooting and installing CWM.
Anyhow, try a different version of Odin. If that doesn't clear up your problem, I suspect some bad blocks in your flash memory are responsible here. It's a dorment issue that would really only be a problem when you flashed the device. If that's the case, you have a new paperweight.
Good luck.
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
I don't think the problem is that I can't flash with Odin, but that the device isn't loading the ROM that's flashed. poking around in the filestructure with android commander after a fresh load shows that the system makes it onto the phone.
Speaking of poking around with Android Commander, I've noted that the device is software rooted, but not hardware rooted. the default.class file shows ro.debuggable set at 0 where it should be 1. this is keeping me from just pushing the CWM recovery onto the system and restoring the backup I made before getting into this mess. Anybody want to help me pull/edit/flash the image to change that?
As for a driver issue, that's a good possibility given that the one-click uses a driver set, kies mini uses another, kies has a different one yet and we (as a community) started screwing with the t839's using vibrant drivers. I've got them all. thusfar the only drivers I've found that work with both flavors of Odin I have (1.61 and 1.85) would be those that came with the Kies (thanks for the tip pmp326).
On bumbling in the dark, yes, yes I am. There isn't much of an instruction manual for Odin past what's written here, and 90% of that is 'put your phone in download mode, connect Odin, plug the pit in pit and the tar in PDA make sure only auto-reboot is checked and hit start'. to be honest I haven't had to use the program previously as the stock one-click actually worked on my T839. This new device is being ... difficult.
the dormant bad blocks issue you spoke about, was this something found in new-out-the-box phones? I haven't seen a lot about that in the threads, can you point in at more info, please?
at any rate, it doesn't matter which version of Odin I use, I got the same result from both. I tried using a different cable/different USB port as well. I haven't tried using a different system (yet), but don't want to go through all the trouble of setting up everything on another box. Win7 is finicky enough, trying to get everything operating on Server2k3 would most likely end up a challenge. *lol*
I'll try repartitioning with KG1 when I get back to the house.
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
I've gotta pop the debug lock in the default.class to be able to push anything into the system folders with Android Commander. I've found a nice walk-thru to do this, it just requires a little knowledge of c++ and some patience. with any luck I should be able to pull default.class out of its img, edit it and flash that back (most likely with Heimdall since it can do itemized flashing).
pmp326 said:
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
Click to expand...
Click to collapse
tried it, no joy.
pmp326 said:
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
Click to expand...
Click to collapse
tried this, brings me back to the boot loop.
orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
currently I'm running into issues with getting ADB to push onto the system as the system is claiming it isn't rooted. Is there a way I haven't read about or found to root the phone without getting into the actual O/S (i.e. from the blue recovery screen)?
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
rpmccormick said:
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
Click to expand...
Click to collapse
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
I like turtles.
Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
Even the end... I mean, your not trying to odin a "tar.md5" are you?
rpmccormick said:
Even the end... I mean, your not trying to odin a "tar.md5" are you?
Click to expand...
Click to collapse
No....
Sorry man. I've never had to ODIN (this phone). I say check the md5 to make sure you downloaded a good copy, and maybe try a different USB cable. The ADB method seems nutz... if it doesn't boot after a successful ODIN, the phone is probably a paperweight.
Good luck!
Samsung Galaxy s 4g T959V-Gingerbread. Rooted it with SuperOneClick... Didnt have CWM. when I tried to install Black Ice and ICNINB. Tried doing with Rom Manager. Then read that doesn't work with this phone. Was able to flash AltonX KJ6 kernal through SGS kernel flasher in order or get CWM on the phone. That worked. But when I went to flash the zip files for the roms again. They still didn't work. I thought I was following the directions. Get into download mode> create a backup> wipe data> make sure the mounts were right> then flash the zip file. Well the first time I did i,t it kinda went through. Although I didn't have RED CWM or Linda. Wanted to get Voodoo and LagFix. So I decided to flash again. When it came time to reboot.. it got stuck in a loop between two different Samsung screens.One with a big swoopy S the other just the normalt-mobile samsung screen before it boots up. Going from one to the other never really rebooting. So again I decided to get into download mode again and then flash a recovery backup file. And NOW it just hangs on the Samsung T-Moblie screen. I've tried battery pulls also tried using a JIG. Screen pops up but just freezes there.
Any suggestions??
pistol865 said:
Samsung Galaxy s 4g T959V-Gingerbread. Rooted it with SuperOneClick... Didnt have CWM. when I tried to install Black Ice and ICNINB. Tried doing with Rom Manager. Then read that doesn't work with this phone. Was able to flash AltonX KJ6 kernal through SGS kernel flasher in order or get CWM on the phone. That worked. But when I went to flash the zip files for the roms again. They still didn't work. I thought I was following the directions. Get into download mode> create a backup> wipe data> make sure the mounts were right> then flash the zip file. Well the first time I did i,t it kinda went through. Although I didn't have RED CWM or Linda. Wanted to get Voodoo and LagFix. So I decided to flash again. When it came time to reboot.. it got stuck in a loop between two different Samsung screens.One with a big swoopy S the other just the normalt-mobile samsung screen before it boots up. Going from one to the other never really rebooting. So again I decided to get into download mode again and then flash a recovery backup file. And NOW it just hangs on the Samsung T-Moblie screen. I've tried battery pulls also tried using a JIG. Screen pops up but just freezes there.
Any suggestions??
Click to expand...
Click to collapse
you don't want voodoo lagfix. unreliable, imho.
Try eollie's stock + root in the second post my oneclick thread. It's a stock rom and blastoff v2.5.
Run the oneclick the first time to flash just the kernel and rom.
Click flash bootloaders.
reboot phone to download mode again
flash again, this time with bootloaders.
After that, you should be golden.
Don't forget to read the directions in the OP.
bhundven said:
you don't want voodoo lagfix. unreliable, imho.
Try eollie's stock + root in the second post my oneclick thread. It's a stock rom and blastoff v2.5.
Run the oneclick the first time to flash just the kernel and rom.
Click flash bootloaders.
reboot phone to download mode again
flash again, this time with bootloaders.
After that, you should be golden.
Don't forget to read the directions in the OP.
Click to expand...
Click to collapse
Thank you so much for getting back to me. A couple of questions if I may?
1) if I'm able to get the samsung screen, does that mean I'm able to get into Download mode? It just seems to hang on that samsung T-Mobile screen.
2) The link to dropbox that I'm supposed too click on, seems to be broken... Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel)- https://dl.dropboxusercontent.com/u/10373328/Stock KJ6 + root-One-Click.jar -
Here's what comes up: Error (404)
We can't find the page you're looking for. Check out our Help Center and forums for help, or head back to home.
3) Assuming that I'm able to get to download mode, I just want to check to make sure that I'm reading your directions correctly.
- when I run OneClick the 1st time, it will automatically apply just the kernel and rom.
- Then I'm supposed to reboot? Or flash the bootloaders?
- After that I'm supposed to reboot phone to download mode again.
- Flash Bootloaders again??
I'm sure I'm messing up the directions or rather misreading them.
Sorry for that. Kinda NOOB when it comes to HEIDENALL
pistol865 said:
Thank you so much for getting back to me. A couple of questions if I may?
Click to expand...
Click to collapse
Well, seeming it is the Q&A forum
pistol865 said:
1) if I'm able to get the samsung screen, does that mean I'm able to get into Download mode? It just seems to hang on that samsung T-Mobile screen.
Click to expand...
Click to collapse
Yes. Sometimes even if the phone seems to turn on and go to a black screen, you might still be able to get to download mode.
Seriously, this phone is like a tank... unless you flash gt-i9000 or vibrant roms. Then you will brick your phone.
pistol865 said:
2) The link to dropbox that I'm supposed too click on, seems to be broken... Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel)- https://dl.dropboxusercontent.com/u/10373328/Stock KJ6 + root-One-Click.jar -
Here's what comes up: Error (404)
We can't find the page you're looking for. Check out our Help Center and forums for help, or head back to home.
Click to expand...
Click to collapse
Dang, I'm uploading a new link to this. Give it 20 minutes. and go back and try the link again.
pistol865 said:
3) Assuming that I'm able to get to download mode, I just want to check to make sure that I'm reading your directions correctly.
- when I run OneClick the 1st time, it will automatically apply just the kernel and rom.
- Then I'm supposed to reboot? Or flash the bootloaders?
- After that I'm supposed to reboot phone to download mode again.
- Flash Bootloaders again??
I'm sure I'm messing up the directions or rather misreading them.
Sorry for that. Kinda NOOB when it comes to HEIDENALL
Click to expand...
Click to collapse
Put your phone into download mode, either by holding vol+ and vol- and plugging in the usb from your computer (keep holding vol+ and vol- till you see download mode) or use a jig.
Once your in download mode. Flash the first time. Yes, it will only flash the kernel and rom. The phone will automatically reboot after the flash.
Wait a little bit after the phone reboots, you'll see a little local update happen and reboot the phone again. Then pull the battery and put the phone back into download mode.
Then check the "flash bootloaders" checkbox. flash the oneclick again this time with bootloaders.
After this, you can go anywhere from this rom, except back to froyo. I'm still working on a simple oneclick method for going back to froyo.
bhundven said:
Well, seeming it is the Q&A forum
Yes. Sometimes even if the phone seems to turn on and go to a black screen, you might still be able to get to download mode.
Seriously, this phone is like a tank... unless you flash gt-i9000 or vibrant roms. Then you will brick your phone.
Dang, I'm uploading a new link to this. Give it 20 minutes. and go back and try the link again.
Put your phone into download mode, either by holding vol+ and vol- and plugging in the usb from your computer (keep holding vol+ and vol- till you see download mode) or use a jig.
Once your in download mode. Flash the first time. Yes, it will only flash the kernel and rom. The phone will automatically reboot after the flash.
Wait a little bit after the phone reboots, you'll see a little local update happen and reboot the phone again. Then pull the battery and put the phone back into download mode.
Then check the "flash bootloaders" checkbox. flash the oneclick again this time with bootloaders.
After this, you can go anywhere from this rom, except back to froyo. I'm still working on a simple oneclick method for going back to froyo.
Click to expand...
Click to collapse
Once again, many thanks for your time and patience
.Just wondering if you fixed that link yet?
I keep clicking on: Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel) , it takes me to this page: https://dl.dropboxusercontent.com/u/10373328/Stock KJ6 + root-One-Click.jar, but I'm still getting the message: Error (404)
We can't find the page you're looking for. Check out our Help Center and forums for help, or head back to home.
That link is Underneath the link: eollie: AntonX's BwaT + Stock Rom... on the page: http://forum.xda-developers.com/showthread.php?t=1358498 .
Again, pardon my detailed reply, but I just want to be sure that I'm clicking on the correct link.
pistol865 said:
Once again, many thanks for your time and patience
.Just wondering if you fixed that link yet?
I keep clicking on: Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel) , it takes me to this page: https://dl.dropboxusercontent.com/u/10373328/Stock KJ6 + root-One-Click.jar, but I'm still getting the message: Error (404)
We can't find the page you're looking for. Check out our Help Center and forums for help, or head back to home.
That link is Underneath the link: eollie: AntonX's BwaT + Stock Rom... on the page: http://forum.xda-developers.com/showthread.php?t=1358498 .
Again, pardon my detailed reply, but I just want to be sure that I'm clicking on the correct link.
Click to expand...
Click to collapse
Yea man. I updated the second post in the onclick thread. Here is the timestamp from the post: "24th July 2013 12:39 PM"
You need to clear the cache on your browser and reload that page. The link is here.
bhundven said:
Yea man. I updated the second post in the onclick thread. Here is the timestamp from the post: "24th July 2013 12:39 PM"
You need to clear the cache on your browser and reload that page. The link is here.
Click to expand...
Click to collapse
Ran into a new problem now...
It's me again... Sorry if I'm being a pain..
So I downloaded the link.. I have it on my desktop...I put my phone into download mode..(Yellow Triangle> Do not unplug).. I clicked on your OneClick... it loads but then tells me to connect my device... It keeps telling me I'm disconnected..
When I plug my phone into my compt via USB.. it now tells me that my device is unrecognized.
Now what did I do wrong?
I was hoping I was close to a resolution... another roadblock.
Can I fix it?
Once again, thank you for any and all the help and advice you have given me.
There is s thread called fresh out of the box now what. It will help you immensely. Sounds like you need to uninstall all samsung and android drivers and reinstall them. In that thread there is a application for your computer called usbview that can remove them (I probably misspelled that apps name). The thread is by lumin30.
limeaide said:
There is s thread called fresh out of the box now what. It will help you immensely. Sounds like you need to uninstall all samsung and android drivers and reinstall them. In that thread there is a application for your computer called usbview that can remove them (I probably misspelled that apps name). The thread is by lumin30.
Click to expand...
Click to collapse
I already installed usbDview.. ran as admisistrator... removed anything that said samsung or android.. plugged in my samsung phone and Still is not recognized. Also downloaded Zadig.. to install the drivers to the phone.. but it doesn't recognize the phone.
Anything else that I'm missing? Can I download something online so that when i plug in via USB it will recognize my phone?
You have tried different usb ports too? Other than that maybe a different computer. I know bhundven says dont use front usb ports too.
limeaide said:
You have tried different usb ports too? Other than that maybe a different computer. I know bhundven says dont use front usb ports too.
Click to expand...
Click to collapse
Tried different usb ports as well as a different computer.. When I hoked up to a different computer, at first it said it was installing the drivers.. then it stopped and said USB device Unrecognized.
Is it a matter of drivers? Can I get them offline? and then plug in my phone?
limeaide said:
You have tried different usb ports too? Other than that maybe a different computer. I know bhundven says dont use front usb ports too.
Click to expand...
Click to collapse
Computer pop up says: usb device has malfunctioned and windows does not recognize it.
limeaide said:
You have tried different usb ports too? Other than that maybe a different computer. I know bhundven says dont use front usb ports too.
Click to expand...
Click to collapse
I just went to the samsung website and downloaded the drivers from there.. Still having the same problem... usb device has malfunctioned and windows does not recognize it.
IIRC when you plug the phone in you need to stop it from installing the samsung drivers. Then use zadig to install them like illustrated in lumin30s guide.
Be sure to use a rear usb port if on a desktop. Dont change ports if things start to work. If you have to use a different port I suggest using usbdeview to remove drivers each time. It seems like overkill but it might work.
limeaide said:
IIRC when you plug the phone in you need to stop it from installing the samsung drivers. Then use zadig to install them like illustrated in lumin30s guide.
Be sure to use a rear usb port if on a desktop. Dont change ports if things start to work. If you have to use a different port I suggest using usbdeview to remove drivers each time. It seems like overkill but it might work.
Click to expand...
Click to collapse
ALMOST THERE.. I think..lol
I think I successfully ran the program.. phone turns on now.. Yayyy...
New Problem:
The screen now says:NO SIM CARD IN PHONE
AFTER YOU INSERT THE CARD, PLEASE REBOOT
EMERGENCY CALLS CAN BE USED
The SIM card is already installed... the phone is not recognizing it now.
What now??
limeaide said:
IIRC when you plug the phone in you need to stop it from installing the samsung drivers. Then use zadig to install them like illustrated in lumin30s guide.
Be sure to use a rear usb port if on a desktop. Dont change ports if things start to work. If you have to use a different port I suggest using usbdeview to remove drivers each time. It seems like overkill but it might work.
Click to expand...
Click to collapse
One more thing, I installed Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel)... That should mean the phone is rooted.. correct? although I don't see SUPERUSER in my apps list.. Also does this have CWM installed? Can I flash a custom rom moving forward?? If so which one do you consider the best? I originally was having trouble because I was running into low internal memory and couldn't download many apps. That's why I wanted to flash BLACK ICE originally.. I thought that would fix my problem..
This phone suffers from low internal memory. However you can move almost all apps to your sdcard from within the rom. If the things that do not work on the JB roms are ok with you I hear good things about those.
As for the sim card..Im not sure. The one click you used doesnt have SU included because it is a stock rom with custom rooted kernel. You would have to install it from the Play store. But I reccomend flashing a different rom anyway. Again the JB roms seem to be pretty awesome so that is a option.
limeaide said:
This phone suffers from low internal memory. However you can move almost all apps to your sdcard from within the rom. If the things that do not work on the JB roms are ok with you I hear good things about those.
As for the sim card..Im not sure. The one click you used doesnt have SU included because it is a stock rom with custom rooted kernel. You would have to install it from the Play store. But I reccomend flashing a different rom anyway. Again the JB roms seem to be pretty awesome so that is a option.
Click to expand...
Click to collapse
Did I do something wrong because I didn't pull the sim card when I flashed: Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel). Also does Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel) come with CWM Red?
pistol865 said:
Did I do something wrong because I didn't pull the sim card when I flashed: Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel). Also does Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel) come with CWM Red?
Click to expand...
Click to collapse
reboot to cwm (recovery). wipe cache partition. advanced -> wipe dalvik cache. advanced -> fix permissions. reboot phone. Let it sit for a few minutes before doing anything (I'd say 10-15 minutes).
Oh weird. did that oneclick come with blastoff v2 and not 2.5?
Hmm, then do this. download blastoff v2.5, put that on your sdcard and install it from red cwm.
Then do what I said above. You should be back to blue after rebooting to recovery after flashing that kernel.
EDIT: if you really want red cwm (voodoo lagfix), I really don't know why you'd want that, but checkout my older subtly modified stock kernel.
bhundven said:
reboot to cwm (recovery). wipe cache partition. advanced -> wipe dalvik cache. advanced -> fix permissions. reboot phone. Let it sit for a few minutes before doing anything (I'd say 10-15 minutes).
Oh weird. did that oneclick come with blastoff v2 and not 2.5?
Hmm, then do this. download blastoff v2.5, put that on your sdcard and install it from red cwm.
Then do what I said above. You should be back to blue after rebooting to recovery after flashing that kernel.
EDIT: if you really want red cwm (voodoo lagfix), I really don't know why you'd want that, but checkout my older subtly modified stock kernel.
Click to expand...
Click to collapse
No..no.. I'll definitely take your word for it.. I'll stick with the blue. I just thought that with the lagfix, it would fix my problem with internal memory.
My problem now is my SIM card.. The phone reboots and I get : NO SIM CARD IN PHONE
AFTER YOU INSERT THE CARD, PLEASE REBOOT
EMERGENCY CALLS CAN BE USED]
I did as you said:
reboot to cwm (recovery). wipe cache partition. advanced -> wipe dalvik cache. advanced -> fix permissions. reboot phone. Let it sit for a few minutes before doing anything (I'd say 10-15 minutes).
Should I still install: download blastoff v2.5?
Thank you again for ALL your help.. You guys saved my phone..