Database Develop

[Q] LPY ICS downgrade to GB. Non wipe or full wipe?

So I am one of the "brave" souls who flashed ICS LPY via Mobile odin from Stock GB prerooted ROM. I flashed it together with cf 5.3 kernel. Its been 10 days now and i haven't had any problems but i was lucky that i haven't used CWR nor factory restore. So after reading all the warnings that LPY has a bug on eMMC i want to safely go back to Gingerbread.
Ive searched the forum and found a few methods (Mobile ODIN, PC ODIN, CWR) but i want to make sure that i don't get my device bricked (have no warranty). So my question is Should i choose Full Wipe or a non wipe option while getting back to GB? Or maybe wait a little longer and just try not to stress the I/O till the issue gets resolved?

yllivia said:
So I am one of the "brave" souls who flashed ICS LPY via Mobile odin from Stock GB prerooted ROM. I flashed it together with cf 5.3 kernel. Its been 10 days now and i haven't had any problems but i was lucky that i haven't used CWR nor factory restore. So after reading all the warnings that LPY has a bug on eMMC i want to safely go back to Gingerbread.
Ive searched the forum and found a few methods (Mobile ODIN, PC ODIN, CWR) but i want to make sure that i don't get my device bricked (have no warranty). So my question is Should i choose Full Wipe or a non wipe option while getting back to GB? Or maybe wait a little longer and just try not to stress the I/O till the issue gets resolved?
Click to expand...
Click to collapse
Full wipe everything just to have a clean gb rom to use afterwards. You don't want to have remains of other roms in there! Just to be sure!
Sent from my GT-N7000 using Tapatalk 2

yllivia said:
So I am one of the "brave" souls who flashed ICS LPY via Mobile odin from Stock GB prerooted ROM. I flashed it together with cf 5.3 kernel. Its been 10 days now and i haven't had any problems but i was lucky that i haven't used CWR nor factory restore. So after reading all the warnings that LPY has a bug on eMMC i want to safely go back to Gingerbread.
Ive searched the forum and found a few methods (Mobile ODIN, PC ODIN, CWR) but i want to make sure that i don't get my device bricked (have no warranty). So my question is Should i choose Full Wipe or a non wipe option while getting back to GB? Or maybe wait a little longer and just try not to stress the I/O till the issue gets resolved?
Click to expand...
Click to collapse
you can use ODIN to flash stock GB ROM! but there are some reports that even that can cause superbrick! read this:
http://forum.xda-developers.com/showthread.php?t=1653582
you can read this thread how to do it using abyssnote kernel:
http://forum.xda-developers.com/showpost.php?p=24535533&postcount=2
and for some more info read this thread:
http://forum.xda-developers.com/showthread.php?t=1659768
hope this helps and good luck!
btw: I was on i9220ZCLP1 kernel and flashed stock GB ROM with ODIN and everything went fine!
Flash this one for wipe:
http://forum.xda-developers.com/showthread.php?t=1552435

yllivia said:
So I am one of the "brave" souls who flashed ICS LPY via Mobile odin from Stock GB prerooted ROM. I flashed it together with cf 5.3 kernel. Its been 10 days now and i haven't had any problems but i was lucky that i haven't used CWR nor factory restore. So after reading all the warnings that LPY has a bug on eMMC i want to safely go back to Gingerbread.
Ive searched the forum and found a few methods (Mobile ODIN, PC ODIN, CWR) but i want to make sure that i don't get my device bricked (have no warranty). So my question is Should i choose Full Wipe or a non wipe option while getting back to GB? Or maybe wait a little longer and just try not to stress the I/O till the issue gets resolved?
Click to expand...
Click to collapse
Download pre rooted rom and flash thru pc odin. I came back to gb litening rom twice from lpy and alba 2.1.
This is the way how I downgraded to gb from ics succesfully. It doesn't mean is 100% no risk at all.
Good luck.
Sent from my GT-N7000 using xda premium

i have identical situation , i want to go back to gb via pc odin ( mobile odin pro crashed after choice of any file )
this rom is good for this operation?
3*Files Wipe N7000XXLC1_N7000OXALC1 Open Europe (02/03/2012)
and after gb restored , full wipe? Or the rom itself full wipe?
or maybe wait for new ics?

netoperek said:
i have identical situation , i want to go back to gb via pc odin ( mobile odin pro crashed after choice of any file )
this rom is good for this operation?
3*Files Wipe N7000XXLC1_N7000OXALC1 Open Europe (02/03/2012)
and after gb restored , full wipe? Or the rom itself full wipe?
or maybe wait for new ics?
Click to expand...
Click to collapse
Full wipe with Odin.
Sent from my GT-N7000 using Tapatalk 2

