Database Info

[HOWTO] Update to JH7 using Kies Mini (USA)

Decided to make a thread on it since I have two posts floating around that have helped people:
I was once one of the large group that the OTA JH7 Update failed at 50%
However, Today after downloading Kies Mini, I was successfully able to upgrade and remain "stock" JH7 from update without root etc.
IMPORTANT NOTES:
THERE APPEARS THERE MAY BE ISSUES WITH KIES MINI ON 64BIT SYSTEMS - USE A 32 BIT OPERATING SYSTEM
Launcher Pro and Kies Mini may not work well together, if you are updating from a NON-FRESH JF6 you must revert to TouchWiz (Stock) Launcher
1.) Flashed a fresh JF6 ODIN One-Click. (With power off, you can enter download mode by holding both volume buttons and inserting USB once ODIN is open)
2.) Enabled USB Debugging and Ran Master Clear.
3.) Installed Kies-Mini on the PC and let it install the new drivers etc.
4.) Checked phone to be sure it was clear of any additional files on the SD.
5.) Under Settings - Applications - USB Settings - Selected "Ask on connection" (you MAY also need to re-enable USB Debugging, try without it first)
5.) Started Kies-Mini and then plugged in my device selecting "Kies"
6.) Upon device detection it notified me an update was available.
7.) Ran update and I am now Official STOCK JH7 including the new QuickOffice and Media Hub
Proof that it made it to 100%: (This screen shows after download & install - It is verifying the install)
You find a download to the JF6 ODIN One-Click here: (Thanks to DESIGNGEARS)
http://forum.xda-developers.com/showthread.php?t=731989
You can download Kies Mini for the Captivate Here: (Thanks to SAMSUNG)
http://downloadcenter.samsung.com/c...0737296/Kies_Mini_For_Captivate_10082_8_1.exe
Special Thanks to Krad for notifying the community that Kies Mini was now available!
Thanks to shawnl01 and ScottyNuttz for discovering that "Enable USB Debugging" may solve a few problems
Thanks to Dxtra for pointing out that Launcher Pro and Kies Mini do not work together
Thanks from:
keitht said:
After pulling my hair out, I tried these steps and it worked! Thank you!
Click to expand...
Click to collapse
IronEagle410 said:
Wow...IT WORKED! Follow these steps to the letter and you will be updated! Thank you!
I was apparently doing the ODIN wrong. Once I sorted that out it worked like a charm!
Click to expand...
Click to collapse
hujingtong said:
Thanks for the post. I have updated it. Now the GPS locks fast.
Click to expand...
Click to collapse
subjectb said:
Worked for me. Kies-Mini, not the full Kies. Just "Unmount SD Card" and leave it unmounted. Set USB setting to "Samsung Kies". Uncheck "USB Debugging Mode".
This assuming that you've done Odin3 (JF6 flash and Master Clear) correctly, and cleared user and data cache.
Click to expand...
Click to collapse

where is my thanks for finding it and also assisting a few users with getting this up and running?
I am going to edit my post to be better then yours!!!!

Krad said:
where is my thanks for finding it and also assisting a few users with getting this up and running?
I am going to edit my post to be better then yours!!!!
Click to expand...
Click to collapse
Included, thanks for the notification of the release of Kies mini and making this possible for so many!

A little nit picking, there is no such firmware as JH6. Please update your OP with correct information. The first release firmware is JF6.

You sir are correct, thanks for catching the mistake!

JH7 over Kies Mini
OK, I decided to give this a try. Here is what I did:
1) Flashed back to stock (JF6);
2) Cleared cache & user data;
3) Formatted SD card;
4) Connected to PC and Kies picked it up and quickly indicated update of JH7 was available;
5) Kies updated - it took about 15 minutes to download and install.
The first think I did was test the GPS and it locked indoors in less than 10 seconds. I did not have WiFi or "Use wireless networks" on. It gave 10 meters accuracy within about 20 seconds.
I also noticed the media scanning was very fast and there seems to be very little lag. All-in-all, so far, I think this is a good update. I will post again after I've tested the GPS out and about and a week or so of use to see if the lag remains minimal.

