Database Develop

[Q] foreplay with SC-02B (Japan/Docomo) : how to go further ?

Hello people !
Since I'm living in Tokyo, I'm the happy owner of a Galaxy S, but unfortunately it doesn't seem to be exactly the same like the other devices.
Anyway, since 2 days ago, I had some fun (and cold sweat also) trying to root it, unbloat it, etc... Some difficulties and questions left without answers, so if anyone has a guess, please be my guest !
My phone as I got it :
SC-02B, with OMJJ1 firmware (Froyo 2.2)
1) Rooting
The easiest thing ever.
The SuperOneClick pack did a wonderful job.
http://forum.xda-developers.com/showthread.php?t=803682
2) Getting a "safe" firmware
Just in case anything would go wrong, I wanted to be able to flash back to an official firmware.
The ones from this post work without any problem so far.
http://forum.xda-developers.com/showpost.php?p=10558974&postcount=134
However, problem 1 : I couldn't get Heimdall flash my device. Since I'm mainly working on Linux and OSX, that would have been of a great help.
But the "handshaking with Loke" step is always failing...
Actually, I even though I had bricked the phone, since I was stucked with a black screen (1PC and 1GSM in orange) and it took me ages to figure out how to get rid of that.
Solution : get myself a Win 7 computer at office and use Odin. No problem so far with this one.
Problem 2 :after flashing with the official update, I get complains in the recovery mode (when unpacking the apps I think), saying that /dev/block/mmcblk0p3 cannot be mounted, because it does not exist.
After searching on japanese sites, it seems that there is a 3rd partition in addition to the one for /sdcard and /data that is used (as far as I know, only for that) by an app called DioDict (japanese / english dictionary).
Not that this is a great loss, but I don't know where and why this 3rd partition was deleted. I tried to restore one, but after a while I just gave up, since I don't have any dump of the data that was there anyway...
Could anybody confirm/infirm this ???
3) Recovery 2e
Since I wanted to test to other roms, I needed to get back to the recovery 2e.
I gave a try to CF-root, which included that also.
http://forum.xda-developers.com/showthread.php?t=788108
Once again, Odin was the only one that could do the job, Heimdall still ignores me.
Problem : the update is successfully done, but for a reason I ignore, I lose my SIM card in the process.
Flashing back an official ROM makes it available again, but CF-root won't allow me to phone in Japan.
How did you people handle that ? Unfortunately I couldn't afford staying too long without a working phone, so I didn't investigate much further, but did other people have the same kind of problem ?
Conclusion :
As of now, I have a rooted device, and am pretty happy with it.
However, I wish I could give a try to the nice work I've seen around (CyanogenMod on Galaxy S seemed very yummy), while still being able to use my SIM card here.
Any feedback is welcome !

I haven't played around that much with DioDict to tell you right away how to solve this, but maybe there's some answer getting the first firmware:
SC02BOMJJ1 (10/10/13) :
http://fus.samsungmobile.com/Phone_...2BDCMJJ1_SC02BOMJJ1_SC02BOMJJ1_OM_DCM.zip.enc
BINARY_ENCRYPT_STRING 1662317

thanks a lot for this link ! just a question, where did you guys find them ??? the site itself seems very dummy
but as far as I could read on japanese threads, that seems to be some prefab settings
in my case, that third partition has been deleted, so I think I would have to recreate again beforehand.
as for the "how", I must confess I don't know... I' had somehow succeeded in running parted to create one, but for a reason I ignore couldn't assign it to the block

I could install a Cyanogen Beta3 today, and though everything is alright, still got no 3G.
SIM card is not recognized, and it seems impossible to input the appropriate APN information. Could it be that the modem embedded in the SC-02B is different from the mainstream one ?
EDIT : seems that indeed the SC-02B has a different modem. At least the firmware has a different size, hence the need of a different PIT file when you flash from an "international" ROM.
I'm starting to wonder whether I'll see the end of it someday >_<

things that seem to work
Now that we have the capability to recover after we trash our ROM what can we do.
Super Oneclick root - works
Z4Mod "because we all have the need for speed" -works after you use titanium backup to remove some of the bloat-ware from /system
Z4Control works if you use Z4Mod to patch the kernel and convert /data to ext2 first.
The UOTKitchen will work to change the battery icon and other status bar icons if after you have completed these steps http://forum.xda-developers.com/showpost.php?p=9318973&postcount=1290 you extract the framework-res.apk from the resulting zip file and use adb to push the new framework-res.apk to /system/framework/framework-res.apk followed by an adb reboot recovery command before you do anything with the phone. From the recovery menu wipe cache and then reboot now. If you don't do this last step it could lead to having to reflash the factory firmware happened to me about 6 times this weekend. DO NOT TRY THIS IF YOU HAVEN'T CLEARED ENOUGH SPACE ON /SYSTEM BECAUSE IT WILL KILL YOUR PHONE!!!!!

For all those who want a pit file, here I leave you a custom pit file created for the sc-02b.
I must make this clear, this PIT file was made for those who flashed their devices with a rom for some other galaxy s version and want to reflash their devices back to the original SC02BOMJJ1 rom. I cannot ensure you it will be useful or that it will work for anything else.
Also, when using this PIT file with odin, be sure to check the "Re-partition".

