Database Develop

Tab bricked, CWM Recovery - Read-only file system issue

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.

[Q] Installing AOSP Beta 8 and 9 for P7300

Hi,
I have tried to install both AOSP Beta 8 and 9 for P7300. I get the error the same error message both times, status 7 which is guess is due to that I'm using the wrong CMW file (version 5.5....). Reading the forums it seems like cmw 6.0.1.0 works pretty well. Is there a repository where I can download these CMW files? I have search but not really found any good place. What combination of AOSP version and CMW is best? Do I need to change the kernal also?
Any help is welcome!
Kind regards,
Mikael Hagström

I recomand you to install the cwm 6.0.0.8, i think it's the best and this should fix your problem.
Sent from my GT-I9300 using Tapatalk 2

Don't think recovery version is to blame.
Do you have the 7300 or 7310 galaxy tab?
What was the last Rom / recovery that you flashed with Odin?
IIRC status 7 is an assert failure, so you could also turn off assert verification in the recovery, before flashing... Or remove offending assert from the update script in aosp ROM zip. (probably a line like test for p5 or p7300)
Or you can flash CWM 6.0.0.8 from the thread on cm9 (kallt_kaffe) , post #2. Although file is named 6008, it really is 6010... If you insist on that route
Sent from mobile app...

Thanks for your replies.
I have the P7300.
I'm back on the stock ROM now since I could not get the AOSP ROM to work.
I tried removing the assert lines. The tablet hang on the X (Nexus) screen when I rebooted.
I will try both again with the new Clockwork Recovery file.

Hi,
I tried again his morning. With CWM 6.0.0.8 from the thread on cm9 and the ROM from http://forum.xda-developers.com/showthread.php?t=1789464. It now installs but when I reboot is gets stuck at the black screen with the colourful Nexus X. I left it like that for 25 min but no change just the X. This is how I do it.
I start of with the stock ROM (Build number HTJ85B P7300XWKL4)
I root the device and install superuser and root check (that tells me it have been rooted)
I install CWM 6.0.0.8 from boot by running the ZIP file
I boot up into Clockwork Recovery and install the AOSP ZIP. The tablet restarts after install but gets stuck at the screen with the X.
Do I need to do a wipe?
I'm I missing some steps?

g3blv said:
Hi,
I tried again his morning. With CWM 6.0.0.8 from the thread on cm9 and the ROM from http://forum.xda-developers.com/showthread.php?t=1789464. It now installs but when I reboot is gets stuck at the black screen with the colourful Nexus X. I left it like that for 25 min but no change just the X. This is how I do it.
I start of with the stock ROM (Build number HTJ85B P7300XWKL4)
I root the device and install superuser and root check (that tells me it have been rooted)
I install CWM 6.0.0.8 from boot by running the ZIP file
I boot up into Clockwork Recovery and install the AOSP ZIP. The tablet restarts after install but gets stuck at the screen with the X.
Do I need to do a wipe?
I'm I missing some steps?
Click to expand...
Click to collapse
Try to fully wipe also format your /system in cwm recovery 6.0.0.8 and then try installing again and reboot it should work man!

Works now! Thanks!

