Related
I modified this post to recap the whole story. You can find the timeline development from the second post on.
My TAB is now bricked, it does not give any sign of life even after letting it charging for hours.
Not Odin or heimdall would recognize it to I cannot flash anything.
Samsung Mexico (where I am now) told me they cannot fix it because the mexican version has a different hardware configuration.
I also called Samsung US and they told me they cannot accept it, I should go back to china and repair it there (??).
I decided not to waste my time anymore on this, as it become anti economic.
(if anyone is interested in buying it as spare-parts, please let me know!)
what happened, for reference:
Chinese unicom GST p1000, previously flashed (and running) with success roto-JME.
I tried to flash JQ1 with bootloaders but ODIN failed at hidden.rfs. Since then I never manage to boot the tab anymore.
I then couldnt flash any ROM containing either hidden.rfs or movinand.mst, it would always FAIL. In order to PASS I had to remove these two from the flash, but TAB will hang at Samsung logo during boot (not sure if the reason for not booting is because of the missing files, or these 2 problems have the same cause, but are not related with eachother).
I tried a huge number of different ROMs, all give same results (even JME will fail at movinand.mst now)
in case you are wondering I already tried different computers, win and ubuntu, Odin and heimdall, changed USB cables, always the same problem.
Given the above situation (base ROM not complete and not booting + /data unmountable) I managed anyway to install Overcome and AF974, but they both hung at GALAXY TAB boot screen (the very first one) and keep rebooting every few seconds. (This is different from when it hangs at samsung logo - see above)
After this recovery started to report partition errors:
I cannot mount /DATA in either CWM or ADB , it says:
mounting /dev/block/mmcblk0p2 on /data failed: No such file or directory
indeed /dev/block/mmcblk0p2 does not exist.
I tried the flashing routine again, and new different partition errors came up
now the internal sd-card was not mountable anymore, instead it would read ext-sd as internal
I tried the flashing routine again, and it bricked completely to death
What I DIND'T do (learned about it too late!) prior to flash JQ1 was to neither ROOT or patch bootloaders before flashing, but I belive I should be ok:
I flashed JME successfully in the past and should be pre-rooted.
I also have reasons to think my bootloaders are not protected as:
I tried chainfire's SGTBootloaderCheck-1.0,it says I am clean.
I can flash CF-root, which is supposed to fail on protected bootloader.
I was brave and stupid enough to format /boot from recovery. Tab would not boot but I could flash it back from Odin with no problems (still, flashed an incomplete ROM without hidden.rfs)
i also tried other ROMS, but have the same problem with all of them
I tried chainfire's SGTBootloaderCheck-1.0 while on recovery mode, but it says I am clean
I cannot get out of this brick, can anyone point me in the right direction?
I'm not the one with the answers, but I casually saw these two posts hours ago:
How to unbrick tabs:
http://forum.xda-developers.com/show....php?t=1133590
This unlocks bootloaders so your SamFirmware.com rom won't brick you:
http://forum.xda-developers.com/showthread.php?t=888071
thanks but I have already seen and tried all of these.
The most commune solution to a soft brick in the forum is: "flash again".
but in my case it seems I just cannot flash anything.
Perhaps what I am looking for is a method/checklist to diagnostic the source of my problem?
or should I just keep trying flashing every possible rom? (i already tried at least 9)
2 cents
Hi,
First of all, get AF974's ROM and also his kernel and the modem for your region. Put these zips on your external SD.
Get into recovery : mount every single thing you can mount, then format every thing (use ext4 if possible). Without leaving recovery, flash the kernel , then the ROM and finally the modem. Reboot and wait ...
thank you but I'd need more directions..
dirlan2001 said:
First of all, get AF974's ROM and also his kernel and the modem for your region. Put these zips on your external SD.
Get into recovery : mount every single thing you can mount, then format every thing (use ext4 if possible). Without leaving recovery, flash the kernel , then the ROM and finally the modem. Reboot and wait ...
Click to expand...
Click to collapse
Thank you. this is a new approach and definitively worth trying it.
I would need more directions thou, as I only can flash roms using odin.
Are you saying I can flash this ROM from the recovery mode, I don't need Odin?
I am a bit confusing about the process: you are saying: 1) mount everything 2) format 3) flash.
1. What do you mean my 'mounting'?
when I go to my recovery mode i can see the option 'apply update from sdcard'. Is this what you mean by mounting?
2. Then format everything. what and how? you mean the SDcard? I am not aware of anything else I could be formatting. Please precise.
3. then flash everything.
how is flash different by Mounting, in this case? havent I already 'applyed' these files in step 1?
I am sorry if all these questions sounds idiot, I probably miss a lot of basic knowledge. I swear I did my homework, I spent DAYS reading all the forums. It's just hard to catch up everything from stratch without help.
thank you!!
i think i got it
I think I got why I dindt understand your previous post:
I dont have thoese options in Recovery.
The only things I see are:
Reboot, apply update from sdcard, wipe data, wipe cache.
This phone was originally working with Roto-JME and then bricked while flashing JQ1. I am not sure which version does this recovery belongs to.
Can I still do anything with this version of recovery?
jacopo3001 said:
I think I got why I dindt understand your previous post:
I dont have thoese options in Recovery.
The only things I see are:
Reboot, apply update from sdcard, wipe data, wipe cache.
This phone was originally working with Roto-JME and then bricked while flashing JQ1. I am not sure which version does this recovery belongs to.
Can I still do anything with this version of recovery?
Click to expand...
Click to collapse
Hi,
Seems you got a old CWM (probably 3.x) that came with Roto"s ROM. Anyway, if you got the files I previously mentioned, make a copy of the kernel.zip and rename it into update.zip, put that 'new' update zip on your SD (eventually replacing the old one) and fire up CWM, running the 'update from SD'.
After reboot you should have a newer CWM that has more options to it. Note that the reboot may take some time... Then you can use the 'mount' to get all partitions mounted r/w... Then you run the kernel.zip and the ROM.zip from 'install zip from SD | go to external SD | choose the kernel.zip // redo the same for the ROM.zip without rebooting in between'
jacopo3001 said:
I think I got why I dindt understand your previous post:
I dont have thoese options in Recovery.
The only things I see are:
Reboot, apply update from sdcard, wipe data, wipe cache.
This phone was originally working with Roto-JME and then bricked while flashing JQ1. I am not sure which version does this recovery belongs to.
Can I still do anything with this version of recovery?
Click to expand...
Click to collapse
This sounds like you are in stock recovery and need cwm installed again.
________________________
Sent from my DROIDX X
dirlan2001 said:
Seems you got a old CWM (probably 3.x) that came with Roto"s ROM. Anyway, if you got the files I previously mentioned, make a copy of the kernel.zip and rename it into update.zip, put that 'new' update zip on your SD (eventually replacing the old one) and fire up CWM, running the 'update from SD'.
Click to expand...
Click to collapse
thank you I will try later tonight.
yesterday I was quite desperate and sent the tab in to the local samsung assistance center, and they just called me they couldnt fix it!
Tonight as I get it back I will try this approach and will let you know.
thanks
jacopo3001 said:
thank you I will try later tonight.
yesterday I was quite desperate and sent the tab in to the local samsung assistance center, and they just called me they couldnt fix it!
Tonight as I get it back I will try this approach and will let you know.
thanks
Click to expand...
Click to collapse
On second thought, it may even be better to install the Overcome kernel first. That has the most recent version of CWM build in, and it makes your device ext4 instead of the old RFS. After that you easily can flash AF974's combo via CWM, whitout need to rename/copy anything. The link provides the guide to the mirror of OC, as their website isn't working anymore...
dirlan2001 said:
it may even be better to install the Overcome kernel
Click to expand...
Click to collapse
I have tried to flash GB-Stock-Safe-v5 (as for Overcome's docs) with Odin but it fails, just like all the other flashes I tried.
Btw, I just discovered that on the back of my TAB (chinese unicom) is written WCDMA. As I always used GSM cards with it I always assumed it was a GSM version, but now I am getting the doubt.
can you confirm I am on GSM version?
the full specs written on the back case are:
WCDMA无线数据终端 (wireless data terminal)
Model：GT-P1000
CMIIT 10 2010CP4950
jacopo3001 said:
I have tried to flash Overcome with Odin before but it fails, just like all the other flashes I tried in this period.
Btw, I just discovered that on the back of my TAB (chinese unicom) is written WCDMA. As I always used GSM cards with it I always assumed it was a GSM version, but now I am getting the doubt.
can you confirm I am on GSM version?
the full specs written on the back case are:
WCDMA无线数据终端 (wireless data terminal)
Model：GT-P1000
CMIIT 10 2010CP4950
Click to expand...
Click to collapse
Hi,
WCDMA is the 3.5G data-line : this means, it's NOT the WiFi alone version. If it's marked as P1000 just as is, then it's the GSM version. That means, you have EDGE/GPRS quadband @ 850/900/1800/1900 Mhz and HSDPA 7.2Mb/s=HSUPA 5.7 Mb/s triband @ 900/1900/2100 Mhz ...
Hmmm, what error did Odin give out when the flash failed ?
BTW, happy newyear etc ...
dirlan2001 said:
BTW, happy newyear etc ...
Click to expand...
Click to collapse
Happy new year to you, and that you very much for your help!
dirlan2001 said:
Hmmm, what error did Odin give out when the flash failed ?
Click to expand...
Click to collapse
Basically it's always the same error, no matter which ROM i flash.
it always fails at either Hidden.rfs or Movinand.mst, depending on the ROM.
here is how it looks like when I try GB-Stock-Safe (recommended by Overcome) for example:
Code:
<ID:0/018> Firmware update start..
<ID:0/018> boot.bin
<ID:0/018> cache.rfs
<ID:0/018> dbdata.rfs
<ID:0/018> factoryfs.rfs
<ID:0/018> movinand.mst
<ID:0/018>
<ID:0/018> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If I remove these files (Hidden.rfs or Movinand.mst) from the TAR i can flash with no errors, but the tablet wouldn't boot.
This apply to EVERY Roms i tried so far, with no exclusion.
I am making up a new theory: the first bricking error happened after I flashed JQ1, which has bootloaders. Could it be that those bootloaders go in conflicts with the chinese version of hardware, and thefore the brick?
I am keep trying flashing different combinations of ROM's, I am just afraid to get worst... :S
jacopo3001 said:
Happy new year to you, and that you very much for your help!
Basically it's always the same error, no matter which ROM i flash.
it always fails at either Hidden.rfs or Movinand.mst, depending on the ROM.
I am keep trying flashing different combinations of ROM's, I am just afraid to get worst... :S
Click to expand...
Click to collapse
Hi,
No thanks, you're welcome LOL
The problem seems indeed the bootloaders playing up. I guess you'll need to try repair them with this thread from the same guy that made this thread
I suggest you try to repair the lot via the guides he gives to get a up and running again. After that you can retry to install AF974's latest...
Cheers, and good luck
dirlan2001 said:
The problem seems indeed the bootloaders playing up. I guess you'll need to try repair them with this thread from the same guy that made this thread.
I suggest you try to repair the lot via the guides he gives to get a up and running again. After that you can retry to install AF974's latest...
Click to expand...
Click to collapse
thanks, I know those threads already (read them all!)
the main problem I don't get about the bootloader fix is that chainfire released a APK, which assume you can boot the phone!
He starts the thread saying his phone was bricked and cannot flash anything on it, then he fixes it with a APK! that got me lost, how to get out of the brick first?
regarding AF974, that's not my priority, I am just trying to have this thing working again..
jacopo3001 said:
He starts the thread saying his phone was bricked and cannot flash anything on it, then he fixes it with a APK! that got me lost, how to get out of the brick first?
Click to expand...
Click to collapse
Hi,
He did a 200 mile trip to have the MoBo changed .. LOL That doesn't help you any further I guess...
Did you try to put the renamed kernel.zip and flash that through CWM as I previously proposed ? What is the outcome ? Or eventual errors ?
PS : as long as you can get it in download mode (odin) or CWM it's not a brick, it just not booting completely...
dirlan2001 said:
Hi,
Did you try to put the renamed kernel.zip and flash that through CWM as I previously proposed ? What is the outcome ? Or eventual errors ?
Click to expand...
Click to collapse
I chickened out last minute!
I could upgrade to a latest version of CWM by simply flashing CF-ROOT with odin.
but I was not sure about proceeding mounting Overcome's kernel:
OC's documentation raccomends to mount on a clean and functioning install of JQ1 (which i dont have) and says that its kernel will automatically convert the formatting to ext4.
I am not sure it's a good idea to convert formatting while at this situation.
Would I be able to revert in case something goes wrong?
What do you think?
jacopo3001 said:
I chickened out last minute!
I could upgrade to a latest version of CWM by simply flashing CF-ROOT with odin.
but I was not sure about proceeding mounting Overcome's kernel:
OC's documentation raccomends to mount on a clean and functioning install of JQ1 (which i dont have) and says that its kernel will automatically convert the formatting to ext4.
I am not sure it's a good idea to convert formatting while at this situation.
Would I be able to revert in case something goes wrong?
What do you think?
Click to expand...
Click to collapse
Hi,
Do I understand correctly your system is up and running again ? In that case I would certainly recommend to run the complete guide to make it first stock again. The kernel indeed does a conversion to ext4, which is a way better filesystem as the rfs from Samsung. Look in the Overcome thread for the mirrors as OC seems still to have serious problems with their serversystem.
And if you take courage (and the habit) you might start looking for a more recent kernel and ROM...
dirlan2001 said:
Do I understand correctly your system is up and running again ?
Click to expand...
Click to collapse
The system is NOT up and running.
It's hanging at the Samsung logo.
But I can at least get to both download and recovery mode.
What happens is that, regardless which ROM I try, I cannot flash neither hidden.rfs nor movinand.mst (depending on Rom's content), they always FAIL on ODIN.
If I flash a ROM removing those 2 it Odin would success, but the tab will not Boot and hang at Samsung logo.
That's why I say the system is not stable now, I am not sure whether it's a good idea to go into changing FS now or would it screw up things even worst...
Hello all,
I have an issue with latest CWM 5.5.0.4 recovery. It says the following error:
E:Error in /cache/recovery/last_log
(Read-only file system)
and other similar errors:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
and I'm unable to reflash GalaxianSoup ROM nor restore the original backed up 3.2 factory rom.
What actually happened ?
Once bought, I managed to root, flash CWM 5.5.0.4 recovery and install the latest GalaxianSoup ROM. Everything based on the guides in development forum and successful (all latest versions). All cool! System was working fine.
Yesterday, I was using tablet, installed few apps, nothing special and later left tablet turned on and charging. When I came back, it was turned off. Okay, tried to turned on, but the system never booted and always looped (seeing only Google logo and moving gears). I rebooted into recovery and noticed the error (see above).
Now, I'm basically unable to do anything. I tried to wipe data, cache and Dalvik cache several times, and reflash GalaxianSoup again (Galaxian + Gapps) or also restore the 3.2 system backup that I've made (always fails).
I've read on some other forums that it might have something to do with damaged SD card partition or something.
I'm out of ideas. Can anyone help me pleeeeease?
EDIT: I've got european Samsung Galaxy Tab 8.9 16GB WIFI version.
EDIT: I must correct myself. After rolling back to factory rom, I was experiencing the same issues, seems there some hardware issue. I sent the tablet back for repair, seems now it had nothing to do with GalaxianSoup. No need to worry, keep up the good work.
whiplash84 said:
Hello all,
I have an issue with latest CWM 5.5.0.4 recovery. It says the following error:
E:Error in /cache/recovery/last_log
(Read-only file system)
and other similar errors:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
and I'm unable to reflash GalaxianSoup ROM nor restore the original backed up 3.2 factory rom.
What actually happened ?
Once bought, I managed to root, flash CWM 5.5.0.4 recovery and install the latest GalaxianSoup ROM. Everything based on the guides in development forum and successful (all latest versions). All cool! System was working fine.
Yesterday, I was using tablet, installed few apps, nothing special and later left tablet turned on and charging. When I came back, it was turned off. Okay, tried to turned on, but the system never booted and always looped (seeing only Google logo and moving gears). I rebooted into recovery and noticed the error (see above).
Now, I'm basically unable to do anything. I tried to wipe data, cache and Dalvik cache several times, and reflash GalaxianSoup again (Galaxian + Gapps) or also restore the 3.2 system backup that I've made (always fails).
I've read on some other forums that it might have something to do with damaged SD card partition or something.
I'm out of ideas. Can anyone help me pleeeeease?
EDIT: I've got european Samsung Galaxy Tab 8.9 16GB WIFI version.
Click to expand...
Click to collapse
Flash your recovery again through odin..
Then reflash your galaxian soup..
If not success, use odin and flash stock rom..
Dont forget backup your file from sdcard just in case if you need reset factory..
suwandiapr said:
Flash your recovery again through odin..
Then reflash your galaxian soup..
If not success, use odin and flash stock rom..
Dont forget backup your file from sdcard just in case if you need reset factory..
Click to expand...
Click to collapse
Flashing of CWM didn't help to fix the issue, installing of GalaxianSoup didnt work at all (corrupted ZIP file error...)
Thanks God, reflashing of stock ROM via Odin did work, tablet is up and running. GalaxianSoup is definitely not stable enough yet, I'll stick to the stock rom fora while. Thank you!
whiplash84 said:
Flashing of CWM didn't help to fix the issue, installing of GalaxianSoup didnt work at all (corrupted ZIP file error...)
Thanks God, reflashing of stock ROM via Odin did work, tablet is up and running. GalaxianSoup is definitely not stable enough yet, I'll stick to the stock rom fora while. Thank you!
Click to expand...
Click to collapse
Galaxian Soup is more then stable enough. Bad flashes happen and you just said you had it up and running.
bdfull3r said:
Galaxian Soup is more then stable enough. Bad flashes happen and you just said you had it up and running.
Click to expand...
Click to collapse
To be honest, it is kind of stable, but not enough, hence the beta label. Some further optimizing will be done once the team has ICS source. In my experience, it was stable, but sometimes it would turn off when in fell into Deep Sleep state. Now, the AOKP milestone 5 is giving me issues with the screen rotation. I've experienced both sides, AOSP and AOKP in their latest versions. Obviously there is more room for improvement, but I'm afraid the team is kinda stuck without source. They've done miracles without source though.
My Girlfriend asked me to update her SGS, so I said, why not trying a costum ROM. She agreed...
So is first installed CWM with hardcore's kernel with the ClockworkMod Recovery and the Heimdall Suite.
I made a backup of her data and installed CM7.
But she did not like it and asked me to recover her old system.
So I opened CWM and choose the backup. Then in the beginning of the progress the phone suddenly rebooted and stuck at the fist samsung Logo...
So I tried to install CM7 again.
"Error in CM7.....zip" (Status 7)
I downloaded it again and moved the new file to the SD. Same Problem.
I tried another ROM.
"Cannot mount \system"
I did hardcore's kernel with the ClockworkMod Recovery and the Heimdall Suite again. Same Problem
I formated the whole file system (and deleted the backup by misstake)
Same Problem...
I read that CM7 changes the partition structure, maybe thats the problem?
I read about Odin but of course, as I used the guide above I did not wrote don the IMEI etc of the SGS.
My GF is going to kill me, this is serious
Any suggestions?
I tried something different with using odin
I tried to install an original ROM but also gut errors from the filesystem.
When rebooting the logo shows up and the animation starts but it loops and never end.
"Cant mount /dbdata your storage not prepared yet. Please use UI menu for format and reboot options"
And bootloader (3e) showing up, when i try to do something it crashes and when trying to reboot BSOD....
Even when I try to start the bootloader alone
cannot mount /dbdata (invalid argument)
faild to mount /dbdata (File exsists)
Cant acess to /system/csc/ELP/system/
Ok then I tried to check the "Re-Partition" Box but Odin is not starting the process if its checked...
Try flashing firmware from here. Most of them contain bootloaders. And repartition with 512 pit.
http://forum.xda-developers.com/showthread.php?p=14273101
Sent from my I9000 running JW5 with Dmore3.3 and Semaphore 2.7.4
I made it to reinstall Cyanogenmod. Dont know how it exactly worked, but it did.
So the first thing I want to do is to backup those EFS-Files.
My problem is that I dont have the possibility to install ROMS because (like at the very first installation) The Progressbar of the CWM Installer stops after a few seconds an the device reboots without having anything installed.
But, as I have CM7 installed, I have SU. so maybe there are other possibilites to backup those important files? Just copy the directory?
I had nerves and made it to install MIUI. It has all the google apps, its shiny and very girl-like.
I realy pray she likes it.
Now, 8 hours later I want to let you know I will not study tomorrow morning. Im just going to BED !!!
hhhhhhhhhhhhh dont do it again
Try to install an official rom with 3 files using odin then re-install the old rom
Sent from my GT-I9000 using xda premium
Borstenhorst said:
My Girlfriend asked me to update her SGS, so I said, why not trying a costum ROM. She agreed...
So is first installed CWM with hardcore's kernel with the ClockworkMod Recovery and the Heimdall Suite.
I made a backup of her data and installed CM7.
But she did not like it and asked me to recover her old system.
So I opened CWM and choose the backup. Then in the beginning of the progress the phone suddenly rebooted and stuck at the fist samsung Logo...
So I tried to install CM7 again.
"Error in CM7.....zip" (Status 7)
I downloaded it again and moved the new file to the SD. Same Problem.
I tried another ROM.
"Cannot mount \system"
I did hardcore's kernel with the ClockworkMod Recovery and the Heimdall Suite again. Same Problem
I formated the whole file system (and deleted the backup by misstake)
Same Problem...
I read that CM7 changes the partition structure, maybe thats the problem?
I read about Odin but of course, as I used the guide above I did not wrote don the IMEI etc of the SGS.
My GF is going to kill me, this is serious
Any suggestions?
Click to expand...
Click to collapse
Try re-installing the stock firmware and redo the update the following link tell you how to do it.
https://www.fixmystuff.in/FMS_Forum/threads/samsung-galaxy-s-gt-i9000-flashing-to-original-rom.46/
it seems like she like it. So im realy releaved
hi guys
this is my first post on this kickass site and i hope that someone can help me with this rather strange error :victory:
as the subject of topic says , i get this error whenever i boot my friends sgs into recovery as normal booting goes on loop forever.
this is the error i get in the recovery of stock I9000XXJVU:
----------------------------------------------------------------------------------------
--Copying media files...
E:failed to mount /sdcard (file exists)
E:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet,please use UI menu for format and reboot actions
media files copy failed
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TRA/system/'.
Successfully applied multi-CSC
----------------------------------------------------------------------------------------
what happened is this:
my friend had a sgs and i wanted to flash it with cyanogenmod 10 (android 4.1)
the stock firmware was 2.2 iirc.
i just rooted the stock and flashed the 4.1
it went ok but i saw the mounting error back then sometime that i rebooted the device with 4.1 on it but didn't get that error all the time and it would boot just fine.
then the error popuped more and more.
so i decided to flash stock 2.3.6 ,rooting it and finaly go back to 4.1.
after i flashed the device using I9000XXJVU it goes on loop.
recovery and downloading mode works.but the recovery give me that error i said above.
i guess a hardware issue but i don't know for sure
i'm lost here :silly:
help me plz
Thanks in advance
Hi flash this http://db.tt/T8ZpfTPa in pda section in odin
Then see & follow my last post in this thread
http://forum.xda-developers.com/showthread.php?t=1993937
Donovan662 said:
Hi flash this http://db.tt/T8ZpfTPa in pda section in odin
Then see & follow my last post in this thread
http://forum.xda-developers.com/showthread.php?t=1993937
Click to expand...
Click to collapse
thanks for the reply.
i did what you said and its still in loop and same error in recover.
why my internal sdcard isn't mountable?can it be hardware failure?
Same errors?
Donovan662 said:
Same errors?
Click to expand...
Click to collapse
yep same error as before.
after flashing is done and it want to install the package,it get stock and give me that mounting error.
i just want to know if this problem is software or hardware
I also had this problem. Was on stock JVT with semaphore, partitions converted to ext4.
I decided to reboot my phone for no particular reason (was working reat) and when i powered it on kept boot looping without really getting past the samsung gt-i9000 white letters / black background screen.
CWM recovery said it was unable to mount any partition. External SD mounted fine, just nothing from the internel sd. No system, data, whatever. Got me thinking i may had my internal sd malfunctioning.
I just flashed it with odin and my stock branded operator rom (2.3.3) and done nothing more. No repartition. Working great. Was probably some ext4 error.
Before that i had been using cyanogen stable. Started giving FC like mad, so i flashed that stock JVT. On hindsight it may only had been the data partition that had run out of free space but i had no way of knowing when it happened and needed my phone running.
Reflashing got mine running again. Maybe try with Heimdall if odin's not working for you? Be sure to get a complete rom, with bootloaders and such. I'd suggest your operator's stock one. That way you can also send it back to samsung if it still doesn't work.
Click to expand...
Click to collapse
Found this post somewhere in the xda forum, it helped many people having the same problem as yours, hope it helps you !!!!
http://forum.xda-developers.com/showthread.php?t=1841250
See problem 11 exact same problem described
thanks for the help guys
i tried everything that came to my mine and used this topic for my errors but still get errors
problem 11 and 12 are the ones i get flashing different roms
even tried a Rescue kit from here but no go...
why this is happening to me?
the failed to mount as i have come to understand is internal SD card failure you will have to give external SD card a try
Check this thread
http://forum.xda-developers.com/showthread.php?t=2059098&page=2
file moved or deleted
hi friend, file link not working file moved or deleted........
Hello, everyone. This is my first post so excuse my newbliness, if any is noticed...
I've been trying to flash my Mini for quite a while and all I got was a series of epic fails. The ROM that I was trying to flash is the Unofficial CyanogenMod 10, by rohan007; to be more specific, Unofficial CM10_15-12-12, which is the latest update, I think. I was using Cyanogenmod Recovery Image 5.0.2.6-tass which worked quite fine, giving me the advanced options and everything, but each time I would try to install zip from sd, I would get the following error:
~some incomplete log text above, not sure if it matters~
/E:Error in /sdcard/customrom/CM-10_15-12-12.zip
(Status 7)
Installation aborted.
Of course, I followed the exact instructions on how to flash a custom ROM; Clear cache partition, Wipe Data/Reset, Clear Dalvik Cache, etc...
My phone is rooted, by the way. I used the universal_gb_root_v25.zip to root my phone, since it was the only method that worked.
Then, after further investigation, I found out that the image version 5.0.2.6 sometimes fails to intall a custom ROM. So, I found the ClockWorkMod Touch Recovery Lilg Version for Galaxy Mini, CWM TOUCH 5.2.0.8 version. And when I flashed it, I just got "Install from sdcard completed" log message. Since I didn't got any advanced options, I tried to flash the ROM by selecting the option to apply update from sdcard and yet again, I got the following error:
~again, some incomplete log text above, not sure if it matters~
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Then, when I rebooted my system, my phone got stuck on the Samsung GALAXY mini GT-S5570I text and now, every time when I press the power button, it keeps doing the same! I'm seriously getting frustrated here... Anyways, I can only go to the Android system recovery, and the Cyanogenmod system recovery and that is it. Also, I can still manipulate my data from the sd card. (Move and remove files from it, I mean).
One more thing about the Android system recovery. Now I get the log text saying:
-- Appling Multi-CSC --
E:failed to mount /system (Invalid argument)
E:failed to mount /system (Invalid argument)
And obviously, I did something(s) wrong in the whole process, so I beg you to help me resolve this issue. Thank you.
If you need any additional data about the whole bundle of problems, I will be more than glad to post them in my next reply.
see if odin detects your phone, and reflash cwm.
yackovsky said:
see if odin detects your phone, and reflash cwm.
Click to expand...
Click to collapse
ODIN MODE works, reflashing only works with image version 5.0.2.6...
As far as I know ...
we can't flash CWM in GT-S5570i
we can use in temporary only ....
this mean we can use CWM 5.0.2.6 in CWM mode and after reboot the phone goes into original CWM mode.
What I would u to do is ...
If u can go into CWM recovery mode then wipe data / Factory reset
if this doesn't help ...
Go into download mode and flash with original firmware using ODIN ...
shwe said:
As far as I know ...
we can't flash CWM in GT-S5570i
we can use in temporary only ....
this mean we can use CWM 5.0.2.6 in CWM mode and after reboot the phone goes into original CWM mode.
What I would u to do is ...
If u can go into CWM recovery mode then wipe data / Factory reset
if this doesn't help ...
Go into download mode and flash with original firmware using ODIN ...
Click to expand...
Click to collapse
For the CWM, I know. You have to flash it every time on reboot on the android system recovery to get it working.
I tried with factory reset several times and that did nothing. Download mode, also nothing.
So the best solution for me would be to find the stock firmware on the internet and flash that. I'll tell you how that went...
Also, when I try to format system, I get an error: "Error mounting /system! Skipping format... Done"
So for the future, is there any other way, besides CWM, to do a full, complete wipe of the Android OS?
Don't flash gts5570 roms on gts5570i for gawds sake, unless you want to brick your phone...
yackovsky said:
Don't flash gts5570 roms on gts5570i for gawds sake, unless you want to brick your phone...
Click to expand...
Click to collapse
Eh... It's too late for that now... Darn it. Any good methods on how to unbrick it? And, can I take it to the service shop to let them fix it?
Symeonus said:
Eh... It's too late for that now... Darn it. Any good methods on how to unbrick it? And, can I take it to the service shop to let them fix it?
Click to expand...
Click to collapse
if your phone gets detected by odin, just flash any official firmware from samfirmware.com and it's done. if not, hopefully you're still under warranty, then only samsung service center can help you. play dumb, don't mention rooting, flashing, custom roms and such...
yackovsky said:
if your phone gets detected by odin, just flash any official firmware from samfirmware.com and it's done. if not, hopefully you're still under warranty, then only samsung service center can help you. play dumb, don't mention rooting, flashing, custom roms and such...
Click to expand...
Click to collapse
YAY! I UNBRICKED MY PHONE! All is working just fine. Now then, if anything gets seriously wrong, I know what to do. Thank you, yackovsky, for your help.
It seems that all of those errors were caused by me trying to flash GTS5570 ROM on GTS5570I.