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

[Q] pls techies help me out I9000 internal sdcard issue

Hi,techies customer brought the fone in restart condition on galaxy s screen with wrong flash.i flashed almost all the firmwares available from samfirmware using odin,with pit and without .pit it gives me the error :
E:cant mount /dev/block/mmcblk01p (no such file or directory)
E:copy_dbdata_media:can't mount SDCARD.
fone starts up normally when flashed with JPJPM but the internal sd caard shows unavailable and cant run any apps and camera.after adb and got the output of
busybox df -h as below.Pls techies sort out this issue as i am not that much familiar with CMD's

I would like to help you, but this is very serious and technically complicated way to solve your problem.
So, first, go to the Google.com, and you have to read all FAQ and help located There
then, if you'll gain enough techie skills, you should buy a small plasma burner, and steel plate, 1.5-2mm thick, 15x20cm.
When you will have this equipment, you can use Google first, asking your question, it should direct you to This thread on XDA here.
And now most complicated thing:
while applying the patch given in this thread, use your plasma burner to cut the sentence: "I will ALWAYS use Google to help myself FIRST"

spamtrash said:
I would like to help you, but this is very serious and technically complicated way to solve your problem.
So, first, go to the Google.com, and you have to read all FAQ and help located There
then, if you'll gain enough techie skills, you should buy a small plasma burner, and steel plate, 1.5-2mm thick, 15x20cm.
When you will have this equipment, you can use Google first, asking your question, it should direct you to This thread on XDA here.
And now most complicated thing:
while applying the patch given in this thread, use your plasma burner to cut the sentence: "I will ALWAYS use Google to help myself FIRST"
Click to expand...
Click to collapse
thanks for response,I have applied the patch file very first attempt, googled every post,
resurrected in riff,flashed with nearly dozen firmwares with and without pit at last used EZodin to flash EZboot_gingerbread and froyo as instructed in guides.
I have searched the google already but with no results

Strange, as it would definitely clarify this specific issue...
Have you tried to:
factory reset;
ginger flash with repartition
apply this patch?

spamtrash said:
Strange, as it would definitely clarify this specific issue...
Have you tried to:
factory reset;
ginger flash with repartition
apply this patch?
Click to expand...
Click to collapse
Yes i have factory reset numerous times for every flash before and after,flashed with JHJV6 gingerbread,but i can't remember i have applied patch after this GB flash,ok any how i will give a try now and let u know.any how thanks for suggestions.

Hmm.. make sure that ROM contains bootloader too...