@shikigamild :
is this PIT file the same that came from komugi.net ?
at the same time, could you tell me how you got the stock rom file links please ?
@dejanet :
so you say that with the Z4mod you have a fully working device ?
has anyone tried the CF-root package ? after applying it I lost my SIM card, so I wonder if you experimented the same kind of inconvenient there

Oh yes went through all of the fun of trying the various kernels everyone leaves you with sim not recognized.
Sent from my SC-02B using XDA App

Aaarghh,that sucks donkey balls...
Guess that means we won't get any, custom rom any time soon will we?

I'm new to all this stuff, so apologies for the noob questions.
I rooted my SC-02B using the tool in this thread. I was able to install and use the Barnacle Wi-Fi tethering app from the market, so I know it was a successful root. Now when I go to install and use Titanium Backup from the market, it tells me I don't have root access or don't have BusyBox installed. When I go to install BusyBox from the market it shows my phone as being rooted, but when I tap install it gives me a failed message saying my phone isn't NAND unlocked.
How do I do that? Once I get that problem solved, what are the next steps for installing the Z4Mod?

So far I've never installed BusyBox through the market. Just install it with Titanium and it should work fine (click the "Problem ?" button).
Then, I suggest that before doing ANYTHING involving a custom initramfs (like ClockWorkMod), you dump somewhere your mmcblk0p3 partition, in case you want to restore your phone exactly to the same state you got it.
If your not that paranoi, you can skip this part, but as I wrote myself a dozen times here, I forgot it and would be interested also ^^

Ok, thank you for the info. Does Z4Mod cause any problems with this phone? I read in dejanet's signature that the lagfix seems to cause problems. Z4Mod is the lagfix he's talking about right?

bnr32jason said:
Ok, thank you for the info. Does Z4Mod cause any problems with this phone? I read in dejanet's signature that the lagfix seems to cause problems. Z4Mod is the lagfix he's talking about right?
Click to expand...
Click to collapse
z4mod is just a rooting app. There's no lagfix. He's probably referring to OCLF which is made by the same developer. It's obsolete now, so do not use it.
About the rom problem, can't you just flash the modem from a Docomo rom after installing the custom rom?

No, z4root is only for rooting, but z4mod is a lagfix application. As far as i know, it will convert your phone system to ext2. However, i scare it will affect the DioDict application in SC-02B, so i haven't tried it yet.

Trojan,if you fear losing diodict,you can still dump your mmcblk0p3 partition.
It is the one containing diodict data.
I would actually be very grateful for an upload of that one (^-^)/
Sent from my SC-02B using XDA App

trojan111 said:
No, z4root is only for rooting, but z4mod is a lagfix application. As far as i know, it will convert your phone system to ext2. However, i scare it will affect the DioDict application in SC-02B, so i haven't tried it yet.
Click to expand...
Click to collapse
Opps. Didn't realise there are two apps with similar names.
Still, wouldn't suggest it. EXT2 is unstable.

Hi, bebert218. Actually, i am a noob, i don't know how to do it. Can you tell me how to view the partitions in the internal memory? I suppose DioDict application contains a database file somewhere in the internal memory, but i don't know where and what the file name is. Appreciate if you could give me a hand on it. Thanks.

Custom Kernel and Roms
From reading through the forums it seems custom roms present issues with the either the sim card or modem on the sc-02b. Are custom kernels causing issues as well on this phone?

Yes it is the kernel that causes the problem. I think a couple of us have tried them all.
Sent from my SC-02B using XDA Premium App

disappointing Other than rooting and using Galaxy tuner to do some tweaks there isn't really much else to do. At least the upgrade to omka5 showed much improvement from 2.2

How can a Captivate phone SGH-i897 show different model in specs screen?

I'm hoping someone here can help in explaining this because this is something I've NEVER seen or heard of before and in theory, shouldnt be possible but i'm seeing it with my own eyes!
I'm (about to) purchase a slightly used Samsung Galaxy S CAPTIVATE model (SGH-i897) at least that is what the "boot up screen" shows.. I KNOW this is the Captivate.. i've seen the physical differences between it and the Vibrant.. they are basically the same phones hardware wise but do have a different physical appearance on the outside.. the Vibrant's model is GT-i9000..
now when I go to the "About screen"...the model shows the GT-i9000! How is this possible? I'm baffled because I know that i'm actually looking at a CAPTIVATE and the boot up screen shows the correct model number..but the android os (which shows the gingerbread 2.3.5 model in the about screen) is showing the model number as the VIBRANT.. gt-i9000, on the same phone!
I want this phone and was about to buy it but i'm thinking this could seriously cause problems when i go to root and mod it as the conflicting model numbers could create problems with the proper files and processes i'll need to follow when doing the root/mods...
Has anyone heard of this or can explain this because I am STUMPED!
THanks

