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.
My phone is dying prematurely, with my camera crapped out and my usb port not fully functional. My phone can charge but it can't be recognized by a computer anymore.
I'm sending it in for a replacement, but I realized now that I can't flash back to Froyo easily. I'm stuck in CM7, and factory reset brings me back to a fresh CM7. I don't want Motorola to use the fact that I used CM7 as an excuse to charge me $300.
Can someone help me please?
you can try restore froyo nandroid backup via custom recovery...
I'll have to remenber tha latest SBF that you flashed on your devide, have a friend with a Defy, flash it on that Defy, give him your SD card to put a full nandroid backup on it ...
basically you need to restore a nandroid backup of froyo of your region since you cannot flash the full sbf. There are already nandroid backups available in xda.
If you have wifi use a simple app called Ftpdroid to copy it to your memory card and restore.
If you do not have wifi then try coping the file using a card reader and restore.
Sent from my MB525 using Tapatalk
I have on my defy cm7 but don't work autofocus and i would to try the rom of defy + . I have to flash froyo ?
inst.
Zinshin said:
My phone is dying prematurely, with my camera crapped out and my usb port not fully functional. My phone can charge but it can't be recognized by a computer anymore.
I'm sending it in for a replacement, but I realized now that I can't flash back to Froyo easily. I'm stuck in CM7, and factory reset brings me back to a fresh CM7. I don't want Motorola to use the fact that I used CM7 as an excuse to charge me $300.
Can someone help me please?
Click to expand...
Click to collapse
FOLLOW THESE STEPS ::
>POWER OFF, PRESS AND HOLD POWER ON + VOL DOWN Till you get recovery mode , erase all data and wipe cache.
>reboot and keep on holding volume up key to get your phone in bootloader mode.
>connect your phone with your PC, open RSD LITE 4.9 , select your full sbf flash file and flash your phone.
NB::install all the drivers from Motorola driver installer or MOTOROLA PHONE TOOLS onto your pc before flashing. CHECK OUT http://forum.xda-developers.com/showthread.php?t=853674 or you can download and install these http://goo.gl/PrA6C
AND you can find the full froyo sbf for your region from the list http://forum.xda-developers.com/showthread.php?t=966537
rachit2588 said:
FOLLOW THESE STEPS ::
>POWER OFF, PRESS AND HOLD POWER ON + VOL DOWN Till you get recovery mode , erase all data and wipe cache.
>reboot and keep on holding volume up key to get your phone in bootloader mode.
>connect your phone with your PC, open RSD LITE 4.9 , select your full sbf flash file and flash your phone.
NB::install all the drivers from Motorola driver installer or MOTOROLA PHONE TOOLS onto your pc before flashing. CHECK OUT http://forum.xda-developers.com/showthread.php?t=853674 or you can download and install these http://goo.gl/PrA6C
AND you can find the full froyo sbf for your region from the list http://forum.xda-developers.com/showthread.php?t=966537
Click to expand...
Click to collapse
My computer does not recognize my phone when it's in Bootloader mode.
I installed the Nordic Rom to use CM7. So I need a nandroid backup. Does anyone know where I can get one?
Whenever I try to connect my phone to USB...
It says there's an error with the device. Windows 7 reports an unknown device, and error 47. That's why I believe there is something wrong with my usb port.
Progress:
I can't load into CM7 anymore, nor the stock rom. I can access the CM7 boot menu however, and go into Clockwork.
I tried a Motorola factory reset, and I tried changing the boot sequence (stock, 2nd-init, 2nd-boot) but no luck.
I'm a little stuck here guys
Have you installed USB drivers? Check all in beginners guide.
Sent from my MB525
You talk about your Defy not being recognized as USB disk?
Did you disable USB Debugging? So the USB Mass Storage option can be enabled after.
The data function in my usb port isn't working, my phone cannot be recognized at all. Even with three different cables and drivers installed.
Any ideas?
Is there a way to repair the port?
Could it have water damage? If it could, let the cap open and let it rest for a couple if days. Open it up and check for visible signs of damage/corrosion. Would not do this if you are trying to claim warranty.
To restore, go to the sbf threat, there are links to the individual threats of each. Normally, you can find there the nand. Place it in the right folder and restore it with cwm. Remove the battery and go to stock recovery. Wipe cache and data. Try to remember what sbf you were on, but don't think it matters much... Don't guaranty it will work. You could try to find someone who wants to try it as they can always flash a sbf if it doesn't work.
Sent from my MB525
i can help u with a nand of any sbf u want...just send me a pm or post here and in 1 hour i will upload it
just be sure u say the correct one, coz any boot cm7 version changes ur kernel, and the nand wont work
LE: after u restore the nand, just use the moto recovery, wipe data/cache so ur phone is back to stock, no root no custom recovery and u can take it to warranty
LLE: i guess i need to make a nand of the tmobile us version also so u can return it to the shop
Hmmm
Hmm but I flashed a nordic sbf. :/
I don't mind restoring nordic though, as long as there's no sign of cyanogen mod. I can replace the bootlogo and animation there.
I have used Cyan 7 for months with none of the problems you are describing. I also dont use any base and wonder why people are so pushy on using a base.
I go into recovery, Wipe all, Then install cyan then gapps.
It sounds to me you did or didnt do something during install.
Download the newest cyan 7 rom
Get into the stable recovery and wipe everything, even dalvik under advanced
Flash cyan
Flash gapps
reboot.
I promise it will work
Base doesn't matter, it gets replaced by stable releases. I think he tries to restore it to claim warrant.
Sent from my MB525
I think you may have overreacted and made things worse. Sometimes my data function stops working in CM7 - it fixes itself after a warm reboot or two.
Hi there,
Help me pls. Seems like infuse doesn't want to reboot at all after GTG's Ultimate Unbrick. Just flash AT&T on the beginning and samsung logo is on all the time.
PS Just restored successfully with Odin_UXKG3_rooted_no_bootloaders_v2
I hope everything will ok. Almost trowed my infuse in the garbage can. Sorry for panic... Fuf...
drov said:
Hi there,
Help me pls. Seems like infuse doesn't want to reboot at all after GTG's Ultimate Unbrick. Just flash AT&T on the beginning and samsung logo is on all the time.
PS Just restored successfully with Odin_UXKG3_rooted_no_bootloaders_v2
I hope everything will ok. Almost trowed my infuse in the garbage can. Sorry for panic... Fuf...
Click to expand...
Click to collapse
You used the wrong unbrick. Read here:
http://forum.xda-developers.com/showthread.php?t=1326143
Just noticed you got it working. I should have finished reading your post before replying
Unlocked Rogers SAMSUNG-Galaxy infuse failed system after GTG's Ultimate Unbrick
Hi, I'm new to this new Unbrick thing... I was about to throw out my Unlocked Galaxy Infuse and saw hope in this thread.
I unrooted my phone (not even sure how it got rooted in the first place) using GTG and Odin 3v 1.7. Did the hard reset. Now I see At&t and Samsung logo just hangs there. It's not even a boot loop because "Samsung" doesn't flashes.
This means I used the wrong Unbrick? So.... what now please? I just want my phone to be as it was when I first got it (Not rooted, default settings).
Can someone please explain to a newbie (I admit it!) step by step how to proceed? (When I hold vol up and down + power, samsung logo flashes like a boot loop. cant get past that.)
Thanks in advance )
PSS Should I use UXKG3, UCLB3 Unbrick... ? So confused...
Dandylion83 said:
Hi, I'm new to this new Unbrick thing... I was about to throw out my Unlocked Galaxy Infuse and saw hope in this thread.
I unrooted my phone (not even sure how it got rooted in the first place) using GTG and Odin 3v 1.7. Did the hard reset. Now I see At&t and Samsung logo just hangs there. It's not even a boot loop because "Samsung" doesn't flashes.
This means I used the wrong Unbrick? So.... what now please? I just want my phone to be as it was when I first got it (Not rooted, default settings).
Can someone please explain to a newbie (I admit it!) step by step how to proceed? (When I hold vol up and down + power, samsung logo flashes like a boot loop. cant get past that.)
Thanks in advance )
PSS Should I use UXKG3, UCLB3 Unbrick... ? So confused...
Click to expand...
Click to collapse
You probably already have it figured out...use UCLB3 if you're phone was released by AT&T, or UXKG3 if you bought through Rogers. I had the same predicament when I thought I bricked my phone and tried to go back to stock (I use Rogers so I was a little confused that my phone was crashing every 15 seconds with the UCLB3 back-to-stock).
Luckily I don't have to follow the UCLB3/UXKG3 conundrum with ROMS like CyanogenMod. Using CM 10.1 with UCLB3 kernel without any issues.
Same problem
joel.maxuel said:
You probably already have it figured out...use UCLB3 if you're phone was released by AT&T, or UXKG3 if you bought through Rogers. I had the same predicament when I thought I bricked my phone and tried to go back to stock (I use Rogers so I was a little confused that my phone was crashing every 15 seconds with the UCLB3 back-to-stock).
Luckily I don't have to follow the UCLB3/UXKG3 conundrum with ROMS like CyanogenMod. Using CM 10.1 with UCLB3 kernel without any issues.
Click to expand...
Click to collapse
Basically I have done the same samething with my phone, shows AT&T World Phone and the stuck on SAMSUNG logo, but I am really new to rooting and just not sure how to get back to Rogers. Just need super clear instructions/baby steps. And yes, the Infuse I have is infact one from Rogers.
Please help and thank you in advance
vingtdeux said:
Basically I have done the same samething with my phone, shows AT&T World Phone and the stuck on SAMSUNG logo, but I am really new to rooting and just not sure how to get back to Rogers. Just need super clear instructions/baby steps. And yes, the Infuse I have is infact one from Rogers.
Please help and thank you in advance
Click to expand...
Click to collapse
Taken from http://forum.xda-developers.com/showthread.php?t=1193927 ...
Odin Instructions:
1) Make sure the drivers for the Infuse 4G are installed. (Installing Kies is the easiest way to accomplish this.)
2) Download and unzip Odin_UXKG3_rooted_no_bootloaders.zip.
3) Run Odin v1.81 as administrator.
4) Place your phone into download mode. (Pull battery, replace battery, and press and hold both volume buttons while plugging in the USB cable.)
5) Make sure your phone shows up in Odin as COM##.
6) Click the PDA button and choose PDA_UXKG3_rooted_no_bootloaders.tar.md5.
7) Click the PHONE button and choose PHONE_UXKG3.tar.md5.
8) Press Start.
9) If the phone doesn't automatically reboot after it completes the flash, just pull the battery and then replace it and turn on the phone.
10) You should perform a factory reset after it boots. Go to Settings > Privacy and select factory reset. Warning: This will clear everything on your internal SD card, so move everything you want to keep to the external SD card first.
Click to expand...
Click to collapse
Download link: Odin_UXKG3_rooted_no_bootloaders_v2.zip (177MB)
As a footnote, I haven't had much luck with Kies for the drivers (step 1), I use these instead.
Hope this helps.
joel.maxuel said:
Taken from http://forum.xda-developers.com/showthread.php?t=1193927 ...
Download link: Odin_UXKG3_rooted_no_bootloaders_v2.zip (177MB)
As a footnote, I haven't had much luck with Kies for the drivers (step 1), I use these instead.
Hope this helps.
Click to expand...
Click to collapse
Probably won't believe me but I just finished what you just said as soon as you posted. GOT IT WORKING! Thank you anyways, your previous comments helped a bunch. Just so I don't screw up again in future rooting attempts, got any tips/links one should look at before attempting to root. I really wanna learn
If you flashed with above, then you are already rooted
Yeah look for superuser app in app drawer! Or download a root checker in Play Store to check!
Fullmetal Jun said:
Yeah look for superuser app in app drawer! Or download a root checker in Play Store to check!
Click to expand...
Click to collapse
Is there any way of checking if CWM Recovery is installed as well? I'm trying to install Cyanfox 4.4.2 ROM which requires a KitKat compatible CWM Recovery, which is what I need. Any suggestions would be great!
vingtdeux said:
Is there any way of checking if CWM Recovery is installed as well? I'm trying to install Cyanfox 4.4.2 ROM which requires a KitKat compatible CWM Recovery, which is what I need. Any suggestions would be great!
Click to expand...
Click to collapse
the following quote from here http://forum.xda-developers.com/showthread.php?t=2091900&page=370
scmfxt said:
@RiseFox
Hmm.. It could be files in your Internal SD card. Best to copy thing your need to your pc then format it. Also seem you using replacing recovery method thru root explorer / file manager to get CWM Recovery 2.5.1.2. My method is a bit different but it get me from GB stock + root and Synthesis GB Kernel to any other Rom without going thru ICS and JB:
1. Either use Odin or Heimdall One-Click. Follow instruction on how to do it.
2. While phone running install sgs kernel flasher from Market/Google Play.
2a. Copy/transfer Synthesis GB Kernel to your Internal SD card.
2b. Start up sgs kernel flasher and choose it from your Internal SD card. Phone will auto-reboot after done flashing.
2c. Wait a bit while your phone convert to new partition format and activate lagfix. Your CWM recovery version should be 2.5.1.3
3. Reboot phone into CWM Recovery and DISABLE vodoo lagfix and /system lagfix. Reboot once done. Phone will convert partition to old format. If you don't turn the lagfix off the phone will hang at Samsung logo when you install new rom.
4. Prepare your flavor rom/gapp for installation by copying them to your Internal SD card.
4a. Go into CWM Recovery mode and install the rom. You will need to do this twice since the 1st time was just a warning about partition format being different.
4b. Reboot once done. You will need to REMOVE the battery to power down the booting process and put it back in.
4c. Go into the New CWM Recovery and install the rom again since the previous attempt only install the new CWM Recovery.
5. Install Gapp.
6. a. Wipe: Cache / Factory Reset <--- Probably don't need it since it's new install from stock unless you installed stuff. Just to be safe.
b. Wipe: Cache Partition
c. Wipe: Dalvik Cache
7. Reboot
Hope that help.
Click to expand...
Click to collapse
i used this method for my at&t infuse and i was able to jump to 4.4.4 CarbonRom but like scmfxt said hope that this helps
vingtdeux said:
Is there any way of checking if CWM Recovery is installed as well? I'm trying to install Cyanfox 4.4.2 ROM which requires a KitKat compatible CWM Recovery, which is what I need. Any suggestions would be great!
Click to expand...
Click to collapse
No custom bootloaders come with the back-to-stock image. To check, do the three-finger salute to turn in on (power, and both volume buttons pressed). Will see either 3e recovery or CWM in the title. If it is the former, you can try this link (method 1), but I ended up doing the below:
Instructions:
1) Create a folder on your internal SD card called Voodoo. Then create another folder inside of it called disable-lagfix.
2) Make sure the Samsung USB drivers are installed. Installing Kies is a good way to accomplish this. It shouldn't matter which version of Kies you install as they all contain the same USB driver.
3) Download and unzip Odin_Infused_Gingerbread_Kernel_v1.zip.
4) Right click on Odin3_v1.81.exe and run it as administrator.
5) Place your phone into download mode. Do this by powering it completely off and then holding down both volume buttons while plugging in the USB cable.
6) Make sure your phone shows up in Odin as COM##.
7) Click the PDA button and choose PDA_Infused_Gingerbread_Kernel_v1.tar.md5.
8) Press Start.
9) If the phone doesn't automatically reboot after it completes the flash, just pull the battery and then replace it and turn on the phone.
10) You should now be rooted and see the Superuser app installed on your phone.
Click to expand...
Click to collapse
Download below. Hope this helps.
6th_Hokage said:
the following quote from here http://forum.xda-developers.com/showthread.php?t=2091900&page=370
i used this method for my at&t infuse and i was able to jump to 4.4.4 CarbonRom but like scmfxt said hope that this helps
Click to expand...
Click to collapse
It worked! Now running 4.4.2 BeanStalk.... and OMG rooting is amazing!
vingtdeux said:
It worked! Now running 4.4.2 BeanStalk.... and OMG rooting is amazing!
Click to expand...
Click to collapse
your welcome
OMG, thanks sooo much you guys for this, you just saved me a trip to rogers to cancel my phone plan (even though its like $90 a month for 6gb of data)
Rooted my phone, then tried to use ODIN for the recovery 3e install thing, which failed. Thought my phone was bricked and used the GTG ultimate unbrick which caused more problems
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..