hi
My Note stop charging, stop working and can't use volume up + home + power buttons (every time restart)
My note not rooted and tried to install stock rom throw odin but every time failed.
after restarting it's give this message:
firmware upgrade encountered an issue. please select recovery mode in kies & try again.
Kies can't see my device.
I installed CWM recovery throw odin and the device restart with yellow triangle and not working.
any suggestion?
<ID:0/035> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000JPKJ4_N7000OJPKJ3_N7000XXKJ4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/035> Odin v.3 engine (ID:35)..
<ID:0/035> File analysis..
<ID:0/035> SetupConnection..
<ID:0/035> Initialzation..
<ID:0/035> Get PIT for mapping..
<ID:0/035> Firmware update start..
<ID:0/035> boot.bin
<ID:0/035> NAND Write Start!!
<ID:0/035> cache.img
<ID:0/035> factoryfs.img
<ID:0/035>
<ID:0/035> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Are you repartitioning your device while flashing ?
Akiainavas said:
Are you repartitioning your device while flashing ?
Click to expand...
Click to collapse
no
How can I know that the rom is suitable for my device ?
Here you go:
http://forum.xda-developers.com/showthread.php?t=1424997
Use dr. ketan's list to get firmware for your device. In theory it's best to use the one that came with your phone - but honestly, every other should work. Choose one from directly rootable according to location/carrier your phone came from.
still not working, odin failed
First uninstall kies n install just driver from stock rom thread(same u hav mentioned in some above post). There is 32 n 64 bit drivers, install according your OS of pc.
Connect direct to pc, dont use extension cable, n preferably back side of pc
Put device in download mode (vol DOWN + home + power) once it will ask to continue, thn will enter in download mode
Now reflash rom.
Sent from my GT-N7000 using xda premium
i am using laptop Vista 32-bit system is that make difference?
May be, rwmove kies n just install 32bit driver
N try
Confirm your device in download mode
Sent from my GT-N7000 using xda premium
removed kies , re installed driver turned off antivirus with firewall
restart and try again with same message, failed
Have you put device in dowload mode?
Dont put rom file too deep inside folder. Just put in a folder on root directory.
If not works then try another pc at last option.
Sent from my GT-N7000 using xda premium
yes used the mobile in download mode
i will try another pc
thank you
have you fix your problem??? ihave the same situation,,pls help me
no not yet, someone advise me to use jig usb
Succeeded to download the rom and the device restart but get back to the first problem
freeze on galaxy note start screen
Dr-Ketan,
Could you tell me what could cause a phone to get stuck at factoryfs.img? Also my galaxy note can only mount to USB storage from clockworkmod, if I mount sdcard, it won't show up on the computer. So only USB storage can be seen in computer. Does this mean the sdcard is dead? Thanks.
Related
Hi everybody!
This is my first posting here, I hope it's in the right category. I've used the search function, found similar problems but no one facing the same issue. I wanted to upgrade to Android 2.3.3 (2.3.4) using Odin. I tried three different Firmware releases but none worked. This is what happens in Odin:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_XWJVI_Sbl.tar.md5 is valid.
<OSM> PHONE_XXJVO.tar.md5 is valid.
<OSM> CSC_DBTJV2.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> param.lfs
<ID:0/006> zImage
I tried with and without repartition. Sometimes the process stops at the SetupConnection line, sometimes at zImage when obviously the kernel should be installed. When in download mode, I see a blue progress bar starting to move across the phone screen, but soon later the whole display turns green/blue/white (it always had a different color) with no more text. Hours later Odin finally displays a FAIL message.
I tried firmware versions I9000XXJVQ and I9000XXJVR from samfirmware.com with 512 PIT file. I recognized some Kies-Thread running in the background on my Win7 machine, which I killed to prevent any problems.
In another forum I was told this issue might be related to some lagfixes installing ext4. When I read that it came to my mind that I indeed had installed the voodoo lagfix in February - I had completely forgotten about that. However, is there a chance to recover the phone? Putting it into DL mode is the only thing that works. Any help is appreciated!
Can you go in recovery mode to disable the lagfix? and when you use the 3 part file always check re-partition.
Had similar problems with Windows 7 x64, 2 in 3 flashes would fail.
Try another pc if possible with Xp.
kuribo67 said:
Can you go in recovery mode to disable the lagfix?
Click to expand...
Click to collapse
Well, I tried, but I did not succeed - (Hold Vol up + Power on) but I'll try again. Is it absolutely necessary to remove the lagfix? As mentioned before someone told me that ext4 might be causing those problems. However, I though the sd was repartitioned (when checkbox is ticked) and the firmware is a kind of disk image which is installed and thus overwrites the existing file system?
aileron79 said:
Well, I tried, but I did not succeed - (Hold Vol up + Power on) but I'll try again. Is it absolutely necessary to remove the lagfix? As mentioned before someone told me that ext4 might be causing those problems. However, I though the sd was repartitioned (when checkbox is ticked) and the firmware is a kind of disk image which is installed and thus overwrites the existing file system?
Click to expand...
Click to collapse
it's vol up + home button + power on, but don't release the button untill your are in the menu.
A stock firmware is made for RFS partition not ext4, i think it's that the problem, but i may be wrong.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_XWJVI_Sbl.tar.md5 is valid.
<OSM> PHONE_XXJVO.tar.md5 is valid.
<OSM> CSC_DBTJV2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> param.lfs
<ID:0/005> zImage
<ID:0/005> boot.bin
<ID:0/005> Sbl.bin
<ID:0/005> factoryfs.rfs
Thank you all so far! Well, it almost worked - at least kind of. I tried it a couple of times, rebooted the PC, rebooted the phone, reinstalled drivers, used another USB port. After a couple of retries it stopped at "factoryfs.rfs" - which obviously contains the file system. This makes me guess that it does not matter which FS currently is installed as it gets overwritten by this factoryfs-thing. Please correct me if I am wrong!
Still, any help on this topic is gladly appreciated!
when you flash pda in odin the file system is over-written and reverts to rfs.
Try without re-partition ticked. Also after several attempts your battery may have no juice left in it: pull the battery, let it sit a couplce of minutes and then plug it in and see if it will re-charge -- may not, you might be stuck at download and odin.
Flash an older 2.2 firmware first: pda. phone and csc, don't bother with the pit file and don't bother with re-partition -- this is just to get you back and working, you can then charge the battery and update to jvr after.
Also check the thread on unbricking the phone -- most issues with flashing are recoverable, its just persistence.
lgsshedden said:
when you flash pda in odin the file system is over-written and reverts to rfs.
Try without re-partition ticked. Also after several attempts your battery may have no juice left in it: pull the battery, let it sit a couplce of minutes and then plug it in and see if it will re-charge -- may not, you might be stuck at download and odin.
Click to expand...
Click to collapse
Well, I tried to flash with and without repartition/pit-file. The download process hangs at different stages. I doubt it has to do with the battery, as the phone has been attached to the PC for almost three days now, I guess the battery is charged then...?
[/QUOTE]
Flash an older 2.2 firmware first: pda. phone and csc, don't bother with the pit file and don't bother with re-partition -- this is just to get you back and working, you can then charge the battery and update to jvr after.
Also check the thread on unbricking the phone -- most issues with flashing are recoverable, its just persistence.[/QUOTE]
To which of the thousands of unbricking threads do you refer? I read something about a tool which puts the phone into recovery mode, from where I can format the sd. However, I can't get to recovery mode by pressing vol up, home + power, i just can enter download mode. I have tried various firmwares, neither did work...
Thanks for your help so far, maybe you can give me another hint on the thread you're talking about?
Try rebooting the phone,rebooting the pc,use a different usb cable(this part made it work for me), and try again. Hope it helps man cause i've been down that road and it sucked bricked my sgs 2 times but thankfully revived it because heimdall one click un-brick oh and 1 more thing if you use 3 files check re partition
Sent from my GT-I9000 using xda premium
Mate, try a full 3 file flash and a pc with Win XP 32-bit and ODIN 1.83
Worked for me
Good luck flashing !!
Thank you all guys, it worked - even though it was none of the tips provided here. I have no clue what the problem was, I moved to another PC, it took me three tries to flash the phone.
- The second PC was Win7 64bit as well.
- I used the original cable (tried with another one as well, no difference)
- I used just the drivers without any Kies installation.
- I used a SINGLE FILE FLASH with Android 2.2.1 first (which I was then unable to boot as it stuck with the S symbol during boot)
- Flashed 2.3.4 afterwards - worked.
My phone has never ever been running so smoothly before, even with lag fixes!
Unfortunately, my external SD makes troubles, but let's see how to fix that.
My note to all of you guys facing similar problems:
Some say, use PIT and repartition, some say, don't
Just don't care - for me it finally worked without (single file flash). Try all possibilities.
Some say, install Kies, just because of the drivers, some say, install the drivers without Kies
Just don't care - try either option, it might work - for me the drivers without Kies finally worked but I have no clue if that had any impact.
Some say, use another USB cable, some say use the original one
Just don't care - try different cables if possible, in my case there was no difference.
Some say, use the USB port closest to your MB, others say, try various USB ports
Just don't care - try different ports, the behavior cannot be reproduced, each try the flashing process got stuck at another stage - independent of the USB port used.
Some say, try another computer with another OS
Good choice - that made it working in my case. Even though the other machine was nearly the same with exactly the same OS installed. Also, I have successfully flashed my phone with the first one before.
Thanks guys, you're the best! And give Android 2.3.4 a try, it's FAST and SMOOTH!
Hi,
I have Galaxy note with Kernel version 2.6.35.7...LA6, Slovenia (SiMobil). As far is i understood from here:
http://forum.xda-developers.com/showthread.php?t=1329360
It's no directly rootable, so i used InitialCFRootFlasher (CF-Root-SGN_XX_SER_LA6-v5.0-CWM5). What happened is visible in the Attachment image - it stops (left it for 30 minutes and then plugged the phone out) at pushing zImage (there is zImage file in zImage folder).
I also tried downgrading to KJ1 (4th post in the link i've provided) and Odin got stuck here:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
As far as i know, i've followed all the steps correctly, i've started odin in recovery mode thingy (and with phone turned on, everything :/) and it gave pretty much the same results. I have unknown sources and USB debugging checked.
Only one thing (if it happens to be relevant): i've reset the phone from recovery mode (volume+home+power) before doing all this and the only visible difference now (except of course from everything gone) is that it now asks me for USB Connection (Copy from/to computer) and it did connected automaticly before.
Also, the keyboard layout has numbers so it reseted to the point of the latest patch.
Help wold be appreciated, thank you for your time.
0bj4ct7
what is the rom version? if its is LA6 then it it not directly rootable and you need to downgrade to root then upgrade again using mobile odin to keep root status
As i said it is LA6 and i tried to downgrade to KJ1 from the link i have posted. Thus the Odin error message in my first post :/
I'm now downloading LA1 from this tutorial:
http://forum.xda-developers.com/showthread.php?t=1535025
and will try to flash/root it with Odin.
Anyone knows why it didn't want to connect the first time? (see the Odin log)
btw my goal is to install CheckROM Note HD 6 with mobile odin after rooted.
Sorry for the double-post, but this is what happened with take 2 on Odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Rooted_Stock_Odex_N7000XXLA6.tar.md5 is valid.
<OSM> MODEM.tar.md5 is valid.
<OSM> CSC_N7000XEULA1_XEU.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
So eventually the same thing happened: It failed to establish connection with my phone, has anyone any idea why and how could i make it work? :/
strange !!
tell you what ,just to be sure :
1. is it odin 1.8.5 , if not then download from this link http://dl.xda-developers.com/attachdl/3f3aee012a84b80d9824245ec63e1c5a/4f99a80d/8/1/5/3/7/0/Odin3-v1.85.zip
2. check your cable ,use another cable if you have any.
3. follow this method by DR.Ketan
dr.ketan said:
---------------------------------------------------------------------------------------------------------------
When No Any other method works to Root your device, use this
---------------------------------------------------------------------------------------------------------------
Note that, this will downgrade your ROM to KJ1, after that you can update it.
Download: https://rapidshare.com/files/369028110/SGN_XX_OXA_KJ1_FACTORYFS.zip
(special thanx to schiwa for providing premium a/c to host file)
Code:
Mirror for Above file (in case above link not works then only)
Download this three files
[url]http://www.mediafire.com/?7vf637co8frdqqg[/url]
[url]http://www.mediafire.com/?kkvdsf5vh8zipzi[/url]
[url]http://www.mediafire.com/?l6qqicvibzhxt18[/url]
- Tool to join them, run the following file and locate the .001 file.
[url]http://www.mediafire.com/?btrusgmd1v2d72q[/url]
- Make sure your SGN is NOT connected to your computer
- Reboot your SGN into "download mode" (Vol down + Home + Power))
- Start ODIN
- Click the PDA button, and select the "SGN_XX_OXA_KJ1_FACTORYFS.tar" file
- Connect the SGN to your computer
- Make sure "repartition" is NOT checked
- Click the START button
- Wait for the phone to reboot TWICE
- Done.
Now you have your device Rooted, Install Mobile Odin Pro n update your device to any new ROM with Mobile Odin
Click to expand...
Click to collapse
also check this thread http://forum.xda-developers.com/showthread.php?t=1329360
Thanks to all here, it turned out i actually wasn't using download, but recowery mode
After i actually pressed VOL. DOWN at the beginning it worked perfectly.
Thanks for all the answers, I'd recommend emphasizing tese keys so people like me won't repeat this.
Cheers (CheckROM works perfectly
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.
Hi everyone
My phone is ''firmware encountered an issue'' i searhing this Thread but i cant do it. Cuz i try everything.
My problem is ODIN always FAIL always
I remove drivers and no kies. I try 6 different offical roms but no different.
So, What did I do?
I use
JB leak
RocketRom JB
RocketRom v12 ICS
I use offical firmware
OJVKL1
XXLRK - N7000VD2LR1
XXLRK
My complaining is This roms is so slow i hate it. Maybe my phone is slow but it's impossible.
HARDRESET-UPDATA-ALLWIPE but always slowly. Firsday everything is good but second day is so laggy. And i think maybe i need a old rom.
GB
So i' download XXLA4 and install. Everything is great but when i XXLA4 root everything messed up.
This is root ''CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5''
and my phone is ''firmware encountered an issue'' and i think back is good ill try XXLRK again but i install mistakenly i select ''N7000_16GB_Q1_20110914-stock.pit'' file and my phone is sleeping now.
So i enter the download mode... Download mode is normal and when i install'a Kernel_JellyBeer_v3.1_STD_CWM_Flashable.zip
I see recovery menu i'll full wipe and back to instaling odin say again FAIL FAIL FAIL...
Please Help me Thank you so much
PEACE
orcunpakten said:
Hi everyone
My phone is ''firmware encountered an issue'' i searhing this Thread but i cant do it. Cuz i try everything.
My problem is ODIN always FAIL always
I remove drivers and no kies. I try 6 different offical roms but no different.
So, What did I do?
I use
JB leak
RocketRom JB
RocketRom v12 ICS
I use offical firmware
OJVKL1
XXLRK - N7000VD2LR1
XXLRK
My complaining is This roms is so slow i hate it. Maybe my phone is slow but it's impossible.
HARDRESET-UPDATA-ALLWIPE but always slowly. Firsday everything is good but second day is so laggy. And i think maybe i need a old rom.
GB
So i' download XXLA4 and install. Everything is great but when i XXLA4 root everything messed up.
This is root ''CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5''
and my phone is ''firmware encountered an issue'' and i think back is good ill try XXLRK again but i install mistakenly i select ''N7000_16GB_Q1_20110914-stock.pit'' file and my phone is sleeping now.
So i enter the download mode... Download mode is normal and when i install'a Kernel_JellyBeer_v3.1_STD_CWM_Flashable.zip
I see recovery menu i'll full wipe and back to instaling odin say again FAIL FAIL FAIL...
Please Help me Thank you so much
PEACE
Click to expand...
Click to collapse
Did you do any full wipes on ics? Where is odin failing, is it factory fs?
Sent from my GT-N7000 using xda premium
happened to me too..
That "firmware encountered an issue" is an indication that the system is corrupted to the point that it cant manage to startup..
I got that problem because of my stupidity.. Plugged my phone to the defective USB port and when I started flashing, I accidentally moved the cable and BAM! Phone is disconnected, and flash failed bigtime..
Your only fix for that if you ask me is do another flash... Try pulling out the battery for 10mins and try to boot into download mode.. That's how i was able to recover my phone from that screen..
I remember that message offering to run emergency recovery using Kies but it is totally useless.. trust me..
Make sure you're plugging in your phone to the USB port DIRECTLY on the motherboard of the computer (the ports at the back) not the ports on the front panel of the case of your computer..
If you're still encountering problems, I believe youre looking at a bricked device and seek more advanced assitance from people here..
SpyderTracks said:
Did you do any full wipes on ics? Where is odin failing, is it factory fs?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
usually factory fail.
i did every time fullwipe
Sounds like superbrick, but try flashing stock gb with pc Odin.
Sent from my GT-N7000 using xda premium
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRQ_N7000DBTLRQ_N7000XXLRK_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Yep, that's superbricked. You can either repartition the emmc chip, you'll lose about 3gb of internal sd card and won't be able to run stock roms.
If you have warranty get a reply placement, just say you were updating through Kies when this happened.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Yep, that's superbricked. You can either repartition the emmc chip, you'll lose about 3gb of internal sd card and won't be able to run stock roms.
If you have warranty get a reply placement, just say you were updating through Kies when this happened.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
But i can get download mode and if i install odin ''AbyssNotekernel42CWTouchOriginalLogo'' i get recovery mode...
just once try to remove the battery for a few seconds and put the phone in download mode and flash the rom again or use a GB rom..
nokiamodeln91 said:
just once try to remove the battery for a few seconds and put the phone in download mode and flash the rom again or use a GB rom..
Click to expand...
Click to collapse
i try another laptop now... Cuz i remember what i do.
My last rom is stock XXLRK rom. And i tired slowly
i try everything HARDRESET-UPDATA-ALLWIPE but always slowly. And i think maybe i need a GB rom.
and i download XXLA4 everything is good and when i try root XXLA4.
this file: 'CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5'' stock phone.
Every time i install this way.
Wipe Data/Factory Reset
Wipe Cache Partition
Format/cache
Format/system
Format/data
Wipe Dalvik Cache
Wipe Battery Stats
Fix Permissions
This way always be good for me cuz i try this way 100 times.
I use Odin 1.85 and i use everytime u1_02_20110310_emmc_EXT4.pit (NO-RE-PARTITION)
So i think my fault is mistakenly last time i select ''N7000_16GB_Q1_20110914-stock.pit'' instal a ''CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5''
I'm tired for try.
I try another pc but result is the same. FAIL FAIL FAIL
N7000XXLA4_N7000OJVKL1_N7000XXLA4_HOME.tar
N7000XXLRL_N7000XXLRK_N7000VD2LR1_HOME.tar
N7000XXLRQ_N7000DBTLRQ_N7000XXLRK_HOME.tar
N7000XXLRT_N7000DBTLRT_N7000XXLRK_HOME.tar
N7000XXLRI_N7000OJVLR3_N7000XXLRB_HOME.tar
I'm like a sammy's storage... I try this roms but result is the same.
Where did i wrong? problem is kernel?rom?pit file? ((
where did it fail?
nokiamodeln91 said:
where did it fail?
Click to expand...
Click to collapse
Odin Fail. I think factoryfs.img fail...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRQ_N7000DBTLRQ_N7000XXLRK_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Why now is the wrong? Thing I did always right way
Done dude.. u r good to go now
Problem is solved
Thank you so much ''nokiamodeln91''
dont do any wipes as of now.. u on ICS and an unsafe kernel
dont forget the thanks button
How did you rectify this nokiamodeln91?
Sent from my GT-N7000 using xda premium
OP used an incorrect file with the PIT16GB file.. i just corrected the mistake
nokiamodeln91 said:
OP used an incorrect file with the PIT16GB file.. i just corrected the mistake
Click to expand...
Click to collapse
Nice man, well done.
Sent from my GT-N7000 using xda premium
nokiamodeln91 said:
OP used an incorrect file with the PIT16GB file.. i just corrected the mistake
Click to expand...
Click to collapse
Where can I get a copy of this PIT file? My phone is bricked and am only able to get into download mode and not recovery mode.
I have received a GT-i8190 which is messed up.
When I start the phone, it says something went wrong with firmware upgrade, and that I need to try installing again.
Tried to install new firmware I8190DXALL3_I8190OLBALL4 using Odin3 v3.07.
Have followed the instructions with PDA only, no re-partition etc...
When I press start in Odin, Firmware update starts, and I can follow progress bar in Odin3 as well as on the phone.
Unfortunately, the process hangs when it tries to write STE_boot2.img, and after waiting a long time I get a write fail.
Have tried with other firmware versions, but each version eventually hangs somewhere (not always with STE_boot2.img). Below an extract of what I get from Odin3.
Any suggestions anyone?
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8190DXALL3_I8190OLBALL4_HOME.TAR.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> system.img
<ID:0/010> NAND Write Start!!
<ID:0/010> STE_boot2.img
Is your battery full, when you are trying to flash the firmwhere? Did you try another cable? Is your computer going to standby with some component or are you actively waiting moving the mouse cursor? If nothing helps, try to flash from another computer.
rarog said:
Is your battery full, when you are trying to flash the firmwhere? Did you try another cable? Is your computer going to standby with some component or are you actively waiting moving the mouse cursor? If nothing helps, try to flash from another computer.
Click to expand...
Click to collapse
First system I used was Vista; battery was full. System does not go on standby.
Have tried on different system (windows 7) with different cable. Now Odin does not hang as it did on the vista system, but Odin crashes at the same moment it hung on the vista system, with the message: Odin Downloader stopped working.
Have tried with Odin3 V3.07 and V1.85
Any other suggestions?
Try with firmware from here: http://forum.xda-developers.com/showthread.php?t=2157105.
Download "I8190 серв. укр.rar". It's made out of service firmware with additional files not included in official firmware.:good:
If that won't do it, then take it to samsung.
tys0n said:
Try with firmware from here: http://forum.xda-developers.com/showthread.php?t=2157105.
Download "I8190 серв. укр.rar". It's made out of service firmware with additional files not included in official firmware.:good:
If that won't do it, then take it to samsung.
Click to expand...
Click to collapse
Well, have used this service firmware following the instructions.
Everything went wel at firstl; could follow the progress in Odin, eventually the phone went down after 8 mins), I assumed for reboot but it did not restart.
Odin then finished stating everything passed (green), so disconnected the phone and tried to start up, unfortunately without success.
I thought that the battery was empty, but I have checked with another phone and it is still at 75%.
I guess the phone is now completely wasted, unless someone still has an idea to revive it?