Tab bricked, CWM Recovery - Read-only file system issue - Galaxy Tab 8.9 General

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.

Related

[Q] Stuck in bootloop...need help

So I updated the MIUI on my Cappy from whatever I had before to 2.3.30 that is GB 2.3.7 from this location:
http://miuiandroid.com/community/threads/archived-miui-versions-captivate-gb.16558/
I didnt care for it so I downloaded SlimICS. I downloaded the base and the cappy essentials. Put them both on my internal sd. I factory reset, wiped data, cache and system and dalvic, just as i do for every phone i work on. I ran the SlimICS base and now it keeps rebooting and going back into recovery and doing this:
Finding update package...
Opening update package...
Installing update...
Slim ICS
Once Slim ICS pops up, it reboots and does it all over. I can yank the battery and manually go into recovery, but if i try to boot it up normal, it goes back into the loop. I am on CWM 5.0.2.7 also.
So what did i miss?
GB bootloaders most likely missing - flash 'em using Heimdall. And SlimICS doesn't have modem. So. Flash my ROM for a change may be.
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
And you flashed the base and the cappy essentials right? Not just the base
Sent from my SGH-I897 using xda premium
korockinout13 said:
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
Click to expand...
Click to collapse
trying to flash again just put it back in the loop. And I read that that does happen alot going from GB to ICS on the Cappy. But for Slim it didnt work.
Wdustin1 said:
And you flashed the base and the cappy essentials right? Not just the base
Click to expand...
Click to collapse
I never could get that far because it was the base that I started to install and it got bootlooped on, everytime it restarted, it went back into recovery and started to run the base again, and repeated boot loop. I read somewhere that teamhacksung's rom would get me over the GB to ICS bridge. This one here:
http://forum.xda-developers.com/showthread.php?t=1363760
It did the bootloop to, but when i yanked the battery and went back in and installed it a 2nd time, it didnt restart and installed correctly. After that I installed SlimICS. But I dont like it as much as i thought i would and now when i try to reinstall teamhacksung ROM, it errors out during the beggining of the installation. The MD5 is still fine. I dont think it likes the version of CWM recovery that SlimICS installed. I know CWMR went to an older version when i went from teamhacksung to SlimICS.
Flash glitch kernel first. Also, don't use the builds from that thread, it is old. Just flash the latest CM9 nightly
Swyped from my ICS Samsung Captivate
Stuck in A boot loop after flashing paranoid rom to cappy i897
I downloaded all needed files to internal SD just as the (how to upgrade the captivate i897 to Paranoid ROM said to do )
wipe data factory reset,wipe cache,selected install zip zip>package (pa_captivatemtd-1.99-13AUGUST2012.zip, md5sum: cc03bacf0f07a94bf25b482d64b94e63) then it started boot looping / att screen twice then android guy ,, then falling over with exclamation point in the middle of him , let it go considering options of 3 button combo weren't working ,, beside guide said 5-10 min to install then it made it to devil kernel installed gapps >> (gapps-jb-20120726-signed.zip, md5sum: f62cfe4a827202899919fd932d5246d7) now back in the boot loop again>>
i did make a nandroid backup but cant seem to get into cwm recovery or download mode . I did follow that guide to a tee.
any help or suggestions on this i would greatly appreciated if this post in wrong spot sry im new.
Also stuck in bootloop reverting to Gingerbread
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Reply Back.
HG_User said:
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Click to expand...
Click to collapse
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out. ??
---------- Post added at 06:38 PM ---------- Previous post was at 06:27 PM ----------
321321wrick said:
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out.
There also Ginger Bread Boot loaders Needed for it to start up Correctly - i personally don't know that much bout gingerbread rom i didn't like it as much as froyo WiFi issues'' the the stock odin should erase all info on your part thou 'e use Is OCD 1 i897UCJF6>lowercase work every time for me.
cept now because my usb is not able to charge phone or enter download mode or recovery which leaves jig option .
Click to expand...
Click to collapse
HG_User,
U can't go back to GB (or froyo/eclair) from CM, MIUI, ICS, JB, AOSP etc., etc. without using Odin or Heimdall---because of the different partitions used---Stock firmware is bml/rfs and all the AOSP etc etc are mtd/yaffs(2).
And u can only restore a backup when u r back running the base rom where u made the back up.
Use this...Stock i897ucKK4 GB 2.3.5 with or without bootloaders... http://forum.xda-developers.com/showthread.php?p=18370912
This kk4 should get u going. Then u can use Odin to flash Corn Kernel to get a cwm back...:thumbup:
Sent from my SGH-I897 using xda premium
... one step on the way: Back to Eclair
thanks for the advice. Ultimately, I decided I should use Odin 3 1-click to revert back to original (2.1 Eclair) firmware that I found on the first post of thread titled
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
This is a huge step forward because it makes my phone work, but it's also a step back in time to the early Eclair days.
Now my next step is to upgrade back to Gingerbread...
Edit: Thanks to all who pointed me in the right direction. I took the phone back to Eclair then used Samsung KiesMini (twice) to get it back to Gingerbread. After re-rooting and removing the AT&T Bloatware, it works fine again. I might try upgrading again to ICS or JB, but I didn't like Cyanogen 9 at all. Maybe I'm just used to the way AT&T polishes the UI, but Cyanogen didn't appeal at all. Now looking for a relatively polished but lightweight ICS or JB version... Also, it would be nice if when I upgrade it preserves the installed apps and what's on my home screens, but that seems unlikely going from AT&T-branded Gingerbread to an independent ICS or JB.

