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?
Related
Any ideas?
I have been experimenting with upgrading and down-grading my tab, it now seems that I can't flash any ROM that contains a hidden.rfs, the flash will just stop near the end of flashing the hidden.rfs and never continue, then I have to go through recovery processes to get a working tab back.
I managed to get my Tab back to CPW standard UK JJ3 by dumping the ROM from my other Tab and writing it, I then tried to update with Kies, which also hung at what seems to be exactly the same place.
I have tried repartitioning several times with the p1_add_hidden.pit but it just doesn't seem to work.
Any ideas? Can I check the size of the hidden partition see if that' the problem? Then modify the hidden.rfs to make it smaller so it fits?
Nobody at all got any feedback on this?
Anyone had any luck with this? I'm guessing it's a partitioning issue but it'd be good to know.
alias_neo said:
Nobody at all got any feedback on this?
Click to expand...
Click to collapse
It sounds like you're currently partitioned without the hidden partition. I would think flashing a full ROM like JJ4 with the P1_add_hidden.pit in Odin would be the fix.
After thats up and running, use my JMC upgrade package to safely upgrade.
rotohammer said:
...use my JMC upgrade package to safely upgrade.
Click to expand...
Click to collapse
Time to upgrade to JMD me thinks
rotohammer said:
It sounds like you're currently partitioned without the hidden partition. I would think flashing a full ROM like JJ4 with the P1_add_hidden.pit in Odin would be the fix.
After thats up and running, use my JMC upgrade package to safely upgrade.
Click to expand...
Click to collapse
Roto i wanna ask you something. You say "safely" upgrade why ? Because on your FW's you remove the boot.bin and the SBL.bin ? So that a user wont be able to flash them and something go wrong ?
As far as i know my tab ( A euro one ), is factory unlocked and i will have no problem whatsoever in upgrading the bootloader and the baseband.
Isnt that right ?
sedde said:
Roto i wanna ask you something. You say "safely" upgrade why ? Because on your FW's you remove the boot.bin and the SBL.bin ? So that a user wont be able to flash them and something go wrong ?
As far as i know my tab ( A euro one ), is factory unlocked and i will have no problem whatsoever in upgrading the bootloader and the baseband.
Isnt that right ?
Click to expand...
Click to collapse
Unlocking is unrelated. I say safely because flashing a bootloader is the only thing that makes me squirm. If it fails your device is toast. I never want to give anyone firmware that has the potential to destroy their device. I'd feel bad
daniel.weck said:
Time to upgrade to JMD me thinks
Click to expand...
Click to collapse
Me too : ) maybe tonight after my guests leave.
rotohammer said:
Unlocking is unrelated. I say safely because flashing a bootloader is the only thing that makes me squirm. If it fails your device is toast. I never want to give anyone firmware that has the potential to destroy their device. I'd feel bad
Click to expand...
Click to collapse
And you are so right in removing them...
The leaks from Samsung's servers of JM6/JMA/JMC/JMD flash a signed recovery, after flashing it is impossible to flash unsigned sbl, boot, and zImage. No more downgrade (and possibly upgrade).
rotohammer said:
It sounds like you're currently partitioned without the hidden partition. I would think flashing a full ROM like JJ4 with the P1_add_hidden.pit in Odin would be the fix.
After thats up and running, use my JMC upgrade package to safely upgrade.
Click to expand...
Click to collapse
I thought my original post covered this? I can't flash _any_ ROM that uses the hidden partition. I have tried repartitioning a dozen times wit hthe p1_add_hidden.pit, that goes through fine, but NO ROM, full or otherwise, down or up from my current one will successfully complete flashing the "hidden" partition.
alias_neo said:
I thought my original post covered this? I can't flash _any_ ROM that uses the hidden partition.
Click to expand...
Click to collapse
You never mentioned JJ4 or Odin specifically, hence my post. Unless you spell out exactly which firmwares you tried and which software you used to flash with, how can anyone offer assistance?
If you've tried ALL firmware and All flashing software, that leaves only your computer or Tab at fault.
rotohammer said:
You never mentioned JJ4 or Odin specifically, hence my post. Unless you spell out exactly which firmwares you tried and which software you used to flash with, how can anyone offer assistance?
If you've tried ALL firmware and All flashing software, that leaves only your computer or Tab at fault.
Click to expand...
Click to collapse
Im not really worried about my Tab, i just think its a cause for concern that somehow iv stumbled on this problem. If its just the flash in my tab thats damaged its not a problem.
I have tried every firmware available on samfirmware as well as ripping the firmware from an identical tab i have.
Neither Heimdall, Kies nor Odin (either version) would get past flashing hidden and they all stop at about the same point. I have tried flashing various firmware without hidden with no problems. If i then repartition it will flash about 80% of the hidden then just stops.
Problem isnt my pc, i have tried several machines and virtual machines.
I think its a curious problem that would be good to find the cause of.
alias_neo said:
I think its a curious problem that would be good to find the cause of.
Click to expand...
Click to collapse
I agree. Do you have time to jump on irc #ModADroid-Galaxy-Tablet?
rotohammer said:
I agree. Do you have time to jump on irc #ModADroid-Galaxy-Tablet?
Click to expand...
Click to collapse
Cant at the mo, just off out to visit family, xmas and all...
Ill get back to you later tonight?
alias_neo said:
Cant at the mo, just off out to visit family, xmas and all...
Ill get back to you later tonight?
Click to expand...
Click to collapse
Sure, we're about to get a blizzard on the east coast of the US, so I may be cancelling my family visiting plans. Just ping me later.
rotohammer said:
Sure, we're about to get a blizzard on the east coast of the US, so I may be cancelling my family visiting plans. Just ping me later.
Click to expand...
Click to collapse
I'm around and will hop on the channel now. Don't have too long but maybe we can look into this a bit.
I just noticed what has veen going on with tje secured boot loaders etc. I will check mine with the script once I get home from my trip tomorrow to see if any info froem my tab is relevent to fixing the problem. I noticed a mention of creating jigs, im not sure what hardware is required but I have a couple of usb-rs232 connectors on order for an unrelated project so if it requires the same hardware I can put a spare one to use and build a jtag/jig cable for the tab and see if I can help the cause.
Sent from my GT-P1000 using XDA App
Question for rotohammer
Once upon a time I bricked my Verizon Galaxy Tab trying to flash a custom ROM, the only way I could bring it back was by using Odin and flashing the hidden pit. Now every time I install the original verizon rom my tab is extremely, extremely slow. I have been trying to reformat and wipe clean to start over, but I haven't had any luck.
Any suggestions on how to: either flash the right pit on it or remove the hidden partition? Anything I can do to bring my tab to full speed. I have also tried the overclocked rom with voodoo5, and at this point anything I put there is extremely slow. The only way I can get it to operate normally (Kind of) is to flash the Honeycomb Alpha rom, then restore to a day when it was working fine, however this breaks my auto rotate sensor.
That is how I use it now a days, but it sucks that I cannot use it on landscape mode.
Any help will be greatly appreciated.
Follow up from my previous question to rotohammer
By the way, just in case you were wondering, the rom I flashed to unbrick it was a GSM ROM, that was the only way to make it past the Samsung logo.
So, my theory is that I have problems with it because now I am trying to flash CDMA roms to a GSM partition/files system? Excuse me if my post does not make much sense or I am using the wrong terminology, I am extremely new a this. I just know enough to get myself in trouble.
Thank you again for any help.
I've encountered the same problem as the original poster. SGT with CPW CSC causes problems with the hidden.rfs when trying to flash ROMs. Does appear to be a size issue with the hidden partition - I wonder whether this has been sized incorrectly when it was originally flashed as re-partitioning doesn't help. I'm currently on a XEU ROM so I guess I'll find out when Gingerbread is officially released whether I can flash that or not. If not, I think it'll need to the internal SD card repartitioning.
Anyone got any tips on how to do this?
Firstly guys, I'd like to apologise for this being my first post. I'm usually a regular over at the SGS forums but am yet to have had a response. I'm ****ting bricks currently, so here goes...
ARGH wtf. Just as I thought I had the perfect phone, it messes up! Darky's ROM went mad on me. Kept rebooting the phone. Kept vibrating throughout. No idea what's wrong with it. Tried to do a wipe install of the ROM again, but the bloody thing has disappeared from the SD card! What am I going to do now? Reflash back to my previous firmware and start all over again, AGAIN? Ffs.
Just for the record, I'm basically stuck in recovery mode. It's either that or staring at the Nexus S logo as it attempts to boot, over and over and over... I'm so angry right now! I didn't do anything to the phone for this to happen! Bad luck or what. Really hope there is a solution to this. I don't suppose there's anyway of accessing the device's SD memory when in recovery mode? I just need to plant the update.zip on the SD card again so I can reflash it!
Click to expand...
Click to collapse
I would massively massively appreciate any help you guys could give me. I've had nothing but bad luck with my Galaxy S
[EDIT] Oh and by the way, I still have full access to my three-button combo modes. Clockwork recovery console and Download mode still fully accessible.
Hi
I'm also new here and got my SGS yesterday, but i had a HTC Desire before.
If you can get in to Clockworkmod recovery you should be able to push the file via adb to the sdcard. That was possible on the Desire at least.
vippe said:
Hi
I'm also new here and got my SGS yesterday, but i had a HTC Desire before.
If you can get in to Clockworkmod recovery you should be able to push the file via adb to the sdcard. That was possible on the Desire at least.
Click to expand...
Click to collapse
Hey there, thanks for your response! What may I ask is 'adb'?
Android development....something
Just flash back to eclair again. The time it took you to get an answer on a forum is longer tham the time it takes to flash.
Sent from my GT-I9000 using XDA App
I'm guessing you screwed up without diabling lagfixes or something, just install JM8 with repartition enabled and using pit 512 file again then install clockwork update.zip then install whatever rom (but in this case darkys). It starts to become habbit when testing new roms to do all of them steps, The first time something happens you **** bricks but soon relize the SGS is alot more brick poof then you think (unless you are one of the poor souls with broken recovery modes)
But anyways, calm the hell down. Everything is fine.
ickyboo said:
I'm guessing you screwed up without diabling lagfixes or something, just install JM8 with repartition enabled and using pit 512 file again then install clockwork update.zip then install whatever rom (but in this case darkys). It starts to become habbit when testing new roms to do all of them steps, The first time something happens you **** bricks but soon relize the SGS is alot more brick poof then you think (unless you are one of the poor souls with broken recovery modes)
But anyways, calm the hell down. Everything is fine.
Click to expand...
Click to collapse
I've absolutely no idea what files to flash... I'm a bit of a noob when it comes to flashing with the SGS. Quite embarrassing actually because I used to flash my old Omnia HD with no problems whatsoever! Don't suppose you could link to files.
Don't worry, your Galaxy is not bricked. Please see here how to reflash from a PC.
I've downloaded all necessary files... I've got a CODE a MODEM the 512.pit but no CSC? Am I okay to flash with no CSC?
Eddzz!! said:
I've downloaded all necessary files... I've got a CODE a MODEM the 512.pit but no CSC? Am I okay to flash with no CSC?
Click to expand...
Click to collapse
CSC contains all carrier-related (like APNs) data.
Depending on the type of packaging some CODE files are complete with CSC.
In any case, you can flash a CSC (like ITV or XEU) even later.
Before to go with flash, I'd like to advise you to backup /efs folder on your SD and/or your PC. This is the only folder with information (like your IMEI configuration) that cannot be recovered in case of a total data loss.
After a long gruelling process of flashing and reflashing, I'm back on Darky's ROM. Problem though - App market is messed up. I can't download anything from the Market and it's also the 'old' Market theme... I think has something to do with the fact that I've flashed from Eclair straight to Darky's? (Which I was advised to do...) - How can I get my Market working again?! Everything is fine besides that!
[EDIT] I now have the new market interface but still cannot download a thing!
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.
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.
I had battery issues with my Note GT-N7000. I purchased the original battery from samsung service center. Phone did restarted several times due to low battery. After one such incident it was not accepting my correct pattern. After some time it just stopped getting start up.
Then i tried to enter into recovery mode. It got stucked at android green logo, wheel spinning every single time.
But download mode is still working. I tried to re-flash it with stock firmware as i was running it before this problem occurred (stock with root).
I followed flashing instructions extremely carefully and as they instruct. When i put my phone into download mode, it got successfully recognized by my computer, But while flashing it got stucks at flashing factoryfs.img, ""NAND write start"" and followed by ""complete write operation failed"".
I did changed my original usb cable to another original cable. My antivirus and firewall are turned off permanently. I did tried it on another computer but same result. Downloaded my firmware from sammobile twice. Did tried different Odin versions from 1.83 to 3.07. But no luck at all. I am attaching my screenshots so that you can have a look.
Please help me out in any way you can. Any links or help will be highly appreciated from the bottom of my heart. Thanks in advance for your reply.
Did you have a ROM on it that required you to change the PIT file? If there is a different partition scheme that could cause an issue. Also try unchecking f reset time.
Sent from my SM-G900T using XDA Premium HD app
zombieplanalpha said:
Did you have a ROM on it that required you to change the PIT file? If there is a different partition scheme that could cause an issue. Also try unchecking f reset time.
Sent from my SM-G900T using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for your quick response. I do not have a ROM that require me to change PIT information. I was on pure stock with root before this issue came up. I did unchecked reset time but same error came up.
Different partition scheme...? As far as i know, i didnt do anything to my partitions.
You bricked your device. Search for threads with "factoryfs.img" and you'll find answers (repartition, replace MB or follow hg42's thread).
And you'll might find your post from Nov 2012 when you had a problem like this before but "solved" it.
ThaiDai said:
You bricked your device. Search for threads with "factoryfs.img" and you'll find answers (repartition, replace MB or follow hg42's thread).
And you'll might find your post from Nov 2012 when you had a problem like this before but "solved" it.
Click to expand...
Click to collapse
So is there any possibility of restoring the data?
Negative. Custom recovery and frequent backups along with an app like titanium backup would have been good to have before this happened
Sent from my SM-G900T using XDA Premium HD app
zombieplanalpha said:
Negative. Custom recovery and frequent backups along with an app like titanium backup would have been good to have before this happened
Sent from my SM-G900T using XDA Premium HD app
Click to expand...
Click to collapse
I do have the backup but its more than 2 months old...but i cannot go into stock recovery....i should have installed cutom recovery. Any links to follow or any proper guides to come out from it?
http://forum.xda-developers.com/showthread.php?t=1667886
ThaiDai said:
http://forum.xda-developers.com/showthread.php?t=1667886
Click to expand...
Click to collapse
As per the article and since i cannot enter into recovery mode, i tried all the PIT files provided with stock rom. But nothing has worked. Every time Odin is failing. I am attaching the screenshot of the same. I did tried to flash speedmod kernel but didnt got success message from Odin. Kindly help me.
i have used custom PIT files due to which my binary counter has increased(i dont care as its out of warranty). My phone shows a yellow warning sign on bootup and now it just dont even start the recovery mode and shows that yellow warning sign when i try to enter recovery.
Download mode is still working but i am unable to perform any write operation. NAND operation is failing everytime. When i used PIT files, it says re-partition operation failed. I can only try things mentioned in the above posts only when i can enter recovery.
Will someone be kind enough to help me out on this one as i really need urgent help? Please help me out guys.
I think you didn't read hg42's thread and didn't follow his big bold red warnings.
Brute Force experiments with different pit files made it only more difficult or impossible.
In his thread there is a link to another thread related to the problem
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
forest describes a manual method to check for errors including a repair option by scanning the device with e2fsck in chapter 4.2.
I remember some users who solved the brick with factorfs.img with this method (at least I remember one where nokiamode gave that hint).
Try this and follow forest`s instructions carefully.
You tried flashing PhilZ-cwm6-DDLSC kernel tar file fusing odin?
ThaiDai said:
I think you didn't read hg42's thread and didn't follow his big bold red warnings.
Brute Force experiments with different pit files made it only more difficult or impossible.
In his thread there is a link to another thread related to the problem
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
forest describes a manual method to check for errors including a repair option by scanning the device with e2fsck in chapter 4.2.
I remember some users who solved the brick with factorfs.img with this method (at least I remember one where nokiamode gave that hint).
Try this and follow forest`s instructions carefully.
Click to expand...
Click to collapse
Thanks for replying. I did read that article carefully but all steps and troubleshooting is valid only and only when your phone's recovery mode is working. In my phone, only download mode is working. So all those steps are not applicable to me.
However i went for case B where he has described solution if we are unable to access recovery mode and suggested to use blind method to use custom pit files. I followed him but it didn't worked out for me. None of the pit files worked for me and i just ended up raising my binary counter to 2 now.
I am not receiving any replies from people(Only 2 or 3 kind people like you have replied, i appreciate it). I am not getting support. Its reallly sad just because my phone is little old now.
Even if i didn't find any solution and my phone becomes a brick( i guess it has become by now) it is still fine for me But the most sad thing is no one cares to reply on a community which was built to help each others. I am continuosly searching for solutions now. Lets see how far i can go. Thanks for your time. Do let me know if you come across any thing or i am ready to try any solution/troubleshooting steps.
nokiamodeln91 said:
You tried flashing PhilZ-cwm6-DDLSC kernel tar file fusing odin?
Click to expand...
Click to collapse
I have downloaded Philz-cwm6-DDLSC tar file....I'll be flashing it soon and'll let you know for sure
vinay28761 said:
I have downloaded Philz-cwm6-DDLSC tar file....I'll be flashing it soon and'll let you know for sure
Click to expand...
Click to collapse
No progress...it just got failed again.....I will get the motherboard replaced by samsung...It'll cost me 170+ USD, original motherboard and a new original battery as well.
vinay28761 said:
No progress...it just got failed again.....I will get the motherboard replaced by samsung...It'll cost me 170+ USD, original motherboard and a new original battery as well.
Click to expand...
Click to collapse
Have you tried another pc, and genuine USB cable by Samsung?
nokiamodeln91 said:
Have you tried another pc, and genuine USB cable by Samsung?
Click to expand...
Click to collapse
Yes i tried on different pc, different cables(all are genuine)