Develop Bugs

Help Please - unable to install CM6

Hi,
I followed the method to root 2.2 (it came installed on my Evo) in this thread:
http://forum.xda-developers.com/showthread.php?t=765496
It appeared to work perfectly, when I look in my list of apps, I see superuser permissions...
However, every time I try to install CM6, I get this error:
assert failed: getprop("ro.bootloader") == "0.76.2000"; assert failed: getprop("ro.bootloader") == "0.79.0000";
I am running bootloader 0.93.0000 with S-OFF.
Can someone please tell me what I'm doing wrong and what I need to do to fix it. I have searched and searched, and spent several hours trying to figure this out before asking for help.
Thanks...

same problem here!!

The way i fixed the problems was. I went to this thread http://forum.xda-developers.com/showthread.php?t=752832 and flashed the PC36IMG.zip file from it. Now i have no problem installing cm6

Damn this has been asked frequently. Try checking the Q&A where, by the way, this should have gone.
Sent from my PC36100 using XDA App

NAND unlock, idiots.

Yes what the above said. Used to happen before with me.
Sent from my Evo 4G using Tapatalk

dhMassacre said:
NAND unlock, idiots.
Click to expand...
Click to collapse
Ouch lol
Sent from my HTC EVO using Tapatalk

dhMassacre said:
NAND unlock, idiots.
Click to expand...
Click to collapse
Checking for a bootloader version is the cheap/wrong way to be checking for the ability to write to a partition.
Sent from my PC36100 using XDA App

[Q] Status 7 ??