This whole update ordeal is sorta tickin' me off.
For whatever reason, I have not been able to install OTA. "Update is failed." message appears every time.
Attempted update last night with standard UK Kies. Said no upgrade was available.
Just attempted Kies mini and every time the phone is plugged into the computer is causes the application to throw an "Application has stopped working" error under Windows 7.
Phone shows JF7. CSC and PDA show JF6.
What... the... hell!

I am also on Windows 7 and had no issue, did you try using the software provided above? Also, did you remove the other version of KIES and follow step by step?
Also maybe try using a different USB port, and run the application in compatibility mode

Colton5419 said:
I am also on Windows 7 and had no issue, did you try using the software provided above? Also, did you remove the other version of KIES and follow step by step?
Also maybe try using a different USB port, and run the application in compatibility mode
Click to expand...
Click to collapse
Yes. Software provided above. Removed all traces of previous Kies. Attempted in XP compatibility mode. Ran with Administrator privileges. All of it.
Still nada.
Guess it's on to Odin, reflash stock JF6 and start fresh.

Anyone have any ideas about the unregistered I get on kies mini? My phone is registered with samsung if thats what it means.

When I was on Cognition etc, I was still able to connect my device to Kies Mini just not update it.
Try this:
On your device, make USB connection to Kies as default by going to [Settings] > [About phone] > [USB settings].
Then unmount both of your SD Cards, Internal and External.
Go where your installed Kies. For example:" C:\Program Files\Samsung\KiesMini" look for AMiniLauncher and start it
Then try to connect your device.

Now im getting a "failed to connect to the model information server" Anyone else experience this?
EDIT: Seems to only happen when in USB debugging mode. When I switch out USB debugging I get the unregistered error.

IronEagle410 said:
Now im getting a "failed to connect to the model information server" Anyone else experience this?
EDIT: Seems to only happen when in USB debugging mode. When I switch out USB debugging I get the unregistered error.
Click to expand...
Click to collapse
What state is your phone in?
Custom ROM? Etc?

Colton5419 said:
What state is your phone in?
Custom ROM? Etc?
Click to expand...
Click to collapse
Nothing...full stock. I did root to remove bloat but have since unrooted.

IronEagle410 said:
Nothing...full stock. I did root to remove bloat but have since unrooted.
Click to expand...
Click to collapse
Is your operating system 64 bit or 32 bit?

Wow...IT WORKED! Follow these steps to the letter and you will be updated! Thank you!
I was apparently doing the ODIN wrong. Once I sorted that out it worked like a charm!

IronEagle410 said:
Wow...IT WORKED! Follow these steps to the letter and you will be updated! Thank you!
I was apparently doing the ODIN wrong. Once I sorted that out it worked like a charm!
Click to expand...
Click to collapse
Glad to hear it worked for you! What did you do wrong in ODIN? It may help someone else out!

I heard somewhere that launcher pro and kies don't work together, go back Touchwiz default launcher. Hope that helps.
Sent from my SAMSUNG-SGH-I897 using XDA App

Dxtra said:
I heard somewhere that launcher pro and kies don't work together, go back Touchwiz default launcher. Hope that helps.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
This is true, I didn't make note of that because the instructions assume that they are starting by flashing a fresh JF6 through ODIN.
But If they make the attempt from a non fresh install that would be a very good point. - added to the instructions! Thank you!

IronEagle410 said:
Now im getting a "failed to connect to the model information server" Anyone else experience this?
EDIT: Seems to only happen when in USB debugging mode. When I switch out USB debugging I get the unregistered error.
Click to expand...
Click to collapse
Make sure you are using Kies USB mode and has TouchWiz as your default launcher and you're on your home screen when you connected your USB cable. All three must be met and if you're doing right, your phone will show MTP Application screen.

[Q] Stock (unrooted, untampered) Nexus S stuck @ Google screen during bootup

