Database Develop

Install Paranoid Android from 2.3.6

Hi, Im trying to install PA but I get an errormessage saying :
Installing update...
set_perm: some changes failed
E:Error in mnt/sdcard/bluetooth/pa_galaxysmtd-1.99_13august2012.zip
(status 7)
Installation aborted
Im running 2.3.6 with latest SpeedMod.
I cleared cache and did factory reset.
Any advice ?

Wich recovery do you use?
I think stock (background is android out a box)
If so:
Download: http://www.mediafire.com/?6qtveztq9997b6n
Put on SD and install it. Reboot phone and then you can install any rom u want!

i have the same error with cwm 6.0.1.0
gonna try this recovery

[SOLVED] Problem in installing SentinelROM

Hi
Firstly, I'm new here, so please don't be too harsh
I tried to install SentinelROM into my i9305, but failed.
I followed the exact instructions by putting the ROM in my internal storage
I'm using CWM v5.5.0.4
When I chose the zip file (the ROM) using "choose zip from internal sdcard", this happened:
Code:
-- Installing: /emmc/sentinelrom_v4_75_i9305.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "
m3" || getprop("ro.build.product") == "m3" ||
getprop("ro.product.device") == "m3xx" || g
etprop("ro.build.prouct") == "m3xx" || g
etprop("ro.product.device") == "i9305" || getpro
p("ro.build.product") == "i9305" || getpr
op("ro.product.device") == "GT-I9305" || getprop
("ro.build.product") == "GT-I9305"
E:Error in /emmc/sentinelrom_v4_75_i9305.zip
(Status 7)
Installation aborted.
I copied the above information exactly as shown on my phone
FYI, I do not have external storage (micro sd card)
Please advise

Try using a newer version of CWM or use Philz Touch Recovery!
It's based on the latest build of CWM and it has extra features like touchscreen support!
Here, look for the I9395 version of it and then flash it either with Odin (or Mobile Odin) or flash the zip through CWM.
Hope it helps
Sent from my GT-I9305 using xda premium

Copy the downloaded SentinelROM zip to your Internal Storage.
Boot into your custom recovery
Back up your stock ROM
Enter custom recovery
Factory Reset and wipe Cache and Dalvik Cache
Format System Partition
Install the ROM

jjpro45 said:
Try using a newer version of CWM or use Philz Touch Recovery!
It's based on the latest build of CWM and it has extra features like touchscreen support!
Here, look for the I9395 version of it and then flash it either with Odin (or Mobile Odin) or flash the zip through CWM.
Hope it helps
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
I followed you advice and the ROM has been successfully installed on my i9305
I used Philz Touch Recovery to install it
Thank you very much!! :good::good:
This thread can now be closed :victory:

JJEgan said:
Copy the downloaded SentinelROM zip to your Internal Storage.
Boot into your custom recovery
Back up your stock ROM
Enter custom recovery
Factory Reset and wipe Cache and Dalvik Cache
Format System Partition
Install the ROM
Click to expand...
Click to collapse
Thank you, but this was exactly what I did and then the problem occurred
As it is now solved, I think the problem was due to CWM
I've successfully installed it using Philz Touch Recovery

Tried several mods, don't get past logo's

I have a Samsung I9001 and I tried several mods. For example the
CM10.1 by ADC: http://forum.xda-developers.com/showthread.php?t=2315448
CM10.2 by ADC: http://forum.xda-developers.com/showthread.php?t=2436670
Mokee Open Source: http://forum.xda-developers.com/showthread.php?t=2425024
and AOKP: http://forum.xda-developers.com/showthread.php?t=2190224
I can format /data, /cache, /system, erase Dalvik cache, install zip's (In the CM mods, I have to delete the
Code:
assert(getprop("ro.product.device") == "ariesve" || getprop("ro.build.product") == "ariesve" ||
getprop("ro.product.device") == "GT-I9001" || getprop("ro.build.product") == "GT-I9001");
from the updater-script, or else I cannot install these mods. AOKP installs without a problem.
But when I boot these mods, they all get stuck at the CM booting logo or the "initiating swagger" logo of AOKP.
I tried installing factory mod of T-Mobile / Netherlands, it worked as expected. I could statup apps, call, sms, etcetera. After that installed AOKP, not passing logo. After that installed CM9 mod: http://forum.xda-developers.com/showthread.php?t=1650615. Not passing spinning CM logo....
I don't know what to do next.
What's missing? And what steps should I take now?

First off all there is no need to remove these lines from the updater-script.
To me its weird that your phone aint booting after installing the custom rom and mods you want.
Are you 1000% sure you have a i9001 and not a i9000?

mrjraider said:
First off all there is no need to remove these lines from the updater-script.
To me its weird that your phone aint booting after installing the custom rom and mods you want.
Are you 1000% sure you have a i9001 and not a i9000?
Click to expand...
Click to collapse
Well, I do have a i9001. I see it when I start the phone, behind the battery, on the package, so I don't think I accidentally think it's one.
I did install the CM9: http://forum.xda-developers.com/showthread.php?t=1650615
This one worked! (Still I had to delete those lines from the update script file)

Do you get some sort of error during flashing?

[Q] Problem installing PacMan

