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
Related
I've got BMI6 (baseband) BMI7 (build) and I've been offered an update OTA today which I've postoned
Has anyone updated their Vodafone UK branded N3 in the last couple of days, what version does it go to?
I'm guessing the update will make it more difficult to root? I haven't rooted yet but I'm not sure how much longer I can resist the temptation!
You can root anytime mate. I'm on MJ7 currently. .. It's the bootloader that gets updated meaning you can't go back to old firmware. The bootloader gets locked from MJ3 onwards. You can root your phone without triggering knox...I wasn't bothered about it so I used the normal way ?
Sent from my SM-N9005 using Tapatalk
DO NOT TAKE OTA IF YOU WANT TO ROOT! It contains the new bootloader...
How to update to latest firmware without bootloader, but camera and wifi working:
Step 1)
Download URDLV (script, sd card files, odin v3.09) from its thread http://forum.xda-developers.com/showthread.php?t=2498850
Download your latest firmware from www.sammobile.com/firmwares
-> to do so type *#1234# in the dialer and put your csc minus the last 4 signs into the sammobile search box (sould look like n9005dbt) and download the topmost file
Put urdlv.bat and all its components in c:/urdlv
Win+r
Cmd.exe
Press Enter
Cd c:/urdlv
Urdlv full
Drag your firmware in the console window
press Enter
Wait until its done
Your files are in the output folder
Untar them with e.g. 7zip
Step 2)
Prepare:
NON-HLOS.bin <- extracted from original firmware
boot.img <- extracted from original firmware
cache.img.ext4 <- created by Universal RDLV
hidden.img.ext4 <- extracted from original firmware
modem.bin <- extracted from original firmware
recovery.img <- extracted from original firmware
system.img.ext4 <- created by Universal RDLV
then follow these steps:
install cygwin64 (with all default)
start it once
go to c:/cygwin/home/<username_u_have>
put mentioned files there
in cygwin:
tar -H ustar -c NON-HLOS.bin boot.img cache.img.ext4 hidden.img.ext4 modem.bin recovery.img system.img.ext4 > DMJ7.tar
md5sum -t DMJ7.tar >> DMJ7.tar
mv DMJ7.tar DMJ7.tar.md5
Step 3)
flash generated file with odin v3.09
step 4)
put the rootdelavega.sh and root_files on your internal storage
reboot
remove the files
reboot
RESULT: KNOX 0x0, binary official, latest firmware, root
leave a 'thanks' if i helped
SM-N9005 URDLV 0x0
XDA Developers 4 premium app
fz9999 said:
I've got BMI6 (baseband) BMI7 (build) and I've been offered an update OTA today which I've postoned
Has anyone updated their Vodafone UK branded N3 in the last couple of days, what version does it go to?
I'm guessing the update will make it more difficult to root? I haven't rooted yet but I'm not sure how much longer I can resist the temptation!
Click to expand...
Click to collapse
I'm on Vodafone UK. I rooted using URDLV method while on MI7 and won't update via OTA. If you're not already rooted, updating to MJ7 via OTA will mean you will flash a locked bootloader. This means you will trip your Knox warranty flag if you try to root after OTA.
This update looks like it's the MJ6 release according to what's available on sammobile.com
PDA: N9005XXUDMJ6
CSC: N9005VFGDMJ1
MODEM: N9005XXUDMJ4
If you're already rooted, the easiest method to update would be to use mobile odin pro 3.85. I.e. download the update zip file from sammobile.com, extract zip to tar.md5 and copy it to your phone storage. Then flash using mobile odin pro. This won't flash your bootloader but will update your phone software.
Sent from my SM-N9005 using Tapatalk
dsm52 said:
I'm on Vodafone UK. I rooted using URDLV method while on MI7 and won't update via OTA. If you're not already rooted, updating to MJ7 via OTA will mean you will flash a locked bootloader. This means you will trip your Knox warranty flag if you try to root after OTA.
This update looks like it's the MJ6 release according to what's available on sammobile.com
PDA: N9005XXUDMJ6
CSC: N9005VFGDMJ1
MODEM: N9005XXUDMJ4
If you're already rooted, the easiest method to update would be to use mobile odin pro 3.85. I.e. download the update zip file from sammobile.com, extract zip to tar.md5 and copy it to your phone storage. Then flash using mobile odin pro. This won't flash your bootloader but will update your phone software.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Have to admit thats far easier thsn mine
And working
Thumbs up!
hit 'thanks' if i helped you
SM-N9005 DMJ7 0x0
XDA Developers 4 premium app
@Killberty
Hi,
I finally took the pludge after a good week of research and tried your method, I was on URDLV MI7 and wanted to upgrade to MK2.
I followed your instructions but it appeared that I encountered a boot loop (3/4 times) so had to power off the phone and then Odin back the stock MI7 to recover the device. Yes I tripped. Phone was also very laggy, the camera didn't work and I got errors such as Process system isn´t responding (wait/ok). WIFI was ok. No SIM was present so I didn't check network connection.
After URDLV'ing MI7 again, I then used Mobile Odin pro to get to MK2 with no problems and the phone was back to its normal performance.
@GalaxHe also described a similar method in the Universal Root de la Vega v0.5 [ Root without tripping KNOX or Malware! ] thread (direct post link) but his method includes the additional files:
rpm.mbn sbl1.mbn sdi.mbn tz.mbn
I would like to ask please;
how long did your device take to install/reboot when you upgraded to the latest bootloader?
how many times did your device reboot?
why did you not include the same files that @GalaxHe did?
Many thanks
& thanks to @Chainfire for Mobile Odin as I was not confident in trying your method a 2nd time in an attempt to recover.
All good.
xitobor said:
@Killberty
Hi,
I finally took the pludge after a good week of research and tried your method, I was on URDLV MI7 and wanted to upgrade to MK2.
I followed your instructions but it appeared that I encountered a boot loop (3/4 times) so had to power off the phone and then Odin back the stock MI7 to recover the device. Yes I tripped. Phone was also very laggy, the camera didn't work and I got errors such as Process system isn´t responding (wait/ok). WIFI was ok. No SIM was present so I didn't check network connection.
After URDLV'ing MI7 again, I then used Mobile Odin pro to get to MK2 with no problems and the phone was back to its normal performance.
@GalaxHe also described a similar method in the Universal Root de la Vega v0.5 [ Root without tripping KNOX or Malware! ] thread (direct post link) but his method includes the additional files:
rpm.mbn sbl1.mbn sdi.mbn tz.mbn
I would like to ask please;
how long did your device take to install/reboot when you upgraded to the latest bootloader?
how many times did your device reboot?
why did you not include the same files that @GalaxHe did?
Many thanks
& thanks to @Chainfire for Mobile Odin as I was not confident in trying your method a 2nd time in an attempt to recover.
All good.
Click to expand...
Click to collapse
1) i did never upgard my bootloader thats why i didnt trip
2) once then i rebooted twice for the URDLV sd card part
3) sbl= secondary bootloader bl1 = bootloader1 so i dont inculde em, no bootloader updates
u might have skipped some step but i myself any many others can confirm it works...
Killberty said:
1) i did never upgard my bootloader thats why i didnt trip
2) once then i rebooted twice for the URDLV sd card part
3) sbl= secondary bootloader bl1 = bootloader1 so i dont inculde em, no bootloader updates
u might have skipped some step but i myself any many others can confirm it works...
Click to expand...
Click to collapse
Thank you for your reply.
Doh, @1) I didn't mean bootloader, I meant to say firmware.
I didn't upgrade my bootloader either and I didn't skip any steps. As I said, its all good, my phone is ok but who knows what happened in my case. Just had a few questions to see if I could understand it more.
Cheers.
xitobor said:
Thank you for your reply.
Doh, @1) I didn't mean bootloader, I meant to say firmware.
I didn't upgrade my bootloader either and I didn't skip any steps. As I said, its all good, my phone is ok but who knows what happened in my case. Just had a few questions to see if I could understand it more.
Cheers.
Click to expand...
Click to collapse
Hahah np and sorry for your knox :/
Maybe you had kies open or a lil bug in the cable or whatever (noone knows what samsung software does....) well i dont understand it at all as is worked for at leasr 5 people...
hit 'thanks' if i helped you
SM-N9005 0x0 X-Note7 ML2
XDA Developers 4 premium app
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.
Hello,
I'm using a SGS4 rooted since more than one year and a half (odin, flash a small root bin file if I remember well, flash counter set to 1, no custom recovery and no nandroid backup)
Since I want to implement NFC card emulation now avaliable in android 4.4 in one of my apps, I'd like to update.
I've seen few threads on the subject, and most of them date from a long time (am I late ? ). I'd like to know how I could update normally my actual rom (provided by Orange, precisely I9505XXUAME2), or move to another slightly modified rom like the base rom provided by samsung without all these apps that you can only remove with root.
I don't want to have any data issue I've read about, I don't want to lose my actual apps and their data. (Nandroid backup then restoring apps and their data through nandroid manager?)
Also, if possible i'd like to update without losing my start screen, my parameters, etc... (in the worst case I'd re-set them manually). And finally of course I want to have it rooted at the end of the process.
In fact I want it to be just like if I had done an OTA update, then rooted it.
Also, How to update without setting the Knox counter to 1 ? (My flash counter is set to 1, should I use Triangle Away?)
Is there any simpler way than flashing the new firmware and then importing everything from my old data to the new and reinstalling the changes I made to the system (like avast & such) ?
Also, maybe there exists newest versions of the firmware, but without the new bootloader that has the knox counter ?
Thanks in advance!
tboss1995 said:
Thanks in advance!
Click to expand...
Click to collapse
1. You can't receive OTA updates if you have rooted your device. You have to flash the firmwares via ODIN.
2. You don't need wipe nothing if you flash new stock firmware. Instructions: Flash new firmware (if you don't have wifi flash it one time more), root it again then and you're done. Your data don't have to be affected (maybe you only have to reinstall some app if the data/cache was moved to the SDCARD).
3. Flashing one new stock firmware don't modify KNOX. You actived KNOX rooting your device or flashing one custom recovery. Knox: 0x1 can't be reset. Triangle away only reset the flash counter.
Thanks for your fast answer !
So, flashing a firmware doesn't impact the data.
Updating via Kies sets the Knox counter. Updating via odin doesn't ? Don't I have to do any sort of un-root before updating ?
Is there anything specific I should know about root ? Because I don't want to flash a firmware that I won't be able to root without setting the knox counter.
Also I think that since we can't revert the bootloader update, maybe i'd better not update that bootloader so that I can update future versions and root them without setting knox counter, by installing a knox-free rom even before a knox-free root is released...
Where can I find these roms?
tboss1995 said:
Thanks for your fast answer !
So, flashing a firmware doesn't impact the data.
Updating via Kies sets the Knox counter. Updating via odin doesn't ? Don't I have to do any sort of un-root before updating ?
Is there anything specific I should know about root ? Because I don't want to flash a firmware that I won't be able to root without setting the knox counter.
Also I think that since we can't revert the bootloader update, maybe i'd better not update that bootloader so that I can update future versions and root them without setting knox counter, by installing a knox-free rom even before a knox-free root is released...
Where can I find these roms?
Click to expand...
Click to collapse
1. Updating via ODIN or Kies don't set the KNOX counter. Downgrading YES.
2. Root dissapear if you flash new update via ODIN.
3. You can flash latest firmware and root them without KNOX. Take a look for the method: HERE.
Thanks for the answer again!
Howerver I still have 3 questions because I like to understand what I'm doing :
1. I understand the two terms ROM (OS of the phone) and bootloader (after a certain update, it adds the knox counter, and you can't downgrade it, and it also prevents towelroot from working). What is the called "kernel" ?
2. Up to exactly what version of the bootloader/rom does towelroot work ?
3. What is the difference between "knox-free" and "knox counter 0"? At the end of the method, will I have the new bootloader with a knox counter set to 0, or the old bootloader ?
tboss1995 said:
Thanks for the answer again!
Howerver I still have 3 questions because I like to understand what I'm doing :
1. I understand the two terms ROM (OS of the phone) and bootloader (after a certain update, it adds the knox counter, and you can't downgrade it, and it also prevents towelroot from working). What is the called "kernel" ?
2. Up to exactly what version of the bootloader/rom does towelroot work ?
3. What is the difference between "knox-free" and "knox counter 0"? At the end of the method, will I have the new bootloader with a knox counter set to 0, or the old bootloader ?
Click to expand...
Click to collapse
1. Take a look: HERE.
2. Nobody know it.
3. - KNOX free: This therm is used for the custom ROMS normally. This mean that flashing this ROM dont touch the KNOX counter.
- KNOX counter: You still having your device in warranty if you have KNOX:0x0. You void your warranty if you have KNOX:0x1 in DOWNLOAD MODE.
So it means I'll still have the new bootloader ?
For those who may come to read this article and don't want to watch a video, I've found an article explaining what kernels are. http://m.androidcentral.com/android-z-what-kernel
Hello all.
I know some (maybe all) questions of mine have been answered somewhere, but I just couldn't find them in a concise list, so to say...so please be gentle if I am asking something that's already been answered somewhere.
Here goes:
I bought a second hand Samsung S5, G900F, with SEE firmware G900FXXU1BOH5, still one year in warranty (it was bought from Telenor Serbia, but I can see it is actually with SEE firmware, no operator bloatware, logos etc and sha256sums are equal for SEE and MSR LP firmwares, both taken from Sammobile).
Since it is a rather fresh LP build, as we all know there is no way to root it and keep warranty (knox will trip), unless you go way back to KK with ANE2 firmware (or earlier).
Now, there are 2 versions of instructions for doing that:
- just flash SEE firmware build ANE2, reboot, wipe, install towelroot
- flash SEE firmware build ANE2, use PIT file, reboot, wipe, install towelroot
First confusion is here: do I need to use PIT file? Did partition layout change and will official KK firmware do it on it's own or not?
If PIT file is required, at what moment I should use it? First PIT, then firmware or the other way around?
Also, are bootloader, kernel and CP files required for anything (I do have full official KK image for SEE, so I guess I don't need these files separately, but...)?
Do I need to flash bootloader at some point because KK has different bootloader than LP, or the full firmware will take care of that too?
Next set of questions regards going back to LP, which does not seem to be answered precisely:
if I downgrade to KK (using one of the procedures mentioned), and successfully install root and SuperSU, how do I upgrade back to LP?
- do I install latest LP firmware for SEE through Odin?
- or, do I activate OTA upgrade and let the phone upgrade/update itself back from KK to LP?
I am pretty sure that the first method will again destroy root access, but is the second method even viable now? Will OTA work or I'd need to go through KIES?
Finally, since I'm dealing with stock firmwares all along, knox should stay at 0x0, but what about status? Will it change at some point from official to custom (shouldn't, but than again...)?
If it is not possible to do what I need, the solution seems to be to go to custom LP rom that has been rooted already, and has knox deactivated etc etc. - is it really the only way?
If so, can you propose which ones will not change the status of the phone (knox, official/custom)? How about Galaxy project, that one seems pretty stock-ish to me...
Sorry again if asking wrong/already answered questions and thank you.
Cheers, Andrea
I'm not sure how/if the partition layout changes between KK and LP, so I can't say for certain that a pit file *is* needed.....
My advice would be to try to roll back to KK without using one.......
If the roll back doesn't work, then try with the pit file.......
Plan A......Odin flash KK firmware then recovery wipe, reboot and towelroot.....In that order.
Plan B......Odin flash pit, odin flash KK firmware then recovery wipe, reboot and towelroot.....again in that order.
The bootloader, kernel etc files are all contained in the firmware that you will have downloaded from Samsung-updates.com or sammobile.com so no need to source and flash them separately.
As for upgrading again and keeping root....
Odin won't do that with a regular firmware, OTA will probably fail and Kies....well, I've always tried to avoid using it.
Realistically, the only options you have for upgrading and keeping root, are one of two apps from Chainfire.......
Either Mobile Odin or Flashfire......Both of which inject root while flashing firmwares......as Flashfire is the 'successor' to Mobile Odin, the chances are that it'll have a better chance of success than the older Mobile Odin.
One last thing......The pit file......
If you *do* find that you need one, make sure you get the CORRECT one......
It's not going to do your device ANY good if you try to flash a 32gb pit onto a 16gb device.....There may be other differences with the available pit files too, so research them before flashing one......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
I'm not sure how/if the partition layout changes between KK and LP, so I can't say for certain that a pit file *is* needed.....
My advice would be to try to roll back to KK without using one.......
If the roll back doesn't work, then try with the pit file.......
Plan A......Odin flash KK firmware then recovery wipe, reboot and towelroot.....In that order.
Plan B......Odin flash pit, odin flash KK firmware then recovery wipe, reboot and towelroot.....again in that order.
The bootloader, kernel etc files are all contained in the firmware that you will have downloaded from Samsung-updates.com or sammobile.com so no need to source and flash them separately.
As for upgrading again and keeping root....
Odin won't do that with a regular firmware, OTA will probably fail and Kies....well, I've always tried to avoid using it.
Realistically, the only options you have for upgrading and keeping root, are one of two apps from Chainfire.......
Either Mobile Odin or Flashfire......Both of which inject root while flashing firmwares......as Flashfire is the 'successor' to Mobile Odin, the chances are that it'll have a better chance of success than the older Mobile Odin.
One last thing......The pit file......
If you *do* find that you need one, make sure you get the CORRECT one......
It's not going to do your device ANY good if you try to flash a 32gb pit onto a 16gb device.....There may be other differences with the available pit files too, so research them before flashing one......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
OK, your plans A and B for downgrade are more or less like I thought they should be...
But, on the subject of returning to LP after the rooting of KK with towelroot...regular firmware with Odin will erase everything and ofcourse kill su, like I said in my original post - but, why do you think OTA won't work?
If the downgrade does not change knox (stays 0x0) and status (stays Official) why would OTA upgrade fail? It changes some components, removes some and adds some new, why would it touch /xbin/su if OTA process does not know about its existance in the first place?
Kies should do the same like OTA (at least so they say) but I don't like it also, so I'd use it as a final resort.
Then we have Flashfire - I'm not quite clear how that works...would I be able to install latest LP over downgraded KK, and at the same time install supersu (from where?) during the installation of the original LP firmware? Because that's what I'm understanding from your post, that the process goes like that...
If not, what kind of firmware does Flashfire use? Custom ROM with su, disabled knox etc, simply allowing you to install it from the phone, or original firmware as well? What would be the procedure with it and would it change knox (shouldn't) or status from Official to Custom if I use it with original LP firmware to return from rooted KK to LP?
At last, the pit file - I could obtain only one for 16GB version that is not specifically marked as for some region or country, and I don't know if there is a pit file for 16GB SEE (South East Europe) G900F to be found. I tried searching but the best I could find was for BTU, which is for UK but seems to be usable for all of North Europe, everything else was much more specific.
Does somebody have/know where to find pit file that would be suitable for my device?
Again, thanks
I need to quantify anything i write by saying that the info i share, is (for me at least) untested.....i've done the research and reading so that i am familiar with the processes if i decide to put them to practical use in the future....right now, I'm happy to stay with my rooted, debloated, modified, stock KitKat setup......
That being said.......
You need to find a way to retain root through the *whole* downgrade/upgrade process......many people are finding it damn near impossible to root the latest LP firmwares.....so keeping root would be an advantage.......
I used towelroot on my phone, and it set the system status on my phone to custom, which is enough to potentially cause issues with OTA (I can't say for certain as I rooted my phone on 4.4.2 and disabled the OTA function so I don't have first hand experience with this).
Flashfire will flash regular firmwares as I said in my previous reply......part of this process is to install superSU, so you don't have to worry about that......
Here's the Chainfire Flashfire thread...
http://forum.xda-developers.com/showthread.php?p=59959596
The pit file........
If your device is the F variant with a 16gb user storage partition, then the BTU 16gb pit you mentioned should be ok.....
As I'm sure you know, the pit file doesn't install any part of the firmware or OS, all it does is to set the 'memory blocks' to their default sizes/quantities/ratios ready for an OS flash......so if your device is 16gb then a 16gb pit should work.....
If you are still unsure about it, there is a way to extract a pit file from your existing setup using commands in terminal emulator.....I read about it here on XDA so a quick search should lead you to the thread......
Edit......here's the link.....
http://forum.xda-developers.com/showthread.php?p=52329647
the title of the thread mentions efs and other stuff (no mention of pit) but the second or third post down explains how to backup your pit.......
Edit 2.....forget about that method.....
You need root access to do it.....and you won't have root access until after the point when you will (potentially) need the pit......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
I need to quantify anything i write by saying that the info i share, is (for me at least) untested.....i've done the research and reading so that i am familiar with the processes if i decide to put them to practical use in the future....right now, I'm happy to stay with my rooted, debloated, modified, stock KitKat setup......
That being said.......
You need to find a way to retain root through the *whole* downgrade/upgrade process......many people are finding it damn near impossible to root the latest LP firmwares.....so keeping root would be an advantage.......
I used towelroot on my phone, and it set the system status on my phone to custom, which is enough to potentially cause issues with OTA (I can't say for certain as I rooted my phone on 4.4.2 and disabled the OTA function so I don't have first hand experience with this).
Flashfire will flash regular firmwares as I said in my previous reply......part of this process is to install superSU, so you don't have to worry about that......
Here's the Chainfire Flashfire thread...
http://forum.xda-developers.com/showthread.php?p=59959596
The pit file........
If your device is the F variant with a 16gb user storage partition, then the BTU 16gb pit you mentioned should be ok.....
As I'm sure you know, the pit file doesn't install any part of the firmware or OS, all it does is to set the 'memory blocks' to their default sizes/quantities/ratios ready for an OS flash......so if your device is 16gb then a 16gb pit should work.....
If you are still unsure about it, there is a way to extract a pit file from your existing setup using commands in terminal emulator.....I read about it here on XDA so a quick search should lead you to the thread......
Edit......here's the link.....
http://forum.xda-developers.com/showthread.php?p=52329647
the title of the thread mentions efs and other stuff (no mention of pit) but the second or third post down explains how to backup your pit.......
Edit 2.....forget about that method.....
You need root access to do it.....and you won't have root access until after the point when you will (potentially) need the pit......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
OK, Flashfire part now confuses me...if I use that (already downloaded) only with LP firmware tarball, do I need to go back to KK to obtain root with towelroot or not?
I mean, if Flashfire will install SuperSU (which I already have installed, but not working obviously) during the flashing of full firmware tarball, why would I need to root before using Flashfire? Or it won't even work if you don't already have root...? Flashfire thread does not give specific requirements, although it makes sense that you need to have root before being able to use Flashfire...
Secondly, I thought that using towelroot will not change the status of the device in any way - no custom status, no knox=0x1? Now, you say that it did change your status to custom...do you think that if that happened to me, flashing original LP firmware tarball through Flashfire would return status to official?
Ah, so many questing that link to each other...and just when you think you've got one answer, it generates another question...
You are correct, you can't use Flashfire unless you already have root.
And Flashfire will only return the device status to official if you don't get it to root the firmware as it flashes it.....
Basically, any modifications made to the original firmware have the potential to set the status to custom.......and in some cases, trip knox.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
You are correct, you can't use Flashfire unless you already have root.
And Flashfire will only return the device status to official if you don't get it to root the firmware as it flashes it.....
Basically, any modifications made to the original firmware have the potential to set the status to custom.......and in some cases, trip knox.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
Hm, I've seen couple of solutions to that official/custom problem, although for Note3...basically, it's cache/dalvik clean, and deinstalling and reinstalling some app that uses root therefore triggering something that changes status to custom.
Which app that would be - it's a guessing game. Sometimes it's Titanium backup, might be Root explorer, Battery Monitor Widget...usually, reinstalling it fixes the problem.
But, now there is a second problem here - it seems that you need to have customized LP firmware to keep root using Flashfire...
http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044
and
http://forum.xda-developers.com/galaxy-s5/development/rom-ane4-kitkat-4-4-2-multi-csc-t2813628
Do you think this is true and stock LP rom can't be flashed with Flashfire, getting rooted along the way?
There is an xposed module which will trick the phone into displaying 'official' rather than 'custom' though how deep into the OS this mod goes, I don't know.....
It *may* be enough to restore OTA functionality, but OTA isn't your 'best solution' anyway.......
It was always (and still is) my understanding, that Flashfire was/is able to flash regular 5.0 firmwares and 'inject' them with root......
But as I said, having not actually used it, I'm the first to admit, I'm probably not the best (most informed) person to answer your questions......My advice would be to visit the Flashfire thread and ask there.....You'll get answers from people who have actually used it
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
I guess you've got your answer then.....
1) Download the lollipop firmware and extract the bootloader and modem....
2) Rollback the device (with or without pit depending on what works) to KitKat.
3) Do the necessary wipes.
4) Reboot and towelroot.
5) Install Flashfire and use to flash and root Lollipop firmware.
6) Do not attempt to boot phone normally as the flash won't be complete.
Instead, 7) boot to download mode and Odin flash the previously extracted bootloader and modem....
8) (Might be necessary at this point to perform recovery wipes of cache and data)
9) Finally, reboot as normal.
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
I guess you've got your answer then.....
1) Download the lollipop firmware and extract the bootloader and modem....
2) Rollback the device (with or without pit depending on what works) to KitKat.
3) Do the necessary wipes.
4) Reboot and towelroot.
5) Install Flashfire and use to flash and root Lollipop firmware.
6) Do not attempt to boot phone normally as the flash won't be complete.
Instead, 7) boot to download mode and Odin flash the previously extracted bootloader and modem....
8) (Might be necessary at this point to perform recovery wipes of cache and data)
9) Finally, reboot as normal.
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
Thank you, I've seen your other post in Flashfire section and already replied to the one you refer to, but just to be sure, let's ask here too:
how to extract BL and modem from original LP tar.md5 file, because that's all I have?
Cheers.
This thread explains how to do it.....
http://forum.xda-developers.com/showthread.php?t=2864264
It's been written with the S3 in mind but I should think the procedure is exactly the same for the S5.
The thread mentions winRAR or similar as the extraction tool and goes on to say that it's 'paid' software.......as a free alternative, I've always used 7 zip and have never had any problems with it......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Winrar has a 30 day trial, and still works fine once that has expired, but gives a nag screen popup when you use it
I use both Winrar & 7zip
Yep, just seen it, reading now...actually, it was also mentioned in a reply to my post in Flashfire thread, so I have to try what's written in this howto and see how it goes...
Hi guys, to my understanding BL/CP are available in tar or zip formats and may be updated via Odin or Twrp respectively. Appreciate any advice as to differences (if any) between the two methods. TIA
The only difference is that one (.zip) can be flashed via TWRP (this would mean you have a custom rom and a tripped Knox counter). The other (.tar) is signed by Samsung and can be flashed via Odin without tripping Knox.
CuBz90 said:
The only difference is that one (.zip) can be flashed via TWRP (this would mean you have a custom rom and a tripped Knox counter). The other (.tar) is signed by Samsung and can be flashed via Odin without tripping Knox.
Click to expand...
Click to collapse
I reckon this probably means it doesn't matter to flash with twrp or odin if knox is already 0x1.
Xp3riaXpr3ss said:
I reckon this probably means it doesn't matter to flash with twrp or odin if knox is already 0x1.
Click to expand...
Click to collapse
Correct. I find it easier to flash in TWRP because it's simpler to stay where I am and download the file, reboot to recovery and flash. Rather than going upstairs to my computer, downloading the file, putting phone in Download mode, opening Odin and loading the files, then connecting the phone to the computer then flashing the files.
CuBz90 said:
Correct. I find it easier to flash in TWRP because it's simpler to stay where I am and download the file, reboot to recovery and flash. Rather than going upstairs to my computer, downloading the file, putting phone in Download mode, opening Odin and loading the files, then connecting the phone to the computer then flashing the files.
Click to expand...
Click to collapse
True that. I only ever return to Odin to flash official firmware in the event of soft bricks with denied access to Twrp, however, was getting confused partly due to written instructions for roms requiring BL/CP to be flashed in download mode. Thanks for clearing this up. Cheers.
my current booloader is version 1...can anybody tell me how can update it to version 4? i am using s7 edge SC02H(snapdragon) japan.
thanks
Looking for the right modem and bootloader files
Hello,
I'm running Nougat on my s7 g930f it's using the tgp rom. In preparation for an oreo upgrade I atempted to flash an odin-zip file I found on LightRom's page, thinking it would give me a modem update. This was an extremely bad idea. Now my system does still boot, but I have no signal at all, my phone number, base band, IMEI, mobile network, etc all show as unknown under settings, about phone and the various status checks. Now when I atempt to go in to odin again to flash another modem update now I'm told that the atempt has failed. I'd appreciate some help. What file do I need to get the bl and the cp file? I'm running twrp 3.2.3, and i'd like my signal back.
Thanks.
Dave.