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

[MOD][CWM][Bell][Gobstopper] Stock 2.2.2 for Bell Updated 10/01/2011

Disclaimer: You may brick your phone. NOT for AT&T
​
Reminder: Make sure your phone has enough battery charge to flash this, it's larger than normal.​Hi,
Here is a huge CWM zip that restores your Bell phone to stock 2.2.2. I have tested it on my phone several times and it worked perfectly, there is still the chance that something may go wrong, but I am feeling confident in it.
What this does is similar to my app or scripts, it puts my backup of Bell's 2.2.2 partitions on your phone, but instead of using dd, it uses tenfar's CWM and flash_image. Some partitions are HUGE, and take a while, your phone is not locked up.
This has been updated to include the Bell bootloader for 2.2.2 and the radio for 2.2.2.
EDIT: This has been updated again to ram fix the boot and recovery partitions if there is a ram problem.
It writes to partitions 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17. 3 is left out because it's your pds partition, and data and cache have no relevant content. You must factory reset after using this to clear those. So, that's your boot, recovery, system, webtop, cdrom, preinstall, and several other partitions. This is to get back to stock Bell 2.2.2, it's not just a boot/system replacement, if that is a fruitcake, this is a gobstopper.
Please note: This restores your Bell phone to stock condition, that means you won't be unlocked, CWM will be overwritten with the stock recovery. It will be just like you bought it. If you want to keep flashing things in CWM with the unlocked bootloader, then immediately after flashing the stock zip, flash the unlock and fix zip. If you don't then you will have to reflash an unlocked bootloader, and reflash CWM recovery, which is time consuming any annoying, it doesn't mean you will be permanently locked again. I had to spell that out to the folks that don't really understand this stuff. At all.
If you want root after installing this, just install Superuser.apk from the market.
Bell_FR_2.2.2.zip (Froyo not France)
(md5 e431b4cc3ba7e3a27b6aad6982a31066)
Cheers!​Oh, I forgot to mention, this is not quite stock, there are su and sudo binaries in /system/bin. Just install Superuser.apk to be rooted. they haven't been a problem for doing an OTA yet, but they are easy enough to remove if it comes up.
unlocked-fixed-Bell-2.2.2.zip
Mirror: unlocked-fixed-Bell-2.2.2.zip​

Damn, nice work as always, man! This should come in handy for lots of us Bell Atrix users that feel left out. Lots will appreciate this!

When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?

Will you eventually be able to compile a zip for Bell gingerbread?

IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
the problem would be hosting it, not sure how he would be able to do that.
akurit said:
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Click to expand...
Click to collapse
keeping in mind that this is only for the recovery with unlocked devices, what he means is that the CWM recovery that tenfar put out has a problem with int'l phones (pretty sure it's all int'l) where IN recovery (not just the normal ROM, like the problem we had before) only 300 and some mb of RAM is available. since this zip is over 300mb, it can't all load into your RAM properly with normal recovery.
NFH found this bug, and patched recovery for us so as to fix the RAM problem. the two files attached are fixed recoveries for the two separate MBR versions of int'l devices.
to find what version you should use, connect to phone via ADB and then
Code:
adb shell
su
cat /proc/cmdline
and then search for the part of the output where it says "tegrapart=mbr:" and read that. it should have either "1100" or "d00" somewhere in it, use the CWM zip attached that has your respective output.
hope that clears up your question, if you have any further ask them in here.

IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
Hi,
I believe y2whisper may be working on something like that. The point of getting back to stock 2.2.2 is to be able to apply the final OTA for Bell GB. Certainly something similar can be done for any firmware you want to flash.
Cheers!

i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery

akurit said:
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
Click to expand...
Click to collapse
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)

NFHimself said:
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
Click to expand...
Click to collapse
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.

raybond25 said:
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
Click to expand...
Click to collapse
Hi,
Sure, it's just replacing the word recovery with boot and having the right boot images in the file.
Cheers!

yes its zipping now. off to bed but tomorrow I will back up my stuff and attempt to flash to see if it works.
@akurit
I forget off the top of my head but there is a file that you just have to delete to prevent that. the file just flashes the old recovery on every reboot. get rid of that and you will be fine.

Awesome work! This makes it much easier to get back to 2.2.2

Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.

This is why hehee
tenfar said:
......
Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.........
Click to expand...
Click to collapse
now it remains unlocked and I have recovery even if i reboot... but the ram issue still exists

