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

[Q] i9000 CWM Assert failed: (status 7)

I've been trying to flash aokp_vibrantmtd_build-25 and\or AOKP_build23_i9000_beta2.1-signed with no success I boot into CWM and select the zip it starts then I get the Asset failed: ro.product.device == GT-I9000M ect and it ends with (Status 7)... Am I using the wrong CWM v2.5.1.0? To be sure I flashed the latest Kernel speedmod-kernel-k16-11 via Odin and still not working. The old ROM I had wont launch any longer and its not hosted so I'd be nice to get the AOKP rom running. Any help would be much appreciated!
A: Wiped everything and formatted everything then flashed another ISC ROM and updated kernel to Semaphore_ICS_0.8.1 CWM updated to v5.5.0.4 re-flashed beta 3 and it works flawlessly now!

Btw for future reference if you know what device you have and know the rom is compatible (hard right?). You can edit out assert statement in install script.
Sent from my SGH-T959 using XDA App

[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

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

[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