Related
Hi all,
I was on the UK Stock 4.03 + Root....
I was trying to connect to a Blue-tooth Device today and the phone was frozen, so I turned it off....
When I tried to turn it back on...it won't go pass the "Samsang Galaxy Note" screen....(it would restart it self every time it reaches that screen)
I tried flashing it to the 4.0.4 German Stock via Odin...and the problem is still there....
is my phone BRICKED??
Please HELP~~!
THANKS!
Forgot to mentioned that when I was trying to reboot the phone for the first time....I had a USB Stick plugged into the phone...dunno if that was the cause of the problem
You said tried to flash 4.0.4, that is insufficient information
whether it was successfull or not?
do you rememeber wat exactly last msg ?
Did u try to completely remove the battery then reflash again stock ics through odin?
↖(^▽^)↗ Sent from Rego Galaxy Note ↖(^▽^)↗
Yeah...I did a flash of this Stock ROM "N7000XXLRG" from this page: http://forum.xda-developers.com/showthread.php?t=1424997.
The flash was SUCCESSFUL by Odin. However, When the phone rebooted after the flash the problem is still there (phone keep restarting once it reaches the "Samsung Galaxy Note" screen)
btw.. this is the log of the flash in Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRG_N7000DBTLRG_N7000XXLRB_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> factoryfs.img
<ID:0/004> NAND Write Start!!
<ID:0/004> zImage
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> Sbl.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
Also...when I am trying to get into recovery mode....it shows the pic of the Android bot lying on the ground with a red triangle??
It seems you have got bootloop
and least chances that you have data.img corrupt
For safety you just download any GB ROM and flash using PC Odin, after that go to recovery and wipe cache and data, it will be solved if only bootloop is there.
if you get error on wiping then it is case of brick bug.
dr.ketan said:
It seems you have got bootloop
and least chances that you have data.img corrupt
For safety you just download any GB ROM and flash using PC Odin, after that go to recovery and wipe cache and data, it will be solved if only bootloop is there.
if you get error on wiping then it is case of brick bug.
Click to expand...
Click to collapse
Thanks for your reply again....is there a SAFE instruction of how I can flash GB ROM by using Odin?
You meant a STOCK GB or CUSTOM one?
Does it matter if I flash the German one when I was on the UK one originally?
THANKS AGAIN
Find stock rom thread by me from stickies in development section
Download ANY stock.gingerbread rom and flash using pc odin
Guide is available on same thread post #2.
Sent from my GT-N7000 using xda premium
dr.ketan said:
Find stock rom thread by me from stickies in development section
Download ANY stock.gingerbread rom and flash using pc odin
Guide is available on same thread post #2.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
ok...downloading now....will let you know the result soon....THANKS
DMax99, hope everything goes well for you! When you were on ICS, didn't you flash a safe kernel like Speedmod? Keep us updated on your situation!
dr.ketan said:
It seems you have got bootloop
and least chances that you have data.img corrupt
For safety you just download any GB ROM and flash using PC Odin, after that go to recovery and wipe cache and data, it will be solved if only bootloop is there.
if you get error on wiping then it is case of brick bug.
Click to expand...
Click to collapse
THANKS Doc.....by flashing the GB STOCK has solved the problem
How can I avoid this from happening in the future? Because I want to upgrade to ICS again
Final5k said:
DMax99, hope everything goes well for you! When you were on ICS, didn't you flash a safe kernel like Speedmod? Keep us updated on your situation!
Click to expand...
Click to collapse
No I didn't....where can I get that Kernel? and do I just flash it in CWM?
cheers for the suggestion
Congrats
It was likely to revive as i said it was seems to be a bootloop rather true brick
Dont worry it was just incidence, n not likely to repeat.
You can flash ics now safely. But first wipe cache and data before flashing ics if you have not perform it still.
Sent from my GT-N7000 using xda premium
Speedmod can be flashed in Odin.
http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install.html
Main thread - go there if you have questions :
http://forum.xda-developers.com/showthread.php?t=1673072
Final5k said:
Speedmod can be flashed in Odin.
http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install.html
Main thread - go there if you have questions :
http://forum.xda-developers.com/showthread.php?t=1673072
Click to expand...
Click to collapse
so....
1. this kernel works with any stock ICS ROM?
2. Does it affect any performances....for example making the phone laggy?
cheers
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'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,
I read now the warning post and I understand now that probably I shouldn't have done it (so please be gentle ).. however maybe someone can still help me with my situation:
I've rooted my Galaxy Note with ClockworkMod recovery successfully and then busybox.
Then I went to recovery mode again (after restarting the phone), however it loaded Android regular recovery mode (not Clockwork), so I installed Clockwork again and without restarting performed WIPE DATA (maybe that was also a mistake?). After it was finished it restarted by itself and now its in the following status:
- stucks at GALAXY NOTE N7000 logo. Sometimes blinks, but never goes beyond it.
- Recovery mode exactly same - stuck at logo.
- when plugging USB it will show the battery, but it's like stuck then.
- Tried download mode, but it's stuck at Downloading... forever.
I couldn't find the exact case as mine, that it restarted by itself and stuck at logo now.
I backed up everything, the previous ROM and etc.
I am aware of the bricking bug of ICS, however I had the ClockworkMod installed, so what did I do wrong??
And most importantly, what should I do now? Can I do something via the download mode? I don't think Odin recognizes any connected device when I plug in the USB, but I don't know how to check if it does or not..
Thanks in advance!
Switch to download mode, connect to PC and install a stock JB (be sure to install the USB drivers before).
Make a snapshot of the errors an post it here.
http://forum.xda-developers.com/showthread.php?t=1424997
May be this helps ...
Just flash a new stock rom..
Sent from my GT-N7000 using xda premium
i believe u use wrong kernal so it's stuck ！ if u don't ever do any factory reset or wipes then u're stillsafe ！
if u do so ? then just follow the instructions above given by the 2members here ：p
if u still haven't do any wipes n factory reset then look for philz safe kernal wif ur rom version flash it n let it update for mins
n ur phone will resume operation ！
Trying
alvinhaw said:
i believe u use wrong kernal so it's stuck ！ if u don't ever do any factory reset or wipes then u're stillsafe ！
if u do so ? then just follow the instructions above given by the 2members here ：p
if u still haven't do any wipes n factory reset then look for philz safe kernal wif ur rom version flash it n let it update for mins
n ur phone will resume operation ！
Click to expand...
Click to collapse
Trying all that right now, will keep you posted.
what is my stock ROM?
whatever61 said:
Trying all that right now, will keep you posted.
Click to expand...
Click to collapse
I don't understand this.. my stock ROM was:
Baseband Version: N7000XXLB2
Kernel Version: 2.6.35.7-N7000XXLC1-CL1003701 [email protected] #2
Build number: GINGERBREAD.XXLC1
I don't know what coutnry, I bought it from Netherlands, I live in Belgium, but it could be from any country in the region!
I cannot find this one exactly. I find many with N7000XXLB2 and many with N7000XXLC1.
Which one should I choose?
Also, can I install a JB or ICS directly?
Please let me know I'm doing it right (cause this is getting really insanely ridicilous):
1. I install PhilZ recovery mode via the phone recovery mode.
2. I install a stock ROM (I tried many) via Odin download mode.
All the time stuck as Galaxy N7000 logo. Never goes past it.
Every time I install a stock ROM it also removes the Philz recevory mode, but maybe that's ok..
Anything I'm doing wrong??
Why don't you follow my advice from second post and then show us a snapshot of PC Odin.
No need for Philz when installing a stock Rom with PC Odin (it's always deleted).
And tell us what Rom you install.
ThaiDai said:
Why don't you follow my advice from second post and then show us a snapshot of PC Odin.
No need for Philz when installing a stock Rom with PC Odin (it's always deleted).
And tell us what Rom you install.
Click to expand...
Click to collapse
So I don't wipe anything and just go to download mode and install a PDA file of a STOCK ROM, that's it?
I tried that, but now I will be more specific (and in another guide they say to do some steps before, so its very confusing already).
I also asked above how do I know which ROM I should install?
and also, how do I get errors log? there were no errors when I was installing the PDA..
whatever61 said:
So I don't wipe anything and just go to download mode and install a PDA file of a STOCK ROM, that's it?
I tried that, but now I will be more specific (and in another guide they say to do some steps before, so its very confusing already).
I also asked above how do I know which ROM I should install?
and also, how do I get errors log? there were no errors when I was installing the PDA..
Click to expand...
Click to collapse
Just let THAIDAI knows which stock rom u're flashing !
alvinhaw said:
Just let THAIDAI knows which stock rom u're flashing !
Click to expand...
Click to collapse
Ok, here we go.
I was trying with ROM: N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar.md5
This is what I got from Odin (I hope that's what you meant by snapshot and not actual screenshot or something ):
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.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> factoryfs.img
<ID:0/008> NAND Write Start!!
<ID:0/008> zImage
<ID:0/008> hidden.img
<ID:0/008> modem.bin
<ID:0/008> cache.img
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
This is something new: just after it was completed it booted to recovery mode and gave me the following message:
Android system recovery <3e>
Finding update package
bla bla
Successfuly installed package.
Wiping cache..
Formatting /cache
Cache wipe complete.
E:failed to mount /data (unknown error: 0)
your storage not prepared yete, please use UI menu to format and reboot actions.
copy application failed.
Applying multi-CSC
Can't access to '/system/csc/ATO/system'
Successfully applied multi-CSC.
and it still doesn't boot.. gonna try another ROM now and post here the results.
Now tried with:
N7000XXLRI_N7000XXLRB_N7000XEFLP2_HOME.tar.md5
This is the original original ROM that I had when I just bought the phone.3
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRI_N7000XXLRB_N7000XEFLP2_HOME.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> cache.img
<ID:0/008> NAND Write Start!!
<ID:0/008> factoryfs.img
<ID:0/008> hidden.img
<ID:0/008> modem.bin
<ID:0/008> zImage
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
No going into recovery mode after restart this time and still same problem.
when you flash a stock rom with pc odin, the phone may not boot. If you have flashed a GB rom then when you are stuck at logo enter stock recovery with three button combo and then wipe data factory reset, wipe cache and then reboot.
I flashed a stock rom as explained above, not a GB. I tried wiping cache and all data through recovery. Nothing helps. You say it might not boot, so how do I make it boot with Stock ROM?
stock roms can be ginger bread (GB), or ICS or JB (jelly Bean)
flash a GB stock rom, wait for the proceedure to finish completely, when you see its not booting then use three buttons to get into stock recovery and then wipe then reboot
rraaka said:
stock roms can be ginger bread (GB), or ICS or JB (jelly Bean)
flash a GB stock rom, wait for the proceedure to finish completely, when you see its not booting then use three buttons to get into stock recovery and then wipe then reboot
Click to expand...
Click to collapse
I already did, the last post was a GB, i tried to wipe out everything afterwards also.
ThaiDai, please see my replies, I did as you requested..
Thanks
whatever61 said:
I've rooted my Galaxy Note with ClockworkMod recovery successfully and then busybox.
Then I went to recovery mode again (after restarting the phone), however it loaded Android regular recovery mode (not Clockwork), so I installed Clockwork again and without restarting performed WIPE DATA ...
....I am aware of the bricking bug of ICS, however I had the ClockworkMod installed, so what did I do wrong??
Thanks in advance!
Click to expand...
Click to collapse
By "ClockworkMod" you mean CWM.zip right? This is a temporary recovery that disappears upon reboot. It also LETHAL to wipe with when running on top of a stock ICS kernel.
So to sum up;-
You were running Stock ICS.
You flashed CWM.zip (from YouTube or where ever) from stock 3e recovery and then flashed Root/busybox file.
Booted back into stock recovery, flashed CWM.zip again and performed wipe data/factory reset with it.
How am I going so far?
Bad news - you have most likely superbricked your device.
If so,new MOBO or repartition is only way out now
it might be mess up.. try get 5files wif bootloader n place it accordingly in odin .
go here to study http://forum.xda-developers.com/showthread.php?t=1424997
shoey63 said:
By "ClockworkMod" you mean CWM.zip right? This is a temporary recovery that disappears upon reboot. It also LETHAL to wipe with when running on top of a stock ICS kernel.
So to sum up;-
You were running Stock ICS.
You flashed CWM.zip (from YouTube or where ever) from stock 3e recovery and then flashed Root/busybox file.
Booted back into stock recovery, flashed CWM.zip again and performed wipe data/factory reset with it.
How am I going so far?
Bad news - you have most likely superbricked your device.
If so,new MOBO or repartition is only way out now
Click to expand...
Click to collapse
Yep, emmc bricked. Send it to servicecenter, they repaired it for free, for me. Or you can do the workaround http://forum.xda-developers.com/showthread.php?t=1667886 , but i dont would do that, as you will get many freezes maybe. Thats very annoying.
Regards
Hello,
I tried to Update my Samsung S3 LTE to the I9305XXUFNI3_I9305DBTFNI3_I9305XXUFNI3 4.4.4 Kitkat stock firmware. My phone had JB 4.3 installed with VD2 branding.
I was using Odin 3.07. But after the flashing procedure my device is stuck at the boot animation screen. I can still access download and recovery mode.
Here is what I tried chronologically (with no success)
Wiped cache and data
Flashed the 4.4.4 stock firmware again
Installed CWMOD and wiped cache and data, Dalvik cache
Installed Omni 4.4.4 with gapps-kk-20140606-signed and later CM11 with the same result stucking at boot animation.
The device isn't rooted IMEI is saved according to this guideline http://forum.xda-developers.com/showthread.php?t=1946915. Unfortunately there is no recovery of the 4.3 rom available, however I think a downgrade is no longer possible because of the new bootloader? Odin givs me SW rev check failed when trying that.
I would really appreciate if somebody has any guess waht else I could do to resolve that.
Thanks,
Jon
jon192694 said:
Hello,
I tried to Update my Samsung S3 LTE to the I9305XXUFNI3_I9305DBTFNI3_I9305XXUFNI3 4.4.4 Kitkat stock firmware. My phone had JB 4.3 installed with VD2 branding.
I was using Odin 3.07. But after the flashing procedure my device is stuck at the boot animation screen. I can still access download and recovery mode.
Here is what I tried chronologically (with no success)
Wiped cache and data
Flashed the 4.4.4 stock firmware again
Installed CWMOD and wiped cache and data, Dalvik cache
Installed Omni 4.4.4 with gapps-kk-20140606-signed and later CM11 with the same result stucking at boot animation.
The device isn't rooted IMEI is saved according to this guideline http://forum.xda-developers.com/showthread.php?t=1946915. Unfortunately there is no recovery of the 4.3 rom available, however I think a downgrade is no longer possible because of the new bootloader? Odin givs me SW rev check failed when trying that.
I would really appreciate if somebody has any guess waht else I could do to resolve that.
Thanks,
Jon
Click to expand...
Click to collapse
Firstly I would recommend to download another rom available to our terminals-the XEO from here:http://samsung-updates.com/device/?id=GT-I9305 This is a 4.4.4 firmware for I9305-Poland ,flash through Odin and see what happens.
viktorak said:
Firstly I would recommend to download another rom available to our terminals-the XEO from here:samsung-updates.com/device/?id=GT-I9305 This is a 4.4.4 firmware for I9305-Poland ,flash through Odin and see what happens.
Click to expand...
Click to collapse
Thanks for your answer, I flashed the Polish version but no change it still keeps stuck at the boot logo animation. Any further tips?
jon192694 said:
Thanks for your answer, I flashed the Polish version but no change it still keeps stuck at the boot logo animation. Any further tips?
Click to expand...
Click to collapse
You said you have CWMRecovery installed?Now you could flash thru recovery a custom Rom from this thread:http://www.htcmania.com/showthread.php?t=738977
You try whith 4.1.2 firmware pre-rooted,this is a modificated firmware containing the Knox bootloader.Theoretically there should be no problem.The phone should boot.
Then we'll see.
viktorak said:
You said you have CWMRecovery installed?Now you could flash thru recovery a custom Rom from this thread:htcmania.com/showthread.php?t=738977
You try whith 4.1.2 firmware pre-rooted,this is a modificated firmware containing the Knox bootloader.Theoretically there should be no problem.The phone should boot.
Then we'll see.
Click to expand...
Click to collapse
Thank very much you, that brang my phone back to life! I had to use twrp recovery, cwm wasn't supporting the zip.
What is different with this packages? I tried to load omni 4.4.4 again but it is stuck again at boot animation. Is Kitkat also available as Zip package for recovery like the packages you linked? In the thread it only goes up to 4.3.
jon192694 said:
Thank very much you, that brang my phone back to life! I had to use twrp recovery, cwm wasn't supporting the zip.
What is different with this packages? I tried to load omni 4.4.4 again but it is stuck again at boot animation. Is Kitkat also available as Zip package for recovery like the packages you linked? In the thread it only goes up to 4.3.
Click to expand...
Click to collapse
Hi,mate,this is a kind of downgrade,but not exactly,becuse contain Knox BL/ bootloader/.
Wait wait you must go back to 4.1.2 version.Then if you want- you can flash back 4.4.4 downloaded from the official website of Samsung.
Use Odin ,but don`t forget to kill all Kies process before flashing.
viktorak said:
Hi,mate,this is a kind of downgrade,but not exactly,becuse contain Knox BL/ bootloader/.
Wait wait you must go back to 4.1.2 version.Then if you want- you can flash back 4.4.4 downloaded from the official website of Samsung.
Use Odin ,but don`t forget to kill all Kies process before flashing.
Click to expand...
Click to collapse
Unfortunately that's not working. when flashing 4.4.4 through Odin I have the same result as before. Only the 4.1.2 from your link is working
Well,let.'s trying to flash first a 4.3 Stock rom thru Odin.Try using Odin 3.09 attached here.
viktorak said:
Well,let.'s trying to flash first a 4.3 Stock rom thru Odin.Try using Odin 3.09 attached here.
Click to expand...
Click to collapse
Unfortunately that's not working, I think because of the new bootloader. See Odin log below:
Code:
<ID:0/022> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXUEMKC_I9305DBTEMJ4_I9305XXUEMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Get PIT for mapping..
<ID:0/022> Firmware update start..
<ID:0/022> SingleDownload.
<ID:0/022> sboot.bin
<ID:0/022> NAND Write Start!!
<ID:0/022> FAIL!
<ID:0/022>
<ID:0/022> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ODIN on phone says: SW REV. CHECK FAIL. DEVICE:3. BINARY:2
Well, let's trying wipes Dalvic, cache and Factory reset,then flashing a Stock 4.4.4.
viktorak said:
Well, let's trying wipes Dalvic, cache and Factory reset,then flashing a Stock 4.4.4.
Click to expand...
Click to collapse
That brings me to the same fault as before - stuck at boot animation. Odin runs without error:
Code:
<ID:0/022> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXUFNI3_I9305DBTFNI3_I9305XXUFNI3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Get PIT for mapping..
<ID:0/022> Firmware update start..
<ID:0/022> SingleDownload.
<ID:0/022> sboot.bin
<ID:0/022> NAND Write Start!!
<ID:0/022> tz.img
<ID:0/022> boot.img
<ID:0/022> recovery.img
<ID:0/022> system.img
<ID:0/022> cache.img
<ID:0/022> hidden.img
<ID:0/022> modem.bin
<ID:0/022> RQT_CLOSE !!
<ID:0/022> RES OK !!
<ID:0/022> Removed!!
<ID:0/022> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Now enter recovery mode and make wipe cache, Dalvik and data again and reboot.
viktorak said:
Now enter recovery mode and make wipe cache, Dalvik and data again and reboot.
Click to expand...
Click to collapse
Already did that but no change
Now you have a Rom flashed .The problem is that can't boot. In this momment I'm not at home.I can be online later.
---------- Post added at 04:29 PM ---------- Previous post was at 04:24 PM ----------
After sucsessful flashed Rom you must be directly enter to Recovery to make all wipes and finaly reboot...
Well,jon192694,let`s trying this.Repeat this step: wipes Dalvic, cache and Factory reset,then flashing a Stock 4.4.4,in Odin uncheck Auto reboot,and when the installation is sucsessfuly terminated:<OSM> All threads completed. (succeed 1 / failed 0),remove the battery/30sec/,enter in recovery and wipe Dalvic cache,cache and data,reboot.
viktorak said:
Well,jon192694,let`s trying this.Repeat this step: wipes Dalvic, cache and Factory reset,then flashing a Stock 4.4.4,in Odin uncheck Auto reboot,and when the installation is sucsessfuly terminated:<OSM> All threads completed. (succeed 1 / failed 0),remove the battery/30sec/,enter in recovery and wipe Dalvic cache,cache and data,reboot.
Click to expand...
Click to collapse
I will try that now - the only problem is that I can't wipe dalvic after flashing because the stock recovery tool isn't offering this option.
viktorak said:
Well,jon192694,let`s trying this.Repeat this step: wipes Dalvic, cache and Factory reset,then flashing a Stock 4.4.4,in Odin uncheck Auto reboot,and when the installation is sucsessfuly terminated:<OSM> All threads completed. (succeed 1 / failed 0),remove the battery/30sec/,enter in recovery and wipe Dalvic cache,cache and data,reboot.
Click to expand...
Click to collapse
There is no change still stuck on boot animation. I did it as you sugested the only thing I didn't do was wiping dalvic. I later installed cusrom recovery to repeat it including wiping dalvic but no change
I did some more testing, omni 4.4.4 is not working neither the most recent cm 11 nightly. What is working is cm 10.1.
So I have the impression my phone will only work with Android 2.1.2 systems?
Would usage of Mobile Odin make any difference?
jon192694 said:
I did some more testing, omni 4.4.4 is not working neither the most recent cm 11 nightly. What is working is cm 10.1.
So I have the impression my phone will only work with Android 2.1.2 systems?
Would usage of Mobile Odin make any difference?
Click to expand...
Click to collapse
Hi,jon192694.Yes, you have to try things, as long as they are properly made.Try to flash 4.4.4 using Odin mobile.Here you have the thread on XDA- http://forum.xda-developers.com/showthread.php?t=1347899.
Has nobody experienced anything similar? I tink I now almost tried everything possible. Would be strange if I am the only one with this effect.
I am thinking about staying at the modified 4.1.2 or send it in to repair service...