yllivia said:
So I am one of the "brave" souls who flashed ICS LPY via Mobile odin from Stock GB prerooted ROM. I flashed it together with cf 5.3 kernel. Its been 10 days now and i haven't had any problems but i was lucky that i haven't used CWR nor factory restore. So after reading all the warnings that LPY has a bug on eMMC i want to safely go back to Gingerbread.
Ive searched the forum and found a few methods (Mobile ODIN, PC ODIN, CWR) but i want to make sure that i don't get my device bricked (have no warranty). So my question is Should i choose Full Wipe or a non wipe option while getting back to GB? Or maybe wait a little longer and just try not to stress the I/O till the issue gets resolved?
Click to expand...
Click to collapse
I will give u more detail how I did it thru pc odin.
1) Download pre rooted rom from bodivas thread. After downloaded please unzip it and simply put at your desktop.
2) Backup sms, contact or others stuff ( optional).
3 Boot your devices into download mode.
4) Open pc odin.
5) Connect your devices to pc usb port with mini usb cable
6) After your devices connected with your pc ( if connected you will able to see yellow colour box at the left upper side from your pc odin). Click pda button and choose the rom tar file u hv put at your pc desktop.
7. After choosen the right rom. Wait for 15 second. Then press start.( - DO NOT....TICK REPARTITION BUTTON at pc odin WHILE FLASH The pre rooted rom.....)
8) if everything go well, your devices will auto reboot. DONE.
Remarks.
...............
- After rebooted if hv fc prob, pls don't panic. Just pull out the battery and boot into the " stock recovery mode" and do full wipe.
Warning
................
- DO NOT....TICK REPARTITION BUTTON at pc odin WHILE FLASH The pre rooted rom.....
Good luck.
Sent from my GT-N7000 using xda premium

lee yun khong said:
I will give u more detail how I did it thru pc odin.
1) Download pre rooted rom from bodivas thread. After downloaded please unzip it and simply put at your desktop.
2) Backup sms, contact or others stuff ( optional).
3 Boot your devices into download mode.
4) Open pc odin.
5) Connect your devices to pc usb port with mini usb cable
6) After your devices connected with your pc ( if connected you will able to see yellow colour box at the left upper side from your pc odin). Click pda button and choose the rom tar file u hv put at your pc desktop.
7. After choosen the right rom. Wait for 15 second. Then press start.( - DO NOT....TICK REPARTITION BUTTON at pc odin WHILE FLASH The pre rooted rom.....)
8) if everything go well, your devices will auto reboot. DONE.
Remarks.
...............
- After rebooted if hv fc prob, pls don't panic. Just pull out the battery and boot into the " stock recovery mode" and do full wipe.
Warning
................
- DO NOT....TICK REPARTITION BUTTON at pc odin WHILE FLASH The pre rooted rom.....
Good luck.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
____________________________________________________
Thanks for the guide. I have one question. Is there a way to test if my eMMC is ALREADY DAMAGED? I read that if the EMMC is damaged that's the reason that flashing with PC Odin causes superbrick.

yllivia said:
____________________________________________________
Thanks for the guide. I have one question. Is there a way to test if my eMMC is ALREADY DAMAGED? I read that if the EMMC is damaged that's the reason that flashing with PC Odin causes superbrick.
Click to expand...
Click to collapse
Sorry no ideal. But based to the info and the detail you given. The emmc damaged should not exists at your devices. Since you never use the cf-lpy cwm. I'm not the pro..but my opinion could be the common answer.
Sent from my GT-N7000 using xda premium

lee yun khong said:
Sorry no ideal. But based to the info and the detail you given. The emmc damaged should not exists at your devices. Since you never use the cf-lpy cwm. I'm not the pro..but my opinion could be the common answer.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
+1
No way you have emmc!
Sent from my GT-N7000 using Tapatalk 2

rom from this thread ?:
http://forum.xda-developers.com/showthread.php?t=1535025
and use only one file no 3?

netoperek said:
rom from this thread ?:
http://forum.xda-developers.com/showthread.php?t=1535025
and use only one file no 3?
Click to expand...
Click to collapse
I think you have to flash 3 files.
Sent from my GT-N7000 using Tapatalk 2

netoperek said:
i have identical situation , i want to go back to gb via pc odin ( mobile odin pro crashed after choice of any file )
this rom is good for this operation?
3*Files Wipe N7000XXLC1_N7000OXALC1 Open Europe (02/03/2012)
and after gb restored , full wipe? Or the rom itself full wipe?
or maybe wait for new ics?
Click to expand...
Click to collapse
If you feel panic with the bricked problem might appear while flashing back to gb. Please don't try ..it was horrible...your heartbeat sure will keep increase fast and faster...believe me..I hv tried twice....
If you feel comfort with the current ics and without any major bug, just keep using it and enjoy while the dev looking for the solution and waiting for kernel sources code realease.
Just keep in mind DUN USE THE CWM.
OR YOU CAN USE TITANIUM BACKUP AND FREEZE THE CWM FOR ANY ACCIDENTALY WRONG PRESS.
Sent from my GT-N7000 using xda premium