I've sucessfully flashed several ROMs to my htc One m7ul, I've followed the convert your device to a google plus edition changing my model name and I've been able to install other m7ul based roms on my device (AOKP for example) but when i download the pacman roms from the official Pacman site under their Other and Stable section for the m7ul and try to install it (after making a wipe) i get the following in my log:
+------------------------------------------------------------------------------------------------+
Installing '/sdcard/Download/pac_m7ul_4.3-build(rest cut off?)
Checking for MD5 file . . .
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == (rest cut off?)
getprop("ro.product.device") == "m7ul" | (rest cut off?)
E: Error excuting updater binary in zip '/sdcar (rest cut off?)
Error flashing zip '/sdcard/Download/pac_m7ul_4 (rest cut off?)
Updating partition details . . .
+------------------------------------------------------------------------------------------------+
the "(rest cut off)" being where i think theres more text to the error but due to the screen formatting it looks like its being cut, I'm using TWRP recovery, have an unlocked bootloader and have s-off, Can anyone help me?

I've been able to install the ROM by using AndroidKitchen to extract the updater-script and edit it. The homescreen is very buggy, no wallpaper display, bootloop issues. I'm Changin the kernels to try and help but im not sure if this is a rom issue or a kernel issue. Does anyone have this ROM installed? and if so what kernel are you using?

One workaround for 'assert failed' during CM install

Error message during failed install of CM zip: assert failed: get prop ("ro.product.device") == "ovation" || get prop ("ro.build.product") = ="ovation"
Solved: See below.
When I first got my HD+, I did an SD "install" of CM 11. Then I installed CM 11 to the emmc, via CWM, per all the instructions on the xda website.
Once CM 11 was installed, I changed to TWRP 2.6.3.0. (I like being able to name the backups.)
Then I did a wipe and dropped down to CM 10.2.1. (More stable.) I did the install from TWRP.
Then I installed the fuzz kernel from TWRP.
Last, I updated to TWRP 2.6.3.0a when I couldn't get Succulent's CM 11 to install.
Okay, so tonight I wanted to do a clean install of CM 10.2.1, without gapps this time.
So I booted to recovery, did a wipe, and tried installing CM 10.2.1.(The build came direct from Cyanogen mod's website for the Ovation.)
I get an error similar to what I got when I tried to install Succulent's CM 11. Here's the error message:
assert failed: get prop ("ro.product.device") == "ovation" || get prop ("ro.build.product") = ="ovation"
I dropped back to CWM and tried installing the ROM from three different versions: CWM 6.0.4.5, 6.0.4.5b, and CWM 6.0.4.6.
I tried installing CM 10.2.1 from the internal and the external SD card.
No joy. Fortunately, a Nandroid backup beforehand and I've restored to where I was.
Any ideas what's wrong? It shouldn't be this hard. It doesn't seem that a ROM install should be Recovery Dependent . But maybe it is?
==========
Solved. leapinlar, in the thread where I originally posted this question, said to use an older version of CWM to install. Apparently some incompatibility between versions of CWM (and TWRP) and the ROM zip.
Another solution was alluded to by King200 in another forum, but it sounded arcane and hard to do. It wasn't.
Here are Windows instructions:
++++++++++
Note: This method removes the "sanity check" built into the recovery image which checks to make sure the ROM you're installing is compatible with your tablet. Obviously, flashing the wrong ROM can/will brick your tablet.
So be warned.
Since I only have one tablet that I flash CM 10.2.1 on, no problem for me. If you have more than one tablet, perhaps you should delete your hacked zip after you install, to be safe.
Okay?
But for educational purposes, here's what I did to work around the problem.
++++++++++
You do this with 7-Zip. (So install 7-Zip if you don't have it already.)
Right click on the ROM that you're trying to install.
A 7-Zip context menu opens.
Select "Open Archive."
Drill your way down to
/META-INF/com/google/android/updater-script
Right click on the updater-script and select "Edit."
Open updater-script with Notepad.
Delete the first line of code, all the way up to the first semicolon. And delete the first semi-colon as well.
Save the edited file in Notepad. You'll get a 7-zip message asking if you want to incorporate your changes back into the archive. "Yes."
Now the ROM will install with later versions of CWM or TWRP.
Note: I had to do with this with the "fuzz" kernel too.
P.S. I don't know how to read code, so I don't understand exactly what the problem here is. I peeked at the scripts. I have an "ovation" tablet. Both the ROM and the Recovery image mention "ovation" in their updater scripts. Seems like they ought to talk to each other.

Please don't do this procedure. It is dangerous. It could brick your device. And the issue is not whether you have more than one tablet, it is if you accidentally download a hummingbird (HD) zip when you have an ovation (HD+) and try to flash it to an HD+. If you remove that assert statement the HD zip will merrily install to an HD+. And you will have a real mess.
A real case happened where a Nook Color user tried to flash a Nook Tablet ROM to his Color. The assert statement which was designed to prevent that did its job and prevented it. However, another user recommended he remove the assert statement, which he did, and thus flashed the Tablet ROM to his Color. His Color ended up bricked.
NEVER REMOVE AN ASSERT STATEMENT!
There are two more safe procedures.
One, use an older version of CWM to flash the older zips.
Two, do as the procedure says by opening the archive, but don't edit the updater-script file to remove the assert line. Look in a newer zip like CM11 and extract the file 'update-binary' and copy it to the old zip replacing the old update-binary file there. Then the old zip is flashable with the newer CWM/TWRP recoveries.
Sent from my BN NookHD+ using XDA Premium HD app