ok, it appears like a custom Kernel was used cause this conflict. Make sense?
I looked at the About screen again and the KERNEL VERSION looks like something that is NOT the stock kernel. It states:
2.6.35.7-I9000XXJVT-CL617736
[email protected] #DarkCore_4.1_JVT_C
this has to be a custom Kernel right?
This phone must have been rooted and mod'd at some point (the seller didn't know and thought his cousin only unlocked the phone).
I assume a custom kernel that likely is typically for the Vibrant GT-i9000 was flahed with or without a custom rom to this phone and that is why there is the conflicting model numbers... this make sense?
Normally that wouldn't be good idea to use another kernel or rom for a slightly different model of phone but i guess it worked..
I would now like to confirm that this is the case and if so, that it is obviously ok..cuz the phone is working fine.
Should I now wipe the phone back to stock rom/kernel? Can I? if I want to do more mod'ing on the phone anyways.. different kernels and likely update os to ICS 4.0
Thanks for any help on this and hopefully this all makes sense now and explains what i'm seeing

Many of the custom builds for the Captivate are based on I-9000 framework. DarkCore is one of the custom kernels. This phone has been flashed. If you prefer a stock Captivate firmware, there are ODIN One-Click programs in the Development section that will put you back to an "Out-of-the-Box" state. Then do some reading if you plan on shopping around for different roms, as there are several different sets of bootloaders among them and a bootloader mishap is a surefire way to brick this phone.
Happy Flashing and good luck! Welcome to the Captivate!

The vibrant model number is T-959 or some ****..I9000 is the international galaxy s. The original.
It is really easy to switch what is displayed in about phone...it's all in the builds.prop located in /system
You can open that up with a plain text editor and change any instance of Gt-I9000 to sgh-I897 and Viola...
But as mentioned above, flashing to stock with Odin/heimdall will get you back to stock.
Btw what does "build number" say in about phone? Cause that is the name of the ROM that was flashed to it.

Build number says: Mosaic 8
So that is the custom rom that was flashed to the phone I take it?
Ultimately I dont want to go back to the stock rom/kernel but want to definitely flash to OTHER custom roms/kernels. With that being said will I have to go back to stock on either rom or kernel FIRST before doing another change?
I'd like a kernel that will allow me to play with some overclocking and the rom(s) can be one of many.. preferrably I want to put ICS 4.0 on this
Can anyone give me the links to the best info/tutorials to flash the kernel/rom's to do so on this phone?
As said, the actual phone is an unlocked and rooted AT&T Samsung Galaxy S Captivate SGH-i897 but has been already flashed with custom rom kernel as follows:
Model Number
GT-i9000
Firmware Version
2.3.5
Baseband Version
I9000UGJK4
Kernel Version
2.6.35.7-I9000XXJVT-CL617736
[email protected] #DarkCore_4.1_JVT_C
Build Number
Mosaic 8
Thanks

M8 is a great custom rom. You shouldn't need to flash to stock before flashing a new rom. Just follow the steps in the first post of each rom you want to flash. A good ROM to try next would be Mosaic 9

yeah...i hear great things about mosaic!

Thanks..i figured it was a good rom..i play around with it for a while.. it also came with the custom kernel from DarkCore..
I'm fairly new mod'ing rooted phones and all that so I'm curious if I can install a different custom kernel on this Mosaic 8 Rom and if so, what's best way? I want to use one of the many on this site that allow for oc'ing...is it ok to replace the Darkcore Kernel that came with this rom to any other or not?
THanks

hey buddy, i happen to be the lead developer for mosaic.
you are more than welcome to change the kernel, the best way to do that would be in cwm recovery...which can be accessed by holding down on the power button and choosing recovery. or by powering off and holding vol up and power til you see the first splash (that should actually say I9000) then let go that will boot into recovery.
if you see an at&t screen at all the its vol up AND down AND power.
as said above i have updated mosaic, and the latest version includes a kernel that is overclockable already, this one to be exact the .tars in post 1 are for use with odin. post 2 are zips to be flashed in recovery. ater the kernel is flashed it will install an app called semaphore, in there are a bunch of options including oc up to 1300Mhz
that being said...FIRST I would play around with it some more and get used to it WHILE DOING SOME RESEARCH AND READING...i mean you just got the phone...get to know it take her out on the town before you get her all nekkid and vulnerable

THANK YOU SO MUCH for this reply! I was just trying to get into recovery mode and I noticed this phone was allowing me.. this is due to the rom/kernel on it..but you're post with the info WORKED! I was about to start doing a bunch of stuff to try and fix.. THANKS
This whole double splash screen is very new to me with it showing the phone as TWO different models..
I see you have the new Mosaic 9 out..and that's the one you're takling about i take it? and it comes with another new custom kernel that will allow for oc'ing too? sounds good..and 1300 is more then enought.. I'm happy with 1.2 if I can.. dont need to get crazy and try for 1.6 like some..
Just follow the steps on the main page for that rom and all should be good? What will be the easiest way for me to flash to your new rom/kernel? Can I do it from a rom manager or use sd card or internal mem? Any help on this is greatly appreciated! Thanks again for posting a response to my concerns!

btw can i just update this Mosaic 8 rom to that new custom kernel you're talking about or do i have to update to the new Mosaic 9 rom first?

