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.
Related
Well I was caught my the new MIUI ROM i saw this morning and decided to switch from Bionix. I have flashed many phones and farmiliar with the process. I left my phone alone while the install occured. I watched it wipe data and cache. Now when it powers up, the samsung logo appears for 2 seconds and a quick I9000 logo flashes for like .25 of a second. The 3 button method to force it into recovery. I dont have a usable copy of windows to boot camp from my mac so ODIN is currently not an option.
I can get the phone into download mode so i know its not a lost sailor, i just need a mac solution without booting windows. I really dont want a refurb replacement from warranty either
You want heimdall.
Yup. heimdall rocks
samsung screen of death...
LinuxBozo said:
You want heimdall.
Click to expand...
Click to collapse
SO here goes...
first off i am rooted, have all appropriate drivers, etc, have used dab to root.
I am a total newb, and was experiencing issues flashing a new ROM. when trying to install the zip through cwm the phone said "signature verification failed" or something to that extent. so being the deductive thinker that I am, I formatted everything: boot, system, sd, etc. After doing this, I realized that I totally wiped out all the files on the internal sd.
so i downloaded the heimdall one click- it connects but fails regardless of whether i flash boot loader.
i can access blue 3e recovery and download mode.
now. i want to know if it is possible to push or even install a ROM through adb. I've been playing around with it all day and have gotten nowhere.
i thought maybe i could load up a rom to an external sd but obviously you can't mount an extsd in cwm.
am i screwed?
ill gladly donate through paypal if someone can help me get my baby up and running again. i do not want to be using my nokia from middle school anymore!!
thank you in advance for ANY help you can give me.
Rob
Ok so im not a newb to flashing ROMs or kernels and such. Both my roomate have the charge with imoseyon's kernel and DarkChargedTQ ROM. While he was on a business trip his phone reset but wouldnt boot, it would just loop at the samsung screen. So he got home, livid of course becuase of his broken phone so I tried to fix it.
I flashed back EP1W using ODIN which completes properly. THen when it reboots the stock recovery comes up saying that it cant mount /cache. THen if you try to factory reset it says that it cant mount /data. When I reboot I am still in the samsung boot loop.
Please Help, I was the one who flashed his phone and now its broken so im kinda freaking out!
I had a slightly different issue, kept getting the recovery halt when trying to go back to stock, all using the directions here. Nothing worked.
I then discovered this process, and it got my phone booting and stock.
http://www.mydroidworld.com/forums/...harge-full-factory-tar-flashing-software.html
There might be an easier fix for you, but just sharing something that helped me out.
Thanks for the suggestion but thats a no go. Here is a little more detail.
After flashing the recovery fails to load the /cache. So when I try to fatory reset, I get this:
E:failed to mount /data (Invalid Argument)
E:install_application_for_customers: Can't mount /data
your storage not prepared yet, pl,ease use UI menu for format and reboot actions
Anyone ever seen this and can you help me?
Have you tried this?http://forum.xda-developers.com/showthread.php?t=1111486
This was the only way I was able to get out of a bootloop condition the very first time I flashed this phone:
http://www.mydroidworld.com/forums/...harge-ee4-full-factory-odin-return-stock.html
You need to download and install SamsungPST
Download the charge.pit file
Download the CI510_VZW_EE4_ALL_ONE-LTE-CP_REV03_user_CL1014954.tar.md5
Next, you pull the battery from your phone, connect the USB cable to your phone and computer. Then, press the volume down button to enter "download" mode. AFTER you have entered download mode you *MUST* put the battery back into the phone. Do not skip this.
So, at this point you should have your phone connected to your computer, in download mode, ready to flash WITH the battery in the phone to provide the extra power it needs during the flash process.
Next, You run the SamsungPST program, load the PIT file in the PIT section, load the .md5 file into the software section below the PIT *AND* you must click the "Repartition" *AND* the "Update Boot" checkbox before you start flashing.
Your phone will reboot after the flash process is complete and you will see some messages on the screen and it will reboot itself again before finally coming up.
BE PATIENT. This process takes a while. It takes more than six minutes to flash the phone AND another ~5 minutes before it boots up on its own. (possibly longer.)
Hopefully this will recover you. The "Repartition" option is very important. Flashing this same ROM with Odin did not work for me when I had to recover my phone. There is something about the SamsungPST program that is somehow more thorough or works better for this type of recovery.
I wrote this down from memory, so the wording might be slightly off, but you should be able to get it.
quarky42 said:
This was the only way I was able to get out of a bootloop condition the very first time I flashed this phone:
http://www.mydroidworld.com/forums/...harge-ee4-full-factory-odin-return-stock.html
You need to download and install SamsungPST
Download the charge.pit file
Download the CI510_VZW_EE4_ALL_ONE-LTE-CP_REV03_user_CL1014954.tar.md5
Next, you pull the battery from your phone, connect the USB cable to your phone and computer. Then, press the volume down button to enter "download" mode. AFTER you have entered download mode you *MUST* put the battery back into the phone. Do not skip this.
So, at this point you should have your phone connected to your computer, in download mode, ready to flash WITH the battery in the phone to provide the extra power it needs during the flash process.
Next, You run the SamsungPST program, load the PIT file in the PIT section, load the .md5 file into the software section below the PIT *AND* you must click the "Repartition" *AND* the "Update Boot" checkbox before you start flashing.
Your phone will reboot after the flash process is complete and you will see some messages on the screen and it will reboot itself again before finally coming up.
BE PATIENT. This process takes a while. It takes more than six minutes to flash the phone AND another ~5 minutes before it boots up on its own. (possibly longer.)
Hopefully this will recover you. The "Repartition" option is very important. Flashing this same ROM with Odin did not work for me when I had to recover my phone. There is something about the SamsungPST program that is somehow more thorough or works better for this type of recovery.
I wrote this down from memory, so the wording might be slightly off, but you should be able to get it.
Click to expand...
Click to collapse
OK this sounds like it might work as its the only solution I have seen that uses the repartion. I have never delt with this and I may be really stupid right now but where do I get teh charge .pit file?
EDIT: I found a link for the charge.pit in the imnuts thread that was posted a few posts back. Does this file not change with different OS builds?
Have you tried the fix my phone thread in development? ?
Sent from my SCH-I510 using xda premium
I tried the fix my phone thread and it did not work. I have tried flashing just EP1W and flashing it with the .pit in both odin and the SamsungPST and I get teh same errors every time about not being able to mount anything. It seems like I dont have any partitions but I though that using the .pit and checking re=partition should fix the problem???
Ugh my roomate is gonna kill me, anyone have any other suggestions?
MasterRy88 said:
I tried the fix my phone thread and it did not work. I have tried flashing just EP1W and flashing it with the .pit in both odin and the SamsungPST and I get teh same errors every time about not being able to mount anything. It seems like I dont have any partitions but I though that using the .pit and checking re=partition should fix the problem???
Ugh my roomate is gonna kill me, anyone have any other suggestions?
Click to expand...
Click to collapse
PIT isn't supposed to be used with GB roms.. go back to EE4 with the PIT file then boot up to make sure it works right, then Odin the GB rom of your choice by itself and you shouldn't have problems
blazing through on my 4G Droid Charge
MasterRy88 said:
EDIT: I found a link for the charge.pit in the imnuts thread that was posted a few posts back. Does this file not change with different OS builds?
Click to expand...
Click to collapse
Using the pit file will take you back to stock EE4. Since there is no official release after EE4 the file wont change. Even if we do get upped to an official OTA of GB you could still use this file to go back to EE4 and then you would get prompted to upgrade to GB.
Sent from my SCH-I510 using XDA App
So basically you are stuck at the Sam recovery screen with some coded right
Sent from my SCH-I510 using xda premium
bfitzpatrickd2d said:
So basically you are stuck at the Sam recovery screen with some coded right
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Correct, Per the suggestions Im going to flash back to EE4 but I just tried and it said the checksum was invalid so im trying to redownload a difffernt one
EDIT: UGH anyone know why the md5 keeps failing or what normall causes that?
No matter what I choose (EE4, ED1, ED2) the md5 fails. Is it safe to just remove the .md5 from the end or is that risky?
Take it to Verizon they will send you out a refurbished device
Sent from my SCH-I510 using xda premium
Something similar happened to me and I took it in and they sent out a new device I think someone told me it has something to do with /system
Sent from my SCH-I510 using xda premium
Ok didnt really follow everything so just gonna throw some stuff out there. So you are stuck at recovery so you can flash a .zip file? I found ee4 as a .zip file so you could try and do that but that doesnt help if you need to re partition. hmm. Instead of ee4 you could always try a download of ed1 or ed2. Or flash a .tar instead of a .md5. Im a noob also so just trying to help. Since you can odin files can you access your sd card? Can you odin clockwork and then try and load a file from there?
He's stuck system Samsung recovery can't flash from there but yeah flash cmw then flash a rom with kernal I think that should fix it cause when u flash w o kernal Samsung stock over writes cwm if I am not mistaking
Sent from my SCH-I510 using xda premium
Found something else but it was for another phone. Can you take your sd card out. Use and adapter to put in your computer, format it then put .zip file on there and see if it see's it. Ok well probably making things worse so as someone said take it to verizon and get replacement.
---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------
So something similar to this might work?
1. Download Odin, cwm_froyo-odin.zip
2. Extract cwm_froyo-odin.zip, place update.zip on root of SD card
3. Power phone down, remove battery
4. Open Odin, hold volume down and plug in USB to enter download mode
5. Select PDA and place cwm_froyo.tar and flash
6. Upon finish, replace battery, hold both volume buttons down and power on until you enter stock recovery (blue)
7. Apply:update.zip to enter red recovery
honestly thank you everyone for all your suggestions.
Here is where im at now. I was able to finally get an ED1 to flash with the pit file. Phone went through the same process of flashing, then went to samsung recovery and said it couldnt mount things, but it wasnt the same. It was like /dev/... and things of that nature. Factory reset, same thing. NOw when I boot I get bootlooped at the eye, which is better than what I was getting.
I didnt even think about flashing CWM to it and then flashing a rom/kernel. I might try that after I go through this. BUt as it is now the phone shouldnt show any signs of tampering so I may take it to verizon. Ill let everynoe know and THANKS AGAIN I really appreciate everyones help
I have clockwork as a .md5 file . Flash that from odin and then recover from there.
No problem; been in your boat before If we helped hit the thanks button ;-)
Sent from my SCH-I510 using xda premium
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.
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!
I am new here and searched for a similar problem but can't seem to find one just like mine. This is my first time to root this phone but have been successful in the past with others. I have a Galaxy Blaze I just bought and attempted to root with blaze.pit and blaze-root-kernel.tar in pit and PDA sections of ODIN respectively. It appeared all went well with a PASS from Odin reporting All threads completed. (Successful 1/faliled 0).
The phone auto rebooted while connected to the PC but froze on the blue "loading" bar (that's what I call it) and is frozen on the battery charging indicator screen which does increment when plugged into AC. If I push the power button it just buzzes. I never got so far as to load a ROM which is what leads me to think my question may be new but stupid me if digging through here didn't turn up what I'm looking for. This is my only phone and I'm SOL without it. I'm afraid I might have gotten the files from an old source (suspicion) and would appreciate any guidance getting me back where I was or rooted so I may continue.
I can get into load mode so not all is lost, except for me. Thanks for any kind person that would take a moment to bail me out.
Update
mikesmccurdy said:
I am new here and searched for a similar problem but can't seem to find one just like mine. This is my first time to root this phone but have been successful in the past with others. I have a Galaxy Blaze I just bought and attempted to root with blaze.pit and blaze-root-kernel.tar in pit and PDA sections of ODIN respectively. It appeared all went well with a PASS from Odin reporting All threads completed. (Successful 1/faliled 0).
The phone auto rebooted while connected to the PC but froze on the blue "loading" bar (that's what I call it) and is frozen on the battery charging indicator screen which does increment when plugged into AC. If I push the power button it just buzzes. I never got so far as to load a ROM which is what leads me to think my question may be new but stupid me if digging through here didn't turn up what I'm looking for. This is my only phone and I'm SOL without it. I'm afraid I might have gotten the files from an old source (suspicion) and would appreciate any guidance getting me back where I was or rooted so I may continue.
I can get into load mode so not all is lost, except for me. Thanks for any kind person that would take a moment to bail me out.
Click to expand...
Click to collapse
I shoult mention that I did try to follow http://forum.xda-developers.com/showthread.php?t=1591601 but was not able to get the TAR file to download.
What version(ICS or GB) were you on when you tried to root? There are root methods that are different for both ICS and GB... Since you can boot into download mode, try getting Clockwordmod on your blaze via Odin. Then from there mount your device(via CWM) and transfer a ROM you want to try out. Don't forget Gapps... then wipe data/cache/dalvik and flash them both..
im_awesome_right? said:
What version(ICS or GB) were you on when you tried to root? There are root methods that are different for both ICS and GB... Since you can boot into download mode, try getting Clockwordmod on your blaze via Odin. Then from there mount your device(via CWM) and transfer a ROM you want to try out. Don't forget Gapps... then wipe data/cache/dalvik and flash them both..
Click to expand...
Click to collapse
^^^ he's right... I did the same thing when I got my Blaze. I forgot to uncheck Repartition. You have to UN-check it after you select the tar and pit. it auto checks repartition once those are selected.
go to the CWM post http://forum.xda-developers.com/showthread.php?t=1591622 and flash CWM via Odin. FOLLOW THE DIRECTIONS CAREFULLY Then if you're able to get into recovery, download whatever Rom you want to your pc, and inside recovery go into Mounts and Storage->Mount USB Storage and plug your phone into the computer. you should then be able to copy the downloaded Rom to your phone (make sure you know whether its your internal or external SD card. Then hit +++Go Back+++ twice and choose Install Zip from SD Card. The pick one: Choose zip from sdcard or choose zip from internal sd card. then navigate to the rom's zip, install, wipe data/factory reset, wipe cache, wipe dalvik, reboot phone and you ***should*** be good to go.
Still trying and eternally grateful
jparnell8839 said:
^^^ he's right... I did the same thing when I got my Blaze. I forgot to uncheck Repartition. You have to UN-check it after you select the tar and pit. it auto checks repartition once those are selected.
go to the CWM post http://forum.xda-developers.com/showthread.php?t=1591622 and flash CWM via Odin. FOLLOW THE DIRECTIONS CAREFULLY Then if you're able to get into recovery, download whatever Rom you want to your pc, and inside recovery go into Mounts and Storage->Mount USB Storage and plug your phone into the computer. you should then be able to copy the downloaded Rom to your phone (make sure you know whether its your internal or external SD card. Then hit +++Go Back+++ twice and choose Install Zip from SD Card. The pick one: Choose zip from sdcard or choose zip from internal sd card. then navigate to the rom's zip, install, wipe data/factory reset, wipe cache, wipe dalvik, reboot phone and you ***should*** be good to go.
Click to expand...
Click to collapse
Thank you so much for the input. I must be totally stupid because Odin loaded Clockwork mod without a hitch but it still freezes at the end of the blue bar and will no further. Odin reoorts pass When I boot do downloading... it only gives me the product name sgh-t789 Custom Binary Download Yes: (4counts) and current binary Custom. There is always a chance that I forgot to uncheck ro-partiton but I was pretty careful. All this to get rod of pages of bloatware...rrgh. Thanks so much to thos who have given me input so far. Unfortunatly I am not sure what I ws running in the first place but I imagine it was not ICS. I can't afford a new phone and know I must get past this!!! Thanks a million guys. I will try to find a rom to flash and see but am not even sure how to get into Cloclwork on ths silly thing yet.
To get into recovery you must do the volume buttons/power button hold. It's explained in the rooting thread. It's not hard, just follow the instructions. You shouldn't have to remove the battery, just turn off your phone, then hold all 3 buttons, release the power button after about 10 seconds but keep holding volume buttons until recovery comes up in your phone.
Sent from NOS_INJECTED ParanoidAndroid Blaze
Still trying and eternally grateful
njstein said:
To get into recovery you must do the volume buttons/power button hold. It's explained in the rooting thread. It's not hard, just follow the instructions. You shouldn't have to remove the battery, just turn off your phone, then hold all 3 buttons, release the power button after about 10 seconds but keep holding volume buttons until recovery comes up in your phone.
Sent from NOS_INJECTED ParanoidAndroid Blaze
Click to expand...
Click to collapse
Thank you. I am able to get into recovery mode without an issue and odin reports that Clockwork Mod Passed but I stil can't get past the blue bar locking up when it reaches the end. I must be missing something stupid as I cand even get Odin to recoginze the stock download so I can try to start over. rrgh. I know I'm missing something stupid but it seems to me that when I boot the phone into recovery I should see a clockworkmod screen giving me boot oprions but not sure what I should be seeing am flying a bit blind. Would appreciate good recommendation of a rom to try and download and where I might find it. I do notice that the rocovery mode screen increments the custom binary dowload indicator everytime I try something.
Im thinking you might have forgotten to repartition the phone. Make sure its selected so you can have a clean partition and redo the steps to root it and see if that works.
The Barron said:
Im thinking you might have forgotten to repartition the phone. Make sure its selected so you can have a clean partition and redo the steps to root it and see if that works.
Click to expand...
Click to collapse
As said above. The mistake was that he clicked repartition.
Sent from my Provisioned Galaxy S Blaze
strange, i always thought you had to partition, at least at some point.
Anywho, if you can get into recovery (and since you said odin loaded cwm) couldn't you just put a rom onto a SD card, pop it in, and just install it with cwm?
The Barron said:
strange, i always thought you had to partition, at least at some point.
Anywho, if you can get into recovery couldn't you just put a rom onto a SD card, pop it in, and just install it with cwm?
Click to expand...
Click to collapse
Also said above...
Bootloader is bad? Doubt it, but only thing i can think of right now.
Still grateful......
The Barron said:
strange, i always thought you had to partition, at least at some point.
Anywho, if you can get into recovery (and since you said odin loaded cwm) couldn't you just put a rom onto a SD card, pop it in, and just install it with cwm?
Click to expand...
Click to collapse
Oddly CWM reports as having loaded in Odin but I cant access it to load a mod unless there is a trick to getting to CWM I haven't figured out yet. I'm also a bit confused that Odin only recognizes TAR files when the mods I downloaded ie liquid are in zip format and not recognized by Odin. sorry for asking stupid questions but I sincerely appreciate the time you all take to respond. I am detrermined to fix this one. I was pretty careful to uncheck repartition but there is always the chance I missed it once.
mikesmccurdy said:
Oddly CWM reports as having loaded in Odin but I cant access it to load a mod unless there is a trick to getting to CWM I haven't figured out yet. I'm also a bit confused that Odin only recognizes TAR files when the mods I downloaded ie liquid are in zip format and not recognized by Odin. sorry for asking stupid questions but I sincerely appreciate the time you all take to respond. I am detrermined to fix this one. I was pretty careful to uncheck repartition but there is always the chance I missed it once.
Click to expand...
Click to collapse
Zips are flashed in CWM.. Not in Odin..
Sent from my Provisioned Galaxy S Blaze
mikesmccurdy said:
Oddly CWM reports as having loaded in Odin but I cant access it to load a mod unless there is a trick to getting to CWM I haven't figured out yet. I'm also a bit confused that Odin only recognizes TAR files when the mods I downloaded ie liquid are in zip format and not recognized by Odin. sorry for asking stupid questions but I sincerely appreciate the time you all take to respond. I am detrermined to fix this one. I was pretty careful to uncheck repartition but there is always the chance I missed it once.
Click to expand...
Click to collapse
to get to download mode, you need to either have a jig or to have your phone plugged into your computer while pressing VOL UP + VOL DOWN and PWR. that will get you to Download (Odin) Mode. To get to CWM Recovery, Unplug your phone from your computer and press VOL UP + VOL DOWN and PWR. The phone will do a short vibrate and the Samsung logo will appear. Then you will see ClockworkMod Recovery at the top with options. If you have standard (non-touch) CWM, use volume up and volume down to navigate and select your choice with the power button (short presses, a long press will power off). Go to mounts and storage -> mount usb storage. then copy your ROM of choice to your phone. go back twice and then enter install zip from sdcard. then either Choose zip from sdcard or Choose zip from internal sdcard. install. wipe data, wipe cache, wipe dalvik. reboot. win.
Continued thanks.....
jparnell8839 said:
to get to download mode, you need to either have a jig or to have your phone plugged into your computer while pressing VOL UP + VOL DOWN and PWR. that will get you to Download (Odin) Mode. To get to CWM Recovery, Unplug your phone from your computer and press VOL UP + VOL DOWN and PWR. The phone will do a short vibrate and the Samsung logo will appear. Then you will see ClockworkMod Recovery at the top with options. If you have standard (non-touch) CWM, use volume up and volume down to navigate and select your choice with the power button (short presses, a long press will power off). Go to mounts and storage -> mount usb storage. then copy your ROM of choice to your phone. go back twice and then enter install zip from sdcard. then either Choose zip from sdcard or Choose zip from internal sdcard. install. wipe data, wipe cache, wipe dalvik. reboot. win.
Click to expand...
Click to collapse
My problem is that I am not able to get into CWM. I am able to get into Odin mode but I get the vibrate when trying to boot into CWM then the Samsung logo then the blue bar that freezes when it reaches the end. After that when I try a regular boot all I see is the battery indicator if I have it plugged into power. I really appreciate these detailed instructions, but until I can get past the blue bar, I am stuck.......
Do you let go of the vol button and power before the Samsung logo? If you do then hold the buttons until the logo appears then let them go. If you let go early it just boots like normal
Sent from my SAMSUNG-SGH-T769 using xda premium
Problem Escalating
woodzx67 said:
Do you let go of the vol button and power before the Samsung logo? If you do then hold the buttons until the logo appears then let them go. If you let go early it just boots like normal
Sent from my SAMSUNG-SGH-T769 using xda premium
Click to expand...
Click to collapse
Search as I might I can't seem to get past this. I have CWM loaded but am getting an error mounting sdcard when I try and e: unable to write to ums lunfile when I try to mount USB. I'm getting in deeper here and would appreciate any further advice.
mikesmccurdy said:
Search as I might I can't seem to get past this. I have CWM loaded but am getting an error mounting sdcard when I try and e: unable to write to ums lunfile when I try to mount USB. I'm getting in deeper here and would appreciate any further advice.
Click to expand...
Click to collapse
I'd try reflashing CWM... something doesnt seem right. its like your mount points are all screwy.
http://forum.xda-developers.com/showthread.php?t=1591622
make sure to use the pit file located in that thread
--------------------EDIT-----------------------------
Just used the files (CWM and pit through Odin) and CWM flashed successfully for me. Able to do a nandroid backup and restore as well as flash a new ROM.
Also, please dont get mad for this, but just to be on the safe side (had a person last week who mistakenly did this) this is the Galaxy S Blaze 4G, not the Galaxy S 4G. If your device model isn't T769, you've got the wrong forum
I had the same issue today with s3 that I fixed will by restoring stock ........,.,...
Sent from my SAMSUNG-SGH-T769 using xda app-developers app