I've read the guide on how to use Towelroot to root my S4 i9505. I have the GNG8 software so Towelroot fails.
http://forum.xda-developers.com/galaxy-s4/general/root-how-to-obtain-root-permissions-t2862768
The guide says at point (7): "flash via Odin your original kernel, matched to the ROM version you are using. You can find HERE a kernel stock collection."
So how do I match the Kernel?
It looks like I can't complete this anyway because Mobile Odin doesn't work yet with new 4.4 updates according to the Mobile Odin instructions. But I'd like to understand everything ready for when Mobile Odin release an update that works with my phone.
Just to clarify, your Knox flag is 0x0, i.e. not tripped?
To get your modem, dial *#1234# into the dialer. The AP should be the modem. From there you should be able to find it in the list. If not in the list, you can get it by downloading the stock ROM from sammobile.com or samsung-updates.com, using the information given through the dialer to search for it.
Hi, when I go into download mode I see that the Knox counter/fuse is 0. So I understand what I'm doing, why does this make a difference what the knox counter is at for the rooting?
So, following instructions, *#1234* gives me the following AP:
AP: I9505XXUGNG8
Going back to the rooting instructions, point (7):
"Reboot your phone into download mode and flash via Odin your original kernel, matched to the ROM version you are using. You can find HERE a kernel stock collection."
I follow the link and see the following file. Is this the one I should flash using Odin at that point?
Kernel_Stock_GNG8.tar.md5
The reason why I asked about the Knox fuse is this: if tripped there's no need to use Towelroot and CF-Autoroot could be used instead.
The file you mentioned is the correct one for your device.
If you're not concerned about tripping knox then use CF-Auto-Root.
Related
I successfully rooted my Note 3(N9005) with Universal Root de la Vega v0.5 ( wasn't alowed to post a thanks in that thread or leave my commend but donated and used thanks button ).
I got the Note 3 last Saturday, mission was to get root without trigger KNOX warenty bit in 14 days or send device back without comment. So far I succeed.
I keept my orginal Firmware Version before root, because I learnt from my Note 1(N7000) that putting the an actual firmware on the device and want to get root is a bad idea.
So now I want to put the actual firmware on device but don't trigger KNOX or loose root.
Mobile Odin is abad idea because it will trigger KNOX. I have also bad expirens with it on my Note 1. 2 times soft brick and once damaged chache partition, needed to use Odin(used v1.85) to get device back running. No succsessfull flash, so never used it again.
I now found what Mobile Odin should work with Knox 0x0: http://forum.xda-developers.com/showthread.php?t=2522729
I still not sure if Ishould use it.
Update over OTA or Kies will not work or update to newer bootloader and loose root.
My idea is to use latest Firmware and Odin( v3.07 version used for Root de la Vega) without flashing bootloader(I never done on my old).
With Odin I will loose root, so I need to root with Universal Root de la Vega method again?
Which partition are nessary AP,CP, CSC and UMS?
Of course not BL and EFS.
Ordered my Note 3 over Amazon. Strange is I got a dutch/netherland version.
I most likly want to have german version(downloaded N9005XXUDMK2_N9005DBTDMK2_DBT from SamMobile).
So far I know the diffrenz is in the cache so maybee I need to wipe cache.
So here also a question why can I flash cache and still have data on, which I need to wipe if I hasve problems?
Are this different partitions?
Could be the old bootloader makes problem with newer firmware?
Is were a save way to dowload actual firmware over Kies without starting the update(will install new bootloader).
Like disconnect device while downloading, can't try because my Note 1 has already actual Firmware and my Note 3 I don't want to risk.
On the Note 1 I could download firmware wit Kies but Update failed(I think because of root), but the I had the firmware and could use Odin.
On my old Note 1 I just flashed back to older firmware with Odin then something was wrong(warenty counter was already one).
I'm just not sure about this KNOX counter, should I use Odin with Universal Root de la Vega on actual Firmware or use Mobile Odin.
Or have you another save method to update with keep root.
Let me hear your comments.
Sony667 said:
I successfully rooted my Note 3(N9005) with Universal Root de la Vega v0.5 ( wasn't alowed to post a thanks in that thread or leave my commend but donated and used thanks button ).
I got the Note 3 last Saturday, mission was to get root without trigger KNOX warenty bit in 14 days or send device back without comment. So far I succeed.
I keept my orginal Firmware Version before root, because I learnt from my Note 1(N7000) that putting the an actual firmware on the device and want to get root is a bad idea.
So now I want to put the actual firmware on device but don't trigger KNOX or loose root.
Mobile Odin is abad idea because it will trigger KNOX. I have also bad expirens with it on my Note 1. 2 times soft brick and once damaged chache partition, needed to use Odin(used v1.85) to get device back running. No succsessfull flash, so never used it again.
I now found what Mobile Odin should work with Knox 0x0: http://forum.xda-developers.com/showthread.php?t=2522729
I still not sure if Ishould use it.
Update over OTA or Kies will not work or update to newer bootloader and loose root.
My idea is to use latest Firmware and Odin( v3.07 version used for Root de la Vega) without flashing bootloader(I never done on my old).
With Odin I will loose root, so I need to root with Universal Root de la Vega method again?
Which partition are nessary AP,CP, CSC and UMS?
Of course not BL and EFS.
Ordered my Note 3 over Amazon. Strange is I got a dutch/netherland version.
I most likly want to have german version(downloaded N9005XXUDMK2_N9005DBTDMK2_DBT from SamMobile).
So far I know the diffrenz is in the cache so maybee I need to wipe cache.
So here also a question why can I flash cache and still have data on, which I need to wipe if I hasve problems?
Are this different partitions?
Could be the old bootloader makes problem with newer firmware?
Is were a save way to dowload actual firmware over Kies without starting the update(will install new bootloader).
Like disconnect device while downloading, can't try because my Note 1 has already actual Firmware and my Note 3 I don't want to risk.
On the Note 1 I could download firmware wit Kies but Update failed(I think because of root), but the I had the firmware and could use Odin.
On my old Note 1 I just flashed back to older firmware with Odin then something was wrong(warenty counter was already one).
I'm just not sure about this KNOX counter, should I use Odin with Universal Root de la Vega on actual Firmware or use Mobile Odin.
Or have you another save method to update with keep root.
Let me hear your comments.
Click to expand...
Click to collapse
Ok, so download the DBT firmware you need to match your bootloader from Sammobile (*#1234# to check current firmware) -- You won't be able to go any higher firmware than your current without upgrading your bootloader without using Mobile ODIN as far as I know. However @Killberty may chime in here as he uses DBT also and may be able to help you better.
Sony667 said:
...
So now I want to put the actual firmware on device but don't trigger KNOX or loose root.
Mobile Odin is a bad idea because it will trigger KNOX.
...
Click to expand...
Click to collapse
Mobile Odin is a bad idea because you will lose root.
Mobile Odin PRO is a great idea - there is an entire thread about that and I have used it with zero problems. We don't know 100% certain that in future versions of firmware it will still work with knox 0x0 , but so far is OK.
So I more and more thing I will give Mobile Odin Pro a change.
Yes I have the Pro version already, but had the bad experience like I posted.
Sorry I forgot to post my current version, I thought I did.
AP: N9005XXUBMI7
CP: N9005XXUBMI6
CSC: N9005PHNBMI2
So I used N9005XXUBMI7_N9005PHNBMI2_PHN to make root(same version as original).
So you think it better to flash first to the N9005XXUBMI7 N9005DBTBMI1 to have german to have same bootloader.
And later go to actual N9005XXUDMK2 N9005DBTDMK2 using Mobil Odin Pro.
Or better first try N9005XXUDMJ7 N9005DBTDMJ4 which is confirmed to work with MOP.
I'm not sure about the change XXUB to XXUD but i think a change in the former digits I also have seen on my Note 1.
Maybe this is the bootloader.
About flash with Odin, I think you right, it Flash always the complete package, this is the reason I flashed on rooting firmware 2 times.
Because I had but the package on AP and CSC.
So the only way to flash without bootloader is to repackage like in Universal RDLV.
Sony667 said:
...
So you think it better to flash first to the N9005XXUBMI7 N9005DBTBMI1 to have german to have same bootloader.
And later go to actual N9005XXUDMK2 N9005DBTDMK2 using Mobil Odin Pro.
Or better first try N9005XXUDMJ7 N9005DBTDMJ4 which is confirmed to work with MOP.
...
Click to expand...
Click to collapse
I have MJ7 but do not know about MK2 - the URDLV + Mobile Odin Pro thread is probably the right place to ask.
http://forum.xda-developers.com/showthread.php?t=2522729
OK Thanks for the answer.
I'm currently reading the URDLV + Mobile Odin Pro thread, if after what it's not clear I will ask were.
Thanks.
If u dont wanna pay 5 bucks for the MOP, just quote me
10mins of work - save 5 bucks
EDIT: uhh mk2 is out ill use my method to flash it soon
EDIT2:
http://forum.xda-developers.com/showthread.php?p=47390175
This btw.
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
I have now flashed the MK2 with Mobile Odin Pro.
I had trouble to download the flash-kernel with MOP, so I downloaded it here in the forum.
The Problem was unstable WiFi with Firmware MI7.
With MK2 I get the full speed of my Internet connection(50 MBit/s,WiFi Interface is 65 MBit/s), the Note 1 didn't(about 5-10 MBit/s).
@Killberty: I have read your thread very nice, I would have used your method if MOP had failed.
It's very good to know the command to create firmware update package.
I had bought MOB over a year ago for my Note 1, but because of 3 times it failed, I newer used it again.
I flashed with Odin and inserted root(Super User + Busybox) with temporary CWM.
This is why I hesitated and asked back here, but after all the positive response I tried.
Only Samsung realy detects what the firmware is rooted, so no firmware downloads from Samsung, I have to trust SamMobiles.
And Knox is not running, they tell you before activation of knox what all your data(in Knox Software) are lost if firmware is modified(won't start).
So I give a status update.
I wanted to find out why I can't update and maybe try Knox.
The strange think was Kies has shown PHN version, but i flashed DBT version with MOP.
I thought maybe language version is in bootloader.
So I first flashed back to MI7 with MOP. Now I don't have Modem acces(no wifi, gms..) and device restarts regulary.
So I wanted to flash the N9005XXUBMI7 N9005DBTBMI1 with standard odin, but failed because of to small hidden partition.
Hidden update for PHN was 8MB and for DBT over 60Mb, I think hidden partion is about 10MB.
So this was why Kies still have shown PHN version, because it couldn't be updated.
So I flashed original N9005XXUBMI7_N9005PHNBMI2_PHN, this was working.
Because I can't flash DBT I downloaded latest PHN N9005XXUDMJ7_N9005PHNDMJ4_PHN without bootloader of course(Killberty method, thanks.).
So I find following out.
I can't change to DBT version, because of to small hidden partition. I need a PIT file to repartition and could probably brick my device I will check forum if someone have successfully done it(I mean successfully repartitioned to other language, not bricked the device).
Kies updates can still be done, problem was I had version language combination with didn't exit from Samsung.
Downgrade is not possible, because modem isn't running.
OTA updates are available on unrooted device, even with RDLV updated script, so it should be possible to unroot by put the system partition to original state except RDLV script and get root later back without re flash.
This will not help to get Knox running, because Knox will check bootloader and not run with old one.(state from Samsung https://www.samsungknox.com/en/blog/about-root-de-la-vega).
I now have changed to DBT version.
To do what I needed a pit file, hadn't found the information on XDA but I found it on another forum.
It's in german and very nicely explained:
http://www.android-hilfe.de/anleitu...note-3-debranding-alle-eu-modelle-zu-dbt.html
http://www.android-hilfe.de/anleitu...8844-anleitung-pit-file-backup-erstellen.html
If somone need this ifo I can try to translate.
So to create a backup of your N9005 pit file you open terminal Emulator on rooted device.
su
dd if=/dev/block/mmcblk0 of=/sdcard/My-N9005.pit bs=1 skip=17408 count=4244
So you have the pit file on your internal sdcard.
I have now attached 2 pit files.
Netherlands N9005_PHN.pit
German N9005_DBT.pit
The DBT has 10 times bigger hidden volume, so the data partition is smaller. The rest is equal.
You need to flash with Re-Partition and Firmware with old boot-loader.
Go in recovery and format data partition.
Now install the actual Firmware with RDLV(without boot-loader).
Glad u got sorted
hit 'thanks' if i helped you
SM-N9005 0x0 X-Note7 ML2
XDA Developers 4 premium app
Hi, quick question. I read that with Note 3, because all the stock ROMs are knox-enabled, I can upgrade by flashing via Odin (even if I have Knox tripped).
So this:
If you try to downgrade to KNOX-disabled system(MGA for example) your device will be flaged as KNOX Void Warranty 0×1 and will get a special lock – you won’t be able to update to any KNOX-enabled firmware even by ODIN.
Click to expand...
Click to collapse
doesn't apply because there aren't knox-disabled firmwares.
What about if I downgrade using Odin? By flashing an older firmware? If I'm not on the newer bootloaders I can, right? But will Knox be tripped?
I also read that if you try to flash a non-Knox firmware onto a Knox phone you'll be bricked. I can't remember which thread/what circumstances, so hoping someone can shed some light on that.
Lastly, if I'm on unrooted stock firmware, can I use URDLV to "patch" the newest firmware, then flash it to get the rooted latest firmware WITHOUT the newer bootloader and WITHOUT tripping knox? So I can choose to downgrade should the new firmware has any problems.
Situation on trip the Knox or not: (No idea on downgrade as I never try, I think it won't under same bootloader version)
Flash any stock ROM including Kitkat officially or not with odin without rooting - won't trip knox.
Officially phone came with MJ1 or older - root with URDLV won't trip knox.
Officially phone came with MJ7 or later - root with any method will trip knox.
Officially phone came with MJ1 but later updates to MJ7 with OTA/KIES/PC Odin and later - root with any method will trip knox.
Officially at MJ1 and rooted and update to any firmware excluding KitKat ROM using Mobile Odin Pro only - root will remain and won't trip the knox.
Install any custom recovery and custom kernel will trip the knox.
Update KitKat via Mobile Odin Pro (MOP) without trip the Knox:
Your current bootloader is not newer than MJ1.
Load Official Poland ROM in MOP
Enable EverRoot, Choose option "Download mode" in after flashing. Start flashing.
After booted into Download Mode, connect your phone to your computer and run PC Odin 3.09.
Load this bootloader http://forum.xda-developers.com/showpost.php?p=49425513&postcount=352 in the BL section
Check Phone Bootloader Update and F.Reset.time, un-check Auto Reboot and Start Flashing.
When Odin says RESET!, switch off your phone and reboot normally.
I usually do this for the Note 3 I have, and it comes in really useful for devs, those running other roms, etc, that just want to upgrade the modem/wifi, bootloader, and CSC without messing with everything else. It's also handy to replace the stock kernel if you need it for whatever reason (towelroot anyone? ). Since I recently picked up a Tab Pro 8.4 from swappa, I did this for mine to do the upgrade, and thought I'd be nice and go ahead and share the extracted parts for everyone else to enjoy.
Here's the MODEM+NON-HLOS (both together and as separate files), Bootloader, Kernel, CSC, and Recovery I extracted from the new T320 1NK1 Firmware. In desktop Odin 3.09, Kernel and recovery would go in AP. Modem + NON-HLOS goes in CP, Bootloader in BL. If you flash the bootloader separately, make sure to tick the box that says bootloader update.
Bootloader:
CSC: http://www.mediafire.com/download/dje1u61d8pk8dou
Kernel: http://www.mediafire.com/download/bi2jsdcub9c9k82
Modem + NON-HLOS (Combined): http://www.mediafire.com/download/3x5bela3la8mllh
modem.bin: http://www.mediafire.com/download/oatak8vgg5vdlu5
NON-HLOS.bin: http://www.mediafire.com/download/xuaar11efato1j7
Recovery: http://www.mediafire.com/download/206e1b2g1uact6s
Full Stock Image T320UEU1ANK1-T320XAR1ANK1: http://www.mediafire.com/download/ul9d01zlrq3dl72/T320UEU1ANK1_T320XAR1ANK1_HOME.tar.md5
If you have trouble getting the bootloader and/or Modem to stick, install "Triangle Away" by @Chainfire and follow the directions to reset your counter (even if it says zero), then boot into download mode, and re-flash them with Odin and they should stick (WARNING: Triangle Away WILL TRIP KNOX).
NOTE: It has also been noted by several people that booting directly into download mode from a powered-off device and flashing the BL/Modems will make them stick as well.
To verify, you can download "Phone Info - Samsung" and make sure that all applicable items say either T320UEU1ANK1 or T320XAR1ANK1 (Bootloader,, PDA and CSC). NOTE: Not all functions of this app work for our tablets, but most do.
Triangle Away by @Chainfire: https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
Phone INFO ★Samsung★ by @vndnguyen: https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Mobile Odin Pro: https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
Enjoy, and as always, slap that Thanks button!
I'm planning on rooting and going back to an old Kernal. After rooting, I am going back to the NK1 kernal but I'm on T320UEU1ANK1. Can I go back to NK1 kernal using the T320XAR1ANK1 kernal you your post or do I have to find the T320UEU1ANK1? I know you have the full T320UEU1ANK1 image but I just to ODIN T320UEU1ANK1 kernal.
Thanks in advance.
Deca4 said:
I'm planning on rooting and going back to an old Kernal. After rooting, I am going back to the NK1 kernal but I'm on T320UEU1ANK1. Can I go back to NK1 kernal using the T320XAR1ANK1 kernal you your post or do I have to find the T320UEU1ANK1? I know you have the full T320UEU1ANK1 image but I just to ODIN T320UEU1ANK1 kernal.
Thanks in advance.
Click to expand...
Click to collapse
You can use the kernel in my post.
Sent from my leanKernel 3.16 powered stock 4.4.2 SM-N900T
Thank you!
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Just a question but I believe it does not affect root, if I were to install the modem/firmware I would not lose root correct? Also, if you were to flash the whole package, does towel root or manual root (think I used Hashcode script vs towel root) does the new firmware allow root access? I don't believe these devices are as locked down as a carrier device, but just wondering! When people refer to firmware and modem, what part is the firmware on this actually? I see the modem, but is firmware part of the NON-HLOS or what ?Thanks!
Edit: Seeing another thread, seems CF Auto-Root will still work, answering my above questions, thanks and sorry for not fully researching first!
bigmike35 said:
Just a question but I believe it does not affect root, if I were to install the modem/firmware I would not lose root correct? Also, if you were to flash the whole package, does towel root or manual root (think I used Hashcode script vs towel root) does the new firmware allow root access? I don't believe these devices are as locked down as a carrier device, but just wondering! When people refer to firmware and modem, what part is the firmware on this actually? I see the modem, but is firmware part of the NON-HLOS or what ?Thanks!
Edit: Seeing another thread, seems CF Auto-Root will still work, answering my above questions, thanks and sorry for not fully researching first!
Click to expand...
Click to collapse
My Tab Pro 8.4 (Wifi) shipped with the latest firmware already installed. I didn't want to use CF Auto-Root because it trips the Knox flag, so I flashed this kernel (http://forum.xda-developers.com/showthread.php?t=2786800) and then was able to use TowelRoot, which doesn't trip Knox.
Nice job. I upgraded using the full image, downgraded the kernel, rooted my T320, restored your kernel. Very simple and all worked great. Thanks for this.
@toastido Could you give me a link to Kernel BNI1 (Portuguese version) plz?
Thanks in advance.
Hi;
I have SG s4 mini duos with xxubnb1 firmware 4.2.2 (PDA: I9192xxubnb1; phone: I9192xxubnb1; CSC: I9192OJVBNB1).
I'd like to root without trip KNOX.
I tried several methods without success:
-saferoot not compatible phone (only MK4 i9192)
- Towelroot not compatible;
-srsroot found a method "root4" but when I check with rootcheker not have root;
-kingoroot after trying several fault, without success, he proposed at the end of injecting this "tar" file "wmrecovery_samsung_GT-I9192.tar" I refused. (could change knox).
This is the compressed file picked from temporaly kingoroot folder: (see in attached file)
After several readings on different forums, an idea occurred to me: doing the same thing using the "ROOT newest 4.4.2 without tripping KNOX" method that involves injecting a kernel that can be root, realize the root then reinject the original kernel.
I explain:
1) flashing the kernel 9192xxubmk4 "boot.img" in my phone;
2) root with saferoot
3) run the phone to see if there is not bug, if
4) flashing the original kernel and keeping the root.
What do you think of this approach?
Thank you
succes
dedelekid said:
Hi;
I have SG s4 mini duos with xxubnb1 firmware 4.2.2 (PDA: I9192xxubnb1; phone: I9192xxubnb1; CSC: I9192OJVBNB1).
I'd like to root without trip KNOX.
I tried several methods without success:
-saferoot not compatible phone (only MK4 i9192)
- Towelroot not compatible;
-srsroot found a method "root4" but when I check with rootcheker not have root;
-kingoroot after trying several fault, without success, he proposed at the end of injecting this "tar" file "wmrecovery_samsung_GT-I9192.tar" I refused. (could change knox).
This is the compressed file picked from temporaly kingoroot folder: (see in attached file)
After several readings on different forums, an idea occurred to me: doing the same thing using the "ROOT newest 4.4.2 without tripping KNOX" method that involves injecting a kernel that can be root, realize the root then reinject the original kernel.
I explain:
1) flashing the kernel 9192xxubmk4 "boot.img" in my phone;
2) root with saferoot
3) run the phone to see if there is not bug, if
4) flashing the original kernel and keeping the root.
What do you think of this approach?
Thank you
Click to expand...
Click to collapse
I just have my answer now : " it's a great et un grand succès".
I have do it just like I had explain in first thread, just use this script to prepare kernel mk4 for flashing with odin:
http://forum.xda-developers.com/show....php?t=2446269
Et voilà, root checker confirme the root and supersu update su binairies with stopping knox .
And in download knox 0x0 ........... yes.
Now I place my double sim to see if all is right, if not i'll flash in second time with the original kerne nb1.
Good night.
Simple, complete. It was my guide of root. Thank you so much.
Hey there, I'm an idiot... I tripped KNOX and now phone is stuck on Tmobile boot screen. With so many different ways to do things and so many variants of this frickin phone and Android it seems the rules are every changing.
So my questions:
1.) How can I get this thing back to working? Can I flash a factory image with ODIN? If so which factory image do I use and what version of ODIN and what boxes need to be ticked in ODIN?
2.) Will #1 reset KNOX? Can KNOX be reset?
3.) Whats the best method to get the thing rooted so I can put a ROM on it. I hate TouchWiz. I tried using this method but it landed me here... http://www.androidrootz.com/2014/04/how-to-root-galaxy-s5-recovery-root.html
Thanks in advance....
Can I just flash the corresponding firmware with ODIN? Is it that simple? Does the firmware version displayed in factory recovery always correspond to the firmware to flash with ODIN? Any insights would help!!!! Thanks for your time!
sammobile dot com, grab a stock ROM for your model S5 (G900T), flash with ODIN
KNOX is permanently tripped now, no way to reset
your knox is permanently tripped, so might as well do what you want with the phone.
if you can get into download mode, you should be able to flash a recovery through ODIN, and then flash the rom of your choice. if that doesn't work, follow Detection's post above and flash a factory Tmobile rom through ODIN and start again.
That's all great thanks all, but does the firmware have to match the version that corresponds to the recovery that is currently on it? For instance, if I flashed 5.1.1 me thinks I wouldn't be able to root it or downgrade it thereafter, correct?
[bor]Its the loosey goosey instructions for multiple methods of doing the same thing for various android versions that make this sketchy. I found it easier to flash my HTC magic with jesus freak and a gold card than it is to flash this thing...or maybe my brain is decaying. Anyway, not what I expected for a common android phone. [/eor]