Database Info

[Q] stuck on fast boot mode after flashing new kernal

Hi, last night i decided to flash a new kernal after the feature became available via Rom Manager. I tried to flash the kernal to which i was prompted with "insufficiant storage space, please reboot" so i did as asked and now im stuck in fastboot,bootloader? I can't access CWM to reflash and i have no idea to push a new recovery.img using a Mac 10.4.
I can get access to a windows PC, could anyone help me out with sorting this out. quite worried im now the owner of an expensive paper weight
Cheer

When you rooted the device you fastboot the recovery the first time then used recovery to flash the su. Just do that same method again. If not just look in the sticky of the development section for the many guides.

ok cheers will try that

When plugging in the device on the bottom of the nexus s screen it says "USB control init" "USB control init end" what does this mean as currently all that shows up in device manager is "Android 1.0" shouldn't it say Nexus S? Btw I used team wins' kernal app which obviously is a piece of ****. Never had a problem flashing within CWM
Sent from my Nexus One using XDA App

Ok pdanet solved that problem
Sent from my Nexus One using XDA App

It's also kernel not a kernal
Sent from my Nexus S using XDA Premium App

zephiK said:
It's also kernel not a kernal
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I don't think a mis-spelling of kernel contributes to the issue. Is this forum populated by pedagogues?

I just unbricked your phone

Here you go.

Yeah **** you grammar troll!!!
Nice one dude you are the best! Ill pop around tomorrow to collect
Sent from my Nexus One using XDA App

There was no way to move the recovery img to the phone by fastboot; this was completely shot. Fortunately there's a separate download mode hack you can use by plugging the phone into USB and holding vol up AND down simultaneously. This opens up a separate Samsung Composite Device which allows you to flash with Odin - Samsung's own flashing/debricking software This failed the first few times but after a few device driver reinstalls it flashed the bootloader, PDA and CSC files and booted quite happily.

leoni1980 said:
I don't think a mis-spelling of kernel contributes to the issue. Is this forum populated by pedagogues?
Click to expand...
Click to collapse
Mis-spelling? Kernal and Kernel are actually two different things:
http://en.wikipedia.org/wiki/KERNAL
The KERNAL is Commodore's name for the ROM-resident operating system core in its 8-bit home computers; from the original PET of 1977, followed by the extended but strongly related versions used in its successors; the VIC-20, Commodore 64, Plus/4, C16, and C128.
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Linux_kernel
The Linux kernel is an operating system kernel used by the Linux family of Unix-like operating systems.[6] It is one of the most prominent examples of free and open source software.[7]
Click to expand...
Click to collapse
And I'm no where close to being a "grammar troll." In fact, I wasn't even judging about your grammar. You were talking about a kernal when its a kernel. They're two different things. And I've helped many people in regards to the topic of fastboot and recovery. I was simply just clarifying on "kernel." I only posted it to to help you out by knowing its a 'kernel' not a 'kernal.' Sorry if that insulted you

That's just being pedantic.

[Tool] Nvflash unbricking released!