Yes offcourse it has the boot.bin file .And for correction it is JPJV6 and not JHJV6 as i mentioned in my previos post.some where in the forum i have found the guide for this and i'll try after i go to office and let u know.
******************
Found this guide:
Basically like everyone else my SGS (I9000M from Bell) died due to an internal SD error, but in my case I haven't updated the phone since I got it in September 2010 (it had the JG9 firmware). The good thing is I was able to flash it to the stock Froyo 2.2, and I'm currently using it as normal and can access the internal SD without problems.
Summary of steps that most likely fixed the problem:
1. Go into recovery mode and "wipe data/factory reset". If your phone boots (but still have problems accessing the SD card) then it's a good indication that you maybe able to fix it.
2. Flash JL2 (from samfirmware.com) using ODIN. Not sure if this is needed, but you may need to ask ODIN to Re-partition. You still get an error "Can't mount DBDATA", and the phone won't boot. That's ok.
3. Flash the SpeedMod Kernel using ODIN (I used SpeedMod K12J with HZ=256). Your phone should boot into JL2 and the SD card should be accessible again.
At this point your internal SD card is fixed and you should be able to flash whatever you want. Just note that Kies will sometimes not work properly with the SpeedMod installed. In my case I flashed 2.1 (JH2) again (this won't work if you have 2.2 without speedmod kernel), then used Kies to update to 2.2 (JL2).
***********************
so will be back after a try as mine is I9000 international

[Q] ow to tell if my GN has eMMC damage?

Hi all,
When I posted a query in the general forum, I was informed about the possibility of the eMMC damaged on my GN. It happened after I hard reset it after upgrading it to the stock ICS (N7000XXLPT/ N7000XXLQ2).
My question is, before I try to fix it by the offered suggestions, how do I know for sure that the eMMC in fact is damaged? The only issue I've with my GN is that my data connection with straight talk is all over and hade to change the APN settings a few times.
Thank you all for your help!

You wont know unless its affected.
But dont go about wiping etc just to find out, though thats the only way to really know.
You can also download Chainfires brick bug app to see if you have a dangerous emmc chip. You can find it in apps/themes section.

me again...
You may or may not have caused damage... it does have a random characteristic. Like I said just don't wipe, factory reset or try to flash or restore anything while on that stock kernel.
Aside from some complicated ADB command lines that try to write to all sectors, you don't know if you are damaged. You are probably ok, in that your phone is mostly working for now! The damage usually show up when trying to use PC odin to flash a full ROM.... it gets stuck at writing the factory image.
Just take your time, study up, wait for more expert help, and don't make a stupid mistake.
My advice if you want to stay on ICS
1. Root it (follow guides for rooting stock ICS)
2. Then flash speedmod or france kernel from CWM or Mobile Odin
Probably safer to flash safe kernel only from PC Odin. Thats what I did. And I think triangle away works now also.
If you scared and want to get back on GB Rom, do what I did and PC odin a CF GB kernel only.
Wait for others advice:....
Sent from my GT-N7000 using xda premium

Thank you, both! I did download an app called "got a brickbug?" which gladly told me that my eMMC chip indeed was at risk of being infected
When I look under the storage, this is what I see:
Device memory
Total space" 1.97 GB
Applications: 360 MB
Available: 1.56 GB
USB storage
Total space: 11.07 GB
App: 50 MB
Available: 11 GB
Do these numbers look right, or am I being paranoid?

Those numbers look perfectly fine.

Ty, Belfia!

suhas2000 said:
Thank you, both! I did download an app called "got a brickbug?" which gladly told me that my eMMC chip indeed was at risk of being infected
When I look under the storage, this is what I see:
Device memory
Total space" 1.97 GB
Applications: 360 MB
Available: 1.56 GB
USB storage
Total space: 11.07 GB
App: 50 MB
Available: 11 GB
Do these numbers look right, or am I being paranoid?
Click to expand...
Click to collapse
where can i find the app you mentioned ?

Look in the apps/themes section. The thread is called "got brick bug"

[Q] Safely delete large files when running stock ICS

I appreciate that threads about the eMMc bug are getting old, but I believe my question is novel (currently the search function isn’t appearing, but I haven’t found a firm answer to my question from my months of reading XDA).
I am currently running ZSLPF Stock ICS 4.0.3 with CF-Root v5.6 Kernel. I have five large files taking up approximately 5gb of my internal storage that I want to delete. I have read that deleting large files when running an affected kernel may cause damage (suspected but not confirmed).
My goal is to safely delete these files and end up on the exact same build I have now (files/data/apps intact, LPF, CF Root Kernel).
I want to avoid flashing GB as I will lose all my files and settings, etc., and I do not believe a NANDroid backup would be any help as it would backup the very files I’m trying to delete [correct me if I’m wrong].
My current belief is that the easiest way to do this would be to flash Entropy’s DAFUQ Kernel, turn on the phone, delete the files, and then flash CF-Root back on.
Is this safe/correct?
Would it be best for me to perform this operation using PC Odin or Mobile Odin? I have successfully run TriangleAway on my current build so I’m not overly concerned about increasing the binary counter.
Thanks in advance for any consideration. I would have posted in Entropy512’s DAFUQ thread (http://forum.xda-developers.com/showthread.php?t=1617981), but I’m prevented from doing so as I am a new member.

[Q] N7000 emmc bricked can now only run GB

Hi,
I was quite happily running ICS4.0.4 (rooted) when I decided to try a different ROM (and/or JB - can't even remember any more).
After I did a wipe (I know, I know!!!) it got stuck on the boot logo screen.
I had the phone fixed by a 3rd-party repair shop, who installed ICS4.0.3 on it and, while at the shop, I used the phone a bit to make sure it was ok.
It kept crashing intermittently, so they had another go at it and now they tell me they could only install GB on it.
So, keeping in mind that the phone had the emmc bug and I tripped over it:
Is there anyway I can install ICS again on it?
I could use some of the tools floating around to detect damaged partition blocks and work around them.
What procedure should I use to go from a stock GB (non-root) to ICS?
Specifically,
- is there a safe way to root GB (given the emmc damage already), so that I can flash the other ROM/kernels (below)
- what kernel should I use
- what ROM should I use
I would greatly appreciate any help on this. I have been eating humble pie for a week now, so I hope there is no more 'why didn't you pay attention' coming my way
Cheers

You could use hydracore kernel which works with all GB and ICS ROMs and JB none Tw ROMs I be leave you can flash with PC odin to gain root and is a safe kernel
Sent from my GT-N7000 using XDA Premium HD app

ttibbetts83 said:
You could use hydracore kernel which works with all GB and ICS ROMs and JB none Tw ROMs I be leave you can flash with PC odin to gain root and is a safe kernel
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks ttibbetts83, I will try that and see how i go

Thanks Arobase40.
I'll get a strong coffee and read your reply from top to bottom and then plan my next move.
The repair was done by people unrelated to Samsung.
I currently have GB v2.3.5, (SGN_XX_OXA_KJ1_FACTORYFS) which works well, it would seem.
I'd love to get ICS back on it but need to gather info (such as that from yourself) before I do anything.
A bit more info on the state of the emmc storage: Using 'adb shell' and executing the command DD did in fact find bad blocks in partitions 9-11 (can't recall right now exactly which ones), so there are issues there.
The partition that is in place now, __appears__ to have successfully skipped those bad blocks.
And on something slightly tangential to the current topic, I know that doing a 'WIPE DATA' from the recovery menu zaps emmc, but does that also happen when you do a factory reset from within Android? From memory, when doing so, it seems to go into recovery mode and do it, so I'd expect that it'd also damage emmc.
Cheers

arobase said:
As opposed to all alarmist and contradictory posts about eMMC bug on stock Samsung ROM : GB or ICS, I never got any issues with this so called eMMC bug and never got bricked G-Note as long as I kept at using the stock kernel, nevertheless I made various and numerous wipe whichever the ways (from recovery or the settings)...
For rooting, I always used the temporary Touch CWM to flash (which has been may be removed from XDA, I guess as it was supposed to cause bricked devices) anything : superuser, busybox, and other custom ROM... ^^
BUT when I flash a custom ROM, I always removed the custom kernel (so called "safe"), and replace it for a stock kernel and never got issues with it.
The first and last time I flashed a custom with custom kernel I got my G-Note bricked (just forgot the replace the custom kernel for a stock one... ^^) !!!
So, if you want to flash an ICS version, get one from Sammobile, and flash it with PC Odin !
You shouldn't have any problem with them !!!
Get all root and busybox files from dr Ketan, and if you can find it again use the temporary Touch CWM which has NO kernel inside : it WORKS quite fine !!!
Click to expand...
Click to collapse
Unfortunately there are no high trees on XDA beause you should look for one before typing this utter personal nonsense that could brick anybody's Gnote.
Taking your own convictions for thruth is one thing, sending innocent ppl into the jungle is another...
What you are saying is: If there is a lightning storm, just go into an open field en enjoy. I cannot say it is 100% safe, but I never got struck....I think they removed the tree i used to seek shelter from the rain, but if you search real hard you might find it anyway.
---------- Post added at 10:33 AM ---------- Previous post was at 10:17 AM ----------
amanmasgaman said:
Hi,
I was quite happily running ICS4.0.4 (rooted) when I decided to try a different ROM (and/or JB - can't even remember any more).
After I did a wipe (I know, I know!!!) it got stuck on the boot logo screen.
I had the phone fixed by a 3rd-party repair shop, who installed ICS4.0.3 on it and, while at the shop, I used the phone a bit to make sure it was ok.
It kept crashing intermittently, so they had another go at it and now they tell me they could only install GB on it.
So, keeping in mind that the phone had the emmc bug and I tripped over it:
Is there anyway I can install ICS again on it?
I could use some of the tools floating around to detect damaged partition blocks and work around them.
What procedure should I use to go from a stock GB (non-root) to ICS?
Specifically,
- is there a safe way to root GB (given the emmc damage already), so that I can flash the other ROM/kernels (below)
- what kernel should I use
- what ROM should I use
I would greatly appreciate any help on this. I have been eating humble pie for a week now, so I hope there is no more 'why didn't you pay attention' coming my way
Cheers
Click to expand...
Click to collapse
Actually you should be happy that they revived your Note after brick even if it's only running GB for now.
However if you are a brave person you can do the same trick on ICS.
Just read and understand the thread that is a guide on doing so.
You can root your GB without a problem, but there is no obligation for it to install ICS with odin.
However what you do need is the following (besides a lot of patience and courage) :
1. get the ICS files you want to flash including the pit file.
2. get a program called PIT MAGIC to recreate a suitable pit file
3. determine where your bad blocks are located
4. Load the pit file into the magic program and alter the stock pit file
with the values needed to ommit your bad emmc area
5. save it and then flash your note in odin with your newly created pit file and repartition ticked.

@OP: could you please check your internal storage capacity? Is it aroung 8GB?

Arobase we are not going to rediscuss this matter for another 556643 pages.
Just ask yourself : if there was no problem then why did samsung patch their JB kernels for it. http://forum.xda-developers.com/showpost.php?p=34933643&postcount=683
Also nobody asks you to reconsider your own experience and beliefs, but the day someone follows your instructions and bricks his phone, are you going to pay for a new motherboard ?
I'll stop this discussion here, and just hope nobody will get struck under the tree.