y2whisper said:
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
Click to expand...
Click to collapse
i could test it for you, i should be able to tell if it works alright or not, since i'm starting from an AT&T build of 2.3.4. would i have to head back to stock Bell using Gobstopper before i use your package too? i got a whole buncha time on my hands this week, so i should be able to test it however you want.

anyone try flashing the bootloader and radio?

kevnb said:
anyone try flashing the bootloader and radio?
Click to expand...
Click to collapse
Hi,
I have tested it, no problems, but went back to IHOP and the ram-fixed bootloader for 2.2.2 in the OP so recovery will work.
Also, the file install_recovery.sh located in your /system/etc/ doesn't exist in the Gobstopper, so that isn't causing recovery to be generated by patching boot.
Cheers!

So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome

y2whisper said:
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
Click to expand...
Click to collapse
Hi,
What recovery are you using, if it's not ram fixed you are going to run into situations where you don't have enough space to flash it.
Cheers!

ahhhh.
you know i was wondering if that was it. I even repackaged the recovery thinking it would be the cause.
I don't believe I was ram fixed at the time of the backup. So I am thinking either, have custom recovery flashed in that spot, or change the order to where recovery gets flashed after.

Bricked Tab???? HELP

HELP! I am so scared...somebody help me!
I tried to installed the Overcome kernel but didn't like it, as each time I boot up, that voice comes up.
And plus, a few of my original apps was lost (including Market). So I thought i'd install with Odin again the:
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
And now, when i switch on the tablet, it'll boot with the animation and sound, but then a blank screen.
I can manage to boot into ClockworkMod recovery. Can i be saved? Please somebody help me!
Thanks

geoyakult said:
HELP! I am so scared...somebody help me!
I tried to installed the Overcome kernel but didn't like it, as each time I boot up, that voice comes up.
And plus, a few of my original apps was lost (including Market). So I thought i'd install with Odin again the:
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
And now, when i switch on the tablet, it'll boot with the animation and sound, but then a blank screen.
I can manage to boot into ClockworkMod recovery. Can i be saved? Please somebody help me!
Thanks
Click to expand...
Click to collapse
If you can boot into CWM, then you should easily be able to get into Download mode as well. You can go back to the stock image for your Tab, or try and reflash a different rom via CWM... sounds like just a bad flash for a soft brick..

pvtjoker42 said:
If you can boot into CWM, then you should easily be able to get into Download mode as well. You can go back to the stock image for your Tab, or try and reflash a different rom via CWM... sounds like just a bad flash for a soft brick..
Click to expand...
Click to collapse
Hi there, thanks for reply back to me.
I've managed to actually get it going again, by reflashing to the Overcome kernel.
However, some apps has disappeared and also the market.
Anyways, i wish to revert the whole thing back to stock, kernel and firmware. Is there a way I can do this via Kies?
Let me know what information regarding my tab you need. I believe it is the CPW (GSM) UK version.
cheers

geoyakult said:
HELP! I am so scared...somebody help me!
I tried to installed the Overcome kernel but didn't like it, as each time I boot up, that voice comes up.
And plus, a few of my original apps was lost (including Market). So I thought i'd install with Odin again the:
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
And now, when i switch on the tablet, it'll boot with the animation and sound, but then a blank screen.
I can manage to boot into ClockworkMod recovery. Can i be saved? Please somebody help me!
Thanks
Click to expand...
Click to collapse
LOL. FYI, your Tab is not haunted. That voice that you refer to, is basically an indicator that the file-system on the Tab is being converted from RFS to EXT4 (what some would affectionately refer to as the lag-fix). You should have left it to continue. That's the reason we ask people to let it finish booting before doing anything else. As always, when it comes to flashing a new firmware/kernel, it's always better to read up and know what to expect.
Anyway, by the looks of it, you might have a corrupted file-system, since you keep shutting it down mid-conversion. That's the reason "the voice" keeps coming back. If you'd allowed it to complete, it should not have returned.
Secondly, flashing the Overcome Kernel alone will NOT remove the Market application. If you were already on the CF-Root kernel, it might remove the CF-Root specific applications like the CwM "app" (and not the recovery functionality, mind you...) and the Tweaks app as these apps were created by ChainFire specifically for his kernel.
Best advice would be to re-flash a stock firmware first, to get your Tab into a clean system. From there, you can continue to to install the kernel of your choice (like ChainFire or Kouxudaxi's fine kernels as well.... these kernels, if I'm not mistaken, do not do automatic EXT4 conversions)
If you're unsure of how to do this, refer to the guide in teamovercome.net and it'll guide you in basic re-stocking (but using our Stock safe package which will provide you with the Gingerbread-based JQ1 firmware).