Thanks lee
everything working on my note, no significant bugs
so i thing i stay on ics (for the moment), my heart is delicate

Help please. This is the history of my flashing btw...
I had a rooted Gingerbread with CF root kernel KKA. When ICS came out i rushed and Flashed a cf root lpy zimage (kernel only) via Recovery ( i know it was stupid.. ) So i got stuck and i could only come up to CWM. I used the CWM to BACK UP MY DATA (this was before i even flashed the ICS rom). From there i used PC odin to flash kka gingerbread rom. Flashed it without problem. Then i flashed ICS LPY rom together with LPY kernel via Mobile Odin and i clicked wipe data. Everything went well. I haven't used CWM. Now i am affraid that i could have bad EMMC. Should i stay on ICS or should i flash stock GB rom again?

starnoise said:
Help please. This is the history of my flashing btw...
I had a rooted Gingerbread with CF root kernel KKA. When ICS came out i rushed and Flashed a cf root lpy zimage (kernel only) via Recovery ( i know it was stupid.. ) So i got stuck and i could only come up to CWM. I used the CWM to BACK UP MY DATA (this was before i even flashed the ICS rom). From there i used PC odin to flash kka gingerbread rom. Flashed it without problem. Then i flashed ICS LPY rom together with LPY kernel via Mobile Odin and i clicked wipe data. Everything went well. I haven't used CWM. Now i am affraid that i could have bad EMMC. Should i stay on ICS or should i flash stock GB rom again?
Click to expand...
Click to collapse
your emmc is fine, don't worry! if your phone works than you've done nothing wrong!
If ICS fits your needs you can stay on it, but DO NOT use CWM!!

starnoise said:
Help please. This is the history of my flashing btw...
I had a rooted Gingerbread with CF root kernel KKA. When ICS came out i rushed and Flashed a cf root lpy zimage (kernel only) via Recovery ( i know it was stupid.. ) So i got stuck and i could only come up to CWM. I used the CWM to BACK UP MY DATA (this was before i even flashed the ICS rom). From there i used PC odin to flash kka gingerbread rom. Flashed it without problem. Then i flashed ICS LPY rom together with LPY kernel via Mobile Odin and i clicked wipe data. Everything went well. I haven't used CWM. Now i am affraid that i could have bad EMMC. Should i stay on ICS or should i flash stock GB rom again?
Click to expand...
Click to collapse
I had answered your question thru email. Stick with your current ICS rom will be the best option and choices. Since I do believe no one at the forum able to give you 100% accurately exactly what happen with your emmc. Just enjoy your ics.
Please don't simply flash any gb rooted kernel so that able use the cwm again and go back to gb. Please read the instruction carefully.
PERSONNAL OPINION: I'm always prefer flash stock or pre rooted gb rom thru pc odin beside flash axxx4.2kernel to perform full wipe.
Good luck bro..
Sent from my GT-N7000 using xda premium

lee yun khong said:
I had answered your question thru email. Stick with your current ICS rom will be the best option and choices. Since I do believe no one at the forum able to give you 100% accurately exactly what happen with your emmc. Just enjoy your ics.
Please don't simply flash any gb rooted kernel so that able use the cwm again and go back to gb. Please read the instruction carefully.
PERSONNAL OPINION: I'm always prefer flash stock or pre rooted gb rom thru pc odin beside flash axxx4.2kernel to perform full wipe.
Good luck bro..
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Need help ,,
I am on stock LPY unrooted and came to LPY from GB LC2 unrooted as well.....but if memory serves then i remember that just after updating to LPY i had gone into recovery mode (stock recovery mode) and cleared the cache....does i mean that i stand a chance for the eMMC issue and that i shudn't be going back to GB unrooted LC2 and wait for the devs to fix this?

