Database Users

Phone won't boot :(

My galaxy 3 (apollo) came with 2.1, so I thought I would update to 2.2. I downloaded JPU from hotfile, the one that uses sampro.pl as password. Had odin set up with .ops, one package, nothing else checked. It flashes it and restarts a few times, then gets to the samsung logo which flashes, then it just freezes.
I have tried wiping the cache and factory reset. I tried JPS too (which I knew worked on my other phone - but that I upgraded from 2.2 to 2.2) but nothing seems to work.
Have I done something wrong?

I would suggest to flash your mobile once again
by following the instructions in the below link.
http://forum.xda-developewjrs.com/showthread.php?t=1372414
I hope it helps.

Somehow I got it working, I flashed Cyanogenmod and it worked, then wiped all including dalvik cache with cwm, still didn't work when I flashed froyo. So I removed sbl.bin and boot.bin from the .tar, tried and still nothing, then wiped data and cache one last time and on reboot it started up!
I had wiped the data and cache tens of times before and after flashing before, so it was either removing the bootloader or wiping the dalvik cache that made a difference. Only took all day to update my phone!

Try to get some different source for froyo....

I'm Glad you got it working again! next time you need stock firmware, use the one available in this forum by searching "stock jpu" the dev has removed the bootloaders and therefore it is much safer, and yeh as you've discovered, when it doubt, wipe the dalvik!

Hi
Yeah I did come across a thread where someone had removed the bootloaders, but all the files were either removed because they were on megaupload, or linked to JPI. I could have used that, infact I did connect it to kies at the start of the day and it said it could upgrade me to JPU. I wanted to do it by odin though! Then 12 hours later and trying countless other firmwares it worked. I just opened the .tar with 7zip and deleted boot.bin and sbl.bin, I had no idea if that would work or not!
It wasn't stuck in a boot loop so the bootloader couldn't have been corrupt? Perhaps it was the dalvik cache needed to be wiped from 2.1 to 2.2? I couldn't see anyway to wipe it with the stock samsung recovery.
Is CWM available for this phone? (without having to flash Cyanogen!)

mike_1983 said:
Hi
Yeah I did come across a thread where someone had removed the bootloaders, but all the files were either removed because they were on megaupload, or linked to JPI. I could have used that, infact I did connect it to kies at the start of the day and it said it could upgrade me to JPU. I wanted to do it by odin though! Then 12 hours later and trying countless other firmwares it worked. I just opened the .tar with 7zip and deleted boot.bin and sbl.bin, I had no idea if that would work or not!
It wasn't stuck in a boot loop so the bootloader couldn't have been corrupt? Perhaps it was the dalvik cache needed to be wiped from 2.1 to 2.2? I couldn't see anyway to wipe it with the stock samsung recovery.
Is CWM available for this phone? (without having to flash Cyanogen!)
Click to expand...
Click to collapse
CM7 is a aftermarket firmware, so it wont be available in the updates....and also, samsung wont give us this kind of good looking ROM anyways, flashing a ROM is a whole lot faster than updating through Kies or others...

J.Purungrit said:
CM7 is a aftermarket firmware, so it wont be available in the updates....and also, samsung wont give us this kind of good looking ROM anyways, flashing a ROM is a whole lot faster than updating through Kies or others...
Click to expand...
Click to collapse
Hi
I just meant is ClockworkMod available for the Galaxy 3. I noticed it was on my phone when I flashed Cyanogen Mod.
I have a Galaxy 5, the CM7 for that seems more complete, I noticed the camera doesn't work on the Galaxy 3 CM7. I thought they would both be about the same functionality.
In my case flashing a rom was slower as it gave me a bunch of problems, but yeah flashing is usually faster

mike_1983 said:
Hi
I just meant is ClockworkMod available for the Galaxy 3. I noticed it was on my phone when I flashed Cyanogen Mod.
I have a Galaxy 5, the CM7 for that seems more complete, I noticed the camera doesn't work on the Galaxy 3 CM7. I thought they would both be about the same functionality.
In my case flashing a rom was slower as it gave me a bunch of problems, but yeah flashing is usually faster
Click to expand...
Click to collapse
Camera has been mostly fixed in CM7 and Galaxy 5 has been out for longer so devs have had more time. Anyway, all custom ROM's come with CWM Recovery.

