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.
Related
Hello,
I am kind of new around here.
I am trying to learn about Android. I have a Samsung Galaxy S (i9000) with Android 2.3.3.
Base band (?) versión says I9000BGJV1
Kernel version: 2.6.35.7-I9000BGJVS-CL307695 [email protected]#2
Compilation number GINGERBREAD.BGJVS
My phone comes from the Telefonica company and I want to install a new clean copy of Android mainly because mine is working way too slow and because it is giving me problems with the modem (it gets stuck when changing from G to 3G or HSPA).
I have downloaded Android 2.3.6 Open Europe from "samfirmware" and want to installed it with the idea of installing afterwards the Semaphore kernel.
I have tried rooting my phone with z4Root but it gave me an error. Later I have found this is not the apropriate way of doing it in Gingerbread. Do I need to be root to install a new copy of Android?
I have some BIG doubts with all this process:
1.- Is the Android version chosen a good one?
2.- In some tutorials that use Odin indicate that I need to be root. Is this correct?
3.- In some tutorials for Odin, they say that the "Repartion" option has to be markede and in some others they do not mark this option. Which one is the correct one?
4.- In case I have to root my phone first, where can I find a tutorial for DUMMIES like me?
Well, I have been trying to find a post that solves all my doubts, but what I have found has only messed me up.
I hope I am posting this in the correct place.
Thanks in advance for your help.
airgus1 said:
Do I need to be root to install a new copy of Android?
Click to expand...
Click to collapse
No.
airgus1 said:
1.- Is the Android version chosen a good one?
Click to expand...
Click to collapse
Your choice (personal preference)
airgus1 said:
2.- In some tutorials that use Odin indicate that I need to be root. Is this correct?
Click to expand...
Click to collapse
It depends on what you are doing. So if whatever the tutorial is for, it is required.
airgus1 said:
3.- In some tutorials for Odin, they say that the "Repartion" option has to be markede and in some others they do not mark this option. Which one is the correct one?
Click to expand...
Click to collapse
As I said, it depends on what you are doing (so all of them are correct).
airgus1 said:
4.- In case I have to root my phone first, where can I find a tutorial for DUMMIES like me?
Click to expand...
Click to collapse
See here: http://forum.xda-developers.com/showthread.php?t=1330252.
OK, thank you very much.
Then, what is exactly what I need to do to install a clean Android copy with a Semaphore kernel (for example)?
I understand that I just need to use Odin to install the clean copy and then the same thing with the Semaphore kernel. Do I need to be root to install this kernel?
airgus1 said:
OK, thank you very much.
Then, what is exactly what I need to do to install a clean Android copy with a Semaphore kernel (for example)?
I understand that I just need to use Odin to install the clean copy and then the same thing with the Semaphore kernel. Do I need to be root to install this kernel?
Click to expand...
Click to collapse
You need a rooted device to install any custom kernel.
Theonew said:
You need a rooted device to install any custom kernel.
Click to expand...
Click to collapse
Then, what is the order?
Should I install the clean copy of Android 2.3.6, then root it and then install the custom kernel? Or should I root it in the first place?
Thanks again.
airgus1 said:
Then, what is the order?
Should I install the clean copy of Android 2.3.6, then root it and then install the custom kernel? Or should I root it in the first place?
Thanks again.
Click to expand...
Click to collapse
Install the rom, root it, then install the kernel (make sure it is stated as compatible with that rom).
Thanks a lot. I think I got it
airgus1 said:
Hello,
I am kind of new around here.
I am trying to learn about Android. I have a Samsung Galaxy S (i9000) with Android 2.3.3.
Base band (?) versión says I9000BGJV1
Kernel version: 2.6.35.7-I9000BGJVS-CL307695 [email protected]#2
Compilation number GINGERBREAD.BGJVS
My phone comes from the Telefonica company and I want to install a new clean copy of Android mainly because mine is working way too slow and because it is giving me problems with the modem (it gets stuck when changing from G to 3G or HSPA).
I have downloaded Android 2.3.6 Open Europe from "samfirmware" and want to installed it with the idea of installing afterwards the Semaphore kernel.
I have tried rooting my phone with z4Root but it gave me an error. Later I have found this is not the apropriate way of doing it in Gingerbread. Do I need to be root to install a new copy of Android?
I have some BIG doubts with all this process:
1.- Is the Android version chosen a good one?
2.- In some tutorials that use Odin indicate that I need to be root. Is this correct?
3.- In some tutorials for Odin, they say that the "Repartion" option has to be markede and in some others they do not mark this option. Which one is the correct one?
4.- In case I have to root my phone first, where can I find a tutorial for DUMMIES like me?
Well, I have been trying to find a post that solves all my doubts, but what I have found has only messed me up.
I hope I am posting this in the correct place.
Thanks in advance for your help.
Click to expand...
Click to collapse
1.It completely depends on you.The higher the number,the latest the firmware is.
2.In some cases the file you try to flash require root.But in your case of flash a new firmware it doesn't require root.
3.checking repartition is done when your downloaded firmware contains 3 files.i.e.PHONE,PDA and CSC.
When using repartition be careful to use a right pit file which should go into pit in ODIN.In your case the pit file is 512.There are some exceptions where repartition is used for firmware with single file also.If repartion is used wrongly your phone might not boot.
4.Flash a custom kernel like semaphore as you said and install "super user" from market.Now your mobile is rooted.Note:before flashing check whether the kernel is supported for your firmware.
Note:Before flashing make sure you have the correct drivers installed and kill kies with task manager before flashing as kies may interrupt the flashing process.
My opinion is rather than rooting your devices you could flash custom rom which has more benefits than stock rom and has been already rooted.So no hassles.
Finally hit thanks if I helped you.Hope I have not confused you
vijai2011 said:
1.It completely depends on you.The higher the number,the latest the firmware is.
2.In some cases the file you try to flash require root.But in your case of flash a new firmware it doesn't require root.
3.checking repartition is done when your downloaded firmware contains 3 files.i.e.PHONE,PDA and CSC.
When using repartition be careful to use a right pit file which should go into pit in ODIN.In your case the pit file is 512.There are some exceptions where repartition is used for firmware with single file also.If repartion is used wrongly your phone might not boot.
4.Flash a custom kernel like semaphore as you said and install "super user" from market.Now your mobile is rooted.Note:before flashing check whether the kernel is supported for your firmware.
Note:Before flashing make sure you have the correct drivers installed and kill kies with task manager before flashing as kies may interrupt the flashing process.
My opinion is rather than rooting your devices you could flash custom rom which has more benefits than stock rom and has been already rooted.So no hassles.
Finally hit thanks if I helped you.Hope I have not confused you
Click to expand...
Click to collapse
You have been really really helpful. I will see if I do not get stuck in the process.
airgus1 said:
You have been really really helpful. I will see if I do not get stuck in the process.
Click to expand...
Click to collapse
Glad that I have helped you.
Well, Android 2.3.6 installed, Semaphore 2.3.0bm installed and superuser installed.
Everything working OK.
The only problem is that I used a backup tool for my applications (App Backup & Restore) that promised to backup my app data and when I restored them I found out that it only copied the clean apps without any other settings.
Next time I will use Titanium backup to see if it works better.
Thanks again.
airgus1 said:
Well, Android 2.3.6 installed, Semaphore 2.3.0bm installed and superuser installed.
Everything working OK.
The only problem is that I used a backup tool for my applications (App Backup & Restore) that promised to backup my app data and when I restored them I found out that it only copied the clean apps without any other settings.
Next time I will use Titanium backup to see if it works better.
Thanks again.
Click to expand...
Click to collapse
Well I always use titanium backup.But sometimes when restoring apps with data will cause the app to fc.
Hey everyone,
A while a go i upgraded to the XXLP2 version of 4.0.3. The ROM was okay, but had a few flaws. After a while, I fouind a better build. However, after the initial upgrade (via ODIN) to ICS, the phone no longer had clockworkmod installed. Only Android recovery 3e, which as I've learned, can only install .zip files which have a proper signature.
Additionally, there is an issue with the USB connection, which might be due to the unfinished build of ICS, or to a hardware issue. It should be added, that the phone charges just fine. I still have a MicroSD card, onto which I can put files.
I've tried many different firmwares and zip files, only to encounter the "E: Signature verification failed" error.
What's worse, in a stroke of bad luck, I installed an old version of google apps.
Now, when I boot up, I get the "tap the android" screen, which runs into an error, because the version of google apps is incompatible with the firmware itself.
In my mind, there are a few different means to solve this issue.
One would be to find a signed version of google apps, which I could install and keep using my current build of android.
Secondly, to find a .zip file, by which I could downgrade to an older version of android (2.3.x), and hopefully fix my USB issue.
What should i do?
Any help would be appreciated!
Thanks!
You should have read the basics and stickies first .
ICS is not released you are using buggy beta test builds .
CWM recovery is not on your phone only Android recovery you need to flash a cwm and root kernel .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
Or wipe the phone install your old firmware from the stock rom posts or search Google Samfirmware.com or Checkfus .
Custom roms rooted roms will not update to official ICS release via Kies or FOTA .
jje
JJEgan said:
You should have read the basics and stickies first .
ICS is not released you are using buggy beta test builds .
CWM recovery is not on your phone only Android recovery you need to flash a cwm and root kernel .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
Or wipe the phone install your old firmware from the stock rom posts or search Google Samfirmware.com or Checkfus .
Custom roms rooted roms will not update to official ICS release via Kies or FOTA .
jje
Click to expand...
Click to collapse
Thanks for your response
I understand that it is a beta build. However, as I mentioned, I have an issue with the USB connection. That is, the computer pops up an error which says that the device is not recognized. I've tried many different ways to fix this, and not found any. Therefore, I am limited only to what i can install with android recovery. The tutorial which you shared still requires an USB connection. I have tried firmware from samfirmware.com, but I keep getting the "E: signature verification failed" error.
Am I doing something wrong?
Is the USB working properly if you boot into download mode using volume down, home key and power button from switched off. If this works you can then just flash another from from Odin.
Sent from my GT-I9100 using Tapatalk
i know that this may be a last case scenario, but ive heard linux (more so ubuntu) may not need drivers for your phone, then maybe you coud install it to a usb and launch it that way?
maybe do some reading into that? http://forum.xda-developers.com/showthread.php?t=1309293
and maybe find the one for i9100
No, the USB conenection doesn't even work in download mode. I still get the "USB device not recognized" prompt.
Could you not download Mobile Odin and try using that, or try using this other app by Chainfire USB Host Diagnostics App
Could try reinstalling USB drivers
http://drivers.softpedia.com/progDo...SB-Driver-for-Windows-x86-Download-96692.html
Sent from my GT-I9100 using XDA App
I'm trying the linux solution at the moment. However, if it turns out to be a hardware fault, can someone please point me in the direction of a google apps zip which would still allow me to use my phone? Currently, i am stuck at the "tap android" screen, and am only able to make emergency calls. I've already tried a few variations i've found, but they get the signature verification error aswell.
Concerning the USB drivers, i've already tried installing the samsung drivers again, as well as ones which come with android SDK.
I would suggest you deal with getting the usb sorted first, then a flash to stock. You can worry about apps at a later date.
Sent from my GT-I9100 using xda premium
Failed USB and users who have flashed beta ICS is it seems a fairly common problem so probably not hardware .
Flash stock firmware via Mobile Odin
jje
As I mentioned, the only thing keeping me from using the phone normally is the somewhat dated version of google apps i installed through android recovery. If i find a version compatible with the xxlp2 build, then I can atleast use the buggy beta version i have, and try solving things from there.
Where could i find the version of google apps that I need, which would also work with 3e recovery?
There is a thread where someone has a CWM flashable via stock recovery update.zip which will let you temporarily use CWM.
I'll try and find it and supply a link.
Sent from my GT-I9100 using XDA
JJEgan said:
Failed USB and users who have flashed beta ICS is it seems a fairly common problem so probably not hardware .
Flash stock firmware via Mobile Odin
jje
Click to expand...
Click to collapse
Thats actually a relief to hear!
However, the phone wont get past the "tap the android" screen, and I'm also not rooted (the root would have been lost anyway when installing 4.0.3).
I can only do something from android recovery mode atm, unless i find a working version of google apps which would allow me to set up my phone.
Additionally, I googled for ways to bypass the setup wizard, the four corners method does not work for me (must be the firmware).
http://forum.xda-developers.com/showthread.php?t=1501719
You could look at the link above and use its idea.
1st flash the CWM etc via stock recovery then use CWM to flash gapps or other CWM tools to see if SD is ok etc.
Worth a shot.
Sent from my GT-I9100 using XDA
Puppiesweekly said:
As I mentioned, the only thing keeping me from using the phone normally is the somewhat dated version of google apps i installed through android recovery. If i find a version compatible with the xxlp2 build, then I can atleast use the buggy beta version i have, and try solving things from there.
Where could i find the version of google apps that I need, which would also work with 3e recovery?
Click to expand...
Click to collapse
You can get what you need here
Hi All Below I occidentally posted in the Galxy SI900 instead of here< I got the usual replies but was grateful all the same. Maybe someone might help before I revert to stock...
Hi all, I know this has been done and dusted but I am having problems with connecting to kies after rooting. I am running standard jelly bean 4.1.2 and is an Australian GT-I9100. I installed the siyah kernal root system and now all I get on kies is "connecting" Windows 7 recognises and I can access the phone via explorer on the PC. The phone after a while comes up with a message that there is no compatible software on the PC, install kies...
I have tried all the so called fixes including formatting the internal SD and memory. The only thing I did before it stopped connecting was the root and running Triangle away (paid version). I have enabled / disabled USB debugging. The only things I haven't tried is a factory reset which I don't really want to do as I am always sceptical that the backup apps will work after to restore everything.
Any help appreciated
Click to expand...
Click to collapse
The thread is here: http://forum.xda-developers.com/showthread.php?p=45907982#post45907982
Hope someone can help...
Regards Ismael
Did you try another PC or reinstall Kies? To know if the problem is in the phone or in PC?
jiseuo said:
Did you try another PC or reinstall Kies? To know if the problem is in the phone or in PC?
Click to expand...
Click to collapse
Yes, Kies definitely sees the phone as it comes up with GTI9100 loading on the left top and in the centre it just sits saying connecting. I think the phone is not seeing kies as the message on my phone always comes up only when trying to connect to kies.
I have tried 3 computers/laptops same result. Different USB cables original plus other really high end ones also. No Joy. Looks like if I want to connect to kies I must revert back to stock kernal as the firmware I never changed it is the OTA from samsung 4.1.2 and rooted the S2 only...
Also Not knowing Samsung but in the about on my Motorola Tablet/phone even when rooted when you try to check for updates they say none available, the samsung actually says "Your device has been modified, no updates available"...
IsmaelJones said:
Yes, Kies definitely sees the phone as it comes up with GTI9100 loading on the left top and in the centre it just sits saying connecting. I think the phone is not seeing kies as the message on my phone always comes up only when trying to connect to kies.
I have tried 3 computers/laptops same result. Different USB cables original plus other really high end ones also. No Joy. Looks like if I want to connect to kies I must revert back to stock kernal as the firmware I never changed it is the OTA from samsung 4.1.2 and rooted the S2 only...
Also Not knowing Samsung but in the about on my Motorola Tablet/phone even when rooted when you try to check for updates they say none available, the samsung actually says "Your device has been modified, no updates available"...
Click to expand...
Click to collapse
Now I am not using KIES, because I use AOSP ROM (4.3 Slimbean), but in past, when i was using STOCK ROM (XWLSN, XWLSS) I used "PhilZ-cwm6 - Safe Stock Based Kernel" http://forum.xda-developers.com/showthread.php?t=1877270 to root my phone.
If I remember correctly, KIES was working with PhillZ, but it is few months ago ...
So you can try PhillZ and see If it will work.(If do not need any special feature from syiah kernel of course)
jiseuo said:
If I remember correctly, KIES was working with PhillZ, but it is few months ago ...
So you can try PhillZ and see If it will work.(If do not need any special feature from syiah kernel of course)
Click to expand...
Click to collapse
Okay had a look at this, thanks. I do have a question though, my Kernel (PDA) is XWLSH, I have downloaded the 2 files but I am wondering how to install? Do I use my CW recovery or do I have to revert back to stock? A little confusing as he dowsn't really give instructions and I am pretty much an amateur when it comes to some of these things? Also I am running JB 4.1.2 he only mentions ICS 4.0.4? Help appreciated here...
Actually just re-read the post and I think I know now what to do. Correct me if I am wrong but the 2 files I downloaded are for 2 different methods of installing, the Zip file via SD card and the MD5 file by odin. Is this correct?
IsmaelJones said:
Actually just re-read the post and I think I know now what to do. Correct me if I am wrong but the 2 files I downloaded are for 2 different methods of installing, the Zip file via SD card and the MD5 file by odin. Is this correct?
Click to expand...
Click to collapse
Yes. ZIP is for flashing from recovery and tar.md5 is for flashing from ODIN.
Maybe the best way will be to reflash your whole stock firmware to get correct previous state before you started flashing syiah. You can get it on Sammobile.com - (simple registration needed) and then use PhilZ recomended method - flash ZIP from stock recovery
What is your Country / operator, Try this http://www.sammobile.com/firmwares/2/ to find right and latest oficial firmware for your country / operator version for your phone.
edit: For XWLSH it may be GT-I9100LKJXSA - unbranded australia version, or GT-I9100LKJOPS - Australia OPTUS operator customized version.
jiseuo said:
Yes. ZIP is for flashing from recovery and tar.md5 is for flashing from ODIN.
Maybe the best way will be to reflash your whole stock firmware to get correct previous state before you started flashing syiah. You can get it on Sammobile.com - (simple registration needed) and then use PhilZ recomended method - flash ZIP from stock recovery
What is your Country / operator, Try this http://www.sammobile.com/firmwares/2/ to find right and latest oficial firmware for your country / operator version for your phone.
edit: For XWLSH it may be GT-I9100LKJXSA - unbranded australia version, or GT-I9100LKJOPS - Australia OPTUS operator customized version.
Click to expand...
Click to collapse
Hi Again, solved the problem... definitely the siyah root was the culprit. I used mobile Odin to install the stock kernel, once done checked and could connect in kies and was still rooted missing busybox only. After that I again used mobile odin to install philZ, again no problems and all seems fine now. Everything working.
Thanks a million for helping and also many thanks to mobile odin developers as this is a far better tool than most and saves connecting to the PC Odin. Also seems a lot safer...
:good:
Hi guys!
This is my first time to post a thread in this forum, I just bought a Samsung Note with model SHV-E160S, Android Version 4.0.4 and Build# IMM76D.VH29. I know that this is a Korean Variant and I'm using it here in Philippines (I can send SMS -- Openline). I don't know if this phone is already rooted, I don't know how to check.
What I'm trying to accomplish is to upgrade this phone from 4.0.4 to 4.1.2 then later on upgrade it to Android Lollipop 5.1 and I don't know how. It will be a great pleasure if someone help me or direct me on what should I do.
I'm totally new to android devices and I'm not familiar on how to upgrade,update or root an android device.
Thanks!
Hello guys, any ideas? Thanks!
jakeortega said:
Hi guys!
This is my first time to post a thread in this forum, I just bought a Samsung Note with model SHV-E160S, Android Version 4.0.4 and Build# IMM76D.VH29. I know that this is a Korean Variant and I'm using it here in Philippines (I can send SMS -- Openline). I don't know if this phone is already rooted, I don't know how to check.
What I'm trying to accomplish is to upgrade this phone from 4.0.4 to 4.1.2 then later on upgrade it to Android Lollipop 5.1 and I don't know how. It will be a great pleasure if someone help me or direct me on what should I do.
I'm totally new to android devices and I'm not familiar on how to upgrade,update or root an android device.
Thanks!
Click to expand...
Click to collapse
Hello guys, any ideas? Thanks!
You'll be able to find your firmware here https://mega.nz/#F!IxJTDDQQ!TTgzxjX8d7EnzemoIj0ogg
4.1.2 was the last official update from Samsung for your device. If you want to update to newer than that, it will have to be done via updating with a custom recovery and custom rom, such as TWRP recovery and CyanogenMod 11 or 12/12.1.
Follow upgrade instructions from here http://forum.xda-developers.com/showthread.php?t=1424997 and sub your firmware file instead of N7000.
es0tericcha0s said:
You'll be able to find your firmware here https://mega.nz/#F!IxJTDDQQ!TTgzxjX8d7EnzemoIj0ogg
4.1.2 was the last official update from Samsung for your device. If you want to update to newer than that, it will have to be done via updating with a custom recovery and custom rom, such as TWRP recovery and CyanogenMod 11 or 12/12.1.
Follow upgrade instructions from here http://forum.xda-developers.com/showthread.php?t=1424997 and sub your firmware file instead of N7000.
Click to expand...
Click to collapse
Thank you es0tericcha0s for this information.
What I'm trying to do right now is updating my SHV-e160s from 4.0.4 to 4.1.2 using Kies v2.6. Unfortunately, I'm getting this error "Failed to run firmware upgrade: unknown error.". Until now, I'm afraid to update my firmware manually as I don't have much knowledge to do that.
1) Download firmware and Odin
2) Open Odin as admin
3) Load firmware in PDA or AP slot depending on which version of Odin used
4) Boot to Download Mode and plug in your phone
5) Once Odin recognizes it ( will show highlighted - COM:xx where "xx" is any number, doesn't matter which ones) hit start
6) Grab a drink and a snack and come back in 10 minutes or so
7) If device bootloops, reset in recovery
Once the files are downloaded, the whole process takes less than 10-12 minutes or so. Everything you need is in the guide I linked to besides the firmware you need, which is in the Mega link. If you need a video guide, there are dozens on YouTube. I find it much easier to use than Kies and once you have it working, then there are not many things you will do that restoring with Odin and a factory reset won't get you out of.
es0tericcha0s said:
1) Download firmware and Odin
2) Open Odin as admin
3) Load firmware in PDA or AP slot depending on which version of Odin used
4) Boot to Download Mode and plug in your phone
5) Once Odin recognizes it ( will show highlighted - COM:xx where "xx" is any number, doesn't matter which ones) hit start
6) Grab a drink and a snack and come back in 10 minutes or so
7) If device bootloops, reset in recovery
Once the files are downloaded, the whole process takes less than 10-12 minutes or so. Everything you need is in the guide I linked to besides the firmware you need, which is in the Mega link. If you need a video guide, there are dozens on YouTube. I find it much easier to use than Kies and once you have it working, then there are not many things you will do that restoring with Odin and a factory reset won't get you out of.
Click to expand...
Click to collapse
Alright, I'll try these steps immediately and will comeback for the result. Thanks again.
es0tericcha0s said:
1) Download firmware and Odin
2) Open Odin as admin
3) Load firmware in PDA or AP slot depending on which version of Odin used
4) Boot to Download Mode and plug in your phone
5) Once Odin recognizes it ( will show highlighted - COM:xx where "xx" is any number, doesn't matter which ones) hit start
6) Grab a drink and a snack and come back in 10 minutes or so
7) If device bootloops, reset in recovery
Once the files are downloaded, the whole process takes less than 10-12 minutes or so. Everything you need is in the guide I linked to besides the firmware you need, which is in the Mega link. If you need a video guide, there are dozens on YouTube. I find it much easier to use than Kies and once you have it working, then there are not many things you will do that restoring with Odin and a factory reset won't get you out of.
Click to expand...
Click to collapse
Hello, sorry I forgot to ask, will this root my device? I'm afraid I might bricked it.
No, this is just the official update. As long as the download is good and you follow those directions, you won't do anything that won't be easily recoverable if it doesn't work right away. Soft bricking is not a big deal and nothing you would do here would cause anything worse unless you unplug the phone in the middle of something important.
---------- Post added at 09:23 AM ---------- Previous post was at 09:20 AM ----------
And because you'll probably ask... It's easy to root. Just download Chainfire's SuperSU zip, put it on your phone's storage and use Odin to install TWRP recovery (just like you do with the whole firmware package) , boot to recovery before it boots to the OS and install the zip. Reboot and enjoy.
es0tericcha0s said:
No, this is just the official update. As long as the download is good and you follow those directions, you won't do anything that won't be easily recoverable if it doesn't work right away. Soft bricking is not a big deal and nothing you would do here would cause anything worse unless you unplug the phone in the middle of something important.
---------- Post added at 09:23 AM ---------- Previous post was at 09:20 AM ----------
And because you'll probably ask... It's easy to root. Just download Chainfire's SuperSU zip, put it on your phone's storage and use Odin to install TWRP recovery (just like you do with the whole firmware package) , boot to recovery before it boots to the OS and install the zip. Reboot and enjoy.
Click to expand...
Click to collapse
Hello again es0tericcha0s, I haven't tried the instructions that you gave me yesterday as I'm still downloading the firmware, last night I encountered an issue after enabling my Bluetooth, something like "NFC Service has stopped." just keeps on popping up. So I turned off the bluetooth then restarted my phone, it went well for a while.
After that, I enabled my 3G Cellular Data to check what was NFC service error is, after a few minutes, I lost my signal, phone turned to No Service, then in Settings -> About Phone, I got an Unknown Baseband.
EDIT
I got No Service since last night up until now.
EDIT Oct. 13, 2015 9:49 AM +08:00 Manila Time
I manage to update my phone from ICS 4.0.4 to JB 4.1.2. But still, my baseband is Unknown and I have no signal.
If it did that before you tried to flash anything...that doesn't sound good. Hard to say without testing it, but kind of sounds like the baseband chip (hardware issue).
es0tericcha0s said:
If it did that before you tried to flash anything...that doesn't sound good. Hard to say without testing it, but kind of sounds like the baseband chip (hardware issue).
Click to expand...
Click to collapse
I also though of that, hopefully not.
When I first got the phone, my gf sent me our pictures via bluetooth , no issues occured. After a while, I noticed that there are so many photos of the previous owner (around 1000+) and mp3s (around 1000+ also). So I connected the phone via usb to my pc and deleted all those pictures and mp3s inside the My Computer -> SHV-E160S -> Phone (Computer\SHV-E160S\Phone). After doing so, I started to encouter some issues, when enabling the bluetooth, the phone hangs and reboots then the error 'NFC service has stopped' keeps on popping up, until it went Unknown Baseband.
Now, the phone keeps on rebooting similar to the symptoms that it gets when baseband version is unknown.
I'm looking for solutions to fix the unknown baseband and saw the Back up and Restore EFS, I just need to root the device to try this fix. Maybe I'll post an update whether if I manage to solve this problem or not, if it didn't fix the issue then maybe the problem is the baseband chip. what a crap!
This is my reference for the EFS Fix
http://techbeasts.com/2014/07/13/fix-samsung-galaxy-unknown-baseband-version-guide/
Thanks!
Rooting will be easy. Just install TWRP with Odin and use the SuperSU zip from Chainfire. Process should take like 5 minutes once everything is downloaded.
es0tericcha0s said:
Rooting will be easy. Just install TWRP with Odin and use the SuperSU zip from Chainfire. Process should take like 5 minutes once everything is downloaded.
Click to expand...
Click to collapse
So I need to install TWRP first before rooting the device? Also I'm planning to use a rooted stock firmware which is 4.1.2, I just don't know the difference between UH24 and MH2, I've read that UH24 is already old and it's better to use a MH2 build and what is the Recovery UH24/MH2?
EDIT:
I forgot, I cannot check my current Baseband since it is still unknown.
EDIT: 12:30PM +8:00
I managed to get my Build#, it is MH2, I'm currently looking for a rooted 4.1.2 MH2 download link.
Way faster and easier to use the method I outlined, but either way should work.
es0tericcha0s said:
Way faster and easier to use the method I outlined, but either way should work.
Click to expand...
Click to collapse
Sorry, I'm really a root virgin here. While following your advise, I'm also currently looking at this guide -> http://forum.xda-developers.com/showthread.php?t=1924535. I'm done downloading Tegrak for MH2, a small problem I encountered here is I don't have a folder named 'sdcard' in my phone, so I created one and copied the 'Kernel' .zip, also I copied it to usbStorage folder.
I'm about to flash the 'Recovery' .tar to my phone. Hoping a success result
Should be fine. Your phone's internal storage is seen by the OS as /sdcard. Doesn't matter where you put the file as long as you remember where it's at so you can navigate to it through recovery to install.
es0tericcha0s said:
Should be fine. Your phone's internal storage is seen by the OS as /sdcard. Doesn't matter where you put the file as long as you remember where it's at so you can navigate to it through recovery to install.
Click to expand...
Click to collapse
Oh crap, I didn't thought of that. Installing 'Kernel' .zip now.
jakeortega said:
Oh crap, I didn't thought of that. Installing 'Kernel' .zip now.
Click to expand...
Click to collapse
Finally! I'm done rooting my phone, though I encountered another issues again. My Menu Button and Back Button does not work.
UPDATE: 4:08PM +8:00GMT
I think I found the problem as to why my Menu button and Back button doesn't work. I'v check my Baseband and it is -> E160SKSJMH1 and my Build # is -> JZO54K.E160SKSJMH2. Am I using a wrong FW as supposed to what I should be using? Which build should I install, the MH1 or the MH2?
Also, the Tegrak Kernel I've used is Build 48 for SHV-E160S MH2. I've also tried factory resetting the phone but the issue still exists.
Thanks!
UPDATE: 4:41PM +8:00GMT
Managed to fixed the issue by updating my Touch Firmware. Cool!
Hi, I have an old Samsung Galaxy Tablet 10.1 SCH-i925 that is not rooted and still has the original OS (Android 4.1.2) on it.
I'm trying to update to Lineage OS 16.0 using Odin, but have not been able to. I've tried several versions of the Samsung USB Driver for Mobile Phones, and several versions of Odin, as well as different USB cables. Does anyone have any advice for what I could do next? I realize this may be a basic question but I've sunk 20+ hours into this and am lost.
smadug2 said:
Hi, I have an old Samsung Galaxy Tablet 10.1 SCH-i925 that is not rooted and still has the original OS (Android 4.1.2) on it.
I'm trying to update to Lineage OS 16.0 using Odin, but have not been able to. I've tried several versions of the Samsung USB Driver for Mobile Phones, and several versions of Odin, as well as different USB cables. Does anyone have any advice for what I could do next? I realize this may be a basic question but I've sunk 20+ hours into this and am lost.
Click to expand...
Click to collapse
You install custom ROM via custom recovery, for example TWRP.
ze7zez said:
You install custom ROM via custom recovery, for example TWRP.
Click to expand...
Click to collapse
Thanks for the prompt reply! I was under the impression that Odin was required to install TWRP in the first place. Is there another way to transfer TWRP to the device and access it through the bootloader mode on the tablet ("power + volume up") ?
smadug2 said:
(...) I was under the impression that Odin was required to install TWRP in the first place.(...)
Click to expand...
Click to collapse
Of course you did, but you wrote:
"I'm trying to update to Lineage OS 16.0 using Odin"
You must use the exact version of Odin that is recommended for your model, which is 3.13.1. I use The Muppets version.
There are no Samsung drivers other than these:
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
ze7zez said:
Of course you did, but you wrote:
"I'm trying to update to Lineage OS 16.0 using Odin"
You must use the exact version of Odin that is recommended for your model, which is 3.13.1. I use The Muppets version.
There are no Samsung drivers other than these:
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
Click to expand...
Click to collapse
Ok! I downloaded Samsung Android USB Driver for Windows v1.7.59 and am using the muppets version of Odin (3.13.1), and it still fails to transfer any files. I tried with an auto-root .tar file and TWRP. I've attached the Odin window output for reference:
Oh, this is for a galaxy *note* tablet, not the thing I have. You may want to update the post title to add that detail. I had to google the SCH-i925 to be sure...
smadug2 said:
Ok! I downloaded Samsung Android USB Driver for Windows v1.7.59 and am using the muppets version of Odin (3.13.1), and it still fails to transfer any files. I tried with an auto-root .tar file and TWRP. I've attached the Odin window output for reference:
Click to expand...
Click to collapse
I don't understand why you want to flash something for n8010 when you have a tablet from Verizon?
Show the tablet property screen with hardware and firmware information.
Have you unlocked the bootloader?
ze7zez said:
I don't understand why you want to flash something for n8010 when you have a tablet from Verizon?
Show the tablet property screen with hardware and firmware information.
Have you unlocked the bootloader?
Click to expand...
Click to collapse
I read in various other places that the auto-root file and TWRP file for the n8010 works for the Verizon version (SCH-i925) since it's essentially the same device. I may be wrong though...I cannot find a specific TWRP file online for this version of the 10.1.
I have attached the device details to this post.
Unfortunately, extensive searching online indicates that there is no easy way to unlock the bootloader for the sch-i925: https://forum.xda-developers.com/t/...root-jailbreak-recovery.3400894/post-79789473
Any advice on these various issues would be greatly appreciated!
smadug2 said:
(...)
Any advice on these various issues would be greatly appreciated!
Click to expand...
Click to collapse
Without an unlocked bootloader, you probably aren't flashing TWRP or a custom ROM. In stock ROM you can root easily, even with Towelroot.
There's nothing more I can't help, so as not to harm.
Ok well thanks for your help!