This thread and these instruction's are no longer needed.Thanks to geohot and towelroot.com. We now can directly root kitkat. Big thanks to @jkeuclid & @Devo7v for the find and testing.
This thread will be left for legacy purposes
READ THE WHOLE OP
I have personally used and applied KK via all method's on this OP multiple times,so have several others.Make sure you are following instruction's 100%.
I HAVE PROVIDED YOU WITH COMPLETE AND EASY TO UNDERSTAND INSTRUCTION'S. Post request's for help that are answered here may be ignored. Technical ?'s are always answered.
IF YOU ARE NOT ON COMPLETELY STOCK J.B 4.3. STOP AND GO HERE----> http://forum.xda-developers.com/showthread.php?t=2629093
This is the lastest I537 OTA (received starting on 6/6/14) reworked to install as a zip in recovery. This OTA is the re-issue by AT&T. It includes several fixes the first attempt at KK upgrade broke. Its been meticulously examined and altered, to make sure all patch checks get completed before patching actually occurs. This helps to ensure everything goes as it should.
This upgrades to full kitkat with all the apps fully working,WITH INIT.D AND WRITE TO EXTERNAL SD CAPABILITY.
Needed item's
1.Pawned Kitkat OTA/ZIP provided below.
2.Stock KK 4.4 kernel provided below.
3.System image from 4.3 link ---> http://forum.xda-developers.com/showthread.php?t=2722073
4.Pawned 4.3 kernel link ---> http://forum.xda-developers.com/showthread.php?t=2722073
5.Stock 4.3 kernel link ---> http://forum.xda-developers.com/showthread.php?t=2722073
6.SuperSU zip link ---> http://forum.xda-developers.com/showthread.php?t=1538053
How to go from? to stock rooted KITKAT
1.Put device in download mode
2.In odin load 4.3 files,load them in this order
CSC_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_ CERT.tar
CP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_C ERT.tar
AP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_C ERT.tar
3.When device reboots go back to download mode and flash pawned 4.3 boot.tar
4.Once rebooted root via method of your choice and install safestrap.
5.Add pawned KK zip to sd flash in recovery(do not wipe dalvik/cache)
6.Install SU zip
7.After zip's install reboot to download mode,flash 4.4 boot tar.
8.Reboot and profit.
Quick and dirty odin file locations
AP=PDA
CP=PHONE
CSC=CSC
BOOT.TAR=PDA
STEPS to ensure full kitkat upgrade experience.
1.Odin of all the 4.3 files except for BL are required, this message must be received in Odin text window exactly as shown below,without receiving the same results I cannot guarantee 100% FULL FUNCTION upgrade.
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
CSC_ATT_I537ATTBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
CP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
AP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Removed!!
Added!!
Removed!!
Added!!
Odin v.3 engine (ID:5)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
recovery.img
persdata.img.ext4
system.img.ext4
modem.bin
Transmission Complete..
Now Writing.. Please wait about 2 minutes
Receive Response from boot-loader
NON-HLOS.bin
Transmission Complete..
Now Writing.. Please wait about 2 minutes
Receive Response from boot-loader
cache.img.ext4
RQT_CLOSE !!
RES OK !!
Removed!!
Remain Port .... 0
All threads completed. (succeed 1 / failed 0)
Removed!!
Added!!
NOTICE THE ORDER IN WHICH ODIN INSTALLED THEM. THIS IS EXACTLY THE ORDER YOU LOAD THEM IN.
2.Do not setup phone,you can initially setup wifi,do not update any apps.
3.Whatever you do.DO NOT ADD ANYTHING ELSE TO SYSTEM BUT SU AND BUSYBOX PERIOD (free busybox installer below.)
4.Profit from your labor.
Ota:Move to cache/fota using root explorer before removing root. Or rename to update.zip and flash in stock recovery. Remove all traces of root/recovery or ota WILL fail.
Alternative method1/ adb push cfg /cache/fota/2400258.cfg
Alternative method 2.
adb shell mount /sdcard
adb shell rm /sdcard/update.zip Remove all traces of root/recovery or ota WILL fail.
adb push *filename* /sdcard/update.zip
Don't know how to use adb go here--->>> http://forum.xda-developers.com/showthread.php?t=517874
Ota: cfg file only Remove all traces of root/recovery or ota WILL fail.
http://d-h.st/Vlf
MD5 Sum: 81ec5340a739409fc1f0d9d261103888
Download:Main/Pawned Ota flashable zip. If you did not follow instruction's 100% this zip MIGHT fail.
http://d-h.st/bmI
MD5 Sum: 7bd31c668ec5c30be226632adc49f906
Alternative KK Pawned zip...Use only if you cannot get main zip to install.This zip will install no matter what
Download------->>> http://d-h.st/wpk
MD5 Sum: ad0e77c504f093b4d8474d79db296016
Use this boot.tar after kitkat zip install(YOU MUST USE THIS BOOT.TAR AFTER ZIP INSTALL)--->>>> http://d-h.st/M6j
Please ensure your download MB's and MD5 matches.Photos below show hub and keyboard working with su installed.
Binaries for sysro/sysrw/zipalign/fstrim/zip/logs/etc
Binaries flashable--flash in recovery-->>> http://d-h.st/qfd
I'll download it now, I'm on factory installed 4.3, no root.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
---------- Post added at 10:01 AM ---------- Previous post was at 09:09 AM ----------
Got it...what's the file name?
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
I don't know what the Ota name actually is. I'll try to find out quickly .
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Proper name is i537ucucnn3, but I'm blowing up my phone looking for it.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Look in data/fota for a cfg file
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Or in cache look for a large zip. Might have to adb pull the Ota once located.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Think this is it.
Then again...maybe not. Think it's the handler for unpacking and installing.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
No i think it should be something around 485mb. I'm at work and my govt pc is monitored. Otherwise I would be hunting it also. Might need something with root to use ota catcher from playstore.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Trying to do this with phone only ..no computer available.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Thanks for all the effort. This is my first samsung. I've been with HTC from the start. If no one gets it before 7pm est. I'll work on it. That way we all can have working kitkat. The Ota runs perfectly as of now. Problem is device manager updated without my knowledge. I woke up on new kitkat software. Which is weird because you need to approve ota install.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
File is in cache directory. Needs to be adb pulled via pc.
Adb pull/cache/fota/ ota name
Sent from my SAMSUNG-SGH-I537 using Tapatalk
The happened to me with the last 4.4 update...pushed it thru without my knowledge, then the screen issues. It'll probably install itself, with it on my phone now...lol.
Edit....It also downloaded itself thru data, not wifi.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
No worries. Once I get it and decrypt it. I'll have ready to flash.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Yeah, without root, no access to cache.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Heres the update zip I pulled from my phone.
http://d01.megashares.com/dl/iR5lWVi/2400258.zip
Ota re-release
Just downloaded the re-released OTA Kit Kat from AT&T minutes ago.
Copied the .cfg file to my SD card with Root Browser before attempted to install.
Update failed, it failed last KitKat OTA too.
I just finished making pawned ota and have the cfg already. I will be providing complete instructions on both very soon.
I have the ota update for kit Kat now but don't wanna take it cause I don't wanna lose root. Since this update is different then the other one from April do I need to wait till someone figures out how to root or can I follow instructions from sunderwear post on how to root kit Kat.Thanks
KITKAT problems are over. Enjoy the new ota and zip. Please follow instructions closely. Pictures are provided for proof of full functions.
Related
Well, I'm a complete noob, though I have a rooted ICS, I never tried to flash a ROM 'till now, but I really wanted to see JellyBean running on my phone.
What I did:
> Saw this thread http://forum.xda-developers.com/showthread.php?t=1953847
> Downloaded the ROM
> I read the first step as "make sure you are on a (rooted ICS-ROM) or (JB-ROM with CWM recovery and brickfree kernel installed)" and not "make sure you are on a [(rooted ICS-ROM) or (JB-ROM with CWM recovery)] and brickfree kernel installed"
> Since I had a "rooted ICS-ROM" I continued to next step, copied he ROM, booted in recovery and did a FullWipe. Obviously, I didn't see the brickbug warnings which even a 5 year old with one eye :cyclops: would have seen.
> So, just to be safe I flashed abyssKernel 4.2 from ODIN via Download Mode (Volume Down + power + home)
> Now I have the yellow triangle and raised flash counter
> Finally I tried to flash Stock ICS ROM from Dr Ketan's guide http://forum.xda-developers.com/showthread.php?t=1424997
Now this is what I see in the Odin3 v1.85 message box:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DDLR9_N7000ODDLR3_N7000DDLR1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
Help plz :| :crying:
clear this step
> Since I had a "rooted ICS-ROM" I continued to next step, copied he ROM, booted in recovery and did a FullWipe
you had just rooted ICS or root + safe kernel, I mean which kernel was there at the time you wiped.
another thing you didn't mentioned have you flash that ROM you have copied to SD or not
Your log still can't confirm brick, keep patience and reply to queries above
as well confirm your device was in download mode while flashing ROM with Odin as well ID com port was added in Odin (I can't see in log).
dr.ketan said:
clear this step
> Since I had a "rooted ICS-ROM" I continued to next step, copied he ROM, booted in recovery and did a FullWipe
you had just rooted ICS or root + safe kernel, I mean which kernel was there at the time you wiped.
another thing you didn't mentioned have you flash that ROM you have copied to SD or not
Your log still can't confirm brick, keep patience and reply to queries above
as well confirm your device was in download mode while flashing ROM with Odin as well ID com port was added in Odin (I can't see in log).
Click to expand...
Click to collapse
Actually, I'm not sure which kernel I had, I think I had either the default kernel or the AbyssKernel (I never used any other kernels)
I didn't flash the copied ROM
And yes, the device was in download mode while flashing stock ICS and ID:COM in odin turned yellow.
Do you remember how you had root ICS?
Anyway issue is not seems that, your device was not added
repeat procedure
Confirm you have installed Kies/Adb driver
Put device in download mode
connect device
ID com should turn yellow
select PDA for ROM file
Hit 'start' to flash
dr.ketan said:
Do you remember how you had root ICS?
Click to expand...
Click to collapse
I followed rootgalaxynote's guide for ICS
http () ://rootgalaxynote. () com/galaxy-note-root/how-to-root-ics-on-galaxy-note-gt-n7000-no-computer-required/
(Sorry I cant post links as I am a new user, so remove the brackets)
Anyway follow as said in my previous post
And yes, you were on which ROM ?(answer this before reflashing, if you were on DDLR9 just flashing kernel will be enough)
dr.ketan said:
Anyway follow as said in my previous post
And yes, you were on which ROM ?(answer this before reflashing, if you were on DDLR9 just flashing kernel will be enough)
Click to expand...
Click to collapse
Yes, I was in DDLR9
Also, I can't even get into download mode now, it says "Low battery! cant download!".
And it is plugged in to the computer for almost two hours now
switch off device and plugin to charger it may get charged. if you get into download mode do this
Ok then download this
http://www.mediafire.com/?b7yee04jkcf60g6
and flash with PC Odin (your counter already raise so nothing to worry about it)
you have to select this file for PDA tab, rest of instruction as few post above said
Otherwise manage for charged battery
dr.ketan said:
switch off device and plugin to charger it may get charged. if you get into download mode do this
Ok then download this
http://www.mediafire.com/?b7yee04jkcf60g6
and flash with PC Odin (your counter already raise so nothing to worry about it)
you have to select this file for PDA tab, rest of instruction as few post above said
Otherwise manage for charged battery
Click to expand...
Click to collapse
Currently its not going into download mode, willl try to get a charged battery and post the results as soon as I can. Thanks in advance.
Also, I get this
'charging_q1.jpg' draw failed
message.
No problem just try download mode working or can you start recovery mode
Sent from my GT-N7100 using xda premium
dr.ketan said:
No problem just try download mode working or can you start recovery mode
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Your a saint ,Dr...!
Sent from my GT-N7000 using Tapatalk 2
howard bamber said:
Your a saint ,Dr...!
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
+1. DR. K, you are always there helping when some one in lost. I remember you said that you no longer own a G.NOTE, but instead a G.NOTE2, but you are so willing to help those whoever facing problem. You are a SAINT. big applause. thank you so much
Sent from my GT-N7000 using Tapatalk 2
I succesfully flashed PhilZ and then tried to flash the stock ICS ROM but it failed.
The Odin message box showed the following:
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DDLR9_N7000ODDLR3_N7000DDLR1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> zImage
<ID:0/013> NAND Write Start!!
<ID:0/013> modem.bin
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/013> Removed!!
May be remove the battery for a few seconds, reinsert and go download mode again and fladh
nokiamodeln91 said:
May be remove the battery for a few seconds, reinsert and go download mode again and fladh
Click to expand...
Click to collapse
Tried, no result, still says low battery cant download :/
I think I should go to the service center then.
either charge the battery on a diff note or try a full charged battery
Samsung service centre had to replace my motherboard. Now it's alright.
I've been reading posts on this forum for about 2-3 hours now and I still have some questions.
I have a galaxy s advance with android version 2.3.6 and baseband version XXLK2
i48.tinypic.com/2rz78sm.png
I was planning on rooting my phone and then maybe installing a custom ROM on it.
But I couldn't find a rooted firmware for my region (BELGIUM). And I also couldn't find the stock firmware for my region.
Neither on sammobile.com and neither on samsung-updates.com
My first question is: can I use rooted firmware that's for another region or will this cause problems for me?
My second question is: can I use rooted firmware with another baseband version than XXLK2?
Third question: if the answer on the first two questions is no, how am i supposed to root my phone then?
fourth and for now the last question: what is twrp recovery, and what is it used for, do I need it to root my phone or flash roms?
Thanks in advance!
ahmett75 said:
I've been reading posts on this forum for about 2-3 hours now and I still have some questions.
I have a galaxy s advance with android version 2.3.6 and baseband version XXLK2
i48.tinypic.com/2rz78sm.png
I was planning on rooting my phone and then maybe installing a custom ROM on it.
But I couldn't find a rooted firmware for my region (BELGIUM). And I also couldn't find the stock firmware for my region.
Neither on sammobile.com and neither on samsung-updates.com
My first question is: can I use rooted firmware that's for another region or will this cause problems for me?
My second question is: can I use rooted firmware with another baseband version than XXLK2?
Third question: if the answer on the first two questions is no, how am i supposed to root my phone then?
fourth and for now the last question: what is twrp recovery, and what is it used for, do I need it to root my phone or flash roms?
Thanks in advance!
Click to expand...
Click to collapse
do you want to stay with gingerbread, or upgrade to jellybean?
because rooting and flashing is much tougher in gb than in JB! tell me that i can help you.
Hi,
I got the same phone / baseband version in Austria. Downloaded XXLK2 firmware from sammobile.com, used simg2img to extract system.img, add su binary (=rooted), made a new system.img with make_ext4fs and flashed with heimdall. Meanwhile I used the same procedure to root and flash the jelly bean firmware XXLPY released for the russian market. Therefore I guess you can also flash a different version of gingerbread.
tom
Brainiac.shri said:
do you want to stay with gingerbread, or upgrade to jellybean?
because rooting and flashing is much tougher in gb than in JB! tell me that i can help you.
Click to expand...
Click to collapse
First i want to root my phone and then i want to install custom roms.
Sent from my GT-I9070 using xda app-developers app
RealBorg said:
Hi,
I got the same phone / baseband version in Austria. Downloaded XXLK2 firmware from sammobile.com, used simg2img to extract system.img, add su binary (=rooted), made a new system.img with make_ext4fs and flashed with heimdall. Meanwhile I used the same procedure to root and flash the jelly bean firmware XXLPY released for the russian market. Therefore I guess you can also flash a different version of gingerbread.
tom
Click to expand...
Click to collapse
But i'm from belgium and i couldnt find one for belgium. So you live in austria and downloaded the firmware for austria?
Sent from my GT-I9070 using xda app-developers app
ahmett75 said:
First i want to root my phone and then i want to install custom roms.
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
if u upgrade to JB, root is a one step, 5 min process after which it takes a few more minutes to start flashing roms after flashing a new kernel with Clockworkmod. if u wanna start with jellybean, go here.http://forum.xda-developers.com/showthread.php?t=2094318(make sure u install the stock samsung rom first , then root then install recovery, then flash a custom rom) this WILL NOT void ur warranty
on the other hand rooting gingerbread is incredibly complex. if u wanna do that go to this thread http://forum.xda-developers.com/showthread.php?t=1985199
its totally safe to flash anither country firmware using odin.then root the supported firmware. also this will void your warranty,
then to install a new kernel with TWRP recovery , go here : http://forum.xda-developers.com/showthread.php?t=1873119
then finally choose the custom rom u want Jetmod or supressed and flash using TWRP(assuming you know how to atleast nter download and recovery mode!)
do all this in the same order.
Brainiac.shri said:
if u upgrade to JB, root is a one step, 5 min process after which it takes a few more minutes to start flashing roms after flashing a new kernel with Clockworkmod. if u wanna start with jellybean, go here.http://forum.xda-developers.com/showthread.php?t=2094318(make sure u install the stock samsung rom first , then root then install recovery, then flash a custom rom) this WILL NOT void ur warranty
on the other hand rooting gingerbread is incredibly complex. if u wanna do that go to this thread http://forum.xda-developers.com/showthread.php?t=1985199
its totally safe to flash anither country firmware using odin.then root the supported firmware. also this will void your warranty,
then to install a new kernel with TWRP recovery , go here : http://forum.xda-developers.com/showthread.php?t=1873119
then finally choose the custom rom u want Jetmod or supressed and flash using TWRP(assuming you know how to atleast nter download and recovery mode!)
do all this in the same order.
Click to expand...
Click to collapse
So what i'm going to do is:
1. download JB and install it
2. Root
3. then install twrp recovery
4. Flash a kernel with clockworkmod (which kernel do you suggest?)
5. Flash custom roms
Is this the correct order or am i wrong?
ahmett75 said:
So what i'm going to do is:
1. download JB and install it
2. Root
3. then install twrp recovery
4. Flash a kernel with clockworkmod (which kernel do you suggest?)
5. Flash custom roms
Is this the correct order or am i wrong?
Click to expand...
Click to collapse
You can't install any recovery by itself. It comes with kernel. Only kernel with permanent recovery - CWM is ThunderZap now.
1. Download JB, flash it with Odin. - go again to recovery - do factory reset.
2. Root with root.zip from stock recovery
3. Install kernel with CWM (ThunderZap) with dd command in terminal editor
4. Flash custom ROM from CWM recovery.
shut_down said:
You can't install any recovery by itself. It comes with kernel. Only kernel with permanent recovery - CWM is ThunderZap now.
1. Download JB, flash it with Odin. - go again to recovery - do factory reset.
2. Root with root.zip from stock recovery
3. Install kernel with CWM (ThunderZap) with dd command in terminal editor
4. Flash custom ROM from CWM recovery.
Click to expand...
Click to collapse
i'm going to give it a try, waiting for the download to finish
UPDATE: went in to recovery mode, plugged the usb and started the flash got this message:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Одг: [Q] questions about rooting, flashing, ...
ahmett75 said:
UPDATE: went in to recovery mode, plugged the usb and started the flash got this message:
Added!!
Odin v.3 engine (ID:3)..
File analysis..
SetupConnection..
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Not recovry, in download mode. Did you unpack file. It should be around 700MB, not 400.
In recovery after flsshing, to do factory reset.
Sent from Galaxy S Advance
exchange exprsee
shut_down said:
Not recovry, in download mode. Did you unpack file. It should be around 700MB, not 400.
In recovery after flsshing, to do factory reset.
Sent from Galaxy S Advance
Click to expand...
Click to collapse
ok, so now i've runned odin as admin, loaded the firmware and i get this.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_I9070XXLPY_I9070SERLPY_660490_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
then i go into download mode and connect my phone and i get this.
<ID:0/003> Added!!
i've read that something has to turn yellow, or isn't that necessary?
EDIT: i just pressed start and it is installing i think
Одг: [Q] questions about rooting, flashing, ...
ahmett75 said:
ok, so now i've runned odin as admin, loaded the firmware and i get this.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_I9070XXLPY_I9070SERLPY_660490_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
then i go into download mode and connect my phone and i get this.
<ID:0/003> Added!!
i've read that something has to turn yellow, or isn't that necessary?
EDIT: i just pressed start and it is installing i think
Click to expand...
Click to collapse
Search google "samsung download mode" and you should see image of it. When you power your phone with vol.down+home+power you get question do you want to continue. You press volume up to confirm. And after that with your phone connected and file in PDA hit start.
Sent from Galaxy S Advance
ahmett75 said:
UPDATE: went in to recovery mode, plugged the usb and started the flash got this message:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I have a similar issue. In Odin/Download mode I tried flashing Jelly Bean. Here is what I get from Odin:
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_I9070XXLPY_I9070SERLPY_660490_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> power_management.bin.md5
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In red on the screen is "CUSTOM PWR MGT BINARY !!"
Did a factory reset. Same issue. Turned on Settings -> Applications -> Development -> USB Debugging + Allow mock locations. Same issue.
Any ideas?
JBAdvXDA said:
I have a similar issue. In Odin/Download mode I tried flashing Jelly Bean. Here is what I get from Odin:
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_I9070XXLPY_I9070SERLPY_660490_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> power_management.bin.md5
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In red on the screen is "CUSTOM PWR MGT BINARY !!"
Did a factory reset. Same issue. Turned on Settings -> Applications -> Development -> USB Debugging + Allow mock locations. Same issue.
Any ideas?
Click to expand...
Click to collapse
How much time does this take? Maybe try to redownload firmware file.
shut_down said:
How much time does this take? Maybe try to redownload firmware file.
Click to expand...
Click to collapse
Maybe 10seconds.
I downloaded Odin3.07 (Was using Odin3v1.7). From: http://forum.xda-developers.com/showthread.php?t=2086965
It is still showing in red "CUSTOM *** BINARY !!!!" but is now progressing to other components.
Will report back.
JBAdvXDA said:
Maybe 10seconds.
I downloaded Odin3.07 (Was using Odin3v1.7). From: http://forum.xda-developers.com/showthread.php?t=2086965
It is still showing in red "CUSTOM *** BINARY !!!!" but is now progressing to other components.
Will report back.
Click to expand...
Click to collapse
It should last couple minutes. Something is wrong at start. I am not saying redownload Odin, whole firmware file. But you did unpack it from zip, it should be noticable that it is corrupted when you did that on pc.
shut_down said:
It should last couple minutes. Something is wrong at start. I am not saying redownload Odin, whole firmware file. But you did unpack it from zip, it should be noticable that it is corrupted when you did that on pc.
Click to expand...
Click to collapse
Thanks.
Used Odin3v3.07 to install JB and it boots! Now the baseband version is "Unknown" and I have no service.
JBAdvXDA said:
Thanks.
Used Odin3v3.07 to install JB and it boots! Now the baseband version is "Unknown" and I have no service.
Click to expand...
Click to collapse
Try wiping cache reset in stock recovery and problem solve
I've succesfully upgraded to JB, rooted and flashed kernel.
Any suggestions about ROMS for i9070 ?
Hello all, new member here.
Ok. First of all, I'm on stock ICS, rooted using framaroot http://forum.xda-developers.com/showthread.php?t=2130276
Installed busybox and installed the applet using smart install.
Now I want sell the phone and I want my phone go back to "completely new unit".
In busybox it has option to uninstall the applets.. Warning popup came out like WHOA! bla3x... I don't have gut to continue so cancelled it..
In framaroot it has unroot option - this worked for me to unroot
My question is:-
should I uninstall the busybox applet?
Do I have to flash ICS stock rom using odin?
Anyone have same problem like mine? What u did?
please help
Just flash a stock GB (safer for next user) rom, it will remove all trace of root and busybox.
Sent from my GT-N7000 using xda premium
are89 said:
Hello all, new member here.
Ok. First of all, I'm on stock ICS, rooted using framaroot http://forum.xda-developers.com/showthread.php?t=2130276
Installed busybox and installed the applet using smart install.
Now I want sell the phone and I want my phone go back to "completely new unit".
In busybox it has option to uninstall the applets.. Warning popup came out like WHOA! bla3x... I don't have gut to continue so cancelled it..
In framaroot it has unroot option - this worked for me to unroot
My question is:-
should I uninstall the busybox applet?
Do I have to flash ICS stock rom using odin?
Anyone have same problem like mine? What u did?
please help
Click to expand...
Click to collapse
you have two options, flash a stock rom as said previously, or you can unroot your current rom.
Do it by acessing the root app, going into the options page, and click "full unroot" option. It will clean up every trace of rooting
projeto56 said:
you have two options, flash a stock rom as said previously, or you can unroot your current rom.
Do it by acessing the root app, going into the options page, and click "full unroot" option. It will clean up every trace of rooting
Click to expand...
Click to collapse
Flashing a stock rom with odine is the best way to full stock.
Sent from my GT-N7000
devll said:
Flashing a stock rom with odine is the best way to full stock.
Sent from my GT-N7000
Click to expand...
Click to collapse
But it isn't the simplest nor the safest
Sent from my GT-N7000 using Tapatalk 4 Beta
projeto56 said:
But it isn't the simplest nor the safest
Sent from my GT-N7000 using Tapatalk 4 Beta
Click to expand...
Click to collapse
He's gotta flash a new rom anyway as he's giving the phone on so may as well just flash.
Sent from my GT-N7000 using xda premium
Thanks to all who replied..
So, after unroot, can I reinstall the firmware via kies too?
By far easiest way would be what is above said but using Mobile Odin with full wipes
It's always so much harder when you have to try (David Gray).
AndroidSlave said:
By far easiest way would be what is above said but using Mobile Odin with full wipes
It's always so much harder when you have to try (David Gray).
Click to expand...
Click to collapse
I connected to kies and there is firmware update popup shows that JB is available..
Since my phone is rooted ICS stock rom, can I upgrade to JB?? or I have to unroot first.
are89 said:
I connected to kies and there is firmware update popup shows that JB is available..
Since my phone is rooted ICS stock rom, can I upgrade to JB?? or I have to unroot first.
Click to expand...
Click to collapse
You can try but it likely won't work
AndroidSlave said:
You can try but it likely won't work
Click to expand...
Click to collapse
Well.. I think I shouldn't, I dont want any trouble.. Thanks though for your help. I use this thread coz I cant even reply at this http://forum.xda-developers.com/showthread.php?t=2130276
Because new member not allowed to..
are89 said:
Well.. I think I shouldn't, I dont want any trouble.. Thanks though for your help. I use this thread coz I cant even reply at this http://forum.xda-developers.com/showthread.php?t=2130276
Because new member not allowed to..
Click to expand...
Click to collapse
That's not compatible with this device.
You should use mobile odin pro and move on. Or PC Odin if u don't want to use mobile
You shouldn't have used framaroot on this device u should have used philz
Be careful read the brickbug thread
Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta
AndroidSlave said:
That's not compatible with this device.
You should use mobile odin pro and move on. Or PC Odin if u don't want to use mobile
You shouldn't have used framaroot on this device u should have used philz
Be careful read the brickbug thread
Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta
Click to expand...
Click to collapse
Ok. What if I unroot the phone and use odin to flash ICS stock rom back? is it bad?
if it success should I wipe cache or hard reset my phone before upgrade to JB?
are89 said:
Ok. What if I unroot the phone and use odin to flash ICS stock rom back? is it bad?
if it success should I wipe cache or hard reset my phone before upgrade to JB?
Click to expand...
Click to collapse
Just flash a stock GB ROM as earlier recommended with PC Odin
ICS has brick bug dangers
Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta
AndroidSlave said:
Just flash a stock GB ROM as earlier recommended with PC Odin
ICS has brick bug dangers
Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta
Click to expand...
Click to collapse
Ok. Thanks for ur advise. I will flash to gb as earlier.. Have to download it first would take a day.. I will update here soon..
Many thanks Androidslave..
AndroidSlave said:
Just flash a stock GB ROM as earlier recommended with PC Odin
ICS has brick bug dangers
Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta
Click to expand...
Click to collapse
I tried twice to flash with GB N7000DXKK1_N7000OLBKJ6_XME download from http://forum.xda-developers.com/showthread.php?t=1424997
or I have downloaded wrong GB stock rom.. I'm from malaysia
I got this from odin pc:-
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DXKK1_N7000OLBKJ6_N7000DXKJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.bin
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
my current version is
PDA N7000DXLR5
PHONE N7000DXLR1
CSC N7000OLBLR2
edit:
Is the usb debugging should be checked or unchecked??
edit
Tried usb checked and unchecked, still same error message in odin..
are89 said:
I tried twice to flash with GB N7000DXKK1_N7000OLBKJ6_XME download from http://forum.xda-developers.com/showthread.php?t=1424997
or I have downloaded wrong GB stock rom.. I'm from malaysia
I got this from odin pc:-
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DXKK1_N7000OLBKJ6_N7000DXKJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.bin
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
my current version is
PDA N7000DXLR5
PHONE N7000DXLR1
CSC N7000OLBLR2
edit:
Is the usb debugging should be checked or unchecked??
edit
Tried usb checked and unchecked, still same error message in odin..
Click to expand...
Click to collapse
It doesn't matter if debugging is checked or not. The flashing procedure should be done in download mode, not on booted state.
Try to use another usb port on your PC.
Sent from my GT-N7000 using Tapatalk 4 Beta
projeto56 said:
It doesn't matter if debugging is checked or not. The flashing procedure should be done in download mode, not on booted state.
Try to use another usb port on your PC.
Sent from my GT-N7000 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I gonna put this action on hold coz I installed philz CWM, I will try to flash stock rom using mobile odin sooner.. I want to study first about mobile odin, rom manager etc to make me more understand.. Thanks for ur support.
Can do with SuperSU/Superuser full unroot option!
Sent from my Lenovo S820_ROW using xda app-developers app
Don't use ROM manager. Use mobile Odin. Seriously why are you making this so difficult.
Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta
Currently using my first android device! Samsung galaxy note 3 for att and I decided to root it. I am currently running 4.3 but want to update to 4.4 in hopes of fixing some gps issues i've been having. I tried to use ODIN to load up the stock 4.3 firmware but have been encountering some errors. My phone no longer turns on, when it does it says "firmware upgrade encountered an issue" please select recovery mode in kies and try again. I have downloaded keys 3 and tried to recover it using that but no luck. Am willing to post screens or answer any questions you guys may have!.
Are you on 4.4.2 or 4.3? If you're on 4.3, have you tried the MJ5 restore posted in the general section?
reply
Face_Plant said:
Are you on 4.4.2 or 4.3? If you're on 4.3, have you tried the MJ5 restore posted in the general section?
Click to expand...
Click to collapse
Im on 4.3. I've only tried using Odin and kies which have both failed me. what im about to try is "androidrootz.com/2013/10/how-to-unrootunbrick-at-galaxy-note-3.html".. can you link to your suggestion?
I'm not sure how to copy/paste links with Tapatalk, but if you go to the general sub form for the AT&T Note 3 on this website it should be on the first page. Look for a thread titled "MJ5 restore and optionally provides root" or something along those lines. It's a somewhat long process that can be intimidating at first, but if you read the directions and follow them exactly you should be good to go.
replyy
Face_Plant said:
Are you on 4.4.2 or 4.3? If you're on 4.3, have you tried the MJ5 restore posted in the general section?
Click to expand...
Click to collapse
Face_Plant said:
I'm not sure how to copy/paste links with Tapatalk, but if you go to the general sub form for the AT&T Note 3 on this website it should be on the first page. Look for a thread titled "MJ5 restore and optionally provides root" or something along those lines. It's a somewhat long process that can be intimidating at first, but if you read the directions and follow them exactly you should be good to go.
Click to expand...
Click to collapse
:/
Was gonna try this "forum.xda-developers.com/showthread.php?t=2559715" was what you said. But alot of the links to the downloads were broken. and i didnt see any reposted :/
I thought only the mi9 firmware was available at kies?
dbartdog said:
:/
Was gonna try this "forum.xda-developers.com/showthread.php?t=2559715" was what you said. But alot of the links to the downloads were broken. and i didnt see any reposted :/
Click to expand...
Click to collapse
Just to show people what all im working with..
ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION: ENABLE
Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Edit:
What happens when i use ODIN3 v3.07 to load the original .tar file (AP_N900AUCUBMI1_1562818_REV03_user_low_ship_MULTI_CERT.tar.md5)
I connect my phone
Odin detects it fine.
Place it in the PDA, Press start.
Only things checked are Auto reboot and F. Reset time
Wait about 5 mins for it to work.
Fails at the end. With this msg.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N900AUCUBMI1_1562818_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
When trying to use Kies 3.
Start up kies with phone plugged in, in odin mode.
-the connected device is not supported by kies 3.
-confirm
so i go to tools>Firmware upgrade and initializ.
Enter model SM-N900A
Followed by S/N
Device can be initialaized to its original settings.
<ok>
Prepare for firmware upgrade
<start upgrade>
Downloads file for firmware emergence recovery of note 3 from server.
waits...
Failed to upgrade firmware due to an unexpected error.
In the restore to MJ5 thread the link to mega is no good(it was all the files in one dl, at one time)
Also I had to disable the antivirus on my computer for the sec_csc to download dont forget to turn it back on
frome901 said:
In the restore to MJ5 thread the link to mega is no good(it was all the files in one dl, at one time)
Also I had to disable the antivirus on my computer for the sec_csc to download dont forget to turn it back on
Click to expand...
Click to collapse
So I got my phone back up and working! WOOT.
But not im back to 4.3 android and am wanting to update to KitKat 4.4 I go to settings and go to software update but it says there is none available. what do?
dbartdog said:
So I got my phone back up and working! WOOT.
But not im back to 4.3 android and am wanting to update to KitKat 4.4 I go to settings and go to software update but it says there is none available. what do?
Click to expand...
Click to collapse
Do you really want to be stuck on KitKat 4.4 the offical is a locked up rom for now. try searching for the "NB4 update" thread? theres also a leaked 4.4 one click too
What ^ this guy said.
I have two rooted s4 actives on stock rooted 4.4.2. Had no problems until recently it's been every day I get a nagging message about an ota being available. I can't seem to disable the ota check or Knox on kit Kat. The ota is for my firmware, apparently I'm a version behind but the phones work fine so I really don't want to fix what isn't broken. Any way to block these messages and the forced reboots? The updates fail every time but it's really annoying.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
SebringTech said:
I have two rooted s4 actives on stock rooted 4.2.2. Had no problems until recently it's been every day I get a nagging message about an ota being available. I can't seem to disable the ota check or Knox on kit Kat. The ota is for my firmware, apparently I'm a version behind but the phones work fine so I really don't want to fix what isn't broken. Any way to block these messages and the forced reboots? The updates fail every time but it's really annoying.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Click to expand...
Click to collapse
I think you mean you're on 4.4.2, maybe the NC9 firmware? If you are you have 2 options:
Delete, freeze, or rename wssyncmldm.apk and wssyncmldm.odex to disable OTA updates
Update to NE3 using the ML2 firmware and the NE3 OTA. You can re-root afterwards with towelroot, but make sure you back stuff up with Titanium Backup because the process will completely wipe your phone.
Yeah 4.4.2 typo fail. I'll check again but last time with my root file Explorer I could only find the .odex file.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Devo7v said:
I think you mean you're on 4.4.2, maybe the NC9 firmware? If you are you have 2 options:
Delete, freeze, or rename wssyncmldm.apk and wssyncmldm.odex to disable OTA updates
Update to NE3 using the ML2 firmware and the NE3 OTA. You can re-root afterwards with towelroot, but make sure you back stuff up with Titanium Backup because the process will completely wipe your phone.
Click to expand...
Click to collapse
I admit I'm fairly new to this phone. I know how to flash the ML2 firmware via ODIN. Now once that is sent to the phone, I leave it stock, if I go to settings -> More -> About Device -> Click "Software Update" Will that download the NE3 OTA? Both my phones are currently on NC9 firmware, I have no issues but my wife has some odd problems with her phone. So if I have to go to stock unrooted and reroot that's fine I'll do what I have to - I just want to make sure I know what I need to do before I start.
When trying to flash ML2 files ODIN fails every time. Is it possible to go from NC9 to ML2? I've installed the drivers from Samsung, it detects the phone in ODIN but it can't write to it.
Readout from ODIN 3.04:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I537ATTBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Now when my phone boots I get "Fimrware upgrade encountered an issue. Please select Recovery Mode in Kies and try again" making it a paperweight...
Also tried on another desktop same results. At this point I'm a bit desperate as it's my only phone.
SebringTech said:
Also tried on another desktop same results. At this point I'm a bit desperate as it's my only phone.
Click to expand...
Click to collapse
Flash everything but the bootloader and you'll be fine. Since you're on 4.4.2, you can't downgrade the bootloader back to 4.3, that's why it's failing.
Devo7v said:
Flash everything but the bootloader and you'll be fine. Since you're on 4.4.2, you can't downgrade the bootloader back to 4.3, that's why it's failing.
Click to expand...
Click to collapse
Phone successfully restored to ML2. I'm now in the process of downloading the ML2 to NE3 OTA File. Hoping that the update goes smoothly. I thank you very much for pointing out my error!
SebringTech said:
Phone successfully restored to ML2. I'm now in the process of downloading the ML2 to NE3 OTA File. Hoping that the update goes smoothly....
Click to expand...
Click to collapse
if you don't mind posting, what was the hangup at your first attempt ? Too many files for Odin at first or something else ?
am trying to help out someone who appears to have the same problem as you did.
xdafly said:
if you don't mind posting, what was the hangup at your first attempt ? Too many files for Odin at first or something else ?
am trying to help out someone who appears to have the same problem as you did.
Click to expand...
Click to collapse
I think he said it was the bootloader.
Devo7v said:
Flash everything but the bootloader and you'll be fine. Since you're on 4.4.2, you can't downgrade the bootloader back to 4.3, that's why it's failing.
Click to expand...
Click to collapse
SebringTech said:
I thank you very much for pointing out my error!
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
xdafly said:
if you don't mind posting, what was the hangup at your first attempt ? Too many files for Odin at first or something else ?
am trying to help out someone who appears to have the same problem as you did.
Click to expand...
Click to collapse
It was the bootloader. When the phone is upgraded to 4.4.2 it's boot loader can't go down from that. So the bootloader from ML2 is incompatible. When I flashed the other three files it worked just fine! Then I applied the patch to get the phone to the latest firmware. It's a .cfg file you rename it to update.zip and put it on the sd card. boot into the stock recovery and install the update. I must admit a few glitches I was having are gone now since upgrading to the latest greatest, and Towelroot made it stupid easy to root.
Ok, good to know, will pass on the information, thank you.