I think you can install cwm for stock Roms..I have seen similar question in some thread posted here..which says your phone should be initially rooted to do this..
I am not sure abt the process..but as far as I know..you have to follow these steps :
download an app called as z4root..search in Google..its not available in market..
root your phone..it will ask two options to either root permanently or temporarily..go permanently..(you can unroot it I think so don't worry)
and finally you can try several custom kernals.. head over to development thread for that.I prefer fugumod kernal..take the tar file and flash it via Odin (safer side wipe dalvik as well as cache and reboot)
since its a stock rom ..you will not be having dedicated option to go for recovery, use volume keys,power button and the center button together..
bit of headache..
try at your own risk..or if I am wrong, please advice

Smonic said:
Camera has been mostly fixed in CM7 and Galaxy 5 has been out for longer so devs have had more time. Anyway, all custom ROM's come with CWM Recovery.
Click to expand...
Click to collapse
Ah I didnt know the Galaxy 5 had been out longer. The camera didn't work when I used the latest CM7 for the Galaxy 3, when it took a picture it looked like a commodore loading screen But I didn't check gallery thinking about it, perhaps they came out alright

prabhuthelegend said:
I think you can install cwm for stock Roms..I have seen similar question in some thread posted here..which says your phone should be initially rooted to do this..
I am not sure abt the process..but as far as I know..you have to follow these steps :
download an app called as z4root..search in Google..its not available in market..
root your phone..it will ask two options to either root permanently or temporarily..go permanently..(you can unroot it I think so don't worry)
and finally you can try several custom kernals.. head over to development thread for that.I prefer fugumod kernal..take the tar file and flash it via Odin (safer side wipe dalvik as well as cache and reboot)
since its a stock rom ..you will not be having dedicated option to go for recovery, use volume keys,power button and the center button together..
bit of headache..
try at your own risk..or if I am wrong, please advice
Click to expand...
Click to collapse
I rooted the phone with SuperOneClick, I think it worked! Anyway I gave the phone to my brother now and hes just interested in a working phone, not messing about with roms! I may get the phone again when it comes down in price again (you can get them refurbished in brand new condition here in UK)
Thanks!

[INFO] Guide to safely go back to GB from LPY (answer is in the OP)

Hey again!
As promised, here is the current result of this thread: As Dr. Ketan can be seen as a very "prominent" and competent developer here on the board, I strongly suggest to orientate yourself on his post (#9) when deciding to go back to GB from LPY ICS!
His suggestion:
EDIT (May, 17th): Generall suggestion by Dr.Ketan:
If you were on stock GB, N now you are on stock ICS with/without Cf root kernel. Dont do anything and wait for next ICS release.
This ICS bug can be result to brick by any sort of flashing procedure , if your luck is not with you. Nothing nothing is guranteed.
Old restore advice:
If one is on ics + cf root
1. Backup app with TB
2. Flash gb ROM using pc odin, root n restore app from TB.
Sent from my GT-N7000 using xda premium
If someone with experience has another suggestion: Just post it here in the thread, I will update the OP when there´s a better solution.
My original post:
Hello Notepeople!
I would love to know how to go back to my GB backup since there is a rising number of issues with LPY (and don´t get me wrong, but please: no discussion about LPY being dangerous or not - I´m sure that there are people who would like to no this too!)
There are some random answers within some threads, but as they all differ a lot, I will change the title and the OP in this thread as soon as we managed to discuss a straight answer, so everyone will be able to find the answer here!
Is it still the same procedure like it was during the Stunner/CM9 bricks-time?
1.) flashing abyss 4.2
2.) wipe (as it is safe with abyss)
3.) flash stock GB / restore backup
And: Is there any danger to damage the emmc while doing this? Some people wrote that while flashing abyss 4.2, there will be no wipe during the process...
As promised: as soon as there is an answer, you will find it here in the OP!
Click to expand...
Click to collapse

Hi, 30 minutes ago I was on Alba Lpy and partial root!
I've flashed first Abyss 3.9 originalLogo, rebooted CW, flashed GB rooted rom, rebooted CW, 3 wipes and reboored: all works good and I'm rooted again
Sent from my GT-N7000 using xda premium

I would like to go.back too but i dont have a backup and id like the safest method
Sent from my GT-N7000 using XDA

I just reverted to gingerbread on 2 galaxy Note's here by using PC Odin and pre rooted rom (Wipe N7000XXLC1_N7000OXALC1 Open Europe (02/03/2012)) from here http://forum.xda-developers.com/showthread.php?t=1535025 All without problems. i dont't know whether it is the safest way but it worked for me

Flashing with PC Odin to Stock GB (even with Pre Rooted GB from Bodivas thread) is by far the safest method.
Sent from my GT-N7000

Master_Unit said:
I just reverted to gingerbread on 2 galaxy Note's here by using PC Odin and pre rooted rom (Wipe N7000XXLC1_N7000OXALC1 Open Europe (02/03/2012)) from here http://forum.xda-developers.com/showthread.php?t=1535025 All without problems. i dont't know whether it is the safest way but it worked for me
Click to expand...
Click to collapse
sorry but can you post the steps you took please?

jbg1 said:
sorry but can you post the steps you took please?
Click to expand...
Click to collapse
Hi, you can see the steps in this video http://www.youtube.com/watch?feature=player_detailpage&v=ehXcnqntsro#t=158s
Hope it helps, its actualy "root tutorial" but the steps are the same.
P.S. all credits for aphroditelikesme who made this video

thanks yeah i just wanted to make sure, im downloading lc1 wipe now ill post back when done

On my view
If one is on ics + cf root
1. Backup app with TB
2. Flash stock ics with pc odin( to remove cf kernel.safely)
3. Hard reset feom setting
4. Flash gb ROM using pc odin, root n restore app from TB.
Sent from my GT-N7000 using xda premium
Edit :
After latest review from CF, And incidence found stock kernel can lead to brick, I suggest some modification in above.
Avoid step 2 and 3 ( recent work suggest stock kernel can also lead to brick)
And directly flash GB ROM (older preferable to get root access easily)
But If you were on stock GB, N now you are on stock ICS with/without Cf root kernel. Dont do anything and wait for next ICS release.
This ICS bug can be result to brick by any sort of flashing procedure , if your luck is not with you. Nothing nothing is guranteed.

