hello i recently updated my galaxy note to 4.0.4 LRK evry thing worked fine but have lot of freezing with backuped application so i tried the wipe factory reset but its take a long time and it rebooted i tried another kernel the same another rom the same flashed another rom the same and its stuck on samsung logo i cant format data what i can do now?
On which kernel you were when doing the factory reset?
xpomar said:
hello i recently updated my galaxy note to 4.0.4 LRK evry thing worked fine but have lot of freezing with backuped application so i tried the wipe factory reset but its take a long time and it rebooted i tried another kernel the same another rom the same flashed another rom the same and its stuck on samsung logo i cant format data what i can do now?
Click to expand...
Click to collapse
See if you can odin back to gingerbread... You wiped on ics.. So many threads warning not to do this.... Was you on stock unrooted when you wiped? If so let Entropy512 on cm9 thread know, he might be able to help you... If you were on stock when you bricked don't do anything till you speak to Entropy512
Sent from my GT-N7000 using xda app-developers app
@denny said:
See if you can odin back to gingerbread... You wiped on ics.. So many threads warning not to do this.... Was you on stock unrooted when you wiped? If so let Entropy512 on cm9 thread know, he might be able to help you... If you were on stock when you bricked don't do anything till you speak to Entropy512
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
What can he do? Is is not the only one with brick expertise. Its time for a brew mother board.
Factory reset an ICS stock kernel results in an instant brick
Sent from my GT-N7000 using Tapatalk 2
kopitalk said:
On which kernel you were when doing the factory reset?
Click to expand...
Click to collapse
in stock kernel and just rooted with SU+BUSYBOX
Use odin to flash a stock GB rom from Dr.ketan thread (link in his signature).
If it stuck in factoryfs.img or datafs.img then have a superbrick Note.
In that case only a new mother board or repartition method below can help:
http://forum.xda-developers.com/showthread.php?t=1661590&page=2
Hope it helps,
Related
Word of caution........ No one has proven that this or any other method.. is without risk...... The Risk of Bricking is still too High..... please consider that before flashing something to see if it really works..
The Moderator
Hi guys....
finally Sammy gave us a real ICS bootloader, and a new kernel (LPF), I managed to flash it to my Note and all went fine....
I'm nearly sure that THIS IS THE KEY, no more BRICK, no more deep sleep problems, no more "failed to restore" nandroid....just flash THIS with ODIN 1.87, run "download mode" on your Note, open Odin, select "bootloader" and flash it....then flash CF LPF kernel with mobile Odin
I'm preparing TMT1.3 to check if I'm right...
first successfully nandroid restore (combined with LPF CF kernel) : http://forum.xda-developers.com/showpost.php?p=26245707&postcount=190
and TMT1.3 beta testing
maxicet said:
Hi guys....
finally Sammy gave us a real ICS bootloader, I managed to flash it to my Note and all went fine....
I'm nearly sure that THIS IS THE KEY, no more BRICK, no more deep sleep problems, no more "failed to restore" nandroid....just flashed THIS with ODIN 1.87, just run "download mode" on your Note, open Odin, select "bootloader" and flash it....
I'm preparing TMT1.3 to check if I'm right...
Click to expand...
Click to collapse
May i flash new bootload with mobiOdin?
I'm not that brave to try it first but i'll follow the thread with feedbacks
Who have lpy stock firmware and have ballz of steel please flash this bootloader and try to do wipe data at cwm recovery >
Many thanks maxicet should we expect new rom from you
i rly rly rly rly hope this will solve the brick risks,
i feel so naked without knowing i can trust my CWM in flashing, restoring and wiping
I'm looking for that guy I've read a few days ago here on the forum, which has a "business" GNote and had no problems even if he brick it...
The ULTIMATE test will be to restore a nandroid backup..
million dollar question:
does the bootloader solve the brick phenomena? waiting for elite developers to dig and give their observations...
has anyone tweeted CF?
edit: okay i tweeted him myself.. just in case..
musashiro said:
has anyone tweeted CF?
Click to expand...
Click to collapse
yes, and apparently his device is in the repair centre from the lp5 brick and wont be able to confirm until he gets it back
Somebody posted in another thread that Chainfire has got his Note bricked because of LP6 kernel so he can't test if bootloader is fixed and free of hardbrick
Anyone try flash it already? Any outcome/feedback?
Sucessfully Flash it using mobile odin pro. Will see if the deep sleep problem goes away
Currently on LPY stock with CF-Root LPY kernel
Sent from my GT-N7000 using xda premium
alxwlc said:
Anyone try flash it already? Any outcome/feedback?
Click to expand...
Click to collapse
like said in OP, I flashed this, and all went fine...
The "ultimate test" we need is a successfully nandroid restore
captainhakan said:
Somebody posted in another thread that Chainfire has got his Note bricked because of LP6 kernel so he can't test if bootloader is fixed and free of hardbrick
Click to expand...
Click to collapse
as i have said, im waiting if at least he can peek on the firmware or comment on it. even just a comment is okay..
maxicet said:
like said in OP, I flashed this, and all went fine...
The "ultimate test" we need is a successfully nandroid restore
Click to expand...
Click to collapse
btw all those ics leaked firmwares before had ics bootloader?
maxicet said:
I'm looking for that guy I've read a few days ago here on the forum, which has a "business" GNote and had no problems even if he brick it...
The ULTIMATE test will be to restore a nandroid backup..
Click to expand...
Click to collapse
Please keep us posted bro ...would be amazing..thank you!
Sent from my GT-N7000 using xda premium
Would someone tell me if I can flash this via mobile odin? and what is the exact process that I have to do with both PC and mobile odin? I appreciate if someone can tell me and maybe others would need these instructions I'm currently running rooted stock GB LC1.
Thanks in advance
maxicet said:
I'm looking for that guy I've read a few days ago here on the forum, which has a "business" GNote and had no problems even if he brick it...
The ULTIMATE test will be to restore a nandroid backup..
Click to expand...
Click to collapse
Hi Maxicet,
What would you require someone to try would it be flashing the new bootloader and then try restoring a nanadroid backup. Would this be a nandroid of gingerbread or ICS LPY rom. I would have a go at it for you. Im at work at the mo but let me know what you want me to test and I will do it. I can get my note replaced no problem.
djtiny said:
Hi Maxicet,
What would you require someone to try would it be flashing the new bootloader and then try restoring a nanadroid backup. Would this be a nandroid of gingerbread or ICS LPY rom. I would have a go at it for you. Im at work at the mo but let me know what you want me to test and I will do it. I can get my note replaced no problem.
Click to expand...
Click to collapse
bless you if maxicet wont mention, please also test wiping data at cwm recovery because plenty got problems while wiping data at cwm recovery with lpy.
djtiny said:
Hi Maxicet,
What would you require someone to try would it be flashing the new bootloader and then try restoring a nanadroid backup. Would this be a nandroid of gingerbread or ICS LPY rom. I would have a go at it for you. Im at work at the mo but let me know what you want me to test and I will do it. I can get my note replaced no problem.
Click to expand...
Click to collapse
ok, best test is : starting from a LPY ICS rom with CF root LPY kernel, flash OP bootloader with ODIN PC (I did it with 1.87 version)
Try to do a nandroid backup (with CWM recovery) and after reboot, try to restore it.
Second test will be to restore a GB nandroid backup....
plz what ics leak mean ? i am new to android world
what is the difference between ics leak and repack and stock and other expressions?
what is the difference between kernel and firmware expression ?
give me example ( stuuner and canyon and lpy and lpf and gb )...
i asked this noob question as i am noob at flashing and i read alot about bricks and emmc bug for leak and repack ICS
now i am using lpf rooted ics + supersu
Ics leak is when the ice cream in the ice cream sandwich is almost melted and starting to leak. In all seriousness a leak is when a company accidentally loses a firmware version for a phone and it goes public.
Sent from my Nexus S 4G using XDA
sehooo said:
plz what ics leak mean ? i am new to android world
what is the difference between ics leak and repack and stock and other expressions?
what is the difference between kernel and firmware expression ?
give me example ( stuuner and canyon and lpy and lpf and gb )...
i asked this noob question as i am noob at flashing and i read alot about bricks and emmc bug for leak and repack ICS
now i am using lpf rooted ics + supersu
Click to expand...
Click to collapse
The first ICS Roms for Note were buit on a DANGEROUS Kernel which came from a "leak". That kernel was responsible for bricking many devices due to its eMMC bug.
Now all the new ICS Roms are "fixed" by using new Kernels, but the problem continues if you go from an old rom (leak kernel) to a new one. There is a specific way to do it. You can read all about it in many threads.
If you tell me which Rom you want to flash and on which Rom you currently use i can give you more detailes!
Hope i could help!
sotiris20 said:
The first ICS Roms for Note were buit on a DANGEROUS Kernel which came from a "leak". That kernel was responsible for bricking many devices due to its eMMC bug.
Now all the new ICS Roms are "fixed" by using new Kernels, but the problem continues if you go from an old rom (leak kernel) to a new one. There is a specific way to do it. You can read all about it in many threads.
If you tell me which Rom you want to flash and on which Rom you currently use i can give you more detailes!
Hope i could help!
Click to expand...
Click to collapse
PLEASE HELP ME TOO! now i am currently on RocketICS rom but my note keep restarting every 30 sec... RocketICS rom was the first rom i flashed after i rooted my new note. Is there anyway to get rid of the bootloop? i really like the rocketICS rom but i cant use it at all if it keeps restarting. Before i flash the rocketics rom, my note was N7000DXLC2.
Please direct me how to remove the bootloop. i really want to use the RocketIcs rom.
myemintun said:
PLEASE HELP ME TOO! now i am currently on RocketICS rom but my note keep restarting every 30 sec... RocketICS rom was the first rom i flashed after i rooted my new note. Is there anyway to get rid of the bootloop? i really like the rocketICS rom but i cant use it at all if it keeps restarting. Before i flash the rocketics rom, my note was N7000DXLC2.
Please direct me how to remove the bootloop. i really want to use the RocketIcs rom.
Click to expand...
Click to collapse
You have already started a thread about your issue. Posting about the same thing in different threads is called spamming, and is against the XDA rules. So, don't do it.
chasmodo said:
You have already started a thread about your issue. Posting about the same thing in different threads is called spamming, and is against the XDA rules. So, don't do it.
Click to expand...
Click to collapse
Okkay sorry i dint know that is called spamming. But i am really nervous and scared now my parents will kill me if my note brick. If u know the soultion or any link please help me. i am really thankful.
myemintun said:
Okkay sorry i dint know that is called spamming. But i am really nervous and scared now my parents will kill me if my note brick. If u know the soultion or any link please help me. i am really thankful.
Click to expand...
Click to collapse
You can at least post link to other thread with comment moved comment to seperate thread.
Do a flash back to stock gb throught pc odin, perform data factory reset through dialer, google for code ending something like 3855.
Root it and put cf kernel on it, perform factory reset from recovery, wipe caches and dalvik cache. Then reinstall rocket by flashing the zip in recovery.
After this do not recover apps just redownload from playstore. Do it one by one so you can eliminate which one is responsible. If thats case.
You loose data but also lingering crap from past that can cause fc an reboot. Now you can best disable keep device backup in Google cloud.
Last read all post in rocket thread. Should it return, there areprobably others with same problem. Check their fixes lmao
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
You can at least post link to other thread with comment moved comment to seperate thread.
Do a flash back to stock gb throught pc odin, perform data factory reset through dialer, google for code ending something like 3855.
Root it and put cf kernel on it, perform factory reset from recovery, wipe caches and dalvik cache. Then reinstall rocket by flashing the zip in recovery.
After this do not recover apps just redownload from playstore. Do it one by one so you can eliminate which one is responsible. If thats case.
You loose data but also lingering crap from past that can cause fc an reboot. Now you can best disable keep device backup in Google cloud.
Last read all post in rocket thread. Should it return, there areprobably others with same problem. Check their fixes lmao
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
thanks bro.. even though i dont get what u mean ;( can u teach me how to flash a lpy stock rom from my current state?
Ok go to first post in this thread http://forum.xda-developers.com/showthread.php?t=1424997
All should become clear reading this thread. Its a sticky in developement with sceenshots on how to install. From development you can also find cf root.
Recap
Download odin, shut down kies and start it on pc.
Download your rom of choice, unzip it.
Turn phone off, turn on and push volume down, home key and buttun at same time, it should go to download mode, Its tricky, may need couple tries.
dont wait to long, connect to pc, watch added in odin, select extracted tar. Md5 file, the largest, put in pda, no repartition no clear efs.
Press volume button up to initiate download mode and select start on odin, if your download was ok, it should flash and show pass on odin.
If I were you I would dl gb rom, because from gb rom the samsung factory reset I mentioned earlier is safe. Usually this fixes bootloop itself, however on ics rom, custom, leak or official this is not safe. (except cm9 with xplodwild kernel)
Sent from my GT-N7000 using Tapatalk 2
Deleted
I had Cyanogenmod on my note, then i flashed stock ics using pc odin. my flash counter is zero and binary is samsung official.
my problem is that when i unlock my phone i cant do anything for 10sec and its pretty laggy. i think that i wiped it using official ics.
and i think it has something to do with the emmc bug.
My question is does this goes under warranty ? or are there any solution for my problem ?
Hopes someone can answer quickly please its realy annoyning.....
alekks said:
I had Cyanogenmod on my note, then i flashed stock ics using pc odin. my flash counter is zero and binary is samsung official.
my problem is that when i unlock my phone i cant do anything for 10sec and its pretty laggy. i think that i wiped it using official ics.
and i think it has something to do with the emmc bug.
My question is does this goes under warranty ? or are there any solution for my problem ?
Hopes someone can answer quickly please its realy annoyning.....
Click to expand...
Click to collapse
Before you take your phone to Samsung, I recommend to reflash your rom and perform a full wipe, clear cache and dalvik cache. But ensure yourself that you are doing it on a safe kernel. Goku, notecore, speedmod, abyss...
Sent from my Galaxy Note running ICS
alekks said:
I had Cyanogenmod on my note, then i flashed stock ics using pc odin. my flash counter is zero and binary is samsung official.
my problem is that when i unlock my phone i cant do anything for 10sec and its pretty laggy. i think that i wiped it using official ics.
and i think it has something to do with the emmc bug.
My question is does this goes under warranty ? or are there any solution for my problem ?
Hopes someone can answer quickly please its realy annoyning.....
Click to expand...
Click to collapse
Go back to CM9
Sent from my GT-N7000 using xda app-developers app
I rooted a custom rom to my Note and I am wondering is factory reset still available to me? I want to get back to stock (I know this method will cause a lot work) and this seems the safest method, If I can get back to ginger bread with way.
It seems too easy but I thought, I'd ask.
Thanks for your help.
Simply download and flash GB ROM with Odin
Then wipe cache and data from recovery
Read 1st link on my signature (post 2 and 3 for GB ROM)
Yes, but
dr.ketan said:
Simply download and flash GB ROM with Odin
Then wipe cache and data from recovery
Read 1st link on my signature (post 2 and 3 for GB ROM)
Click to expand...
Click to collapse
Dear Doc,
Thank you for your quick response, Of course, I'll take a look at it. Actually, however, I really wanted to know if factory reset was still an option -- no matter how bad -- for me.
Thanks Again
its an option, but not a good one, youre better off listening to the docter which is why he prescribes this.
That or find out how to flash tar files with ktool, then backup current kernel, flash a safe one like hydra, do your factory resetting, then reflash old kernel with ktool.
all at own risk. Dr Ketans way is best.
Sent with a grin (^.^)
Thanks
baz77 said:
its an option, but not a good one, youre better off listening to the docter which is why he prescribes this.
That or find out how to flash tar files with ktool, then backup current kernel, flash a safe one like hydra, do your factory resetting, then reflash old kernel with ktool.
all at own risk. Dr Ketans way is best.
Sent with a grin (^.^)
Click to expand...
Click to collapse
Thanks for your input. By way of explanation, I bricked my phone thursday night and was lucky enough to get the service people to "fix" it for me while I waited. It scared the bejesus out of me. I use this device hourly - not just daily and the thought of losing it for a week or 10 days caused much anxiety.
So my thought is that doing a factory reset, letting Samsung upgrade the software and then restoring my back up is the 'safest" thing I can do to get my phone back to stock
So if you would take a moment and tell me why a factory reset is not a good alternative, I'd be very interested.
I look forward to your response.
wel if you dont mind emmc bug risk, then its good option. If you do mind, like I do, then its not good option. Personal choice really
Sent with a grin (^.^)
Confused
baz77 said:
wel if you dont mind emmc bug risk, then its good option. If you do mind, like I do, then its not good option. Personal choice really
Sent with a grin (^.^)
Click to expand...
Click to collapse
I thought a factory reset was a good idea because it would give stock GB 2.3.6. I also thought that the bug you are referring to came in ICS 4.0.3.
I think the emmc bug is a major league disaster and if I am exposing myself to it by using a factory reset, I'll dump the idea.
I really appreciate your helping me with this.
no problem.
If your custom rom is gb, then no risk, do your factory reset. If ICS dont cause of bug risk. A safe kernel could help, but its easier dr Ketans way.
Factory resetting on ICS will not give gb by the way.
Sent with a grin (^.^)
Hmmmm
baz77 said:
no problem.
If your custom rom is gb, then no risk, do your factory reset. If ICS dont cause of bug risk. A safe kernel could help, but its easier dr Ketans way.
Factory resetting on ICS will not give gb by the way.
Sent with a grin (^.^)
Click to expand...
Click to collapse
The note N7000 came with GB, I updated to stock 4.0.3 ( got lucky) and then updated to the current custom rom.- Here's where I sit.
Android Version: 4.0.3
Baseband version N7000XXLPT
Kernel version
3.0.15-N70000XXLPY-CL474507
[email protected]#3
SMP Preenpt Fri May 4 04:49:06 KST 2012
BUILD NUMBER
IML74KXXLPY
The phone is NOT rooted
All I want to do is go back to GB stock SAFELY. I thought of using factory reset to do that but wanted to ask about possible problems.
humphster said:
The note N7000 came with GB, I updated to stock 4.0.3 ( got lucky) and then updated to the current custom rom.- Here's where I sit.
Android Version: 4.0.3
Baseband version N7000XXLPT
Kernel version
3.0.15-N70000XXLPY-CL474507
[email protected]#3
SMP Preenpt Fri May 4 04:49:06 KST 2012
BUILD NUMBER
IML74KXXLPY
The phone is NOT rooted
All I want to do is go back to GB stock SAFELY. I thought of using factory reset to do that but wanted to ask about possible problems.
Click to expand...
Click to collapse
Ok, you are not running a custom ROM but a stock one. Factory reset in stock ICS will brick your device. To safely revert to GB, use PC ODIN. Go to Dr. Ketan's thread and find your stock GB firmware, then flash it. Do not wipe anything in stock ICS. This is the thread:
http://forum.xda-developers.com/showthread.php?p=20963707
Sent from my GT-N7000 using xda app-developers app
Duhhhhh
glevitan said:
Ok, you are not running a custom ROM but a stock one. Factory reset in stock ICS will brick your device. To safely revert to GB, use PC ODIN. Go to Dr. Ketan's thread and find your stock GB firmware, then flash it. Do not wipe anything in stock ICS. This is the thread:
http://forum.xda-developers.com/showthread.php?p=20963707
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Just for my info, what tells you it is a stock rom?
Boy, do I feel stupid
So I got everything downloaded and extracted and disconnected the phone and put in download mode (Odin Mode), started Odin, plugged in the extracted file, and then connected the phone to the PC. The PC recognizes the phone but Odin doesn't - no "added" and no port. The firewall and virus checker.
What's next?
Have you installed driver on pc? Even if you have kies installed then also works.
If you dont have it, then find toolbox on my signature, find driver and install to PC, then it will detect device.
Sent from my GT-N7000 using xda premium
yep and switch of usb debugging in settings, development. Just in case thats on. Probably doesnt interfere, but might.
Close Kies when using pc odin.
When in download mode dont forget to confirm with volume up. First time I was like ok nothings happening, Then I saw, damn need to confirm it lol.
Flashing takes a while, so let it complete, even if it looks stuck it might not be. Might take up to an hour to complete. Usually not thought.
Do not check clear efs. Coming from ICS flashing with standard pitfile can be recommended, optional. Anyway after flashing throught Odin, and if rom doesnt boot straight away, do factory reset from recovery mode, then it should boot.
The cleanest factory reset, don't ask me why is from dialer with a code ending in 3855 by the way.
Sent with a grin (^.^)
Hello all
I know I might sound paranoid but I want to confirm something.
I wiped cache/date when I was on custom rom before flashing Philz safe kernel (actually wiped to flash that kernel).
I updated from SGS and there before flashing anything its recommended to wipe cache/dalvik but after reading few topics here I came to know that that's not the way to go with N7000 and now I am worried as I read on a few topics that users have got their cell or usb bricked few months after doing what I did (wipe cache on stock rom).
Now I would like to know is their anything I can do to prevent same happening with me or I should just wait and pray that that doesn't happen to me.
I am currently on stock JB rooted with Philz kernel.
Thanks in advance for advice
Indian Devil
Sent from my GT-N7000 using xda app-developers app
Indian Devil said:
Hello all
I know I might sound paranoid but I want to confirm something.
I wiped cache/date when I was on custom rom before flashing Philz safe kernel (actually wiped to flash that kernel).
I updated from SGS and there before flashing anything its recommended to wipe cache/dalvik but after reading few topics here I came to know that that's not the way to go with N7000 and now I am worried as I read on a few topics that users have got their cell or usb bricked few months after doing what I did (wipe cache on stock rom).
Now I would like to know is their anything I can do to prevent same happening with me or I should just wait and pray that that doesn't happen to me.
I am currently on stock JB rooted with Philz kernel.
Thanks in advance for advice
Indian Devil
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Always do wipes in Philz kernel or Any others custom safe kernels. Never do any kind of wipes/factory reset, formats or even format usb storage in stock kernel .
Firstly, always read the thread carefully before you flash, especially the instructions pertaining to the required recovery to flash and ROM support(for kernels and MODs). And also factory reset, wipe cache and other things as the respective ROM threads guide you. And flashing is very safe once you follow the instructions.
Indian Devil said:
Hello all
I know I might sound paranoid but I want to confirm something.
I wiped cache/date when I was on custom rom before flashing Philz safe kernel (actually wiped to flash that kernel).
I updated from SGS and there before flashing anything its recommended to wipe cache/dalvik but after reading few topics here I came to know that that's not the way to go with N7000 and now I am worried as I read on a few topics that users have got their cell or usb bricked few months after doing what I did (wipe cache on stock rom).
Now I would like to know is their anything I can do to prevent same happening with me or I should just wait and pray that that doesn't happen to me.
I am currently on stock JB rooted with Philz kernel.
Thanks in advance for advice
Indian Devil
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Since I had done it already, what are the chances that I might face issues? Can it brick after a few days/months even if I don't do anything?
Or as its running fine now, I can breath easy unless I do something stupid again.. lol.. Which I am sure I won't.
Sent from my GT-N7000 using xda app-developers app
Indian Devil said:
Since I had done it already, what are the chances that I might face issues? Can it brick after a few days/months even if I don't do anything?
Or as its running fine now, I can breath easy unless I do something stupid again.. lol.. Which I am sure I won't.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Don't worry mate, if the phone is working alright now, it won't be bricked. And if you follow the instructions well, it's difficult to hard brick your phone! There won't be any issues, stick to the instructions to the letter though!