[i9001] The phone will just load up (FeaCore Phoenix) CWM Recovery.how to get out?

Hi everybody.
In the past I already flashed custom ROM to routers, so I thought I had the skill to undergo the path of flashing ROM to a phone.
Wrong.
I have countless tabs opened tried to solve my stucked phone, and my PC is running out of memory; and I'm running out of hope.
I own a S Plus GT-i9001.
I wanted to get rid of all the bloatware present in the phone, so I gained root privileges.
Like explained here. It worked perfectly.
Since deleting all the unnecessary apps didn't look working, I thought "well, it is a rainy day, you had this device for a while, why don't you flash some ROM?"
So,
1. I followed this guide, but, needless to say, Rom Manager was not fulfilling to its duty. Indeed I backuped everything I needed, but the stock rom
2. I followed then this guide, point 3, to install ClockworkMod Recovery directly. Before, everytime I tried to enter the recovery menu, I was bounced to the original recovery menu, because ROM manager did not succeed.
With this guide, I managed to boot into ClockworkMod Recovery.
I then started backing up the ROM to the external SD, and it seemed working.
It was popping out with a message "E:Can't mount /cache/recovery/command", but since all the operations went successful, I did not care much (fail, I suppose)
3. I tried to boot back into the phone, before installing the new ROM, just to double check I saved everything, and then the drama began. I was just continuously bounced back at CWM Recovery menu, no way to get in the phone.
I tried anyway to install the AOSP 4.0.4. and all the steps went successful, but still nothing, I would always reboot automatically into CWM Recovery.
4. I tried restore from backup in external SD, it ran successfully, but still couldn't load the phone
5. I then googled into the "E:Can't mount /cache/recovery/command" error, so I ended up somewhere that they were advising to flash FeaCore Phoenix Recovery tool. Indeed it did not display anymore such an error
6. I tried again with he AOSP 4.0.4 ROM, but it showed then the following error
Code:
assert failed: getprop("ro.product.device") == "thunderc" || getprop("ro.build.product") == "thunderc"
so I ended up here and changed the zip accordingly.
7. I also tried this instructions here to perform the most ultimate massive wiping.
8. I installed the AOSP 4.0.4, and the update-Gapps-ICS-20712.zip, it worked, no errors.
Still, it reboots into the recovery menu.
I can't get out of this damned recovery menu, it is crazy! I have used so many recovery tools in PCs, you usually are able to leave them, maybe not able to restore the OS, but you never get stuck into a circle of hell like this!
Please, does anyone has some advice for me? I don't want to waste a 6-months old device
thank you!
You should reflash CWM with odin like this then try flashing a rom again.
If that doesn't work flash a stock frimware through Odin also with the AriesVE.ops file active.
All guides tell you to put the "recovery-clockwork-5.5.0.4-ariesve.tar.md5" or the stock firmware file as "one package". Doing that results into large file errors or odin getting stuck on "downloading..."
Putting the file under phone got my phone back to life, after softbricking it by using CWM 6 thouch.
switchboy said:
You should reflash CWM with odin like this then try flashing a rom again.
If that doesn't work flash a stock frimware through Odin also with the AriesVE.ops file active.
All guides tell you to put the "recovery-clockwork-5.5.0.4-ariesve.tar.md5" or the stock firmware file as "one package". Doing that results into large file errors or odin getting stuck on "downloading..."
Putting the file under phone got my phone back to life, after softbricking it by using CWM 6 thouch.
Click to expand...
Click to collapse
man, you saved my life!
you and the powerful, mighty Odin, god of the Valhalla!
oh, it feels so awesome!
but since I never learn (that was enough of a message to tell me to stop messing around)...
how do I install the ROM I'd like, go through the same process (my phone is now as as when I bought it) or can I use somehow Odin?
jv_guano said:
man, you saved my life!
you and the powerful, mighty Odin, god of the Valhalla!
oh, it feels so awesome!
but since I never learn (that was enough of a message to tell me to stop messing around)...
how do I install the ROM I'd like, go through the same process (my phone is now as as when I bought it) or can I use somehow Odin?
Click to expand...
Click to collapse
I realised that, since I flashed the recovery-clockwork-5.5.0.4-ariesve.tar you provided, if I would boot in recovery mode, it would be still there.
and it is.
but still it is showing the error
E:Can't mount /cache/recovery/command and, needless to say, it is not loading the ROM correctly, it stucked again
I don't get which part am I doing wrong!
jv_guano said:
I realised that, since I flashed the recovery-clockwork-5.5.0.4-ariesve.tar you provided, if I would boot in recovery mode, it would be still there.
and it is.
but still it is showing the error
E:Can't mount /cache/recovery/command and, needless to say, it is not loading the ROM correctly, it stucked again
I don't get which part am I doing wrong!
Click to expand...
Click to collapse
Well, I sorted it out (absolutely, in a mysterious way!!! )
I downloaded the recovery-clockwork-6.0.1.2-ancora.tar.md5 from here, and I followed again your instructions for flashing it with Odino (rigorously NOT ticking one package).
When rebooted, I had the AOSP 4.0.4 Stock, shiny and sparkling!
without even entering the recovery menu and reinstalling!
but I guess I will need to do a clean install again, now that seems that CWM 6 is digested by my phone