I just flashed a cf gb kernel with heimdall and used cwm to restore gb. Then flashed ics lpy again without a wipe and all apps were fine and up and running. I think reflashing stock is only required if the boot loaders were changed with the older ics leaks. Lpy does not seem to flash new boot loaders.
Sent from my GT-N7000 using xda premium

dr.ketan said:
On my view
If one is on ics + cf root
1. Backup app with TB
2. Flash stock ics with pc odin( to remove cf kernel.safely)
3. Hard reset feom setting
4. Flash gb ROM using pc odin, root n restore app from TB.
Click to expand...
Click to collapse
In my opinion, you can skip steps 2 and 3 if you flash a wipe version of gingerbread from bodivas with PC Odin. The only advice I would like to give is stay away from CWM recovery on LPY rom.

i did it but its failing, im getting calender force close, gooogle framework force close, it said success but when it reboots it gets force closes and reboots again and again
PLEASE HELP!

jbg1 said:
i did it but its failing, im getting calender force close, gooogle framework force close, it said success but when it reboots it gets force closes and reboots again and again
PLEASE HELP!
Click to expand...
Click to collapse
What method did you use? if you flashed gingerbread rom it should be safe to do factory reset/wipe in recovery

i flashed the wipe gingerbread lc1 in pc odin it said sucess and it boots up but force closes a bunch doesnt let me do anything

have you tried factory reset/wipe in recovery?

Thank you based god!!!!
---------- Post added at 09:18 PM ---------- Previous post was at 09:15 PM ----------
ok so yeah i can cosign it works, i flashed via mobile odin no wipe to get ics from stock gingerbread...to go back as Master_unit says follow the video and download a wipe version, and dont forget to wipe in recovery like i did and panic lol

NP mate, Glad to hear that you and your Note are ok now!

i just reverted back to GB from LPY.
i had KJ4 on my laptop at home so i flashed that with PC Odin.
Took 5 minutes, phone booted up.
i received a lot of FCs
booted into system recovery (vol up + menu + power)
factory data reset + cache delete
reboot
everything is now working. it was good to be in ICS but i hated the poor battery life. i am quite a heavy user but still got a day of battery with GB.. with LPY, 12-14 hours barely. will be flashing either stunner or cm9 now.

OP updated!

dr.ketan said:
On my view
If one is on ics + cf root
1. Backup app with TB
2. Flash stock ics with pc odin( to remove cf kernel.safely)
3. Hard reset feom setting
4. Flash gb ROM using pc odin, root n restore app from TB.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Dr.Ketan I read many of your excellent posts and they are all really welcome but please please please will you stop using the letter "N" to mean the word "AND" especially like you have done in previous guides or instructions. it is very confusing to me... let alone the newbies.
Thanks in advance.

Softbrick caused by LPY - How did you recover your phone?

There have been few more cases of Superbrick since Chasmodo's and now I'm worried that there would be more of such cases when people start flashing custom LPY ROMs, LPY mods and use Stock and Clockwork recovery functions.
I have created this thread specially for those people to share their methods/experience - when the softbrick happened to them and how they managed to recover their phone (symptoms such as nand write failure, factoryfs failure etc).
So if more of such incidents happen, possible solutions would be at one place.
Please do not troll! Do not post comments such as 'So far so good', 'No problem what so ever'. I have flashed LPY multiple times myself but I'm still not sure.
Do not post solutions if you have not successfully tried it yourself.
Regards.

fixed my superbrick by sending it back to india to get sent in for new motherboard

JamieD81 said:
fixed my superbrick by sending it back to india to get sent in for new motherboard
Click to expand...
Click to collapse
Thanks a lot sir.
I successfully returned to GB fourth time (Had used stock recovery many times). Gotta wait till experts find a solution.

Boy124 said:
Thanks a lot sir.
I successfully returned to GB fourth time (Had used stock recovery many times). Gotta wait till experts find a solution.
Click to expand...
Click to collapse
if its a hardbrick super brick, then it will need a motherboard replaced because it would fry your emmc, which there is no recovery unless u send out or replace yourself
*motherboards are as much as the digitizer..

JamieD81 said:
if its a hardbrick super brick, then it will need a motherboard replaced because it would fry your emmc, which there is no recovery unless u send out or replace yourself
*motherboards are as much as the digitizer..
Click to expand...
Click to collapse
Yeah. But few users said that they got write failure error but were able return to GB successfully.
Some of them used PIT file, others used different kernels.
Perhaps it was 'nearly superbrick'.

Boy124 said:
Yeah. But few users said that they got write failure error but were able return to GB successfully.
Some of them used PIT file, others used different kernels.
Perhaps it was 'nearly superbrick'.
Click to expand...
Click to collapse
If you could recover it was a softbrick, nothing more. This thread is about hard bricks - for which as stated there's only one answer - mainboard replacement.

wildestpixel said:
If you could recover it was a softbrick, nothing more. This thread is about hard bricks - for which as stated there's only one answer - mainboard replacement.
Click to expand...
Click to collapse
+1 perfect reply