You can flash that on 8.
Don't ever use ROM manager, it doesn't work right on the galaxy line.
And whenever sdcard is mentioned, that is the internal sd, cwm does not flash from an external sdcard.
To flash mosaic 9 over 8 just put ROM on sdcard, boot into recovery, wipe data/factory reset, then go to install zip from sdcard, choose zip, and find the ROM you just downloaded.
Flash the kernel the same way, just don't do the wipe first.
The ROM flash will wipe all your apps, the kernel will not, use titanium backup to backup your apps, then restore them after the flash. Again only needed if you're flashing the ROM and you can flash the kernel on the ROM you have now,
but a backup is a good idea before any flash if something were to go arwy.
As for the 2 boot screens (and the different button combos for recovery, btw download mode is vol down and power), is because the phone has I9000 bootloaders, which is the first splash you see, the second splash is the kernel, both darkcore and semaphore use the same splash the one that says sgh-I897. some kernels use a custom image there instead.
But again, i urge you STRONGLY, PLEASE read, and understand completely what it is that you want to do, and more importantly how to fix a situation that doesn't go as planned, BEFORE you start flashing stuff. Please.

Thanks again bud this is all so helpful. I already downloaded your mosaic 9 zip. Quick question..do i have to format my sd card a certain way first for the update to work? on past.flashes on different phone certain.partioning had to be done on the sd card in order for the update to work.successfully.
Thanks n looking forward to this mosaic 9.
Sent from my GT-I9000 using XDA App

Nope, you're good. Anything that was needed, which was flashing gingerbread bootloaders, has already been done by the previous owner.

Thanks again bud. That last question was pointless cuz i read back again and u mentioned that the sd card stated is always internal and not external..so obviously i wouldnt need to format n partition etc. Thats a bit newer for me well on this new phone anyways. Used to using ext card in past.
As of now ive only updated the kernel to the new one and not the whole new rom...yet. Will play around with it for a bit. The oc was very easy and working just fine.
Btw any plans to do this mosaic rom on ICS 4.0 at all? Or maybe there is one u could recommend? i really want to check it out as so many are "raving" about the new ics os and that it the best by far, etc. Whats your take?
One other question about the flashing from the internal sd now, hope this aint silly but if the zip rom file is saved to the internal mem and im doing the usual data wipe/factory reset wont everything get cleared.including the rom file itself and then not find it when i go to do the update?
and again thanks for all the info, still a bit of noob when it comes to the phones side of things but fyi im definitely a techie when it comes to the pc hardware, software and networking side. Take care
Sent from my GT-I9000 using XDA App

Data wipe/factory reset only wipes the /data partition. Leaving all others including /sdcard intact.