A bundle of problems when trying to flash...

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.

[Q] Galaxy S Plus black screen, CWMrecovery says "can't mount...

I'm a noob I know and yes I watched the noob-video. But I need help! Cuz I'm too dump! So please help me
I wanted to update my Galaxy S Plus to the newest CM 10 (Beta 4) (before it was the Beta 3) over the CWM recovery it suddenly says
"symlinks failed"
"error in /sdcard/cm-10-20130324-invendor-beta4-ariesve.zip"
"(Status 7)"
"installation aborted"
so I looked to the CWM recovery and I saw that I don't have the latest version....okay I downloaded the latest one and installed it over the CWM recovery. The same error .... with friends. Now I got when I went into the CWM recovery: (after I tried to wipe data/factory reset or wipe cache)
"E:Can't mount /cache/recovery/log"
"E:Can't open /cache/recovery/log"
"E:Can't mount /cache/recovery/last_log"
"E:Can't open /cache/recovery/last_log"
I tried to restart the phone...black-screen after the samsung cyanogen mod screen.
Okay
So I tried to flash a older firmware "I9001XXKQ7_I9001DBTKP2_I9001XXKPK_HOME.tar.md5" with Odin. I restarted the phone...nope black screen. I installed the newest CWM recovery again and tried to flash again the CM 10. Black-screen. So I tried the old version of the CM which I had before (Beta 3) -> black-screen and still errors in the recovery mode.
I can still go into the download mode and the recovery mode. The charging symbol is not working when i connect it (just the battery but bot moving)
My device:
Samsung Galaxy S Plus
Provider: Vodafone IT
ROM: CM 10 (Beta 3) installed but not working
Kernel: Phenom 3.2 UV (updated after the symlinks failed error)
I hope some genius out there can help me
And sorry for my bad english...I don't use it often (Italy)
Follow my HOW TO Guide at Bottom till you get to Flash CM 10 and use the one you want
Remember Use PIT and Re-Partition to Flash 2.3.6..then Root then use yours!
Will clear up any errors you may have
Thanks!
Hey! Thanks a lot! I'll try it out and report it if its working :good:
EwOkie said:
Follow my HOW TO Guide at Bottom till you get to Flash CM 10 and use the one you want
Remember Use PIT and Re-Partition to Flash 2.3.6..then Root then use yours!
Will clear up any errors you may have
Click to expand...
Click to collapse
!!!!!!!!
dont download the files there!
i think they are for i9000, but the thread starter has an i9001
!!!!!!!!!
have you tried to flash a recovery like CWM 5.x.x.x via odin? it is stable. i think it is linked in the i9001 development at the CM9 Rom by arco
edit: just found
http://forum.xda-developers.com/showthread.php?p=39640245
Regards
Okay
Okay! I didn't do it yet sooo ... I'll try that one and thanks for the link! :good:
then...?
"have you tried to flash a recovery like CWM 5.x.x.x via odin? it is stable. i think it is linked in the i9001 development at the CM9 Rom by arco"
I flashed the CWM recovery via odin, I could format now tho folders and mount them again, but the recovery always freezes when I wanna format the user data. Why? and what should I do as my next step?
Imanidiot said:
I flashed the CWM recovery via odin, I could format now tho folders and mount them again, but the recovery always freezes when I wanna format the user data. Why? and what should I do as my next step?
Click to expand...
Click to collapse
take your time...
what errors does the cwm 5.5.0.4 recovery shows without doing anything?
try to additionally mount system and data partition (see under <mount and storage>)
then click on wipe data/factory reset in the main menu
Hi everybody I'm new.
My situation is exactly the same, I did the same things, got the same problems... got stuck with no solutions yet if not to send it to samsung assistance.
Flashad many other android phones in the past and never had issues like this... it's a nightmare...
try to additionally mount system and data partition (see under <mount and storage>)
then click on wipe data/factory reset in the main menu
Click to expand...
Click to collapse
Without doing anything the recovery says nothing....just the normal main-screen.
After I mounted system and data I click on wipe data/factory...but then it doesn't do anything. It freezes after "Formatting /data..."
I flashed the FeaMod Recovery v.1.2. based on CWM v5.0.2.7
Imanidiot said:
Without doing anything the recovery says nothing....just the normal main-screen.
After I mounted system and data I click on wipe data/factory...but then it doesn't do anything. It freezes after "Formatting /data..."
I flashed the FeaMod Recovery v.1.2. based on CWM v5.0.2.7
Click to expand...
Click to collapse
I also tried the broodROM RC5, succesfully flashed with Odin but still the same problems as before.
Can't format /data.
Stock-Firmware
I am trying to flash now the latest stock firmware with Odin...hopefully it will work.... Still waiting for other ideas :/
Imanidiot said:
I am trying to flash now the latest stock firmware with Odin...hopefully it will work.... Still waiting for other ideas :/
Click to expand...
Click to collapse
I already did that too but it didn't work...
I'm gonna go to the samsung assistance in the afternoon... :crying:
Well....Nothing is working...Anyone who could help me? ... Or better us..
If my guide is no use to you as its for i9000 : try this HERE
If that helps you in any way let me know.
I did this already... I flashed it with the newest stock-FW but it doesn't do anything...and the stock-recovery can't make a factory reset. It always freezes....
other things that could be worth a try:
try flashing different recoveries - not only feamod... also cwm,...
for me cwm5.5.0.4 works
look: our wiki-page -> un-brick
if all doesnt help you could try to reset all partitions
I tried already a few recoveries...like the CWM or the TeamWin... How can I reset them? Can you give me a link please? ^^
Flash BroodROM RC 5... flash this multiple times without touching any buttons like repartion etc..
After that, wipe system and data via the recovery provided in the ROM.
Then flash the newest stock FW from samsung..
This solved all my issues multiple times xD
thanks for the reply, but my phone is now finally brocked....it doesn't even start....and I don't have any idea what i can do now...
??
So, now Samsung, no Samsung Galaxy S Plus GT-I9001? No nothing. Not even the soft brick image (see wiki)

