[HELP]Getting a custom recovery and rom on Galaxy S2 Plus I9105P - Samsung Galaxy S II Plus

Hey guys,
I got my hands on a somewhat old Galaxy S2 Plus GT-I9105P. Decided it was long overdue for some help so I decided to install a custom recovery (CWM) and in turn a custom rom in order to breathe some new life into it. Searched around xda and I found a very basic and easy-to-follow guide on how to install a custom recovery on my phone (Talking about this one over here : http://forum.xda-developers.com/showthread.php?t=2663834 ). I basically followed every single step 1 to 1 with the guide until I got to a problem. The .exe file I had downloaded through the provided link for Odin gave an error in Chinese and it mentioned an .ini file. Couldn't find it so I turned to a newer version of Odin. So far so good. Boot up my phone in Download Mode, plug it up to my pc, drivers start to install and bam, would you have guessed it, the drivers failed to install. I turned to google to find the suitable drivers for my device. Downloaded them, installed them, and when in Download Mode the PC recognized the device properly, no errors , no nothing. I open up Odin ( the newer version I downloaded [3.10.7]) and I see the device being recognised, showed up in a blue box. I go to locate my desired recovery file, add it and uncheck the boxes I was told to. Basically I've been doing things 1 to 1 with the instructions on the post. I click on Start and the thing sits on Localising connection or something of that sort not really sure. It stayed there for awhile until I decided to try again. This time I downloaded an older version of Odin I saw in the youtube video, which beegee had linked to. This time things go a bit further, as far as I can tell, and then BAM a big red FAIL. The error was "complete(write) operation failed". Tried with a few different versions of Odin and a few different driver versions as well but no luck.
After some head scratching I decided to turn to linux, but since I am not that savy with the environment I followed a guide which led me to installing the SDK for Android. I noticed that the only thing that it would lead me to would be to root my phone so I ditched it and found a linux alternative to Odin called Heimdall. Installed it but I currently have no idea how to properly operate it.
If any bright individual knows a solution to my problem, please do share as I am in need.
Thanks,
VoidViper

bump.

Related

“Firmware upgrade encountered an issue” when using Heimdall

Howdy folks!
I am working my way through a minor (?) technical difficulty.
Would appeciate any suggestions you folks can off this newbie along the way.
Earlier today, I made an absent-minded mistake. Tried to go to my stock Froyo kernel without undoing my voodoo/lagfix/ext/watchamacallit setup. Whoops. Bootloop. No recovery mode available.
So, I attempted to use the procedure described in [ROM] [2.3.6] Heimdall One-click Back-To-Stock UCLB3 here:
http://forum.xda-developers.com/showthread.php?t=1524081
I’m in Windows 7.
I right-clicked on the Heimdall one-click program (Stock_SGH_I997_UCLB3_Repartition-One-Click), but there was no option to run as administrator. So I just double clicked it and it opened it (deviated from instructions on the first step...oh oh).
With the Heimdall one-click program now open, I put my phone in download mode and it indicated connected (perhaps in retrospect I connected too early)
I followed instruction on the PC program to install drivers, which it did (I already had Samsung drivers installed that I used successfully for SOC root program and for EFS Pro, I’m not sure what it was installing).
The pc program told me it needed to reboot. The phone screen said something about “dont’t shut off...”. I wasn’t sure what to do at that point, so I granted the pc permission to reboot.
PC rebooted, phone remains attached the whole time
Upon reboot, the Heimdall one-click program did not start up again.
So I double-clicked it and started it again.
The phone remained attached, but was not recognized as connected by the pc one-click program.
So I pushed 3 buttons on the phone to get it to turn off, then removed the batteries.
.
Then started pc Heimdal one-click program again. Then put my phone in download mode which it did successfully.
Then ran the flash and go the message “The FACTORYFS upload failed!”
(This occurred run without the checkbox about bootloaders)
At that point I checked the checkbox about bootloaders, and it came up with some scarey warning so I didn’t flash (probably should have).
I once again deenergized the phone (three-buttons, remove battery during the brief period it’s deenergized). Shut down pc heimdall one-click program.
Then started pc heimdall program.
Tried to put phone into download mode and received the following inauspicous message:
“Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again”
Deenergized phone again. Shutdown pc program. Powered PC off. Restarted pc. Restarted Heimdall one click.
Tried to put the phone in download mode again and got the same error message.
I don’t know anything about selcting recover mode, not sure how to follow that instruction (any ideas?).
What I did next was search for the error message. It apparently has not been reported in the Infuse section, but I found two threads with this message discussed in the Galaxy S2 section.
“help” is the title of the first
http://forum.xda-developers.com/showthread.php?t=1189473
“Firmare upgrade encountered an issue - Am i done for?” is the title of the 2nd:
http://forum.xda-developers.com/showthread.php?t=1386232
There may be some more out there...
What I gathered was that I needed to remove my drivers.
I did remove the Sansung USG drivers in my control panel. I think these are the one’s I already had installed prior to me SOC root.
Rebooted.
Reinstalled drivers (filename SGH-i997_Infuse4G_USB_Drivers_5_2_0_2)
Restarted Heimdall one-click.
Put phone in download mode.
The same error message indicating that my phone has “issues”
Uninstalled my Samsung USB driver again.
Went back and looked at my control panel, there is another program. Keis. Uninstalled that. Rebooted.
Reinstalled SGH-i997_Infuse4G_USB_Drivers_5_2_0_2 driver
Reinstalled Kies_Mini_For_Captivate_11011_4.exe
Rebooted
Started the Heimdall one-click program.
Put phone in download.
Get the same error message on the phone (firmware upgraded encountered an issue...).
PC at this time thinks the phone is “connected”. So I clicked flash.
It proceeds to the next screen for driver installation.
I selected options / all / Samsung usb / Replace
PC Error message: Driver installation failed.
From those other threads, I’m pretty sure if I get my drivers straightened out I’ll be all right.
I don't know what I did wrong with the drivers... if anyone has a link with concise instructions for uninstalling/reinstalling the required drivers, maybe that would help me see if I've done something wrong.
Any other suggestions?
My java version is Version 6 Update 25
I have made a couple of change to this, a post I did for someone else today. You have done an excellent job of trying to resolve this- I hope this will be helpful.
There are a couple of things to point out:
Get Kies off your computer - it is a source of problems. Also means delete from recycle bin if there.
Download the Infuse drivers from bigjoe's ISET here: http://d-h.st/sKF
Thanks to bigjoe for an amazing page of resources !!
Be sure you have the latest version of Java here: http://www.java.com/en/download/index.jsp
Follow qkster's instructions he provides here:http://forum.xda-developers.com/showthread.php?t=1524081
Post 1 gets you back to stock- Post 2 gets root back.
Big thanks to qkster for doing this - saved many phones for countless number of users !! Me alone over a million times and counting
A video- no academy award nomination, but can be helpful : http://www.youtube.com/watch?v=sHyY7WHx4zc
Video is returning to Gingerbread.
You are willing to learn - therefore there will be many who are willing to help.
Take your time- do it right once and it will be easy next time !!
Heimdall uses it's own driver.
Once you install heimdall on one USB port of your pc, reserve that 1 port for going back. Also good to use that same USB cord.
The first part where it failed was because of bad connection. You just needed to change USB cord or change the port.
Read the heimdall thread and the how to thread a few times...
You could also use the froyo heimdall i put together for ucke3..see my sig link
Thanks very much for the replies.
Updated java.
Uninstalled Kies and Samsung driver (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2)
Rebooted.
Reinstalled Samsung driver from bigjoe's link (same file).
I think it asked me to reboot.
Started the PC Heimdall program.
Attempted to put phone in download mode, it says "Firmware upgrade encountered an issue....".
So phone is not recognizing PC.
But PC recognizes the phone as connected.
Press flash. It goes to next page... I list all drivers, there is nothing Samsung in there.
Disconnected phone. Shut down program. Removed drivers/rebooted / reinstalled Samsung driver
Started Heimdall.
Attempted download mode, same error message "Firmware upgrade encountered an issue..."
Tried flash anyway, the next screen list of devices still has no Samsung.
Oddly when I go back to the first pc screen and try plug/unplug the phone, the PC recognizes phone as connected/disconnected. But it doesn't recognize it on the 2nd page where it tries to install the driver. And the phone has never successfully entered download mode since the first one or two tries...I get this "Firmware upgrade encountered an issue with yellow triangle screen every time since.
All above was on a single USB. I then tried on two other USB's same result. I may try another PC tomorrow night after work.
And will review the qkster's thread again as well as the video link posted by Pony Express.
Will report those results...
For now my head hurts . Time to call it a day.
Thanks for all your help.
I definitely appreciate it.
post deleted by op
meaning of this error message?
deleted
I see there is one other current thread in this forum on similar issue
"stuck on screen with (phone)---!----(Computer) "
http://forum.xda-developers.com/show...rch+this+forum
I noticed one thing we had in common is we both had Kies installed at some time early in our process (now removed).
I have some questions about the meaning of this screen that appears on my phone when I attempt to get to download mode:
"Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again"
The screen has a yellow warning triangle on it
Is that a common screen to see on your phone during this process ?
Does it represent download mode? (I don't think so, since I saw a different screen on my phone the first time I connected... but maybe that had something to do with Kies?)
Is there any point in even trying to flash/download drivers when I see that message?
If the opportunity presents itself, is it advisable to attempt flash with "download bootloaders checked" when this error message is present?
(* If these questions are answered by the video, then I apologize in advance. I don't have the opportunity to watch that video here from my work computer, but I am eager to get a head start so I can hit the ground running when I get home after work tonight).
electricpete1 said:
I see there is one other current thread in this forum on similar issue
"stuck on screen with (phone)---!----(Computer) "
http://forum.xda-developers.com/show...rch+this+forum
I noticed one thing we had in common is we both had Kies installed at some time early in our process (now removed).
I have some questions about the meaning of this screen that appears on my phone when I attempt to get to download mode:
"Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again"
The screen has a yellow warning triangle on it
Is that a common screen to see on your phone during this process ?
Does it represent download mode? (I don't think so, since I saw a different screen on my phone the first time I connected... but maybe that had something to do with Kies?)
Is there any point in even trying to flash/download drivers when I see that message?
If the opportunity presents itself, is it advisable to attempt flash with "download bootloaders checked" when this error message is present?
(* If these questions are answered by the video, then I apologize in advance. I don't have the opportunity to watch that video here from my work computer, but I am eager to get a head start so I can hit the ground running when I get home after work tonight).
Click to expand...
Click to collapse
For the moment don't check the bootloaders. You will only need them for ICS and JB to get rid of rainbows in the recovery. A bootloader flash is practically the only thing that can brick our phone.
Is that "firmware upgrade.." screen the one with the pc!phone? It has been a long time since I soft bricked so I don't recall if it said that somewhere.
If heimdall is giving you issues, try Odin and see how it goes there.
Sent from my sweet & buttery Infuse
electricpete1 said:
I see there is one other current thread in this forum on similar issue
"stuck on screen with (phone)---!----(Computer) "
http://forum.xda-developers.com/show...rch+this+forum
I noticed one thing we had in common is we both had Kies installed at some time early in our process (now removed).
I have some questions about the meaning of this screen that appears on my phone when I attempt to get to download mode:
"Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again"
The screen has a yellow warning triangle on it
Is that a common screen to see on your phone during this process ?
Does it represent download mode? (I don't think so, since I saw a different screen on my phone the first time I connected... but maybe that had something to do with Kies?)
Is there any point in even trying to flash/download drivers when I see that message?
If the opportunity presents itself, is it advisable to attempt flash with "download bootloaders checked" when this error message is present?
(* If these questions are answered by the video, then I apologize in advance. I don't have the opportunity to watch that video here from my work computer, but I am eager to get a head start so I can hit the ground running when I get home after work tonight).
Click to expand...
Click to collapse
Yes...that's represents download mode...just another form...heimdall should still work
Sent from my SGH-I997 using Tapatalk 2
Thanks to everyone. That is very helpful.
I have some more questions. I'm not trying to be nit-picky, but just want to make sure I understand exactly what is being said.
qkster wrote:
Heimdall uses it's own driver.
Click to expand...
Click to collapse
Does that mean we don't need the Samsung driver SGH-i997_Infuse4G_USB_Drivers_5_2_0_2 driver ?
Any guess whether it works better with or without it? I will definitely try without it, but if anyone knows a preferred configuration, that would be helpful so I can focus on changing other things.
qkster's how to:
2. If you have not used Heimdall, you will need to set up the driver for device recognition
Click to expand...
Click to collapse
As a clarification. I'm not sure precisely what that means. All I'm doing is starting the program, letting it load drivers on first screen, connecting the phone in download mode (with error screen), pushing flash which will hopefully get me to the 2nd screen where I select options/all/Samsung/Replace to set up the driver. Is this statement intended to say anything different?
qkster's how to:
6. If it did not work, you will have to put it back into DOWNLOAD mode and reflash a second time, with the FLASH BOOTLOADER box checked.
Click to expand...
Click to collapse
I take it that in my situation (with error message and no evidence of success in previous flashing, and going to GB) this is really only a last resort after all other options exhausted as per andros' suggestion above?
By the way, I'm going to keep trying to install the UCLB3 GB (vs Froyo), as long as the chance of success is the same on both.
qkster's how to
4. Click on the FLASH button. (In my opinion: I recommend that you do this in a safe environment. Do not disturb your phone will flashing this firmware. Turn off Antivirus. Do not run any other programs, upload/download/youtube/burning DVD etc)
Click to expand...
Click to collapse
I'm a little nervous about turning off my security program (a/v, firewall etc) since I haven't done that in years.
Have there been problems attributed to doing this with security enabled, or is it just a general suggestion to avoid interruptions from unexpected scans or pop-ups etc? (my security runs peacefully in background and never interrupts me unless I ask it)
If it's really necessary to disable security program, I'd feel better about keeping my internet disconnected for the duration that the anti-virus is off. Is there any problem created if the internet connection remains disconnected for the duration of this process?
electricpete1 said:
Thanks to everyone. That is very helpful.
I have some more questions. I'm not trying to be nit-picky, but just want to make sure I understand exactly what is being said.
Does that mean we don't need the Samsung driver SGH-i997_Infuse4G_USB_Drivers_5_2_0_2 driver ?
Any guess whether it works better with or without it? I will definitely try without it, but if anyone knows a preferred configuration, that would be helpful so I can focus on changing other things.
As a clarification. I'm not sure precisely what that means. All I'm doing is starting the program, letting it load drivers on first screen, connecting the phone in download mode (with error screen), pushing flash which will hopefully get me to the 2nd screen where I select options/all/Samsung/Replace to set up the driver. Is this statement intended to say anything different?
I take it that in my situation (with error message and no evidence of success in previous flashing, and going to GB) this is really only a last resort after all other options exhausted as per andros' suggestion above?
By the way, I'm going to keep trying to install the UCLB3 GB (vs Froyo), as long as the chance of success is the same on both.
Click to expand...
Click to collapse
Drivers: when you launch heimdall it will install its own custom drivers for whatever usb port its pluged into...so if you plug it into one of your ports in the front and run heimdal only the port the phone is currently plugged into will be effected by the new driver. the driver is only used when in download mode...so dont uninstall your current drivers
selecting device: i think you got it (if my memory is correct...) just launch and run heimdall with device connected in dl mode...when you get to installing drivers just go to options and choose list all...i cant remember the exact name the infuse shows up as though
Bootloaders: just flash the first time without it checked...if it doesnt go through then check it and flash again
Antivirus: i have never turned off my anti virus when using heimdall on any of my computers (one computer uses norton 360 premier, the other one uses avast free) i never had it conflict with the process...so just leave it on for now...and only turn it off if you are having problems...if your worried about viruses then disconnect from the internet when you turn off your anti virus -i dont think the heimdall relies on internet at all...well maybe for the drivers...so just dont turn anything off until after you get the drivers
EDIT: i have a frseh install of windows 7 on my dev computer that i havent used heimdal on yet...so ill run it and clarify the driver section...i dual boot both linux and windows...currently im near the end of a repo sync so as soon as that finishes ill boot into windows and run heimdal...in less then a half hour hopefully...
Thanks mg2195.
Very good info.
I have tried my Windows 7 PC and another windows Vista PC.
On both pc's I tried with drivers pre-installed on the pc and without. Reboots in between.
I also used two different cables and tried all usb ports that were available.
In all cases but one, the anti-virus/firewall was on and pc connected to internet
In one case I tried with anti-virus off and pc diconnected from internet.
In all cases (except for the first one or two at the beginning of this thread), here's what happens:
I start Heimdall, it takes me to the first Heimdall screen, which shows "device status" red/disconnected as expected.
I try to put phone in download. Get the error message screen on the phone (see subject line). The "device status" shown on the pc changes from red/disconnected to green/connected (as expected).
I Click flash.
It asks to run the program, I say ok, it takes me to the second Heimdall screen, where I select Options/List-all.
There is no samsung driver choice.
I close the selection window (click x in upper right hand corner), it takes me back to the first Heimdall screen.
Device status still shows green/connected on the first Heimdall screen.
If I press flash again, the experience at the second screen repeats without showing Samsung driver.
Before I go to the next configuration (next usb port or cord or whatever), I remove the phone and close out the Heimdall program.
The bootloader option is available to be checked in the first Heimdall screen, but I have not done it
I’m not sure if I explained before that I have not had a successful driver installation in that second Heimdall screen (since the first one or two attempts). Does this change fact change your suggestion about checking the flash bootloaders box?
electricpete1 said:
Thanks mg2195.
Very good info.
I have tried my Windows 7 PC and another windows Vista PC.
On both pc's I tried with drivers pre-installed on the pc and without. Reboots in between.
I also used two different cables and tried all usb ports that were available.
In all cases (except for the first one or two at the beginning of this thread), here's what happens:
I start Heimdall.
Try to put phone in download. Get the error message screen.
Click flash in the first Heimdall screen.
It asks to run the program, I say ok, it takes me to the second Heimdall screen, where I select Options/List-all.
There is no samsung driver choice.
I close the selection window (click x in upper right hand corner), it takes me back to the first Heimdall screen.
The bootloader option is available to be checked in the first Heimdall screen, but I have not done it.
I’m not sure if I explained before that I have not had a successful driver installation in that second Heimdall screen (since the first one or two attempts). In this circumstance, do you still think it’s ok to check bootloaders?
Click to expand...
Click to collapse
you should probably wait until you get the heimdal drivers installed...im still wating for my reposync to finish...for some reason the download slowed down to 200kb/s,,,so it could take a while...
but for the drivers do this
1) On the menu bar (Device,Options,Help) Click Options --> List All Devices
2) Under USB Device select “Samsung USB Composite Device”
if its not locating it then try differnt ports/cables...if still no then run as admin...rightclick or shift+rightclick...if still not showing up...maybe bad usb port on the phone?
Quick response... thanks again!
Bad usb on phone is certainly possible, but I've never had a problem with it before.
I can believe the pc usb port might be finicky. Because historically on my Windows 7 PC, every once in awhile when I insert a flash drive memory stick, it does not get recognized. I will see if I can try a 3rd computer.
Regarding "run as administator":
When I right-click on the file, I don't see any option for "run as administrator" in either my Windows 7 pc or my Windows Vista pc.
So I have just been double-clicking the file. I think the Windows Vista asked me if I trusted the program and I said yes. Windows 7 just launches it.
Maybe there's some setting I need to change somewhere in order to get this "run as administator" ....I will google that... tomorrow. Right now, my pillow awaits.
electricpete1 said:
Quick response... thanks again!
Bad usb on phone is certainly possible, but I've never had a problem with it before.
I can believe the pc usb port might be finicky. Because historically on my Windows 7 PC, every once in awhile when I insert a flash drive memory stick, it does not get recognized. I will see if I can try a 3rd computer.
Regarding "run as administator":
When I right-click on the file, I don't see any option for "run as administrator" in either my Windows 7 pc or my Windows Vista pc.
So I have just been double-clicking the file. I think the Windows Vista asked me if I trusted the program and I said yes. Windows 7 just launches it.
Maybe there's some setting I need to change somewhere in order to get this "run as administator" ....I will google that when I get a chance.
Click to expand...
Click to collapse
Did you try holding shift while right clicking?
Sent from my SGH-I997 using Tapatalk 2
electricpete1 said:
I take it that in my situation (with error message and no evidence of success in previous flashing, and going to GB) this is really only a last resort after all other options exhausted as per andros' suggestion above?
Click to expand...
Click to collapse
Thanks for pointing out the imprecise grammar, Pete.
I corrected the op.
Recheck step 6 and 7.
To get heimdall to install its drivers, Zadig, you need the initial Samsung Android drivers. so when you pull down the zadig menu, Samsung Adroid device should show up.
Then reboot the PC.
Then try connect in dl mode again.
You had it at some point...
Thanks all.
That is now very clear qkster. (Actually it was reasonably clear before and I was pretty sure I knew what you meant, but just wanted to double check in case I was misunderstanding something)
I've had some trouble running as administrator, apparenlty others don't
Here's my difficulties and how I resolved it (I think):
DIFFICULTIES IN RUN-AS-ADMINISTRATOR.
If I right-click on an executable file (anything.exe), I get option to run as administrator. Great.
If I right click on a jar file (like the one I'm trying to run), no such option. Sad.
Same thing with short-cuts.
If I right-click on shortcut to exe, I can choose compatibility tab and select run as administrator. Great.
If I right-click on shortcut to jar, there is no compatibility tab. Sad.
HOW I RESOLVED RUN-AS-ADMINISTRATOR (I think)
I found some instructions for specifically for running jar as administrator here:
http://stackoverflow.com/questions/...r-with-administrators-privileges-on-windows-7
Specifically, click start, type cmd in the window just above start, right-click on the cmd result, and click "run as administrator.
That takes you to an elevated command prompt with the word administrator in the window heading.
Navigate to the directory and type
java -jar myfile.jar
where myfile is your file name (I renamed it to shorter name to make it easier).
RESULT:
I was able to launch Heimdal from the elevated command prompt.
Unfortunately, results have been the same thus far when using Heimdall launched from elevated command prompt as the previously reported results.
QUESTION: is there any way to check the program truly has admin priveleges?... it didn't ask any permission when launching Heimdall from the elevated command prompt.. the only permission asked was when launched cmd from the windows start menu screen.
I will repeat a few of yesterdays trials.
If those are unsuccessful, I think next step is trying GTG's package with ODIN.
QUESTION: Is there any way to clear any settings loaded into the USB ports by the Heimdall so they don't interfere with ODIN?
For Odin, just install the drivers you see at the iset page or kies drivers.
If you had a pc, one user when you log on, it is auto assume admin.
You can also go to control panel, users, look at privileges

[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.

Is my phone dead?

I tried to upgrade to Android on the phone as written here
http://forum.xda-developers.com/showthread.php?t=1601844
After first step when installed the firmware from zip and going back into recovery mode I can only see this (picture attached).
Tried to reboot in CVM or regular, it won't go any further.
If I place it in download mode the Odin won't see it. (Installed Kies 3 to have the drivers).
What else can I do and make it work?
Thx
http://forum.xda-developers.com/showthread.php?t=1524081&page=33
qkster said:
http://forum.xda-developers.com/showthread.php?t=1524081&page=33
Click to expand...
Click to collapse
Actually I could fixed it, the point Odin didn't see it was because the drivers for USB samsung weren't installed properly by Kies under Win 8 x64, so I went into Device Manager and installed by hand.
After that Odin saw the phone, and from there it was a piece of cake to solve it.
I had some other couple of issues with the correct JB installation for it, after a couple of rounds of restoring everything via Odin I finally had success with this build http://forum.xda-developers.com/showthread.php?t=2130816 which for some reason was the last on my list to try. But it works pretty well.

N8010 Problems

Hi,
Figured id start off by explaining the history on my Samsung Note N8010
A while back i installed Hyperdrive Rom RS8 (i think), no problems, flawless. However it did change my device id to an N8013, not sure why.
Recently i wanted to use SkyGo Tablet app, however root cloak and Voodoo does not cloak SkyGo Tablet app on this specific rom so i figured id revert back to the original 4.1.2 stock.
I used Mobile Odin, grabbed the zip/tar from the Sam-mobile and hit go.
On reboot, it would not load in, stuck on the Samsung Note 10.1 splash. I do have access to download mode and recovery mode, but it's labelled Android System Reocvery <3e>.
It is worth noting that USB debug did not work on Hyperdrive, so currently no matter what computer i connect this tablet to Odin, Kies or anything will not see it.
When trying to "apply update from sd card" i get E:\ mount problems, it pretty much fails every time.
Any suggestions?
kitchenspoon said:
Hi,
Figured id start off by explaining the history on my Samsung Note N8010
A while back i installed Hyperdrive Rom RS8 (i think), no problems, flawless. However it did change my device id to an N8013, not sure why.
Recently i wanted to use SkyGo Tablet app, however root cloak and Voodoo does not cloak SkyGo Tablet app on this specific rom so i figured id revert back to the original 4.1.2 stock.
I used Mobile Odin, grabbed the zip/tar from the Sam-mobile and hit go.
On reboot, it would not load in, stuck on the Samsung Note 10.1 splash. I do have access to download mode and recovery mode, but it's labelled Android System Reocvery <3e>.
It is worth noting that USB debug did not work on Hyperdrive, so currently no matter what computer i connect this tablet to Odin, Kies or anything will not see it.
When trying to "apply update from sd card" i get E:\ mount problems, it pretty much fails every time.
Any suggestions?
Click to expand...
Click to collapse
The original issue is probably one of two things. If you downloaded the rom directly to your device its Likely a bad download. DID YOU CHECK MD5 Before flashing. There are also limitations to Mobile odin.
What i would suggest is to uninstall Kies . Make sure you have no other android devices installed on your computer .Download the older version again from Samsung website. Install on your computer. Download odin again i think you want the one a version back as well NOT Latest.
Reboot into download mode. Run odin. if it still does not see your device check Device manager and see if its showing up with a yellow mark. Look for a post i made last week explaining how to correct usb driver for windows.. Download mode should work with out usb debug on if i remember correctly..
erica_renee said:
The original issue is probably one of two things. If you downloaded the rom directly to your device its Likely a bad download. DID YOU CHECK MD5 Before flashing. There are also limitations to Mobile odin.
What i would suggest is to uninstall Kies . Make sure you have no other android devices installed on your computer .Download the older version again from Samsung website. Install on your computer. Download odin again i think you want the one a version back as well NOT Latest.
Reboot into download mode. Run odin. if it still does not see your device check Device manager and see if its showing up with a yellow mark. Look for a post i made last week explaining how to correct usb driver for windows.. Download mode should work with out usb debug on if i remember correctly..
Click to expand...
Click to collapse
Hi, cheers for the response,
I have tried all of what you have said but unfortunately no PC will see my device, not even an "unrecognized device". I have access to android system reocvery <e3> and Download mode (Odin) but the pc just won't recognized, tried new leads and so forth, nothing.

G930T stuck in recovery after reboot

I rooted my my few weeks ago with snapdragon root, and yesterday I realized that some apps kept crashing, so I rebooted my phone, but it stucks at Tmobile logo. So I opened up smart switch on my pc, tries to restore my phone, but it said that : SM-G930T does not support initializing. It's confusing since I restore using smart switch before, but I downloaded stock firmware from xda forum, and flashed with odin. And it shows sw rev check fail device 4, binary 3. And it boots in to recovery mode everytime I forced to restart. btw, it says dm-verity verification failed. What can I do to fix this? Thanks for any suggesions.
i had the same problem with my s7 SM-G930T
JokerCat233 said:
I rooted my my few weeks ago with snapdragon root, and yesterday I realized that some apps kept crashing, so I rebooted my phone, but it stucks at Tmobile logo. So I opened up smart switch on my pc, tries to restore my phone, but it said that : SM-G930T does not support initializing. It's confusing since I restore using smart switch before, but I downloaded stock firmware from xda forum, and flashed with odin. And it shows sw rev check fail device 4, binary 3. And it boots in to recovery mode everytime I forced to restart. btw, it says dm-verity verification failed. What can I do to fix this? Thanks for any suggesions.
Click to expand...
Click to collapse
I had the exact same problem with my phone which is the same model as yours, and after almost 2 days of surfing in the internet like crazy and trying all the diferent programs I found the solution.
1. first go to this video youtube,com/watch?v=RSZiVxJyFb4 (I cant post links so I will substitute the dot in "DOT COM" by a comma)
2.Download the firmware and Samsung drivers in the link in the video which is pangu.in/samsung_firmware.html skip thru the pages until you find your model(this link will download the drivers and a notepad with the link to the actual firmware download page which is sammobile,com/firmwares/
3. type the model number in the search bar (SM-G930T) and select the first one in the list and download it(note: you will need to create an account in this page in order to download the firmware but its only put your email and choose a password so it shouldn't be a problem. extract the firmware after downloaded.
4.Download the version of odin that is linked in the video link: pangu.in/odin_tool.html . Scroll down a lil bit and download the one that says "ODIN 3.11 (GALAXY S7)"HAS TO BE THIS ONE other versions wont work. extract it.
5.After you have downloaded everything(make sure you installed the drivers if you haven't done before) proceed to run ODIN with your phone unplugged from your pc and turned off
6.Load the AP file from the extracted firmware file into the AP tab you will see in ODIN(do all this with your phone UNPLUGED from the PC.
7.Now put your phone(which should be off and disconnected from the PC) into download mode[hold vol down+home+pwr button
then you will be aske to press button up to continue, do so(you probably know how to do this but I said in case other people don't)
8.connect your phone onto your pc and you should see your device show up in odin, now click start and you should be good to go
I hope it works for you since I know how frustrating it is to have such and expensive phone bricked.
juanernestous said:
I had the exact same problem with my phone which is the same model as yours, and after almost 2 days of surfing in the internet like crazy and trying all the diferent programs I found the solution.
1. first go to this video youtube,com/watch?v=RSZiVxJyFb4 (I cant post links so I will substitute the dot in "DOT COM" by a comma)
2.Download the firmware and Samsung drivers in the link in the video which is pangu.in/samsung_firmware.html skip thru the pages until you find your model(this link will download the drivers and a notepad with the link to the actual firmware download page which is sammobile,com/firmwares/
3. type the model number in the search bar (SM-G930T) and select the first one in the list and download it(note: you will need to create an account in this page in order to download the firmware but its only put your email and choose a password so it shouldn't be a problem. extract the firmware after downloaded.
4.Download the version of odin that is linked in the video link: pangu.in/odin_tool.html . Scroll down a lil bit and download the one that says "ODIN 3.11 (GALAXY S7)"HAS TO BE THIS ONE other versions wont work. extract it.
5.After you have downloaded everything(make sure you installed the drivers if you haven't done before) proceed to run ODIN with your phone unplugged from your pc and turned off
6.Load the AP file from the extracted firmware file into the AP tab you will see in ODIN(do all this with your phone UNPLUGED from the PC.
7.Now put your phone(which should be off and disconnected from the PC) into download mode[hold vol down+home+pwr button
then you will be aske to press button up to continue, do so(you probably know how to do this but I said in case other people don't)
8.connect your phone onto your pc and you should see your device show up in odin, now click start and you should be good to go
I hope it works for you since I know how frustrating it is to have such and expensive phone bricked.
Click to expand...
Click to collapse
Thanks alot! I fixed it somehow, I reflash the root ap file, and it works
I never EVER post in these chats/forums, but you, whoever you are, you are a life saver. Thank you, THANK you, THANK YOU so much. it worked like a charm on my t-mobile SM-G930T

Categories

Resources