Data factory reset clears (/data, /dbdata or /datadata depends on the ROM you are on, /cache, and /mnt/sd_card/android.secure

Definitely gonna wait a while before flashing any ICS4 roms as still too early and lots of bugs to workout. Im hoping u guys eventually come out with an ics rom cuz this mosaic 8 n 9 are damn good and high quality and read a lot of good things too.
Sent from my GT-I9000 using XDA App

So the bootloaders, when are they input or changed? Is it a seperate update or do they typically come with a rom or kernel? So the ones i have now with the dual splash screens (gt-i9000 then sgh-i897), will i keep those if i wipe and flash a different rom or will a new set of different bootloaders come with most other custom roms? I still dont fully understand that yet and would prefer to mess with them as little as possible cuz i know how important they are and thats an easy way to mess up a phone.
Another quick question i have is about the Captivate phone itself...i know all the specific hardware specs and its states it has 512 ram outside of the 16gb storage/2gb internal rom but why can i only find spec screens that show my phone having 323mb of ram and of that most of it is used up all the time even after a fresh wipe and flash of the mosaic 8 rom ane nothing new installed? Does this have something to do with the rom itself or am i missing something? a little puzzled by this. Part reason i upgraded to this phone was to get better hardware and have more memory cuz i like to eventually install a ton of apps but im thinking i could quickly run into issues with the numbers im seeing. Any thoughts on this? Thanks
Sent from my GT-I9000 using XDA App

Bootloaders ate only flashed with a pc flashing program such as Odin or heimdall.
The second image may change, that within the kernel itself, the first image will not.
As far as storage space goes, you have 16gb on the entire phone. 2gb of that is for user apps. About a Gb for the system, and about 13Gb on the sdcard.
you do have 512mb of ram, but some of that is always used by the system leaving the user with 323. And THAT being mostly used up is just they way Android handles memory. It keeps recently opened applications loaded in memory so that if you wanna access it again it will open much faster than having to reload it. It will also kill off apps as the memory load grows. Put simply: free ram is wasted ram.

What did I do wrong? N7000 bricked.

Good evening!
I've around with Androids for quite some time, and today, I finally got my N7000 to replace my I9100.
I've played around quite a lot with my I9100 and was happy with the CM9 nightlies for it.
I got my N7000 today and did the following:
1. Rooted it with this method: http://forum.xda-developers.com/showthread.php?t=1501719t=1501719
2. Decided to install the latest CM9 nightly. I booted the same CWM from the tutorial above, chose install zip from SD card and... It hang. I left it for about 5 minutes and nada, nothing. I decided to shut if off and...
3. Nada. Black screen, no recovery, no battery charging, no download mode, no nada, nothing. Dead!
I'll take it this week to the nearest Samsung repair center and check how much it's gonna cost to get it fixed (if they can get it fixed at all). I don't intend to use any warranty whatsoever since I know even tough I have not voided the warranty flashing a different kernel, I did messing with it.
I just wish to know what was my mistake, so I do not do it again in the future. AFAIK I did not mess with the bootloader, so I was supposed to be safe, right?
Do I have ANY hope of getting it resurrected?
Any opinion helps!
Thanks!

marcelo.ellmann said:
Good evening!
I've around with Androids for quite some time, and today, I finally got my N7000 to replace my I9100.
I've played around quite a lot with my I9100 and was happy with the CM9 nightlies for it.
I got my N7000 today and did the following:
1. Rooted it with this method: http://forum.xda-developers.com/showthread.php?t=1501719t=1501719
2. Decided to install the latest CM9 nightly. I booted the same CWM from the tutorial above, chose install zip from SD card and... It hang. I left it for about 5 minutes and nada, nothing. I decided to shut if off and...
3. Nada. Black screen, no recovery, no battery charging, no download mode, no nada, nothing. Dead!
I'll take it this week to the nearest Samsung repair center and check how much it's gonna cost to get it fixed (if they can get it fixed at all). I don't intend to use any warranty whatsoever since I know even tough I have not voided the warranty flashing a different kernel, I did messing with it.
I just wish to know what was my mistake, so I do not do it again in the future. AFAIK I did not mess with the bootloader, so I was supposed to be safe, right?
Do I have ANY hope of getting it resurrected?
Any opinion helps!
Thanks!
Click to expand...
Click to collapse
ALWAYS flash a GB Kernel or ROM BEFORE flashing a CUSTOM ICS ROM.

Okay. Lesson learned, trust me.
Now here's the part where I feel very stupid: what's a GB kernel? Why is that a requirement for ICS ROMs? Was it not for Gingergread ROMs?
And now here's the second part where I feel even stupidier: doesn't the kernel reside on the ROM/OS part of Android? Why would the kernel, which comes AFTER the bootloader, affect the boot of the Android? Wouldn't it just screw my phone, but wouldn't it still give me the chance of flashing another ROM?
Thanks for the help.

marcelo.ellmann said:
Okay. Lesson learned, trust me.
Now here's the part where I feel very stupid: what's a GB kernel? Why is that a requirement for ICS ROMs? Was it not for Gingergread ROMs?
And now here's the second part where I feel even stupidier: doesn't the kernel reside on the ROM/OS part of Android? Why would the kernel, which comes AFTER the bootloader, affect the boot of the Android? Wouldn't it just screw my phone, but wouldn't it still give me the chance of flashing another ROM?
Thanks for the help.
Click to expand...
Click to collapse
Because of an eMMC brick bug!
Anyways to round up, my way of flashing ROMS is flashing a GB Kernel called Abyss 4.2 and then reboot recovery, from then I wipe everything then flash any custom ICS Roms. I've had my Note for almost a week now and found no problems in flashing! But it did take me 2hrs to root doing heavy research but it paid off!
The guide I followed is from here take a few moments to read and understand then you will have no troubles in rooting/flashing again!

hing98 said:
Because ICS has not been officially released on the Galaxy Notes therefore we use a GB Kernel or ROM before we flash any custom ICS ROM.
Yes it was confusing at the start but to avoid bricking you must alwaysfollow the guides given by the Developer!
Anyways to round up, my way of flashing ROMS is flashing a GB Kernel called Abyss 4.2 and then reboot recovery, from then I wipe everything then flash any custom ICS Roms. I've had my Note for almost a week now and found no problems in flashing! But it did take me 2hrs to root doing heavy research but it paid off!
Click to expand...
Click to collapse
You may want to recheck your facts....ICS has actually been officially released in many countries......
Sent from my GT-N7000 using xda premium

stoney73 said:
You may want to recheck your facts....ICS has actually been officially released in many countries......
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Sorry was reading from another guide. Your right
---------- Post added at 01:12 PM ---------- Previous post was at 12:23 PM ----------
hing98 said:
Sorry was reading from another guide. Your right
Click to expand...
Click to collapse
Anyways its a bug that bricks your device,
you can find more information here
Cheers

I had a galaxy S where flashing process was different Wen u flash CM9 roms and if you want to get back to GB roms only way out was PC Odin and moreover you can wipe on ICS roms and install other roms. But wen i got the note the procedure was slightly different Brickin problems and moreover wen you are in ICS you can get back to GB with GB kernel only no need for PC odin. Just keep a copy of Abyss kernel 4.2 in your sd card and be sure to flash it when changing roms.....

Doesn't Franco rev3+ solve the brick bug?
Hi all,
since you're saying we have *always* to flash a GB kernel before having a factory reset, are you talking about those having the CF/Stock kernel?
I'll make it clear: as far as I know, Franco made a kernel that should avoid the brickage since its 3rd version (thread here --> http://forum.xda-developers.com/showthread.php?t=1491428). Who installed this kernel could just wipe from ICS and install any ICS ROM. Am I wrong? If so, please explain the whys.

UNBRICKED!
I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.

I'm on i9220ZCLP6 kernel. Need some advise.

I'm on ICS Stunner right now which means my kernel is I9220ZCLP6. I've read that i can not flash from this kernel which is about to be right because since I'm on this ROM I can't flash any other custom rom because of some error while installing a ROM. I did full wipe in CWM many times and i remember that about four months ago my phone stopped working correctly and I couldn't install any ROM not even ISC Stunner. Then what I did was installed I9220LP1-N7000-ICS-REPACK again and it worked fine and since then I'm on ISC Stunner. But now I want change and install Rocket ROM or Asylum. Mostly I need tablet mode and I know that Asylum got one but I'm not sure if Rocket ROM have one? In Rocket ROM thread I found:
d) coming from CM9, ROMs based on CM9 or other ICS AOSP ROM:
- boot in Recovery
- FullWipe
- Flash ROM
- reboot system
-...you are done
Whenever you do a FullWipe:
- install Abyss Kernel 4.2
- boot back in Recovery (find it under 'advanced')
- now FullWipe!!!
- Flash ROM
- reboot system
-...you are done
==> ONLY, ONLY, ONLY FullWipe with Abyss Kernel 4.2 installed!!!! NEVER, NEVER, NEVER Full Wipe with CF-Root Kernel installed!!!
But I also found that first I have to return to stock ROM and some people hardbricked theirs phones doing this. So I don't want any mistakes. Please tell me what's best in my situation?

