Database Develop

[HELP] - upgrade gone wrong?

hi all,
i was on KL3, rooted, then KIES kept bothering me so i thought i'd upgrade to the new LA3 i think....
then the thing crashed and now all i get is the Firmware upgrade encounted an issue. PLease recovery mode in Kies and try again.
problem is, i cant get it to go into recovery mode?!??!?! (volume up, power?)
nothng works, KIes cant detect it, and cant upgrade anything, i am a total noob, and can only get into ODin mode..
HELP please?!?!?
what do i need to do, please step by step, what to download, what to press and whether i need to get a micro sd to install some firmware?
thankyou - urgent help needed!

First of all, relax
You said you can get into "Odin Mode"? I suppose that's download mode. Just go to this thread and everything is explained here. No need to worry
http://forum.xda-developers.com/showthread.php?t=1424997
Just flash another firmware (why not the latest) and everything will be just fine.
P.S. Once rooted, you should probably stay away from stock upgrades...
Press thanks if it helped

Recovery : vol up + home + power
If you get into recovery just wipe cache n wipe data
If error still there
Go to download :
vol dwn + home + power
Reflash new rom
Sent from my GT-N7000 using xda premium

this is all i get and gets stuck???
i chose this one: N7000XXLC1---------2.3.6-------2012 March----------N7000OXXLB3-----------France------------------------------------Download
went to bed for 2 hours and it didnt move...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLC1_N7000OXXLB3_N7000XXLB2_HOME.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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img