LOL, +100000000000000000000000 thepitbull...

thepittbull said:
LOL. FYI, your Tab is not haunted. That voice that you refer to, is basically an indicator that the file-system on the Tab is being converted from RFS to EXT4 (what some would affectionately refer to as the lag-fix). You should have left it to continue. That's the reason we ask people to let it finish booting before doing anything else. As always, when it comes to flashing a new firmware/kernel, it's always better to read up and know what to expect.
Anyway, by the looks of it, you might have a corrupted file-system, since you keep shutting it down mid-conversion. That's the reason "the voice" keeps coming back. If you'd allowed it to complete, it should not have returned.
Secondly, flashing the Overcome Kernel alone will NOT remove the Market application. If you were already on the CF-Root kernel, it might remove the CF-Root specific applications like the CwM "app" (and not the recovery functionality, mind you...) and the Tweaks app as these apps were created by ChainFire specifically for his kernel.
Best advice would be to re-flash a stock firmware first, to get your Tab into a clean system. From there, you can continue to to install the kernel of your choice (like ChainFire or Kouxudaxi's fine kernels as well.... these kernels, if I'm not mistaken, do not do automatic EXT4 conversions)
If you're unsure of how to do this, refer to the guide in teamovercome.net and it'll guide you in basic re-stocking (but using our Stock safe package which will provide you with the Gingerbread-based JQ1 firmware).
Click to expand...
Click to collapse
Hi there,
Thank you so much for your time in replying - I've managed to install what i believe is stock Gingerbread from Samsfirmware. So everything looks back to normal... tho i have posted another Question, with all my firmware details so I can be reassured I am back to stock.
So sorry, I panicked so badly last night..ha!

You have also special thread with many scenarios how to fix your tablet if anything goes wrong.
It helped me yesterday to revive my Galaxy Tab. Just suddenly it started freezing and restarting, after 3 weeks working perfectly on Overcome. Nothing changed, or updated, nothing installed for days, and all what was ever installed are programs I already have on my two other Android phones, it simply froze in the middle of work. Wipe didn't work, changing file system didn't work, etc...
Read the thread: http://forum.xda-developers.com/showthread.php?t=1133590
Very good material.

nidza said:
You have also special thread with many scenarios how to fix your tablet if anything goes wrong.
It helped me yesterday to revive my Galaxy Tab. Just suddenly it started freezing and restarting, after 3 weeks working perfectly on Overcome. Nothing changed, or updated, nothing installed for days, and all what was ever installed are programs I already have on my two other Android phones, it simply froze in the middle of work. Wipe didn't work, changing file system didn't work, etc...
Read the thread: http://forum.xda-developers.com/showthread.php?t=1133590
Very good material.
Click to expand...
Click to collapse
Im very glad that the guide helps many ppl
@the Op : do me a fav and flash safe
Sent from my GT-P1000 using Tapatalk

k0sh said:
Im very glad that the guide helps many ppl
@the Op : do me a fav and flash safe
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Yup, in future i will be more careful when flashing, so glad that my tablet is back to normal (albeit with the Italian release of GB ) but everything works fine.
Will do more reading on the forums before undertaking any more flashing, make sure i know what i am doing and which Rom is best for me to use.
Cheers
Sent from my GT-P1000 using XDA App

geoyakult said:
Yup, in future i will be more careful when flashing, so glad that my tablet is back to normal (albeit with the Italian release of GB ) but everything works fine.
Will do more reading on the forums before undertaking any more flashing, make sure i know what i am doing and which Rom is best for me to use.
Cheers
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
best reaction i never read

Gingerbread 2.3.3 Q&A

I think we need to sticky/pin this for us who just flash the stock/leaked GB 2.3.3 along with the optional root from this thread since we can't post there http://forum.xda-developers.com/showthread.php?t=1127249
Since this is the route that I went I would be able to help answer questions for others. I see cognition, mosaic.... but how about us who like to keep it stock?