Its suggested to flash stock root able gb rom first and foremost, then you can follow the steps above.
It sounds like the damage is already done though. If the flash gets stuck at factoryfs.img then you know there's trouble ahead and you may need to repartition the emmc chip.
Best of luck.
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!

Since Stunner thread got closed and many people suppose that ROM won't get any further development it would be a good idea to write a thorough instruction on how to switch from the Stunner ROM safely.
Need some brave guy to try to escape "already damaged but still working NOTE by Stunner" and update an instruction on this for everyone.

The reason I said that it seems the damage has already been done is that you were only able to reflash the same ics repack kernel. This suggests that you're only able to access the emmc that you were originally using. When trying to write a different kernel or rom, it sounds like its failing to write to the new sections of emmc, suggesting damage.
It would be more helpful if you tell us how the writes were failing, how you were flashing (PC Odin/mobile)? Was it failing at factoryfs.img?
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!

SpyderTracks said:
The reason I said that it seems the damage has already been done is that you were only able to reflash the same ics repack kernel. This suggests that you're only able to access the emmc that you were originally using. When trying to write a different kernel or rom, it sounds like its failing to write to the new sections of emmc, suggesting damage.
It would be more helpful if you tell us how the writes were failing, how you were flashing (PC Odin/mobile)? Was it failing at factoryfs.img?
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
Click to expand...
Click to collapse
It was few months ago and I don't remember but 90% it was factoryfs.img error and that happened few seconds after begining install process of other ROM then Stunner. All the time I've been using CWM for data wipe/cashes/dalvik/installing roms/fixes. I didn't know about this issue then and I don't think that anyone knew. I remember that my phone didn't want to boot up sometimes before stopped working but after i fixed it it's alright so obviously I shouldn't change anything and leave it like that But before I start doing anything with this phone I need to know where can I get new motherboard from in UK and what is the cost? For 50 pound I can take the risk but if it's much more it's not worth it. It needs to be in the UK because if I'll ****ed up I need new parts as soon as possible. Ok, I'm waiting for some answers now. Thanks.
PS. I've found this tutorial

bulla666 said:
It was few months ago and I don't remember but 90% it was factoryfs.img error and that happened few seconds after begining install process of other ROM then Stunner. All the time I've been using CWM for data wipe/cashes/dalvik/installing roms/fixes. I didn't know about this issue then and I don't think that anyone knew. I remember that my phone didn't want to boot up sometimes before stopped working but after i fixed it it's alright so obviously I shouldn't change anything and leave it like that But before I start doing anything with this phone I need to know where can I get new motherboard from in UK and what is the cost? For 50 pound I can take the risk but if it's much more it's not worth it. It needs to be in the UK because if I'll ****ed up I need new parts as soon as possible. Ok, I'm waiting for some answers now. Thanks.
Click to expand...
Click to collapse
Where did you buy the phone? If it was bought new from operator or sim-free then you'll be under warranty and if you brick again, there's no way they can check for binary counter or what rom you have installed. You just say it broke after ota update to ics, and it'll be fixed under standard 1 year warranty. Just need proof of purchase. Either send it to your operator, usually next day collection and up to 2 weeks fix, or Samsung will direct you to a local partner who'll fix it, probably under similar time frame.
If it was eBay or second hand then different story. From what I've read of others getting replacements outside warranty its around £150-200 for new motherboard.
That emmc "fix" you've found will repartition the chip so you bypass the damaged section, so you lose storage, often between 3 or 4gb of internal storage.
Hope it helps.
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!

