Hello Everyone,
Firstly, I need to say that as a previous owner of an original droid, I was able to root it with no problems on the first go around. However, as a new owner of a Samsung Galaxy SII I am finding root a real challenge.
I have no problems getting into download mode and so on....I have successfully placed the clockworks rom onto the phone with again no problems and I have all the drivers working properly. I guess this is where I am obviously an idiot....because I start the Super One Click and it gets to Step 6 and then stops. I unplug the USB....click the debugg off and then back on and reconnect my USB like directed by many posters. However, in my case it will not continue on and finish the install.....
I reboot and do get the small triangle on boot up ( not that I care too much about that really...do have a jig on order however) but I simply can't seem to get it to root.
Again I have followed all the posts and guides for unplugging, unchecking and rechecking the debugging and then plug back in the USB and still nothing.
Phone works fine....everything works...love the phone...just seems puzzling to me. I have Odin 1.82, I have SuperOneClick 2.1.1 and like I said installed the .tar fine to the phone with no worries....just cant get it to root.
Any advice?
i used (this) with no issues.
Does your phone currently have the new KJ1 update? I've read that this new update will not root with the usual methods.. (I could also be wrong...)
RE: Rooting
TheElectricalGuru said:
Hello Everyone,
Firstly, I need to say that as a previous owner of an original droid, I was able to root it with no problems on the first go around. However, as a new owner of a Samsung Galaxy SII I am finding root a real challenge.
I have no problems getting into download mode and so on....I have successfully placed the clockworks rom onto the phone with again no problems and I have all the drivers working properly. I guess this is where I am obviously an idiot....because I start the Super One Click and it gets to Step 6 and then stops. I unplug the USB....click the debugg off and then back on and reconnect my USB like directed by many posters. However, in my case it will not continue on and finish the install.....
I reboot and do get the small triangle on boot up ( not that I care too much about that really...do have a jig on order however) but I simply can't seem to get it to root.
Again I have followed all the posts and guides for unplugging, unchecking and rechecking the debugging and then plug back in the USB and still nothing.
Phone works fine....everything works...love the phone...just seems puzzling to me. I have Odin 1.82, I have SuperOneClick 2.1.1 and like I said installed the .tar fine to the phone with no worries....just cant get it to root.
Any advice?
Click to expand...
Click to collapse
Try this rooter "su-3.0-efgh-signed.zip".
Here is the link for it: http://www.megaupload.com/?d=LBTUWW1J
After downloading copy the zipfile to your sdcard and flash it in
CWM recovery just like you would flash a rom using the option
"Install zip from sdcard" in CWM.
When its done reboot the phone and it should be rooted.
Misterjunky said:
Try this rooter "su-3.0-efgh-signed.zip".
Here is the link for it: http://www.megaupload.com/?d=LBTUWW1J
After downloading copy the zipfile to your sdcard and flash it in
CWM recovery just like you would flash a rom using the option
"Install zip from sdcard" in CWM.
When its done reboot the phone and it should be rooted.
Click to expand...
Click to collapse
that file is in the link I posted above...just an FYI.
I tried using the "su-3.0-efgh-signed.zip" and it failed.
Related
SuperOneClick seems to stall at the point where it says 'Starting ADB Server'. I do have the drivers installed & have transferred stuff back & fourth over USB, so I'm confident that it's not a driver issue. It is frustrating that I rooted other devices w/o a hitch when this one just isn't budging. My US Galaxy Player 5.0 is running 2.3.5. Has anyone else had this issue rooting their US model Galaxy Player 5.0? How might I solve this?
Thanks.
Have you tried odin to flash kernel? But make sure you have the from on your internal sd card before falshing.and also make sure u put the phone in download mode ie power+vol down. I have attached the odin.
Put the .tar file at the pda section and click start
once is down boot into cwm bye holding power+vol up.
Am I supposed to do anything else after that to be rooted? Or is it now done since I followed them steps & got a pass?
you are rooted find a Rom .zip and install from cwm or if you are not on the stock rom install the stock rom with odin at the pda section.
One of the last lines in the log should be something like 'testing su' if that says pass, it means the rooting was successful. (note: su is the linux command used to become the root user).
When you run an app requiring root, you'll get a prompt asking if you want to allow it to run as root. Once you say yes for an app, it'll just flash a 'app was was granted superuser permission' message for a couple seconds each time the app starts (this can be changed in the settings of Superuser).
Hello, I just got a Samsung Galaxy S2 from a friend (Stock firmware GB 2.3.3)
For some reason I am not able to establish a connection between the phone and the PC.
I tried to install and reinstall Kies and/or the drivers multiple times (and everyone of the other suggestions i found with google) but with no success. The phone recognizes that it's been charged when the cable is plugged in and sometimes the phone even indicates that it's establishing a connection to kies (but this appears randomly, not always). On the PC there's no sign of any connection to the phone, neither Kies connects to it nor the phone is shown as any kind of device in the device-manager or in explorer ("adb devices" and Odin also don't recognize the phone).
Since my fathers S2 (2.3.6 Stock Firmware) connects fine with the same drivers and cable i finally gave up searching for any any other possible reason than a damaged connector on the phone.
So i tried to search for ways to root the phone, put CWM on it and a custom ROM without any PC connection.
I encountered some things like signed custom kernels that should grant you root access, an exploitation, ...
The exploitation didn't work out for my phone, and the kernels I've found are for Jellybean or ICS, so not suitable for my Gingerbread-Firmware,
I've found some older threads on various websites that promised such kernels for Gingerbread, but there were either dead links or nothing suitable for my phone.
So now I'd like to ask the community if anyone knows any signed kernel to gain root access for my phone, or any other way to accomplish my task of upgrading to a custom firmware, or if there's no possible way to do this and I should stop wasting m time on this...
(btw, for some reason the update of the firmware via WiFi doesn't work either, so I would be glad if anyone just knows a way to upgrade to a newer stock-firmware)
My phone:
model: GT-I9100
Android: 2.3.3
Baseband: I9100NEKD5
Kernel: 2.6.35.7-I9100XWKE1-CL181974
Buildnr.: GINGERBREAD.XWKE1
thank you all in advance
Can you download and install the latest version of Odin and check if it recognises that your phone is connected?
Let me know
Sent from my GT-I9100 using Tapatalk 2
You can try ExynosAbuse ( http://forum.xda-developers.com/showthread.php?t=2050297) for rooting; not sure if it works for gingerbread though.
Once you're rooted you should be able to flash cwm with MobileOdinPro (costs 5 bucks; https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro)
Sent from my GT-I9100 using xda app-developers app
MarkyG82 said:
Disi01
Try these:
Boot to recovery and factory reset (backup any pics etc if required)
Set debugging in usb access
Try other usb ports on the pc.
I wanted the same thing untill it took me 2 weeks to decide I wanted to flash in odin. Swapping to a different port gave me access.
Good luck.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
This is what I tried too and for me it didn't work. I got the same problem as TO. I'm going to try some more stuff and if it would work i'll let you know and will follow this.
ps. I even have switched the board inside with the micro usb connector. Didn't work. I am on 4.0.4.
I already tried if Odin recognizes my phone -> no success...
I also tried ExynosAbuse before, it tells me when I start the app made by chainfire, that my device is unable to be rooted via this method.
And I've already tried to connect through every single port on every single computer that's available to me, still no success...
The only chance a can see right now might be to find a signed kernel that gives me root-access via the "install update from SD card" function, I've already found a few, but none of them was suitable for my device...
The problem is that this firmware apparently is that "old", that most of the results when searching for this topic are JB or ICS-related.
disi01 said:
I already tried if Odin recognizes my phone -> no success...
I also tried ExynosAbuse before, it tells me when I start the app made by chainfire, that my device is unable to be rooted via this method.
And I've already tried to connect through every single port on every single computer that's available to me, still no success...
The only chance a can see right now might be to find a signed kernel that gives me root-access via the "install update from SD card" function, I've already found a few, but none of them was suitable for my device...
The problem is that this firmware apparently is that "old", that most of the results when searching for this topic are JB or ICS-related.
Click to expand...
Click to collapse
You really gotta get your device rooted and flashed (mobile odin pro might is a good choice)
Don't you have an External SD card? if not, I'm sure you know someone who does.
Once you get it, you can get your device rooted & flash whatever you want via recovery.
And remember, you can always say to your dad "hey old man, how about this: I give you my phone, and you give me yours".
gastonw said:
You really gotta get your device rooted and flashed (mobile odin pro might is a good choice)
Don't you have an External SD card? if not, I'm sure you know someone who does.
Once you get it, you can get your device rooted & flash whatever you want via recovery.
And remember, you can always say to your dad "hey old man, how about this: I give you my phone, and you give me yours".
Click to expand...
Click to collapse
Yes, I do have an external SD card, but as far as I know, to flash your phone via MobileOdin it needs root access, and I still haven't figured out how to grant my applications root access on this device without any PC connection... I haven't found any useable kernel/update yet that helps me with my problem and can be installed without the phone being rooted already... If you know one, I would be glad if you could tell me
I already tried to negotiate with my dad but he doesnt seem very cooperative. He didn't like the fact that my phone has an older firmware than his and that I haven't found a way to update it... (Somehow the firmware-update via WiFi doesn't work too, it tells me everytime that the phone failed to connect to the server)
disi01 said:
Yes, I do have an external SD card, but as far as I know, to flash your phone via MobileOdin it needs root access, and I still haven't figured out how to grant my applications root access on this device without any PC connection... I haven't found any useable kernel/update yet that helps me with my problem and can be installed without the phone being rooted already... If you know one, I would be glad if you could tell me
I already tried to negotiate with my dad but he doesnt seem very cooperative. He didn't like the fact that my phone has an older firmware than his and that I haven't found a way to update it... (Somehow the firmware-update via WiFi doesn't work too, it tells me everytime that the phone failed to connect to the server)
Click to expand...
Click to collapse
lol, okay, stop and read for a min.
You can root your device with that SD card.
Read this guy's method.
After you root it, you're up for some flashing.
But take it one step at the time.
If we get you to flash a nice looking ROM, your dad's gonna say something like this "hey, that's a nice looking OS you got there, how about I give you mine + 100 bucks"
About the OTA (over the air) update, I recall reading something about it. I'ma see if I can find a thread about that.
Also, you might like to try removing kies from your system (every last trace of it) and reinstalling the latest version. Then try connecting the phone again.
Sent from my GT-I9100 using Tapatalk 2
gastonw said:
lol, okay, stop and read for a min.
You can root your device with that SD card.
Read this guy's method.
After you root it, you're up for some flashing.
But take it one step at the time.
If we get you to flash a nice looking ROM, your dad's gonna say something like this "hey, that's a nice looking OS you got there, how about I give you mine + 100 bucks"
About the OTA (over the air) update, I recall reading something about it. I'ma see if I can find a thread about that.
Click to expand...
Click to collapse
Dude. That method (Rachmat3's) only works for ICS. He's on GB.
ctomgee said:
Dude. That method (Rachmat3's) only works for ICS. He's on GB.
Click to expand...
Click to collapse
Quantity rather than quality lol.
Yes, this method doesn't work on GB, I've tried this before with a huge load of different CWM-bootloaders from a lot of different sources and it always throws an "signature verification failed" or "failed to verify whole-file signature" error or both...
Isn't there any similar way to do this on GB? I've been an iPhone user for a few years now and didn't check the android hacking/modding community very often and because of this I'm not aware of any rooting methods that may have been available back then...
All you need to do is use the exynos exploit to gain root. You can do this via a simple apk.
Once you have root install Mobile Odin and flash Siyah kernel (.tar) to get custom kernel, cwm recovery etc.
Then you're off! Just reboot into recovery and wipe/flash away :good:
ctomgee said:
Dude. That method (Rachmat3's) only works for ICS. He's on GB.
Click to expand...
Click to collapse
ooops.
disi01 said:
I also tried ExynosAbuse before, it tells me when I start the app made by chainfire, that my device is unable to be rooted via this method.
Click to expand...
Click to collapse
Unfortunately the ExynosAbuse-method isn't an option for me neither...
EDIT:
found this in the changelog of ExynosAbuse (added in v1.20):
- Gingerbread-related fixes - note that not all Gingerbread firmwares of affected devices are vulnerable (for example, I know several SGS2 GB firmwares are not exploitable)
I think that unfortunately I have one of those firmwares...
What about changing the usb board.
If nothing else works this will be my last option in the end i guess, but I'd rather prefer a software-based solution because I assume it might be a bit cheaper
Looks like your only option to me.
try this
open the phone dialer
enter *#7284#
then make sure your phone is set to usb mode
you can try switching it to modem or the other option then reboot phone
then enter code again and pick usb option
you might need to reboot again
I had a problem in the past where USB would not connect and when I did the above it worked.
droiduzr2 said:
try this
open the phone dialer
enter *#7284#
then make sure your phone is set to usb mode
you can try switching it to modem or the other option then reboot phone
then enter code again and pick usb option
you might need to reboot again
I had a problem in the past where USB would not connect and when I did the above it worked.
Click to expand...
Click to collapse
You, Sir, are my personal hero from now on I couldn't really try by now if this solved the problem with the USB-connection, but somehow it solved the problem with the firmware-update per WiFi, and now I was able to update to the newest ICS-firmware available to my device. And hopefully I will be able to root it now with one of the signed kernels available for ICS-firmware
Hi all -
Model SAMSUNG-SGH-1337
Baseband: 1337UCUAMF3
Build: JDQ39.1337UCUAMF3
First off, I have an Samsung Galaxy S4 ATT SGH-1337. I have lurked around these forums and have come to understand the rooting / recovery flash processes. Getting root on the phone is no problem using the following method: http://forum.xda-developers.com/showthread.php?t=2387577
Where my issue lies is within the recovery mode. I have tried GooManager / RomManager / CASUAL /ODIN and nothing I try seems to work. It short when I use CWM or GooManager or CASUAL everything works correctly and I receive no errors. When I first tried this i used GooManager and when it went to reboot into recovery mode It said COULD NOT DO NORMAL BOOT and put me in download mode - in short my stock recovery mode is gone/corrupted.
No matter what I try via (STOCK FW load for example) ODIN i always get a FAIL and can not get it to work. It should be noted that I have the correct USB driver installed also official USB cable and I've tried many versions of ODIN with the same result. It looks like it always fails on write. When I re-try the other methods to install a custom recovery they seem to work but I end up with the same COULD NOT DO NORMAL BOOT.
I thought I was stuck in this download mode until I rebooted the phone manually put in download mode and smashed VOL-DOWN. When I did this the phone booted up.
The strange part is that I have root, and can get into the OS, but all the recovery methods seem to fail. I have even tried the DD method via TWRP page with no luck.
I do not understand why this is the case, or why when I first did this with Goomanager it hosed my recovery mode. I am literally out of ideas, and have tired everything I can think of to get a recovery mode installed.
It should be noted that all the "gotya's" are enabled such as USB Debugging, and version verification. I do notice that when download mode appears, and i see COULD NOT DO NORMAL BOOT it does say "WRITE PROTECTION ENABLED". From my Googleing it would appear this is ok.
I have also made sure I was using the LOKI exploit; but it simply seems that my bootloader is locked no matter what I try.
If anyone has any ideas I would greatly appreciate it.
Thanks
-Ya5e
Ya5e said:
Hi all -
Model SAMSUNG-SGH-1337
Baseband: 1337UCUAMF3
Build: JDQ39.1337UCUAMF3
If anyone has any ideas I would greatly appreciate it.
Thanks
-Ya5e
Click to expand...
Click to collapse
One thing I could think of trying is taking a look at this video here on how to install CWM Recovery on the ATT Galaxy S4. As you watch the video make sure you've done everything exactly as he has done in the video, this way you can determine if you have overlooked or missed any steps.
Thanks for the video link. However it looks like this won't work due to the MF3 firmware.
Q6: I have a AT&T S 4 (OTA MF3) and I have rooted my device can I install a custom rom or a custom recovery?
The answer is "NO" you can not install a custom recovery or a rom at this moment.
Click to expand...
Click to collapse
I found the above in this thread http://forum.xda-developers.com/showthread.php?t=2413746&nocache=1
My phone came with MF3; I would assume this is the issue.
=(
so I managed to root my device without bricking it
and now I needed the twrp recovery thing so I could install cm 10.2
now I followed some tut on youtube that told me to use flashify which I did and I then downloaded some old version of twrp with it
when I rebooted my device it said safe reboot error or something.. and now it does nothing (freaking out here)
it won't turn on even when I try to reboot into recovery when I put it in my pc it shows like 10 storage devices that I need to format
pleasse help me (I had this phone for less than a week now))))))
ipsmaxes said:
so I managed to root my device without bricking it
and now I needed the twrp recovery thing so I could install cm 10.2
now I followed some tut on youtube that told me to use flashify which I did and I then downloaded some old version of twrp with it
when I rebooted my device it said safe reboot error or something.. and now it does nothing (freaking out here)
it won't turn on even when I try to reboot into recovery when I put it in my pc it shows like 10 storage devices that I need to format
pleasse help me (I had this phone for less than a week now))))))
Click to expand...
Click to collapse
First step: Don't panic!
Second step: Tell us which version of the G2 you have (carrier) and which update you had on before things went south, and also which version of TWRP you have.
Third step: Please explain what you mean by it not turning on but plugging it into the PC shows odd things.
Does that mean you CAN still get into recovery? Can you get to download mode? But either way, just stay calm. I just helped my buddy with the ATT version fix his phone from a similar issue a couple of days ago and I have also played with the Sprint version quite a bit and am familiar with LGs in general. Lemme know these things and I can help get you back on the right track.
Can you get into recovery mode?
If you can, try the factory reset and reboot your device.
Does your phone connect to adb?
If so i guess you could flash a fresh rom from there.
Correct me if i'm wrong, i am a new user with slight experience.
Same Thing Happened to Me
I'm freaking out a bit as well. I tried the Flashify method of installing TWRP and got the error message followed by a blank unresponsive phone. Got there via a "Phone Tech Kid" video explaining how to install TWRP. Plugging it into my computer results in being able to open a "drive" with one folder titled "image". The image file that I flashed is 2.6.3.2-g2vzw obtained via a link from this video:
Has anyone come up with a solution?
alferdjeffers said:
I'm freaking out a bit as well. I tried the Flashify method of installing TWRP and got the error message followed by a blank unresponsive phone. Got there via a "Phone Tech Kid" video explaining how to install TWRP. Plugging it into my computer results in being able to open a "drive" with one folder titled "image". The image file that I flashed is 2.6.3.2-g2vzw obtained via a link from this video:
Has anyone come up with a solution?
Click to expand...
Click to collapse
Probably would be best to start your own thread. However, what update were you on? I'm hoping that you do have the Verizon version of the G2? What error is on the screen? But generally speaking, you should be able to boot to the software update mode and re-install the stock OS with the kdz file, for most G2 things. I haven't worked on a VZW one though, only Sprint and T-Mobile ones and they're all a bit different.
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!