Hello readers,
MY girlfriend decided that she wanted a costum ROM on her n7000. So she looked up how to do it on YouTube...
What she Tried to do was flash a kernel in stock recovery. She was on a ICS stock ROM, not rooted. And what she got was a phone that only went into download mode. When i turned it on it was stuck in the samsung screen. booting intoo recovery dint respond. Then she came to me. So i read on the xda forums that this might result in a bricked phone.
When i got it i tried tot flash speedmod 3k v13 kernel. Via PC Odin. It all completed normaly but the reboot (I know Odin a bit since i flash roms since the Sgs1 and now i still have an Sgs3.)
The problem we have now is that the cwmr v5.8.1.8 doesnt see the external SD. so i cant flash a rom of the sd. But now i am not shure if this is the emmc brick or my recovery doesnt support flashing from external SD cards. The SD card is good, tested it.
So if anyone knows what the best step from here is, please share it. I'm thinking about scanning For Bicked blocks. But i have never gone so far in computing. So im a bit scared of it.. XD Might reflash the kernel or update cwmr.
Download a stock Rom and try to install it with PC Odin.
If it stops with an error at factoryfs.img it is bricked.
If it succeeds you have a solid base for installing a Custom Rom (even if it is for your girl I wouldn't use a "costum" Rom).
ronnos said:
Hello readers,
MY girlfriend decided that she wanted a costum ROM on her n7000. So she looked up how to do it on YouTube...
What she Tried to do was flash a kernel in stock recovery. She was on a ICS stock ROM, not rooted. And what she got was a phone that only went into download mode. When i turned it on it was stuck in the samsung screen. booting intoo recovery dint respond. Then she came to me. So i read on the xda forums that this might result in a bricked phone.
When i got it i tried tot flash speedmod 3k v13 kernel. Via PC Odin. It all completed normaly but the reboot (I know Odin a bit since i flash roms since the Sgs1 and now i still have an Sgs3.)
The problem we have now is that the cwmr v5.8.1.8 doesnt see the external SD. so i cant flash a rom of the sd. But now i am not shure if this is the emmc brick or my recovery doesnt support flashing from external SD cards. The SD card is good, tested it.
So if anyone knows what the best step from here is, please share it. I'm thinking about scanning For Bicked blocks. But i have never gone so far in computing. So im a bit scared of it.. XD Might reflash the kernel or update cwmr.
Click to expand...
Click to collapse
I would first go to PhilZ thread
http://forum.xda-developers.com/showthread.php?p=31911620
Look for a kernel for ICS, any of the version 3.99 should do. Choose the tar file to flash it via odin. After that try go into recovery again to see if it works.
Sent from my phone.
forest1971 said:
I would first go to PhilZ thread
http://forum.xda-developers.com/showthread.php?p=31911620
Look for a kernel for ICS, any of the version 3.99 should do. Choose the tar file to flash it via odin. After that try go into recovery again to see if it works.
Sent from my phone.
Click to expand...
Click to collapse
Thank u for the reply. I will try it. I will keep u updated!
forest1971 said:
I would first go to PhilZ thread
http://forum.xda-developers.com/showthread.php?p=31911620
Look for a kernel for ICS, any of the version 3.99 should do. Choose the tar file to flash it via odin. After that try go into recovery again to see if it works.
Sent from my phone.
Click to expand...
Click to collapse
I tryed it, and it didnt flash. this is what i got:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XXLT5-OXX-5.03.0.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can u make anything of that?
It does not look good at all. I would try again with PhilZ 3.99 tar file.
Sent from my phone.
forest1971 said:
It does not look good at all. I would try again with PhilZ 3.99 tar file.
Sent from my phone.
Click to expand...
Click to collapse
Oke, so i un-installed kies, and un-installed the phone drives from my pc, then installed the drivers from the ''stock rom n7000'' post. i flashed the kernel again using odin for pc, gues what, it worked!
The booted up normaly and it also uses philz touch recovery normaly.
I installed the App root checker, and i have root acces.
Now i can just flash towards anything i want right? becuase i am now on a safe kernel?
Thanks alot for your help!
Good to know you can get back to safety. Yes. Just nees to read and follow rom installation guide carefully from respective rom that you want.
Sent from my phone.
forest1971 said:
Good to know you can get back to safety. Yes. Just nees to read and follow rom installation guide carefully from respective rom that you want.
Sent from my phone.
Click to expand...
Click to collapse
just flashed CM9.1 and its all good!!
I'm so happy, and my girlfriend says thanks!
ThaiDai said:
Download a stock Rom and try to install it with PC Odin.
If it stops with an error at factoryfs.img it is bricked.
If it succeeds you have a solid base for installing a Custom Rom (even if it is for your girl I wouldn't use a "costum" Rom).
Click to expand...
Click to collapse
thank u for your reply, but i fixed it whith the help of the other poster.
thanks again.
Flash cm 10.2, its newer & better
GT-N7000 cihazımdan Tapatalk 2 ile gönderildi
maktama said:
Flash cm 10.2, its newer & better
GT-N7000 cihazımdan Tapatalk 2 ile gönderildi
Click to expand...
Click to collapse
I will. Thanks.
Related
Please who can help me?
I installed the new rom ICS German, but when I tried to return to gingerbeard ODIN PC I get stuck at the following error
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000XXLC1_CL1003701_REV02_user_low_ship.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> boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> Sbl.bin
<ID:0/004> param.lfs
<ID:0/004> zImage
<ID:0/004> factoryfs.img
PLESEE my phone now not working
Does recovery still work for you?
Had the same similar problem when I flashed ICS with a friend of mine a few days ago. Been trying to find out how to fix the phone for a day and a half. Tryed to flash LA6 stockrom and a few other stockroms. But also kept hanging at factoryfs.img everytime. We also weren't able to get into recovery mode anymore, only download mode.
Last night my friend succeeded in getting recovery back operational again by flashing a file via Odin. Still haven't fixed the phone yet, but at least with recovery we'll stand a better chance I think.
So let me know if you still have recovery or not. If not, then I'll try uploading the file that he used to get recovery back for his N7000. At least that way you can try a factory reset or something like that. I'm not sure if I can upload something since that I'm still new here.
All with all, good luck.
Yes i have recovery
buy when i want install a room with install to zip.. not working grrr
did you flashed CF LPY kernel before?
thehackersz said:
did you flashed CF LPY kernel before?
Click to expand...
Click to collapse
yes if you want i can ...
edt: sorry ... i have bad english
I had it
_giggino_ said:
Yes i have recovery
buy when i want install a room with install to zip.. not working grrr
Click to expand...
Click to collapse
Same here.
Have you tryed a factory reset?
I've tryed it, but when I do it just hangs. Another friend of mine recommended me to wipe/format everything except "System".
Haven't tryed this yet though, so I'm not sure what will happen.
I will let you know the outcome later today.
i'm sure you did a cwm wipe while on LPY and now wants to go back to GB?
if so.... sorry to tell you are now a member of the "superbrick club".
when will people learn to read? it's NOT SAFE to do CWM wipe on LPY. DO NOT BELIEVE what others say "it's fine in my case, did it a hundred times". they are simply yanking your chains and they wait until somebody posts a new thread (like this) and off they go snickering in the darkness.
HAXTC said:
Same here.
Have you tryed a factory reset?
I've tryed it, but when I do it just hangs. Another friend of mine recommended me to wipe/format everything except "System".
Haven't tryed this yet though, so I'm not sure what will happen.
I will let you know the outcome later today.
Click to expand...
Click to collapse
ok i wait you.. but in the meantime I continue to seek a solution ...
_giggino_ said:
ok i wait you.. but in the meantime I continue to seek a solution ...
Click to expand...
Click to collapse
Be very careful, you don't have much trial & error room left. Let the next step be spot on and only do so if you are 100% sure. It's better to wait a few days for a good answer than hurry and end up with a brick. I had the exact same problem but the more possible solutions I tried the more the problems increased and since yesterday my Phone is officially a "brick". Because I've tried so much options I no longer can tell the difference what possibilities are OK and what are NOT OK. Lots of succes.
---------- Post added at 03:09 PM ---------- Previous post was at 03:02 PM ----------
praetorius said:
if so.... sorry to tell you are now a member of the "superbrick club".
when will people learn to read?
Click to expand...
Click to collapse
For a lot of "superbrick club members", including me, the problems started/harm was done when even the specialists on this forum were not completely sure what the cause of the problem was and what to do and what not. A few days ago reading threads didn't give consistent answers....that was also part of the problem. Mind you...I don't blame anyone but myself.
This happened before with Angelom's kernel and now again-
PC Odin stuck at Factoryfs.img== SUPERBRICK.
If you have a superbrick, you have kernel/download mode but you CANNOT write to certain blocks of memory card, so its a MOBO replacement!
Sorry guys!
when I tried to install another recovery I went out this screen
photo
anilisanil said:
This happened before with Angelom's kernel and now again-
PC Odin stuck at Factoryfs.img== SUPERBRICK.
If you have a superbrick, you have kernel/download mode but you CANNOT write to certain blocks of memory card, so its a MOBO replacement!
Sorry guys!
Click to expand...
Click to collapse
+1 totally agreed. At least in this thread there are no clueless naysayers that keep arguing that this case is recoverable.
Try to wipe it again but not in CWM but in stock recovery.
_giggino_ said:
when I tried to install another recovery I went out this screen
photo
Click to expand...
Click to collapse
who can help me?
Please i do not want to believe the brick
SquirtingCherry said:
Try to wipe it again but not in CWM but in stock recovery.
Click to expand...
Click to collapse
I tried .. The process takes a long time, is completed, but it always presents the same problem
I have read in another topic if flashing fails at Factoryfs.img then your eMMC is damaged and you have to get the motherboard replaced.
I see a lot of similarities with the problems I had. I think you're also having bad luck, sorry.
i can change kernel,
I can change recovery,
i can flash all but no factoryreset.img
i can entry in download mode...
i can entry in recovery mode...
:'( i'm cry not is possibile this.. my phone have 3 months
my count now is 6 what will I say to assistance?
now i have a stock recovery... stock modem and stock csc
_giggino_ said:
who can help me?
Please i do not want to believe the brick
Click to expand...
Click to collapse
I've the exact message before, that is when I try to flash something in cwmr not knowing that I've lost full root ... Have to flashed back to GB (Rooted Stock LC1) using PC Odin, I think PC Odin is your only option also ...
_giggino_ said:
i can change kernel,
I can change recovery,
i can flash all but no factoryreset.img
i can entry in download mode...
i can entry in recovery mode...
:'( i'm cry not is possibile this.. my phone have 3 months
my count now is 6 what will I say to assistance?
now i have a stock recovery... stock modem and stock csc
Click to expand...
Click to collapse
use a jig and reset your counter, go to samsung service and tell that your phone conked while updating via kies and act as if you had no idea whatsoever and you woke up to a dead phone, they will replace your mother board.
My Galaxy Note GT-N7000 was on CM10 last night and I followed Zedomax's rootgalaxynote.com GT-N7000 unrooting method and when I was installing the Mobile Odin Lite on my phone, it said it needs to download more add-on to be able to flash it, then all the sudden my internet connection was down, so I couldn't download it, but followed his instruction and tried wipe and factory reset, but it got stuck at formatting (no progress), then I flashed cm9 again, but it was stuck at cm9 boot logo, nothing else. Then I followed Zedomax's rootgalaxynote.com's first method using my Computer Desktop but
"<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DXKL1_N7000OLBKJ6_N7000DXKJ3_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> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> factoryfs.img
" it got stuck at here, no progress. The only thing I can do with my phone is that to either put on download mode or it says "Firmware upgrade encountered an isssue. Please select recovery mode in Kies & try again." Please help me with this friends. I am looking forward to your help. Thank you.
Khai.
you give not detail as needed. but nevermine, from the last part it seems you has bricked your phone.
i think you might need to refer "hg42" thread to revive your note.
Sad to be hear that.
Sent from my GT-N7000 using xda premium
immediately contact dr.ketan
khaino said:
My Galaxy Note GT-N7000 was on CM10 last night and I followed Zedomax's rootgalaxynote.com GT-N7000 unrooting method and when I was installing the Mobile Odin Lite on my phone, it said it needs to download more add-on to be able to flash it, then all the sudden my internet connection was down, so I couldn't download it, but followed his instruction and tried wipe and factory reset, but it got stuck at formatting (no progress), then I flashed cm9 again, but it was stuck at cm9 boot logo, nothing else. Then I followed Zedomax's rootgalaxynote.com's first method using my Computer Desktop but
"<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DXKL1_N7000OLBKJ6_N7000DXKJ3_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> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> factoryfs.img
" it got stuck at here, no progress. The only thing I can do with my phone is that to either put on download mode or it says "Firmware upgrade encountered an isssue. Please select recovery mode in Kies & try again." Please help me with this friends. I am looking forward to your help. Thank you.
Khai.
Click to expand...
Click to collapse
Contact dr.ketan for yr solution. He is the sweet n right person to guide u.
khaino said:
My Galaxy Note GT-N7000 was on CM10 last night and I followed Zedomax's rootgalaxynote.com GT-N7000 unrooting method and when I was installing the Mobile Odin Lite on my phone, it said it needs to download more add-on to be able to flash it, then all the sudden my internet connection was down, so I couldn't download it, but followed his instruction and tried wipe and factory reset, but it got stuck at formatting (no progress), then I flashed cm9 again, but it was stuck at cm9 boot logo, nothing else. Then I followed Zedomax's rootgalaxynote.com's first method using my Computer Desktop but
"<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DXKL1_N7000OLBKJ6_N7000DXKJ3_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> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> factoryfs.img
" it got stuck at here, no progress. The only thing I can do with my phone is that to either put on download mode or it says "Firmware upgrade encountered an isssue. Please select recovery mode in Kies & try again." Please help me with this friends. I am looking forward to your help. Thank you.
Khai.
Click to expand...
Click to collapse
the ever GOLDEN RULE: Don't ever ever attempt to WIPE data if your on a unsafe or on a stock ICS kernel. That's should be at the top of your list before you do anything on your phone. If you need to WIPE, make sure your already in a safe kernel or if you haven't still, then flash one.
Now going back on your perennial issue. The only thing you can and will do is FLASH a stock GB on download mode using PC ODIN. Yes Doc Ketan's thread/s have those old GB's ROM.. -> http://forum.xda-developers.com/showthread.php?t=1424997, follow it to a tee.
One added thing when your going to start to flash GB again... Pray, that it would not stuck back again at 'factoryfs.img'
Good luck bud!
No luck...yet.
letters_to_cleo said:
the ever GOLDEN RULE: Don't ever ever attempt to WIPE data if your on a unsafe or on a stock ICS kernel. That's should be at the top of your list before you do anything on your phone. If you need to WIPE, make sure your already in a safe kernel or if you haven't still, then flash one.
Now going back on your perennial issue. The only thing you can and will do is FLASH a stock GB on download mode using PC ODIN. Yes Doc Ketan's thread/s have those old GB's ROM.. -> http://forum.xda-developers.com/showthread.php?t=1424997, follow it to a tee.
One added thing when your going to start to flash GB again... Pray, that it would not stuck back again at 'factoryfs.img'
Good luck bud!
Click to expand...
Click to collapse
I spent two days straight working on it, but no luck. I think I am gonna contact Samsung and send it to them for the warranty and I don't know if they would know that I rooted it. But I am just gonna give a try. Please share your knowledge and thoughts. Thank you.
Reflash it with PC odin (Again? )... refer to Dr Ketan... I encounter same issues before, I just try try to reflash old GB... link at #4
khaino said:
I spent two days straight working on it, but no luck. I think I am gonna contact Samsung and send it to them for the warranty and I don't know if they would know that I rooted it. But I am just gonna give a try. Please share your knowledge and thoughts. Thank you.
Click to expand...
Click to collapse
Can you get the Note into Download mode?
If so, try using desktop Odin (latest desktop version not mobile version) and flash the Abyss 4.2 kernel. the Tar file is easily found on XDA. This is a GB kernel and should allow you to get into full Recovery. From there you can flash a new ROM as you are now on a safe kernel.
Tried that, but not sure about the latest desktop version.
Alba Donzo said:
Can you get the Note into Download mode?
If so, try using desktop Odin (latest desktop version not mobile version) and flash the Abyss 4.2 kernel. the Tar file is easily found on XDA. This is a GB kernel and should allow you to get into full Recovery. From there you can flash a new ROM as you are now on a safe kernel.
Click to expand...
Click to collapse
Hi, thank you for your message, I was on Abyskernel when I factory data reset, and tried to flash back to cm9 from cm10, but no luck. Then I used Odin3-v1.85 on desktop with Gingerbread Rom, it got stuck at factoryfs.img.. I have tried with different pc disabling firewall and anti virus. What is the latest desktop version of Odin that you know? What specific tar file do you know that is the best? Thank you again.
khaino said:
Hi, thank you for your message, I was on Abyskernel when I factory data reset, and tried to flash back to cm9 from cm10, but no luck. Then I used Odin3-v1.85 on desktop with Gingerbread Rom, it got stuck at factoryfs.img.. I have tried with different pc disabling firewall and anti virus. What is the latest desktop version of Odin that you know? What specific tar file do you know that is the best? Thank you again.
Click to expand...
Click to collapse
Latest Odin is 3.0.4
Sent from my GT-N7000 using xda app-developers app
khaino said:
Hi, thank you for your message, I was on Abyskernel when I factory data reset, and tried to flash back to cm9 from cm10, but no luck. Then I used Odin3-v1.85 on desktop with Gingerbread Rom, it got stuck at factoryfs.img.. I have tried with different pc disabling firewall and anti virus. What is the latest desktop version of Odin that you know? What specific tar file do you know that is the best? Thank you again.
Click to expand...
Click to collapse
your CM10 to CM9 downgrade sounds like a bad flash, it can happen. I would try Odin3 V3.05 with Abyss (search for "AbyssNotekernel42CWTouchOriginalLogo.tar" or go here - https://www.dropbox.com/s/yoe791qq3atbung/AbyssNotekernel42CWTouchOriginalLogo.tar).
this should allow you to install a safe kernel to flash from. if you can now access Recovery, then you can flash a ROM from there. I would use a Stock based one (I always recommend Chrack ROM or Criskelo), If you prefer, you can download a Stock tar file and use Odin but I would try downloading the latest Chrack ROM or Criskelo ROM, transferring it to your micro SD and flashing after you have installed the Abyss tar.
I hope this helps. Please hit Thanks if it did.
Question!
Alba Donzo said:
your CM10 to CM9 downgrade sounds like a bad flash, it can happen. I would try Odin3 V3.05 with Abyss (search for "AbyssNotekernel42CWTouchOriginalLogo.tar"
this should allow you to install a safe kernel to flash from. if you can now access Recovery, then you can flash a ROM from there. I would use a Stock based one (I always recommend Chrack ROM or Criskelo), If you prefer, you can download a Stock tar file and use Odin but I would try downloading the latest Chrack ROM or Criskelo ROM, transferring it to your micro SD and flashing after you have installed the Abyss tar.
I hope this helps. Please hit Thanks if it did.
Click to expand...
Click to collapse
You gave me the AbyssNotekernel, but the only thing my phone can now do when I turn on is either show a screen with "Firmware upgrade encounters an issue. Please select recovery mode in Kies and try again" or on download mode. Or is there any way I can use the Desktop Odin and try to install the AbyssNotekernel that you gave me? I really don't know bro. Thank you for the message, please let me know.
khaino said:
You gave me the AbyssNotekernel, but the only thing my phone can now do when I turn on is either show a screen with "Firmware upgrade encounters an issue. Please select recovery mode in Kies and try again" or on download mode. Or is there any way I can use the Desktop Odin and try to install the AbyssNotekernel that you gave me? I really don't know bro. Thank you for the message, please let me know.
Click to expand...
Click to collapse
Yes, the Abyss tar file is for use with Odin. install Odin on your PC, put the Note into Download and connect. Flash the tar file and wait for the Note to reboot (search for notes on how to flash with Odin if you're not 100% sure). you should now be able to use Recovery to flash a ROM from this safe kernel.
Just a quick question.
Alba Donzo said:
Yes, the Abyss tar file is for use with Odin. install Odin on your PC, put the Note into Download and connect. Flash the tar file and wait for the Note to reboot (search for notes on how to flash with Odin if you're not 100% sure). you should now be able to use Recovery to flash a ROM from this safe kernel.
Click to expand...
Click to collapse
Sorry I didn't explain in details, I am on pc Odin version 3.07 and clicked on PDA but the Abyss tar file is not appearing there even after unzipping it a couple of times on the desktop. Please let me know bro. Thank you for your response.
Khai.
khaino said:
Sorry I didn't explain in details, I am on pc Odin version 3.07 and clicked on PDA but the Abyss tar file is not appearing there even after unzipping it a couple of times on the desktop. Please let me know bro. Thank you for your response.
Khai.
Click to expand...
Click to collapse
.tar file is to be flashed with odin directly. It has an image inside and should not extract it. Should put the .tar file in one folder but not on desktop screen. Select pda box in odin and brow to the folder where you put .tar file. Should see it there.
BTW, if flash using CWM failed again, then should use hg42 scanner to check if there is partition damage.
http://forum.xda-developers.com/showthread.php?t=1823918
Update.
forest1971 said:
.tar file is to be flashed with odin directly. It has an image inside and should not extract it. Should put the .tar file in one folder but not on desktop screen. Select pda box in odin and brow to the folder where you put .tar file. Should see it there.
BTW, if flash using CWM failed again, then should use hg42 scanner to check if there is partition damage.
http://forum.xda-developers.com/showthread.php?t=1823918
Click to expand...
Click to collapse
Thanks for your patience on your instruction, I actually was able to flash the Abysskernel that you gave me with ODIN and it went straight to the recovery mode, but then I can't install anything, then I put it back to download mode and tried to flash a Gingerbread ROM, but as always it got stucked at factoryfs.img. What do you think I can do bro? Please let me know about it. Thank you.
Khai.
khaino said:
Thanks for your patience on your instruction, I actually was able to flash the Abysskernel that you gave me with ODIN and it went straight to the recovery mode, but then I can't install anything, then I put it back to download mode and tried to flash a Gingerbread ROM, but as always it got stucked at factoryfs.img. What do you think I can do bro? Please let me know about it. Thank you.
Khai.
Click to expand...
Click to collapse
It seem to show you have an emmc brick, although using the partition scanner will confirm. The options are to send to ss service for warranty or to revise using repartition. For warranty you will need to reset flash counter using a jig.
Sent from my phone
Update and question.
forest1971 said:
It seem to show you have an emmc brick, although using the partition scanner will confirm. The options are to send to ss service for warranty or to revise using repartition. For warranty you will need to reset flash counter using a jig.
Sent from my phone
Click to expand...
Click to collapse
Hi bro,
I flashed the Abysskernel again and it went to Samsung Galaxy Note GT-N7000 logo with big Triangle at the bottom and it then goes to Android system recovery <3e>, then it looks like there is no option for me to access the SD card, but its own 16GB storage it came with and that one has CM10 in it. Tried to flash that, but it says "E:failed to verify whole-file signature". If I attempt to claim for warranty will Samsung know that I rooted it after clearing the binary counts? Please let me know. Thank you for your instructions. If there is anything else you want me to try out, please let me know. Thank you.
Khai.
khaino said:
Hi bro,
I flashed the Abysskernel again and it went to Samsung Galaxy Note GT-N7000 logo with big Triangle at the bottom and it then goes to Android system recovery <3e>, then it looks like there is no option for me to access the SD card, but its own 16GB storage it came with and that one has CM10 in it. Tried to flash that, but it says "E:failed to verify whole-file signature". If I attempt to claim for warranty will Samsung know that I rooted it after clearing the binary counts? Please let me know. Thank you for your instructions. If there is anything else you want me to try out, please let me know. Thank you.
Khai.
Click to expand...
Click to collapse
Once reset flash counter the triangle will go and you can flash a stock kernel find link from dr.ketan toolbox, then it is ok to send to warranty.
Sent from my phone
Update.
forest1971 said:
Once reset flash counter the triangle will go and you can flash a stock kernel find link from dr.ketan toolbox, then it is ok to send to warranty.
Sent from my phone
Click to expand...
Click to collapse
Hi bro, it somehow managed to get on CWM and but any flashing was aborted. And tried to flash Criskelo, but got stuck at installing, no progress. What should I do? Thank you.
Just two options above, warranty or repartition.
Sent from my phone
Hello All
I have a GT 7000 with stock 4.1.2 on it and it is only rooted.
It told me it had downloaded firmware update which i pressed install ( not knowing I shouldn't have because of my note being rooted) , and in doing so it is now just showing the little android dude with the blue thing in his tummy going round
Pressing volume up, home, power button won't do anything.
I can only get it into odin mode ( volume down, home, power button )
I am a complete noob and not sure what to do to get my note to work.
A friend said I need to flash a new rom via odin and I cant find a clear guide on how to do that.
For I can't afford to brick my note.
Please help
Kindest regards
pipsqueak 22 ooox
You have to have the samsung drivers installed for odin to work.
To get a stock rom google for sammobile. There are all official formwares (You will have to register).
After that extract that file, run odin and select the pda file (extracted md5 file).
Flash it. After reboot go to stock cwm and wipe data.
You should be fixed now.
Sent from note, a phone like never before
Odin is the way to go and the only way. Use this link http://forum.xda-developers.com/showthread.php?t=1901191 it will show how to flash Philz kernel on your phone and then you will have cwm. After that you will have to get a cwm flashable Rom out of the android dev section and put on your sd card, usb mass storage my work in philz kernel if so just put Rom on card and flash through cwm. Then phone will work or find a guide on pc Odin for flashing stock n7000 roms they are out there
Sent from my GT-N7000 using XDA Premium 4 mobile app
This just happened to me!!
Thanks jakuburban for your advice.
Though i didn't need to "After reboot go to stock cwm and wipe data." or maybe i do.
I just let it finish booting etc and everything was working fine,everything intact and okey dokey.
Can anyone say why this happened and what to do about updates in the future please?
Thanks again guys.:laugh:
Yeah, you sometimes don't need to wipe data. I told You to do this to be 100% sure it will work.
For the future, You can't use official update if You have root (normally it should give You information that You can't update the os because "Your device has been modified"), as You don't have original cwm and it won't boot into cwm to update Your os.
Sent from note, a phone like never before
Okey dokey.
Thanks again for the info.
Still having Trouble
Hi Guys,
Thanks heaps for your advice
I did what you said jakuburban but odin would get through seemmed like it was almost there then hung/froze
this is what was in the Odin txt box
"
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5120XXCMI1_N5120VNZCMH5_N5120XXCMG7_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.."
and just hung/froze at that point well over an hour.
and unpluged it - can still only get into odin mode
Not sure what to do?
Is this where I have to flash a hole new Rom?
Im not sure how to do this as I was looking at putting cyanogenMod rom on but I was reading some where not all rom's come in .tar forms
and I downloaded the latest stable rom from cyanogenMod but it is a . zip
so im not sure what to do there?
Thanks heaps
pipsqueak 22
Hanging at that place means there is some problem with the connection between note and pc. Make sure you have all the drivers installed and use original USB cable and main USB ports.
zip file roms need to be installed using clockwork mod recovery.
nokiamodeln91 said:
Hanging at that place means there is some problem with the connection between note and pc. Make sure you have all the drivers installed and use original USB cable and main USB ports.
zip file roms need to be installed using clockwork mod recovery.
Click to expand...
Click to collapse
yes I Used the origianl USB cable and have the latest Usb driver
turned off my firewall and antivirus softwared ( on work desktop)
then tryed on my laptop using kies USB driver - still no luck
ooo
Pipsqueak22 i've PM'd ya.
Yes you WILL be flashing a new ROM in Odin.
Make sure it's the right ROM you need.:good:
Raggerty64 said:
Pipsqueak22 i've PM'd ya.
Yes you WILL be flashing a new ROM in Odin.
Make sure it's the right ROM you need.:good:
Click to expand...
Click to collapse
Thanks ooo
Please help me out guys.. Yesterday i installed Xperiacle's awesome N8XT ROM and while i updated all google apps i also Super Su app.. When i opened the Super Su app it asked me to updated Binaries and gave me 2 options, one via NORMAL method and other being via CWM or TWRP.. Since i have CWM i chose that and phone got restarted and its stuck in samsung logo ever since!..
I tried taking out the battery for a few mins that doesnt help..
I tried Pressing VOL UP + HOME + POWER but the its doesnt get into recovery!
Right now i am downloading Stock Rom and thinking of flashing it via ODIN.. Is that the only solution?..
Is there any other solution apart from this?..
Thanks in advance
P.S:- I didnt check into Developer options so i dont know whether USB Debugging was checked or not!!.. I suppose this may be a cause to this problem??..
If you can't get into recovery mode then better flash the rom using Odin.
@ Nokia Thanks for your reply
Currenly my mobile has Philz kernel but i doubt it it is in usable mode since i cant even get into it..
1) So do i have to flash philz kernel once again using odin before flashing stock Rom or after flashing stock Rom?..
2) Odin can only be used to flash Stock Roms rite?.. Custom Roms Can't be flashed using Odin right?..
Fight_note said:
@ Nokia Thanks for your reply
Currenly my mobile has Philz kernel but i doubt it it is in usable mode since i cant even get into it..
1) So do i have to flash philz kernel once again using odin before flashing stock Rom or after flashing stock Rom?..
2) Odin can only be used to flash Stock Roms rite?.. Custom Roms Can't be flashed using Odin right?..
Click to expand...
Click to collapse
1. Yes you have to flash philz kernel to get custom cwm recovery after flashing stock rom, you can also flash the .zip file of the philz kernel in stock rom.
2. Custom roms can easily be installed via philz recovery.
@ Treacherous Thanks man
Do i have to restore EFS?..
Fight_note said:
@ Treacherous Thanks man
Do i have to restore EFS?..
Click to expand...
Click to collapse
no
Just happen to see this post " http://forum.xda-developers.com/showpost.php?p=43707730&postcount=47 "
and apparently he too faced the same issue but he says, he resolved the issue by flashing hardcore.tar via odin!!.. Does anybody know where is this hardcore.tar file available?.. Thanks for your help..
Fight_note said:
Just happen to see this post " http://forum.xda-developers.com/showpost.php?p=43707730&postcount=47 "
and apparently he too faced the same issue but he says, he resolved the issue by flashing hardcore.tar via odin!!.. Does anybody know where is this hardcore.tar file available?.. Thanks for your help..
Click to expand...
Click to collapse
dont know what that is.. but look at the last line. Hes having problems.. you go the long and better way.
Well, i have downloaded the Stock rom and the Odin is stuck in the following message
" <ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DDLSC_N7000ODDLSC_N7000DDLS6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection.. "
Its been a while and i dont see a msg after setupconnection!.. Previously i tried using Odin vV3.09 and i received a FAIL msg but Dr.ketan in his guide uses Odin V 1.85.. So right now using 1.85 and stuck at setupconnection!.. Wonder whether the version of Odin will make any difference?!..
Would this normally take this much time to flash a stock rom via Odin?.. Thanks for your help..
No.. it should not make any difference.. Make sure all the kies processes are terminated and run odin as admin.. then use the main USB port. And yeah... reboot phone into download mode and retry,
Awesome! I did a quick research in Dr.ketan's thread and found this post " http://forum.xda-developers.com/showpost.php?p=41136158&postcount=6055 ".. You also gave me the same Advice .. So i disconnected and did as you guys suggested and now voila! Odin finished flashing the Firmware but i am facing a " Bootloop! "..
I also found out that this kernel " http://forum.xda-developers.com/showthread.php?t=2252977 " is great for touchwiz based roms and gives great battery life!.. So is it ok now to flash the kernel without minding the " Bootloop "??..
UPDATE:- Fixed the bootloop by going into recovery and Factory reset & wipe cache.. Now it works!
For boot loop you need to boot into recovery and wipe data. Yes that kernel is good.. but you can also try this
Oh my god! Thank you for the kernel link!.. Thanks a lot man!.. Between do you happen to know any TW based ROMs alive other than Arya MOD , ultimate Jellybean etc..??..
Fight_note said:
Oh my god! Thank you for the kernel link!.. Thanks a lot man!.. Between do you happen to know any TW based ROMs alive other than Arya MOD , ultimate Jellybean etc..??..
Click to expand...
Click to collapse
I don't know may man.. Just Aryamod is the most recent one with new updates going in..
Hi,
I have rooted my galaxy n7000 running on stock 4.1.2 DDLSC using the supersu. After root tried to install the cmw custom recovery but failed then tried to flash/install the philz custom recovery and its also failed. I have tried following options.
1. downloaded the .zip version of philz and tried to flash it using stock recovery "Update from external storage". When it was updating suddenly phone was getting turned off. Tried two to three times.
2. Also tried the ODIN v1.85 and v3+. downloaded the tar.md5 file matching to n7000, and when tried to flash it using ODIN two times it got struck at "SetupConnection: and 2 to 3 times it got failed. saying
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.12.8-n7000.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> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
please help me. any kind of your help will be greatly appreciated.
I am getting mad now.
(Phone is working fine not bricked)
Exactly what PhilZ kernel do you have downloaded?
this "philz_touch_6.12.8-n7000.tar.md5" i have downloaded from the site.
Rooted using Supersu.
My n7000 details are given below.
Model number
GT-N7000
Android version
4.1.2
Baseband version
N7000DDLs6
Kernal version
3.0.31-906407
[email protected] #3
SMP PREEMPT Web Mar 6 19:53:40 KST 2013
Build number
JZO54K.N7000DDLSC
Hope this help. I am still on stock. Just rooted with supersu and trying to install customer recovery.
What is the reason for other recovery?
What rom do you want to install?
User_99 said:
What is the reason for other recovery?
What rom do you want to install?
Click to expand...
Click to collapse
wanted to install the lollipop or kitkat.
Please guide me how to install philz or cmw recovery.
What am I doing wrong, why the philz is not getting flash using ODIN or stock recovery.
I have also tried the "flashify" app. and when flashing philz recovery its saying "Partition flashed successfully" but when going to recovery mode there I find stock recovery. Nothing is working.
you need to flash a custom kernel which includes the recovery. as far as i know it is not possible to flash recovery only with keeping stock kernel. philz provided several kernels for N7000 with appropriate recovery for many different android versions.
Zoomselection said:
wanted to install the lollipop or kitkat.
Please guide me how to install philz or cmw recovery.
What am I doing wrong, why the philz is not getting flash using ODIN or stock recovery.
I have also tried the "flashify" app. and when flashing philz recovery its saying "Partition flashed successfully" but when going to recovery mode there I find stock recovery. Nothing is working.
Click to expand...
Click to collapse
Get a philz kernel that matches your ROM build number. In your case its ddlsc. If you don't find that xxlta will also do.
I understand that need to download the kernal. just to confirm is it "Signed" .zip file of philz?
Last time I was rooted with the philz signed .zip file. Root was successfull but recovery was still stock. and when I flash the recovery using CWM App. my phone bricked. it was struck at samsung logo. Some how I flashed the stock rom and my note got a life.
Now this time I am scared to do the same. But still will give a try.
Right now my phone is rooted with supersu. To flash the philz kernal with recovery, Do i have to unroot first and then flash? Or I can flash without unrooting?
Thanks for suppoting. XDA is the good place for anyking of troublesooting and memebers here are best in supporting.
Can you please provide the url from where to download the philz kernal.
You can use the zip or tar file. Zip is preferred. You don't need to unroot.
Thanks you so much. was able to successful install the philz recovery
My phone is bricked due to my friend mistake. As per your suggestion I have downloaded the philz kernel. flashed it and philz recovery was installed. I was so happy, My friend asked to see the phone and I gave him. In my phone the "ClockWorkMod app" was installed from google play. My friend asked me whether he can backup the data or not. I said ok do it. He open the "ClockWorkMode app" and went to backup and clicked on it. it asked for the name of the backup. He have given the name and clicked on the ok button. Suddently phone got turned off and was struck at "Galaxy Note GT N7000" boot screen. I tried to do the power off using power button but again it was getting turned on automatically and getting struck at boot screen. Taken the battery out.
tried to go into recovery mode but was not able to go there. Only download mode is working. I flash the "Philz recovery" using ODIN.
and when reboot the phone got struck at same boot screen with an additional yellow triangle.
Can it be re-cover or it is hard brick? Please suggest something. I have downloaded the stock DDLC tar file from sammobile site. Do I need the partition .pit file? I tried to find out the partition .pit file for 16gb version but all links are broken.
Help me please.
Zoomselection said:
Thanks you so much. was able to successful install the philz recovery
My phone is bricked due to my friend mistake. As per your suggestion I have downloaded the philz kernel. flashed it and philz recovery was installed. I was so happy, My friend asked to see the phone and I gave him. In my phone the "ClockWorkMod app" was installed from google play. My friend asked me whether he can backup the data or not. I said ok do it. He open the "ClockWorkMode app" and went to backup and clicked on it. it asked for the name of the backup. He have given the name and clicked on the ok button. Suddently phone got turned off and was struck at "Galaxy Note GT N7000" boot screen. I tried to do the power off using power button but again it was getting turned on automatically and getting struck at boot screen. Taken the battery out.
tried to go into recovery mode but was not able to go there. Only download mode is working. I flash the "Philz recovery" using ODIN.
and when reboot the phone got struck at same boot screen with an additional yellow triangle.
Can it be re-cover or it is hard brick? Please suggest something. I have downloaded the stock DDLC tar file from sammobile site. Do I need the partition .pit file? I tried to find out the partition .pit file for 16gb version but all links are broken.
Help me please.
Click to expand...
Click to collapse
Ouch, try reflashing everything according to the previous instructions again. Remember to clear cache and do a factory reset after that, the Rom Manager aka ClockWorkMode app is kinda useless..
Back to life,
After bricking my phone I was in so much stress. Was thinking all the possible way like re-partition csc etc... then suddenly thought why not flashing the stock rom which is downloaded. Puts the phone in download mode. open the ODIN 1.85 connected the phone with pc and selected the stock DDLSC tar md5 file, taken a deep breath and remembered all the gods and clicked on the start button.
flashing started within 10 min it finished and phone re-booted. back to stock rom without loosing any kind of data. To my surprise all the app which was moved to external card was automatically detected and checked the sd phone memory and all my personal file and data with contacts and messages was available. Once again many many thanks to XDA and all of you.
Again rooted the phone with Philz kernel. LOL.
Can you please help me. How to do nandroid backup and whether it can be flash by ODIN or not.
Make a nandroid backup by booting into recovery and choosing backup. Or use an app like zipinstaller.
No odin cannot flash a nandroid backup. It has to be restored using recovery only.