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
Related
[Q] /dev/block/mmcblk0p1 error, busy
well, everything is working perfectly in jpk.......the only that isn't is clockworkmod recovery. that is where it gives the error "can't mount sdcard, /dev/block/mmcblk0p1 is busy" or something along those lines.
now, i reflashed with odin, click re-partition, and on first boot, went and took a look, those files/directories in the /dev partition are all there. but after a power cycle or two, they're gone again (except "vold" which is empty). i even tried formating the sdcard via jpk, and it goes through fine, but i still get this error in recovery.
i have no idea what i did. my phone did crash once and i had to pull the battery out to shut it off, but it hasn't done that since. and if it's relevant, i now have a "LOST.DIR" in the root of my sdcard.
suggestions anyone please?
what if you flash back to stock 2.1 ROMs ?
does it work?
yeah, i was thinking about that.......but it's soooooooo much work to setup, but i guess that's the only way to tell for sure.
i was just wondering if anyone else was having these issues. maybe this is why samsung didn't officially release it.
EDIT: well, that did it.......sadly i'm back on 2.1, but happily, my partitions are back! so it looks like it's related to the froyo update. i don't know if it was because i used the 512 pit and not 803 or what, and i don't care. i'm happy again
there's another thread i responded too where someone said they had trouble with their internal sdcard right after they installed froyo, so it might actually be froyo causing this.
Hi,
I have tried upgrading my bell I9000m to froyo twice now and both times I have gotten the following error leaving my phone partially bricked:
Update Media please wait
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E:copy_dbdata_media:Can't mount SDCARD:"
I have sent the device into samsung twice now and both times they have fixed the issue with a full phone software restore.
I have tried the repartition option and a full restore via ODIN with no luck. I know there are others out there with the same issue and have just returned/exchanged the phone.
I donot want to try any of the JPx releases again as I am scared and dont want to be without the Galaxy S for 2 weeks.
I am creating this thread to see if anyone has managed to find a fix to the above issue or if we want to explore options to create a fix.
Serious, It bricked twice. Does that tell you anything about running Froyo Beta? Also sounds like you happen to have one of the phones from a batch that had bad memory chips. I'd replace the whole thing If I was you. Installing the Froyo Beta just showed you the problem.
I ran into the same error but got lucky enough that I was able to re-flash jh2 with re-partition and fixed the sd problem. Then flashed jpk without re-partition and no more error.
Rumy,
I had the same thing happen the first time I tried to flash to JPK from JPH. My JPH was updated through Kies. I was running a custom ROM on it with the OCLF which I forgot to uninstall before upgrading to JPK. This may have caused the problem but I really don't know.
I was stumped. I could not format the SD card without getting the same message. The first time I tried was with the 803 pit. So I tried with the 512 pit and the same thing happened. Tried several times and it finally let me reformat the SD card. Tried to flash JPK again with 512 pit and I got the same error. I figured I bricked it.
I did some reading on the forums here and I found a post advising to re-flash back to Eclair and then try again which is what I did and it worked.
I used the XWJM8 pda the bell(BMCJH2) CSC and the XXJM4 Modem with the 512 pit to go back to Eclair. Once the phone booted up properly I just followed the JPK instructions again using the 512 pit and I had no issues.
I have a rooted JPK custom rom(Rombie's 2A Full) running now with the OCLF for a little over a week and I have no issues with the phone. I was certainly crapping my pants at the time though so I hope you find a way around this.
Good luck.
Phone is the GT-I9000
Hey guys thanks for the info.
I just got my phone back and have tried to upgrade to JPK, so far so good. Hopefully it stays like that. If not I will be knocking on your doors for help
I created this thread to try and figure out a solution for everyone on the Bell I9000M, and it looks like Banger242 might have one, but there is another thread with a similar goal.
http://forum.xda-developers.com/showthread.php?p=8424399#post8424399
rumy, someone who's been a member of these forums for as long as you have, should already be well aware that this thread belongs in the Q&A section as it has nothing to do with ROM development.
Also, searching a little more on this subject before posting would have revealed that the info you needed has already been well covered in previous existing threads.
Thread moved to Q&A, and closed.
how did you fix it?
wang1chung said:
yeah, i was thinking about that.......but it's soooooooo much work to setup, but i guess that's the only way to tell for sure.
i was just wondering if anyone else was having these issues. maybe this is why samsung didn't officially release it.
EDIT: well, that did it.......sadly i'm back on 2.1, but happily, my partitions are back! so it looks like it's related to the froyo update. i don't know if it was because i used the 512 pit and not 803 or what, and i don't care. i'm happy again
there's another thread i responded too where someone said they had trouble with their internal sdcard right after they installed froyo, so it might actually be froyo causing this.
Click to expand...
Click to collapse
Can't mount /dev/block/mmcblk0p1Arrow
tried this on the 2 phone i've have got here without invoices, and it's not working
still gives the error message "Can't mount /dev/block/mmcblk0p1"
Banger242 said:
Rumy,
I had the same thing happen the first time I tried to flash to JPK from JPH. My JPH was updated through Kies. I was running a custom ROM on it with the OCLF which I forgot to uninstall before upgrading to JPK. This may have caused the problem but I really don't know.
I was stumped. I could not format the SD card without getting the same message. The first time I tried was with the 803 pit. So I tried with the 512 pit and the same thing happened. Tried several times and it finally let me reformat the SD card. Tried to flash JPK again with 512 pit and I got the same error. I figured I bricked it.
I did some reading on the forums here and I found a post advising to re-flash back to Eclair and then try again which is what I did and it worked.
I used the XWJM8 pda the bell(BMCJH2) CSC and the XXJM4 Modem with the 512 pit to go back to Eclair. Once the phone booted up properly I just followed the JPK instructions again using the 512 pit and I had no issues.
I have a rooted JPK custom rom(Rombie's 2A Full) running now with the OCLF for a little over a week and I have no issues with the phone. I was certainly crapping my pants at the time though so I hope you find a way around this.
Good luck.
Phone is the GT-I9000
Click to expand...
Click to collapse
Hi there!
Recently I've been trying to upgrade my SGS with a custom ROM, Darky's 4.0. After installing the ROM as instructed (using CWM and copying the ROM to the internal SD card), the ROM Installs, after the 1st boot it keeps looping, see video:
http://www.youtube.com/watch?v=kWrijyv-8PM (not edited, sorry for that)
Original SGS:
GT-I9000T
I9000TUBJG7
Product code: GT-I9000HKTPCW
kernel: 2.6.28
Build: eclair.ubjg5
The first upgrade I made was via Kies reg-hack to: GT-I9000HKDXEU, 'I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3, and it installed Stock Froyo update. The SGS worked fine with exception of the radio, which didn't lock my 3G over the 850 band.
Currently:
9000M running STOCK Australian I9000UGJG8 (due to radio issues, besides the Canadian ROM, this is pretty much the only ROM which modem.bin's works properly with my network, 3G 850MHz).
FW:2.1-update1
Kernel 2.3.29 [email protected] #2
Eclair.UGJG8
I tried with the following STOCK ROMs prior to the custom ROM install: I9000XWJM1, I9000XWJG5, I9000XWJM9 and I9000UGJH2.
I have ALLWAYS made an SD unmount and format, formatted the cache and factory reset. After it loops, the only way to get it back is using downloader mode and installing a STOCK ROM via ODIN (always do a .512 pit repartition)
Any suggestions to make this SGS get the ROM? maybe the kernel is bad?
Cheers!
Have u tried to format everything (exept for sd) and flash again?
Btw i love infected
Sent from my GT-I9000 using Tapatalk
Format everything? Using which app or program?
I've always used the recovery's wipe commands and the *2767*3855# command. Is that enough? or am I missing another cooler and invasive method ? A friend has suggested to use davlik.
Yeah! Infected rulz, that's what I listen when I'm in the bricking-mood lol
As i saw you have cwm installed... Boot in recovery and select mount and storrage and then select eveeything that contains format (boot wont work to format) and dont select format internal sd but DO select format sd-ext
Edit: if it doesnt work write again then ill upload u the kernel that fixed it for me yesterday. Its from this forum but since ive discovered it by coinsidence, i cant remember how its called. U can format everything then select mout usb storrage (in cwm) and push it on the root of sd. Its an update.zip
Sent from my GT-I9000 using Tapatalk
shrooms90 said:
As i saw you have cwm installed... Boot in recovery and select mount and storrage and then select eveeything that contains format (boot wont work to format) and dont select format internal sd but DO select format sd-ext
Edit: if it doesnt work write again then ill upload u the kernel that fixed it for me yesterday. Its from this forum but since ive discovered it by coinsidence, i cant remember how its called. U can format everything then select mout usb storrage (in cwm) and push it on the root of sd. Its an update.zip
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I gave that a shot, still no cigar. I guess that it goes deeper than just a formatting... maybe that secret kernel u have might brick me... erhm! I mean help me
Shoot! and I'll try it.... this OEM sucky ROM aint working that good over the Australian ROM lol. now I lost access to my cam ! sucks.
Thanx!
Try any universal lagfix kernel with clockwork enabled. Since ur phone is still flashable and ur phone still has funktionality (cwm works) im pretty hopefull that it is software/sd format related. Thats one of those cases where servic centre sais a full flash is needed by now only they are able to do that:-( but till now i always found a way to work around that by trying everything in every way. I always thought my phone is bricked anyhow so it can just get better and by coincidence it worked all of a sudden
Sent from my GT-I9000 using Tapatalk
Ihave I900T with same rom image
and am trying to upgrade to FROYO as well. Any advice on how to do so would be appreciated. Tried the various registry hacks and none have worked. I'm happy to use Odin but not sure which is the correct ROM image to use (from samfirmware). Thanks!
zevrosenthal said:
and am trying to upgrade to FROYO as well. Any advice on how to do so would be appreciated. Tried the various registry hacks and none have worked. I'm happy to use Odin but not sure which is the correct ROM image to use (from samfirmware). Thanks!
Click to expand...
Click to collapse
Well, first thing is first. I've been a couple of weeks away from my SGS tweaking. I'm right know figuring a way to make a backup of my ROM (non-nandroid), in which I can extract the Kernel, Modem and CSC (I received a brand-new unit from my provider, so I will take advantage of it )
That way I can flash them back in case of a screw-up. I didn't have that much luck with modems offered in other ROMs, so I need to keep an OEM copy of my stuff.
Also make a good copy of your /efs folder in case you mess it up. It took me around 3 weeks of reading before I started making any changes to my phone, so I'll recommend doing the same; there's no "quick-start" or quickguide on how to start. You will en up with 6 different windows open reading from everywhere
The FWs from samfw are OEMs. Theres like "not much" of improvemente if you switch to those. Take special attention to the one you chose cause most likely you will lose your 3G and/or 850MHz band. I recommend using only Australian and Canadian ROMs(I9000UGJG8 and I9000UGJH2 worked for me, you might try also I9000UGJK3). Regarding custom ROMs, you will need to try and try until you get it right as our SGS model is not the most popular. This means endless flashing
Cheers.
Sgs froyo flash nam bands
Thanks for the advice. This project consumed my thanksgiving but I finally got a good working SGS in the ATT network. I bought an unlocked SGS from Negri Electronics with the USA 3G bands but it came without FROYO and didn't have the 3 button restore available. After reading and reading (your note about multiple open windows at the same time is all too true!) and trying and trying, I was finally able to get to download mode by installing all the Android SDK tools onto my PC then going in by way of ADB. Far more complicated than a simple registry hack and ODIN but it worked.
I installed the DOC BUJP8 v9 ROM with all the enhancements and AOSP Email (I tried and tried to get stock FROYO email to work with 2 exchange accounts but it was impossibly slow and didn't work) while AOSP is working fine.
It seems, because my SGS had the 850 bands to begin with, that it's working fine. I found this other post on XDA (#770041) that had some keycodes I was able to use (*#2263#) and confirm I still have the 850 band.
Needless to say, make a good backup and be prepared - as already warned - to flash several times and it was ultimately a "trial and error" process that worked.
does anyone have the original brazilian/latinamerican i9000T firmware? I flashed the SGS I got from Negri with spike speedy and it looks like I lost my 850 3G band.
I never did find out how to totally back up the SGS as in back up each PDA, PHONE, and CSC file so as to be able to truly factory default it.
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
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?
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.