[SOLVED] [Q] Assert failed (Can't install ROMs)

Hello!
I have a Samsung Galaxy S Captivate previously rooted over a year ago. I was mostly using CyanogenMod for a while, and some time ago, I decided to try out some random ROM (can't remember the name, but it was an unofficial port of ICS).
It had some issues and bugs, so I decided to switch back to CyanogenMod. I've tried installing CyanogenMod 7.2, 9.0 and 10.0
Everytime, I get the following error message:
Code:
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "captivate" ||
getprop.("ro.build.product") || ... (and so on)
E:Error in /sdcard/#whateverpackage#.zip
Status 7
Installation aborted.
*Where "whateverpackage" is the zip/ROM I am trying to install.
Things I attempted to no avail:
1. Toggling asserts. I get the same error.
2. Reflashing recovery-clockwork-2.5.1.2, but I get the same type of error.
3. Installed USB Drivers for Samsung, and attempted to run Odin3 One-Click Downloader (I897UCJF6-final-OCD-REV0.exe), but it isn't responding it seems.
I'm thinking of trying to install ADB and see if I can get the device to properly go into "download mode" and see if Odin responds.
This may be important: When I boot in recovery, the top of my screen shows "CWM-based Recovery v5.5.0.2"
So if anyone knows a straightforward fix to this, or can at least give me rough steps to try/follow, I would greatly appreciate your help.
Thanks for taking the time to read this!

You could have quickly found an answer if you searched "status 7" or "assert failed." It simply means your phone is identifying as a different device because of the ROM you flashed. You can get around this by flashing a kernel appropriate for whatever you're trying to install, so Devil or Semaphore will do. From there, reboot recovery and install the ROM.

korockinout13 said:
You could have quickly found an answer if you searched "status 7" or "assert failed." It simply means your phone is identifying as a different device because of the ROM you flashed. You can get around this by flashing a kernel appropriate for whatever you're trying to install, so Devil or Semaphore will do. From there, reboot recovery and install the ROM.
Click to expand...
Click to collapse
I did look up assert failed, but I couldn't get a clear answer.
I didn't occur to me to look up "status 7"; just seemed like a very cryptic error code.
Thank you for your advice nonetheless. I'll update if the error persists.

Semaphore & CyanogenMod
So, I flashed Semaphore 2.8.0 and then attempted to install CyanogenMod 10 (Android 4.1.2, I think).
Got Status 0.
Tried reflashing Semaphore 2.8.0, and 1.2.6. No progress.
Any recommendations?
I tried to flash CyanogenMod 9 on Semaphore 1.2.6 and got Status 7.
Thanks.

Headless_One said:
So, I flashed Semaphore 2.8.0 and then attempted to install CyanogenMod 10 (Android 4.1.2, I think).
Got Status 0.
Tried reflashing Semaphore 2.8.0, and 1.2.6. No progress.
Any recommendations?
I tried to flash CyanogenMod 9 on Semaphore 1.2.6 and got Status 7.
Thanks.
Click to expand...
Click to collapse
If you would read a bit before doing the flashing you would know that status 0 is from rebuilding the partition. You simply need to flash CM10.1 twice. So it goes like this: Flash CM10.1, reboot recovery, flash CM10.1.

BWolf56 said:
If you would read a bit before doing the flashing you would know that status 0 is from rebuilding the partition. You simply need to flash CM10.1 twice. So it goes like this: Flash CM10.1, reboot recovery, flash CM10.1.
Click to expand...
Click to collapse
I do look up the error. Just no one actually mentioning that until your post.
Thank you for your advice.
I flashed it 3 times (rebooting each time) and I always get Status 0.
More explicitly:
Code:
-- Installing: /sdcard/cm-10.0.0-captivatemtd.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-10.0.0-captivatemtd.zip
(Status 0)
Installation aborted.
Side note: I'm on Semaphore 2.8.0 and I used Heimdell to flash it (through Ubuntu).
Any additional thoughts?

Headless_One said:
I do look up the error. Just no one actually mentioning that until your post.
Thank you for your advice.
I flashed it 3 times (rebooting each time) and I always get Status 0.
More explicitly:
Code:
-- Installing: /sdcard/cm-10.0.0-captivatemtd.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-10.0.0-captivatemtd.zip
(Status 0)
Installation aborted.
Side note: I'm on Semaphore 2.8.0 and I used Heimdell to flash it (through Ubuntu).
Any additional thoughts?
Click to expand...
Click to collapse
Tried simply booting up?
If that doesn't work, reflash without rebooting recovery.

BWolf56 said:
Tried simply booting up?
If that doesn't work, reflash without rebooting recovery.
Click to expand...
Click to collapse
I tried rebooting the device, but, after shortly showing "At&t", it goes straight to the Recovery screen.
I tried installing CM10 again, but same error.
Just reflashed Semaphore. It always gets stuck on At&t after flashing (for several minutes). Is that normal?
So I've been removing the battery, and putting it back in. Then it goes straight to 'Semaphore CWM Recovery v6.0.2.0'.
My steps from there:
Attempted to install CM10. Status 0 error. Turned phone off.
Rebooted straight to CWM-Based Recovery v6.0.1.5.
Tried installing CM10 from there. Status 0 error.
Rebooted. Right back to Recovery v6.0.1.5.
Tried installing CM10 again. Status 0 error
Tried installing CM9. Phone rebooted midway and got stuck on 'At&t' screen.
Rebooted using 3-key button combo (to get to recovery screen).
Went to Recovery v6.0.1.1. (What the hell is going on?)
Tried installing CM9. SUCCESSFUL. Also installed gapps for ICS while at it.
Booted to CM9 correctly.
Rebooted to Recovery and it was still Recovery v6.0.1.1.
Rebooted back to CM9 properly.
Edit:
Rebooted to Recovery. Updated to CM10.
Noticed that Recovery version changed back to v6.0.1.5.
CM10 seems to be working properly.​
Anyone knows why I am getting 3 different Recovery versions?
Note: Sorry for the somewhat long post. I just figured I should tell you everything I am doing step-by-step.

Headless_One said:
I tried rebooting the device, but, after shortly showing "At&t", it goes straight to the Recovery screen.
I tried installing CM10 again, but same error.
Just reflashed Semaphore. It always gets stuck on At&t after flashing (for several minutes). Is that normal?
So I've been removing the battery, and putting it back in. Then it goes straight to 'Semaphore CWM Recovery v6.0.2.0'.
My steps from there:
Attempted to install CM10. Status 0 error. Turned phone off.
Rebooted straight to CWM-Based Recovery v6.0.1.5.
Tried installing CM10 from there. Status 0 error.
Rebooted. Right back to Recovery v6.0.1.5.
Tried installing CM10 again. Status 0 error
Tried installing CM9. Phone rebooted midway and got stuck on 'At&t' screen.
Rebooted using 3-key button combo (to get to recovery screen).
Went to Recovery v6.0.1.1. (What the hell is going on?)
Tried installing CM9. SUCCESSFUL. Also installed gapps for ICS while at it.
Booted to CM9 correctly.
Rebooted to Recovery and it was still Recovery v6.0.1.1.
Rebooted back to CM9 properly.​
Anyone knows why I am getting 3 different Recovery versions?
Note: Sorry for the somewhat long post. I just figured I should tell you everything I am doing step-by-step.
Click to expand...
Click to collapse
Actually that's great details, thanks!
Have you tried flashing CM10 from CM9? It will still have to rebuild the partition so 2 flashes will be needed.

BWolf56 said:
Actually that's great details, thanks!
Have you tried flashing CM10 from CM9? It will still have to rebuild the partition so 2 flashes will be needed.
Click to expand...
Click to collapse
Yes sir, I just did that. It works
Thanks for your help.

Just wanted to thank you both for this thread. Totally helped me upgrade my Cappy to CM10.1 today. Thanks!

[Q] Continuous boot, assert failed troubles (Help)

So I posted a help thing about EFS a while back and didnt get to much help with that but i managed to figure things out. Now however
ive got myself into another predicament i cant seem to get out of.
So, from the start, i have a galaxy s3 (GT i-9305T) it was rooted, i still had the stock rom, but was running the beoffla kernal.
The idea was to download and install "JustArchi I9300XXUGML2 stock, deodexed and all the rest" then start finding
some nice themes. Ive got philz_touch_6.07.9-i9305.tar installed for my recovery.
This is where the trouble starts...
So first off i wipe the cache and the davik cache, go to install the rom then i get this: (ill go from installing update)
assert failed: write_raw_image (" /tmp/boot.img" , " /dev/block/mmcblk0p5" )
E: Error in /storage/sdcard1/Just archi........zip
(Status 7)
Installation aborted
Now i looked up a whole heap of pages to see if i could sort it out myself and i tried a few different things,
none of which have prevailed. First i tried to reflash an insecure boot image then try again, nup. I tried to
flash back to stock recovery and re format (No errors) then back to custom. Mounted /data and /system
and re formatted which worked with no error, still same error when flashing rom though. Also tried flashing
with different custom recovery, no luck there either.
There were a few other things i tried but i cant really remember what i did because
this has been a problem for a while now. Some of the pages i looked over for
information were:
http://www.droidforums.net/forum/android-hacks-help/26658-assert-failed-write_raw_image-tmp-boot-img.html
http://forum.xda-developers.com/showthread.php?t=1045887
And this is the one im on at the moment, im currently downloading a stock rom from sammobile to try flash.
http://forum.xda-developers.com/galaxy-s3/help-i9305/i9305t-10-2-upgrade-boot-stops-unable-t2406422
"UPDATE"
Finished downloading the stock rom, tried to install with philz recovery and got this:
Installing: /storage/sdcard1/I9305TDVBME2_I9305TTELBME1_TEL (STOCK).zip
Finding update package...
Opening update package....
Installing update...
Installation aborted.
And thats it, no kind of specific error codes or anything.
Thanks in advance to anyone who can help me out,
really stuck on this one.​

IIEsoticoII said:
So I posted a help thing about EFS a while back and didnt get to much help with that but i managed to figure things out. Now however
ive got myself into another predicament i cant seem to get out of.
So, from the start, i have a galaxy s3 (GT i-9305T) it was rooted, i still had the stock rom, but was running the beoffla kernal.
The idea was to download and install "JustArchi I9300XXUGML2 stock, deodexed and all the rest" then start finding
some nice themes. Ive got philz_touch_6.07.9-i9305.tar installed for my recovery.
This is where the trouble starts...
So first off i wipe the cache and the davik cache, go to install the rom then i get this: (ill go from installing update)
assert failed: write_raw_image (" /tmp/boot.img" , " /dev/block/mmcblk0p5" )
E: Error in /storage/sdcard1/Just archi........zip
(Status 7)
Installation aborted
Now i looked up a whole heap of pages to see if i could sort it out myself and i tried a few different things,
none of which have prevailed. First i tried to reflash an insecure boot image then try again, nup. I tried to
flash back to stock recovery and re format (No errors) then back to custom. Mounted /data and /system
and re formatted which worked with no error, still same error when flashing rom though. Also tried flashing
with different custom recovery, no luck there either.
There were a few other things i tried but i cant really remember what i did because
this has been a problem for a while now. Some of the pages i looked over for
information were:
http://www.droidforums.net/forum/android-hacks-help/26658-assert-failed-write_raw_image-tmp-boot-img.html
http://forum.xda-developers.com/showthread.php?t=1045887
And this is the one im on at the moment, im currently downloading a stock rom from sammobile to try flash.
http://forum.xda-developers.com/galaxy-s3/help-i9305/i9305t-10-2-upgrade-boot-stops-unable-t2406422
"UPDATE"
Finished downloading the stock rom, tried to install with philz recovery and got this:
Installing: /storage/sdcard1/I9305TDVBME2_I9305TTELBME1_TEL (STOCK).zip
Finding update package...
Opening update package....
Installing update...
Installation aborted.
And thats it, no kind of specific error codes or anything.
Thanks in advance to anyone who can help me out,
really stuck on this one.​
Click to expand...
Click to collapse
Can anybody at all shed some light on my situation,
or at least a place for me to start learning myself...

Hi.
If you downloaded the stock ROM from sammy mobile are these not meant to be installed via Odin?
There are a few post if you search for some of the pre rooted stock ROMs that you can flash with odin.
I would start from there.
Sent from my GT-I9305 using xda app-developers app

johnnyblaze1977 said:
Hi.
If you downloaded the stock ROM from sammy mobile are these not meant to be installed via Odin?
There are a few post if you search for some of the pre rooted stock ROMs that you can flash with odin.
I would start from there.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
The roms i downloaded from samsmobile were in .zip files, which im pretty
sure has to be flashed with one of the custom recoveries.
Thanks though

at first seems you tried to flash rom designed for i9300
then, you downloaded an ODIN image and you have to flash it by ODIN, no way you'd flash it over any recovery
to be more specific:
unzip the file I9305TDVBME2_I9305TTELBME1_TEL (STOCK).zip you downloaded, you should get a huge file with extension of .md5 or .tar
read in the forums how to use ODIN to flash firmware

adamuadamu said:
at first seems you tried to flash rom designed for i9300
then, you downloaded an ODIN image and you have to flash it by ODIN, no way you'd flash it over any recovery
to be more specific:
unzip the file I9305TDVBME2_I9305TTELBME1_TEL (STOCK).zip you downloaded, you should get a huge file with extension of .md5 or .tar
read in the forums how to use ODIN to flash firmware
Click to expand...
Click to collapse
Yes ive just done this now and flashed the stock rom with odin
and i think everything has gone well (im not sure as my screen is
water damaged but i did here boot audio only once) so im
letting my phone sit in a bag of rice in pieces for the night
and am going to check things out tommorrow.

Installation aborted, any fix?

I just found my old N7000 somewhere in the house and was trying to boot it up, it worked but it was JB Touchwizz.
Touchwizz is to heavy for my old N7000 and i was looking for a CM7 built, couldn't find it so i decided to flash CM9 onto it.
I downloaded a kernel and installed it on my device, after that i flashed CM9 onto it but it says it's not for my device, i was sure it was for my device so i toggled signature verification off but it still says the same 'Installation aborted' because it's the wrong device...
Now i don't have any roms.... my backups can't be restored too... and i can't flash a newer kernel since it also says installation aborted.
What to do?
PS: I know there is always Odin and download mode but i would love to hear some better suggestions.

Elya_Dragon said:
I just found my old N7000 somewhere in the house and was trying to boot it up, it worked but it was JB Touchwizz.
Touchwizz is to heavy for my old N7000 and i was looking for a CM7 built, couldn't find it so i decided to flash CM9 onto it.
I downloaded a kernel and installed it on my device, after that i flashed CM9 onto it but it says it's not for my device, i was sure it was for my device so i toggled signature verification off but it still says the same 'Installation aborted' because it's the wrong device...
Now i don't have any roms.... my backups can't be restored too... and i can't flash a newer kernel since it also says installation aborted.
What to do?
PS: I know there is always Odin and download mode but i would love to hear some better suggestions.
Click to expand...
Click to collapse
Check recovery version if older than update it iff problm still persist try on other recovery..