confirm you have close antivirus if running
Dont put ROM file too deep, better keep on Root folder e.g. C:/Folder/***.tar.md5
Dont use USB extension, attach USB cable direct to slot on PC, try using different slot (preferably back side PC)
N dont forget to put device in download mode.

Thankyou Dr.Ketan and eug3n91
worked after i switched to the onboard USB.
i guess thats probably why Kies failed too....
this site is fantastic, been a lurker for a while, but never needed to post until today and its proven to be very succesful with both of you helping out so quick.
cant thankyou enough!

Dr.Ketan I am facing the same problem and did exactly the same but this is all i get
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK3_N7000ODDKK1_N7000DDKJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Set PIT file..
<ID:0/015> DO NOT TURN OFF TARGET!!
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> boot.bin
<ID:0/015> cache.img
<ID:0/015> factoryfs.img

same problem here. flashed ROCKET ROM but now i can just go into download mode and CWM. ICS roms stuck on NAND WRITE START and GB roms on FACTORYFS.IMG
I tried everything ever mentioned i guess:
-Tried fix it with KIES but it doesn't even find my device
-use different USB port
-install USB drivers new
-flash Q1_20110914_16GB.pit
-flash other kernel "CF-Root-SGN_XX_OXA_LPY-v5.3-CWM5"
-flash "N7000_XXKL8" where i have to flash three files with odin v1.85
-took the battery out for a longer time
-Flashed different Stock Roms (wipa and without wipe)
-flashed the Abyss Kernel 4.2 again
-flashed "Criskelo's Rom" with CMW
-Tried on different PC with Windows XP
Please there must be a way to help me and khok3893

ow1166 said:
same problem here. flashed ROCKET ROM but now i can just go into download mode and CWM. ICS roms stuck on NAND WRITE START and GB roms on FACTORYFS.IMG
I tried everything ever mentioned i guess:
-Tried fix it with KIES but it doesn't even find my device
-use different USB port
-install USB drivers new
-flash Q1_20110914_16GB.pit
-flash other kernel "CF-Root-SGN_XX_OXA_LPY-v5.3-CWM5"
-flash "N7000_XXKL8" where i have to flash three files with odin v1.85
-took the battery out for a longer time
-Flashed different Stock Roms (wipa and without wipe)
-flashed the Abyss Kernel 4.2 again
-flashed "Criskelo's Rom" with CMW
-Tried on different PC with Windows XP
Please there must be a way to help me and khok3893
Click to expand...
Click to collapse
I'm afraid this has to do with corrupted memory partitions. It's what devs called 'superbricks' if I'm not mistaking...
You could try a ROM with a PIT file, hoping that would repartition any bad sectors.
Again, I could be mistaken. Try to read some other threads around here. A lot of.others have also encountered this problem

khok3893 said:
<ID:0/015> factoryfs.img
Click to expand...
Click to collapse
When you stuck at factoryfs.img = system partition corrupted

I tried with PIT file (Q1_20110914_16GB.pit) and ICS LYP Rom and it stucks on "NAND WRITE START" that comes after "factoryfs.img" I even uses "re-partition" in Odin. Nothing works.....

[Q] Galaxy Note Flashing Failed need help

Hi,
My Galaxy Note has failed when i tried to flash into 4.0.3, story was like this.
My Note has rooted long time ago and flashed with N7000DXLA1_N7000OLBKL2_XSP, and then I noticed a new 4.0.3 has officially came up on kies for upgrade, so I plug my phone into kies, however its said i can not upgrade with my current firmware. then I went to restore my phone back to my very 1st backup with my original firmware KK1. however still no luck, kies still said I can not upgrade with my current firmware. so at the end I decided to flash the rom with Moblie Odin Pro into N7000ZSLPF_N7000OZSLPF_TGY (Hong Kong). then It was finally upgraded into 4.0.3, however my data has all gone, so I then tried to restore my phone using CWM Manage back to my LA1. and then problem comes!!!
when I restore back to LA1, my Note went in to boot loop, and never wanted to boot up. so then I decided to flash it back to N7000ZSLPF_N7000OZSLPF_TGY (Hong Kong) with PC Odin, However it stays in the samsung logo and not going any further. then I tried to flash it with N7000ZSKK1, but even worst , it stucks at the <ID:0/006> data.img for a long time about 2 hours, and then finally said FAILED, I have copy the log below.
now I turn on my phone it said "firmware upgarde encountered an issue. please select recovery mode in kies & try again". I tried to connect my note with kies, but then kies connection file too.
Could anyone please help ??
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000ZSKK1_CL706440_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7000XXKJ6_REV_05_CL1070146.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OZSKK1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> zImage
<ID:0/006> factoryfs.img
<ID:0/006> data.img
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!

could you enter in CWM recovery?

Probably bricked. Send back to ssc to get it fixed if still have warranty else read this post and try fixing it yourself, http://forum.xda-developers.com/showthread.php?t=1667886
Sent from my GT-N7000 using Tapatalk 2

Your mistake was recovering through cwm. That recovers nearly the whole rom, and on ICS, can be dangerous. Not counting the fact you are rewriting a ics rom with gb.
Your device is bricked. Maybe not hardbricked.
Download pitfile for your phone from drketans thread, redo flash of your rom choice with pitfile selected. I recommend a GB rom as ICS factory reset or wipe from recovery is dangerous. This should enable safely repartition. Do not check this without pitfile selected. This should safely fix your brick. Do not select clear efs.
If it doesnt reboot, bootloop, at least you got gb. The rom you flashed is not wipe version and stuff is lingering that stops reboot. Go to recovery and perform factory reset. If no bootloop,
do a safe factory reset from dialer anyway. Code google it, it should have 3855 in it. Now root it and with mobile odin install cf kernel and in recovery, after safe reboot retore your cwm backup. Note, with ICS it is not recommended recovering data or apps. Should you want to backup and recover apps, non system ones you can with titanium backup. Data again not recommended.
All at own risk.
Sent from my GT-N7000 using Tapatalk 2

Hi Derekzxy,
Follow what Baz77 said.
I'm just curious what kernel were you using when you performed nandroid restore?
Hope you get your device working back soon.

DrKetans thread is the one in development section, then in stickies btw
Sent from my GT-N7000 using Tapatalk 2

riccardo_1958 said:
could you enter in CWM recovery?
Click to expand...
Click to collapse
Yes I can, however it only has these option and error message:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
test redbend fota[FS]
E: failed to mount / data (unknown error: 0)
-- copying media files..
-- updating application ..
E:filed to mount / data (unknown error: 0)
E: install_application_for_customer:Cant's mount /data
your storage not prepared yet. please use UI menu for format and reboot actions. copy application failed.
-- Appling Multi-CSC...
installing Multi-CSC
Copied the packages.
Copied the default_wallpaper file.
Coplied the power on / off animation files.
Can't access to '/system/csc/TGY/system/'.
Successfully applied multi-CSC.
Thats all i have got.

derekzxy said:
Yes I can, however it only has these option and error message:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
test redbend fota[FS]
E: failed to mount / data (unknown error: 0)
-- copying media files..
-- updating application ..
E:filed to mount / data (unknown error: 0)
E: install_application_for_customer:Cant's mount /data
your storage not prepared yet. please use UI menu for format and reboot actions. copy application failed.
-- Appling Multi-CSC...
installing Multi-CSC
Copied the packages.
Copied the default_wallpaper file.
Coplied the power on / off animation files.
Can't access to '/system/csc/TGY/system/'.
Successfully applied multi-CSC.
Thats all i have got.
Click to expand...
Click to collapse
Can you try what I posted?
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
Can you try what I posted?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks I will try that later and will let you know the result

Boy124 said:
Hi Derekzxy,
Follow what Baz77 said.
I'm just curious what kernel were you using when you performed nandroid restore?
Hope you get your device working back soon.
Click to expand...
Click to collapse
I have upgraded to N7000ZSLPF and then restored to N7000DXLA1.
Ya, i hope i can get it fix soon.

baz77 said:
Your mistake was recovering through cwm. That recovers nearly the whole rom, and on ICS, can be dangerous. Not counting the fact you are rewriting a ics rom with gb.
Your device is bricked. Maybe not hardbricked.
Download pitfile for your phone from drketans thread, redo flash of your rom choice with pitfile selected. I recommend a GB rom as ICS factory reset or wipe from recovery is dangerous. This should enable safely repartition. Do not check this without pitfile selected. This should safely fix your brick. Do not select clear efs.
If it doesnt reboot, bootloop, at least you got gb. The rom you flashed is not wipe version and stuff is lingering that stops reboot. Go to recovery and perform factory reset. If no bootloop,
do a safe factory reset from dialer anyway. Code google it, it should have 3855 in it. Now root it and with mobile odin install cf kernel and in recovery, after safe reboot retore your cwm backup. Note, with ICS it is not recommended recovering data or apps. Should you want to backup and recover apps, non system ones you can with titanium backup. Data again not recommended.
All at own risk.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Hi, I'm trying to find the pitfile you mentioned, but I couldn't find it, may you post the link to the pitfile, and do I use Odin to flash it, and what option I should check and which i shouldn't, sorry to bother you, but you may be my life saver

http://forum.xda-developers.com/showthread.php?t=1424997
Best read whole ghread, I provided shortcut route lol
If you have 16gb you can use this one I thinkhttp://forum.xda-developers.com/showthread.php?p=26162413
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
http://forum.xda-developers.com/showthread.php?t=1424997
Best read whole ghread, I provided shortcut route lol
If you have 16gb you can use this one I thinkhttp://forum.xda-developers.com/showthread.php?p=26162413
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Hi, I have found the pitfile, and I have looked through most of the post up there, but I still couldn't found the option which i need to check in PC Odin when flashing with the pitfile. please kindly help me out Thanks x 1000

Select tar md5 file in pda, select pit file in pit file and see that repartion is now checked.
Its that easy Odin is even supplied with the pit file,
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
Select tar md5 file in pda, select pit file in pit file and see that repartion is now checked.
Its that easy Odin is even supplied with the pit file,
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
No Luck. My 1st try, its stuck at factorygf.img
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DXLA1_N7000OLBKL2_N7000DXKL2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> cache.img
<ID:0/006> NAND Write Start!!
<ID:0/006> factoryfs.img
see attachment
I have tried to flash with KK1 which has Code, Modem and CSC file and also Pit file.. it has passed the factorys.img, however stuck at DATA see result below:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000ZSKK1_CL706440_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7000XXKJ6_REV_05_CL1070146.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OZSKK1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> zImage
<ID:0/006> factoryfs.img
<ID:0/006> data.img
should I perform this action in the post http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
THanks

Hello,
I too have same problem now. Please help me.

If it getsvstuck on factory thrn you have hardbrick, best to return phone dude
Sent from my GT-N7000 using Tapatalk 2

derekzxy said:
Hi, I have found the pitfile, and I have looked through most of the post up there, but I still couldn't found the option which i need to check in PC Odin when flashing with the pitfile. please kindly help me out Thanks x 1000
Click to expand...
Click to collapse
Try this method my friend
http://forum.xda-developers.com/showthread.php?t=1667886
It works for me..

wipe helps
I have exactly the same problem after flashing the stock gingerbread and custom pit file with odin to solve a brick (http://forum.xda-developers.com/showthread.php?t=1667886
In the recovery mode with
E: failed to mount / data (unknown error: 0) ...
Click to expand...
Click to collapse
error message. Just do
wipe data/factory reset and then 'reboot system now
Click to expand...
Click to collapse
It works for me.
Do not 'wipe data' with CWM, that caused me the brick in the first place.

[Q] PIT or not PIT ?

I updated my Samsung Galaxy Note GT-N7000 (bought from Amazon France in fev-12) to the latest official Android version begining of July (4.1.2 or something like that) using Samsung Kies. No root nor any unnofficial modifications.
About 2 weeks later, as I was using it normaly (reading emails or browsing simple website), it turned off and it has not been able to restart since then. Starting screen is freezed to SGNote GT-N7000 ; no recovery mode available ; only download mode available.
I've tried to instal official Firmware with no success, with theses configs :
- Firmware : N7000XXLSZ_N7000XXLSO_N7000XEFLS4_HOME.tar
- Win7 64bits : with Odin v1.85 ; 1.83 ; 3.07 ; 3.07 in XP SP3 + administrator mode ; supermarket bougth cable or official Nexus 4 cable (official GT-N7000 cable broken...)
- Win7 32bits with Odin 3.07 normal mode and XP SP3 + administrator mode ; official Nexus 4 cable
- WinXP with Odin 3.07 ; official Nexus 4 cable
Here is the message I get on each 3 PC, with Odin 3.07
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLSZ_N7000XXLSO_N7000XEFLS4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
I'm getting to the conclusion my SNote is semi-bricked and it needs a new PIT ; before triying it I'd like to have an "expert opinion" as adviced on many sites ; what do you think ? Should I give it a try or consider sending it to Samsung (2y warranty applicable it seems to me) ?
I'm currently downloading an older Firmware version just to give it one last try before PIT or sending to Samsung. (N7000XXLRI_N7000XEFLP2_XEF.zip)
Thx in advance,
Quinteen

I forgot to add that :
- I installed latest USB drivers (latest KIES on Win7 64b ; standalone drivers on others PC)
- I killed all Kies processes before starting Odin
- I Disabled Anti-virus on Win XP & Uninstalled antivirus on Win 7 64b
Thx
q

One last precision : when using Odin 1.85 there is no error message ; it seems blocked writing NAND (waited for round 1h) :
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLSZ_N7000XXLSO_N7000XEFLS4_HOME.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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
Thx
q

No better result with an older firmware on Odin3.07 win7 64b (N7000XXLRI_N7000XXLRB_N7000XEFLP2_HOME.tar.md5) : same faillure message as in first post.
My phone was pretty full (230 MB free), might it be that I need to cilck the Erase NAND option ?
Thx,
Q

quinteen said:
No better result with an older firmware on Odin3.07 win7 64b (N7000XXLRI_N7000XXLRB_N7000XEFLP2_HOME.tar.md5) : same faillure message as in first post.
My phone was pretty full (230 MB free), might it be that I need to cilck the Erase NAND option ?
Thx,
Q
Click to expand...
Click to collapse
take out battery, reinsert, go to download mode, flash philz kernel (.tar) file (the one corresponding to your rom), flash using odin, once done, go to recovery (volume up+home+power), just to confirm that you have philz kernel, it would have option as philz settings. From there you can do factory reset and in mounts and storage you can wipe /system /data /preload /cache and then go to download mode and try to flash stock rom again. Also make sure stock rom download is not incomplete. Although these steps are might not help but you can still try.
Edit: did you wipe anything on stock recovery before trying to flash stock rom?

treacherous_hawk said:
take out battery, reinsert, go to download mode, flash philz kernel (.tar) file (the one corresponding to your rom), flash using odin, once done, go to recovery (volume up+home+power), just to confirm that you have philz kernel, it would have option as philz settings. From there you can do factory reset and in mounts and storage you can wipe /system /data /preload /cache and then go to download mode and try to flash stock rom again. Also make sure stock rom download is not incomplete. Although these steps are might not help but you can still try.
Edit: did you wipe anything on stock recovery before trying to flash stock rom?
Click to expand...
Click to collapse
Thanks for your answer Treacherous_hawk :
1/ I didn't wipe anything as my phone could only start in download mode when I started having these pb
2/ my phone isn't rooted and if I install philz kernel I guess the flash count will be incremented and I won't be able to send my phone to Samsung, right ?...
Quinteen

quinteen said:
Thanks for your answer Treacherous_hawk :
1/ I didn't wipe anything as my phone could only start in download mode when I started having these pb
2/ my phone isn't rooted and if I install philz kernel I guess the flash count will be incremented and I won't be able to send my phone to Samsung, right ?...
Quinteen
Click to expand...
Click to collapse
And by the way how do I get the ROM number given that I can't boot my phone ?....

quinteen said:
And by the way how do I get the ROM number given that I can't boot my phone ?....
Click to expand...
Click to collapse
you can flash xxlsz, xxlt5/6/7 any one of those. yes the counter might increase but if it works you can reset it to 0 using triangle away, but again only if it works, and if it is not booting and if you still have warranty why not send it for repair as it is.

quinteen said:
I updated my Samsung Galaxy Note GT-N7000 (bought from Amazon France in fev-12) to the latest official Android version begining of July (4.1.2 or something like that) using Samsung Kies. No root nor any unnofficial modifications.
About 2 weeks later, as I was using it normaly (reading emails or browsing simple website), it turned off and it has not been able to restart since then. Starting screen is freezed to SGNote GT-N7000 ; no recovery mode available ; only download mode available.
I've tried to instal official Firmware with no success, with theses configs :
- Firmware : N7000XXLSZ_N7000XXLSO_N7000XEFLS4_HOME.tar
- Win7 64bits : with Odin v1.85 ; 1.83 ; 3.07 ; 3.07 in XP SP3 + administrator mode ; supermarket bougth cable or official Nexus 4 cable (official GT-N7000 cable broken...)
- Win7 32bits with Odin 3.07 normal mode and XP SP3 + administrator mode ; official Nexus 4 cable
- WinXP with Odin 3.07 ; official Nexus 4 cable
Here is the message I get on each 3 PC, with Odin 3.07
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLSZ_N7000XXLSO_N7000XEFLS4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
I'm getting to the conclusion my SNote is semi-bricked and it needs a new PIT ; before triying it I'd like to have an "expert opinion" as adviced on many sites ; what do you think ? Should I give it a try or consider sending it to Samsung (2y warranty applicable it seems to me) ?
I'm currently downloading an older Firmware version just to give it one last try before PIT or sending to Samsung. (N7000XXLRI_N7000XEFLP2_XEF.zip)
Thx in advance,
Quinteen
Click to expand...
Click to collapse
Maybe this should prove of some help with the right Philz kernel:
http://forum.xda-developers.com/showthread.php?t=2384160
I think u have lost recovery and by flashing the right recovery, you can boot ur phone and take the next steps.

[Q] Need help with rooting i8190XXANI4

Hello,
(I've rooted 3 HTC's and 1 Samsung in the past so this is not new for me)
I'm trying to root a Galaxy S3 Mini (i8190XXANI4) for my friend.
I've tried several tutorials, but I cant seem to get past the ODIN step.
Every time when I reboot into the Recovery, I get the "Android System Recovery 3e" instead of the CWM recovery.
I've tried at least 3 different versions of ODIN (v3+), and 3 different sites with tutorials.
I've tried these tutorials:
- http://www.android.gs/root-galaxy-s3-mini-i8190/
- http://smartphones.wonderhowto.com/how-to/root-your-samsung-galaxy-s3-mini-smartphone-0140735/
- and a YT video.
Every time ODIN tells me: "RESET" -> Device Reboot -> "OK" . Then I turn off the phone, and Reboot into recovery using the 3-button-combo.
How can I succesfully install CWM ?
Thanks in advance, Jeroen

Easy way is use vroot. It'll fail first time so just do it again.
Once you have root you can then flash cwm.
Make sure you enable usb debugging first!.

jeroen_13 said:
Hello,
(I've rooted 3 HTC's and 1 Samsung in the past so this is not new for me)
I'm trying to root a Galaxy S3 Mini (i8190XXANI4) for my friend.
I've tried several tutorials, but I cant seem to get past the ODIN step.
Every time when I reboot into the Recovery, I get the "Android System Recovery 3e" instead of the CWM recovery.
I've tried at least 3 different versions of ODIN (v3+), and 3 different sites with tutorials.
I've tried these tutorials:
- http://www.android.gs/root-galaxy-s3-mini-i8190/
- http://smartphones.wonderhowto.com/how-to/root-your-samsung-galaxy-s3-mini-smartphone-0140735/
- and a YT video.
Every time ODIN tells me: "RESET" -> Device Reboot -> "OK" . Then I turn off the phone, and Reboot into recovery using the 3-button-combo.
How can I succesfully install CWM ?
Thanks in advance, Jeroen
Click to expand...
Click to collapse
uncheck in ODIN "auto reboot" before installing cwm, when ODIN is done turn phone off by removing battery, then put battery back in and go to recovery with 3 buttons. this should work

thout said:
uncheck in ODIN "auto reboot" before installing cwm, when ODIN is done turn phone off by removing battery, then put battery back in and go to recovery with 3 buttons. this should work
Click to expand...
Click to collapse
Thanks man, It worked!
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery-clockwork-touch-6.0.2.7-golden.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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!

Recently I learned that there are several 'one click methods' for rooting which are really easy, you can find a list of such methods in the How do I root my Android device? thread in Android StackExchange. I used Kingo Root for a i9200 without problem.

Try Galaxy S3 mini ToolKit 2.0

Loop reboot after the "FIX Ram Management"

Hi
My S6 is in loop reboot after i edit the build.prop... I have the original build.prop on my pc but how to restore it ??? Please help!

master-i said:
Hi
My S6 is in loop reboot after i edit the build.prop... I have the original build.prop on my pc but how to restore it ??? Please help!
Click to expand...
Click to collapse
If you have TWRP installed, you can just ADB the file over. Easy.
If you only rooted and want to preserve your KNOX flag, you need to ODIN back to stock and then re-root. It's not destructive, so it's not nearly as bad as it sounds

I don't have twrp for now but can i Install it on download mode ? I just tried to install it and it stop on Start upload (on odin)

Follow these instructions. Download ODIN from that link too
http://forum.xda-developers.com/tmo...irmware-sm-g920t-firmware-odin-guide-t3077706

Do i lose my data? and where Can I find the [Unified Driver Installer] on step 2?

No you won't lose your data at all, you will lose root, but all you need to do is re-root the phone.
http://developer.samsung.com/technical-doc/view.do?v=T000000117

I think it's easier to flash only the build.prop no? is it possible?
Thanx to help me bro!

No at this point, IMO, this is the easiest way to get you back to where you were. I assume you're on the stock ROM just rooted.

Yes, I were on the stock room just rooted by PingPong. Hope it will not make my phone slower or make it crash more often... :/

Yeah just ODIN back to stock, then re-root using PingPong, it's really not as bad as it sounds. All of your apps and user data including all settings will still be there.

@se1000
Please look this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU1AOCG_G920TTMB1AOCG_G920TUVU1AOCG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Have you had your phone in download mode for a while? If so, try rebooting the phone

se1000 said:
Have you had your phone in download mode for a while? If so, try rebooting the phone
Click to expand...
Click to collapse
Of course I just retried again same error... I can't understand because I see the 0:COM3 on Odin...

Are you using the ODIN from the link? I had problems with other versions

se1000 said:
Are you using the ODIN from the link? I had problems with other versions
Click to expand...
Click to collapse
Yes the V3.10

Were you trying to run ADB earlier? Try rebooting the PC

I closed and reopen Ondin on Administrator and now it's blocked with: <ID:0/003> SetupConnection..

Try a different USB cable or different USB port. Seems ODIN can get a bit finicky

I rebooted PC and my Phone and unplugged and still the same
maybe it's because i tried to install twrp?

Shouldn't matter, as long as you're in download mode and ODIN shows light blue it should work