[Q] Cannot install any custom roms. Phone acting weird

Hey guys. I've been using CyanogenMod on my Galaxy S for quite a long time. Few days ago my battery died and phone wouldn't pass the CyanogenMOD logo. I've decided to go back to stock rom and then upgrade to one of the new roms.
So I flashed the stock rom using Odin 3.07, rooted, went to recovery mode and tried to flash: Mackay ROM, Beast ROM ( black and white as well as beastxl), Avatar ROM, Slim Bean, Tsunami, CyanogenMOD but none of the above worked.
It starts the installation and after few seconds phone restarts itself and gets stuck on new boot logo.
The only thing that gets installed is the CWM which won't let me do the factory reset, wipe data, wipe dalvik cache etc. Keeps saying can't mount /data, /cache, /system.
The only time I can do factory reset is when I install stock rom.
I only succeeded installing Franzy ROM once but after reboot gets stuck on boot logo.
Sometimes even the stock ROM is giving me issues like process com.android.phone has stopped unexpectedly (does it for dialer, calculator, market, launcher)
Another weird thing is that even when I go back to stock rom and open up for instance a picture with bright background or web browser I can see transparent battery and CyanogemMod in the middle of the screen even tho phone's not charging and running on stock rom not CyanogenMod.
I think I've tried everything from fixing permissions, flash and re-partition using Odin and 512 pit file.
Even rang my Mom like advised in xda's video, didn't help either
Is there anything else I can try to get my phone in "shape"?
Any suggestions?
AllUsernamesAlreadyInUse said:
Hey guys. I've been using CyanogenMod on my Galaxy S for quite a long time. Few days ago my battery died and phone wouldn't pass the CyanogenMOD logo. I've decided to go back to stock rom and then upgrade to one of the new roms.
So I flashed the stock rom using Odin 3.07, rooted, went to recovery mode and tried to flash: Mackay ROM, Beast ROM ( black and white as well as beastxl), Avatar ROM, Slim Bean, Tsunami, CyanogenMOD but none of the above worked.
It starts the installation and after few seconds phone restarts itself and gets stuck on new boot logo.
The only thing that gets installed is the CWM which won't let me do the factory reset, wipe data, wipe dalvik cache etc. Keeps saying can't mount /data, /cache, /system.
The only time I can do factory reset is when I install stock rom.
I only succeeded installing Franzy ROM once but after reboot gets stuck on boot logo.
Sometimes even the stock ROM is giving me issues like process com.android.phone has stopped unexpectedly (does it for dialer, calculator, market, launcher)
Another weird thing is that even when I go back to stock rom and open up for instance a picture with bright background or web browser I can see transparent battery and CyanogemMod in the middle of the screen even tho phone's not charging and running on stock rom not CyanogenMod.
I think I've tried everything from fixing permissions, flash and re-partition using Odin and 512 pit file.
Even rang my Mom like advised in xda's video, didn't help either
Is there anything else I can try to get my phone in "shape"?
Any suggestions?
Click to expand...
Click to collapse
try to flash stock rom again via odin , root , then flash cm 9 ( to not loose you IMEI ) , then flash CM 10.1 stable from here : http://get.cm/?device=galaxysmtd&type=stable
then install any costum rom you want
The Tox said:
try to flash stock rom again via odin , root , then flash cm 9 ( to not loose you IMEI ) , then flash CM 10.1 stable
then install any costum rom you want
Click to expand...
Click to collapse
Thanks for your reply. Installing CM 9 worked but trying to install CM 10 throws up this error:
assert failed: run_program("tmp/updater.sh") == 0
E: Error in sdcard/cm-10.1.zip
(Status 7)
Installation aborted.
Flash this one :
http://get.cm/get/3Fb
then install this one :
http://get.cm/get/9aJ
Thanks for your help. CM 9.1.0 installs fine, same error for 10.1.2 :/
AllUsernamesAlreadyInUse said:
Thanks for your help. CM 9.1.0 installs fine, same error for 10.1.2 :/
Click to expand...
Click to collapse
did you tried to install other costum roms , like slimbean ?
There MIGHT be a problem with your internal SD card. Slight chance :/
did you tried to install other costum roms , like slimbean ?
Click to expand...
Click to collapse
Yes I did and only Franzys installed successfully but then stopped working after phone reboot.
There MIGHT be a problem with your internal SD card. Slight chance :/
Click to expand...
Click to collapse
I think that might be the case. I get encryption unsuccessful with my sdcard in and CWM doesn't see any files with sdcard out.
I found an article here on forum that explains how to use your external sdcard as the internal one. Will give it a try and see if it works.
For now I don't mind using CM 9.1.
Thanks for your help guys and let me know if you have any other suggestions.

Categories

Resources