Hi,
As most of you probably already know by now, I have released a fully functional nvflash for Transformer yesterday
More information is available at http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
UPDATE 15-06-2011:Bumble-Bee (Apache14) is just as much to thank for this as me! Both of us (from AndroidRoot.Mobi) have worked hard on making this happen! Thanks to Roach for providing the nvflash-ready Prime 1.4 ROM!
UPDATE: The Prime 1.4 linked is European (WW) build! Roach will release 1.5 soon probably and there'll be both WW and US available. I'm planning to write a quick guide on how to root when running stock 3.1 already (it's pretty easy!)! E.g. to stay on full stock and *just* have root
Windows nvflash
Linux nvflash
Quick guide to unbricking:
Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
(Windows only) Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip
Run download.sh (linux) or download.bat (windows)
???
Profit

Awesome! Thanks a lot!!

rayman84 said:
Hi,
As most of you probably already know by now, I have released a fully functional nvflash for Transformer yesterday
More information is available at http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
Windows nvflash
Linux nvflash
Quick guide to unbricking:
Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
(Windows only) Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip
Run download.sh (linux) or download.bat (windows)
???
Profit
Click to expand...
Click to collapse
WOW, It's "just like that"? Really that's all what you have to do to unbrick a device? I guess times when flashing roms was dangerous have passed
Great job

Very thanks and keep up the good work!!!

unbrick tool came before root tool. lol
but it's a very useful program for all of us.
thanks for this!
i have a question though, my Samsung Vibrant was HARDWARE LOCKED, which makes button combinations to enter recovery/download modes impossible.
Is there any possibility that my TF has a hardware lock too which will prevent me from accessing the USB when it gets bricked?
i have experience in rooting and/or jailbreaking but i havent rooted my TF yet, coz the only way to root right now is kind of "not layman friendly". and i hate the terms BLOBS. lol
thank you.

So I'm rooted running prime 1.4 could some one explain in laymans terms what difference this makes to me and what if anything I need to do to benefit to my TF
DESIRE HD using leedroid. ASUS TRANSFORMER using prime

atlaswingpasaway said:
unbrick tool came before root tool. lol
but it's a very useful program for all of us.
thanks for this!
i have a question though, my Samsung Vibrant was HARDWARE LOCKED, which makes button combinations to enter recovery/download modes impossible.
Is there any possibility that my TF has a hardware lock too which will prevent me from accessing the USB when it gets bricked?
i have experience in rooting and/or jailbreaking but i havent rooted my TF yet, coz the only way to root right now is kind of "not layman friendly". and i hate the terms BLOBS. lol
thank you.
Click to expand...
Click to collapse
Either you didn't read the post or you might be dyslexic. If you unbrick your device you're pushing a custom ROM which means you automatically get root.

combat goofwing said:
So I'm rooted running prime 1.4 could some one explain in laymans terms what difference this makes to me and what if anything I need to do to benefit to my TF
DESIRE HD using leedroid. ASUS TRANSFORMER using prime
Click to expand...
Click to collapse
You don't need this your already rooted. This is a easy way to root and it can also revive bricks, custom flash different partitions and who knows what other functions can be done with nvflash.
Sent from my HTC Vision using XDA Premium App

Will this wipe your data partition if using this to get a rooted custom rom on?

seshmaru said:
Either you didn't read the post or you might be dyslexic. If you unbrick your device you're pushing a custom ROM which means you automatically get root.
Click to expand...
Click to collapse
it might be both! lol sorry my bad.
im new to tablet/honeycomb rooting so i dont know much about this.
so... im on stock 3.1 right now (i guess the build number wont matter anymore?)
and no root. should i just follow the OP instructions or what?

Canadoc said:
Will this wipe your data partition if using this to get a rooted custom rom on?
Click to expand...
Click to collapse
Using the script included it will wipe all user data. But it may be tweaked later.
Sent from my HTC Vision using XDA Premium App

atlaswingpasaway said:
it might be both! lol sorry my bad.
im new to tablet/honeycomb rooting so i dont know much about this.
so... im on stock 3.1 right now (i guess the build number wont matter anymore?)
and no root. should i just follow the OP instructions or what?
Click to expand...
Click to collapse
Yes if u want a custom rom with root. No more downgrading firmwares anymore like before

Cannot mount SD card in clockwork mod?
EDIT: Nevermind. I tried a different microsd card and it worked fine. False alarm... Move along... nothing to see here
I used the NVFlash utility to flash Prime 1.4 without a hitch but now that I'm trying to deploy the overclock kernel clockwork mod is not playing nice. I get an error E: Can't mount /sdcard when trying to choose a zip file. My understanding is that /sdcard is not the microsd anyway. How do I resolve this? I already tried reformatting the microsd card on my pc but that didn't solve the issue.
Thanks!
-Matt

I thought /Removable/sdcard/ was the sdcard.
Sent from my HTC Vision using XDA Premium App

david279 said:
I thought /Removable/sdcard/ was the sdcard.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
/Removable/MicroSD/ is the MicroSD card slot on the TF104
/SDCard is the 30gigs on the 32gb NAND

Also check the CWM installed. If it's the old one it erases your sd card and internal card on data wipes. You don't want that.
Sent from my HTC Vision using XDA Premium App

david279 said:
I thought /Removable/sdcard/ was the sdcard.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
It's /Removable/MicroSD
But I think the key thing here is that /sdcard is whatever the booting process mounts as /sdcard. This is why CWM has no problem listing the zip files for ROMs, etc. as being from the sdcard. It has accessed it through the actual block device which doesn't change. The whole internal sdcard that we see is some trickery that allows us to have access to all the space on our internal memory, but CWM doesn't know or care about that.
Sent from my Transformer TF101 using XDA Premium App

So...
No rooting, and no CWM..
Just use the tools and profit?

It flashes CWM for future flashing fun.
Sent from my HTC Vision using XDA Premium App

i just dont seem to get it.. . so does this give my stock 3.1 root?

Qhsusb_dload

Just tried to install CWM using Recovery Mangaer APP. Now it wont boot and i get QHSUSB_DLOAD in device manager. Am i fubar'd or is this brick recoverable? TIA

probably just need to get someone to dump the recovery partition and flash it with odin

designgears said:
probably just need to get someone to dump the recovery partition and flash it with odin
Click to expand...
Click to collapse
Any suggestions on where to start? at least i'm glad it happened to me instead of they guy i recommended it to. He was looking for a way to install CWM without a computer.. I don't need anymore enemies :angel:

designgears said:
probably just need to get someone to dump the recovery partition and flash it with odin
Click to expand...
Click to collapse
any idea where i can fond the drivers for 64bit win 7?

got the drivers installed. have the mmcblk0p22.img. Whats next? lol

Have you tried to RUU? Since the drivers are installed.
Sent from my HTC One X using Tapatalk 2

kleeman7 said:
Have you tried to RUU? Since the drivers are installed.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
no but i will. thanks.
Hunting Odin download now.

kleeman7 said:
Have you tried to RUU? Since the drivers are installed.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
ruu doesn't see it

QHUSB_DLOAD mode usually means you bricked hard and unless you have some software that the rest of us mere mortals don't, you will need to warranty it.

looks like odin is for Samsung devices?
anyone have any ideas? Device manager now reads:
Qualcomm HS-USB QDloader 9008 (com 7)

Hunt3r.j2 said:
QHUSB_DLOAD mode usually means you bricked hard and unless you have some software that the rest of us mere mortals don't, you will need to warranty it.
Click to expand...
Click to collapse
Qualcomm tools people have been looking for? I saw a post somewhere here at XDA and the OP was talking about some Qualcom tool kit. The'yve also been talking about some qualcom tools in the s-off thread.. Same thing??

nugzo said:
Qualcomm tools people have been looking for? I saw a post somewhere here at XDA and the OP was talking about some Qualcom tool kit. The'yve also been talking about some qualcom tools in the s-off thread.. Same thing??
Click to expand...
Click to collapse
I dunno, but it was talked about in the Sensation Unbricking Project, it isn't easy to recover at all, and for most it's a lost cause....

Hunt3r.j2 said:
I dunno, but it was talked about in the Sensation Unbricking Project, it isn't easy to recover at all, and for most it's a lost cause....
Click to expand...
Click to collapse
Thank you. The only tools i could find was revskills. Dont know if that's what i need or not. 90% of that is over my head.

nugzo said:
looks like odin is for Samsung devices?
anyone have any ideas? Device manager now reads:
Qualcomm HS-USB QDloader 9008 (com 7)
Click to expand...
Click to collapse
Yes Odin is Samsung. Get in touch with the s-off guys they have been playing around with download mode and may be able to help.
Borrowed this maybe it throwing you into recovery may help, also they said fastboot flash works, maybe flash twrp from fastboot.
beaups said:
I tried the pg1fs. sig check failure. As a matter of fact doing "fastboot flash aksldjflkadsfjdlsk pg1fs.img" causes the same error, so something is in the img that causes sig check or any flash attempt except recovery is sig checked. Fastbook oem refurbish puts out a lot of interesting text, then reboots into recovery and looks for something (doesn't say what).on sd card (I tried copying IMG's to internal and external sd, no luck). Interesting thing about refurb command is it seems particularly "excited" about the fact that we have super CID - run it yourself and see, no harm is done (data, etc.). one recovery boots you can screw around with volume and power keys to see the text.
Click to expand...
Click to collapse
Sent from my HTC One X using Tapatalk 2

Just thought I'd mention this to the op, I saw the thread where you were trying to help someone else flash a recovery without a pc with all the best intentions and ended up bricking. It broke my heart...lol sounds mushy I know, but really. Best of luck getting it fixed up man.
Sent from my HTC One X using Tapatalk 2

anyone find solution?

initialz said:
anyone find solution?
Click to expand...
Click to collapse
Thanks for the three month necro, but once again, go to the S-OFF thread...

what version was the last ruu you ran before it bricked..

You are probably SOL.
Sent from my One X using xda app-developers app

When you turn your phone on the first (idk) seconds your in emmc mode which you can dd the hboot partition in to fix your phone. Read it a while back in the S-Off thread, seems like it worked.
Edit: Rewrote whole thing, remembered how
Sent from my HTC One XL using xda premium

[Q] Hard Bricked GS3

Hello, I just got my new GS3 yesterday. Eager to root and ROM and all the fun stuff. I rooted and unlocked, and used Odin to flash CWM Recovery. Flashed the latest version of Android Revolution HD 16. I wiped cache, dalvik, the whole 9 yards. I did not WIPE boot.img though. Flashed Android Revolution 16, it all went good. Clicked Reboot Phone in CWM Recovery and nothing. No LED light on when plugged into USB or via wall charger. No Download mode, or recovery. Nothing, like nothing at all. Anything you guys suggest?
EDIT: I am not sure if it is Hard Bricked. When I plug it into my PC, it makes a sound. Also tries to install a driver and fails every time.
EDIT2: Okay guys, my fault. Downloaded a ROM that was meant for a different model/type GS3 forum when I have a Verizon GS3 (SCH-1535). Anyone know how to fix this problem? Please disregard this incorrect forum post.

If you flashed anything related to the international S3, Google search J-tag! Or return the device and play dumb...

droidstyle said:
Google search J-tag! Or return the device and play dumb...
Click to expand...
Click to collapse
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?

T Greezy said:
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?
Click to expand...
Click to collapse
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.

droidstyle said:
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.
Click to expand...
Click to collapse
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?

T Greezy said:
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?
Click to expand...
Click to collapse
No that verifies what i previously posted.

droidstyle said:
No that verifies what i previously posted.
Click to expand...
Click to collapse
I have faith, thought. I can maybe push something using ADB you think?

You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app

josh995 said:
You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!

T Greezy said:
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!
Click to expand...
Click to collapse
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!

No one is going to stop you. You flashed an international ROM on an s3. This is a known method of hard bricking your s3.
Sent from my SCH-I535 using xda app-developers app

T Greezy said:
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!
Click to expand...
Click to collapse
That sounds about right. Luckily it's $60 and not $600 for a new phone
Sent from my SCH-I535 using xda app-developers app

Same thing happened to me. Needed a j-tag but risked calling Verizon told them my phone wouldn't come on all they asked me was if I damaged it with water or heat. (Either Verizon doesn't care or actually they just scrap the phone) I was rooted and unlocked but flashed the wrong carrier rom. Now I have a replacement phone that cost me $0.
They sent me the 16g and not the 32g by mistake I figured I've pushed my luck enough
Sent from my SCH-I535 using Tapatalk 2

