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
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!
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
Hi,
I came from an LG 2x, so I thought rooting my device in order to have some extra authorizations was no big deal. I first tried with pc software Unlockroot, but it failed in the process.
Being my GB 236 Note quite dirty I wanted to do some extra backup and cleanup. So I googled and stopped at rootyourgalaxynote.com, I tried the first ROOT method, not working, I tried the second method with pc ODIN 3.04 and abyss kernel 42, ODIN says it worked, note reboots but it stops at Samsung galaxy Note Gt-N7000 with yellow triangle. shocked, I didnt really expect that! After reading a little bit else, I went to sammobile downloaded italian gb 236 stock (the version I had befor kernel flashing) and tried to flash with PC Odin. It Failed. Device still gets in download mode. But now I'm seriously worried. What can I do?
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty
strangermyself said:
Hi,
I came from an LG 2x, so I thought rooting my device in order to have some extra authorizations was no big deal. I first tried with pc software Unlockroot, but it failed in the process.
Being my GB 236 Note quite dirty I wanted to do some extra backup and cleanup. So I googled and stopped at rootyourgalaxynote.com, I tried the first ROOT method, not working, I tried the second method with pc ODIN 3.04 and abyss kernel 42, ODIN says it worked, note reboots but it stops at Samsung galaxy Note Gt-N7000 with yellow triangle. shocked, I didnt really expect that! After reading a little bit else, I went to sammobile downloaded italian gb 236 stock (the version I had befor kernel flashing) and tried to flash with PC Odin. It Failed. Device still gets in download mode. But now I'm seriously worried. What can I do?
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty
Click to expand...
Click to collapse
First you should t have flash abyss through odin since now you are not rooted and do t have the warranty too, the counter of flashes increased to 1 (look at the download mode small text), for rooting you can use chainfire's tool (in the cf-root kernel thread look for it in devolepment section) next get a stock rooted kernel and flash using the tool (read instructions).
For now use pc odin 1.87 and get a firmware 2.3.6 use the pc odin select the file on PDA and flash it, make sure phone is charged 100% and press start, if it doesn't work then uninstall drivers, reboot machine, reinstall them and kill kies process if present in task manager and then goto download mode connect USB and open pc odin wait for the port to be ready aka green and select file then start.... you should be fine its a soft brick afterall.
Sent from my GT-N7000 using Tapatalk 2
Yeah I know atm I don't have system nor root nor warranty.
I tried odin 1.87 with the stock rom from sammobile but at one point or another is it cache.img or factoryfs.img, it fails (I also uninstalled kies and drivers and reinstalled them, i also tried installing only drivers, for at&at note, but it doesn't let me). I'm gonna download another stock rom, I just hope in some way I soon solve the thing, given that I also don't know how much charge is left and if the phone still gets charged. it just displays an idle circle near an empty battery when connected to pc or A\C cable.
strangermyself said:
Yeah I know atm I don't have system nor root nor warranty.
I tried odin 1.87 with the stock rom from sammobile but at one point or another is it cache.img or factoryfs.img, it fails (I also uninstalled kies and drivers and reinstalled them, i also tried installing only drivers, for at&at note, but it doesn't let me). I'm gonna download another stock rom, I just hope in some way I soon solve the thing, given that I also don't know how much charge is left and if the phone still gets charged. it just displays an idle circle near an empty battery when connected to pc or A\C cable.
Click to expand...
Click to collapse
When connected to charger make sure phone is off the battery meter will show as soon as you connect, case it doesnt leave it for like 3 hours is fine... next about that ROM redownload. The package cleanup you temp directories in PC and try again if still goto recovery abyss I guess? Wipe everything and use the mount option and format partitions I would recommed you to have repartition but I dont have the file you can look for ot in forum its. PIT file download fireup odin select it in PIT section and see if repartitioning is shocked, of so select firmware as PDA and flash again.
Sent from my GT-N7000 using Tapatalk 2
REVERSiN said:
... if still goto recovery abyss I guess? Wipe everything and use the mount option and format partitions I would recommed you to have repartition but I dont have the file you can look for ot in forum its. PIT file download fireup odin select it in PIT section and see if repartitioning is shocked, of so select firmware as PDA and flash again.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thx for your prompt answer, but I really didn't catch this part, if it still fails I must go in recovery and wipe cache and dalvik cache?I don't have CWM installed as rooting was the first flashing I tried on NOTE, so I don't have recovery installed. Since it stopped in the middle of flashing factoryfs.img, my Note is now displaying sth like 'updrading went wrong, try recovery mode in Kies': can it help in anyway? The PIT file and procedure are the same that are used for the EMMC bug?
strangermyself said:
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty
Click to expand...
Click to collapse
If you are stcuk at factoyfs.img I think you have got a super Brick
use this link and follow the instructions given.. Worked for me
http://forum.xda-developers.com/showthread.php?t=1682444
Whiskeyjack4855 said:
If you are stcuk at factoyfs.img I think you have got a super Brick
use this link and follow the instructions given.. Worked for me
http://forum.xda-developers.com/showthread.php?t=1682444
Click to expand...
Click to collapse
Dude its a GB rom not superbrick bug in it and he didn't mention LPY yet.
Sent from my GT-N7000 using Tapatalk 2
strangermyself said:
Thx for your prompt answer, but I really didn't catch this part, if it still fails I must go in recovery and wipe cache and dalvik cache?I don't have CWM installed as rooting was the first flashing I tried on NOTE, so I don't have recovery installed. Since it stopped in the middle of flashing factoryfs.img, my Note is now displaying sth like 'updrading went wrong, try recovery mode in Kies': can it help in anyway? The PIT file and procedure are the same that are used for the EMMC bug?
Click to expand...
Click to collapse
Sorry for tea doubled post its a dumb app X's
You wipe using the CWM file in the Iss root section, and a normal recovery wipe would do too (aka restore defaults)
Sent from my GT-N7000 using Tapatalk 2
Hi REVERSIN,
Thx. I was starting to fear it could be sth more than a soft brick. Can the initial use of unlockroot have caused anything (at least a week ago, Note still working after that)?
Sorry but I really can't understand what procedure should I follow since these initial attempts at flashing stocks failed. Should I try to flash CWM? What is the ISS root section (is it in the forum)? Where can i do a normal recovery wipe from? CWM I guess..
THX for your help
strangermyself said:
Hi REVERSIN,
Thx. I was starting to fear it could be sth more than a soft brick. Can the initial use of unlockroot have caused anything (at least a week ago, Note still working after that)?
Sorry but I really can't understand what procedure should I follow since these initial attempts at flashing stocks failed. Should I try to flash CWM? What is the ISS root section (is it in the forum)? Where can i do a normal recovery wipe from? CWM I guess..
THX for your help
Click to expand...
Click to collapse
If you have the stock recovery, restore default wipes everything.
If you have stock re every and want CWM temporary just to wipe goto n7000 devolepment and check how to root by dr.ketan and get files there
If you have CWM then wipe data, wipe cache, wipe dalvik.... and try. Old download another firmware like kk5.... something else not the new LC1 LX1 releases.... (Latest GB) get an old one to get root easly
Sent from my GT-N7000 using Tapatalk 2
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.
hello everyone
my friend bricked his note and i don't know what to do for him, my friend has no exper experience, he did a restore on a nonsafe kernel
his phone is semi bricked (if not fully bricked), i tried using odin to flash a stock rom (gb then ics) but had no luck and proccess stops at "NAND write start", i tried only to flash a kernel which was abyssnote but also got stuck on "NAND write start" and i tried to use the pit file from this post (http://forum.xda-developers.com/showthread.php?t=1667886) with a stock rom and with re-partition checked on odin and now it is stuck on:
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
please help me as the phone has been stuck on this state (pit file way) for over 80 minutes
waiting for your answer...
i unpluged my phone now and i am trying a custom pit file (N7000_16GB_Q1_20110914--patched--brick-between-281-and-3770-MB--FACTORYFS-moved-by-3328-MiB.pit) after leaving my phone for up to 2 hours and with no progress using N7000_16GB_Q1_20110914-stock.pit
file, hope i can revive my friend phone and please try to point me for any solution i can try.
Check your connection. Usually if bricked the process will start ok but halt at factory.fs. Try with a different usb cable, make sure it's in a mobo usb port not front one.
Pit files should be a last resort. I don't think it's bricked personally. Does it power on at all?
Sent from my GT-N7000 using xda app-developers app
SpyderTracks said:
Check your connection. Usually if bricked the process will start ok but halt at factory.fs. Try with a different usb cable, make sure it's in a mobo usb port not front one.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
how can i use mobie odin if i can't even access phone nor recovery?
hope there is a way
darkelfa2 said:
how can i use mobie odin if i can't even access phone nor recovery?
hope there is a way
Click to expand...
Click to collapse
Yeah, edited afterward.
Sent from my GT-N7000 using xda app-developers app
come on people... there most be someone who knows what i should do, please help
SpyderTracks said:
Check your connection. Usually if bricked the process will start ok but halt at factory.fs. Try with a different usb cable, make sure it's in a mobo usb port not front one.
Pit files should be a last resort. I don't think it's bricked personally. Does it power on at all?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
when odin get stuck on nand write start, the box above the port number with yellow mark says factoryfs, and yes the phone can olny boot to download mode
darkelfa2 said:
when odin get stuck on nand write start, the box above the port number with yellow mark says factoryfs, and yes the phone can olny boot to download mode
Click to expand...
Click to collapse
What is the outcome of flashing the "N7000_16GB_Q1_20110914--patched--brick-between-281-and-3770-MB--FACTORYFS-moved-by-3328-MiB.pit" as you mentioned above?
If you can also get into recovery, then better try to use hg42 partition scanner first, to see if and where the damage is in the emmc.
http://forum.xda-developers.com/showthread.php?t=1823918
forest1971 said:
What is the outcome of flashing the "N7000_16GB_Q1_20110914--patched--brick-between-281-and-3770-MB--FACTORYFS-moved-by-3328-MiB.pit" as you mentioned above?
If you can also get into recovery, then better try to use hg42 partition scanner first, to see if and where the damage is in the emmc.
http://forum.xda-developers.com/showthread.php?t=1823918
Click to expand...
Click to collapse
phone been on odin for about 40 minutes or so (is that normal?) but stuck on set partition and as i mentioned above, i cant access my phone nor recovery but i can access download mode.
darkelfa2 said:
phone been on odin for about 40 minutes or so (is that norma?l) but stuck on set partition and as i mentioned above, i cant access my phone nor recovery but i can access download mode.
Click to expand...
Click to collapse
If that long, then that pit doesn't seem to work.
I would try to flash a custom kernel such as hydracore or some other kernel that are available in .tar format. Then see if it help the phone get into recovery.
If that does not work, then just need to try other pit file from hg42 thread which move factoryfs by bigger number until it work. This is not a good strategy but it seems to be the only way.
---------- Post added at 11:29 PM ---------- Previous post was at 11:19 PM ----------
This is a gb kernel that can be flashed via odin to see if recovery works.
http://www.mediafire.com/?smwswkxwa3u3p4s
forest1971 said:
If that long, then that pit doesn't seem to work.
I would try to flash a custom kernel such as hydracore or some other kernel that are available in .tar format. Then see if it help the phone get into recovery.
If that does not work, then just need to try other pit file from hg42 thread which move factoryfs by bigger number until it work. This is not a good strategy but it seems to be the only way.
---------- Post added at 11:29 PM ---------- Previous post was at 11:19 PM ----------
This is a gb kernel that can be flashed via odin to see if recovery works.
http://www.mediafire.com/?smwswkxwa3u3p4s
Click to expand...
Click to collapse
i got stuck on NAND write start agine, i think its time to try your other strategy, should i go with pit file that has factoryfs moved by the largest number first or the one with the less number?
darkelfa2 said:
i got stuck on NAND write start agine, i think its time to try your other strategy, should i go with pit file that has factoryfs moved by the largest number first or the one with the less number?
Click to expand...
Click to collapse
I would try the first way of flash a kernel since it does not take much time.
Anyway, if want to try second strategy should move up by 500 mb or 1 gb each time.
I saw some people reported problem after flashing a pit with big number them move back to flash a pit with small number so should try to avoid that situattion.
The next pit I would choose it the one move fatoryfs by 4608mib for example.
forest1971 said:
I would try the first way of flash a kernel since it does not take much time.
Anyway, if want to try second strategy should move up by 500 mb or 1 gb each time.
I saw some people reported problem after flashing a pit with big number them move back to flash a pit with small number so should try to avoid that situattion.
The next pit I would choose it the one move fatoryfs by 4608mib for example.
Click to expand...
Click to collapse
thank you for your replies, i will try to try them as you mentioned above and by the way and will wait 15-20 minutes in each operation, i already tried the last version of hydracore but had no success, one last thing, if none of them worked (hope not), is there any other possible way to revive from the brick(other than replacing the motherboard or replacing the phone from samsung)?
bricked or not
same problem here, was on stock ics rooted for quite sometime, today decided to flash alliance rom v2.1, booted to cwm recovery, did a full wipe and after that i just hated myself. phone didnt boot into recovery and odin gets stucked at factoryfs, tried to flash with pit file too but no result same stuck in problem. then i flashed different kernel fm note kernel through odin which was a success, got my recovery back but unfortunately the only rom i have on internal sd was alliance rom which doesnt install, either says emmc error alliance rom or stucks at extracting system. so again flashed abyss kernel and did a full wipe again but odin still does not go beyond factory fs and i am trying to flash ics rom again. any idea what i should do now as i can flash a kernel and go into recovery. help will be appreciated. meanwhile downloading gb rom to check as i read in other posts it works tough not sure.
sahil4u said:
same problem here, was on stock ics rooted for quite sometime, today decided to flash alliance rom v2.1, booted to cwm recovery, did a full wipe and after that i just hated myself. phone didnt boot into recovery and odin gets stucked at factoryfs, tried to flash with pit file too but no result same stuck in problem. then i flashed different kernel fm note kernel through odin which was a success, got my recovery back but unfortunately the only rom i have on internal sd was alliance rom which doesnt install, either says emmc error alliance rom or stucks at extracting system. so again flashed abyss kernel and did a full wipe again but odin still does not go beyond factory fs and i am trying to flash ics rom again. any idea what i should do now as i can flash a kernel and go into recovery. help will be appreciated. meanwhile downloading gb rom to check as i read in other posts it works tough not sure.
Click to expand...
Click to collapse
it is good as far as you can access cwm recovery, try to get any external sd, download a rom and put it on the external sd using other phone
and flash it using cwm and dont forget your safe kernel , and can you tell me please what kernel you've used?
sahil4u said:
same problem here, was on stock ics rooted for quite sometime, today decided to flash alliance rom v2.1, booted to cwm recovery, did a full wipe and after that i just hated myself. phone didnt boot into recovery and odin gets stucked at factoryfs, tried to flash with pit file too but no result same stuck in problem. then i flashed different kernel fm note kernel through odin which was a success, got my recovery back but unfortunately the only rom i have on internal sd was alliance rom which doesnt install, either says emmc error alliance rom or stucks at extracting system. so again flashed abyss kernel and did a full wipe again but odin still does not go beyond factory fs and i am trying to flash ics rom again. any idea what i should do now as i can flash a kernel and go into recovery. help will be appreciated. meanwhile downloading gb rom to check as i read in other posts it works tough not sure.
Click to expand...
Click to collapse
Once get recovery it is best to try to scan partition to identify where the damage is. You can you adb method in my manual repartition guide or the scanner from hg42 which is even better.
Sent from my phone
---------- Post added at 06:30 AM ---------- Previous post was at 06:25 AM ----------
darkelfa2 said:
thank you for your replies, i will try to try them as you mentioned above and by the way and will wait 15-20 minutes in each operation, i already tried the last version of hydracore but had no success, one last thing, if none of them worked (hope not), is there any other possible way to revive from the brick(other than replacing the motherboard or replacing the phone from samsung)?
Click to expand...
Click to collapse
Should try the kernel I sent and also the fm kernel suggested in the post above. Once having recovery it is much easier and there are more options. Otherwise, custom pit is the last resort before mobo replacement.
Sent from my phone
sahil4u said:
same problem here, was on stock ics rooted for quite sometime, today decided to flash alliance rom v2.1, booted to cwm recovery, did a full wipe and after that i just hated myself. phone didnt boot into recovery and odin gets stucked at factoryfs, tried to flash with pit file too but no result same stuck in problem. then i flashed different kernel fm note kernel through odin which was a success, got my recovery back but unfortunately the only rom i have on internal sd was alliance rom which doesnt install, either says emmc error alliance rom or stucks at extracting system. so again flashed abyss kernel and did a full wipe again but odin still does not go beyond factory fs and i am trying to flash ics rom again. any idea what i should do now as i can flash a kernel and go into recovery. help will be appreciated. meanwhile downloading gb rom to check as i read in other posts it works tough not sure.
Click to expand...
Click to collapse
Hi there, sounds like a bad flash or bad download. Firstly remove your external micro SD card and connect it to a PC / Laptop (standard SD adaptor or Card Reader). Download a "default" ROM and kernel and KEEP them on the card (you never know when you need to go back to them). I use Abyss 4.2 kernel and Chrack ROM personally. I always have the jBroid Kernel Cleaner saved also). Replace the micro SD card.
If you can get into Recovery, flash the jBroid script cleaner. Now flash Abyss 4.2 kernel (GB safe kernel) and reboot into Recovery again. Now flash Chrack Rom. I've had a number of bad flashes and these 3 zips have always pulled me out a hole.
Hope this helps. Hit Thanks if it did.
Alba Donzo said:
Hi there, sounds like a bad flash or bad download. Firstly remove your external micro SD card and connect it to a PC / Laptop (standard SD adaptor or Card Reader). Download a "default" ROM and kernel and KEEP them on the card (you never know when you need to go back to them). I use Abyss 4.2 kernel and Chrack ROM personally. I always have the jBroid Kernel Cleaner saved also). Replace the micro SD card.
If you can get into Recovery, flash the jBroid script cleaner. Now flash Abyss 4.2 kernel (GB safe kernel) and reboot into Recovery again. Now flash Chrack Rom. I've had a number of bad flashes and these 3 zips have always pulled me out a hole.
Hope this helps. Hit Thanks if it did.
Click to expand...
Click to collapse
i've already mentioned that it has no recovery mode, and yes, i always have abyssnote kernel in my ex-sd also in my friend's phone, the thing is that he don't know about the emmc bug and he did a restore on a none safe kernel and thats how he bricked his phone
what i've done so far is trying the pit file way but had no luck, now the thing is that the binary counter is 5 and i can't go to have a m/b replacement for free as the warranty is voided, is there any way to reset the counter or to hardbrick the phone except for the jig method?