what does this mean ?? [ assert failed:getprop("ro,product.device") == "maguro" ll getprop("ro.build.product") == "maguro"
E:Error in akop_maguro_build-35.zip (Status 7 )
Any Ideas on what i can do to fix this and what it means?
Any help would be much appreciated!

Are you trying to flash this rom on a non GSM phone?
Sent from my Galaxy Nexus using xda premium

WonkyYew said:
what does this mean ?? [ assert failed:getprop("ro,product.device") == "maguro" ll getprop("ro.build.product") == "maguro"
E:Error in akop_maguro_build-35.zip (Status 7 )
Any Ideas on what i can do to fix this and what it means?
Any help would be much appreciated!
Click to expand...
Click to collapse
Are you sure you downloaded the right version for your phone?
You need the maguro version.
Try download it again and make sure its the maguro version.
If that doesn't work try reflash cwm to the newest version.
---------- Post added at 02:12 AM ---------- Previous post was at 02:11 AM ----------
El Daddy said:
Are you trying to flash this rom on a non GSM phone?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
We don't have cdma in Ireland only GSM.

i downloaded the GSM and didnt work but ill try it again but it's weird cause i used the Android Revolution Wipe and i flashed that and it worked fine but soon went to install Rom it gave me that :S

It could be a bad download too.
Try flashing another version of cwm by fastboot and see of that works if flashing the rom again doesn't work.
What the error is saying is that the zip doesn't match the type of phone you have so either its the wrong version, corrupt download or cwm isn't working properly.
Are you downloading on your computer and the transferring to your phone via USB??

nodstuff said:
We don't have cdma in Ireland only GSM.
Click to expand...
Click to collapse
Sorry. The xda app doesn't show country flags

nodstuff said:
It could be a bad download too.
Try flashing another version of cwm by fastboot and see of that works if flashing the rom again doesn't work.
What the error is saying is that the zip doesn't match the type of phone you have so either its the wrong version, corrupt download or cwm isn't working properly.
Are you downloading on your computer and the transferring to your phone via USB??
Click to expand...
Click to collapse
Turns out it was the CWM after all !! Thanks for the help man much appreciated !!

WonkyYew said:
Turns out it was the CWM after all !! Thanks for the help man much appreciated !!
Click to expand...
Click to collapse
No hassle bud.

[UNOFFICIAL][ROM]Paranoid Android 2.53 BUILD 2[4.1.2][CM10 HYBRID]

DISCLAIMER:
Flash at your own risk
I take no responsibility for what happens to your device
although if some thing goes wrong I will try to help
Hi Everyone!
I compiled Paranoid Android from source for the TF300T!
I decided to share my work
PA has alot of customation options
So check out there website
http://www.paranoid-rom.com/
SOURCES:
https://github.com/ParanoidAndroid
Updated to P.A. version 2.53 for build 2
also I fixed the density/DPI issues on initial boot
I had to edit and add a bunch of code
DOWNLOAD:
pa_tf300t-2.53-03NOV2012-152643 Build 2
WARNING: this is for the JB bootloader only
How to install:
1. reboot to recovery
2. make a nandroid backup
3. wipe data/factory reset
4. wipe cache
5. wipe dalvic cache
6. Install zip from sdcard
7. Choose zip from sdcard
8. flash gapps (optional)
9. reboot and enjoy
Possible Future Plans
init.d scripts
some tweaks
maybe some battery icons
some light theming
Bugs:
GPS wont lock
Possibly more
credits:
XpLoDWilD
timmytim
gokussjx
Paranoid Android
CyanogenMod

Changelog
Code:
Nov. 3
-updated to 2.53
-fixed density issues
Nov. 1
- first build

Can't wait to try this tmrw!
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

This is awesome man, nice work.

Finally new ****. I will test this mother trucker
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Paranoid Android is great on Toro. I'm thinking I'll be upping to the JB bootloader today.
Sent from my Galaxy Nexus using xda premium

gchild320 said:
Paranoid Android is great on Toro. I'm thinking I'll be upping to the JB bootloader today.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I assume I have to flash stock ROM to get jb boot loader right, including the kernel and RE ROOTING?
Sent from my Transformer Pad TF300T using xda app-developers app

diamantericos said:
I assume I have to flash stock ROM to get jb boot loader right, including the kernel and RE ROOTING?
Sent from my Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
yes you would have to flash the latest Asus stock rom you should not have to reroot but you will have to install a recovery
but I recommend using NVflash first

Has anyone tried this?

Drgravy said:
yes you would have to flash the latest Asus stock rom you should not have to reroot but you will have to install a recovery
but I recommend using NVflash first
Click to expand...
Click to collapse
Going to use the Asus hydro method seems simpler I'm lazy this weekend . Then ill just flash this when I'm done.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

New Build is up!
new P.A. version 2.53
also fixed the density issues
let me know what you think

Drgravy said:
New Build is up!
new P.A. version 2.53
also fixed the density issues
let me know what you think
Click to expand...
Click to collapse
About to flash. I'll give feedback soon
Edit
Im having trouble flashing this
E:Error in ' /sdcard/<name of zip>.zip '...
(Status 7)
Error flashing zip ' <name of zip>.zip '
I also had this problem when flashing the latest cm10 nightly.
Can anyone help?
Thanks

RolloJarvis said:
About to flash. I'll give feedback soon
Edit
Im having trouble flashing this
E:Error in ' /sdcard/<name of zip>.zip '...
(Status 7)
Error flashing zip ' <name of zip>.zip '
I also had this problem when flashing the latest cm10 nightly.
Can anyone help?
Thanks
Click to expand...
Click to collapse
What recovery?
Sent from my SGH-T989 using xda app-developers app

I used CWM 6.0.1.4 touch recovery
Which rom are you coming from?
Sent from my MB865 using XDA Premium HD app

What recovery?
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
TWRP for Jelly bean.
Can make backups fine in recovery, just dont seem to be able to flash ROMs. It did let me flash the superuser script in order to root the stock JB rom however...
Here is the exact error from the TWRP log file:
Code:
Installing '/sdcard/Download/paranoid.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
script aborted: assert failed: getprop("ro.product.device") == "tf300t" || getprop("ro.build.product") == "tf300t"
assert failed: getprop("ro.product.device") == "tf300t" || getprop("ro.build.product") == "tf300t"
E:Error in /sdcard/Download/paranoid.zip
(Status 7) Error flashing zip '/sdcard/Download/paranoid.zip'
Updating partition details...
EDIT: im coming from stock rooted. latest JB firmware (WW i think)
I'll try to use a different recovery maybe

RolloJarvis said:
TWRP for Jelly bean.
Can make backups fine in recovery, just dont seem to be able to flash ROMs. It did let me flash the superuser script in order to root the stock JB rom however...
Here is the exact error from the TWRP log file:
Code:
Installing '/sdcard/Download/paranoid.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
script aborted: assert failed: getprop("ro.product.device") == "tf300t" || getprop("ro.build.product") == "tf300t"
assert failed: getprop("ro.product.device") == "tf300t" || getprop("ro.build.product") == "tf300t"
E:Error in /sdcard/Download/paranoid.zip
(Status 7) Error flashing zip '/sdcard/Download/paranoid.zip'
Updating partition details...
EDIT: im coming from stock rooted. latest JB firmware (WW i think)
I'll try to use a different recovery maybe
Click to expand...
Click to collapse
All fine here, 2.53 with TWRP, no issues. US Model

Installed and running fine, other than GPS not working, I noticed that wallpaper changes don't stick after reboot, the tablet reboots to a black screen. Other than that the build is solid and snappy.
Thanks for the work.
Erik
Sent from my Transformer Pad TF300T using Tapatalk 2

Closed as per OP's request.

[Q] Problem - install PAC 4.1.2 or MIUI

Hello, i have Xperia S (26i) rooted. I download and install CWM, copy files of new rom to internal SDcard, reboot in recovery and make all steps, but process stops and error message appears:
assert failed: getprop("ro.product.device") == "LT26i" I I getprop(ro.build.product") == "LT26i" ==getprop(ro.product.device") ==nozomi I I getprop(ro.buil.product) == nozomi
I think the problem is conflict with lt26i and nozomi. It´s correct ? How i do to change ?
Thanks and sorry... my english is very bad..... lol

Is your bootloader unlocked?
Sent from my Xperia S using xda app-developers app

Fastboot advanced stock kernel first then try again
Sent from my JB Xperia S

I have Locked B. But try to install MIUI and error came again, the same.
Using Google i found xda link and resolution is edit build.prop and change "nozomi" to "LT26I". I try to do this :
Unzip ROM, edit build.prop and zip.
But now i have another error. I think MD5 maybe is the key..... I do no if "rom zip file" have signature or other Type of file confirm.....
Sent from my LT26i using xda app-developers app

Nvm.

sr_redhot said:
I have Locked B. But try to install MIUI and error came again, the same.
Using Google i found xda link and resolution is edit build.prop and change "nozomi" to "LT26I". I try to do this :
Unzip ROM, edit build.prop and zip.
But now i have another error. I think MD5 maybe is the key..... I do no if "rom zip file" have signature or other Type of file confirm.....
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
There's your problem, you have a locked bootloader, YOU NEED A UNLOCKED BOOTLOADER to install PAC, I dont know about miui, but anything with custom kernel YOU NEED UNLOCKED BOOTLOADER. So first unlock you bootloader then it should work perfectly fine. You seriously need to read the requirements to install a custom Rom.
Sent from my Xperia S using xda app-developers app

I know if a lot of custom roms needs unlocked bootloader. In PAC V19 i do no, But MIUI are ok with Locked bootloader. I try muiu first, But when error appears i try PAC. Im thinking if i really want to unlock bootloader.....
But thanks for that.
Sent from my LT26i using xda app-developers app

sr_redhot said:
I know if a lot of custom roms needs unlocked bootloader. In PAC V19 i do no, But MIUI are ok with Locked bootloader. I try muiu first, But when error appears i try PAC. Im thinking if i really want to unlock bootloader.....
But thanks for that.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
flash stock rom first.. preferably using flashtool, use fw .50 or below (as long as it's ics one), root it, and install cwm. then u can flash miui.

m1st3r1 said:
flash stock rom first.. preferably using flashtool, use fw .50 or below (as long as it's ics one), root it, and install cwm. then u can flash miui.
Click to expand...
Click to collapse
I try all :
-Format
-unlock BL
-Install FW .55
But the same error appears. I really thing : in some moment custom rom say "nozomi" and my cell say"LT26i" and stopped instalation.
Now i´m downloading more ROMs to testing instalation,

sr_redhot said:
I try all :
-Format
-unlock BL
-Install FW .55
But the same error appears. I really thing : in some moment custom rom say "nozomi" and my cell say"LT26i" and stopped instalation.
Now i´m downloading more ROMs to testing instalation,
Click to expand...
Click to collapse
Updated:
TurboROM installed..... But MIUI and PAC get the same error

WTF. No one ever gave right advice. Wow.
Well, I've got sometimes the same error.
There is one solution:
Unzip installation file.
Delete this line inside META-INF/com/google/android/updater-script:
Code:
assert(getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi");
Then zip this file back to it's place in archive. Try to install, and BOOM - it's fine now!

Dr.Alexander_Breen said:
WTF. No one ever gave right advice. Wow.
Well, I've got sometimes the same error.
There is one solution:
Unzip installation file.
Delete this line inside META-INF/com/google/android/updater-script:
Code:
assert(getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi");
Then zip this file back to it's place in archive. Try to install, and BOOM - it's fine now!
Click to expand...
Click to collapse
I follow you tip,
Download new files from PAC and MIUI
Unzip, make changes, zip, copy to sd reboot into recovery, make all steps in PAC tutorial and nothing done:
"Finding update package
Opening update package
Installing update
Instalation aborted"
I do know what´s gonna hell ........
So hard to do one simple thing.... :crying:

sr_redhot said:
I try all :
-Format
-unlock BL
-Install FW .55
But the same error appears. I really thing : in some moment custom rom say "nozomi" and my cell say"LT26i" and stopped instalation.
Now i´m downloading more ROMs to testing instalation,
Click to expand...
Click to collapse
Try flash advanced kernel first. Then try flash Miui. Wipe all (wipe data, format system and dalvik cache).
I'm in relocked bootloader, using .55 kernel, got no problem flashing miui.maybe u did something wrong in the first steps...
Dr.Alexander_Breen said:
WTF. No one ever gave right advice. Wow.
Well, I've got sometimes the same error.
There is one solution:
Unzip installation file.
Delete this line inside META-INF/com/google/android/updater-script:
Code:
assert(getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi");
Then zip this file back to it's place in archive. Try to install, and BOOM - it's fine now!
Click to expand...
Click to collapse
Is the wtf really necessary? Ofc, I know this solution, but I don't think it is a good solution. As you know this phone is lt26i with nozomi as its codename, and the rom op want to flash is built for lt26i, so in my opinion, it's kinda wrong change something that supposed to be working.
Sent from my LT26i using Tapatalk 2

m1st3r1 said:
Try flash advanced kernel first. Then try flash Miui. Wipe all (wipe data, format system and dalvik cache).
I'm in relocked bootloader, using .55 kernel, got no problem flashing miui.maybe u did something wrong in the first steps...
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
GREAT !!! Now it´s working !!! MIUI installed. And next step is testing PAC.
Tks !!:laugh:

[Q] Status 7, cannot overcome

Hello,
I own the wind variant of the Galaxy SIII Model T-999v
For the last...forever... I have relentlessly been trying to have Cyanogenmod 10.1.2 running on my device
I have taken every precaution, followed every method, read every thread
Lets rule out the basics...
I have:
Made sure CM is of the T-Mobile variant
Updated CWM to the latest version (6.0+) using the .img file available from their webpage and terminal emulator
Flashed the device in CWM prior to trying to install from zip
The phone is rooted and SuperSU is available
Ive tried using the in-fw version of CWM
Ive tried reverting my OS to stock 4.04 (launch date) in odin and rerooting and reapplying the latest bootloader because one thread suggested i should downgrade the baseband version from the one available in jellybean
Ive even used updated the bootloader from the link available in this thread:
http://forum.xda-developers.com/showthread.php?t=2290118
g-apps installs fine, superSU installs fine, everything with the exception of the main piece.
If anybody has any form of input into the matter it would be greatly appreciated. Cheers

Edit the update script to include your bootloader or remove the asserts. The T999v isn't officially supported by 10.1.2.

Aerowinder said:
Edit the update script to include your bootloader or remove the asserts. The T999v isn't officially supported by 10.1.2.
Click to expand...
Click to collapse
I now receive a status 6 error (it's a little humbling to see at least some progress).
The follwing was removed from META-INF->com->google->android->updater-script:
assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo");
assert(getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999VVLDLL1");
Do I need to modify these lines to correspond with my device's bootloader specifically? If so how where I obtain that information?
Thanks

voxmaris said:
I now receive a status 6 error (it's a little humbling to see at least some progress).
The follwing was removed from META-INF->com->google->android->updater-script:
assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo");
assert(getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999VVLDLL1");
Do I need to modify these lines to correspond with my device's bootloader specifically? If so how where I obtain that information?
Thanks
Click to expand...
Click to collapse
Status 6 is syntax error. Means you messed something up If using CWM, there is a show log under advanced. That will tell you what line in the script the syntax error can be found.

Aerowinder said:
Status 6 is syntax error. Means you messed something up If using CWM, there is a show log under advanced. That will tell you what line in the script the syntax error can be found.
Click to expand...
Click to collapse
I: using /data/media for /sdcard/0/clockworkmod/.recovery_version
I: using /data/media for sdcard/clockworkmod/.recovery_version
I: Can't partition non-vfat: datamedia
I: Can't partition non-vfat: auto
I: Can't format unknown volume: /emmc
This is all it spat out after running show log after re-attempting a CM installation.

Did you delete signatures? In the meta-information folder it's the 3 files there.
You could also try TWRP. I don't know about CWM, but TWRPs recovery log often tells you exactly which line and which column (character) it encountered the error.
Also check if you didn't leave a semi colon or something behind when deleting the asserts.
This one does support the T999V, but they haven't changed the script to include the newest boot loader. VLDMF2 I think. DLL1 is the older one.
Sent from my SGH-T999L using XDA Premium 4 mobile app

DocHoliday77 said:
Did you delete signatures? In the meta-information folder it's the 3 files there.
You could also try TWRP. I don't know about CWM, but TWRPs recovery log often tells you exactly which line and which column (character) it encountered the error.
Also check if you didn't leave a semi colon or something behind when deleting the asserts.
This one does support the T999V, but they haven't changed the script to include the newest boot loader. VLDMF2 I think. DLL1 is the older one.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ive deleted the three signature files as well. The error remains identical. I've double checked the assert file and there's no rogue discrepancies between the lines. If the bootloader was previously updated does that mean I wouldn't be able to install cfw?

If the asserts are on the script, and you are on build MF2, then it will not flash. But that's the 7 error.
Try using the original script and replace T999VVLDLL1, with T999VVLDMF2. Check in Settings to make sure I'm remembering the new build number right.
Sent from my SGH-T999L using XDA Premium 4 mobile app
---------- Post added at 06:53 PM ---------- Previous post was at 06:49 PM ----------
You could also try mine. Go to my T999L thread linked in my Sig. Post 6 has the Rom I think you want. When I edited it for the T999L, I also did so for yours.
Sent from my SGH-T999L using XDA Premium 4 mobile app

DocHoliday77 said:
If the asserts are on the script, and you are on build MF2, then it will not flash. But that's the 7 error.
Try using the original script and replace T999VVLDLL1, with T999VVLDMF2. Check in Settings to make sure I'm remembering the new build number right.
Sent from my SGH-T999L using XDA Premium 4 mobile app
---------- Post added at 06:53 PM ---------- Previous post was at 06:49 PM ----------
You could also try mine. Go to my T999L thread linked in my Sig. Post 6 has the Rom I think you want. When I edited it for the T999L, I also did so for yours.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I replaced that line in updater-script that references T999VVLDLL1 with T999VVLLE6, still status 6. It seems that any modification to the zip archive will spit out status 6.

Don't forget to delete the signatures too. But also, check the recovery log. As aerowinder pointed out, 6 is a syntax error. 7 is when it fails the asserts check. So you probably forgot a semi colon, or something like that. Make sure there is no empty first line too. Not sure if it has any effect, but I might.
Also, you may want to update your firmware anyway. LE6 is O.L.D.!
Sent from my SGH-T999L using XDA Premium 4 mobile app

So which one am I carrying then? My baseband is LE6, yet my build is MF2. I've reverted back to jelly bean and the baseband didn't update from LE6.
Sent from my SGH-T999V using XDA Premium 4 mobile app

Oh ok, then you don't want to put LE6 in the asserts. If your build is MF2 you are on the latest. Don't go by the baseband. That's just telling you which build your modem is from.
Sent from my SGH-T999L using XDA Premium 4 mobile app

I changed the last line of code from that sequence to MF2 and removed the three files in meta.inf and still receive the same error.
Sent from my SGH-T999V using XDA Premium 4 mobile app

Ok, did you enter it like this: T999VVLDMF2?
Is it giving you the Status 7 or 6 error?
You can attach your updater-script and I can look at it for you. But also, after flashing, copy log to sd, then attach the log as well.
You are trying to flash CM 10.1.2? Did you try the one in my T999L thread? Its linked in my sig, and is currently at the top of the Q&A section. Post 6 has this ready to flash for you already.

DocHoliday77 said:
Ok, did you enter it like this: T999VVLDMF2?
Is it giving you the Status 7 or 6 error?
You can attach your updater-script and I can look at it for you. But also, after flashing, copy log to sd, then attach the log as well.
You are trying to flash CM 10.1.2? Did you try the one in my T999L thread? Its linked in my sig, and is currently at the top of the Q&A section. Post 6 has this ready to flash for you already.
Click to expand...
Click to collapse
I suspect he is making his edits with Notepad; CRLF instead of LF for new lines. We haven't seen the code, so have no way of knowing for sure. Best guess, though.
You should be using Notepad++ for this job. Anyhow, delete the signature files:
META-INF/com/android - entire folder
META-INF/CERT.RSA
META-INF/CERT.SF
META-INF/MANIFEST.MF
And overwrite the script (META-INF/com/google/android/updater-script) in the archive with this one http://db.tt/RDCDYS0z
Or just flash Doc's. He already repacked it for people not comfortable with editing the packages.

Aerowinder said:
I suspect he is making his edits with Notepad; CRLF instead of LF for new lines. We haven't seen the code, so have no way of knowing for sure. Best guess, though.
You should be using Notepad++ for this job. Anyhow, delete the signature files:
META-INF/com/android - entire folder
META-INF/CERT.RSA
META-INF/CERT.SF
META-INF/MANIFEST.MF
And overwrite the script (META-INF/com/google/android/updater-script) in the archive with this one http://db.tt/RDCDYS0z
Or just flash Doc's. He already repacked it for people not comfortable with editing the packages.
Click to expand...
Click to collapse
Beautiful, it worked. You've both been too awesome, can't thank you enough.