Hi all,
there is a new app for rooting phones, the name is Towelroot and it was made especially for Verizon Glaxaxy s5 but the dev says that every phone with kernel build date < 3 June can be rooted.
With this app you can root Galaxy S4 Mini with kitkat firmware without tripping knox counter. It will stay 0x0 and you will have root access.
First of all you must put a vulnerable kernel with build date <3 june
you can grab one from [INDEX] Official Stock KERNEL collection for Galaxy S4 Mini (Kernel for I9195XXUCNF7 is the one you have to grab to work with towelroot, offcourse if you own an i9195 )
Flash it via odin. Leave everything intact and load the kernel to AP.
After the phone boots, install towelroot, press makeitra1n and you are rooted.
Next step is to install SupserSU from google play.
After all the above steps are done, flash the kernel from your firmware the same way as you did it the first time.
There you go, knox 0x0 and root access.
http://forum.xda-developers.com/showthread.php?t=2783157
Download link?
Inviato dal mio GT-I9195 utilizzando Tapatalk
96DANGER96 said:
Download link?
Inviato dal mio GT-I9195 utilizzando Tapatalk
Click to expand...
Click to collapse
http://towelroot.com/
click the logo and save as
just tried it.rooted successfully the phone in 15 seconds.the bad thing is that I've already tripped Knox warranty so I cannot tell if it stays 0x0.I'm on latest 4.4.2 stock
vriz27 said:
just tried it.rooted successfully the phone in 15 seconds.the bad thing is that I've already tripped Knox warranty so I cannot tell if it stays 0x0.I'm on latest 4.4.2 stock
Click to expand...
Click to collapse
Ooohhh - this is tempting
towelroot did not work for 4.2.2. latest stock for my German device. Can you tell which is your firmeare and if German is a supported language?
I think KNOX should NOT be tripped if you only upgrade to official FW (i.e. kernel and recovery builds have valid checksums) - so how did you get KNOX tripped earlier - for CWM based rooting?
I have latest official stock 4.4.2. which I think is for Belgium,but as far as I know it's the only one that has already came out. German language is fully functional and supported. I live in Greece and Greek language is also supported. I think that official Roms are multilingual
vriz27 said:
I have latest official stock 4.4.2. which I think is for Belgium,but as far as I know it's the only one that has already came out. German language is fully functional and supported. I live in Greece and Greek language is also supported. I think that official Roms are multilingual
Click to expand...
Click to collapse
How can you be sure that the root explot worked from towelroot and not from your actions earlier tripping KNOX?
You have already a custom recovery and custom ROM - this would not be possible without bootloader having KNOX triggered. So I guess that with this price paid you have already rooted the "regular" way - didn't you?
---------- Post added at 06:29 PM ---------- Previous post was at 06:21 PM ----------
Another thing with upgrade is that you may loose your installed apps.
I remember this from my first steps with Xperia Ray some years ago, but this could also have been due to unlocking the bootloader and installing a custom kernel. Back that time I was not so knowing about what should be done in the process of unlocking bootloader, CWM recovery install and finally rooting. I may have scratched data partition that time without knowing what it actually means - and without it being needed as well.
Is this the case here as well? Non-root means no Nandroid backup and so what happens to the data-partition in this process?
---------- Post added at 06:43 PM ---------- Previous post was at 06:29 PM ----------
Finally to all who want to dare testing:
It is highly unlikely that KNOX would be tripped here. As far I understand the process of image integrity that KNOX tries to maintain, the booloader checks if the image checksum of the kernel or recovery partition is intact - at upgrade time (not runtime at boot?). The towelroot exploit is compromising kernel security (aka "exploit") with some instructions (lib\armeabi\libexploit.so) to gain root and retain that state across the re-boot process. I am not aware of the details how this can be achieved (this is real high-tech hackery) - but the towelroot exploit does NOT install SU on system partition yet - this has to happen in a second step - and failed with 4.2.2 stock ROM on my GT-I9195.
So if there is anyone out there with just upgraded 4.4.2 and confirmed non-rooted - please check if you can get root with this method!
EDIT 20140705: Towelroot does NOT make the reboot in case of successful root. It gets you root in the same session immediately after you click "make it ra1n". So there is no reason why/how KNOX could be tripped. I did root my device with this method and still have KNOX intact (I just checked again to be sure). I have in the meantime made some changes to the /system folder, e.g. removed the photo-click sound, freed some space by removing the japanese language files for text-to-speech (gives you 25MB) and inserted all the updated system apps back to the system (did not ODEX them and removed classes.dex from the .apk - so they are all larger than the ODEXed originals). Also I moved out Google+ from System to be regular app.
tobbbie said:
How can you be sure that the root explot worked from towelroot and not from your actions earlier tripping KNOX?
You have already a custom recovery and custom ROM - this would not be possible without bootloader having KNOX triggered. So I guess that with this price paid you have already rooted the "regular" way - didn't you?
---------- Post added at 06:29 PM ---------- Previous post was at 06:21 PM ----------
Another thing with upgrade is that you may loose your installed apps.
I remember this from my first steps with Xperia Ray some years ago, but this could also have been due to unlocking the bootloader and installing a custom kernel. Back that time I was not so knowing about what should be done in the process of unlocking bootloader, CWM recovery install and finally rooting. I may have scratched data partition that time without knowing what it actually means - and without it being needed as well.
Is this the case here as well? Non-root means no Nandroid backup and so what happens to the data-partition in this process?
---------- Post added at 06:43 PM ---------- Previous post was at 06:29 PM ----------
Finally to all who want to dare testing:
It is highly unlikely that KNOX would be tripped here. As far I understand the process of image integrity that KNOX tries to maintain, the booloader checks if the image checksum of the kernel or recovery partition is intact - at upgrade time (not runtime at boot?). The towelroot exploit is compromising kernel security (aka "exploit") with some instructions (lib\armeabi\libexploit.so) to gain root and retain that state across the re-boot process. I am not aware of the details how this can be achieved (this is real high-tech hackery) - but the towelroot exploit does NOT install SU on system partition yet - this has to happen in a second step - and failed with 4.2.2 stock ROM on my GT-I9195.
So if there is anyone out there with just upgraded 4.4.2 and confirmed non-rooted - please check if you can get root with this method!
Click to expand...
Click to collapse
well maybe i wasn't so clear. i was on CM m7 snapshot,then flashed through odin the samsung's 4.4.2 firmware. after that my root privilages were gone(as i presume,flashing the new firmware formats system,and installs new one) and i was left with plain stock firmware. checked with root checker,tried with titanium,tried with ES file explorer to remove anything from system partition but this was a no-go. so NO root after installing 4.4.2. installed towelroot,run the app and after 15 or so seconds,the phone rebooted and root privileges were back on! track!
with ES and Titanium i removed all of the knox related stuff with absolutely no problem. i read in the towelroot app's that SU app is not installed and i manually installed it from chainfire's thread. that's all i did.
the knox warranty 0x1 was triggered loooooooooong ago, and thankfully i haven't need the waranty for the time being...
hope it helps :laugh:
There are several testimonials that this don't trip KNOX on S5.
vriz27 said:
just tried it.rooted successfully the phone in 15 seconds.the bad thing is that I've already tripped Knox warranty so I cannot tell if it stays 0x0.I'm on latest 4.4.2 stock
Click to expand...
Click to collapse
4.4.2? ?
KumailHyderMirza said:
4.4.2? ?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here are some screenshots for those who don't believe KNOX is not triggered:
What about Verizon S4 mini, anyone can confirm it.
This doesn't work for me. It just reboots my phone. It's an unbranded european S4 mini LTE.
I'm on 4.2.2 and I read before someone couldn't root with it on 4.2.2, and I'm not sure I can update it to 4.4.2 because
1) I tried flashing it before and it says i have an unofficial rom (or kernel, can't rememebr which) which in the end I don't have... edit "updates are not available because your device had been modified".
2) I'm not sure the update has rolled out for France. Edit : It hasn't, according to Sammobile. Only Belgium. I'll try to update through Odin and get back to you. In the mean time, feel free to make any suggestion to resolve the issue! Thanks
comaX13 said:
This doesn't work for me. It just reboots my phone. It's an unbranded european S4 mini LTE.
I'm on 4.2.2 and I read before someone couldn't root with it on 4.2.2, and I'm not sure I can update it to 4.4.2 because
1) I tried flashing it before and it says i have an unofficial rom (or kernel, can't rememebr which) which in the end I don't have... edit "updates are not available because your device had been modified".
2) I'm not sure the update has rolled out for France. Edit : It hasn't, according to Sammobile. Only Belgium. I'll try to update through Odin and get back to you. In the mean time, feel free to make any suggestion to resolve the issue! Thanks
Click to expand...
Click to collapse
You have to upgrade with Odin.
But don't do it if you're in the old bootloader
sent from my i9192 with CM11 by sekil
comaX13 said:
This doesn't work for me. It just reboots my phone. It's an unbranded european S4 mini LTE.
I'm on 4.2.2 and I read before someone couldn't root with it on 4.2.2, and I'm not sure I can update it to 4.4.2 because
1) I tried flashing it before and it says i have an unofficial rom (or kernel, can't rememebr which) which in the end I don't have... edit "updates are not available because your device had been modified".
2) I'm not sure the update has rolled out for France. Edit : It hasn't, according to Sammobile. Only Belgium. I'll try to update through Odin and get back to you. In the mean time, feel free to make any suggestion to resolve the issue! Thanks
Click to expand...
Click to collapse
if it says that the updates are not available because your device has been modified, it means that you are rooted. you have to install supersu separretly.
this exploit was meant for all kernel built before 3 june, so it will work on your device.
Dear friends, now we have learned to put ROOT using TowelROOT without a computer, and that's a great application with which you can easily install and Rekoveri kernel (Kernel and Recovery) in the form *. Img files. You can also do a pre-backup.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Sent from my GT-I9190 using XDA Free mobile app
Towelroot with GT-I9192
No go for my i9192 having jdq39.i9192ububnd2 build. :crying:
I have gone back to the stock firmware and this did not work. Baseband - ddu1bml1
Related
Help i have a Australian SM-N9005 and i rooted fine and flashed the Omega rom which worked perfectly. I decided to some of the other roms out there and after flashing ROM][XXBUMI7][V1.1][8/10][N9005] K.I.D.1412| Fast|Clean|Stable|battery life| now my phone just boot loops after intial Samsung Note 3 logo. I can get into CWM still and Odin Mode and have tried flashing Kernel, Recovery etc etc and also a few other roms with the same boot loop. Anyone know what would be going on?
If that was happening to me. I would take out my Sd card and go into cwm wipe all! Then flash over stock with Odin
Sent from my SM-N9005 using XDA Premium 4 mobile app
I ended up getting a swap over as the Aussie XSA Firmware not out yet. I'm not rooting mine again until more roms released and Aussies be careful flashing the roms already released
I recently upgraded my Optus contract and picked up the note 3. It has Optus branding. Once the Australian XSA firmware is released am I able to flash over the Optus firmware via odin like we used to do with previous Samsung devices or am I going to trigger knox? I'm not fussed about root for now, I just don't want the Optus crap.
Hey guys,
Any updates on if we can flash the sea firmware over the top via Odin?
Tobz
VanHermiz said:
I recently upgraded my Optus contract and picked up the note 3. It has Optus branding. Once the Australian XSA firmware is released am I able to flash over the Optus firmware via odin like we used to do with previous Samsung devices or am I going to trigger knox? I'm not fussed about root for now, I just don't want the Optus crap.
Click to expand...
Click to collapse
There is one called SM-N9005 Australia 2013 October 4.3 N9005XXUBMI7 N9005XSABMI1
from sammobile.com
does it work?
I dont dare to flash yet... cos I dont want to lose my 2+1 years warranty.
Knox and Region Lock better play safe, who knows after flash firmware from different region Our phone will become one of region locked phone.
-I wait for Devs figure out the way to disable Knox counter flag.
uccoffee.forum said:
There is one called SM-N9005 Australia 2013 October 4.3 N9005XXUBMI7 N9005XSABMI1
from sammobile.com
does it work?
I dont dare to flash yet... cos I dont want to lose my 2+1 years warranty.
Click to expand...
Click to collapse
I tried to flash this on my n9005 from Kogan (Phone come from Hong Kong) & it kept failing in odin right at the end.
I eventually had to do a firmware recovery with Kies to get it working again
uccoffee.forum said:
There is one called SM-N9005 Australia 2013 October 4.3 N9005XXUBMI7 N9005XSABMI1
from sammobile.com
does it work?
I dont dare to flash yet... cos I dont want to lose my 2+1 years warranty.
Click to expand...
Click to collapse
I downloaded that from sammobile.com last night, I don't want to flash until I know it wont trigger knox. I've got 2 more years on this contract so warranty is important right now lol.
KTM690 said:
I tried to flash this on my n9005 from Kogan (Phone come from Hong Kong) & it kept failing in odin right at the end.
I eventually had to do a firmware recovery with Kies to get it working again
Click to expand...
Click to collapse
Not sure but could be that your phone is region locked to Hong Kong and you're flashing firmware from another region? But then again I remember reading someone downloaded Unknown - XSI from sammobile and flashed it without having problems and it supposedly didn't trigger knox not sure what firmware he was on though.
If it's region locked it says so on the box
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Didn't know that cause I didn't have that sticker on my note 3 box. Thanks for the info.
Sent from my SM-N9005 using XDA Premium 4 mobile app
My N3 is also from Kogan. I suspect mine was activated in Hong Kong before being shipped to me even though the OLB region is not meant to have Region Lock enabled. I had written to Kogan before buying the phone enquiring on the Region Lock of the devices they ship. I guess they activated the phone in Hong Kong just to be safe.
Looking forward to rooting and loading Omega ROM but until the process is a little more mature, I'm holding off.
Great to see so many people working hard on this device.
Sent from my SM-N9005 using XDA Premium 4 mobile app
For others who purchased from Kogan, refer to this post and the responses:
http://forum.xda-developers.com/showthread.php?p=46449951
Sent from my SM-N9005 using XDA Premium 4 mobile app
I have an Optus N3. Flashed another stock firmware over the optus one before flashing Omega Rom. Works beautifully. Cant wait for kernels to come out so i can play with it more (undervolting, etc).
Love the Xposed installer with modules.
Hi,
I also am worried to flash anything at the moment.
Does that XSA Firmware (I'm assuming that means open, like directly from Samsung AUS...?) trigger KNOX counter? Its official firmware, I'd assume not, just wanted to see what others say or have had happen...
Do you guys think its better to wait till carrier updates to 4.4.2, so bootloader and everything gets done officially. then root and flash 4.4.2 roms?
Or I can just flash the Polish (or other NA7) 4.4.2 (NA7) and just go from there? Dam, I'm not sure yet...if anyone shed some light on this that would be great!!
Thanks advance guys!!
Lambetts said:
Hi,
I also am worried to flash anything at the moment.
Does that XSA Firmware (I'm assuming that means open, like directly from Samsung AUS...?) trigger KNOX counter? Its official firmware, I'd assume not, just wanted to see what others say or have had happen...
Do you guys think its better to wait till carrier updates to 4.4.2, so bootloader and everything gets done officially. then root and flash 4.4.2 roms?
Or I can just flash the Polish (or other NA7) 4.4.2 (NA7) and just go from there? Dam, I'm not sure yet...if anyone shed some light on this that would be great!!
Thanks advance guys!!
Click to expand...
Click to collapse
You can flash any Stock Samsung rom without triggering Knox however, due to a new bootloader in the Kitkat rom once you flash it you can't go back to the Aussie JB rom...
You should be able to go to the Aussie KK rom when it comes out but until then you are stuck using other country roms and modems....
I had the Polish NA7 rom installed and it worked OK however my phone was rooted so I didn't have some of the problems others have reported - apps unable to access/write to internal/external sd cards...
Since then I went to custom roms, much better...
Oh ok I see. Thanks for your reply.
So what do you recommend? Can't I flash the polish to get my boot loader updated then flash a custom kit kat rom? Then when an Australian one comes out flash stock again then root again? Is that possible?
I've never had this problem where I've been faced with how I can't "go back" Haha.
Thanks again.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Anyone know where i can get stock aus firmware higher than;
N9005XXUBMI7_N9005XSABMI1_XSA
Was preloaded JB 4.3 i forgot to save backup before i flashed.
I went to a KK 4.4 CM ROM straight out of the box.
I decided i wanted to revert to stock and play with the touchwiz features.
Strangely i flashed via odin the wrong firmware.
Pretty sure it was this one;
N9005XXUDML3_N9005IDEDML4_IDE
Which ended up being polish JB 4.3 (Orange)
And it worked.
=\
Forgetting my confusion about reverting from KK to JB,
After downloading aus firmware from sammobile,
Both the retail and telstra are failing with this message;
W REV. CHECK FAIL : fused : 2 . Binary : 1
Checked the forums but only found threads relevant to SGSIV.
Something about new OTA update blocking root.
Any help?
Oh and if possible id prefer stock retail to telstra branded.
Cheers.
Edit ; sorted, found them, Sammobile just takes abit of navigating.
Wobzy said:
Anyone know where i can get stock aus firmware higher than;
N9005XXUBMI7_N9005XSABMI1_XSA
Was preloaded JB 4.3 i forgot to save backup before i flashed.
I went to a KK 4.4 CM ROM straight out of the box.
I decided i wanted to revert to stock and play with the touchwiz features.
Strangely i flashed via odin the wrong firmware.
Pretty sure it was this one;
N9005XXUDML3_N9005IDEDML4_IDE
Which ended up being polish JB 4.3 (Orange)
And it worked.
=\
Forgetting my confusion about reverting from KK to JB,
After downloading aus firmware from sammobile,
Both the retail and telstra are failing with this message;
W REV. CHECK FAIL : fused : 2 . Binary : 1
Checked the forums but only found threads relevant to SGSIV.
Something about new OTA update blocking root.
Any help?
Oh and if possible id prefer stock retail to telstra branded.
Cheers.
Edit ; sorted, found them, Sammobile just takes abit of navigating.
Click to expand...
Click to collapse
Not sure whether you have found out already but there is NO going back to 4.3 courtesy of the Samsung d1cktatorship.
Hi all,
Myself new into S4 forum. I bought one second hand (previously used) Galaxy S4 I9500. When i got the phone, it's having the SuperSU app installed on it. So i hope its having root access. For confirming root access i installed root browser and checked whether i can see the system files. I confirmed :highfive:
So my phone is rooted. Isn't right guys ? (i previously owned sony phone, so am making all my doubts clear)
Then i asked in noob's QA section for checking boot-loader status and i found my system status as following in the download mode.
CURRENT-BINARY : Custom
SYSTEM STATUS : Custom.
This means my phone has unlocked boot-loader . I just want to confirm whether i am right or not, thats why i am writing all these
I tried to update via Phone, it says my Phone has been modified. There is NO updates. :crying:
And about the recovery,i found the Android System Recovery in there. (Probably Not a custom Recovery)
My Current phone Status is
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The build shows I9500UBUBMG1: means some foreign region(Uruguay) update and i am from INDIA, Is it weird ?
So coming to my actual topic question, (there is a lot of questions )
1.How can i update to latest version with my current system?
2.What is MODEM and Knox mean ? (just a short answer)
3.Is it possible to update my phone to any region update ?
4. If i need to install custom ROM's, how can i do that ? ((Suggest Recoveries if any))
5. Can i go back to original official system(no root and no custom recovery), i mean remain in warranty ?
Seeking for Solutions eagerly, i hope someone will help me out.
FAQ threads are making me mad. Once i get a basic idea, i'll catch up.
Regards
Ajith
its obvious it's been 'messed' with same **** happend to me when i got a 'NEW' s4 i checked it out and it said custom this and custom that also has super user installed on it.... (i was fuming and kicked off on the guy) he thought he can get a sale lol
Ajith Roy said:
So coming to my actual topic question, (there is a lot of questions )
1.How can i update to latest version with my current system?
2.What is MODEM and Knox mean ? (just a short answer)
3.Is it possible to update my phone to any region update ?
4. If i need to install custom ROM's, how can i do that ? ((Suggest Recoveries if any))
5. Can i go back to original official system(no root and no custom recovery), i mean remain in warranty ?
Click to expand...
Click to collapse
1. Download Odin and download the lastest firmware in your region
2. Not sure Google it but be specific on what kind of modem is it a router of a program its used etc
3. Yes but I'd advise not to as your WiFi or something else may not work etc.. but you can give it ago if you wish
4. Download the latest Odin and Google your build or ask on here and they'll point you to the correct firmware, also watch a few Youtube video on how to use Odin its quite easy.
5. I'm guessing you can as I've done it to mine just delete any traces of it being rooted such as old folders etc...
Carl Blance said:
1. Download Odin and download the lastest firmware in your region
2. Not sure Google it but be specific on what kind of modem is it a router of a program its used etc
3. Yes but I'd advise not to as your WiFi or something else may not work etc.. but you can give it ago if you wish
4. Download the latest Odin and Google your build or ask on here and they'll point you to the correct firmware, also watch a few Youtube video on how to use Odin its quite easy.
5. I'm guessing you can as I've done it to mine just delete any traces of it being rooted such as old folders etc...
Click to expand...
Click to collapse
Thanks Carl.
And what about custom recoveries. Anyone knows ?
Is there any tutorial for "HOW TO USE ODIN TO FLASH FIRMWARES"
Also one more question, my current build is I9500UBUBMG1, can i flash indian firmware via ODIN ?
Is there any way to download these firmware files fastly, hotfile is slow and doesn't support Resuming.
Regards..
my current build is I9500UBUBMG1, can i flash indian firmware I9500XWUBMG5_I9500ODDBMG5_INS.zip via ODIN ?
Is there any way to download these firmware files fastly, hotfile is slow and doesn't support Resuming.
Regards..
Just put custom ROM PAC man rom
Sent from my GT-P3100 using xda app-developers app
Hi ! Si for respond to you Yes you can do the update ! And the best i suggest you is to installed a custom rom ans to prêter if you prêter Touchwizz (Samsung's Android version for make it simple).
Yes you can go back to official statut useful if One day you have to go back to S.A.V etc You will have juste to use Triangle away it s an application for supress the foot etc.
Or simple flash a stock rom (official firmwire from Samsung).
No on Samsung phones the bootloader are ALWAY unlocked contrary to Sony LG etc it s also for that that it s Very easy to pût them in custom.
I suggest you the Échos rom the best based on Touchwizz.It had ben updated recently to Android 4.3 with la test modem (MJ5).
Seek for the mos récent version of Your MoDem for Your country (the 2 lettres after the 9500??/9505??).
Download Odin for beginning ans make sûre that Kies us completely desactivated ! Make all drivers installer Aldo (the ones for Your s4 meaning).
Ajith Roy said:
my current build is I9500UBUBMG1, can i flash indian firmware I9500XWUBMG5_I9500ODDBMG5_INS.zip via ODIN ?
Is there any way to download these firmware files fastly, hotfile is slow and doesn't support Resuming.
Regards..
Click to expand...
Click to collapse
yes, flash this http://www.hotfile.com/dl/236064286/504393c/I9500XWUBMG5_I9500ODDBMG5_INS.zip.html
tutorial http://forum.xda-developers.com/showthread.php?t=2265477
i prefer to wipe before and after flashing
I agrée with samersh.Even if it s not say to wipe after flashing i do it each time.It s cosy nothing.
But wipe us Very important ni matter what you flash it erased some bug problème.
Why it shows like " Phone has been modified." while i try to update my phone ?
Is it because of the rooting ?
In settings, the phone status is set to OFFICIAL.
Why it shows like " Phone has been modified." while i try to update my phone ?
Is it because of the rooting ?
In settings, the phone status is set to OFFICIAL.
Ajith Roy said:
Why it shows like " Phone has been modified." while i try to update my phone ?
Is it because of the rooting ?
In settings, the phone status is set to OFFICIAL.
Click to expand...
Click to collapse
Yes, because of rooting.
Sent from my Galaxy
samersh72 said:
Yes, because of rooting.
Sent from my Galaxy
Click to expand...
Click to collapse
hi,
I wonder when i checked my download mode status now, it is changed to Samsung Official
Earlier it was like CUSTOM.
And when i check for updates, it is saying "you device has the latest updates"
Earlier it was "your device is modified, blah blah..."
Wow...What's happening..
edit: i just enabled developer option today. that is the only change i made to my phone.
samersh72 said:
Yes, because of rooting.
Sent from my Galaxy
Click to expand...
Click to collapse
Hi,
Today i installed 4.2.2 INS-I9500XWUBMG5-20130726135849 (i hope its correct indian version) through ODIN.
But in the Kies, it says like
Here is my current device status :
I hope someone can help me. Did i installed wrong version for my phone ?
Hi Guys,
Im a new user here, but have been using the site for firmwares for ages. This place is awesome.
Can someone help me with this?
I recently got a note3 4G from UAE (Damam) to india. Its really awesome, except for the lack of firmware updates.
Hence, the fiddler in me thought i should just go ahead and try oin a new firmware.
Previously, i was 'fiddling' with the galaxy s3, which seemed easy enough, but with the Note3, there seems to be a massive divide between regions and firmware versions. I wouldn't want tot do anything that might take away features like the 2K video recording and what not.
I am also getting quite sick of the phone heating up because of some process using the camera (mm-camera-daemon).
Hence, i figured, it might have been fixed in the Kitkat update.
Can anyone direct me as to how i can go about finding the right firmware for my phone, and if i will still recieve OTA updates after an Odin flash (Possibly from another regions firmware).
Thanks a lot!
Keep up the great work!
No one? Really?
I am currently running the BTU NB7 Stock Rom from sammobile.com, this would give you region updates from btu, the uk.
Just flash it via odin the same as you would have done on your s3.
Edit: your device is the N9005, correct?
Also, if you update to Kitkat, you cannot downgrade back to JB.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N9005 using Tapatalk
Thank you very much celderic.
Finally some real answers. Much appreciated.
What are the differences between the various regions by the way? Is it only the language packs? Could you confirm if this update is safe for me, my AP right now ends with MJ7 (UAE).
Also, i've been reading some bad press about the new update. Would you recommend updating anyway? And will the camera still shoot at 2K?
Edit: Been reading a lot about knox. my warranty is already void, so do i need to worry about it? Also, what are the pros and cons of using a custom rom (like omega) and why arent you using them. I want to switch to 4.4 more so for the Ok Google wake up command - will work wonders in my car.
Thanks!!!!
raahilkulshreshtha said:
Thank you very much celderic.
Finally some real answers. Much appreciated.
What are the differences between the various regions by the way? Is it only the language packs? Could you confirm if this update is safe for me, my AP right now ends with MJ7 (UAE).
Also, i've been reading some bad press about the new update. Would you recommend updating anyway? And will the camera still shoot at 2K?
Edit: Been reading a lot about knox. my warranty is already void, so do i need to worry about it? Also, what are the pros and cons of using a custom rom (like omega) and why arent you using them. I want to switch to 4.4 more so for the Ok Google wake up command - will work wonders in my car.
Thanks!!!!
Click to expand...
Click to collapse
Aslong as you only flash official packages from samsung via odin, your knox will remain at 0x0, but as soon as you flash a custom recovery for example, it will go to 0x1 like mine has.
Yes the camera is fine at 4k, i rarely use it though thr file size is too big for me
The CSC code mainly determines where it will get the updates from, my phone was bought as a BTU device, when kitkat first came out i flashed the polish XEO firmware, no problems with it
I am using my own modified version of stock instead of other peoples work, i just didnt like the themes some of the other roms had, and i noticed lots of tiny bugs. Just little things that made me want to put together something for my own use. But ofcourse my phone is rooted and i have no warranty, knox 0x1
I hope this helps feel free to ask if you need any more information.
Edit: i didnt realise you said your knox is already void, i would suggest flashing the stock nb7 btu rom, or even nc2 of another region. To update the modem and bootloader, then flash the latest TWRP recovery, then flash alexndrs latest nc2 rom in recovery it is pre rooted. And when installing from recovery you can set your CSC during the install.
Sent from my SM-N9005 using Tapatalk
Ok, i get it. You seem very wise on these matters. And kudos on the modified ROM, i would love to do the same if i knew how.
Let me take you though the full story, and then you can advise me on what i should do.
I live in India. A friend of mine bought the note3 for me from the UAE (Damam). He was told that he would have to use it with a uae local sim card for a few days there to 'unlock' it, after which, he could use it anywhere (Seriously, is that the best you can do Samsung?). Anyway, he did so, and all worked perfectly. I am using it just fine (more than just fine, its awesome) here in India. Also, since i am not in the UAE, warranty is void. Thats why i mentioned the knox bit since it seems that it will makes no difference to my life.
Now, there are couple of things which are bugging me with the update.
1) Regional differences - what are the differences. Apart from the CSC, the PDA files also seem to be named differently. Why?
2) Is 4.4 really worth it (Since downgrading is an impossibility after that)? I've heard battery life issues and what not. Are you facing these issues as well? Currently, on 4.3, im not having any battery problems, but some process called mm-camera-daemon keeps heating up the camera area on the phone. I was considering buying a portable mini fire extinguisher a few weeks back, but then i thought i might look silly carrying it around I was also hoping that the "Ok Google" command works, but am not clear if samsung has allowed it over sVoice.
3) If i update, will my phone get Sim locked again?
4) Custom Roms - Will i be able to come back to the official roms later if required and recieve OTA updates?
5) Modem and bootloader - I am in india anyway, so the existing modem doesnt apply to me anyway (even though it works). Still fine?
Thanks again!
there is not any update available for your region ( Dubai )
you can use another region
Also, how do i backup the efs without rooting it first? or is it safe for me to just go ahead with a odin update to official 4.4.2?
EDIT:
Alright! Just to keep you updated, i did it!
used the UK BTU firmware you provided and flashed with odin, whilst holding tightly onto my chair.
Booted up, android is upgrading nonsense... etc etc.All working fine.
However, the "Ok Google" command doesnt work, i've read up everywhere about what to do, but nothing i do will make it work, works when the screen is on the lockscreen though.
Anyway, SVoice is going to end samsung one day.
Is there any point in shifting to a custom rom now? Or am i good with just rooting (will i still get updates)?
raahilkulshreshtha said:
Ok, i get it. You seem very wise on these matters. And kudos on the modified ROM, i would love to do the same if i knew how.
Let me take you though the full story, and then you can advise me on what i should do.
I live in India. A friend of mine bought the note3 for me from the UAE (Damam). He was told that he would have to use it with a uae local sim card for a few days there to 'unlock' it, after which, he could use it anywhere (Seriously, is that the best you can do Samsung?). Anyway, he did so, and all worked perfectly. I am using it just fine (more than just fine, its awesome) here in India. Also, since i am not in the UAE, warranty is void. Thats why i mentioned the knox bit since it seems that it will makes no difference to my life.
Now, there are couple of things which are bugging me with the update.
1) Regional differences - what are the differences. Apart from the CSC, the PDA files also seem to be named differently. Why?
2) Is 4.4 really worth it (Since downgrading is an impossibility after that)? I've heard battery life issues and what not. Are you facing these issues as well? Currently, on 4.3, im not having any battery problems, but some process called mm-camera-daemon keeps heating up the camera area on the phone. I was considering buying a portable mini fire extinguisher a few weeks back, but then i thought i might look silly carrying it around I was also hoping that the "Ok Google" command works, but am not clear if samsung has allowed it over sVoice.
3) If i update, will my phone get Sim locked again?
4) Custom Roms - Will i be able to come back to the official roms later if required and recieve OTA updates?
5) Modem and bootloader - I am in india anyway, so the existing modem doesnt apply to me anyway (even though it works). Still fine?
Thanks again!
Click to expand...
Click to collapse
1) There is a region unlock app by chainfire, you need to be rooted though.
2) I am having a very good experience using 4.4 also if i am not mistaken the mm-camera-daemon raises the cou frequency when using the camera, i did see a fix posted online recently that will be included in the next update from google, after 4.4
3/4) To get back to an official rom all you have to do is flash the package via odin. For sim locking, see the app by chainfire.
5)as you are on JB currently it will work on other JB firmwares, im not shre if it will work on KK though i have never tried. Just updated and never had to go back.
raahilkulshreshtha said:
Also, how do i backup the efs without rooting it first? or is it safe for me to just go ahead with a odin update to official 4.4.2?
EDIT:
Alright! Just to keep you updated, i did it!
used the UK BTU firmware you provided and flashed with odin, whilst holding tightly onto my chair.
Booted up, android is upgrading nonsense... etc etc.All working fine.
However, the "Ok Google" command doesnt work, i've read up everywhere about what to do, but nothing i do will make it work, works when the screen is on the lockscreen though.
Anyway, SVoice is going to end samsung one day.
Is there any point in shifting to a custom rom now? Or am i good with just rooting (will i still get updates)?
Click to expand...
Click to collapse
If there are certain apps you would like to remove from the system partition i would suggest alexndrs rom as it has everything you have currently.
Also the TWRP 2.7 recovery is working well for me. You will need to flash that in odin to install the other rom on your phone, same button combo to get to recovery and download mode as your s3 was.
As for efs backups i found a good aroma script, let me find it i will edit when when i have it.
Edit: You will meed TWRP Recovery for this, your knox will go to 0x1 as mine has from flashing the recovery though, just make sure you want too. But here is what you need to flash in TWRP and follow the onscreen instructions to backup the efs for your n9005, backup is about 14mb when finished i think, so make sure. I uploaded it because i couldnt find the thread - http://uppit.com/y9fwqktntlei/EFS_Backup_restore_Aroma.zip
Edit: i hope i have answered everything you asked, sort of rushing to cook dinner whilst typing this found the thread for the aroma efs backup tool too - http://forum.xda-developers.com/showthread.php?t=2611903
Sent from my SM-N9005 using Tapatalk
celderic said:
1) There is a region unlock app by chainfire, you need to be rooted though.
2) I am having a very good experience using 4.4 also if i am not mistaken the mm-camera-daemon raises the cou frequency when using the camera, i did see a fix posted online recently that will be included in the next update from google, after 4.4
3/4) To get back to an official rom all you have to do is flash the package via odin. For sim locking, see the app by chainfire.
5)as you are on JB currently it will work on other JB firmwares, im not shre if it will work on KK though i have never tried. Just updated and never had to go back.
If there are certain apps you would like to remove from the system partition i would suggest alexndrs rom as it has everything you have currently.
Also the TWRP 2.7 recovery is working well for me. You will need to flash that in odin to install the other rom on your phone, same button combo to get to recovery and download mode as your s3 was.
As for efs backups i found a good aroma script, let me find it i will edit when when i have it.
Edit: You will meed TWRP Recovery for this, your knox will go to 0x1 as mine has from flashing the recovery though, just make sure you want too. But here is what you need to flash in TWRP and follow the onscreen instructions to backup the efs for your n9005, backup is about 14mb when finished i think, so make sure. I uploaded it because i couldnt find the thread - http://uppit.com/y9fwqktntlei/EFS_Backup_restore_Aroma.zip
Edit: i hope i have answered everything you asked, sort of rushing to cook dinner whilst typing this found the thread for the aroma efs backup tool too - http://forum.xda-developers.com/showthread.php?t=2611903
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Wow. You are a GOD!
Cant remember the last time someone put time out to help out like this.
All seems well, and im all set to flash TWRP.
Once question though, is it possible that the UK modem is causing connectivity losses here in india? I seem to be loosing my network (have network issues at my workplace, but not sure if this is because of the new modem. Maybe its psychosomatic.) If so, should i flash some other regions firmware before the final alexandr rom?
xdaAdmin - The thanks button disappeared on clicking it once. Please fix this 'bug' to allow upto 100 thanks.
Edit: I installed alexndr rom!!!! Dont see much difference though. How do i make ok google work while the phone is off?
Alright! 3 hours with the new firmware. Everything works. I even managed to uninstall SVoice. But 2 things:
1) Ok Google command is still not working. Do i need a different ROM where samsung apps are not included?
2) The EFS tool you mentioned : Does it do anything different from the TWRP efs backup option?
Also, have you tried http://forum.xda-developers.com/showthread.php?t=2472301
Thanks mate!
raahilkulshreshtha said:
Wow. You are a GOD!
Cant remember the last time someone put time out to help out like this.
All seems well, and im all set to flash TWRP.
Once question though, is it possible that the UK modem is causing connectivity losses here in india? I seem to be loosing my network (have network issues at my workplace, but not sure if this is because of the new modem. Maybe its psychosomatic.) If so, should i flash some other regions firmware before the final alexandr rom?
xdaAdmin - The thanks button disappeared on clicking it once. Please fix this 'bug' to allow upto 100 thanks.
Edit: I installed alexndr rom!!!! Dont see much difference though. How do i make ok google work while the phone is off?
Click to expand...
Click to collapse
Anytime other people may find this thread useful. Just sharing what i have learnt from this device, i have owned it since christmas.
In the alexndr thread, did you flash the latest nc2 modem via odin? You will have to shut down your phone, do the button combo for download mode then flash it, it is in the first post of his thread, this may help. Also the bootloader if you havent (i dont think this needs to be updated, but i have anyway) flash the modem and bootloader seperately
I will try and look up the ok google command, i have never used it. I try to use just the essentials for best battery life and speed
raahilkulshreshtha said:
Alright! 3 hours with the new firmware. Everything works. I even managed to uninstall SVoice. But 2 things:
1) Ok Google command is still not working. Do i need a different ROM where samsung apps are not included?
2) The EFS tool you mentioned : Does it do anything different from the TWRP efs backup option?
Also, have you tried http://forum.xda-developers.com/showthread.php?t=2472301
Thanks mate!
Click to expand...
Click to collapse
The reason i gave you that to flash in recovery is because i have had problems restoring backups in twrp, apparently there is an update coming soon to fix this, but better to be safe and have 2. Put them on your pc or somewhere safe.
I did use the last version of x-note a few weeks ago(been updated since) but i did not like it, too many features that are useless for my daily usage. I think other users favour that rom though.
Sent from my SM-N9005 using Tapatalk
celderic said:
Anytime other people may find this thread useful. Just sharing what i have learnt from this device, i have owned it since christmas.
In the alexndr thread, did you flash the latest nc2 modem via odin? You will have to shut down your phone, do the button combo for download mode then flash it, it is in the first post of his thread, this may help. Also the bootloader if you havent (i dont think this needs to be updated, but i have anyway) flash the modem and bootloader seperately
I will try and look up the ok google command, i have never used it. I try to use just the essentials for best battery life and speed
The reason i gave you that to flash in recovery is because i have had problems restoring backups in twrp, apparently there is an update coming soon to fix this, but better to be safe and have 2. Put them on your pc or somewhere safe.
I did use the last version of x-note a few weeks ago(been updated since) but i did not like it, too many features that are useless for my daily usage. I think other users favour that rom though.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
The NC2 modem and bootloader is in the UK BTU Official update right? Yup, i did that.
Also, apparently, since there is a core on the phone dedicated to system services, the Ok Google command doesnt take much juice to run. Its quite neat. Svoice apparently does eat up quite a lot of battery, but then again, thats what you get when you name something 'Svoice'... Seems like they are trying very hard to piss off apple.
You should try the Google Experience System (or whatever its called). I was using it on the s3 inside my car/for alarms with voice commands. Quite convenient and accurate (even with our indian names to call here) and i havent really faced any issues with a false startup till now on the s3.
Will do the efs thing tomorrow. Thanks for the warning on TRWP.
Would you know of any other ROM which completely boycotts samsungs propitiatory apps?
Will flashing official firmware of another country void my warranty
hi I have a n900 from Dubai, and have flashed KSA csc firmware. My KNOX is 0x0. will it be serviced for problems if I send it to Dubai. I have lost my iemi and baseband.
Can I get official update of lollipop on manually installed kitkat?
I have Note 3. I have manually installed Lollipop. Now it restarts automatically once or twice a day. How i can i Solve this problem?
I was thinking of to downgrade back to kitkat, but will i get official update of lollipop on the manually installed kitkat?
Thanks
As you may be aware, GeoHotz has created an app to root an android device using a recently discovered exploit.
I tried it on my LTE Tab Pro 8.4 which had the latest firmware for my region "BTU" which is NB7,
It wouldn't work, but another XDA member @Inuit, said it worked for him with the DBT NE5 firmware he has on his device.
SO! I downloaded the DBT NE5 file, extracted the Kernel and repackaged it and flashed the Kernel on it's own. Then tried the root method.
I have now successfully rooted the device and kept Knox at a cool 0x0.
I chose to do things this way, as I wanted to keep my regions firmware and not that of another county.
So I still have my original firmware, but I am now using the newer Kernel, everything seems to be working fine but considering I only did this 15 minutes ago, I haven't had enough time to test. But connectivity is fine, battery levels fine etc...
UPDATE: Everything is fine for me, loaded Xposed modules, no adverse affects at all
I have attached the repackaged Kernel, all you need to do, is go into download mode and flash the file under the "AP" Tab in Odin 3.09.
Then install the TowelRoot app, which you can get from the links in the thread below:
http://forum.xda-developers.com/showthread.php?t=2783157
Install the latest, SuperSU (again links in the above thread).
You should be rooted and Knox kept at a cool 0x0.
I have tested the this on my Device the T325 and another user tested the Kernel for the Wi-Fi version T320 and are working fine But!
You try at your own risk!
Download links below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TR Rootable Kernel for LTE 8.4 SM-T325
Original NG1 Kernel for LTE 8.4 SM-T325
TR Rootable Kernel for Wi-Fi Only 8.4 SM-T320
Original NG1 Kernel for Wifi Only 8.4 SM-T320
TR Rootable Kernel for SM-T525 10.1 LTE SM-T525
RavenY2K3 said:
As you may be aware, GeoHotz has created an app to root an android device using a recently discovered exploit.
I tried it on my LTE Tab Pro 8.4 which had the latest firmware for my region "BTU" which is NB7,
It wouldn't work, but another XDA member @Inuit, said it worked for him with the DBT NE5 firmware he has on his device.
SO! I downloaded the DBT NE5 file, extracted the Kernel and repackaged it and flashed the Kernel on it's own. Then tried the root method.
I have now successfully rooted the device and kept Knox at a cool 0x0.
I chose to do things this way, as I wanted to keep my regions firmware and not that of another county.
So I still have my original firmware, but I am now using the newer Kernel, everything seems to be working fine but considering I only did this 15 minutes ago, I haven't had enough time to test. But connectivity is fine, battery levels fine etc...
I have attached the repackaged Kernel, all you need to do, is go into download mode and flash the file under the "AP" Tab in Odin 3.09.
Then install the TowelRoot app, which you can get from the links in the thread below:
http://forum.xda-developers.com/showthread.php?t=2783157
Install the latest, SuperSU (again links in the above thread).
You should be rooted and Knox kept at a cool 0x0.
Remember: My device and these files are for the SM-T325. You try at your own risk!
Click to expand...
Click to collapse
good trick
Hi RavenY2K3,
Thanks for your guide. May I know if Knox will be triggered if I install your attached Kernel via Odin?
@spectro_axis
As you can see in the screenshot, mine has not tripped, neither has anyone else's that I'm aware of on ANY Knox enabled device. What tab have you got?
Sent from my SM-N9005 using Tapatalk
RavenY2K3 said:
@spectro_axis
As you can see in the screenshot, mine has not tripped, neither has anyone else's that I'm aware of on ANY Knox enabled device. What tab have you got?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Hi RavenY2K3,
Thanks for your prompt reply. I currently own a Tab pro 8.4 LTE. I am actually thinking of updating my Tab pro with the latest T325 Firmware from Germany via odin. I am currently on the firmware from Singapore ,2014 March, 4.4.2, T325XXU1ANBB. Do you know whether will knox be tripped if i flash the Germany firmware over the current Singapore firmware? Thanks for your assistance.
spectro_axis said:
Hi RavenY2K3,
Thanks for your prompt reply. I currently own a Tab pro 8.4 LTE. I am actually thinking of updating my Tab pro with the latest T325 Firmware from Germany via odin. I am currently on the firmware from Singapore ,2014 March, 4.4.2, T325XXU1ANBB. Do you know whether will knox be tripped if i flash the Germany firmware over the current Singapore firmware? Thanks for your assistance.
Click to expand...
Click to collapse
My Tab came from China going by the firmware that came with mine out of the box and I replaced it with the UK BTU firmware no problems, you have to wipe the device etc for the CSC to apply though.
Pretty certain you can get difficulties if the new ROM is older than the one installed, if it's number is greater than or equal to the currently installed firmware you should be fine.
All the above is for official firmware though, not custom creations.
Sent from my SM-N9005 using Tapatalk
SM-T320 With T320XXU1ANAI from Peru
I want to confirm that using the kernel posted in this thread I was able to root the Galaxy Tab Pro 8.4 using [TR] with the stock firmware T320XXU1ANAI
Of course Knox flag was not tripped.
Thanks!
I already have 0x1. It is to return KNOX 0x0? It goes?
dansafe said:
I already have 0x1. It is to return KNOX 0x0? It goes?
Click to expand...
Click to collapse
No, once it's been triggered, that's it no going back. Unless someone figures out how to crack it.
Sent from my SM-N9005 using Tapatalk
one question left: what about an official OTA after flashing this modified kernel? will it work as it should?
Wysłane z mojego SM-T320 przy użyciu Tapatalka
macioh said:
one question left: what about an official OTA after flashing this modified kernel? will it work as it should?
Wysłane z mojego SM-T320 przy użyciu Tapatalka
Click to expand...
Click to collapse
It's not modified, it's a stock kernel from an exploitable firmware, for those who don't have an exploitable firmware for their respective region. As I mentioned, the latest version available for UK, is a step behind the German version, the UK version will be the same as the German one "at some point" in the future, but why wait when it can be done now.
Sent from my SM-T325 using Tapatalk
Someone successfully tested T520-kernel? I tried, but failed
Gesendet von meinem SM-T520
Hey can OP or anyone else upload the SM-T320 kernel to another site that doesn't require registration to download?
Thanks!
Edit: I guess Mega requires registration if you are trying to DL via a mobile device but you don't have to in order to DL via a PC.
Uploading for the benefit of others who are trying to DL via their tablets.
dansafe said:
I already have 0x1. It is to return KNOX 0x0? It goes?
Click to expand...
Click to collapse
no.
some discussions long ago suggest knox may used a technology called eFUSE, originally invented by IBM.
once knox detects a tampered bootloader, it will "blow" a micro-fuse in chip. then we see the warranty bit set to 1.
this is a physical-level change, so no way can revert it.
Lin Gi said:
Someone successfully tested T520-kernel? I tried, but failed
Gesendet von meinem SM-T520
Click to expand...
Click to collapse
Yes doesnt work for me either.
RavenY2K3 said:
My Tab came from China going by the firmware that came with mine out of the box and I replaced it with the UK BTU firmware no problems, you have to wipe the device etc for the CSC to apply though.
Pretty certain you can get difficulties if the new ROM is older than the one installed, if it's number is greater than or equal to the currently installed firmware you should be fine.
All the above is for official firmware though, not custom creations.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Hi, sorry noob question.
I have SM T325 with Hong Kong firmware originally. If I want to flash another firmware from a different country via Odin, will it trip the Knox? You said yours was Chinese firmware and you flashed a British one and it didn't trip the Knox, but I just wanted to confirm it. Also, after I flash the different firmware and I flash the root kernel, it won't trip Knox right? Sorry for repeating your words, just wanted to make sure, thanks
Zakanam said:
Hi, sorry noob question.
I have SM T325 with Hong Kong firmware originally. If I want to flash another firmware from a different country via Odin, will it trip the Knox? You said yours was Chinese firmware and you flashed a British one and it didn't trip the Knox, but I just wanted to confirm it. Also, after I flash the different firmware and I flash the root kernel, it won't trip Knox right? Sorry for repeating your words, just wanted to make sure, thanks
Click to expand...
Click to collapse
flashing official firmware from different region won't trigger knox, only rooting and installing custom recovery will.
SMT520 was kernel jan14 flashed his kernel apr3
used towelrootv2 and don't have root access
on build anae fwiw
it also seems to know something is up because now i get a notification that tells me there was suspicious activity on my tablet and to reboot to make changes. rebooted and still get the notification so i assume it's just trying to revert. at this point i dont feel the need to flash stock recovery i'm sure a reliable, working root method will be there sooner than later.
on further reading it just appears that any exynos processor tablet wont be able to take advantage of towelroot until geo decides to open support. makes sense the 8.4 (wifi/lte) versions as well as all the qualcomm LTE versions of the tab pro/note lines are working.
jason_jiang said:
flashing official firmware from different region won't trigger knox, only rooting and installing custom recovery will.
Click to expand...
Click to collapse
Not true it can trigger Knox. I found out the hard way on my European 8.4 flashing a US ROM. It didn't flash properly (ext4) error and then I had to restore with kies.
Sent from my Nexus 5 using Tapatalk
Can confirm it works on Tab Pro 8.4. I didn't have to mess about with flashing different Kernel for some reason. Below is the firmware that was on my device.
Device: Galaxy Tab Pro 8.4 WiFi Only (SM-T320)
Region: UK
Version: T320XXU1BNE3
Build Date: 2014/5/27
After installing towelroot V2 I just pressed the button on the app and let it do it's magic and then installed SuperSU/Pro. And that was it. All rooted and it didn't trip the Knox flag. Now titanium backup and similar root like apps work. Brilliant. Well pleased
I am trying to root my N900V via many many methods and yes i studied everything first before asking this question which is asked thousands of times before, i tried yemen tool, CWM, TWRP, TR, Farmaroot nothing works for me i don't know why, i am on OF1 5.0 Lollipop,.
Please advice, thank you
Did you buy a SM-N900V?
I see this is your first post in this sub-forum, and you have many posts in the "Xiomi Red Note 3" (kenzo) forum.
(There isn't much reason to believe that a root method for one device will work on a completely different device.)
Anyway, your root options for the SM-N900V on either OB6 or OF1 are only the Yemen tools - no other choices.
Using Odin, you can flash any of the factory stock firmwares for NK1, OB6, OF1, or PL1 without hitting the anti-rollback prevention... but only OB6 and OF1 have publicly available rooting methods (the two Yemen threads). Towelroot v3 has not worked since the NC4 release; that is now five releases in the past.
The only other method (much much harder) would be for you to research and implement your own root exploit. (The PL1 release was a security bug patch release, suggesting that one or more severe vulns exist in those older releases)
So go back and try the Yemen tools again - either with OF1, or with OB6. And if you get nothing but failures, describe the setup and observed behaviors during those failures - more than just "it didn't work". No-one wants to play a game of "twenty questions" back-and-forth across the Internet.
bftb0 said:
Did you buy a SM-N900V?
I see this is your first post in this sub-forum, and you have many posts in the "Xiomi Red Note 3" (kenzo) forum.
(There isn't much reason to believe that a root method for one device will work on a completely different device.)
Anyway, your root options for the SM-N900V on either OB6 or OF1 are only the Yemen tools - no other choices.
Using Odin, you can flash any of the factory stock firmwares for NK1, OB6, OF1, or PL1 without hitting the anti-rollback prevention... but only OB6 and OF1 have publicly available rooting methods (the two Yemen threads). Towelroot v3 has not worked since the NC4 release; that is now five releases in the past.
The only other method (much much harder) would be for you to research and implement your own root exploit. (The PL1 release was a security bug patch release, suggesting that one or more severe vulns exist in those older releases)
So go back and try the Yemen tools again - either with OF1, or with OB6. And if you get nothing but failures, describe the setup and observed behaviors during those failures - more than just "it didn't work". No-one wants to play a game of "twenty questions" back-and-forth across the Internet.
Click to expand...
Click to collapse
First of all thank you for your detailed answer.
No I didn't bought N900V it's my little brother who snatched Redmi Note 3 from me and gave me this piece of work.
Today I will try to downgrade the firmware to OB6 and try Yemen tools again and see if it works, I will get back to you with the report. Sighhhhh I hope it will work on OB6.
P.S how long should Yemen tools take to root the phone? Because I gave it good 15 mins and it was still running in download mode with no progress bar so I thought it's not working.
Update: Didn't worked on OB6 even
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ecrudragon said:
First of all thank you for your detailed answer.
No I didn't bought N900V it's my little brother who snatched Redmi Note 3 from me and gave me this piece of work.
Today I will try to downgrade the firmware to OB6 and try Yemen tools again and see if it works, I will get back to you with the report. Sighhhhh I hope it will work on OB6.
P.S how long should Yemen tools take to root the phone? Because I gave it good 15 mins and it was still running in download mode with no progress bar so I thought it's not working.
Update: Didn't worked on OB6 even
Click to expand...
Click to collapse
Dang. I wrote you a long reply and it didn't take and disappeared out of my cache when I hit the back button.
Anyway, I see you are on one of those two yemen threads. That's the right place to continue this discussion.
I'm not much help as I am still on NC4 and have never used either of those methods. So I am not of much technical help.
I did just read both of those threads - every last post - and I can conclude this:
What a mess.
and... you symptoms sound a lot like what everyone else with troubles reports.
Obviously both methods are very fragile. Because they involve a Windows PC, I imagine that a first thing to suspect is Antivirus Programs / Driver version Issues / USB3 vs. USB2.
Since it appears that both methods cause the phone to reboot into different phone modes, at a minimum I would:
(a) verify that the PC's drivers recognize the phone in all modes (adb, Odin)
(b) perhaps toggle the default storage setting (MTP vs PTP) in addition to enabling ADB
maybe even clear the ADB certificate cache before starting.
The thing to be cautious about in both those threads is jumping to conclusions that are not warranted. A lot of people in there are insisting (for instance) "Windows 10 only", despite the fact that there are success reports on Win7, Win8.1 (and even someone reporting success on Win Vista!). Usually they come to those conclusions erroneously because of "post-hoc fallacy": they assume that "the last thing that I changed right before I succeeded" was the critical factor involved in success.
(If the exploit relies on a race condition it could be possible to succeed in seconds ... or never at all. If that is what makes the successes random, then all the fiddling with the PC may not have anything to do with the outcomes.)
good luck
I just happened across this thread after having problems rooting a SM-900V on NK1. Coincidentally enough, the Note 3 in question also belongs to my younger brother. (He is 50, so I will stop short of calling him my 'little' brother).
I have kept my own Note 3 rooted and am currently running Temasek CM13, but he was/is still using KK, and it has been so long that I had lost track of how to root it. I was using Arabic Tools, but it only appeared to work with OB6 and OF1.
I read somewhere that NK1 cannot be downgraded, but what I am gathering from this thread is that it is possible to just apply OB6 or OF1 using Odin then use the Arabic Tools to root? If true, that would make my weekend.
Is the best upgrade route (recognizing that best is subjective) to CM13 going to be using Odin to apply OB6 or OF1, root, unlock bootloader and apply CM13?
Thanks for any advice. I hope I am not hijacking your thread, ecrudragon, but our situations sound similar.
Gundie said:
I read somewhere that NK1 cannot be downgraded, but what I am gathering from this thread is that it is possible to just apply OB6 or OF1 using Odin then use the Arabic Tools to root? If true, that would make my weekend.
Click to expand...
Click to collapse
That is possible, yes. As you see from not only this thread but also the two Yemen threads, some people succeed at getting root (on OB6 or OF1) with those tools and some people don't The rooting method seems to be sort of fragile at best.
Before you go racing off though, remember something else: CM13 needs a custom kernel - so even if you can root, you would still need to unlock the bootloader afterwards in order to be able to boot a custom kernel. An additioinal prerequisite of the unlock method is that the CID value of the eMMC flash memory chip on the phone needs to start with 0x15 (indicating manufacture by Samsung)
==> You don't need to be rooted to check the CID value - just download the "eMMC Brickbug (Vinagre)" app to find out what your CID value is before you do anything else. If you are 0x11, you aren't going to get CM13 running whether you can root or not. Only a little value in rooting if you can't unlock the bootloader IMO.
Gundie said:
Is the best upgrade route (recognizing that best is subjective) to CM13 going to be using Odin to apply OB6 or OF1, root, unlock bootloader and apply CM13?
Click to expand...
Click to collapse
Yes, more or less. "best" here really only means "the only way that is available without developing some brand new rooting method".
The incrementing of the firmware anti-rollback occurs at certain trip points, which appear to be the releases: MJ7, NC4, and NK1.*
You can not revert backwards prior to the nearest previous (to your currently installed release) of any of these three. Of course, you can always flash forward - possibly going beyond and establishing a new trip point.
(* Because of a lack of reporting, It is possible that NJ6 is the actual trip point, meaning that someone on NK1 could Odin flash back to NJ6 at the earliest. Unfortunately, after I put together all those recovery-flashable Stock ROMs, I installed NJ6 and tried using Towelroot v3 - and no joy. It works on MJ7 through NC4, but not beyond that. So while that possibility (of Odin back-flashing to NJ6) still remains, there doesn't seem to be much of a reason to attempt it.)
For your NK1 unit, that means you can flash forward or backward at will (using Odin) among this group of releases:
NK1 OB6 OF1 PL1
At this point in time - since that device is on NK1, and there are no trip points above NK1 (yet as of 4/2/2017) you can Odin flash whatever you want within the above group.
good luck
PS Note something else that falls out of the above analysis: If for whatever reason you can't root or you can't unlock (CID starting with 0x11), it is probably the right thing to do to flash the PL1 firmware. Might as well as it has the most recent security patches available if the device is to continue to be in use as a daily driver. You can always flash back to NK1 - right where you are now - in the event of some new development or rooting opportunity.
Thank you very kindly for all of your help bftb0, I am gratified. I remember being relieved when I ran EMMC Check and seeing the 15. I am running a tweaked kernel (and Kernel Adiutor) with CM13 now, but my brother is still on KitKat. He runs a tethering program that he apparently couldn't get to work under Lollipop, so he unrooted and went back to KK and never thought about it again. I want to get him onto CM while I am visiting him this week.
I will locate those firmwares (thank you for assembling them!) and start working. I fully agree about PL1 - worst case scenario, I would like to see him there. I'll find another way for him to do his damned tethering even if I have to buy him a hotspot.
Major thanks again,
G
Dear @bftb0 didn't read a word you said, kidding read everything and thank you for kind answer.
Arabic Tools didn't worked for me i tried 100 times but fortunately "SM-N900V_FI_ROOTE BY Dr.Android" worked for me like a charm then i replaced Kingroot with SuperSu via some commands, running Stock LP with all the bloatware disabled. Happy now
Hey Guys, I'm having trouble rooting my Note 3. It is an SM-900V (verizon) on PL1. I've tried Yemen and Arabic tools, but I receive error messages on both. Yemen states "not compatible" and Arabic continues to say, 'Enable USB debugging" (which I have). From what I understand, these tools shouldn't work because I'm not on OB6 or OF1. What can I do to get rid of all this bloatware!? Help is appreciated!
note3newbie said:
Hey Guys, I'm having trouble rooting my Note 3. It is an SM-900V (verizon) on PL1. I've tried Yemen and Arabic tools, but I receive error messages on both. Yemen states "not compatible" and Arabic continues to say, 'Enable USB debugging" (which I have). From what I understand, these tools shouldn't work because I'm not on OB6 or OF1. What can I do to get rid of all this bloatware!? Help is appreciated!
Click to expand...
Click to collapse
Oh man you're seriously messed up, there's no way until now for PL1 to be rooted whatsoever, wait n watch maybe it will come or find your own cure.
ecrudragon said:
Oh man you're seriously messed up, there's no way until now for PL1 to be rooted whatsoever, wait n watch maybe it will come or find your own cure.
Click to expand...
Click to collapse
Not true. He can Odin flash back to OB6 or OF1 stock firmware.
The bootloader RP SWREV flags did not increment between OF1 and PL1 (or so I am told), so there shouldnt be an issue back-rev'ing. (Kind of a surprise actually; I expect Big Red to try and screw us at every turn.)
bftb0 said:
Not true. He can Odin flash back to OB6 or OF1 stock firmware.
The bootloader RP SWREV flags did not increment between OF1 and PL1 (or so I am told), so there shouldnt be an issue back-rev'ing. (Kind of a surprise actually; I expect Big Red to try and screw us at every turn.)
Click to expand...
Click to collapse
Oh, i thought there's no going back from PL1, if so then he can work twice as hard as i did and now i am running AryaMod 6.0.1 MM, Rooted & Bootloader unlocked, Learn learn & learn :fingers-crossed:
P.S if anybody want i can share my whole journey from rooting stock to TWRP/AryaMod MM.
Hey guys, non Note 3 user here.
My buddy has a 900V with EOF1 and is on one of the cheaper AT&T LTE alternative plans.
He's still in "official" status and has never rooted before.
I'd like to get him onto an AOSP or CM (LOS) ROM.
Can anyone recommend a super stable one where everything works?
Doesn't need to be the fastest or have most options or best battery.
Just... everything works and is better than stock.
Can anyone recommend a root/TWRP/ROM plan for me?
I won't need heavy details.
I'm a heavy flasher, familiar with ADB/Odin/Fastboot.
Just the quick details and then I can figure it out from there.
Am not however, familiar with non SuperSU rooting methods.
Would like to stay with 5.X or maybe 6.X.
Not at all interested in 7.X.
I'm Verizon N900V on version 5.0 - Build N900VVRSERPL1 Dec 2016 update. From what I'm reading, my bootloader is locked. If I flash and roll back to OF1, OB6 or NK1, can the bootloader be unlocked? I do not use this phone as a primary phone. It's only used when connected to WiFi. It's an old phone that I want to root and don't care if any Verizon service works on it at all. Any advice? On and my CID starts with 15, not 0x11.
akosha13 said:
I'm Verizon N900V on version 5.0 - Build N900VVRSERPL1 Dec 2016 update. From what I'm reading, my bootloader is locked. If I flash and roll back to OF1, OB6 or NK1, can the bootloader be unlocked? I do not use this phone as a primary phone. It's only used when connected to WiFi. It's an old phone that I want to root and don't care if any Verizon service works on it at all. Any advice? On and my CID starts with 15, not 0x11.
Click to expand...
Click to collapse
You can only roll back to OF1 but yes, then it can be rooted and bootloader unlocked.
Sent from my SM-N900V using Tapatalk
donc113 said:
You can only roll back to OF1 but yes, then it can be rooted and bootloader unlocked.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I'm in a very similar situation and odin'd ob6... which was previously root able but not now (seeking help in my own thread aswell).
Does my device also qualify for of1? I'm pretty sure I grabbed that Img last night and for what ever reason clicked ob6 :/ as it was what I was running before.
tbonedude said:
I'm in a very similar situation and odin'd ob6... which was previously root able but not now (seeking help in my own thread aswell).
Does my device also qualify for of1? I'm pretty sure I grabbed that Img last night and for what ever reason clicked ob6 :/ as it was what I was running before.
Click to expand...
Click to collapse
OF1 is what you need, NOT ob6
Sent from my SM-N900V using Tapatalk