Has anyone run Mobile Odin on a Note which I understand must be rooted? I cannot use PC Odin to root my Note because Odin does not detect my Note. However, there now is a way to root the Note without using PC Odin (see link below). I would like to flash the new UK ICS ROM on my Note using Mobile Odin because I cannot use PC Odin.
http://forum.xda-developers.com/showthread.php?t=1647148
Gaugerer said:
Has anyone run Mobile Odin on a Note which I understand must be rooted? I cannot use PC Odin to root my Note because Odin does not detect my Note. However, there now is a way to root the Note without using PC Odin (see link below). I would like to flash the new UK ICS ROM on my Note using Mobile Odin because I cannot use PC Odin.
http://forum.xda-developers.com/showthread.php?t=1647148
Click to expand...
Click to collapse
I haven`t used it yet but i`am 99,99 % sure you can use it without a problem. It`s similar to the pc-version in its function. I purchased the MobileOdin Pro version wich flashes firmware and injects root ans SuperSU.
Though CWM-manager can also be used for flashing firmware, but i think you loose root after the flash.
yes you can use Mobile Odin i have upgraded to uk ics with it and downgrade it back to gb i no you need root thow
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
i was on 4.3 on my galaxy note3 32gb CYO and wanted to change to 4.4.2 for COS (greek provider) i used odin and failed saying odin invalid ext4 image i used the .pit file and enabled the re-partition im using the official cable and tried both usb 2 and 3 ports same problem. also installed samsung drivers for this device. Im running windows 8.1 if this helps at all
SiLeNtOnegr said:
i was on 4.3 on my galaxy note3 32gb CYO and wanted to change to 4.4.2 for COS (greek provider) i used odin and failed saying odin invalid ext4 image i used the .pit file and enabled the re-partition im using the official cable and tried both usb 2 and 3 ports same problem. also installed samsung drivers for this device. Im running windows 8.1 if this helps at all
Click to expand...
Click to collapse
I also had issues when I first tried rooting my phone with odin. I ended up using Kingo to root my phone at first. After that it has been smooth sailing flashing custom roms. I am assuming you are running a rooted 4.3 or are you on a stock 4.3 trying to flash to an official kitkat?
Sent from my SM-N900V using XDA Free mobile app
I want to update my Galaxy S5 (SM-G900M) for the last update but I want to keep the root without change the Knox counter, so I'm trying to update via Odin Mobile Pro but I need the Bootloader and the Modem files in the .tar format for Odin on PC (right?).. So anyone can please provide me these files for my cell phone cuz I can't find they and don't know what I have to do to get them :S
Luckzao said:
I want to update my Galaxy S5 (SM-G900M) for the last update but I want to keep the root without change the Knox counter, so I'm trying to update via Odin Mobile Pro but I need the Bootloader and the Modem files in the .tar format for Odin on PC (right?).. So anyone can please provide me these files for my cell phone cuz I can't find they and don't know what I have to do to get them :S
Click to expand...
Click to collapse
Just flash the unpacked md5. file you use with pc Odin to flash with Mobile Odin Pro and enable Everroot and the other 2 options.
gee2012 said:
Just flash the unpacked md5. file you use with pc Odin to flash with Mobile Odin Pro and enable Everroot and the other 2 options.
Click to expand...
Click to collapse
I did it but the phone get stuck at the boot. I already tried select the wipe data/cache option in Mobile Odin and nothing :/ I can only access the Download Mode and then flash the previous ROM.
I bought a note 3 which probably came with 4.4.2 D3 firmware (last 2 letters) with singtel carrier. I OTA updated to 4.4.2 NH1 which is the latest update for singtel version. I tried downgrading the kernel for towelroot cause it needed < jun 2014 so I tried flashing ND3 firmware which failed. Then my device never worked and is always in download mode or it asks for kies recovery which i tried but never worked. I tried flashing like 6 different stock tar's with odin but all fail at the system.img point. Not using any PIT file. I've still not tried flashing the NH1 which i'm currently downloading. Not if this will also fail and i'll be bricked forever. Please HELP! I've tried at least 3 -4 diffrent tars but not NH1 tar so far
Note 3 N9005 32gb LTE 4G SM-9005 (Signtel Singapore)
Also i did not enable usb debugging at all, will that cause a problem?
Ok I tried nh1 firmware as well, it still failed at system ext4 write failure
Solution: Do Not install odin firmwares using vm ware fusion virtual machine. Run bootcamp for mac users and flash via odin in windows native
iamyohann said:
I bought a note 3 which probably came with 4.4.2 D3 firmware (last 2 letters) with singtel carrier. I OTA updated to 4.4.2 NH1 which is the latest update for singtel version. I tried downgrading the kernel for towelroot cause it needed < jun 2014 so I tried flashing ND3 firmware which failed. Then my device never worked and is always in download mode or it asks for kies recovery which i tried but never worked. I tried flashing like 6 different stock tar's with odin but all fail at the system.img point. Not using any PIT file. I've still not tried flashing the NH1 which i'm currently downloading. Not if this will also fail and i'll be bricked forever. Please HELP! I've tried at least 3 -4 diffrent tars but not NH1 tar so far
Note 3 N9005 32gb LTE 4G SM-9005 (Signtel Singapore)
Also i did not enable usb debugging at all, will that cause a problem?
Ok I tried nh1 firmware as well, it still failed at system ext4 write failure
Click to expand...
Click to collapse
You should show us your Odin error as well...
Do you have reactivation lock enabled?
You should enable the usb debugging for odin flash dude , why not enabling it !!??
alii91 said:
You should enable the usb debugging for odin flash dude , why not enabling it !!??
Click to expand...
Click to collapse
Do you even know what you're talking about? You don't need to activate USB Debugging.
USB Debugging is only for in the firmware adb usage. If he's in Download mode, whatever you set in the firmware does not apply anymore. It has its own Download Mode connection.
Yes man I know whay i said and he is talking about firmware adb and I'm talking because I had this problem many times until activated it
alii91 said:
Yes man I know whay i said and he is talking about firmware adb and I'm talking because I had this problem many times until activated it
Click to expand...
Click to collapse
Odin has no relation with USB Debugging/ADB.
It will not make a difference whether it is activated or not.
Also please read the OP, he is stuck in Download Mode, you can't access the system.
Ok maybe you're right I'm sorry, in this case checking the Samsung usb drivers on the pc and install the latest version of it ( could ) be the problem.
Solved
Solved the problem. It was vm ware fusion. Do not try odin on vmware fusion, it has problems. Installed windows, odin ran with succes, now i have knox 0x0 and root
iamyohann said:
Solved the problem. It was vm ware fusion. Do not try odin on vmware fusion, it has problems. Installed windows, odin ran with succes, now i have knox 0x0 and root
Click to expand...
Click to collapse
Parallels works perfectly as well.
Sent from my leanKernel 3.10 powered stock 4.4.2 (NF9) SM-N900T
iamyohann said:
Solved the problem. It was vm ware fusion. Do not try odin on vmware fusion, it has problems. Installed windows, odin ran with succes, now i have knox 0x0 and root
Click to expand...
Click to collapse
toastido said:
Parallels works perfectly as well.
Sent from my leanKernel 3.10 powered stock 4.4.2 (NF9) SM-N900T
Click to expand...
Click to collapse
Regardless, no one should be using a virtual machine to do something that may damage your warranty....
Yes it may work, but it's not true Windows you are working under, you are relying on USB device rerouting and hoping it will work. That bridge shouldn't be trusted, even if it might work as shown above, they are not under XDA's standard supported procedures.
When I use Odin to flash back my original Samsung S4, I received a 'Failed' message. I need to flash back the original rom as I need to send my phone back to service station. The Odin version I'm using is 3.07
My present rom is rooted and have Philiz recovery installed.
Anyone can assist?
Thanks.
greeny2010 said:
When I use Odin to flash back my original Samsung S4, I received a 'Failed' message. I need to flash back the original rom as I need to send my phone back to service station. The Odin version I'm using is 3.07
My present rom is rooted and have Philiz recovery installed.
Anyone can assist?
Thanks.
Click to expand...
Click to collapse
Odin troubleshooting:*If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
Sent from my GT-I9505 using XDA Free mobile app
greeny2010 said:
When I use Odin to flash back my original Samsung S4, I received a 'Failed' message. I need to flash back the original rom as I need to send my phone back to service station. The Odin version I'm using is 3.07
My present rom is rooted and have Philiz recovery installed.
Anyone can assist?
Thanks.
Click to expand...
Click to collapse
Make sure you have kies 3 installed and drivers installed and koes not running in background when uaing Odin