Database Develop

[Q] Nexus One "Status 7 error "

I've rooted and unlocked my N1 and flashed it several times with custom Roms. I recently went from CM7 RC1 to a rooted stock 2.3.3, for which I had installed HBOOT. Now I am only able to perform a nandroid restore to change the roms and am unable to install CM7 RC2 or even to reinstall CM7 RC1 with which I was previously running. The error I see is:
Installing update . . . .
assert failed: getprop("ro.product.device") =="
one" || getprop("ro.buiE:unknown command [ld.product")]
E: Error in /sdcard/update.zio
(Status 7)
Installation aborted.
I've looked through Cyanogen and XDA forums but I haven't seen a direct response to this particular issue. I've tried Wiping and wiping the davlik cache, and I've flashed Clockwork recovery and RA recovery via rom manager. I've tried 4 separate roms and get the same error, and these are roms I was able to use previously.
Any help or even a push in the right direction would be very much appreciated, as I've essentially hit a wall. Please excuse the noobish picture of my N1 screen , I don't know how to take screen shots.

status 7 error
i have the same problem. solution plz

So this happened only after flashing the hboot right?
Did you try wipe/data factory from the recovery menu?

Looks like a problem in build.prop of the ROM currently on device.
Solution: check build.prop for the line that the installation scripts fails at, see what it's expecting and what's there, and change accordingly. You can do all that by ADB shell in recovery.

fakey97 said:
I've rooted and unlocked my N1 and flashed it several times with custom Roms. I recently went from CM7 RC1 to a rooted stock 2.3.3, for which I had installed HBOOT. Now I am only able to perform a nandroid restore to change the roms and am unable to install CM7 RC2 or even to reinstall CM7 RC1 with which I was previously running. The error I see is:
Installing update . . . .
assert failed: getprop("ro.product.device") =="
one" || getprop("ro.buiE:unknown command [ld.product")]
E: Error in /sdcard/update.zio
(Status 7)
Installation aborted.
I've looked through Cyanogen and XDA forums but I haven't seen a direct response to this particular issue. I've tried Wiping and wiping the davlik cache, and I've flashed Clockwork recovery and RA recovery via rom manager. I've tried 4 separate roms and get the same error, and these are roms I was able to use previously.
Any help or even a push in the right direction would be very much appreciated, as I've essentially hit a wall. Please excuse the noobish picture of my N1 screen , I don't know how to take screen shots.
Click to expand...
Click to collapse
From the screen shot, i think you are trying to flash an NS ROM!! That's the reason it fails
Sent from my icy cool nexus

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.

I think I bricked my Tab

As I was trying to install recovery on my tab, I think I screwed up big time.
After rooting following this guide(which worked) this is what happened when I tried to restart to recovery from the Rom Manager app (I stress : I didn't install the recovery from the Rom Manager, I know it's not the proper one) :
http://imgur.com/SBAb8
It's the screen I get when I launch the tab with the power button.
Worse : this is what I get when I power it on holiding the volume up button :
http://imgur.com/LqqFC
It's bad isn't it ? Any way to fix it ?
It won't power off.
Thanks...

Ive done this before. Can you not boot into download mode. I first started by leaving it to see if it would eventually restart on its own. If that doesn't work for you, while trying to turn it off hold down the volume down key. If I'm no mistaken this is how I managed to get mine back. Kind of forcing the restart in the direction you want it to go. Once there, I used fast boot to boot a known recovery, did a wipe but not sure if this was necessary, and then a restart, while holding thumbs. Hopefully you will have some luck with this as well.
Sent from my Nexus 7 using XDA Premium HD app

Well, I think Santa came by this night : when I woke up, the tab was working and almost fully charged...
Thanks !
Update : oh God, I'm an idiot ! You what that icon is ? It's the background of the recovery. It's just that it's not showing the usual list of actions by default. You need to press Power+Volume Down while on that screen to make it work !
However my problem is that I can't seem to flash another recovery (it's Android System Recovery <3e>) and that one doesn't allow any Rom to flash...I tried flashing the latest recovery with Odin and through fastboot : it does seem to work from the reports but when I try to access it, it's this this old recovery...
EDIT : Actually whenever I try to flash newer recoveries through Odin and Fastboot, I always end up having that old recovery instead...
EDIT : I dared it, I try installing the latest Recovery from the Rom Manager App (not the touch though) and it worked but I can't flash any rom due to a getprop error (assert failed : getprop ("ro.product.device") == "p3" || getprop ("ro.build.product") == "p3" E:Error in /sdcard/path to the rom I flash.zip (Status 7).
It may be because it's a recovery for the p4. But still it's the only recovery that will flash instead of that old recovery...

So I went back to stock 3.0 with Odin. I rooted it (through skitzandroid-recovery.img) and now I tried installing the latest recovery through fastboot and it still doesn't work.
Here's a capture of the Recovery and the attempt to flash a CM9 rom :
http://i.imgur.com/lsqSo.jpg
Any idea ?

DannyBiker said:
So I went back to stock 3.0 with Odin. I rooted it (through skitzandroid-recovery.img) and now I tried installing the latest recovery through fastboot and it still doesn't work.
Here's a capture of the Recovery and the attempt to flash a CM9 rom :
http://i.imgur.com/lsqSo.jpg
Any idea ?
Click to expand...
Click to collapse
Glad you came right with the fix, I haven't been able to flash a new recovery since the 3.2 update. Nothing works, I've tried fast boot flash, Odin and even ROM manager (I know, I thought why not, this tab is practically unbrickable ) which caused the issue you reported in this thread for me. Its a real hassle not having a working recovery. On all my other devices, I download an update, boot to recovery, and flash it. On the p7100 I have to take out my laptop, and boot into the recovery.
Very frustrating. But last week I got an early Christmas present, the nexus 7
so I will probably put a good stable cm9 on the p7100 ( thanks pershoot) and let my kids and wife carry on with what has been a very good tablet.
Sent from my Nexus 7 using XDA Premium HD app

But can you access a recovery in any way that allow flashing cm9 or cm10 ?
When it comes to recovery, rooting, etc, this tab is a piece of crap...

DannyBiker said:
As I was trying to install recovery on my tab, I think I screwed up big time.
After rooting following this guide(which worked) this is what happened when I tried to restart to recovery from the Rom Manager app (I stress : I didn't install the recovery from the Rom Manager, I know it's not the proper one) :
http://imgur.com/SBAb8
It's the screen I get when I launch the tab with the power button.
Worse : this is what I get when I power it on holiding the volume up button :
http://imgur.com/LqqFC
Click to expand...
Click to collapse
The first screen is the stock recovery in action, you need to wait for the timeout (5-10m) for the tablet to reboot itself to normal mode; rebooting through the power button wont work since it is locked into recovery boot (second screen).
DannyBiker said:
EDIT : Actually whenever I try to flash newer recoveries through Odin and Fastboot, I always end up having that old recovery instead...
EDIT : I dared it, I try installing the latest Recovery from the Rom Manager App (not the touch though) and it worked but I can't flash any rom due to a getprop error (assert failed : getprop ("ro.product.device") == "p3" || getprop ("ro.build.product") == "p3" E:Error in /sdcard/path to the rom I flash.zip (Status 7).
It may be because it's a recovery for the p4. But still it's the only recovery that will flash instead of that old recovery...
Click to expand...
Click to collapse
Either you flashed the wrong recovery or you used Rom Manager; Rom Manager has no proper 10.1v support, and will try to flash the p7500 recovery, which will work for most tasks; however, most CM-based ROMs have a pre-flash test which will be tripped up by the wrong recovery version, giving the error above.
You can flash the proper recovery through fastboot/Odim and then install the ROMs, but do not use Rom Manager afterwards, since it will detect a different recovery and try to flash the wrong one again.

I tried that and I still can't flash any working recovery. Odin or Fastboot, the flash goes fine but it just doesn't show...

So I make it worked by pure luck :
I tried flashing the .tar.md5 recovery with fastboot (instead of the .img one) which caused an error on boot. Something that said "unrecoverable bootloader error 0*00000" that scared the **** out of me.
However, Odin mode was still accessible. I flashed the tar.md5 through Odin and this time, it worked !
Thanks...

[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

[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.