heyy plz help me.
i can't update my s2 i-9100 from odin.
sometimes it gets stuck at setup connection and after 10 minutes it shows Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1).
i have changed ROM's also but still the same.
sometimes it gets to boot.bin then stucks for all eternity.
i don't know what to do.
please HELP me!
So I have an N8013, completely and totally stock updated with all the latest from KIES/OTA.
I just want to root it. I have searched and what I have found so far is rooting via Exynos Exploit (can't because of OTA patch) and ODIN.
But from what I understand ODIN is for rooting, CWM and flashable ROM's.
I don't want to flash any ROM's. I wan't to root, run titanium backup and triangle away.
So the quickest current method to root a stock device and leave everything else intact is....?
Temetka said:
So I have an N8013, completely and totally stock updated with all the latest from KIES/OTA.
I just want to root it. I have searched and what I have found so far is rooting via Exynos Exploit (can't because of OTA patch) and ODIN.
But from what I understand ODIN is for rooting, CWM and flashable ROM's.
I don't want to flash any ROM's. I wan't to root, run titanium backup and triangle away.
So the quickest current method to root a stock device and leave everything else intact is....?
Click to expand...
Click to collapse
As you can't run the exynos exploit you will need to use ODIN... You Aren't changing roms or kernels but obtaining root and installing a custom recovery.
If you don't want to have a custom recovery use chainfires cf-autoroot - http://forum.xda-developers.com/showthread.php?t=1957002
This will give root access but leave everything else stock. You will need to run triangle away to reset flash counter...
ultramag69 said:
As you can't run the exynos exploit you will need to use ODIN... You Aren't changing roms or kernels but obtaining root and installing a custom recovery.
If you don't want to have a custom recovery use chainfires cf-autoroot - http://forum.xda-developers.com/showthread.php?t=1957002
This will give root access but leave everything else stock. You will need to run triangle away to reset flash counter...
Click to expand...
Click to collapse
Lol, just came back ehre to say I found chainfire's method.
Now I have an issue. I followed all instructions to the letter.
I rebooted in download mode and did not select any options.
I then plugged in my USB cable, fired up ODIN, selected my .MD5 file (both ODIN and .MD5 file were downloaded from the links in the thread).
This is the ODIN output:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-p4notewifi-p4notewifiue-gtn8013.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-p4notewifi-p4notewifiue-gtn8013.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
So basically nothing happens. I installed SuperSU from the play store, but it won't run.
My current ROM is still stock, ver
JZO54K.B8013UEUCMD3
Android 4.1.2
Kernel 3.0.31-813049
Model: GT-N8013
In the past when I have rooted a Galaxy S, ODIN filled in #'s in part of the window. I have attached a SS.
I think I might be missing a step? But I have gone over the instructions line by line three times and I still get the same results. Any help would of course be greatly appreciated.
Thanks!
Temetka said:
Lol, just came back ehre to say I found chainfire's method.
Now I have an issue. I followed all instructions to the letter.
I rebooted in download mode and did not select any options.
I then plugged in my USB cable, fired up ODIN, selected my .MD5 file (both ODIN and .MD5 file were downloaded from the links in the thread).
This is the ODIN output:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-p4notewifi-p4notewifiue-gtn8013.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-p4notewifi-p4notewifiue-gtn8013.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
So basically nothing happens. I installed SuperSU from the play store, but it won't run.
My current ROM is still stock, ver
JZO54K.B8013UEUCMD3
Android 4.1.2
Kernel 3.0.31-813049
Model: GT-N8013
In the past when I have rooted a Galaxy S, ODIN filled in #'s in part of the window. I have attached a SS.
I think I might be missing a step? But I have gone over the instructions line by line three times and I still get the same results. Any help would of course be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
From what I'm looking at there it seems like the Note hasn't been detected. There should be a value in id:com box....
All it looks like it did was check the MD5 sum...
Have you connected the Note to the PC before? If not, you might require the USB drivers needed by installing KIES. Remember to exit KIES before you try flashing with ODIN though as it can cause problems...
ultramag69 said:
From what I'm looking at there it seems like the Note hasn't been detected. There should be a value in id:com box....
All it looks like it did was check the MD5 sum...
Have you connected the Note to the PC before? If not, you might require the USB drivers needed by installing KIES. Remember to exit KIES before you try flashing with ODIN though as it can cause problems...
Click to expand...
Click to collapse
framaroot
Did you forget to set your Note to 'Download Mode'?
Before connecting the Note to your PC, you have to set your Note to 'Download Mode'.
Turn off your Note, then press and hold Power and Volume-Down buttons, until you get a screen that says 'Press Volume Up'. You should be in download mode now. If you have Odin open on your PC, and when you connect your Note, you should see your Note being detected. I forgot, but the first box on ODIN turns Yellow. You can flash the .MD5 now.
Temetka said:
Lol, just came back ehre to say I found chainfire's method.
Now I have an issue. I followed all instructions to the letter.
I rebooted in download mode and did not select any options.
I then plugged in my USB cable, fired up ODIN, selected my .MD5 file (both ODIN and .MD5 file were downloaded from the links in the thread).
This is the ODIN output:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-p4notewifi-p4notewifiue-gtn8013.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-p4notewifi-p4notewifiue-gtn8013.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
So basically nothing happens. I installed SuperSU from the play store, but it won't run.
My current ROM is still stock, ver
JZO54K.B8013UEUCMD3
Android 4.1.2
Kernel 3.0.31-813049
Model: GT-N8013
In the past when I have rooted a Galaxy S, ODIN filled in #'s in part of the window. I have attached a SS.
I think I might be missing a step? But I have gone over the instructions line by line three times and I still get the same results. Any help would of course be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Man I feel like a fool, lunadomain is correct. You need to go to download mode before using ODIN...
Should've thought of that myself but because I've been doing this for years it's a step that's sort of automatic... Also shift work over 8 or 9 days straight doesn't help....
lunadomain said:
Before connecting the Note to your PC, you have to set your Note to 'Download Mode'.
Turn off your Note, then press and hold Power and Volume-Down buttons, until you get a screen that says 'Press Volume Up'. You should be in download mode now. If you have Odin open on your PC, and when you connect your Note, you should see your Note being detected. I forgot, but the first box on ODIN turns Yellow. You can flash the .MD5 now.
Click to expand...
Click to collapse
Yeah, I do that and I get this screen:
Android System Recovery (3e)
Volume up/down to move highlight;
power button to select
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CDC-code : XAR
Successfully applied multi-CSC.
After that I fire up ODIN, plug in the tablet and nothing.
I just synced it with KIES the other day, and backed up some files so I know the drivers are installed.
Ideas?
lunadomain said:
Before connecting the Note to your PC, you have to set your Note to 'Download Mode'.
Turn off your Note, then press and hold Power and Volume-Down buttons, until you get a screen that says 'Press Volume Up'. You should be in download mode now. If you have Odin open on your PC, and when you connect your Note, you should see your Note being detected. I forgot, but the first box on ODIN turns Yellow. You can flash the .MD5 now.
Click to expand...
Click to collapse
I am an idiot.
I was swapping the volume +/- buttons.
Grr.
Ok so it's rebooting.
Will check SU in a sec.
Next is nandroid backup, then some other ROM.
Probably CM10. Who knows.
So I am rooted and de-triangled.
Yay.
But I am sticking with stock. I have almost 50 notebooks in Snote and my research has revealed that Snote won't run on non-Touchwiz ROM's.
Since I can't add Touchwiz to CM10, I am sticking with it.
You don't have to use cm Roms you can always check out touchwood touchwiz based roms
Sent from my HTC One using xda premium
Help me please..
My note died yesterday, started hanging while i was listening to music.
Tried to reset my note but now its stuck on Samsung Galaxy note 10.1 logo.
I'm using Omega Rom http://forum.xda-developers.com/showthread.php?t=2131474 for about 2 months with no problem encoutered until this one.
Can't access Recovery mode (just shows black screen but when i press the screen the device vibrates) - using Philz advance recovery
I can only access Download Mode, custom binary download: Yes (2 counts) and current binary/system status: both Custom
I tried flashing stock rom but failed
<ID:0/040> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8000DXUCMB1_N8000OLBCMB1_795498_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/040> Odin v.3 engine (ID:40)..
<ID:0/040> File analysis..
<ID:0/040> SetupConnection..
<ID:0/040> Initialzation..
<ID:0/040> Get PIT for mapping..
<ID:0/040>
<ID:0/040> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried Flashing some n8000 note 10 pit files I've found searching on google but with no luck, saying that Re-partition operation failed.
Sorry if my english is bad, i am just desperate to fix my note T.T
F***** up partition information table .
You need a service centre repair but as you have no warranty it may be worth you trying to repair . See PIT info thread in development .
http://forum.xda-developers.com/showthread.php?t=2363703
I've tried the pit files for n8000 in the link you gave, still operation failed.
I guess i need to download stock ics rom in sammobile first as I only have stock jb available.
tnx btw
Did it Work?
So it's the same case for me too,
I was using Omega ROM. It was very good actually but one day it went to the boot screen and ceased there.
So I got the .pit files as mentioned above.
As you flashed 4.0.4 with the above pit file, did it work?
help me
hi friends & master
please help me
excuse me for question
I did not know what questions to ask
Is there any way to transfer games and apps to the internal storage with app2sd (moving apps & games in from system Rom to SD card(internal) no memory card)?
my system rom There is almost full
1.44 GB (148 MB free)
internal 12.6 GB (5.8 GB free)
SD card 12.5 GB (5.6 GB free)
I do not need to memory card
hi again
why long press and holding any app in menu not move in to info or recycle bin(for deleted) ?
this for all or me?
Unfortunately, flashing ICS stock or JB stock roms + pit file didnt work.
Tried different Odin versions to no luck.
Guess I need to send my note to samsung service center
So it's the same case for me too,
Hello,
Have just got a used Note 4 unrooted with 5.0.1 firmware. Trying to root it using (CF-Auto-Root-trlte-trltexx-smn910f). Can't get Odin to flash it on the phone.
It seems like the phone somehow blocks everything from flashing. This is what I get after each attempt:
On the phone
UDC Start
SECURE CHECK: FAIL
In Odin
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
The same happens with any md5 i am trying to flash (TWRP/Philz). Went through all available forums and could not find any solution.
Re-activation lock disabled as never signed in to Samsung.
Has anyone got any ideas on this please
I upgraded my sm-n915t T-Mobile Note Edge to Marshmallow 6.0.1 (N915TUVU2DPE3) a few days ago and a few things don't work on the newer firmware. I would like to go back to the Kit-Kat firmware 4.4.4 (N915TUVU1ANK3), but everything I have tried doesn't work to go back to 4.4.4.
First I tried wiping everything except the external sd card through TWRP and restroing a 4.4.4 nandroid backup, but this causes a bootloop.
Then I tried downloading N915TUVU1ANK3, going into download mode and flashing through odin but this always fails, giving the error
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I read about flashing the bootloader first so I put the aboot.mbn, MPM-HLOS.bin, rpm.mbn, sbl1.mbn, sdi.mbn, and tz.mbn files from the 4.4.4 firmware in a .tar file and tried to flash it using odin 3.09. This also failed.
Did the 6.0.1 firmware upgrade or lock the bootloader so I can't return to 4.4.4? And if it did, is there a way to downgrade the bootloader?
Or am I doing something wrong?
Thank you for your help!
See here on how to do it!