Hello all,
I have a sg-n7000. And i was trying to put another rom on it.
I downloaded odin mobile because the pc odin did not past further then ''zimage''.
I selected abys kernel. (i have a lpy kernel on android 4.03. this is ICS?)
after i executed the file, my note restarted. And didn't past the samsung boot screen.
it's still possible to enter download mode & clok workmod recovery v5.8.1.5. (entered by pressing volume up, home and power button)
I went to cwm and selected wipe data. it's still possible to enter cwm and download mode.
But i don't know what to do, to recover to a working phone. At this point it doesn't matter to me if it's going back to stock rom or to custom rom. As long as get's back to live.
Please who can help me.
many thanks
bearhunt said:
Hello all,
I have a sg-n7000. And i was trying to put another rom on it.
I downloaded odin mobile because the pc odin did not past further then ''zimage''.
I selected abys kernel. (i have a lpy kernel on android 4.03. this is ICS?)
after i executed the file, my note restarted. And didn't past the samsung boot screen.
it's still possible to enter download mode & clok workmod recovery v5.8.1.5. (entered by pressing volume up, home and power button)
I went to cwm and selected wipe data. it's still possible to enter cwm and download mode.
But i don't know what to do, to recover to a working phone. At this point it doesn't matter to me if it's going back to stock rom or to custom rom. As long as get's back to live.
Please who can help me.
many thanks
Click to expand...
Click to collapse
Just try and enter download mode and flash stock rom. You gonna be alright, trust me.
Aluyi said:
Just try and enter download mode and flash stock rom. You gonna be alright, trust me.
Click to expand...
Click to collapse
Ok, does it matter which stock rom. because i had the lky kernel.
1. I'm downloading now "N7000XXLPY_N7000XENLP1_XEN.zip" on http://forum.xda-developers.com/showthread.php?t=1424997
is this a good one?
So long as its stock it shouldnt matter, You should try to get the original one your phone came with, Or as close as possible.
I believe the issue is the kernel, You could try to flash another one before going down the route of restoring to stock.
Give speedmod a try, if it fails to boot still, then flash stock GB
azzledazzle said:
So long as its stock it shouldnt matter, You should try to get the original one your phone came with, Or as close as possible.
I believe the issue is the kernel, You could try to flash another one before going down the route of restoring to stock.
Give speedmod a try, if it fails to boot still, then flash stock GB
Click to expand...
Click to collapse
Ok, my note came with gb. And was updated by KIES.
And it has the lpy kernel. I believe this one was a unstable version.
In odin i get this:
<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> zImage
and it hangs on zimage. doesn't more.
What now.
how long has it been stuck like that for ? if anything was to fail it would be datafs or factoryfs. Its weird that its sticking on the kernel.
Have you tried to flash stock kernel in ODIN, and then the firmware on top ?
azzledazzle said:
how long has it been stuck like that for ? if anything was to fail it would be datafs or factoryfs. Its weird that its sticking on the kernel.
Have you tried to flash stock kernel in ODIN, and then the firmware on top ?
Click to expand...
Click to collapse
the first time i used odin, downloaded abys kernel as it would be a safe kernel. It hung for 45 min.
the second time, i downloaded the N7000XXLPY_N7000XXLPT_N7000XENLP1_HOME.tar.md5. And it hung.
And if i'm right i cant put that file on de sd card and install from cwm.
close KIES and try again with pc odin.
praetorius said:
close KIES and try again with pc odin.
Click to expand...
Click to collapse
i'm on a different computer without KIES. I installed samsung usb driver.
Ok,
i downloaded the stockrom.
Went to annother pc.
Started odin up.
Selected the downloaded tar file with the pda button.
did select only reboot & reset time.
hit start.
it went further now. But in the end. odin gave a red flashin fault.
Is it now bricked?
Could be a communication error with the device...
As mentioned Hard brick would usually hang on FactoryFS or Data..
Try rebooting your PC
Use an alternate USB port and retry..
Hi all,
Thanx all. I managed to get a gb xxkk5 running on the note.
I went to another computer.
And used odin.
selected:
- pit file (downloaded from here)
- stockrom (downloaded from sammobile)
removed sd card and sim card.
hit start.
Now he is in configure mode of a new samsung account.
Again, thanks.
Related
Hi, I have rooted my tab ,no problem. But I read all the posts about EXT4 and kernel flashing needed for flashing roms, but I cannot find a definitive guide on how to flash the kernel using odin or EXT4.
Can anyone help with a small , simple guide on how to do this please?
I've been looking for hours and darent try it without knowing fully how.
Thanks
Stu.
Galaxy Tab UK
Recovery mod installed and Rom backed up.
Havent looked yet but i quick guide would be great if it doesnt already exist.
Sent from my HTC HD2 using XDA App
You can follow the instructions from this thread
http://forum.xda-developers.com/showthread.php?t=925760
Stu308 said:
Hi, I have rooted my tab ,no problem. But I read all the posts about EXT4 and kernel flashing needed for flashing roms, but I cannot find a definitive guide on how to flash the kernel using odin or EXT4.
Can anyone help with a small , simple guide on how to do this please?
I've been looking for hours and darent try it without knowing fully how.
Thanks
Stu.
Galaxy Tab UK
Recovery mod installed and Rom backed up.
Click to expand...
Click to collapse
Sent from my GT-P1000 using Tapatalk
Seen that post , but it doesnt say what to do with odin? As in where to load the .tar file etc.
You flash the Modaco kernel via Odin, if your file system isn't ext4 (which it won't be then you may need to manually reboot your phone - My phone still rebooted automatically coming from a rfs file system)
Once your phone reboots it should enter recovery automatically and you just sit back and let CWM backup / covert your file system to ext4 / restore your rom back on to your coverted file system
(I believe there are instance also when you phone does not automatically enter recovery on reboot, in this situation you will need to manually enter recover after flashing the kernel in Odin - to do this you hold down the power button and volume up)
Another thing worth noting, i had encountered an issue during the conversion process where CWM was not able to restore my existing rom, when this happens you can download a ext4 rom (i.e. modaco rom or overcome 1.1.3) and flash the file via CWM - i.e. you can leave the kernel and try another Rom.
Hope this helps.
thanks bendjlee, but how do I use odin? (where to put .tar file which mode should tab be in etc..).
Stu308 said:
thanks bendjlee, but how do I use odin? (where to put .tar file which mode should tab be in etc..).
Click to expand...
Click to collapse
under pda
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
This is what I get, doesnt work. Should I be in recovery or the phone in normal mode?
I also had "fail" in red in the left had box of odin, my tab is rooted and clockwork mod installed. What is wrong?
You'll need to put your tab to download mode first before connecting to your computer to odin. Turn on the tab with "volume down" held
Stu308 said:
I also had "fail" in red in the left had box of odin, my tab is rooted and clockwork mod installed. What is wrong?
Click to expand...
Click to collapse
Sent from my GT-P1000 using Tapatalk
ahh, will try it that way , but Im sure I tried that. Do I put phone in debugging mode before I go into download mode?
Download mode is different than recovery and debug. It would display an image of an android with a shovel. That is the mode you need to be in.
Even though the question was asked by someone else, these attempts to answer the question helped solve a similar problem on my side. Thanks!
OK, I flashed to a new ROM and would now like to flash back to the stock ROM due to some issues with the new ROM, but whenever I do it, I wind right back where I started, with the flashed ROM, not the stock ROM (2.1). I may have deleted a file that is needed to get back to stock. Is there such a file? I follow all the instructionals and everything works well, it just doesn't flash back to stock?
We would need allot more details in order to pinpoint where you are going wrong.
My best guess is that you are not being recognized by odin, you are clicking start and nothing is happening. How long is the odin flash taking?
CM7
Im using Odin 3 v1.00. With the Captivate, I go into download mode and Odin recognizes it. I get the following
<ID:0/009> Added!!
Then I click start and the list expands to
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> Removed!!
It says Reset up top, but when the phone reboots, it just reboots back to the Cognition 4.1.1 that I was running
I had this exact problem last night, I was trying to flash back to stock from a I9000 ROM I had installed and it wasn't running good for me. So I did what I had done in the past, I was using the Captivate ToolBox to flash back to stock, my phone would go into Download mode, but Odin never saw it. I thought that was odd, so I tried the regular Odin flash to stock as well, using the pulling the battery and holding down vol up and down and plugging in the USB. Still Odin didn't see my phone.... I then rebooted my computer, put my phone in download mode and plugged in into my computer and for some odd reason Windows said it was installing new drivers for my device. After it completed, Odin saw my phone and I was able to flash back to stock, so you could try that, it may help you.
EDIT...Oops, sorry not the same deal I had, sorry..
Try different usb port
Make sure odin is open first
Be aware of what build tourer phone is, located under battery something like 1008. If 1010 our higher don't use one click
If box in odin turns yellow and days "com#" then you are recognized if not you are not
Phone must be in dl mode
Correct drivers must be installed
CM7
Beowulf, you commented
YYou need to supply the firmware file to flash (click on the "PDA" button, and browse to where you downloaded it--you *did* download it, right?), and optionally the ".pit" file if you need to re-partition when you flash.
I think you are right, but what would I point to in order to flash back to stock? Where would I get it? I can find what to point to if I wanted to flash to Cognition 4.1.1 or one of the other custom ROM's, but I cant seem to find what file I can download/point to in order to restore to stock ROM.
mcord11758 said:
Try different usb port
Make sure odin is open first
Be aware of what build tourer phone is, located under battery something like 1008. If 1010 our higher don't use one click
If box in odin turns yellow and days "com#" then you are recognized if not you are not
Phone must be in dl mode
Correct drivers must be installed
CM7
Click to expand...
Click to collapse
I believe I installed the correct drivers (that allow me to connect to Odin) as I do get the yellow box and it says 0:[com9]. Phone is in download mode. Also, it says 1008 under the battery.
http://www.samfirmware.com/WEBPROTECT-i897.htm
You need to create an account. Jf6 put listed bottom page
ThaRide said:
Beowulf, you commented
YYou need to supply the firmware file to flash (click on the "PDA" button, and browse to where you downloaded it--you *did* download it, right?), and optionally the ".pit" file if you need to re-partition when you flash.
I think you are right, but what would I point to in order to flash back to stock? Where would I get it? I can find what to point to if I wanted to flash to Cognition 4.1.1 or one of the other custom ROM's, but I cant seem to find what file I can download/point to in order to restore to stock ROM.
Click to expand...
Click to collapse
CM7
I wound up following teh lead that Beowulf gave me as I was using the full blown Odin and not the 1 click. When I watched videos on how to flash back to stock, I did wonder why teh version I was using looked different. I had assumed that it was just a slightly newer version.
To make a long story short. Once I used the 1 click Odin, I flashed back to stock easily. Thanks to all for your help. Much appreciated.
I was good when I first got my Tab, and followed all best practices, and made a Roto Backup of my Tab right after rooting.
I just tried to flash my Roto Restore back, and now my Tab is messed up. On startup, it will flash some corrupted graphics and static, play the Samsung sound and then sit on a black screen until it shuts off.
Fortunately, I still seem able to boot to download mode.
This is the procedure I followed to Roto Restore:
adb push data.tar.gz /sdcard/data.tar.gz
adb shell su -c "tar -zxvf /sdcard/data.tar.gz"
adb reboot download
Click to expand...
Click to collapse
Then from a Linux system, I executed:
tar -cf mybackup.tar cache.rfs dbdata.rfs factoryfs.rfs modem.bin param.lfs zImage
Then I opened up Odin, connected in download mode, and flashed the tar as PDA, with all options default.
How do I fix my tab, and how do I restore my Roto Backup?
Hmm in case anyone is able to help, now the situation is slightly worse. I realized I had a .pit file in my Roto Backup folder that I had not accounted for, so I flashed that again via Odin/download mode together with the .tar as PDA.
Now Odin seems to be hung doing nothing with this text:
<ID:0/005> Added!!
<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!!
It's been like this for about 15 minutes now with no activity.
Any advice on what to do?
Is anyone able to help me?
After Odin sat there for 4 hours doing nothing, I finally closed it and turned off the Tab. Now I can no longer get to download mode, and whenever I turn it on, there's a picture of a cell phone and a picture of a computer with a yellow exclamation mark in between.
Okay, final update for today, I found out from another thread that if you're lucky it's still in download mode even though it you get the dreaded yellow triangle.
I was lucky.
I used the fact that Odin could still flash it to reflash to Team Overcome's European stock safe ROM. Not exactly where I wanted to end up, but I'm just happy my Tab isn't a brick.
I'm a little scared to try and use my Roto Backup again, can anyone advise me on what the proper way to use this is without turning your Tab into a brick?
If you are in download mode, just flash a JME or other froyo rom. You have to use a .pit file and check the repartition box.
Get your tab working, then work on getting it to stock.
rangercaptain said:
If you are in download mode, just flash a JME or other froyo rom. You have to use a .pit file and check the repartition box.
Get your tab working, then work on getting it to stock.
Click to expand...
Click to collapse
Yeah, it's working again now, I'm running Overcome's stock safe ROM which is JQ1 I believe.
How can I use my Roto Backup now to re-stock?
Not until you flash a froyo rom first, like I already told you above, or you will get the crazy rainbows from messed up bootloaders.
rangercaptain said:
If you are in download mode, just flash a JME or other froyo rom. You have to use a .pit file and check the repartition box.
Get your tab working, then work on getting it to stock.
Click to expand...
Click to collapse
so you say, flash stock rom froyo (lets say from samfirm)
use p1.pit (as it says in the site)
check the repartition
also to put the 'tar' (rom) file in pda and go?
after checking on my tab, that's a yes.
When you get your froyo rom flashed, and you confirm everything works, you must do this next step:
Go find the chainfire bootloader patch. Froyo roms have bootloaders that can make your tab dead.
With the bootloader safely patched, then you are free to do anything.
Hi
I was on RocketRom V5 and wanted to go back to GB
so i tried to install a stock GB rom using PC odin but it failed in the middle of the proccess
now the phone can only go to download mode
and if I tried to boot it or go to recovery mode it says "Frimware upgrade encountered an issue. please select recovery mode in kies & try again"
now every time i try to install a stock rom using PC odin it fails
and the useless kies is giving me an error like massage in chinese
so if there is a way to install any rom without using kies it will very helpful
max-thamer said:
Hi
I was on RocketRom V5 and wanted to go back to GB
so i tried to install a stock GB rom using PC odin but it failed in the middle of the proccess
now the phone can only go to download mode
and if I tried to boot it or go to recovery mode it says "Frimware upgrade encountered an issue. please select recovery mode in kies & try again"
now every time i try to install a stock rom using PC odin it fails
and the useless kies is giving me an error like massage in chinese
so if there is a way to install any rom without using kies it will very helpful
Click to expand...
Click to collapse
I too am facing the same situation. Hope someone comes up with a solution.
have you made a wipe while on ICS? was your phone booting normaly when you flashed it with PC ODIN?
try version 1.87 ,and if that doen't work then search for version 3 of ODIN
also do note that you should open task manager and shutdown any kies processes (usually two of them) ,kies will stop an ODIN flash ,so make sure to kill it first
i was really excited when i saw a reply i thought it was an answer
if you found a solution please post it here
max-thamer said:
i was really excited when i saw a reply i thought it was an answer
if you found a solution please post it here
Click to expand...
Click to collapse
it is an answer !!
kill KIES and you should have a smooth flashing ,unless you have corrupted your emmc by wiping on ICS of course
MR.change said:
have you made a wipe while on ICS? was your phone booting normaly when you flashed it with PC ODIN?
try version 1.87 ,and if that doen't work then search for version 3 of ODIN
also do note that you should open task manager and shutdown any kies processes (usually two of them) ,kies will stop an ODIN flash ,so make sure to kill it first
Click to expand...
Click to collapse
my phone was ok on rocketrom and it was booting ok until i tried to install a rom using PC odin
and i uninstalled kies completly to avoid any problems
i even tried odin 3 and still no luck
i will try odin 1.87 and reply back
MR.change said:
it is an answer !!
kill KIES and you should have a smooth flashing ,unless you have corrupted your emmc by wiping on ICS of course
Click to expand...
Click to collapse
i was referring to the post above you
as i said i uninstalled kies completely
and i was on speedmod kernel which its developer says he did something to the kernel which should prevent the emmc bug
is there a way to know for sure that i corrupted the emmc or not ?
when you uninstalled kies, drivers may have been affected. reinstall drivers and try again. if you can, use another pc.
Zapped through server hops to XDA forums
just tried PC odin 1.87 and no diffrence
when you uninstalled kies, drivers may have been affected. reinstall drivers and try again. if you can, use another pc.
Zapped through server hops to XDA forums
Click to expand...
Click to collapse
i tried to install the drivers again but it said the drivers are already installed
i think i will try another pc
max-thamer said:
i was referring to the post above you
as i said i uninstalled kies completely
and i was on speedmod kernel which its developer says he did something to the kernel which should prevent the emmc bug
is there a way to know for sure that i corrupted the emmc or not ?
Click to expand...
Click to collapse
yes speedmod is safe ,you have nothing to worry about a brick.
now there could be many things that effect a flash:
1.bad cable
2.running as a standard account (select run as administrator)
3.wrong set of drivers ,to resolve download and install the latest KIES ,then kill it's processes.
4.wrong ODIN version (1.87 recommended)
5.as a last resort you shold flash a pit file (but that's risky)
anyway go to this thread and download ODIN from there and flash a GB ROM
http://forum.xda-developers.com/showthread.php?t=1424997
note that the drivers are included in this thread if you do not wish to install KIES again.
just follow this guide to the letter and you should be fine.
i changed the cable with a brand new cable that was in the original package of the phone
run as administrator
reinstalled the drivers from DR.ketan thread
tried odin 1.85 & 1.87 & the new odin 3 that has a slightly diffrent cyan UI
so im afraid i need to take the risk (BTW, what are the risks ?)
and flash a pit file
so can you please tell the right way to flash a PIT file so i can avoid the risks
your help are greatly appreciated
so anybody has a sulotion for this ?
i have been searching for a solution till now with no luck
max-thamer said:
so anybody has a sulotion for this ?
i have been searching for a solution till now with no luck
Click to expand...
Click to collapse
If you can have it covered under warranty somehow, then try to seek help from SS service. Otherwise, the method in the thread below could be useful.
http://forum.xda-developers.com/showthread.php?t=1661590&page=2
cheers,
i think i will take to samsung service
thank you guys for helping
max-thamer said:
i changed the cable with a brand new cable that was in the original package of the phone
run as administrator
reinstalled the drivers from DR.ketan thread
tried odin 1.85 & 1.87 & the new odin 3 that has a slightly diffrent cyan UI
so im afraid i need to take the risk (BTW, what are the risks ?)
and flash a pit file
so can you please tell the right way to flash a PIT file so i can avoid the risks
your help are greatly appreciated
Click to expand...
Click to collapse
the risks could involve a permanent brick (not even download mod) , can you post exactly what ODIN says?
post ODIN log please
EDIT: maybe by any chance that you flashed an ICS bootloader? if so then it maybe the cause for this ,you should try to flash the official LPf using ODIN ,and if it works and the phone boots then flash Speedmod ics kernel on top of it (before wiping or anything).
here I found this pit file on the internet ,you need to choose your model (16gb or 32 gb) ,it's most likely 16gb ,right?
remember this is a last resort ,so don't use it
i will go with safer method and take it to samsung service :d
thanks anyway youve been a great help
EDIT :
sh*t , its a day off for samsung service
so ill live another day without my Gnote
this is ODIN log
<ID:0/009> Firmware update start..
<ID:0/009> cache.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
what do you think ?? flashing a .pit file would solve anything
and should i load a pit and a PDA file in odin or only .pit file ??
max-thamer said:
i will go with safer method and take it to samsung service :d
thanks anyway youve been a great help
Click to expand...
Click to collapse
if you still have warranty then by all means ,take it to the service center.
if you don't however then you should not give up this easily ,unless you have some cash lying around and you wish to give it to them.
either ways it's your call
good luck
max-thamer said:
i will go with safer method and take it to samsung service :d
thanks anyway youve been a great help
EDIT :
sh*t , its a day off for samsung service
so ill live another day without my Gnote
this is ODIN log
<ID:0/009> Firmware update start..
<ID:0/009> cache.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
what do you think ?? flashing a .pit file would solve anything
and should i load a pit and a PDA file in odin or only .pit file ??
Click to expand...
Click to collapse
weird ,it's failing to flash at factoryfs ,but it's not getting stuck during the operation.
I want you to try two things:
1.try to flash just a kernel ,try this http://forum.xda-developers.com/attachment.php?attachmentid=1068654&d=1337346991
this is the cm9 safe kernel ,if the flash with ODIN goes successful then you can boot into recovery and try to fire a nandroid restore from there
be careful flashing this with ODIN will give you a triangle and count ,so if you still have your warranty ,try to find and flash a stock kernel (which will not give you a triangle).
2.if none of the above works ,then select only the 16 GB pit file and flash it alone ,do not interrupt a pit file flash ,let it take as long as it wants . if you interrupt it then your phone is gone.
after that flash a full GB ROM with removing .pit and unticking repartition.
but I haven't done this before so if you want to go through with it I suggest you wait for someone with actual experience at this.
pit file
Here you go with 16 GB pit file
FIRST OF: Im not the typical n00b guy who joins a forum and ask my stupid ass question without any searching done before. Trust me, I've been searching around here, google and youtube for the past 2 days now. And yes, I have found some answers, but non that has worked for me. So please, no hating. If you guys are mad at me for some reason, or cant help me.. please just leave the thread. Thank you!
Ok, here we go..
Around xmas, my Galaxy Note broke. I couldn't charge it anymore. Well, 2 days ago I got it back, with some new chip installed plus the latest FW (4.0.4).
My GN was now "unrooted", so I thought "Hey, lets root this biatch and flash a rom". I like my phone in tablet mode so. So I used the classic cwm-method, yeah stupid me, and tried a rom (can't remember which.. anyhow, my phone got stuck in bootloop (samsung galaxy note-screen). Oh well, let's formatting data, wipe catch, wipe dalvik. Well everything went good until formatting data.. it froze and went back to bootloop.
I've tried flashing different Kernals, which seems to work cuz the recovery menu looks different. I'm right now on the latest Philz Kernal.
I've tried to flash like 4 different roms. The either freeze on flash (and jump back into bootloop), or complete flash and go back to bootloop.
So in conclusion..
- Have tried different Kernals
- Can go into "recovery menu" (vol up+power button+home)
- CAN'T "formatting data" (it freezes and jump back to bootloop)
- CAN wipe catch and dalvik
Any ideas?
Flash a stock rom with PC Odin.
If you get errors, make a snapshot.
Then there might be a chance to analyze
Sent from my GT-N7000 using xda premium
ThaiDai said:
Flash a stock rom with PC Odin.
If you get errors, make a snapshot.
Then there might be a chance to analyze
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thanks for kind and quick response!
4 (stupid) questions, just to be clear..
1) Which costum rom should I pick? I've looked around, but there's so many! And i don't wanna pick the wrong kind.
As I said before, I hade/have stock 4.0.4 before it went bye-bye
2) Which Kernal should I be on before I flash?
3) In what order should I flash (using Odin)? Kernal first?
4) Which version of Odin is the right one for me? (GN N-7000)
The one I have is "Odin v1.85"
ThanksĀ½!
Search for dr ketans thread for stock roms.. U have to download stock rom not custom rom. Just put the phone in download mode (volume down+power+home button) and flash stock rom using pc odin. No need to flash any kernel.
Sent from my GT-N7000 using xda app-developers app
treacherous_hawk said:
Search for dr ketans thread for stock roms.. U have to download stock rom not custom rom. Just put the phone in download mode (volume down+power+home button) and flash stock rom using pc odin. No need to flash any kernel.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I did, thanks. But it have been stuck at the last step "NAND write start"
For a couple of hours now
update
can't go into recovery mode. just asks me to connect to kies or what ever it's called. I can go into download mode, and that's where I am now.
Trying to flash N7000XXLT5_N7000XXLT3_N7000OXXLT2_HOME.tar but get stuck at "Factoryfs.img" all the time. Around 75%.
Have you tried uninstalling kies, and changing the USB cable and port too. Sounds silly but worked for me when I had this problem .......
Sent from my GT-N7000
PJ147 said:
Have you tried uninstalling kies, and changing the USB cable and port too. Sounds silly but worked for me when I had this problem .......
Sent from my GT-N7000
Click to expand...
Click to collapse
Different ports - yes
uninstalling kies - yes + re-install
different cable - trying now.. brb in 5 min.
same results with different cabe
<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> boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> factoryfs.img
Did you dammage it doing all that wiping on a stock kernel?
sent by reversed alien technology....
howard bamber said:
Did you dammage it doing all that wiping on a stock kernel?
sent by reversed alien technology....
Click to expand...
Click to collapse
yeah i think i did. Got my phone back from service unrooted and on 4.0.4
I wanted to root it, so I searched here.. and found "root with cwm.zip" something. The flash went well, but when i flashed a different rom something happend, so i thought "ok lets full wipe dalvik, cach and data", and that's when it all happend. Cant go into recovery mode. When i turn on the phone, i get that message that i need to connetct via usb to keis and choose recovery mode. I can however go into download mode.. trying to flash a stock rom via Odin, but it gets stuck in between 75-95% on factoryfs.img
_terror_ said:
yeah i think i did. Got my phone back from service unrooted and on 4.0.4
I wanted to root it, so I searched here.. and found "root with cwm.zip" something. The flash went well, but when i flashed a different rom something happend, so i thought "ok lets full wipe dalvik, cach and data", and that's when it all happend. Cant go into recovery mode. When i turn on the phone, i get that message that i need to connetct via usb to keis and choose recovery mode. I can however go into download mode.. trying to flash a stock rom via Odin, but it gets stuck in between 75-95% on factoryfs.img
Click to expand...
Click to collapse
Hmmm..after flashing cwm.zip, which rom ("flashed a different rom") did u flash? If you have wiped on stock ICS kernel, you might have bricked your device
Shyam said:
Hmmm..after flashing cwm.zip, which rom ("flashed a different rom") did u flash? If you have wiped on stock ICS kernel, you might have bricked your device
Click to expand...
Click to collapse
Yeah i think i did. Cuz i tried flashing paranoidandroid or what ever the name is. And i knew that they had a different bootloader. But after the flash (it said it was completet) i restared the phone, but the bootloader was still the same old samsung one. So i thought "huh, the flash didn't work after all. Better wipe everything and try again". So I guess i was on the stock 4.0.4 when i wiped.
So what if its bricked? Am i totally f:ed?
update
tried flashing stock rom on my other computer. same thing, odin freezes on the same place.
_terror_ said:
Yeah i think i did. Cuz i tried flashing paranoidandroid or what ever the name is. And i knew that they had a different bootloader. But after the flash (it said it was completet) i restared the phone, but the bootloader was still the same old samsung one. So i thought "huh, the flash didn't work after all. Better wipe everything and try again". So I guess i was on the stock 4.0.4 when i wiped.
So what if its bricked? Am i totally f:ed?
Click to expand...
Click to collapse
If the flash was complete, you were on paranoidandroid when you wiped & not on 4.0.4. Anyways, I will PM Ketan about this thread. He should be knowing what exactly the problem/solution is..
Shyam said:
If the flash was complete, you were on paranoidandroid when you wiped & not on 4.0.4. Anyways, I will PM Ketan about this thread. He should be knowing what exactly the problem/solution is..
Click to expand...
Click to collapse
well, when i'm under 'download mode' it says custom after rom. So i'm not on stock, thats for sure.
and the flash count is on 2.
UPDATE
fixed the brick with the help from this thread: http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
got into recovery mode, flashed philz kernal, and flashed paranoidandroid!
got the yellow triangle under the samsung logo followed by bootloop on paranoidandroid 3+.
will be posting more updates on my progress.
If you have philz kernel before flashing then there is nothing to worry about wiping, just reboot to recovery wipe cache, delvic cahce and data
If still reboot, i recommend to flash pure stock GB rom +wipe.
got it all to work. Still have that yellow triangle though.. "Triangle away" dont work. but the phone does so i dont care