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?
Related
Samfirmware tweet 3hr ago that the new Froyo JPC firmware have some bootloader problem.
Any clue about this? Does it will permanently damage your phone?
I'm considering Flash this via ODIN or the HK one.
Yeah a lot of people are flashing it because it WILL permanently damage your phone.... just think about it for a sec.
MomijiTMO said:
Yeah a lot of people are flashing it because it WILL permanently damage your phone.... just think about it for a sec.
Click to expand...
Click to collapse
Simple english please.
I don't think anyone more should flash this fw.
It's buggy and crazy.
Also your nv-data.bin is modified.
I don't want my warranty to be un-voidable(by flashing original firmware).
I flashed through KIES and I believe this doesn't damage your phone. It's only thorugh Odin??
No, Kies modifies your /efs data as well. Flashing this firmware in any way shape or form will more or less permanently alter your phone
Zilch25 said:
No, Kies modifies your /efs data as well. Flashing this firmware in any way shape or form will more or less permanently alter your phone
Click to expand...
Click to collapse
Implying restoring a backup of the /efs folder after flashing back an original firmware will not undo any changes made by JPC.
I've restored the stuff in /efs to get my phone back to working order- I still have goofed up build numbers and things like that. It's unfair to imply that this is totally safe for anyone to do, especially those that aren't super comfortable screwing around with protected areas on their phones. It's doubly unfair for people to have the impression that odin is the only unsafe way to install it =P
dutchcow said:
Implying restoring a backup of the /efs folder after flashing back an original firmware will not undo any changes made by JPC.
Click to expand...
Click to collapse
So essentially I'm f*cked then.
Thread Astaire said:
So essentially I'm f*cked then.
Click to expand...
Click to collapse
Not necessarily, it's too soon to tell if it will effect anything... take comfort in the fact that 85% of the SGS XDA community flashed this. Even if there IS an issue people will find ways around it =P
So what exactly is stored in the /efs folder and why is it such a bad thing that JPC has modified it? I've flashed this firmware. Does this mean I can't go back to an older firmware now?
I'm not sure of everything contained in the efs folder, but it contains your nv_data.bin files which contain all the unlock codes and such, so at least for people who have carrier locked phones it causes a mandatory network unlock request. You can get around that by restoring the backup files that the firmware conveniently makes.
Those are really the only show-stopping bugs, the rest of them are a bit more subtle, such as marking your phone as being a korean variant =P Though this problem apparently hasn't cropped up for everyone.
ed10000 said:
So what exactly is stored in the /efs folder and why is it such a bad thing that JPC has modified it? I've flashed this firmware. Does this mean I can't go back to an older firmware now?
Click to expand...
Click to collapse
You can, I flashed back JP3 after having a lot of errors with JPC
Zilch25 said:
I'm not sure of everything contained in the efs folder, but it contains your nv_data.bin files which contain all the unlock codes and such, so at least for people who have carrier locked phones it causes a mandatory network unlock request. You can get around that by restoring the backup files that the firmware conveniently makes.
Those are really the only show-stopping bugs, the rest of them are a bit more subtle, such as marking your phone as being a korean variant =P Though this problem apparently hasn't cropped up for everyone.
Click to expand...
Click to collapse
Ah that's good to hear. Mine is the international version, so it should be fine. I thought the new recovery mode and stuff had problems or something.
EDIT:
iuzar said:
You can, I flashed back JP3 after having a lot of errors with JPC
Click to expand...
Click to collapse
After flashing back to JP3, do you still have the new recovery mode or back to the old one? Can you use Clockwork Recovery now?
ed10000 said:
Ah that's good to hear. Mine is the international version, so it should be fine. I thought the new recovery mode and stuff had problems or something.
Click to expand...
Click to collapse
It does, you've got to flash your stock I9000 kernel before trying to apply update.zip files- since your power button wont work as the selector haha So far that's the only issue I know of with it though
Edit: Make sure you flash back to the JPC kernel before you try to actually boot
Zilch25 said:
It does, you've got to flash your stock I9000 kernel before trying to apply update.zip files- since your power button wont work as the selector haha So far that's the only issue I know of with it though
Click to expand...
Click to collapse
Are you sure? Because right after flashing JPC, I went into recovery mode and did a Factory Reset. The volume up/down buttons worked fine for navigating through the menu and the Home button worked fine for clicking a menu item.
ed10000 said:
Are you sure? Because right after flashing JPC, I went into recovery mode and did a Factory Reset. The volume up/down buttons worked fine for navigating through the menu and the Home button worked fine for clicking a menu item.
Click to expand...
Click to collapse
That might be an issue for me because I'm on a captivate No physical home for me haha. I know for I9000 people rooting though they had to flash the original kernel to get it to work (Stole their trick but substituted the I897 kernel to get it to work for me), but I'm not sure why that is
Samsung have disabled the test keys in all firmwares after JP2. We don't have a real key yet, so gotta flash back to JP2 or before in order to apply an update.zip
Hopefully someone will find a new root-workaround soon.
windy31 said:
Samfirmware tweet 3hr ago that the new Froyo JPC firmware have some bootloader problem.
Any clue about this? Does it will permanently damage your phone?
I'm considering Flash this via ODIN or the HK one.
Click to expand...
Click to collapse
Perhaps SamFirmware had his SGS brick when he try to flash it with odin3.
Sent from my GT-I9000 using XDA App
Thanks for the clarification Ryan
As for samsung firmwares it seems he's just erring on the side of caution, he's got a post in Dutch up there that seems to roughly translate into him trying to avoid throwing up a suspicious firmware (the EFS changes etc) and potentially screwing tons of people, gotta respect that
Yes, especially since Samsung put this firmware up as a "beta" in kies withouth worrying about screwing people...
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 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?
I need the Stock Firmware version G900AUCU2AND3 So that I can flash back to stock. In the thread return to stock it has the previous version G900AUCU1ANCE. I get a error when trying to odin back (SW REV CHECK FAIL : [about]Fused 2 > Binary 1). So I am not sure how its done but need someone who has it do a dump or how ever its done to get it in a way that it can be flashed either by odin or in recovery... Any help will be appreciated... Thanks
i will need this too, i have my phone on at&t next and after a year i can trade it in, but if its custom os and stuff i cant return it, so i will need this too if i want to return to stock so i can upgrade to a new phone next year.
Bump: This is needed very badly. As I imagine many people had to take that bloat ware update. If anyone that has this firm ware has a problem and needs to restore back to stock. They won't be able to use the one that's listed in on this forum as its the older one, and now that there is Root. Its very likely this will happen daily that people will need it. I don't know exactly what soft bricked my phone so it can happen to anyone. My phone was fine until a reboot. Please, please, please. I'm begging everyone that has it. I asked Samsung and they wouldn't help. Next maybe going to AT&T store and having warranty claim done. I don't really want to find the out come of that.
I need this very badly as well. I rooted my phone and then tried to alter my screen density via an app I found on Google Play. It requested root, I granted the permission and then when the phone rebooted it hung on "Samsung Galaxy S5" splash screen and will no go any further. ODIN will not allow me to flash G900AUCU1ANCE firmware since I did the OTA update. If anyone could post up their G900AUCU2AND3, I would appreciate it very much.
kwikrat said:
I need this very badly as well. I rooted my phone and then tried to alter my screen density via an app I found on Google Play. It requested root, I granted the permission and then when the phone rebooted it hung on "Samsung Galaxy S5" splash screen and will no go any further. ODIN will not allow me to flash G900AUCU1ANCE firmware since I did the OTA update. If anyone could post up their G900AUCU2AND3, I would appreciate it very much.
Click to expand...
Click to collapse
I estimate we will get @ least One to two of these per-day until we get the files. Since we now have Root. It may take a bit as At&t version don't seem to have much for devs. Or ones that care to really help.(I'll probably get reamed for this. Sorry for you that help and for your time) I contacted At&t they told me they could not help but I could send my phone in for warranty exchange. Its that or go to BestBuy and they can flash it back. I don't have a Bestbuy Nearby.
Guys, check that post. Shortydoggg found a temporary fix for any soft bricks. It's for extreme cases. My phone is fine (apart from some deleted stock apps) so I'll hold off until i get some more info but if you cant boot at all, his method should come in handy.
http://forum.xda-developers.com/showthread.php?t=2785185&goto=newpost
+1 :highfive:
NotDavid said:
Guys, check that post. Shortydoggg found a temporary fix for any soft bricks. It's for extreme cases. My phone is fine (apart from some deleted stock apps) so I'll hold off until i get some more info but if you cant boot at all, his method should come in handy.
http://forum.xda-developers.com/showthread.php?t=2785185&goto=newpost
Click to expand...
Click to collapse
Thank you. The above link solved my problem. I am back up and running! At first data wasn't working other than wi-fi but I merely had to re-enter my APN that I got from here: http://forum.xda-developers.com/showthread.php?t=2746380 :good:
can you update to G900AUCU2AND3 after flashing this?
dave1977nj said:
can you update to G900AUCU2AND3 after flashing this?
Click to expand...
Click to collapse
YUP, I did the AT&T update check and got it immediately afterwards. I instead of flashing every one separately and rebooting loaded the three files so minus the Bl file. I did not have the problems of having to reload APN this way.
pcidiot said:
YUP, I did the AT&T update check and got it immediately afterwards. I instead of flashing every one separately and rebooting loaded the three files so minus the Bl file. I did not have the problems of having to reload APN this way.
Click to expand...
Click to collapse
Thanks!!! :good:
pcidiot said:
YUP, I did the AT&T update check and got it immediately afterwards. I instead of flashing every one separately and rebooting loaded the three files so minus the Bl file. I did not have the problems of having to reload APN this way.
Click to expand...
Click to collapse
A flash of the CSC file restores the APN after flashing the AP file, or flashing it together with the AP file, but it factory resets the phone. Flashing the AP file only is mostly for those who do not want a factory reset. But, a factory reset along with flashing only the AP file will indeed wipe the APN. I found all of that out through trial and error.
shortydoggg said:
A flash of the CSC file restores the APN after flashing the AP file, or flashing it together with the AP file, but it factory resets the phone. Flashing the AP file only is mostly for those who do not want a factory reset. But, a factory reset along with flashing only the AP file will indeed wipe the APN. I found all of that out through trial and error.
Click to expand...
Click to collapse
Thanks for your trials this will be useful to many.
pcidiot said:
Thanks for your trials this will be useful to many.
Click to expand...
Click to collapse
No problem.
dave1977nj said:
can you update to G900AUCU2AND3 after flashing this?
Click to expand...
Click to collapse
Yes do not root first, flash it then wait a few minutes then do a check for updates it will download the crap update with the yp yellow pages app,
then reboot and root
and take it away !!
pcidiot said:
Bump: This is needed very badly. As I imagine many people had to take that bloat ware update. If anyone that has this firm ware has a problem and needs to restore back to stock. They won't be able to use the one that's listed in on this forum as its the older one, and now that there is Root. Its very likely this will happen daily that people will need it. I don't know exactly what soft bricked my phone so it can happen to anyone. My phone was fine until a reboot. Please, please, please. I'm begging everyone that has it. I asked Samsung and they wouldn't help. Next maybe going to AT&T store and having warranty claim done. I don't really want to find the out come of that.
Click to expand...
Click to collapse
Same troubles here pcidiot!!!! soft bricked and nothing will load onto the phone. ODIN gives me the same kind of error as listed on the starting thread! I can get to recovery mode and Download (ODIN) mode on the phone but nothing wants to flash. Do we dump? Do we Erase Nand? CONFUSING!!! why is it so easy to bunk up a phone!
Achilles5410 said:
Same troubles here pcidiot!!!! soft bricked and nothing will load onto the phone. ODIN gives me the same kind of error as listed on the starting thread! I can get to recovery mode and Download (ODIN) mode on the phone but nothing wants to flash. Do we dump? Do we Erase Nand? CONFUSING!!! why is it so easy to bunk up a phone!
Click to expand...
Click to collapse
There should only be two boxes checked in odin thats f. reset time and auto reboot. Also Make sure you only check and load your firmware in the ap slot in odin. Now flash.
Achilles5410 said:
Same troubles here pcidiot!!!! soft bricked and nothing will load onto the phone. ODIN gives me the same kind of error as listed on the starting thread! I can get to recovery mode and Download (ODIN) mode on the phone but nothing wants to flash. Do we dump? Do we Erase Nand? CONFUSING!!! why is it so easy to bunk up a phone!
Click to expand...
Click to collapse
Are you following this guide?
http://forum.xda-developers.com/showpost.php?p=53454972&postcount=1
shortydoggg said:
Are you following this guide?
http://forum.xda-developers.com/showpost.php?p=53454972&postcount=1
Click to expand...
Click to collapse
Yea I did thank you. Did it today and thanked the poster too.
Want to start over! Need help!
So I want to do whats written out in step 4 of shorttydogs thread but I don't want to mess up or brick my phone. My goal is to start over and go back to stock with bloatware and everything that is available on stock if I were to go AT&T and buy it today. Here is a little background on my phone. My phone is rooted and I do have safestrap (and busybox). I backed up everything on my microSD card. I also have the g900AUCU2AND3 firmware on my phone. In addition, I deleted some but not all AT&T bloatware, which I want back. Lastly, for some reason the "add call button" during my calls is missing and was replaced with a "record" button I think this was because of me playing around with xposed. I deleted xposed framework as well as wanam and tried everything to get the "add call button" back but I couldn't. Thus, I just want to go back to stock to fix all these issues. I just have a few questions before I proceed just to make sure I'm not doing anything wrong.
1) If I flash the AP, CP and CSC files will I achieve 100% stock with bloatware?
2) Will this return my "add call button"?
3) Is it as simple as just using odin 3.09 and flashing the AP, CP, and CSC files?
4) I also understand that this will take me back to G900AUCU1ANCE but will I be able to do an OTA do go to G900AUCU2AND3?
5) Is there anything else I need to know to prevent my phone from bricking!
Sorry for the long post but I am fairly new to this stuff and don't want mess anything up!
It seems that I may have flashed one to many times or something else is playing up. Anywho, I came to check my phone this morning and everything was working fine. Checked the battery status and I thought it was time for a top-up . I decide to do it via USB via my computer and that's when things started to go south. I came back to check my phone and...nothing. I done a hard restart and at first everything seemed fine only to get a continuous boot-loop. I tried to enter TWRP and it hangs on the "teamwin" logo. Then I decided to flash stock via Odin and I still get the same boot-loop. I can still access downloader but that's it.
For reference the version of TWRP I was running was 2.8.6.1 (flashed back to 2.8 Nova version) and the ROM I was running was the latest version of Ressurection Remix by Maclaw.
So, I'm open to any suggestions. Any help would be much appreciated and paid forward.
Thanks for hearing me out.
So going by the lack of feedback I'm basically screwed?
Oh for ****s sake come on! I've had this up for 3 days on this site full of so called enthusiasts and "professionals" and not one response? I'm sorely disappointed.
So there is honestly no one that can help me with this?
Pathetic...
Come on there must be someone that can help me with this, otherwise I'll have to risk buying a broken one for parts.
Haven't done any custom stuff in a while but the boot loop sounds familiar, have you wiped the dalvik cache in the advanced menu also have you tried a factory reset?
---------- Post added at 12:35 PM ---------- Previous post was at 12:30 PM ----------
Use the Volume keys in order to navigate through the recovery menu.
Select “advanced” and choose “wipe dalvik cache”.
Return to main menu.
Then select “wipe data factory reset”.
Return and this time choose “wipe cache partition”.
Return and select “reboot system now”.
Your handset should start in Android OS now.
Grumpy Cat said:
It seems that I may have flashed one to many times or something else is playing up. Anywho, I came to check my phone this morning and everything was working fine. Checked the battery status and I thought it was time for a top-up . I decide to do it via USB via my computer and that's when things started to go south. I came back to check my phone and...nothing. I done a hard restart and at first everything seemed fine only to get a continuous boot-loop. I tried to enter TWRP and it hangs on the "teamwin" logo. Then I decided to flash stock via Odin and I still get the same boot-loop. I can still access downloader but that's it.
For reference the version of TWRP I was running was 2.8.6.1 (flashed back to 2.8 Nova version) and the ROM I was running was the latest version of Ressurection Remix by Maclaw.
So, I'm open to any suggestions. Any help would be much appreciated and paid forward.
Thanks for hearing me out.
Click to expand...
Click to collapse
TheMadTurnip said:
Haven't done any custom stuff in a while but the boot loop sounds familiar, have you wiped the dalvik cache in the advanced menu also have you tried a factory reset?
---------- Post added at 12:35 PM ---------- Previous post was at 12:30 PM ----------
Use the Volume keys in order to navigate through the recovery menu.
Select “advanced” and choose “wipe dalvik cache”.
Return to main menu.
Then select “wipe data factory reset”.
Return and this time choose “wipe cache partition”.
Return and select “reboot system now”.
Your handset should start in Android OS now.
Click to expand...
Click to collapse
Thanks for the feedback but as I have already stated I can't access any recovery only Odin, and desktop Odin won't allow me to re-partition only write. Still, whether it be stock or a custom ROM it is the same result: bootloop and recovery freezes on splash screen.
So any other takers? Yes? No?
Why even have a "help & troubleshooting" section if, well, I don't know, no one helps!!!
Dude you're puerile attitude is baffling, I understand you desperately want help, but do you really think you'll get it if you keep throwing toys out of your pram?
The problem you've described suggests that you're phone is 'fixable' however, it may take a few different methods to restore it. Ok, so you cannot access recovery mode, therefore you're unable to clear your phone like TheMadTurnip suggested, and you're also unable to access any backup you might have made. The downloader works so I can only recommend you try to investigate what's going wrong when you flash via Odin, does the flash show as pass or fail? Have you tried flashing using a different cable or computer, heck have you even tried using another version of Odin? Is Kies installed on your computer, if so then remove it. Have you flashed using a PIT file as well as the stock firmware? Elaborate on your situation so tailored advice can be given to you.
Kind Regards,
Pinda
Pinda007 said:
Dude you're puerile attitude is baffling, I understand you desperately want help, but do you really think you'll get it if you keep throwing toys out of your pram?
Click to expand...
Click to collapse
In light of how active this section still is I think a week is more than enough time to expect a response, I was even quite polite in my OP. Even a simple "no I can't help but maybe try this" would have sufficed. But I'll take it under advisement...
Pinda007 said:
does the flash show as pass or fail?
Click to expand...
Click to collapse
It shows a pass, won't allow me to re-partition though.
Pinda007 said:
Have you tried flashing using a different cable or computer, heck have you even tried using another version of Odin?
Click to expand...
Click to collapse
I have tried flashing using the original cable the phone came with; so I have tried 2. I even tried other USB ports. And yes I have tried another version of Odin.
Flashing doesn't seem to be a problem at the moment, just everything else.
Pinda007 said:
Is Kies installed on your computer, if so then remove it.
Click to expand...
Click to collapse
It is installed along with the Samsung USB driver. Having it installed hasn't caused a problem. I'll uninstall it if you think that will help.
Pinda007 said:
Have you flashed using a PIT file as well as the stock firmware? Elaborate on your situation so tailored advice can be given to you.
Click to expand...
Click to collapse
A pit file? And yes, as I have already mentioned I have installed the stock firmware.
Grumpy Cat said:
In light of how active this section still is I think a week is more than enough time to expect a response, I was even quite polite in my OP. Even a simple "no I can't help but maybe try this" would have sufficed. But I'll take it under advisement...
It shows a pass, won't allow me to re-partition though.
I have tried flashing using the original cable the phone came with; so I have tried 2. I even tried other USB ports. And yes I have tried another version of Odin.
Flashing doesn't seem to be a problem at the moment, just everything else.
It is installed along with the Samsung USB driver. Having it installed hasn't caused a problem. I'll uninstall it if you think that will help.
A pit file? And yes, as I have already mentioned I have installed the stock firmware.
Click to expand...
Click to collapse
As it stands it's about ruling things out to pinpoint what's going wrong, I'm no expert, merely a trial and error kind of guy. Anyway, yes, I would suggest uninstalling Kies and try the flash again, although if Odin is flashing successfully then this might not be the issue, but it's worth a shot. When I resolved my bootloop, using a PIT file was one of the things I did, so perhaps that's something you might want to look into. Also, make sure your firmware downloads are clean, basically make sure they download smoothly and aren't disturbed by a network disconnection etc. Could you post links to where you downloaded your stock firmware?
Pinda007 said:
As it stands it's about ruling things out to pinpoint what's going wrong, I'm no expert, merely a trial and error kind of guy. Anyway, yes, I would suggest uninstalling Kies and try the flash again, although if Odin is flashing successfully then this might not be the issue, but it's worth a shot. When I resolved my bootloop using a PIT file was one of the things I did, so perhaps that's something you might want to look into. Also, make sure your firmware downloads are clean, basically make sure they download smoothly and aren't disturbed by a network disconnection etc. Could you post links to where you downloaded your stock firmware?
Click to expand...
Click to collapse
I got my firmware from sammobile.com, right down to my network provider. I've flashed it before and never had any problems. I'm just trying to figure out why my phone self-bricked. I was on latest "Resurrection Remix" when it happened.
Where can I find this "PIT" file and how do I use it? I notice an option in Odin so I can probably figure that part out. At the moment my knowledge is limited to rooting, flashing custom recoveries and ROMs. Sorry.
Grumpy Cat said:
I got my firmware from sammobile.com, right down to my network provider. I've flashed it before and never had any problems. I'm just trying to figure out why my phone self-bricked. I was on latest "Resurrection Remix" when it happened.
Where can I find this "PIT" file and how do I use it? I notice an option in Odin so I can probably figure that part out. At the moment my knowledge is limited to rooting, flashing custom recoveries and ROMs. Sorry.
Click to expand...
Click to collapse
Ahh ok, yes my knowledge is also limited in that respect. I guess it's all about learning and helping each other out, which is where I guess it can be frustrating when there's a lack of 'available' support in these forums. Nevertheless, I must stop droning on, I used a PIT file for my S variant after noticing numerous users mentioning the significance of it when using Odin to flash. Here's an interesting thread to find out more (http://forum.xda-developers.com/showthread.php?t=999097). It's a sort of map if you like, which inadvertently tells the software where everything has to go on the handset, that's my noob interpretation of it anyway. I found the relevant PIT file for my variant on a XDA thread, so it might be worth scurrying through archived threads to see if you can find one for your phone, make sure there's legit feedback for it though. You just flash it with the firmware like you normally would.
Remember, I'm no expert, I'm just going by how I fixed my phone over the weekend. I apologise my attempts to help are meager, I'm still relatively new to all this, just like you.
Pinda007 said:
Ahh ok, yes my knowledge is also limited in that respect. I guess it's all about learning and helping each other out, which is where I guess it can be frustrating when there's a lack of 'available' support in these forums. Nevertheless, I must stop droning on, I used a PIT file for my S variant after noticing numerous users mentioning the significance of it when using Odin to flash. Here's an interesting thread to find out more (http://forum.xda-developers.com/showthread.php?t=999097). It's a sort of map if you like, which inadvertently tells the software where everything has to go on the handset, that's my noob interpretation of it anyway. I found the relevant PIT file for my variant on a XDA thread, so it might be worth scurrying through archived threads to see if you can find one for your phone, make sure there's legit feedback for it though. You just flash it with the firmware like you normally would.
Remember, I'm no expert, I'm just going by how I fixed my phone over the weekend. I apologise my attempts to help are meager, I'm still relatively new to all this, just like you.
Click to expand...
Click to collapse
I tried installing stock firmware with the PIT file I found here and still get the same result. I might be screwed.
Grumpy Cat said:
I tried installing stock firmware with the PIT file I found here and still get the same result. I might be screwed.
Click to expand...
Click to collapse
I think that's the exact file that worked for me
I don't know what else to suggest at the moment, the fact that you cannot get into recovery makes it that much harder.
I'll come back to you if something comes to mind.
EDIT- Have you tried re flashing a custom recovery to overwrite your current one? If you can somehow get into recovery you could trying clearing your phone of cache and installing a ROM zip-folder. Also, have you got another battery you can try in your handset? I cannot help you with the Odin method no because you've pretty much exhausted all the possible solutions that I know of, perhaps screenshot the Odin log and post it on here for more info.
My s3 mini also got same problem.any solution found