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

Can't flash any ROM via CWM (status 7 / efs not mounted)

I was on Darkys ROM for some months without any flashing problems. Now i wanted to change from Darkys ROM 10.1 (Gingerbread 2.3.4) to Galnet MIUI. I had to downgrade to Froyo and then install the CWM zip in CWM. This was NOT succesful. It always says "Installation aborted (Status 7)". Then i tried to install CyanogenMod 7.1. Upgraded to Gingerbread Stock with CWM 3 and when i first flashed it via ODIN the phone first booted in the standart Android CWM display (dont know the name sry). The phone automatically formated cache etc. but then it showed me 2 times "/efs is not mounted". I was able to boot and to open CWM but ALWAYS when i want to install ANY CWM ROM it shows me the message with Status 7 ...
EDIT: The message when i try to install a zip via CWM:
--INSTALLING: SDCARD: update-cm-7.1.0-GalaxyS-signed.zip
Finding update package
Opening update package
Installing update
Checking state of BML/MTD
assert failed: run_program("tmp/updater.sh) == 0
E:Error in /mnt/sdcard/update-cm-7.1.0-GalaxyS-signed.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
How can i mount /efs again and make CWM ROM Flashing able again?
Thank you.

I am not a dev, but I suggest you do a fresh ODIN flash to stock rom or this SIMPLY HONEY ( its got odin version & hence very easy to install ) rom.

I already flashed several (stock) roms... still not working

The first thing you every do before flashing a rom is a nandroid backup.... use this to recover...
I hope to hear oh thanks i didn't remember about that, lol. But i do not expect it...
Do you have any backups, of the /efs maybe? If you do then find out how to put that back on..
An option would be to use adb to try fix it, first try the obvious and try mount the ef, if that doesn't work then tell me what files you have in the efs... and we'll try help you from there.
If you don't know hoe to use adb there is a pinned thread in the general forum, and I have made a there is a basic tutorial in a number of places either search here or google

[Q] Error during ROM installation

Hi, I experienced a problem during ROM installation (CyanogenMod 9) on Samsung Galaxy Mini. When phone starts, there appears CM9 logo for a while and then phone gets stuck on black screen with white "ANDROID". During installation I got this error:
[4/5] Installing system...
E:Error in /tmp/sideload/package.zip
(Status 0)
Installation aborted.
I CAN access CWM menu. Is there any solution to bring the phone back to life?
Thanks.

restore nandroid if u have, or flash to other custom rom, do a full wipe, or...back to stock using odin.
sent from my Walkman

maybe the zip file is domage ,just download again CM9 or another ROM and flash it........your phone is not dead if you can get access to CMW, it's just empty (no rom)

You're still out of danger since your phone is not dead. Follow this: Wipe data+cache //// install zip from SD //// another rom //// wipe data+cache //// reboot
Sent from my GT-S5570 using xda premium

[Q] CM9 reinstall: make_ext4fs failed on /cache

Hi everybody, I'm quite scary about what I've done today with my tab.
1. I was running under CM 9.1 stable and everything was fine.
2. I backed up my data using ROM Manager and tried today a nightly build of CM 10 from get.cm. I installed it from CWM as written in Cyanogen wiki. Before install I was warned about partition format that wasn't the same as previsouly, and I was asked to choose the update.zip again to enable the ROM flashing to start. CM 10 booted correctly, and it ran very well at first. Then I chose to install Gapps through CWM, the same I did for CM 10.
3. After rebooting, I experienced a bug: the included keyboard kept crashing and was then unusable. I decided then to restore my backup of CM 9 through CWM.
4. I did not encounter any trouble restoring the backup to my old CM 9. But I had no radio, no IMEI, no baseband etc.. in "settings/about the device" and at this point I didn't know that this was because "/radio" wasn't mounted.
5. Now I don't remember what I exactly did but I try wiping caches, restoring again, reinstalling CM 9 stable, reinstalling CM 10 stable, restoring my backup again, flashing the Kernel using Hemsfall but what I remember is:
- I first had problems with /cache
- After that I had the "E:format_volume: "make_ext4fs failed on /cache" message
- My tab reboots if I try to install CM9 stable
- I tried to install a fresh firmware through http://forum.xda-developers.com/showthread.php?t=1133590 but I get stuck at hidden.fs
Now my tab can only boot to CWM or download mode, and whether I choose to flash to CM9 or CM10 I get the message:
assert failed: getprop("ro.product.device")== "galaxtab"...
E: Error in /sdcard/cm-10-nightly....zip
(Status 7)
Installation aborted
I don't know what to do now, and I'm quite desperate right now, please help me to get rid of that "make_ext4fs" error. I'm really afraid.:crying:

When you update to cm10, the mtd partition scheme changed to a new one. Nandroid restore won't work until the partition is made back to the same as when backup was taken.
To be able to run cm again, you need to restock to GB using Odin,
then flash overcome kernel to get cwm.
Only the kernel, not the ROM.
Then use cwm to install cm,
then restore from nandroid.
Follow my signature for overcome guide.
Get GB stock safe v5, the PDF guide, and the overcome kernel.
Jump to page 7.
Sent from my GT-P1000 using xda app-developers app

Thanks you very much, be blessed, it works perfectly using your solution. I felt really really bad, thank you so much!

you are welcome.
You may want to try CM10 again.
Make sure you flash gapps for cm10 only, not gapps for cm9 or cm10.1
It shouldn't be as unstable as you said.

[Q] Boot into CWM does not work.

Hi. I have GT-N7000 with rooted Stock Android 4.1.2.
I installed a fresh stock and rooted for testing / attempting to upgrade to 4.4.X and now I have CWM Manager PRO with Touch CWM (I payed for both).
When I get it to boot into CWM, it restarts, shows the green Android logo with that rotating thing inside... but it suddenly shows black screen and the phone is closed. If I turn ON the phone it loads into Android System Recovery 3e.
I have latest
- CWM Manager 5.5.3.7
- CWM 6.0.4.3
Please how can I boot into CWM?

N7000 doesnot work that way... Read http://forum.xda-developers.com/showthread.php?t=2780703

Thanks for your reply. Installing the Philz Touch CWR with the Stock recovery shows this error:
This package is for "galaxynote,n7000,N7000,GN-n7000" devices; this device is a ''
E:Error in /tmp/sideload/package.zip
(status 7)
Please guide me, I am completely lost. All methods to install it don't work.

dnp_sgn said:
Thanks for your reply. Installing the Philz Touch CWR with the Stock recovery shows this error:
This package is for "galaxynote,n7000,N7000,GN-n7000" devices; this device is a ''
E:Error in /tmp/sideload/package.zip
(status 7)
Please guide me, I am completely lost. All methods to install it don't work.
Click to expand...
Click to collapse
Check the build number of your current rom in settings and then go to philz thread. Search for TW kernels link and find the one that matches your ROM build number. Flash the one either using recovery or odin.

nokiamodeln91 said:
Check the build number of your current rom in settings and then go to philz thread. Search for TW kernels link and find the one that matches your ROM build number. Flash the one either using recovery or odin.
Click to expand...
Click to collapse
Thanks so much, now I have it working