Related
Hello guys, I'm a mac (OSX 10.7.3) user and would like to install ICS on my SG9100. Does anyone knows a trustworthy tutorial that suites my needs?
Thanks in advance.
Unfortunately the easiest way is to use a PC and update through Kies, although Kies can be a pain to use also. The other option is to root and flash an ICS ROM.
There are various ways to do this, all which are explained throughout the forum.
Hey,
first, there's Kies for Mac...
http://www.samsung.com/uk/support/usefulsoftware/KIES/JSP
It suppose to provide firmware updating if your device has been intact (you got it without custom rom / rooted).
secondly,
there is Heimdall which is open source alternative that should be able to flash roms. though I must admit your easiest solution is PURE bootcamp (no parallels/virtualization) and ODIN if your not going the 100% samsung way.
I was going to suggest Kies for Mac but the mac version does not appear to support firmware upgrades, so I had to borrow a friends PC. I then went ahead and rooted and Flashed a vanilla ICS, but that's by the by.
Hi Guys,
Long-time listener, first-time caller..
I have a feeling I’ve broken my HTC One X+ [enrc2b] (UK Vodafone running CM10.2) due to a bad upgrade.
I had Cyanogen 10.2 installed and have been happily using and updating it via the built in CM update tool.
I went from stable to nightly a couple months ago and have never found any major issues so continued to use nightlies.
On Sunday (12th Jan) a new CM update was made available and I went through the usual process without really looking closely at the update. The update was for CM11. (Shouldn't matter? I've flashed new boot.img's before when required).
The update downloaded so the phone rebooted and went to flash, but failed halfway through due to a corrupt download.
I’m not sure if it was the file on the CM servers or if the download simply corrupted but I’ve never seen a similar issue and didn’t interrupt the update so I’m guessing it was a bad file uploaded for the update.
This is where it gets messy.
I had removed the previous update files so there are none available in the /cmupdate/ folder other than the CM11 version. If I had kept just one I wouldn't be in this situation (lesson learnt!).
My phone DOES NOT have USB debugging turned on, therefore I am not able to use ADB to push files to the device. Is there anyway to send files to the phone without using ADB. I'm pretty familiar with fastboot but can only flash recovery/boot using fastboot (?).
I’ve tried flashing the stock recovery so I can use the RUU for Vodafone UK but the RUU flsah fails. I’ve re-locked the bootloader and have the stock recovery but I get an error when using the RUU.
The RUU is v1.14 and my phone has v1.17 (from CM) so I suspect this is the problem as the version needs to be greater than the current?
The error from the RUU is related to the bootloader (error 140). I’ve tried a couple different versions of RUU such as a Europe one with v1.17 but it throws the wrong region code error when trying to flash.
I don’t have a nandriod back up. I thought I had done when I originally unlocked and rooted the phone. Turns out that it didn’t work.
I have downloaded a couple nandriods that I think would work but because I don’t have ADB working I can’t push the files to the device anyway.
I have CWM recovery installed again now, after the failed RUU update, and a version of hboot (that’ll check when I get home). I think it’s 1.400?
So, is my phone save-able, or is it now a paperweight. Any and all help appreciated.
A lot of the posts relating to fixing similar issues assume you have ADB/USB debug available, and I don’t! I have done a lot of reading over the past couple of days but am no closer to resolving this.
In case it helps, I can grab the zips from the RUU temp folder but wouldn't know how to flash them (does it need ADB?).
Can anyone help?
max3o6 said:
Hi Guys,
Long-time listener, first-time caller..
I have a feeling I’ve broken my HTC One X+ [enrc2b] (UK Vodafone running CM10.2) due to a bad upgrade.
I had Cyanogen 10.2 installed and have been happily using and updating it via the built in CM update tool.
I went from stable to nightly a couple months ago and have never found any major issues so continued to use nightlies.
On Sunday (12th Jan) a new CM update was made available and I went through the usual process without really looking closely at the update. The update was for CM11. (Shouldn't matter? I've flashed new boot.img's before when required).
The update downloaded so the phone rebooted and went to flash, but failed halfway through due to a corrupt download.
I’m not sure if it was the file on the CM servers or if the download simply corrupted but I’ve never seen a similar issue and didn’t interrupt the update so I’m guessing it was a bad file uploaded for the update.
This is where it gets messy.
I had removed the previous update files so there are none available in the /cmupdate/ folder other than the CM11 version. If I had kept just one I wouldn't be in this situation (lesson learnt!).
My phone DOES NOT have USB debugging turned on, therefore I am not able to use ADB to push files to the device. Is there anyway to send files to the phone without using ADB. I'm pretty familiar with fastboot but can only flash recovery/boot using fastboot (?).
I’ve tried flashing the stock recovery so I can use the RUU for Vodafone UK but the RUU flsah fails. I’ve re-locked the bootloader and have the stock recovery but I get an error when using the RUU.
The RUU is v1.14 and my phone has v1.17 (from CM) so I suspect this is the problem as the version needs to be greater than the current?
The error from the RUU is related to the bootloader (error 140). I’ve tried a couple different versions of RUU such as a Europe one with v1.17 but it throws the wrong region code error when trying to flash.
I don’t have a nandriod back up. I thought I had done when I originally unlocked and rooted the phone. Turns out that it didn’t work.
I have downloaded a couple nandriods that I think would work but because I don’t have ADB working I can’t push the files to the device anyway.
I have CWM recovery installed again now, after the failed RUU update, and a version of hboot (that’ll check when I get home). I think it’s 1.400?
So, is my phone save-able, or is it now a paperweight. Any and all help appreciated.
A lot of the posts relating to fixing similar issues assume you have ADB/USB debug available, and I don’t! I have done a lot of reading over the past couple of days but am no closer to resolving this.
In case it helps, I can grab the zips from the RUU temp folder but wouldn't know how to flash them (does it need ADB?).
Can anyone help?
Click to expand...
Click to collapse
the phone when on recovery doesn't need the USB debugging to be turned on....
if u had installed the proper drivers u will be able to see ur phone as on recovery.....
[email protected] said:
the phone when on recovery doesn't need the USB debugging to be turned on....
if u had installed the proper drivers u will be able to see ur phone as on recovery.....
Click to expand...
Click to collapse
Hmm, ok thanks. Maybe I need to reinstall ADB drivers. The HTC USB drivers work ok (fastboot usb is fine) and I do have ADB installed but having meddled with it (reinstalled ADB) I should try pushing again I guess.
Thanks, will try when when home! :good:
ADB without USB debugging turn on
Now sorted!
ADB works when the phone is in recovery, not in hboot. Dur.
Thanks!
I have searched multiple threads and sites, however, I still haven't found someone that's had a similar problem to mine, so here it goes.
I have a Samsung Galaxy S III GT-I9300 and the Android version is currently 4.0.4 (More information about my device in the screenshots below)
I've been trying to update it to the latest Android version (Jellybean 4.3 I believe, since Kit Kat 4.4 is not yet available for Samsung Galaxy devices yet). However, whenever I try to do a Software update, it tells me "No update available". Someone suggested that I install the updates through Kies, and I did install Kies on my Mac (OS X 10.9.1), but it won't connect to my phone--as in, it will say "Connecting" for hours without ever connecting to the phone or it will say "Connecting" for a few seconds then tell me to "Please connect a device". I've checked with my phone, and it says "Connected as a media device" with the USB symbol to the left of it. I have also tried to unplug my USB cord, enable USB debugging mode, and plug it back into my Mac to no avail.
The phone is fairly new, I got it a couple of weeks ago from China. I believe that it is rooted since it had to be unlocked to work with US carriers (I'm on T-Mobile network), but at the same time I'm also not quite sure. The phone status says 'Modified', if that helps at all.
SuperSU is installed on my phone (I wasn't the one who installed it), but when I try to access the application, it tells me "There is no SU binary installed, and SuperSU cannot install it. This is a problem!
CWM Manager is also installed (v3.60), but it says "This version of CWM Manager should be used with CF-Root v5.0 or newer. It apepars you are running a different kernel. Various features have been disabled." I don't know what CF-Root is, and I don't think that it's installed on my phone either, since I can't find it in my Application Manager.
I installed an application called RootValidator from the Google Play store, and when I run it, it tells me "No, but you might have root as our request was denied. Did you deny root access? While you don't have a busy box, it is not required to root a device, some apps just need it." (See attachments for more information)
So now my questions are...:
Is my phone actually rooted or not? If it is, how can I grant or deny root access? (I want to download TitaniumBackup, but it requires root access, which I don't know how to give)
Since Kies isn't reading/connecting my device, how can I get Kies to connect to my phone?
And since my phone keeps on telling me "No update available" whenever I try to do a software update, I'm going to assume that I have to update my phone's firmware by using Kies. And if my phone is rooted/unrooted, but I can't connect to Kies, how can I update my Android 4.0.4 to the latest Jellybean 4.3 version?
Thank you for any help you can give!
wohuifei said:
I have searched multiple threads and sites, however, I still haven't found someone that's had a similar problem to mine, so here it goes.
I have a Samsung Galaxy S III GT-I9300 and the Android version is currently 4.0.4 (More information about my device in the screenshots below)
I've been trying to update it to the latest Android version (Jellybean 4.3 I believe, since Kit Kat 4.4 is not yet available for Samsung Galaxy devices yet). However, whenever I try to do a Software update, it tells me "No update available". Someone suggested that I install the updates through Kies, and I did install Kies on my Mac (OS X 10.9.1), but it won't connect to my phone--as in, it will say "Connecting" for hours without ever connecting to the phone or it will say "Connecting" for a few seconds then tell me to "Please connect a device". I've checked with my phone, and it says "Connected as a media device" with the USB symbol to the left of it. I have also tried to unplug my USB cord, enable USB debugging mode, and plug it back into my Mac to no avail.
The phone is fairly new, I got it a couple of weeks ago from China. I believe that it is rooted since it had to be unlocked to work with US carriers (I'm on T-Mobile network), but at the same time I'm also not quite sure. The phone status says 'Modified', if that helps at all.
SuperSU is installed on my phone (I wasn't the one who installed it), but when I try to access the application, it tells me "There is no SU binary installed, and SuperSU cannot install it. This is a problem!
CWM Manager is also installed (v3.60), but it says "This version of CWM Manager should be used with CF-Root v5.0 or newer. It apepars you are running a different kernel. Various features have been disabled." I don't know what CF-Root is, and I don't think that it's installed on my phone either, since I can't find it in my Application Manager.
I installed an application called RootValidator from the Google Play store, and when I run it, it tells me "No, but you might have root as our request was denied. Did you deny root access? While you don't have a busy box, it is not required to root a device, some apps just need it." (See attachments for more information)
So now my questions are...:
Is my phone actually rooted or not? If it is, how can I grant or deny root access? (I want to download TitaniumBackup, but it requires root access, which I don't know how to give)
Since Kies isn't reading/connecting my device, how can I get Kies to connect to my phone?
And since my phone keeps on telling me "No update available" whenever I try to do a software update, I'm going to assume that I have to update my phone's firmware by using Kies. And if my phone is rooted/unrooted, but I can't connect to Kies, how can I update my Android 4.0.4 to the latest Jellybean 4.3 version?
Thank you for any help you can give!
Click to expand...
Click to collapse
First of all, I suggest you reboot your device into download mode:
http://m.youtube.com/watch?v=1tdznfLJsyY
And check if the device info actually indicates its i9300 (just to be sure that you didn't fall into quality fake)
Second, (and I suggesting using a pc for following procedures) try to reinstall kies (make sure you aren't using kies3) and make sure your device is recognized as i9300. Most chances that you won't be able to update with kies, but samsung drivers are needed.
Third- you've got 2 options:
1- flash sumsung's newest official rom fron sammobile using this guide: http://forum.xda-developers.com/showthread.php?t=1671969
2- root your device using this guide:
http://forum.xda-developers.com/galaxy-s3#root
Than install this updated recovery: http://forum.xda-developers.com/showthread.php?t=2002953
If all goes well, you'll be able to install custom roms using the recovey. Like this awesome one: http://forum.xda-developers.com/showthread.php?t=2060403
Ps- if something isn't clear enough, feel free to ask.
Sent from my GT-I9300 using Tapatalk
amirTor said:
First of all, I suggest you reboot your device into download mode:
http://m.youtube.com/watch?v=1tdznfLJsyY
And check if the device info actually indicates its i9300 (just to be sure that you didn't fall into quality fake)
Second, (and I suggesting using a pc for following procedures) try to reinstall kies (make sure you aren't using kies3) and make sure your device is recognized as i9300. Most chances that you won't be able to update with kies, but samsung drivers are needed.
Third- you've got 2 options:
1- flash sumsung's newest official rom fron sammobile using this guide: http://forum.xda-developers.com/showthread.php?t=1671969
2- root your device using this guide:
http://forum.xda-developers.com/galaxy-s3#root
Than install this updated recovery: http://forum.xda-developers.com/showthread.php?t=2002953
If all goes well, you'll be able to install custom roms using the recovey. Like this awesome one: http://forum.xda-developers.com/showthread.php?t=2060403
Ps- if something isn't clear enough, feel free to ask.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot for your help!
So for the first step, I rebooted it into the Download mode following the video tutorial you linked to, and it told me:
ODIN MODE
Product Name: GT-I9300
Custom Binary Download: Yes (4 counts)
Current Binary: Custom
System Status: Custom
So I'm assuming that yes, my Samsung is an official I9300 device?
For the second step, does it matter which version of Kies I install as long as it's not Kies 3?
For the first option in the third step, will flashing the newest official ROM still allow me to keep on the T-Mobile network? (Since I originally had this device bought in China then had someone else unlock it so that it could be compatible with the US network carriers)
Thanks again!
wohuifei said:
Thanks a lot for your help!
So for the first step, I rebooted it into the Download mode following the video tutorial you linked to, and it told me:
ODIN MODE
Product Name: GT-I9300
Custom Binary Download: Yes (4 counts)
Current Binary: Custom
System Status: Custom
So I'm assuming that yes, my Samsung is an official I9300 device?
For the second step, does it matter which version of Kies I install as long as it's not Kies 3?
For the first option in the third step, will flashing the newest official ROM still allow me to keep on the T-Mobile network? (Since I originally had this device bought in China then had someone else unlock it so that it could be compatible with the US network carriers)
Thanks again!
Click to expand...
Click to collapse
1-It seems so (but if you want to do a double-check: https://play.google.com/store/apps/details?id=com.cpuid.cpu_z and see if it says 'Exynos 4412' in the SOC tab, and 'GT-I9300' + '832MB of ram' in System.
2- Get the lastest available.
3- Then I suggest using the second method. If you already have working CWM recovery, than you should be able to install Philz recovery directly as a zip file in your current recovery.
After updating the recovery (and backing-up all important data!), download NeatRom zip file, and copy it into device's SD.
Reboot to recovery mode, do "wipe to install new rom" + "wipe cache partition" + "advance->wipe delvik cache", and than-
"instal zip from sd/sd1 (depends on where you saved the zip of neatRom) and follow installation instructions.
after the flashing is done, check if the sim works as it should, if not- than you'll have 2 option to unlock it (which costs about 5-7$):
1- https://play.google.com/store/apps/details?id=com.spocky.galaxsimunlock
2- http://www.youtube.com/watch?v=GefyYn63dR4
There are some free turorials online, but they seem to be for older versions / questioned reliability...
A word of caution- moving to 4.3 will change the EFS partition to V2, which by itself isn't a problem (but causing a real headache for those trying to downgrade).
I bought a Samsung Galaxy II GT-I9100P today and I want to update the software (currently rocking Android 2.3.6) and install Cyanogenmod. Bearing in mind that this is my first foray into the Android World (though I would say I am fairly tech savvy) would you be able to direct me to some resources for achieving this. Also please note that I only have a mac (therefore I believe I will be using Heindall) and there is no possibility of borrowing, bootcamping or emulating a Windows partition.
Thanks
poliosynthesis said:
I bought a Samsung Galaxy II GT-I9100P today and I want to update the software (currently rocking Android 2.3.6) and install Cyanogenmod. Bearing in mind that this is my first foray into the Android World (though I would say I am fairly tech savvy) would you be able to direct me to some resources for achieving this. Also please note that I only have a mac (therefore I believe I will be using Heindall) and there is no possibility of borrowing, bootcamping or emulating a Windows partition.
Thanks
Click to expand...
Click to collapse
You should update your device first to the latest official firmware (4.1.2) either by using OTA updates or Kies to update your device. That way the installation process will go more smoothly.
regards, gsstudios
gsstudios said:
You should update your device first to the latest official firmware (4.1.2) either by using OTA updates or Kies to update your device. That way the installation process will go more smoothly.
Click to expand...
Click to collapse
OTA does not appear to be working, the phone seems to believe that it has no available updates. Would you be able to send me some resources for updating the phone manually?
poliosynthesis said:
OTA does not appear to be working, the phone seems to believe that it has no available updates. Would you be able to send me some resources for updating the phone manually?
Click to expand...
Click to collapse
Download and install Samsung kies for mac, connect your phone to your Mac, select update firmware in kies.
Please let me know if this doesn't work, so I can give you next set of instructions.
Regards, gsstudios
gsstudios said:
Download and install Samsung kies for mac, connect your phone to your Mac, select update firmware in kies.
Please let me know if this doesn't work, so I can give you next set of instructions.
Regards, gsstudios
Click to expand...
Click to collapse
I downloaded Kies and finally managed to get it to connect to my phone, however the upgrade progress bar sticks at 0%. Is it possible to download the firmware independently of Kies and try to load it then? If not what do you recommend instead?
poliosynthesis said:
I downloaded Kies and finally managed to get it to connect to my phone, however the upgrade progress bar sticks at 0%. Is it possible to download the firmware independently of Kies and try to load it then? If not what do you recommend instead?
Click to expand...
Click to collapse
Firmware update can not be downloaded separately in Kies. Instead, you could try using jodin (google it) to flash the firmware downloaded from sammobile.
Have a look at this post I posted earlier this week: http://forum.xda-developers.com/showpost.php?p=64214982&postcount=2
Instructions should be similar for application use. As you can tell, it's harder to flash roms in Mac OSX.
Regards, gsstudios.
gsstudios said:
Firmware update can not be downloaded separately in Kies. Instead, you could try using jodin (google it) to flash the firmware downloaded from sammobile.
Have a look at this post I posted earlier this week: http://forum.xda-developers.com/showpost.php?p=64214982&postcount=2
Instructions should be similar for application use. As you can tell, it's harder to flash roms in Mac OSX.
Regards, gsstudios.
Click to expand...
Click to collapse
Managed it at last! What now?
poliosynthesis said:
Managed it at last! What now?
Click to expand...
Click to collapse
Now you need to root your device using CF auto root by chainfire or Framaroot. Or you can install custom kernel like siyah kernel on your device (make sure to choose the right version otherwise your phone will bootloop).
- Download required cyanogenmod version (11 or 12.1 in this case) onto your phone
- Download Siyah kernel onto your phone
- Flash custom kernel via jodin (Select under PDA, tick auto-reboot, un-tick repartition)
- Wait for your phone to boot into OS. If it doesn't, you flash the wrong version
- After back into os, check if you have root. There should be SuperSU or Superuser app in your app drawer
- Download kitkatcompatible recovery such as Philz recovery or a kernel like DorimanX 10.XX onto your phone
- Reboot into recovery mode
- Flash kitkatcompatible recovery such as Philz recovery or a kernel like DorimanX 10.XX
- Reboot recovery (not phone, in advanced menu). If it prompts to fix root, just select yes. If it prompts to install root, select no.
- Factory reset, wipe system, cache while in new recovery
- Install cyanogenmod
- Reboot system/device
If you were unaware, if you flash any roms for the i9100 international edition, you will lose nfc.
Im currently on Lineage ROM, and i got a new phone so i need to flash the stock ROM on this K20 Plus, what would be the easiest way to do it? MetroPCs model.
I know you may have long since found the answer, but for others who may be curious simply search for the official LG software suite PC program and install it. You will need the phone device drivers. There is a thread here in the xda K20 plus ROMs and development forum with links to the necessary files and some basic guides. You'll also need to download the official stock image from the lg-firmwares.com or any such similar host sites. Although I believe the official and recent version of the LG backup/restore suite can download the image file automatically but I may be wrong. The crucial thing is to install all the necessary drivers on your PC and ensure the phone can be recognized on it. I haven't kept up with any of the latest releases to know if maybe the suite does the downloading and drivers setup with ease. But more or less the whole stock reflash process is the same and not difficult.