SpyderTracks said:
Where did you buy the phone? If it was bought new from operator or sim-free then you'll be under warranty and if you brick again, there's no way they can check for binary counter or what rom you have installed. You just say it broke after ota update to ics, and it'll be fixed under standard 1 year warranty. Just need proof of purchase. Either send it to your operator, usually next day collection and up to 2 weeks fix, or Samsung will direct you to a local partner who'll fix it, probably under similar time frame.
If it was eBay or second hand then different story. From what I've read of others getting replacements outside warranty its around £150-200 for new motherboard.
Hope it helps.
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
Click to expand...
Click to collapse
I've got my phone from affordablemobiles.co.uk with T-mobile. Now I don't know if there won't be any problem returning this to T-mobile. Propably I'll have to deal with affordablemobiles because they sold me the contract about 10 months ago. That tutorial I've posted in my last post it seems to be alright. Maybe I'll test it later. First I need to change display in my old HTC HD2 for in case of hardbricked N7000.

All the best dude. Repartitioning does work, no doubt about it, but for a true fix and if you're able, it would be worth sending it for replacement under warranty to regain maximum internal storage space.
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!

[Q] In light of the eMMC bug, is the N7000 still worth getting?

Hi All,
Just curious how serious the eMMC bug is, and whether the N7000 is still worth getting??
1) Is the bug only present in ICS Roms, with unsafe kernels?
2) Is the phone safe using any of the GB or JB Roms, assuming it is only ICS thats at fault with the chip?
3) I've heard CWM is also dangerous to use, is there a certain one/version to use? (namely, Philz?)
4) How do you prepare the phone from ROM flash? All other Android devices I use to do Factory Reset Wipe in CWM, followed by wiping System and the Cache section. What can I do now, or cant I do... for fear of bricking?
5) Is this App [GalaxSim Unlock, by spocky] ok to unlock, does it work or can it be dangerous in light of eMMC? Or should I get a carrier unlock?
6) If using this phone normally, normal Apps... Is there a risk to bricking if the App write to write to the internal storage?? (such as saving files/settings) or is only if you attempt to wipe it?
7) Whats the absolute do's and DONT's with this device, like to stay away from....
I'm really keen to buy it, but dont want to end up with a BRICK through a silly mistake....
- sorry for all the questions, just really confused by whats ok and whats not...
Thanks, Lister

Emmc brick bug was there in ICS for sure but it is not worth trying on JB as it is no fun to see if the device gets bricked or not.
You can use GB (which has safe kernel) you can do the wipes. ICS and JB there are many custom kernel which are brick bug safe, meaning that it would not brick your phone if you have these kernel (say Philz for example) which also give you CWM and you can do wipes as many times you want without the risk of getting bricked. Philz kernel is available for all the versions.
For how to flash stock rom and list of stock roms use this:
http://forum.xda-developers.com/showthread.php?t=1424997
i dont have any idea about unlock, you may wait for someone to respond to that.
when using the phone normally there is no risk of brick.
Dont wipe the device on stock recovery and you are safe, to be safer always use Philz kernel. if you want to claim warranty at any time you can always flash stock rom again.

Own a note for 5 months now and this device is as good as any for the flashing of ROMs and kernels. So this is surely a safe buy. The PhilZ kernel is not particularly what i am fond of as it caused problems for the flashing of certain ROMs as the recovery is CWM based and not CWM recovery. And i do not have any info about the unlock app

Hi Treacherous_Hawk and Varad297,
Thank you both for your comments and suggestions, all this info I am picking up is very useful for me... As I may of said above, but have certainly said in other places across this board (and other sites). I'm fairly ok/confidant when it comes to Android, and the other Android hardware in my collection. (ZTE Blade, HP Touchpad, and MK802-II) Dont suffer from any kinda serious bug, and are brick free, they will never die... But I must admit, I am a little scared of this eMMC bug in N7000.
So thanks for putting my mind at rest....
If / When I do get this phone (through a mate of a mate), in October when her contract runs out. Will be locked to Vodafone UK, and I am T-Mobile UK, and I believe its currently running on Android 4.1.2 JB Stock.
However I want to flash the P.A.C. Rom to it straight away, as I have this on my ZTE Blade and HP Touchpad and love it...
So whats the best way to do it...??
1) Download Philz Recovery (and which version would I need, being that the rom its on is 4.1.2, and the rom I'll be taking it too is 4.2.2)
- I assume I copy this to SD Card, and flash in Stock Recovery, via going to Download Mode
2) What steps would I follow to clear of current rom? What wipes are safe, or are they all safe with Philz? Normally I do Factory Data wipe, and then System and Cache...
- Are these fine under Philz recovery? As from above two comments... First reply says its safe to do so, second reply says its dangerous... Just really scared about this bug, cant believe Sammy released a device like that...
3) I assume I flash it in Philz CWM, rather than ODIN? Do I need to re-flash a kernel straight after or is the one in P.A.C. (4.2.2) safe from bug?
4) I think the ROM is pre-rooted, but what should I do in case its not? Use ODIN or is there an easier method?
I assume flashing the above rom, via the above method (Philz CWM) will then result in the Yellow Triangle, and bump the count upto 1? So do I just use Triangle Away to clear and reset this, and this is again safe of bricking???
Thanks, Lister