Brickster
Just want to say that I have learned so much on here and I have a lot of fun trying out different ROMs. Thanks to all the DEVs, when I get a job I'll buy you guys some beers lol.
So... This has soft bricked my phone every single time. The first 4 attempts were from stock eclair. My last attempt I was successfully running Stock I9000 2.3.3 NEE so I thought I would try it from there. Odin gets to boot.bin and then says FAIL! I got into download mode using VOL DWN and PWR which is the key combination from Stock I9000 2.3.3 NEE. I have been running I897UCJF6-final-OCD-REV0 to flash back to stock after brickness.
So i'm sure i'm missing something pretty simple, but any help is appreciated.

Woah dude, that was very very very close to being a hard brick. Boot.bin is the primitive bootloader. so you had a kf1 pbl, and since you had the combos for I9k boots you obviously had an I9000 sbl, (secondary bootloader that's where the combos are contained.)
Make sure the usb chord is on a port attached to the motherboard (in the back of the pc), if it is already switch to another. Reboot the computer and try again.
But with such a close call like that, and the fact that you said it fails every time I would avoid it altogether I mean its a stock rom, is it worth bricking over??

Well, I really wanted to try the Cognition 5 v2 ROM. Instructions say to be on Samsung Gingerbread. So that's why I tried so many times and I am really more curious to find out why it's not working than I am worried about it bricking.
I was on a port directly on the motherboard Odin displayed as com10.
I was thinking that maybe it is my computer since most have success with this 1-click. I forget sometimes I'm running a 64-bit version of Windows 7 maybe that's the culprit. Is there anything I can check on my computer to keep this from happening again?

ttr187 said:
Well, I really wanted to try the Cognition 5 v2 ROM. Instructions say to be on Samsung Gingerbread. So that's why I tried so many times and I am really more curious to find out why it's not working than I am worried about it bricking.
I was on a port directly on the motherboard Odin displayed as com10.
I was thinking that maybe it is my computer since most have success with this 1-click. I forget sometimes I'm running a 64-bit version of Windows 7 maybe that's the culprit. Is there anything I can check on my computer to keep this from happening again?
Click to expand...
Click to collapse
Use admin mode for Odin and change the compatiblity to Xp service pack 2. This is the best way to run Odin for Windows 7 x 64. Since I use Cog 5 v2, I strongly recommend following the instructions 100%. Please remember when you need to loading stock UCKF1 and when you load UCKF1, you are loading bootloaders, so any disconnection can brick you hard. Thank goodness for the simplified instructions there.

GB stock? I thougth captivate stock were eclair or froyo.

KF1 is the leaked gingerbread firmware for the captivate...

popfan said:
Use admin mode for Odin and change the compatiblity to Xp service pack 2.
Click to expand...
Click to collapse
After changing the compatibility mode to XP pack 2 everything worked like a charm. Then I was able to successfully flash Cognition 5 v2. Sweet!
Thanks.

Hello. I use Darky's rom 10.2. And I have problem with Dialer. It sometimes crushes and exits. Problem will be solved with reboot. how can I fix it? thanks.

I would try to flash again and make sure you do a data/cache wipe. I've had random issues with other ROMs when I did not wipe, and all was fixed once I flashed properly.

I know I'm not wiping everything while flashing, but I flash it as told as in FAQ. But my memory will stay unwiped after I run newly installed ROM.

When you say "memory" what exactly do you mean?
If you mean the /sdcard storage partition, that is normal.

yes, /sdcard storage partition.
Before flashing, I get warning message about wiping all data in my internal storage... what does it mean then?

The /data and /cache partitions. And the dalvik cache.
The first 2 are in the cwm main menu. Wipe data/factory reset and wipe cache. Dalvik is in the advanced sub menu.

When i flash this, my phone asks me for a password. It won't let me do anything without the password and I have no idea what it is. I've tried samfirmware.com and that most certainly is not it.

Griff1220 said:
When i flash this, my phone asks me for a password. It won't let me do anything without the password and I have no idea what it is. I've tried samfirmware.com and that most certainly is not it.
Click to expand...
Click to collapse
It appears to be asking for some encryption password according to one of these guys that posted in the following thread. But there is a way to get past it by the method in this thread...http://forum.xda-developers.com/show...02&postcount=7
Remove ur external sd and copy over/back up anything u want to save from ur internal sd before u do this, just in case.

data/chache wipe i should do right after flashing right?

Tab reboots before BML/MTD can even get started. Then no recovery

Ok guys,
I am not new to Android but this is really really starting to give me the sh!ts. I have no f#*%ing idea how many times I have gone and restocked this POS tab.
I follow the guide to a T for Overcome etc etc. I know all that.
I can flash CM10 through recovery from there and it completes oddly enough. However it does not boot at all. I have done this maybe 10 times. No boot. Just constant re-install of the kernel and Cyangen Bootanimation. I also have no recovery as soon as that happens and then I have to start ALL OVER AGAIN!!!!
Ok so I decide to try CM 9.1.0 stable. Surely this will allow something. Guess what? It doesn't even install. YES I have removed the lines from the updater script. I mean how stupid. If you don't even have a system for a getprop to querey of course it is going to fail.
Remove the lines, gets to BML/MTP and starts to process for maybe about 10-15 seconds and then reboots and becomes a brick
What in gods name am I missing here that isn't in the million and 1 guides I have already read and the conflicting opinions of people say 'flash CM10 straight after Overccome kernel' and 'No no no you need to be onn CM9 first' and I have even read 'No you need to flash CM7 first then from there you can flash CM10'
Like WTF?
Cant there just be a 100% true guide. For starters Overcome ROM guide only gets you to there, nothing more. There is no steps in between. There are only guides that assume that you have done the steps to get to Overcome ROM.
I am about to scour the internet now and see if I can find CM7 cause I am sick to death of restocking and starting from scratch on this stupid POS. I mean FFS I thought that this would be straight forward like when I updated my i9000 Galaxy S to ICS, but noooooooo nothing I have done gets the results of what people claim in the guides.

These are my steps
Odin
PIT = gt-p1000_mr.pit
PDA = GB_Stock_Safe_v5.tar
Modem = modem.bin (JK3 as per the guide)
reboot download - it does boot otherwise
Odin
PDA = CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
reboots into Gingerbread
reboot download again
Odin
PDA = Overcome_Kernel_v4.0.0.tar
Sexy voice does her sh!t (I thought that this was where we did BML to MTD but it's not its rfs to ext4 - thought I'd add that for anyone that has in the past like me had experience with doing this stuff before and needs a refresher).
Reboot into recovery and from here is anybodys guess?
I need the EXACT EXPLICIT DETAILS FROM THIS POINT!
Everything I try from here completely messes the P1000 and I have to start again.
CM10 - Flashes but doesn't boot - recovery updates but flashing anything else obviously kills it and I start again
Overcome ROM wipe - Flashes but exists the script before completing
CM9.1.0 - Flashes, gets to BML/MTD and quits - note Recovery is completely screwed after this point
CM7 - Yes I am about to try this. Please tell me why this is wrong and explain and I will listen. Please also advise all the other people out there with guides that are wrong to update them and include the important details that they have overlooked for people like myself.
Thanks

Overcome kernel converts rfs to ext4 but still in BML.
When you flash cm9 or cm10, flash it 3 times.
That is by selecting the zip. Flash it, it reboots to recovery (a new recovery, no longer overcome).
Flash zip again. Now it converts to MTD. It then reboots to recovery. (Many people think it is bootlooping. )
At this point flash zip again. Now it does the longer install.
Screen says a lot of thing about /system and stuff.
Let it finish and reboot to cm.
The weakness of most guides is that they never say 3 times.
The noobs thinks it is a bootloop without reading what the recovery is doing.
Sent from my GT-N7100 using xda app-developers app

priyana said:
Overcome kernel converts rfs to ext4 but still in BML.
When you flash cm9 or cm10, flash it 3 times.
That is by selecting the zip. Flash it, it reboots to recovery (a new recovery, no longer overcome).
Flash zip again. Now it converts to MTD. It then reboots to recovery. (Many people think it is bootlooping. )
At this point flash zip again. Now it does the longer install.
Screen says a lot of thing about /system and stuff.
Let it finish and reboot to cm.
The weakness of most guides is that they never say 3 times.
The noobs thinks it is a bootloop without reading what the recovery is doing.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
You may have missed the point where Recovery becomes unreachable the minute I flash CM9 the first time. After that I can no longer get recovery and device becomes a brick.
Jarmezrocks said:
CM9.1.0 - Flashes, gets to BML/MTD and quits - note Recovery is completely screwed after this point
Click to expand...
Click to collapse
If you can provide a link to a known 100% certain to work version of CM9 or any CM I would be greatly appreciated! I believe there is much confusion (and to be honest I got lost with so many different opinions about changes made to CM in their thread) as to what version is best to flash. I personally tried the latest CM of version 9.1.0 and the stable (to which there were two and I tried one but not the other?) and did not have any luck with either.
Look forward to hearing from you
Thanks for your reply mate :good:

Not sure why your cm9 gone bad.
Make sure you download the p1 variant and check the md5 sum of the file.
It has always been on with me.
Restock. Overcome kernel. Then flash cm 3 times.
Unless there is a hardware issue?
Sent from my GT-N7100 using xda app-developers app

priyana said:
Not sure why your cm9 gone bad.
Make sure you download the p1 variant and check the md5 sum of the file.
It has always been on with me.
Restock. Overcome kernel. Then flash cm 3 times.
Unless there is a hardware issue?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thats the thing though, I believe that CM 9 has changed several times since the beginning. Both the latest and stable didn't work. There is another stable version but really got put off the whole ordeal because I was reading so many posts of people confused as to which version they should be flashing and which one they made the stable version in the end.
Something else also thrown in was that some guys where flashing Overcome and not allowing conversion to ext4 and then upgrading to CM10?
Should flashing Overcome kernel over the top of standard Gingerbread allow the device to boot and run stock GB with ext4? How would this be different to running stock and using OCLF4 on stock kernel with CWM Recovery? Say CF root Recovery?
Sorry for all the questions but the device isn't mine and I am now looking for the simplest solution to making it run normal and stable. Seems like normal GB is so unstable its not funny! Is it normal to get random reboots on stock Gingerbread?

It is not normal for GB to reboot by itself. There must be something not right.
About overcome kernel on top of normal GB with ext4, yes that is possible to run it that way.
About allowing overcome kernel to convert to ext4, or not to allow that, it doesn't matter.
CM kernel will repartition the internal storage and everything will dissappear once a new partition scheme is in.
My suggestion is usually for people to not wait for overcome kernel to convert since it is not needed.
Sent from my GT-N7100 using xda app-developers app

Hey I got some good news!:good:
And....I will need you @priyana to update your OP for the Overcome ROM thread too, this will apply to all Australian P1000 Tabs I guess...well at least the Optus ones anyway.
Essentially the GB_Stock_Safe_v5.tar and gt-p1000_mr.pit are NOT safe like we are lead to believe....well not for the tablet I have just repaired. It is now running CM10 no problems!
I have created a new firmware package that incorporates a new PIT and various combos of files from the old GB_Stock_Safe_v5.tar and the standard firmware package.
What I found was flashing the completely stock firmware the device would not boot or function what so ever, which is really strange as most people would expect that standard firmware would at least be stable enough to use. Not even with the stock PIT or the gt-p1000_mr.pit.
You can down load the files here >>> GB_Stock_AUST_Jarmezrocks+P1.pit
This will have a firmware package and pit file combination that is suited to Australian P1000 TABS
Containing
GB_Stock_AUST_Jarmezrocks.tar
P1_add_hidden.pit
These are the ONLY files that will allow the Tab to boot, run and function normally. Before the thing was just so unstable you could barely do anything with it.
So from here Australian user who are having issues/problems with the Overcome ROM guide and getting continual reboots or bootloops should flash this package.
I will start a new thread in the dev section where it will be seen by others who are wanting to salvage their device.

That is good to hear.
BTW, the new overcome thread is sos_sifou's, not mine ?
Regarding the stock ROM, I remember that Stimpz0r, one of the great devs here, used to own a P1000 from optus and have no issue with overcome GB stock safe v5.
Makes me wonder if there are different variant of optus P1000.
Sent from my GT-P1000 using XDA Free mobile app

priyana said:
That is good to hear.
BTW, the new overcome thread is sos_sifou's, not mine ?
Regarding the stock ROM, I remember that Stimpz0r, one of the great devs here, used to own a P1000 from optus and have no issue with overcome GB stock safe v5.
Makes me wonder if there are different variant of optus P1000.
Sent from my GT-P1000 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry yeah you are right, you're just the heavy promoter of it (with good reason too eh?)
I will PM him and see if he can include it in the OP?
All I know is that without a doubt there was no way that package was saving this Tab, and that the one I posted most certainly did....so it would suggest to me that there is a difference between some models...I mean why else would they create a different firmware with a different .pit file? It makes no sense to do it without reason when really it is much easier to maintain the status-quo...don't you think?
Thanks for your valuable input too by the way. I really appreciate it :good:

can you re-upload ? i cannot download it