gurnishdhillon said:
Need help ,,
I am on stock LPY unrooted and came to LPY from GB LC2 unrooted as well.....but if memory serves then i remember that just after updating to LPY i had gone into recovery mode (stock recovery mode) and cleared the cache....does i mean that i stand a chance for the eMMC issue and that i shudn't be going back to GB unrooted LC2 and wait for the devs to fix this?
Click to expand...
Click to collapse
Well according to the devs here you should be good. But noone can guarantee you are 100%. I decided to wait till the issue gets resolved even though i haven't used recovery at all. I am taking my chances on ICS. But again staying on ICS isn't safe either I am quoting CHainfire here..
"Originally Posted by Chainfire
Ok so it still isn't really clear if the problem is still present in LPY, or if the issue is "left-over" due to previous ROMs.
It's all possible. Either way, what I wan't to make absolutely clear again:
If the problem is present in CF-Root LPY (and it's not a "leftover" problem from previous ROM - this is possibly the case), then it's also present in stock LPY. This means you *can* randomly brick your phone even if fully booted into Android, under heavy I/O load.
(on the Note there normal and recovery kernels are the same, and CWM is just a userspace program, nothing special(!) - so if the problem can happen in CWM, it can happen in Android)"
So whichever choice you make... good luck.

yllivia said:
Well according to the devs here you should be good. But noone can guarantee you are 100%. I decided to wait till the issue gets resolved even though i haven't used recovery at all. I am taking my chances on ICS. But again staying on ICS isn't safe either I am quoting CHainfire here..
"Originally Posted by Chainfire
Ok so it still isn't really clear if the problem is still present in LPY, or if the issue is "left-over" due to previous ROMs.
It's all possible. Either way, what I wan't to make absolutely clear again:
If the problem is present in CF-Root LPY (and it's not a "leftover" problem from previous ROM - this is possibly the case), then it's also present in stock LPY. This means you *can* randomly brick your phone even if fully booted into Android, under heavy I/O load.
(on the Note there normal and recovery kernels are the same, and CWM is just a userspace program, nothing special(!) - so if the problem can happen in CWM, it can happen in Android)"
So whichever choice you make... good luck.
Click to expand...
Click to collapse
Yup, is true. Beside you need to stay away from cwm, you should be aware when doing the large file transfer.
Stick with Lpy, do not touch cwm at all, try to avoid do any large files transfer.
Relax bro...u should be fine...just follow what the instruction given by the dev. Since no one really know exactly what happen.
Sent from my GT-N7000 using xda premium

[Q] newbie - HELP PLS - bricked?

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

[SOLVED] downgrade from stock ics to stock gb -> stuck at bootscreen

hello,
i bought a fresh n7000 with stock ics firmware on it. i wanted to go to paranoid android.
1. i rooted the stock ics
2. found out that i need gingerbread to flash custom firmware
3. installed sdk, driver on ubuntu
4. installed heimdall, as its the odin for linux
5. downloaded N7000XXKJ4 from samfirmware.com
6. extracted it to have the single images to flash with heimdall 1.3.1
7. booted in download mode, attached the phone to usb and hitted detect device in heimdall
8. device was found
9. started flashing, first without repartition
boot.img as BOOT
param.lfs as PARAM
factoryfs.img as FACTORYFS
cache.img as CACHE
zImage as KERNEL
Sbl.bin as SBL1
hidden.img as HIDDEN
modem.bin as MODEM
10. flashing went all thru, the phones screen showed the progress also
11. phone did a reboot, after all flashing was done
12. stuck at bootscreen
13. found in the web that its normal and i should do a factory reset in the recovery (its not cwm)
14. stuck at bootscreen
15. repeated step 9. with pit file and repartition
16. same bootscreen
i know the phone is not dead, just not booting, but i have absolutely no chance to find out what to flash exactly and how to do it.

hm could i now just flash the abyss kernel and cwm recovery.bin or so and install a custom rom?

if you are now on GB then flash a kernel, either in CWM or odin and do a full factory reset along with all caches and dalvik cache.
i wouldnt recommend flashing a custom ROM until the stock rom is booting, you dont want to be covering up any underlying errors.
Also, Why did you re-partition ? Did you re-partition using a 3 file firmware (PDA, CSC, Phone) or just a single firmware - PDA ??

hm i dont know on what i am, because it doesnt boot.
i thought i eventually had to repartition because i changed from 4.0 to 2.3.5 ... i used the n7000 16gb pit file.

Well what did ODIN say ? Did it complete or did it get stuck and fail ?
You can flash a kernel in ODIN which should allow you to enter CWM and do a wipe, However you might get issues if you flash a GB kernel over ICS Firmware and vice versa

heimdall ran complete through, said its all fine and the phone rebooted at the end of flashing as it should be. seems all perfect.
the issues i get can not be worse?! if i would now flash a gb kernel, even if there is ics under the hood, the phone would also just not boot?!

I dont know really, Ive never tried, nor do i intend to lol.
But i imagine GB is now on your phone considering it all passed without fail So i guess you should try to flash a kernel and then do a full wipe and see if it boots then
chances are there are some ICS files left on the system preventing it from booting.

and following the guides on xda im not allowed to flash the other kernel with heimdall/odin.
i should use the cf-kernel for my firmware and flash it with the bat-script, is this correct?

Just flash this in ODIN and you will be fine
https://dl.dropbox.com/u/69014495/GingerBread-speedmod-kernel-n7000-k2-12-Odin.tar
boot into recovery, do a factory reset, then clear cache partition, then go to advanced and clear dalvik cache, then reboot
then report back

ok. now i have the yellow triangle. i wanted to avoid this.
BUT it looks very promising. clockword mod is starting. did the wipes. and when i reboot it boots directly in cwm. i think this is good atm.
i have to leave at work now. tomorrow morning i can flash a rom with cwm right? and if i flash an ics rom, then i have to flash a ics kernel, too?!

Dont worry about the triangle, Use this app to remove it https://dl.dropbox.com/u/69014495/eu.chainfire.triangleaway-47fe5bbd55070e4eddce741c0ef13110.apk
Like i said above, Make sure the phone boots before flashing any other ROMs. If you want to upgrade to ICS you will need to flash ICS in ODIN, Unless you want to use a CM9 / AOSP based ROM like Paranoid Android, In this case you will stay on GB, Just full wipe and flash ROM in CWM
EDIT: I mis read your post, Your phone is not booting, But only booting into CWM, In this case, try a custom ROM, Nothing to extreme just a simple GB ROM and see if it boots properly then

thanks so much!
flashed checkrom notehd via cwm. boots clean and nicely up.
i flashed/rooted some phones before htc hero, hd2, zte blade. but none of them, even the hd2 with its windows conversion was as unclear as the n7000. i think because in former times the developers wherent as many as actual, and there were much less guides/tuts/howtos which made an user less unsecure.
nevertheless, your support is gorgeous: friendly, fast and ultracompetent.
edit: can i change the title in solved anyhow?

xmaskx said:
thanks so much!
flashed checkrom notehd via cwm. boots clean and nicely up.
i flashed/rooted some phones before htc hero, hd2, zte blade. but none of them, even the hd2 with its windows conversion was as unclear as the n7000. i think because in former times the developers wherent as many as actual, and there were much less guides/tuts/howtos which made an user less unsecure.
nevertheless, your support is gorgeous: friendly, fast and ultracompetent.
edit: can i change the title in solved anyhow?
Click to expand...
Click to collapse
Your welcome!
Glad to see you're up and running again
Oh and if you go to your very first post on this thread, Click edit then you should be able to put [Solved] in the title bar

Buddy start from crap...and one advice..u never know the depth of an ocean unless u dive into it..be brave...just follow cursed4eva tutorials on youtube.u will know everything...and only u can teach uraelf no one else..what i did when i was a boy,i mean when i was new to note,i followed this guy and he saved my daymy recommendations is to use odin...flash a 3file rom whose links are provided in cursed4eva's video..and flash it...u will be on stock gb..
Sent from my GT-N7000 using xda app-developers app

[SOLVED] G7000 Stuck at "Samsung Galaxy Note GT-N7000"

Hello!
First of all I've searched all the posts about this problem.. and personally I can't fix it.
So here is what I've done to brick my Galaxy Note GT-N7000 (I think that's called a non-usable device).
Installed few ROMs and finally after taking some decisions I've returned back on ICS 4.0.3 (Flashed with ODIN 1.85).
Restored EFS with kTool (because ClearNotev5 did something wrong with my phone.. and discovered after few hours that I can restore EFS).
Updated ICS 4.0.3 to 4.0.4 using WIFI (OTA I think it's called) and BANG after restart phone stucked at Bootscreen.
So from yesterday untill now I've restored my phone to factory settings few times(GB 2.3.5 & 2.3.6/ICS 4.0.4),repartitioned with .pit files for N7000 16GB,installed different custom/stock ROMs and nothing.
I've discovered few minutes ago while triyng to make a factory restore (GB 2.3.5) that my phone stucked at data.img... I've read about this and it is said that I must change my N7000 motherboard.. I have no warranty so please help.. and sorry for my bad english

Read many times about ota harbrick, i think its not advisable to use ota for upgrade. Sorry for your loss.
Flash gb in pc odin, if sucessfull and still stuck in logo go to CWMR and perform 3 wipes. This is all advise i can give you.
And try different gb rom.

allexsava said:
So from yesterday untill now I've restored my phone to factory settings few times(GB 2.3.5 & 2.3.6/ICS 4.0.4),repartitioned with .pit files for N7000 16GB,installed different custom/stock ROMs and nothing.
I've discovered few minutes ago while triyng to make a factory restore (GB 2.3.5) that my phone stucked at data.img...
Click to expand...
Click to collapse
^^
I think you had already tried the recovery method from a bricked device. So if you still facing problems you have to change the MB.

OTA Brick or Soft Brick?
I still haven't fix it but here is what I want:
Can someone give me different versions of GB (I've tried only one with CSC,MODEM but this now stops at data.img..) :crying:
I have to make a repartition to my phone? Will that help?
And can someone guide me through a tutorial step by step on how to revive my phone from EMMC Bug..?
PS: When I try to wipe data in CWM (using Hydracore Kernel v2.0b STD) with ICS 4.0.4 (Stock) my N7000 stucks,same for installing CleaNotev5.0 (stucks at Extracting\System).. But what is curios is that, I can clear Dalvik Cache and Cache, I can install Kernels and run N7000 in DOWNLOAD/CWM or stock Restore mode.
Any solutions?Please help..

allexsava said:
I still haven't fix it but here is what I want:
Can someone give me different versions of GB (I've tried only one with CSC,MODEM but this now stops at data.img..) :crying:
I have to make a repartition to my phone? Will that help?
And can someone guide me through a tutorial step by step on how to revive my phone from EMMC Bug..?
PS: When I try to wipe data in CWM (using Hydracore Kernel v2.0b STD) with ICS 4.0.4 (Stock) my N7000 stucks,same for installing CleaNotev5.0 (stucks at Extracting\System).. But what is curios is that, I can clear Dalvik Cache and Cache, I can install Kernels and run N7000 in DOWNLOAD/CWM or stock Restore mode.
Any solutions?Please help..
Click to expand...
Click to collapse
You can try the post here :
http://forum.xda-developers.com/showthread.php?t=1667886&highlight=emmc
Just follow the step there.
I've experienced before, and revive it using this method. So far mine still work well, and no further error ever since.
You will loose certain GB on your internal storage. Which for me it's not a big deal. I'm kinda lazy to go to samsung repair center, unless my phone is totally dead.
Here is my step (follow at your own risk) :
1. You have to know first your N7000 is the 16GB or 32GB, and then you download the correct pit for your phone.
2. After you download, extract the zip file.
3. Since mine is the 16GB, I've picked this pit file to use (inside the zip) : Q1_20110914_16GB-patched-regain-0102400-kB.pit (the pit file will be vary depending on which sector your phone brick)
4. Put your phone on to download mode.
5. Open ODIN PC and connect your phone, and wait till ODIN say "Added" and you see that your phone has connected.
6. Put the patch pit file I choose, then put the samsung stock rom as the PDA (if you downloaded 1 file only for the stock ROM, if not, put properly for the PDA, Phone, and CSC).
7. Check ON the "repartition", "Auto-reboot", "F-reset time"
8. Click Start, and wait till the process has finished. Your phone should auto reboot by then.
9. My phone has recovered, and I lost 1GB internal storage.
One last thing, try not to do wipe on ICS, unless you are on a safe kernel like speedmod / GLNotecore.
For Hydracore (You may check with the developer), I haven't tested it yet for wiping. But for those speedmod and GLNotecore, is confirm safe kernel. I've tried these 2 for wiping.
PS : if you are not sure with my step on reviving with the pit file, I suggest you to read the link above from the OP for the pit revive method.
Good Luck !

antique_sonic said:
You can try the post here :
http://forum.xda-developers.com/showthread.php?t=1667886&highlight=emmc
Just follow the step there.
I've experienced before, and revive it using this method. So far mine still work well, and no further error ever since.
You will loose certain GB on your internal storage. Which for me it's not a big deal. I'm kinda lazy to go to samsung repair center, unless my phone is totally dead.
Here is my step (follow at your own risk) :
1. You have to know first your N7000 is the 16GB or 32GB, and then you download the correct pit for your phone.
2. After you download, extract the zip file.
3. Since mine is the 16GB, I've picked this pit file to use (inside the zip) : Q1_20110914_16GB-patched-regain-0102400-kB.pit (the pit file will be vary depending on which sector your phone brick)
4. Put your phone on to download mode.
5. Open ODIN PC and connect your phone, and wait till ODIN say "Added" and you see that your phone has connected.
6. Put the patch pit file I choose, then put the samsung stock rom as the PDA (if you downloaded 1 file only for the stock ROM, if not, put properly for the PDA, Phone, and CSC).
7. Check ON the "repartition", "Auto-reboot", "F-reset time"
8. Click Start, and wait till the process has finished. Your phone should auto reboot by then.
9. My phone has recovered, and I lost 1GB internal storage.
One last thing, try not to do wipe on ICS, unless you are on a safe kernel like speedmod / GLNotecore.
For Hydracore (You may check with the developer), I haven't tested it yet for wiping. But for those speedmod and GLNotecore, is confirm safe kernel. I've tried these 2 for wiping.
PS : if you are not sure with my step on reviving with the pit file, I suggest you to read the link above from the OP for the pit revive method.
Good Luck !
Click to expand...
Click to collapse
Thank you for this magnific guide but.. I got one question? How do I know wich sector on my phone is bricked? Is there a tool to flash or something? Can you simplify for me because here(http://forum.xda-developers.com/show...highlight=emmc) it's to complicated for me

Find your gb rom here. http://forum.xda-developers.com/showthread.php?t=1424997
No more option left, for mmc cap erase brick, go here. Pls read carefully. http://forum.xda-developers.com/showthread.php?t=1667886

I've got a problem: I am from Romania and all GB's from Romania are on COSMOSTE and VODAFONE but I'm on ORANGE..Is there a problem to install a VODAFONE/COSMOTE GB?

allexsava said:
I've got a problem: I am from Romania and all GB's from Romania are on COSMOSTE and VODAFONE but I'm on ORANGE..Is there a problem to install a VODAFONE/COSMOTE GB?
Click to expand...
Click to collapse
No problem. Just pick any gb rom, one problem at a time, your problem now is how your phone can boot up.
If you want go to www.sammobile.com and pick your specific rom.

I've downloaded the COSMOTE GB ROM and I will flash it with PC ODIN.
After that I need as I was saying few posts ago how to identify which part of my internal storage is bricked..but a simplified method/guide please.. and sorry for my requests but believe me I'm kinda desperate..

allexsava said:
I've downloaded the COSMOTE GB ROM and I will flash it with PC ODIN.
After that I need as I was saying few posts ago how to identify which part of my internal storage is bricked..but a simplified method/guide please.. and sorry for my requests but believe me I'm kinda desperate..
Click to expand...
Click to collapse
You may refer to this post.
http://forum.xda-developers.com/showthread.php?t=1823918
The OP stated very clear on how to get the part of your bricked storage.

After emmc_find_brick_start.zip I get stucked on:
scanning 1167 Mib = 1224 MB ... (picture below)
And now I am waiting emmc_find_brick_end.zip to get stuck
LE: emmc_find_brick_end.zip stuck at:
scanning 3356 MiB = 3520 MB ... (picture below)

allexsava said:
I've got a problem: I am from Romania and all GB's from Romania are on COSMOSTE and VODAFONE but I'm on ORANGE..Is there a problem to install a VODAFONE/COSMOTE GB?
Click to expand...
Click to collapse
Shouldn't be a problem. However, best to root current, then efs backup multiple locations. See dr ketans toolbox thread on how.
Your phones csc is also Romania? Best to stick with your phones csc and those country roms if you want to continue ota/kies updatability in the future Dial *#06# for emei and then *#272*yourimeihere# to find out 3 letter csc.
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
Shouldn't be a problem. However, best to root current, then efs backup multiple locations. See dr ketans toolbox thread on how.
Your phones csc is also Romania? Best to stick with your phones csc and those country roms if you want to continue ota/kies updatability in the future Dial *#06# for emei and then *#272*yourimeihere# to find out 3 letter csc.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
If I can boot up my phone I'll consider your reply

allexsava said:
If I can boot up my phone I'll consider your reply
Click to expand...
Click to collapse
goodluck booting!
Sent from my GT-N7000 using Tapatalk 2

SOLVED
:fingers-crossed: Sorry for late response guys but yeah I've fixed it by patching the right .pit file and got only 8,83 GB internal memory.. Flashing CriskeloRomNOTE.vICS-V11.2 and HydraCore v3.5 STD.. I've got few problems with ROM, suddenly stuck in different situations but again yeah.. I'm happy I didn't changed my MB ..if someone got some ideas why it stucks please reply

At least you dont have to pay for mobo which is 200 dollars.
Sent from my GT-N7000 using xda premium

if you get succesful flash of gb then stay on it don't upgrade to ics.. "something is better then nothing"
Sent from my GT-N7000 using Tapatalk 2

Thank you all for the support
Sent from my GT-N7000 using xda premium

[Q] Soft Bricked N7000

I was trying to install Ultimate_N7000_LSC_JB_4.1.2_v5.1 on non-rooted device.
After booting into Recovery and installing CWM, i tried Data wipe/Factory reset.
(Battery was 100%)
The screen switched of suddenly and now i am stuck.
Here are somethings i have tried:
1) Tried flashing N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 using ODIN. Never goes beyond NAND flashing (Tried in Admin mode, with ODIN Mode)
2) Tried flashing cm-9.1.0-n7000 and had status 0 and status 7 error many times.
Most of the flashing methods mention : "wipe data/Factory reset". Whenever i do that, i get stuck in "Wiping Data... .Formatting /data"
I have tried "Fix permissions", it wont work.
I didnt take a ROM backup and now i really regret it.
Currently when i navigate using CWM i can see all my internal as well as external memory files. So, i guess my OS is gone and files are still there.
The Custom Rom Counter says: Yes (Count 4) in ODIN mode.
Can someone help ? Please i am desperate.

What rom you on before flashing?..GB or ICS?
Sent from my GT-N7000 using Tapatalk 2

ICS 4.0.4
I had not done any Modifications, rooting to my N7000 before yesterday.
Would like to go back to Any ROM.
Unrooted ROM (ICS 4.0.4), Leaked JB Rom, CM9, CM10. Any ROM. Just want to get my phone up and running

What error do you get when flashing with Odin?
Does it stop at "factoryfs.img"?
How did you install CSM on your stock Rom ICS 4.0.4?

Your "soft bricked" sounds more like "super bricked" to me.. Did you use CWM.zip to wipe?
Tapatalking on my n7000

Yes. I used CWM.zip.
But now that my phone is not working, how do know what is the firmware version?
(http://forum.xda-developers.com/showthread.php?t=1656635)
Can you tell me the exact file names i should use
PDA: CODE_N7000xxxxx_CL627135_REV02_user_low_ship.tar.m d5
PHONE: MODEM_N7000xxxxx_REV_05_CL1067428.tar.md5
CSC: GT-N7000-MULTI-CSC-Oxxxxx.tar.md5
What does xxxx stand for? I have the Serial No. of my phone. And have done normal OTA updates only.
Brought from flipkart in August (if it helps narrow down the xxxx)
Superbricked or soft, please help.
Just downloaded some CWM file (Sorry i searched a lot, i couldnt remember the source)
Here are the steps:
Flash it with Odin 1.85, (Click PDA, choose the file and press Start)
After this you will have Root on your phone.
Now you can go into CWM and flash the Rom.
1) Download Ultimate XXLSC Jelly Bean 4.1.2 custom ROM for Galaxy Note to the PC
2) Connect the device to PC using USB cable and transfer the downloaded ROM zip file to the phone's SD card
3) Unplug the USB cable from the phone and then turn it off
4) Enter into Recovery mode by switching on the phone while pressing and holding Volume Up, Home and Power buttons together
5) In CWM Recovery, perform a full data wipe
Here is where it suddenly stopped and the screen went blank. (I am double sure battery was 100%)
Thanks for the prompt replies

