Related
Hi All,
I have used CF-Auto-Root when I first got my phone about 3 months ago and rooted successfully and it changed my device status from Official to custom and therefore I was never able to check for OTA or install them.
I have also tried CF's Triangle Away at that time but it never set the status back to Official until last night when I installed the latest TA version 3.05 and this had worked it's magic and my phone status is now back to Official and I found an available OTA and downloaded it but I have not installed it yet. Why? Because I am almost sure I will lose root after installing the OTA update and I am not sure if I am able to re-root it again as I have heard and read that Samsung is trying to lock things down to make it harder for us to play around with our phones.
I My current build number is JDQ39.I9505XXUAMDE so if I am not mistaken, that means I am on firmware XXUAMDE.
The phone does not tell me any info after it completed the OTA download about this upfate apart "Stability Improvement"
My questions are:
1. How can I tell if this new firmware is not going to lock things down?
2. Would I be able to easily re-root after completing the firmware update?
I just plugged in my phone to my computer and Samsung Kies is telling me this:
Current firmware version : PDA:MDE / PHONE:MD8 / CSC:MD8 (VAU)
Latest firmware version : PDA:MG4 / PHONE:MG1 / CSC:MG1 (VAU)
and asking me if I want to upgrade.
Can someone help me answer my questions and clear this for me?
Sorry for all these questions but I am just a little worried this update will be a bad move and I don't want to regret it.
Thanking you in advance for putting up with me and my apologies if some of these questions are repeated or dumb.
AFAIK, MG4/MG1 is not sooo new, and it's still not afected by the 'knox' bootloader thing.
I upgraded to MGA (AMN) some 3 weeks ago, using KIES, temporarylly lost root, but flashet CF Auto Root again, and .... voila! good to go again.
.... oh yes, I had to install supersu again from play store (somehow it was rooted, but the application was not there).
Hope that can help you!
Bak
Thanks Bak for the info.
I was doing some more googling and I came across these 2 pages:
http://www.ibtimes.co.uk/articles/4...ial-android422-xxuamde-jellybean-firmware.htm
http://www.ibtimes.co.uk/articles/4...roid422-xxuamdn-jellybean-official-update.htm
There is something wrong here as my phone is I9505 and it came with the amde unlike what is suggesting that official firmware for I9505 is amdn.
I got my phone from Voda Australia hence the VAU.
If I am reading this correctly:
Current firmware version : PDA:MDE / PHONE:MD8 / CSC:MD8 (VAU)
Latest firmware version : PDA:MG4 / PHONE:MG1 / CSC:MG1 (VAU)
Then after the OTA update then I should be on XXUAMG4 ? I really don't get this whole PDA / PHONE / CSC variables.
I am just tempted to install it and thinking if anything goes wrong or not to my liking then I can use the link I provided above to flash my phone with the official xxaumdn and this does not have the "knox" bootloader thing?
good decision mate! dont flash to the latest MH8 firmware cuz it locks out your fone.
sadly i've flashed mine without reading around. little did in know, MH8 includes knox with locked my phone.
right now i'm having root problems. tried using CF 1.60 the latest one.. which they said can bypass the knoxx thing. we'll i'm still having problems getting root access.. IDK why.
just wait and see. a dev might come up with some work around this KNOX bootloader thing
Saturn007 said:
Thanks Bak for the info.
I was doing some more googling and I came across these 2 pages:
http://www.ibtimes.co.uk/articles/4...ial-android422-xxuamde-jellybean-firmware.htm
http://www.ibtimes.co.uk/articles/4...roid422-xxuamdn-jellybean-official-update.htm
There is something wrong here as my phone is I9505 and it came with the amde unlike what is suggesting that official firmware for I9505 is amdn.
I got my phone from Voda Australia hence the VAU.
If I am reading this correctly:
Current firmware version : PDA:MDE / PHONE:MD8 / CSC:MD8 (VAU)
Latest firmware version : PDA:MG4 / PHONE:MG1 / CSC:MG1 (VAU)
Then after the OTA update then I should be on XXUAMG4 ? I really don't get this whole PDA / PHONE / CSC variables.
I am just tempted to install it and thinking if anything goes wrong or not to my liking then I can use the link I provided above to flash my phone with the official xxaumdn and this does not have the "knox" bootloader thing?
Click to expand...
Click to collapse
Just checked with www.samfirmware.com
If you select the 'check your firmware', you'll see that the last version for i9505 and Australia VAU (vodaphone) is PDA:MG4 / PHONE:MG1 / CSC:MG1
So your carrier (vodaphone) hasn't released the MHx version yet (versions MHx hsve the knox thing)
PDA / PHONE / CSC are different pieces of the software/firmware, and may have different releases (you can even play with different ones, for instance, a diferent PHONE to be able to sim unlock, etc....)
If I was you, I'd let KIES do the update (it's the safest, together with the OTA), and re-root it.
Good luck
Bak
Thanks Bak. I upgraded over the weekend and re-rooted it and all is back to normal now.
I even got Triangleaway to reset counter and back to official status.
Thanks for all your info.
Hi,
i got a Samsung Galaxy Note 3 with Android 4.3 currently installed.
I would like to update it to 4.4.2 but i have several questions before i want to take the risk of updating the device.
As a german user i downloaded this firmware file from sammobile.com:
N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME.tar.md5
This should be the german unbranded 4.4.2 firmware file for the Note 3 N9005.
After reading a few tutorials i saw some people who have problems while flashing this Firmware, because of that i hope you can help me here.
First question:
In Odin i can select the "Phone Bootloader Update", some people are saying i have to select this or the device or it won't work properly after the flash.
Do i have to select this and what happens when i do it?
Second question:
A lot of people also have problems while flashing this firmware because of a missing .pit file (-> http://forum.xda-developers.com/showthread.php?t=2664461)
So do I have to select an .pit file or not?
I really, really hope you can help me with that because Google couldn't help me at all so far.
Geicher said:
I would like to update it to 4.4.2
Click to expand...
Click to collapse
I am actually trying to do the very same thing
The thing is: if you didn't already get an update OTA / via kies (since samsung rolled out kitkat in germany a few days ago) chances are, you are not having a german phone, like myself.
so please enter *#1234# into the dialer app and post the results
also, it would be nice to know your country/product code: if you happen to have the box the phone came in, check the label where your imei and gsm frequencies are mentioned.
There, you'll find a string like "SM-N9005ZKEROM" which (in my case) means a black note 3 from romania
or hook it up with kies and tell the last three characters between the brackets in your firmware version
to your first question: uncheck it. AFAIK, if it is set, the firmware will flash a new bootloader onto your device, and in most cases you don't want that, it could mess your phone up badly. correct me if i'm wrong.
Back to the rom, which also addresses you 2nd question:
The actual problem with simply flashing the DBT rom is that the EU devices happen to be partitioned differently from the german ones, so odin will fail if you have a device with an uncompatible CSC/Product code (e.g. an east-european device), which in turn may or may not trigger knox and/or void your warranty.
i currently try to get more information on that topic.
nevertheless, pocketpc.ch provides a tutorial which mentions flashing DBT firmware along with a custom pit file, which may or may not void your warranty, but doesn't seem to trigger knox (pm me for a link or google it yourself: "Flashen der DBT-FW auf EU-Geräte")
Thank you very much for your detailed answer, as far as i know i will receive the device tomorrow. (Amazon DE order)
I will post the details as soon as i have access to them!
Hi,
I have tried with the one here, and it does not accept my device.
I become the following error message:
=================================
[*] Starting rooting program.
ro.build.product=jflte
ro.build.id=JSS15J
setsockopt<> failed: Bad address.
this device is not supported.
kallsyms_addresses search failed.
[*] Checking if rooting succeeded
[*] Unfortunately, rooting failed. Cleaning up.
=================================
I thought, this method runs on every stock from 4.3. I have the following: I9505XXUENAA_I9505YBTENB2_I9505XXUENAA_HOME.tar
Does someone knows a link with a newer version for my firmware? Or could the developer write it for this firmware? All the olders firmware from 4.3 also are supported.
Because I am a newbie, I cant post directly in the thread.
I would appreciate very much, if someone could help me.
I need a method, that dont triggers knox warranty.
Thanks in forward.
Hi,
I think the link you mentioned is showing the latest version of the saferoot script.
I used it last week for my: JSS15J.I9505XXUEMKF and it worked perfectly.
I first installed Samsung Kies version 3 and the I used the youtube link in post #1 to check what to do.
Some steps showed different, but eventually, with a good result.
I am not sure if your version of the firmware is any different than mine. I hope you will get it to work.
Good Luck.
Thanks, my version is different. You have firmware ...MKF, I have the latest ...NAA.
Both of them are Android 4.3, but the version has little updates, like missing 3g after deep standby, and so on.
I think the script is still not optimized for ...NAA.
RobertdeHoop said:
Hi,
I think the link you mentioned is showing the latest version of the saferoot script.
I used it last week for my: JSS15J.I9505XXUEMKF and it worked perfectly.
I first installed Samsung Kies version 3 and the I used the youtube link in post #1 to check what to do.
Some steps showed different, but eventually, with a good result.
I am not sure if your version of the firmware is any different than mine. I hope you will get it to work.
Good Luck.
Click to expand...
Click to collapse
Hey All,
I got a Note 3 N9005, which supposedly was purchased in UAE.
Currently trying to use it in India, but, the device always says "No Service", with a crossed circle instead of network signal icon on notification bar.
Phone is on 4.2.2 with UGNH1. Below are some observations:
- Phone does NOT ask for any PIN / Unlock Code.
- In Settings > Status.. irrespective of any SIM, or no SIM.. Mobile Network Type = Unknown, Service State= Out of service, Mobile Network State=Disconnected.
- Orig CSC code is displayed as XTC from Phone Info App
- Tried to select a different CSC from CSC Select app.. it changed the boot logo but, network status.. still crossed circle
- IMEI is proper as printed below the battery
- Still i tried ChainFire's RegionLockAway. But, as expected, the method is only for MI7 / MJ1 / MJ3 JB versions. Sadly mine has already crossed and has A2 bootloader. So, no change was observed with CF RegionLockAway. Reverted the cahnges.
- Tried to flash MJ1 / MJ3 binaries from sammobile. As expected the latest bootloader won't allow to downgrade.
- Flashed Omega, but for no luck. Still no service and crossed circle icon.
- Flashed latest CyanogenMod. Though there was no Crossed Circle icon, there was an icon of network signal with zero network.
- Flashed official Lollipop verson to see if any changes.. no luck. Reverted back.
- Installed advanced network info app, network status, neighboring MSC, cells.. etc was shown as none.
No clue how to enable the device's network capabilities (all else like WiFi and other feature work as usual).
It will be a great help if you can guide me through! Please let me know if any other info is required.
Thanks a lot in advance. !!
Purchased in UAE doesn't necessarily it was a UAE phone. Phone Info Samsung from Play Store can tell you where it is from.
What I would do is...
Download the firmware from Sammobile to suit your phone. One fairly common issue is that Hong Kong or Chinese phones get sold into Europe or other markets and their PIT and other partitions are different. So first thing is to go back to scratch.
If you phone IS from where you think, make sure you have the stock firmware for that location and flash the latest version using Odin and Download mode.
Start Odin - v3.09 is best.
To enter DL mode for anything to do with BL or Modem you MUST turn phone off. It is best to remove the battery and wait a while, then put it in and use the Power On+Vol-Down+Home key to get into DL mode, then [plug phone into PC and wait for Odin to notice it is there.
(if Odin doesn't notice it, get the latest Samsung USB drivers for the phone and install them with phone unplugged, then plug in phone and Windows should give a pop-up)
Click on AP in Odin and navigate to where you saved the firmware - note you DL'd a zip but you need the md5 file so use 7zip to unpack the zip.
Click on the md5 file and wait for it to load into Odin.
* [Auto Reboot] and [F.Reset Time] should be the ONLY things ticked.
Click [Start] and wait.
Let phone restart and set it up with your details. Once done see if you have network.
Journyman16 said:
Purchased in UAE doesn't necessarily it was a UAE phone. Phone Info Samsung from Play Store can tell you where it is from.
......
Let phone restart and set it up with your details. Once done see if you have network.
Click to expand...
Click to collapse
Thanks Journyman16 for the quickreply.
I installed the "Phone Info Samsung" app as you mentioned and found the phone's CSC code is XTC! (= Philippines (Open Line))!!
Thanks for the hint. I will download the latest firmware from sammobile for n98005 for XTC and check. Will be back with updates in some time.
maesiva said:
Thanks Journyman16 for the quickreply.
I installed the "Phone Info Samsung" app as you mentioned and found the phone's CSC code is XTC! (= Philippines (Open Line))!!
Thanks for the hint. I will download the latest firmware from sammobile for n98005 for XTC and check. Will be back with updates in some time.
Click to expand...
Click to collapse
Update:
Flashed below 3 stock firmwares from sammobile, each time cleared cache and factory wipe.. still the crossed circle is hopelessly adamant and persistent.
4.4.2 N9005XXUGNH1
4.4.2 N9005XXUGNI4
4.3 N9005XXUDMJ7 (failed to flash, i guess due to current bootloader version A3)
I tried with Odin 3.09.3 & 3.10.6 & 3.07 .... same result.
Any suggestions? please share.. I'm ok to soft brick the phone Recovered from boot loop few times
Any further suggestions? Please share.. Shall i give a try with full wipe (/system/ folder wipe) with TWRP ? Or any other thing ?!
Tried a different sim card ??
Checked APN settings .
Checked you have modem/ baseband via settings .
maesiva said:
Update:
Any suggestions? please share.. I'm ok to soft brick the phone Recovered from boot loop few times
Any further suggestions? Please share.. Shall i give a try with full wipe (/system/ folder wipe) with TWRP ? Or any other thing ?!
Click to expand...
Click to collapse
They are old stock ROMs - how sure are you the phone wasn't updated to the new version of BL? I'm not sure if you're on the new version and then try to downgrade it, which version you will see in Phone Info but check it. There's also a phone # code to use that returns the basics for the phone, but I can't recall if you said you get calls or not and I'm heading for bed. Think the code is something like *#12334#* - google for secret smartphone codes.
JJEgan said:
Tried a different sim card ??
Checked APN settings .
Checked you have modem/ baseband via settings .
Click to expand...
Click to collapse
Hi JJEgan, thanks for your suggestions..
I tried with different SIM, yet no luck.
APN settings.. shows my SIM operator's default settings.
When I search networks Manually.. it searches for a ~10 seconds and returns without any list/error.
Select automatically shows "Automatic registration.." progress continuously for > 5 mins.. i closed manually.
Attached screenshot of Baseband, Modem, CSC versions.
AP: UGNH1
CP: UGNH1
CSC: BGNH1
Baseband: UGNH1
Kernel: 3.4.0-1955971
Journyman16 said:
They are old stock ROMs - how sure are you the phone wasn't updated to the new version of BL? I'm not sure if you're on the new version and then try to downgrade it, which version you will see in Phone Info but check it. There's also a phone # code to use that returns the basics for the phone, but I can't recall if you said you get calls or not and I'm heading for bed. Think the code is something like *#12334#* - google for secret smartphone codes.
Click to expand...
Click to collapse
Yea Journyman16, they seem to be still good old of 4.4.2. Latest must be 5.0. On samobile, for XTC i could see only till 4.4.2. Maybe for this phone version, there are no updates? Not sure.
And, yes, sadly BL is updated to A3. Which I could see in Recovery mode's REV line. (if it was A1, I could have flashed MI7 and tried RegionLockAway.. )
*#1234# gives the below info:
AP: UGNH1
CP: UGNH1
CSC: BGNH1
Any heads up ?!
/system/csc/GLB/system/csc/customer.xml has a line:
<NbNetworkLock>1</NbNetworkLock>
Which ChainFire's RegionLockAway changes to
<NbNetworkLock>0</NbNetworkLock>.. but as mentioned in it's details, the method is compatible only with MI7, MJ1, MJ3 firmwares and i'm on UGNH1 and unable to downgrade
Chainfire said:
Sammy, in their never-ending quest to make sure they've pissed off every single one of their customers at least once, have decided to region lock their latest model devices.
...
Compatible devices
- Galaxy Note 3 SM-N9005 (MI7, MJ1, MJ3 firmwares)
...
Click to expand...
Click to collapse
Any method to downgrade the BL to A1 would help !?
Attached adb logs, if of any use to analyze.
aeroplaemodeoffon.log
boot.log
networksearch.log
shutdown.log
maesiva said:
Attached adb logs, if of any use to analyze.
aeroplaemodeoffon.log
boot.log
networksearch.log
shutdown.log
Click to expand...
Click to collapse
I'd upgrade rather than try to get around the downgrade issues. What Region do you WANT to have? European ones seem to get early release of upgrades - e.g. many LP ROMs are based around the Polish release.
I don't know enough to interpret logs, but my thought would be to find a non-Philippines version (one of the Europe ones perhaps) and find a PIT file for that one. Then go read up on how to safely flash a new PIT. Then flash your preferred firmware and follow the root process etc.
I started with a HK version of S3 - every time I tried to flash a new ROM it failed and bricked my phone. Eventually I found that the PIT file on most Asian phones was different and I flashed PIT, then stock FW for the region I wanted then re-rooted and flashed the custom ROM.
Read many time, flash once, OK? I do not make bricks, nor need them, so I will not accept them delivered to my door...
Journyman16 said:
Read many time, flash once, OK? I do not make bricks, nor need them, so I will not accept them delivered to my door...
Click to expand...
Click to collapse
good one
maesiva said:
good one
Click to expand...
Click to collapse
There's a Euro PIT on the link at This Post - I checked and the dropbox is still valid. It's 4.4.2 so could be just what you need.
Now you probably want an India ROM but I haven't any links for that 0 there's a thread for India users though I think.
What I think might be happening is that different countries use different frequencies and formats for signal. It might be that India's set up simply doesn't work with the modem you've been using and the India ROM will not set up with the Asian PIT set up etc.
But read up on the process first, OK? The more you know about it the better chance you have to recover from anything going wrong.
Also, I presume from your OP that the phone NEVER worked once you got it? Do you know for a fact it worked prior to that? Maybe you're chasing solutions for a faulty hardware issue?
Journyman16 said:
There's a Euro PIT on the link at This Post - I checked and the dropbox is still valid. It's 4.4.2 so could be just what you need.
....
Also, I presume from your OP that the phone NEVER worked once you got it? Do you know for a fact it worked prior to that? Maybe you're chasing solutions for a faulty hardware issue?
Click to expand...
Click to collapse
Hi Journyman16, thanks for the suggestions.. i tried the pit file you referred, but, still no luck. And, if i'm not wrong pit file is all about allocating ROM space for /system & /dbdata and has nothing to deal with the antenna/telephony module, please correct if i'm not right.
About the phone's status yea you're right. It never worked after i received it. But, it was working usually in UAE, as per the info i got. Maybe.. as you suspected.. it might be faulty hardware too.. I don't know.. just exploring the options.. to conclude something..
maesiva said:
And, yes, sadly BL is updated to A3. Which I could see in Recovery mode's REV line. (if it was A1, I could have flashed MI7 and tried RegionLockAway.. )
*#1234# gives the below info:
AP: UGNH1
CP: UGNH1
CSC: BGNH1
Any heads up ?!
Click to expand...
Click to collapse
The only unbranded NH1's seem to be Greece or Netherlands. Netherlands has a 5.0 - maybe DL that and flash in Odin? Greece has a v5.0 but it's branded with (EUR) so I don't know if that's a company or general... I'd go the Netherlands one.
Other than that, I'm not sure - might be time to get the phone checked properly?
Finally.. could trace the root cause.. antenna / receiver chip malfunction. So, it was an hardware issue that had to be replaced at a cost at service center.
Summary: If network icon is crossed circle, its not a good sign !! Thanks
Journyman16 said:
Journyman16
Click to expand...
Click to collapse
,
JJEgan said:
JJEgan
Click to expand...
Click to collapse
!!
I need your help. I have a problem after flashing lollipop firmware on samsung galaxy note 3, sm-n900s the signal or the device has no service. Any modem use to flash?
Please, I need your help xda devs as soon as possible. Really appreciated. Thank you.
Naedean said:
I need your help. I have a problem after flashing lollipop firmware on samsung galaxy note 3, sm-n900s the signal or the device has no service. Any modem use to flash?
Please, I need your help xda devs as soon as possible. Really appreciated. Thank you.
Click to expand...
Click to collapse
Please search and read before posting.Multiple identical questions posted day after day .
Usual is wrong IMEI .
Sent from my SM-N930F using XDA-Developers Legacy app
After a whole week of searching and tripping knox i finally done it:
SM-G9208 root
After using CROM service and unlocking the CROM using ODIN to flash the attached file.
The source is this:
http://apk.tw/thread-704730-1-1.html
http://pan.baidu.com/s/1ntu1gjn
No credit to me
Here is my uploaded copy:
http://farzad.devbro.com/SM-9208_root_0902.tar
Dude, you saved my life
Was about to sell my s6 when I saw this man. Thank you so much
Edit: By any chance can you reupload the file here? Takes so long to download because it throttles at 25 kbps for me :/
Edit 2: Nvm got it to download fast haha FINALLY ROOT ACCESS!!
u root without tripping knox ?
ham4ever said:
u root without tripping knox ?
Click to expand...
Click to collapse
My knox was tripped before hand. Not sure if it does or not.
JoeCatarata said:
Was about to sell my s6 when I saw this man. Thank you so much
Edit: By any chance can you reupload the file here? Takes so long to download because it throttles at 25 kbps for me :/
Edit 2: Nvm got it to download fast haha FINALLY ROOT ACCESS!!
Click to expand...
Click to collapse
What is your Knox status?
Is it also for g920f with coh2? Knox?
devbro said:
What is your Knox status?
Click to expand...
Click to collapse
Don't really know how to check lol haha
JoeCatarata said:
Don't really know how to check lol haha
Click to expand...
Click to collapse
my knox is tripped.
After following this method I get a bootloop, any idea why and how to correct it?, already tried a factory reset but it doesn´t work, I had to flash stock rom again.
Edit: It happens because I upgraded to the latest 5.1.1 version available last week:
Model SM-G9208
Model name GALAXY S6
Country Taiwan
Version Android 5.1.1
Changelist 5683207
Build date Tue, 06 Oct 2015 11:54:52 +0000
Product code BRI
PDA G9208ZTU2COJ2
CSC G9208ZZT2COJ2
So if you get the update alert in your phone DON´T do it, there is no known way to ROOT this new version.
It was not possible to install a previous 5.1.1 version either (G9208ZTU1BOH2), when I try to flash it with ODIN, the phone just displays an error message “SW REV CHECK FAIL DEVICE 2 BINARY 1”.
Any Ideas are appreciated.
EDIT:
Finally rooted with xiao1u root method!
devbro said:
After a whole week of searching and tripping knox i finally done it:
SM-G9208 root
After using CROM service and unlocking the CROM using ODIN to flash the attached file.
The source is this:
http://apk.tw/thread-704730-1-1.html
http://pan.baidu.com/s/1ntu1gjn
No credit to me
Here is my uploaded copy:
http://farzad.devbro.com/SM-9208_root_0902.tar
Click to expand...
Click to collapse
Root works perfectly, but has anybody got TWRP working on 5.1? I've always had unusable touchscreen issues on it so stayed back on 5.0.2 until somebody devs a working build.
Dissmeister said:
Root works perfectly, but has anybody got TWRP working on 5.1? I've always had unusable touchscreen issues on it so stayed back on 5.0.2 until somebody devs a working build.
Click to expand...
Click to collapse
no go. i used the TWRP app to flash all new files.
devbro said:
no go. i used the TWRP app to flash all new files.
Click to expand...
Click to collapse
So your twrp works perfectly on 5.1 base? If so, could you share it with me?
I've been looking for a twrp that worked on 5.1 without the touchscreen not working. Thanks man
Definitely no luck rooting my phone,
Product code BRI
PDA G9208ZTU2COJ2
CSC G9208ZZT2COJ2
The file on first post didn´t work, and 3 days after I rooted (and everything was working perfectly) using this file:
http://pan.baidu.com/wap/album/file...26914354&fsid=128909912720545&adapt=pc&fr=ftw
I get the following error message every time i need root access:
"There is no SU binary installed, and SuperSU cannot install it. This is problem! If you upgraded to Android 5.0, you will need to manually re-root - consult the relevant forums for your device!"
If the phone is restarted or turned off after getting this error message the phone is death, it doesn´t start again.
I tried reflashing the root file, but it didn´t work.
I had to reinstall the stock ROM agan, and waiting for any effective root method for 5.1.1 OJ2 ROM.
0ptimus82 said:
After following this method I get a bootloop, any idea why and how to correct it?, already tried a factory reset but it doesn´t work, I had to flash stock rom again.
Edit: It happens because I upgraded to the latest 5.1.1 version available last week:
Model SM-G9208
Model name GALAXY S6
Country Taiwan
Version Android 5.1.1
Changelist 5683207
Build date Tue, 06 Oct 2015 11:54:52 +0000
Product code BRI
PDA G9208ZTU2COJ2
CSC G9208ZZT2COJ2
So if you get the update alert in your phone DON´T do it, there is no known way to ROOT this new version.
It was not possible to install a previous 5.1.1 version either (G9208ZTU1BOH2), when I try to flash it with ODIN, the phone just displays an error message “SW REV CHECK FAIL DEVICE 2 BINARY 1”.
Any Ideas are appreciated.
EDIT:
Finally rooted with xiao1u root method!
Click to expand...
Click to collapse
Hey, the same thing happened to me, I was stupid enough to not read this before. I tried the xiao1u method and it works, but it breaks mobile data. Did you get that issue?
Dissmeister said:
Hey, the same thing happened to me, I was stupid enough to not read this before. I tried the xiao1u method and it works, but it breaks mobile data. Did you get that issue?
Click to expand...
Click to collapse
Not in my case, my data was working perfectly, but problems started to show up 3 days after I rooted it, in the end it didn´t start again.
I haven´t found any other way to root this build yet and I´m still looking for a custom rom with no success.
If you want to give another try to xiao1u file try to disable the setting for "allow Google to regularly check device activity for security problems or warn about potential harm" after a clean ROM install, you can do it going to the GOOGLE SETTINGS app > SECURITY > VERIFY APPS & uncheck Scan For Security Threats.
Please keep us updated, I´ll post if I find any way to solve it.
0ptimus82 said:
Not in my case, my data was working perfectly, but problems started to show up 3 days after I rooted it, in the end it didn´t start again.
I haven´t found any other way to root this build yet and I´m still looking for a custom rom with no success.
If you want to give another try to xiao1u file try to disable the setting for "allow Google to regularly check device activity for security problems or warn about potential harm" after a clean ROM install, you can do it going to the GOOGLE SETTINGS app > SECURITY > VERIFY APPS & uncheck Scan For Security Threats.
Please keep us updated, I´ll post if I find any way to solve it.
Click to expand...
Click to collapse
Ok you may know this already but I'll post just to let you everybody else know.
DONT UPDATE TO THE LATEST 5.1 OTA. It adds rollback protection to your bootloader, which makes it impossible for you to odin to another build, unless its the same or a future update.
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/general/psa-odin-5-1-1-t3136151
As for our case, mate, I tried everything so far, the root method given by the OP bootloops on the latest OTA (previous 5.1 firmware on Sammobile is fine) and xiao1u method breaks mobile data for me although root does work perfectly. Funny thing is that if you tried the root by the OP and it got bricked, flashing the xiao1u method on top of it will get it working again, because its just the boot partition.
Atm, I just got sick of Samsung and their cr*p, had the same issues with my old Galaxy S4 with their Exynos. Got the Nexus 6P today and absolutely loving it.
I'll try to work it out sometime soon, if I do manage to get it working (mobile data for me) I'll post the fix here. This device is next to DOA for us as we've just got a couple of few blessed asian devs on it (all thanks to them). Unfortunately it may never be enough. I never got the issue you had, though it was just for last night, can you get into download mode? If so, odin the same firmware again. I used the 5.1 OTA on Sammobile, Taiwan. This is only for us who are already stuck in the new bootloader. You wont have root but at least your phone will work.
Cheers mate, all the best. Will update if I find a fix.
Dissmeister said:
Ok you may know this already but I'll post just to let you everybody else know.
DONT UPDATE TO THE LATEST 5.1 OTA. It adds rollback protection to your bootloader, which makes it impossible for you to odin to another build, unless its the same or a future update.
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/general/psa-odin-5-1-1-t3136151
As for our case, mate, I tried everything so far, the root method given by the OP bootloops on the latest OTA (previous 5.1 firmware on Sammobile is fine) and xiao1u method breaks mobile data for me although root does work perfectly. Funny thing is that if you tried the root by the OP and it got bricked, flashing the xiao1u method on top of it will get it working again, because its just the boot partition.
Atm, I just got sick of Samsung and their cr*p, had the same issues with my old Galaxy S4 with their Exynos. Got the Nexus 6P today and absolutely loving it.
I'll try to work it out sometime soon, if I do manage to get it working (mobile data for me) I'll post the fix here. This device is next to DOA for us as we've just got a couple of few blessed asian devs on it (all thanks to them). Unfortunately it may never be enough. I never got the issue you had, though it was just for last night, can you get into download mode? If so, odin the same firmware again. I used the 5.1 OTA on Sammobile, Taiwan. This is only for us who are already stuck in the new bootloader. You wont have root but at least your phone will work.
Cheers mate, all the best. Will update if I find a fix.
Click to expand...
Click to collapse
The results of my attempt to root is not very consistent or stable since 5.02 to 5.1.1 on different updates of the Taiwan variant (G9208).
Since first 5.1.1 update, I used xiaolu method and succeed for few days, I don't know what do you mean " xiao1u method breaks mobile data", my 4G signal was fine. With xposed hooked, I also observed the much more boot time of previous rooted phone, sometimes a smaller bootloop (3 or 4 repeated loops).
But after a very recent "samsung security policy update", the root has "gone" an re-root became impossible no matter by xiaolu's or chainfire UPDATE-SuperSU-v2.46, most time they will cause bootloop and I can use odin to get back to initial status. Does that mean I don't have hope to root again?
Dissmeister said:
So your twrp works perfectly on 5.1 base? If so, could you share it with me?
I've been looking for a twrp that worked on 5.1 without the touchscreen not working. Thanks man
Click to expand...
Click to collapse
This works on my Taiwan variant G9208 on stock 5.1.1,
Go on TWRP repository of dl.twrp.me/zeroflte, seek two .tar files as below and inject them stepwisely with different method
1st (Odin via USB). Twrp-2.8.7.2-zeroflte.img.tar
2nd(use that TWRP -2.8.7.2, operate via an "OTG linked usb mouse" since touch not working...) . to flash Twrp-2.8.7.0-zerofltespr.img (but it's actually 2.8.7.1)
now you have a touchable TWRP.
But I can't get root now, even with xiaolu method, any one with luck, please note me
ttyy121 said:
The results of my attempt to root is not very consistent or stable since 5.02 to 5.1.1 on different updates of the Taiwan variant (G9208).
Since first 5.1.1 update, I used xiaolu method and succeed for few days, I don't know what do you mean " xiao1u method breaks mobile data", my 4G signal was fine. With xposed hooked, I also observed the much more boot time of previous rooted phone, sometimes a smaller bootloop (3 or 4 repeated loops).
But after a very recent "samsung security policy update", the root has "gone" an re-root became impossible no matter by xiaolu's or chainfire UPDATE-SuperSU-v2.46, most time they will cause bootloop and I can use odin to get back to initial status. Does that mean I don't have hope to root again?
Click to expand...
Click to collapse
It happened the same way with my phone, no hope so far.
Has anybody tried arter97 kernel?, G9208 support was added in the last beta but the problem is OJ2 particular release.
http://forum.xda-developers.com/showpost.php?p=63345352&postcount=2080
What is possible with this model?