Related
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
Hi,
I'm having a problem with a specific app.
I upgraded from Darky's Rom 8.0 to 9.1 (wipe). Didn't detected any problems whatsoever.
After applying lagfix Asphalt 5 app disappears after each restart.
Already disabled lagfix but the error still remains.
Can anyone help me on this issue?
Thanks,
I know that error Asphalt has been posted recently with the same rom .
So a search may find the answer .
jje
JJEgan said:
I know that error Asphalt has been posted recently with the same rom .
So a search may find the answer .
jje
Click to expand...
Click to collapse
Hi,
Thanks for replying,
Already see that post, but no one explains why this error happens or how to fix it.
They only say to download Apps2sd and transferring all the Apps to the external SD, and that I don't want to do. I only want to fix this particular issue.
Thanks,
why is this not posted inside the 'darky's rom' thread? (just curious)
I had the same problem with some of the custom roms like the cyanogen 6.1 beta's.
Some roms install apps on ext SD by default and after a reboot the app is missing in the drawer.
Check in app management, it should be still there and if you chose "move to phone" its back.
Hope this helps you out, it worked for me.
tmzbeme said:
why is this not posted inside the 'darky's rom' thread? (just curious)
Click to expand...
Click to collapse
It's also there.
But first of all I don't know if this is an issue caused by the new darky's rom or some other known android sd card issue.
And second I don't see any problem in posting this issue in the xda forum where also darky have his rom posted.
why is this not posted inside the 'darky's rom' thread? (just curious)
I would guess cos it wont get an answer .
jje
JJEgan said:
why is this not posted inside the 'darky's rom' thread? (just curious)
I would guess cos it wont get an answer .
jje
Click to expand...
Click to collapse
Exactly...
Thanks,
had the same problem with dark's 9.1 but with root explorer and other system apps. I don't have an external SD Card. Now the rom gone crazy and I had to reflash the V8. If this one goes crazy too, i will probably got o stock or on DOc's rom
I had the same problem with DocRom, it was caused by the deodex process that runs when phone is restarted.
It was caused by not having enough space in one partition (I think it was /system). So deodex failed. This only caused problems when deodexing big apps, like asphalt. You cans see the error by doing a logcat while phone is rebooting.
I couldn't find a solution. You might want to post in darky's thread. Maybe there is a way to disable deodex for some apps.
If you find a solution please post it here, I'd like to know how to fix this.
Thanks guys,
I thing that this error it's associated with another, I explain.
I was starting to wipe dalvik cache to see if it solve this issue but is says:
E:Can't mount /dev/block/mmcblk1p2 (file exists).
I had this error once and the Asphast 5 App also disappeared after each restart.
Then I flashed with Odin and re-partition a new rom and the error was gone.
Also, the App error was also solved.
Now I have the same two errors, so they are related.
I need to find more information about this issue.
If anyone knows more please share.
Thanks,
I receive that dalvik cache error every time when i'm wipeing the dalvik, but never lost apps before.
I only lose one, "Asphast 5".
I re-flashed the phone with Odin and JPU stock rom, re-partition.
Formatted my internal and external card, then clean installed a wipe 9.1 Darky version and the Asphalt 5 app remained on the phone.
After I started to install all the apps again with Titanium Backup the Asphalt 5 app disappeared after restart.
I really don't know what's going wrong. I know that with my old Darky 8.0 this didn't happened...
Anyone has ideas?
latest doc rom + hardcore kernel, same problem only 1 app keep missing after restart. (asphalt5 from samsung apps)
I think must be something with the big size apk, can't find other bigger apps then asphalt5.
You may check if this solution in the ROM Kitchen Thread works here as well.
Hi xda!
I'm experiencing a problem since I'm using modded-AOSP ROMs.
In practice, I bought this device used from another one person that has never updated it (when I get it it was slooow).
So I connected to Kies and i got all the official updates needed.
I discovered this world and I started to search and install modded roms starting by kernels for obtain root access.
Since I flashed 2.3.3 kernel mod (DarkCore if I'm not wrong) I occasionally got black screens of death.
I search for related topics on xda but I only found problems related to startup.
I got those kind of freezes during normal using (especially when the device is connected to AC for battery charge).
Now I'm on Android 4.0.3 port by Onecosmic (thanking this guy will never be enough) more than a week ago and this morning I woke up and the phone was stuck on this black screen.
No way to get a screen without pressing power button for seconds and get a reboot.
There's a way to fix this problem?
I thought there was a problem of Android 2.3 builds but now this issue is showing on version 4.
Another one got this problem?
Thanks @ all
Excuse me if a topic-related thread is already opened, I search before posting this
i've done a full terminal reset including internal SD and deleting all previous backup (to avoid the possibility to restore a corrupted backup) and now the problem seems solved.
sna696 said:
i've done a full terminal reset including internal SD and deleting all previous backup (to avoid the possibility to restore a corrupted backup) and now the problem seems solved.
Click to expand...
Click to collapse
how do you do this? if you dont mind me asking
You need to have root permissions.
You enter recovery and mount sd card.
Then you wipe all caches and sd.
One you have done that you need to flash a stock rom then install ICS.
Doing this you are sure you haven't garbage or something else on your phone.
Hello,
I tried searching for my problem in the forums but I didn't find my exact setup and don't want to brick my phone. (Well maybe it already is)
I had Cyanogenmod 7 for quite a while and tried the Nightlies for 9 some months ago. In the early days of my phone I used ODIN to flash the newest Stock firmwares and then used the chroot kernel to root my phone and install cwm. Since then I installed Cyanogenmod 7 and later Cyanogenmod 9 Nightlies with cwm recover and there was never a problem.
Today I tried the ROM from DerTeufel1980 http://forum.xda-developers.com/showthread.php?p=28819140
I flashed the rom, the addons, the superuser and google now fix. Then I flashed the kernel Devil3_1.0.0-Rc5_datadata_i9000_CFS_BLN_CMC_20120719.zip and fixed permissions. After that my phone wouldn't boot. The boot animation was the old standard android logo.
I managed to get into Devil Kernel Recovery and thought to try a reflash of just the ROM but when I try to "choose a zip" it always tells me
E:can't mount /sdcard/
After that I flashed the kernel with odin and now the phone seems to boot but veeeery slow and it has a ton of flickering the whole time. The bootanimation is the cyanogenmod 9 boot animation. I got into Devil Recovery and I still can't mount the sdcard. And it seems that it doesn't detect my sim card.
I hope you can help me.
Edit: Actually after rebooting several times the boot sped up and I could get into the ROM. I still can't mount the internal sdcard though and I have no phone functionality. It seems that my IMEI number is gone.
Hey
Downgrade your sgs to 2.3.6 valuepack using odin3...
Then root it and use it for a day atleast..
Then flash CM9 nightly..use that for a day too..
Then flash JB...not the same one u did earlier..
Instead Goto teamjellybean.noez.in (ad www.)
Find d latest version of jb and follow the instruction there..
Cheers
Sent from my GT-I9000 using xda app-developers app
Thanks that's exactly what I have done and it worked.
I've seen a lot of folks saying that they might have bricked their phones when some issue occured while flashing a new rom.
Personally whenever I face issues, I just goto the Download mode and Flash a GB rom and then move my way up (GB --> ICS --> JB).
As long as you can go into Download mode, shouldnt be a problem
Fwiw, I lost my IMEI for the first time trying out the JBs. Not sure if it was Slim or DerTeufel's. I ended up with the kind that allows you to connect to your mobile provider, a fake but working IMEI. But when I saw that I tried to go to GB and it didn't come back automagically. And the IMEI was totally wiped so I couldn't even register on the network. Ended up getting to ICS and only then did Root Browser let me write to the efs folder.
Lesson, in short: make a backup zip of your efs folder (to preserve permissions) and double back it up using Nitrality from the Play store.
Glad you got yours back, too.
sent from a telephonic device
tchindalia said:
Hey
Downgrade your sgs to 2.3.6 valuepack using odin3...
Then root it and use it for a day atleast..
Then flash CM9 nightly..use that for a day too..
Then flash JB...not the same one u did earlier..
Click to expand...
Click to collapse
OK, so I'm *definitely* a crappy speed-reader, because I missed this part about waiting on each version. What does the waiting do? I'm now wondering if that means I need to use the phone and, with the restored /efs folder, sometimes later /dev/block/stl3 will repopulate itself with the proper info.
Hey
I asked to wait on roms coz it can just make a few things working...like data..if it doesnt work on 1 rom it would not (probably) work on the next update..(personal experience)..
Cheers
If my post helped, don't mind hitting the Thanks button..
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.