Dude dont panic.
P.A.C. Rom is rooted and does not trigger the emmc bug.
Safe way from stock is as follows:
1.
!DO NOT WIPE ANYTHING ON STOCK!
2.
Get philz kernel for your stock version.
there are packages for flashing with either ODIN which involves connectiong a Computer or with Stock Recovery, which does not involve a computer.
The latter, which is simpler is simply a file on SD you can flash through stock recovery (when off press power+home+volup), it wont even void your warranty.
That provides you with a CWM like recovery from which you can wipe or flash other roms WITHOUT triggering the brickbug.
3.
Get your favourite Rom and flash it through cwm recovery.
BTW: Almost everyone who releases for N7000 puts something in the description that says if the rom is bricksafe.
All newer AOSP/CM based roms should be bricksafe.
Most of the customized Touchwiz Roms are also bricksafe, but watch their thread to be sure.
hjsdfbglsmhjc8we
EDIT:
IMO if you get the Note 1 for free or cheap its well worth getting. If you plan to buy one rather look for the Note 2 because I feel that it is better supported and has better customisation diversity.
Or if I ask myself what my next phone will be... dunno. Maybe a Nexus or Xperia Z or HTC? I cant seem to find the perfectly blended device. Might go with Jolla Sailfish device if it proves usable.
EDIT 2:
I think someone should sticky this as a simple guide for this. Also the existing stickies really need a cleanup to not confuse people with too much information out of differing times.
Does XDA pay moderators? I'd happily clean stickies and test stuff all day. (I'd also assume a neutral persona/state of mind for such activity.)

Hi Illidan Pornrage,
Thank you so much for going into great detail of the steps I need to follow, I'm starting to feel more comfortable at doing and using this now... So any ROM that says they are Brick free means there is no way to trigger it?? Not that I have ever done this, maybe when I first got my Android back in 2010 just to see what it was like... If I did Factory Data Reset in P.A.C. Rom it wont trigger the eMMC bug? (not that Im likely to ever use it... just making sure).
And with Philz CWM Recovery, I can use the Wipe Data/Factory Reset and then goto other screen and wipe the System partition, and the Cache and Davlik Cache with it all being ok... its 100% safe in Philz Recovery to not brick it??
I am so use to CWM on other devices, I am scared of using the wrong selection on the famous N7000 eMMC brick bug... lol
But with the other steps, thank you so much, such a HUGE HELP!!! and I am sure that will put other new (to N7000) users minds at rest...
-- So useful that ya know the above ROM too, as it makes it even easier/safer for me knowing all is gonna be ok with it...
Cant wait to get ROMing now... Just gotta wait till October... b*gger!! lol
Cheers, Lister

If I did Factory Data Reset in P.A.C. Rom it wont trigger the eMMC bug? Yes as often as you like. I flash cm nightlies, so I wipe very often.
And my window manager somehow always loses focus of the textbox. So I write half posts and have to edit 346243 times. Sorry.
And with Philz CWM Recovery, I can use the Wipe Data/Factory Reset and then goto other screen and wipe the System partition, and the Cache and Davlik Cache with it all being ok... its 100% safe in Philz Recovery to not brick it??
Also yes.
As for 100%. I cant assure you that nothing obscure that only happens 1 in a million times happens. But the menchanism that triggers the great evil bug is removed from philz and the mentioned roms.

Phewwww..... so this eMMC bug is no big deal then....
Only an issue if you stay on stock firmwares really, esp that of ICS??
Well thats made me feel a whole lot safer and more determined to want to get it. Had my hopes set on getting it, and then when I heard about the eMMC bug, thought is this gonna be a wise purchase or will I be spending the best part of £150 (dont know the final price yet) on a very large and heavy paper weight!! lol
Thanks so much for putting my mind at rest, great help...

Hi Illidan Pornrage,
I've only just seen/noticed your updates to my original questions, thanks for the updates.... Re: Why am I going for just the Note 1 rather than the Note 2. Is that someone a know (mate of a mate) will be upgrading her phone (she prolly gonna go back to Apple... boooo) and so hopefully she will be parting with her Note (and cheaply I hope, esp re the bug... a-haaaa)
- and couldnt agree more about tidying up the Stickies, as yes a lot of it is out of date, hence my asking and checking... To which you fully re-assured me of the steps, so think this would be useful to all...
Just to add to this, which Philz Kernel would I need??
Phone: Galaxy Note 1 / N7000
Network: Vodafone UK
Current OS: Android 4.1.2 JB Stock
Planned OS to update Too: P.A.C. 22:30 (Android 4.2.2)
So not sure what Kernel I would need from the below link, and if so, can you explain why I need THIS one? What do I need to look for in a kernel?
http://forum.xda-developers.com/showthread.php?t=1901191
Also, can anyone confirm if they have a UK Note 1 on contract (esp Vodafone) as I am hearing the contract ones are unlocked by default. Its only PAYG that are locked down....
thanks, Lister

Hi Illidan Pornrage / Guys,
As per my above post, any idea what Kernel I need based on the above details...??
Thanks, Lister