Entropy was refering to Epic 4G Touch forum so I searched there and found useful info there. Credit goes to xST4T1K
How to Avoid Brick
-If you are on ICS with an ICS kernel, DO NOT WIPE! this has the potential to brick your device (until source arrives, just have patience)
-Using a bad USB cable to ODIN back to GB from ICS
-Rom Manager
-Touch recovery
-Avoid flashing any custom rom in stock ICS recovery
-Avoid restoring a GB backup when running an ICS leak
-Avoid restoring a ICS backup when running a GB rom
-Always use PC odin to return GB - Do flash custom GB kernel on non-GB rom to flash GB firmware

Boy124 said:
....................
So if more of such incidents happen, possible solutions would be at one place.
Please do not troll! Do not post comments such as 'So far so good', 'No problem what so ever'. I have flashed LPY multiple times myself but I'm still not sure.
Do not post solutions if you have not successfully tried it yourself.
Regards.
Click to expand...
Click to collapse
Your post in itself is tantamount to trolling.

wildestpixel said:
Your post in itself is tantamount to trolling.
Click to expand...
Click to collapse
If you do not have anything useful to say, better stay away from this thread.
I am not offering you the job.
And you don't seem to have much knowledge than proving
superbrick != softbrick

You should change the title of your thread. As it was already pointed out,
superbrick can only be cured by MoBo replacement, period.
Everything else is a soft brick.

chasmodo said:
You should change the title of your thread. As it was already pointed out,
superbrick can only be cured by MoBo replacement, period.
Everything else is a soft brick.
Click to expand...
Click to collapse
100% accurate
nothing about superbrick is anything to do with softbricking a device.

Thanks Chas.
People won't contribute but will waste time on what is what and what's not.

I had to use a combination of many things:
- Heimdall to flash CF-Root kernel to get CWM (PC Odin equivalent for Mac, older 1.3.0 because 1.3.2 does not work) introduced the bad yellow triangle but thats better than having a brick
- CWM refused to restore any backup or wipe anything (FREAKED OUT)
- Used CWM to flash Abyss 3.9 (I know 4.2 is recommended but had this on the phone)
- Used Redpill restore my backup
- Booted fine, but unable to remount /system/ as rw, tried a lot but no luck so far, I guess I will not be able to flash again.
Now for details, how did I get the softbrick in the first place:
- Bought and installed Mobile Odin PRO
- Downloaded LPY .tar.md5 and cf-root LPY kernel
- Asked Mobile Odin to flash LPY .tar.md5 without wipe (stock kernel, because most posts on XDA said to do it separately) and wanted to keep my data and apps
- Stuck on Samsung logo
hmmm, no recovery installed
- flash CF-root kernel for CWM, via heimdall
- factory reset (wipe data)
- Yipee boot into marvelous ICS-LPY
- Ooops all my data and apps are in GB
- Backup via CWM current ICS
- Restore GB backup
- nothing, no boot, no recovery, nothing, well download mode was still showing up, so recovered as mentioned above.

tazzix said:
I had to use a combination of many things:
- Heimdall to flash CF-Root kernel to get CWM (PC Odin equivalent for Mac, older 1.3.0 because 1.3.2 does not work) introduced the bad yellow triangle but thats better than having a brick
- CWM refused to restore any backup or wipe anything (FREAKED OUT)
- Used CWM to flash Abyss 3.9 (I know 4.2 is recommended but had this on the phone)
- Used Redpill restore my backup
- Booted fine, but unable to remount /system/ as rw, tried a lot but no luck so far, I guess I will not be able to flash again.
Now for details, how did I get the softbrick in the first place:
- Bought and installed Mobile Odin PRO
- Downloaded LPY .tar.md5 and cf-root LPY kernel
- Asked Mobile Odin to flash LPY .tar.md5 without wipe (stock kernel, because most posts on XDA said to do it separately) and wanted to keep my data and apps
- Stuck on Samsung logo
hmmm, no recovery installed
- flash CF-root kernel for CWM, via heimdall
- factory reset (wipe data)
- Yipee boot into marvelous ICS-LPY
- Ooops all my data and apps are in GB
- Backup via CWM current ICS
- Restore GB backup
- nothing, no boot, no recovery, nothing, well download mode was still showing up, so recovered as mentioned above.
Click to expand...
Click to collapse
So in my opinion all you had to do to avoid the damage was flash GB to do your wiping, and never backup/restore. (providing you want to use LPY)

eitama said:
So in my opinion all you had to do to avoid the damage was flash GB to do your wiping, and never backup/restore. (providing you want to use LPY)
Click to expand...
Click to collapse
I would guess so, and wish I knew that earlier, it was supposed to be able to UPGRADE without wipe, otherwise if I would have gone the standard way of backup, titanium backup, wipe, flash; I would not have goten any damage for sure.

For me it has been to Flash a wipe rom.
Skickat från min GT-N7000 via Tapatalk 2

Installed LPY w/ root via mobileOdin pro without issue, but was having many issues with FC's. I was thinking of doing a full wipe, but decided to see if it was safe considering the issues with the previous leaked ICS roms, checked xda where I saw the warning about LPY.
Decided to go back to GB by flashing AbyssNote kernel 4.2, then restoring backup.
The most recent backup gave me an error, so I went to the back before that. Everything seemed to go fine but on reboot I got stuck at the Samsung logo.
Was able to still get in cwm so I reflashed AbyssNote kernel, then flashed Cassie Xtralite rom, which is the gb rom that I had been on before flashing ICS.
Everything booted up so I went through the procedure to get Cassies rom up and running and everything has been fine since.
Will try ICS again at some point but will wait a little bit longer until things seem more sorted.

