My phone has/was working fine for the longest time. Was running cog 3.04. Ever since trying to update to cog4, i get symlink error EVERY time i try to install. I am flashing back to stock, and doing a master clear every time.
Thinking it was the cog4 rom, i have tried serendipity, and paragon. Though the error is on different lines, it gives me a symlink error everytime it is installing. What gives! I will throw this phone in the garbage if i have to be stuck on stock now!
On another note, anytime i try to restore a backup (os backup, not apps), it will successfully restore, but then when it reboots it is back to the stock recovery. UGH. Someone please give me some guidance!
Do you get an error like this:
E: Can't symlink /system/bin/cat
E: Failure a lin 7:
symlink toolbox SYSTEM:bin/cat
installation aborted
I probably get at least one of these errors every time that I flash. I have asked around and some people say that it can be a bad download. I would recommend downloading cog4 again and maybe even 2 to 3 times and putting all of those on your internal memory (name them cog4, cog4a, cog4b.zip or something like that). This is what I do and typically at least one of the three/four that I have on there will work.
Yea I had one of these last night and it was just a bad download. Compared the file size and they were different
Sent from my SAMSUNG-SGH-I897 using XDA App
PLEAE SOMEBODY HELP I AM BEGGING PLEASE.
The ONLY custom rom i can install is cog3.04. Nothing else will work. I have flashed back to stock 2.1 and 2.2 and it does not make a difference. I have master cleared a million times. I have repartitioned my sd card also. From what i am gathering on the internet, is that i need to change the size of the system partition. It is too small. I cannot find ANY WAY AT ALL to do that. I will seriously send someone money over paypal if they just please try to help me. I am dead serious.
xsteven77x said:
PLEAE SOMEBODY HELP I AM BEGGING PLEASE.
The ONLY custom rom i can install is cog3.04. Nothing else will work. I have flashed back to stock 2.1 and 2.2 and it does not make a difference. I have master cleared a million times. I have repartitioned my sd card also. From what i am gathering on the internet, is that i need to change the size of the system partition. It is too small. I cannot find ANY WAY AT ALL to do that. I will seriously send someone money over paypal if they just please try to help me. I am dead serious.
Click to expand...
Click to collapse
The errors are different on every rom, but pretty much the same. It's always symlink error system/xbin/su or system/xbin/cap. ALWAYS. No matter what rom it is. BESIDES COG 3.04. That was the rom i had RIGHT before all this started. I tried to install cog 4 and it ****ed my phone. Not sure what to do....
Dead serious about paying someone to help me.
xsteven77x said:
The errors are different on every rom, but pretty much the same. It's always symlink error system/xbin/su or system/xbin/cap. ALWAYS. No matter what rom it is. BESIDES COG 3.04. That was the rom i had RIGHT before all this started. I tried to install cog 4 and it ****ed my phone. Not sure what to do....
Dead serious about paying someone to help me.
Click to expand...
Click to collapse
You have tried the full ODIN, and using Partition?
When flashing back to stock, use Odin3, and have the Re-Partition box checked
Note: Note I have not ever had to do that before, so not sure if would work
indomikey said:
You have tried the full ODIN, and using Partition?
When flashing back to stock, use Odin3, and have the Re-Partition box checked
Note: Note I have not ever had to do that before, so not sure if would work
Click to expand...
Click to collapse
Yes i have used the one click and the regular full odin. And yes i clicked the re-partition thinking that would help me. Makes no difference
The key to this mystery i think is the fact that cog 3.04 is the ONLY custom rom that will go on here...and was the one i had right before my phone got royally ****ed.
xsteven77x said:
Yes i have used the one click and the regular full odin. And yes i clicked the re-partition thinking that would help me. Makes no difference
The key to this mystery i think is the fact that cog 3.04 is the ONLY custom rom that will go on here...and was the one i had right before my phone got royally ****ed.
Click to expand...
Click to collapse
How about formatting through recovery menu? and then reinstalling with odin
indomikey said:
How about formatting through recovery menu? and then reinstalling with odin
Click to expand...
Click to collapse
Yes i have. Someone with a different phone but the same problem fixed it by doing some type of rm- rf /system through adb? It just totally deletes/wipes system partition? Not sure if that would help but anytime i try it says it cannot access system whether i have it mounted or not.
The problem seems to be (gathered this from reading) that the system partition is full and thats why it can't symlink or something. But if the system partition is getting formatted everytime i dont understand how that makes any sense.
xsteven77x said:
Yes i have. Someone with a different phone but the same problem fixed it by doing some type of rm- rf /system through adb? It just totally deletes/wipes system partition? Not sure if that would help but anytime i try it says it cannot access system whether i have it mounted or not.
The problem seems to be (gathered this from reading) that the system partition is full and thats why it can't symlink or something. But if the system partition is getting formatted everytime i dont understand how that makes any sense.
Click to expand...
Click to collapse
But even then, why would cog 3.04 install? And no other custom rom?
xsteven77x said:
But even then, why would cog 3.04 install? And no other custom rom?
Click to expand...
Click to collapse
Maybe Cog is still "suck" in that partition and can't be deleted, thereby taking up the space..... not sure why though and how to get at it, can you see the files through adb?
indomikey said:
Maybe Cog is still "suck" in that partition and can't be deleted, thereby taking up the space..... not sure why though and how to get at it, can you see the files through adb?
Click to expand...
Click to collapse
Thats an interesting theory, seems to make sense! I know how to do basic adb functions but i never really messed with the files/file system thorugh it. If you wanna give me any type of directions i would love it!
xsteven77x said:
Thats an interesting theory, seems to make sense! I know how to do basic adb functions but i never really messed with the files/file system thorugh it. If you wanna give me any type of directions i would love it!
Click to expand...
Click to collapse
Sorry I'm noobish when it comes to ADB, try this thread.... not sure if it will help: http://forum.xda-developers.com/showthread.php?t=717874 realize, it is not specific for captivate or any of our ROMS, its talking about Cyanogenmod, but hopefully you can use something there
I have to head out, if you are still having problems when I get back, I'll keep searching, good luck
Somebody ANYBODY. I can only install cog 3.04. Anything else and i mean ANYTHING gives me symlink system/xbin/su. That file is not even IN the roms i'm trying to flash in that folder! WTF
xsteven77x said:
Somebody ANYBODY. I can only install cog 3.04. Anything else and i mean ANYTHING gives me symlink system/xbin/su. That file is not even IN the roms i'm trying to flash in that folder! WTF
Click to expand...
Click to collapse
if the file isnt there, THAT is the problem. the update-script is looking for that file. have you tried actually removing that line from the update-script?
Pirateghost said:
if the file isnt there, THAT is the problem. the update-script is looking for that file. have you tried actually removing that line from the update-script?
Click to expand...
Click to collapse
I have tried removing that line, and tried moving that file into the folder. Makes no difference. It's doing this error on EVERY custom rom...i can't believe that every rom maker messed up the su symlink lol.
xsteven77x said:
I have tried removing that line, and tried moving that file into the folder. Makes no difference. It's doing this error on EVERY custom rom...i can't believe that every rom maker messed up the su symlink lol.
Click to expand...
Click to collapse
they didnt. there are literally thousands of people flashing roms every day....
that symlink works properly on all the captivates i have with all the roms that i throw together.....
Pirateghost said:
they didnt. there are literally thousands of people flashing roms every day....
that symlink works properly on all the captivates i have with all the roms that i throw together.....
Click to expand...
Click to collapse
That didnt come out right. It was meant to read "i do not believe that every rom maker messed up the su symlink". Meaning that ya, it is just me, i know it works fine for everyone else.
Related
When booting the Nexus One I get an Android with an explanation point, then I am able to toggle the volume key and power to get into "Android system recovery <2e>" screen which gives me the options
-reboot system now
-apply sdcard:update.zip
-wipe data/factory reset
-wipe cache partition
when it's in this screen I can NOT access it through fastboot or adb.
It looks like it is only allowing me to push "officially" signed update.zip files to it and nothing else.
I cannot get it in to hboot or anything else it ONLY boots into "Android system recovery <2e>"
Maybe someone has an official update.zip boot image they can send me to or some other idea it would be much appreciated since I cannot use the phone at all.
Thank you in advanced, Please help!!!
Did you try holding trackball and power button when the phone is turned off to bring you directly to fastboot?
irishrally said:
Did you try holding trackball and power button when the phone is turned off to bring you directly to fastboot?
Click to expand...
Click to collapse
Yes, with no luck, it just goes straight to the Android and explanation point
Are you rooted? Unlocked bootloader? What did you do to get you into this situation?
Not to worry you, but usually not being able to boot into fastboot is not a good thing.
hyperandy said:
Maybe someone has an official update.zip boot image they can send me to or some other idea it would be much appreciated since I cannot use the phone at all.
Thank you in advanced, Please help!!!
Click to expand...
Click to collapse
Heres a thread that contains the official 2.1 update1 zip.
http://forum.xda-developers.com/showthread.php?t=627823
Maybe the volume key or trackball is stuck/damaged?
irishrally said:
Are you rooted? Unlocked bootloader? What did you do to get you into this situation?
Not to worry you, but usually not being able to boot into fastboot is not a good thing.
Click to expand...
Click to collapse
ya at this point I was kinda figuring that but I am hopeful ...I unlocked the boot loader and everything was going great until I partitioned the sd in the recovery image, then I started getting a weird MISC error and couldn't boot up at all, only in recovery but fastboot and everything still worked. Then I saw a post about applying the original image to the device via fastboot, preformed that and ever since then I have had a $500 brink that lights up
I don't think you can brick the N1 by just flashing a ROM, usually this only happens when changing the radio or spl.
I would try taking out your sd card, copy all your files you your computer, format your sd card, copy your files back to your sd card and see what that does for you. Maybe some issue arose when you partitioned your sd card, although you said fastboot still worked until you flashed the ROM. Worth a shot though.
If you can access fastboot then, I would flash Amon Ra's custom recovery image via fastboot and take it from there.
well I actually tried a completely different sdcard and then none at all. No luck. If it's not letting me into hboot do you think it may have gotten corrupted or something
hyperandy said:
well I actually tried a completely different sdcard and then none at all. No luck. If it's not letting me into hboot do you think it may have gotten corrupted or something
Click to expand...
Click to collapse
Honetly, I don't know. Did you try copying the .zip in the link posted above to your sdcard and then applying that zip in recovery?
Hopefully someone that knows more than me will chime in and have some better ideas.
irishrally said:
Honetly, I don't know. Did you try copying the .zip in the link posted above to your sdcard and then applying that zip in recovery?
Hopefully someone that knows more than me will chime in and have some better ideas.
Click to expand...
Click to collapse
maybe it's because I just woke up but I am not clear what you are asking, can you rephrase that? The link above my SD card?
hyperandy said:
maybe it's because I just woke up but I am not clear what you are asking, can you rephrase that? The link above my SD card?
Click to expand...
Click to collapse
Did you try copying the .zip file in the link below to your sd card and trying to flash it in recovery?
http://forum.xda-developers.com/showthread.php?t=627823
Thank you, ya I didn't see the link the first time. duh. Yep I tried that and I get a build.prop error (although this update says installing for a second and i see a progress bar, I have tried that same file from a few download locations to make sure it wasn't a bad download too):
file_getprop: Failed to stat "/system/build.prop": No such file or directory
E:Error in /sdcard/update.zip
(status 7)
Installation aborted
Thank you for all your help!! but I am afraid this isn't looking to good.
I also tried creating that file just to see but since it wasn't officially signed it gave me an error about that
I think at this point it is looking for a specific signed update.zip file, where I find that, I have no idea.
It almost seems like I need the whole update.zip officially signed by google and/or HTC and then it would flash. I highly doubt they are going to hand that over. I am half temped to see if I could send it in to them to be reflashed even for a fee if it means I can get this thing working again, but I don't even know if they would offer that. It's only 2 months old and I think the file I need maybe out there but damned if I have been able to find it anywhere.
hyperandy said:
I think at this point it is looking for a specific signed update.zip file, where I find that, I have no idea.
It almost seems like I need the whole update.zip officially signed by google and/or HTC and then it would flash. I highly doubt they are going to hand that over. I am half temped to see if I could send it in to them to be reflashed even for a fee if it means I can get this thing working again, but I don't even know if they would offer that. It's only 2 months old and I think the file I need maybe out there but damned if I have been able to find it anywhere.
Click to expand...
Click to collapse
I wouldn't give up yet. I'm sure there is someone out there that can tell you you are completely hosed, or help you fix the problem.
If you can't fix it, I have heard it will cost $196 for a new motherboard if you send it in to HTC. They could just reflash your phone but I heard they handle a case like this by charging you for a motherboard swap. Second hand information though.
irishrally said:
I wouldn't give up yet. I'm sure there is someone out there that can tell you you are completely hosed, or help you fix the problem.
If you can't fix it, I have heard it will cost $196 for a new motherboard if you send it in to HTC. They could just reflash your phone but I heard they handle a case like this by charging you for a motherboard swap. Second hand information though.
Click to expand...
Click to collapse
I believe that, I work in the field service industry and I see stuff like that all the time. Although I would rather pay the 196 instead of 560+ again. I am almost 100% certain this could be re-flashed with the right file. but I have so far spent 2 full days trying different things, I think I will give it until tomorrow and then send it in (by then I should be good an sick of searching). Unfortunately, I am in love with my Nexus. it's been a while since I had a phone I really enjoyed as much. If I knew another great phone was coming out in a week I would probably say the heck with it and just buy the next one but this is still an awesome device.
hyperandy said:
I believe that, I work in the field service industry and I see stuff like that all the time. Although I would rather pay the 196 instead of 560+ again. I am almost 100% certain this could be re-flashed with the right file. but I have so far spent 2 full days trying different things, I think I will give it until tomorrow and then send it in (by then I should be good an sick of searching). Unfortunately, I am in love with my Nexus. it's been a while since I had a phone I really enjoyed as much. If I knew another great phone was coming out in a week I would probably say the heck with it and just buy the next one but this is still an awesome device.
Click to expand...
Click to collapse
Have you tried every option in all the other "HELP BRICK" posts?? I don't really have time to search (and my nexus is working fine) but I know there has been plenty of threads like this before. Multiple options where tried, some successfully and some not. I would not give up unless it won't power on at all. Does ADB logcat work during a boot? Fastboot Devices? anything??????
martin0285 said:
Have you tried every option in all the other "HELP BRICK" posts?? I don't really have time to search (and my nexus is working fine) but I know there has been plenty of threads like this before. Multiple options where tried, some successfully and some not. I would not give up unless it won't power on at all. Does ADB logcat work during a boot? Fastboot Devices? anything??????
Click to expand...
Click to collapse
No haven't tried those checking the Help Brick post I will see what I can find. No adb and not fastboot devices, just says waiting for device if I try anything.
Since you have unlocked the bootloader have you tried a complete reload?
fastboot: flash boot, flash recovery
recovery: wipe everything, reset, install latest CM.
Did you ever figure this out?
I have done many searches trying to find the answer but I haven't found an answer that I thought explained it. Some people have said that the file downloaded incorrectly and I should just re-download the ROM again. I have flashed many ROMs such as Cog, Perception, Phoenix, FF, SN and for every one of my flashes I have gotten one of these errors at least once.
I have flashed back to stock, master cleared, fixed permissions, flashed over ROMs without doing those steps and I still get at least one of these:
E: Can't symlink /system/bin/cat
E: Failure a lin 7:
symlink toolbox SYSTEM:bin/cat
installation aborted
E: Can't chown/mod /system/xbin/su
(no such file or directory)
E: Failure at line 71:
set_perm 0 0 04755 SYSTEM:xbin/su
Installation aborted
I have started putting 3 to 4 .zip files on my phone before I try to flash to save me from having to flash back to stock. I would just like to know if there was any way to do something about this on my end so my flashing time doesn't take an hour or more instead of a few minutes.
Quick question you are using cwm to flash and not stock recovery
[ROM] Precision 3.5 [Kernel] Suckerpunch #51
I am using cwm
Wow dude i have the SAME exactly problem and no one can help me! This all started cause i tried the cog4 rom and my phone has been ****ed ever since! Wont install any roms, all symlink errors, and now i can't even get it to restore a backup. It will successfully restore but upon reboot it just goes back to stock recovery UGH. I just want my phone back! And yes i am doing odin and master clear EVERY SINGLE TIME. Have downloaded each rom file over 10 times each. This is killing me!
xsteven77x said:
Wow dude i have the SAME exactly problem and no one can help me! This all started cause i tried the cog4 rom and my phone has been ****ed ever since! Wont install any roms, all symlink errors, and now i can't even get it to restore a backup. It will successfully restore but upon reboot it just goes back to stock recovery UGH. I just want my phone back! And yes i am doing odin and master clear EVERY SINGLE TIME. Have downloaded each rom file over 10 times each. This is killing me!
Click to expand...
Click to collapse
I actually just responded to the thread you started before I noticed that you replied to mine. I just suggested that you download some more files but it seems like you have done that already.
If someone with knowledge would just PLEASE read this they can fix this for us. I found someone with the same problem, just different phone. They fixed it! We just need someone with the know-how to convert the directions into how you would do the same things on our phones...
http://forum.samdroid.net/f38/cannot-install-any-rom-recovery-4091/
PLEASE PLEASE GUYS HELP
You will need to flash back to stock. Odin 1-Click should do the trick, however you should Master Clear BEFORE you start flashing the stock ROM. The idea is to wipe the card of any inconsistencies in file system structure; sometimes parts can still be in Ext4 (even after 'unlagfixing') when other partitions are back to rfs.
I'd try that. I had a devil of a time with the same issue and after a lot of troubleshooting this worked for me.
Good luck!
clemmie said:
You will need to flash back to stock. Odin 1-Click should do the trick, however you should Master Clear BEFORE you start flashing the stock ROM. The idea is to wipe the card of any inconsistencies in file system structure; sometimes parts can still be in Ext4 (even after 'unlagfixing') when other partitions are back to rfs.
I'd try that. I had a devil of a time with the same issue and after a lot of troubleshooting this worked for me.
Good luck!
Click to expand...
Click to collapse
I have flashed back to stock with one click odin, 3 button odin, and every odin ever made(exaggerating) probably 40-50 times today . I have master cleared before flashing, after flashing. I have re-partitioned. I have fixed permissions. I have done all of the above in every order imaginable.
I have also tried to install over 5 different roms. This all started whenever i flashed the cog4 that was ORIGINALLY posted yseterday. It had a line 15 error and apparently a wrong kernel. Ever since my phone has never been the same. It must have really ****ed something up.
After reading all night...this is NOT exclusive to the captivate. This has happened to just about every android phone out there. And every topic in existence ends up dying and no one ever gives a solution. Most point to the system partition being full, and it messing up and thats why it's not able to symlink. Others say apps2sd being built in a rom can do that. ONE guy did the rm wipe system thing through adb and got it to work. Please guys HELP PLEASE. My phone is absolutely useless right now being able to run nothing but stock. PLEASE.
I am trying to do a rm -rf /system in an root adb shell in recovery. It always says device is busy. Any ideas!?
Sorry, wrong thread. Ignore me.
Dam thought we were finally getting some help!
Are you using some kind of download accellerator or manager?
Sent from my HTC Vision
Pirateghost said:
Are you using some kind of download accellerator or manager?
Sent from my HTC Vision
Click to expand...
Click to collapse
No? I'm not getting where your going with this....
BTW XDA i'm NOT gonna let this go till i get some answers my phone is totally useless right now. I either accept that i just wasted hundreds of dollars on a phone OR that i may annoy some of the community to get them to pay attention. Obviously i'm gonna go with no. 2.
xsteven77x said:
No? I'm not getting where your going with this....
BTW XDA i'm NOT gonna let this go till i get some answers my phone is totally useless right now. I either accept that i just wasted hundreds of dollars on a phone OR that i may annoy some of the community to get them to pay attention. Obviously i'm gonna go with no. 2.
Click to expand...
Click to collapse
FOR THE LOVE OF GOD SOMEONE PLEASE. i have scoured the entire internet...if someone here can't help then my phone is garbage.
Hi guys,
I have been searching the forums for 2 weeks now trying to fix this myself, but I have put my pride in my pocket and am asking for help.
Backstory: Rooted phone, flashed CWM, used tons of custom froyo ROM's (doc roms mainly) and most recently Darky's 9.3 (awesome).
But then i decided I wanted Gingerbread (this is where the trouble began). Gingerbread worked just fine, but as there is no custom roms, I flashed back to 2.2 (obviosly screwed something up), because since then I have been plagued with process com.whatever.android.somethingelse has stopped unexpectedly. please try again.
please don't ask which force close message I am getting, lets just say, I am pretty sure I am getting them all!
I have flashed stock 2.1, custom 2.1, stock 2.2, custom 2.2's, I even went back to gingerbread a few times trying to fix this ***** of a problem. I tried re partitioning just the .pit file and then the other 3 files seporatly. NOTHING WORKS.
So, I am calling out to all you guys and girls who are heaps smarter than me to please help. the phone functions, turns on, make or receive calls and texts (not mms), emails work sometimes, but if I turn the phone off and on all the settings are wiped and I need to reload all the user details.
Oh, I should also add another major issue, I cannot use the internal memory for anything, I cannot take pictures unless I select the external SD card, I cannot install apps from market or .apk. I cannot even move data to it when its mounted on the pc.
I am completely lost. please help me.
And thanks in advance.
I
C'mon guys, I know there is a lot to read, but please, can no-body help me?
Sounds like it might be a dead internal sd card. You said you tried a re-partition with 3 file firmware? That should fix pretty much anything. I think your only option is to return to samsung at this point.
DrFredPhD said:
Sounds like it might be a dead internal sd card. You said you tried a re-partition with 3 file firmware? That should fix pretty much anything. I think your only option is to return to samsung at this point.
Click to expand...
Click to collapse
Thanks for the response.
is it possible to fix myself?
As Samsung will not cover it, even if I flash the stock Telstra ROM, it will still show that it has been rooted?
In doing your research, I'm sure you've heard of the internal SD problems that plague the i9000, are you by chance with Bell Mobility? This line concerns me..
"Oh, I should also add another major issue, I cannot use the internal memory for anything"
When I experienced multiple FCs (force closes) and incompatible system UID's, I tried flashing every kind of ROM there was with every kind of PIT file as well to no avail. However, one in particular worked for me and others. It is usually referred to as a full ROM. It contains the .csc and .sbl in it as well as the usual ROM contents.
The ROM I used is called FULL-i9000UGJH2.tar. Note, flashing this ROM with a pit file (be it 512, 513, or 803) wouldn't help me at all. What fixed the problem was flashing ONLY the ROM file in ODIN. Unfortunately, I can't find the thread where I found this ROM. I suggest searching around for it, if you can't find it PM me, and I will up it somewhere for you.
I'm not sure if this will help with your specific case, but its worth a shot. Also, wherever applicable, do a factory reset, clear your cache, and a full wipe install.
Good luck.
[edit]
Do a complete wipe and install with a stock 2.2 or 2.1 ROM in ODIN, there will be no evidence of a root.
Kops said:
In doing your research, I'm sure you've heard of the internal SD problems that plague the i9000, are you by chance with Bell Mobility? This line concerns me..
"Oh, I should also add another major issue, I cannot use the internal memory for anything"
When I experienced multiple FCs (force closes) and incompatible system UID's, I tried flashing every kind of ROM there was with every kind of PIT file as well to no avail. However, one in particular worked for me and others. It is usually referred to as a full ROM. It contains the .csc and .sbl in it as well as the usual ROM contents.
The ROM I used is called FULL-i9000UGJH2.tar. Note, flashing this ROM with a pit file (be it 512, 513, or 803) wouldn't help me at all. What fixed the problem was flashing ONLY the ROM file in ODIN. Unfortunately, I can't find the thread where I found this ROM. I suggest searching around for it, if you can't find it PM me, and I will up it somewhere for you.
I'm not sure if this will help with your specific case, but its worth a shot. Also, wherever applicable, do a factory reset, clear your cache, and a full wipe install.
Good luck.
[edit]
Do a complete wipe and install with a stock 2.2 or 2.1 ROM in ODIN, there will be no evidence of a root.
Click to expand...
Click to collapse
Thanks for this dude, I will start my search for that rom.
I do a factory reset, wipe cache and data every time, however after doing all of that and flashing a new rom, it still has my google account details in the phone?? this is wierd, as I factory reset from recovery mode AND wipe all data from within the phone? Any suggestions?
Edit: and no, its is an Australian Telstra i9000
glennr said:
Thanks for this dude, I will start my search for that rom.
I do a factory reset, wipe cache and data every time, however after doing all of that and flashing a new rom, it still has my google account details in the phone?? this is wierd, as I factory reset from recovery mode AND wipe all data from within the phone? Any suggestions?
Edit: and no, its is an Australian Telstra i9000
Click to expand...
Click to collapse
Hmm, that is odd. How are you flashing your ROMs, using CWM? Have you used ODIN before?
Kops said:
Hmm, that is odd. How are you flashing your ROMs, using CWM? Have you used ODIN before?
Click to expand...
Click to collapse
I am using odin, this is the wierd part. I have tried repartitioning, not repartitioning, I have tried 512.pt 803.pit, full wipe and reset from both in the phones settings and recovery mode. reboot it, go through settup wizzard (which eventually force closes requiring me to reboot), go into accounts and there is my google account still set up???
Edit: also, I cannot find a file called FULL-i9000UGJH2.tar, I am downloading i9000UGJH2.tar as we speak, but i doubt it is the one you were reffering to, if you are able to point in in the right direction, that would be ace.
Cheers
glennr said:
I am using odin, this is the wierd part. I have tried repartitioning, not repartitioning, I have tried 512.pt 803.pit, full wipe and reset from both in the phones settings and recovery mode. reboot it, go through settup wizzard (which eventually force closes requiring me to reboot), go into accounts and there is my google account still set up???
Click to expand...
Click to collapse
If you're entering your gmail address in during the setup wizard, our google account will be linked. If you're not setting anything up and it is remembering your info, then something is definitely fishy.
I would flash back to a stock rom, and see what Samsung or your provider can do for you. In all honesty, the only thing I would be able to suggest is flashing and wiping
[edit]
When you download that ROM, open it up (using a program like WinRAR). The point of a full rom is that it contains
-cache.rfs
-dbdata.rfc
-factoryfs.rfs
-modem.bin
-param.lfs
-sbl.bin
-zimage
I'm unsure of any incompatibilities between the Canadian and Australian versions, but I will upload my copy for you to try.
Kops said:
If you're entering your gmail address in during the setup wizard, our google account will be linked. If you're not setting anything up and it is remembering your info, then something is definitely fishy.
I would flash back to a stock rom, and see what Samsung or your provider can do for you. In all honesty, the only thing I would be able to suggest is flashing and wiping
Click to expand...
Click to collapse
I'm not entering any info during the setup wizard?
could it be something to do with the file system gingerbread uses? these issues only started when I went back from gingerbread to froyo? (and before you ask, I have tried going back to gingerbread with no solution)
I may have to bite the bullet and shoot it back to Samsung... or just buy another one! would love to try FULL-i9000UGJH2.tar if you could remember where you got it?
Thanks again for your help.
Cheers,
glennr said:
I'm not entering any info during the setup wizard?
could it be something to do with the file system gingerbread uses? these issues only started when I went back from gingerbread to froyo? (and before you ask, I have tried going back to gingerbread with no solution)
I may have to bite the bullet and shoot it back to Samsung... or just buy another one! would love to try FULL-i9000UGJH2.tar if you could remember where you got it?
Thanks again for your help.
Cheers,
Click to expand...
Click to collapse
I seem to have remembered it being in this thread, which is why i had it on bookmark, but I'm not sure if the link has been removed or if i had been mistaken since I can no longer find it. I'm uploading for you to Rapidshare, where you can download as a free user...~30 mins . Again, I'm not sure if there are modem incompatibilities or not since this I am in Canada, and you are in Australia.
Another place to check may be here...
http://forum.xda-developers.com/showthread.php?t=846913
Kops said:
If you're entering your gmail address in during the setup wizard, our google account will be linked. If you're not setting anything up and it is remembering your info, then something is definitely fishy.
I would flash back to a stock rom, and see what Samsung or your provider can do for you. In all honesty, the only thing I would be able to suggest is flashing and wiping
[edit]
When you download that ROM, open it up (using a program like WinRAR). The point of a full rom is that it contains
-cache.rfs
-dbdata.rfc
-factoryfs.rfs
-modem.bin
-param.lfs
-sbl.bin
-zimage
I'm unsure of any incompatibilities between the Canadian and Australian versions, but I will upload my copy for you to try.
Click to expand...
Click to collapse
Mate that would be great, I am not too fussed about compatibility at this stage, just want to get access to the internal sd again, then I can flash one of the many working froyo roms I have.
Cheers bud.
glennr said:
Mate that would be great, I am not too fussed about compatibility at this stage, just want to get access to the internal sd again, then I can flash one of the many working froyo roms I have.
Cheers bud.
Click to expand...
Click to collapse
The way you're referring to accessing this internal SD....are you flashing your ROMs to an external microsd card?
Here is the full UGJH2 that I flashed (with no other options) that saved me.
http://rapidshare.com/files/456841681/FULL-I9000UGJH2.tar
Give it a shot.
Kops said:
The way you're referring to accessing this internal SD....are you flashing your ROMs to an external microsd card?
Here is the full UGJH2 that I flashed (with no other options) that saved me.
http://rapidshare.com/files/456841681/FULL-I9000UGJH2.tar
Give it a shot.
Click to expand...
Click to collapse
No, by accessing my SD, i mean being able to download ansd install apps (and things like that). also, just tried to remove my google (gmail) account from my phone, and it wouldn't let me, it keeps force closing.
Thanks for the upload mate, I really appreciate it, currently downloading it, will let you know.
Cheers again.
Kops said:
The way you're referring to accessing this internal SD....are you flashing your ROMs to an external microsd card?
Here is the full UGJH2 that I flashed (with no other options) that saved me.
http://rapidshare.com/files/456841681/FULL-I9000UGJH2.tar
Give it a shot.
Click to expand...
Click to collapse
Hey mate, no go, i got some functionality back on the phone, but still force closes and I cannot save anything to SD (or install apps).
another email account (an exchange server account) that was previously deleted has appeared back set up and working (I have not been able to set this up for a week), it appeared on its own which leads me to think there is a hidden partition on my internal sd, hence I cannot access it. must be something to do with Gingerbread.
Thanks for all your help though.
glennr said:
Hey mate, no go, i got some functionality back on the phone, but still force closes and I cannot save anything to SD (or install apps).
another email account (an exchange server account) that was previously deleted has appeared back set up and working (I have not been able to set this up for a week), it appeared on its own which leads me to think there is a hidden partition on my internal sd, hence I cannot access it. must be something to do with Gingerbread.
Thanks for all your help though.
Click to expand...
Click to collapse
Edit: It just completely crashed again, force closes just about everything that is open, phone functionality is gone (phone icon vanished) as did contacts. freezes for a couple of minutes and then reboots. i may have to throw it at a wall!
I cannot find anything about the gingerbread partition that would cause problems with froyo. damn this thing!!!
Have you tried reformatting your internal SD
Settings>SD card and phone storage>internal SD>Format
http://forum.xda-developers.com/showthread.php?t=845708
You might find it useful.
SCIENTYREAL said:
Have you tried reformatting your internal SD
Settings>SD card and phone storage>internal SD>Format
Click to expand...
Click to collapse
Hi mate,
I have tried that several times, i think there is a hidden partition thanks to Gingerbread.
I would be sure that your internal sd card is screwed but since everything worked fine before gingerbread something else has probably happened. Also your data wont delete and that seems to be the source of the problem. Try to install the lagfix from k13d and see if it had any results. This should reformat all partitions on the internal sd.
It's been quite a learning curve getting my Sprint CDMA Galaxy Tab and attempting to load every Miui, CM7/CM9 I could find on XDA and Rootzwiki. I never fully tested my tablet before beginning the delve into the flashing world so I don't know if this is an issue with the tablet itself or caused by my endless flashing trials.
I simply am unable to save any settings or data. Everytime I boot up, no matter which ROM (Miui CM7/9), it is always factory reset. This is quite frustrating.
I'm back on stock from odining Sprint EF17 GB w/ original PIT file and this is still happening. Does anyone have any idea if this was self-incurred or if there is a partitioning bug of some sort that I have missed.
Much Thanks in advance!
So every time you turn on your Tab it loads and then reboots in a continuous loop? Do you see the Android OS unlock screen or the load process does not gets so far? Because if it does not then in my opinion the boot loader is incorrect for some reason. That is my opinion.
What you can do if you suspect that the PIT is incorrect, you read your PIT and save via Heimdall and compare it with somebody else who has the same Tab as you have.
Unable to personalize "issue"
Zero_Tab_2011 said:
So every time you turn on your Tab it loads and then reboots in a continuous loop? Do you see the Android OS unlock screen or the load process does not gets so far? Because if it does not then in my opinion the boot loader is incorrect for some reason. That is my opinion.
What you can do if you suspect that the PIT is incorrect, you read your PIT and save via Heimdall and compare it with somebody else who has the same Tab as you have.
Click to expand...
Click to collapse
Negative. This is not a continuous loop bug. It is a "unable to personalize" bug. I can install market/apps/data/contacts etc etc, but every single time I boot up. it's a Fresh Copy with no personalized settings.
sounds like permission issue? Is there a fix permission in recovery?
priyana said:
sounds like permission issue? Is there a fix permission in recovery?
Click to expand...
Click to collapse
Yes I booted into CWM,fixed permissions, rebooted, put 2-3 icons on desktop, rebooted.
Nothing, it was back to factory default settings.
A permissions issue does make sense, but it didn't work and this is just mind boggling to me.
jrhsu529 said:
Yes I booted into CWM,fixed permissions, rebooted, put 2-3 icons on desktop, rebooted.
Nothing, it was back to factory default settings.
A permissions issue does make sense, but it didn't work and this is just mind boggling to me.
Click to expand...
Click to collapse
I've got the exact same problem... after reading forums for 14hrs seems like a galaxy tab thing not common at all with no real answers
Sprint SPH-P100
I'm sorry you have the same problem.
However I'm glad to have someone to share it with. Misery loves company. I've scoured the web for 3 days and have nothing.
Please if anybody knows what's going on. From my non-developer logic I need to find a way to get the changes I make to my phone to write permanently (so to speak), everything I do is temporary until I reboot.
Hmmmm... I suppose you guy's already tried to wipe all caches and reflash the kernel (= not the ROM, just the kernel) ?
Where do I find the Kernal?
It's the zImage file right?
The ROM I'm on right now is JT's CM7 here:
I wanted to try just flashing the kernal but I am unable to locate the zImage file. What directory is it in?
Edit: I found the Kernal, it's actually in the CWM 5.0.2.7 package. I'm gonna try flashing the kernal over to see if it fixes the issue.
Edit2: No cigar, reflashing kernal does not fix this issue. On a side note, I tried to upgrade to CM9 and got "Encryption Unsuccessful". Not that I am knowledgable in this, but it seems the issue may share some commonality with that.
jrhsu529 said:
Where do I find the Kernal?
It's the zImage file right?
The ROM I'm on right now is JT's CM7 here:
I wanted to try just flashing the kernal but I am unable to locate the zImage file. What directory is it in?
Click to expand...
Click to collapse
Hi,
Yah, zImage should be the kernel.
In this thread, I found something about the issue you have. It might have something to do with NoFrillsCPU... Hope this helps
dirlan2001 said:
Hi,
Yah, zImage should be the kernel.
In this thread, I found something about the issue you have. It might have something to do with NoFrillsCPU... Hope this helps
Click to expand...
Click to collapse
Eh, I just went through all 37 pages of that thread. Couldn't find anything on NoFrillsCPU and didn't see any issues that resemble mine. Was that tthe right thread? I'll do a google for nofrillscpu and see if that brings up anything.
jrhsu529 said:
Eh, I just went through all 37 pages of that thread. Couldn't find anything on NoFrillsCPU and didn't see any issues that resemble mine. Was that tthe right thread? I'll do a google for nofrillscpu and see if that brings up anything.
Click to expand...
Click to collapse
you read very fast then LOL
Anyway, my bad, it's not NoFrillsCPU but it's SetCPU ... It's in the OP : "Please DO NOT check the "Set on Boot" button in SetCPU untill you have tested it, or you may not be able to get control back without a reflash."
EDIT : Looks like there's a misunderstanding in me confused about the CDMA versions. Sounds like this thread has all the solutions you need. I may be wrong , of course...
dirlan2001 said:
you read very fast then LOL
Anyway, my bad, it's not NoFrillsCPU but it's SetCPU ... It's in the OP : "Please DO NOT check the "Set on Boot" button in SetCPU untill you have tested it, or you may not be able to get control back without a reflash."
Click to expand...
Click to collapse
I think you have my issue confused with another . My issue is that everytime I boot it's a clean boot with google account reset/desktop reset. I can't save any settings or download any apps without it getting wiped by a boot. I don't even think my ROM is currently overclocked but I'll look to see if indeed it's hiding in here somewhere.
Let me know if you see anything else that I can try :-(
Thanks though
Edit: Just checked, my system was not overcloccked and set on boot was not checked so this is definetely not the same issue.
jrhsu529 said:
I think you have my issue confused with another . My issue is that everytime I boot it's a clean boot with google account reset/desktop reset. I can't save any settings or download any apps without it getting wiped by a boot. I don't even think my ROM is currently overclocked but I'll look to see if indeed it's hiding in here somewhere.
Let me know if you see anything else that I can try :-(
Thanks though
Edit: Just checked, my system was not overcloccked and set on boot was not checked so this is definetely not the same issue.
Click to expand...
Click to collapse
LOL this is getting even more confused... while you wrote your reply, I edited my post and added this link...
Anyhow, I'm about to surrender on this, so I'm in for wishing you good luck
Bump! Bump Bump.
I know this is a common thing, as I searched before coming to the conclusion that I had to create my own thread about this topic. However, everyone says to re-flash to stock, which is what caused this problem for me. I had a huge error with the phone, and after 2 weeks of flashing, I am able to get it to this stage where it will boot up, but after booting up, the screen turns black, but the bottom buttons light up, and can be pressed, but no action.
I can access recovery and download mode. Odin recognizes my phone. I can charge with phone off (the battery image shows it charging.)
Here is the thread where I discussed my issues if you care to learn more about my issues (it was a dbdata error).
androidforums.com/samsung-galaxy-s/567335-factory-reset-wont-fix-galaxy-s-infinite-boot-mode.html
Anyways, now there is no errors (no red lines during recovery mode). But I have no idea what to do.
No one has a clue? This really sucks, I've spent so much time trying to fix it when all along it can't really be fixed it seems.
Try flashin to Stock i897ucKK4.... http://forum.xda-developers.com/showthread.php?p=18370912
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
Try flashin to Stock i897ucKK4.... http://forum.xda-developers.com/showthread.php?p=18370912
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I've tried that. With that rom it boot loops and gives me a dbdata error.
Edit. Just tried again and after the att screen during boot up it gives me different variations of this screened like a grainy type of image. I snapped a pic below. I tried going into recovery and it gave me the same image on the screen.
Imgur.com/qyo5P.jpg
U need to flash the KK4 WITH the GB Bootloaders.
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
U need to flash the KK4 WITH the GB Bootloaders.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
(I've tried that as well, and I tried it again)
After flashing it booted in recovery, and tried to do the wipes.
Failed to mount /sdcard (I/O error) -- (There's no SD card inside, so that's probably why)
E:copy_dbdata_media: can't mount /sdcard your storage not prepared yet, please use UI menu format and reboot actions.
--Wiping data
Formatting /data...
Formatting/dbdata...
Formatting /cache...
Data wipe failed.
Then I tried a wipe data/factory reset. And this time it said Data wipe completed.
Then when I rebooted it said
Failed to mount /data (invalid argument)
And then it said another error but it was in yellow, so I didn't really catch it.
And it boot loops.
[Thank you for attempting to help me by the way!]
Do a search in the Q & A forum for the dbdata error that you are getting. This has happened before to several persons and i do remember that there were a few threads on this already.
U probably are going to have to flash a stock firmware (that is contained in a .tar file) through regular Odin3 v1.83 (or similar). This Odin is Not a "one click". Make sure the .tar file for the stock contains the dbdata.rfs file and also don't use the pit file. See if that works. --- The i897ucKF1 in the Dev forum would be a firmware that comes to mind that has all u need. Quick search should lead u to that one.
If successful, u should be able to flash up to KK4 afterwards or go to Dev Roms if u want.
4-2ndtwin said:
Do a search in the Q & A forum for the dbdata error that you are getting. This has happened before to several persons and i do remember that there were a few threads on this already.
U probably are going to have to flash a stock firmware (that is contained in a .tar file) through regular Odin3 v1.83 (or similar). This Odin is Not a "one click". Make sure the .tar file for the stock contains the dbdata.rfs file and also don't use the pit file. See if that works. --- The i897ucKF1 in the Dev forum would be a firmware that comes to mind that has all u need. Quick search should lead u to that one.
If successful, u should be able to flash up to KK4 afterwards or go to Dev Roms if u want.
Click to expand...
Click to collapse
I've tried 3 different roms with Odin3 v1.85. (that contain dbdata.rfs in the tar)
Maybe with that rom I'll have better luck. I searched for that rom at samfirmware and downloaded it. I searched in the dev forum, and all I got was an odin one click for that rom, and you said to do the regular version.
I flashed it, and it gave me the same error as before. With the data wipe failed and other errors. Then when it boots, it boot loops only the att logo.
Att logo, darkness for a second. Then repeat.
Also. I've done numerous searches for the words I'm getting, and every one says to flash back to the kk4 stock rom, but that's what causes the problems for me.
Is there anyone that can help at this point?
Is it possible that I have messed up partitions on the internal SD card? I found a way to fix that, but its for the HTC incredible. Any ideas on a captivate version of this thread?
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/#entry56396
albokid2468 said:
Is there anyone that can help at this point?
Is it possible that I have messed up partitions on the internal SD card? I found a way to fix that, but its for the HTC incredible. Any ideas on a captivate version of this thread?
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/#entry56396
Click to expand...
Click to collapse
Have you tried this one yet? http://forum.xda-developers.com/showthread.php?t=731989
This is probably the best restore rom I know of, it will flash eclair bootloaders so you will have to reflash gingerbread bootloaders before you flash any current roms.
If this doesn't do it then it sounds like you may have a bad spot in the memory module itself, possibly a bad transistor in the circuit. You may need some advanced help from a technician, I don't know if any of these jtag guys have advanced diagnostics but it wouldn't hurt to check it out.
As a last resort, you may have to send it in to Samsung.
crt60 said:
Have you tried this one yet? http://forum.xda-developers.com/showthread.php?t=731989
This is probably the best restore rom I know of, it will flash eclair bootloaders so you will have to reflash gingerbread bootloaders before you flash any current roms.
If this doesn't do it then it sounds like you may have a bad spot in the memory module itself, possibly a bad transistor in the circuit. You may need some advanced help from a technician, I don't know if any of these jtag guys have advanced diagnostics but it wouldn't hurt to check it out.
As a last resort, you may have to send it in to Samsung.
Click to expand...
Click to collapse
I've tried that one. That is one of the few where it will give no errors, however it boots up to a black screen. I believe that was the state I was in when I started this thread, with that rom.
Is the memory module or the transistor in the circuit located on the main board of the device. I was thinking of buying a logic board (mother board) and replacing it with a new one.
Although at this point, I got the Galaxy S3 so this phone isn't really a necessity at this point.
albokid2468 said:
I've tried that one. That is one of the few where it will give no errors, however it boots up to a black screen. I believe that was the state I was in when I started this thread, with that rom.
Is the memory module or the transistor in the circuit located on the main board of the device. I was thinking of buying a logic board (mother board) and replacing it with a new one.
Although at this point, I got the Galaxy S3 so this phone isn't really a necessity at this point.
Click to expand...
Click to collapse
Hi bro, have you solved your problem? Eager to hear from you cause I am having the excat same trouble.....
qaler2010 said:
Hi bro, have you solved your problem? Eager to hear from you cause I am having the excat same trouble.....
Click to expand...
Click to collapse
Look here: http://forum.xda-developers.com/showthread.php?p=39614278#post39614278
BWolf56 said:
Look here: http://forum.xda-developers.com/showthread.php?p=39614278#post39614278
Click to expand...
Click to collapse
Thks for your reply
I am not new to captivate, I have already had it for nearly 2 years, and everything including odin ways that used to work now doesn't....
So strange, yesterday it was ok as usual ,but when I got up this morning and it couldn't light up the screen no matter what physical button I hit. So I did flashing but it results in nothing.
Use I897UCJF6-final-OCD-REV0 and my phone can boot up but screen comes black during boot animation
Use 3FileKF1NOBOOT or JF6_secure, my phone just gets stuck on the first boot screen
Use custom recovery, then (E:failed to mount /data (file exists) E:delete_data_files: can't mount /data your storage not prepared yet, please use ui menu for format and reboot actions)
So sad now...I haven't backed up my data and for now it looks like I could never get it back...
qaler2010 said:
Thks for your reply
I am not new to captivate, I have already had it for nearly 2 years, and everything including odin ways that used to work now doesn't....
So strange, yesterday it was ok as usual ,but when I got up this morning and it couldn't light up the screen no matter what physical button I hit. So I did flashing but it results in nothing.
Use I897UCJF6-final-OCD-REV0 and my phone can boot up but screen comes black during boot animation
Use 3FileKF1NOBOOT or JF6_secure, my phone just gets stuck on the first boot screen
Use custom recovery, then (E:failed to mount /data (file exists) E:delete_data_files: can't mount /data your storage not prepared yet, please use ui menu for format and reboot actions)
So sad now...I haven't backed up my data and for now it looks like I could never get it back...
Click to expand...
Click to collapse
Try using Odin KK4 with bootloaders. JF6 is really outdated.
BWolf56 said:
Try using Odin KK4 with bootloaders. JF6 is really outdated.
Click to expand...
Click to collapse
Thanks again for your quick reply.
//Now I have only found one kk4 with bootloader download link in hotfile.com, which is currently not banned in my country...
So would you please be that kind to post another download link like in mediafire, dropbox or googled docs?
But I don't really think it is the problem of being outdated or not, JF6 and that I said above worked fine before...
FYI, I was using Slim 4.2.2 build 2.5 when I got the trouble, maybe there is something special I don't know when downgrading to GB?
Regards!
--------
Found the link:http://www.mediafire.com/?zqpip6uac4n7ov7
qaler2010 said:
Thanks again for your quick reply.
Now I have only found one kk4 with bootloader download link in hotfile.com, which is currently not banned in my country...
So would you please be that kind to post another download link like in mediafire, dropbox or googled docs?
But I don't really think it is the problem of being outdated or not, JF6 and that I said above worked fine before...
FYI, I wasing using Slim 4.2.2 build 2.5 when I got the trouble, maybe there is something special I don't know when downgrading to GB?
Regards!
Click to expand...
Click to collapse
JF6 is Froyo, not GB. Therefor, you're flashing the wrong bootloaders. You need the GB bootloaders, hence why I'm telling you to use KK4.
As for links, the only one I have is: http://hotfile.com/dl/137865417/4bc...S_Bootloaders_Re-partition_Full_Wipe.zip.html - Which is hotfile.com and I can't upload it to my db at work.
BWolf56 said:
JF6 is Froyo, not GB. Therefor, you're flashing the wrong bootloaders. You need the GB bootloaders, hence why I'm telling you to use KK4.
As for links, the only one I have is: http://hotfile.com/dl/137865417/4bc...S_Bootloaders_Re-partition_Full_Wipe.zip.html - Which is hotfile.com and I can't upload it to my db at work.
Click to expand...
Click to collapse
Pretty sure not the issue of bad flash after odining KK4...
I start to believe corrupted, or even worse, dead internal storage causes all the hell....
qaler2010 said:
Pretty sure not the issue of bad flash after odining KK4...
I start to believe corrupted, or even worse, dead internal storage causes all the hell....
Click to expand...
Click to collapse
Sorry but this isn't very clear.. Did you manage to flash Odin KK4 with bootloaders? Did it say complete and reboot the phone? If so, what exactly happened and what exactly did you do?