First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.

ericerk said:
First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.
Click to expand...
Click to collapse
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.

I do have a question for the op and the other guy who flashed an international ROM. Were did you get them and how did you find then ( like was it a site you googled?) I've noticed a lot of these lately and am wondering if it's something that can be avoided (besides the obvious read what you're flashing)
To the adb guy there us no recovery on his phone it was overwritten by part of the international ROM. he needs to JTAG his phone, don't call Verizon. You did this to your own phone, pay the 60 and learn your lesson.
Sent from my SGS3 running Eclipse 2.1

droidstyle said:
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.
Click to expand...
Click to collapse
One day someone is going to find a way to unbrick the hard brick, lol. Eventually. Anyways, if it was "dead" then why would it show my S3 as "QHSUSB_DLOAD"? and attempts to install a driver. I'm gonna try to find the right driver to manually install, and troubleshoot from there. I mean come on guys, be optimistic. How great if this problem was RESOLVED? Also, the download mode got wiped/overwritten from a different ROM for a different model of the GS3. What about the Recovery? CWM? If I can just magically, somehow, maybe even push some type of command. Even maybe ADB? Or something in the terminal. I'm really trying to find a solution. So in the future, we will have a SOLUTION.
Anyways, I'm going to be shipping my GS3 Monday or Tuesday for Samsung to repair (If they can) or replace for no charge!
Wish me luck guys, gonna be really thinking out of the box.

Hope you can figure it out. But someone had a way to fix a hard brick.... The JTAG
Sent from my SGS3 running Eclipse 2.1

Okay guys, I've actually have gotten some good progress, I hope! I came across a thread that a guy named (therockk) he also, hard bricked his S3. Sent him a PM, and he told me he got ODIN to recognize his hard bricked S3 "WITHOUT" download mode. He said he found a driver for QHSUSB_DLOAD and manually applied the driver update. His PC, then recognized his S3 as a ID CODE: COM10 - I do not know what that means, I asked around. Some people say that it is the code for when your phone is connected in Download Mode? Nevertheless, this is good in my eyes. The phone as now, recognized as COM10 in ODIN, in its hard-bricked stage. This could be that also, maybe, the phone will be recognized in ADB/Fastboot commands. Maybe we can get something going here guys! I'm trying to look on the bright side. I'll keep you posted.
EDIT: Okay guys, was looking at some screenshots of the CODE ID's. Like I said, my buddy "therockk" said he got ODIN to recognize his phone as a COM10, while being hard-bricked. I am guessing there are different CODE ID's for each model/version of the S3. I did make an observation that he, has a different model S3 ( i747 ) and he got his to see COM10. Which means it was Added!! - My Verizon S3 (SCH-1525) should come up as COM4 when the PC recognizes it. When I do get my PC to recognize my S3, I will confirm that my SCH-1535 phone comes up as COM4, if not, I will confirm the correct CODE ID. therockk's i747 came up as a COM10, that is confirmed.
EDIT 2: Okay guys! Updated the driver successfully! QSHUSB_DLOAD is now Qualcomm HS-USB QDLoader 9008 (COM8). I feel like we're getting closer. Now to see if Odin will pick it up!

I can probably help you through this problem after work tonight if you are still having trouble. Just pm me around 10pm est
Sent from my SCH-I535 using xda app-developers app

Soft Bricked! Physical volume button broken, Please Help!

Hi Everyone, my galaxy S 4G SGH-T959V has had its volume down key broken for a while now, but stupid me flashed a ROM + another zip causing an endless boot. I cant go into recovery because my volume down key doesn't work! i'm a noob at this and i have valuable credentials on this phone that I cant afford to lose. Is there any way I can flash the (or a) ROM again and be out of the boot loop (while keeping my data) I've made this mistake before and that solves the case every time. if I need adb or Odin please guide me step by step. I really appreciate any help I receive. Thank you.
Boots forever and ever, does charge, volume up works, power key works, SD card slot work, hardware keys a-OK. vibration is a no-go from a concrete fall (don't know how my screen isn't shattered haha)
Also, I have a galaxy s 4 as a replacement and willing to donate this T959V to a dev here after I recover my data (that is if i do )
Thanks guys.

A "recovery jig" will do it. You can make one for a couple dollars, or get one off eBay for probably about the same.
Posted from my SGS4G, thanks to Team Acid development

jeffsf said:
A "recovery jig" will do it. You can make one for a couple dollars, or get one off eBay for probably about the same.
Posted from my SGS4G, thanks to Team Acid development
Click to expand...
Click to collapse
Thanks for helping! I googled that and it seems that would do the trick, however there are none on ebay, only on a not so local craiglist. Is this the only hope for me? Thanks again.

I just bought a unit for 8 dollars! could you give me a quick explanation of the steps to flash now? do i need anything other than odin? and what do i select/input into odin just for a reflash. thanks!

Czajkus said:
Thanks for helping! I googled that and it seems that would do the trick, however there are none on ebay, only on a not so local craiglist. Is this the only hope for me? Thanks again.
Click to expand...
Click to collapse
I bought a JIG from ebay for 99 cents with free shipping for I9000 and it worked on T959V.

Rebel_X said:
I bought a JIG from ebay for 99 cents with free shipping for I9000 and it worked on T959V.
Click to expand...
Click to collapse
Yeah I finally found one on ebay for 2 bucks so just cancelled the other order. could you explain me how to use this thing?
Thanks

Why don't you fire up your PC and adb recovery..everything is here(files and quick guide)
http://forum.xda-developers.com/showthread.php?t=1853159
Sent from my SAMSUNG-SGH-I577 using xda app-developers app

It's been a while since I've bricked a phone, but if you want to preserve data, I would get it into download mode and only flash "kernel" -- for the SGS4G, that includes recovery, so you should be able to get it up and running without wiping/flashing /data

I don't see why he couldn't adb into recovery ,wipe cache and dalvic and flash a known working ROM w/gapps and reboot...I've done it a few time on my little Sammy..(soft bricking that is)...just my 2 cents..
Sent from my SAMSUNG-SGH-I577 using xda app-developers app

I take
Czajkus said:
... causing an endless boot.
Click to expand...
Click to collapse
as meaning that there isn't a time where adb could be used as it is boot looping
There is a possibility that something like
Code:
adb wait-for-device && adb reboot recovery
or even
Code:
adb wait-for-device reboot recovery
might work.
Here's a link to an XDA thread for some info on how to (generally) use a Samsung recovery jig.

Czajkus said:
Yeah I finally found one on ebay for 2 bucks so just cancelled the other order. could you explain me how to use this thing?
Thanks
Click to expand...
Click to collapse
Simple, when the phone is off, put the jig in usb port, download mode appears, remove the jig and attach the usb cable from your pc to the phone and flash using heimdall or odin.
Oh, the jig also works on S2 and S3 as I tried.

jeffsf said:
I take
as meaning that there isn't a time where adb could be used as it is boot looping
There is a possibility that something like
Code:
adb wait-for-device && adb reboot recovery
or even
Code:
adb wait-for-device reboot recovery
might work.
Here's a link to an XDA thread for some info on how to (generally) use a Samsung recovery jig.
Click to expand...
Click to collapse
okay guys sorry for the delay i've been busy thanks for all the help, i'm running Odin v3.09 and wondering what do i need to flash? there's a pit file, BL, AP,CP, and csc. i know in my knowledge that i can get out of my endless boot with just re flashing the ROM zip file. so I can someone tell me which files (bl, AP) i need to use? thank you

Czajkus said:
okay guys sorry for the delay i've been busy thanks for all the help, i'm running Odin v3.09 and wondering what do i need to flash? there's a pit file, BL, AP,CP, and csc. i know in my knowledge that i can get out of my endless boot with just re flashing the ROM zip file. so I can someone tell me which files (bl, AP) i need to use? thank you
Click to expand...
Click to collapse
You could go wrong easily with Odin if you do not know what you are doing or
what the parameters mean. So I suggest you use Heimdall One-Click. After that you can flash anything you want using the recovery.

A one-click, as I recall, may/will wipe your data partition. If you want to be able to preserve your data, the only thing you want to flash is the kernel/boot/recovery (it's all the same thing on the SGS4G). Then you should be able to get into recovery, make a backup, and go from there.
I definitely recommend Heimdall over Odin.