Yup..its a wrong way to flash costum rom on stock ics...
try flash stock rom using odin, if its stuck on "factoryfs.img".. I'm sure your super bricked your phone..
Sent from my GT-N7000 using Tapatalk 2

zai89 said:
Yup..its a wrong way to flash costum rom on stock ics...
try flash stock rom using odin, if its stuck on "factoryfs.img".. I'm sure your super bricked your phone..
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
ok. But please help me. How to take it out of super-brick.
In ODIN it gets stuck in "NAND write start"
I already tried flashing Stock ROM N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 in ODIN and it gets stuck in "NAND write start"
I found this post. http://forum.xda-developers.com/show....php?t=1656635
Should i follow this?
Can you tell me the exact file names i should use
PDA: CODE_N7000xxxxx_CL627135_REV02_user_low_ship.tar.m d5
PHONE: MODEM_N7000xxxxx_REV_05_CL1067428.tar.md5
CSC: GT-N7000-MULTI-CSC-Oxxxxx.tar.md5
What does xxxx stand for? I have the Serial No. of my phone. And have done normal OTA updates only.
Brought from flipkart in August (if it helps narrow down the xxxx)
(Thanks in advance)

If you have warranty then claim it.. Super brick means that the emmc chip it's burned.. There's some methods to get it to partially work but you lose around 3Gb of memory and generally you can not use TW roms.. Or at least stock TW.. Not to mention the random reboots and freezes..
So most likely if you don't have warranty then use the pit file method or pay for a motherboard replacement..
Tapatalking on my n7000

Thanks for the suggestion.
I managed to flash 4.0.3 ROM and stock Kernel and it somehow worked. (did too many things)
Here's the current status: Running 4.1.2 (XXSLO, ZSLM5). Unrooted and stock ROM. (Updated from 4.0.3 to 4.1.2 in kies)
Everything is back. The phone runs good. But when i try installing any software, it will freeze. The apk/app installs eventually but after 2-3 reboots.
Can you tell me the issue?
I read it somewhere that the "Cache" partition is damaged.
Can someone please tell me any way to avoid freezes.
msedek said:
If you have warranty then claim it.. Super brick means that the emmc chip it's burned.. There's some methods to get it to partially work but you lose around 3Gb of memory and generally you can not use TW roms.. Or at least stock TW.. Not to mention the random reboots and freezes..
So most likely if you don't have warranty then use the pit file method or pay for a motherboard replacement..
Tapatalking on my n7000
Click to expand...
Click to collapse