Hi folks. I've tried searching on this subject and looks like every thread I've seen on this site related to a stuck Google screen was the result of trying to root the device. My situation is different. I have a stock phone given to me by Google (I'm a former Googler) and up until recently the phone started to go awry whenever I had to reboot it. It would stay stuck at the Google logo. I've tried recover, clearing the cache and also factory wipe and it will always restart and get stuck at the logo. I've found some threads on Google's support forums that mention it may be hardware related with faulty memory being the issue. I'm trying here as a last resort.
The phone is the regular Nexus S 3G for Tmobile. Please help before I smash this phone into the wall.

I'd try rooting and installing a custom rom. If it works after that and you want it to be stock again you could just reverse the process. If none of that works then I'm guessing it's similar to the other phones with hardware problems.

ex-googler said:
Hi folks. I've tried searching on this subject and looks like every thread I've seen on this site related to a stuck Google screen was the result of trying to root the device. My situation is different. I have a stock phone given to me by Google (I'm a former Googler) and up until recently the phone started to go awry whenever I had to reboot it. It would stay stuck at the Google logo. I've tried recover, clearing the cache and also factory wipe and it will always restart and get stuck at the logo. I've found some threads on Google's support forums that mention it may be hardware related with faulty memory being the issue. I'm trying here as a last resort.
The phone is the regular Nexus S 3G for Tmobile. Please help before I smash this phone into the wall.
Click to expand...
Click to collapse
have you tried manually flashing the stock signed by google rom through your stock recovery yet? it sounds like it got corrupted or has some corrupted data. id try to manually flash it.

aliiasgar said:
I'd try rooting and installing a custom rom. If it works after that and you want it to be stock again you could just reverse the process. If none of that works then I'm guessing it's similar to the other phones with hardware problems.
Click to expand...
Click to collapse
I can't seem to root it. I've installed the adb drivers and windows detects it whenever I plug the USB in, but I can't unlock it to root it. When I run this command, "fastboot oem unlock" it just keeps trying to detect the phone but never does. I think it's because USB debugging isn't enabled and I can't enable it without being able to get back into the phone.

ex-googler said:
I can't seem to root it. I've installed the adb drivers and windows detects it whenever I plug the USB in, but I can't unlock it to root it. When I run this command, "fastboot oem unlock" it just keeps trying to detect the phone but never does. I think it's because USB debugging isn't enabled and I can't enable it without being able to get back into the phone.
Click to expand...
Click to collapse
you need the nexus s drivers go to the pdanet website http://junefabrics.com/android/ and download and install the free version on your desktop. then follow the on screen instructions and it will install the drivers for you. thats the easiest way to install the drivers.

simms22 said:
you need the nexus s drivers go to the pdanet website and download and install the free version on your desktop. then follow the on screen instructions and it will install the drivers for you. thats the easiest way to install the drivers.
Click to expand...
Click to collapse
I've already installed that. It won't detect the phone properly because I can't enable the USB thing within the android OS since I'm blocked from fully loading up the phone.

It sounds like the sdcard memory won't mount. This is a hardware issue.
Sent from my Nexus S 4G using xda premium

Rem3Dy said:
It sounds like the sdcard memory won't mount. This is a hardware issue.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
That's interesting you say that because I do notice an error during recovery and selecting data wipe. I had a colleague in the android dept tell me it's most likely bad flash memory.
"E:format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/userdata"
I'm gonna call Samsung tomorrow.

[SOLVED] USB still not recognized (ICS Leak)

Edit:
This problem has been solved. For any of you that are having issues with ADB recognizing your phone, even after you have uninstalled and reinstalled the correct drivers (As I had done several times on 2 computers), a factory reset might be your answer. So, if you are on ICS leak, and the last thing you want to do is try to FXZ back to 2.3.6...Try wiping data/factory reset first. It solved my problem once and for all.
------------------------------------------------------------------------------------------------
First, I must say that I have already found similar threads of this type, and some even with solutions, but I still cannot fix this problem.
I am on ICS Leak on my AT&T Atrix 2 and everything is running great, aside from one thing. I cannot get my computer to recognize my device. When I plug it in, it will charge, but I get no USB options in my notification bar on my phone. I have tried other solutions, and I have installed the necessary drivers, (Windows 7), I have uninstalled and reinstalled, and rebooted with no luck. If anyone could help me, that would be great! Let me know if any more details are needed...

Recognition problem solved. Root script still hanging at *daemon started successfully*
Debugging is on, Stay awake on, Install from unknown sources on, drivers installed, what else could be the problem?

I had to uninstall drivers and all moto services. Then plug in phone let it look for install drivers. It failed on one of them. I then installed the moto portal disconnected my phone, rebooted computer and phone, plugged it back in and it worked. Good luck.
Sent from my MB865 using Tapatalk 2

Garnerj013 said:
Recognition problem solved. Root script still hanging at *daemon started successfully*
Debugging is on, Stay awake on, Install from unknown sources on, drivers installed, what else could be the problem?
Click to expand...
Click to collapse
First off if you found similar threads post in them, no need to start a new thread
I'm guessing you are trying to root?
if you are, the script takes a while to run your phone will reboot several times it will tell you when it is done

Garnerj013 said:
Recognition problem solved. Root script still hanging at *daemon started successfully*
Debugging is on, Stay awake on, Install from unknown sources on, drivers installed, what else could be the problem?
Click to expand...
Click to collapse
adb devices command showing your device? If so, try again.. and wait, like drgravy said.
Or do what leif said and switch between the 3 different usb connection types and wait for the drivers to install.. and try putting it in mtp or ptp mode to run the root batch file..
Sent from my phone's mind

Drgravy said:
First off if you found similar threads post in them, no need to start a new thread
I'm guessing you are trying to root?
if you are, the script takes a while to run your phone will reboot several times it will tell you when it is done
Click to expand...
Click to collapse
Sorry about the new thread. Blame it on the n00b status. I have rooted with this method before on the same model phone with ICS leak and it worked after a few unsuccessful tries. It usually shows some activity in the command prompt, but this time it is hanging at *daemon started successfully*
alteredlikeness said:
adb devices command showing your device? If so, try again.. and wait, like drgravy said.
Or do what leif said and switch between the 3 different usb connection types and wait for the drivers to install.. and try putting it in mtp or ptp mode to run the root batch file..
Click to expand...
Click to collapse
I've tried in every connection mode, and I have the drivers installed. I've been trying every way possible. Also, for simplicity sake, could you tell me how to use the adb devices command? I'm tech savvy but pretty green to the development/programming side of things.

leifemagnuson said:
I had to uninstall drivers and all moto services. Then plug in phone let it look for install drivers. It failed on one of them. I then installed the moto portal disconnected my phone, rebooted computer and phone, plugged it back in and it worked. Good luck.
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Also, once i uninstall Motorola Device Manager, do I have to manually uninstall more drivers, or does that get them all? If not, how do I manually uninstall the drivers?

http://forum.xda-developers.com/showthread.php?p=29609879
I was having the exact same issue where it was hanging at daemon started successfully. Was totally a driver issue. Follow the link in my link...
I would suggest completely uninstalling everything Moto from your PC, rebooting and then follow the steps again, being sure to install those new drivers that are linked in that post.
Edit: I'm trying to remember when I did it....but I seem to recall having a bit of weirdness when I installed the new drivers. I had the install driver wizard pop up while I was installing the drivers from the moto driver executable. I just let the wizard sit there and wait while the moto driver installer did its thing.

So, instead of uninstalling all that is Moto on my laptop, I moved the Moto Device Driver executable and the batch files (with Su and Superuser.apk and all the extras to my desktop. Ran the moto executable and plugged my phone in to install the drivers and rebooted the computer. Still nothing. Do i need adb on my desktop to root my phone? I'm getting flustered with this. It really should be working one way or the other....

Same issue for me..i reinstalled drivers and connected the phone in media transfer mode..rest of procedure same..am successfuly rooted now
Sent from my MB865 using xda app-developers app

devilhunter47 said:
Same issue for me..i reinstalled drivers and connected the phone in media transfer mode..rest of procedure same..am successfuly rooted now
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
I tried and tried to reinstall the drivers, and even installing them on a different PC didn't work. Finally, I did a factory reset, and the phone was recognized by ADB. Thankfully, I am now rooted and on SCv7!! (Thanks to Jimbridgman, Ikrasner, and a couple other devs.) Thank you all.

[Q] I've tried everything to get out of boot loop

Hello everybody,
I am new to the forum and also new to Androids. After years of using iPhones and finally becoming fed up Apple, I've decided to try something new (please don't judge my prior smartphone selection and start posting opinions about the 2 operating systems, I do not want this thread to turn into one of the "battle of the phones" thread that I've experienced many times on iPhone forums). My friend recently got an S3 and had no use for his Galaxy S 4g, so he gave it to me so that I could try out an Android. There was one issue though, he said that the phone would not get past the Galaxy S screen and would keep re-booting itself (stuck in a boot loop). He said if I could figure out a way to fix it then it's mine.
That being said, here's my dilemma. I've tried many different methods to get the phone out of a boot loop. The first method I tried was putting the phone into restore mode and selecting the "reinstall packages" option. After this executes I get the message:
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
After some further research I discovered a nice little program called Odin I read a lot about Odin and how to properly use it. After trying at least 5 different methods to get the phone into download mode with no success, I purchased a jig. The jig did the trick and instantly put me into download mode, I was ecstatic and hopeful that I could now fix the phone with Odin. I connected the phone to my PC in download mode, but Odin still didn't recognize the phone (I tried many versions of Odin, 1.85, 1.87, and the most recent 3.07). I do have the latest drivers for this phone, which I downloaded from Samsung's website. The phone will charge through the computer but the computer does not recognize it otherwise and will not allow me access its mass storage (I am running Windows 7 64 bit). I have tried using a different USB cable, and I have tried to use a different PC, the other PC I used popped up with a message saying that Windows could not successfully download the drivers (that was after I downloaded the drivers from Samsung's webpage and plugged the phone into the computer). I've even tried transferring stock firmware onto an external SD card and loading it onto the phone from restore mode (is that even possible to do?). I have also tried running Odin in compatibility mode, still didn't detect the phone. I should probably also mention that Kies Mini also does not recognize the phone. I asked my friend if he ever tried rooting this phone and he said no, so I'm assuming this issue has nothing to do with a failed attempt to root.
I really want to get this phone working, but I have run out of options to try. I am hoping that someone on here has a solution for me from a similar experience. After reading through the forum, I have noticed that people on here are very helpful and also very friendly; something that I can say is very different from some of iPhone forums I've used. I apologize if there is already a similar thread to mine, I've read through many threads and none of the solutions have worked for me. I also apologize for my first post being so lengthy, I just wanted to state all of the methods that I've tried to fix this phone. Thanks for your replies.

Hi hubbs134
You have come to the right place.
First,
I suggest you read a little bit about this phone and how to put it in Recovery (by holding Volume Up + Volume Down + Power until you see the SGS4G splash screen) and Download modes, it will help you in the future.
You can find it all in the Wiki.
Second, use this guide to One-Click Heimdall your way to Stock KJ6 2.3.6 Gingerbread ROM (latest official ROM for this phone).
If you use this file (instead) with that guide, you will also get phone rooted, or else you will need to make another flash of a rooted kernel (as the guide suggests).
Now, if you have the official latest stock, but still want some ICS/JB lovin', if you have CWM recovery v5 (you will see the recovery info once you're in that mode), you can flash CM9/AOKP/HebMIUI/UltraGen/RemICS/CM10/Slimbin/etc. etc. etc. ROMs.
Enjoy and welcome aboard!
P.S what the @#%#$ were you doing with an iphone ?

itzik2sh said:
Hi hubbs134
You have come to the right place.
First,
I suggest you read a little bit about this phone and how to put it in Recovery (by holding Volume Up + Volume Down + Power until you see the SGS4G splash screen) and Download modes, it will help you in the future.
You can find it all in the Wiki.
Second, use this guide to One-Click Heimdall your way to Stock KJ6 2.3.6 Gingerbread ROM (latest official ROM for this phone).
If you use this file (instead) with that guide, you will also get phone rooted, or else you will need to make another flash of a rooted kernel (as the guide suggests).
Now, if you have the official latest stock, but still want some ICS/JB lovin', if you have CWM recovery v5 (you will see the recovery info once you're in that mode), you can flash CM9/AOKP/HebMIUI/UltraGen/RemICS/CM10/Slimbin/etc. etc. etc. ROMs.
Enjoy and welcome aboard!
P.S what the @#%#$ were you doing with an iphone ?
Click to expand...
Click to collapse
Thanks for your reply, I have read a lot about this phone and know how to get into download and recovery mode. I tried the method you mention, however, when running the command window I get errors for both roms you suggested (i attatched a screen shot of the errors I'm getting). Do you know how I can fix these errors so that I can proceed with the rest of the tutorial? Thanks.
PS I only had an iPhone because I had yet to discover how bad a** Androids are

It sounds like you can't use Odin because of a windows issue. Try installing linux. I use ubuntu
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 07:48 AM ---------- Previous post was at 07:47 AM ----------
You can also run as live CD or in a virtual machine
Sent from my HTC One X+ using xda app-developers app

hubbs134 said:
Thanks for your reply, I have read a lot about this phone and know how to get into download and recovery mode. I tried the method you mention, however, when running the command window I get errors for both roms you suggested (i attatched a screen shot of the errors I'm getting). Do you know how I can fix these errors so that I can proceed with the rest of the tutorial? Thanks.
PS I only had an iPhone because I had yet to discover how bad a** Androids are
Click to expand...
Click to collapse
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !

itzik2sh said:
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
Click to expand...
Click to collapse
I second this... This should fix your driver issues.

Thanks for both of your replies. Odin detected my friends GS3 so I know it's not a Windows issue.
itzik2sh I did what you suggested and now got the command to function properly. I am going to try and finish the tutorial, I will be back soon with results. Thanks.

The phone is in download mode with Heimdall One-click 1.3.1 running and nothing is popping up in the command window. Neither is showing that the device is connected. Any suggestions? Thanks

Irish Enigma said:
I second this... This should fix your driver issues.
Click to expand...
Click to collapse
I forgot to mention that I can here the sound that a device was just connected to the computer via USB, and a message pops up saying USB device not recognized. When I click on the message it says "One of the USB devices connected to this computer has malfunctioned, and Windows does not recognize it."

Tried a different port? Tried second different port with a different USB cable?

itzik2sh said:
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
Click to expand...
Click to collapse
Theraze said:
Tried a different port? Tried second different port with a different USB cable?
Click to expand...
Click to collapse
Ok I got the device connected and I got Zadig running, however, there is no option for "Samsung USB Composite Driver" on the drop down list, on "gadget Serial", "Gadget Serial Control (interface 0), and "1.3 HD Webcam (Interface 0)'. What should I do?

On the one-clicks, you don't actually want to use zadig. Apparently it conflicts, which is awesome for something that gets released WITH the tool.
If you're doing manual Heimdall, make sure you've told zadig to list all devices in the menus. Your phone should show up after that.
If you're using a one-click, make sure you're using a USB port on your computer where you have NOT installed zadig, Kies, or Samsung official drivers. Follow the steps in the one-click religiously, and it should cooperate.

Follow the guide %100 then Odin should work
Sent from my HTC One X+ using xda app-developers app

Ok I ended up getting the phone to register in Odin. I flashed it with the stock rom in Odin and it said success. The phone booted and it seemed like it was going to work but then the recovery menu came up. I posted a screen shot of what it says, what action should I take from here? Thanks

I am also in a different boot loop now, before it would load to the first screen (black screen saying samsung galaxy 4g) then restart, now it boots to past the splash screen to where it says "Samsung" and then reboots back to the screen where the pink letters roll across the whole screen. I don't need to flash bootloaders do I?

Looks like recovery is broken or the updater script on the ROM you're trying to flash is messed up. Flash a new and the proper recovery via Odin then download a new Rom and either sideload it or mount usb from recovery and push it... Or you could just use Odin XD
EDIT: Samsung's are easy to brick and hard to debrick it may take a couple of trys
Sent from my HTC One X+ using xda app-developers app

Irish Enigma said:
Looks like recovery is broken or the updater script on the ROM you're trying to flash is messed up. Flash a new and the proper recovery via Odin then download a new Rom and either sideload it or mount usb from recovery and push it... Or you could just use Odin XD
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
OK GREAT NEWS! After flashing with Odin and that screen popping up, I clicked update from SD card, which failed. I then click system reboot, which brought me into the new boot loop. I put back into download mode and re-flashed with One-Click. Same recovery menu came up as before but when I clicked reboot system it hung at the "Samsung" black screen (after the splash screen) for about 20-30 seconds and then booted up I'm afraid to turn the phone off and see if it reloads lol. Is it safe to say that it is fixed? Or should I still follow your advice and run the proper recovery in Odin and then sideload a new rom? Or take different action? Thanks for all your help guys! Everyone gets a thanks click for being so helpful and friendly on an unhappy/confused/pissed off/ now happy new Android user!

Ok I just put my Tmobile simcard in and the phone is not detecting the sim. Any suggestion?

The IMEI number and baseband both say "unknown", I'm assuming this has to do with the simcard not registering?

hubbs134 said:
The phone is in download mode with Heimdall One-click 1.3.1 running and nothing is popping up in the command window. Neither is showing that the device is connected. Any suggestions? Thanks
Click to expand...
Click to collapse
What Heimdall package are you applying ?
After JAR package runs you are ready to go.
As I wrote, according to guide you can reinstall "Gadget" driver.
EDIT :
Enigma, if you're not an owner of an SGS 4G please stop advising.
Odin is not the common way since we have MTD ROMs and it had its problems.
hubbs134,
blank IMEI is a serious problem. without a proper IMEI your device is everything but a phone.
Try this : take battery off, press the POWER button for 10 seconds, leave device untouched for 15 minutes and then put battery back and power up.
This could bring your IMEI back to life. If not... maybe another flash will help.
P.S
The 3e recovery image you put on post #14 is a snapshot of the the stock unrooted ROM recovery.

Atrix 2 not recognized by computer after brick, RSD/fastboot still works fine.

Here's the rundown on what happened:
1. Flashed SlimKat after using Cyanogen11 for a while.
2. The phone softbricked when I installed slim gapps.
3. I was dumb and was doing this on relatively low battery, so I couldn't use fastboot to reflash.
4. I built a motorola factory cable and reflashed InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml (ATT 4.0.4) via RSD and fastboot.
5. RSD works just fine, but instead of getting to the "Finished" step, it always says "manually power on phone" when the phone is already on the welcome screen. I suspect this is because the computer won't recognize the phone and therefore RSD doesn't know that it has a phone connected to it.
6. The phone charges from the computer, but does not recognize data connection. Says "USB not recognized" on my computer when I reboot phone.
Here's what I've tried:
1. Uninstalled/Reinstalled all motorola drivers on my computer
2. Reflashed using RSD
3. Turned on USB debugging
4. Tried all 3 USB modes under Storage->USB Connection Type
5. Tried 3 different usb cables as well as different usb ports on my computer, to no avail.
I'm stuck. Help please.

Well u didn't happen to try another computer did u?

jdog1989 said:
Well u didn't happen to try another computer did u?
Click to expand...
Click to collapse
Hi, yeah, I tried to edit that in, but I had to wait out the 5 minute timer. I have tried it on 2 other computers, no dice.

But ur phone works correct?

jdog1989 said:
But ur phone works correct?
Click to expand...
Click to collapse
Yeah, it works fine. It has stock 4.0.4 and is not rooted.
I'd like to be able to root and go back to CM11, but don't know how to do that if I can't connect to PC.

Google which "one-click root" app works for it. I think framaroot works but don't quote me on that. There is always a work around for that

jdog1989 said:
Google which "one-click root" app works for it. I think framaroot works but don't quote me on that. There is always a work around for that
Click to expand...
Click to collapse
I normally use one click root to root, but it doesn't work unless the computer recognizes there is a phone connected to it, which mine does not.

Try framaroot. Its an app

Doesn't work on my device

Try gaining root thru terminal

jdog1989 said:
Try gaining root thru terminal
Click to expand...
Click to collapse
I have no idea how to do that...

Google man, google.

Since your fastboot still works fine., you can try this fastboot method to gain root
http://forum.xda-developers.com/showthread.php?t=2093923
but you should be on JB leak to do this..
good luck ..