Related
Update for Galaxy Note 8.0 LTE (GT-N5120) are out today
Model: GT-N5120
Country: United Kingdom
Version: Android 4.2.2
Changelist: 1210063
Build date: Thu, 01 Aug 2013 12:21:19 +0000
Product Code: BTU
PDA: N5120XXCMH1
CSC: N5120BTUCMH1
MODEM: N5120XXCMG7
Get it Here
Changelist is the same as the former UK 4.2.2 release, so no idea what changed really.
Will download, update and report back
Slipurson said:
Update for Galaxy Note 8.0 LTE (GT-N5120) are out today
Model: GT-N5120
Country: United Kingdom
Version: Android 4.2.2
Changelist: 1210063
Build date: Thu, 01 Aug 2013 12:21:19 +0000
Product Code: BTU
PDA: N5120XXCMH1
CSC: N5120BTUCMH1
MODEM: N5120XXCMG7
Get it Here
Changelist is the same as the former UK 4.2.2 release, so no idea what changed really.
Will download, update and report back
Click to expand...
Click to collapse
Any update on what the differance is over the previous release?
If this ROM causes the S-Pen to have an offset, please let us know here:
4.2.2 Update S-Pen Inaccuracy Thread
KTM690 said:
Any update on what the differance is over the previous release?
Click to expand...
Click to collapse
I cant find any differences at all actually, the offset for the S-Pen is there still and everything else works just as it did with the previous 4.2.2
CafeKampuchia said:
If this ROM causes the S-Pen to have an offset, please let us know here:
4.2.2 Update S-Pen Inaccuracy Thread
Click to expand...
Click to collapse
Ill post my findings in the thread.
I am assuming you are talking about the browser bug? That was an issue with chrome's zoom being inaccurate on, frankly, every Galaxy Note up until now. They fixed it recently.
Sent from my SAMSUNG-SGH-I467 using xda premium
'H+' vs 'H' Icon
Hi
Just flashed this ROM on my HK Note N5120 LTE (CSC Was TGY). The device came from Panamoz.com as I was struggling to buy the LTE version sim free in the UK for reasonable money, and Kies was not offering to upgrade the stock 4.1.2 firmware to 4.2.2.
Used this method: http://forum.xda-developers.com/showpost.php?p=44241666&postcount=4
All worked fine, Answered 'No' when asked about making CWM recovery permanent. The CSC became BTU (UK) after the flash. CWM recovery was replaced with stock during the flash.
Since I am in the UK, I flashed the modem files that came with the ROM, and still get 4G. I have the same issue as everyone else regarding the S-Pen offset - probably not bad enough to flash back to 4.1.2 for me, but hopefully Samsung will fix.
My main issue is that compared to 4.1.2, I hardly ever see the device show 'H+', only 'H'. I travel the same route on the train daily, and now, I see 'H+' 10% of the time rather than 90% of the time. My other device on the same network still shows H+.
Maybe others have seen my 'H' vs 'H+' issue?
Does this device support DC-HSPA?? I recall that with the S3 and Note2, one gained DC-HSPA+42 (so called 3.75G theoretical max 42Mbps), when one bought the LTE version of the phone. The non LTE versions only had HSPA+21. Reason I am asking is I am wondering if the 'H+' now only shows for DC-HSPA rather than for HSPA+21 ??
Tempted to flash the old modem files again, see if my H+ returns to normal operation - and of course to see if its any faster.
My device is still rooted with the flash counter == 2, and It does still appear to be recognized by kies when connected to the PC. Time will tell whether I will get updates via Kies still. If not then maybe I will need to use Triangle to reset the flash counter, and then do a full unroot.
Nigel
veletron said:
Hi
Just flashed this ROM on my HK Note N5120 LTE (CSC Was TGY). The device came from Panamoz.com as I was struggling to buy the LTE version sim free in the UK for reasonable money, and Kies was not offering to upgrade the stock 4.1.2 firmware to 4.2.2.
Used this method: http://forum.xda-developers.com/showpost.php?p=44241666&postcount=4
All worked fine, Answered 'No' when asked about making CWM recovery permanent. The CSC became BTU (UK) after the flash. CWM recovery was replaced with stock during the flash.
Since I am in the UK, I flashed the modem files that came with the ROM, and still get 4G. I have the same issue as everyone else regarding the S-Pen offset - probably not bad enough to flash back to 4.1.2 for me, but hopefully Samsung will fix.
My main issue is that compared to 4.1.2, I hardly ever see the device show 'H+', only 'H'. I travel the same route on the train daily, and now, I see 'H+' 10% of the time rather than 90% of the time. My other device on the same network still shows H+.
Maybe others have seen my 'H' vs 'H+' issue?
Does this device support DC-HSPA?? I recall that with the S3 and Note2, one gained DC-HSPA+42 (so called 3.75G theoretical max 42Mbps), when one bought the LTE version of the phone. The non LTE versions only had HSPA+21. Reason I am asking is I am wondering if the 'H+' now only shows for DC-HSPA rather than for HSPA+21 ??
Tempted to flash the old modem files again, see if my H+ returns to normal operation - and of course to see if its any faster.
My device is still rooted with the flash counter == 2, and It does still appear to be recognized by kies when connected to the PC. Time will tell whether I will get updates via Kies still. If not then maybe I will need to use Triangle to reset the flash counter, and then do a full unroot.
Nigel
Click to expand...
Click to collapse
Just got mine from the same place. Your post has helped me with some questions I had. Thanks.:good:
No OTA For me
So, the next stage was to run Triangle away, which worked fine (counter reset to 'No'). Just be brave and accept the big red warning.
Following on from that, I unrooted using the unroot option in Super User app that was installed by chainfire's 'auto root'.
This worked too, and I confirmed root gone. After a reboot, I reconnected to Kies, to check that it recognized the firmware on the device as the 'latest'. It was.
I then tried the 'Software Update' option under Settings->about device, unfortunately, this no longer works it just says 'connecting to server' forever and eventually comes up with a message: 'your device has been modified, software updates are not available'. So No OTA for me.
Any idea how to get OTA working again??
Here is the screenshot from the downloading screen, showing 'official' for all the firmwares on the device. Could it have something to do with the CSC? (TGY on 4.1.2 and BTU on 4.2.2) ?
http://photos.veletron.com/index.php/album151/P1070688
If I goto Settings-->About Device-->Status, and wait an age while the 'Device Status' field updates, it reports 'custom'. I guess this is why, but how come given that the 'download' screen reports as per the above screen shot?!
Prior to running Triangle Away, and unrooting, the OTA check on the device, span for a while before reporting no new updates available.
Nigel
veletron said:
Hi
Just flashed this ROM on my HK Note N5120 LTE (CSC Was TGY). The device came from Panamoz.com as I was struggling to buy the LTE version sim free in the UK for reasonable money, and Kies was not offering to upgrade the stock 4.1.2 firmware to 4.2.2.
Used this method: http://forum.xda-developers.com/showpost.php?p=44241666&postcount=4
All worked fine, Answered 'No' when asked about making CWM recovery permanent. The CSC became BTU (UK) after the flash. CWM recovery was replaced with stock during the flash.
Since I am in the UK, I flashed the modem files that came with the ROM, and still get 4G. I have the same issue as everyone else regarding the S-Pen offset - probably not bad enough to flash back to 4.1.2 for me, but hopefully Samsung will fix.
My main issue is that compared to 4.1.2, I hardly ever see the device show 'H+', only 'H'. I travel the same route on the train daily, and now, I see 'H+' 10% of the time rather than 90% of the time. My other device on the same network still shows H+.
Maybe others have seen my 'H' vs 'H+' issue?
Does this device support DC-HSPA?? I recall that with the S3 and Note2, one gained DC-HSPA+42 (so called 3.75G theoretical max 42Mbps), when one bought the LTE version of the phone. The non LTE versions only had HSPA+21. Reason I am asking is I am wondering if the 'H+' now only shows for DC-HSPA rather than for HSPA+21 ??
Tempted to flash the old modem files again, see if my H+ returns to normal operation - and of course to see if its any faster.
My device is still rooted with the flash counter == 2, and It does still appear to be recognized by kies when connected to the PC. Time will tell whether I will get updates via Kies still. If not then maybe I will need to use Triangle to reset the flash counter, and then do a full unroot.
Nigel
Click to expand...
Click to collapse
I can not say anything about the OTAupdates since I never use Kies to update, but as for the modem, I am running the "old" 4.1.2 modem and it is working well for me, tho I have not compared my note now and before in regards to how ofteni see H+ or just H, most often I see the 4G icon where I usually hang out.
But I would try the 4.1.2 modem for your region and see if it changes anything.
Sent from Galaxy no. N5120 via the LTE-network
Got mine updated to 4.2.2 yesterday.
Not sure why but my battery life seemed to have taken a hit since upgrading.
On 4.1.2 i used to be able to last a day easily with about 30 - 40% left each day (7am till 9pm). after updating to 4.2.2 I am down to 30% in 5 hrs. Tab gets hotter too. Anyone experience the same issue?
I am back on 4.1.2 for now. Everything's good again.
thanks man for update.
Just for info
After the update to 4.2.2 Mh1 by flashing the firmware here, I never got OTA again (says device status custom). Stock rom and flash counter zero. I was however able to update to MH2 via kies. I am still told device status custom!
No difference for me re pen pointer offset on MH1/MH2 not sure Samsung will ever bother to fix this.
My device now BTU but it started as Hong Kong. I suspect this is why it reckons it's "custom".
Nigel
veletron said:
Just for info
After the update to 4.2.2 Mh1 by flashing the firmware here, I never got OTA again (says device status custom). Stock rom and flash counter zero. I was however able to update to MH2 via kies. I am still told device status custom!
No difference for me re pen pointer offset on MH1/MH2 not sure Samsung will ever bother to fix this.
My device now BTU but it started as Hong Kong. I suspect this is why it reckons it's "custom".
Nigel
Click to expand...
Click to collapse
I have the same device but not the same problem. I also updated to MH2 via Odin and my status is normal. The offset for me is much better than previous, and I have no problem with the battery lasting more than a day using WiFi and push mail along with the normal use. However although recognized by Kies it would not update, I recon because of the CSC.
craylim said:
Not sure why but my battery life seemed to have taken a hit since upgrading.
On 4.1.2 i used to be able to last a day easily with about 30 - 40% left each day (7am till 9pm). after updating to 4.2.2 I am down to 30% in 5 hrs. Tab gets hotter too. Anyone experience the same issue?
I am back on 4.1.2 for now. Everything's good again.
Click to expand...
Click to collapse
Sent from my GT-N5120 using XDA Premium HD app
Battery seem to drain faster since I upgraded to 4.2.2
Multi Window
Hey,
I've update my rom on my 5120 to the MH2 and still having problem with multi window greyed out in the setting>display
Has anybody else have this problem?
Is they any way to fix it?
I upgraded the rom using the odin version 1.85 had the tick in auto reboot and F. Rest time and I ticked PDA and put the md5 file on the pda line where I placed the tick is that all correct or should I've used a different version?
Please can anybody help me.
Thanks
Gigino
THANK YOU! THANK YOU! THAAAAAAAANK YOOOOOOOU! (if it didn't look and/or feel weird, I'd kiss you! *LOL* I wouldn't it was a joke)
BUT you saved my stupid self from self pity. You see, I didn't realize - until too late - that there were 3 versions of this device, and attempted to install a 5110 ROM. That caused me 5 DAYS of hell until I cam across this, and voila! I got my tablet back. So again - TANK YOU THANK YOU THANK YOU!
One Note: Baseband I467MVLAMG2 and Build Number: JDQ39.N5120XXCMH2 (not 1)
_Allan_ said:
THANK YOU! THANK YOU! THAAAAAAAANK YOOOOOOOU! (if it didn't look and/or feel weird, I'd kiss you! *LOL* I wouldn't it was a joke)
BUT you saved my stupid self from self pity. You see, I didn't realize - until too late - that there were 3 versions of this device, and attempted to install a 5110 ROM. That caused me 5 DAYS of hell until I cam across this, and voila! I got my tablet back. So again - TANK YOU THANK YOU THANK YOU!
One Note: Baseband I467MVLAMG2 and Build Number: JDQ39.N5120XXCMH2 (not 1)
Click to expand...
Click to collapse
Great post. I feel your joy
THere is a newer version. Does anyone know how we can go from JDQ39.N5120XXCMH2 to the new JDQ39.N5120XXCMI2 version?
My phone also says custom like Nigels problem above, I am having same problem that he was having when he first went to 4.2.2 from 4.2.1... I'm currently on 4.2.2 trying to go to the new CMI2.
CCJ22 said:
THere is a newer version. Does anyone know how we can go from JDQ39.N5120XXCMH2 to the new JDQ39.N5120XXCMI2 version?
My phone also says custom like Nigels problem above, I am having same problem.
Click to expand...
Click to collapse
I downloaded the CMI2 version from samsmobile site. It was a KIES file extracted the file and using mobile odin flashed it to my device. All working fine.:good:
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.
So today I got my new Note 3. I've been doing some reading but am not sure about the Knox issue.
It's Android 4.3, Baseband - N9005XXUBMI5, Build - JSS15J.N9005ZHUBMI7, and I am being offered an update.
I'm thinking from the threads I am already above the version that let's De La Vega rooting work without tripping Knox? Can I downgrade using Odin, root the phone and then get updates?
Also, what is SELinux status - says it's 'enforcing' - I'll do some searching tomorrow.
Once I worked out how to shut the 'Talkback' voice up it's been enjoyable - nothing quite like having a screen non-responsive because every time you try to do something she yabbers at you in a foreign language. As soon as that turned off the phone behaved properly - very quick too.
More tomorrow - end of a long day here.
need help with this myself
Trying to root this same phone as well.
AP: N9005ZHUBMI7
CP: N9005XXUBMI5
CSC: N9005ZZHBMI7
Can't seem to find any working links for those though.
Rdlv works for pre mj1 firmwares. After mj1 kingo is supposed to work. But didnt for me. Just come to the dark side and trip knox
Journyman16 said:
So today I got my new Note 3. I've been doing some reading but am not sure about the Knox issue.
It's Android 4.3, Baseband - N9005XXUBMI5, Build - JSS15J.N9005ZHUBMI7, and I am being offered an update.
...
Click to expand...
Click to collapse
makaveli72 said:
Trying to root this same phone as well.
AP: N9005ZHUBMI7
CP: N9005XXUBMI5
CSC: N9005ZZHBMI7
Can't seem to find any working links for those though.
Click to expand...
Click to collapse
DO NOT take any update (and also disable the separate SECURITY update).
Read the UNIVERSAL ROOT DE LA VEGA thread.
Found the security update one but it's been on for a day... crossing fingers. I have read a lot of the RDLV thread - one thing I'm not sure of - if I root successfully does an OTA official update trip Knox?
I guess there's a question behind that - if I root and remain on stock ROM, will I get an update at all?
Not particularly worried about it. I figure I'll remain stock for a bit in case the phone plays up but will shortly be rooting and custom ROM'ing like I did with my S3.
Pretty good battery so far - all the setup stuff and configuring and only down to 48% after 16 hours.
double post
Journyman16 said:
Found the security update one but it's been on for a day... crossing fingers. I have read a lot of the RDLV thread - one thing I'm not sure of - if I root successfully does an OTA official update trip Knox?
I guess there's a question behind that - if I root and remain on stock ROM, will I get an update at all?
Not particularly worried about it. I figure I'll remain stock for a bit in case the phone plays up but will shortly be rooting and custom ROM'ing like I did with my S3.
Pretty good battery so far - all the setup stuff and configuring and only down to 48% after 16 hours.
Click to expand...
Click to collapse
No updating via OTA won't trip KNOX, you'll lose root though.
Rooting means your device (depending on the method used) will show custom status and cannot receive OTA updates, but they work via KIES still. URDLV shows Official iirc, so you may be able to update OTA with no issues, but as I said you'll lose root. There are methods of using Mobile ODIN to update and re-root and keep KNOX preserved as well.. But I tripped mine instantly, so not sure how you'd go about it all.
Battery on the Note 3 is a blinder, you think Stock is good, wait til you decide to trip KNOX and install a custom ROM, then you'll see how powerful the battery actually is haha
Well, I will keep reading. If I find a way to do it I will post back here about it. I guess my 1st port of call is the RDLV thread - I need to know if I will trip Knox anyway - if so I'll give it maybe a month to be sure phone isn't faulty then root and custom it. I do miss Greenify...
I'm used to good battery - I was using Purelook 8 on my S3 and getting more than 4 days on med to light use.
And now there's a whole new world to explore...
Another answer I am looking for - is there a way to do a Nandroid backup without root? I want to try some things but don't want to lose all i have done so far.
Journyman16 said:
Another answer I am looking for - is there a way to do a Nandroid backup without root? I want to try some things but don't want to lose all i have done so far.
Click to expand...
Click to collapse
Helium is a good non-root backup tool, although I think you need the premium version for all the features.
Finally Rooted! N9005
Much thanks to @brangalm for his step by step breakdown in the RDLV 0.5 thread; I was able to find my way and got my first Android device (the Note 3 SM-N9005 32GB hdd, 3GB mem, Snapdragon cpu Behemoth of a phone) rooted. His POST really made the process much more approachable.
Only thing, at step 9 and 10 in my case I had to use forward slashes / instead of \ backslashes.
For ex.
[email protected] /cygdrive/c/Users/MaKaveli/Desktop/Note3
$ cd C:/Users/MaKaveli/Desktop/Note3
And
[email protected] /cygdrive/c/Users/MaKaveli/Desktop/Note3
$ ./URDLV.sh full C:/Users/MaKaveli/Desktop/Note3/N9005ZHUBMI7_N9005ZZHBMI7_N9005XXUBMI5_HOME.tar.md5
And at step 22 I would recommend leaving the phone alone for at least 10 mins while it does its thing (rebooting etc.) After seeing 'Pass' in Odin the screen was blacked out for some time..so I say just leave it for a while.
Besides that the root process was straight. Both Knox statuses are 0x0 with Custom status. Woot!
I would thank @brangalm directly in the RDLV 0.5 thread but the xda-dev forum has me as a newb (rightfully so) and has restricted me posting in the developers section for now.
My phone info. for whom it may concern.
Model: SM-N9005
Country: Hong Kong
Version: Android 4.3
Changelist: 1626679
Build date: Wed, 11 Sep 2013 10:54:57 +0000
Product Code: TGY
PDA/AP: N9005ZHUBMI7
CSC: N9005ZZHBMI7
MODEM/CP: N9005XXUBMI5
PS: downloading my stock fw from terafile.co via sammobile.com was a P.I.T.A. Took multiple tries and lots of patience before getting a decent copy.
Congratulations and happy flashing.
I have a GSS4 i9505.
it is unrooted/100% stock, as I do not wish to muck around with any of that just incase the worst happens and it needs to go back to repair again i'd feel safer knowing that its device status remains Official.
about 6 months ago it went back to optus for repair as the battery had swollen leading to problems.... when i got it back the repair slip said, replaced battery, tested phone - no issues, updated to latest firmware.....
which i thought to be weird as i thought i was on 4.2.2 already.
anyway... Optus has now finally released their version of android 4.3... except when i go into phone settings and click update.. it says i am already running the latest version... when i connect to Kies via USB it says "your devices current firmware version is not supported to update firmware via Kies"
in Kies i get
PDA:MDE - PHONE:MD8 - CSC:MD6 (OPS)
when i do *#1234# i get
AP: I9505XXUAMDE
CP: I9505DVUAMD8
CSC: I9595OPSAMD6
i have no idea what any of that means
would i be correct in assuming that since i have never mucked around with roms,etc and the only time anything like that has happened was when it went back to optus for repair.... that optus stuffed something up and that why i cant update ?
If you are sure to be fully stock and unrooted, then maybe kies is gone crazy.
You can manually update your phone by using odin and the last official firmware available on sammobile. (I see that for Australia(Optus) it's the 4.3 MK8)
invano said:
If you are sure to be fully stock and unrooted, then maybe kies is gone crazy.
You can manually update your phone by using odin and the last official firmware available on sammobile. (I see that for Australia(Optus) it's the 4.3 MK8)
Click to expand...
Click to collapse
*NOTICE TO OP
Using this method will trigger KNOX warranty void
cheers.... i had thought of odin but as mentioned about, figured that it'd probably void warranty which i would like to avoid as knowing my luck the screen would all of a sudden stop working and i'd have no way of re-official'ing it.
might just have to take it into optus and get them to update it themselves.
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?