I came directly from Rocket v23 and flashed with mobile odin pro with the original instructions of Dr. Ketan from here: http://forum.xda-developers.com/showpost.php?p=25916135&postcount=1840 I could never get passed the "Samsung" logo so flashed directly back to Rocket V22 (23 wouldn't work for some reason) via CWM. After reading that there could be some issue with the CF Root I just reflashed the same way minus the zimage file. I got stuck at the "Samsung" logo this time but tried "Factory Reset" and it worked like a charm. The funny thing was that I didn't lose any data (pics, music, vids, etc.)

bmcsfuze said:
I came directly from Rocket v23 and flashed with mobile odin pro with the original instructions of Dr. Ketan from here: http://forum.xda-developers.com/showpost.php?p=25916135&postcount=1840 I could never get passed the "Samsung" logo so flashed directly back to Rocket V22 (23 wouldn't work for some reason) via CWM. After reading that there could be some issue with the CF Root I just reflashed the same way minus the zimage file. I got stuck at the "Samsung" logo this time but tried "Factory Reset" and it worked like a charm. The funny thing was that I didn't lose any data (pics, music, vids, etc.)
Click to expand...
Click to collapse
In a Factory Reset you only lose your apps, contacts, gmail settings etc.. i.e. what you have in the system.

[GUIDE] On ICS LPY ROM [DO's & DONT)

From the Moderator... Please read my Caution in post #27-thanks
First, before flashing the ICS LPY Rom, go back to any STOCK GB according to your liking.
Second, do a full wipe/dalvik/data WHILE YOU'RE ON STOCK GB. Restart/Reboot and start flashing the official ICS LPY Rom on ur device.
Third, since this is not a wipe rom, DONT DO IT. Once booted, RESTORE FACTORY SETTING and WIPE using the ICS OS menu. Not thru RECOVERY or CWMR. As long as u wipe/reset thru the os menu, u should be fine.
Lastly, you'll be greeted with a new device setup wizard and all the premium apps will be installed. It'll take sometime for the premium app to initialize. You'll think u're stuck at the boot screen (samsung logo), but no. Just wait, it could last a good 3 to 4 min before u see the device setup wizard.
For the time being, to avoid bricking, it is not advisable to root or install CWM for this particular release. Some kernel code might have changed making it problematic for CWMR to live side by side.
And if you do decide to root and get CWMR on ur device, DONT WIPE/FACTORY RESET thru stock recovery or CWMR. It is known to mess up ur eMMC. Just DONT.
Hope it helps.
Edit: Shorty66 just posted he bricked his note by doing factory reset from within the os. So far he's the only one at the moment. But numerous members reported bricking their device using CWM recovery & stock recovery. Just to be safe, use the os factory reset rather than recovery. Me myself have used the os factory reset at least 6-7 times as we speak without any issue for the time being.

Nice guide, perhaps you could also add the steps to safely go to a 'safe' kernel/rom if one is already using LPY?
Sent from my GT-N7000 using xda premium

+1
Would also like to know the go back to b/cm9 etc steps
Sent from my GT-N7000 using xda premium

Entropy covered that earlier. But whatever u do if u're on LPY, avoid wiping under CWM or stock recovery. Get any safe GB cf-root kernel and wipe/reset/flash from there. And dont restore nandroid backup from any leaked ics or LPY kernel. As to stock LPY device, u can just flash back to any stock gb and from there to get to any custom roms or rooted gb.

Ashren81 said:
Entropy covered that earlier. But whatever u do if u're on LPY, avoid wiping under CWM or stock recovery. Get any safe GB cf-root kernel and wipe/reset/flash from there. And dont restore nandroid backup from any leaked ics or LPY kernel. As to stock LPY device, u can just flash back to any stock gb and from there get to any custom roms or rooted gb.
Click to expand...
Click to collapse
So just to be clear, as I am currently on rooted LPY ROM + kernel, the safest thing would be to flash CF-Root GB kernel whilst still on LPY? How would this be done? Because obviously CWM functions aren't safe, and flashing a GB kernel (through Mobile Odin) on a ICS build would cause a brick also?
I really hate LPY and I want to get on to CM9 just to be safe, but I'm having trouble figuring a safe way to do so any help would be greatly appreciated.
Sent from my White Galaxy Note using Tapatalk 2

MamaSaidWhat? said:
So just to be clear, as I am currently on rooted LPY ROM + kernel, the safest thing would be to flash CF-Root GB kernel whilst still on LPY? How would this be done? Because obviously CWM functions aren't safe, and flashing a GB kernel (through Mobile Odin) on a ICS build would cause a brick also?
I really hate LPY and I want to get on to CM9 just to be safe, but I'm having trouble figuring a safe way to do so any help would be greatly appreciated.
Sent from my White Galaxy Note using Tapatalk 2
Click to expand...
Click to collapse
flash using pc odin or heimdall. get to recovery and flash/wipe or install gb backup from there. but i advise u to get back to stock gb to get a clean start and move from there.

Ashren81 said:
First, before flashing the ICS LPY Rom, go back to any STOCK GB according to your liking.
Second, do a full wipe/dalvik/data WHILE YOU'RE ON STOCK GB. Restart/Reboot and start flashing the official ICS LPY Rom on ur device.
Third, since this is not a wipe rom, DONT DO IT. Once booted, RESTORE FACTORY SETTING and WIPE using the ICS OS menu. Not thru RECOVERY or CWMR. As long as u wipe/reset thru the os menu, u should be fine.
Lastly, you'll be greeted with a new device setup wizard and all the premium apps will be installed. It'll take sometime for the premium app to initialize. You'll think u're stuck at the boot screen (samsung logo), but no. Just wait, it could last a good 3 to 4 min before u see the device setup wizard.
For the time being, to avoid bricking, it is not advisable to root or install CWM for this particular release. Some kernel code might have changed making it problematic for CWMR to live side by side.
And if you do decide to root and get CWMR on ur device, DONT WIPE/FACTORY RESET thru stock recovery or CWMR. It is known to mess up ur eMMC. Just DONT.
Hope it helps.
Click to expand...
Click to collapse
i agree with u but rooting using this way is safe for all stock changer
http://forum.xda-developers.com/showthread.php?t=1647148
i did that for 3 notes here
and u can change the the default twlancher for the lpy as its laggy with any other launcher
now its all ok for lpy ( ICS + CLEAN+ SMOOTH +ROOT )
i prefer go launcher ex

sehooo said:
i agree with u but rooting using this way is safe for all stock changer
http://forum.xda-developers.com/showthread.php?t=1647148
i did that for 3 notes here
and u can change the the default twlancher for the lpy as its laggy with any other launcher
now its all ok for lpy ( ICS + CLEAN+ SMOOTH +ROOT )
i prefer go launcher ex
Click to expand...
Click to collapse
apex launcher FTW!

nice guide!

Ashren81 said:
Third, since this is not a wipe rom, DONT DO IT. Once booted, RESTORE FACTORY SETTING and WIPE using the ICS OS menu. Not thru RECOVERY or CWMR. As long as u wipe/reset thru the os menu, u should be fine.
Click to expand...
Click to collapse
I question the validity of this, because was a reported issue using the settings factory reset too. As far as I know, settings/factory reset still uses recovery to wipe data. Might want to double check that and update your post accordingly.
The post I referenced: http://forum.xda-developers.com/showthread.php?p=26086599#post26086599

k1ng617 said:
I question the validity of this, because was a reported issue using the settings factory reset too. As far as I know, settings/factory reset still uses recovery to wipe data. Might want to double check that and update your post accordingly.
Click to expand...
Click to collapse
Yeah shorty66 just said he bricked his note using the os factory reset menu. So now we have all method bugged. But I still recommend doing a factory reset from within the os on first boot to clear things out. U wont get the premium apps installed on the first boot if u're coming from any other previous rom because LPY is not a wipe rom. U wont even get the device setup wizard on the first boot. When u do the factory reset, it'll get the premium apps to install upon boot and u get the chance to set the device up using the welcome wizard. I see most people who bricked their device went straight to the recovery and do a wipe from there. Just dont do that, never.

Ashren81 said:
Yeah shorty66 just said he bricked his note using the os factory reset menu. So now we have all method bugged. But I still recommend doing a factory reset from within the os on first boot to clear things out. U wont get the premium apps installed on the first boot if u're coming from any other previous rom because LPY is not a wipe rom. U wont even get the device setup wizard on the first boot. When u do the factory reset, it'll get the premium apps to install upon boot and u get the chance to set the device up using the welcome wizard. I see most people who bricked their device went straight to the recovery and do a wipe from there. Just dont do that, never.
Click to expand...
Click to collapse
This is how i go back to GB from ics
From lpy go to recovery, flash abyss 4.2 redpilltouch, reboot recovery, so now i'm on GB kernel recovery, wipe data, cache, dalvik. DON'T BOOT SYSTEM. Restore any nandroid GB backup, after that reboot system.
Hope it help.

hgberry said:
This is how i go back to GB from ics
From lpy go to recovery, flash abyss 4.2 redpilltouch, reboot recovery, so now i'm on GB kernel recovery, wipe data, cache, dalvik. DON'T BOOT SYSTEM. Restore any nandroid GB backup, after that reboot system.
Hope it help.
Click to expand...
Click to collapse
yes that should be the way like i've post earlier. just use the safe-kernel of ur choice. but dont restore nandroid backup from any previous ics, nandroid from previous gb is fine. nice to see ur note safely back on gb. /thumbsup

I don't understand what's all this fuss about really...
I flashed lpy thru mobile Odin (coming from gingerbread) with root option checked, and all went smooth! No pc was used at all! I was even at University when I did that!
Then 2 days later, I factory reset using stock recovery... And all went fine! I was even in a friend's car!
So what's up with all the bricking all over the forum?!!
Sent from my GT-N7000 using xda premium

Goodm7sn said:
I don't understand what's all this fuss about really...
I flashed lpy thru mobile Odin (coming from gingerbread) with root option checked, and all went smooth! No pc was used at all! I was even at University when I did that!
Then 2 days later, I factory reset using stock recovery... And all went fine! I was even in a friend's car!
So what's up with all the bricking all over the forum?!!
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
It happen randomly due to I/O bug on the kernel. While wiping big chunk of data off the partition, it'll glitch. Maybe after a wipe, 10th wipe, 11th wipe, 50 wipe etc. Maybe ur upcoming wipe will be ur last wipe, u might never know. Wiping thru CWM and stock recovery is known to produce the bricking effect. Only 1 person reported bricking thru the os factory reset.

I have to agree I don't understand how these bricks are happening. I have gone from Darky LC1 to LPY and then flashed Chainfire LPY kernel through mobile odin. I then got bored and flashed ICS stunner 26.1 through CWM. I have then gone back to CWM whilst on Stunner and Flashed Abyss Note Kernel 4.2. Then on the top of that I have flashed Alba V2 repack of LPY after a wipe/data from CWM and still no brick. I understand the risks involved but like I said not bricked yet.
Does anyone think that there maybe a different eMMC chip on some of these notes that have shipped which have bricked. Wounder if there is anyway to tell anyone looked into this. Just a thought as it might not be the software but the chip on certain devices ???

djtiny said:
I have to agree I don't understand how these bricks are happening. I have gone from Darky LC1 to LPY and then flashed Chainfire LPY kernel through mobile odin. I then got bored and flashed ICS stunner 26.1 through CWM. I have then gone back to CWM whilst on Stunner and Flashed Abyss Note Kernel 4.2. Then on the top of that I have flashed Alba V2 repack of LPY after a wipe/data from CWM and still no brick. I understand the risks involved but like I said not bricked yet.
Does anyone think that there maybe a different eMMC chip on some of these notes that have shipped which have bricked. Wounder if there is anyway to tell anyone looked into this. Just a thought as it might not be the software but the chip on certain devices ???
Click to expand...
Click to collapse
hardware conflict with newly kernel source is possible. different chip revision on different batch of notes produced could also lead to the issue. but if that is to be ruled out not to be the case, then its either samsung released a broken/buggy kernel for public usage or they make changes to the kernel source to react to CWM and the rooting community. just like how apple kept changing their baseband kernel every now and then to block jailbreaking on idevices.
to me its more like a buggy kernel. no wonder they kept pushing and delaying the ics release. ever thought of that?

djtiny said:
I have to agree I don't understand how these bricks are happening. I have gone from Darky LC1 to LPY and then flashed Chainfire LPY kernel through mobile odin. I then got bored and flashed ICS stunner 26.1 through CWM. I have then gone back to CWM whilst on Stunner and Flashed Abyss Note Kernel 4.2. Then on the top of that I have flashed Alba V2 repack of LPY after a wipe/data from CWM and still no brick. I understand the risks involved but like I said not bricked yet.
Does anyone think that there maybe a different eMMC chip on some of these notes that have shipped which have bricked. Wounder if there is anyway to tell anyone looked into this. Just a thought as it might not be the software but the chip on certain devices ???
Click to expand...
Click to collapse
You might just be in the lucky position to have a phone which doesn't have the error.
But somebody also suggested that it makes a difference what you have fleshaed before the LPY rom...
I did not have anything else than stock GB befor the official update, but perhaps there is a way to flash a specific rom before going to LPY to be safe.
Do you still know your flash history?

Hi Shorty66,
Sorry to hear about your note. I can remember being on Darky LC1 base rom full root. I downloaded the LPY.tar file flashed this via mobile odin to flash LPY via mobile odin and wiped data/cache from that program. When this was completed I had full root with the premium suit installed. Battery life was naff so I booted into CWM did full wipe along with cache davlik and flashed Stunner 26.1 rom then when this was fully booted I flashed the kernel extracted from. 19 stunner rom via mobile odin. Then when Alba releashed V2 full repack this was flashed via Red Pill 4.2 as I have this on my SD card because of the brick issues. After this was flashed I rebooted into redpill and proceeded with Flashing the Alba V2 full repack zip. This has fully booted with full root and no brick. So I dont quiet understand why my device has never bricked as im a flashaholic I tell you my mrs I always on to me about it.
Sent from my GT-N7000 using xda premium

Yeah I can understand a buggy kernel but why release it as a proper update. I cannot see them delaying it just to add the premium suit. The note and S2 share the same hardware so the building of the rom should have taken the same amount of development time apart from adding the spen into the framework. The emmc chip if im not mistaken is what the rom and the free memory is on for the internal part of storage feel free to correct me. Im just spit balling ideas here but the way the partition are read on ICS is different as somebody developed a way to bind it like on gingerbread roms. What if the way that ics roms are made screws up and when another rom is flashed when wiping takes place it just erases all the partition info on the chip and this causes the brick. If that makes any sense and when it comes to write the info that seems to start bit sticks and there is no partition information of chip info to write to which is why it just hangs.
Sent from my GT-N7000 using xda premium

Pretty Weird Soft Brick

I wasnt sure where or even if I should post this I normally use V.5 as a daily driver but I wanted to try the latest Hydracore OC kernel with latest JB Paranoid Rom. Everything was cool on ParaJB, as it has been in other test drives, except that I kept losing root whenever I flashed Hydracore, and I know thats been reported many times but I couldnt fix it and I started thinking that it might have something to do with the way the PreRooted gb roms are rooted. No idea but anyway heres what I did:
I wasnt sure if I should flash try to SuperSu .96 from CWR to regain root (I think that I should have) so I started over and downgraded to gb via PC Odin using a pre rooted GB rom. I booted, confirmed root then flashed JB Paranoid 2.1 from recovery, booted and updated superuser in market and updated to latest binary in app.
So I try Hydracore again now that I updated the binary confirmed root GB to JB, but I lost root again with HydraCore so I was thinking, based on what i had read, that I probably messed up with Superuser but letting the market update it every time and that I should have downloaded and updated the binary with SuperSu instead. I really dont know why I didnt do that in the first place but I do that carelessness can get you into trouble.
So I flash the pre rooted GB again in PC Odin but this time I get into a bootloop and I cant even boot recovery...soft bricked? Tried to flash it in PC Odin a few more times, its flashing fine wo errors but no change no loop, its just stuck on N7000 logo.
I went back into download mode and did the standard download a stock gb rom, hope 4 the best procedure. This time it got further, it actually played the music, which I took as an encouraging sign that stock recovery would work & it did (I was a little nervous but I worrry 2 much) so I wiped cache, factory reset and finally booted, finally.
I still have no idea what happened and I still have to re-upgrade but I don't anticipate any issues with that. I guess this time I will try to install SuperSu from market before I flash HydraCore and/or flash .96 via CWR afterward I lost root and then Triangle Away.
...I must have flashed a thousand Roms, (counting other devices) but I cant remember ever losing the ability to charge. Only now do I realize why it always says have at least 50% charge, you really dont want to try flashing wo a lot of juice.

OC version of hydracore is not stable for all Notes. Try to reflash everything from Odin, use Speedmod
Sent from my GT-N7000 using Tapatalk 2

TopOfNewYork said:
I wasnt sure where or even if I should post this I normally use V.5 as a daily driver but I wanted to try the latest Hydracore OC kernel with latest JB Paranoid Rom. Everything was cool on ParaJB, as it has been in other test drives, except that I kept losing root whenever I flashed Hydracore, and I know thats been reported many times but I couldnt fix it and I started thinking that it might have something to do with the way the PreRooted gb roms are rooted. No idea but anyway heres what I did:
I wasnt sure if I should flash try to SuperSu .96 from CWR to regain root (I think that I should have) so I started over and downgraded to gb via PC Odin using a pre rooted GB rom. I booted, confirmed root then flashed JB Paranoid 2.1 from recovery, booted and updated superuser in market and updated to latest binary in app.
So I try Hydracore again now that I updated the binary confirmed root GB to JB, but I lost root again with HydraCore so I was thinking, based on what i had read, that I probably messed up with Superuser but letting the market update it every time and that I should have downloaded and updated the binary with SuperSu instead. I really dont know why I didnt do that in the first place but I do that carelessness can get you into trouble.
So I flash the pre rooted GB again in PC Odin but this time I get into a bootloop and I cant even boot recovery...soft bricked? Tried to flash it in PC Odin a few more times, its flashing fine wo errors but no change no loop, its just stuck on N7000 logo.
I went back into download mode and did the standard download a stock gb rom, hope 4 the best procedure. This time it got further, it actually played the music, which I took as an encouraging sign that stock recovery would work & it did (I was a little nervous but I worrry 2 much) so I wiped cache, factory reset and finally booted, finally.
I still have no idea what happened and I still have to re-upgrade but I don't anticipate any issues with that. I guess this time I will try to install SuperSu from market before I flash HydraCore and/or flash .96 via CWR afterward I lost root and then Triangle Away.
...I must have flashed a thousand Roms, (counting other devices) but I cant remember ever losing the ability to charge. Only now do I realize why it always says have at least 50% charge, you really dont want to try flashing wo a lot of juice.
Click to expand...
Click to collapse
Well I am glad that your phone is back to life. In your post I can not see that you have made a full wipe between flashes (GB and the custom rom). Maybe a wipe cache and dalvik could have helped. As you were already told, Hydracore OC version is not for all devices and might behave ramdonly so try to flash the Standard version of it.

iam pretty sure that I got tge wipes right but yea it wasnt a huge deal just strange
You don't want to wipe after you replace supersu either BC then you will lose it right and it will cause some sort of binary issue, is that even possible?
So I am pretty sure it was in fact an issue w supersu vs superuser
BC I am now once again using hydracore 3.4 OC group B wo issue (and its GREAT btw i love it) on paranoid v.5 w full root rights retained...but i dont think i csn factoryvl reset now wo losing root unless I first tell superuser to update ot bibary and retake control of root from Supersu then uninstall Supersu, or something like that, I haven't experimented enough to know what's what
So if u want to flash hydracore u just have to update supersu after you flash paranoid and probably any other Rom thats includes Superuser
From what I have gathered, if you download and update the binary from with SuperSu it replaces super user (as there can only be one at a time) I've found, at least on paranoid rooms, that if before you switch kernels you need to let supersu become the primary root binary and then flash hydracore you will retain root rights...messing around with the wrong binaries or perhaps having 2 might have messed up things when I went back to pre rooted GB and couldnt boot recovery, so I had to go back to stock
Hopefully this helps somebody who might have similar issues
Sent from my GT-N7000